Network access management

Abstract

A wireless device receives network access information from a first network, the network access information including an identifier of a second network and one or more parameters indicating a condition for determining whether the wireless device is permitted to access the second network. The wireless device determines that the condition is satisfied, and sends a second registration request message to the second network based on the determination.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 322,714, filed March 23, 2022, the entire contents of which are incorporated herein by reference. Attached Figure Description

[0003] Examples of several embodiments of the various embodiments of this disclosure are described herein with reference to the accompanying drawings.

[0004] Figure 1A and Figure 1B This illustrates an example communication network that includes an access network and a core network.

[0005] Figure 2A , Figure 2B , Figure 2C and Figure 2D Various examples of service-based architecture frameworks within the core network are shown.

[0006] Figure 3 An example communication network containing core network functions is shown.

[0007] Figure 4A and Figure 4B An example of a core network architecture with multiple user plane functions and untrusted access is shown.

[0008] Figure 5 An example of the core network architecture for roaming scenarios is shown.

[0009] Figure 6 An example of a network slice is shown.

[0010] Figure 7A , Figure 7B and Figure 7C It shows the user plane protocol stack, the control plane protocol stack, and the services set between the protocol layers of the user plane protocol stack.

[0011] Figure 8 An example of a quality of service model for data exchange is shown.

[0012] Figure 9A , Figure 9B , Figure 9C and Figure 9D This shows example states and state transitions of a wireless device.

[0013] Figure 10 An example of a registration procedure for a wireless device is shown.

[0014] Figure 11 This shows an example of a service request procedure for a wireless device.

[0015] Figure 12 This shows an example of the Protocol Data Unit (PDU) session establishment procedure for a wireless device.

[0016] Figure 13 Examples of components shown are examples of elements in a communication network.

[0017] Figure 14A , Figure 14B , Figure 14C and Figure 14D Various examples of physical core network deployments, each having one or more network functions or portions thereof, are shown.

[0018] Figure 15 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0019] Figure 16 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0020] Figure 17 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0021] Figure 18 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0022] Figure 19 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0023] Figure 20 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0024] Figure 21 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0025] Figure 22 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0026] Figure 23 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0027] Figure 24 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0028] Figure 25 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0029] Figure 26 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0030] Figure 27 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0031] Figure 28 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0032] Figure 29 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0033] Figure 30 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0034] Figure 31 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0035] Figure 32 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0036] Figure 33 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0037] Figure 34 This is an exemplary diagram of one aspect of the implementation of this disclosure. Detailed Implementation

[0038] In this disclosure, various embodiments are presented in the form of examples of how the disclosed techniques can be implemented and / or how the disclosed techniques can be practiced in environments and scenarios. It will be apparent to those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the invention. Indeed, after reading the specification, it will be apparent to those skilled in the art how to implement alternative embodiments. Embodiments of the invention should not be limited to any of the described exemplary embodiments. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments may be combined to create additional embodiments within the scope of this disclosure. Any diagrams highlighting functionality and advantages are given for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in ways other than those shown. For example, actions listed in any flowchart may be reordered or optionally used only in certain embodiments.

[0039] The implementation scheme can be configured to operate as needed. For example, in wireless devices, base stations, radio environments, networks, combinations thereof, etc., the disclosed mechanisms can be executed when certain criteria are met. Exemplary criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, service characteristics, combinations thereof, etc. Various exemplary implementation schemes can be applied when one or more criteria are met. Therefore, exemplary implementation schemes that selectively implement the disclosed protocols can be implemented.

[0040] A base station can communicate with a hybrid of wireless devices. The wireless devices and / or base stations can support multiple technologies and / or multiple versions of the same technology. Wireless devices may have one or more specific capabilities. When this disclosure refers to a base station communicating with multiple wireless devices, this disclosure may refer to a subset of the total number of wireless devices in the coverage area. For example, this disclosure may refer to multiple wireless devices having a given capability and a given LTE or 5G version in a given sector of a base station. Multiple wireless devices in this disclosure may refer to a selected set of wireless devices, and / or a subset of the total number of wireless devices in the coverage area performing according to the disclosed method, etc. Multiple base stations or multiple wireless devices may exist in the coverage area that may not conform to the disclosed method; for example, these wireless devices or base stations may be based on older versions of LTE or 5G technology.

[0041] In this disclosure, the terms “a” and “an” and similar phrases refer to a single instance of a particular element but should not be construed as excluding other instances of that element. For example, a bicycle with two wheels can be described as having “wheels”. Any term ending with the suffix “(s)” will be construed as “at least one” and / or “one or more”. In this disclosure, the term “may” is construed as “may, for example”. In other words, the term “may” indicates that the phrase following the term “may” is an example of one of a number of suitable possibilities that may or may not be used in one or more embodiments of various embodiments. As used herein, the terms “comprising” and “consisting of” enumerate one or more parts of the element being described. The terms “comprising” and “including” are interchangeable and do not exclude the inclusion of unlisted parts in the element being described. In contrast, “consisting of” provides a complete enumeration of the one or more parts of the element being described.

[0042] The phrases “based on,” “in response to,” “depending on,” “adopted,” “used,” and similar phrases indicate the presence and / or influence of a particular factor and / or condition on an event and / or action, but do not exclude the presence and / or influence of uncounted factors and / or conditions on the event and / or action. For example, if action X is performed “based on” condition Y, this is interpreted as the action being performed “at least based on” condition Y. For example, if action X is performed when both conditions Y and Z are satisfied, the execution of action X can be described as “based on Y.”

[0043] The term "configured" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configured" can also mean specific settings within the device that affect its operational characteristics, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within the device to provide specific characteristics to the device, whether the device is in an operational or non-operational state. Similarly, the term "control messages generated in the device" can mean that the control messages have parameters that can be used to configure specific characteristics in the device or to perform certain actions in the device, regardless of whether the device is in an operational or non-operational state.

[0044] In this disclosure, a parameter may include one or more information objects, and an information object may include one or more other objects. For example, if parameter J includes parameter K, and parameter K includes parameter L, and parameter L includes parameter M, then J includes L, and J includes M. A parameter may be referred to as a field or information element. In the example implementation, when one or more messages include multiple parameters, it means that a parameter among the multiple parameters is present in at least one of the one or more messages, but not necessarily in every one of the one or more messages.

[0045] This disclosure may relate to possible combinations of enumerated elements. For brevity and readability, this disclosure does not explicitly describe every permutation that can be obtained by selecting from the optional features of the group. This disclosure should be interpreted as explicitly disclosing all such permutations. For example, the seven possible combinations of enumerated elements A, B, C consist of: (1) “A”; (2) “B”; (3) “C”; (4) “A and B”; (5) “A and C”; (6) “B and C”; and (7) “A, B, and C”. For brevity and readability, these seven possible combinations can be described using any of the following interchangeable expressions: “at least one of A, B, and C”; “at least one of A, B, or C”; “one or more of A, B, and C”; “one or more of A, B, or C”; “A, B, and / or C”. It should be understood that impossible combinations are excluded. For example, “X and / or not X” should be interpreted as “X or not X”. It should also be understood that these expressions may describe alternative terms for overlapping and / or synonymous concepts, such as “identifier, identifier and / or ID number”.

[0046] This disclosure may relate to sets and / or subsets. As an example, a set X may be a set of elements comprising one or more elements. If every element of X is also an element of Y, then X may be called a subset of Y. In this disclosure, only non-empty sets and subsets are considered. For example, if Y consists of elements Y1, Y2, and Y3, then possible subsets of Y are {Y1, Y2, Y3}, {Y1, Y2}, {Y1, Y3}, {Y2, Y3}, {Y1}, {Y2}, and {Y3}.

[0047] Figure 1A An example of a communication network 100 in which embodiments of the present disclosure may be implemented is shown. The communication network 100 may include, for example, a Public Land Mobile Network (PLMN) operated by a network operator. Figure 1A As shown, the communication network 100 includes a wireless device 101, an access network (AN) 102, a core network (CN) 105, and one or more data networks (DN) 108.

[0048] Wireless device 101 can communicate with DN 108 via AN 102 and CN 105. In this disclosure, the term "wireless device" can refer to and encompass any mobile or fixed (non-mobile) device for which wireless communication is required or permitted. For example, a wireless device can be a telephone, smartphone, tablet, computer, laptop computer, sensor, meter, wearable device, Internet of Things (IoT) device, roadside unit (RSU) of a vehicle, relay node, automobile, drone, urban air traffic, and / or any combination thereof. The term "wireless device" encompasses other terms including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handheld device, wireless transmit and receive unit (WTRU), and / or wireless communication equipment.

[0049] AN 102 can connect wireless device 101 to CN 105 in any suitable manner. The communication direction from AN 102 to wireless device 101 is referred to as the downlink, and the communication direction from wireless device 101 to AN 102 is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using Frequency Division Duplex (FDD), Time Division Duplex (TDD), and / or some combination of these two duplex technologies. AN 102 can be connected to wireless device 101 via radio communication through an air interface. An access network operating at least partially via an air interface can be referred to as a Radio Access Network (RAN). CN 105 can establish one or more end-to-end connections between wireless device 101 and one or more DNs 108. CN 105 can authenticate wireless device 101 and provide billing functionality.

[0050] In this disclosure, the term "base station" can refer to and encompass any element of AN102 that facilitates communication between wireless device 101 and AN 102. Access networks and base stations have many different names and implementations. A base station can be a terrestrial base station fixed to the ground. A base station can be a mobile base station with mobile coverage areas. A base station can be in space, such as on a satellite. For example, WiFi and other standards use the term "access point." As another example, the 3rd Generation Partnership Project (3GPP) has produced specifications for three generations of mobile networks, each using different terminology. Third-generation (3G) and / or Universal Mobile Telecommunications System (UMTS) standards can use the term "node B." 4G, Long Term Evolution (LTE), and / or Evolved Universal Terrestrial Radio Access (E-UTRA) standards can use the term "eNB." 5G and / or New Radio (NR) standards can describe AN 102 as a Next Generation Radio Access Network (NG-RAN) and can refer to the base station as a Next Generation eNB (ng-eNB) and / or gNB (Generation Node B). Future standards (e.g., 6G, 7G, 8G) may use new terminology to refer to elements (e.g., wireless devices, base stations, AN, CN, and / or components thereof) that implement the methods described in this disclosure. A base station may be implemented as a repeater or relay node for extending the coverage area of ​​a donor node. A repeater node may amplify and replay radio signals received from a donor node. A relay node may perform the same / similar functions as a repeater node, but may decode radio signals received from a donor node to remove noise before amplifying and replaying the radio signals.

[0051] AN 102 may include one or more base stations, each having one or more coverage areas. The geographical size and / or extent of the coverage area may be defined by the range in which a receiver of AN 102 can successfully receive transmissions from a transmitter (e.g., wireless device 101) operating within the coverage area (and / or vice versa). The coverage area may be referred to as a zone or cell (but in some contexts, the term cell refers to the carrier frequency used in a particular coverage area, rather than the coverage area itself). A base station with a large coverage area may be referred to as a macrocell base station. Other base stations cover smaller areas to provide coverage, for example, in areas with weak macrocell coverage, or to provide additional coverage in areas with high traffic (sometimes referred to as hotspots). Examples of small cell base stations, in descending order of coverage area, include: microcell base stations, picocell base stations, and femtocell base stations or femtocell base stations. The coverage areas of the base stations may together provide wireless device 101 with wireless coverage over a wide geographical area to support wireless device mobility.

[0052] A base station may include one or more sets of antennas for communicating with wireless device 101 via an air interface. Each set of antennas may be controlled independently by the base station. Each set of antennas may have a corresponding coverage area. As an example, a base station may include three sets of antennas to control three coverage areas on three different sides of the base station, respectively. The entire base station (and its corresponding antennas) may be deployed at a single location. Alternatively, a controller at a central location may control one or more sets of antennas at one or more distributed locations. The controller may be, for example, a baseband processing unit, which is part of a centralized or cloud RAN architecture. The baseband processing unit may be centralized in a cluster or virtualized. A set of antennas at distributed locations may be referred to as a remote radio head (RRH).

[0053] Figure 1B Another example communication network 150 is shown, in which embodiments of the present disclosure may be implemented. Communication network 150 may include, for example, a PLMN operated by a network operator. Figure 1B As shown, the communication network 150 includes a UE 151, a Next-Generation Radio Access Network (NG-RAN) 152, a 5G Core Network (5G-CN) 155, and one or more DNs 158. The NG-RAN 152 includes one or more base stations, shown as a Next-Generation Node B (gNB) 152A and a Next-Generation Evolved Node B (ng eNB) 152B. The 5G-CN 155 includes one or more network functions (NFs), which include control plane functions 155A and user plane functions 155B. The one or more DNs 158 may include public DNs (e.g., the Internet), private DNs, and / or carrier-internal DNs. (Relative to...) Figure 1A The corresponding components shown may represent specific implementations and / or terms.

[0054] The base station of NG-RAN 152 can connect to UE 151 via the Uu interface. The base stations of NG-RAN 152 can connect to each other via the Xn interface. The base station of NG-RAN 152 can connect to 5G CN 155 via the NG interface. The Uu interface may include an air interface. The NG and Xn interfaces may include air interfaces, or may consist of direct physical connections and / or indirect connections via an underlying transport network (e.g., an Internet Protocol (IP) transport network).

[0055] Each of the Uu, Xn, and NG interfaces can be associated with a protocol stack. The protocol stack can contain a user plane (UP) and a control plane (CP). Typically, user plane data can contain data about the user of UE 151, such as Internet content downloaded via a web browser application, sensor data uploaded via a tracking application, or email data transmitted to or from an email server. In contrast, control plane data can include signaling and messages that facilitate the packaging and routing of user plane data so that it can be exchanged with the DN. For example, the NG interface can be divided into an NG user plane interface (NG-U) and an NG control plane interface (NG-C). The NG-U interface provides delivery of user plane data between the base station and one or more user plane network functions 155B. The NG-C interface can be used for control signaling between the base station and one or more control plane network functions 155A. The NG-C interface can provide, for example, NG interface management, UE context management, UE mobility management, NAS message delivery, paging, PDU session management, and configuration delivery and / or warning message transmission. In some cases, the NG-C interface can support the transmission of user data (e.g., small data transfers for IoT devices).

[0056] One or more NG-RAN 152 base stations can be split into a Central Unit (CU) and one or more Distribution Units (DUs). A CU can be connected to one or more DUs via an F1 interface. A CU can handle one or more upper layers of the protocol stack, and a DU can handle one or more lower layers of the protocol stack. For example, a CU can handle RRC, PDCP, and SDAP, while a DU can handle RLC, MAC, and PHY. The one or more DUs can be located geographically disparately from the CU and / or from each other. Accordingly, the CU / DU split architecture allows for increased coverage and / or better coordination.

[0057] The gNB 152A and ng-eNB 152B can provide different user plane and control plane protocol terminations for UE 151. For example, the gNB 154A can provide New Radio (NR) protocol termination via the Uu interface associated with the first protocol stack. The ng-eNB 152B can provide Evolved UMTS Terrestrial Radio Access (E-UTRA) protocol termination via the Uu interface associated with the second protocol stack.

[0058] The 5G-CN 155 can authenticate UE 151, establish an end-to-end connection between UE 151 and one or more DNs 158, and provide billing functionality. The 5G-CN 155 can be based on a service-based architecture, wherein the NFs comprising the 5G-CN 155 provide services to each other via interfaces and to other elements of the communication network 150. The 5G-CN 155 can contain any number of other NFs and any number of instances of each NF.

[0059] Figure 2A , Figure 2B , Figure 2C and Figure 2D Various examples of service-based architecture frameworks are shown within the core network. In a service-based architecture, service consumers can seek services, which are then provided by service producers. Before obtaining a specific service, an NF can determine where this service is available. To discover services, an NF can communicate with a Network Repository Function (NRF). As an example, an NF providing one or more services can register with the Network Repository Function (NRF). The NRF can store data related to the one or more services that an NF is prepared to provide to other NFs in the service-based architecture. A consumer NF can query the NRF to discover producer NFs (e.g., by obtaining a list of NF instances providing a specific service from the NRF).

[0060] exist Figure 2A In the example, NF 211 (in this example, the consumer NF) may send request 221 to NF 212 (the producer NF). Request 221 may be a request for a specific service and may be sent based on the discovery that NF 212 is a producer of said service. Request 221 may include data related to NF 211 and / or the requested service. NF 212 may receive request 221, perform one or more actions (e.g., retrieve data) associated with the requested service, and provide response 221. The one or more actions performed by NF 212 may be based on request data contained in request 221, data stored by NF 212, and / or data retrieved by NF 212. Response 222 may notify NF 211 that the one or more actions have been completed. Response 222 may include response data related to NF 212, the one or more actions, and / or the requested service.

[0061] exist Figure 2B In the example, NF 231 sends request 241 to NF 232. In this example, part of the service provided by NF 232 will be sending request 242 to NF 233. NF 233 may perform one or more actions and provide response 243 to NF 232. Based on response 243, NF 232 may send response 244 to NF 231. Figure 2B It will be understood that a single NF can perform the roles of service producer, service consumer, or both. A particular NF service can contain any number of nested NF services generated by one or more other NFs.

[0062] Figure 2C This illustrates an example of a subscription-notification interaction between a consumer NF and a producer NF. Figure 2C In this context, NF 251 sends subscription 261 to NF 252. NF 253 sends subscription 262 to NF 252. For illustrative purposes... Figure 2C The diagram illustrates two NFs (to demonstrate that NF 252 can provide multiple subscription services to different NFs), but it should be understood that a subscription-notification interaction requires only one subscriber. NFs 251 and 253 can operate independently of each other. For example, NFs 251 and 253 can independently discover NF 252 and / or independently determine which services are subscribed to by NF 252. In response to receiving a subscription, NF 252 can provide a notification to the subscribing NF. For example, NF 252 can send notification 263 to NF 251 based on subscription 261, and can send notification 264 to NF 253 based on subscription 262.

[0063] like Figure 2C As illustrated in the example diagram, the sending of notifications 263 and 264 may be based on the determination that a certain condition has occurred. For example, notifications 263 and 264 may be based on the determination that a specific event has occurred, the determination that a specific condition is pending, and / or the determination that the duration associated with the subscription has elapsed (e.g., the period associated with a subscription for periodic notifications). Figure 2C As illustrated in the example diagram, NF 252 may send notifications 263 and 264 to NF 251 and 253 simultaneously and / or in response to the same condition. However, it should be understood that NF 252 may provide notifications at different times and / or in response to different notification conditions. In the example, NF 251 may request notification if a specific parameter measured by NF 252 exceeds a first threshold, and NF 252 may request notification if said parameter exceeds a second threshold different from the first threshold. In the example, the parameter of interest and / or the corresponding threshold may be indicated in subscriptions 261 and 262.

[0064] Figure 2D This shows another example of a subscription-notification interaction. Figure 2D In this context, NF 271 sends subscription 281 to NF 272. In response to receiving subscription 281 and / or determining that a notification condition has occurred, NF 272 may send notification 284. Notification 284 may be sent to NF 273. Unlike... Figure 2C Example in the image (where notifications are sent to the subscribed NF), Figure 2DDisplays, subscriptions, and their corresponding notifications can be associated with different NFs. For example, NF 271 can subscribe to services provided by NF 272 on behalf of NF 273.

[0065] Figure 3 Another example communication network 300 in which embodiments of the present disclosure may be implemented is shown. The communication network 300 includes a user equipment (UE) 301, an access network (AN) 302, and a data network (DN) 308. Figure 3 The remaining elements described herein may be included in and / or associated with the core network. Each element of the core network may be referred to as a network function (NF).

[0066] Figure 3 The NFs described herein include User Plane Functions (UPF) 305, Access and Mobility Management Functions (AMF) 312, Session Management Functions (SMF) 314, Policy Control Functions (PCF) 320, Network Repository Functions (NRF) 330, Network Openness Functions (NEF) 340, Unified Data Management (UDM) 350, Authentication Server Functions (AUSF) 360, Network Slice Selection Functions (NSSF) 370, Charging Functions (CHF) 380, Network Data Analysis Functions (NWDAF) 390, and Application Functions (AF) 399. UPF 305 can be a user plane core network function, while NFs 312, 314, and 320-390 can be control plane core network functions. Although... Figure 3 Not illustrated in the examples, the core network may contain additional instances of the depicted NF and / or any of one or more different NF types providing different services. Other examples of NF types include Gateway Mobility Location Center (GMLC), Location Management Function (LMF), Operations, Administration and Maintenance Function (OAM), Public Alert System (PWS), Short Message Service Function (SMSF), Unified Data Repository (UDR), and Unstructured Data Storage Function (UDSF).

[0067] Figure 3 Each element depicted has an interface with at least one other element. This interface can be a logical connection, rather than, for example, a direct physical connection. Any interface can be identified using reference point representation and / or service-based representation. In reference point representation, the letter 'N' followed by a number indicates the interface between two specific elements. For example, such as... Figure 3As shown, AN 302 and UPF 305 are interfaced via 'N3', while UPF 305 and DN 308 are interfaced via 'N6'. In contrast, in the service-based representation, the letter 'N' is followed by a letter. This letter identifies the NF providing the service to the core network. For example, PCF 320 may provide services via interface 'Npcf'. PCF 320 may provide services to any NF in the core network via 'Npcf'. Accordingly, the service-based representation may correspond to a set of reference point representations. For example, the Npcf interface between PCF 320 and the core network may typically correspond to the N7 interface between PCF 320 and SMF 314, the N30 interface between PCF 320 and NEF 340, and so on.

[0068] UPF 305 can act as a gateway for user plane services between AN 302 and DN 308. UE 301 can connect to UPF 305 via the Uu interface and the N3 interface (also described as the NG-U interface). UPF 305 can connect to DN 308 via the N6 interface. UPF 305 can connect to one or more other UPFs (not shown) via the N9 interface. UE 301 can be configured to receive services via Protocol Data Unit (PDU) sessions, which are the logical connection between UE 301 and DN 308. UPF 305 (or, as needed, multiple UPFs) can be selected by SMF 314 to handle a specific PDU session between UE 301 and DN 308. SMF 314 can control the functionality of UPF 305 relative to the PDU session. SMF 314 can connect to UPF 305 via the N4 interface. UPF 305 can handle any number of PDU sessions (via any number of ANs) associated with any number of UEs. For the purpose of handling the one or more PDU sessions, the UPF 305 can be controlled by any number of SMFs via any number of corresponding N4 interfaces.

[0069] Figure 3 The AMF 312, as depicted, controls the UE's access to the core network. UE 301 can register with the network via the AMF 312. UE 301 may need to register before establishing a PDU session. The AMF 312 manages the UE 301's registration area, enabling the network to track the UE 301's physical location within the network. For UEs in connected mode, the AMF 312 manages UE movement, such as handover from one AN or part thereof to another AN. For UEs in idle mode, the AMF 312 performs registration updates and / or paging the UE to transition it to connected mode.

[0070] AMF 312 can receive Non-Access Plane (NAS) messages transmitted from UE 301 according to the NAS protocol. NAS messages pertain to communication between UE 301 and the core network. Although NAS messages may be relayed to AMF 312 via AN 302, they can be described as communication via the N1 interface. NAS messages can facilitate UE registration and mobility management, for example, by authenticating, identifying, configuring, and / or managing UE 301's connectivity. NAS messages can support session management procedures for maintaining user plane connectivity and Quality of Service (QoS) of the session between UE 301 and DN 309. If the NAS message pertains to session management, AMF 312 can send the NAS message to SMF 314. NAS messages can be used to transmit messages between UE 301 and other components of the core network (e.g., core network components other than AMF 312 and SMF 314). AMF 312 can act on a specific NAS message itself or forward the NAS message to the appropriate core network function (e.g., SMF 314, etc.).

[0071] Figure 3 The SMF 314 described herein can establish, modify, and / or publish PDU sessions based on message reception and delivery received at UE 301. The SMF 314 can, for example, allocate, manage, and / or assign IP addresses to UE 301 after a PDU session is established. Multiple SMFs may exist in the network, each associated with a corresponding group of radio devices, base stations, and / or UPFs. A UE with multiple PDU sessions can be associated with a different SMF for each PDU session. As described above, the SMF 314 can select one or more UPFs to handle PDU sessions, and can control the selected UPF's handling of PDU sessions by providing rules (PDR, FAR, QER, etc.) for packet processing. Rules related to the QoS and / or charging of a specific PDU session can be obtained from PCF 320 and provided to UPF 305.

[0072] The PCF 320 can provide services related to policy rules to other NFs. The PCF 320 can use subscription data and information about network conditions to determine policy rules, and then provide these policy rules to specific NFs that can be responsible for enforcing them. Policy rules may relate to policy control for access and mobility, and can be enforced by the AMF. Policy rules may relate to session management, and can be enforced by the SMF 314. Policy rules can be, for example, network-specific, radio device-specific, session-specific, or data stream-specific.

[0073] The NRF 330 can provide service discovery. The NRF 330 may belong to a specific PLMN. The NRF 330 can maintain NF profiles related to other NFs in the communication network 300. The NF profile may contain, for example, the NF's address, PLMN and / or type, slice identifier, a list of one or more services provided by the NF, and the authorization required to access the service.

[0074] Figure 3 The NEF 340 depicted herein provides an interface to an external domain, allowing the external domain to selectively access the control plane of the communication network 300. The external domain may include, for example, third-party network functions, application functions, etc. The NEF 340 can act as a proxy between external components and network functions such as AMF 312, SMF 314, PCF 320, UDM 350, etc. As an example, the NEF 340 can determine the location or reachability status of the UE 301 based on reports from the AMF 312 and provide this status information to the external component. As an example, the external component can provide information via the NEF 340 to facilitate the setting of parameters used to establish a PDU session. The NEF 340 can determine which control plane data and capabilities are exposed to the external domain. The NEF 340 can provide secure exposure, which authenticates and / or authorizes the data or capabilities of the communication network 300 to be exposed to external entities. The NEF 340 can selectively control exposure, allowing the internal architecture of the core network to be hidden from the external domain.

[0075] The UDM 350 can provide data storage for other NFs. The UDM 350 allows for a consolidated view of network information, which can be used to ensure that most relevant information is available to different NFs from a single resource. The UDM 350 can store and / or retrieve information from the Unified Data Repository (UDR). For example, the UDM 350 can obtain user subscription data related to UE 301 from the UDR.

[0076] AUSF 360 supports authentication of UE 301 by the mutual core network and authentication of the core network by UE 301. AUSF 360 can execute key agreement procedures and provide key materials that can be used to improve security.

[0077] The NSSF 370 can select one or more network slices to be used by the UE 301. The NSSF 370 can select a slice based on slice selection information. For example, the NSSF 370 can receive a single network slice selection assistance information (S-NSSAI) and map the S-NSSAI to a network slice instance identifier (NSI).

[0078] CHF 380 can control billing-related tasks associated with UE 301. For example, UPF 305 can report service usage associated with UE 301 to SMF 314. SMF 314 can collect usage data from UPF 305 and one or more other UPFs. Usage data may indicate how much data is exchanged, with which DN is data exchanged, the network slice associated with the data, or any other information that may affect billing. SMF 314 can share the collected usage data with CHF. CHF can use the collected usage data to perform billing-related tasks associated with UE 301. CHF may, depending on the billing status of UE 301, instruct SMF 314 to restrict or affect UE 301's access and / or provide billing-related notifications to UE 301.

[0079] The NWDAF 390 can collect and analyze data from other network functions and provide data analytics services to those functions. For example, the NWDAF 390 can collect data related to the load levels of specific network slice instances from UPF 305, AMF 312, and / or SMF 314. Based on the collected data, the NWDAF 390 can provide load level data to PCF 320 and / or NSSF 370, and / or notify PCF 320 and / or NSSF 370 slices whether their load levels have reached and / or exceeded load level thresholds.

[0080] AF 399 can operate outside the core network but can interact with it to provide information about QoS requirements or service routing preferences associated with specific applications. AF 399 can access the core network based on the open constraints imposed by NEF 340. However, the core network operator can treat AF 399 as a trusted domain with direct network access.

[0081] Figure 4A , 4B And 5 show similarities in some aspects Figure 3 Other examples of the core network architecture of the core network architecture 300 described herein are omitted for brevity. Figure 3 Some of the core network components described in the document. Figure 4A , 4B Many of the elements depicted in 5 are similar in some respects to Figure 3 The components depicted are shown in the image. For the sake of brevity, some details related to their function or operation have been omitted.

[0082] Figure 4AAn example of a core network architecture 400A is shown, comprising an arrangement of multiple UPFs. The core network architecture 400A includes UE 401, AN 402, AMF 412, and SMF 414. This differs from the previous example of the core network architecture described above. Figure 4A This describes multiple UPFs, including UPF 405, UPF 406, and UPF 407, and multiple DNs, including DN 408 and DN 409. Each of the multiple UPFs 405, 406, and 407 can communicate with the SMF 414 via the N4 interface. DNs 408 and 409 communicate with UPFs 405 and 406, respectively, via the N6 interface. Figure 4A As shown, multiple UPF 405, 406, and 407 can communicate with each other via the N9 interface.

[0083] UPF 405, 406, and 407 can perform service detection, whereby the UPF identifies and / or classifies packets. Packet identification can be performed based on Packet Detection Rules (PDRs) provided by SMF 414. A PDR may contain packet detection information including one or more of the following: source interface, UE IP address, core network (CN) tunnel information (e.g., the CN address corresponding to the N3 / N9 tunnel of a PDU session), network instance identifier, Quality of Service Flow Identifier (QFI), filter set (e.g., IP packet filter set or Ethernet packet filter set), and / or application identifier.

[0084] In addition to indicating how a specific packet will be detected, the PDR may further indicate the rules for processing the packet after it has been detected. These rules may include, for example, Forwarding Action (FAR) rules, Multiple Access (MAR) rules, Usage Reporting (URR) rules, QoS Enforcement (QER) rules, etc. For instance, the PDR may include one or more FAR identifiers, MAR identifiers, URR identifiers, and / or QER identifiers. These identifiers indicate the rules specified for processing the specific detected packet.

[0085] UPF 405 can perform traffic forwarding based on FAR. For example, FAR can instruct packets associated with a specific PDR to be forwarded, copied, dropped, and / or buffered. FAR can instruct the destination interface, such as "access" for downlink or "core" for uplink. If packets will be buffered, FAR can instruct a Buffer Action Rule (BAR). As an example, UPF 405 can perform data buffering of a specific number of downlink packets upon termination of the PDU session.

[0086] The UPF 405 can perform QoS enforcement based on a QER. For example, a QER can indicate an authorized guaranteed bit rate and / or a maximum bit rate to be enforced for packets associated with a particular PDR. The QER can indicate that a specific guaranteed and / or maximum bit rate is available for uplink and / or downlink packets. The UPF 405 can use a corresponding QFI to mark packets belonging to a specific QoS flow. This marking enables the packet receiver to determine the packet's QoS.

[0087] UPF 405 can provide usage reports to SMF 414 according to URRs. URRs can indicate one or more triggering conditions for the generation and reporting of usage reports, such as immediate reporting, periodic reporting, thresholds for incoming uplink traffic, or any other suitable triggering conditions. URRs can indicate methods for measuring network resource usage, such as data volume, duration, and / or events.

[0088] As described above, DNs 408 and 409 may include public DNs (e.g., the Internet), private DNs (e.g., dedicated, internally owned DNs), and / or carrier-owned DNs. Each DN can provide carrier services and / or third-party services. The services provided by the DN may be the Internet, IP Multimedia Subsystem (IMS), augmented or virtual reality networks, edge computing or mobile edge computing (MEC) networks, etc. Each DN can be identified using a Data Network Name (DNN). UE 401 can be configured to establish a first logical connection with DN 408 (first PDU session), a second logical connection with DN 409 (second PDU session), or both simultaneously (first and second PDU sessions).

[0089] Each PDU session may be associated with at least one UPF configured to operate as a PDU session anchor (PSA or "anchor"). The anchor may be a UPF that provides an N6 interface to the DN.

[0090] exist Figure 4AIn the example, UPF 405 could be an anchor for a first PDU session between UE 401 and DN 408, while UPF 406 could be an anchor for a second PDU session between UE 401 and DN 409. The core network can use anchors to provide service continuity (e.g., IP address continuity) for a specific PDU session as UE 401 moves from one access network to another. For example, suppose UE 401 establishes a PDU session using a data path to DN408 from an access network other than AN 402. The data path may include UPF 405, which acts as an anchor. Further suppose UE 401 later moves to the coverage area of ​​AN 402. In this scenario, SMF 414 can select a new UPF (UPF 407) to bridge the gap between the newly entered access network (AN 402) and the anchor UPF (UPF 405). The continuity of the PDU session can be maintained by adding or removing any number of UPFs from the data path. When a UPF is added to the data path, such as... Figure 4A As shown, it can be described as an intermediate UPF and / or a cascaded UPF.

[0091] As mentioned above, UPF 406 can be an anchor for a second PDU session between UE 401 and DN 409. Although Figure 4A The anchors used for the first and second PDU sessions are associated with different UPFs, but it should be understood that this is only an example. It will also be understood that multiple PDU sessions with a single DN can correspond to any number of anchors. When multiple UPFs exist, the UPF at the branch point (UPF 407 in Figure 4) can operate as an uplink classifier (UL-CL). UL-CL allows uplink user plane traffic to be offloaded to different UPFs.

[0092] SMF 414 can, for example, allocate, manage, and / or assign IP addresses to UE 401 after a PDU session is established. SMF 414 can maintain an internal set of IP addresses to be assigned. If necessary, SMF 414 can assign IP addresses provided by a Dynamic Host Configuration Protocol (DHCP) server or an Authentication, Authorization, and Accounting (AAA) server. IP address management can be performed according to Session and Service Continuity (SSC) modes. In SSC mode 1, the IP address of UE 401 can be maintained as the wireless device moves within the network (and the same anchor UPF can be used). In SSC mode 2, the IP address of UE 401 changes as UE 401 moves within the network (e.g., the old IP address and UPF can be discarded, and a new IP address and anchor UPF can be established). In SSC mode 3, it is possible to temporarily maintain the old IP address (similar to SSC mode 1) when a new IP address is established (similar to SSC mode 2), thus combining features of SSC modes 1 and 2. Applications sensitive to IP address changes can operate according to SSC mode 1.

[0093] UPF selection can be controlled by SMF 414. For example, after establishing and / or modifying a PDU session between UE 401 and DN 408, SMF 414 can select UPF 405 as the anchor for the PDU session and / or select UPF 407 as an intermediate UPF. Criteria for UPF selection include path efficiency and / or speed between AN 402 and DN 408. Reliability, load status, location, slicing support, and / or other capabilities of the candidate UPFs may also be considered.

[0094] Figure 4B This illustrates an example of a core network architecture 400B adapted for untrusted access. Similar to... Figure 4A ,like Figure 4B The UE 401 depicted is connected to DN 408 via AN 402 and UPF 405. AN 402 and UPF 405 constitute a trusted (e.g., 3GPP) access to DN 408. In contrast, UE 401 can also access DN 408 using an untrusted access network, AN 403, and the non-3GPP network interoperability function (N3IWF) 404.

[0095] AN 403 can be, for example, a Wireless Land Area Network (WLAN) operating according to the IEEE 802.11 standard. UE 401 can connect to AN 403 via interface Y1 in any way specified for AN 403. The connection to AN 403 may or may not involve authentication. UE 401 can obtain an IP address from AN 403. UE 401 can determine to connect to core network 400B and select untrusted access for this purpose. AN 403 can communicate with N3IWF 404 via interface Y2. After selecting untrusted access, UE 401 can provide N3IWF 404 with sufficient information to select an AMF. The selected AMF can be, for example, the same AMF used by UE 401 for 3GPP access (in this example, AMF 412). N3IWF 404 can communicate with AMF 412 via interface N2. UPF 405 can be selected, and N3IWF 404 can communicate with UPF 405 via the N3 interface. UPF 405 can be a PDU session anchor (PSA) and remains an anchor for the PDU session even as UE 401 switches between trusted and untrusted access.

[0096] Figure 5 An example of a core network architecture 500 in which UE 501 is in a roaming scenario is shown. In the roaming scenario, UE 501 is a subscriber to a first PLMN (Home PLMN or HPLMN) but attached to a second PLMN (Visit PLMN or VPLMN). The core network architecture 500 includes UE 501, AN 502, UPF 505, and DN 508. AN 502 and UPF 505 may be associated with a VPLMN. The VPLMN can manage AN 502 and UPF 505 using core network elements associated with the VPLMN, including AMF 512, SMF 514, PCF 520, NRF 530, NEF 540, and NSSF 570. AF 599 may be adjacent to the VPLMN's core network.

[0097] UE 501 may not be a VPLMN subscriber. AMF 512 may authorize UE 501 to access the network based on, for example, roaming restrictions imposed on UE 501. To obtain network services provided by the VPLMN, the VPLMN's core network may need to interact with the core network elements of UE 501's HPLMN, specifically PCF 521, NRF 531, NEF 541, UDM 551, and / or AUSF 561. The VPLMN and HPLMN can communicate using an N32 interface that connects to their respective Secure Edge Protection Agents (SEPPs). Figure 5In this context, the corresponding SEPPs are described as VSEPP 590 and HSEPP 591.

[0098] VSEPP 590 and HSEPP 591 communicate via the N32 interface for defined purposes, while hiding information about each PLMN from another PLMN. SEPP can apply roaming policies based on communications via the N32 interface. PCF 520 and PCF521 can communicate via SEPP to exchange policy-related signaling. NRF 530 and NRF 531 can communicate via SEPP to enable service discovery for NFs in their respective PLMNs. VPLMN and HPLMN can independently maintain NEF 540 and NEF 541. NSSF 570 and NSSF571 can communicate via SEPP to coordinate slice selection for UE 501. HPLMN handles all authentication and subscription-related signaling. For example, when UE 501 registers or requests service via VPLMN, VPLMN can authenticate UE 501 and / or obtain UE 501's subscription data by accessing HPLMN via SEPP's UDM 551 and AUSF 561.

[0099] Figure 5 The core network architecture 500 described can be referred to as a local breakout configuration, where UE 501 accesses DN 508 using one or more UPFs (i.e., UPF 505) of the VPLMN. However, other configurations are possible. For example, in a home-routed configuration ( Figure 5 (Not shown in the diagram) UE 501 can access the DN using one or more UPFs of the HPLMN. In the home routing configuration, the N9 interface can operate in parallel with the N32 interface, crossing the boundary between the VPLMN and HPLMN to carry user plane data. One or more SMFs of the corresponding PLMN can communicate via the N32 interface to coordinate session management for UE 501. The SMF can control its corresponding UPF on either side of the boundary.

[0100] Figure 6 An example of network slicing is shown. Network slicing can refer to dividing shared infrastructure (e.g., physical infrastructure) into distinct logical networks. These distinct logical networks can be controlled independently, isolated from each other, and / or associated with dedicated resources.

[0101] Network architecture 600A illustrates a non-sliced ​​physical network corresponding to a single logical network. Network architecture 600A includes a user plane, where UEs 601A, 601B, and 601C (collectively referred to as UE 601) have physical and logical connections to DN 608 via AN 602 and UPF 605. Network architecture 600A also includes a control plane, where AMF 612 and SMF 614 control various aspects of the user plane.

[0102] Network architecture 600A may have a specific set of characteristics (e.g., related to maximum bit rate, reliability, latency, bandwidth usage, power consumption, etc.). This set of characteristics may be influenced by the nature of the network elements themselves (e.g., processing power, availability of free memory, proximity to other network elements, etc.) or by their management (e.g., optimization to maximize bit rate or reliability, reduce latency or power bandwidth usage, etc.). The characteristics of network architecture 600A may change over time, for example, by upgrading equipment or by modifying procedures to target specific characteristics. However, at any given time, network architecture 600A will have a single set of characteristics that may or may not be optimized for a specific use case. For example, UEs 601A, 601B, and 601C may have different requirements, but network architecture 600A may be optimized for only one of the three.

[0103] Network Architecture 600B is an example of a sliced ​​physical network divided into multiple logical networks. Figure 6 In this configuration, the physical network is divided into three logical networks, called slice A, slice B, and slice C. For example, UE 601A can be served by AN 602A, UPF 605A, AMF 612, and SMF 614A. UE 601B can be served by AN 602B, UPF 605B, AMF 612, and SMF 614B. UE 601C can be served by AN 602C, UPF 605C, AMF 612, and SMF 614C. Although logically the corresponding UE 601 communicates with different network elements, these network elements can be deployed by the network operator using the same physical network elements.

[0104] Each network slice can be customized for network services with a different set of characteristics. For example, slice A could correspond to enhanced mobile broadband (eMBB) service. Mobile broadband refers to internet access typically associated with mobile users and smartphones. Slice B could correspond to ultra-reliable low-latency communication (URLLC), which focuses on reliability and speed. Compared to eMBB, URLLC improves the feasibility of use cases such as autonomous driving and remote surgery. Slice C could correspond to massive machine-type communication (mMTC), which focuses on low-power services delivered to a large number of users. For example, slice C could be optimized for dense networks of battery-powered sensors that provide small amounts of data at regular intervals. Many mMTC use cases would be prohibitively expensive to operate using eMBB or URLLC networks.

[0105] If the service requirements for one of UE 601 change, the network slice for the UE service can be updated to provide better service. Furthermore, the set of network characteristics corresponding to eMBB, URLLC, and mMTC can vary, enabling the provision of differentiated types of eMBB, URLLC, and mMTC. Alternatively, network operators can provide entirely new services in response to, for example, customer demands.

[0106] Figure 6 In example UE 601, each UE has its own network slice. However, it should be understood that a single slice can serve any number of UEs, and a single UE can use any number of slices for operation. Furthermore, in example network architecture 600B, AN602, UPF 605, and SMF 614 are divided into three separate slices, while AMF 612 is non-sliced. However, it should be understood that network operators can deploy any architecture that selectively utilizes any mixture of sliced ​​and non-sliced ​​network elements, where different network elements are divided into different numbers of slices. Although... Figure 6 Only three core network functions are described, but it should be understood that other core network functions can also be sliced. A PLMN that supports multiple network slices can maintain a separate Network Repository Function (NFR) for each slice, enabling other NFs to discover network services associated with said slice.

[0107] Network slice selection can be controlled by the AMF or by a separate Network Slice Selection Function (NSSF). For example, the network operator can define and implement distinct Network Slice Instances (NSIs). Each NSI can be associated with a single Network Slice Selection Assistance Information (S-NSSAI). The S-NSSAI can contain a specific slice / service type (SST) indicator (indicating eMBB, URLLC, mMTC, etc.). As an example, a specific tracking area can be associated with one or more configured S-NSSAIs. The UE can identify one or more requested and / or subscribed S-NSSAIs (e.g., during registration). The network can indicate one or more allowed and / or denied S-NSSAIs to the UE.

[0108] S-NSSAI may further include a slice distinguisher (SD) to differentiate between different tenants for a specific slice and / or service type. For example, a tenant could be a customer of a network operator (e.g., a vehicle manufacturer, service provider, etc.) that obtains (e.g., purchases) guaranteed network resources and / or specific policies for processing its subscribers. The network operator can configure different slices and / or slice types and use the SD to determine which tenant is associated with a specific slice.

[0109] Figure 7A , Figure 7B and Figure 7C This shows the user plane (UP) protocol stack, the control plane (CP) protocol stack, and the services between the protocol layers set up in the UP protocol stack.

[0110] The layers can be associated with the Open Systems Interconnection (OSI) model, which describes the functionality of computer networking. In the OSI model, Layer 1 may correspond to the bottom layer, with higher layers on top of the bottom layer. Layer 1 may correspond to the physical layer, which relates to the physical infrastructure (e.g., cables, optical fibers, and / or radio frequency transceivers) used to transmit signals. In New Radio (NR), Layer 1 may include the Physical Layer (PHY). Layer 2 may correspond to the Data Link Layer. Layer 2 may relate to the physical infrastructure that packages data (e.g., data frames) for transmission between nodes in the network using Layer 1. In NR, Layer 2 may include the Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Layer (PDCP) layer, and Service Data Application Protocol (SDAP) layer.

[0111] Layer 3 may correspond to the network layer. Layer 3 may relate to the routing of data already encapsulated in Layer 2. Layer 3 may handle the prioritization of data and traffic avoidance. In NR, Layer 3 may include the Radio Resource Control (RRC) layer and the Non-Access Layer (NAS) layer. Layers 4 through 7 may correspond to the transport layer, session layer, presentation layer, and application layer. The application layer interacts with the end user to provide application-related data. In the example, the end user implementing the application may generate application-related data and initiate the transmission of said information to a target data network (e.g., the Internet, application server, etc.). Starting at the application layer, each layer in the OSI model may manipulate and / or re-encapsulate information and deliver it to the next layer. At the lowest layer, manipulated and / or re-encapsulated information may be exchanged via physical infrastructure (e.g., electrically, optically, and / or electromagnetically). As it approaches the target data network, the information is decapsulated and provided to increasingly higher layers until it reaches the application layer again in a form available to the target data network (e.g., the same form it was provided by the end user). In response to end users, the data network can reverse-execute this procedure.

[0112] Figure 7A The user plane protocol stack is shown. The user plane protocol stack can be a New Radio (NR) protocol stack for the Uu interface between UE 701 and gNB 702. In layer 1 of the UP protocol stack, UE 701 can implement PHY 731 and gNB 702 can implement PHY 732. In layer 2 of the UP protocol stack, UE 701 can implement MAC 741, RLC 751, PDCP 761, and SDAP 771. gNB 702 can implement MAC 742, RLC 752, PDCP 762, and SDAP 772.

[0113] Figure 7B The control plane protocol stack is shown. The control plane protocol stack can be an NR protocol stack for the Uu interface between UE 701 and gNB 702 and / or the N1 interface between UE 701 and AMF 712. In layer 1 of the CP protocol stack, UE 701 can implement PHY 731 and gNB 702 can implement PHY 732. In layer 2 of the CP protocol stack, UE 701 can implement MAC 741, RLC 751, PDCP 761, RRC 781, and NAS 791. gNB 702 can implement MAC 742, RLC 752, PDCP 762, and RRC 782. AMF 712 can implement NAS 792.

[0114] NAS can relate to the non-access layer, specifically communication between UE 701 and the core network (e.g., AMF 712). Lower layers can relate to the access layer, such as communication between UE 701 and gNB 702. Messages sent between UE 701 and the core network can be referred to as NAS messages. In this example, NAS messages may be relayed by gNB 702, but the content of the NAS message (e.g., the information elements of the NAS message) may not be visible to gNB 702.

[0115] Figure 7C Showing the setting in Figure 7A The diagram illustrates an example of services between protocol layers of the NR user plane protocol stack. UE 701 can receive services via a PDU session, which can be a logical connection between UE 701 and a data network (DN). UE 701 and the DN can exchange data packets associated with the PDU session. The PDU session may include one or more Quality of Service (QoS) flows. SDAP 771 and SDAP 772 can perform mapping and / or demapping between the one or more QoS flows and one or more radio bearers (e.g., data radio bearers) of the PDU session. The mapping between QoS flows and data radio bearers can be determined by gNB 702 in SDAP 772 and can inform UE 701 of the mapping (e.g., based on control signaling and / or reflection mapping). For reflection mapping, SDAP 772 of gNB 220 can tag downlink packets with QoS Flow Indicators (QFIs) and deliver the downlink packets to UE 701. UE 701 can determine the mapping based on the QFI of the downlink packets.

[0116] PDCP 761 and PDCP 762 can perform header compression and / or decompression. Header compression reduces the amount of data transmitted at the physical layer. PDCP 761 and PDCP 762 can perform encryption and / or decryption. Encryption reduces unauthorized decoding of data transmitted at the physical layer (e.g., intercepted at the air interface) and protects data integrity (e.g., ensuring control messages originating from a designated source). PDCP 761 and PDCP 762 can perform retransmission of undelivered packets, packet delivery and reordering, packet duplication, and / or identification and removal of duplicate packets. In dual connectivity scenarios, PDCP 761 and PDCP 762 can perform splitting the mapping between radio bearers and RLC channels.

[0117] RLCs 751 and 752 can perform segmentation and retransmission via Automatic Repeat Request (ARQ). RLCs 751 and 752 can remove duplicate data units received from MACs 741 and 742, respectively. RLCs 213 and 223 can serve the RLC channel as a service to PDCPs 214 and 224, respectively.

[0118] MAC 741 and MAC 742 can perform multiplexing and / or demultiplexing of logical channels. MAC 741 and MAC 742 can map logical channels to transport channels. In the example, UE 701 can multiplex data elements of one or more logical channels into a transport block in MAC 741. UE 701 can use PHY 731 to transmit the transport block to gNB 702. gNB 702 can use PHY 732 to receive the transport block and demultiplex the data elements of the transport block back into the logical channels. MAC 741 and MAC 742 can perform error correction via Hybrid Automatic Repeat Request (HARQ), logical channel prioritization, and / or padding.

[0119] PHY 731 and PHY 732 can perform transmission channel to physical channel mapping. PHY 731 and PHY 732 can perform digital and analog signal processing functions (e.g., decoding / decoding and modulation / demodulation) for transmitting and receiving information (e.g., transmission via air interface). PHY 731 and PHY 732 can perform multi-antenna mapping.

[0120] Figure 8 An example of a Quality of Service (QoS) model for differentiated data exchange is shown. Figure 8 In the QoS models, there are UE 801, AN 802, and UPF 805. QoS models promote the prioritization of certain packets or Protocol Data Units (PDUs) (also known as packets). For example, higher priority packets can be exchanged faster and / or more reliably compared to lower priority packets. The network can allocate more resources to exchanging high QoS packets.

[0121] exist Figure 8 In the example, a PDU session 810 is established between UE 801 and UPF 805. PDU session 810 may be a logical connection enabling UE 801 to exchange data with a specific data network (e.g., the Internet). UE 801 may request the establishment of PDU session 810. When establishing PDU session 810, UE 801 may, for example, identify the target data network based on its Data Network Name (DNN). PDU session 810 may, for example, be managed by a Session Management Function (SMF, not shown). To facilitate the exchange of data associated with PDU session 810 between UE 801 and the data network, the SMF may select UPF 805 (and optionally, one or more other UPFs, not shown).

[0122] One or more applications associated with UE 801 may generate uplink packets 812A-812E associated with PDU session 810. To operate within the QoS model, UE 801 may apply QoS rule 814 to uplink packets 812A-812E. QoS rule 814 may be associated with PDU session 810 and may be determined and / or provided to UE 801 when PDU session 810 is established and / or modified. Based on QoS rule 814, UE 801 may classify uplink packets 812A-812E, mapping each of them to a QoS flow, and / or tagging uplink packets 812A-812E with a QoS flow indicator (QFI). As the packets travel through the network and potentially mix with other packets from other UEs with potentially different priorities, the QFI indicates how the packets should be processed according to the QoS model. In the current diagram, uplink packets 812A and 812B are mapped to QoS flow 816A, uplink packet 812C is mapped to QoS flow 816B, and the remaining packets are mapped to QoS flow 816C.

[0123] QoS flows can be the finest granular level of QoS differentiation within a PDU session. The diagram shows three QoS flows 816A-816C. However, it should be understood that any number of QoS flows can exist. Some QoS flows may be associated with a guaranteed bit rate (GBR QoS flow), while others may have a non-guaranteed bit rate (non-GBR QoS flow). QoS flows may also experience per-UE and per-session total bit rates. One of the QoS flows can be the default QoS flow. QoS flows can have different priorities. For example, QoS flow 816A may have a higher priority than QoS flow 816B, and QoS flow 816B may have a higher priority than QoS flow 816C. Different priorities can be reflected by different QoS flow characteristics. For example, QoS flows can be associated with a flow bit rate. A specific QoS flow can be associated with a guaranteed flow bit rate (GFBR) and / or a maximum flow bit rate (MFBR). A QoS flow can be associated with a specific packet delay budget (PDB), packet error rate (PER), and / or maximum packet loss rate. QoS flows can also experience total bit rates per UE and per session.

[0124] To function within the QoS model, UE 801 can apply resource mapping rule 818 to QoS flows 816A-816C. The air interface between UE 801 and AN 802 can be associated with resource 820. In the current illustration, QoS flow 816A is mapped to resource 820A, while QoS flows 816B and 816C are mapped to resource 820B. Resource mapping rule 818 can be provided by AN 802. To meet QoS requirements, resource mapping rule 818 can specify more resources for relatively high-priority QoS flows. With more resources, high-priority QoS flows, such as QoS flow 816A, are more likely to obtain high stream bit rates, low packet delay budgets, or other characteristics associated with QoS rule 814. Resource 820 may include, for example, radio bearers. Radio bearers (e.g., data radio bearers) can be established between UE 801 and AN 802. The 5G radio bearer between UE 801 and AN 802 may differ from the LTE bearer, such as the evolved packet system (EPS) bearer between the UE and the packet data network gateway (PGW), the S1 bearer between the eNB and the service gateway (SGW), and / or the S5 / S8 bearer between the SGW and the PGW.

[0125] Once a packet associated with a specific QoS flow is received at AN 802 via resource 820A or resource 820B, AN 802 separates the packet into the corresponding QoS flows 856A-856C based on QoS profile 828. QoS profile 828 may be received from the SMF. Each QoS profile may correspond to a QFI, such as the QFI marked on uplink packets 812A-812E. Each QoS profile may contain QoS parameters such as a 5G QoS identifier (5QI) and allocation and retention priority (ARP). QoS profiles for non-GBR QoS flows may further contain additional QoS parameters such as reflection QoS attributes (RQA). QoS profiles for GBR QoS flows may further contain additional QoS parameters such as guaranteed flow bit rate (GFBR), maximum flow bit rate (MFBR), and / or maximum packet loss rate. The 5QI may be a standardized 5QI with a one-to-one mapping from each well-known service to a standardized combination of 5G QoS features. 5QI can be dynamically assigned, and its standardized 5QI value is not defined. 5QI can represent 5G QoS characteristics. 5QI can include resource type, default priority, packet delay budget (PDB), packet error rate (PER), maximum data burst size, and / or average window. Resource type can indicate a non-GBR QoS flow, a GBR QoS flow, or a delay-critical GBR QoS flow. Average window can represent the duration experienced during the calculation of GFBR and / or MFBR. ARP can include priorities for preemption and preemption capabilities. Based on ARP, AN 802 can apply admission control to QoS flows under resource constraints.

[0126] AN 802 may select one or more N3 tunnels 850 for transmitting QoS flows 856A-856C. After the packets are segmented into QoS flows 856A-856C, the packets may be sent to UPF 805 (e.g., toward DN) via the selected one or more N3 tunnels 850. UPF 805 may verify that the QFI of uplink packets 812A-812E is aligned with QoS rule 814 provided to UE 801. UPF 805 may measure packets and / or count packets and / or provide packet metrics to, for example, PCF.

[0127] The diagram also illustrates the process used for the downlink. Specifically, one or more applications may generate downlink packets 852A-852E. UPF 805 may receive downlink packets 852A-852E from one or more DNs and / or one or more other UPFs. According to the QoS model, UPF 805 may apply Packet Detection Rule (PDR) 854 to downlink packets 852A-852E. Based on PDR 854, UPF 805 may map packets 852A-852E to QoS flows. In the current diagram, downlink packets 852A and 852B are mapped to QoS flow 856A, downlink packet 852C is mapped to QoS flow 856B, and the remaining packets are mapped to QoS flow 856C.

[0128] QoS flows 856A-856C can be sent to AN 802. AN 802 can apply resource mapping rules to QoS flows 856A-856C. In the current diagram, QoS flow 856A is mapped to resource 820A, while QoS flows 856B and 856C are mapped to resource 820B. To meet QoS requirements, resource mapping rules can specify more resources for high-priority QoS flows.

[0129] Figures 9A to 9D Example states and state transitions of a wireless device (e.g., a UE) are shown. At any given time, a wireless device may be in a Radio Resource Control (RRC) state, a Registration Management (RM) state, and a Connection Management (CM) state.

[0130] Figure 9A This is an example diagram illustrating the RRC state transitions of a wireless device (e.g., a UE). A UE can be in one of three RRC states: RRC Idle 910 (e.g., RRC_IDLE), RRC Inactive 920 (e.g., RRC_INACTIVE), or RRC Connected 930 (e.g., RRC_CONNECTED). A UE may implement different RAN-related control plane procedures depending on its RRC state. Other elements of the network (e.g., base stations) may track the RRC states of one or more UEs and implement RAN-related control plane procedures appropriate to each UE's RRC state.

[0131] In an RRC connection 930, it is possible for the UE to exchange data with the network (e.g., a base station). Parameters necessary for establishing this data exchange are known to both the UE and the network. These parameters may be mentioned and / or included in the UE's RRC context (sometimes referred to as the UE context). These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. The base station connected to the UE may store the UE's RRC context.

[0132] When in an RRC connection 930, the UE's mobility can be managed by the access network, while the UE itself can manage mobility when in an RRC idle 910 and / or RRC inactive 920. When in an RRC connection 930, the UE can manage mobility by measuring signal levels (e.g., reference signal levels) from the serving cell and neighboring cells and reporting these measurements to the base station currently serving the UE. The network can initiate a handover based on the reported measurements. The RRC state can transition from an RRC connection 930 to an RRC idle 910 via a connection release procedure 930, and to an RRC inactive 920 via a connection termination procedure 932.

[0133] In RRC idle 910, an RRC context may not be established for the UE. In RRC idle 910, the UE may not have an RRC connection with the base station. When in RRC idle 910, the UE may be in a dormant state most of the time (e.g., to conserve battery power). The UE may periodically wake up (e.g., once per discontinuous reception cycle) to monitor paging messages from the access network. The UE's mobility can be managed by the UE through a procedure called cell reselection. The RRC state can transition from RRC idle 910 to RRC connection 930 via connection establishment procedure 913, which may involve a random access procedure, as discussed in more detail below.

[0134] In RRC inactivity 920, the previously established RRC context is maintained in both the UE and the base station. This allows for a faster transition to RRC connection 930 with reduced signaling overhead compared to the transition from RRC idle 910 to RRC connected 930. The RRC state can be transitioned to RRC connected 930 via connection restoration procedure 923. The RRC state can be transitioned to RRC idle 910 via connection release procedure 921, which may be the same as or similar to connection release procedure 931.

[0135] RRC status can be associated with mobility management mechanisms. In RRC Idle 910 and RRC Inactive 920, mobility can be managed by the UE via cell reselection. The purpose of mobility management in RRC Idle 910 and / or RRC Inactive 920 is to allow the network to notify the UE of an event via a paging message, without having to broadcast the paging message across the entire mobile network. The mobility management mechanisms used in RRC Idle 910 and / or RRC Inactive 920 allow the network to track the UE at the cell-group level, enabling paging messages to be broadcast on cells within the cell group where the UE is currently camped, rather than across the entire network. Tracking can be based on different packet granularities. For example, there can be three levels of cell packet granularity: a single cell; cells within a RAN area identified by a RAN Area Identifier (RAI); and cells within a group of RAN areas referred to as a tracking area and identified by a Tracking Area Identifier (TAI).

[0136] A tracking area can be used to track the UE at the CN level. The CN can provide the UE with a list of TAIs associated with the UE's registration area. If the UE moves to a cell associated with a TAI not included in the list of TAIs associated with the UE's registration area via cell reselection, the UE can perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new UE registration area.

[0137] RAN areas can be used to track UEs at the RAN level. For a UE in the RRC inactive 920 state, a RAN notification area can be assigned to that UE. A RAN notification area can include one or more cell identities, a list of RAIs, and / or a list of TAIs. In the example, a base station can belong to one or more RAN notification areas. In the example, a cell can belong to one or more RAN notification areas. If a UE moves via cell reselection to a cell not included in its assigned RAN notification area, the UE can perform a notification area update to update its RAN notification area.

[0138] The base station that stores the RRC context for the UE, or the UE's last serving base station, may be referred to as the anchor base station. The anchor base station may maintain the UE's RRC context at least during the time period during which the UE remains in the anchor base station's RAN notification area and / or during the time period during which the UE remains in RRC inactivity.

[0139] Figure 9B This is an example diagram illustrating the registration management (RM) state transitions of a wireless device (e.g., a UE). The state is RM deregistration 940 (e.g., RM-DEREGISTERED) and RM registration 950 (e.g., RM-REGISTERED).

[0140] In RM deregistration 940, the UE does not register with the network, and the network cannot reach the UE. To become reachable by the network, the UE must perform an initial registration. As an example, the UE may register with the network's AMF. If registration is rejected (registration rejection 944), the UE remains in RM deregistration 940. If registration is accepted (registration acceptance 945), the UE transitions to RM registration 950. While the UE is in RM registration 950, the network may store, maintain, and / or sustain the UE's UE context. The UE context may be referred to as the radio device context. The UE context corresponding to network registration (maintained by the core network) may differ from the RRC context corresponding to the RRC state (maintained by the access network, such as a base station). The UE context may include a record of the UE identifier and various information associated with the UE, such as UE capability information, policy information for UE access and mobility management, a list of allowed or established slices or PDU sessions, and / or the UE's registration area (i.e., a list of tracking areas covering the geographic area where radio devices are likely to be found).

[0141] When a UE is in RM Registration 950, the network can store the UE's UE context and use it to reach the UE when necessary. Furthermore, some services cannot be provided by the network unless the UE is registered. A UE can update its UE context while remaining in RM Registration 950 (Registration Update Acceptance 955). For example, if a UE leaves one tracking area and enters another, the UE can provide the tracking area identifier to the network. The network can deregister the UE, or the UE can deregister itself (Deregistration 954). For example, the network can automatically deregister a radio device if it remains inactive for a specific amount of time. After deregistration, the UE can proceed to RM Deregistration 940.

[0142] Figure 9C This is an example diagram illustrating the connection management (CM) state transitions of a wireless device (e.g., a UE) from the perspective of the wireless device. The UE may be in CM idle 960 (e.g., CM-IDLE) or CM connected 970 (e.g., CM-CONNECTED).

[0143] In CM idle 960, the UE does not have a Non-Access Layer (NAS) signaling connection with the network. Therefore, the UE may not communicate with core network functions. The UE can transition to CM connection 970 by establishing an AN signaling connection (AN signaling connection establishment 967). This transition can be initiated by sending an initial NAS message. The initial NAS message can be a registration request (e.g., if the UE is in RM deregistration 940) or a service request (e.g., if the UE is in RM registration 950). If the UE is in RM registration 950, the UE can initiate AN signaling connection establishment by sending a service request, or the network can send a paging message, thereby triggering the UE to send a service request.

[0144] In CM Connection 970, the UE can use NAS signaling to communicate with core network functions. As an example, the UE can exchange NAS signaling with the AMF for registration management purposes, service request procedures, and / or authentication procedures. As another example, the UE can exchange NAS signaling with the SMF to establish and / or modify PDU sessions. The network can disconnect the UE, or the UE can disconnect itself (AN signaling connection release 976). For example, if the UE transitions to RM Deregistration 940, the UE can also transition to CM Idle 960. When the UE transitions to CM Idle 960, the network can terminate the user plane connection of the UE's PDU session.

[0145] Figure 9D This is an example diagram illustrating the CM state transitions of a wireless device (e.g., UE) from a network perspective (e.g., AMF). The CM state of the UE tracked by the AMF can be either CM Idle 980 (e.g., CM-IDLE) or CM Connected 990 (e.g., CM-CONNECTED). When the UE transitions from CM Idle 980 to CM Connected 990, the AMF can establish the UE's N2 context (N2 context establishment 989). When the UE transitions from CM Connected 990 to CM Idle 980, the AMF can release the UE's N2 context (N2 context release 998).

[0146] Figure 10-12 Example procedures are shown for UE registration, service requests, and PDU session establishment.

[0147] Figure 10 An example of a registration procedure for a wireless device (e.g., a UE) is shown. Based on the registration procedure, the UE can transition from, for example, RM deregistration 940 to RM registration 950.

[0148] Registration can be initiated by the UE for purposes such as obtaining authorization to receive services, enabling mobility tracking, enabling reachability, or other purposes. The UE may perform initial registration as the first step in connecting to the network (e.g., when the UE is powered on, airplane mode is off, etc.). Registration can also be performed periodically to keep the network aware of the UE's presence (e.g., when in CM-IDLE state), or in response to changes in UE capabilities or registration area. Deregistration can be performed (…). Figure 10 (Not shown in the image) to stop network access.

[0149] At position 1010, the UE transmits a registration request to the AN. As an example, the UE may have moved from the coverage area of ​​a previous AMF (shown as AMF#1) to the coverage area of ​​a new AMF (shown as AMF#2). The registration request can be a NAS message. The registration request may contain the UE identifier. The AN may select an AMF for the UE's registration. For example, the AN may select a default AMF. For example, the AN may select an AMF already mapped to the UE (e.g., a previous AMF). The NAS registration request may contain a network slice identifier, and the AN may select an AMF based on the requested slice. After selecting an AMF, the AN may send the registration request to the selected AMF.

[0150] At position 1020, the AMF (AMF#2) receiving the registration request performs a context transfer. The context can be the UE context, such as the UE's RRC context. As an example, AMF#2 can send a message to AMF#1 requesting the UE's context. This message may contain the UE identifier. This message may be a Namf_Communication_UEContextTransfer message. AMF#1 can send a message to AMF#2 containing the requested UE context. This message may be a Namf_Communication_UEContextTransfer message. After receiving the UE context, AMF#2 can coordinate the UE's authentication. After authentication is complete, AMF#2 can send a message to AMF#1 indicating that the UE context transfer is complete. This message may be a Namf_Communication_UEContextTransfer response message.

[0151] Authentication may require the participation of the UE, AUSF, UDM, and / or UDR (not shown). For example, the AMF may request the AUSF to authenticate the UE. For example, the AUSF may perform UE authentication. For example, the AUSF may obtain authentication data from the UDM. For example, the AUSF may send a Subscription Permanent Identifier (SUPI) to the AMF based on successful authentication. For example, the AUSF may provide an intermediate key to the AMF. The intermediate key can be used to derive the UE's access-specific security key, enabling the AMF to perform Security Context Management (SCM). The AUSF may obtain subscription data from the UDM. Subscription data may be based on information obtained from the UDM (and / or UDR). Subscription data may include subscription identifiers, security credentials, access and mobility-related subscription data, and / or session-related data.

[0152] At point 1030, the new AMF (AMF#2) registers and / or subscribes to the UDM. AMF#2 can perform registration using the UDM's UE Context Management Service (Nudm_UECM). AMF#2 can obtain the UE's subscription information using the UDM's Subscriber Data Management Service (Nudm_SDM). AMF#2 can further request the UDM to notify AMF#2 whether the UE's subscription information has changed. With the new AMF registering and subscribing, the old AMF (AMF#1) can be deregistered and unsubscribed. After deregistration, AMF#1 no longer has responsibilities for UE mobility management.

[0153] At position 1040, AMF#2 retrieves Access and Mobility (AM) policies from the PCF. As an example, AMF#2 can provide the UE's subscription data to the PCF. The PCF can determine access and mobility policies for the UE based on the subscription data, network operator data, current network conditions, and / or other suitable information. For instance, the owner of a first UE may purchase a higher service tier than the owner of a second UE. The PCF can provide rules associated with different service tiers. Based on the respective UE's subscription data, the network can apply different policies that promote different service tiers.

[0154] For example, access and mobility policies may involve service area restrictions, RAT / Frequency Selection Priority (RFSP, where RAT stands for Radio Access Technology), authorization and prioritization of access type (e.g., LTE versus NR), and / or selection of non-3GPP access (e.g., Access Network Discovery and Selection Policy (ANDSP)). Service area restrictions may include a list of tracking areas in which service is permitted (or prohibited) for the UE. Access and mobility policies may include UE route selection policies (URSP) that affect the routing of established or new PDU sessions. As mentioned above, different policies may be obtained and / or implemented based on the UE's subscription data, the UE's location (i.e., the location of the AN and / or AMF), or other suitable factors.

[0155] At 1050, AMF#2 can update the context of the PDU session. For example, if the UE has an existing PDU session, AMF#2 can coordinate with the SMF to activate the user plane connection associated with the existing PDU session. The SMF can update and / or release the session management context of the PDU session (Nsmf_PDUSession_UpdateSMContext, Nsmf_PDUSession_ReleaseSMContext).

[0156] At position 1060, AMF#2 sends a registration accept message to the AN, which forwards the registration accept message to the UE. The registration accept message may contain a new UE identifier and / or a new configured slice identifier. The UE may transmit a registration complete message to the AN, which forwards the registration complete message to AMF#2. The registration complete message acknowledges receipt of the new UE identifier and / or the new configured slice identifier.

[0157] At position 1070, AMF#2 can obtain UE policy control information from the PCF. The PCF can provide Access Network Discovery and Selection Policy (ANDSP) to facilitate non-3GPP access. The PCF can provide UE Route Selection Policy (URSP) to facilitate the mapping of specific data services to specific PDU session connectivity parameters. As an example, URSP can indicate that data services associated with a specific application should be mapped to a specific SSC mode, network slice, PDU session type, or preferred access type (3GPP or non-3GPP).

[0158] Figure 11 An example of a service request procedure for a wireless device (e.g., a UE) is shown. Figure 11 The service request procedure described herein is a network-triggered service request procedure for UEs in CM-IDLE state. However, see also [reference needed]. Figure 11Learn about other service request procedures (e.g., UE-triggered service request procedures), which will be discussed in more detail below.

[0159] At 1110, the UPF receives data. The data may be downlink data for transmission to the UE. The data may be associated with an existing PDU session between the UE and the DN. The data may be received, for example, from the DN and / or another UPF. The UPF may buffer the received data. In response to receiving data, the UPF may notify the SMF of the received data. The identity of the SMF to be notified may be determined based on the received data. The notification may be, for example, an N4 session report. The notification may indicate that the UPF has received data associated with the UE and / or a specific PDU session associated with the UE. In response to receiving the notification, the SMF may send PDU session information to the AMF. The PDU session information may be sent in an N1N2 message pass for forwarding to the AN. The PDU session information may include, for example, UPF tunnel endpoint information and / or QoS information.

[0160] At 1120, the AMF determines that the UE is in CM-IDLE state. This determination at 1120 is made in response to the receipt of PDU session information. Based on the determination that the UE is in CM-IDLE, the service request procedure can proceed to 1130 and 1140, as follows... Figure 11 As described in the document. However, if the UE is not in CM-IDLE (e.g., the UE is in CM-CONNECTED), steps 1130 and 1140 can be skipped, and the service request procedure can proceed directly to step 1150.

[0161] At 1130, the AMF pages the UE. Paging at 1130 can be performed based on the UE being in CM-IDLE. To perform paging, the AMF can send the paging message to the AN. This paging may be referred to as a paging message or a paging request message. The paging message may be an N2 request message. The AN may be one of multiple ANs in the UE's RAN notification area. The AN can send the paging message to the UE. The UE may be within the coverage area of ​​the AN and may receive the paging message.

[0162] At point 1140, the UE can request service. The UE can transmit the service request to the AMF via the AN. For example... Figure 11 As described, the UE can request service at 1140 in response to receiving a paging at 1130. However, as mentioned above, this is a specific case for a network-triggered service request procedure. In some scenarios (e.g., if uplink data becomes available at the UE), the UE can initiate a UE-triggered service request procedure. A UE-triggered service request procedure can begin at 1140.

[0163] At 1150, the network can authenticate the UE. Authentication may require the participation of the UE, AUSF, and / or UDM, such as authentication similar to that described elsewhere in this disclosure. In some cases (e.g., if the UE has recently been authenticated), authentication at 1150 can be skipped.

[0164] At 1160, AMF and SMF can perform PDU session updates. As part of the PDU session update, SMF can provide AMF with one or more UPF tunnel endpoint identifiers. In some cases ( Figure 11 (Not shown in the figure), an SMF may have to coordinate with one or more other SMFs and / or one or more other UPFs to set up the user face.

[0165] At 1170, the AMF can send PDU session information to the AN. The PDU session information can be included in the N2 request message. Based on the PDU session information, the AN can configure user plane resources for the UE. To configure user plane resources, the AN can, for example, perform an RRC reconfiguration of the UE. The AN can acknowledge receipt of the PDU session information to the AMF. The AN can notify the AMF that user plane resources have been configured and / or provide information related to user plane resource configuration.

[0166] In the event of a UE-triggered service request procedure, the UE can receive a NAS service acceptance message from the AMF via the AN at 1170. After configuring user plane resources, the UE can transmit uplink data (e.g., uplink data that caused the UE to trigger the service request procedure).

[0167] At 1180, the AMF can update the Session Management (SM) context of the PDU session. For example, the AMF can notify the SMF (and / or one or more other associated SMFs) that user plane resources have been configured, and / or provide information related to user plane resource configuration. The AMF can provide the SMF (and / or one or more other associated SMFs) with one or more AN tunnel endpoint identifiers. After the SM context update is complete, the SMF can send an Update SM Context Response message to the AMF.

[0168] Based on updates to the Session Management Context (SMF), the SMF can update the PCF for policy control purposes. For example, if the UE's location has changed, the SMF can notify the PCF of the UE's new location.

[0169] Based on updates to the session management context, the SMF and UPF can perform session modifications. Session modifications can be performed using the N4 session modification message. After the session modification is complete, the UPF can transmit downlink data (e.g., downlink data that causes the UPF to trigger a network-triggered service request procedure) to the UE. The transmission of downlink data can be based on one or more AN tunnel endpoint identifiers of the AN.

[0170] Figure 12 An example of a Protocol Data Unit (PDU) session establishment procedure for a wireless device (e.g., a UE) is shown. The UE may determine to transmit a PDU session establishment request to create a new PDU session, to hand over an existing PDU session to the 3GPP network, or for any other suitable reason.

[0171] At 1210, the UE initiates PDU session establishment. The UE may transmit the PDU session establishment request to the AMF via the AN. The PDU session establishment request may be a NAS message. The PDU session establishment request may indicate: PDU session ID; the requested PDU session type (new or existing); the requested DN (DNN); the requested network slice (S-NSSAI); the requested SSC mode; and / or any other suitable information. The PDU session ID may be generated by the UE. The PDU session type may be, for example, an Internet Protocol (IP) based type (e.g., IPv4, IPv6, or dual-stack IPv4 / IPv6), an Ethernet type, or an unstructured type.

[0172] The AMF can select an SMF based on a PDU session establishment request. In some scenarios, the requested PDU session may already be associated with a specific SMF. For example, the AMF may store the UE's UE context, and the UE context may indicate that the PDU session ID of the requested PDU session is already associated with a specific SMF. In some scenarios, the AMF can select an SMF based on determining that the SMF is ready to handle the requested PDU session. For example, the requested PDU session may be associated with a specific DNN and / or S-NSSAI, and the SMF can be selected based on determining that it can manage PDU sessions associated with a specific DNN and / or S-NSSAI.

[0173] At 1220, the context of the network management PDU session is established. After selecting the SMF at 1210, the AMF sends a PDU session context request to the SMF. The PDU session context request may include the PDU session establishment request received from the UE at 1210. The PDU session context request may be an Nsmf_PDUSession_CreateSMContext request and / or an Nsmf_PDUSession_UpdateSMContext request. The PDU session context request may indicate the UE's identifier; the requested DN; and / or the requested network slice. Based on the PDU session context request, the SMF may retrieve subscription data from the UDM. The subscription data may be the UE's session management subscription data. The SMF may subscribe to updates to the subscription data, allowing the PCF to send new information if the UE's subscription data changes. After obtaining the UE's subscription data, the SMF may transmit the PDU session context response to the AMG. The PDU session context response may be an Nsmf_PDUSession_CreateSMContext response and / or an Nsmf_PDUSession_UpdateSMContext response. The PDU session context response may include the session management context ID.

[0174] At point 1230, secondary authorization / authentication can be performed if necessary. Secondary authorization / authentication can involve the UE, AMF, SMF, and DN. The SMF can access the DN via the Data Network Authentication, Authorization, and Accounting (DN AAA) server.

[0175] At 1240, the network configures the data path for uplink data associated with a PDU session. The SMF can select a PCF and establish a session management policy association. Based on this association, the PCF can provide an initial set of policy control and charging rules (PCC rules) for the PDU session. When targeting a specific PDU session, the PCF can instruct the SMF on the method for assigning IP addresses to the PDU session, the default charging method for the PDU session, the address of the corresponding charging entity, the triggering factor for requesting a new policy, etc. The PCF can also target Service Data Flows (SDFs) that include one or more PDU sessions. When targeting an SDF, the PCF can instruct the SMF on policies for applying QoS requirements, monitoring services (e.g., for charging purposes), and / or offloading services (e.g., by using one or more specific N6 interfaces).

[0176] SMF can determine and / or assign IP addresses for PDU sessions. SMF can select one or more UPFs (in Figure 12In the example, a single UPF handles the PDU session. The SMF can send N4 session messages to the selected UPF. N4 session messages can be N4 session establishment requests and / or N4 session modification requests. N4 session messages can contain packet detection, enforcement, and reporting rules associated with the PDU session. In response, the UPF can acknowledge by sending N4 session establishment responses and / or N4 session modification responses.

[0177] The SMF can send PDU session management information to the AMF. PDU session management information can be a session service request (e.g., Namf_Communication_N1N2MessageTransfer) message. PDU session management information can include the PDU session ID. PDU session management information can be a NAS message. PDU session management information can include N1 session management information and / or N2 session management information. N1 session management information can include a PDU session establishment acceptance message. The PDU session establishment acceptance message can include the UPF's tunneling endpoint information and the Quality of Service (QoS) information associated with the PDU session.

[0178] The AMF can send an N2 request to the AN. The N2 request may include a PDU session establishment acceptance message. Based on the N2 request, the AN can determine the AN resources for the UE. AN resources can be used by the UE to establish a PDU session with the DN via the AN. The AN can determine the resources to be used for the PDU session and indicate the determined resources to the UE. The AN can send a PDU session establishment acceptance message to the UE. For example, the AN can perform an RRC reconfiguration for the UE. After setting the AN resources, the AN can send an N2 request acknowledgment to the AMF. The N2 request acknowledgment may include N2 session management information, such as the PDU session ID and the AN's tunneling endpoint information.

[0179] After setting the data path for uplink data at position 1240, the UE can optionally transmit uplink data associated with the PDU session. For example... Figure 12 As shown, uplink data can be sent to the DN associated with the PDU session via the AN and UPF.

[0180] At position 1250, the network can update the PDU session context. The AMF can transmit a PDU session context update request to the SMF. The PDU session context update request can be an Nsmf_PDUSession_UpdateSMContext request. The PDU session context update request can include N2 session management information received from the AN. The SMF can acknowledge the PDU session context update. The acknowledgment can be an Nsmf_PDUSession_UpdateSMContext response. The acknowledgment can include a request to notify the SMF of any UE mobility event subscriptions. Based on the PDU session context update request, the SMF can send an N4 session message to the UPF. The N4 session message can be an N4 session modification request. The N4 session message can contain tunneling endpoint information of the AN. The N4 session message can contain forwarding rules associated with the PDU session. In response, the UPF can acknowledge by sending an N4 session modification response.

[0181] After receiving the tunneling endpoint information from the AN, the UPF can relay downlink data associated with the PDU session. For example... Figure 12 As shown in the diagram, downlink data can be received from the DN associated with the PDU session via the AN and UPF.

[0182] Figure 13 Examples of components shown are examples of elements in a communication network. Figure 13 A physical deployment 1330 (hereinafter "deployment 1330") includes a wireless device 1310, a base station 1320, and one or more network functions. Any wireless device described in this disclosure may have similar components and may be implemented in a similar manner to wireless device 1310. Any other base station (or any part thereof, depending on the architecture of the base station) described in this disclosure may have similar components and may be implemented in a similar manner to base station 1320. Any physical core network deployment (or any part thereof, depending on the architecture of the base station) in this disclosure may have similar components and may be implemented in a similar manner to deployment 1330.

[0183] Wireless device 1310 can communicate with base station 1320 via air interface 1370. The communication direction from wireless device 1310 to base station 1320 via air interface 1370 is called the uplink, and the communication direction from base station 1320 to wireless device 1310 via air interface 1370 is called the downlink. Downlink transmission can be separated from uplink transmission using a combination of FDD, TDD, and / or duplex technologies. Figure 13 A single wireless device 1310 and a single base station 1320 are shown, but it should be understood that the wireless device 1310 can communicate with any number of base stations or other access network components via air interface 1370, and the base station 1320 can communicate with any number of wireless devices via air interface 1370.

[0184] Wireless device 1310 may include processing system 1311 and memory 1312. Memory 1312 may include one or more computer-readable media, such as one or more non-transitory computer-readable media. Memory 1312 may contain instructions 1313. Processing system 1311 may process and / or execute instructions 1313. Processing and / or execution of instructions 1313 may cause wireless device 1310 and / or processing system 1311 to perform one or more functions or activities. Memory 1312 may contain data (not shown). One of the functions or activities performed by processing system 1311 may be storing data in memory 1312 and / or retrieving previously stored data from memory 1312. In the example, downlink data received from base station 1320 may be stored in memory 1312, and uplink data for transmission to base station 1320 may be retrieved from memory 1312. Figure 13 As shown, wireless device 1310 can communicate with base station 1320 using transmission processing system 1314 and / or reception processing system 1315. Alternatively, transmission processing system 1314 and reception processing system 1315 can be implemented as a single processing system, or both can be omitted, and all processing in wireless device 1310 can be performed by processing system 1311. Although Figure 13 Not shown in the diagram, but the transmission processing system 1314 and / or the reception processing system 1315 may be coupled to a dedicated memory similar to but separate from memory 1312, and containing instructions that can be processed and / or executed to perform one or more of their respective functionalities. The wireless device 1310 may include one or more antennas 1316 for access to the air interface 1370.

[0185] Wireless device 1310 may include one or more other elements 1319. These other elements 1319 may include software and / or hardware providing features and / or functionality, such as speakers, microphones, keypads, displays, touchpads, satellite transceivers, Universal Serial Bus (USB) ports, hands-free headsets, FM radio units, media players, internet browsers, electronic control units (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, light sensors, ultrasonic sensors, light sensors, cameras, GPS sensors, etc.). Wireless device 1310 may receive user input data from and / or provide user output data to these other elements 1319. These other elements 1319 may include a power source. Wireless device 1310 may receive power from the power source and may be configured to distribute power to other components within wireless device 1310. The power source may include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof.

[0186] Wireless device 1310 can transmit uplink data to and / or receive downlink data from base station 1320 via air interface 1370. To perform transmission and / or reception, one or more of processing system 1311, transmission processing system 1314, and / or receiving system 1315 can implement Open Systems Interconnection (OSI) functionality. As an example, transmission processing system 1314 and / or receiving system 1315 can implement layer 1 OSI functionality, and processing system 1311 can implement higher-layer functionality. Wireless device 1310 can use one or more antennas 1316 to transmit and / or receive data via air interface 1370. In scenarios where said one or more antennas 1316 include multiple antennas, the multiple antennas can be used to perform one or more multi-antenna techniques, such as spatial multiplexing (e.g., single-user multiple-input multiple-output (MIMO) or multi-user MIMO), transmit / receive diversity, and / or beamforming.

[0187] Base station 1320 may include processing system 1321 and memory 1322. Memory 1322 may include one or more computer-readable media, such as one or more non-transitory computer-readable media. Memory 1322 may contain instructions 1323. Processing system 1321 may process and / or execute instructions 1323. Processing and / or execution of instructions 1323 may cause base station 1320 and / or processing system 1321 to perform one or more functions or activities. Memory 1322 may contain data (not shown). One of the functions or activities performed by processing system 1321 may be storing data in memory 1322 and / or retrieving previously stored data from memory 1322. Base station 1320 may communicate with wireless device 1310 using transmission processing system 1324 and reception processing system 1325. Although Figure 13 Not shown in the diagram, but the transmission processing system 1324 and / or the reception processing system 1325 may be coupled to a dedicated memory similar to but separate from memory 1322, and containing instructions that can be processed and / or executed to perform one or more of their respective functionalities. The wireless device 1320 may include one or more antennas 1326 for access to the air interface 1370.

[0188] Base station 1320 can transmit downlink data to and / or receive uplink data from wireless device 1310 via air interface 1370. To perform transmission and / or reception, one or more of processing system 1321, transmission processing system 1324, and / or receiving system 1325 can implement OSI functionality. As an example, transmission processing system 1324 and / or receiving system 1325 can implement layer 1 OSI functionality, and processing system 1321 can implement higher-layer functionality. Base station 1320 can use one or more antennas 1326 to transmit and / or receive data via air interface 1370. In scenarios where said one or more antennas 1326 include multiple antennas, the multiple antennas can be used to perform one or more multi-antenna techniques, such as spatial multiplexing (e.g., single-user multiple-input multiple-output (MIMO) or multi-user MIMO), transmit / receive diversity, and / or beamforming.

[0189] Base station 1320 may include interface system 1327. Interface system 1327 may communicate with one or more base stations and / or one or more elements of the core network via interface 1380. Interface 1380 may be wired and / or wireless, and interface system 1327 may include one or more components adapted for communication via interface 1380. Figure 13In this configuration, interface 1380 connects base station 1320 to a single deployment 1330; however, it should be understood that wireless device 1310 may communicate with any number of base stations and / or CN deployments via interface 1380, and deployment 1330 may communicate with any number of base stations and / or other CN deployments via interface 1380. Base station 1320 may include one or more other elements 1329 similar to one or more of the other elements 1319.

[0190] Deployment 1330 may include any number of portions of any number of instances of one or more Network Functions (NFs). Deployment 1330 may include processing system 1331 and memory 1332. Memory 1332 may include one or more computer-readable media, such as one or more non-transitory computer-readable media. Memory 1332 may contain instructions 1333. Processing system 1331 may process and / or execute instructions 1333. Processing and / or execution of instructions 1333 may cause deployment 1330 and / or processing system 1331 to perform one or more functions or activities. Memory 1332 may contain data (not shown). One of the functions or activities performed by processing system 1331 may be storing data in memory 1332 and / or retrieving previously stored data from memory 1332. Deployment 1330 may access interface 1380 using interface system 1337. Deployment 1330 may include one or more other elements 1339 similar to one or more of the other elements 1319.

[0191] One or more of systems 1311, 1314, 1315, 1321, 1324, 1325, and / or 1331 may include one or more controllers and / or one or more processors. The one or more controllers and / or processors may include, for example, general-purpose processors, digital signal processors (DSPs), microcontrollers, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) and / or other programmable logic devices, discrete gate and / or transistor logic, discrete hardware components, onboard units, or any combination thereof. One or more of systems 1311, 1314, 1315, 1321, 1324, 1325, and / or 1331 may perform signal decoding / processing, data processing, power control, input / output processing, and / or any other functionality that enables wireless device 1310, base station 1320, and / or deployment 1330 to operate in a mobile communication system.

[0192] Many elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs the defined function and has defined interfaces to other elements. Modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, wet hardware (e.g., hardware with biological elements), or combinations thereof, all of which may be behaviorally equivalent. For example, a module can be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript. It is possible to implement modules using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include computers, microcontrollers, microprocessors, DSPs, ASICs, FPGAs, and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors can be programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs, and CPLDs are frequently programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog. These languages ​​configure connections between limited internal hardware modules on a programmable device. The aforementioned techniques are often combined to achieve the desired functional module results.

[0193] Wireless device 1310, base station 1320, and / or deployment 1330 may implement timers and / or counters. A timer / counter may be started at an initial value. As used herein, starting may include restarting. Once started, the timer / counter can operate. The operation of the timer / counter may be associated with an event. When the event occurs, the value of the timer / counter may change (e.g., increment or decrement). The event may be, for example, an exogenous event (e.g., receiving a signal, measuring conditions, etc.), an endogenous event (e.g., transmitting a signal, calculating, comparing, performing an action, or making a decision thus performed, etc.), or any combination thereof. In the case of a timer, the event may be the elapsed amount of time. However, it should be understood that a timer may be described and / or implemented as a counter that counts the elapsed time units. The timer / counter may operate in the direction of the final value until it reaches the final value. The reaching of the final value may be referred to as the timer / counter expiration. The final value may be referred to as the threshold. The timer / counter may be paused, wherein the current value of the timer / counter is maintained, sustained, and / or extended, even after one or more events that would otherwise have changed the value of the timer / counter have occurred. The timer / counter can be canceled from pause or resumed, wherein the value, which has been held, maintained, and / or extended, begins to change again upon the occurrence of one or more of the events. The timer / counter can be set and / or reset. Setting may include resetting, as used herein. When a timer / counter is set and / or reset, its value may be set to an initial value. The timer / counter can be started and / or restarted. Starting may include restarting, as used herein. In some embodiments, when the timer / counter is restarted, its value may be set to an initial value and the timer / counter may begin running.

[0194] Figure 14A , 14B Figures 14C and 14D illustrate various example arrangements of physical core network deployments, each having one or more network functions or portions thereof. Core network deployments include deployments 1410, 1420, 1430, 1440, and / or 1450. Each deployment may, for example, be similar to... Figure 13Deployment 1330 is depicted in the description. Specifically, each deployment may include a processing system for performing one or more functions or activities, a memory for storing data and / or instructions, and an interface system for communicating with other network elements (e.g., other core network deployments). Each deployment may include one or more network functions (NFs). The term NF may refer to a particular set of functions and / or one or more physical elements configured to perform those functions (e.g., a processing system and memory including instructions that, when executed by the processing system, cause the processing system to perform the functions). For example, in this disclosure, when a network function is described as performing X, Y, and Z, it should be understood that this means the one or more physical elements are configured to perform X, Y, and Z, regardless of how or where the one or more physical elements are deployed. The term NF may refer to a network node, network element, and / or network device.

[0195] As will be discussed in more detail below, there are many different types of NFs, and each type of NF can be associated with different sets of functionalities. Multiple different NFs can be flexibly deployed in different locations (e.g., in different physical core network deployments) or in the same location (e.g., co-located in the same deployment). A single NF can be flexibly deployed in different locations (implemented using different physical core network deployments) or in the same location. Furthermore, a physical core network deployment can also implement one or more base stations, application functions (AFs), data networks (DNs), or any part thereof. NFs can be implemented in many ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtual functions instantiated on a platform (e.g., a cloud-based platform).

[0196] Figure 14A An example arrangement of a core network deployment is shown, where each deployment includes a network function. Deployment 1410 includes NF 1411, deployment 1420 includes NF 1421, and deployment 1430 includes NF 1431. Deployments 1410, 1420, and 1430 communicate via interface 1490. Deployments 1410, 1420, and 1430 may have different physical locations with different signal propagation delays relative to other network elements. This diversity of physical locations of deployments 1410, 1420, and 1430 enables services to be delivered to a wide area with improved speed, coverage, security, and / or efficiency.

[0197] Figure 14B An example layout is shown where a single deployment comprises more than one NF. Unlike... Figure 14A (Each NF is deployed in a separate deployment), Figure 14BThe diagram illustrates multiple NFs in deployments 1410 and 1420. In this example, deployments 1410 and 1420 may implement Software-Defined Networking (SDN) and / or Network Functions Virtualization (NFV).

[0198] For example, deployment 1410 includes an additional network function NF 1411A. NF 1411 and 1411A may consist of multiple instances of the same NF type, cooperatively located at the same physical location within the same deployment 1410. NF 1411 and 1411A may be implemented independently of each other (e.g., isolated and / or independently controlled). For example, NF 1411 and 1411A may be associated with different network slices. The processing systems and memory associated with deployment 1410 may perform all the functions associated with NF 1411 in addition to those associated with NF 1411A. In this example, NF 1411 and 1411A may be associated with different PLMNs, but deployment 1410 implementing NF 1411 and 1411A may be owned and / or operated by a single entity.

[0199] exist Figure 14B Elsewhere, deployment 1420 includes NF 1421 and additional network function NF 1422. NFs 1421 and 1422 can be different NF types. Similar to NFs 1411 and 1411A, NFs 1421 and 1422 can be co-located within the same deployment 1420, but implemented separately. As an example, a first PLMN may own and / or operate deployment 1420 with NFs 1421 and 1422. As another example, a first PLMN may implement NF 1421, and a second PLMN may obtain (e.g., lease, borrow, acquire, etc.) at least a portion of the capabilities of deployment 1420 (e.g., processing power, data storage, etc.) from the first PLMN to implement NF 1422. As yet another example, the deployment may be owned and / or operated by one or more third parties, and the first PLMN and / or the second PLMN may obtain corresponding portions of the capabilities of deployment 1420. When multiple NFs are provided at a single deployment, the network can operate with greater speed, coverage, security, and / or efficiency.

[0200] Figure 14C An example arrangement of core network deployment is shown, in which a single instance of an NF is implemented using multiple different deployments. Specifically, a single instance of NF 1422 is implemented at deployments 1420 and 1440. As an example, the functionality provided by NF 1422 can be implemented as a bundle or a series of sub-services. Each sub-service can be implemented independently, for example, at different deployments. Each sub-service can be implemented in different physical locations. By implementing sub-services of a single NF distributed across different physical locations, the mobile communication network can operate with greater speed, coverage, security, and / or efficiency.

[0201] Figure 14D This illustrates an example layout for a core network deployment, where one or more network functions are implemented using data processing services. Figure 14D In this context, NFs 1411, 1411A, 1421, and 1422 are included in deployment 1450, which is implemented as a data processing service. Deployment 1450 may include, for example, a cloud network and / or a data center. Deployment 1450 may be owned and / or operated by a PLMN or by a non-PLMN third party. NFs 1411, 1411A, 1421, and 1422 implemented using deployment 1450 may belong to the same PLMN or different PLMNs. The PLMN may obtain (e.g., lease, borrow, acquire, etc.) at least a portion of the capabilities of deployment 1450 (e.g., processing power, data storage, etc.). By providing one or more NFs through the data processing service, the mobile communication network can operate at greater speed, coverage, security, and / or efficiency.

[0202] As shown in the figure, different network elements (e.g., NFs) may be located in different physical deployments or co-located in a single physical deployment. It should be understood that, in this disclosure, the sending and receiving of messages between different network elements is not limited to inter-deployment or intra-deployment transmissions, unless explicitly indicated.

[0203] In the example, the deployment can be a 'black box' that pre-configures one or more NFs and is pre-configured to communicate with other 'black box' deployments (e.g., via interface 1490) in a prescribed manner. Alternatively, the deployment can be configured to operate according to open-source instructions (e.g., software) designed to implement the NF and to communicate with other deployments transparently. The deployment can operate according to the Open RAN (O-RAN) standard.

[0204] To obtain connectivity services, a UE can select a network to which it performs a registration procedure. The UE can attempt to register with the selected network. For example, when the UE is on, it can perform network selection to choose a network for registration. For network selection, the UE can identify one or more candidate networks, select a network from these candidate networks, and / or attempt to register with the selected network.

[0205] To determine one or more candidate networks, the UE can use a network selection list, information about the UE's home network, etc. The network selection list may include information about one or more networks, priority information for one or more networks, and / or information about one or more access technologies for one or more networks. For example, information about one or more access technologies may include one or more identifiers for one or more access technologies (e.g., NG-RAN, Satellite NG-RAN, E-UTRAN (WB-S1 mode), E-UTRAN (NB-S1 mode), UTRAN, GERAN, GERAN EC-GSM-IoT).

[0206] In the example, when the UE is activated, it can select a home network to which it has a subscription. Based on this selection, the UE can perform a cell search to detect one or more cells belonging to the home network. If the UE finds one or more cells of the selected home network, it can attempt to register with the home network. If the UE does not find one or more cells of the selected home network, it can use a list of network selections. If the registration attempt with the selected home network fails, the UE can use the list of network selections. For example, the UE can select a first network (e.g., a first-priority network) from one or more networks indicated by the network list. For the selected network (e.g., the first-priority network), the UE can attempt a cell search for the selected network and / or register with the selected network. If the cells of the selected network are unavailable and / or if the UE fails to register with the selected network, the UE can select a second network (e.g., a second-priority network) from one or more networks indicated by the network list. The UE can search for one or more cells of the second network and / or attempt to register with the second network. If the cell search and / or registration fails, the UE can select another network from one or more networks indicated by the network list. This iteration can continue until the UE successfully registers with the network.

[0207] Figure 15 An example implementation is described in which the network provides connectivity services to UEs within a specific area (e.g., within coverage area), and / or the network may not provide connectivity services to UEs within a specific area (e.g., outside coverage area). In the example, to construct a coverage area in which the network provides connectivity services to UEs, the network may include one or more base stations. Within the network's coverage area, UEs may transmit signals to and / or receive signals from one or more base stations of the network.

[0208] In implementations, network coverage may not cover one or more areas where the UE might be located. For example, one or more areas could include areas of a stadium, a theater, a private property, a shopping mall, etc. In one example, theater management might decide not to allow the network to have a base station within the theater. If the network has no base station within the theater, it may not provide connectivity service to the UE. Due to the lack of a base station within the theater, network coverage may not include the area within the theater. In one example, a stadium might be located in a remote area where users are not present most of the time. Based on the absence of users, the network could determine not to deploy a base station near the stadium. In one example, the owner of a shopping mall might not allow the network to install a base station within the shopping mall.

[0209] Figure 16 An example implementation is described, in which one or more networks can provide connectivity services to UEs in one or more areas.

[0210] In one implementation, a network (e.g., a home network) can provide connectivity services to UEs in a specific area (e.g., the coverage area of ​​the home network). The network (e.g., the home network) may not provide connectivity services to UEs in other areas (e.g., outside the coverage area of ​​the home network). For areas where the home network does not provide connectivity services, a managed network can provide connectivity services to UEs. For example, in an area of ​​a theater where UEs cannot connect to the home network, the theater's management can operate a managed network. The managed network can provide connectivity services to UEs visiting the theater. Similarly, in an area of ​​a stadium where the home network does not provide connectivity services, the stadium operator can deploy a network (e.g., a managed network) including one or more base stations installed in the stadium. One or more base stations can provide connectivity services to UEs. The stadium operator can allow one or more visitors to the stadium to use the managed network. For example, a shopping mall owner can determine to provide connectivity services to its customers and / or can deploy a managed network. A managed network in the shopping mall can provide connectivity services to UEs. In this example, if the quality of service (e.g., data rate, error rate) of the managed network is superior to that of the home network, the UE may prefer to use the managed network.

[0211] In the example, UE (UE 1) can be a subscriber to network (Network A). Network (Network A) can be the home network of UE (UE 1). For example, UE (UE 1) can be associated with a theater, stadium, and / or shopping mall. For example, a user of UE (UE 1) could be the owner of a theater, have tickets for a sports game, and / or be a customer of a shopping mall. Based on this association, the theater's management, the stadium's operator, and / or the shopping mall's owner can allow the UE to use connectivity services provided by the hosting network. Based on the subscription to network (Network A), if the UE is within the coverage area of ​​network (Network A), the UE can use connectivity services provided by that network. Based on authorization to the hosting network, if the UE is within the coverage area of ​​the hosting network, the UE can use connectivity services provided by the hosting network.

[0212] Figure 17 An example implementation is described in which a UE moves from location A to location C via location B. For example, location A may be within the coverage of the serving network, location B may be within the coverage of a first managed network (e.g., managed network 1), and / or location C may be within the coverage of a second managed network (e.g., managed network 2). The coverage of the first managed network may not include location A. The coverage of the serving network may not include location B and / or location B1. The coverage of the first managed network may not include location C. When the UE is within the coverage of the serving network (e.g., location A), the UE can use connectivity services via the serving network. For example, the first managed network may allow the UE to use connectivity services from the first managed network, and / or the second managed network may not allow the UE to use connectivity services from the second managed network.

[0213] In the example, as the UE moves from location A to location B, the UE may need to change its connectivity from the serving network to the first managed network. For this change in connectivity from the serving network to the first managed network, the UE may need to perform measurements on one or more cells of the first managed network, and / or the NG-RAN of the serving network may need the measurement results reported by the UE. Based on these measurements, the UE can determine to select the first managed network, and / or the NG-RAN can determine to hand over the UE to the first managed network.

[0214] In existing technologies, the UE may not know when it is permitted to use one or more managed networks (e.g., a first managed network). In one implementation, the UE may begin searching for one or more cells in locations where one or more managed networks (e.g., the first managed network) are unavailable. For example, the UE may begin searching / measuring / detecting one or more cells of the first managed network at location A. Given that location A is not within the coverage area of ​​the first managed network, the UE may not find any cells of the first managed network, and the UE may consume battery power. In existing technologies, the UE may waste power resources searching for potentially unavailable cells.

[0215] In existing technologies, the UE may not know where it is permitted to use one or more managed networks. In one implementation, after experiencing a connectivity service interruption, the UE may begin searching for one or more cells. For example, when moving along a line from location A to location B, the UE may not begin searching / measuring / detecting cells of the first managed network. For example, when the UE approaches location B1 and / or moves out of the coverage area of ​​the serving network, the UE may lose connectivity to the serving network without preparing for connectivity to the first managed network. This loss of connectivity may degrade the UE's quality of service.

[0216] In existing technology, a UE can attempt to establish connectivity to a managed network that does not allow the UE to connect. For example, at location C, when the UE loses connectivity to the first managed network, the UE can detect that it is within the coverage area of ​​a second managed network. Since no other available network exists, the UE can attempt to establish connectivity with the second managed network. Because the UE is not allowed to obtain connection services from the second managed network, the UE's access attempt to the second managed network may be rejected, and may lead to signaling congestion to the second managed network.

[0217] like Figure 18As depicted, the example embodiments of this disclosure improve system efficiency through signaling enhancements targeting network access information. For example, based on activation information (e.g., time / location conditions) of the network access information, the UE can determine whether / when / where the UE can use the network access information. For example, based on information about one or more networks in the network access information and / or based on activation information, the UE can efficiently search for connectivity to one or more networks and / or select a network to register with. The use of network access information can reduce unnecessary searches for networks (e.g., managed networks), reduce unnecessary measurements for one or more cells, and / or improve the power efficiency of the UE. Through signaling exchange between one or more network nodes and / or the UE, the example embodiments of this disclosure can reduce attempts by the UE to register with managed networks, which are not permitted by the UE. The example embodiments can assist the network in constructing network access information. For example, based on network access assistance information from the AF and / or managed networks, one or more core network nodes can determine information and / or activation information for one or more networks. The example embodiments can assist the NG-RAN in determining when to configure measurements for the UE, when to perform UE handover, and / or to which network to perform handover. The example implementation can support reduced connection interruptions and selection of appropriate networks for host network access.

[0218] In this specification, the home network can be interpreted as the network to which the UE has a subscription. The home network can be a primary network that stores and manages the UE's information, generates the UE's billing / accounting information, and / or publishes security contexts (e.g., USIM, security keys) for the UE. For example, the UE's information may include at least one of the UE's identifier and / or UE's credentials. For example, credentials may include a key value shared by the UE and the home network for UE authentication. For example, the UE's identifier (e.g., telephone number, Integrated Services Digital Network, IMEI, IMSI, SUCI, SUPI, etc.) can be used by one or more networks to identify the UE and / or may be a number assigned to the UE that others can use to contact the UE.

[0219] In the specification, a serving network can be interpreted as a network to which the UE has registered. For example, when the UE registers with a first network, the first network can be the UE's serving network. When the UE registers with a second network, the second network can be the UE's serving network. When the UE deregisters from the first network, the first network may no longer be the UE's serving network. For example, if the UE's serving network is not the UE's home network, the serving network can retrieve the UE's information from the UE's home network.

[0220] In this specification, a managed network can be interpreted as a network that provides connectivity services to UEs that have subscriptions to networks other than the managed network. For example, the managed network of a UE can be a network other than the UE's home network. For example, a first UE can be a subscriber to a first network (e.g., a first PLMN, a first private network, a first non-public network, a first closed network, a first credential holder, etc.), and / or a second UE can be a subscriber to a second network (e.g., a second PLMN, a second private network, a second non-public network (NPN), a second closed network, a second credential holder, a second PLMN integrated NPN (PNI-NPN), a second independent NPN (SNPN), etc.). The first network can provide connectivity services to the second UE. For the second UE, the second network can be the home network and / or the first network can be the managed network. The second network can determine not to provide connectivity services to the first UE. For the first UE, the first network can be the home network and / or the second network can be neither a managed network nor a home network. For the UE, a third party (e.g., neither the first nor the second network) can determine whether the UE can access the managed network (e.g., the first network, the second network). For example, a third party (e.g., a service provider, theater management, shop owner, stadium operator) may allow a second UE to use a hosted network (e.g., the first network) and / or may request the hosted network to provide connectivity services to the second UE. For example, the hosted network (e.g., the first network) may have information about the UE (e.g., the second UE) and / or may pre-authorize the UE's access before the UE can access the hosted network. For example, the hosted network may not be a public network and / or may allow access from UEs with specific restrictions (e.g., business owners, shop customers, theater visitors, etc.).

[0221] In this specification, network access information can be interpreted as information used to select a network (e.g., a hosted network). For example, network access information can be delivered between one or more network nodes, one or more access nodes, and / or UEs. For example, network access information may include a selection list of networks (e.g., a network list), activation information, one or more access technologies for one or more networks, etc. A UE can use network access information to select a network to attempt registration. For example, a UE can select a network for registration. For example, a UE can select a network to search for / detect cells of that network. For example, a UE can select a network based on one or more cells associated with one or more detected cells. For example, based on the activation information of the network access information, a UE can determine when and / or where to use the network access information and / or the network list. Based on the network access information, a UE can trigger a search for one or more cells of one or more networks indicated by the network list. Based on the activation information of the network access information, a UE can switch from using first network access information to using second network access information. For example, network access information may include SOR information (roaming information guidance), a list of preferred network / access technology combinations, a list of allowed networks, security packets, a SoR transparency container, and / or access and mobility subscription data. For example, network access information may include information about one or more networks that the UE can access. For example, information about one or more networks may include information about one or more managed networks.

[0222] In the specification, information about one or more networks may be interpreted as a network list. For example, a network list may include one or more identifiers for one or more networks. For example, an identifier (of one or more identifiers) may indicate a network. For example, an identifier may include at least one of MNC (Mobile Network Code), MCC (Mobile Country Code), NID (Network Identifier), and / or network name.

[0223] In the specification, activation information can be interpreted as one or more conditions under which one or more pieces of information can be applied. For example, one or more pieces of information may include network access information, network access assistance information, network lists, network information, mobility assistance information, etc. For example, one or more conditions may include at least one of time information (e.g., when one or more pieces of information are permitted, when one or more pieces of information are valid, etc.) and / or at least one of location information (e.g., where one or more pieces of information are permitted, where one or more pieces of information are valid, etc.). If one or more conditions are met, one or more pieces of information may be used. If one or more conditions are not met, one or more pieces of information may not be used.

[0224] In this specification, network access assistance information can be interpreted as information used to assist a network node in determining the network access information of a UE. For example, a network node may receive network access assistance information from one or more other network nodes and / or application functions. For example, a network node may request network access assistance information from one or more other network nodes and / or application functions. Based on the network access assistance information, the network node is able to determine and / or construct the network access information.

[0225] In this specification, mobility assistance information can be interpreted as information indicating which networks the UE can use and / or to which the access node can hand over the UE across areas. For example, an access node (e.g., NG-RAN) can use mobility assistance information to determine which networks it can establish measurement configurations for, which networks the access node can hand over the UE to, and / or which networks the UE can access. For example, mobility assistance information may include information on when and / or where it can be used. This "when and / or where" information can be activation information. Based on this "when and / or where" information, the access node can determine when to use mobility assistance information and / or in which area it can use it. For example, mobility assistance information may include information on which networks the UE can use. For example, one or more networks may include one or more managed networks that the UE is allowed to use / access.

[0226] In this specification, the term NG-RAN can be interpreted as a base station, which may include at least one of gNB, eNB, ng-eNB, NodeB, access node, access point, N3IWF, relay node, base station central unit (e.g., gNB-CU), base station distributed unit (e.g., gNB-DU), etc.

[0227] In this specification, the term "core network node" can be interpreted as "core network equipment," which may include at least one of AMF, SMF, NSSF, UPF, NRF, UDM, PCF, SoR-AF, AF, etc. The term "core network" can also be interpreted as "core network node." In this specification, the term "access node" can be interpreted as "base station," which may include NG-RAN, etc. In this specification, the term "network node" can be interpreted as "core network node," "access node," "UE," etc.

[0228] In this specification, AF (Application Function) can be interpreted as a network node, an application, a third party, and / or an application server. For example, an AF can send requests to a network node and / or receive responses from a network node. For example, a first network node in a first network can send requests to a second network node in a second network and / or receive requests from a second network node in a second network. For example, a second network can consider a first network node as an AF.

[0229] In this specification, the term SoR-AF can be interpreted as core network device and / or AF. SoR-AF may include at least one of mobility management functions, access management functions, network list management functions, network access information management functions, and activation information management functions. SoR-AF can generate activation information, network access information, mobility assistance information, etc.

[0230] Figure 19 An example implementation of this disclosure is depicted. In the example, the UE may indicate whether it supports processing associated with network access information. For example, the UE's indication may assist one or more network nodes in determining whether to deliver network access information to the UE.

[0231] In the example, the UE can send NAS messages (e.g., UL NAS messages, registration request messages, etc.) to network nodes (e.g., AMF, PCF, UDM, SoR-AF, etc.). NAS messages can include indications that the UE supports eSOR (enhanced roaming guidance) capabilities. eSOR capabilities can instruct the UE to support processing network access information, sending network access information requests, receiving network access information, processing activation information, etc. For example, eSOR capabilities can help network nodes determine whether network access information needs to be delivered to the UE.

[0232] In the example, a first network node (e.g., AMF) can receive a NAS message sent by the UE. Based on the NAS message including eSOR capabilities, the first network node can send a policy request message (e.g., Npcf_AMPolicyControl_Create request, Npcf_AMPolicyControl_Update request) including eSOR capabilities to a second network node (e.g., PCF). Based on the eSOR capabilities, the second network node can determine whether to provide the UE with network access information services. For example, the network access information service could be information that provides network access information to the UE and / or handles / processes network access information. For example, if the UE has subscribed to the network access information service, the second network node can determine whether to provide the UE with the network access information service. For example, if the second network node supports the network access information service, the second network node can determine whether to provide the UE with the network access information service. For the received policy request message, the second network node can send a policy response message (e.g., Npcf_AMPolicyControl_Create response, Npcf_AMPolicyControl_Update response) to the first network node. For example, the policy response message may include an indication that network access information is supported. The indication supporting network access information can indicate whether a network node (e.g., a second network node) can provide network access information services to the UE, whether a network node can generate network access information for the UE, etc. The first network node can receive policy responses sent by the second network node.

[0233] In one example, for a NAS message received from a UE, the first network may send a UDM service request (e.g., Nudm_SDM_Get request, etc.) message to a third network node (e.g., UDM, UDR). The UDM service request message may include eSOR capability and / or an eSOR support indicator. The eSOR support indicator can indicate to the receiving network node (e.g., the third network node) whether the sending network node (e.g., the first network node) supports the service of providing network access information. For example, if the third network node does not receive the eSOR support indicator, it may assume that the first network node may not provide the network access information service. Based on the eSOR capability and / or the eSOR support indicator, the third network node can determine whether to provide the network access information service to the UE. For example, if the UE has subscribed to the network access information service, the third network node can determine whether to provide the network access information service to the UE. For example, if the third network node supports the network access information service, it can determine whether to provide the network access information service to the UE. Based on determining the service for providing network access information to the UE, the third network node can send a SoR service request (e.g., Nsoraf_SoR_Get request) message to the fourth network node (e.g., SoR-AF). The SoR service request message may include (e.g., eSOR capability and / or eSOR support indicator from the first network or the third network). Based on the eSOR capability and / or eSOR support indicator, the fourth network node can determine whether to provide the network access information service to the UE. For example, if the UE has subscribed to network access information, the fourth network node can determine whether to provide the network access information service to the UE. For example, if the fourth network node supports providing network access information, the fourth network node can determine whether to provide the network access information service to the UE. Upon receiving the SoR service request message, the fourth network node can send a SoR service response request (e.g., Nsoraf_SoR_Get response) message to the third network node. For example, the SoR service response message may include information about whether the fourth network node provides the network access information service. The third network node can receive the SoR service response message from the fourth network node. Upon receiving a UDM service request message and / or a SoR-based service response message, the third network node may send a UDM service response message (e.g., a Nudm_SDM_Get response) to the first network node. For example, the UDM service response message may include information about whether the third and / or fourth network nodes provide network access information services. The first network node may receive the UDM service response message from the third network node.

[0234] In the example, in response to a NAS message received from the UE, the first network node may send a DL NAS message to the UE (e.g., a registration acceptance message, a UE configuration update message). The DL NAS message may include information about whether the network supports eSOR. This information can indicate whether the network can provide network access information services to the UE and / or whether the network can provide network access information.

[0235] In the example, the UE can receive a DL NAS message. Based on the DL NAS message, the UE can determine whether the network supports eSOR. For example, if the network supports eSOR, the UE can send a message including a network access information request. If the network does not support eSOR, the UE can choose not to send a message including a network access information request.

[0236] In the example, the network node can send network access information to the UE based on whether the UE supports eSOR capability. For example, if the UE transmits eSOR capability to the network, the network can send network access information to the UE. Conversely, if the UE does not transmit eSOR capability to the network, the network may not send network access information to the UE. If the UE supports eSOR capability and / or if the network provides network access information services, then [the following applies]. Figures 20 to 34 The example shown is shown in the image.

[0237] Figure 20 An example implementation of this disclosure is depicted. In the example, the application function can provide network access assistance information to network nodes.

[0238] In the example, the AF (e.g., an application, an entity with a protocol to use the network, an entity managing credentials for network access, an entity managing the network, a network node hosting the network, etc.) can determine whether the UE is permitted to use connectivity services from the network (e.g., the hosting network). For example, a user of the UE can establish a contract with the AF to provide connectivity services. Based on the determination to provide connectivity services to the UE, the AF can send a NEF service request message to a network node (e.g., NEF, SoR-AF) to deliver auxiliary information associated with directing the UE to the network. For example, to determine the network node and / or the network associated with the network node, the AF can collect information from the UE about networks the UE may have subscribed to, information about the UE, information about the UE's home network, information about the UE's serving network, etc. The network node may belong to the UE's home network and / or the UE's serving network.

[0239] In the example, the AF can send a NEF service request message (e.g., a Network Access Assistance Information Provision Request, Nnef_ParameterProvision_Create and / or Nnef_ServiceParameter_Create, Nnef_ApplyPolicy_Create, etc.) to a network node (e.g., the NEF). For example, the NEF service request message may include network access assistance information. Network access assistance information may include at least one of the following:

[0240] -UE list information: UE list information can indicate one or more identifiers of one or more UEs to which the NEF service request message is applied.

[0241] - Network list information: Network list information can indicate one or more pieces of information about one or more networks. One or more networks can provide connectivity services to one or more UEs indicated by the UE list information. Network list information can include a list of networks.

[0242] - Event Information: Event information can indicate the time (when), location (where), and / or validity conditions of network access assistance information. For example, one or more networks indicated by the network list information can provide connectivity services to one or more UEs indicated by the UE list information during a time period indicated by the time information. The time period can include a start time, an end time, and / or a duration. For example, location information can indicate an area, one or more geographic coordinates, one or more tracking areas, one or more cells, etc. When one or more UEs are located at the location indicated by the location information, one or more networks indicated by the network list information can provide connectivity services to one or more UEs indicated by the UE list information. For example, validity conditions can indicate one or more conditions that indicate when the information delivered by the network access assistance information can be valid and / or applicable.

[0243] In the example, a network node (e.g., NEF) can receive NEF service request messages. In response to a received NEF service request message, the network node (e.g., NEF) can perform an authorization check to determine whether an AF is authorized to send NEF service request messages. For example, the network node (e.g., NEF) can use the AF's identifier to check whether the AF is permitted to send NEF service request messages.

[0244] In the example, based on a successful authorization check, a network node (e.g., NEF) can send a UDM service request message (e.g., parameter provision request, Nudm_ParameterProvision_Create request, Nudm_ServiceSpecificAuthorization_Create request, etc.) to a data management node (e.g., UDM, UDR). The UDM service request message may include network access assistance information.

[0245] In the example, the data management node can receive UDM service requests from a network node (e.g., NEF). For a UDM service request received from a network node (e.g., NEF), the data management node can perform subscription checks and / or capability checks. For example, the UE may not have a subscription to the Network Access Information service. Based on the UE's lack of a subscription to the Network Access Information service, the data management node can reject the UDM service request message from the network node (e.g., NEF). For example, the UE may have a subscription to the Network Access Information service. Based on the UE's subscription to the Network Access Information service, the data management node can accept the UDM service request message from the network node (e.g., NEF). For example, the UE may not have the capability for the Network Access Information service (e.g., eSOR capability). Based on the UE's lack of this capability, the data management node can reject the UDM service request from the network node (e.g., NEF). For example, the UE may have this capability (e.g., eSOR capability). Based on the UE's capability, the data management node can accept the UDM service request message from the network node (e.g., NEF).

[0246] In response to a received UDM service request message, the data management node can send a SoR-AF service request message (e.g., an Nsoraf_SoR_Provision request). For example, the data management node can send a SoR-AF service request to request the SoR-AF to process network access assistance information and / or generate updated network access information. The SoR-AF service request message may include network access assistance information.

[0247] In the example, the SoR-AF can store network access assistance information received from the SoR-AF service request message and / or one or more pieces of information that can process the SoR-AF service request message. For example, the SoR-AF can generate one or more network access information for one or more UEs indicated by the UE list information of the network access assistance information. For example, the one or more UEs indicated by the UE list information may include a first UE and / or a second UE. The first UE may have a first capability (e.g., a first set of supported radio access technologies, a first set of supported frequency bands, etc.) and / or may subscribe to a first set of services (e.g., eMBB service, gold-level service, etc.). The second UE may have a second capability (e.g., a second set of supported radio access technologies, a second set of supported frequency bands, etc.) and / or may subscribe to the first set of services (e.g., IoT service, silver-level service, etc.). For example, based on the first capability and / or the first set of services, the SoR-AF can generate first network access information for the first UE. For example, based on the second capability and / or the second set of services, the SoR-AF can generate second network access information for the second UE.

[0248] In the example, based on the received SoR-AF service request message, SoR-AF can send a SoR-AF service response message (e.g., an Nsoraf_SoR_Provision response) to the data management node. For example, the SoR-AF service response message can indicate the processing result of the SoR-AF service request message (e.g., success, failure, etc.).

[0249] In the example, the data management node can receive SoR-AF service response messages from SoR-AF. In response to the received SoR-AF service response messages and / or based on the received UDM service request messages, the data management node can send UDM service responses (e.g., parameter provision responses, Nudm_ParameterProvision_Create responses, Nudm_ServiceSpecificAuthorization_Create responses, etc.) to the network node (e.g., NEF). For example, the UDM service response message can indicate the processing result of the UDM service request message (e.g., success, failure, etc.).

[0250] In the example, a network node (e.g., NEF) can receive a UDM service response message from a data management node. In response to the received UDM service response message and / or based on the received NEF service request message, the NEF can send a NEF service response to the AF (e.g., a Network Access Assistance Information Provision response, an Nnef_ParameterProvision_Create response, and / or an Nnef_ServiceParameter_Create response, an Nnef_ApplyPolicy_Create response, etc.). For example, the NEF service response message can indicate the processing result of the NEF service request message (e.g., success, failure, etc.). This result can indicate to the AF whether the AF's request has been accepted / processed.

[0251] Figure 21 An example implementation of this disclosure is depicted. In the example, the application function can provide network access assistance information to network nodes.

[0252] In the example, SoR-AF can register with the NRF to provide one or more SoR-AF services to one or more network nodes. To register, SoR-AF can send a first NRF service request message (e.g., an Nnrf_NFManagement_NFRegister request). For example, the first NRF service request message may include at least one of the following: network node type, instance ID, IP address, supported services, etc. For example, the network node type may indicate the SoR-AF. For example, supported services may indicate one or more services supported by the SoR-AF. For example, the services supported by the SoR-AF may include processing of network access information and / or processing of network access assistance information. The NRF can receive the first NRF service request message and / or can store the information delivered by the first NRF service request message. In response to the received first NRF service request message, the NRF can send a first NRF service response message to the SoR-AF indicating successful registration. The SoR-AF can receive the first NRF service response message.

[0253] In the example, the AF can determine to provide connectivity services to one or more UEs. For example, Figure 20 The examples depicted can be applied. The AF can send NEF service request messages to the NEF. For example, a NEF service request message may include network access assistance information. The NEF can perform authorization checks on received NEF service request messages.

[0254] In the example, based on a successful authorization check, the NEF can send a second NRF service request (e.g., an Nnrf_NFDiscovery request) message to the NRF. For example, the NEF can send the second NRF service request to determine a SoR-AF that may be associated with the NEF service request message. The second NRF service request may include at least one of a target service name and / or a network node type. For example, the network node type may indicate a SoR-AF. The NRF can receive the second NRF service request message from the NEF. Based on the received second NRF service request message and / or based on stored SoR-AF information, the NRF can determine a SoR-AF that matches the information in the second NRF request message. Based on the determined SoR-AF, the NRF can send a second NRF service response (e.g., an Nnrf_NFDiscovery response) message to the NEF. For example, the second NRF service response message may include at least one of the SoR-AF's IP address, the SoR-AF's identifier, etc. In the example, if the NEF has information about the SoR-AF, it may not need to send a second NRF service request based on its local configuration and / or previously received information. Based on the SoR-AF information, the NEF can determine which SoR-AF the service request was sent to.

[0255] In the example, in response to a NEF service request and / or information based on SoR-AF, NEF may send a SoR-AF service request message (e.g., Nsoraf_SoR_Provision request, etc.) to SoR-AF. The SoR-AF service request message may include network access assistance information. SoR-AF may receive SoR-AF service request messages.

[0256] In the example, SoR-AF can perform subscription checks and / or capability checks on the UE (indicated by the UE list information). For example, the UE may not have a subscription to the Network Access Information service. Based on the UE's lack of a subscription to the Network Access Information service, SoR-AF can reject a SoR-AF service request message from the NEF. For example, the UE may have a subscription to the Network Access Information service. Based on the UE's subscription to the Network Access Information service, SoR-AF can accept a SoR-AF service request from the NEF. For example, the UE may not have the capability for the Network Access Information service (e.g., eSOR capability). Based on the UE's lack of the capability for the Network Access Information service, SoR-AF can reject a SoR-AF service request from the NEF. For example, the UE may have the capability for the Network Access Information service. Based on the UE's capability for the Network Access Information service, SoR-AF can accept a SoR-AF request from the NEF. In one example, SoR-AF can send a UDM service request to the UDM. In response, SoR-AF can receive the UE's subscription information and / or capability information from the UDM.

[0257] In the example, SoR-AF may store network access assistance information and / or one or more pieces of information that can process the received SoR-AF service request message.

[0258] For example, SoR-AF can generate one or more network access information for one or more UEs indicated by the UE list information of the network access assistance information. For example, SoR-AF can process one or more pieces of information in a SoR-AF service request message for one or more UEs, which may have the ability to subscribe to services related to the network access information and / or have the capability to provide services related to the network access information. For example, the one or more UEs indicated by the UE list information may include a first UE and / or a second UE. The first UE may have a first capability (e.g., a first set of supported radio access technologies, a first set of supported frequency bands, etc.) and / or may be able to subscribe to a first set of services (e.g., eMBB service, Gold service, etc.). The second UE may have a second capability (e.g., a second set of supported radio access technologies, a second set of supported frequency bands, etc.) and / or may be able to subscribe to the first set of services (e.g., IoT service, Silver service, etc.). For example, based on the first capability and / or the first set of services, SoR-AF can generate first network access information for the first UE. For example, based on the second capability and / or the second set of services, SoR-AF can generate second network access information for the second UE.

[0259] In the example, in response to a received SoR-AF service request message, SoR-AF can send a SoR-AF service response message (e.g., an Nsoraf_SoR_Provision response, etc.) to NEF. In the example, NEF can receive a SoR-AF service response message from SoR-AF. In response to a received SoR-AF service response message and / or based on a received NEF service request message, NEF can send a NEF service response to AF (e.g., a Network Access Assistance Information Provision response, an Nnef_ParameterProvision_Create response, and / or an Nnef_ServiceParameter_Create response, an Nnef_ApplyPolicy_Create response, etc.). For example, the NEF service response message can indicate the processing result of the NEF service request message (e.g., success, failure, etc.). This result can indicate to AF whether the request was accepted / processed.

[0260] Figure 22 An example implementation of this disclosure is depicted. In the example, the UE can request network access information to be provided to the network node.

[0261] In the example, the UE may send a first NAS message (e.g., a UL NAS transport message) to the AMF. In one example, the UE may send a first NAS message if it requests network access information and / or if it does not have network access information. In another example, the UE may request network access information if it obtains information about a network (e.g., a managed network) and / or if it needs to access the network. For example, the first NAS message may include at least one of the UE's identifier and / or the network access information request. The network access information request may indicate that the UE needs network access information and / or that the UE does not have network access information. For example, the network access information request may include information about the network (e.g., a managed network) (e.g., address, identifier, name, etc.), network authorization information, the address of the AF associated with access to the network, etc. The AF and / or the network may use the authorization information to authenticate the UE's request. One or more networks may use the information in the network access information request to determine whether to provide network access information to the UE and / or collect network access assistance information.

[0262] In the example, the AMF can receive a first NAS message from the UE. For example, based on the network access information request in the first NAS message, the AMF can determine to provide network access information to the UE. In the example, based on the received first NAS message, the AMF can send a UDM service request (e.g., Nudm_SDM_Info request) message to the data management node (e.g., UDM, UDR). For example, the UDM service request message may include at least one of the UE's identifier and / or the network access information request. Based on the UDM service request message, the data management node can determine that network access information needs to be provided to the UE. Based on this determination, the data management node can send a SoR-AF service request message (e.g., Nsoraf_SoR_Get request, etc.) to the SoR-AF. For example, the SoR-AF service request message may include at least one of the UE's identifier, the network access information request, and / or the network access information stored at the data management node. For example, based on the network access information stored at the data management node, the SoR-AF can determine whether to update the UE's network access information. For example, based on the network access information request, the SoR-AF can determine to generate the UE's network access information.

[0263] In the example, based on a network access information request, the SoR-AF can determine to send a message to the network (e.g., a managed network) or the AF to check whether the UE is authorized to receive connectivity services from the network (e.g., a managed network). For example, the SoR-AF can send a request for network access assistance information to the network (e.g., a managed network) or the AF. For example, based on the request sent to the network or the AF, the SoR-AF can receive network access assistance information and / or authorization information from the AF or the network (e.g., a managed network). For example, the authorization information can indicate whether the UE is authorized to use the network (e.g., a managed network). The SoR-AF can receive network access assistance information, such as... Figure 19 , Figure 20 As shown in the example.

[0264] In the example, return to Figure 22 Based on network access assistance information and / or based on network access information requests, the SoR-AF can determine the UE's network access information. The SoR-AF can send the network access information to the UE. The UE's network access information can be delivered from the SoR-AF to the UE via the data management node and / or AMF. The UE can receive the network access information and / or can store the network access information.

[0265] Figure 23 An example implementation of this disclosure is depicted. In the example, the UE can request network access information to be provided to the network node.

[0266] In the example, the UE may send a first NAS message (e.g., a UL NAS transport message) to the AMF. For example, the UE may send the first NAS message if it requests network access information and / or if it does not have network access information. For example, the UE may request network access information if it obtains information about a network (e.g., a managed network), if it receives information from a network / AF, if it needs to access the network, and / or if it is authorized to access the network. For example, the first NAS message may include at least one of the UE's identifier and / or the network access information request. The network access information request may indicate that the UE needs network access information, does not have network access information, and / or needs a network access policy. For example, the network access information request message may include information about the network (e.g., a managed network) (e.g., address, identifier), the network's authorization information, the AF's address, the identifier of the network access policy, etc. The AF and / or the network may use the authorization information to authenticate the UE. The identifier of the network access policy may indicate the network access information the UE can have and / or the network access policy the UE can have.

[0267] In the example, the AMF can receive a first NAS message from the UE. Based on the received first NAS message, the AMF can determine whether it needs to provide network access information and / or network access policy to the UE. For example, based on the network access information request in the first NAS message, the AMF can determine a policy for requesting network access from the PCF used by the UE.

[0268] In the example, based on the received first NAS message, the AMF can send a PCF service request message (e.g., Npcf_AMPolicyControl_Create request, Npcf_AMPolicyControl_Update request) to the PCF. For example, the PCF service request message may include at least a network access information request and / or an indication that a network access policy is required. Based on the PCF service request message, the PCF can determine that network access information needs to be provided to the UE. Based on this determination, the PCF can send a SoR-AF service request message (e.g., Nsoraf_SoR_Get request, etc.) to the SoR-AF. For example, the SoR-AF service request message may include at least one of the UE's identifier and / or the network access information request. For example, based on the network access information request, the SoR-AF can determine the UE's network access information.

[0269] In the example, based on the received SoR-AF service request, the SoR-AF can send a message to the network (e.g., a managed network) or the AF to check whether the UE is authorized to receive connectivity services from the network (e.g., a managed network). For example, based on the request sent to the network or AF, the SoR-AF can receive network access assistance information and / or authorization information from the AF or the network (e.g., a managed network). For example, the authorization information can indicate whether the UE is authorized to use the network (e.g., a managed network). The SoR-AF can receive network access assistance information, such as... Figure 19 , Figure 20 As shown in the example.

[0270] In the example, return to Figure 23 Based on network access assistance information, SoR-AF can determine network access policy assistance information. This network access policy assistance information may include information indicating one or more networks that the UE is allowed to select, information indicating one or more networks that are prioritized, information indicating one or more networks to which the UE needs to be guided, and / or network access information. In response to a SoR-AF service request received from the PCF, SoR-AF can send a SoR-AF service response (e.g., an Nsoraf_SoR_Get response) message to the PCF. The SoR-AF service response message may include network access policy assistance information. The PCF can receive the SoR-AF service response message. Based on the network access policy assistance information in the SoR-AF service response message, the PCF can construct the UE's network access information. In response to a received PCF service request, the PCF can send a PCF service response (e.g., an Npcf_AMPolicyControl_Create response, an Npcf_AMPolicyControl_Update response, or a policy response) to the AMF. The PCF service response message may include network access information. The AMF can receive the PCF service response message from the PCF. Based on the PCF service response message, the AMF can send a second NAS message (e.g., a DL NAS transmission message) to the UE. The second NAS message may include network access information. The UE can receive the second NAS message sent by the AMF and / or store the network access information from the second NAS message.

[0271] Figure 24 An example implementation of this disclosure is depicted. In the example, one or more network nodes can deliver network access information. In the example, the UE can use the delivered network access information.

[0272] In the example, SoR-AF can construct, process, and / or generate network access information. For example... Figure 20 , Figure 21 , Figure 22As shown in the example, SoR-AF can generate network access information based on network access assistance information.

[0273] In the example, the SoR-AF can determine to deliver network access information to the UE. For example, if the AF and / or the UE requests the delivery of network access information, if the SoR-AF receives / processes network access assistance information, and / or if the conditions (e.g., time and / or location) indicated by the event information of the network assistance information are met, the SoR-AF can determine to deliver network access information to the UE. For example, if the event information indicates a time (e.g., 5 PM), the SoR-AF can determine that the delivery of network access information is triggered, for example, at approximately a certain time (e.g., 1:00 PM). For example, if the event information indicates a location (e.g., city A), the SoR-AF can determine to trigger the delivery of network access information when the UE approaches the boundary of that location (e.g., 10 miles from city A). For example, the SoR-AF can determine to trigger the delivery of network access information with a guard time.

[0274] In the example, SoR-AF can determine one or more UEs to which network access information is sent. For instance, based on one or more UEs indicated by UE list information, SoR-AF can determine to send network access information to these one or more UEs.

[0275] In the example, network access information may include at least one of the following:

[0276] - Network Selection List (Network List): The network selection list can indicate one or more pieces of information (e.g., one or more identifiers) for one or more networks. The network selection list can include one or more entries. Entries (among the one or more entries) can indicate network identifiers. Network identifiers can include at least one of MNC (Mobile Network Code), MCC (Mobile Country Code), NID (Network Identifier), and / or network name. In one example, one or more entries in the network selection list can be listed in priority order. For example, the first entry in the network selection list (e.g., the first network) can have a higher priority than the second entry in the selection list (e.g., the second network). In one example, the entries (one or more entries) in the network selection list can include network priority information. For example, the third entry (e.g., the third network) can include information with a priority of 1. For example, the fourth entry (e.g., the fourth network) can include information with a priority of 2. Based on the priority information, the UE can determine the priority among the one or more entries. For example, the UE can determine that the third network has a higher priority than the fourth network. Based on the determination of network priorities, the UE can search for one or more cells of one or more networks, starting with one or more cells of a higher priority entry. For example, the UE can search for one or more cells of the first network before searching for one or more cells of the second network. If the UE discovers and / or selects a cell in a network, and / or successfully registers with a network, the UE may not search for / discover / select cells in a network (with a lower priority than the registered network).

[0277] - Access Technology Information: Access technology information can be a network indicator (in one or more networks) of one or more access technologies that the UE can use to access the network. In order to search for one or more cells in a network, the UE can use one or more access technologies indicated by the access technology information.

[0278] - Activation Information: Activation information may include information indicating when and / or where network access information is used. Activation information may indicate one or more conditions (criteria) for determining whether network access information is applicable. For example, activation information may include a valid time (e.g., time information). Valid time may include at least one of a start time, an end time, and a duration. Valid time may indicate when network access information can be used, when the UE needs to begin using network access information associated with the valid time (e.g., start time), when the UE needs to stop using network access information (e.g., end time), and / or how long the UE can use network access information (e.g., duration). For example, activation information may include a valid location (e.g., location information). Valid location may include at least one of information about one or more cells, information about one or more geographic coordinates, information about one or more tracking areas, etc. Valid location may indicate where the UE can use network access information and / or where the UE can not use network access information.

[0279] In the example, the SoR-AF can send a first UDM service request message (e.g., a Nudm_Parameter_Provision request) to the UDM. The UDM can receive the first UDM service request message from the SoR-AF. For example, to receive the first UDM service request, the UDM can register its address with the SoR-AF and / or request to be notified when the SoR-AF generates / updates network access information. The first UDM service request message may include network access information and / or UE information (e.g., an identifier). The UE information may indicate the UE to which the network access information is delivered.

[0280] In the example, the UDM can store the received network access information. Based on the network access information, the UDM can send a second UDM service request (e.g., a Nudm_SDM_Notification request) message to the AMF associated with the UE. For example, to receive the second UDM service request, the AMF can register its address with the UDM, and / or the UDM can store the AMF's address. Based on the registered address, the UDM can send the second UDM service request to the AMF. For example, the second UDM service request message may include network access information and / or an indication of whether acknowledgment is required. The indication of whether acknowledgment is required can indicate whether the UE needs to send an acknowledgment of successful security check when it receives the network access information. For example, by receiving an acknowledgment of successful security check, the UDM can determine whether the network access information sent by the UDM has been modified by a network node between the UDM and the UE. For example, if a network node between the UDM and the UE modifies one or more pieces of information in the network access information sent by the UDM, the UE may fail to perform the security check.

[0281] In the example, the AMF can receive a second UDM service request message sent by the UDM. Based on the second UDM service request message, the AMF can send a DL NAS message to the UE (e.g., DL NAS transmission, registration acceptance, UE configuration update command). The DLNAS message may include network access information (e.g., second network access information). In the example, the UE can receive the DL NAS message and / or the UE can store the network access information of the DL NAS message. For example, the network access information may also include an indication of whether acknowledgment is required. If the DL NAS message includes an indication of whether acknowledgment is required, the UE can send a ULNAS message to the AMF (e.g., UL NAS transmission, UE configuration update complete). For example, the UL NAS message may include a SoR transparent container containing UE acknowledgment. If the UE successfully checks the security of the information in the DL NAS message, the UE may include the UE acknowledgment in the SoR transparent container.

[0282] The AMF can receive UL NAS messages. Based on the UL NAS message including the SoR transparent container, the AMF can send a third UDM service request message (e.g., Nudm_SDM_Info request) to the UDM to deliver the SoR transparent container. The third UDM service request message may include the SoR transparent container. Based on the SoR transparent container, the UDM can verify that the UE has provided UE acknowledgment. If the UDM successfully verifies that the UE has provided UE acknowledgment, the UDM can send a SoR-AF service request message (e.g., Nsoraf_SoR_Info request) to the SoR-AF to notify the SoR-AF of the successful delivery of network access information (e.g., a list of preferred network / access technology combinations, a network list). The SoR-AF service request may include the UE's identifier and / or an indication of the successful delivery of network service information. Based on the indication of successful delivery, the SoR-AF can determine that the network access information has been successfully delivered to the UE.

[0283] In the example, based on one or more pieces of information in the received network access information, the UE can determine when and / or where to use the received network access information. For example, the UE can determine whether it needs to use the received network access information. For example, the network access information may include activation information. Activation information may include valid time, valid location, valid criteria, etc. For example, valid time (e.g., 3:00 PM, from 9:00 AM to 1:00 PM, Tuesday, weekday, etc.) can indicate when the UE applies the network access information. For example, if the valid time indicates a specific time (e.g., 2:00 PM), and that time is a first time (e.g., 1:59 PM), then the UE can determine that it does not apply the network access information. For example, if the valid time indicates a specific time (e.g., from 3:00 PM to 5:00 PM), and that time is a second time (e.g., 3:00 PM), then the UE can determine that it applies the network access information. For example, a valid location (e.g., at TAC=1, GPS coordinates (30.0N, 125.0E)) can indicate where the UE applies network access information. For example, if the valid location indicates a specific location (e.g., TAC=2, 3, 5), and the cell associated with the UE indicates a first location (e.g., TAC=4), then the UE can determine that it does not apply network access information. For example, if the valid location indicates a specific location (e.g., GPS coordinates (from 25.0N to 25.1N, from 30.0E to 30.1E)), and the UE's location is a second location (e.g., GPS coordinates (25.05N, 30.05E)), then the UE can determine that it applies network access information (e.g., second network access information).

[0284] In the example, based on determining the network access information applied by the UE, the UE can apply network access information. For example, the UE may no longer use previous network access information and / or the UE may begin using network access information applied with associated activation information. For example, the UE may use first network access information before receiving network access information (e.g., second network access information). For example, the second network information may include activation information and / or the first network information may not include activation information. For example, the UE may use first network access information when the conditions of the activation information of the second network access information (e.g., valid time, valid location, valid conditions) are not met. For example, the UE may use second network access information when the conditions of the activation information of the second network access information (e.g., valid time, valid location, valid conditions) are met. For example, the UE may not use network access information if the activation information of the received network access information is not met. For example, the UE may use network access information if the activation information of the received network access information is met. For example, based on determining the network access information used by the UE, the UE may begin using the network access information (e.g., the second network access information) and / or may trigger a change from using the first network access information to using the second network access information.

[0285] In the example, based on one or more pieces of information from the network access information, the UE can trigger a search / discovery of a network associated with the network access information, and / or can change its registration from one network to another based on the search / discovery results. For example, if the UE discovers one or more cells of a network based on the network access information, the UE selects that network and / or can send a registration request message to that network. For example, the selected network could be a managed network.

[0286] Figure 25 An example implementation of this disclosure is depicted. In the example, one or more network nodes can deliver network access information. In the example, the UE can use the delivered network access information.

[0287] In the example, SoR-AF can construct, process, and / or generate network access information. For example... Figure 20 , Figure 21 , Figure 22 As shown in the example, SoR-AF can generate network access information based on network access assistance information.

[0288] In the example, return to Figure 25The SoR-AF can determine to deliver network access information to the UE. For example, if the AF and / or the UE requests the delivery of network access information, if the SoR-AF receives / processes network access assistance information, and / or if conditions indicated by event information based on the network assistance information (e.g., time and / or location) are met, the SoR-AF can determine to deliver network access information to the UE. For example, if the event information indicates a time (e.g., 2 PM), the SoR-AF can determine that the delivery of network access information is triggered around that time (e.g., 1:59 PM, 2:00 PM). For example, if the event information indicates a location (e.g., city A), the SoR-AF can determine that the delivery of network access information is triggered when the UE approaches the boundary of that location (e.g., 0.3 miles from the boundary of city A). For example, if the SoR-AF determines that the UE needs to use the network access information when the UE receives it, the SoR-AF may not send network access information that does not include activation information.

[0289] In the example, SoR-AF can identify one or more UEs to which network access information needs to be sent. For example, based on one or more UEs indicated by UE list information, SoR-AF can determine to send network access information to these one or more UEs. For example, if the time is close to the start of an event, and / or if the location of the UE is close to the location of the event, SoR-AF can determine to send network access information.

[0290] In the example, network access information may include at least one of the following:

[0291] - Network Selection List (Network List): The network selection list can indicate one or more pieces of information about one or more networks. For a network (among one or more networks), network access information may or may not include access technology information. The network selection list can include one or more entries. Entries in one or more entries can indicate network identifiers. Network identifiers can include at least one of MNC (Mobile Network Code), MCC (Mobile Country Code), NID (Network Identifier), and / or network name. One or more entries in the network selection list can be listed in priority order. For example, the first entry in the network selection list (e.g., the first network) can have a higher priority than the second entry in the selection list (e.g., the second network). For example, entries in the network selection list can include network priority information. For example, the third entry (e.g., the third network) can include information with a priority of 1. For example, the fourth entry (e.g., the fourth network) can include information with a priority of 2. Based on priority, the UE can determine the priority between entries. For example, the UE can determine that the third network has a higher priority than the fourth network. Based on the determination of priority, the UE can search for one or more cells of one or more networks, starting with higher priority entries. For example, the UE can search for one or more cells of the first network before searching for one or more cells of the second network. If the UE discovers and / or selects a cell in a network (with higher priority) and / or successfully registers to a network (with higher priority), the UE may not search for / discover / select a cell in a network (with lower priority).

[0292] - Access technology information: Access technology information can indicate to the network one or more access technologies that the UE can use in that network. In order to search for one or more cells in the network, the UE can use one or more access technologies indicated by the access technology information.

[0293] In the example, the SoR-AF can send a first UDM service request message (e.g., a Nudm_Parameter_Provision request) to the UDM. The UDM can receive the first UDM service request message from the SoR-AF. The first UDM service request message may include network access information and / or the UE's identifier. The network access information may not include activation information. The UE's identifier may indicate the UE to which the network access information was delivered.

[0294] In the example, the AMF can receive a second UDM service request message sent by the UDM. Based on the second UDM service request message, the AMF can send a DL NAS message to the UE (e.g., DL NAS transmission, registration acceptance, UE configuration update command). The DLNAS message may include network access information. For example, the network access information may also include an indication of whether acknowledgment is required. If the DL NAS message includes an indication of whether acknowledgment is required, the UE can send a UL NAS message to the AMF (e.g., UL NAS transmission, UE configuration update complete). For example, the UL NAS message may include a SoR transparent container containing UE acknowledgment. The UE can receive the DL NAS message. The UE can perform a security check on the DL NAS message. If the UE successfully checks the security of the information in the DL NAS message (e.g., the SoR transparent container), the UE can include the UE acknowledgment in the SoR transparent container. The UE can send a UL NAS message including the SoR transparent container to the AMF.

[0295] In the example, based on received network access information, the UE can use the received network access information and / or the UE can apply the network access information. For example, if the received network access information does not include activation information, the UE can begin using the received network access information and / or the UE can apply the network access information. For example, based on received network access information, the UE can stop using previous network access information. Based on the network access information, the UE can trigger a search / discovery of the network associated with the network access information, and / or the UE can change its registration from one network to another based on the search results. For example, if the UE discovers one or more cells of a network based on the network access information, the UE can select that network and / or can send a registration request message to that network. For example, the selected network could be a managed network.

[0296] Figure 26 An example implementation of this disclosure is depicted. In the example, the UE can use the delivered network access information.

[0297] For example, the UE can use first network access information. Based on the first network access information, the UE can select a network (e.g., a first network) and / or register with that network. The UE can receive network access information (second network access information). The UE can receive network access information (second network access information), such as... Figure 20 , Figure 21 , Figure 22 , Figure 24 As shown in the example. The second network access information may include activation information.

[0298] In the example, return to Figure 26Based on one or more pieces of information in the second network access information, the UE can determine when and / or where to use the second network access information. For example, the UE can determine whether it needs to use the second network access information. For example, the second network access information may include activation information. Activation information may include at least one of valid time, valid location, valid criteria, etc. For example, valid time (e.g., at 3:00 PM, from 9:00 AM to 1:00 PM, Tuesday, weekday, etc.) can indicate when the UE applies the second network access information. For example, if the valid time indicates a specific time (e.g., at 2:00 PM), and if that time is a first time (e.g., 1:59 PM), the UE can determine that it does not apply the second network access information. For example, if the valid time indicates a specific time (e.g., from 3:00 PM to 5:00 PM), and if that time is a second time (e.g., 3:00 PM), the UE can determine that it applies the second network access information. For example, a valid location (e.g., at TAC=1, GPS coordinates (30.0N, 125.0E)) can indicate where the UE applies the second network access information. For example, if the valid location indicates a specific location (e.g., TAC=2, 3, 5), and the cell associated with the UE indicates a first location (e.g., TAC=4), then the UE can determine that it does not apply the second network access information. For example, if the valid location indicates a specific location (e.g., GPS coordinates (from 25.0N to 25.1N, from 30.0E to 30.1E)), and the UE's location is a second location (e.g., GPS coordinates (25.05N, 30.05E)), then the UE can determine that it applies the second network access information (e.g., the second network access information).

[0299] In the example, based on determining that the UE applies second network access information, the UE can apply the second network access information. For example, the UE may no longer use previous network access information (e.g., first network access information) and / or the UE may begin using the second network access information applied by the associated activation information. For example, the UE can use the first network access information used before the UE received the second network access information. In one example, the second network access information may include activation information and / or the first network access information may not include activation information. For example, the UE can use the first network access information when the conditions of the activation information of the second network access information (e.g., valid time, valid location, valid conditions) are not met. For example, the UE can use the second network access information when the conditions of the activation information of the second network access information (e.g., valid time, valid location, valid conditions) are met. For example, the UE may not use the second network access information if the activation information of the second network access information is not met. For example, for the second network access information, the UE can use the second network access information if the activation information of the second network access information is met. For example, based on determining that the UE is using second network access information, the UE may begin using the second network access information, may begin searching for cells of the network indicated by the second network access information, and / or may trigger a change from using first network access information to using second network access information.

[0300] In the example, based on one or more pieces of information from the second network access information, the UE can trigger a search for networks associated with the second network access information, and / or can change its registration from the first network to another network based on the search results. For example, if the UE discovers one or more cells of a network (the second network) based on the second network access information, the UE selects the second network and / or can send a registration request message to the second network. For example, the selected second network may be a managed network and / or the second network access information may include information from the second network.

[0301] In the example, the UE can begin using / applying second network access information. The UE can check whether the activation information of the second network access information is met. If the conditions indicated by the activation information of the second network access information are no longer met, the UE can stop using the second network access information. For example, based on the UE stopping the use of the second network access information, the UE can perform orientation registration to the second network. For example, based on the UE stopping the use of the second network access information, if third network access information is available and / or if one or more conditions of the activation information of the third network access information are met, the UE can begin using the third network access information. For example, based on the UE stopping the use of the second network access information, if first network access information is available and / or if the first network access information does not include the activation information of the first network access information, the UE can begin using the first network access information. Based on the first network access information and / or based on the third network access information, the UE can begin searching for one or more cells of one or more networks indicated in the first network access information and / or the third network access information. Based on this search, if the UE finds one or more cells of one or more networks indicated by the first network access information and / or the third network access information, the UE can select a network from the one or more networks. Based on the selected network, the UE can send a registration message to the core network node of the selected network.

[0302] Figure 27 An example implementation of this disclosure is depicted. In the example, the UE can use network access information.

[0303] For example, the UE may be using primary network access information. Based on the primary network access information, the UE can select a network (e.g., a first network) and / or register with that network. For example, primary network access information can be network access information that the UE can use when no other network access information (e.g., secondary network access information) is delivered.

[0304] In the example, the core network node (e.g., SoR-AF, UDM, PCF, etc.) can determine whether the conditions for event information are met (e.g., based on network access assistance information). If the core network node determines that the conditions are met, it can send network access information (secondary network access information) to the UE. For example, the secondary network access information may not include activation information. The UE can receive the network access information (secondary network access information) sent by the core network, such as... Figure 25 As shown in the example.

[0305] In the example, return to Figure 27Based on the received secondary network access information, the UE can determine whether to use the secondary network access information. Based on this determination, the UE can begin applying the secondary network access information. For example, the UE may no longer use previous network access information (e.g., primary network access information) and / or the UE may begin using secondary network access information.

[0306] In the example, based on one or more pieces of information from the secondary network access information, the UE can trigger a search for the network indicated by the secondary network access information. For example, the UE can change its registration from a first network to another network based on the search results. For example, if the UE discovers one or more cells of a network (second network) based on the secondary network access information, the UE selects the second network and / or can send a registration request message to the second network. For example, the selected second network may be a managed network and / or the second network access information may include information from the second network.

[0307] In the example, the UE can apply secondary network access information. For instance, secondary network access information may include deactivation information. Deactivation information may include one or more conditions under which the UE can stop using secondary network access information. For example, deactivation information may indicate a first time (e.g., 10:00 AM). The UE can check if the time is the time indicated in the deactivation information. For example, if the time (e.g., 09:59 AM) is not the first time, the UE can continue using secondary network access information. For example, if the time (e.g., 10:00 AM) is the first time, the UE can stop using secondary network access information and / or the UE can begin using primary network access information.

[0308] In the example, based on the initial use of primary network access information, the UE can begin searching for one or more cells of one or more networks indicated in the primary network access information. Based on this search, if the UE discovers one or more cells of one or more networks, the UE can select a network from the one or more networks. Based on the selected network, the UE can send a registration message to the core network node of the selected network.

[0309] Figure 28 An example implementation of this disclosure is depicted. In the example, one or more network nodes may generate mobility assistance information to assist NG-RAN in processing UE mobility in RRC connection mode. RRC connection mode can be an RRC connection state. For example, if the UE has an active PDU session, the UE may be in RRC connection mode and / or may have an RRC connection with NG-RAN.

[0310] In the example, SoR-AF can generate the UE's network access information. For example... Figure 20 , Figure 21, Figure 22 , Figure 23 As shown in the example, SoR-AF can have network access assistance information and / or SoR-AF can generate network access information based on network access assistance information.

[0311] In the example, return to Figure 28 The SoR-AF can send a first UDM service request (e.g., Nudm_Parameter_Provision request) message to the UDM (e.g., UDM, UDR). The first UDM service request message may include at least one of network access information, a UE identifier, network access policy assistance information, etc. The UE identifier may indicate the UE to which the network access information and / or network access policy assistance information can be applied. In the example, the UDM can receive the first UDM service request message from the SoR-AF.

[0312] In the example, the UDM may store network access information and / or network access policy assistance information received from the first UDM service request message. Based on the received first UDM service request message, the UDM may send a second UDM service request (e.g., a Nudm_SDM_Notification request) message to the PCF associated with the UE. For example, to receive the second UDM service request message, the PCF may register its address with the UDM, and / or the UDM may store the PCF's address. Based on the registered address, the UDM may send the second UDM service request message to the PCF. For example, the second UDM service request message may include at least one of network access information, network access policy assistance information, and / or the UE's identifier.

[0313] In the example, the PCF can receive a second UDM service request message sent by the UDM. Based on the network access policy assistance information and / or network access information in the second UDM service request message, the PCF can construct the UE's network access policy information. In response to receiving the second UDM service request message, the PCF can send a PCF service request message (e.g., Npcf_AMPolicyControl_Create response, Npcf_AMPolicyControl_Update response, policy response, Npcf_AMPolicy_Notify, etc.) to the AMF. The PCF service request message may include at least one of network access information and / or network access policy information. In one example, network access information may include network access policy information. For example, network access policy information may include mobility assistance information. For example, mobility assistance information may indicate information that the NG-RAN can hand over the UE to one or more networks. For example, a first network (e.g., a first managed network) may allow the UE to access the first network, and / or a second network (e.g., a second managed network) may disallow the UE to access the second network. Mobility assistance information may indicate that the UE can use the first network and / or the UE can choose not to use the second network. For example, mobility assistance information may include validity information, which indicates when and / or where information from one or more networks can be used or is valid.

[0314] In the example, the AMF can receive a PCF service request message from the PCF. Based on the network access information and / or network access policy information received from the PCF service request message, the AMF can determine information to provide to the NG-RAN that can assist the NG-RAN in controlling the UE's mobility. For example, based on the network access information and / or network access policy information received via the PCF service request message, the AMF can generate mobility assistance information. In response to receiving the PCF service request message, the AMF can send an N2 message to the NG-RAN (e.g., initial context establishment, UE context modification). For example, the N2 message may include mobility assistance information and / or network access information.

[0315] In the example, NG-RAN can receive an N2 message sent by AMF. Based on the mobility assistance information in the N2 message, NG-RAN can determine whether it can begin using the mobility assistance information. For example, if the mobility assistance information does not include validity information (e.g., when and / or where the mobility assistance information is applied), NG-RAN can begin using the mobility assistance information. For example, if the mobility assistance information includes validity information, NG-RAN can determine whether one or more conditions indicated by the validity information are met. For example, the validity information may indicate a first time (e.g., 09:00 AM) and / or a first location (e.g., cell A, TA B). For example, NG-RAN can determine whether the first time indicated by the validity information is met. For example, if the time (e.g., 08:59 AM) is not the first time, NG-RAN may not begin using the mobility assistance information. For example, if the time (e.g., 09:00 AM) is the first time, NG-RAN can begin using the mobility assistance information. For example, NG-RAN can determine whether the first location indicated by the validity information is met. For example, if the current location (e.g., TAB) is not within the first location, NG-RAN may not start using mobility assistance information. For example, if the current location (e.g., cell A) is within the first location, NG-RAN may start using mobility assistance information.

[0316] In the example, based on determining that mobility assistance information has been initiated, NG-RAN can send an RRC configuration message (e.g., RRCReconfiguration, RRCResume) to the UE. For example, the RRC configuration message may include a measurement configuration (e.g., measConfig). For example, the measurement configuration may include a network measurement configuration. The network measurement configuration may include information about one or more networks that the UE can measure and / or report. For example, NG-RAN can construct the network measurement configuration based on mobility assistance information. For example, the network measurement configuration may include at least one of one or more identifiers of one or more networks (e.g., NCC, NMC, NID, network name, etc.), reporting information, and / or measurement gap information for network searching. For example, the reporting information may indicate how / when the UE sends a report to NG-RAN and / or the content of the UE's report. For example, the reporting information may indicate that the UE can send a report to NG-RAN when it detects one or more networks indicated by the network measurement configuration. For example, the reporting information may indicate that the UE can send reports about one or more networks and / or may indicate one or more frequencies that one or more networks can use. The measurement gap information for network searching may indicate one or more time-related information when the UE can perform a search for one or more networks. For example, the UE and / or NG-RAN may not transmit data during a time period indicated by one or more time information.

[0317] In the example, the UE can search for one or more networks based on network measurement configuration. For example, based on measurement gap information used for network search, the UE can search for one or more networks during a time period indicated by the measurement gap information used for network search. In the example, the UE can discover one or more cells of one or more networks indicated by the network measurement configuration. If the UE discovers one or more cells, the UE can send a measurement report to the NG-RAN. For example, the measurement report can include information about one or more networks detected by the UE. For example, the network measurement configuration can include information about a first network and / or a second network. For example, the information about the first network can be the identifier of the first network (e.g., MCC=A, MNC=B, NID=C). For example, the information about the second network can be the identifier of the second network (e.g., network name = "host network A"). For example, if the UE detects a third cell, the UE can read the information about the network associated with the third cell via the system information of the third cell. For example, the information about the network associated with the third cell can indicate the third identifier of the third network (e.g., MCC=A, MNC=B, NID=D). If the network measurement configuration does not include the identifier of the third network, the UE may not report the detection of the third cell and / or the third network to the NG-RAN. For example, if the UE detects a second cell, it can read information about the network associated with that second cell via the second cell's system information. For instance, the network information associated with the second cell might indicate a second identifier for the second network (e.g., network name = "host network A"). Based on the network measurement configuration including the identifier of the second network, the UE can send a measurement report to the NG-RAN that includes information about the detected network. For example, the detected network information might include information about the second cell and / or information about the second network.

[0318] In the example, NG-RAN can receive a measurement report sent by the UE. For example, based on the measurement report including information about detected networks and / or based on mobility assistance information, NG-RAN can determine whether it needs to hand over the UE. For example, based on the mobility assistance information including information about detected networks, NG-RAN can determine to hand over the UE to a target network. For example, the target network can be a network indicated in the detected network information (e.g., a second network). For example, to switch the UE to the target network (e.g., the second network), NG-RAN can send an RRC message (e.g., an RRC reconfiguration message). The RRC message (e.g., an RRC reconfiguration message) can include information about the target network, indicating the cell in the target network the UE accesses. In one example, based on the mobility assistance information including information about detected networks, NG-RAN can determine to release the RRC connection to the UE and / or instruct the UE to select a target network. For example, based on determining to release the RRC connection and / or instructing the UE to select a target network, NG-RAN can send an RRC message (e.g., an RRC release message). The RRC message (e.g., an RRC release message) can include information about the target network. The UE can receive the RRC message. Based on information about the target network, the UE can perform cell selection and / or network selection. For example, the UE can select a target network and / or begin a registration process for the target network.

[0319] Figure 29 An example implementation of this disclosure is depicted. In the example, one or more network nodes may generate mobility assistance information to assist NG-RAN in processing UE mobility in RRC connectivity mode. For example, if the UE has an active PDU session, the UE may be in RRC connectivity mode and / or may have an RRC connection with NG-RAN.

[0320] In the example, SoR-AF can generate the UE's network access information. For example... Figure 20 , Figure 21 , Figure 22 , Figure 23 As shown in the example, SoR-AF can collect network access assistance information. Based on the network access assistance information, SoR-AF can generate network access information.

[0321] In the example, return to Figure 29The SoR-AF can send a first UDM service request (e.g., Nudm_Parameter_Provision request) message to the UDM (e.g., UDM, UDR). The first UDM service request message may include at least one of network access information, a UE identifier, network access policy assistance information, etc. The UE identifier may indicate the UE to which the network access information and / or network access policy assistance information can be applied. In the example, the UDM can receive the first UDM service request message from the SoR-AF.

[0322] In the example, the UDM may store the received network access information. Based on the received first UDM service request, the UDM may send a second UDM service request (e.g., a Nudm_SDM_Notification request) message to the AMF associated with the UE. For example, to receive the second UDM service request message, the AMF may register its address with the UDM, and / or the UDM may store the AMF's address. Based on the registered address, the UDM may send the second UDM service request message to the AMF. For example, the second UDM service request message may include at least one of network access information and / or mobility assistance information. In one example, network access information may include mobility assistance information. For example, mobility assistance information may indicate information about one or more networks to which the NG-RAN may hand over the UE. For example, a first network (e.g., a first managed network) may allow the UE to access the first network, and / or a second network (e.g., a second managed network) may disallow the UE to access the second network. Mobility assistance information may indicate that the UE may use the first network and / or the UE may not use the second network. For example, mobility assistance information may include validity information, which indicates when and / or where information from one or more networks can be used or is valid.

[0323] In the example, the AMF can receive a second UDM service request message from the UDM. Based on the network access information and / or mobility assistance information in the UDM service request message, the AMF can determine information to provide to the NG-RAN that can assist the NG-RAN in controlling the UE's mobility. In one example, based on the network access information, the AMF can generate mobility assistance information. In response to receiving the UDM service request message, the AMF can send an N2 message to the NG-RAN (e.g., initial context establishment, UE context modification). For example, the N2 message may include mobility assistance information and / or network access information.

[0324] In the example, NG-RAN can receive N2 messages sent by AMF. For example... Figure 28As shown in the example, based on information delivered via N2 messages, NG-RAN can determine whether to activate network measurement configuration, NG-RAN can send network measurement configuration to UE, NG-RAN can receive measurement reports from UE, UE can perform measurements, UE can send measurement reports to NG-RAN, NG-RAN can hand over UE across regions, NG-RAN can release RRC connection, UE can perform handover, and / or UE can perform network selection.

[0325] Figure 30 An example implementation of this disclosure is depicted. In the example, one or more network nodes can generate mobility assistance information to assist the NG-RAN in processing UE mobility in RRC connected mode. For example, if the UE has an active PDU session, the UE can be in RRC connected mode.

[0326] In the example, SoR-AF can generate the UE's network access information. For example... Figure 20 , Figure 21 , Figure 22 , Figure 23 As shown in the example, SoR-AF can collect network access assistance information and / or SoR-AF can generate network access information based on network access assistance information.

[0327] Return to Figure 30 In one example, SoR-AF can determine when to send network access information and / or network policy assistance information to one or more network nodes, such as Figure 25 As shown in the example. Return to Figure 30 If the SoR-AF determines that it needs to send network access information and / or network policy assistance information, the SoR-AF may send a first UDM service request (e.g., Nudm_Parameter_Provision request) message to the UDM (e.g., UDM, UDR). The first UDM service request may include at least one of network access information, the UE's identifier, validity information, and / or network policy assistance information. In one example, the network access information may include mobility assistance information and / or validity information. The UDM may receive the first UDM service request message from the SoR-AF.

[0328] In one example, based on the received first UDM service request message, the UDM may store network access information, the UE's identifier, validity information, and / or network policy assistance information. In another example, based on the validity information of the received first UDM service request, the UDM may determine whether one or more conditions indicated by the validity information are met. For example, one or more conditions (of the validity information) may include time information. If the time information condition is met (e.g., the time is within the time period indicated by the time information), the UDM may send a second UDM service request (e.g., a Nudm_SDM_Notification request) message to the AMF associated with the UE. For example, the second UDM service request message may include network access information and / or mobility assistance information. For example, mobility assistance information may indicate to the NG-RAN that the NG-RAN can hand over the UE to and / or that the UE can reselect to one or more networks. For example, the UDM may construct mobility assistance information based on the UE's network access information and / or subscription information.

[0329] In one example, based on the received first UDM service request message, the UDM may store network access information, the UE's identifier, validity information, and / or network policy assistance information. In another example, the UDM may send a third UDM service request message to the PCF associated with the UE. For example, the third UDM service request message may include at least one of network access information, network access policy assistance information, the UE's identifier, and / or validity information. The PCF may receive the third UDM service request message sent by the UDM.

[0330] In one example, based on the validity information of the received third UDM service request, the PCF can determine whether one or more conditions indicated by the validity information are met. For example, one or more conditions in the validity information may include time information. If the time information condition is met (e.g., the time is within the time period indicated by the time information), the PCF may send a PCF service request message (e.g., Npcf_AMPolicyControl_Create response, Npcf_AMPolicyControl_Update response, policy response, Npcf_AMPolicy_Notify, etc.) to the AMF. The PCF service request message may include at least one of network access information, network access policy information, validity information, and / or the UE's identifier. The network access information and / or network access policy information may include mobility assistance information.

[0331] In the example, the AMF can receive a second UDM service request message from the UDM and / or a PCF service request message from the PCF. Based on the second UDM service request message and / or the PCF service request message, the AMF can determine when to send an N2 message to the NG-RAN (e.g., initial context establishment, UE context modification). For example, the AMF can use validity information to determine when to send an N2 message. The AMF can send an N2 message when one or more conditions indicated by the validity information are met. For example, the AMF can determine to send an N2 message when it does not receive validity information. For example, to control UE mobility, the N2 message may include mobility assistance information.

[0332] In the example, NG-RAN can receive N2 messages sent by AMF. For example... Figure 28 , Figure 29 As shown in the example, based on the N2 message, NG-RAN can determine whether to activate the network measurement configuration, NG-RAN can send the network measurement configuration to the UE, NG-RAN can receive the measurement report from the UE, the UE can perform the measurement, the UE can send the measurement report, NG-RAN can hand over the UE across areas, NG-RAN can release the RRC connection, the UE can perform the handover, and / or the UE can perform network selection.

[0333] Figure 31 An example implementation of this disclosure is depicted. In the example, based on information from one or more network slices provided by one or more networks (e.g., one or more managed networks), NG-RAN can determine to hand over the UE to one or more networks.

[0334] In the example, the AMF can receive a second UDM service request message from the UDM, and / or the AMF can receive a PCF service request message from the PCF, such as... Figure 28 , Figure 29 , Figure 30 As shown in the example. Return to Figure 31 The second UDM service request message and / or PCF service request message may also include information about the target network slice. For example, network access information, network access assistance information, and / or mobility assistance information may include information about the target network slice. The information about the target network slice may include information about one or more network slices that one or more networks indicated by the network access information can provide to the UE. For example, one or more networks in the network access information may include a fifth network and / or a sixth network. The fifth network can provide a fifth network slice (e.g., S-NSSAI 5) and / or the sixth network can provide a sixth network slice (e.g., S-NSSAI 6). The information about the target network slice may instruct the fifth network to provide a fifth network slice and / or the sixth network to provide a sixth network slice.

[0335] In the example, based on the second UDM service request message and / or PCF service request message, the AMF can determine to provide the NG-RAN with mobility assistance information that can help the NG-RAN control the mobility of the UE. For example, to deliver the assistance information, the AMF can construct mobility assistance information and / or mobility access information. The AMF can send an N2 message to the NG-RAN (e.g., initial context establishment, UE context modification). For example, the N2 message may include mobility assistance information and / or network access information. For example, the mobility assistance information and / or network access information may include information about the target network slice. The NG-RAN can receive the N2 message sent by the AMF.

[0336] In the example, NG-RAN can use information about the target network slice delivered by the N2 message. Based on the target network slice information, NG-RAN can send RRC configuration messages (e.g., RRCReconfiguration, RRCResume) to the UE. For example, the RRC configuration message may include measurement configuration (e.g., measConfig). For example, the measurement configuration may include network measurement configuration. The network measurement configuration may include information about the target network slice that the UE can measure and / or report. For example, the target network slice information may include at least one of one or more identifiers of one or more network slices (e.g., S-NSSAI, etc.), reporting information, and / or measurement gap information for network search. For example, the reporting information may indicate how / when the UE sends a report to NG-RAN and / or the content of the UE's report. For example, the reporting information may indicate that the UE can send a report to NG-RAN when it detects one or more cells indicating one or more network slices. For example, the reporting information may indicate that the UE can send a report including information about one or more network slices and / or broadcast information about one or more network slices. The measurement gap information for network search may indicate one or more time information when the UE can perform a search for one or more network slices. In one example, a network slice (among one or more network slices) can be identified by the identifier of the network slice (e.g., S-NSSAI) and / or the identifier of the network slice group to which the network slice belongs.

[0337] In the example, the UE can search for one or more cells, one or more network slices, and / or one or more networks based on network measurement configuration. For example, based on measurement gap information used for network search, the UE can search for one or more cells indicating one or more network slices during the time period indicated by the measurement gap information used for network search. If the UE discovers one or more cells indicating one or more network slices, the UE can send a measurement report to the NG-RAN. For example, the measurement report may indicate information about one or more network slices detected / discovered by the UE, information about one or more cells indicating one or more network slices, and / or information about one or more networks associated with one or more cells.

[0338] In the example, NG-RAN can receive measurement reports sent by the UE. For example, based on the measurement report and / or based on information from the target network slice, NG-RAN can determine whether NG-RAN needs to hand over the UE and / or whether the UE needs to reselect a network. For example, based on the target network slice information, including one or more identifiers of one or more network slices reported in the measurement report, NG-RAN can determine to hand over the UE to the target network. For example, the target network can be a network associated with the network slice reported in the measurement report. For example, to switch the UE to the target network, NG-RAN can send an RRC message (e.g., an RRC reconfiguration message). The RRC message (e.g., an RRC reconfiguration message) can include information about the target network, indicating the cell in the target network to which the UE accesses. In one example, NG-RAN can determine to release the RRC connection to the UE and / or instruct the UE to select a target network. For example, based on determining to release the RRC connection and / or instruct the UE to select a target network, NG-RAN can send an RRC message (e.g., an RRC release message). The RRC message (e.g., an RRC release message) can include information about the target network. The UE can receive the RRC message. Based on information about the target network, the UE can perform cell selection and / or network selection. For example, the UE can select a target network and / or begin a registration process for the target network.

[0339] Figure 32 An example implementation of this disclosure is depicted. In the example, the UE can use network access information to select a network, and / or can perform registration to the selected network.

[0340] In the example, the UE may have network access information. For example, the network access information may include one or more entries. For example, one or more entries may include a first entry (entry 1) indicating a first network (network A) and / or a second entry (entry 2) indicating a second network (network B).

[0341] In the example, the UE can register to a third network (network C). For example, the UE can be in the third cell (cell 3) of the third network.

[0342] In the example, the UE can determine to use network access information. For example, based on the valid time and / or valid location of the network access information, the UE can begin using the network access information. For example, the UE can begin using the first entry of the network access information. Based on the first entity indicating a first network, the UE can attempt to discover and / or search for cells of the first network. For example, if no cells of the first network exist near the UE, the UE may not be able to discover cells of the first network. Based on the absence of cells of the first network, the UE can begin using the next entry of the network access information. For example, the UE can begin using the second entry of the network access information. The UE can attempt to discover and / or search for cells of a second network. For example, the UE can discover a second cell (cell 2) of the second network. For example, the UE can receive an SIB indicating the second network from the second cell. Based on the UE discovering cells of the second network, the UE can select the second network. The UE can select the second network to perform a registration procedure. For example, the UE can send a registration request message to the selected network. Based on the UE selecting the second network, the UE may not select a third network and / or the UE may stop selecting a third network. Based on the UE not selecting a third network, the UE may not perform registration to the third network and / or may perform deregistration to the third network.

[0343] In one example, the UE can initiate a network search procedure and / or a cell search procedure. Based on the network search procedure and / or cell search procedure, the UE can discover one or more cells. Depending on the one or more cells, the UE can determine information about one or more networks (detected networks) associated with the one or more cells by reading the SIBs of the one or more cells. For the one or more networks (detected networks), the UE can determine whether the network access information includes network information (e.g., identifiers) (among the detected networks). If the network access information includes network information (among the detected networks), the UE can select that network and perform registration to that network.

[0344] Figure 33 An example implementation of this disclosure is depicted. In the example, the UE can receive and / or apply network access information based on activation information.

[0345] In the example, the UE can receive network access information from core network nodes (e.g., AMF, PCF, UDM, SoR-AF). The network access information may include at least one of the following: information about one or more networks (e.g., networks that the UE is allowed to access, networks that the UE needs to switch to, target networks, managed networks) and / or activation information.

[0346] In the example, the UE can determine whether one or more conditions indicated by the activation information are met. For example, one or more conditions could indicate when the network access information is valid / applicable validity period information, and / or where the network access information is valid / applicable validity area information. If one or more conditions are met, the UE can begin using the network access information. For example, the UE can begin using information from one or more networks. If one or more conditions are not met, the UE can choose not to use the network access information.

[0347] In the example, based on network access information, the UE can begin searching for one or more cells of one or more networks indicated by information from one or more networks. For example, the UE can begin by attempting to discover a cell of a first network (e.g., the highest priority network among one or more networks). If the UE discovers a cell of the first network, the UE can select the first network to send a registration request. The UE can send a registration request to the first network. If the UE fails to discover a cell of the first network and / or fails to register with the first network, the UE can attempt to discover a cell of a second network (e.g., the second highest priority network among one or more networks). If the UE discovers a cell of the second network, the UE can select the second network to send a registration request. If the UE selects the second network, the UE can send a registration request. The selection iteration can continue until there are no more networks to try among the one or more networks.

[0348] In the example, the UE can receive messages (e.g., DL NAS transmission, UE configuration update, UE parameter update, security packet, transparent container, registration acceptance, etc.) from a core network node of a first network (e.g., AMF, SoR-AF, UDM, PCF, NEF), including network access information for selecting a network. The first network may include at least one of the serving network to which the UE is registered and / or the home network that owns / manages the UE's subscription. In response to receiving the message, the UE can send a response (e.g., UE configuration update, UL NAS transmission, security packet, transparent container, etc.) to the core network node to indicate the receipt of network access information and / or to indicate successful security checks of the network access information. For example, the UE can send an indication that the UE supports the processing of activation information and / or network access information. Based on this indication, the core network node can send network access information to the UE, including the activation time.

[0349] In the example, the UE can use network access information to select a network. In one example, the UE can perform a search for one or more cells of the selected network. In another example, the UE can perform a search / discovery / detection of one or more cells, identify one or more networks associated with one or more discovered / detected cells, select a network from one or more networks, and / or perform a registration procedure to the selected network. For example, for network selection, the UE can use network access information. For example, the UE can attempt to search / discover / detect one or more cells of one or more networks indicated by the network access information. For example, the UE can choose not to attempt to search / discover / detect one or more cells of one or more networks not indicated by the network access information. For example, the UE can search / discover / detect one or more cells of one or more networks, and identify one or more networks of one or more cells. One or more networks may include a first one or more networks that the network access information can indicate and / or a second one or more networks that the network access information cannot indicate. The UE can select a network from the first one or more networks and / or perform registration to the selected network.

[0350] In the example, network access information may include at least one of the following: information about one or more networks (network list); activation information indicating one or more conditions for the network list to be valid / used; and / or information about one or more access network types. The network list may include information about one or more networks that the UE can access and / or can be allowed to access. For example, the network list may include information about one or more managed networks. For example, the network list may include one or more identifiers of one or more networks. One or more identifiers of one or more networks may include at least one of one or more mobile country codes, one or more mobile network codes, one or more network identifiers (NIDs), and / or one or more names of one or more networks. For example, one or more conditions may include at least one of valid time information and / or valid area information. For example, valid time information may indicate one or more time periods during which the UE is allowed to use the network list for network selection. For example, one or more time periods may include at least one of the following: a start time indicating when the UE can use the network list; an end time indicating when the UE can stop using the network list; and / or the duration indicating the amount of time the UE can use the network list. For example, valid area information may indicate one or more location information during which the UE is allowed to use the network list for network selection. For example, one or more location information may include at least one of the following: information about one or more areas; information about one or more geographic coordinates; information about one or more cell identifiers; and / or information about one or more tracking areas. For example, one or more access network types can indicate one or more access network types (e.g., NG-RAN, E-UTRAN, GSM, E-UTRA, NR, etc.) that allow the UE to search for / select / register to networks (in the network list).

[0351] In the example, based on activation information, the UE can determine whether to allow the UE to use the network list. For example, to determine whether to allow the UE to use the network list, the UE can determine whether one or more conditions of the activation information are met. If one or more conditions are met, the UE can determine that the UE is allowed to use the network list, that the UE is allowed to access a network (in the network list), and / or that one or more networks are activated. If one or more conditions are not met, the UE can determine that the UE is not allowed to use the network list, and / or that the UE is not allowed to access one or more networks (in the network list). In the example, if the network access information does not include activation information, the UE can begin using the network list.

[0352] In the example, based on determining that the UE is allowed to use the network list and / or that the UE is allowed to access a network (in the network list), the UE begins using the network list. For example, the UE may begin searching / detecting / discovering one or more cells indicated by the network list. For example, if the search / detection / discovery of one or more cells associated with the network list is successful, the UE may select a network (e.g., a second network) from the one or more networks associated with those cells. Based on the network selection, the UE may begin the registration process for the selected network. For example, the UE may send a registration request message to the selected network. The registration request message may include at least one of the following: the UE's identifier, the reason for registration, one or more identifiers of a network slice, the identifier of a first network, the identifier of the home network, and / or the UE's capabilities. In response to sending the registration request message, the UE may receive a registration acceptance message from the second network. For example, if the UE fails to discover a cell in the second network, the UE may not select the second network.

[0353] In the example, based on activation information, the UE can determine whether it is no longer allowed to use the network list. For example, to determine whether the UE needs to stop using the network list, the UE can determine whether one or more conditions of the activation information are met. If one or more conditions are no longer met, the UE can determine that it needs to stop using the network list. In one example, a network node of a second network can send an indication to the UE that the UE needs to deregister from the second network and / or that the UE is no longer allowed to use the second network. In one example, if the UE receives an indication from the second network, the UE can choose not to use network access information, can stop using the network list, can begin selecting a third network, and / or can stop selecting the second network.

[0354] In the example, based on determining the list of networks the UE needs to stop using, the UE can search for one or more cells. For example, the UE can search for one or more cells based on second network access information. For example, if the UE discovers a cell in a third network indicated by the second network access information, the UE can select the third network. The UE can send a registration request message to the third network. In the example, the UE can use the second network access information to register with a first network. For example, the third network may include at least one of the first network and / or the network indicated by the second network access information.

[0355] Figure 34 An example implementation of this disclosure is depicted. In the example, the UE can use network access information to select a network, and / or can perform registration to the selected network.

[0356] In the example, the UE can receive network access information from the core network node of a first network (e.g., network 1). The network access information may include information from one or more networks and / or one or more activation information from one or more networks. For example, the information from one or more networks in the network access information may include information from a fourth network (network 4) and / or information from a second network (network 2). For example, one or more activation information may include activation information from the fourth network and / or activation information from the second network. The activation information from the fourth network may include a fourth condition (condition 4), and / or the activation information from the second network may include a second condition (condition 2). For example, the fourth condition may indicate a fourth time period (e.g., from 2:00 PM to 4:00 PM) and / or the second condition may indicate a second time period (e.g., from 5:00 PM to 6:00 PM). For example, the network activation information may indicate when the UE is allowed to access / search / select / register to a network. For example, based on the second condition of the second activation information associated with the second network, the UE may be allowed to access the second network during a second time period. For example, the network activation information may indicate when entries associated with the activation information (e.g., information elements, entries in the network access information) can be used by the UE. For example, information about one or more networks may include one or more identifiers of one or more networks.

[0357] In the example, for the activation information (one or more activation messages), the UE can determine whether the conditions indicated by the activation information are met. If the conditions are met, the UE can determine that it is permissible to access / use / select / register the network associated with the activation information. If the conditions are not met, the UE can determine that it is not permissible to access / use / select / register the network associated with the activation information. For example, at a certain time (e.g., 5:30 PM), based on the fact that the second condition is met at that time, the UE can determine that it is permissible to access / use / select / register to the second network. For example, at that time (e.g., 5:30 PM), based on the fact that the fourth condition is not met at that time, the UE can determine that it is not permissible to access / use / select / register to the fourth network. Based on the determination that the UE is permissible to access the second network, the UE can search for cells in the second network, the UE can select the second network, and / or the UE can send a registration request message to the second network.

[0358] In one example, based on network access information, the UE can determine whether one or more conditions of the second network's network access information are met. For example, if one or more conditions of the second network are met, the UE begins searching for / discovering cells in the second network. For example, at this time (e.g., 5:30 PM), the UE can determine that the conditions of the second network are met. Based on this determination, the UE can determine that it is allowed to access the second network. Based on this determination, the UE can begin searching for cells in the second network. If the UE discovers a cell in the second network, the UE can select the second network and / or can send a registration request message to the second network. For example, if the UE fails to discover a cell in the second network, the UE may not select the second network and / or may not send a registration request message to the second network. For example, at this time (e.g., 11:00 AM), the UE can determine that the conditions of the second network are not met. Based on this determination, the UE can determine that it is not allowed to access the second network. Based on this determination, the UE may not begin searching for cells in the second network.

[0359] In the example, the UE can receive network access information from the core network nodes of the first network (e.g., AMF, SoR-AF, UDM, PCF, AF). The network access information may include at least one of the identifier of the second network and / or the activation information of the second network. In the example, the UE can determine whether the second network is activated / active based on the activation information. For example, the activation of the network access information can indicate when the second network is active / activated. For example, the second network (e.g., a managed network) may operate within one or more time periods (e.g., from 10:00 AM to 5:00 PM, from Monday to Friday, etc.) and / or in one or more areas (e.g., geographic coordinates (x1, y1, z1), in city A, etc.). For example, the activation information of the second network can indicate that the second network can operate and / or may be active within one or more time periods and / or in one or more areas. Based on the activation information of the second network, the UE can determine whether the second network is active and / or operational. For example, at a first time (e.g., 08:00 AM), the UE can determine that the second network is inactive. For example, at a second time (e.g., 1:00 PM), the UE can determine that the second network is active. For instance, based on network access information including information about the second network, when the second network is activated, the UE can determine that it is permitted to access the second network. In this example, based on determining that the second network is active / activated, the UE can begin searching for cells of the second network and / or the UE can select the second network. In one example, if the UE discovers / detects a cell of the second network, the UE can select the second network. Based on the UE's selection of the second network and / or based on the discovery / detection of a cell of the second network, the UE can send a registration request message to the second network.

[0360] In the example, the UE can receive network access information from the core network nodes (AMF, SoR-AF, UDM) of the first network. This network access information can assist the UE in selecting a network (e.g., a managed network). The network access information may include at least one of one or more network information and / or activation information. In the example, based on the activation information, the UE can determine to use the network access information. For example, the UE can use information from one or more networks to search for / select a network indicated by that information.

[0361] In the example, the UE can receive first network access information from the core network nodes (AMF, SoR-AF, UDM, PCF, AF) of a first network for network selection. For example, the first network access information includes information and / or activation information for one or more networks. The information for one or more networks may include information from a second network. In the example, based on the first network access information, the UE can register to the second network. In the example, the UE can determine to stop using the first network access information based on at least one of the activation information from the first network access information and / or an indication from the second network. For example, the second network can send a message to the UE including this indication. This indication may instruct the UE to deregister from the second network, not to allow access to the second network, for the UE to perform network selection, and / or for the UE to stop using the first network selection information. Based on determining to stop using the first network access information, the UE can search for cells in a third network. For example, the UE can perform a search based on the second network access information.

[0362] In the example, the UE can register to a second network. In the example, the UE can determine to stop using the first network access information based on at least one of activation information from the first network access information and / or an indication from the second network. For example, the second network can send a message to the UE including this indication. This indication could instruct the UE to deregister from the second network, be disallowed from accessing the second network, require the UE to perform network selection, and / or require the UE to stop using the first network selection information. Based on determining to stop using the first network access information, the UE can search for cells in a third network. For example, the UE can perform the search based on the second network access information.

[0363] In the example, the core network node can determine whether to send network access information to the UE based on activation information. Network access information may include information about one or more networks. These one or more networks can be one or more networks that the UE is allowed to use / select. Based on the determination to send network access information, the core network node can send the network access information to the UE.

[0364] In the example, the UE can send a request for network access information to a core network node (e.g., AMF, SoR-AF, UDM, etc.). For example, the core network node could be the core network node of a first network. The core network node can receive the request for network access information from the UE. The network access information may include information about one or more networks that the UE is allowed to use / access. In response to the request, the core network node can send the network access information to the UE. The UE can use the network access information to select a network. In response to the request to send network access information, the UE can receive the network access information from the core network node. Based on the received network access information, the UE can select a second network for registration. The network access information may include information about the second network.

[0365] In the example, the core network node can receive network access assistance information. This network access assistance information may include at least one of one or more UEs' information and / or one or more networks' information. In the example, based on the network access assistance information, the core network node can determine network access information. This network access information may include information from one or more networks. In the example, the core network node can send network access information to one or more UEs.

[0366] In the example, the UE can send a message (e.g., a registration request) to the core network node of a first network (e.g., AMF, UDM, SoR-AF, PCF) indicating the capability to process network access information for selecting a network (e.g., a managed network). The core network node can receive from the UE a message indicating the capability to process network access information for selecting a network. This capability can indicate whether the UE is capable of processing network access information and / or whether the UE is capable of processing activation information for network access information. The core network node can determine the network access information based on this message. The network access information may include at least one of one or more network information and / or activation information. Based on the determined network access information, the core network can send a message including the network access information to the UE. In the example, the UE can receive a message including the network access information from the core network node. Based on the network access information, the UE can select a second network. For example, the network access information may include information about the second network.

Claims

1. A method comprising: A non-access layer (NAS) message is sent by a radio device to the Access and Mobility Management Function (AMF) of a public terrestrial mobile network (PLMN). The NAS message indicates that the radio device is capable of supporting an enhanced roaming guidance (SOR) for selecting an independent non-public network (SNPN). In the enhanced SOR, the radio device checks whether one or more location validity conditions for accessing one or more SNPNs are met. and The wireless device receives network access information from the AMF, the network access information including: The identifier of the first SNPN; and Location validity conditions, indicating where the wireless device is permitted to access the first SNPN, wherein the location validity conditions include one or more tracking areas; and When the location validity condition is met, the wireless device sends a registration request message to the first SNPN.

2. The method of claim 1, wherein the NAS message indicates that the wireless device supports processing the network access information.

3. The method according to claim 1, wherein, The NAS message includes at least one of the following: The identifier of the wireless device; One or more identifiers of the requested network slice; or The identifier of the first SNPN.

4. The method of claim 3, wherein the wireless device receives the network access information in response to sending the NAS message.

5. The method according to claim 3, wherein, The NAS message includes a first registration request message.

6. The method according to claim 1, wherein, The network access information includes time period conditions during which the wireless device is allowed to access the first SNPN.

7. The method according to claim 6, wherein, The time period condition includes at least one of the following: From the start time when the wireless device is allowed to access the first SNPN; From the end time when the wireless device is not allowed to access the first SNPN; or The wireless device is allowed access to the first SNPN for the duration specified.

8. A wireless device comprising one or more processors and a memory storing instructions, wherein when the instructions are executed by the one or more processors, the wireless device: Send a Non-Access Layer (NAS) message to the Access and Mobility Management Function (AMF) of the Public Land Mobile Network (PLMN). The NAS message indicates that the radio device is capable of supporting Enhanced Roaming Guidance (SOR) for selecting a Standalone Non-Public Network (SNPN). In the Enhanced SOR, the radio device checks whether one or more location validity conditions for accessing one or more SNPNs are met. and The network access information received from the AMF includes: The identifier of the first SNPN; and Location validity conditions, indicating where the wireless device is permitted to access the first SNPN, wherein the location validity conditions include one or more tracking areas; and When the location validity condition is met, a registration request message is sent to the first SNPN.

9. The wireless device according to claim 8, wherein, The NAS message indicates that the wireless device supports processing the network access information.

10. The wireless device according to claim 8, wherein, The NAS includes at least one of the following: The identifier of the wireless device; One or more identifiers of the requested network slice; or The identifier of the first SNPN.

11. The wireless device of claim 10, wherein the wireless device receives the network access information in response to sending the NAS message.

12. The wireless device according to claim 10, wherein, The NAS message includes a first registration request message.

13. The wireless device according to claim 8, wherein, The network access information includes time period conditions during which the wireless device is allowed to access the first SNPN.

14. The wireless device according to claim 13, wherein, The time period condition includes at least one of the following: From the start time when the wireless device is allowed to access the first SNPN; From the end time when the wireless device is not allowed to access the first SNPN; or The wireless device is allowed access to the first SNPN for the duration specified.

15. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause a wireless device to: Send a Non-Access Layer (NAS) message to the Access and Mobility Management Function (AMF) of the Public Land Mobile Network (PLMN). The NAS message indicates that the radio device is capable of supporting Enhanced Roaming Guidance (SOR) for selecting a Standalone Non-Public Network (SNPN). In the Enhanced SOR, the radio device checks whether one or more location validity conditions for accessing one or more SNPNs are met. and The network access information received from the AMF includes: The identifier of the first SNPN; and Location validity conditions, indicating where the wireless device is permitted to access the first SNPN, wherein the location validity conditions include one or more tracking areas; and When the location validity condition is met, a registration request message is sent to the first SNPN.

16. The computer-readable medium of claim 15, wherein, The NAS message indicates that the wireless device supports processing the network access information.

17. The computer-readable medium of claim 15, wherein, The NAS message includes at least one of the following: The identifier of the wireless device; One or more identifiers of the requested network slice; or The identifier of the first SNPN.

18. The computer-readable medium of claim 17, wherein, The wireless device receives the network access information in response to sending the NAS message.

19. The computer-readable medium of claim 17, wherein, The NAS message includes a first registration request message.

20. The computer-readable medium of claim 15, wherein, The network access information includes time period conditions during which the wireless device is allowed to access the first SNPN.

Images