Patent Description:
Long Term Evolution (LTE), <NUM> new radio (NR), and other recently developed communication technologies allow wireless devices to communicate information at data rates (e.g., in terms of Gigabits per second, etc.) that are orders of magnitude greater than what was available just a few years ago.

Today's communication networks are also more secure, resilient to multipath fading, allow for lower network traffic latencies, provide better communication efficiencies (e.g., in terms of bits per second per unit of bandwidth used, etc.). These and other recent improvements have facilitated the emergence of the Internet of Things (IOT), large scale Machine to Machine (M2M) communication systems, autonomous vehicles, and other technologies that rely on consistent and secure communications. "<NPL> discloses key issues and potential solutions for integrity protecting the user plane, including potential enhancements needed to support UP IP up to the full data rate in various combinations as defined in 3GPP TR <NUM>.

Various aspects include methods for supporting user plane integrity protection (UP IP) for communications with a radio access network (RAN). Various aspects may include indicating whether or not a wireless device supports UP IP over Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (eUTRA) by setting one of the Evolved Packet System (EPS) Encryption Algorithm (EEA) or EPS Integrity Algorithm (EIA) bits in the fifth generation (<NUM>) user equipment (UE) security capability information element (IE). In some aspects, the same bit may also be used to indicate that the wireless device supports the same maximum data rate capability for UP IP over eUTRA. Various aspects may include indicating whether or not a wireless device supports UP IP over eUTRA by setting one of the EEA or EIA bits in the fourth generation (<NUM>) S <NUM> UE security capability IE. In some aspects, the same bit may also be used to indicate that the wireless device supports UP IP over New Radio (NR). In some aspects, a different bit in the <NUM> S <NUM> UE security capability IE may indicate that the wireless device supports UP IP over NR.

Various aspects may include determining whether a wireless device supports UP IP for eUTRA connections established between the wireless device and a RAN, generating a first security capability information element including a first UP IP support indication, wherein the first UP IP support indication indicates whether the wireless device supports UP IP for eUTRA connections established between the wireless device and the RAN, and sending the first security capability information element to a base station. In some aspects, the first UP IP support indication may be a bit setting in the first security capability information element. In some aspects, the first security capability information element may be a S <NUM> UE security capability. In various aspects, a UP IP support indication may indicate support of UP IP with one or more algorithms.

Various aspects may further include generating a second security capability information element including a second UP IP support UE equipment computing device supports UP IP for eUTRA connections established between the wireless device and the RAN or UP IP for NR connections established between the wireless device and the RAN; and sending the second security capability information element to the base station. In some aspects, the second UP IP support indication may be a bit setting in the second security capability information element. In some aspects, the second security capability information element may be a <NUM> UE security capability.

Various aspects may further include determining whether the wireless device supports UP IP for NR connections established between the wireless device and a RAN, wherein generating the first security capability information element including the first UP IP support indication may include generating the first security capability information element including the first UP IP support indication and a third UP IP support indication, wherein the third UP IP support indication indicates whether the wireless device supports UP IP for NR connections established between the wireless device and the RAN. In some aspects, the third UP IP support indication may be another bit setting in the first security capability information element.

Various aspects may include receiving a security capability information element at a processor of a network computing device of a wireless device, the security capability information element including a UP IP support indication, and determining whether the security capability information element indicates that the wireless device supports UP IP for eUTRA connections established with the wireless device based at least in part on the UP IP support indication. In some aspects, the UP IP support indication may be a bit setting in the security capability information element. In some aspects, the security capability information element may be a S <NUM> UE security capability or a <NUM> UE security capability. Various aspects may further include determining whether the security capability information element indicates that the wireless device supports UP IP for NR connections established with the wireless device. In some aspects, the UP IP support indication may indicate whether the UP IP is supported for NR connections. In some aspects, the security capability information element may include another UP IP support indication that indicates whether the UP IP is supported for NR connections. In some aspects, the other UP IP support indication may be another bit setting in the security capability information element. In various aspects, a UP IP support indication may indicate support of UP IP with one or more algorithms.

In some aspects, the RAN may be a <NUM> RAN or a <NUM> RAN. In some aspects, the RAN may be connected to an Evolved Packet Core (EPC) network or a Next Generation Core (NGC) network. In some aspects, the base station may be an enode B (eNB) or a next generation-eNB (ng-eNB). In some aspects, the UP IP support indication may be delivered to one type of core network and may be used when the wireless device moves to another type of core network.

Further aspects may include a wireless device having a processor configured to perform one or more operations of the methods summarized above. Further aspects may include a non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a processor of a wireless device to perform operations of the methods summarized above. Further aspects include a wireless device having means for performing functions of the methods summarized above. Further aspects include a system on chip for use in a wireless device that includes a processor configured to perform one or more operations of the methods summarized above. Further aspects include a system in a package that includes two systems on chip for use in a wireless device that includes a processor configured to perform one or more operations of the methods summarized above. Further aspects may include a network computing device having a processor configured to perform one or more operations of the methods summarized above. Further aspects may include a non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a processor of a network computing device to perform operations of the methods summarized above. Further aspects include a network computing device having means for performing functions of the methods summarized above.

Various embodiments will be described in detail with reference to the accompanying drawings. References made to particular examples and implementations are for illustrative purposes, and are not intended to limit the scope of the claims.

Various aspects include methods for supporting user plane integrity protection (UP IP) for communications with a radio access network (RAN). Support for UP IP may enable wireless devices and/or network computing devices to detect that user plane data has been modified in transit. Detection of modifications to user plane data may improve network and/or wireless device security.

The terms "wireless device" or "computing device" are used interchangeably herein to refer to any one or all of wireless router devices, wireless appliances, cellular telephones, smartphones, portable computing devices, personal or mobile multi-media players, laptop computers, tablet computers, smartbooks, ultrabooks, palmtop computers, wireless electronic mail receivers, multimedia Internet-enabled cellular telephones, medical devices and equipment, biometric sensors/devices, wearable devices including smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart rings, smart bracelets, etc.), entertainment devices (e.g., wireless gaming controllers, music and video players, satellite radios, etc.), wireless-network enabled Internet of Things (IoT) devices including smart meters/sensors, industrial manufacturing equipment, large and small machinery and appliances for home or enterprise use, wireless communication elements within autonomous and semiautonomous vehicles, wireless devices affixed to or incorporated into various mobile platforms, global positioning system devices, and similar electronic devices that include a memory, wireless communication components and a programmable processor.

The term "system in a package" (SIP) may be used herein to refer to a single module or package that contains multiple resources, computational units, cores and/or processors on two or more IC chips, substrates, or SOCs. For example, a SIP may include a single substrate on which multiple IC chips or semiconductor dies are stacked in a vertical configuration. Similarly, the SIP may include one or more multichip modules (MCMs) on which multiple ICs or semiconductor dies are packaged into a unifying substrate. A SIP may also include multiple independent SOCs coupled together via high speed communication circuitry and packaged in close proximity, such as on a single motherboard or in a single wireless device. The proximity of the SOCs facilitates high speed communications and the sharing of memory and resources.

The term "multicore processor" may be used herein to refer to a single integrated circuit (IC) chip or chip package that contains two or more independent processing cores (e.g., CPU Core, Internet protocol (IP) Core, graphics processor unit (GPU) Core, etc.) configured to read and execute program instructions. A SOC may include multiple multicore processors, and each processor in an SOC may be referred to as a Core. The term "multiprocessor" may be used herein to refer to a System or device that includes two or more processing units configured to read and execute program instructions.

Various embodiments are described herein using the term "server" to refer to any computing device capable of functioning as a server, such as a master exchange server, web server, mail server, document server, content server, or any other type of server. A server may be a dedicated computing device or a computing device including a server module (e.g., running an application that may cause the computing device to operate as a server). A server module (e.g., server application) may be a full function server module, or a light or secondary server module (e.g., light or secondary server application) that is configured to provide synchronization services among the dynamic databases on receiver devices. A light server or secondary server may be a slimmed-down version of server-type functionality that can be implemented on a receiver device thereby enabling it to function as an Internet server (e.g., an enterprise e-mail server) only to the extent necessary to provide the functionality described herein.

User plane integrity protection allows a network operator's computing devices and a wireless device (e.g., user equipment (UE) computing device) to detect that user plane data has been modified in transit between each other. Integrity protection on the user plane over at least the radio interface is currently available for a fifth generation (<NUM>) access network with a <NUM> core but not for a Long Term Evolution (LTE) access network with an Evolved Packet Core (EPCs) or LTE with a <NUM> core. Integrity protection is currently specified for the control plane to protect signaling messages, but is only currently specified partially for the <NUM> user plane. There are various options for how <NUM> and fourth generation (<NUM>) technologies can be implemented together, for example, Option <NUM> - Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (eUTRA) with EPC, Option <NUM> - new radio (NR) standalone with a <NUM> Core, Option <NUM> - EPC based Dual Connectivity of eUTRA and NR radio access technology (RAT), Option <NUM> - <NUM> core based Dual Connectivity (NR master - eUTRA secondary), Option <NUM> - <NUM> core with eUTRA, and Option <NUM> - <NUM> core based Dual Connectivity (eUTRA master - NR secondary). Thus, supporting user plane integrity protection (UP IP) in different various options for <NUM> and <NUM> implementations may be beneficial.

<NUM> wireless device support of UP IP over NR is signalled to the 5GC network using a user equipment (UE) security capability information element (IE) during wireless device registration to a <NUM> system. Section <NUM>. <NUM> of 3rd Generation Partnership Project (3GPP) Technical Specification (TS) (3GPP TS) <NUM> describes the UE security capability IE for <NUM> systems. The UE security capability IE indicates the supported NR integrity protection algorithms for NR and the integrity protection algorithms for eUTRA. Fourth generation (<NUM>) UE security capability, such as Evolved Packet System (EPS) UE security capability, is indicated to the network using a separate IE in <NUM> systems, referred to as the S1 UE security capability IE in <NUM> systems, and similar IEs are used when the wireless device registers to EPS and are defined in sections <NUM>. <NUM> and <NUM>. <NUM> of 3GPP TS <NUM>. As discussed herein, the IEs used when registering to EPS are referred to as the <NUM> S1 UE security capability IE.

Various embodiments may enable a separate indication of UP IP support over eUTRA to a network. In various embodiments, the separate indication of UP IP support over eUTRA may be in addition to signaling of <NUM> wireless device support of UP IP over NR in <NUM> systems. In various embodiments, the separate indication of UP IP support over eUTRA may be indicated when the wireless device starts supporting UP IP over eUTRA. Various embodiments may enable a wireless device to indicate support for UP IP over eUTRA when the wireless device is connecting to a <NUM> Core (5GC) via a base station in a <NUM> radio access network (RAN), such as a next generation-eNB (ng-eNB). Various embodiments may enable a wireless device to indicate support for UP IP over eUTRA when the wireless device is connecting to a <NUM> core network, such as an EPC, via a base station of a <NUM> RAN, such as an enode B (eNB). Various embodiments may enable a wireless device to indicate support for UP IP over eUTRA, as well as NR, when the wireless device is connecting to a <NUM> core network, such as an EPC, via a base station of a <NUM> RAN, such as an eNB. In some embodiments, a UP IP support indication may be delivered to one type of core network (e.g., an EPC or a 5GC), but may be used when the wireless device moves to another type of core network (e.g., an EPC or a 5GC).

Various embodiments include methods for supporting user plane integrity protection (UP IP) for communications with a radio access network (RAN). Various embodiments may include indicating whether or not a wireless device supports UP IP over eUTRA by setting one of the unused or spare Evolved Packet System (EPS) Encryption Algorithm (EEA) or EPS Integrity Algorithm (EIA) bits in the <NUM> UE security capability IE. In some embodiments, the same bit may also be used to indicate that the wireless device supports the same maximum data rate capability for UP IP over eUTRA. Various embodiments may include indicating whether or not a wireless device supports UP IP over eUTRA by setting one of the unused or spare EEA or EIA bits in the <NUM> S <NUM> UE security capability IE. In some embodiments, the same bit may also be used to indicate that the wireless device supports UP IP over New Radio (NR). In some embodiments, a different bit in the <NUM> S <NUM> UE security capability IE may indicate that the wireless device supports UP IP over NR. Indicating whether or not a wireless device supports UP IP over eUTRA by setting one of the unused or spare bits in the <NUM> UE security capability IE and/or <NUM> S <NUM> UE security capability IE may enable the wireless device to interact with legacy <NUM> RAN nodes, such as legacy eNBs, that do not support UP IP. For example, legacy <NUM> RAN nodes may ignore the unused or spare bits in the <NUM> UE security capability IE and/or <NUM> S <NUM> UE security capability IE. In this manner, various embodiments may enable a wireless device to transition between legacy <NUM> RAN nodes and <NUM> RAN and <NUM> RAN nodes that do support UP IP without determining the state of UP IP support of any specific RAN node to which the wireless device may connect.

<FIG> is a system block diagram illustrating an example communication system <NUM> suitable for implementing any of the various embodiments. The communications system <NUM> may be a Fifth Generation (<NUM>) New Radio (NR) network, or any other suitable network such as an LTE network, <NUM> network, etc. While <FIG> illustrates a <NUM> network, later generation networks may include the same or similar elements. Therefore, the reference to a <NUM> network and <NUM> network elements in the following descriptions is for illustrative purposes and is not intended to be limiting.

The communications system <NUM> may include a heterogeneous network architecture that includes a core network <NUM> and a variety of mobile devices (also referred to as user equipment (UE) computing devices) (illustrated as wireless device 120a-120e in <FIG>). The communications system <NUM> may also include a number of base stations (illustrated as the BS 110a, the BS 110b, the BS 110c, and the BS 110d) and other network entities. A base station is an entity that communicates with wireless devices (mobile devices or UEs), and also may be referred to as an NodeB, a Node B, an LTE evolved nodeB (eNB), an Access point (AP), a radio head, a transmit receive point (TRP), a New Radio base station (NR BS), a <NUM> NodeB (NB), a Next Generation NodeB (gNB), or the like. Each base station may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to a coverage area of a base station, a base station subsystem serving this coverage area, or a combination thereof, depending on the context in which the term is used.

A base station <NUM>10a-<NUM>10d may provide communication coverage for a macro cell, a pico cell, a femto cell, another type of cell, or a combination thereof. A macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by mobile devices with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by mobile devices with service subscription. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by mobile devices having association with the femto cell (for example, mobile devices in a closed subscriber group (CSG)). A base station for a macro cell may be referred to as a macro BS. A base station for a pico cell may be referred to as a pico BS. A base station for a femto cell may be referred to as a femto BS or a home BS. In the example illustrated in <FIG>, a base station 110a may be a macro BS for a macro cell 102a, a base station 110b may be a pico BS for a pico cell 102b, and a base station 110c may be a femto BS for a femto cell 102c. A base station 110a-110d may support one or multiple (for example, three) cells.

In some examples, a cell may not be stationary, and the geographic area of the cell may move according to the location of a mobile base station. In some examples, the base stations 110a-110d may be interconnected to one another as well as to one or more other base stations or network nodes (not illustrated) in the communications system <NUM> through various types of backhaul interfaces, such as a direct physical connection, a virtual network, or a combination thereof using any suitable transport network.

The base station 110a-110d may communicate with the core network <NUM> over a wired or wireless communication link <NUM>. The wireless device 120a-120e (UE computing device) may communicate with the base station 110a-110d over a wireless communication link <NUM>.

The communications system <NUM> also may include relay stations (e.g., relay BS 110d). A relay station is an entity that can receive a transmission of data from an upstream station (for example, a base station or a mobile device) and send a transmission of the data to a downstream station (for example, a wireless device or a base station). A relay station also may be a mobile device that can relay transmissions for other wireless devices. In the example illustrated in <FIG>, a relay station 110d may communicate with macro the base station 110a and the wireless device 120d in order to facilitate communication between the base station 110a and the wireless device 120d. A relay station also may be referred to as a relay base station, a relay base station, a relay, etc..

The wireless devices (UE computing devices) 120a, 120b, 120c may be dispersed throughout communications system <NUM>, and each wireless device may be stationary or mobile. A wireless device also may be referred to as an access terminal, a UE, a terminal, a mobile station, a subscriber unit, a station, etc..

A macro base station 110a may communicate with the communication network <NUM> over a wired or wireless communication link <NUM>. The wireless devices 120a, 120b, 120c may communicate with a base station 110a-110d over a wireless communication link <NUM>.

The wireless communication links <NUM>, <NUM> may include a plurality of carrier signals, frequencies, or frequency bands, each of which may include a plurality of logical channels. The wireless communication links <NUM> and <NUM> may utilize one or more radio access technologies (RATs). Examples of RATs that may be used in a wireless communication link include 3GPP LTE, <NUM>, <NUM>, <NUM> (e.g., NR), GSM, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMAX), Time Division Multiple Access (TDMA), and other mobile telephony communication technologies cellular RATs. Further examples of RATs that may be used in one or more of the various wireless communication links <NUM>, <NUM> within the communication system <NUM> include medium range protocols such as Wi-Fi, LTE-U, LTE-Direct, LAA, MuLTEfire, and relatively short range RATs such as ZigBee, Bluetooth, and Bluetooth Low Energy (LE).

For example, the spacing of the subcarriers may be <NUM> and the minimum resource allocation (called a "resource block") may be <NUM> subcarriers (or <NUM>). Consequently, the nominal Fast File Transfer (FFT) size may be equal to <NUM>, <NUM>, <NUM>, <NUM> or <NUM> for system bandwidth of <NUM>, <NUM>, <NUM>, <NUM> or <NUM> megahertz (MHz), respectively. For example, a subband may cover <NUM> (i.e., <NUM> resource blocks), and there may be <NUM>, <NUM>, <NUM>, <NUM> or <NUM> subbands for system bandwidth of <NUM>, <NUM>, <NUM>, <NUM> or <NUM>, respectively.

While descriptions of some embodiments may use terminology and examples associated with LTE technologies, various embodiments may be applicable to other wireless communications systems, such as a new radio (NR) or <NUM> network. NR may utilize OFDM with a cyclic prefix (CP) on the uplink (UL) and downlink (DL) and include support for half-duplex operation using time division duplex (TDD). A single component carrier bandwidth of <NUM> may be supported. NR resource blocks may span <NUM> sub-carriers with a sub-carrier bandwidth of <NUM> over a <NUM> duration. Each radio frame may consist of <NUM> subframes with a length of <NUM>. Consequently, each subframe may have a length of <NUM>. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission and the link direction for each subframe may be dynamically switched. Each subframe may include DL/UL data as well as DL/UL control data. Multiple Input Multiple Output (MIMO) transmissions with precoding may also be supported. MIMO configurations in the DL may support up to eight transmit antennas with multi-layer DL transmissions up to eight streams and up to two streams per wireless device. Multi-layer transmissions with up to <NUM> streams per wireless device may be supported. Aggregation of multiple cells may be supported with up to eight serving cells. Alternatively, NR may support a different air interface, other than an OFDM-based air interface.

Some mobile devices may be considered machine-type communication (MTC) or Evolved or enhanced machine-type communication (eMTC) mobile devices. MTC and eMTC mobile devices include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with a base station, another device (for example, remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (for example, a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some mobile devices may be considered Internet-of Things (IoT) devices or may be implemented as NB-IoT (narrowband internet of things) devices. A wireless device 120a-e may be included inside a housing that houses components of the wireless device, such as processor components, memory components, similar components, or a combination thereof.

In some implementations, two or more mobile devices 120a-e (for example, illustrated as the wireless device 120a and the wireless device 120e) may communicate directly using one or more sidelink channels <NUM> (for example, without using a base station <NUM> as an intermediary to communicate with one another). For example, the wireless devices 120a-e may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or similar protocol), a mesh network, or similar networks, or combinations thereof. In this case, the wireless device 120a-e may perform scheduling operations, resource selection operations, as well as other operations described elsewhere herein as being performed by the base station 110a.

In general, any number of communications systems and any number of wireless networks may be deployed in a given geographic area. Each communications system and wireless network may support a particular RAT and may operate on one or more frequencies. A RAT also may be referred to as a radio technology, an air interface, etc. A frequency also may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area in order to avoid interference between communications systems of different RATs. In some cases, <NUM>/LTE and/or <NUM>/NR RAT networks may be deployed. For example, a <NUM> non-standalone (NSA) network may utilize both <NUM>/LTE RAT in the <NUM>/LTE RAN side of the <NUM> NSA network and <NUM>/NR RAT in the <NUM>/NR RAN side of the <NUM> NSA network. The <NUM>/LTE RAN and the <NUM>/NR RAN may both connect to one another and a <NUM>/LTE core network (e.g., an evolved packet core (EPC) network) in a <NUM> NSA network. Other example network configurations may include a <NUM> standalone (SA) network in which a <NUM>/NR RAN connects to a <NUM> core network.

For example, <NUM> and <NUM> technologies may be deployed together. As specific examples, <FIG> illustrate various deployment options for <NUM> and <NUM> RAN connections to a <NUM> core network and <FIG> illustrate various deployment options for <NUM> and <NUM> RAN connections to a <NUM> core network.

With reference to <FIG>, as shown in <FIG>, example LTE/NR EPC connection deployment options may include Option <NUM> - a standalone LTE RAN including a base station, such as an eNB <NUM> (e.g., a base station 110a-d), connected to an EPC <NUM> (e.g., core network <NUM>). The EPC <NUM> may include a mobility management entity (MME) server <NUM> and a packet data network and serving gateway (P/SGW) server <NUM>. A wireless device <NUM> (e.g., wireless device 120a-120e) may connect to the eNB <NUM> and send/receive user plane data to the eNB <NUM> which may send/receive the user plane data to the EPC <NUM> via the S1-U interface with the P/SGW server <NUM>. As shown in <FIG>, example LTE/NR EPC connection deployment options may include Option <NUM> - Master Cell Group (MCG) split bearer with a non-standalone LTE anchor connected to the EPC <NUM>. In such a deployment, a master base station, such as a master eNB (MeNB) <NUM> (e.g., base station 110a-110d) may control a secondary gNB (SgNB) <NUM> (e.g., 110a-110d). The MeNB <NUM> may connect to the SgNB <NUM> and may provide the connection for the SgNB <NUM> to the EPC <NUM>. The wireless device <NUM> may connect to the MeNB <NUM> or the SgNB <NUM> and send/receive user plane data to the MeNB <NUM> or the SgNB <NUM>. The SgNB <NUM> may send/receive user plane data from the MeNB <NUM> via the X2-U interface. The MeNB <NUM> may send/receive user plane data to the EPC <NUM> via the S1-U interface with the P/SGW server <NUM>. As shown in <FIG>, example LTE/NR EPC connection deployment options may include Option 3a - Secondary Cell Group (SCG) bearer with a non-standalone LTE anchor connected to the EPC <NUM>. In such a deployment, the SgNB <NUM> may connect to the EPC <NUM>. The wireless device <NUM> may connect to the SgNB <NUM> and send/receive user plane data to the SgNB <NUM>, which may send/receive the user plane data to the EPC <NUM> via the S1-U interface with the P/SGW server <NUM>. As shown in <FIG>, example LTE/NR EPC connection deployment options may include Option 3x - SCG split bearer with a non-standalone LTE anchor connected to the EPC <NUM>. The SgNB <NUM> may connect to the MeNB <NUM> and may provide the connection for the MeNB <NUM> to the EPC <NUM>. The wireless device <NUM> may connect to the MeNB <NUM> or the SgNB <NUM> and send/receive user plane data to the MeNB <NUM> or the SgNB <NUM>. The MeNB <NUM> may send/receive user plane data from the SgNB <NUM> via the X2-U interface. The SgNB <NUM> may send/receive user plane data to the EPC <NUM> via the S1-U interface with the P/SGW server <NUM>.

As shown in <FIG>, example LTE/NR 5GC connection deployment options may include Option <NUM> - a standalone LTE RAN including a base station, such as an eNB <NUM> (e.g., a base station 110a-d) connected to a next generation core (NGC) <NUM> (e.g., core network <NUM>). In such deployments, the eNB <NUM> may be an enhanced LTE (eLTE) base station configured to connect a 5GC, such as NGC <NUM>. The EPC <NUM> may include a control plane function (CPF) server <NUM> and a user plane function (UPF) server <NUM>. The wireless device <NUM> (e.g., wireless device 120a-e) may connect to the eNB <NUM> and send/receive user plane data to the eNB <NUM> which may send/receive the user plane data to the NGC <NUM> via the N3 interface with the UPF server <NUM>. As shown in <FIG>, example LTE/NR 5GC connection deployment options may include Option <NUM> -MCG split bearer with a non-standalone LTE anchor connected to the NGC <NUM>. In such a deployment, a master base station, such as a MeNB <NUM> (e.g., base station 110a-110d) may control the SgNB <NUM> (e.g., 110a-110d). In such deployments, the MeNB <NUM> may be an eLTE base station configured to connect a 5GC, such as NGC <NUM>. The MeNB <NUM> may connect to the SgNB <NUM> and may provide the connection for the SgNB <NUM> to the NGC <NUM>. The wireless device <NUM> may connect to the MeNB <NUM> or the SgNB <NUM> and send/receive user plane data to the MeNB <NUM> or the SgNB <NUM>. The SgNB <NUM> may send/receive user plane data from the MeNB <NUM> via the Xn interface. The MeNB <NUM> may send/receive user plane data to the NGC <NUM> via the N3 interface with the UPF server <NUM>. As shown in <FIG>, example LTE/NR 5GC connection deployment options may include Option 7a -SCG bearer with a non-standalone LTE anchor connected to the NGC <NUM>. In such a deployment, the SgNB <NUM> may connect to the NGC <NUM>. The wireless device <NUM> may connect to the SgNB <NUM> and send/receive user plane data to the SgNB <NUM>, which may send/receive the user plane data to the NGC <NUM> via the N3 interface with the UPF server <NUM>. As shown in <FIG>, example LTE/NR 5GC connection deployment options may include Option 7x - SCG split bearer with a non-standalone LTE anchor connected to the NGC <NUM>. The SgNB <NUM> may connect to the MeNB <NUM> and may provide the connection for the MeNB <NUM> to the NGC <NUM>. The wireless device <NUM> may connect to the MeNB <NUM> or the SgNB <NUM> and send/receive user plane data to the MeNB <NUM> or the SgNB <NUM>. The MeNB <NUM> may send/receive user plane data from the SgNB <NUM> via the Xn interface. The SgNB <NUM> may send/receive user plane data to the NGC <NUM> via the N3 interface with the UPF server <NUM>.

The deployment options illustrated in <FIG> are merely examples of deployment options and other deployment options exist. The example deployment options illustrated in <FIG>, as well as other deployment options, may be used with the various embodiments.

<FIG> is a component block diagram illustrating an example computing and wireless modem system <NUM> suitable for implementing any of the various embodiments. Various embodiments may be implemented on a number of single processor and multiprocessor computer systems, including a system-on-chip (SOC) or system in a package (SIP).

With reference to <FIG>, the illustrated example wireless device <NUM> (which may be a SIP in some embodiments) includes a two SOCs <NUM>, <NUM> coupled to a clock <NUM>, a voltage regulator <NUM>, and a wireless transceiver <NUM> configured to send and receive wireless communications via an antenna (not shown) to/from network wireless devices, such as a base station 110a. In some embodiments, the first SOC <NUM> operate as central processing unit (CPU) of the wireless device that carries out the instructions of software application programs by performing the arithmetic, logical, control and input/output (I/O) operations specified by the instructions. In some embodiments, the second SOC <NUM> may operate as a specialized processing unit. For example, the second SOC <NUM> may operate as a specialized <NUM> processing unit responsible for managing high volume, high speed (e.g., <NUM> Gbps, etc.), and/or very high frequency short wave length (e.g., <NUM> mmWave spectrum, etc.) communications.

The first SOC <NUM> may include a digital signal processor (DSP) <NUM>, a modem processor <NUM>, a graphics processor <NUM>, an application processor (AP) <NUM>, one or more coprocessors <NUM> (e.g., vector co-processor) connected to one or more of the processors, memory <NUM>, custom circuity <NUM>, system components and resources <NUM>, an interconnection/bus module <NUM>, one or more temperature sensors <NUM>, a thermal management unit <NUM>, and a thermal power envelope (TPE) component <NUM>. The second SOC <NUM> may include a <NUM> modem processor <NUM>, a power management unit <NUM>, an interconnection/bus module <NUM>, the plurality of mmWave transceivers <NUM>, memory <NUM>, and various additional processors <NUM>, such as an applications processor, packet processor, etc..

The first and second SOC <NUM>, <NUM> may include various system components, resources and custom circuitry for managing sensor data, analog-to-digital conversions, wireless data transmissions, and for performing other specialized operations, such as decoding data packets and processing encoded audio and video signals for rendering in a web browser. For example, the system components and resources <NUM> of the first SOC <NUM> may include power amplifiers, voltage regulators, oscillators, phase-locked loops, peripheral bridges, data controllers, memory controllers, system controllers, access ports, timers, and other similar components used to support the processors and software clients running on a wireless device. The system components and resources <NUM> and/or custom circuitry <NUM> may also include circuitry to interface with peripheral devices, such as cameras, electronic displays, wireless communication devices, external memory chips, etc..

The first and second SOC <NUM>, <NUM> may communicate via interconnection/bus module <NUM>. The various processors <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, may be interconnected to one or more memory elements <NUM>, system components and resources <NUM>, and custom circuitry <NUM>, and a thermal management unit <NUM> via an interconnection/bus module <NUM>. Similarly, the processor <NUM> may be interconnected to the power management unit <NUM>, the mmWave transceivers <NUM>, memory <NUM>, and various additional processors <NUM> via the interconnection/bus module <NUM>. The interconnection/bus module <NUM>, <NUM>, <NUM> may include an array of reconfigurable logic gates and/or implement a bus architecture (e.g., CoreConnect, AMBA, etc.). Communications may be provided by advanced interconnects, such as high-performance networks-on chip (NoCs).

The first and/or second SOCs <NUM>, <NUM> may further include an input/output module (not illustrated) for communicating with resources external to the SOC, such as a clock <NUM>, a voltage regulator <NUM>, and one or more wireless transceivers <NUM>. Resources external to the SOC (e.g., clock <NUM>, voltage regulator <NUM>) may be shared by two or more of the internal SOC processors/cores.

In addition to the example SIP <NUM> discussed above, various embodiments may be implemented in a wide variety of computing systems, which may include a single processor, multiple processors, multicore processors, or any combination thereof.

<FIG> illustrates an example of a software architecture <NUM> including a radio protocol stack for the user and control planes in wireless communications between a base station <NUM> (e.g., the base station 110a-110d, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) and a wireless device (also referred to as a UE or UE computing device) <NUM> (e.g., the wireless device 120a-120e, <NUM>, <NUM>).

With reference to <FIG>, the wireless device <NUM> may implement the software architecture <NUM> to communicate with the base station <NUM> of a communication system (e.g., <NUM>). In various embodiments, layers in software architecture <NUM> may form logical connections with corresponding layers in software of the base station <NUM>. The software architecture <NUM> may be distributed among one or more processors (e.g., the processors <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>). While illustrated with respect to one radio protocol stack, in a multi-SIM (subscriber identity module) wireless device, the software architecture <NUM> may include multiple protocol stacks, each of which may be associated with a different SIM (e.g., two protocol stacks associated with two SIMs, respectively, in a dual-SIM wireless communication device). While described below with reference to LTE communication layers, the software architecture <NUM> may support any of variety of standards and protocols for wireless communications, and/or may include additional protocol stacks that support any of variety of standards and protocols wireless communications.

The software architecture <NUM> may include a Non-Access Stratum (NAS) <NUM> and an Access Stratum (AS) <NUM>. The NAS <NUM> may include functions and protocols to support Packet filtering, security management, mobility control, session management, and traffic and signaling between a SIM(s) of the wireless device (e.g., SIM(s) <NUM>) and its core network <NUM>. The AS <NUM> may include functions and protocols that support communication between a SIM(s) (e.g., SIM(s) <NUM>) and entities of supported access networks (e.g., a base station). In particular, the AS <NUM> may include at least three layers (Layer <NUM>, Layer <NUM>, and Layer <NUM>), each of which may contain various sub-layers.

In the user and control planes, Layer <NUM> (L1) of the AS <NUM> may be a physical layer (PHY) <NUM>, which may oversee functions that enable transmission and/or reception over the air interface. Examples of such physical layer <NUM> functions may include cyclic redundancy check (CRC) attachment, coding blocks, scrambling and descrambling, modulation and demodulation, signal measurements, MIMO, etc. The physical layer may include various logical channels, including the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH).

In the user and control planes, Layer <NUM> (L2) of the AS <NUM> may be responsible for the link between the wireless device <NUM> and the base station <NUM> over the physical layer <NUM>. In the various embodiments, Layer <NUM> may include a media access control (MAC) sublayer <NUM>, a Radio link control (RLC) sublayer <NUM>, and a Packet data convergence protocol (PDCP) <NUM> sublayer, each of which form logical connections terminating at the base station <NUM>.

In the control plane, Layer <NUM> (L3) of the AS <NUM> may include a Radio resource control (RRC) sublayer <NUM>. While not shown, the software architecture <NUM> may include additional Layer <NUM> sublayers, as well as various upper layers above Layer <NUM>. In various embodiments, the RRC sublayer <NUM> may provide functions including broadcasting system information, paging, and establishing and releasing an RRC signaling connection between the wireless device <NUM> and the base station <NUM>.

In various embodiments, the PDCP sublayer <NUM> may provide uplink functions including multiplexing between different Radio bearers and logical channels, sequence number addition, handover data handling, integrity protection, ciphering, and header compression. In the downlink, the PDCP sublayer <NUM> may provide functions that include in-sequence delivery of data packets, duplicate data Packet detection, integrity validation, deciphering, and header decompression.

In the uplink, MAC sublayer <NUM> may provide functions including multiplexing between logical and transport channels, random access procedure, logical channel priority, and hybrid-ARQ (HARQ) operations. In the downlink, the MAC layer functions may include channel mapping within a cell, de-multiplexing, discontinuous reception (DRX), and HARQ operations.

While the software architecture <NUM> may provide functions to transmit data through physical media, the software architecture <NUM> may further include at least one host layer <NUM> to provide data transfer services to various applications in the wireless device <NUM>. In some embodiments, application-specific functions provided by the at least one host layer <NUM> may provide an interface between the software architecture and the general purpose processor <NUM>.

In other embodiments, the software architecture <NUM> may include one or more higher logical layer (e.g., transport, session, presentation, application, etc.) that provide host layer functions. For example, in some embodiments, the software architecture <NUM> may include a network layer (e.g., IP layer) in which a logical connection terminates at a Packet data network (PDN) gateway (PGW). In some embodiments, the software architecture <NUM> may include an application layer in which a logical connection terminates at another device (e.g., end user device, server, etc.). In some embodiments, the software architecture <NUM> may further include in the AS <NUM> a hardware interface <NUM> between the physical layer <NUM> and the communication hardware (e.g., one or more Radio frequency (RF) transceivers).

<FIG> is a component block diagram illustrating a system <NUM> for supporting user plane integrity protection (UP IP) for communications with a RAN in accordance with various embodiments. In some embodiments, system <NUM> may include one or more computing platforms <NUM> and/or one or more remote platforms <NUM>. With reference to <FIG>, computing platform(s) <NUM> may include a base station (e.g., the base station 110a-110e, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) and/or a wireless device (e.g., the wireless device 120a-120e, <NUM>, <NUM>, <NUM>). Remote platform(s) <NUM> may include a base station (e.g., the base station 110a-110e, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) and/or a wireless device (e.g., the wireless device 120a-120e, <NUM>, <NUM>, <NUM>).

Computing platform(s) <NUM> may include processors <NUM> configured by machine-readable instructions <NUM>. Machine-readable instructions <NUM> may include one or more instruction modules. The instruction modules may include computer program modules. The instruction modules may include one or more of user equipment (UE) computing device determination module <NUM>, security capability IE generating module <NUM>, security capability IE sending module <NUM>, security capability IE receiving module <NUM>, security capability IE determination module <NUM>, and/or other instruction modules.

UE computing device determination module <NUM> may be configured to determine whether the wireless device supports UP IP for eUTRA connections established between the wireless device and a RAN. In various embodiments, determining whether the wireless device supports UP IP for eUTRA may include checking a capability setting of the wireless device. User equipment computing device determination module <NUM> may be configured to determine whether the wireless device supports UP IP for NR connections established between the wireless device and a RAN. In various embodiments, determining whether the wireless device supports UP IP for NR connections may include checking a capability setting of the wireless device.

Security capability IE generating module <NUM> may be configured to generate one or more security capability IEs including a one or more UP IP support indications. The UP IP support indications may be bit settings in the security capability IEs. For example, a security capability IE may be a <NUM> UE security capability IE or may be a S <NUM> UE security capability IE. The UP IP support indication may indicate whether the wireless device supports UP IP for eUTRA connections established between the wireless device and the RAN and/or whether the wireless device supports UP IP for NR connections established between the wireless device and the RAN. The UP IP support indication may indicate UP IP support with several integrity algorithms. The first UP IP support indication may be a setting of one of the Evolved Packet System (EPS) Encryption Algorithm (EEA) or EPS Integrity Algorithm (EIA) bits in the <NUM> UE security capability IE or the S <NUM> UE security capability IE. In various embodiments, more than one security capability IE may be generated by the security capability IE generating module <NUM>. For example, a first security capability IE and a second security capability IE may be generated. As a specific example, the first security capability IE may be a S <NUM> UE security capability IE and the second security capability IE may be a <NUM> UE security capability IE, or vice versa. In various embodiments, the security capability IE generating module <NUM> may be configured to generate a security capability IE including two UP IP support indications. For example, each UP IP support indication may be a separate bit setting in the security capability IE. One bit setting may indicate whether the wireless device supports UP IP for eUTRA and the other bit setting may indicate whether the wireless device supports UP IP for NR connections established between the wireless device and the RAN.

Security capability IE sending module <NUM> may be configured to send the security capability IEs to base stations of the RAN. As examples, the base station may be an eNB or a ng-eNB. In some embodiments the security capability IEs may be sent to the RAN via other nodes.

Security capability IE receiving module <NUM> may be configured to receive the security capability IEs.

Security capability IE determination module <NUM> may be configured to determine whether the security capability IE indicates that the wireless device supports UP IP for eUTRA connections established with the wireless device based at least in part on the UP IP support indication. Security capability IE determination module <NUM> may be configured to determine whether the security capability IE indicates that the wireless device supports UP IP for NR connections established with the wireless device.

<FIG> shows a process flow diagram of an example method <NUM> of supporting UP IP for communications with a RAN according to various embodiments. With reference to <FIG>, the method <NUM> may be implemented by a processor (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) of a wireless device (e.g., the wireless device 120a-120e, <NUM>, <NUM>, <NUM>, <NUM>).

In block <NUM>, the processor may perform operations including determining whether the wireless device supports UP IP for eUTRA connections established between the wireless device and a RAN. In various embodiments, determining whether the wireless device supports UP IP for eUTRA may include checking a capability setting of the wireless device.

In block <NUM>, the processor may perform operations including generating a first security capability IE including a first UP IP support indication. The first UP IP support indication may indicate whether the wireless device supports UP IP for eUTRA connections established between the wireless device and the RAN. In some embodiments, the first security capability IE may be a <NUM> S <NUM> UE security capability IE. In some embodiments, the first security capability IE may be a <NUM> UE security capability IE. In various embodiments, the first UP IP support indication may be a bit setting in the first security capability IE. For example, the first UP IP support indication may be a setting of one of the EEA or EIA bits in a <NUM> S <NUM> UE security capability IE or a <NUM> UE security capability IE. In some embodiments, the setting of the bit in the <NUM> S <NUM> UE security capability IE, such as the setting of one of the EEA or EIA bits in a <NUM> S <NUM> UE security capability IE, may indicate both that the wireless device supports UP IP for eUTRA connections established between the wireless device and a RAN and UP IP for NR connections established between the wireless device and a RAN. In various embodiments, the first UP IP support indication may indicate UP IP support with one or more (e.g., several) integrity algorithms.

In block <NUM>, the processor may perform operations including sending the first security capability IE to a base station. In some embodiments, the base station may be a base station of the RAN. In some embodiments, the base station may be a base station outside the RAN, which may be configured to forward the first security capability IE to a network device of the RAN, such as a base station of the RAN, an MME server of the RAN, etc. For example, the first security capability IE may be sent as part of a wireless device registration request sent to the RAN.

In blocks <NUM>, <NUM>, and <NUM>, the processor may perform operations of like numbered blocks of method <NUM> described with reference to <FIG>.

In block <NUM>, the processor may perform operations including generating a second security capability IE including a second UP IP support indication. In networks including both <NUM> and <NUM> RAN elements, two security capability IEs may be provided to the RAN, such as one security capability IE for <NUM> systems and one security capability IE for <NUM> systems. Each security capability IE may separately indicate whether the wireless device supports UP IP for eUTRA connections and/or UP IP for NR connections. For example, the first security capability IE may be a <NUM> S <NUM> UE security capability IE and the second security capability IE may be a <NUM> UE security capability IE. In various embodiments, the second UP IP support indication may be a bit setting in the second security capability IE. For example, the second UP IP support indication may be a setting of one of the EEA or EIA bits in a <NUM> S <NUM> UE security capability IE or a <NUM> UE security capability IE depending on the type of the second security capability IE. In various embodiments, the second UP IP support indication may indicate UP IP support with one or more (e.g., several) integrity algorithms.

In block <NUM>, the processor may perform operations including sending the second security capability IE to the base station. In some embodiments, the base station may be a base station of the RAN. In some embodiments, the base station may be a base station outside the RAN, which may be configured to forward the second security capability IE to a network device of the RAN, such as a base station of the RAN, an MME server of the RAN, etc. For example, the second security capability IE may be sent as part of a wireless device registration request sent to the RAN.

While <FIG> illustrates a method <NUM> for sending two separate security capability IEs, such as one security capability IE for <NUM> systems and another security capability IE for <NUM> systems, in other networks only one security capability IE may be generated and sent as the network may be configured to share the security capability IE and/or the indication of the support for UP IP by the wireless device between <NUM> and <NUM> systems. In such networks sharing wireless device support for UP IP indications across <NUM> and <NUM> systems, re-registration of the wireless device when crossing between <NUM> and <NUM> coverage may not be required.

<FIG> shows a process flow diagram of an example method <NUM> of supporting UP IP for communications with a RAN according to various embodiments. With reference to <FIG>, the method <NUM> may be implemented by a processor (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) of a wireless device (e.g., the wireless device 120a-120e, <NUM>, <NUM>, <NUM>, <NUM>). In various embodiments, the operations of method <NUM> may be implemented in conjunction with the operations of methods <NUM> (<FIG>) and/or <NUM> (<FIG>). For example, the operations of method <NUM> may be performed as part of generating the first security capability IE upon determining whether the wireless device supports UP IP for eUTRA connections established between the wireless device and a RAN in block <NUM>.

In block <NUM>, the processor may perform operations including determining whether the wireless device supports UP IP for NR connections established between the wireless device and a RAN. In various embodiments, determining whether the wireless device supports UP IP for NR connections may include checking a capability setting of the wireless device.

In block <NUM>, the processor may perform operations including generating the first security capability IE including the first UP IP support indication and a third UP IP support indication. The third UP IP support indication may indicate whether the wireless device supports UP IP for NR connections established between the wireless device and the RAN. In some embodiments, the first security capability IE may be a <NUM> S1 UE security capability IE. In various embodiments, the first UP IP support indication may be a bit setting in the first security capability IE and the third UP IP support indication may be another bit setting in the first security capability IE. For example, the first UP IP support indication may be a setting of one of the EEA or EIA bits in a <NUM> S <NUM> UE security capability IE and the third UP IP support indication may be a setting of another one of the EEA or EIA bits in the <NUM> S1 UE security capability IE.

In response to generating the first security capability IE, the processor may perform operations of block <NUM> as described with reference to <FIG> and <FIG> to send the first security capability IE.

<FIG> shows a process flow diagram of an example method <NUM> of supporting UP IP for communications with a RAN according to various embodiments. With reference to <FIG>, the method <NUM> may be implemented by a processor of a network computing device (e.g., the base station 110a-110e, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, network controller <NUM>, and/or other network entities). In various embodiments, the operations of method <NUM> may be implemented in conjunction with the operations of methods <NUM> (<FIG>), <NUM> (<FIG>), and/or <NUM> (<FIG>).

In block <NUM>, the processor may perform operations including receiving a security capability IE of a wireless device (such as the wireless device 120a-120e, <NUM>, <NUM>). The security capability IE may be received as part of a wireless device registration and/or authentication procedures. The security capability IE may include a UP IP support indication. In some embodiments, the security capability IE may be a <NUM> S <NUM> UE security capability IE. In some embodiments, the security capability IE may be a <NUM> UE security capability IE. In various embodiments, a UP IP support indication may indicate UP IP support with one or more (e.g., several) integrity algorithms. In various embodiments, the UP IP support indication may be a bit setting in the security capability IE. For example, the UP IP support indication may be a setting of one of the EEA or EIA bits in a <NUM> S <NUM> UE security capability IE or a <NUM> UE security capability IE. In some embodiments, the security capability IE may be received directly from a wireless device, such as by a base station of the RAN. In some embodiments, the security capability ID may be received from the wireless device via forwarding from another network computing device, such as forwarded from a base station, forwarded from an MME server, etc..

In block <NUM>, the processor may perform operations including determining whether the security capability IE indicates that the wireless device supports UP IP for eUTRA connections established with the wireless device based at least in part on the UP IP support indication. In various embodiments, the bit setting of the UP IP support indication in the security capability IE may indicate whether or not the wireless device supports UP IP for eUTRA connections established with the wireless device. For example, the setting of one of the EEA or EIA bits in a <NUM> S <NUM> UE security capability IE or a <NUM> UE security capability IE to the value "<NUM>" may indicate that the wireless device does support UP IP for eUTRA. In some embodiments, the setting of the bit in the <NUM> S <NUM> UE security capability IE, such as the setting of one of the EEA or EIA bits in a <NUM> S <NUM> UE security capability IE, may indicate both that the wireless device supports UP IP for eUTRA connections established between the wireless device and a RAN and UP IP for NR connections established between the wireless device and a RAN. In various embodiments, the UP IP support indication may be a bit setting in the security capability IE.

In block820, the network computing device may use the determined capability of the wireless device to support UP IP for eUTRA connections and/or UP IP for NR connections to establish user plane connections having integrity protection with the wireless device.

In blocks <NUM> and <NUM>, the processor may perform operations of like numbered blocks of method <NUM> described with reference to <FIG>.

In block <NUM>, the processor may perform operations including determining whether the security capability IE indicates that the wireless device supports UP IP for NR connections established with the wireless device. In some embodiments, the UP IP support indication may have dual meaning indicating both that the wireless device supports UP IP for eUTRA and supports UP IP for NR. In some embodiment, the security capability IE may include more than one UP IP support indication. For example, one UP IP support indication, such as one bit setting, may indicate that the wireless device supports UP IP for eUTRA connections, and another UP IP support indication, such as another bit setting, may indicate that the wireless device supports UP IP for NR connections.

Various embodiments may be implemented on a variety of wireless network devices, an example of which is illustrated in <FIG> in the form of a wireless network computing device <NUM> functioning as a network element of a communication network, such as a base station (e.g., the base station 110a-110e, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>). Such network computing devices may include at least the components illustrated in <FIG>. With reference to <FIG>, the network computing device <NUM> may typically include a processor <NUM> coupled to volatile memory <NUM> and a large capacity nonvolatile memory, such as a disk drive <NUM>. The network computing device <NUM> may also include a peripheral memory Access device such as a floppy disc drive, compact disc (CD) or digital video disc (DVD) drive <NUM> coupled to the processor <NUM>. The network computing device <NUM> may also include network Access ports <NUM> (or interfaces) coupled to the processor <NUM> for establishing data connections with a network, such as the Internet and/or a local area network coupled to other system computers and servers. The network computing device <NUM> may include one or more antennas <NUM> for sending and receiving electromagnetic radiation that may be connected to a wireless communication link. The network computing device <NUM> may include additional Access ports, such as USB, Firewire, Thunderbolt, and the like for coupling to peripherals, external memory, or other devices.

Various embodiments may be implemented on a variety of computing devices, such as wireless devices (e.g., the wireless device 120a-120e, <NUM>, <NUM>, <NUM>, <NUM>), an example of which is illustrated in <FIG> in the form of a smartphone <NUM>. With reference to <FIG>, the smartphone <NUM> may include a first SOC <NUM> (e.g., a SOC-CPU) coupled to a second SOC <NUM> (e.g., a <NUM> capable SOC). The first and second SOCs <NUM>, <NUM> may be coupled to internal memory <NUM>, <NUM>, a display <NUM>, and to a speaker <NUM>. Additionally, the smartphone <NUM> may include an antenna <NUM> for sending and receiving electromagnetic radiation that may be connected to a wireless data link and/or cellular telephone transceiver <NUM> coupled to one or more processors in the first and/or second SOCs <NUM>, <NUM>. Smartphones <NUM> typically also include menu selection buttons or rocker switches <NUM> for receiving user inputs.

A typical smartphone <NUM> also includes a sound encoding/decoding (CODEC) circuit <NUM>, which digitizes sound received from a microphone into data packets suitable for wireless transmission and decodes received sound data packets to generate analog signals that are provided to the speaker to generate sound. Also, one or more of the processors in the first and second SOCs <NUM>, <NUM>, wireless transceiver <NUM> and CODEC <NUM> may include a digital signal processor (DSP) circuit (not shown separately).

The processors of the wireless network computing device <NUM> and the smart phone <NUM> may be any programmable microprocessor, microcomputer or multiple processor chip or chips that can be configured by software instructions (applications) to perform a variety of functions, including the functions of the various embodiments described below. In some Mobile devices, multiple processors may be provided, such as one processor within an SOC <NUM> dedicated to wireless communication functions and one processor within an SOC <NUM> dedicated to running other applications. Typically, software applications may be stored in the memory <NUM>, <NUM> before they are accessed and loaded into the processor. The processors may include internal memory sufficient to store the application software instructions.

As used in this application, the terms "component," "module," "system," and the like are intended to include a computer-related entity, such as, but not limited to, hardware, firmware, a combination of hardware and software, software, or software in execution, which are configured to perform particular operations or functions. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a wireless device and the wireless device may be referred to as a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one processor or core and/or distributed between two or more processors or cores. In addition, these components may execute from various non-transitory computer readable media having various instructions and/or data structures stored thereon. Components may communicate by way of local and/or remote processes, function or procedure calls, electronic signals, data packets, memory read/writes, and other known network, computer, processor, and/or process related communication methodologies.

A number of different cellular and Mobile communication services and standards are available or contemplated in the future, all of which may implement and benefit from the various embodiments. Such services and standards include, e.g., third Generation partnership project (3GPP), long term evolution (LTE) systems, third Generation wireless Mobile communication technology (<NUM>), fourth Generation wireless Mobile communication technology (<NUM>), fifth Generation wireless Mobile communication technology (<NUM>), global System for Mobile communications (GSM), Universal Mobile Telecommunications System (UMTS), 3GSM, general Packet Radio service (GPRS), code division multiple Access (CDMA) systems (e.g., cdmaOne, CDMA1020TM), enhanced data rates for GSM evolution (EDGE), advanced Mobile phone System (AMPS), digital AMPS (IS-<NUM>/TDMA), evolution-data optimized (EV-DO), digital enhanced cordless Telecommunications (DECT), Worldwide Interoperability for Microwave Access (WiMAX), wireless local area network (WLAN), Wi-Fi Protected Access I & II (WPA, WPA2), and integrated digital enhanced network (iDEN). Each of these technologies involves, for example, the transmission and reception of voice, data, signaling, and/or content messages. It should be understood that any references to terminology and/or technical details related to an individual telecommunication standard or technology are for illustrative purposes only, and are not intended to limit the scope of the claims to a particular communication system or technology unless specifically recited in the claim language.

Various embodiments illustrated and described are provided merely as examples to illustrate various features of the claims. However, features shown and described with respect to any given embodiment are not necessarily limited to the associated embodiment and may be used or combined with other embodiments that are shown and described. Further, the claims are not intended to be limited by any one example embodiment. For example, one or more of the operations of the methods <NUM>, <NUM>, <NUM>, <NUM>, and/or <NUM> may be substituted for or combined with one or more operations of the methods <NUM>, <NUM>, <NUM>, <NUM>, and/or <NUM>.

The hardware used to implement various illustrative logics, logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A processor may also be implemented as a combination of receiver smart objects, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Alternatively, some operations or methods may be performed by circuitry that is specific to a given function.

In one or more embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable storage medium or non-transitory processor-readable storage medium. The operations of a method or algorithm disclosed herein may be embodied in a processor-executable software module or processor-executable instructions, which may reside on a non-transitory computer-readable or processor-readable storage medium. Non-transitory computer-readable or processor-readable storage media may be any storage media that may be accessed by a computer or a processor. By way of example but not limitation, such non-transitory computer-readable or processor-readable storage media may include RAM, ROM, EEPROM, FLASH memory, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage smart objects, or any other medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer. Combinations of the above are also included within the scope of non-transitory computer-readable and processor-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory processor-readable storage medium and/or computer-readable storage medium, which may be incorporated into a computer program product.

Claim 1:
A method (<NUM>) for supporting user plane integrity protection, UP IP, for communications with a radio access network, RAN, comprising:
determining (<NUM>), by a processor of a wireless device, whether the wireless device supports UP IP for Evolved Universal Mobile Telecommunications System, UMTS, Terrestrial Radio Access, eUTRA, connections established between the wireless device and a RAN;
generating (<NUM>), by the processor, a first security capability information element, IE, including a first UP IP support indication, wherein the first UP IP support indication indicates whether the wireless device supports UP IP for eUTRA connections established between the wireless device and the RAN; and
sending (<NUM>), by the processor, the first security capability IE to a base station, wherein the first UP IP support indication is a bit setting in the first security capability IE, and wherein the bit setting also indicates that the wireless device supports the same maximum data rate capability for UP IP over eUTRA.