Network access optimization in private 5g networks resolving plmn id conflicts

Abstract

This application relates to network access optimization in private 5G networks that address PLMN ID conflicts. Systems and methods are provided for improving network acquisition procedures for user equipment (UE) performing initial registration, mobility registration, periodic registration, or service request on a private network. For example, a base station can route signaling for a UE to an AMF for a GUAMI. If the base station is unable to identify the reported GUAMI, the base station can decide that the UE is a non-subscribed UE and that it should use an RRC connection release procedure to release the RRC connection for the UE. In another example, a UE can exchange non-access stratum (NAS) messages with an AMF that include a GUAMI. The AMF can be configured with a list of approved GUAMIs and can check whether the GUAMI for the UE belongs to the list of supported GUAMIs. If the GUAMI cannot be identified, the UE can be rejected.

Description

Background Technology

[0001] There are countless communication-ready devices on a cellular network. To help manage communications of user equipment (UEs) on public networks, public mobile operators are assigned unique identifiers. These unique identifiers are typically assigned by the International Telecommunication Union (ITU) or national / regional regulatory authorities. Unique identifiers are assigned to each public network provider, and public network providers can provide unique identifiers to UEs so that UEs can use the network.

[0002] When a UE searches for its network, it can provide a unique identifier that allows the UE to be matched with a public network provider. The public network provider, along with its corresponding network components (such as base stations, access and mobility management functions (AMF), and unified data management (UDM)), can identify whether the UE is permitted to transmit communications on its network. Attached Figure Description

[0003] This disclosure is described in detail with reference to the following figures, based on one or more various examples. These figures are provided for illustrative purposes only and depict only typical, non-limiting aspects of such examples.

[0004] Figure 1 The illustration shows an example communication system in which the disclosed techniques can be implemented;

[0005] Figure 2 The illustration shows an example message flow based on the disclosed technology.

[0006] Figure 3 The illustration shows an example message flow based on the disclosed technology.

[0007] Figure 4 The illustration shows an example registration process based on the disclosed technology.

[0008] Figure 5 It is an example computing component that can be used to implement various features of the disclosed technology.

[0009] Figure 6 The illustration shows an example message flow based on the disclosed technology.

[0010] Figure 7 It is an illustrative 3GPP 5G-GUTI data format based on examples of the disclosed technology.

[0011] Figure 8 The illustration shows an example registration process based on the disclosed technology.

[0012] Figure 9It is an example computing component that can be used to implement various features of the disclosed technology.

[0013] Figure 10 It is an example computing component that can be used to implement various features of the disclosed technology.

[0014] Figure 11 A block diagram depicts an example computer system that can implement various examples of the publicly disclosed techniques described herein.

[0015] The accompanying drawings are not exhaustive and do not limit this disclosure to the precise form disclosed. Detailed Implementation

[0016] In some current communication networks, a globally unique Public Land Mobile Network (PLMN) identifier (ID) can be assigned to the network. The PLMN ID can be broadcast by the base station to UEs within the network coverage area. Once the PLMN ID is received and decoded, the UE can compare the received PLMN ID with its stored PLMN ID to determine whether the detected network belongs to the UE's home PLMN or an equivalent PLMN, thereby determining whether it should attempt to request access to the detected network.

[0017] A PLMN ID consists of a 3-digit Mobile Country Code (MCC) and a 2-3 digit Mobile Network Code (MNC). The assignment of MCC and MNC is managed accordingly by the ITU-T and the regulatory authorities of each region to ensure that each Mobile Network Operator (MNO) is assigned a globally unique PLMN ID.

[0018] This document describes various “base stations,” and in some examples, the descriptions of these base stations may be interchangeable based on the type of network implemented without departing from the essence of the disclosed technology. For example, a gNodeB or gNB is a 5G radio base station that uses an NR radio interface to connect 5G New Radio (NR) UEs to a 5G core network. An ng-eNodeB is a 4G LTE radio base station that uses an LTE radio interface to connect 4G LTE devices to a 5G core network. An eNodeB or eNB is a Long Term Evolution (LTE) radio base station that connects LTE-enabled UEs to a 4G core network. Some base stations can operate in 5G spectrum, including low-band spectrum (i.e., spectrum below 1 GHz); mid-band spectrum (i.e., spectrum below 6 GHz); and / or high-band spectrum, such as millimeter wave (mmWave) operating between 25 GHz and 100 GHz.

[0019] However, the regulatory body allocates only a limited number of PLMN IDs for use by private networks around the world, resulting in private network operators sharing PLMN IDs. In other words, private operators do not have access to their own unique PLMN ID. Instead, PLMN IDs are defined by geographic location and shared among multiple private network operators within a specific geographic area (e.g., including 262-98 in Germany; 240-41, 240-49, 240-65, and 240-66 in Sweden; and 315-010 in the United States).

[0020] Because of the potential for a large number of private networks and the lack of centralized control over the management of the PLMN IDs of each of these private networks, it is difficult for each private network to use its PLMN ID to distinguish itself from other private networks in the same geographic area. For example, in the United States, there are currently thousands of private networks deployed on specific spectrums that share the same PLMN ID. When a UE attempts to attach to a private network based on the detection of the network PLMN ID broadcast by the base station, the UE cannot determine whether the broadcast PLMN ID belongs to a preferred network or a private network it has not signed a contract with.

[0021] By preventing the UE from making this initial determination, the UE could initiate an attempt to obtain network access to a private network to which it does not belong, which may ultimately fail. Attempts to obtain network access could include transmitting multiple unnecessary communications to these networks, potentially wasting over-the-air resources and the processing power of network components (e.g., base stations, AMFs, and UDMs) in those networks configured to handle these requests. Therefore, a lack of a sufficient number of private network PLMN IDs to distinguish private networks from each other can lead to PLMN ID conflicts in communications using overlapping PLMN IDs between private cellular networks (e.g., multiple private networks using the same PLMN ID).

[0022] This disclosure provides several examples of modifying the behavior or infrastructure of current communication network frameworks when processing network attachment requests from UEs, thereby minimizing the waste of network resources.

[0023] The first example illustrates an improved network acquisition procedure when a UE performs initial registration, mobility registration, periodic registration, or service request. The acquisition procedure can be initiated by the UE. For example, in a 5G communication system, the UE can provide a globally unique AMF ID (GUAMI) in the Radio Resource Control (RRC) SETUP COMPLETE message specified in Section 5.3.3.4 of TS 38.331. This GUAMI is an identifier of the AMF the UE can register with in its previous 5G sessions. The base station can then route the UE's signaling to the AMF with that GUAMI. If the base station does not recognize the reported GUAMI from the UE, it can determine that the UE is an uncontracted UE, and it should release the UE's RRC connection using the RRC connection release procedure defined in Section 5.3.8 of TS 38.331. Therefore, by releasing the UE's RRC connection, air resources and the processing capacity of network components configured to handle these requests (e.g., base station, AMF, and UDM) are not wasted.

[0024] In some examples, the GUAMI list can contain both native and mapped GUAMIs. Even after a change in the communication system, a native GUAMI may correspond to a GUAMI value that remains unchanged, while a mapped GUAMI may correspond to a GUAMI value that changes after the communication system change. The AMF can use the presence of native / mapped GUAMI indications to distinguish the type of communication system the UE was registered to in a previously successful registration. This determination can be performed based on an explicit indication sent from the UE to the base station in the RRC establishment completion message, and can also be relayed to the AMF by the base station in the initial UE message.

[0025] In some examples, the UE can provide a mapped GUAMI instead of a native GUAMI in the RRC setup completion message. This GUAMI can be mapped from a Globally Unique Mobility Management Entity (MME) Identifier (GUMMEI), which corresponds to the identifier of the MME to which the UE can register in its previous sessions. The base station can route the UE's signaling to the MME with that GUMMEI. If the base station does not recognize the reported mapped GUAMI from the UE, it can determine that the UE is an uncontracted UE and it should use the RRC connection release procedure to release the UE's RRC connection. Therefore, by releasing the UE's RRC connection, air resources and the processing capacity of network components configured to handle these requests (e.g., base station, MME, HSS / HLR, and UDM) are not wasted.

[0026] In some examples, the base station can configure the UE not to attempt further network acquisition within the same base station coverage area for a specific time period by including a waitTime parameter. This waitTime parameter is used to set the UE's T302 timer (defined in Section 7.1 of TS 38.331). Therefore, it can prevent the UE from transmitting multiple unnecessary communications to network components in an attempt to acquire network access.

[0027] In some examples, the base station is configured with the complete GUAMI list of the AMF by its serving AMF during the Next Generation (NG) setup procedure or AMF configuration update procedure (as specified accordingly in Sections 8.7.1 and 8.7.3 of TS 38.413). The GUAMI list may include the identifier of the AMF of the roaming partner network to support subscriber roaming between 5G private enterprise networks, and includes mapped GUAMIs of the MME (as specified in Section 2.10.2 of TS 23.003) to support subscriber roaming from 4G networks to 5G networks.

[0028] In other examples, the base station is configured with a complete list of GUMMEIs of the MME by its serving MME during the S1 setup procedure or MME configuration update procedure (as specified accordingly in Sections 8.7.3 and 8.7.5 of TS 36.413). The GUMMEI list may include the identifiers of the MMEs of roaming partner networks to support subscriber roaming between 4G private enterprise networks, and includes mapped GUMMEIs of AMFs (as specified in Section 2.10.2 of TS 23.003) to support subscriber roaming from 5G networks to 4G networks.

[0029] The second example also implements an improved network acquisition procedure when the UE performs initial registration, mobility registration, or periodic registration (e.g., by submitting a registration request to the AMF / MME). This procedure can be initiated by the UE. For example, the UE can exchange Non-Access Stratum (NAS) information with the AMF or MME. As specified in Section 5.3.3.4 of TS 38.331 or TS 36.331 and Section 8.6.1 of TS 38.413 or Section 8.6.2.1 of TS 36.413, the NAS information can be encapsulated in an over-the-air RRC setup completion message between the UE and the base station, and in an initial UE message between the base station and the AMF or MME via the NG or S1 interface. The NAS information may include the UE's 5G Globally Unique Temporary Identifier (5G-GUTI) or GUTI, which the UE obtains from a previous successful registration with its 5G home PLMN or 4G home PLMN. The 5G-GUTI contains the GUAMI information specified in Section 5.9.4 of TS 23.501, and the GUTI includes the GUMMEI information specified in Section 5.2.2 of TS 23.401. In this example, the AMF or MME can be configured with an approved list of GUAMIs (or an approved list of GUMMEIs), and the UE's GUAMI or GUMMEI can be checked to see if it belongs to the list of supported GUAMIs or GUMMEIs. If no GUAMI or GUMMEI is identified, the UE can be rejected without further consuming Radio Access Network (RAN) or Core Network (CN) resources. As specified in Section 5.5.1 of TS 24.501 or TS 23.501, a rejection can be implemented using Cause #15 "No suitable cell in the tracking area" to allow the UE to attempt to acquire access to a network in a different tracking area. Rejection can also be implemented using reasons other than Cause #15, if appropriate. Therefore, the AMF or MME can initiate a rejection of the UE's registration request and further instruct the base station to release the UE's RRC connection. This can help prevent the UE from transmitting multiple unnecessary communications to RAN or CN resources. It can also help save air resources and network component processing power. The GUAMI or GUMMEI list can include the identifier of the AMF (or MME) of the roaming partner network to support subscriber roaming between private enterprise networks, and / or include the mapped GUAMI (or mapped GUMMEI of the AMF) of the MME in the roaming partner's 4G (or 5G) communication system.

[0030] Technical improvements are achieved throughout this disclosure. For example, both the first and second examples can improve network processing by reducing the amount of communication transmitted at least between the UE, base station, and AMF. Reduced communication may also result in reduced signal load on the air interface and network resources. Additionally, network acquisition attempts by uncontracted UEs may not contact the UDM and other devices in the core / central logical network. The UDM can be configured to handle the registration, authorization, and authentication processes for all contracted UEs, so reducing communication with this device can improve overall network stability and reliability by helping to prevent UDM outages due to signaling overload.

[0031] Figure 1 This is an illustrative cellular communication system 100 that can implement various examples of the present disclosure. Cellular communication system 100 may include three private networks, including a 4G communication system 120 and a first 5G communication system 130 as roaming partners, and a second 5G communication system 160 that has no partnership with the 4G communication system 120 and the first 5G communication system 130.

[0032] The diagram also illustrates various components of the cellular communication system 100, including multiple base stations or cells (e.g., base stations 102, 106, 166) and user equipment (UE) 104 (including UE 104a and UE 104b). Base stations 102, 106, and 166 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Figure 1 In the illustrative example, base station 102 is configured according to the 4G / LTE standard and is connected to the 4G communication system 120 via the S1 interface. Base stations 106 and 166 are configured according to the 5G standard and are connected to the first 5G communication system 130 and the second 5G communication system 160 via the N1 / N2 interfaces.

[0033] Base stations 102, 106, and 166 can wirelessly communicate with one or more UEs 104. For example, each of base stations 102, 106, and 166 can provide communication coverage for corresponding geographic coverage areas 110 and 112. In some scenarios, these geographic coverage areas may overlap. For example, base station 102 may have a coverage area 110 that overlaps with the coverage area 112 of one or more other base stations, such as base station 106 shown.

[0034] Although a single base station 102 (e.g., a base station configured for 4G / LTE) and two base stations 106, 166 (e.g., base stations configured for 5G) are illustrated, the cellular communication system disclosed herein is not limited thereto. One or more base stations 102 and / or one or more base stations 106 may be provided. For example, multiple base stations 102 may be provided, each with a corresponding coverage area 110. One or more of the corresponding coverage areas 110 may overlap. Similarly, multiple base stations 106 may be provided, each with a corresponding coverage area 112. One or more of the corresponding coverage areas 112 may overlap. Furthermore, one or more coverage areas 110 may overlap with one or more coverage areas 112.

[0035] The 4G communication system 120 includes various network function entities, including, but not limited to, one or more MMEs 122, Serving Gateways (S-GW) (not shown), Packet Data Network (PDN) Gateways (not shown), and other network function entities. In some examples, MME 122 may be used herein to refer to one or more of the following: an MME, a Serving General Packet Radio Service (GPRS) Support Node (SGSN), an S4-SGSN (e.g., an SGSN that can interface with a 4G network), an Access Location Register (VLR), or similar network function entities included in the 4G communication system. The term "traditional mobility management equipment" may also be used herein to refer to one or more of the SGSN, S4-SGSN, VLR, etc. Additionally, "location and service information interface" may be used to refer to one or more of the S6a, S6d, D, Gr, or similar interfaces between the HSS and the corresponding mobility management equipment. Although in Figure 1 The diagram illustrates MME 122, but the device can correspond to any type of mobility management device, and these terms are used interchangeably in this disclosure.

[0036] Each MME 122 can communicate with the Home Subscriber Server (HSS) 140 via a designated interface (e.g., the S6a interface for exchanging subscriber authentication, location, and server information between the HSS 140 and the MME 122). Each MME 122 can serve as a control node for handling signaling between the UE 104 and the 4G communication system 120, including providing bearer and connection management functions. The Packet Data Network (PDN) gateway can be connected to IP services such as the Internet, intranets, IP Multimedia Subsystem (IMS), Packet Switched (PS) streaming services, and / or other IP services.

[0037] The network function (NF) of the 4G communication system 120 can be implemented as a computing system, such as one or more servers. The NF of the EPC 120 can communicate using protocols such as the Diameter protocol and / or the SS7 protocol's Mobile Application Part (MAP). For example, the Diameter protocol can be used for message transmission between the MME and HSS or between the S4-SGSN and HSS, while the MAP can be used for message transmission between the Home Location Register (HLR) and the SGSN or VLR. Data included in messages on the 4G communication system can be formatted according to the U.S. Standard Code for Information Interchange (ASCII) protocol.

[0038] The first 5G communication system 130 may include various virtualized NFs, such as, but not limited to, Authentication Server Function (AUSF) (not shown), AMF 132, Policy Control Function (PCF) (not shown), Session Management Function (SMF) (not shown), Unified Data Repository (UDR) 134, and Network Repository Function (NRF) 136 (to name just a few). For example, AMF 132 may be a control node that processes signaling between UE 104 and the first 5G communication system 130 via base station 106.

[0039] The AMF 132 can receive connection and mobility management tasks from the UE 104 and can process connection and mobility management tasks while forwarding session management tasks / messages to the Session Management Function (SMF). The AMF 132 can communicate with the UDM 150 through a service-based interface (SBI) (such as the Nudm interface).

[0040] The first 5G communication system 130 may also include an NRF 136 that provides network function service registration, authorization, and discovery, and otherwise enables network functions to identify each other. The first 5G communication system 130 may also include a user plane function (UPF) (not shown) connected to an IP service, which may include the Internet, an intranet, IMS, PS streaming service, and / or other IP services.

[0041] The NF of the first 5G communication system 130 can be implemented as a computing system, such as one or more servers. The NF of the first 5G communication system 130 can communicate using protocols such as Hypertext Transfer Protocol (HTTP). For example, HTTP methods (such as POST, PATCH, GET, PUT, etc.) can be used to send communications and operations.

[0042] As mentioned in this article, the AMF 132 can receive connection and session-related information from the UE across the N1 / N2 reference point interface (between the UE and the AMF / between the RAN and the AMF) and can handle connection and mobility management tasks. That is, the AMF instance can be assigned to the UE in a NAS message routed from the RAN to the AMF instance, for example, UE 104a or 104b. Performing the access point role of the 5G core network (terminating RAN and UE control plane traffic), the AMF instance can authenticate the UE and manage, for example, the UE's handover between base stations.

[0043] The second 5G communication system 160 may include various virtualized NFs similar to the first 5G communication system 130, such as, but not limited to, AMF 162, UDR 164, and NRF 167 (to name just a few). For example, AMF 162 may be a control node that processes signaling between the UE and the second 5G communication system 160 via base station 166. AMF 162 may receive connection and mobility management tasks from UE 104 and may process connection and mobility management tasks while forwarding session management tasks / messages to SMF. AMF 162 may communicate with UDM 165 via its SBI (such as the Nudm interface). NRF 167 provides network function service registration, authorization, and discovery, and otherwise enables network functions to identify each other.

[0044] UDM 150 and 165 provide services to other functions of the Service-Based Architecture (SBA), such as AMF 132 and 162 and other network functions. UDM 150 and 165 can store information in local storage. UDM 150 and 165 can also store information externally, for example, within UDR 134 and 164 respectively. UDM 150 and 165 can provide authentication credentials when used by AMF 132 and 162 to retrieve subscriber data and access registration context data.

[0045] While the preceding description provides examples of 5G-based communication systems, it should be understood that the concepts described herein can be applied to other types of telecommunications networks, including 4G / LTE. For example, the concepts described herein can be applied to legacy networks such as GPRS, CDMA, GSM, and / or other wireless technologies in which the UE can operate. For instance, the 4G communication system 120 may include network functions of a legacy type of telecommunications network. The GPRS core network may include an SGSN configured to perform functions similar to MME 122. The 4G communication system 120 may include, or be communicatively coupled to, an SGSN 124, which communicates with the HSS 140 via a designated interface, such as a Gr interface for routing information between the SGSN 124 and the HSS / HLR 140. In some GPRS core networks, the S4-SGSN is used to perform functions similar to MME 122. The 4G communication system 120 may include or be communicatively coupled to an S4-SGSN 126, which communicates with the HSS 140 via a designated interface, such as an s6d interface for exchanging authentication, location, and server information about subscribers between the HSS 140 and the S4-SGSN 126. The GSM core network includes an Access Location Register (VLR) configured to perform functions similar to those of the MME 122 and an HLR performing functions similar to those of the HSS 140. The 4G communication system 120 may include or be communicatively coupled to a VLR 128, which communicates with the HSS 140 via a designated interface, such as a D interface for routing information between the VLR 128 and the HSS / HLR 140.

[0046] exist Figure 1 In the illustrated example, three private networks (including 4G communication system 120, the first 5G communication system 130, and the second 5G communication system 160) are assigned the same PLMN ID because all private networks in the area are assigned only one PLMN ID. In the example scenario, when UE 104 moves out of the coverage area of ​​base station 102 of communication system 120, it can detect base station 166 and initiate an initial registration process because the PLMN ID broadcast by base station 166 is the same as the PLMN ID broadcast by base station 106 (eNB), which is provided in UE 104's SIM / eSIM as the home PLMN ID or equivalent PLMN ID. At this time, UE 104 may (erroneously) determine that base station 166 belongs to its subscribed preferred network. In this example, UE 104 can rely on base station 166 and the corresponding 5G communication system 160 to process UE 104's registration process. Additional details regarding the communication process in the receiving network (e.g., 5G communication system 160) are further provided in this document.

[0047] Figure 2 An example message flow based on the disclosed technology is illustrated. In this example, a 5G communication system is illustrated, including UDM 208, AMF 206, base station 204, and UE 202, corresponding accordingly. Figure 1 The examples include UDM 165, AMF 162, base station 166, and UE 104. In this example, when UE 202 attempts to attach to a private network based on the detection of a network PLMN ID broadcast by base station 204 for a private network, UE 202 cannot determine whether the broadcast PLMN ID belongs to a preferred network or a private network to which it is not subscribed. UE 202 may initiate an attempt to obtain network access to a private network to which it does not belong, which may ultimately fail. Attempts to obtain network access may include transmitting multiple unnecessary communications to these networks, which may waste air resources and the processing power of network components (e.g., base station 204, AMF 206, and UDM 208) in those networks configured to handle these requests.

[0048] For example, at box 218, AMF 206 can construct a GUAMI list. The GUAMI list can include the identifiers of the roaming partner's AMF and / or MME. For instance, AMF 206 can construct a GUAMI list that includes all identifiers of the AMF belonging to the private network and all identifiers of the AMF and / or MME of the roaming partner's public or private network (e.g., the roaming partner's network) interconnected with the private network. When implementing the GUMMEI list, the MME's GUMMEI can be mapped to the UE's GUMMEI based on the operations specified in Section 2.10.2 of TS23.003.

[0049] At box 220, AMF 206 may transmit / provide a list of GUAMIs to base station 204 in an NG SETUP RESPONSE message. Since the GUAMIs are included in the NG SETUP RESPONSE message from AMF 206, base station 204 may store the received values ​​and use them for further AMF selection, as defined in TS 23.501 (box 226).

[0050] At box 222, UE 202 can transmit an RRC / RRC SETUPCOMPLETE message to base station 204. RRC SETUPCOMPLETE indicates that a Radio Resource Control (RRC) connection has been established and completed. The RRC / RRC SETUPCOMPLETE message may include GUAMI and NAS-PDU messages. The NAS message may include Protocol Data Unit (PDU) session requests or releases to establish and release PDU sessions in 5G. The NAS-PDU message may correspond to a RegReq (Registration Request) message or a SerReq (Service Request) message.

[0051] At block 224, base station 204 may determine that the GUAMI from UE 202 is invalid. For example, a GUAMI may be invalid if it is not included in the GUAMI list by a comparison operation at base station 204. However, as defined in TS 23.501, base station 204 may continue to select an AMF despite the GUAMI being invalid. Blocks 220, 222, and 224 may correspond to a first message flow procedure 280, in which base station 204 identifies that the GUAMI received from UE 202 is invalid.

[0052] At box 226, base station 204 can initiate an AMF selection process that includes AMF 206. Base station 204 can select AMF 206 based on factors such as network slicing, UE capabilities, and location information. The selection of AMF helps determine which core network component will handle the registration and mobility management of UE 202 within the network.

[0053] At box 228, base station 204 may transmit an NGAP / INITIAL UE MESG to AMF 206 to initiate a connection procedure. The NGAP / INITIAL UE MESG message may include a NAS-PDURegReq message or a SerReq message with the identifier of UE 202. For example, when transmitting a RegReq message, the message may include the Globally Unique Temporary Identifier (GUTI) of UE 202. When transmitting a SerReq message, the message may include the S-Temporary Mobile Subscriber Identifier (S-TMSI) of UE 202.

[0054] At box 230, AMF 206 can determine that the check process corresponding to the NAS-PDU RegReq message has failed. For example, AMF 206 can determine that the GUTI check has failed in response to the RegReq message, or it can determine that the S-TMSI check has failed in response to the SerReq message.

[0055] At box 232, AMF 206 can transmit an NGAP / DL NAS transfer (NGAP / DL NASTRANSPORT) message to base station 204. The downlink NAS transfer procedure can be used to transparently transmit NAS messages to UE 202 via base station 204. In this example, the NGAP / DL NAS transfer message may include a NAS-PDU containing IdentityReq, AMF UE NGAP-ID, and RAN UE NGAP ID.

[0056] At box 234, base station 204 can transmit an RRC / DL INFO transmission (RRC / DL INFOTRANSFER) message to UE 202. This message delivers RRC configuration information to UE 202, instructing UE 202 on how to access the network and manage radio resources, including details such as which cells to use and how to transmit data. The RRC / DL INFO transmission message may include a NAS-PDU message with IdentityReq.

[0057] At box 236, UE 202 may transmit an RRC / UL INFO transmission (RRC / UL INFOTRANSFER) message to base station 204. The RRC / UL INFO transmission message may include a NAS-PDU message with an IdentityRsp (identification response), which includes a Subscribed Hidden Identifier (SUCI). UE 202 can obtain the SUCI by using the public key of the provided Home PLMN (HPLM).

[0058] At box 238, base station 204 can transmit NGAP / UL NAS Transport (NGAP / UL NASTRANSPORT) messages to AMF 206. UL NAS Transport messages may include NAS-PDU messages with an IdentityReq, which includes a SUCI.

[0059] At box 240, AMF 206 can transmit AuthReq (authentication request) with SUCI to UDM 208.

[0060] At box 242, UDM 208 can determine that the SUCI check failed.

[0061] At box 244, UDM 208 can transmit AuthReject to AMF 206.

[0062] At box 246, AMF 206 can transmit NGAP / DL NAS transmission messages to base station 204. NGAP / DL NAS transmission messages may include NAS-PDUs with RegReject (registration rejected).

[0063] At box 248, base station 204 may transmit an RRC / DL INFO transmission message to UE 202. The RRC / DL INFO transmission message may include a NAS-PDU message with a RegReject message. The RegReject message may include reason #15 as the reason for rejection. Reason #15, "No suitable cell in the tracking area," allows UE 202 to attempt to obtain access to a network in a different tracking area, as specified in section 5.5.1.1 of TS 24.501.

[0064] At box 250, AMF 206 can transmit an NGAP / UE context release command (NGAP / UECONTEXT RELEASE COMMAND) message to base station 204. AMF 206 can send a message to base station 204 to initiate the release of the context of UE 202. This can instruct base station 204 to release resources allocated to a specific UE (UE 202) on its network.

[0065] At box 252, base station 204 can transmit an RRC / RRC release message to UE 202. For example, upon receiving a UE context release command message, base station 204 can release all associated signaling and user data transmission resources.

[0066] At box 254, base station 204 can transmit the NGAP / UE context release complete (NGAP / UECONTEXT RELEASE COMPLETE) message to AMF 206.

[0067] Figure 3 An example message flow based on the disclosed technology is illustrated. In this example, a 5G communication system is illustrated, including UDM 308, AMF 306, base station 304, and UE 302, corresponding accordingly. Figure 2 UDM 208, AMF 206, base station 204, and UE 202 are included.

[0068] Compare Figure 2 The first message flow process 280 and Figure 3The second message flow procedure 380, and both message flow procedures can implement the GUAMI list generated by AMF 306 and stored at base station 304. However, in the second message flow procedure 380, base station 304 can adjust its response to the GUAMI list by preventing base station 304 from selecting AMF for invalid GUAMIs. When UE 302 attempts to establish a connection / authenticate with the network, the second message flow procedure 380 can additionally update the rules implemented by base station 304 to access the GUAMI list, and initiate registration determination at base station 304 instead of AMF 306. Figure 2 The first message stream process 280 in the middle is updated to Figure 3 In the second message flow process 380, the additional messages within the message flow may be unnecessary and will not be sent over the network in the second message flow process 380.

[0069] At box 310, AMF 306 can construct a GUAMI list that includes the identifiers of the roaming partner's AMF and / or MME. For example, AMF 306 can construct a GUAMI list that includes all identifiers of the AMF belonging to the current private network and all identifiers of the AMF and / or MME of the roaming partner's public or private network (e.g., the roaming partner's network) interconnected with that private network. When implementing the GUMMEI list, the MME's GUMMEI can be mapped to the UE's GUMMEI based on the operations specified in Section 2.10.2 of TS23.003.

[0070] In some examples, AMF 306 can use a GUAMI list to configure a complete list of GUAMIs for all relevant AMFs for base station 304. This configuration can accordingly utilize the NG establishment procedure or AMF configuration update procedure specified in sections 8.7.1 and 8.7.3 of TS 38.413. In some examples, the GUAMI list may include the identifiers of AMFs in roaming partner networks. This can help support the UE when roaming between various enterprise networks.

[0071] At box 320, AMF 306 can provide / transmit the GUAMI list to base station 304.

[0072] At box 330, base station 304 can store a list of GUAMIs.

[0073] At box 340, UE 302 may transmit an RRC / RRC establishment complete message to base station 304. As specified in section 5.3.3.4 of TS 38.331, UE 302 may include the same GUAMI in the RRC establishment complete message. Figure 2As discussed in box 222, the RRC / RRC setup completion message may include GUAMI and NAS-PDU messages.

[0074] At box 350, base station 304 can determine that the GUAMI from UE 302 is invalid. For example, if base station 304 does not recognize the GUAMI from UE 302, base station 304 can determine that UE 302 is an uncontracted UE, and it should use the standardized RRC connection release procedure to release the UE's RRC connection as defined in section 5.3.8 of TS 38.331.

[0075] In some examples, base station 304 can configure UE 302 to attempt further network acquisition outside the coverage area of ​​the same base station. For example, base station 304 can include a wait time parameter to set the UE's T302 timer. The configuration of the T302 timer can be defined in section 7.1 of TS 38.331.

[0076] At box 360, base station 304 can transmit an RRC / RRC release message to UE 302. The RRC release message is a message instructing UE 302 to enter the RRC idle state and can be sent via the PDCP protocol. For example, upon receiving a UE context release command message, base station 304 can release all related signaling and user data transmission resources and reply to AMF 306 using a UE context release completion message. The RRC / RRC release message may include T302 as the reason for the release.

[0077] Figure 4 An example registration process based on the disclosed technology is illustrated. In this example, a 5G communication system is illustrated. The boxes / steps illustrated herein are performed by any of the devices discussed herein, including... Figure 2 AMF 206 or Figure 3 AMF 306 in the middle.

[0078] At box 405, the process can activate the base station (e.g., via a network management system). For example, the base station can be physically connected to the network, and its settings can be configured using cell information, PLMN ID, and information from the 5G communication system (e.g., via an NF interface). The base station can initiate a registration process with the network to allow it to begin providing services to devices within its coverage area. In some examples, the network management system can configure the base station and its parameters based on a specific vendor and network setup.

[0079] At box 410, this process can initiate an NG SETUP PROCESS. For example, an NG SETUP REQUEST message can be sent from the base station to the AMF to request configuration data. An NG SETUPRESPONSE message can transmit / provide a list of GUAMIs from the AMF to the base station.

[0080] At box 415, the process can store the GUAMI list at the base station.

[0081] At box 420, this process can initiate a registration request or service request from a specific UE. For example, the UE can transmit an RRC / RRC establishment complete message to the base station, which indicates that the RRC connection has been established and completed.

[0082] At box 425, this procedure can initiate RRC for a specific UE. For example, the base station can identify the UE, allocate dedicated radio resources (e.g., SRB, DRB), and generate an RRC CONNECTION SETUP message. This message can be transmitted to the UE on the assigned downlink channel. The UE can send an RRC CONNECTION COMPLETE message to confirm the successful establishment of the RRC connection.

[0083] At box 430, the procedure can determine whether the GUAMI received from the UE is included in the stored GUAMI list. For example, if the GUAMI is not included in the GUAMI list by comparison at the base station, the GUAMI may be invalid. If yes (e.g., the GUAMI is on the list), the procedure can proceed to box 435. If no (e.g., the GUAMI is not on the list), the procedure can proceed to box 450.

[0084] At box 435, this procedure can forward the UE's NAS information to the AMF. For example, the base station can transmit NGAP / Initial UE MESG to the AMF, which includes a NAS-PDU RegReq message or a SerReq message with the UE identifier. The RegReq message may include the UE's GUTI, and the SerReq message may include the UE's S-TMSI.

[0085] At box 440, a NAS registration process can be initiated for the UE. When the registration process fails (e.g., a NAS-PDURegReq message failure), the base station cannot recognize the GUAMI from the UE, and the base station can determine that the UE is an unsubscribed UE. In some examples, the base station can configure the UE to attempt further network acquisition outside the coverage area of ​​the same base station.

[0086] At box 450, the procedure can release the UE's RRC (e.g., using an RRC release message). In some examples, this release may include a T302 code.

[0087] The process can end at box 455.

[0088] Figure 5 The illustration shows a computing component 500 that can be used to execute instructions, according to an example of the disclosed technology. For example, computing component 500 can be a server computer, a controller, or any other similar computing component capable of processing data. Figure 5 In an example implementation, computing component 500 includes a hardware processor 502 and a machine-readable storage medium 504. According to one example of the disclosed technology, computing component 500 can be used to implement, for example, base station functions.

[0089] Hardware processor 502 may be one or more central processing units (CPUs), semiconductor-based microprocessors, and / or other hardware devices suitable for fetching and executing instructions stored in machine-readable storage medium 504. Hardware processor 502 may fetch, decode, and execute instructions (such as instructions 506-514). As an alternative to fetching and executing instructions, or in addition to fetching and executing instructions, hardware processor 502 may include one or more electronic circuits, including electronic components for the function of executing one or more instructions, such as field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), or other electronic circuits.

[0090] Machine-readable storage media (such as machine-readable storage media 504) can be any electronic, magnetic, optical, or other physical storage device that contains or stores executable instructions. Therefore, machine-readable storage media 504 can be, for example, random access memory (RAM), non-volatile RAM (NVRAM), electrically erasable programmable read-only memory (EEPROM), storage devices, optical discs, etc. In some examples, machine-readable storage media 504 can be a non-transient storage medium, where the term "non-transient" does not cover transient propagation signals. As described in detail below, machine-readable storage media 504 can be encoded using executable instructions (e.g., instructions 506-514).

[0091] Hardware processor 502 can execute instructions 506 to receive a list of GUAMIs associated with a communication network. This list can be received by a base station from an AMF (Advanced Management Function) in the communication network. In some examples, the AMF can construct the list of GUAMIs associated with the communication network. The AMF can provide the list of GUAMIs to multiple base stations associated with the AMF.

[0092] Hardware processor 502 can execute instructions 508 to receive a network attachment request from the UE. The network attachment request may include the UE's NAS information. For example, a network attachment request may be initiated when the UE is activated / powered on, reset, or in other instances where the UE is permitted to request network access. In some examples, the network identifier associated with the UE may be the GUAMI of the AMF to which the UE was registered in a previous communication session.

[0093] The hardware processor 502 can execute instruction 510 to compare the GUAMI with the GUAMI list. For example, the AMF can be configured with an approved GUAMI list and can check whether the UE's GUAMI belongs to the list of supported GUAMIs.

[0094] Hardware processor 502 can execute instruction 512 to forward NAS information to AMF. Forwarding can be initiated in response to a GUAMI being identified in the GUAMI list. NAS information may include the UE's GUAMI, and the AMF can be specified by the UE in a NAS message, which is routed from the RAN to the AMF. The AMF can authenticate the UE and manage the UE's handover and other operations between access points and base stations.

[0095] Hardware processor 502 can execute instruction 514 to initiate RCC connection release for the UE in response to identifying that the GUAMI is not on the GUAMI list. In some examples, the initiation of RCC connection release for the UE can be performed immediately after the comparison without contacting the AMF, UDM, and other devices.

[0096] By releasing the UE, multiple unnecessary communications by the UE to the base station for attempting to obtain network access (as described above) can be prevented. Therefore, air resources and the processing capacity of network components configured to handle these requests (e.g., base station, AMF, and UDM) are not wasted.

[0097] Figure 6 An example message flow based on the disclosed technology is illustrated. In this example, a 5G communication system is illustrated, including UDM 608, AMF 606, base station 604, and UE 602, corresponding accordingly. Figure 1 The components include UDM 150, AMF 132, base station 106, and UE 104. Figure 2 The first message flow process 280 and Figure 3 Compared to the second message flow process 380 in the middle, Figure 6The third message flow process 680 can implement the GUAMI list generated by AMF 606 and also stored at AMF 606. The response from AMF 606 can be adjusted by preventing AMF 606 from contacting UDM 608 during the registration process.

[0098] Specifically, the third message flow procedure 680 can implement a list of GUAMI or GUMMEI generated by AMF 606 and stored at AMF 606. The third message flow procedure 680 can configure UE 602 to exchange NAS information with AMF 606. As specified in Section 5.3.3.4 of TS 38.331 and Section 8.6.1 of TS 38.413, the NAS information can be encapsulated in an over-the-air RRC Setup Complete message between UE 602 and base station 604, and in an initial UE message between base station 604 and AMF 606 via the NG interface. The NAS information may include UE 602's 5G-GUTI, which the UE obtained from a previous successful registration with its home PLMN. As specified in Section 5.9.4 of TS 23.501, the 5G-GUTI contains GUAMI or GUMMEI information. When AMF 606 (via base station 604) receives GUAMI from UE 602, AMF 606 can determine the authorization of UE 602 from an early stage of the establishment / authentication process, thereby reducing the number of messages between AMF 606 and UDM608 and creating a more efficient registration process.

[0099] In some examples, AMF 606 can be configured with an approved list of GUAMIs and can check whether UE 602's GUAMI belongs to the list of supported GUAMIs. If the GUAMI is not recognized, UE 602 can be rejected without further consuming RAN or CN resources. As specified in Section 5.5.1.1 of TS 24.501, the rejection can be achieved using reason #15 "No suitable cell in the tracking area" to allow UE 602 to attempt to acquire access to a network in a different tracking area.

[0100] At box 610, AMF 606 can construct a list of GUAMIs. For example, AMF 606 can construct a list of GUAMIs that includes the identifiers of the AMFs that UE 602 has registered in its previous 5G sessions.

[0101] At box 612, UE 602 can transmit an RRC / RRC establishment complete message to base station 604. In this example, UE 602 can encapsulate NAS information within the RRC establishment complete message. As specified in section 5.3.3.4 of TS 38.331, the message can be encapsulated over the air between the UE and the base station. Figure 2 As discussed in box 222, the RRC / RRC setup completion message may include GUAMI and NAS-PDU messages.

[0102] At box 614, base station 604 may transmit an NGAP / Initial UE message to AMF 606. As specified in section 8.6.1 of TS 38.413, GUAMI may be included in the initial UE message between base station 604 and AMF 606.

[0103] At box 616, AMF 606 can determine that the GUAMI from UE 602 is invalid and that the GUAMI check may fail. For example, if AMF 606 does not recognize a GUAMI from UE 602, AMF 606 can determine that UE 602 is an uncontracted UE and it should release the UE's RRC connection using the standardized RRC connection release procedure, as defined in section 5.3.8 of TS 38.331.

[0104] At box 618, the AMF 606 can assign an AMF UE NGAP ID. The AMF UE NGAP ID can be a unique identifier assigned by the AMF 606 to the UE 602, allowing the AMF 606 to specifically identify and manage the UE 602 within its domain. In some examples, the identifier can be used for communication between the AMF 606 and the RAN of the 5G network via the NGAP protocol.

[0105] At box 620, AMF 606 can transmit an NGAP / DL NAS transmission message to base station 604. This message may include a NAS-PDU with RegReject, an AMF UE NGAP ID (associated with UE 602), and a RAN UE NGAP ID (associated with the NG-RAN node). The RAN UE NGAP ID and AMF UE NGAP ID pair can provide a globally unique context reference for UE 602 across base station 604 and AMF 606.

[0106] At box 622, base station 604 may transmit an RRC / DL INFO transmission message to UE 602. This message may include a NAS-PDU with a RegReject listing reason #15. Reason #15 may allow UE 602 to attempt to obtain access to a network in a different tracking area, as specified in section 5.5.1.1 of TS 24.501.

[0107] At box 624, AMF 606 can transmit an NGAP / UE context release command message to base station 604. For example, AMF 606 can send a message to base station 604 to initiate the release of the context of UE 602. This can instruct base station 604 to release resources allocated to a specific UE (UE 602) on its network.

[0108] At box 626, base station 604 can transmit an RRC / RRC release message to UE 602. For example, upon receiving a UE context release command message, base station 604 can release all associated signaling and user data transmission resources. Therefore, by releasing the UE's RRC connection, multiple unnecessary communications by UE 602 to attempt to acquire the network access described above can be prevented from being transmitted to base station 604. Thus, air resources and the processing capacity of network components configured to handle these requests (e.g., base station 604, AMF 606, and UDM 608) are not wasted.

[0109] In some examples, base station 604 can configure UE 602 not to attempt further network acquisition within the same base station coverage area by setting a T302 timer for the UE by including a wait time parameter. This T302 timer is defined in section 7.1 of TS38.331.

[0110] At box 628, base station 604 can transmit an NGAP / UE context release complete message to AMF 606. When base station 604 transmits the NGAP / UE context release complete message to AMF 606, base station 604 can convey to AMF 606 that the base station has successfully released all UE context information associated with a specific user. This can indicate that the UE is no longer connected to the network and that its associated data on the base station has been cleared, thereby notifying AMF to update its UE context accordingly.

[0111] Figure 7This is an illustrative 3GPP 5G-GUTI data format based on examples of the disclosed technology. In this example, a 5G-GUTI data format is provided. For example, a UE can obtain a 5G-GUTI from a previous successful registration with its home PLMN. The 5G-GUTI can be defined as MCC 710, MNC 720, AMF area identifier 730 (the area where the UE is located), AMF set identifier 740 (the set of AMFs within the AMF area), AMF pointer 750 (the AMF within the AMF set), and 5G Temporary Mobile Subscriber Identifier (5G-TMSI) 760.

[0112] 5G-GUTI can also define other identifiers from parts of the data. For example, the first part of the data can define GUAMI, including MCC 710, MNC 720, AMF area identifier 730, AMF set identifier 740, and AMF pointer 750. The second part of the data can also define AMF identifiers, including AMF area identifier 730, AMF set identifier 740, and AMF pointer 750.

[0113] Figure 8 The illustration depicts an example registration process based on the disclosed technology. In some examples, the AMF can implement the process illustrated herein in a 5G communication system. The illustrated AMF in... Figure 6 It is provided as AMF 606.

[0114] At box 805, this procedure can construct a list of GUAMIs. For example, AMF can construct a list of GUAMIs that includes the identifier of AMF.

[0115] At box 810, the process can begin registration for a specific UE. For example, the UE can provide a GUAMI that it registered in its previous 5G sessions. The AMF can determine whether the GUAMI from a specific UE is valid. This can include comparing the GUAMI from the UE (received via the base station) with GUAMIs in the GUAMI list.

[0116] At box 815, the procedure can determine if the UE's GUAMI belongs to the GUAMI list. This may include an exact match of the GUAMI identifier. If a match exists, the procedure can proceed to box 820. If no match exists, the procedure can proceed to box 830.

[0117] At box 820, this process can complete the UE registration. For example, accepting the UE's registration attempt can provide the UE with network approval parameters (identity, tracking area, slice, timer, etc.) for continuous 5G service.

[0118] At box 830, this procedure can use reason #15 to reject the UE's registration. For example, if the AMF does not identify a GUAMI from the UE, the AMF can determine that the UE is an uncontracted UE, and it should use the standardized RRC connection release procedure to release the UE's RRC connection, as defined in section 5.3.8 of TS 38.331. Therefore, the AMF can initiate a rejection of the UE's RRC connection and help prevent the UE from transmitting multiple unnecessary communications to RAN or CN resources. This also helps conserve air-to-air resources and network component processing power.

[0119] The process can end at box 835.

[0120] Figure 9 The illustration shows a computing component that can be used to execute instructions, according to an example of the disclosed technology. (Refer to...) Figure 9 The computing component 900 can be, for example, a server computer, a controller, or any other similar computing component capable of processing data. Figure 9 In an example implementation, computing component 900 includes a hardware processor 902 and a machine-readable storage medium 904. According to one example of the disclosed technology, computing component 900 can be used to implement, for example, AMF functionality.

[0121] Hardware processor 902 may be one or more central processing units (CPUs), semiconductor-based microprocessors, and / or other hardware devices suitable for fetching and executing instructions stored in machine-readable storage medium 904. Hardware processor 902 may fetch, decode, and execute instructions, such as instructions 906-916. As an alternative to fetching and executing instructions, or in addition to fetching and executing instructions, hardware processor 902 may include one or more electronic circuits, including electronic components for the function of executing one or more instructions, such as field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), or other electronic circuits.

[0122] Machine-readable storage media (such as machine-readable storage media 904) can be any electronic, magnetic, optical, or other physical storage device that contains or stores executable instructions. Therefore, machine-readable storage media 904 can be, for example, random access memory (RAM), non-volatile RAM (NVRAM), electrically erasable programmable read-only memory (EEPROM), storage devices, optical discs, etc. In some examples, machine-readable storage media 904 can be a non-transient storage medium, where the term "non-transient" does not cover transient propagation signals. As described in detail below, machine-readable storage media 904 can be encoded using executable instructions (e.g., instructions 906-916).

[0123] Hardware processor 902 can execute instructions 906 to generate a list of GUAMIs or GUMMEIs associated with the communication network. In some examples, the list of GUAMIs or GUMMEIs is generated by an AMF or MME in the communication network.

[0124] Hardware processor 902 can execute instructions 908 to receive a registration request from the UE. In some examples, the registration request is received by the AMF or MME. The registration request may include 5G-GUTI or GUTI.

[0125] The hardware processor 902 can execute instruction 910 to obtain GUAMI or GUMMEI from 5G-GUTI or GUTI. GUAMI or GUMMEI can be obtained from AMF or MME.

[0126] The hardware processor 902 can execute instruction 912 to compare GUAMI or GUMMEI with a list of GUAMI or GUMMEI. The comparison of GUAMI or GUMMEI with the list can be performed by the AMF or MME.

[0127] The hardware processor 902 can execute instruction 914 to continue processing the UE's registration request in the AMF or MME of the communication network. Continuing to process the registration request can be initiated in response to the identification of a GUAMI or GUMMEI in the GUAMI or GUMMEI list.

[0128] Hardware processor 902 can execute instruction 916 to initiate a UE registration rejection procedure in the AMF or MME. The registration rejection procedure can be initiated in response to the identification that the GUAMI or GUMMEI is not on the GUAMI or GUMMEI list. In some examples, the UE registration rejection procedure can be initiated immediately after the comparison without contacting the AMF / MME, UDM, or other devices.

[0129] By initiating a registration rejection procedure, the UE can be prevented from transmitting multiple unnecessary communications to the base station in an attempt to obtain the network access described above. Therefore, air resources and the processing capacity of network components configured to handle these requests (e.g., base station, AMF / MME, and UDM) are not wasted.

[0130] Figure 10 The illustration shows a computing component 1000, an example of the disclosed technology, that can be used to execute instructions. The computing component 1000 can be, for example, a server computer, a controller, or any other similar computing component capable of processing data. Figure 10In an example implementation, computing component 1000 includes a hardware processor 1002 and a machine-readable storage medium 1004. According to one example of the disclosed technology, computing component 1000 can be used to implement, for example, base station functions.

[0131] The hardware processor 1002 may be one or more central processing units (CPUs), semiconductor-based microprocessors, and / or other hardware devices suitable for fetching and executing instructions stored in the machine-readable storage medium 1004. The hardware processor 1002 may fetch, decode, and execute instructions, such as instructions 1006-1014. As an alternative to fetching and executing instructions, or in addition to fetching and executing instructions, the hardware processor 1002 may include one or more electronic circuits, including electronic components for the function of executing one or more instructions, such as field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), or other electronic circuits.

[0132] Machine-readable storage media (such as machine-readable storage media 1004) can be any electronic, magnetic, optical, or other physical storage device that contains or stores executable instructions. Therefore, machine-readable storage media 1004 can be, for example, random access memory (RAM), non-volatile RAM (NVRAM), electrically erasable programmable read-only memory (EEPROM), storage devices, optical discs, etc. In some examples, machine-readable storage media 1004 can be a non-transient storage medium, where the term "non-transient" does not cover transient propagation signals. As described in detail below, machine-readable storage media 1004 can be encoded using executable instructions (e.g., instructions 1006-1014).

[0133] Hardware processor 1002 can execute instruction 1006 to receive a list of GUMMEIs associated with a communication network. This list can be received from the MME by a base station in the communication network. In some examples, the MME can construct a list of GUMMEIs associated with the communication network. The MME can provide the list of GUMMEIs to multiple base stations associated with the MME.

[0134] Hardware processor 1002 can execute instructions 1008 to receive a network attachment request from the UE. The network attachment request may include the UE's NAS information. For example, a network attachment request can be initiated when the UE is activated / powered on, reset, or in other instances where the UE is permitted to request network access. In some examples, the network identifier associated with the UE is the GUMMEI of the AMF that the UE registered with in a previous communication session.

[0135] The hardware processor 1002 can execute instruction 1010 to compare the GUMMEI with a list of GUMMEIs. For example, the MME can be configured with an approved list of GUMMEIs, and can check whether the UE's GUMMEI belongs to the list of supported GUMMEIs.

[0136] Hardware processor 1002 can execute instruction 1012 to forward NAS information to MME. Forwarding can be initiated in response to identifying a GUMMEI in the GUMMEI list. NAS information may include the UE's GUMMEI, and the MME can be specified by the UE in a NAS message routed from the RAN to the MME. The MME can authenticate the UE and manage the UE's handover and other operations between access points and base stations.

[0137] Hardware processor 1002 can execute instruction 1014 to initiate RCC connection release for the UE in response to identifying that GUMMEI is not on the GUMMEI list. In some examples, the initiation of RCC connection release for the UE can be performed immediately after comparison without contacting the MME, UDM, and other devices.

[0138] By releasing the UE, multiple unnecessary communications by the UE to the base station for attempting to obtain the network access described above can be prevented. Therefore, air resources and the processing capacity of network components configured to handle these requests (e.g., base station, MME, and UDM) are not wasted.

[0139] Figure 11 A block diagram of an example computer system 1100 is depicted, illustrating various examples of the disclosed techniques described herein. The computer system 1100 includes a bus 1102 or other communication mechanism for transmitting information, and one or more hardware processors 1104 coupled to the bus 1102 for processing information. For example, the hardware processors 1104 may be one or more general-purpose microprocessors.

[0140] Computer system 1100 also includes main memory 1106 (such as random access memory (RAM), cache, and / or other dynamic storage devices) coupled to bus 1102 for storing information and instructions to be executed by processor 1104. Main memory 1106 may also be used to store temporary variables or other intermediate information during the execution of instructions by processor 1104. When stored in storage media accessible to processor 1104, such instructions make computer system 1100 a special-purpose machine customized to perform the operations specified in the instructions.

[0141] Computer system 1100 also includes a read-only memory (ROM) 1108 or other static storage device coupled to bus 1102 for storing static information and instructions of processor 1104. Storage device 1110, such as a disk, optical disk, or USB thumb drive (flash drive), is provided and coupled to bus 1102 for storing information and instructions.

[0142] Generally, the terms "component," "engine," "system," "database," and "data storage" used in this article can refer to logic embodied in hardware or firmware, or to a set of software instructions (which may have entry and exit points) written in programming languages ​​such as Java, C, or C++. Software components can be compiled and linked into an executable program, installed in a dynamic link library, or written in an interpreted programming language such as BASIC, Perl, or Python. It is important to understand that software components can be invoked by other components or by themselves, and / or can be invoked in response to detected events or interrupts. Software components configured to execute on a computing device can be provided on computer-readable media (such as compressed disks, digital video disks, flash drives, hard disks, or any other tangible media) or as digital downloads (and may initially be stored in a compressed or installable format that requires installation, decompression, or decryption before execution). This software code can be stored, partially or entirely, on a memory device executing the computing device for execution by the computing device. Software instructions can be embedded in firmware, such as EPROM. It is also important to understand that hardware components may include connected logic units (such as gates and flip-flops), and / or may include programmable units (such as programmable gate arrays or processors).

[0143] Computer system 1100 may implement the techniques described herein using custom hardwired logic, one or more ASICs or FPGAs, firmware, and / or program logic, which, in combination with the computer system, make computer system 1100 a special-purpose machine, or program computer system 1100 as a special-purpose machine. According to one example of the disclosed techniques, the techniques herein are executed by computer system 1100 in response to processor(s) 1104 executing one or more sequences of one or more instructions contained in main memory 1106. Such instructions may be read into main memory 1106 from another storage medium, such as storage device 1110. Executing the sequence of instructions contained in main memory 1106 causes processor(s) 1104 to perform the process steps described herein. In alternative examples, hardwired circuitry may be used in place of or in combination with software instructions.

[0144] As used herein, the term "non-transient medium" and similar terms refer to any medium that stores data and / or instructions that cause a machine to operate in a particular manner. Such non-transient media can include non-volatile media and / or volatile media. Non-volatile media include, for example, optical discs or magnetic disks, such as storage device 1110. Volatile media include dynamic memory, such as main memory 1106. Common forms of non-transient media include, for example, floppy disks, floppy disks, hard disks, solid-state drives, magnetic tape, or any other magnetic data storage medium, CD-ROMs, any other optical data storage media, any physical medium with a perforated pattern, RAM, PROMs and EPROMs, flash memory EPROMs, NVRAMs, any other memory chips or tape cartridges and their networking versions. Non-transient media are distinct from transmission media, but can be used in conjunction with transmission media.

[0145] Computer system 1100 also includes an interface 1118 coupled to bus 1102. Interface 1118 provides bidirectional data communication coupling with one or more network links connected to one or more local networks. For example, interface 1118 may be an Integrated Services Digital Network (ISDN) card, a cable modem, a satellite modem, or a modem for providing data communication connectivity with a corresponding type of telephone line. As another example, interface 1118 may be a Local Area Network (LAN) card to provide data communication connectivity with a compatible LAN (or a WAN component communicating with a WAN). Wireless links may also be implemented. In any such implementation, interface 1118 transmits and receives electrical, electromagnetic, or optical signals carrying digital data streams representing various types of information.

[0146] Each of the processes, methods, and algorithms described in the preceding sections can be embodied in code components executed by one or more computer systems or computer processors including computer hardware, and can be fully or partially automated by them. One or more computer systems or computer processors can also operate to support the execution of related operations in a “cloud computing” environment or as “Software as a Service” (SaaS). Processes and algorithms can be implemented, partially or wholly, in dedicated circuitry. The various features and processes described above can be used independently of each other or can be combined in various ways. Different combinations and sub-combinations are intended to fall within the scope of this disclosure, and certain method or process blocks can be omitted in some implementations. The methods and processes described herein are not limited to any particular order, and the blocks or states associated with them can be executed in other suitable orders, or can be executed in parallel, or can be executed in some other way. Blocks or states can be added to or removed from the disclosed examples. The execution of a particular operation or process can be distributed among computer systems or computer processors, residing not only within a single machine but also deployed across multiple machines.

[0147] As used herein, the term “or” can be interpreted in an inclusive or exclusive sense. Furthermore, descriptions of resources, operations, or structures in the singular form should not be construed as excluding the plural form. Unless otherwise specifically stated or understood in the context to be used otherwise, conditional language (such as “can,” “could,” “might,” or “may”) is generally intended to convey that certain examples include certain features, elements, and / or steps while others do not.

[0148] Unless otherwise expressly stated, the terms and phrases used in this document, and their variations thereof, should be interpreted as open-ended rather than restrictive. Adjectives such as “regular,” “traditional,” “normal,” “standard,” “known,” and similar terms should not be interpreted as limiting the described items to a given time period or to items available at a given time, but should be understood to encompass regular, traditional, normal, or standard techniques that may be available or known at any time now or in the future. In some instances, the presence of extended words and phrases (such as “one or more,” “at least,” “but not limited to,” or other similar phrases) should not be interpreted as implying a narrower meaning or requirement in instances where such extended phrases may not exist.

Claims

1. A method comprising: The base station receives a list of globally unique AMF identifiers (GUAMIs) associated with the communication network from the Access and Mobility Management Function (AMF) in the communication network; The base station receives a network attachment request from the user equipment (UE), the network attachment request including the UE's non-access stratum (NAS) information, and the network identifier associated with the UE is the GUAMI of the AMF to which the UE was registered in a previous communication session; The base station compares the GUAMI with the GUAMI list; In response to identifying the GUAMI in the GUAMI list, the base station forwards the NAS information of the UE to the AMF of the communication network; as well as In response to the indication that the GUAMI is not on the GUAMI list, the base station initiates an RRC connection release procedure for the UE.

2. The method according to claim 1, further comprising: The AMF generates a list of GUAMIs associated with the communication network; as well as The AMF provides the GUAMI list to multiple base stations associated with the AMF.

3. The method of claim 2, wherein the provision is implemented during the next-generation (NG) setup process.

4. The method of claim 2, wherein the provisioning is performed during the next-generation (NG) configuration update process.

5. The method of claim 1, wherein the network attachment request is triggered due to the UE performing a registration process.

6. The method of claim 1, wherein the network attachment request is triggered due to the UE performing a service request procedure.

7. The method of claim 1, wherein the network identifier received from the UE is the native GUAMI of the AMF to which the UE was registered in a previous 5G communication session.

8. The method of claim 1, wherein the network identifier received from the UE is a mapped GUAMI of the Mobility Management Entity (MME) to which the UE was registered in a previous 4G communication session.

9. The method according to claim 1, further comprising: In response to not being on the GUAMI list, the base station transmits to the UE the wait time (waitTime) to be used by the UE to set the T302 timer of the UE.

10. A method comprising: The base station receives a list of globally unique MMF identifiers (GUMMEIs) associated with the communication network from the Mobility Management Entity (MME) in the communication network; The base station receives a network attachment request from the user equipment (UE), the network attachment request including the UE's non-access stratum (NAS) information, and the network identifier associated with the UE is the GUMMEI of the access and mobility management function (AMF) to which the UE was registered in a previous communication session; The base station compares the GUMMEI with the GUMMEI list; In response to identifying the GUMMEI in the GUMMEI list, the base station forwards the NAS information of the UE to the MME of the communication network; as well as In response to the indication that the GUMMEI is not on the GUMMEI list, the base station initiates an RRC connection release procedure for the UE.

11. The method of claim 10, further comprising: The MME generates a list of GUMMEIs associated with the communication network; as well as The MME provides the GUMMEI list to multiple base stations associated with the MME.

12. The method of claim 11, wherein the provision is performed during the S1 establishment process.

13. The method of claim 11, wherein the provisioning is performed during the MME configuration update process.

14. The method of claim 10, wherein the network identifier received from the UE is the native GUMMEI of the MME to which the UE was registered in a previous 4G communication session.

15. The method of claim 10, wherein the network identifier received from the UE is a mapped GUMMEI of the AMF to which the UE was registered in a previous 5G communication session.

16. The method of claim 10, further comprising: In response to not being on the GUMMEI list, the base station transmits to the UE the wait time (waitTime) to be used by the UE to set the T302 timer of the UE.

17. A method comprising: A list of globally unique AMF identifiers (GUAMI) or a list of globally unique MME identifiers (GUMMEI) associated with the communication network is generated by the Access and Mobility Management Function (AMF) or Mobility Management Entity (MME) in the communication network. The AMF or the MME receives a registration request from the user equipment (UE), the registration request including a 5G globally unique temporary identifier (5G-GUTI) or a globally unique temporary identifier (GUTI). The GUAMI or GUMMEI is obtained from the 5G-GUTI or the GUTI accordingly by the AMF or MME; The AMF or the MME compares the GUAMI or GUMMEI with the GUAMI list or the GUMMEI list; In response to the identification of the GUAMI or GUMMEI in the GUAMI list or GUMMEI list, the AMF or MME continues to process the registration request for the UE in the AMF or MME of the communication network; as well as In response to the identification that the GUAMI or GUMMEI is not on the GUAMI list or the GUMMEI list, the AMF or the MME initiates a registration rejection procedure for the UE in the AMF or the MME.

18. The method of claim 17, wherein the registration rejection process transmits a rejection message, the rejection message including the reason 15 that there is no suitable cell in the tracking area.

19. The method of claim 17, further comprising: When the communication network to which the AMF or the MME belongs supports roaming between 4G and 5G networks, the GUAMI list or the GUMMEI list accordingly includes mapped GUAMIs or mapped GUMMEIs.

20. The method of claim 17, wherein the 5G-GUTI or the GUTI is transmitted in non-access stratum (NAS) information between the UE and the AMF or the MME.

Images