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 conditions for determining whether the wireless device is allowed 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-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 322,714, filed on March 23, 2022, the entire contents of which are hereby incorporated by reference. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0004] Figure 1A and Figure 1B An example communication network including an access network and a core network is shown.

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

[0006] Figure 3 An example communication network including core network functionality 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 a core network architecture for a roaming scenario is shown.

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

[0010] Fig. 7A , Figure 7B and Figure 7C A user plane protocol stack, a control plane protocol stack, and services provided between protocol layers of the user plane protocol stack are shown.

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

[0012] Fig.9A , Fig. 9B , Fig. 9C and Fig.9D Example states and state transitions of a wireless device are shown.

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

[0014] Fig.11 An example of a service request procedure for a wireless device is shown.

[0015] Fig.12 An example of a protocol data unit session establishment procedure for a wireless device is shown.

[0016] Fig.13 An example of an assembly of elements in a communication network is shown.

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

[0018] Fig.15 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0019] Fig.16 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0020] Fig.17 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0021] Fig.18 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0022] Fig.19 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0023] Fig. 20 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0024] Fig.21 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0025] Fig. 22 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0026] Fig.23 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0027] Fig.24 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0028] Fig.25 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0029] Fig.26 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0030] Fig. 27 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0031] Fig.28 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0032] Fig.29 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0033] Fig.30 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0034] Fig.31 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0035] Fig.32 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0036] Fig.33 is an exemplary diagram of one aspect of an embodiment of the present disclosure.

[0037] Fig.34 is an exemplary diagram of one aspect of an embodiment of the present disclosure. DETAILED DESCRIPTION

[0038] In the present disclosure, various embodiments are presented in the form of examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in environments and scenarios. It will be apparent to those skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope of the present invention. In fact, after reading the specification, it will be apparent to those skilled in the relevant art how to implement alternative embodiments. The embodiments of the present invention should not be limited to any described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Restrictions, features and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of the present disclosure. Any figure highlighting functionality and advantages is provided only for illustrative purposes. The disclosed architecture is flexible and configurable enough so that it can be utilized in a manner different from that shown. For example, the actions listed in any flow chart can be reordered or only optionally used in certain embodiments.

[0039] Embodiments may be configured to operate as desired. For example, in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., when certain criteria are met, the disclosed mechanism may be executed. Exemplary criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. When one or more criteria are met, various exemplary embodiments may be applied. Therefore, exemplary embodiments that selectively implement the disclosed protocol may be implemented.

[0040] A base station may communicate with a mixture of wireless devices. A wireless device and / or a base station may support multiple technologies and / or multiple versions of the same technology. A wireless device may have one or more specific capabilities. When the present disclosure refers to a base station communicating with multiple wireless devices, the present disclosure may mean a subset of the total wireless devices in the coverage area. For example, the present disclosure may mean multiple wireless devices of a given LTE or 5G version with a given capability and in a given sector of a base station. The multiple wireless devices in the present disclosure may refer to a selected plurality of wireless devices, and / or a subset of the total wireless devices in the coverage area that perform according to the disclosed method, etc. There may be multiple base stations or multiple wireless devices in the coverage area that may not comply with the disclosed method, for example, these wireless devices or base stations may perform based on older versions of LTE or 5G technology.

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

[0042] The phrases "based on," "in response to," "depending on," "using," "using," and similar phrases indicate the presence and / or influence of certain factors and / or conditions on an event and / or action, but do not exclude the presence and / or influence of uncounted factors and / or conditions. For example, if action X is performed "based on" condition Y, this is interpreted as performing the action "based at least on" condition Y. For example, if action X is performed when conditions Y and Z are both met, then the performance of action X can be described as "based on Y."

[0043] The term "configured" may relate to the capabilities of a device, whether the device is in an operational state or a non-operational state. "Configured" may also mean a specific setting in a device that affects the operational characteristics of the device, whether the device is in an operational state or a non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. may be "configured" within a device to provide specific characteristics to the device, whether the device is in an operational state or a non-operational state. Terms such as "a control message caused in a device" may mean that the control message has parameters that can be used to configure specific characteristics in the device or parameters that can be used to implement certain actions in the device, whether the device is in an operational state or a non-operational state.

[0044] In the present 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. Parameters may be referred to as fields or information elements. In an example embodiment, when one or more messages include multiple parameters, it means that a parameter in the multiple parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages.

[0045] The present disclosure may relate to possible combinations of enumerated elements. For the sake of brevity and readability, the present disclosure does not explicitly describe each arrangement that can be obtained by selecting from the set of optional features. The present disclosure should be interpreted as explicitly disclosing all such arrangements. For example, seven possible combinations of enumerated elements A, B, and C are composed of the following: (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 the sake of 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 non-X" should be interpreted as "X or non-X". It should also be understood that these expressions may describe alternative wordings of overlapping and / or synonymous concepts, for example, "identifier, identification and / or ID number."

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

[0047] Figure 1A 1 shows an example of a communication network 100 in which embodiments of the present disclosure may be implemented. The communication network 100 may include, for example, a public land mobile network (PLMN) operated by a network operator. Figure 1A As shown in , 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] The wireless device 101 may communicate with the DN 108 via the AN 102 and the CN 105. In the present disclosure, the term wireless device may refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is required or can be used. For example, the wireless device may be a phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a vehicle roadside unit (RSU), a relay node, a car, a drone, an 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, handset, wireless transmission and reception unit (WTRU), and / or wireless communication device.

[0049] AN 102 may connect the wireless device 101 to CN 105 in any suitable manner. The direction of communication from AN 102 to the wireless device 101 is referred to as downlink, while the direction of communication from the wireless device 101 to AN 102 is referred to as uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplex (FDD), time division duplex (TDD), and / or some combination of the two duplex technologies. AN 102 may be connected to the wireless device 101 by radio communication via an air interface. An access network that operates at least partially via an air interface may be referred to as a radio access network (RAN). CN 105 may set up one or more end-to-end connections between the wireless device 101 and the one or more DNs 108. CN 105 may authenticate the wireless device 101 and provide billing functionality.

[0050] In the present disclosure, the term base station may 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 may be a terrestrial base station fixed to the ground. A base station may be a mobile base station with a mobile coverage area. A base station may be in space, such as on a satellite. For example, WiFi and other standards may use the term access point. As another example, the third generation partnership project (3GPP) has produced specifications for three generations of mobile networks, each of which uses different terms. The third generation (3G) and / or universal mobile telecommunications system (UMTS) standards may use the term node B. 4G, long term evolution (LTE), and / or evolved universal terrestrial radio access (E-UTRA) standards may use the term evolved node B (eNB). 5G and / or new air interface (NR) standards may describe AN 102 as a next generation radio access network (NG-RAN), and may refer to base stations as next generation eNBs (NextGeneration eNBs, ng-eNBs) and / or gNBs (Generation Node Bs). Future standards (e.g., 6G, 7G, 8G) may use new terminology to refer to elements (e.g., wireless devices, base stations, ANs, CNs, and / or components thereof) that implement the methods described in the present 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 rebroadcast a radio signal received from a donor node. A relay node may perform the same / similar functions as a repeater node, but may decode a radio signal received from a donor node to eliminate noise before amplifying and rebroadcasting the radio signal.

[0051] AN 102 may include one or more base stations, each of which has one or more coverage areas. The geographical size and / or range of the coverage area may be defined according to the range in which the 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 partition or cell (but in some contexts, the term cell refers to the carrier frequency used in a particular coverage area, not 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 include, in descending order of coverage area: microcell base stations, picocell base stations, and femtocell base stations or home base stations. The coverage areas of the base stations may together provide wireless coverage to the wireless device 101 over a wide geographic area to support wireless device mobility.

[0052] The base station may include one or more groups of antennas for communicating with the wireless device 101 via an air interface. Each group of antennas may be controlled individually by the base station. Each group of antennas may have a corresponding coverage area. As an example, the base station may include three groups of antennas to respectively control three coverage areas on three different sides of the base station. 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 groups of antennas at one or more distributed locations. The controller may be, for example, a baseband processing unit that is part of a centralized or cloud RAN architecture. The baseband processing unit may be concentrated in a pool of baseband processing units or virtualized. A group of antennas at a distributed location may be referred to as a remote radio head (RRH).

[0053] Figure 1B 1 shows another example communication network 150 in which embodiments of the present disclosure may be implemented. The communication network 150 may include, for example, a PLMN operated by a network operator. Figure 1B As shown in , 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 a control plane function 155A and a user plane function 155B. The one or more DNs 158 may include a public DN (e.g., the Internet), a dedicated DN, and / or an intra-operator DN. With respect to Figure 1A , and the corresponding components shown in the figure may represent specific implementations and / or terms.

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

[0055] Each of the Uu, Xn, and NG interfaces may be associated with a protocol stack. The protocol stack may include a user plane (UP) and a control plane (CP). Typically, user plane data may include data about a 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 may include signaling and messages that facilitate the packaging and routing of user plane data so that it can be exchanged with a DN. For example, the NG interface may be divided into an NG user plane interface (NG-U) and an NG control plane interface (NG-C). The NG-U interface may provide for the delivery of user plane data between a base station and the one or more user plane network functions 155B. The NG-C interface may be used for control signaling between a base station and the one or more control plane network functions 155A. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transmission of NAS messages, paging, PDU session management, and configuration delivery and / or warning message transmission. In some cases, the NG-C interface may support the transmission of user data (e.g., small data transmission for IoT devices).

[0056] One or more of the base stations of the NG-RAN 152 may be split into a central unit (CU) and one or more distributed units (DUs). The CU may be connected to the one or more DUs via an F1 interface. The CU may process one or more upper layers in the protocol stack, and the DU may process one or more lower layers in the protocol stack. For example, the CU may process RRC, PDCP, and SDAP, and the DU may process RLC, MAC, and PHY. The one or more DUs may be in geographically distinct locations relative to the CU and / or relative to each other. Accordingly, the CU / DU split architecture may allow for increased coverage and / or better coordination.

[0057] gNB 152A and ng-eNB 152B may provide different user plane and control plane protocol terminations toward UE 151. For example, gNB 154A may provide new air interface (NR) protocol termination via a Uu interface associated with a first protocol stack. ng-eNB 152B may provide evolved UMTS terrestrial radio access (E-UTRA) protocol termination via a Uu interface associated with a second protocol stack.

[0058] 5G-CN 155 may authenticate UE 151, set up end-to-end connection between UE 151 and the one or more DNs 158, and provide charging functionality. 5G-CN 155 may be based on a service-based architecture, in which the NFs that make up 5G-CN 155 provide services to each other and to other elements of the communication network 150 via interfaces. 5G-CN 155 may include 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 frameworks for a service-based architecture within a core network are shown. In a service-based architecture, service consumers may seek services and services are provided by service producers. Before obtaining a particular service, the NF may determine where this service can be obtained. In order to discover services, the NF may communicate with a network repository function (NRF). As an example, a NF that provides one or more services may register with a network repository function (NRF). The NRF may store data related to the one or more services that the NF is preparing to provide to other NFs in the service-based architecture. A consumer NF may query the NRF to discover a producer NF (e.g., by obtaining a list of NF instances that provide a particular service from the NRF).

[0060] exist Figure 2A In the example of , NF 211 (in this example, a consumer NF) may send a request 221 to NF 212 (a 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 the 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 associated with the requested service (e.g., retrieve data), and provide response 221. The one or more actions performed by NF 212 may be based on the 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 of FIG. 24 , NF 231 sends request 241 to NF 232. In this example, part of the service generated by NF 232 will be to send 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 may perform the role of a service producer, a service consumer, or both. A particular NF service may contain any number of nested NF services produced by one or more other NFs.

[0062] Figure 2C An example of a subscription-notification interaction between a consumer NF and a producer NF is shown. Figure 2C , NF 251 sends subscription 261 to NF 252. NF 253 sends subscription 262 to NF 252. For illustrative purposes, Figure 2C 252 may provide multiple subscription services to different NFs), but it should be understood that the subscription-notification interaction requires only one subscriber. NFs 251, 253 may be independent of each other. For example, NFs 251, 253 may independently discover NF 252 and / or independently determine to subscribe to services provided by NF 252. In response to receiving a subscription, NF 252 may provide a notification to the subscribing NF. For example, NF 252 may send notification 263 to NF 251 based on subscription 261, and may send notification 264 to NF 253 based on subscription 262.

[0063] like Figure 2C As shown in the example diagram of , the sending of notifications 263, 264 may be based on determining that a certain condition has occurred. For example, notifications 263, 264 may be based on determining that a particular event has occurred, determining that a particular condition is pending, and / or determining that a duration associated with a subscription has elapsed (e.g., a period associated with a subscription for periodic notifications). Figure 2C As shown in the example illustration of , NF 252 may send notifications 263, 264 to NF 251, 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 when a specific parameter as measured by NF 252 exceeds a first threshold, and NF 252 may request notification when the parameter exceeds a second threshold different from the first threshold. In the example, the parameters of interest and / or the corresponding thresholds may be indicated in the subscriptions 261, 262.

[0064] Figure 2D Another example of a subscribe-notify interaction is shown. Figure 2D In the example, NF 271 sends a subscription 281 to NF 272. In response to receiving the subscription 281 and / or determining that a notification condition has occurred, NF 272 may send a notification 284. Notification 284 may be sent to NF 273. Figure 2C Example in (where notification is sent to subscribing NF), Figure 2DPresentation, subscription and its corresponding notification can be associated with different NFs. For example, NF 271 can subscribe to the service provided by NF 272 on behalf of NF 273.

[0065] Figure 3 Another example communication network 300 is shown in which embodiments of the present disclosure may be implemented. 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 depicted in the figure 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 NF depicted in FIG. 1 includes a user plane function (UPF) 305, an access and mobility management function (AMF) 312, a session management function (SMF) 314, a policy control function (PCF) 320, a network repository function (NRF) 330, a network exposure function (NEF) 340, a unified data management (UDM) 350, an authentication server function (AUSF) 360, a network slice selection function (NSSF) 370, a charging function (CHF) 380, a network data analysis function (NWDAF) 390, and an application function (AF) 399. UPF 305 may be a user plane core network function, and NFs 312, 314, and 320-390 may be control plane core network functions. Although Figure 3 Not shown in the example of FIG, the core network may include additional instances of any of the depicted NFs and / or one or more different NF types providing different services. Other examples of NF types include Gateway Mobile Location Center (GMLC), Location Management Function (LMF), Operation, Administration and Maintenance Function (OAM), Public Warning System (PWS), Short Message Service Function (SMSF), Unified Data Repository (UDR), and Unstructured Data Storage Function (UDSF).

[0067] Figure 3 Each element depicted in has an interface with at least one other element. The interface may be a logical connection rather than, for example, a direct physical connection. Any interface may be identified using a reference point representation and / or a service-based representation. In a reference point representation, the letter 'N' followed by a number indicates an interface between two specific elements. For example, 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 a service-based representation, the letter 'N' is followed by a letter. The letter identifies the NF that provides services to the core network. For example, PCF 320 can provide services via interface 'Npcf'. PCF 320 can provide services to any NF in the core network via 'Npcf'. Accordingly, the service-based representation can correspond to a set of reference point representations. For example, the Npcf interface between PCF 320 and the core network can generally correspond to the N7 interface between PCF 320 and SMF 314, the N30 interface between PCF 320 and NEF 340, and so on.

[0068] The UPF 305 may act as a gateway for user plane traffic between the AN 302 and the DN 308. The UE 301 may be connected to the UPF 305 via the Uu interface and the N3 interface (also described as the NG-U interface). The UPF 305 may be connected to the DN 308 via the N6 interface. The UPF 305 may be connected to one or more other UPFs (not shown) via the N9 interface. The UE 301 may be configured to receive services via a protocol data unit (PDU) session, which is a logical connection between the UE 301 and the DN 308. The UPF 305 (or multiple UPFs, as required) may be selected by the SMF 314 to handle a specific PDU session between the UE 301 and the DN 308. The SMF 314 may control the functions of the UPF 305 with respect to the PDU session. The SMF 314 may be connected to the UPF 305 via the N4 interface. The UPF 305 may handle any number of PDU sessions associated with any number of UEs (via any number of ANs). For the purpose of handling the one or more PDU sessions, the UPF 305 may be controlled by any number of SMFs via any number of corresponding N4 interfaces.

[0069] Figure 3 The AMF 312 depicted in FIG. 3 may control the UE's access to the core network. The UE 301 may register with the network via the AMF 312. The UE 301 may have to register before establishing a PDU session. The AMF 312 may manage the registration area of ​​the UE 301, thereby enabling the network to track the physical location of the UE 301 within the network. For a UE in connected mode, the AMF 312 may manage UE mobility, such as handover from one AN or part thereof to another AN. For a UE in idle mode, the AMF 312 may perform registration updates and / or paging the UE to transition the UE to connected mode.

[0070] AMF 312 may receive non-access stratum (NAS) messages transmitted according to the NAS protocol from UE 301. NAS messages relate to communications between UE 301 and the core network. Although NAS messages may be relayed to AMF 312 via AN 302, they may be described as communications via the N1 interface. NAS messages may facilitate UE registration and mobility management, for example, by authenticating, identifying, configuring and / or managing the connection of UE 301. NAS messages may support session management procedures for maintaining user plane connectivity and quality of service (QoS) for sessions between UE 301 and DN 309. If the NAS message relates to session management, AMF 312 may send the NAS message to SMF 314. NAS messages may 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 may act on a specific NAS message itself, or forward the NAS message to an appropriate core network function (e.g., SMF 314, etc.).

[0071] Figure 3 The SMF 314 depicted in FIG. 314 may establish, modify and / or publish a PDU session based on the message reception and reception received at the UE 301. The SMF 314 may, for example, allocate, manage and / or assign an IP address to the UE 301 after establishing the PDU session. There may be multiple SMFs in the network, each of which may be associated with a wireless device, a base station and / or a UPF of a corresponding group. A UE with multiple PDU sessions may be associated with a different SMF for each PDU session. As described above, the SMF 314 may select one or more UPFs to process the PDU session, and may control the processing of the PDU session by the selected UPF by providing rules (PDR, FAR, QER, etc.) for packet processing. Rules related to QoS and / or charging for a specific PDU session may be obtained from the PCF 320 and provided to the UPF 305.

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

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

[0074] Figure 3 The NEF 340 depicted in FIG. 3 may provide an interface to an external domain, thereby 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 may act as a proxy between external elements and network functions such as AMF 312, SMF 314, PCF 320, UDM 350, etc. As an example, the NEF 340 may determine the location or reachability status of the UE 301 based on a report from the AMF 312, and provide the status information to the external element. As an example, the external element may provide information that facilitates setting parameters for establishing a PDU session via the NEF 340. The NEF 340 may determine which data and capabilities of the control plane are open to the external domain. The NEF 340 may provide a secure opening that authenticates and / or authorizes the data or capabilities of the communication network 300 to be opened to the external entity. The NEF 340 may selectively control the opening so that the internal architecture of the core network is hidden from the external domain.

[0075] The UDM 350 may provide data storage for other NFs. The UDM 350 may allow a consolidated view of network information, which may be used to ensure that the most relevant information may be made available to different NFs from a single resource. The UDM 350 may store and / or retrieve information from a unified data repository (UDR). For example, the UDM 350 may obtain user subscription data associated with the UE 301 from the UDR.

[0076] AUSF 360 may support mutual core network authentication of UE 301 and authentication of UE 301 to the core network. AUSF 360 may perform key agreement procedures and provide key material that may be used to improve security.

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

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

[0079] The NWDAF 390 may collect and analyze data from other network functions and provide data analysis services to other network functions. As an example, the NWDAF 390 may collect data related to the load level of a specific network slice instance from the UPF 305, the AMF 312, and / or the SMF 314. Based on the collected data, the NWDAF 390 may provide the load level data to the PCF 320 and / or the NSSF 370, and / or notify the PCF 320 and / or the NSSF 370 whether the load level of the slice reaches and / or exceeds a load level threshold.

[0080] AF 399 may be external to the core network but may interact with the core network to provide information about QoS requirements or traffic routing preferences associated with a particular application. AF 399 may access the core network based on open constraints imposed by NEF 340. However, the operator of the core network may view AF 399 as a trusted domain that may directly access the network.

[0081] Figure 4A , 4B and 5 show in some respects similar Figure 3 For the sake of brevity, other examples of core network architectures of the core network architecture 300 are omitted. Figure 3 Some core network elements depicted in . Figure 4A , 4B Many of the elements depicted in and 5 are similar in some respects to Figure 3 For the sake of brevity, some details related to their functions or operations are omitted.

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

[0083] The UPFs 405, 406, 407 may perform traffic detection, wherein the UPF identifies and / or classifies packets. Packet identification may be performed based on packet detection rules (PDRs) provided by the SMF 414. The PDR may include packet detection information including one or more of the following: a source interface, a UE IP address, core network (CN) tunnel information (e.g., a CN address of an N3 / N9 tunnel corresponding to a PDU session), a network instance identifier, a quality of service flow identifier (QFI), a filter set (e.g., an IP packet filter set or an Ethernet packet filter set), and / or an application identifier.

[0084] In addition to indicating how a particular packet will be detected, the PDR may further indicate rules for handling the packet after the packet is detected. The rules may include, for example, forwarding action rules (FARs), multiple access rules (MARs), usage reporting rules (URRs), QoS enforcement rules (QERs), etc. For example, the PDR may include one or more FAR identifiers, MAR identifiers, URR identifiers, and / or QER identifiers. These identifiers may indicate rules that are specified for handling a particular packet that is detected.

[0085] The UPF 405 may perform traffic forwarding based on the FAR. For example, the FAR may indicate that packets associated with a particular PDR will be forwarded, copied, discarded, and / or buffered. The FAR may indicate a destination interface, such as "access" for a downlink or "core" for an uplink. If a packet is to be buffered, the FAR may indicate a buffer action rule (BAR). As an example, the UPF 405 may perform data buffering of a specific number of downlink packets in the case of a PDU session being released.

[0086] UPF 405 may perform QoS enforcement based on the QER. For example, the QER may indicate an authorized guaranteed bit rate and / or a maximum bit rate to be enforced for packets associated with a particular PDR. The QER may indicate that a particular guaranteed and / or maximum bit rate may be used for uplink packets and / or downlink packets. UPF 405 may mark packets belonging to a particular QoS flow with a corresponding QFI. The marking may enable the receiver of the packet to determine the QoS of the packet.

[0087] UPF 405 may provide the usage report to SMF 414 based on the URR. The URR may indicate one or more trigger conditions for the generation and reporting of the usage report, such as immediate reporting, periodic reporting, a threshold for incoming uplink traffic, or any other suitable trigger condition. The URR may indicate a method for measuring the usage of network resources, such as data volume, duration, and / or event.

[0088] As described above, DN 408, 409 may include a public DN (e.g., the Internet), a private DN (e.g., a private, internal company-owned DN), and / or an intra-operator DN. Each DN may provide operator services and / or third-party services. The services provided by the DN may be the Internet, an IP Multimedia Subsystem (IMS), an augmented or virtual reality network, an edge computing or mobile edge computing (MEC) network, etc. Each DN may be identified using a data network name (DNN). UE 401 may be configured to establish a first logical connection (a first PDU session) with DN 408, a second logical connection (a second PDU session) with DN 409, or both (a first and a second PDU session) at the same time.

[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 with the DN.

[0090] exist Figure 4AIn the example of , UPF 405 may be an anchor for a first PDU session between UE 401 and DN 408, and UPF 406 may be an anchor for a second PDU session between UE 401 and DN 409. The core network may use anchors to provide service continuity (e.g., IP address continuity) for a particular PDU session as UE 401 moves from one access network to another. For example, assume that UE 401 establishes a PDU session using a data path to DN 408 using an access network other than AN 402. The data path may include UPF 405 acting as an anchor. Further assume that UE 401 later moves into the coverage area of ​​AN 402. In this scenario, SMF 414 may 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 as any number of UPFs are added or removed from the data path. Figure 4A As shown, it can be described as an intermediate UPF and / or a cascaded UPF.

[0091] As described above, UPF 406 may be the anchor for the second PDU session between UE 401 and DN 409. Figure 4A The anchors for the first and second PDU sessions in FIG. 4 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 may correspond to any number of anchors. When multiple UPFs are present, the UPF at the branch point (UPF 407 in FIG. 4) may operate as an uplink classifier (UL-CL). The UL-CL may divert uplink user plane traffic to different UPFs.

[0092] SMF 414 may allocate, manage and / or assign an IP address to UE 401, for example, after establishing a PDU session. SMF 414 may maintain an internal pool of IP addresses to be assigned. If necessary, SMF 414 may assign an IP address provided by a Dynamic Host Configuration Protocol (DHCP) server or an Authentication, Authorization and Accounting (AAA) server. IP address management may be performed according to a Session and Service Continuity (SSC) mode. In SSC Mode 1, the IP address of UE 401 may be maintained as the wireless device moves within the network (and the same anchor UPF may 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 may be discarded, and a new IP address and anchor UPF may be established). In SSC Mode 3, it is possible to temporarily maintain the old IP address (similar to SSC Mode 1) while establishing a new IP address (similar to SSC Mode 2), thus combining the features of SSC Modes 1 and 2. Applications that are sensitive to IP address changes can operate according to SSC Mode 1.

[0093] UPF selection may be controlled by SMF 414. For example, after establishing and / or modifying a PDU session between UE 401 and DN 408, SMF 414 may select UPF 405 as an 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, slice support, and / or other capabilities of candidate UPFs may also be considered.

[0094] Figure 4B An example of a core network architecture 400B that accommodates untrusted access is shown. Figure 4A ,like Figure 4B 408 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 a non-3GPP network interworking function (N3IWF) 404.

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

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

[0097] UE 501 may not be a subscriber of the VPLMN. AMF 512 may authorize UE 501 to access the network based on, for example, roaming restrictions imposed on UE 501. In order to obtain network services provided by the VPLMN, the core network of the VPLMN may have to interact with the core network elements of the HPLMN of UE 501, specifically PCF 521, NRF 531, NEF 541, UDM 551 and / or AUSF 561. The VPLMN and the HPLMN may communicate using the N32 interface connected to the corresponding security edge protection proxy (SEPP). Figure 5, the corresponding SEPPs are depicted 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 of NFs in the corresponding PLMN. 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 can handle all authentication and subscription-related signaling. For example, when UE 501 registers or requests services via VPLMN, VPLMN can authenticate UE 501 and / or obtain subscription data of UE 501 by accessing UDM 551 and AUSF 561 of HPLMN via SEPP.

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

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

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

[0102] The 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 affected by the nature of the network elements themselves (e.g., processing power, availability of free memory, proximity to other network elements, etc.) or their management (e.g., optimized to maximize bit rate or reliability, reduce latency or power bandwidth usage, etc.). The characteristics of the network architecture 600A may change over time, such as by upgrading equipment or by modifying programs to target specific characteristics. However, at any given time, the 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, 601C may have different requirements, but the 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 the example, the physical network is divided into three logical networks, referred to as slice A, slice B, and slice C. For example, UE 601A may be served by AN 602A, UPF 605A, AMF 612, and SMF 614A. UE 601B may be served by AN 602B, UPF 605B, AMF 612, and SMF 614B. UE 601C may be served by AN 602C, UPF 605C, AMF 612, and SMF 614C. Although from a logical perspective, the respective UEs 601 communicate with different network elements, these network elements may be deployed by the network operator using the same physical network elements.

[0104] Each network slice may be customized for a network service with a different set of characteristics. For example, slice A may correspond to an enhanced mobile broadband (eMBB) service. Mobile broadband may refer to Internet access by mobile users, typically associated with smartphones. Slice B may correspond to ultra-reliable low-latency communications (URLLC), which focuses on reliability and speed. Relative to eMBB, URLLC may improve the feasibility of use cases such as autonomous driving and remote surgery. Slice C may correspond to massive machine type communications (mMTC), which focuses on low-power services delivered to a large number of users. For example, slice C may be optimized for a dense network 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 requirement for one of the UEs 601 changes, the network slice serving the UE may be updated to provide better service. In addition, the set of network features corresponding to eMBB, URLLC, and mMTC may vary so that differentiated types of eMBB, URLLC, and mMTC are provided. Alternatively, the network operator may provide a completely new service in response to, for example, customer demand.

[0106] Figure 6 6, each of the UEs 601 has its own network slice. However, it should be understood that a single slice may serve any number of UEs, and a single UE may operate using any number of slices. Furthermore, in the example network architecture 600B, the AN 602, UPF 605, and SMF 614 are divided into three separate slices, while the AMF 612 is non-slicing. However, it should be understood that a network operator may deploy any architecture that selectively utilizes any mix of slicing and non-slicing network elements, where different network elements are divided into different numbers of slices. Although Figure 6 Only three core network functions are depicted, but it should be understood that other core network functions may also be sliced. A PLMN supporting multiple network slices may maintain a separate network repository function (NFR) for each slice, enabling other NFs to discover network services associated with the slice.

[0107] The network slice selection may be controlled by the AMF or by a separate network slice selection function (NSSF). For example, a network operator may define and implement distinct network slice instances (NSIs). Each NSI may be associated with a single network slice selection assistance information (S-NSSAI). The S-NSSAI may include a specific slice / service type (SST) indicator (indicating eMBB, URLLC, mMTC, etc.). As an example, a specific tracking area may be associated with one or more configured S-NSSAIs. The UE may identify one or more requested and / or subscribed S-NSSAIs (e.g., during registration). The network may indicate to the UE one or more allowed and / or rejected S-NSSAIs.

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

[0109] Fig. 7A , Figure 7B and Figure 7C A user plane (UP) protocol stack, a control plane (CP) protocol stack, and services provided between protocol layers of the UP protocol stack are shown.

[0110] The layers may be associated with an open systems interconnection (OSI) model of computer networking functionality. 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 is related to the physical infrastructure (e.g., cables, optical fibers, and / or radio frequency transceivers) used to transmit signals. In a new radio (NR), layer 1 may include a physical layer (PHY). Layer 2 may correspond to a data link layer. Layer 2 may be related to packaging data (e.g., data frames) for transmission between nodes of a network using the physical infrastructure of layer 1. In NR, layer 2 may include a media access control layer (MAC), a radio link control layer (RLC), a packet data convergence layer (PDCP), and a service data application protocol layer (SDAP).

[0111] Layer 3 may correspond to the network layer. Layer 3 may be related to the routing of data that has been encapsulated in layer 2. Layer 3 may handle prioritization of data and traffic avoidance. In NR, layer 3 may include a radio resource control layer (RRC) and a non-access layer layer (NAS). Layers 4 to 7 may correspond to a transport layer, a session layer, a presentation layer, and an application layer. The application layer interacts with the end user to provide data associated with the application. In an example, an end user implementing an application may generate data associated with the application and initiate the sending of the information to a target data network (e.g., the Internet, an application server, etc.). Starting at the application layer, each layer in the OSI model may manipulate and / or repackage information and deliver it to the lower layers. At the lowest layer, the manipulated and / or repackaged information may be exchanged via a physical infrastructure (e.g., electrically, optically, and / or electromagnetically). As it approaches the target data network, the information will be decapsulated and provided to higher and higher layers until it reaches the application layer again in a form that is usable by the target data network (e.g., the same form as when it was provided by the end user). The data network may reverse this process in order to respond to the end user.

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

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

[0114] NAS may be related to the non-access layer, specifically, the communication between the UE 701 and the core network (e.g., AMF 712). The lower layer may be related to the access layer, such as the communication between the UE 701 and the gNB 702. The message sent between the UE 701 and the core network may be referred to as a NAS message. In an example, the NAS message may be relayed by the gNB 702, but the content of the NAS message (e.g., the information element of the NAS message) may not be visible to the gNB 702.

[0115] Figure 7C Shown set at Fig. 7A 772 and SDAP 773. UE 701 may receive services via a PDU session, which may be a logical connection between UE 701 and a data network (DN). UE 701 and DN may 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 may 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 the QoS flows and the data radio bearers may be determined by gNB 702 in SDAP 772, and the UE 701 may be notified of the mapping (e.g., based on control signaling and / or reflection mapping). For reflection mapping, SDAP 772 of gNB 220 may mark the downlink packet with a QoS flow indicator (QFI) and deliver the downlink packet to UE 701. UE 701 may determine the mapping based on the QFI of the downlink packet.

[0116] PDCP 761 and PDCP 762 may perform header compression and / or decompression. Header compression may reduce the amount of data transmitted on the physical layer. PDCP 761 and PDCP 762 may perform encryption and / or decryption. Encryption may reduce unauthorized decoding of data transmitted on the physical layer (e.g., intercepted on the air interface) and protect data integrity (e.g., to ensure that control messages originate from intended sources). PDCP 761 and PDCP 762 may perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, duplication of packets, and / or identification and removal of duplicate packets. In a dual connectivity scenario, PDCP 761 and PDCP 762 may perform mapping between split radio bearers and RLC channels.

[0117] RLC 751 and RLC 752 may perform segmentation, retransmission via automatic repeat request (ARQ). RLC 751 and RLC 752 may perform removal of duplicate data units received from MAC 741 and MAC 742, respectively. RLC 213 and 223 may provide RLC channels as services to PDCP 214 and 224, respectively.

[0118] MAC 741 and MAC 742 may perform multiplexing and / or demultiplexing of logical channels. MAC 741 and MAC 742 may map logical channels to transport channels. In an example, UE 701 may multiplex data units of one or more logical channels into a transport block in MAC 741. UE 701 may transmit the transport block to gNB 702 using PHY 731. gNB 702 may receive the transport block using PHY 732 and demultiplex the data units of the transport block back into the logical channels. MAC 741 and MAC 742 may perform error correction via hybrid automatic repeat request (HARQ), logical channel prioritization, and / or padding.

[0119] PHY 731 and PHY 732 may perform mapping of transport channels to physical channels. PHY 731 and PHY 732 may perform digital and analog signal processing functions (e.g., coding / decoding and modulation / demodulation) for sending and receiving information (e.g., transmitted via an air interface). PHY 731 and PHY 732 may 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 model of FIG. 801 , there are UE 801, AN 802, and UPF 805. The QoS model facilitates prioritization of certain packets or protocol data units (PDUs) (also referred to as packets). For example, higher priority packets can be switched faster and / or more reliably than lower priority packets. The network can devote more resources to switching high QoS packets.

[0121] exist Figure 8 In the example of , a PDU session 810 is established between UE 801 and UPF 805. PDU session 810 may be a logical connection that enables UE 801 to exchange data with a specific data network (e.g., the Internet). UE 801 may request to establish PDU session 810. When establishing PDU session 810, UE 801 may identify the target data network, for example, based on its data network name (DNN). PDU session 810 may be managed, for example, by a session management function (SMF, not shown). In order to facilitate the exchange of data associated with PDU session 810 between UE 801 and the data network, SMF may select UPF 805 (and optionally, one or more other UPFs, not shown).

[0122] One or more applications associated with the UE 801 may generate uplink packets 812A-812E associated with the PDU session 810. To operate within the QoS model, the UE 801 may apply QoS rules 814 to the uplink packets 812A-812E. The QoS rules 814 may be associated with the PDU session 810 and may be determined and / or provided to the UE 801 when establishing and / or modifying the PDU session 810. Based on the QoS rules 814, the UE 801 may classify the uplink packets 812A-812E, map each of the uplink packets 812A-812E to a QoS flow, and / or mark the 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 having potentially different priorities, the QFI indicates how the packets should be handled according to the QoS model. In the current illustration, uplink packets 812A, 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 flow can be the finest granularity of QoS differentiation in PDU session. In the figure, three QoS flows 816A-816C are shown. However, it should be understood that there may be any number of QoS flows. Some QoS flows may be associated with guaranteed bit rates (GBR QoS flows), and other QoS flows may have non-guaranteed bit rates (non-GBR QoS flows). QoS flows may also experience per UE and per session total bit rates. One of the QoS flows may be a default QoS flow. QoS flows may 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 may be reflected by different QoS flow characteristics. For example, QoS flows may be associated with flow bit rates. A specific QoS flow may be associated with a guaranteed flow bit rate (GFBR) and / or a maximum flow bit rate (MFBR). QoS flows may be associated with a specific packet delay budget (PDB), a packet error rate (PER), and / or a maximum packet loss rate. QoS flows may also experience per-UE and per-session aggregate bit rates.

[0124] In order to work within the QoS model, UE 801 may apply resource mapping rules 818 to QoS flows 816A-816C. The air interface between UE 801 and AN 802 may be associated with resources 820. In the current illustration, QoS flow 816A is mapped to resource 820A, while QoS flows 816B, 816C are mapped to resource 820B. Resource mapping rules 818 may be provided by AN 802. In order to meet QoS requirements, resource mapping rules 818 may specify more resources for relatively high priority QoS flows. With more resources, high priority QoS flows such as QoS flow 816A may be more likely to obtain high flow bit rates, low packet delay budgets, or other characteristics associated with QoS rules 814. Resources 820 may include, for example, radio bearers. Radio bearers (e.g., data radio bearers) may be established between UE 801 and AN 802. The 5G radio bearer between UE 801 and AN 802 may be different from the LTE bearer, such as an Evolved Packet System (EPS) bearer between the UE and a Packet Data Network Gateway (PGW), an S1 bearer between an eNB and a Serving Gateway (SGW), and / or an S5 / S8 bearer between an SGW and a PGW.

[0125] Once a packet associated with a particular QoS flow is received at AN 802 via resource 820A or resource 820B, AN 802 separates the packet into corresponding QoS flows 856A-856C based on the QoS profile 828. The QoS profile 828 may be received from the SMF. Each QoS profile may correspond to a QFI, such as the QFI marked on the uplink packets 812A-812E. Each QoS profile may include QoS parameters such as a 5G QoS identifier (5QI) and an allocation and retention priority (ARP). The QoS profile for non-GBR QoS flows may further include additional QoS parameters such as reflective QoS attributes (RQA). The QoS profile for GBR QoS flows may further include additional QoS parameters such as a guaranteed flow bit rate (GFBR), a maximum flow bit rate (MFBR) and / or a maximum packet loss rate. The 5QI may be a standardized 5QI with a one-to-one mapping of each well-known service to a standardized combination of 5G QoS characteristics. 5QI may be a dynamically assigned 5QI, for which a standardized 5QI value is not defined. 5QI may represent 5G QoS characteristics. 5QI may include resource type, default priority, packet delay budget (PDB), packet error rate (PER), maximum data burst, and / or averaging window. Resource type may indicate a non-GBR QoS flow, a GBR QoS flow, or a delay-critical GBR QoS flow. The averaging window may represent the duration over which GFBR and / or MFBR are calculated. ARP may be a priority including preemptive capability and preemptible capability. Based on ARP, AN 802 may apply admission control for QoS flows in the case of resource limitations.

[0126] AN 802 may select one or more N3 tunnels 850 for transporting QoS flows 856A-856C. After the packets are divided 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 the uplink packets 812A-812E is aligned with the QoS rules 814 provided to UE 801. UPF 805 may measure the packets and / or count the packets and / or provide the packet metrics to, for example, PCF.

[0127] The figure also shows a process for 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 rules (PDRs) 854 to downlink packets 852A-852E. Based on PDR 854, UPF 805 may map packets 852A-852E to QoS flows. In the current illustration, downlink packets 852A, 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 may be sent to AN 802. AN 802 may apply resource mapping rules to QoS flows 856A-856C. In the current illustration, QoS flow 856A is mapped to resource 820A, while QoS flows 856B, 856C are mapped to resource 820B. To meet QoS requirements, resource mapping rules may specify more resources for high priority QoS flows.

[0129] 9A to 9D Example states and state transitions of a wireless device (eg, UE) are shown. At any given time, a wireless device may have a radio resource control (RRC) state, a registration management (RM) state, and a connection management (CM) state.

[0130] Fig.9A 9 is an example diagram showing RRC state transitions of a wireless device (e.g., UE). The UE may 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). The 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 for the RRC state of each UE.

[0131] In the RRC connection 930, it is possible for the UE to exchange data with the network (e.g., a base station). Parameters necessary for data exchange may be established, and these parameters are known to both the UE and the network. Parameters may be referred to and / or included in the RRC context of the UE (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., involving 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 RRC context of the UE.

[0132] When in RRC connection 930, the mobility of the UE may be managed by the access network, while the UE itself may manage mobility when in RRC idle 910 and / or RRC inactive 920. When in RRC connection 930, the UE may manage mobility by measuring signal levels (e.g., reference signal levels) from serving cells and neighboring cells and reporting these measurements to the base station currently serving the UE. The network may initiate a handover based on the reported measurements. The RRC state may transition from RRC connection 930 to RRC idle 910 via a connection release procedure 930, and to RRC inactive 920 via a connection cancellation 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 a base station. When in RRC idle 910, the UE may be in a dormant state most of the time (e.g., to save battery power). The UE may wake up periodically (e.g., once per discontinuous reception cycle) to monitor paging messages from the access network. The mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 910 to RRC connected 930 via a connection establishment procedure 913, which may involve a random access procedure, as discussed in more detail below.

[0134] In RRC Inactive 920, the previously established RRC context is maintained in the UE and the base station. This may allow a quick transition to RRC Connected 930 with reduced signaling overhead compared to the transition from RRC Idle 910 to RRC Connected 930. The RRC state may transition to RRC Connected 930 via a Connection Recovery Procedure 923. The RRC state may transition to RRC Idle 910 via a Connection Release Procedure 921, which may be the same as or similar to a Connection Release Procedure 931.

[0135] The RRC state can be associated with a mobility management mechanism. 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 broadcasting the paging message on the entire mobile communication network. The mobility management mechanism used in RRC idle 910 and / or RRC inactive 920 can allow the network to track the UE at the cell-group level, so that the paging message can be broadcast on the cell of the cell group where the UE currently resides rather than on the entire communication network. Tracking can be based on different grouping granularities. For example, there can be three levels of cell grouping granularity: a single cell; a cell within a RAN area identified by a RAN area identifier (RAI); and a cell within a group of RAN areas referred to as tracking areas and identified by a tracking area identifier (TAI).

[0136] Tracking areas may be used to track UEs at the CN level. The CN may provide the UE with a list of TAIs associated with the UE registration area. If the UE moves through cell reselection to a cell associated with a TAI that is not included in the list of TAIs associated with the UE registration area, the UE may 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] The RAN area may be used to track the UE at the RAN level. For a UE in the RRC inactive 920 state, a RAN notification area may be assigned to the UE. The RAN notification area may include one or more cell identities, a list of RAIs, and / or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell may belong to one or more RAN notification areas. If the UE moves to a cell not included in the RAN notification area assigned to the UE through cell reselection, the UE may perform a notification area update on the RAN to update the RAN notification area of ​​the UE.

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

[0139] Fig. 9B is an example diagram showing registration management (RM) state transitions of a wireless device (eg, UE). The states are RM deregistration 940 (eg, RM-DEREGISTERED) and RM registration 950 (eg, RM-REGISTERED).

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

[0141] When the UE is in RM registration 950, the network may store the UE context of the UE and use the UE context to reach the UE when necessary. In addition, some services cannot be provided by the network unless the UE is registered. The UE may update its UE context (Registration Update Accept 955) while remaining in RM registration 950. For example, if the UE leaves one tracking area and enters another tracking area, the UE may provide the tracking area identifier to the network. The network may deregister the UE, or the UE may deregister itself (Deregister 954). For example, the network may automatically deregister the wireless device if the wireless device is inactive for a certain amount of time. After deregistration, the UE may transition to RM deregistration 940.

[0142] Fig. 9C is an example diagram showing connection management (CM) state transitions of a wireless device (e.g., UE) shown from the perspective of the wireless device. The UE can 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 stratum (NAS) signaling connection with the network. Therefore, the UE may not communicate with the core network function. The UE may transition to CM Connected 970 by establishing an AN signaling connection (AN Signaling Connection Establishment 967). This transition may be initiated by sending an initial NAS message. The initial NAS message may 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 may initiate AN signaling connection establishment by sending a service request, or the network may send a page, thereby triggering the UE to send a service request.

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

[0145] Fig.9D is an example diagram showing 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 may be in 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 may establish an N2 context of the UE (N2 context establishment 989). When the UE transitions from CM-CONNECTED 990 to CM-IDLE 980, the AMF may release the N2 context of the UE (N2 context release 998).

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

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

[0148] Registration may be initiated by the UE for the purpose of obtaining authorization to receive services, enabling mobility tracking, enabling reachability, or other purposes. The UE may perform an initial registration as the first step to connect to the network (e.g., when the UE is powered on, airplane mode is disconnected, etc.). Registration may 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 areas. Deregistration may be performed ( Fig.10 (not shown) to stop network access.

[0149] At 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 may be a NAS message. The registration request may include a UE identifier. The AN may select an AMF for registration of the UE. For example, the AN may select a default AMF. For example, the AN may select an AMF that has been mapped to the UE (e.g., a previous AMF). The NAS registration request may include a network slice identifier, and the AN may select an AMF based on the requested slice. After selecting the AMF, the AN may send the registration request to the selected AMF.

[0150] At 1020, the AMF (AMF#2) that receives the registration request performs a context transfer. The context may be a UE context, such as an RRC context of the UE. As an example, AMF#2 may send a message to AMF#1 requesting the context of the UE. The message may include a UE identifier. The message may be a Namf_Communication_UEContextTransfer message. AMF#1 may send a message containing the requested UE context to AMF#2. This message may be a Namf_Communication_UEContextTransfer message. After receiving the UE context, AMF#2 may coordinate the authentication of the UE. After the authentication is completed, AMF#2 may 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 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 authentication of the UE. 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 may be used to derive access-specific security keys for the UE, thereby enabling the AMF to perform security context management (SCM). The AUSF may obtain subscription data from the UDM. The subscription data may be based on information obtained from the UDM (and / or UDR). The subscription data may include a subscription identifier, security credentials, access and mobility related subscription data, and / or session related data.

[0152] At 1030, the new AMF (AMF#2) registers and / or subscribes to the UDM. AMF#2 may perform the registration using the UE context management service (Nudm_UECM) of the UDM. AMF#2 may obtain the subscription information of the UE using the subscriber data management service (Nudm_SDM) of the UDM. AMF#2 may further request the UDM to notify AMF#2 whether the subscription information of the UE has changed. With the new AMF registered and subscribed, the old AMF (AMF#1) may deregister and unsubscribe. After deregistration, AMF#1 has no responsibility for the mobility management of the UE.

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

[0154] For example, access and mobility policies may involve service area restrictions, RAT / frequency selection priorities (RFSP, where RAT stands for radio access technology), authorization and prioritization of access types (e.g., LTE compared to 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 the UE is allowed to be served (and prohibited from being served). Access and mobility policies may include UE route selection policies (URSP) that affect the routing of established PDU sessions or new PDU sessions. As described 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 may update the context of the PDU session. For example, if the UE has an existing PDU session, AMF#2 may coordinate with the SMF to activate the user plane connection associated with the existing PDU session. The SMF may update and / or release the session management context of the PDU session (Nsmf_PDUSession_UpdateSMContext, Nsmf_PDUSession_ReleaseSMContext).

[0156] At 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 include the new UE identifier and / or the 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 may confirm receipt of the new UE identifier and / or the new configured slice identifier.

[0157] At 1070, AMF#2 may obtain UE policy control information from PCF. PCF may provide an access network discovery and selection policy (ANDSP) to facilitate non-3GPP access. PCF may provide a UE route selection policy (URSP) to facilitate mapping of specific data services to specific PDU session connectivity parameters. As an example, the URSP may 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] Fig.11 An example of a service request procedure for a wireless device (eg, UE) is shown. Fig.11 The service request procedure depicted in is a network-triggered service request procedure for a UE in CM-IDLE state. Fig.11Other service request procedures (eg, UE-triggered service request procedures) are understood, as 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 the 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 N1N2 messaging 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. The determination at 1120 may be in response to receiving the PDU session information. Based on the determination that the UE is in CM-IDLE, the service request procedure may proceed to 1130 and 1140, as shown in FIG. Fig.11 However, if the UE is not in CM-IDLE (eg, the UE is in CM-CONNECTED), 1130 and 1140 may be skipped, and the service request procedure may proceed directly to 1150.

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

[0162] At 1140, the UE may request a service. The UE may transmit the service request to the AMF via the AN. Fig.11 , the UE may request service at 1140 in response to receiving the paging at 1130. However, as described 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 may start a UE-triggered service request procedure. The UE-triggered service request procedure may start at 1140.

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

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

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

[0166] In the case of a UE-triggered service request procedure, the UE may receive a NAS service accept message from the AMF via the AN at 1170. After configuring the user plane resources, the UE may transmit uplink data (eg, uplink data that causes the UE to trigger the service request procedure).

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

[0168] Based on the update of the session management context, the SMF may update the PCF for policy control purposes. For example, if the location of the UE has changed, the SMF may inform the PCF of the new location of the UE.

[0169] Based on the update of the session management context, the SMF and the UPF may perform session modification. The session modification may be performed using an N4 session modification message. After the session modification is completed, the UPF may 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 the downlink data may be based on the one or more AN tunnel endpoint identifiers of the AN.

[0170] Fig.12 An example of a protocol data unit (PDU) session establishment procedure for a wireless device (eg, UE) is shown. The UE may determine to transmit a PDU session establishment request to create a new PDU session, to handover an existing PDU session to a 3GPP network, or for any other suitable reason.

[0171] At 1210, the UE initiates a PDU session establishment. The UE may transmit a 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: a PDU session ID; a requested PDU session type (new or existing); a requested DN (DNN); a requested network slice (S-NSSAI); a 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 may select an SMF based on the 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 context of the UE, 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 may 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 may be selected based on determining that the SMF can manage the PDU session associated with the specific DNN and / or S-NSSAI.

[0173] At 1220, the network manages the context of the PDU session. 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 a Nsmf_PDUSession_CreateSMContext request and / or a Nsmf_PDUSession_UpdateSMContext request. The PDU session context request may indicate an identifier of the UE; a requested DN; and / or a 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 session management subscription data of the UE. The SMF may subscribe to updates to the subscription data so that the PCF will send new information if the UE's subscription data changes. After obtaining the UE's subscription data, the SMF may transmit a PDU session context response to the AMG. The PDU session context response may be a Nsmf_PDUSession_CreateSMContext response and / or a Nsmf_PDUSession_UpdateSMContext response. The PDU session context response may include a session management context ID.

[0174] At 1230, secondary authorization / authentication may be performed if necessary. Secondary authorization / authentication may involve UE, AMF, SMF, and DN. SMF may access DN via a data network authentication, authorization, and accounting (DN AAA) server.

[0175] At 1240, the network sets up a data path for uplink data associated with the PDU session. The SMF may select a PCF and establish a session management policy association. Based on the association, the PCF may provide an initial set of policy control and charging rules (PCC rules) for the PDU session. When targeting a specific PDU session, the PCF may indicate to the SMF a method for assigning an IP address to the PDU session, a default charging method for the PDU session, an address of a corresponding charging entity, a trigger for requesting a new policy, etc. The PCF may also target a service data flow (SDF) that includes one or more PDU sessions. When targeting an SDF, the PCF may indicate to the SMF a policy for applying QoS requirements, monitoring services (e.g., for charging purposes) and / or diverting services (e.g., by using one or more specific N6 interfaces).

[0176] The SMF may determine and / or allocate IP addresses for PDU sessions. The SMF may select one or more UPFs (in Fig.12In the example of FIG. 1 , a single UPF) is used to handle the PDU session. The SMF may send an N4 session message to the selected UPF. The N4 session message may be an N4 session establishment request and / or an N4 session modification request. The N4 session message may include packet detection, enforcement, and reporting rules associated with the PDU session. In response, the UPF may confirm by sending an N4 session establishment response and / or an N4 session modification response.

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

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

[0179] After setting up the data path for uplink data at 1240, the UE may optionally send uplink data associated with the PDU session. Fig.12 As shown in , uplink data can be sent via the AN and UPF to the DN associated with the PDU session.

[0180] At 1250, the network may update the PDU session context. The AMF may transmit a PDU session context update request to the SMF. The PDU session context update request may be a Nsmf_PDUSession_UpdateSMContext request. The PDU session context update request may include N2 session management information received from the AN. The SMF may confirm the PDU session context update. The confirmation may be a Nsmf_PDUSession_UpdateSMContext response. The confirmation may include a subscription requesting notification of any UE mobility events to the SMF. Based on the PDU session context update request, the SMF may send an N4 session message to the UPF. The N4 session message may be an N4 session modification request. The N4 session message may include tunneling endpoint information of the AN. The N4 session message may include forwarding rules associated with the PDU session. In response, the UPF may confirm by sending an N4 session modification response.

[0181] After the UPF receives the tunneling endpoint information of the AN, the UPF may relay the downlink data associated with the PDU session. Fig.12 As shown in , downlink data can be received from the DN associated with the PDU session via the AN and UPF.

[0182] Fig.13 An example of an assembly of elements in a communication network is shown. Fig.13 A physical deployment 1330 (hereinafter "deployment 1330") including 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 as the wireless device 1310. Any other base station (or any portion 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 as the base station 1320. Any physical core network deployment (or any portion thereof, depending on the architecture of the base station) in this disclosure may have similar components and may be implemented in a similar manner as the deployment 1330.

[0183] Wireless device 1310 may communicate with base station 1320 via air interface 1370. The direction of communication from wireless device 1310 to base station 1320 via air interface 1370 is referred to as uplink, and the direction of communication from base station 1320 to wireless device 1310 via air interface 1370 is referred to as downlink. Downlink transmissions may be separated from uplink transmissions using some combination of FDD, TDD, and / or duplexing techniques. Fig.13 A single wireless device 1310 and a single base station 1320 are shown, but it is understood that the wireless device 1310 can communicate with any number of base stations or other access network components via the air interface 1370, and the base station 1320 can communicate with any number of wireless devices via the 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 include 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 include 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 an 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. Fig.13 As shown in , wireless device 1310 may communicate with base station 1320 using transmit processing system 1314 and / or receive processing system 1315. Alternatively, transmit processing system 1314 and receive processing system 1315 may be implemented as a single processing system, or both may be omitted, and all processing in wireless device 1310 may be performed by processing system 1311. Although Fig.13 1314 and / or the receive processing system 1315 may be coupled to a dedicated memory that is similar to but separate from the memory 1312 and includes instructions that may 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 to access the air interface 1370.

[0185] The wireless device 1310 may include one or more other elements 1319. The one or more other elements 1319 may include software and / or hardware that provides features and / or functionality, such as a speaker, a microphone, a keypad, a display, a touch pad, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, a global positioning sensor (GPS), etc.). The wireless device 1310 may receive user input data from the one or more other elements 1319 and / or provide user output data to the one or more other elements. The one or more other elements 1319 may include a power source. The wireless device 1310 may receive power from the power source and may be configured to distribute power to other components in the 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] The wireless device 1310 may transmit uplink data to the base station 1320 and / or receive downlink data from the base station via the air interface 1370. To perform transmission and / or reception, one or more of the processing system 1311, the transmission processing system 1314, and / or the reception system 1315 may implement open system interconnection (OSI) functionality. As an example, the transmission processing system 1314 and / or the reception system 1315 may perform layer 1 OSI functionality, and the processing system 1311 may perform higher layer functionality. The wireless device 1310 may transmit and / or receive data via the air interface 1370 using one or more antennas 1316. For scenarios where the one or more antennas 1316 include multiple antennas, the multiple antennas may 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 a processing system 1321 and a 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 include 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 include 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 Fig.13 1320. Although not shown, the transmit processing system 1324 and / or the receive processing system 1325 may be coupled to a dedicated memory that is similar to but separate from the memory 1322 and includes instructions that may 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 to access the air interface 1370.

[0188] The base station 1320 may transmit downlink data to the wireless device 1310 and / or receive uplink data from the wireless device via the air interface 1370. To perform transmission and / or reception, one or more of the processing system 1321, the transmission processing system 1324, and / or the reception system 1325 may implement OSI functionality. As an example, the transmission processing system 1324 and / or the reception system 1325 may perform layer 1 OSI functionality, and the processing system 1321 may perform higher layer functionality. The base station 1320 may transmit and / or receive data via the air interface 1370 using one or more antennas 1326. For scenarios where the one or more antennas 1326 include multiple antennas, the multiple antennas may 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 suitable for communicating via interface 1380. Fig.1313, interface 1380 connects base station 1320 to a single deployment 1330, but it should be understood that wireless device 1310 can communicate with any number of base stations and / or CN deployments via interface 1380, and deployment 1330 can 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 one or more other elements 1319.

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

[0191] One or more of the 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 one or more processors may include, for example, a general purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and / or other programmable logic devices, discrete gates and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. One or more of the 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 may enable the wireless device 1310, the base station 1320, and / or the deployment 1330 to operate in a mobile communication system.

[0192] Many elements described in the disclosed embodiments can be implemented as modules.Modules are defined here as elements that perform defined functions and have defined interfaces to other elements.Modules described in the present disclosure can be implemented with hardware, software, firmware, wetware (for example, hardware with biological elements) or combinations thereof in conjunction with hardware, all of which can be equivalent in behavior.For example, a module can be implemented as a software routine written in a computer language, which is configured to be performed 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 LabVIEWMathScript.It is possible to implement a module using physical hardware that is incorporated with 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 often programmed using a hardware description language (HDL), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configures the connections between less functional internal hardware blocks on the programmable device. The mentioned techniques are often used in combination to achieve the results of the functional blocks.

[0193] The wireless device 1310, the base station 1320 and / or the deployment 1330 may implement a timer and / or a counter. The timer / counter may be started at an initial value. As used herein, starting may include restarting. Once started, the timer / counter may run. The operation of the timer / counter may be associated with an event. When an event occurs, the value of the timer / counter may change (e.g., increase or decrease). The event may be, for example, an exogenous event (e.g., receiving a signal, measuring a condition, etc.), an endogenous event (e.g., transmitting a signal, calculating, comparing, performing an action or making a decision so performed, etc.), or any combination thereof. In the case of a timer, the event may be the passage of a specific amount of time. However, it should be understood that the timer may be described and / or implemented as a counter that counts the passage of a specific unit of time. The timer / counter may run 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 expiration of the timer / counter. The final value may be referred to as a threshold. The timer / counter may be suspended, wherein the current value of the timer / counter is maintained, maintained and / or continued, even after one or more events that would otherwise change the value of the timer / counter occur. The timer / counter may unpause or continue, wherein the value maintained, maintained and / or continued begins to change again when the one or more events occur. The timer / counter may be set and / or reset. As used herein, setting may include resetting. When setting and / or resetting the timer / counter, the value of the timer / counter may be set to an initial value. The timer / counter may be started and / or restarted. As used herein, starting may include restarting. In some embodiments, when the timer / counter is restarted, the value of the timer / counter may be set to an initial value and the timer / counter may begin to run.

[0194] Fig.14A , 14B , 14C and 14D show various example arrangements of physical core network deployments each having one or more network functions or portions thereof. The core network deployments include deployment 1410, deployment 1420, deployment 1430, deployment 1440 and / or deployment 1450. Each deployment may be similar to Fig.131330 depicted in . 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 specific set of functionalities and / or one or more physical elements configured to perform those functionalities (e.g., a processing system and memory including instructions that, when executed by a processing system, cause the processing system to perform the functionality). For example, in the present disclosure, when a network function is described as performing X, Y, and Z, it should be understood that this means that 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, a network element, and / or a network device.

[0195] As will be discussed in more detail below, there are many different types of NFs, and each type of NF may be associated with a different set of functionality. Multiple different NFs may be flexibly deployed at 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 may be flexibly deployed at different locations (implemented using different physical core network deployments) or in the same location. In addition, a physical core network deployment may also implement one or more base stations, application functions (AFs), data networks (DNs), or any portion thereof. NFs may 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] Fig.14A An example arrangement of core network deployments is shown, where each deployment includes one network function. Deployment 1410 includes NF 1411, deployment 1420 includes NF 1421, and deployment 1430 includes NF 1431. Deployments 1410, 1420, 1430 communicate via interface 1490. Deployments 1410, 1420, 1430 may have different physical locations with different signal propagation delays relative to other network elements. The diversity of physical locations of deployments 1410, 1420, 1430 may enable services to be provided to a wide area with improved speed, coverage, security, and / or efficiency.

[0197] Fig. 14B An example arrangement is shown where a single deployment includes more than one NF. Fig.14A (where each NF is deployed in a separate deployment), Fig. 14BMultiple NFs are shown in deployments 1410, 1420. In an example, deployments 1410, 1420 may implement software defined networking (SDN) and / or network function virtualization (NFV).

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

[0199] exist Fig. 14B Elsewhere in the figure, the deployment 1420 includes NF 1421 and additional network functions NF 1422. NF 1421, 1422 may be different NF types. Similar to NF 1411, 1411A, NF 1421, 1422 may be co-located within the same deployment 1420, but implemented separately. As an example, a first PLMN may own and / or operate a deployment 1420 having NF 1421, 1422. As another example, the first PLMN may implement NF 1421, and the second PLMN may obtain (e.g., rent, lease, obtain, etc.) at least a portion of the capabilities of the deployment 1420 (e.g., processing power, data storage, etc.) from the first PLMN in order 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 the deployment 1420. When multiple NFs are provided at a single deployment, the network may operate at greater speed, coverage, security, and / or efficiency.

[0200] Fig. 14C An example arrangement of a core network deployment is shown, in which a single instance of a NF is implemented using multiple different deployments. Specifically, a single instance of NF 1422 is implemented at deployments 1420, 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 distributing the implementation of the sub-services of a single NF across different physical locations, the mobile communication network can operate at greater speed, coverage, security and / or efficiency.

[0201] Fig.14D An example arrangement of a core network deployment is shown, in which one or more network functions are implemented using data processing services. Fig.14D In the embodiment, NFs 1411, 1411A, 1421, 1422 are included in a deployment 1450 implemented as a data processing service. The deployment 1450 may include, for example, a cloud network and / or a data center. The deployment 1450 may be owned and / or operated by a PLMN or by a non-PLMN third party. The NFs 1411, 1411A, 1421, 1422 implemented using the deployment 1450 may belong to the same PLMN or to different PLMNs. The PLMN may obtain (e.g., rent, lease, acquire, etc.) at least a portion of the capabilities of the deployment 1450 (e.g., processing power, data storage, etc.). By providing one or more NFs using data processing services, the mobile communication network may operate at a 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 the present disclosure, the sending and receiving of messages between different network elements is not limited to inter-deployment transmission or intra-deployment transmission, unless explicitly indicated.

[0203] In an example, a deployment may be a 'black box' that is pre-configured with one or more NFs and pre-configured to communicate with other 'black box' deployments (e.g., via interface 1490) in a prescribed manner. Additionally or alternatively, a deployment may be configured to operate according to open source instructions (e.g., software) designed to implement the NFs and communicate with other deployments in a transparent manner. A deployment may operate according to an open RAN (O-RAN) standard.

[0204] To obtain a connection service, the UE may select a network for which the UE performs a registration procedure. The UE may attempt to register with the selected network. For example, when the UE is turned on, the UE may perform network selection to select a network for registration. For network selection, the UE may determine one or more candidate networks, the UE may select a network among the one or more candidate networks, and / or the UE may attempt to register with the selected network.

[0205] For determining one or more candidate networks, the UE may use a selection list of networks, information of the UE's home network, etc. The selection list of networks may include information of one or more networks, may indicate priority information of one or more networks, and / or may include information of one or more access technologies for one or more networks. For example, the one or more information of one or more access technologies may include one or more identifiers of 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 an example, when the UE is turned on, the UE may select a home network to which the UE has a subscription. Based on the selection, the UE may 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, the UE may attempt to register with the home network. If the UE does not find one or more cells of the selected home network, the UE may use a selection list of networks. If the registration attempt for the selected home network fails, the UE may use a selection list of networks. For example, the UE may select a first network (e.g., a first prioritized network) in one or more networks indicated by the list of networks. For the selected network (e.g., the first prioritized network), the UE may attempt a cell search for the selected network and / or register with the selected network. If a cell of the selected network is not available and / or if the UE fails to register with the selected network, the UE may select a second network (e.g., a second prioritized network) in one or more networks indicated by the list of networks. The UE may search for one or more cells of the second network and / or may attempt to register with the second network. If the cell search and / or registration fails, the UE may select another network in one or more networks indicated by the list of networks. This iteration may continue until the UE successfully registers with the network.

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

[0208] In an embodiment, the coverage of the network may not cover one or more areas where the UE may be located. For example, the one or more areas may include an area of ​​a stadium, an area of ​​a theater, an area of ​​a private property, an area of ​​a shopping mall, etc. In one example, the management of the theater may decide not to allow the network to have a base station of the network within the theater. If the network does not have a base station within the theater, the network may not provide connection services to the UE. Due to the lack of base stations within the theater, the coverage of the network may not include the area within the theater. In one example, the stadium may be located in a remote area where there are no users most of the time. Based on the absence of users, the network may determine not to deploy base stations near the stadium. In one example, the owner of the shopping mall may not allow the network to install base stations within the shopping mall.

[0209] Fig.16

[0013] Example implementations are depicted in which one or more networks may provide connectivity services to UEs in one or more regions.

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

[0211] In an example, a UE (UE 1) may be a subscriber of a network (Network A). The network (Network A) may be the home network of the UE (UE 1). For example, the UE (UE 1) may be associated with a theater, a stadium, and / or a shopping mall. For example, a user of the UE (UE 1) may be the owner of a theater, may have a ticket to a game at the stadium, and / or may be a customer of a shopping mall. Based on the association, the management of the theater, the operator of the stadium, and / or the owner of the shopping mall may allow the UE to use the connection services provided by the hosted network. Based on the subscription to the network (Network A), if the UE is within the coverage of the network (Network A), the UE may use the connection services provided by the network. Based on the authorization to the hosted network, if the UE is within the coverage of the hosted network, the UE may use the connection services provided by the hosted network.

[0212] Fig.17 An example implementation is depicted in which a UE moves from location A to location C via location B. For example, location A may be within the coverage of a serving network, location B may be within the coverage of a first hosted network (e.g., hosted network 1), and / or location C may be within the coverage of a second hosted network (e.g., hosted network 2). The coverage of the first hosted 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 hosted network may not include location C. When the UE is in the coverage of the serving network (e.g., location A), the UE may use connection services via the serving network. For example, the first hosted network may allow the UE to use connection services from the first hosted network, and / or the second hosted network may not allow the UE to use connection services from the second hosted network.

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

[0214] In the prior art, the UE may not know when the UE is allowed to use one or more hosted networks (e.g., the first hosted network). In one embodiment, the UE may start searching for one or more cells at a location where one or more hosted networks (e.g., the first hosted network) are not available. For example, the UE may start searching / measuring / detecting one or more cells of the first hosted network at location A. Considering that location A is not within the coverage of the first hosted network, the UE may not find the cells of the first hosted network, and the UE may consume battery power. In the prior art, the UE may waste power resources to search for cells that may not be available.

[0215] In the prior art, the UE may not know where the UE is allowed to use one or more hosted networks. In one embodiment, after the UE experiences a connection service interruption, the UE may start searching for one or more cells. For example, when moving along a line from location A to location B, the UE may not start searching / measuring / detecting cells of the first hosted network. For example, when the UE approaches location B1 and / or moves out of the coverage of the serving network, the UE may lose connectivity to the serving network without preparing connectivity to the first hosted network. The loss of connectivity may reduce the quality of service to the UE.

[0216] In the prior art, a UE may attempt to establish connectivity to a hosted network that does not allow the UE to connect. For example, at location C, when the UE loses connectivity to the first hosted network, the UE may detect that it is within the coverage of the second hosted network. Based on the absence of other available networks, the UE may attempt to establish connectivity with the second hosted network. Because the UE is not allowed to obtain connection services from the second hosted network, the UE's access attempt to the second hosted network may be rejected and may cause signaling congestion to the second hosted network.

[0217] like Fig.18As depicted, the exemplary embodiments of the present disclosure improve system efficiency by enhancing signaling for network access information. For example, based on activation information of the network access information (e.g., time / location conditions), the UE can determine whether / when / where the UE can use the network access information. For example, based on information of one or more networks in the network access information and / or based on activation information, the UE can efficiently search for connectivity of one or more networks and / or can select a network for registration. The use of network access information can reduce unnecessary searches for networks (e.g., hosted networks), can reduce unnecessary measurements of one or more cells, and / or can improve the power efficiency of the UE. Through signaling exchanges between one or more network nodes and / or UEs, the exemplary embodiments of the present disclosure can reduce attempts by the UE to register with a hosted network, which is not allowed for the UE. The exemplary embodiments can help the network build network access information. For example, based on network access assistance information from an AF and / or a hosted network, one or more core network nodes can determine information and / or activation information of one or more networks. The exemplary embodiments can help the NG-RAN determine when to configure measurements for the UE, when to perform handover of the UE, and / or which network to perform handover to. Example embodiments may support reduction of connection interruptions and selection of an appropriate network for host network access.

[0218] In the specification, the home network may be interpreted as a network to which the UE has a subscription. The home network may be a primary network that may store and manage the information of the UE, may generate the charging / billing information of the UE, and / or may issue a security context (e.g., USIM, security key) for the UE. For example, the information of the UE may include at least one of an identifier of the UE and / or a credential of the UE. For example, the credential may include a key value shared by the UE and the home network for authentication of the UE. For example, an identifier of the UE (e.g., a telephone number, a mobile station integrated services digital network, IMEI, IMSI, SUCI, SUPI, etc.) may be used by one or more networks to identify the UE and / or may be a number assigned to the UE that others may use to contact the UE.

[0219] In the specification, a serving network may be interpreted as a network that the UE has registered with. For example, when the UE registers with a first network, the first network may be the serving network of the UE. When the UE registers with a second network, the second network may be the serving network of the UE. When the UE deregisters from the first network, the first network may not be the serving network of the UE. For example, if the serving network of the UE is not the home network of the UE, the serving network may retrieve the information of the UE from the home network of the UE.

[0220] In the specification, a hosted network may be interpreted as a network that provides connection services to UEs that have subscriptions to other networks other than the hosted network. For example, the hosted network of the UE may be a network other than the home network of the UE. For example, the first UE may 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 the second UE may 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 may provide connection services to the second UE. For the second UE, the second network may be a home network and / or the first network may be a hosted network. The second network may determine not to provide connection services to the first UE. For the first UE, the first network may be a home network and / or the second network may be neither a hosted network nor a home network. For the UE, a third party (e.g., not the first network nor the second network) may determine whether the UE can access the hosted network (e.g., the first network, the second network). For example, a third party (e.g., a service provider, a theater management, a store owner, a stadium operator) may allow a second UE to use a hosted network (e.g., a first network) and / or may request that the hosted network provide a connection service to the second UE. For example, before the UE can access the hosted network, the hosted network (e.g., a first network) may have information of the UE (e.g., a second UE) and / or may pre-authorize access to the UE. For example, the hosted network may not be a public network and / or may allow access from UEs with specific restrictions (e.g., the owner of a business, a customer of a store, a visitor of a theater, etc.).

[0221] In the specification, network access information may be interpreted as information for selecting a network (e.g., a hosted network). For example, network access information may 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, and the like. The UE may use network access information to select a network to attempt registration. For example, the UE may select a network for registration. For example, the UE may select a network to search / detect a cell of the network. For example, the UE may select a network based on one or more cells associated with one or more detected cells. For example, based on activation information of the network access information, the UE may determine when and / or where to use network access information and / or a network list. Based on the network access information, the UE may 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, the UE may switch from using the first network access information to using the second network access information. For example, the network access information may include SOR information (guidance of roaming information), a list of preferred network / access technology combinations, a list of allowed networks, a security package, a SoR transparent container, and / or access and mobility subscription data. For example, the network access information may include information of one or more networks that the UE may access. For example, the information of one or more networks may include information of one or more hosted networks.

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

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

[0224] In the specification, network access assistance information may be interpreted as information used to assist a network node in determining 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 may determine and / or construct network access information.

[0225] In the specification, mobility assistance information may be interpreted as information indicating one or more networks that the UE can use and / or to which the access node can handover the UE. For example, an access node (e.g., NG-RAN) may use mobility assistance information to determine one or more networks for which the access node can establish a measurement configuration, a network to which the access node can handover the UE, and / or a network that the UE can access. For example, the mobility assistance information may include information about when and / or where the mobility assistance information can be used. The information about when and / or where may be activation information. Based on the information about when and / or where, the access node may determine when to use the mobility assistance information and / or in which area to use the mobility assistance information. For example, the mobility assistance information may include information about one or more networks that the UE can use. For example, one or more networks may include one or more hosted 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 the specification, the term of core network node may be interpreted as a core network device, which may include at least one of AMF, SMF, NSSF, UPF, NRF, UDM, PCF, SoR-AF, AF, etc. The term of core network may be interpreted as a core network node. In the specification, the term of access node may be interpreted as a base station that may include NG-RAN, etc. In the specification, the term of network node may be interpreted as a core network node, access node, UE, etc.

[0228] In the specification, AF (application function) may be interpreted as a network node, an application, a third party and / or an application server. For example, an AF may send a request to a network node and / or may receive a response from a network node. For example, a first network node of a first network may send a request to a second network node of a second network and / or receive a request from a second network node of a second network. For example, the second network may regard the first network node as an AF.

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

[0230] Fig.19 An example implementation of the present disclosure is depicted. In an example, a 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 an example, the UE may send a NAS message (e.g., a UL NAS message, a registration request message, etc.) to a network node (e.g., AMF, PCF, UDM, SoR-AF, etc.). The NAS message may include an indication that the UE supports eSOR (enhanced roaming steering) capability. The eSOR capability may indicate that the UE supports processing network access information, sending network access information requests, receiving network access information, processing activation information, etc. For example, the eSOR capability may help the network node determine whether the network access information needs to be delivered to the UE.

[0232] In an example, a first network node (e.g., AMF) may receive a NAS message sent by a UE. Based on the NAS message including the eSOR capability, the first network node may send a policy request (e.g., Npcf_AMPolicyControl_Create request, Npcf_AMPolicyControl_Update request) message including the eSOR capability to a second network node (e.g., PCF). Based on the eSOR capability, the second network node may determine whether to provide a service of network access information to the UE. For example, the service of network access information may be information of providing network access information to the UE and / or handling / processing network access information. For example, if the UE subscribes to the service of network access information, the second network node may determine the service of providing network access information to the UE. For example, if the second network node supports the service of network access information, the second network node may determine the service of providing network access information to the UE. For the received policy request message, the second network node may send a policy response (e.g., Npcf_AMPolicyControl_Create response, Npcf_AMPolicyControl_Update response) message to the first network node. For example, the policy response message may include an indication of supporting network access information. The indication of supporting network access information may indicate whether the network node (eg, the second network node) can provide a network access information service to the UE, whether the network node can generate the network access information of the UE, etc. The first network node may receive a policy response sent by the second network node.

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

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

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

[0236] In an example, based on whether the UE supports the eSOR capability, the network node may send the network access information to the UE. For example, if the UE sends the eSOR capability to the network, the network may send the network access information to the UE. For example, if the UE does not send the eSOR capability to the network, the network may not send the network access information to the UE. If the UE supports the eSOR capability and / or if the network provides a service for the network access information, the network node may apply Figures 20 to 34 The example shown in .

[0237] Fig. 20 An example implementation of the present disclosure is depicted.In an example, an application function may provide network access assistance information to a network node.

[0238] In an example, an AF (e.g., an application, an entity having an agreement with a network to use the network, an entity that manages credentials for accessing a network, an entity that manages a network, a network node that hosts a network, etc.) may determine that a UE is allowed to use a connection service from a network (e.g., a hosted network). For example, a user of the UE may establish a contract for a connection service with the AF. Based on determining to provide the connection service to the UE, the AF may send a NEF service request message to a network node (e.g., NEF, SoR-AF) to deliver assistance information associated with directing the UE to the network. For example, in order to determine a network node and / or a network associated with the network node, the AF may collect from the UE information about networks to which the UE may have subscribed, information about the UE, information about the UE's home network, information about the UE's service network, etc. The network node may belong to the UE's home network and / or the UE's service network.

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

[0240] -UE list information: The UE list information may indicate one or more identifiers of one or more UEs to which the NEF service request message applies.

[0241] - Network list information: The network list information may indicate one or more information of one or more networks. The one or more networks may provide connection services to the one or more UEs indicated by the UE list information. The network list information may include a network list.

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

[0243] In an example, a network node (e.g., NEF) may receive a NEF service request message. In response to the received NEF service request message, the network node (e.g., NEF) may perform an authorization check to determine whether the AF is authorized to send the NEF service request message. For example, the network node (e.g., NEF) may use an identification of the AF to check whether the AF is allowed to send the NEF service request message.

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

[0245] In an example, the data management node may receive a UDM service request from a network node (e.g., NEF). For the UDM service request received from the network node (e.g., NEF), the data management node may perform a subscription check and / or a capability check. For example, the UE may not have a subscription to a service of network access information. Based on the UE not having a subscription to a service of network access information, the data management node may reject a UDM service request message from the network node (e.g., NEF). For example, the UE may have a subscription to a service of network access information. Based on the UE having a subscription to a service of network access information, the data management node may accept a UDM service request message from the network node (e.g., NEF). For example, the UE may not have a capability (e.g., eSOR capability) for a network access information service. Based on the UE not having the capability, the data management node may reject a UDM service request from the network node (e.g., NEF). For example, the UE may have the capability (e.g., eSOR capability). Based on the UE having the capability, the data management node may accept a UDM service request message from the network node (e.g., NEF).

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

[0247] In an example, the SoR-AF may store the network access assistance information of the received SoR-AF service request message and / or may process one or more information of the SoR-AF service request message. For example, the SoR-AF may 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 supported radio access technology set, a first supported frequency band set, etc.) and / or may subscribe to a first service set (e.g., eMBB service, gold service, etc.). The second UE may have a second capability (e.g., a second supported radio access technology set, a second supported frequency band set, etc.) and / or may subscribe to a first service set (e.g., IoT service, silver service, etc.). For example, based on the first capability and / or the first service set, the SoR-AF may generate first network access information for the first UE. For example, based on the second capability and / or the second service set, the SoR-AF may generate second network access information for the second UE.

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

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

[0250] In an example, a network node (e.g., NEF) may 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 may send a NEF service response (e.g., a network access assistance information provision response, a Nnef_ParameterProvision_Create response and / or a Nnef_ServiceParameter_Create response, a Nnef_ApplyPolicy_Create response, etc.) to the AF. For example, the NEF service response message may indicate a processing result (e.g., success, failure, etc.) of the NEF service request message. The result may indicate to the AF whether the AF's request is accepted / processed.

[0251] Fig.21 An example implementation of the present disclosure is depicted.In an example, an application function may provide network access assistance information to a network node.

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

[0253] In an example, the AF may determine to provide a connection service to one or more UEs. For example, Fig. 20 The examples described in can be applied. The AF can send a NEF service request message to the NEF. For example, the NEF service request message can include network access assistance information. The NEF can perform an authorization check on the received NEF service request message.

[0254] In an example, based on a successful authorization check, the NEF may send a second NRF service request (e.g., Nnrf_NFDiscovery request) message to the NRF. For example, the NEF may send a 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 may receive a second NRF service request message from the NEF. Based on the received second NRF service request message and / or based on the stored information of the SoR-AF, the NRF may determine a SoR-AF that matches the information of the second NRF request message. Based on the determined SoR-AF, the NRF may send a second NRF service response (e.g., Nnrf_NFDiscovery response) message to the NEF. For example, the second NRF service response message may include at least one of an IP address of the SoR-AF, an identifier of the SoR-AF, etc. In an example, if the NEF has information of the SoR-AF, then based on local configuration and / or based on previously received information, the NEF may not send the second NRF service request.Based on the information of the SoR-AF, the NEF may determine the SoR-AF to which the SoR-AF service request is sent.

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

[0256] In an example, the SoR-AF may perform a subscription check and / or a capability check on the UE (indicated by the UE list information). For example, the UE may not have a subscription to a service of network access information. Based on the UE not having a subscription to a service of network access information, the SoR-AF may reject a SoR-AF service request message from the NEF. For example, the UE may have a subscription to a service of network access information. Based on the UE having a subscription to a service of network access information, the SoR-AF may accept a SoR-AF service request from the NEF. For example, the UE may not have a capability (e.g., eSOR capability) for a service of network access information. Based on the UE not having a capability for a service of network access information, the SoR-AF may reject a SoR-AF service request from the NEF. For example, the UE may have a capability for a service of network access information. Based on the UE having a capability for a service of network access information, the SoR-AF may accept a SoR-AF request from the NEF. In one example, the SoR-AF may send a UDM service request to the UDM. In response, the SoR-AF may receive subscription information and / or capability information of the UE from the UDM.

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

[0258] For example, the SoR-AF may 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 SoR-AF may process one or more information of the SoR-AF service request message for one or more UEs, and the one or more UEs may have a subscription to a service of the network access information and / or may have a capability for a service of 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 supported radio access technology set, a first supported frequency band set, etc.) and / or may subscribe to a first service set (e.g., eMBB service, gold service, etc.). The second UE may have a second capability (e.g., a second supported radio access technology set, a second supported frequency band set, etc.) and / or may subscribe to a first service set (e.g., IoT service, silver service, etc.). For example, based on the first capability and / or the first service set, the SoR-AF may generate first network access information for the first UE. For example, based on the second capability and / or the second service set, the SoR-AF may generate second network access information for the second UE.

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

[0260] Fig. 22 An example implementation of the present disclosure is depicted.In an example, a UE may request that network access information be provided to a network node.

[0261] In an 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 the UE requests network access information and / or if the UE does not have network access information. In one example, if the UE obtains information of a network (e.g., a hosted network) and / or if the UE needs to access the network, the UE may request network access information. For example, the first NAS message may include at least one of an identifier of the UE and / or a 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 (e.g., an address, an identifier, a name, etc.) of the network (e.g., a hosted network), authorization information of the network, an address of an 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 of 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 an example, the AMF may receive a first NAS message from the UE. For example, based on the network access information request of the first NAS message, the AMF may determine to provide the network access information to the UE. In an example, based on the received first NAS message, the AMF may send a UDM service request (e.g., Nudm_SDM_Info request) message to a data management node (e.g., UDM, UDR). For example, the UDM service request message may include at least one of an identifier of the UE and / or a network access information request. Based on the UDM service request message, the data management node may determine that network access information needs to be provided to the UE. Based on the determination, the data management node may 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 an identifier of the UE, a network access information request, and / or 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 may determine whether to update the network access information of the UE. For example, based on the network access information request, the SoR-AF may determine to generate the network access information of the UE.

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

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

[0265] Fig.23 An example implementation of the present disclosure is depicted.In an example, a UE may request that network access information be provided to a network node.

[0266] In an example, the UE may send a first NAS message (e.g., a UL NAS transport message) to the AMF. For example, if the UE requests network access information and / or if the UE does not have network access information, the UE may send the first NAS message. For example, if the UE obtains information of a network (e.g., a hosted network), if the UE receives information from a network / AF, if the UE needs to access the network, and / or if the UE is authorized to access the network, the UE may request network access information. For example, the first NAS message may include at least one of an identifier of the UE and / or a network access information request. The network access information request may indicate that the UE needs network access information, that the UE does not have network access information, and / or that a policy for network access is required. For example, the network access information request message may include information (e.g., address, identification) of the network (e.g., a hosted network), authorization information of the network, an address of the AF, an identifier of a 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 network access information that the UE may have and / or a network access policy that the UE may have.

[0267] In an example, the AMF may receive a first NAS message from the UE. Based on the received first NAS message, the AMF may determine that network access information needs to be provided to the UE and / or that a network access policy needs to be provided to the UE. For example, based on the network access information request of the first NAS message, the AMF may determine a policy for requesting network access from the PCF for the UE.

[0268] In an example, based on the received first NAS message, the AMF may send a PCF service request (e.g., Npcf_AMPolicyControl_Create request, Npcf_AMPolicyControl_Update request) message 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 may determine that network access information needs to be provided to the UE. Based on the determination, the PCF may 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 an identifier of the UE and / or a network access information request. For example, based on the network access information request, the SoR-AF may determine the network access information of the UE.

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

[0270] In the example, return to Fig.23 Based on the network access assistance information, the SoR-AF may determine the network access policy assistance information. The 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 directed, and / or network access information. In response to the SoR-AF service request received from the PCF, the SoR-AF may send a SoR-AF service response (e.g., Nsoraf_SoR_Get response) message to the PCF. The SoR-AF service response message may include the network access policy assistance information. The PCF may receive the SoR-AF service response message. Based on the network access policy assistance information of the SoR-AF service response message, the PCF may construct the network access information of the UE. In response to the received PCF service request, the PCF may send a PCF service response (e.g., Npcf_AMPolicyControl_Create response, Npcf_AMPolicyControl_Update response, policy response) to the AMF. The PCF service response message may include the network access information. The AMF may receive the PCF service response message from the PCF. Based on the PCF service response message, the AMF may send a second NAS message (e.g., a DL NAS transport message) to the UE. The second NAS message may include network access information. The UE may receive the second NAS message sent by the AMF and / or may store the network access information of the second NAS message.

[0271] Fig.24 An example implementation of the present disclosure is depicted. In an example, one or more network nodes may deliver network access information. In an example, a UE may use the delivered network access information.

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

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

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

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

[0276] -Selection list of networks (network list): The selection list of networks may indicate one or more information (e.g., one or more identifiers) of one or more networks. The selection list of networks may include one or more entries. An entry (of the one or more entries) may indicate an identifier of a network. The identifier of a network may include at least one of an MNC (Mobile Network Code), an MCC (Mobile Country Code), an NID (Network Identifier), and / or a network name. In one example, one or more entries of the selection list of networks may be listed in a priority order. For example, a first entry (e.g., a first network) of the selection list of networks may have a higher priority than a second entry (e.g., a second network) of the selection list. In one example, an entry (one or more entries) of the selection list of networks may include priority information of the networks. For example, a third entry (e.g., a third network) may include information with a priority of 1. For example, a fourth entry (e.g., a fourth network) may include information with a priority of 2. Based on the priority information, the UE may determine a priority in one or more entries. For example, the UE may determine that the third network has a higher priority than the fourth network. Based on the determination of the priority of the network, the UE may search for one or more cells of the one or more networks starting from one or more cells of the higher priority entry. For example, the UE may 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 of a network, and / or successfully registers with the network, the UE may not search / discover / select a cell of a network (having a lower priority than the registered network).

[0277] - Access technology information: The access technology information may indicate one or more access technologies that a UE may use to access a network (of one or more networks). To search for one or more cells of a network, the UE may use one or more access technologies indicated by the access technology information.

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

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

[0280] In an example, the UDM may store the received network access information. Based on the network access information, the UDM may send a second UDM service request (e.g., Nudm_SDM_Notification request) message to the AMF associated with the UE. For example, in order to receive the second UDM service request, the AMF may register its address with the UDM, and / or the UDM may store the address of the AMF. Based on the registered address, the UDM may send a 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 a confirmation is required to be received. The indication of whether a confirmation is required to be received may indicate whether the UE needs to send a confirmation of a successful security check when the UE receives the network access information. For example, by receiving a confirmation of a successful security check, the UDM may determine whether the network access information sent by the UDM is changed by a network node between the UDM and the UE. For example, if the network node between the UDM and the UE changes one or more information in the network access information sent by the UDM, the UE may not be able to successfully perform a security check.

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

[0282] The AMF may receive a UL NAS message. Based on the UL NAS message including the SoR transparent container, the AMF may 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 may verify that the UE provides a UE confirmation. If the UDM successfully verifies that the UE provides a UE confirmation, the UDM may send a SoR-AF service request (e.g., Nsoraf_SoR_Info request) message 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 an identifier of the UE and / or an indication of successful delivery of the network service information. Based on the indication of successful delivery, the SoR-AF may determine that the network access information is successfully delivered to the UE.

[0283] In an example, based on one or more information in the received network access information, the UE may determine when and / or where to use the received network access information. For example, the UE may determine whether it needs to use the received network access information. For example, the network access information may include activation information. The activation information may include a valid time, a valid location, a valid standard, etc. For example, the valid time (e.g., at 3:00PM, from 9:00AM to 1:00PM, Tuesday, weekdays, etc.) may indicate when the UE applies the network access information. For example, if the valid time indicates a specific time (e.g., at 2:00PM) and the time is a first time (e.g., 1:59PM), the UE may determine that the UE does not apply the network access information. For example, if the valid time indicates a specific time (e.g., from 3:00PM to 5:00PM) and the time is a second time (e.g., 3:00PM), the UE may determine that the UE applies the network access information. For example, a valid location (e.g., at TAC=1, GPS coordinates (30.0N, 125.0E)), etc.) may 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), the UE may determine that the UE 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)), the UE may determine that the UE applies network access information (e.g., second network access information).

[0284] In an example, based on determining that the UE applies network access information, the UE may apply the network access information. For example, the UE may no longer use the previous network access information and / or the UE may start using the network access information applied by the associated activation information. For example, before the UE receives network access information (e.g., second network access information), the UE may use the first 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, when the conditions of the activation information of the second network access information (e.g., valid time, valid location, valid condition) are not met, the UE may use the first network access information. For example, when the conditions of the activation information of the second network access information (e.g., valid time, valid location, valid condition) are met, the UE may use the second network access information. For example, for the received network access information, if the activation information of the network access information is not met, the UE may not use the network access information. For example, for the received network access information, if the activation information of the network access information is met, the UE may use the network access information. For example, based on determining that the UE applies the network access information, the UE may start using the network access information (eg, the second network access information) and / or may trigger a change from using the first network access information to the second network access information.

[0285] In an example, based on one or more information of the network access information, the UE may trigger a search / discovery of a network associated with the network access information, and / or may change registration from a network to another network based on the result of the search / discovery. For example, if the UE discovers one or more cells of a network based on the network access information, the UE selects the network and / or may send a registration request message to the network. For example, the selected network may be a hosted network.

[0286] Fig.25 An example implementation of the present disclosure is depicted. In an example, one or more network nodes may deliver network access information. In an example, a UE may use the delivered network access information.

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

[0288] In the example, return to Fig.25, the SoR-AF may determine to deliver the network access information to the UE. For example, if the AF and / or the UE requests delivery of the network access information, if the SoR-AF receives / processes the network access assistance information, and / or if a condition (e.g., time and / or location) indicated by the event information based on the network assistance information is met, the SoR-AF may determine to deliver the network access information to the UE. For example, if the event information indicates a time (e.g., 2PM), the SoR-AF may determine to trigger delivery of the network access information at about the time (e.g., 1:59PM, 2:00PM). For example, if the event information indicates a location (e.g., city A), the SoR-AF may determine to trigger delivery of the network access information when the UE approaches a boundary of the location (e.g., 0.3 miles from city A, 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 the network access information, the SoR-AF may not send the network access information that does not include the activation information.

[0289] In an example, the SoR-AF may determine one or more UEs to which the network access information needs to be sent. For example, based on the one or more UEs indicated by the UE list information, the SoR-AF may determine to send the network access information to the 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, the SoR-AF may determine to send the network access information.

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

[0291] -Selection list of networks (network list): The selection list of networks may indicate one or more information of one or more networks. For a network (of the one or more networks), the network access information may include or may not include access technology information. The selection list of networks may include one or more entries. An entry in the one or more entries may indicate an identifier of a network. The identifier of a network may include at least one of an MNC (mobile network code), an MCC (mobile country code), an NID (network identifier), and / or a network name. One or more entries of the selection list of networks may be listed in order of priority. For example, a first entry of the selection list of networks (e.g., a first network) may have a higher priority than a second entry of the selection list (e.g., a second network). For example, an entry of the selection list of networks may include priority information of the network. For example, a third entry (e.g., a third network) may include information with a priority of 1. For example, a fourth entry (e.g., a fourth network) may include information with a priority of 2. Based on the priority, the UE may determine a priority between the entries. For example, the UE may determine that the third network has a higher priority than the fourth network. Based on the determination of the priority, the UE may search for one or more cells of the one or more networks starting from the higher priority entry. For example, the UE may 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 of a network (with a higher priority) and / or successfully registers with the network (with a higher priority), the UE may not search / discover / select a cell of a network (with a lower priority).

[0292] - Access technology information: The access technology information may indicate to the network one or more access technologies that the UE may use for the network. To search for one or more cells of the network, the UE may use one or more access technologies indicated by the access technology information.

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

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

[0295] In an example, based on receiving the network access information, the UE may use the received network access information and / or the UE may apply the network access information. For example, based on the received network access information not including activation information, the UE may start using the received network access information and / or the UE may apply the network access information. For example, based on receiving the network access information, the UE may no longer use the previous network access information. Based on the network access information, the UE may trigger a search / discovery of a network associated with the network access information, and / or the UE may change registration from a network to another network based on the result of the search. For example, if the UE discovers one or more cells of a network based on the network access information, the UE may select the network and / or may send a registration request message to the network. For example, the selected network may be a hosted network.

[0296] Fig.26 An example implementation of the present disclosure is depicted. In an example, the UE may use the delivered network access information.

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

[0298] In the example, return to Fig.26, based on one or more information in the second network access information, the UE may determine when and / or where to use the second network access information. For example, the UE may determine whether it needs to use the second network access information. For example, the second network access information may include activation information. The activation information may include at least one of a valid time, a valid location, a valid standard, etc. For example, the valid time (e.g., at 3:00PM, from 9:00AM to 1:00PM, Tuesday, weekdays, etc.) may indicate when the UE applies the second network access information. For example, if the valid time indicates a specific time (e.g., at 2:00PM), and if the time is a first time (e.g., 1:59PM), the UE may determine that the UE does not apply the second network access information. For example, if the valid time indicates a specific time (e.g., from 3:00PM to 5:00PM), and if the time is a second time (e.g., 3:00PM), the UE may determine that the UE applies the second network access information. For example, a valid location (e.g., at TAC=1, GPS coordinates (30.0N, 125.0E)), etc.) may 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), the UE may determine that the UE 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)), the UE may determine that the UE applies the second network access information (e.g., the second network access information).

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

[0300] In an example, based on one or more information of the second network access information, the UE may trigger a search for a network associated with the second network access information, and / or may change registration from the first network to another network based on the result of the search. 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 may send a registration request message to the second network. For example, the selected second network may be a hosted network and / or the second network access information may include information of the second network.

[0301] In an example, the UE may start using / applying the second network access information. The UE may check whether the activation information of the second network access information is satisfied. If the condition indicated by the activation information of the second network access information is no longer satisfied, the UE may stop using the second network access information. For example, based on the UE stopping using the second network access information, the UE may perform orientation registration to the second network. For example, based on the UE stopping using the second network access information, if the third network access information is available and / or if one or more conditions of the activation information of the third network access information are satisfied, the UE may start using the third network access information. For example, based on the UE stopping using the second network access information, if the 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 may start using the first network access information. Based on the first network access information and / or based on the third network access information, the UE may start 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 the 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 may select a network in the one or more networks. Based on the selected network, the UE may send a registration message to a core network node of the selected network.

[0302] Fig. 27 An example implementation of the present disclosure is depicted. In an example, a UE may 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 may select a network (e.g., a first network) and / or may register with the network. For example, the primary network access information may be network access information that the UE may use when no other network access information (e.g., secondary network access information) is delivered.

[0304] In an example, a core network node (e.g., SoR-AF, UDM, PCF, etc.) may determine whether a condition of the event information is met (e.g., based on the network access assistance information). If the core network node determines that the condition is met, the core network node may 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 may receive the network access information (secondary network access information) sent by the core network, such as Fig.25 as shown in the example.

[0305] In the example, return to Fig. 27Based on receiving the secondary network access information, the UE may determine to use the secondary network access information. Based on the determination, the UE may start to apply the secondary network access information. For example, the UE may no longer use the previous network access information (e.g., the primary network access information) and / or the UE may start to use the secondary network access information.

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

[0307] In an example, the UE may apply the secondary network access information. For example, the secondary network access information may include deactivation information. The deactivation information may include one or more conditions for when the UE may stop using the secondary network access information. For example, the deactivation information may indicate a first time (e.g., 10:00 AM). The UE may check whether 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 may continue to use the secondary network access information. For example, if the time (e.g., 10:00 AM) is the first time, the UE may stop using the secondary network access information and / or the UE may start using the primary network access information.

[0308] In an example, based on starting to use the primary network access information, the UE may start searching for one or more cells of the one or more networks indicated in the primary network access information. Based on the search, if the UE finds one or more cells of the one or more networks, the UE may select a network from the one or more networks. Based on the selected network, the UE may send a registration message to a core network node of the selected network.

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

[0310] In an example, the SoR-AF may generate network access information for the UE. Fig. 20 , Fig.21, Fig. 22 , Fig.23 As shown in the example of , the SoR-AF may have the network access assistance information and / or the SoR-AF may generate the network access information based on the network access assistance information.

[0311] In the example, return to Fig.28 , 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 message may include at least one of network access information, an identifier of the UE, network access policy assistance information, etc. The identifier of the UE may indicate a UE to which the network access information and / or the network access policy assistance information may be applied. In an example, the UDM may receive the first UDM service request message from the SoR-AF.

[0312] In an example, the UDM may store the network access information and / or network access policy assistance information of the received 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., Nudm_SDM_Notification request) message to the PCF associated with the UE. For example, in order to receive the second UDM service request message, the PCF may register its address with the UDM, and / or the UDM may store the address of the PCF. 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 the network access information, the network access policy assistance information and / or the identifier of the UE.

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

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

[0315] In an example, the NG-RAN may receive an N2 message sent by the AMF. Based on the mobility assistance information of the N2 message, the NG-RAN may determine whether the NG-RAN may start 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), the NG-RAN may start using the mobility assistance information. For example, if the mobility assistance information includes validity information, the NG-RAN may 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, TAB). For example, the NG-RAN may 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, the NG-RAN may not start using the mobility assistance information. For example, if the time (e.g., 09:00 AM) is the first time, the NG-RAN may start using the mobility assistance information. For example, the NG-RAN may determine whether the first location indicated by the validity information is met. For example, if the current location (e.g., TA B) is not within the first location, the NG-RAN may not start using the mobility assistance information. For example, if the current location (e.g., cell A) is within the first location, the NG-RAN may start using the mobility assistance information.

[0316] In an example, based on determining to start using mobility assistance information, the NG-RAN may 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 may measure and / or report. For example, the NG-RAN may construct a network measurement configuration based on the mobility assistance information. For example, the network measurement configuration may include at least one of one or more identifiers (e.g., NCC, NMC, NID, network name, etc.) of one or more networks, report information, and / or measurement gap information for network search. For example, the report information may indicate how / when the UE sends a report to the NG-RAN and / or the content of the UE report. For example, the report information may indicate that the UE may send a report to the NG-RAN when the UE detects one or more networks indicated by the network measurement configuration. For example, the report information may indicate that the UE may send a report to the NG-RAN. For example, the report information may indicate that the UE may send a report to the one or more networks and / or may indicate one or more frequencies that the one or more networks may use. The measurement gap information for network search may indicate one or more time information when the UE may perform a search for one or more networks. For example, the UE and / or the NG-RAN may not send data during a time period indicated by the one or more time information.

[0317] In an example, the UE may search for one or more networks based on a network measurement configuration. For example, based on measurement gap information for network search, the UE may search for one or more networks during a time indicated by the measurement gap information for network search. In an example, the UE may 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 may send a measurement report to the NG-RAN. For example, the measurement report may include information of one or more networks detected by the UE. For example, the network measurement configuration may include information of a first network and / or a second network. For example, the information of the first network may be an identifier of the first network (e.g., MCC=A, MNC=B, NID=C). For example, the information of the second network may be an identifier of the second network (e.g., network name="host network A"). For example, if the UE detects a third cell, the UE may read information of a network associated with the third cell via system information of the third cell. For example, the information of the network associated with the third cell may indicate a third identifier of the third network (e.g., MCC=A, MNC=B, NID=D). Based on the network measurement configuration not including an identifier of the third network, the UE may not report detection of the third cell and / or the third network to the NG-RAN. For example, if the UE detects a second cell, the UE may read information about a network associated with the second cell via system information of the second cell. For example, the information about a network associated with the second cell may indicate a second identifier of 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 may send a measurement report including information about the detected network to the NG-RAN. For example, the information about the detected network may include information about the second cell and / or information about the second network.

[0318] In an example, the NG-RAN may receive a measurement report sent by the UE. For example, based on the measurement report including information of the detected network and / or based on the mobility assistance information, the NG-RAN may determine whether the NG-RAN needs to hand over the UE. For example, based on the mobility assistance information including information of the detected network, the NG-RAN may determine to hand over the UE to the target network. For example, the target network may be a network (e.g., a second network) indicated in the information of the detected network. For example, in order to switch the UE to the target network (e.g., the second network), the NG-RAN may send an RRC message (e.g., an RRC reconfiguration message). The RRC message (e.g., the RRC reconfiguration message) may include information of the target network, indicating that the UE accesses a cell of the target network. In an example, based on the mobility assistance information including information of the detected network, the NG-RAN may determine to release the RRC connection to the UE and / or command the UE to select the target network. For example, based on determining to release the RRC connection and / or commanding the UE to select the target network, the NG-RAN may send an RRC message (e.g., an RRC release message). The RRC message (e.g., an RRC release message) may include information of the target network. The UE may receive the RRC message. Based on the information of the target network, the UE may perform cell selection and / or network selection. For example, the UE may select a target network and / or may start a registration procedure to the target network.

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

[0320] In an example, the SoR-AF may generate network access information for the UE. Fig. 20 , Fig.21 , Fig. 22 , Fig.23 As shown in the example of FIG. 1 , 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 Fig.29, 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 message may include at least one of network access information, an identifier of the UE, network access policy assistance information, etc. The identifier of the UE may indicate a UE to which the network access information and / or the network access policy assistance information may be applied. In an example, the UDM may receive the first UDM service request message from the SoR-AF.

[0322] In an 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., Nudm_SDM_Notification request) message to the AMF associated with the UE. For example, in order to receive the second UDM service request message, the AMF may register its address with the UDM, and / or the UDM may store the address of the AMF. Based on the registered address, the UDM may send a second UDM service request message to the AMF. For example, the second UDM service request message may include at least one of the network access information and / or the mobility assistance information. In one example, the network access information may include the mobility assistance information. For example, the mobility assistance information may indicate information of one or more networks to which the NG-RAN may handover the UE. For example, the first network (e.g., the first hosted network) may allow the UE to access the first network, and / or the second network (e.g., the second hosted network) may not allow the UE to access the second network. The mobility assistance information may indicate that the UE may use the first network and / or that the UE may not use the second network. For example, the mobility assistance information may include validity information indicating when and / or where information of one or more networks may be used or valid.

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

[0324] In the example, the NG-RAN may receive the N2 message sent by the AMF. Fig.28As shown in the example, based on the information delivered via the N2 message, the NG-RAN may determine whether to activate the network measurement configuration, the NG-RAN may send the network measurement configuration to the UE, the NG-RAN may receive a measurement report from the UE, the UE may perform measurements, the UE may send a measurement report to the NG-RAN, the NG-RAN may hand over the UE, the NG-RAN may release the RRC connection, the UE may perform a handover, and / or the UE may perform network selection.

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

[0326] In an example, the SoR-AF may generate network access information for the UE. Fig. 20 , Fig.21 , Fig. 22 , Fig.23 As shown in the example of , the SoR-AF may collect the network access assistance information and / or the SoR-AF may generate the network access information based on the network access assistance information.

[0327] Back to Fig.30 In one example, the SoR-AF may determine when to send network access information and / or network policy assistance information to one or more network nodes, such as Fig.25 Return to Fig.30 If the SoR-AF determines to send the network access information and / or the 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 the network access information, the identifier of the UE, the validity information, and / or the network policy assistance information. In one example, the network access information may include the mobility assistance information and / or the 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, an identifier of the UE, validity information, and / or network policy assistance information. In one 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, the condition (of the one or more conditions of the validity information) may include time information. If the condition of the time information is met (for example, the time is within the time indicated by the time information), the UDM may send a second UDM service request (for example, 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, the mobility assistance information may indicate to the NG-RAN information about one or more networks to which the NG-RAN can hand over the UE and / or to which the UE can reselect. For example, the UDM may construct the mobility assistance information based on the network access information and / or subscription information of the UE.

[0329] In one example, based on the received first UDM service request message, the UDM may store network access information, an identifier of the UE, validity information, and / or network policy assistance information. In one example, the UDM may send a third UDM service request message to a PCF associated with the UE. For example, the third UDM service request message may include at least one of the network access information, the network access policy assistance information, an identifier of the UE, 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 may determine whether one or more conditions indicated by the validity information are met. For example, the condition (of the one or more conditions of the validity information) may include time information. If the condition of the time information is met (for example, the time is within the time indicated by the time information), the PCF may send a PCF service request (for example, Npcf_AMPolicyControl_Create response, Npcf_AMPolicyControl_Update response, policy response, Npcf_AMPolicy_Notify, etc.) message 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 an identifier of the UE. The network access information and / or the network access policy information may include mobility assistance information.

[0331] In an example, the AMF may 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 may determine when to send an N2 message (e.g., initial context establishment, UE context modification) to the NG-RAN. For example, the AMF may use validity information to determine when to send the N2 message. The AMF may send the N2 message when one or more conditions indicated by the validity information are met. For example, when the AMF does not receive validity information, the AMF may determine to send the N2 message. For example, in order to control the mobility of the UE, the N2 message may include mobility assistance information.

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

[0333] Fig.31 An example implementation of the present disclosure is depicted. In the example, based on information of one or more network slices provided by one or more networks (e.g., one or more hosted networks), the NG-RAN may determine to handover a UE to one or more networks.

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

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

[0336] In an example, the NG-RAN may use the information of the target network slice delivered by the N2 message. Based on the information of the target network slice, the NG-RAN may 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 of the target network slice that the UE may measure and / or report. For example, the information of the target network slice may include at least one of one or more identifiers (e.g., S-NSSAI, etc.) of one or more network slices, report information, and / or measurement gap information for network search. For example, the report information may indicate how / when the UE sends a report to the NG-RAN and / or the content of the UE report. For example, the report information may indicate that the UE may send a report to the NG-RAN when the UE detects one or more cells indicating one or more network slices. For example, the reported information may indicate that the UE may send a report including information of one or more network slices and / or information of one or more networks broadcasting information of one or more network slices. The measurement gap information for network search may indicate one or more time information when the UE may perform a search for one or more network slices. In one example, a network slice (of one or more network slices) may be identified by an identifier of the network slice (e.g., S-NSSAI) and / or an identifier of a network slice group to which the network slice belongs.

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

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

[0339] Fig.32 An example implementation of the present disclosure is depicted.In an example, the UE may use the network access information to select a network, and / or may perform registration with the selected network.

[0340] In an example, the UE may have network access information. For example, the network access information may include one or more entries. For example, the one or more entries 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 an example, the UE may be registered to a third network (Network C). For example, the UE may be in a third cell (Cell 3) of the third network.

[0342] In an example, the UE may determine to use the network access information. For example, based on the valid time and / or valid location of the network access information, the UE may start using the network access information. For example, the UE may start using the first entry of the network access information. Based on the first entity indicating the first network, the UE may attempt to discover and / or search for a cell of the first network. For example, if there is no cell of the first network near the UE, the UE may not be able to discover the cell of the first network. Based on the absence of the cell of the first network, the UE may start using the next entry of the network access information. For example, the UE may start using the second entry of the network access information. The UE may attempt to discover and / or search for a cell of the second network. For example, the UE may discover a second cell (cell 2) of the second network. For example, the UE may receive an SIB indicating the second network from the second cell. Based on the UE discovering the cell of the second network, the UE may select the second network. The UE may select the second network to perform a registration procedure. For example, the UE may 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 the third network. Based on the UE not selecting the third network, the UE may not perform a registration to the third network and / or may perform a deregistration procedure to the third network.

[0343] In one example, the UE may start searching for a network search procedure and / or a cell search procedure. Based on the network search procedure and / or the cell search procedure, the UE may discover one or more cells. Based on the one or more cells, the UE may determine information of one or more networks (detected networks) associated with the one or more cells by reading the SIB of the one or more cells. For one or more networks (detected networks), the UE may determine whether the network access information includes information (e.g., an identifier) ​​of the network (in the detected network). If the network access information includes information of the network (in the detected network), the UE may select the network and may perform registration to the network.

[0344] Fig.33 An example implementation of the present disclosure is depicted.In an example, the UE may receive and / or apply network access information based on the activation information.

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

[0346] In an example, the UE may determine whether one or more conditions indicated by the activation information are met. For example, the one or more conditions may indicate valid time information when the network access information is valid / applicable, and / or valid area information where the network access information is valid / applicable. If one or more conditions are met, the UE may start using the network access information. For example, the UE may start using information of one or more networks. If one or more conditions are not met, the UE may not use the network access information.

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

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

[0349] In an example, the UE may use the network access information to select a network. In one example, the UE may perform a search for one or more cells of the selected network. In one example, the UE may perform a search / discovery / detection of one or more cells, may identify one or more networks associated with one or more discovered / detected cells, may select a network from the one or more networks, and / or may perform a registration procedure to the selected network. For example, for the selection of a network, the UE may use the network access information. For example, the UE may attempt to search / discover / detect one or more cells of one or more networks indicated by the network access information. For example, the UE may not 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 may search / discover / detect one or more cells of one or more networks, and may identify one or more networks of one or more cells. The one or more networks may include a first one or more networks that the network access information may indicate and / or a second one or more networks that the network access information may not indicate. The UE may select a network in the first one or more networks, and / or may perform a registration to the selected network.

[0350] In an example, the network access information may include at least one of information of one or more networks (network list), activation information indicating one or more conditions under which the network list is valid / used, and / or information of one or more access network types. The network list may include information of one or more networks that the UE can access and / or is allowed to access. For example, the network list may include information of one or more hosted networks. For example, the network list may include one or more identifiers of one or more networks. The 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, the 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, the one or more time periods may include at least one of a start time indicating the time when the UE can use the network list, an end time indicating the time when the UE can stop using the network list, and / or a duration indicating the amount of time the UE can use the network list. For example, the valid area information may indicate one or more location information that allows the UE to use the network list for network selection. For example, the one or more location information may include at least one of information of one or more regions, information of one or more geographic coordinates, information of one or more cell identifiers, and / or information of one or more tracking areas. For example, the one or more access network types may indicate one or more access network types (e.g., NG-RAN, E-UTRAN, GSM, E-UTRA, NR, etc.) that the UE is allowed to use to search / select / register to a network (in the network list).

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

[0352] In an example, based on determining that the UE is allowed to use the network list and / or the UE is allowed to access the network (in the network list), the UE starts using the network list. For example, the UE may start searching / detecting / discovering one or more cells indicated by the network list. For example, if one or more cells associated with the network list are searched / detected / discovered, the UE may select a network (e.g., a second network) from one or more networks associated with the one or more cells. Based on the selection of the network, the UE may start a registration procedure to 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 an identification of the UE, a registration reason, one or more identifiers of a network slice, an identifier of a first network, an identifier of a home network, and / or capabilities of the UE. 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 of the second network, the UE may not select the second network.

[0353] In an example, based on the activation information, the UE may determine whether the UE is no longer allowed to use the network list. For example, in order to determine whether the UE needs to stop using the network list, the UE may determine whether one or more conditions of the activation information are met. If one or more conditions are no longer met, the UE may determine that the UE needs to stop using the network list. In one example, a network node of the second network may send an indication to the UE to indicate 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 may not use the network access information, may stop using the network list, may start selecting a third network, and / or may stop selecting the second network.

[0354] In an example, based on determining that the UE needs to stop using the network list, the UE may search for one or more cells. For example, the UE may search for one or more cells based on the second network access information. For example, if the UE finds a cell of a third network indicated by the second network access information, the UE may select the third network. The UE may send a registration request message to the third network. In an example, the UE may register with the first network using the second network access information. 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] Fig.34 An example implementation of the present disclosure is depicted.In an example, the UE may use the network access information to select a network, and / or may perform registration with the selected network.

[0356] In an example, the UE may receive network access information from a core network node of a first network (e.g., network 1). The network access information may include information of one or more networks and / or one or more activation information of one or more networks. For example, the information of one or more networks in the network access information may include information of a fourth network (network 4) and / or information of a second network (network 2). For example, the one or more activation information may include activation information of a fourth network and / or activation information of a second network. The activation information of the fourth network may include a fourth condition (condition 4), and / or the activation information of 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 activation information of the network may indicate when the UE is allowed to access / search / select / register to the 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 within the second time period. For example, the activation information of the network may indicate when an entry associated with the activation information (e.g., an information element, an entry in the network access information) may be used by the UE. For example, the information of the one or more networks may include one or more identifiers of the one or more networks.

[0357] In an example, for activation information (of one or more activation information), the UE may determine whether the condition indicated by the activation information is met. If the condition is met, the UE may determine that the UE may be allowed to access / use / select / register the network associated with the activation information. If the condition is not met, the UE may determine that the UE is not allowed 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 time satisfying the second condition, the UE may determine that the UE is allowed to access / use / select / register to the second network. For example, at the time (e.g., 5:30 PM), based on the time not satisfying the fourth condition, the UE may determine that the UE is not allowed to access / use / select / register to the fourth network. Based on determining that the UE is allowed to access the second network, the UE may search for cells of the second network, the UE may select the second network and / or the UE may send a registration request message to the second network.

[0358] In one example, based on the network access information, the UE may determine whether one or more conditions of the network access information of the second network are met. For example, if one or more conditions of the second network are met, the UE starts using the search / discovery of the cell of the second network. For example, at this time (e.g., 5:30 PM), the UE may determine that the conditions of the second network are met. Based on the determination, the UE may determine that the UE is allowed to access the second network. Based on the determination, the UE may start searching for the cell of the second network. If the UE finds the cell of the second network, the UE may select the second network and / or may send a registration request message to the second network. For example, if the UE fails to find the cell of 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 may determine that the conditions of the second network are not met. Based on the determination, the UE may determine that the UE is not allowed to access the second network. Based on the determination, the UE may not start searching for the cell of the second network.

[0359] In an example, the UE may receive network access information from a core network node (e.g., AMF, SoR-AF, UDM, PCF, AF) of the first network. The network access information may include at least one of an identifier of the second network and / or activation information of the second network. In an example, the UE may determine whether the second network is activated / active based on the activation information. For example, the activation of the network access information may indicate when the second network is active / activated. For example, the second network (e.g., the hosted network) may operate within one or more time periods (e.g., from 10:00AM to 5:00PM, from Monday to Friday, etc.) and / or at one or more areas (e.g., geographic coordinates (x1, y1, z1), in city A, etc.). For example, the activation information of the second network may indicate that the second network may operate and / or may be active within one or more time periods and / or at one or more areas. Based on the activation information of the second network, the UE may determine whether the second network is active and / or operating. For example, at a first time (e.g., 08:00AM), the UE may determine that the second network is inactive. For example, at a second time (e.g., 1:00 PM), the UE may determine that the second network is active. For example, based on the network access information including information of the second network, when the second network is activated, the UE may determine that the UE is allowed to access the second network. In the example, based on determining that the second network is active / activated, the UE may start searching for a cell of the second cell and / or the UE may select the second network. In one example, if the UE discovers / detects a cell of the second network, the UE may select the second network. Based on the UE selecting the second network and / or based on discovering / detecting a cell of the second network, the UE may send a registration request message to the second network.

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

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

[0362] In an example, the UE may register with the second network. In an example, the UE may determine to stop using the first network access information based on at least one of activation information of the first network access information and / or an indication from the second network. For example, the second network may send a message including the indication to the UE. The indication may indicate that the UE is to deregister from the second network, access to the second network is not allowed, the UE needs to perform network selection, and / or the UE needs to stop using the first network selection information. Based on determining to stop using the first network access information, the UE may search for a cell of a third network. For example, the UE may perform the search based on the second network access information.

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

[0364] In an example, the UE may 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 may be a core network node of a first network. The core network node may receive a 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 may send the network access information to the UE. The UE may use the network access information to select a network. In response to sending the request for network access information, the UE may receive the network access information from the core network node. Based on the received network access information, the UE may select a second network for registration. The network access information may include information about the second network.

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

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

Claims

1. A method comprising: sending, by the wireless device, capability information to a core network node of the first network, the capability information indicating that the wireless device supports processing one or more conditions for determining whether the wireless device is allowed to access one or more second networks; The wireless device receives network access information from the core network node of the first network, the network access information comprising: an identifier of the second network; and one or more parameters indicating time period conditions for allowing the wireless device to access the second network; determining, by the wireless device, that the time period condition is satisfied; and A registration request message is sent, by the wireless device, to the second network and based on the determination.

2. A method comprising: The wireless device receives network access information from a first network, the network access information comprising: an identifier of the second network; and one or more parameters indicating conditions for determining whether the wireless device is allowed to access the second network; determining, by the wireless device, that the conditions are satisfied; and A second registration request message is sent, by the wireless device, to the second network and based on the determination.

3. The method of claim 2, further comprising sending, by the wireless device, capability information to the first network, the capability information indicating that the wireless device supports processing the network access information for determining whether the wireless device is allowed to access one or more second networks.

4. The method of claim 3, wherein the capability information is sent by the wireless device in a first message, the first message comprising at least one of the following: an identification of the wireless device; one or more identifiers of the requested network slice or slices; an identifier of the second network; or The capability information.

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

6. The method of one of claims 4 to 5, wherein the first message comprises a first registration request message.

7. The method according to one of claims 2 to 6, wherein the condition comprises a time period condition for allowing the wireless device to access the second network.

8. The method of claim 7, wherein the time period condition comprises at least one of the following: a start time from when the wireless device is allowed to access the second network; an end time from when the wireless device is not allowed to access the second network; or The duration for which the wireless device is allowed to access the second network.

9. The method according to claim 2 , wherein: The first network comprises a Public Land Mobile Network (PLMN); and The second network includes a non-public network NPN.

10. The method according to one of claims 2 to 9, wherein the network access information further comprises a location condition under which the wireless device is allowed to access the second network.

11. The method of claim 10, wherein the location condition comprises 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 identities; or Information about one or more tracking areas.

12. The method of one of claims 2 to 11, further comprising searching, by the wireless device and based on the determination, for one or more cells of the second network.

13. The method of claim 12, further comprising selecting, by the wireless device, the second network based on a cell of the one or more cells of the second network discovered by the wireless device. The method of claim 13 , wherein the cell broadcasts an identifier of the second network.

15. The method of claims 13 to 14, wherein the wireless device sends the second registration request message to the second network based on selecting the second network.

16. The method of one of claims 2 to 15, further comprising sending, by the wireless device, a response message to the first network in response to receiving the network access information, the response message comprising at least one of the following: an identifier of the wireless device; and A confirmation of the one or more parameters is received.

17. The method according to one of claims 2 to 16, wherein the network access information further comprises priority information of the second network.

18. The method of claim 17, wherein the wireless device selects the second network based on the priority information.

19. The method according to one of claims 2 to 18, wherein the network access information further comprises information of one or more access network types that are allowed to access the second network.

20. The method of claim 19, wherein the wireless device sends the second registration request message via the one or more access network types.

21. The method of one of claims 2 to 20, wherein the wireless device receives the network access information from a core network node of the first network.

22. The method of one of claims 2 to 21, wherein the second network comprises a hosted network.

23. The method of one of claims 2 to 22, further comprising sending, by the wireless device, a deregistration request message to the second network and based on a change in the time period condition from being satisfied to not being satisfied.

24. A wireless device comprising one or more processors and a memory storing instructions which, when executed by the one or more processors, cause the wireless device to perform the method of any one of claims 1 to 23.

25. A non-transitory computer readable medium comprising instructions which, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 1 to 23.

26. A method comprising: receiving, by a core network node of a first network, capability information from a wireless device, the capability information indicating that the wireless device supports processing network access information for determining whether the wireless device is allowed to access one or more second networks; as well as The core network node sends network access information to the wireless device, where the network access information includes: an identifier of the second network; as well as One or more parameters indicating conditions for determining whether the wireless device is allowed to access the second network.

27. The method of claim 26, wherein the capability information is received from the wireless device in a first message, the first message comprising at least one of: an identification of the wireless device; one or more identifiers of the requested network slice or slices; an identifier of the second network; or The capability information.

28. The method of one of claims 26 to 27, wherein the first message comprises a first registration request message.

29. The method of one of claims 26 to 28, wherein the condition comprises a time period condition for allowing the wireless device to access the second network.

30. The method of claim 29, wherein the time period condition comprises at least one of the following: a start time from when the wireless device is allowed to access the second network; an end time from when the wireless device is not allowed to access the second network; or The duration for which the wireless device is allowed to access the second network.

31. The method of one of claims 26 to 30, wherein: The first network comprises a Public Land Mobile Network (PLMN); and The second network includes a non-public network NPN.

32. The method of one of claims 26 to 31, wherein the network access information further comprises a location condition for the wireless device to be allowed to access the second network.

33. The method of claim 32, wherein the location condition comprises 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 identities; or Information about one or more tracking areas.

34. The method of one of claims 26 to 33, wherein the second network comprises a hosted network.

35. The method of claim 26, wherein the first network comprises at least one of the following: a network having subscription information for the wireless device; or A network serves the wireless device.

36. A core network node, the core network node comprising one or more processors and a memory storing instructions, the instructions, when executed by the one or more processors, causing the core network node to perform the method of any one of claims 26 to 35.

37. A non-transitory computer readable medium comprising instructions which, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 26 to 35.

38. A system comprising: A wireless device comprising: one or more processors and a memory storing instructions, the instructions, when executed by the one or more processors, causing the wireless device to perform operations comprising: Receive network access information from a core network node of a first network, the network access information comprising: an identifier of the second network; and one or more parameters indicating conditions for determining whether the wireless device is allowed to access the second network; determining that the conditions are met; and sending a second registration request message to the second network and based on the determination; and The core network node, wherein the core network node comprises: one or more processors and a memory storing instructions, wherein the instructions, when executed by the one or more processors, cause the core network node to perform operations, the operations comprising: The network access information is sent to the wireless device.

39. A method comprising: sending, by the wireless device, a message including a network access information request for a hosted network to a core network node of a first network; The network access information is received by the wireless device from the core network node, wherein the network access information includes at least one of the following: Information about the second network; as well as information on activation conditions of the second network; Determining, by the wireless device, that the activation condition is satisfied; as well as A registration request message is sent, by the wireless device, to the second network and based on the determination.

40. A method comprising: receiving, by the core network node and from the wireless device, a message indicating a capability for processing network access information for selecting a hosted network; determining, by the core network node, network access information for the wireless device based on the message, wherein the network access information includes information of the hosted network and validity information for the hosted network; as well as The core network node sends the network access information to the wireless device.

41. A method comprising: receiving, by a core network node of the first network, a registration request message from a wireless device; Receiving, by the core network node, network access assistance information from a hosted network, wherein the network access assistance information comprises at least one of the following: information of the wireless device; information about the hosting network; as well as a time period for accessing the hosted network; Determining, by the core network node, network access information based on the network access auxiliary information; as well as The core network node sends the network access information to the wireless device.

Images