US20220104080A1 - Method to Retrieve Security Keys of UE in Gateways - Google Patents
Method to Retrieve Security Keys of UE in Gateways Download PDFInfo
- Publication number
- US20220104080A1 US20220104080A1 US17/486,907 US202117486907A US2022104080A1 US 20220104080 A1 US20220104080 A1 US 20220104080A1 US 202117486907 A US202117486907 A US 202117486907A US 2022104080 A1 US2022104080 A1 US 2022104080A1
- Authority
- US
- United States
- Prior art keywords
- message
- hng
- mme
- enodeb
- handover
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
- H04W36/0038—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information of security context information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
- H04W12/043—Key management, e.g. using generic bootstrapping architecture [GBA] using a trusted network node as an anchor
- H04W12/0431—Key distribution or pre-distribution; Key agreement
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
- H04L5/0055—Physical resource allocation for ACK/NACK
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
- This application claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Pat. App. No. 63/083,263, filed Sep. 25, 2020, titled “A Method to Retrieve Security Keys of UE from MME in Gateways,” which is hereby incorporated by reference in its entirety for all purposes. This application hereby incorporates by reference each of U.S. Pat. App. Pub. Nos. US20110044285, US20140241316; WO Pat. App. Pub. No. WO2013145592A1; EP Pat. App. Pub. No. EP2773151A1; U.S. Pat. No. 8,879,416, “Heterogeneous Mesh Network and Multi-RAT Node Used Therein,” filed May 8, 2013; U.S. Pat. No. 8,867,418, “Methods of Incorporating an Ad Hoc Cellular Network Into a Fixed Cellular Network,” filed Feb. 18, 2014; U.S. patent application Ser. No. 14/777,246, “Methods of Enabling Base Station Functionality in a User Equipment,” filed Sep. 15, 2016; U.S. patent application Ser. No. 14/289,821, “Method of Connecting Security Gateway to Mesh Network,” filed May 29, 2014; U.S. patent application Ser. No. 14/642,544, “Federated X2 Gateway,” filed Mar. 9, 2015; U.S. patent application Ser. No. 14/711,293, “Multi-Egress Backhaul,” filed May 13, 2015; U.S. Pat. App. No. 62/375,341, “S2 Proxy for Multi-Architecture Virtualization,” filed Aug. 15, 2016; U.S. patent application Ser. No. 15/132,229, “MaxMesh: Mesh Backhaul Routing,” filed Apr. 18, 2016, each in its entirety for all purposes, having attorney docket numbers PWS-71700US01, 71710US01, 71717US01, 71721US01, 71756US01, 71762US01, 71819US00, and 71820US01, respectively. This application also hereby incorporates by reference in their entirety each of the following U.S. Pat. applications or Pat. App. Publications: US20150098387A1 (PWS-71731US01); US20170055186A1 (PWS-71815US01); US20170273134A1 (PWS-71850US01); US20170272330A1 (PWS-71850US02); and Ser. No. 15/713,584 (PWS-71850US03). This application also hereby incorporates by reference in their entirety U.S. patent application Ser. No. 16/424,479, “5G Interoperability Architecture,” filed May 28, 2019; and U.S. Provisional Pat. Application No. 62/804,209, “5G Native Architecture,” filed Feb. 11, 2019.
- The LTE standard defines S1 interface between eNodeB and EPC, X2 interface between eNodeBs and RRC(UU) the air interface between UE and eNodeB. Further down, S1-C handles control plane messages between eNodeB and MME and S1-U handles the data plane(eGTP) between SGW and eNodeB. Similarly, X2-C handles control plane messages between eNodeBs and X2-U handles data plane (eGTP) between eNodeBs. Procedures for handling mobility within LTE involves RRC along with S1 or X2 interfaces. In a real-time scenario, LTE handsets are mobile and arise a need to re-establish RRC connection with base stations through standard procedures. While doing so, security keys at both handset and base station changes as per 3GPP TS 33.401, which is hereby incorporated by reference in its entirety for all purposes. Gateways serving as MME for multiple eNodeBs keep real EPC oblivious to these procedures. Most gateways retrieve security keys from EPC while failing to derive by themselves. S1 mobility procedure demands fresh key derivations to be provided to target eNodeB to eliminate possibility of handover failures using horizontally derived keys at UE and source eNodeB during RRC connection re-establishment procedure.
- A method to retrieve fresh security key context for User Equipment (UE) from Mobility Management Entity (MME) by Virtualized eNodeB (HNG) is defined. In field, UEs re-establishing air interface connection is quite common and it is associated with horizontal key derivation procedure. However, while S1 handovers within HNG vertical key derivations are necessary to eliminate any horizontally derived keys and sync keys at Non-Access Stratum (NAS) and Access Stratum (AS or RRC) level. HNG uses signaling from X2 handover procedure defined in 3GPP TS 36423 to retrieve keys and pass it to target eNodeB there by increasing the robustness of S1 handover procedures occurring among eNodeBs within the same HNG.
- In one embodiment, a method of retrieving security keys from a User Equipment (UE) in gateways includes retrieving, by a HetNet Gateway (HNG) as the HNG virtualizes an eNodeB towards n Mobility Management Entity (MME) through a first message and a second message exchange, a fresh Next Hop, Next Hop Chaining Count {NH, NCC} pair from the MME; and mocking, by the HNG, an X2 handover towards the MME by sending a third message with required Information Elements filled when a fourth message from the eNodeB reaches the HNG.
- In another embodiment, a system for retrieving security keys in gateways includes a HetNet Gateway (HNG); wherein the HNG retrieves, as the HNG virtualizes an eNodeB towards the MME through a first message and a second message exchange, a fresh {NH, NCC} from MME; and sends a third message with required Information Elements filled when a fourth message reaches the HNG.
- In another embodiment a non-transitory computer-readable medium contains instructions for providing retrieving security keys from a User Equipment (UE) in gateways, which, when executed, cause a network node to perform steps including retrieving, by a HetNet Gateway (HNG) as the HNG virtualizes an eNodeB towards n Mobility Management Entity (MME) through a first message and a second message exchange, a fresh Next Hop, Next Hop Chaining Count {NH, NCC} pair from the MME; and mocking, by the HNG, an X2 handover towards the MME by sending a third message with required Information Elements filled when a fourth message from the eNodeB reaches the HNG.
-
FIG. 1 is an architectural diagram, in accordance with some embodiments. -
FIG. 2 is a call flow diagram without key retrieval, in accordance with some embodiments. -
FIG. 3 is a call flow diagram with key retrieval, in accordance with some embodiments. -
FIG. 4 is a schematic network architecture diagram for various radio access technology core networks. -
FIG. 5 is an enhanced eNodeB for performing the methods described herein, in accordance with some embodiments. -
FIG. 6 is a coordinating server for providing services and performing methods as described herein, in accordance with some embodiments. -
FIG. 1 shows anexample environment 100 including an HNG 101, a first node eNB1 102 In communication with the HNG and with a User Equipment (UE) 104. Also shown is asecond node eNB2 103 in communication with the HNG. The HNG is also in communication with an Mobility Management Entity (MME) 105 and a Serving Gateway (SGW) 106. -
FIG. 2 shows a call flow withoutkey retrieval 200, in some embodiments, within a system including a UE, a EnodeB1, an HNG, an MME and an eNodeB2. The HNG is a gateway node as described elsewhere herein and provides virtualization, proxying, and gatewaying between the RAN and the core. - When eNodeB1 and eNodeB2 are connected to same HNG and HNG is performing handovers in intra-HNG mode, if UE has performed RRC Connection Reestablishment prior to being handed out from serving eNodeB1, key derivations at target eNodeB2 will fail the incoming handover procedure there by degrading Key Performance Indicators (KPIs). Mobility KPIs are crucial factors influencing base station capabilities and user experiences.
- A UE connected to eNodeB1 undergoes link re-establishment with the same eNodeB through 3GPP defined procedure known as RRC Connection Reestablishment. As a part of this procedure, UE and eNodeB are required to derive new set of security keys through horizontal key derivation procedures mentioned in 3GPP specifications.
- Security keys comprise of a pair: Next hop parameter (NH) and Next hop chaining count (NCC). Noteworthy that at 203 the HNG fills the security context IE with received {NH, NCC} 1.
-
FIG. 3 shows key retrieval, in some embodiments. Subsequently, due to deteriorating radio conditions, this UE is decided to be handed out from eNodeB1 via S1 handover procedure to eNodeB2, connected to same HNG. As per 3GPP, a vertical key derivation of security keys shall be needed to perform. This includes deriving fresh NH and NCC parameters at HNG (acting as MME) and inform the NCC to UE via eNodeB2 to sync at NAS level. As HNG stores keys obtained through 51 procedures from MME (as HNG is just a relay), it populates the old keys issued for this UE during initial attach procedure and forwards to target eNodeB2. Point to note here is that as UE's keys and eNodeB2's keys are out of sync, UE's subsequent air interface (RRC) communication with target eNodeB2 will fail. - As shown by the call flow diagram 300 of
FIG. 3 , during 51 handovers a fresh {NH, NCC} pair are derived at MME. Since HNG keeps MME oblivious to S1 handovers for eNodeBs connected within HNG, retrieving fresh {NH, NCC} pair from MME is not possible via 3GPP defined 51 Handover procedures. However, by creating a message that appears to be a part of X2 handover procedure defined by 3GPP, HNG can force MME to derive a fresh {NH, NCC} pair. As HNG virtualizes eNodeB towards MME, through PATH SWITCH REQUEST and PATH SWITCH REQUEST ACK message exchanges. HNG can retrieve a fresh {NH, NCC} from MME. When HANDOVER REQUIRED message from eNodeB1 reaches HNG, HNG creates a mock X2 handover towards MME by sending PATH SWITCH REQUEST with required Information Elements filled. MME responds back with PATH SWITCH REQUEST ACK message comprising of fresh {NH, NCC} pair. Now, HNG sends HANDOVER REQUEST towards eNodeB2 with new keys used for vertical derivation. Subsequent handover message exchanges among eNodeB1, HNG and eNodeB2 continue unchanged. - In some embodiments, a Virtual eNodeB instance uses one additional interface each towards MME(S1-C) and SGW(S1-U) posing as a different eNodeB. Internal mapping of unique S1AP UE IDs along with EGTP Transport layer addresses for the bearers used for this UE and network interfaces of Virtual eNodeB instance shall be maintained at HNG during S1 handover (both control and data plane).
- It is noted that 5G security builds on 4G security, and as a result the present methods would be able to be used with 5G, in some embodiments. In particular, 5G NSA uses an EPC core and is capable of the above messaging without modification, in some embodiments. In some embodiments, notably for 5G standalone (SA), the 5G equivalents of the 4G EPC messages described above are used, as described further in 3GPP, “Security Architecture and Procedures for 5G System” (Release 15), technical specification (TS) 33.501, which is hereby incorporated by reference in its entirety for all purposes. As well, in some embodiments an interworking function is used in a 4G/5G core to enable the use of either a 4G core with a 5G gNB, or a 5G core with a 4G eNB, as described in U.S. Pat. Pub. No. 20210084714A1, “4G/5G Core Interworking,” which is also hereby incorporated by reference in its entirety for all purposes. When a 4G/5G core interworking function is used, the above methods could be used with either the 4G or 5G core as appropriate, using interworking at the HNG (e.g., a gateway node) to enable the messaging to function as described above.
-
FIG. 4 is a schematic network architecture diagram for 3G and other-G prior art networks. The diagram shows a plurality of “Gs,” including 2G, 3G, 4G, 5G and Wi-Fi. 2G is represented byGERAN 401, which includes a2G device 401 a,BTS 401 b, andBSC 401 c. 3G is represented byUTRAN 402, which includes a3G UE 402 a,nodeB 402 b,RNC 402 c, and femto gateway (FGW, which in 3GPP namespace is also known as a Home nodeB Gateway or HNBGW) 402 d. 4G is represented by EUTRAN or E-RAN 403, which includes anLTE UE 403 a andLTE eNodeB 403 b. Wi-Fi is represented by Wi-Fi access network 404, which includes a trusted Wi-Fi access point 404 c and an untrusted Wi-Fi access point 404 d. The Wi-Fi devices AP circuit core network 405 includes a 2G MSC/VLR; 2G/3Gpacket core network 406 includes an SGSN/GGSN (for EDGE or UMTS packet traffic);3G circuit core 407 includes a 3G MSC/VLR;4G circuit core 408 includes an evolved packet core (EPC); and in some embodiments the Wi-Fi access network may be connected via an ePDG/TTG using S2a/S2b. Each of these nodes are connected via a number of different protocols and interfaces, as shown, to other, non-“G”-specific network nodes, such as the SCP 430, the SMSC 431, PCRF 432, HLR/HSS 433, Authentication, Authorization, and Accounting server (AAA) 434, and IP Multimedia Subsystem (IMS) 435. An HeMS/AAA 436 is present in some cases for use by the 3G UTRAN. The diagram is used to indicate schematically the basic functions of each network as known to one of skill in the art, and is not intended to be exhaustive. For example,5G core 417 is shown using a single interface to5G access 416, although in somecases 5G access can be supported using dual connectivity or via a non-standalone deployment architecture. - Noteworthy is that the
RANs specialized core networks BSC 401 c is required for Abis compatibility withBTS 401 b, while for the 3G UTRAN, anRNC 402 c is required for Iub compatibility and anFGW 402 d is required for Iuh compatibility. These core network functions are separate because each RAT uses different methods and techniques. On the right side of the diagram are disparate functions that are shared by each of the separate RAT core networks. These shared functions include, e.g., PCRF policy functions, AAA authentication functions, and the like. Letters on the lines indicate well-defined interfaces and protocols for communication between the identified nodes. - The system may include 5G equipment. 5G networks are digital cellular networks, in which the service area covered by providers is divided into a collection of small geographical areas called cells. Analog signals representing sounds and images are digitized in the phone, converted by an analog to digital converter and transmitted as a stream of bits. All the 5G wireless devices in a cell communicate by radio waves with a local antenna array and low power automated transceiver (transmitter and receiver) in the cell, over frequency channels assigned by the transceiver from a common pool of frequencies, which are reused in geographically separated cells. The local antennas are connected with the telephone network and the Internet by a high bandwidth optical fiber or wireless backhaul connection.
- 5G uses millimeter waves which have shorter range than microwaves, therefore the cells are limited to smaller size. Millimeter wave antennas are smaller than the large antennas used in previous cellular networks. They are only a few inches (several centimeters) long. Another technique used for increasing the data rate is massive MIMO (multiple-input multiple-output). Each cell will have multiple antennas communicating with the wireless device, received by multiple antennas in the device, thus multiple bitstreams of data will be transmitted simultaneously, in parallel. In a technique called beamforming the base station computer will continuously calculate the best route for radio waves to reach each wireless device, and will organize multiple antennas to work together as phased arrays to create beams of millimeter waves to reach the device.
- Shown in
FIG. 5 is an enhanced eNodeB for performing the methods described herein, in accordance with some embodiments.eNodeB 500 may includeprocessor 502,processor memory 504 in communication with the processor,baseband processor 506, andbaseband processor memory 508 in communication with the baseband processor.Mesh network node 500 may also includefirst radio transceiver 512 andsecond radio transceiver 514, internal universal serial bus (USB) port 516, and subscriber information module card (SIM card) 518 coupled to USB port 516. In some embodiments, thesecond radio transceiver 514 itself may be coupled to USB port 516, and communications from the baseband processor may be passed through USB port 516. The second radio transceiver may be used for wirelessly backhaulingeNodeB 500. -
Processor 502 andbaseband processor 506 are in communication with one another.Processor 502 may perform routing functions, and may determine if/when a switch in network configuration is needed.Baseband processor 506 may generate and receive radio signals for bothradio transceivers processor 502. In some embodiments,processors -
Processor 502 may identify the appropriate network configuration, and may perform routing of packets from one network interface to another accordingly.Processor 502 may usememory 504, in particular to store a routing table to be used for routing packets.Baseband processor 506 may perform operations to generate the radio frequency signals for transmission or retransmission by bothtransceivers 510 and 512.Baseband processor 506 may also perform operations to decode signals received bytransceivers Baseband processor 506 may usememory 508 to perform these tasks. - The
first radio transceiver 512 may be a radio transceiver capable of providing LTE eNodeB functionality, and may be capable of higher power and multi-channel OFDMA. Thesecond radio transceiver 514 may be a radio transceiver capable of providing LTE UE functionality. Bothtransceivers transceivers Transceiver 512 may be coupled toprocessor 502 via a Peripheral Component Interconnect-Express (PCI-E) bus, and/or via a daughtercard. Astransceiver 514 is for providing LTE UE functionality, in effect emulating a user equipment, it may be connected via the same or different PCI-E bus, or by a USB bus, and may also be coupled toSIM card 518.First transceiver 512 may be coupled to first radio frequency (RF) chain (filter, amplifier, antenna) 522, andsecond transceiver 514 may be coupled to second RF chain (filter, amplifier, antenna) 524. -
SIM card 518 may provide information required for authenticating the simulated UE to the evolved packet core (EPC). When no access to an operator EPC is available, a local EPC may be used, or another local EPC on the network may be used. This information may be stored within the SIM card, and may include one or more of an international mobile equipment identity (IMEI), international mobile subscriber identity (IMSI), or other parameter needed to identify a UE. Special parameters may also be stored in the SIM card or provided by the processor during processing to identify to a target eNodeB thatdevice 500 is not an ordinary UE but instead is a special UE for providing backhaul todevice 500. - Wired backhaul or wireless backhaul may be used. Wired backhaul may be an Ethernet-based backhaul (including Gigabit Ethernet), or a fiber-optic backhaul connection, or a cable-based backhaul connection, in some embodiments. Additionally, wireless backhaul may be provided in addition to
wireless transceivers processor 502 for reconfiguration. - A
GPS module 530 may also be included, and may be in communication with aGPS antenna 532 for providing GPS coordinates, as described herein. When mounted in a vehicle, the GPS antenna may be located on the exterior of the vehicle pointing upward, for receiving signals from overhead without being blocked by the bulk of the vehicle or the skin of the vehicle. Automatic neighbor relations (ANR)module 532 may also be present and may run onprocessor 502 or on another processor, or may be located within another device, according to the methods and procedures described herein. - Other elements and/or modules may also be included, such as a home eNodeB, a local gateway (LGW), a self-organizing network (SON) module, or another module. Additional radio amplifiers, radio transceivers and/or wired network connections may also be included.
-
FIG. 6 is a coordinating server for providing services and performing methods as described herein, in accordance with some embodiments.Coordinating server 600 includesprocessor 602 andmemory 604, which are configured to provide the functions described herein. Also present are radio access network coordination/routing (RAN Coordination and routing)module 606, includingANR module 606 a,RAN configuration module 608, andRAN proxying module 610. TheANR module 606 a may perform the ANR tracking, PCI disambiguation, ECGI requesting, and GPS coalescing and tracking as described herein, in coordination with RAN coordination module 606 (e.g., for requesting ECGIs, etc.). In some embodiments, coordinatingserver 600 may coordinate multiple RANs usingcoordination module 606. In some embodiments, coordination server may also provide proxying, routing virtualization and RAN virtualization, viamodules downstream network interface 612 is provided for interfacing with the RANs, which may be a radio interface (e.g., LTE), and anupstream network interface 614 is provided for interfacing with the core network, which may be either a radio interface (e.g., LTE) or a wired interface (e.g., Ethernet). -
Coordinator 600 includes local evolved packet core (EPC)module 620, for authenticating users, storing and caching priority profile information, and performing other EPC-dependent functions when no backhaul link is available.Local EPC 620 may includelocal HSS 622,local MME 624,local SGW 626, andlocal PGW 628, as well as other modules.Local EPC 620 may incorporate these modules as software modules, processes, or containers.Local EPC 620 may alternatively incorporate these modules as a small number of monolithic software processes.Modules local EPC 620 may each run onprocessor 602 or on another processor, or may be located within another device. - In any of the scenarios described herein, where processing may be performed at the cell, the processing may also be performed in coordination with a cloud coordination server. A mesh node may be an eNodeB. An eNodeB may be in communication with the cloud coordination server via an X2 protocol connection, or another connection. The eNodeB may perform inter-cell coordination via the cloud communication server when other cells are in communication with the cloud coordination server. The eNodeB may communicate with the cloud coordination server to determine whether the UE has the ability to support a handover to Wi-Fi, e.g., in a heterogeneous network.
- Although the methods above are described as separate embodiments, one of skill in the art would understand that it would be possible and desirable to combine several of the above methods into a single embodiment, or to combine disparate methods into a single embodiment. For example, all of the above methods could be combined. In the scenarios where multiple embodiments are described, the methods could be combined in sequential order, or in various orders as necessary.
- Although the above systems and methods for providing interference mitigation are described in reference to the Long Term Evolution (LTE) standard, one of skill in the art would understand that these systems and methods could be adapted for use with other wireless standards or versions thereof. The inventors have understood and appreciated that the present disclosure could be used in conjunction with various network architectures and technologies. Wherever a 4G technology is described, the inventors have understood that other RATs have similar equivalents, such as a gNodeB for 5G equivalent of eNB. Wherever an MME is described, the MME could be a 3G RNC or a 5G AMF/SMF. Additionally, wherever an MME is described, any other node in the core network could be managed in much the same way or in an equivalent or analogous way, for example, multiple connections to 4G EPC PGWs or SGWs, or any other node for any other RAT, could be periodically evaluated for health and otherwise monitored, and the other aspects of the present disclosure could be made to apply, in a way that would be understood by one having skill in the art.
- Additionally, the inventors have understood and appreciated that it is advantageous to perform certain functions at a coordination server, such as the Parallel Wireless HetNet Gateway, which performs virtualization of the RAN towards the core and vice versa, so that the core functions may be statefully proxied through the coordination server to enable the RAN to have reduced complexity. Therefore, at least four scenarios are described: (1) the selection of an MME or core node at the base station; (2) the selection of an MME or core node at a coordinating server such as a virtual radio network controller gateway (VRNCGW); (3) the selection of an MME or core node at the base station that is connected to a 5G-capable core network (either a 5G core network in a 5G standalone configuration, or a 4G core network in 5G non-standalone configuration); (4) the selection of an MME or core node at a coordinating server that is connected to a 5G-capable core network (either 5G SA or NSA). In some embodiments, the core network RAT is obscured or virtualized towards the RAN such that the coordination server and not the base station is performing the functions described herein, e.g., the health management functions, to ensure that the RAN is always connected to an appropriate core network node. Different protocols other than S1AP, or the same protocol, could be used, in some embodiments.
- In some embodiments, the base stations described herein may support Wi-Fi air interfaces, which may include one or more of IEEE 802.11a/b/g/n/ac/af/p/h. In some embodiments, the base stations described herein may support IEEE 802.16 (WiMAX), to LTE transmissions in unlicensed frequency bands (e.g., LTE-U, Licensed Access or LA-LTE), to LTE transmissions using dynamic spectrum access (DSA), to radio transceivers for ZigBee, Bluetooth, or other radio frequency protocols, or other air interfaces.
- In some embodiments, the software needed for implementing the methods and procedures described herein may be implemented in a high level procedural or an object-oriented language such as C, C++, C#, Python, Java, or Perl. The software may also be implemented in assembly language if desired. Packet processing implemented in a network device can include any processing determined by the context. For example, packet processing may involve high-level data link control (HDLC) framing, header compression, and/or encryption. In some embodiments, software that, when executed, causes a device to perform the methods described herein may be stored on a computer-readable medium such as read-only memory (ROM), programmable-read-only memory (PROM), electrically erasable programmable-read-only memory (EEPROM), flash memory, or a magnetic disk that is readable by a general or special purpose-processing unit to perform the processes described in this document. The processors can include any microprocessor (single or multiple core), system on chip (SoC), microcontroller, digital signal processor (DSP), graphics processing unit (GPU), or any other integrated circuit capable of processing instructions such as an x86 microprocessor.
- In some embodiments, the radio transceivers described herein may be base stations compatible with a Long Term Evolution (LTE) radio transmission protocol or air interface. The LTE-compatible base stations may be eNodeBs. In addition to supporting the LTE protocol, the base stations may also support other air interfaces, such as UMTS/HSPA, CDMA/CDMA2000, GSM/EDGE, GPRS, EVDO, 2G, 3G, 5G, TDD, or other air interfaces used for mobile telephony.
- In some embodiments, the base stations described herein may support Wi-Fi air interfaces, which may include one or more of IEEE 802.11a/b/g/n/ac/af/p/h. In some embodiments, the base stations described herein may support IEEE 802.16 (WiMAX), to LTE transmissions in unlicensed frequency bands (e.g., LTE-U, Licensed Access or LA-LTE), to LTE transmissions using dynamic spectrum access (DSA), to radio transceivers for ZigBee, Bluetooth, or other radio frequency protocols, or other air interfaces.
- The foregoing discussion discloses and describes merely exemplary embodiments of the present invention. In some embodiments, software that, when executed, causes a device to perform the methods described herein may be stored on a computer-readable medium such as a computer memory storage device, a hard disk, a flash drive, an optical disc, or the like. As will be understood by those skilled in the art, the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. For example, wireless network topology can also apply to wired networks, optical networks, and the like. The methods may apply to LTE-compatible networks, to UMTS-compatible networks, or to networks for additional protocols that utilize radio frequency data transmission. Various components in the devices described herein may be added, removed, split across different devices, combined onto a single device, or substituted with those having the same or similar functionality.
- Although the present disclosure has been described and illustrated in the foregoing example embodiments, it is understood that the present disclosure has been made only by way of example, and that numerous changes in the details of implementation of the disclosure may be made without departing from the spirit and scope of the disclosure, which is limited only by the claims which follow. Various components in the devices described herein may be added, removed, or substituted with those having the same or similar functionality. Various steps as described in the figures and specification may be added or removed from the processes described herein, and the steps described may be performed in an alternative order, consistent with the spirit of the invention. Features of one embodiment may be used in another embodiment.
Claims (18)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/486,907 US11638181B2 (en) | 2020-09-25 | 2021-09-27 | Method to retrieve security keys of UE in gateways |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US202063083263P | 2020-09-25 | 2020-09-25 | |
US17/486,907 US11638181B2 (en) | 2020-09-25 | 2021-09-27 | Method to retrieve security keys of UE in gateways |
Publications (2)
Publication Number | Publication Date |
---|---|
US20220104080A1 true US20220104080A1 (en) | 2022-03-31 |
US11638181B2 US11638181B2 (en) | 2023-04-25 |
Family
ID=80821910
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/486,907 Active US11638181B2 (en) | 2020-09-25 | 2021-09-27 | Method to retrieve security keys of UE in gateways |
Country Status (1)
Country | Link |
---|---|
US (1) | US11638181B2 (en) |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110223919A1 (en) * | 2008-11-21 | 2011-09-15 | Vikberg Jari | Network Gateway Configured to Provide a Handover, Converting and Routing Function |
US20110269465A1 (en) * | 2010-04-28 | 2011-11-03 | Beijing Samsung Telecom R & D Center | Handover method and apparatus in mobile communication system |
US20110286429A1 (en) * | 2008-11-21 | 2011-11-24 | Vikberg Jari | Gateway configured to provide a handover, converting and routing function |
US20130301610A1 (en) * | 2010-11-08 | 2013-11-14 | Motorola Mobility Llc | Wireless communication system, method of routing data in a wireless communication system, and method of haning over a wireless communication device, having an established data connection to a local network |
US20140192782A1 (en) * | 2011-08-24 | 2014-07-10 | Telefonaktiebolaget L M Ericsson (Publ) | Gateway device for handling ue context and a method thereof |
US20140308959A1 (en) * | 2013-04-15 | 2014-10-16 | Nokia Siemens Networks Oy | Methods and Apparatus for Handover Management |
US20150172964A1 (en) * | 2012-01-18 | 2015-06-18 | Zte Corporation | Ue context release method, enb and home enb gateway |
US20160105838A1 (en) * | 2014-10-13 | 2016-04-14 | At&T Intellectual Property I, Lp | System and Methods for Managing a User Data Path |
US20190268815A1 (en) * | 2018-02-26 | 2019-08-29 | Qualcomm Incorporated | User plane function (upf) duplication based make before break handover |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11425790B2 (en) | 2019-09-15 | 2022-08-23 | Parallel Wireless, Inc. | 4G/5G core interworking |
-
2021
- 2021-09-27 US US17/486,907 patent/US11638181B2/en active Active
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110223919A1 (en) * | 2008-11-21 | 2011-09-15 | Vikberg Jari | Network Gateway Configured to Provide a Handover, Converting and Routing Function |
US20110286429A1 (en) * | 2008-11-21 | 2011-11-24 | Vikberg Jari | Gateway configured to provide a handover, converting and routing function |
US20110269465A1 (en) * | 2010-04-28 | 2011-11-03 | Beijing Samsung Telecom R & D Center | Handover method and apparatus in mobile communication system |
US20130301610A1 (en) * | 2010-11-08 | 2013-11-14 | Motorola Mobility Llc | Wireless communication system, method of routing data in a wireless communication system, and method of haning over a wireless communication device, having an established data connection to a local network |
US20140192782A1 (en) * | 2011-08-24 | 2014-07-10 | Telefonaktiebolaget L M Ericsson (Publ) | Gateway device for handling ue context and a method thereof |
US20150172964A1 (en) * | 2012-01-18 | 2015-06-18 | Zte Corporation | Ue context release method, enb and home enb gateway |
US20140308959A1 (en) * | 2013-04-15 | 2014-10-16 | Nokia Siemens Networks Oy | Methods and Apparatus for Handover Management |
US20160105838A1 (en) * | 2014-10-13 | 2016-04-14 | At&T Intellectual Property I, Lp | System and Methods for Managing a User Data Path |
US20190268815A1 (en) * | 2018-02-26 | 2019-08-29 | Qualcomm Incorporated | User plane function (upf) duplication based make before break handover |
Also Published As
Publication number | Publication date |
---|---|
US11638181B2 (en) | 2023-04-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20230328845A1 (en) | 5G Interoperability Architecture | |
US11711685B2 (en) | Support for CUPS PFCP session at UE level for serving gateway | |
US11483790B2 (en) | Multiple context issue for single UE in the network | |
US11924926B2 (en) | 4G/5G core interworking | |
US20210051745A1 (en) | SON Assisted RAT Selection for UE in a Virtualized RAN Environment | |
US11470505B2 (en) | Support for linking of packet detection rules (PDR) for optimizing throughput of combined serving gateway (SGW)/packet gateway (PGW) architecture | |
US20220330354A1 (en) | Mesh Connectivity Establishment | |
US20200396785A1 (en) | Multi-RAT Dual Connectvity | |
US11638181B2 (en) | Method to retrieve security keys of UE in gateways | |
US20220116832A1 (en) | Inter Virtual-eNodeB Optimized Handover for Gateway Core Network (GWCN) | |
US20220353751A1 (en) | CSFB with RIM Without Network Support | |
US20220124577A1 (en) | Handover Forking Support for Improving Handover Success Rate in LTE | |
US11611898B2 (en) | Slow eNodeB/HNB identification and impact mitigation | |
US20230072249A1 (en) | Distributed Paging Optimization | |
US20230155893A1 (en) | Optimization of E2 Signaling and Reducing Load and Complexity on eNodeBs/gNodeBs | |
US20220116383A1 (en) | Enterprise Multi-Technology Core and Subscriber Management | |
US11936620B2 (en) | Randomized SPI for distributed IPsec | |
US20220110040A1 (en) | SON Assisted Optimized RAT Selection For UE In A Virtualized RAN Environment | |
US20220272600A1 (en) | S1AP Optimal Retransmission | |
US20230008393A1 (en) | X2GW Multi-Cell Support | |
US20210250839A1 (en) | FAR ID Provisioning During Dedicated Bearer Creation | |
US20230030933A1 (en) | Optimized S1-X2 Handovers | |
US11889470B2 (en) | Paging optimization | |
US20230043184A1 (en) | ENDC Connectivity with Virtualized eNBs | |
US20230361929A1 (en) | Outer-Loop Adaptation |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO SMALL (ORIGINAL EVENT CODE: SMAL); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
AS | Assignment |
Owner name: PARALLEL WIRELESS, INC., NEW HAMPSHIRE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NANDYAL, ARJUN;REEL/FRAME:058415/0379 Effective date: 20211214 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
AS | Assignment |
Owner name: WTI FUND X, INC., CALIFORNIA Free format text: SECURITY INTEREST;ASSIGNOR:PARALLEL WIRELESS, INC.;REEL/FRAME:059279/0851 Effective date: 20220225 Owner name: VENTURE LENDING & LEASING IX, INC., CALIFORNIA Free format text: SECURITY INTEREST;ASSIGNOR:PARALLEL WIRELESS, INC.;REEL/FRAME:059279/0851 Effective date: 20220225 |
|
AS | Assignment |
Owner name: PARALLEL WIRELESS, INC., NEW HAMPSHIRE Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:VENTURE LENDING & LEASING IX, INC.;WTI FUND X, INC.;REEL/FRAME:060900/0022 Effective date: 20220629 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |