Multiple access network processing

Abstract

The present invention relates to a method comprising: sending, by a wireless device, a first message to a first mobility management node of a network, the first message indicating that secondary registration with a secondary network associated with the network is supported; receiving, by the wireless device, a second message from the first mobility management node, the second message comprising network-permitted information for secondary registration; and sending, by the wireless device, a third message requesting the secondary registration to a second mobility management node of the allowed network.

Description

Technical Field

[0001] This invention relates to a method and corresponding apparatus for managing a set of multiple connections (e.g., connections associated with cellular communication). In some embodiments, these connections may be 5G or 6G communication, or may be based on other technologies such as WLAN. Background Technology

[0002] With the development of 5G systems (5GS), 3GPP access may also develop. For example... Figure 20 As shown, one or more 3GPP RANs can be diverse and / or can be deployed in different areas. In the prior art, access nodes and / or radio access networks can be deployed as terrestrial nodes (on the ground) or at similar frequencies (e.g., 2GHz). In other words, access nodes can be deployed on the ground, in buildings, etc., and can use similar frequency bands due to limitations in supported frequencies. As a result, distinguishing (e.g., type 1) 3GPP RANs from other (e.g., type 2) 3GPP RANs may not offer much benefit. As 5G system equipment becomes smaller and the signals of power-limited UEs become capable of reaching satellites, deploying 3GPP access nodes on satellites may become feasible. For example, a first NG-RAN in one or more 3GPP RANs can be deployed in geostationary equatorial orbit (GEO). For example, a second NG-RAN in one or more 3GPP RANs can be deployed in low Earth orbit (LEO). For example, a third NG-RAN in one or more 3GPP RANs can be deployed as a terrestrial (e.g., on the ground, inside a building) access network. For example, a fourth E-UTRAN in one or more 3GPP RANs can be deployed as a terrestrial access network. These different 3GPP RANs can provide different characteristics. For example, a first NG-RAN can provide coverage in remote areas where terrestrial 3GPP RANs cannot be deployed. For example, a second NG-RAN can provide wider coverage than a terrestrial NG-RAN, but with reduced throughput. For example, one or more 3GPP RANs can connect to one or more 3GPP core networks. For example, one or more 3GPP core networks can belong to one or more networks. For example, a first NG-RAN and / or a second NG-RAN can connect to a first core network. For example, a third NG-RAN can connect to a second core network. For example, a first core network can belong to a first network and / or a first operator. For example, a second core network can belong to a second network and / or a second operator. In these diverse scenarios, using multiple 3GPP RANs or networks for a UE can be beneficial because the UE can connect to the appropriate RAN or network based on the required service. However, this raises several issues, such as how the UE should choose the network or RAN it must use. Summary of the Invention

[0003] The purpose of this invention is to alleviate the above-mentioned problems.

[0004] Another objective of this invention is to provide a more robust process, reduce connection latency, or offer an acceptable fallback solution while maintaining short processing times.

[0005] Another object of the present invention is to provide a method for mobility management of wireless devices within a network.

[0006] Therefore, a method as claimed in claims 1, 3, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41 and 42, and an apparatus as claimed in claim 43 or 44 are proposed.

[0007] It should be understood that the preferred embodiments of the present invention may also be any combination of the dependent claims or the above embodiments with the corresponding independent claims.

[0008] These and other aspects of the invention will become apparent and will be elucidated with reference to the embodiments described below. Attached Figure Description

[0009] This document describes examples of several embodiments of various embodiments of the present disclosure with reference to the accompanying drawings.

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

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

[0012] Figure 3 An example communication network including core network functions is shown.

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

[0014] Figure 5 An example of the core network architecture for a roaming scenario is shown.

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

[0016] Figure 7A , Figure 7B and Figure 7CThe diagram illustrates the user plane protocol stack, the control plane protocol stack, and the services provided between the protocol layers of the user plane protocol stack.

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

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

[0019] Figure 10 An example of the registration process for wireless devices is shown.

[0020] Figure 11 An example of a service request process for a wireless device is shown.

[0021] Figure 12 An example of the Protocol Data Unit (PDU) session establishment process for a wireless device is shown.

[0022] Figure 13 An example of a component in a communication network is shown.

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

[0024] Figure 15A and Figure 15B This is a schematic diagram of one or more aspects of exemplary embodiments of this disclosure.

[0025] Figure 16 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0026] Figure 17 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0027] Figure 18 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0028] Figure 19 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0029] Figure 20 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0030] Figure 21 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0031] Figure 22 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0032] Figure 23 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0033] Figure 24 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0034] Figure 25 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0035] Figure 26 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0036] Figure 27 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0037] Figure 28 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0038] Figure 29 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0039] Figure 30 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0040] Figure 31 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0041] Figure 32 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0042] Figure 33 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure.

[0043] Figure 34 This is a schematic diagram of one aspect of an exemplary embodiment of the present disclosure. Detailed Implementation

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

[0045] The embodiments can be configured to operate as needed. The disclosed mechanisms can be executed when certain criteria are met, such as in wireless devices, base stations, radio environments, networks, combinations thereof, etc. Example criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, service characteristics, combinations thereof, etc. Various example embodiments can be applied when one or more criteria are met. Therefore, it is possible to implement example embodiments that selectively implement the disclosed protocols.

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

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

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

[0049] The term "configured" may relate to the capacity of a device, regardless of whether the device is in an operational or non-operational state. Configuration can refer to specific settings within the device that affect its operational characteristics, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within the device to provide specific characteristics, regardless of whether the device is in an operational or non-operational state. Terms such as "control messages induced in the device" may mean that control messages have parameters that can be used to configure specific characteristics or to implement certain actions within the device, regardless of whether the device is in an operational or non-operational state.

[0050] In this disclosure, parameters may include one or more information objects, and information objects may include one or more other objects. For example, if parameter J includes parameter K, 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 the example embodiment, when one or more messages include multiple parameters, this means that one of the multiple parameters is in at least one of the one or more messages, but not necessarily in every one of the one or more messages.

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

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

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

[0054] Wireless device 101 can communicate with DN 108 via AN 102 and CN 105. In this disclosure, the term "wireless device" can refer to and include any mobile or fixed (non-mobile) device that requires or can use wireless communication. For example, a wireless device can be a telephone, smartphone, tablet, computer, laptop, sensor, instrument, wearable device, Internet of Things (IoT) device, roadside unit (RSU) of a vehicle, relay node, automobile, drone, urban air traffic, and / or any combination thereof. The term "wireless device" includes other terms including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handheld device, wireless transmitting and receiving unit (WTRU), and / or wireless communication equipment.

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

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

[0057] AN 102 may include one or more base stations, each having one or more coverage areas. The geographical size and / or extent of a coverage area can be defined based on the range within which a receiver of AN 102 can successfully receive transmissions from a transmitter (e.g., wireless device 101) operating within the coverage area (and vice versa). A coverage area may be referred to as a sector or cell (although in some cases, the term cell refers to the carrier frequency used in a particular coverage area, rather than the coverage area itself). A base station with a large coverage area may be referred to as a macrocell base station. Other base stations cover smaller areas, for example, providing coverage in areas with weak macrocell coverage, or providing 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 femtocell base stations. The coverage areas of the base stations can together provide radio coverage to wireless device 101 over a wide geographical area to support wireless device mobility.

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

[0059] Figure 1B Another example communication network 150 in which embodiments of the present disclosure can be implemented is shown. Communication network 150 may include, for example, a PLMN operated by a network operator. Figure 1B As shown, the communication network 150 includes a UE 151, a Next-Generation Radio Access Network (NG-RAN) 152, a 5G Core Network (5G-CN) 155, and one or more DNs 158. The NG-RAN 152 includes one or more base stations, shown as a Next-Generation Evolved 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), including control plane function 155A and user plane function 155B. The one or more DNs 158 may include public DNs (e.g., the Internet), private DNs, and / or operator-internal DNs. (Relative to...) Figure 1A The corresponding components shown may represent specific implementation methods and / or terms.

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

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

[0062] One or more base stations in NG-RAN 152 can be divided into a Central Unit (CU) and one or more Distributed Units (DUs). The CU can be coupled to one or more DUs via an F1 interface. The CU can handle one or more upper layers of the protocol stack, and the DU can handle one or more lower layers of the protocol stack. For example, the CU can handle RRC, PDCP, and SDAP, while the DU can handle RLC, MAC, and PHY. One or more DUs can be located geographically different from the CU and / or from each other. Therefore, a CU / DU separation architecture can allow for increased coverage and / or better coordination.

[0063] The gNB 152A and ng-eNB 152B can provide different user plane and control plane protocol terminations to UE 151. For example, the gNB 154A can provide a new radio (NR) protocol termination on the Uu interface associated with the first protocol stack. The Ng-eNB 152B can provide evolved UMTS terrestrial radio access (E-UTRA) protocol termination through the Uu interface associated with the second protocol stack.

[0064] The 5G-CN 155 can authenticate UE 151, establish end-to-end connections between UE 151 and one or more DNs 158, and provide billing functions. The 5G-CN 155 can be based on a service-based architecture, in which the NFs comprising the 5G-CN 155 provide services to each other and to other elements of the communication network 150 through interfaces. The 5G-CN 155 can include any number of other NFs and any number of instances of each NF.

[0065] Figure 2A , Figure 2B , Figure 2C and Figure 2D Various examples of service-based architecture frameworks within the core network are illustrated. In a service-based architecture, service consumers can seek services, and service producers can provide those services. Before obtaining a specific service, an NF can determine where such a service can be obtained. To discover services, an NF can communicate with a Network Repository Function (NRF). For example, an NF providing one or more services can register with the NRF. The NRF can store data related to one or more services that an NF is preparing to provide to other NFs in the service-based architecture. Consumer NFs can query the NRF to discover producer NFs (e.g., by obtaining a list of NF instances providing a specific service from the NRF).

[0066] exist Figure 2A In the example, NF 211 (the consumer NF in this example) can send request 221 to NF 212 (the producer NF). Request 221 can be a request for a specific service and can be sent based on the discovery that NF 212 is the producer of that service. Request 221 can include data related to NF 211 and / or the requested service. NF 212 can 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 can be based on the requested data included in request 221, data stored by NF 212, and / or data retrieved by NF 212. Response 222 can notify NF 211 that one or more actions have been completed. Response 222 can include response data related to NF 212, one or more actions, and / or the requested service.

[0067] exist Figure 2B In the example, NF 231 sends request 241 to NF 232. In this example, part of the service provided by NF 232 is sending request 242 to NF 233. NF 233 can perform one or more actions and provide a response 243 to NF 232. Based on response 243, NF 232 can send response 244 to NF 231. Figure 2B It is understood that a single NF can act as a service producer, a service consumer, or both. A specific NF service can include any number of nested NF services produced by one or more other NFs.

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

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

[0070] Figure 2D This shows another example of a subscription notification interaction. Figure 2D In this context, NF 271 sends subscription 281 to NF 272. In response to receipt of subscription 281 and / or confirmation that notification conditions have occurred, NF 272 may send notification 284. Notification 284 may then be sent to NF 273. Figure 2C The example in [the example] (where notifications are sent to the subscribed NF) is different. Figure 2D This demonstrates that subscriptions and their corresponding notifications can be associated with different NFs. For example, NF 271 can subscribe to a service provided by NF 272 on behalf of NF 273.

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

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

[0073] Figure 3 Each element depicted has an interface with at least one other element. The interface can be a logical connection, rather than, for example, a direct physical connection. Any interface can be identified using a reference point representation and / or a service-based representation. In the reference point representation, the letter "N" followed by a number indicates the interface between two specific elements. For example, as... Figure 3As shown, AN 302 and UPF 305 interface via “N3”, while UPF 305 and DN 308 interface via “N6”. In contrast, in service-based representations, the letter “N” is followed by another letter. These letters identify the NFs providing 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”. Therefore, service-based representations can correspond to a set of reference point representations. For example, the Npcf interface between PCF 320 and the core network can typically correspond to the N7 interface between PCF 320 and SMF 314, the N30 interface between PCF 320 and NEF 340, and so on.

[0074] UPF 305 can be used as a gateway for user plane services between AN 302 and DN 308. UE 301 can connect to UPF 305 via the Uu interface and the N3 interface (also known as the NGU interface). UPF 305 can connect to DN 308 via the N6 interface. UPF 305 can connect to one or more other UPFs (not shown) via the N9 interface. UE 301 can be configured to receive services via Protocol Data Unit (PDU) sessions, which are logical connections between UE 301 and DN 308. SMF 314 can select UPF 305 (or multiple UPFs if needed) to handle specific PDU sessions between UE 301 and DN 308. SMF 314 can control the functionality of UPF 305 regarding PDU sessions. SMF 314 can connect to UPF 305 via the N4 interface. UPF 305 can handle any number of PDU sessions (via any number of ANs) associated with any number of UEs. To handle one or more PDU sessions, the UPF 305 can be controlled by any number of SMFs via any number of corresponding N4 interfaces.

[0075] Figure 3 The AMF 312 described herein can control the UE's access to the core network. UE 301 can register with the network through the AMF 312. UE 301 may need to register before establishing a PDU session. The AMF 312 manages the UE 301's registration area, enabling the network to track the UE 301's physical location within the network. For UEs in connected mode, the AMF 312 can manage UE mobility, such as switching from one AN or part thereof to another AN. For UEs in idle mode, the AMF 312 can perform registration updates and / or page the UE to transition it to connected mode.

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

[0077] Figure 3 The SMF 314, as depicted, can establish, modify, and / or release PDU sessions based on messages received by UE 301. For example, when establishing a PDU session, the SMF 314 can allocate, manage, and / or assign IP addresses to UE 301. Multiple SMFs may exist in the network, each potentially associated with a corresponding set of radio devices, base stations, and / or UPFs. A UE with multiple PDU sessions can be associated with a different SMF for each PDU session. As described above, the SMF 314 can select one or more UPFs to handle PDU sessions and can control the processing of PDU sessions by the selected UPFs by providing packet processing rules (PDR, FAR, QER, etc.). Rules related to QoS and / or charging for a specific PDU session can be obtained from the PCF 320 and provided to the UPF 305.

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

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

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

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

[0082] AUSF 360 can support mutual authentication between the core network and UE 301, as well as authentication between UE 301 and the core network. AUSF 360 can perform key negotiation processes and provide key materials that can be used to improve security.

[0083] The NSSF 370 can select one or more network slices for use by the UE 301. The NSSF 370 can select slices based on slice selection information. For example, the NSSF 370 can receive Single Network Slice Selection Assistance Information (S-NSSAI) and map the S-NSSAI to a Network Slice Instance Identifier (NSI).

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

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

[0086] AF 399 can operate outside the core network but can interact with it to provide information related to application-specific QoS requirements or traffic routing preferences. AF 399 can access the core network based on exposure constraints imposed by NEF 340. However, the core network operator can treat AF 399 as a trusted domain with direct network access.

[0087] Figure 4A , Figure 4B and Figure 5 It shows something similar in some respects Figure 3 Other examples of the core network architecture of the core network architecture 300 shown are omitted for simplicity. Figure 3 Some of the core network elements described in the text. Figure 4A , Figure 4B and Figure 5 Many of the elements depicted in the text are similar in some respects to Figure 3 The elements depicted are shown in the image. For the sake of brevity, some details related to their function or operation have been omitted.

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

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

[0090] In addition to indicating how to detect a specific packet, a PDR can also indicate the rules used to process that packet when it is detected. These rules can include, for example, Forwarding Action (FAR) rules, Multiple Access (MAR) rules, Usage Reporting (URR) rules, QoS Enforcement (QER) rules, etc. For example, a PDR can include one or more FAR identifiers, MAR identifiers, URR identifiers, and / or QER identifiers. These identifiers can indicate the rules specified for processing a particular detected packet.

[0091] UPF 405 can perform traffic forwarding based on FARs. For example, a FAR can instruct packets associated with a specific PDR to be forwarded, copied, dropped, and / or buffered. A FAR can specify the destination interface, such as "access" for downlink or "core" for uplink. If packets need to be buffered, a FAR can instruct a Buffer Action Rule (BAR). For example, if a PDU session is deactivated, UPF 405 can perform data buffering for a specific number of downlink packets.

[0092] UPF 405 can enforce QoS based on QERs. For example, a QER can indicate the authorized guaranteed bit rate and / or the maximum bit rate to be enforced for packets associated with a particular PDR. A QER can indicate specific guaranteed and / or maximum bit rates that can be used for uplink and / or downlink packets. UPF 405 can mark packets belonging to a specific QoS flow with corresponding QFIs. Marking allows the packet receiver to determine the QoS of the packet.

[0093] UPF 405 can provide usage reports to SMF 414 based on URRs. A URR can indicate one or more triggering conditions for generating and reporting the usage report, such as immediate reporting, periodic reporting, a threshold for incoming uplink traffic, or any other suitable triggering condition. A URR can also indicate methods for measuring network resource usage, such as data volume, duration, and / or events.

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

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

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

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

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

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

[0100] Figure 4B An example of a 400B core network architecture accommodating untrusted access is shown. Figure 4A Similarly, such as Figure 4B The UE 401 shown is connected to DN 408 via AN 402 and UPF 405. AN 402 and UPF 405 constitute trusted (e.g., 3GPP) access to DN 408. In contrast, UE 401 can also access DN 408 using untrusted access network AN 403 and non-3GPP interoperability function (N3IWF) 404.

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

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

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

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

[0105] Figure 5 The core network architecture 500 described can be referred to as the local interruption configuration, in which UE 501 accesses DN 508 using one or more UPFs (i.e., UPF 505) of the VPLMN. However, other configurations are also possible. For example, in the home routing configuration ( Figure 5 (Not shown in the diagram) In this configuration, UE 501 can use one or more UPFs of the HPLMN to access the DN. In the home routing configuration, the N9 interface can operate in parallel with the N32 interface, carrying user plane data across the boundary between the VPLMN and HPLMN. One or more SMFs of each PLMN can communicate via the N32 interface to coordinate session management of UE 501. The SMF can control its respective UPF on both sides of the boundary.

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

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

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

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

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

[0111] If the service requirements for one of UEs 601 change, the network slice providing the service to that UE can be updated to offer better service. Furthermore, the network feature sets corresponding to eMBB, URLLC, and mMTC can change, thus providing different types of eMBB, URLLC, and mMTC. Alternatively, network operators can provide entirely new services in response to, for example, customer demands.

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

[0113] Network slice selection can be controlled by the AMF (Agency Management Function) or by a separate Network Slice Selection Function (NSSF). For example, network operators can define and implement different Network Slice Instances (NSIs). Each NSI can be associated with a single Network Slice Selection Assistance Information (SNSSAI). SNSSAIs can include specific slice / service type (SST) indicators (indicating eMBB, URLLC, mMTC, etc.). For example, a specific tracking area can be associated with one or more configured SNSSAIs. The UE can identify one or more requested and / or subscribed SNSSAIs (e.g., during registration). The network can indicate one or more allowed and / or denied SNSSAIs to the UE.

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

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

[0116] These layers can be associated with the Open Systems Interconnection (OSI) model for computer networking capabilities. In the OSI model, Layer 1 can correspond to the bottom layer, with higher layers above it. Layer 1 can correspond to the physical layer, which involves the physical infrastructure used to transmit signals (e.g., cables, optical fibers, and / or radio frequency transceivers). In New Radio (NR), Layer 1 can include the Physical Layer (PHY). Layer 2 can correspond to the Data Link Layer. Layer 2 may involve using the physical infrastructure of Layer 1 to package data between nodes in the network (e.g., packing it into data frames) for transmission. In NR, Layer 2 can include the Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Layer (PDCP) layer, and Service Data Application Protocol Layer (SDAP).

[0117] Layer 3 can correspond to the network layer. Layer 3 may involve routing data already packaged in Layer 2. Layer 3 can handle data prioritization and traffic avoidance. In NR, Layer 3 may include the Radio Resource Control (RRC) layer and the Non-Access Layer (NAS). Layers 4 through 7 can correspond to the transport, session, presentation, and application layers. The application layer interacts with the end user to provide application-related data. In one example, the end user implementing the application can generate application-related data and initiate the transmission of that information to a target data network (e.g., the Internet, an application server, etc.). Starting from the application layer, each layer in the OSI model can manipulate and / or repackage information and pass it down to lower layers. At the lowest layer, manipulated and / or repackaged information can be exchanged via physical infrastructure (e.g., electrical, optical, and / or electromagnetic). As it approaches the target data network, the information is unpacked and provided to increasingly higher layers until it reaches the application layer again in a form available to the target data network (e.g., the same form the end user provided it in). In response to the end user, the data network can reverse this process.

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

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

[0120] NAS can relate to the non-access stratum, specifically communication between UE 701 and the core network (e.g., AMF 712). Lower layers can relate to the access stratum, such as communication between UE 701 and gNB 702. Messages sent between UE 701 and the core network can be called NAS messages. In one example, gNB 702 can relay NAS messages, but gNB 702 may not see the content of the NAS message (e.g., the information elements of the NAS message).

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

[0122] PDCP 761 and PDCP 762 can perform header compression and / or decompression. Header compression reduces the amount of data transmitted through the physical layer. PDCP 761 and PDCP 762 can perform encryption and / or decryption. Encryption reduces unauthorized decoding of data transmitted through the physical layer (e.g., interception on the air interface) and protects data integrity (e.g., ensuring control messages originate from the intended source). PDCP 761 and PDCP 762 can perform retransmission of undelivered packets, packet reordering and repackaging, packet duplication, and / or identification and removal of duplicate packets. In dual-connectivity scenarios, PDCP 761 and PDCP 762 can perform mapping between separate radio bearers and RLC channels.

[0123] RLC 751 and RLC 752 can perform segmentation and retransmission via Automatic Repeat Request (ARQ). RLC 751 and RLC 752 can remove duplicate data units received from MAC 741 and MAC 742, respectively. RLC 213 and 223 can provide RLC channels as services to PDCCH 214 and 224, respectively.

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

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

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

[0127] exist Figure 8In the example, a PDU session 810 is established between UE 801 and UPF 805. PDU session 810 may be a logical connection enabling UE 801 to exchange data with a specific data network (e.g., the Internet). UE 801 may request the establishment of PDU session 810. When establishing PDU session 810, UE 801 may 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). To facilitate data exchange between UE 801 and the data network associated with PDU session 810, the SMF may select UPF 805 (and optionally one or more other UPFs, not shown).

[0128] One or more applications associated with UE 801 can generate uplink packets 812A-812E associated with PDU session 810. To operate within the QoS model, UE 801 can apply QoS rule 814 to uplink packets 812A-812E. QoS rule 814 can be associated with PDU session 810 and can be determined and / or provided to UE 801 when PDU session 810 is established and / or modified. Based on QoS rule 814, UE 801 can classify uplink packets 812A-812E, map each uplink packet 812A-812E to a QoS flow, and / or tag uplink packets 812A-812E with a QoS flow indicator (QFI). When a packet propagates through the network and potentially mixes with other packets from other UEs with potentially different priorities, the QFI indicates how the packet should be handled according to the QoS model. In this diagram, uplink packets 812A and 812B are mapped to QoS flow 816A, uplink packet 812C is mapped to QoS flow 816B, and the remaining packets are mapped to QoS flow 816C.

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

[0130] To function within the QoS model, UE 801 can apply resource mapping rule 818 to QoS flows 816A-816C. The air interface between UE 801 and AN 802 can be associated with resource 820. In this illustration, QoS flow 816A is mapped to resource 820A, while QoS flows 816B and 816C are mapped to resource 820B. Resource mapping rule 818 can be provided by AN 802. To meet QoS requirements, resource mapping rule 818 can specify more resources for relatively high-priority QoS flows. With increased 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 rule 814. Resource 820 may include, for example, radio bearers. Radio bearers (e.g., data radio bearers) can be established between UE 801 and AN 802. The radio bearers in 5G between UE 801 and AN 802 can be different from those in LTE, such as the Evolved Packet System (EPS) bearers between the UE and the Packet Data Network Gateway (PGW), the S1 bearers between the eNB and the Serving Gateway (SGW), and / or the S5 / S8 bearers between the SGW and the PGW.

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

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

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

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

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

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

[0137] In an RRC connection (930), the UE may exchange data with the network (e.g., a base station). Parameters required for this data exchange can be established, and these parameters are known to both the UE and the network. These parameters may be referenced to the UE's RRC context (sometimes referred to as the UE context) and / or contained within the UE's RRC context. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., related to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. The base station connected to the UE may store the UE's RRC context.

[0138] When in RRC Connection 930, the UE's mobility can be managed by the access network, while the UE itself can manage mobility when in RRC Idle 910 and / or RRC Inactive 920. When in RRC Connection 930, the UE can manage mobility by measuring signal levels (e.g., reference signal levels) from the serving cell and neighboring cells and reporting these measurements to the base station currently serving the UE. The network can initiate a handover based on the reported measurements. The RRC state can transition from RRC Connection 930 to RRC Idle 910 via Connection Release Procedure 930, or to RRC Inactive 920 via Connection Deactivation Procedure 932.

[0139] During RRC Idle 910, an RRC context may not be established for the UE. During RRC Idle 910, the UE may not have an RRC connection with the base station. When in RRC Idle 910, the UE may be in sleep mode most of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once in each discontinuous receive cycle) to monitor paging messages from the access network. UE mobility can be managed by the UE through a process called cell reselection. The RRC state can be transitioned from RRC Idle 910 to RRC Connection 930 through Connection Establishment Procedure 913, which may involve a random access procedure, discussed in more detail below.

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

[0141] RRC status can be associated with mobility management mechanisms. In RRC Idle 910 and RRC Inactive 920, the UE can manage mobility through cell reselection. The purpose of mobility management in RRC Idle 910 and / or RRC Inactive 920 is to allow the network to notify UE events via paging messages without broadcasting paging messages across the entire mobile network. The mobility management mechanisms used in RRC Idle 910 and / or RRC Inactive 920 allow the network to track the UE at the cell group level so that paging information can be broadcast on the cell of the UE's current cell group instead of across the entire network. Tracking can be based on different packet granularities. For example, there may be three levels of cell packet granularity: a single cell; cells within a RAN area identified by a RAN Area Identifier (RAI); and a group of cells within a RAN area (called a tracking area and identified by a Tracking Area Identifier (TAI)).

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

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

[0144] A base station that stores the RRC context of the UE or the UE's last serving base station can be called an anchor base station. The anchor base station may maintain the UE's RRC context at least during the time period when the UE is in the anchor base station's RAN notification area and / or during the time period when the UE is in RRC inactivity.

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

[0146] In RM Deregistration 940, the UE has not registered with the network, and the network cannot reach the UE. To reach the network, the UE must perform an initial registration. For example, the UE can register with the network's AMF. If registration is rejected (Registration Rejection 944), the UE remains in RM Deregistration 940. If registration is accepted (Registration Acceptance 945), the UE transitions to RM Registration 950. When the UE is in RM Registration 950, the network can store, save, and / or maintain the UE's UE context. The UE context can be referred to as the radio device context. The UE context corresponding to network registration (maintained by the core network) can be different from the RRC context corresponding to RRC status (maintained by the access network (e.g., 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, UE access and mobility management policy information, a list of allowed or established slices or PDU sessions, and / or the UE's registration area (i.e., a list of tracking areas covering the geographic area where the radio device may be found).

[0147] When a UE registers with the RM (Registration Manager) at 950, the network can store the UE's UE context and use it to reach the UE when necessary. Furthermore, the network may be unable to provide certain services unless the UE is registered. A UE can update its UE context while remaining in RM registration at 950 (Registration Update Acceptance 955). For example, if a UE leaves one tracking area and enters another, the UE can provide the network with a tracking area identifier. The network can deregister the UE, or the UE can deregister itself (Deregistration 954). For example, if a radio device is inactive for a certain period, the network can automatically deregister that radio device. After deregistration, the UE can proceed to RM Deregistration at 940.

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

[0149] In CM Idle 960, the UE has no Non-Access Stratum (NAS) signaling connection to the network. Therefore, the UE cannot communicate with core network functions. The UE can transition to CM Connection 970 by establishing an AN signaling connection (AN signaling connection establishment 967). This transition can be initiated by sending an Initial NAS message. The Initial NAS message can be a registration request (e.g., if the UE is RM Deregistration 940) or a service request (e.g., if the UE is RM Registration 950). If the UE is RM Registration 950, the UE can initiate AN signaling connection establishment by sending a service request, or the network can send a paging request, thereby triggering the UE to send a service request.

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

[0151] Figure 9D This is an example diagram illustrating the CM state transitions of a wireless device (e.g., a UE) from a network perspective (e.g., the AMF). The UE's CM state, tracked by the AMF, can 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 can establish the UE's N2 context (N2 context establishment 989). When the UE transitions from CM Connected 990 to CM Idle 980, the AMF releases the UE's N2 context (N2 context release 998).

[0152] Figure 10-12 An example procedure for UE registration, service request, and PDU session establishment is shown.

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

[0154] To obtain authorization to receive services, implement mobility tracking, achieve reachability, or for other purposes, a UE can initiate registration. A UE can perform initial registration as the first step in connecting to the network (e.g., if the UE is powered on, airplane mode is off, etc.). Registration can also be performed periodically to inform the network of the UE's presence (e.g., when in CM-IDLE state), or in response to changes in UE capabilities or registration area. Deregistration can be performed. Figure 10 (Not shown in the image) to stop network access.

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

[0156] At position 1020, the AMF (AMF#2) that received the registration request performs a context transfer. This context can be the UE context, such as the UE's RRC context. For example, AMF#2 can send a message to AMF#1 requesting the UE's context. This message can include the UE identifier. This message can be a Namf_Communication_UEContextTransfer message. AMF#1 can send a message to AMF#2 including the requested UE context. This message can also be a Namf_Communication_UEContextTransfer message. After receiving the UE context, AMF#2 can coordinate the UE's authentication. After authentication is complete, AMF#2 can send a message to AMF#1 indicating that the UE context transfer is complete. This message can be a Namf_Communication_UEContextTransfer response message.

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

[0158] At position 1030, the new AMF (AMF#2) registers and / or subscribes to the UDM. AMF#2 can perform registration using the UDM's UE Context Management Service (Nudm_UECM). AMF#2 can use the UDM's Subscriber Data Management Service (Nudm_SDM) to obtain the UE's subscription information. If the UE's subscription information changes, AMF#2 can also request the UDM to notify AMF#2. With the new AMF registering and subscribing, the old AMF (AMF#1) can deregister and unsubscribe. After deregistration, AMF#1 is no longer responsible for the UE's mobility management.

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

[0160] For example, access and mobility policies may involve service area restrictions, RAT / Frequency Selection Priority (RFSP, where RAT stands for Radio Access Technology), access type authorization and prioritization (e.g., LTE vs. 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 that allow (or prohibit) service to the UE. Access and mobility policies may include UE Routing Selection Policy (URSP), which affects the routing of established PDU sessions or new PDU sessions. As mentioned above, different policies may be obtained and / or enforced 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.

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

[0162] At position 1060, AMF#2 sends a registration acceptance message to the AN, which forwards the message to the UE. The registration acceptance message may include a new UE identifier and / or a newly configured slice identifier. The UE may send a registration completion message to the AN, which forwards it to AMF#2. The registration completion message acknowledges receipt of the new UE identifier and / or the newly configured slice identifier.

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

[0164] Figure 11 An example of a service request process for a wireless device (e.g., a UE) is shown. Figure 11 The service request procedure described herein is a network-triggered service request procedure for a UE in CM-IDLE state. However, other service request procedures (e.g., UE-triggered service request procedures) can also be found by referring to [reference needed]. Figure 11 To understand this, we will discuss it in more detail below.

[0165] At 1110, the UPF receives data. This data may be downlink data for transmission to the UE. This data may be associated with an existing PDU session between the UE and the DN. For example, data may be received from the DN and / or another UPF. The UPF may buffer the received data. In response to the data reception, 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. This notification may be, for example, an N4 session report. This notification may indicate that the UPF has received data associated with the UE and / or a specific PDU session associated with the UE. In response to receiving the notification, the SMF may send PDU session information to the AMF. The PDU session information may be sent in an N1N2 message transmission for forwarding to the AN. The PDU session information may include, for example, UPF tunnel endpoint information and / or QoS information.

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

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

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

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

[0170] At 1160, AMF and SMF can perform PDU session updates. As part of the PDU session update, SMF can provide AMF with one or more UPF tunnel endpoint identifiers. In some cases ( Figure 11 (not shown in the image) An SMF may need to coordinate with one or more other SMFs and / or one or more other UPFs to establish a user plane.

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

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

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

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

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

[0176] Figure 12 An example of a Protocol Data Unit (PDU) session establishment process for a wireless device (such as a UE) is shown. The UE may decide to send a PDU session establishment request to create a new PDU session, to switch an existing PDU session to the 3GPP network, or for any other suitable reason.

[0177] At 1210, the UE initiates a PDU session establishment. The UE can send a PDU session establishment request to the AMF via the AN. The PDU session establishment request can be a NAS message. The PDU session establishment request can indicate: the PDU session ID; the requested PDU session type (new or existing); the requested DN (DNN); the requested network slice (S-NSSAI); the requested SSC mode; and / or any other suitable information. The PDU session ID can be generated by the UE. The PDU session type can 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.

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

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

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

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

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

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

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

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

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

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

[0188] Figure 13 An example of a component in a communication network is shown. Figure 13A physical deployment 1330 (hereinafter referred to as "Deployment 1330") including wireless device 1310, base station 1320, and one or more network functions. Any wireless device described in this disclosure may have similar components and may be implemented in a similar manner to wireless device 1310. Any other base station (or any part thereof, depending on the architecture of the base station) described in this disclosure may have similar components and may be implemented in a similar manner to base station 1320. Any physical core network deployment (or any part thereof, depending on the architecture of the base station) in this disclosure may have similar components and may be implemented in a similar manner to deployment 1330.

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

[0190] 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 executing 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 one example, downlink data received from base station 1320 may be stored in memory 1312, and uplink data for transmission to base station 1320 may be retrieved from memory 1312. Figure 13 As shown, wireless device 1310 can communicate with base station 1320 using transmitting processing system 1314 and / or receiving processing system 1315. Alternatively, transmitting processing system 1314 and receiving processing system 1315 can be implemented as a single processing system, or both can be omitted, and all processing in wireless device 1310 can be performed by processing system 1311. Although Figure 13Not shown, but the transmitting processing system 1314 and / or the receiving processing system 1315 may be coupled to a dedicated memory similar to but separate from memory 1312, and containing instructions that can be processed and / or executed to perform one or more of their respective functions. The wireless device 1310 may include one or more antennas 1316 for access to the air interface 1370.

[0191] Wireless device 1310 may include one or more other elements 1319. These other elements 1319 may include software and / or hardware providing features and / or functionality, such as a speaker, microphone, keyboard, display, touchpad, satellite transceiver, Universal Serial Bus (USB) port, hands-free headset, FM radio unit, media player, internet browser, electronic control unit (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometer, gyroscope, temperature sensor, radar sensor, lidar sensor, ultrasonic sensor, light sensor, camera, GPS sensor, etc.). Wireless device 1310 may receive user input data from and / or provide user output data to these other elements 1319. These other elements 1319 may include a power source. Wireless device 1310 may receive power from the power source and may be configured to distribute power to other components within wireless device 1310. The power source may include one or more power sources, such as a battery, solar cell, fuel cell, or any combination thereof.

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

[0193] Base station 1320 may include processing system 1321 and memory 1322. Memory 1322 may include one or more computer-readable media, such as one or more non-transitory computer-readable media. Memory 1322 may 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 transmitting processing system 1324 and receiving processing system 1325. Although Figure 13 Not shown, but the transmitting processing system 1324 and / or the receiving processing system 1325 may be coupled to a dedicated memory similar to but separate from memory 1322, and containing instructions that can be processed and / or executed to perform one or more of their respective functions. The wireless device 1320 may include one or more antennas 1326 for access to the air interface 1370.

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

[0195] Base station 1320 may include interface system 1327. Interface system 1327 may communicate with one or more base stations and / or one or more components in 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 communication via interface 1380. Figure 13In this configuration, interface 1380 connects base station 1320 to a single deployment 1330. However, it should be understood that wireless device 1310 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 other elements 1319.

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

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

[0198] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs a defined function and has a defined interface with other elements. The modules described in this disclosure can be implemented as hardware that is behaviorally equivalent, software combined with hardware, firmware, wet hardware (e.g., hardware with biological elements), or a combination thereof. For example, a module can be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). It is possible to implement modules using physical hardware that includes 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 typically programmed using hardware description languages ​​(HDLs) such as VHSIC (VHDL) or Verilog, which configure connections between internal hardware modules with limited functionality on the programmable device. These techniques are often used in combination to achieve the desired functional modules.

[0199] Wireless device 1310, base station 1320, and / or deployment 1330 may implement timers and / or counters. A timer / counter may start from an initial value. Startup, as used herein, may include restarting. Once started, the timer / counter may run. The operation of the timer / counter may be event-dependent. When an event occurs, the value of the timer / counter may change (e.g., increment or decrement). Events may be, for example, exogenous events (e.g., signal reception, condition measurement, etc.), endogenous events (e.g., signal transmission, calculation, comparison, action execution, or decision to execute, etc.) or any combination thereof. In the case of a timer, an event may be the elapsed time of a specific amount of time. However, it should be understood that a timer may be described and / or implemented as a counter that counts the elapsed time of a specific unit of time. The timer / counter may run in the direction of a final value until the final value is reached. Reaching 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 paused, wherein the current value of the timer / counter is maintained, preserved, and / or continued even when one or more events that would otherwise cause a change in the value of the timer / counter occur. A timer / counter can be canceled from pause or resumed, whereby the value of a hold, sustain, and / or continuer begins to change again when one or more events occur. A timer / counter can be set and / or reset. As used herein, setting can include resetting. When a timer / counter is set and / or reset, its value can be set to its initial value. A timer / counter can be started and / or restarted. As used herein, starting can include restarting. In some embodiments, when a timer / counter is restarted, its value can be set to its initial value, and the timer / counter can begin running.

[0200] Figure 14A , Figure 14B , Figure 14C and Figure 14D Various example arrangements of physical core network deployments are shown, each physical core network deployment having one or more network functions or portions thereof. Core network deployments include deployment 1410, deployment 1420, deployment 1430, deployment 1440, and / or deployment 1450. Each deployment can be similar to, for example... Figure 13The deployment 1330 shown is illustrated. Specifically, each deployment may include a processing system for performing one or more functions or activities, 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 functions and / or one or more physical elements (e.g., processing systems and memory, where the memory includes instructions that, when executed by the processing system, cause the processing system to perform those functions) configured to perform those functions. For example, in this disclosure, when a network function is described as performing X, Y, and Z, it is understood that this means one or more physical elements are configured to perform X, Y, and Z, regardless of how or where such one or more physical elements are deployed. The term NF may refer to a network node, network element, and / or network device.

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

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

[0203] Figure 14B An example layout is shown where a single deployment includes more than one NF. (Compared to...) Figure 14A different, Figure 14A Each NF is deployed in a separate deployment. Figure 14BMultiple NFs in deployments 1410 and 1420 are shown. In one example, deployments 1410 and 1420 can implement Software-Defined Networking (SDN) and / or Network Functions Virtualization (NFV).

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

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

[0206] Figure 14CAn example layout of the core network deployment is shown, in which multiple different deployments are used to implement a single instance of an NF. Specifically, a single instance of NF 1422 is implemented at deployments 1420 and 1440. For example, the functionality provided by NF 1422 can be implemented as a bundle or sequence of subservices. Each subservice can be implemented independently, for example, at a different deployment. Each subservice can be implemented in a different physical location. By distributing the implementation of the subservices of a single NF across different physical locations, mobile communication networks can operate with higher speed, coverage, security, and / or efficiency.

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

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

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

[0210] In such Figure 15A and Figure 15B In the example embodiment shown, the UE can access the 3GPP system (network) via (using) one or more access types. For example, one or more access types may include at least one of 3GPP access types, non-3GPP (N3GPP) access types, and / or combinations thereof.

[0211] For example, such as Figure 15A As shown, a UE can access the network via a 3GPP access type. For example, network access via a 3GPP access type can be through one or more 3GPP RANs. For instance, one or more 3GPP RANs can include at least one of the following: Global System for Mobile Communications (GSM) Evolution Global Enhanced Data Rate (EDGE) Radio Access Network (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved UTRAN (E-UTRAN), Next Generation Radio Access Network (NG-RAN), and / or combinations thereof. The network operator can trust the UE's network access via a 3GPP access type because one or more 3GPP RANs are managed and / or deployed by the operator.

[0212] For example, such as Figure 15B As shown, a UE can access the network via N3GPP access (e.g., N3GPP access type). For example, network access via N3GPP access type can be via one or more N3GPP RANs (or N3GPP ANs). For example, one or more N3GPP RANs can include at least one of trusted WiFi, untrusted WiFi, wired broadband, WiMAX, and / or combinations thereof. Network operators may not trust network access via N3GPP access type because they may not manage or deploy one or more N3GPP RANs. To prevent unauthorized access by the UE via one or more N3GPP RANs and / or protect data / signaling, non-3GPP interoperability functions (N3IWF) can be used for N3GPP access type. For example, N3IWF can be used for interoperability between one or more non-3GPP RANs and the 5G core network.

[0213] In such Figure 16In the example embodiment shown, the UE can exchange one or more data with the data network (DN) via 3GPP access (type). The 3GPP access (type) can use one or more 3GPP RATs. The one or more 3GPP RATs can include at least one of NR, E-UTRA, UTRA, GSM, and / or combinations thereof. The 3GPP access can use one or more 3GPP RANs. The one or more 3GPP RANs can include at least one of NG-RAN, E-UTRAN, UTRAN, GERAN, and / or combinations thereof. The 3GPP RAN can use one or more 3GPP RATs. The one or more 3GPP RANs can interface with one or more core networks. The one or more core networks can include at least one of 5G core (5GC), evolved packet core (EPC), packet core (PC), network switching system (NSS), and / or combinations thereof.

[0214] In such Figure 17 In the example embodiment shown, the UE can exchange one or more data with a data network via N3GPP access (type). N3GPP access can use one or more N3GPP RATs. One or more N3GPP RATs can include at least one of trusted WiFi, untrusted WiFi, wired broadband, and / or combinations thereof. N3GPP access can use one or more N3GPP access networks (nodes). One or more N3GPP access network nodes can include at least one of N3IWF, evolved packet data gateway (ePDG), trusted non-3GPP gateway function (TNGF), wired access gateway function (W-AGF), and / or combinations thereof. One or more N3GPP access nodes can interface with one or more core networks (e.g., EPC and / or 5GC).

[0215] In such Figure 18In the example embodiment shown, the UE can establish a Multiple Access PDU (MA PDU) session with the network. If the UE and network support Access Traffic Switching Split (ATSSS) functionality (an ATSSS feature), then an MA-PDU session can be supported. The ATSSS feature can enable MA PDU connectivity services, which can exchange one or more PDUs between the UE and the data network via a first tunnel of 3GPP access (e.g., an N3 / N9 tunnel between a UPF (e.g., an anchor UPF, packet switching anchor) and the 3GPP RAN) and a second tunnel of non-3GPP access (e.g., an N3 / N9 tunnel between the UPF and the N3GPP RAN). MA PDU connectivity services can be implemented by establishing a Multiple Access PDU (MA PDU, MA-PDU) session. An MA PDU session can be a PDU session that has user plane resources on both 3GPP access and N3GPP access. For example, resources on 3GPP access may include those provided by 3GPP RATs (e.g., E-UTRA, NR), 3GPP RAN nodes (e.g., gNB, ng-eNB, eNB, en-gNB, etc., and / or combinations thereof), a first UPF (UPF-1, if configured between the anchor UPF and the 3GPP RAN), an anchor UPF, etc. Similarly, resources on N3GPP access may include those provided by N3GPP RATs (e.g., WiFi, WiMAX, wired broadband, etc.), N3GPP RAN nodes (e.g., ePDG, N3IWF, TNGF, W-GAN, etc., and / or combinations thereof), a second UPF (UPF-2, if configured between the anchor UPF and the N3GPP RAN), an anchor UPF, etc. For MA PDU sessions, the UE's data network or application can use the same identity (e.g., IP address). For example, the source IP address (and / or destination IP address) of a packet (e.g., PDU) of an MA PDU session sent via 3GPP access can be the same as the source IP address (and / or destination IP address) of a packet of an MA PDU sent via N3GPP access.

[0216] In one example, using two resources for an MA PDU session can provide enhanced reliability, efficient use of network resources, and / or adaptability to changing environments. For example, as... Figure 19 As shown, the UE and UPF (e.g., anchor UPF) can establish an MA PDU session. The MA PDU session can include 3GPP access and N3GPP access. For example, 3GPP access can use... Figure 18 The resources and / or N3GPP access shown can be used Figure 18 The resources shown. Return. Figure 193GPP and N3GPP access can offer different characteristics for data transmission. For example, 3GPP access can provide wider coverage than N3GPP access. N3GPP access can offer higher throughput than N3GPP access. By utilizing these different characteristics of the two accesses, network operators can determine how to transmit PDUs on both accesses in an MA PDU session. For example, if the two accesses offer similar performance, the operator can determine to distribute the load evenly across these accesses. For example, half of the PDUs (e.g., packets 1 and 3) can be transmitted via the 3GPP access, while the other half (e.g., packets 2 and 4) can be transmitted via the N3GPP access. In another example (not shown in the figure), if the transmission delay on the 3GPP access (e.g., 30 ms) is three times that on the N3GPP access (e.g., 10 ms), the operator can determine that the number of PDUs transmitted via the N3GPP access (e.g., packets 6, 7, and 8) is three times that transmitted via the 3GPP access (e.g., packet 5). In the prior art, for MA PDU sessions, core network nodes (e.g., AMF, SMF, UPF) may be able to distinguish one access type (e.g., 3GPP access type) from another access category (e.g., N3GPP access type) because different network nodes (e.g., gNB, N3IWF) are used for each access.

[0217] With the development of 5G systems (5GS), 3GPP access may also develop. For example... Figure 20As shown, one or more 3GPP RANs can be diverse and / or can be deployed in different areas. In the prior art, access nodes and / or radio access networks can be deployed as terrestrial nodes (on the ground) or at similar frequencies (e.g., 2GHz). In other words, access nodes can be deployed on the ground, in buildings, etc., and can use similar frequency bands due to limitations in supported frequencies. As a result, distinguishing (e.g., type 1) 3GPP RANs from other (e.g., type 2) 3GPP RANs may not offer much benefit. As 5G system equipment becomes smaller and the signals of power-limited UEs become capable of reaching satellites, deploying 3GPP access nodes on satellites may become feasible. For example, a first NG-RAN in one or more 3GPP RANs can be deployed in geostationary equatorial orbit (GEO). For example, a second NG-RAN in one or more 3GPP RANs can be deployed in low Earth orbit (LEO). For example, a third NG-RAN in one or more 3GPP RANs can be deployed as a terrestrial (e.g., on the ground, in a building) access network. For example, a fourth E-UTRAN in one or more 3GPP RANs can be deployed as a terrestrial access network. These different 3GPP RANs can provide different characteristics. For example, a first NG-RAN can provide coverage in remote areas where a terrestrial 3GPP RAN cannot be deployed. For example, a second NG-RAN can provide wider coverage than a terrestrial NG-RAN, but with reduced throughput. For example, one or more 3GPP RANs can connect to one or more 3GPP core networks. For example, one or more 3GPP core networks can belong to one or more networks. For example, a first NG-RAN and / or a second NG-RAN can connect to a first core network. For example, a third NG-RAN can connect to a second core network. For example, a first core network can belong to a first network and / or a first operator. For example, a second core network can belong to a second network and / or a second operator. In these diverse scenarios, using multiple 3GPP RANs for UE and / or MA PDU sessions may be beneficial, rather than using one 3GPP access and one N3GPP access. However, this may present a problem, as described below.

[0218] In such Figure 21 In the example embodiment shown, the UE can register with one or more core network nodes (or core network, network).

[0219] In one example, the UE may send a first message (e.g., a registration request message) to a first core network node (e.g., AMF, MME, etc.) of a first network. In response to receiving the first message, the first core network node may register itself with a data management node (e.g., a mobility management node) of the home network. For example, the home network may manage the UE's subscription. For example, the first core network node may send a second message (e.g., a Nudm message) to the data management node to register the UE with the data management node. After registering with the first network, the UE may determine to perform registration with another network. For example, to use the resources of multiple networks for an MA-PDU session, the UE may determine to perform registration with said other network. For example, the UE may search for one or more available networks. For example, the UE may find a second network and / or a third network. For example, if the signal strength of a third cell (based on) the third network is stronger than the signal strength of a second cell in the second network, the UE may select the third network for another registration.

[0220] In one example, the UE can send a third message to a third network. For example, the third message could request registration with the third network. A third core network node (e.g., AMF 3) of the third network can receive the third message. Based on the receipt of the third message, and / or based on the UE's subscription to the home network, the third core network node can determine to register with the data management node of the home network. For example, the third core network node can send a fourth message to the data management node.

[0221] In one example, the data management node can receive a fourth message. In response to receiving the fourth message, based on the fact that the fourth message was received from a third network, and / or based on the fact that a first core network node of the first network has registered the UE, the data management node can determine at least one of the following: the UE changes location, or the UE moves from the first network to the third network. For example, based on this determination, based on the fact that the third network does not support another registration, and / or based on the fact that the first network and the third network have no service agreement, the data management node can cancel the registration of the UE with the first core network node and can allow the registration of the third core network node at the data management node. For example, the first core network node and / or the first network can delete the UE's information from the first network and / or can stop providing the UE with any resources for data communication.

[0222] In one example, the UE may lose registration in the first network and / or the first core network node. To improve reliability and / or data rate, the UE may be unable to use the first RAN of the first network and / or may be unable to use the first RAN with other RANs of other networks. Existing technology may cause the UE to connect to an unsupported network (or a network without a service level agreement with other networks to use multiple RANs / core networks / networks), may reduce the UE's data connection opportunities (e.g., MA-PDU sessions), and / or may increase signaling exchange due to deregistration.

[0223] In another example, a UE may use one or more subscriptions (e.g., the UE may be equipped with multiple USIMs and / or multiple SUPIs and / or may operate two logically independent (partial) UE implementations within the same UE (e.g., two independent protocol stacks). Such a UE may be able to support secondary registration to a second network. However, these two registrations will be completely independent and will end up in different UPFs, DNs, slices, etc. For example, the UE may use a first subscription to a first network and / or the UE may use a second subscription to a second network. While this may prevent the first network from deleting the UE's registration, data exchange in the first network may be incompatible with data exchange in the second network when the UE performs registration to the second network. For example, the first IP address supported by the first subscription may be different from the second IP address supported by the second subscription. This may not properly support MA-PDU sessions if the QoS allowed by the first subscription is different from the QoS allowed by the second subscription. Moreover, it will not allow the use of multiple registrations to enhance reliability and / or increase data rates.

[0224] In the examples disclosed herein, the UE can indicate whether it supports secondary registration, whether the registration process is used for primary registration, and whether the registration process is used for secondary registration. This helps the network determine whether to send secondary network information to the UE. The secondary network information helps the UE identify a target network among one or more detected networks to perform secondary registration. This reduces the sending of unnecessary signaling to networks that do not support secondary registration. In another example, the data management node can receive secondary network information from the policy decision node and / or the turnaround management node. This helps the mobility management node transmit relevant information to the UE. In another embodiment, the home network can send information from one or more compatible networks for the UE to use one or more resources (e.g., radio access technology, radio access network, core network, network). This helps the UE determine whether to request secondary registration. This reduces congestion in signaling exchange. In another example, the radio access node can send information on whether the network supports secondary registration. This helps reduce signaling messages between the UE and the network.

[0225] In this specification, the term "5G access network" may be interpreted as or may refer to an access network that includes at least one of NG-RAN and / or non-3GPP AN and is connected to the 5G core network.

[0226] In this specification, the term "5G core network" can be interpreted as, or may refer to, the core network connected to the 5G access network. This can be the 5G core (5GC).

[0227] In this specification, the term "3GPP RAN" may be interpreted as, or may refer to, a radio access network using 3GPP RAT. For example, this may include at least one of gNB, eNB, ng-eNB, en-gNB, etc., and / or combinations thereof. For example, this may be at least one of E-UTRAN, NG-RAN, etc., and / or combinations thereof.

[0228] In this specification, the term "3GPP RAT" may be interpreted as or may refer to a radio access technology based on the Third Generation Partnership Project (3GPP). For example, this may include at least one of NR, E-UTRA, UTRA, GSM, and / or combinations thereof.

[0229] In this specification, the term "N3GPP RAN" can be interpreted as, or can refer to, an access network using a non-3GPP (N3GPP) RAT. This can be an N3GPP access network (AN). For example, this can include at least one of N3IWF, ePDG, TNGF, W-GAN, and / or combinations thereof.

[0230] In this specification, the term "network node" may be interpreted as or may refer to at least one of a core network node, an access node, a UE, and / or a combination thereof. A network may include one or more network nodes.

[0231] In this specification, the term "3GPP access node" can be interpreted as, or can refer to, an access node using the 3GPP RAT. For example, this may include at least one of gNB, eNB, ng-eNB, en-gNB, and / or combinations thereof.

[0232] In this specification, the term "N3GPP access node" can be interpreted as an access node using the N3GPP RAT. For example, this may include at least one of N3IWF, ePDG, TNGF, W-GAN, and / or combinations thereof.

[0233] In this specification, the term "N3GPP RAT" can be interpreted as, or may refer to, a radio access technology not based on the 3GPP RAT. This can be an access technology not developed by 3GPP. For example, this can include WiFi, trusted WiFi, untrusted WiFi, fixed access, wired broadband, and / or combinations thereof.

[0234] In this specification, the term "access type" can be interpreted as, or may refer to, the access type used to communicate with the network. For example, this can include a 3GPP access type (or 3GPP access) and / or an N3GPP access type (or N3GPP access). For example, if the access type is a 3GPP access type, this can indicate that the UE communicates with the network using one or more 3GPP RATs and / or via one or more 3GPP RANs. For example, if the access type is an N3GPP access type, this can indicate that the UE communicates with the network using one or more N3GPP RATs and / or via one or more N3GPP RANs. In one example, access can include at least one of sending data, receiving data, sending signaling messages, receiving signaling messages, performing registration, etc.

[0235] In this specification, the term "3GPP access type" may be interpreted as or may refer to access using one or more 3GPP PRATs and / or via one or more 3GPP RANs.

[0236] In this specification, the term "N3GPP access type" may be interpreted as or may refer to access using one or more N3GPP RATs and / or via one or more N3GPP RANs.

[0237] In this specification, the term "MA PDU session" can be interpreted as a PDU session that provides PDU connection services, which can use / establish one access type at a time, or use / establish one 3GPP access and one N3GPP access simultaneously, or use / establish more than one path of 3GPP access type simultaneously, or use / establish more than one path of N3GPP access type simultaneously.

[0238] In this specification, the term "NG-RAN" may be interpreted as or may refer to a base station, which may include at least one of gNB, ng-eNB, relay node, base station central unit (e.g., gNB-CU), base station distributed unit (e.g., gNB-DU), etc. This may be a radio access network connected to 5GC, supporting at least one of NR, E-UTRA, and / or combinations thereof.

[0239] In this specification, the term "E-UTRAN" may be interpreted as or may refer to a base station, which may include at least one of eNB, en-gNB, etc. This may be a radio access network connected to the evolved packet core (EPC) that supports at least one of NR, E-UTRA, and / or combinations thereof.

[0240] In this specification, the term "RAT type" can be interpreted as, or can refer to, the transmission technology used for 3GPP access and / or non-3GPP access in an access network. For example, a RAT type for 3GPP access may include at least one of NR, NB-IoT, E-UTRA, etc. For example, a RAT type for non-3GPP access may include at least one of untrusted non-3GPP, trusted non-3GPP, trusted IEEE 802.11 non-3GPP access, wired, wired cable, wired BBF, WiFi, etc.

[0241] In this specification, the term "core network node" may be interpreted as or may refer to core network equipment, which may include at least one of AMF, SMF, NSSF, UPF, NRF, UDM, PCF, SoR-AF, AF, DDNMF, MB-SMF, MB-UPF, MME, SGW, PGW, SMF+PGW-C, SMF+GGW-U, UDM+HSS, etc.

[0242] In this specification, the term "network system" may be interpreted as or may refer to a communication system and / or a generation of a communication system. For example, one or more network systems may include EPS, 5GS. For example, the first network system may be EPS. EPS may include one or more UEs, one or more eNBs, one or more en-gNBs, and one or more EPCs. One or more EPCs may include MME, SGW, PGW, etc. For example, the second network system may be 5GS. 5GS may include one or more UEs, one or more gNBs, one or more ng-eNBs, and one or more 5G core networks. One or more 5G core networks may include AMF, SMF, PCF, etc.

[0243] In this specification, the term "5G system" may be interpreted as or may refer to a 3GPP system consisting of at least one of a 5G access network (or NG-RAN), a 5G core network, and / or a UE.

[0244] In this specification, the term "EPS" may be interpreted as or may refer to a 3GPP system consisting of at least one of EPC, E-UTRAN and / or UE.

[0245] In this specification, the term "access path" can be interpreted as, or may refer to, the path between the UE and the network used for exchanging data and / or signaling. An access path can be an access tributary, path, access route (route), access track (track), access channel (channel), access corridor (corridor), etc. An access path can indicate (associated with) at least one of the following: a path from the UE to the RAN, a path from the UE to the core network, and a path from the RAN to the core network, and / or combinations thereof. For example, an access path can be defined as a pair of core networks and / or access networks. For example, if the access node and the core network may not be able to exchange control signaling, the path of data between the access node and the core network may not be an access path. For example, if a secondary node of the NG-RAN cannot exchange signaling messages with the AMF, the path from the secondary node of the NG-RAN to the core network may not be an access path. In one example, one or more access paths can be defined for an access type. One or more access paths can be established for an access type. In another example, an access path can be associated with one or more core networks (e.g., roaming network, access network, home network, anchor network) and / or access networks.

[0246] For example, for each access type, there may be one or more access paths. For example, one or more access paths can be used to transmit signaling messages for that access type. For example, there may be one or more (established, active) access paths (signaling, control message passing) between the UE and the core network (e.g., AMF, SMF, PCF). For each access path, there may be associated control plane connections. For example, for the UE, the AMF can exchange control messages with the first gNB and / or the UPF can exchange data with the first gNB and / or the second gNB. In this case, the UE can be considered to have a path. For example, a link via the first gNB can be an access path because the first gNB can exchange control plane signaling with the AMF (and / or SMF). For example, a link via the second gNB may not be considered a path because the AMF and the second gNB may not be able to exchange control plane signaling.

[0247] For example, an access path may include at least a control plane. For example, an access path may or may not have a user plane. An access path may not have a user plane before a bearer for transmitting user data (e.g., voice data, IP packets) is established. After the bearer is established, the access path may have a user plane.

[0248] For example, using Figure 20 For example, one or more access paths may include:

[0249] – The path from the UE to the 3GPP core via NG-RAN on a GEO satellite.

[0250] – The path from the UE to the 3GPP core via NG-RAN on a LEO satellite.

[0251] – The path from the UE to the 3GPP core via the NG-RAN (gNB) on land.

[0252] – The path from the UE to the 3GPP core via the NG-RAN (eNB) on land.

[0253] – The path from the UE via NG-RAN via the first 3GPP core (e.g., the first AMF) to the second 3GPP core (e.g., the second AMF).

[0254] For example, a UE may have one or more 3GPP access paths. One or more 3GPP access paths can be defined / established / associated for a 3GPP access type. Each of the one or more 3GPP access paths can support the delivery of control messages (e.g., registration request messages, PDU session establishment request messages, etc.) and / or control messages (e.g., initial UE messages, N2 messages, etc.) for 3GPP access nodes. For example, one or more 3GPP access paths may include at least one of the following:

[0255] - One or more Type 1 3GPP access paths: Type 1 3GPP access paths can be routes associated with the UE, NG-RAN, and core network.

[0256] - One or more Type II 3GPP access paths: Type II 3GPP access paths can be routes associated with the UE, E-UTRAN, and core network.

[0257] For example, a UE may have one or more N3GPP access paths. One or more N3GPP access paths can be defined, established, or associated for an N3GPP access type. Each of the one or more N3GPP access paths can support the delivery of control messages (e.g., registration request messages, PDU session establishment request messages, etc.) and / or control messages (e.g., initial UE messages, N2 messages, etc.) for N3GPP access nodes. For example, one or more N3GPP access paths may include at least one of the following:

[0258] - One or more Type I N3GPP access paths: Type I N3GPP access paths can be routes associated with the UE, N3IWF, and core network.

[0259] - One or more Type II N3GPP access paths: Type II N3GPP access paths can be routes associated with the UE, ePDG, and core network.

[0260] - One or more Type 3 N3GPP access paths: Type 3 N3GPP access paths can be routes associated with the UE, TNGF (Trusted Non-3GPP Gateway Function), and the core network.

[0261] - One or more Type 4 N3GPP access paths: Type 4 N3GPP access paths can be routes associated with the UE, W-AGF (Wired Access Gateway Function), and the core network.

[0262] In this specification, the term "home network" can be interpreted as or can refer to a network to which a UE has a subscription. For example, a UE may subscribe to services of a home network. For example, a UE may have a service agreement with a home network. For example, within the coverage area of ​​a home network, a UE may access the home network by using one or more RANs and / or one or more core network nodes of the home network. For example, outside the coverage area of ​​a home network, a UE may use one or more RANs of a visited network and / or one or more core network nodes of a visited (roaming) network. For example, a UE may use one or more RANs of a visited network, one or more RANs of a home network, one or more core network nodes of a home network, and / or one or more core network nodes of a visited (roaming) network. Based on the UE's subscription and / or based on the service agreement between the home network and / or the visited network, the visited network may determine whether to allow the UE of the home network to use the resources of one or more RANs of the visited network and / or the resources of one or more core network nodes of the visited network. Based on the resources used for the UE, the visited (accessing) network may send billing records to the home network. When a UE is not subscribed to a visited network, subscribing to a home network allows the UE to use the resources of the visited network.

[0263] In this specification, the term "secondary registration" can be interpreted as, or can refer to, registering with a second (or subordinate, secondary, controlled, etc.) network simultaneously with registering with a first (or master, main, controlling, primary, etc.) network. For example, upon power-on and / or when the UE is not registered with any network, the UE may perform a first (initial) registration with the first network. To add additional resources, increase reliability, improve data rates, etc., the UE may perform secondary (or additional, dual, multiple, concurrent, simultaneous, backup, etc.) registration with the second network. For example, when the UE performs secondary registration with the second network, the first network may not remove (delete, cancel, etc.) the UE's registration with the first network. For example, in this case, the UE may remain registered with the second network and / or may remain registered with the first network. For example, when the UE performs non-secondary registration with the second network (e.g., normal registration, not secondary registration), the first network may remove (delete, cancel, etc.) the UE's registration with the first network. For example, in this case, the UE may remain registered with the second network and / or may not remain registered with the first network.

[0264] In this specification, the term "primary network" can be interpreted as, or may refer to, the network that the UE maintains primary registration with. For example, the network used for the UE's first (initial, basic) registration after power-on can be the primary network. For example, the network used for the UE's first registration when the UE is not registered with any network can be the primary network; for example, when the UE registers with only one network, that one network can be the primary network. For example, the primary network can identify one or more networks for secondary registration. For example, the primary network can determine whether to use / allow another network as a secondary network. For example, the primary network can manage the UE's context information, determine the configuration used in secondary networks, determine whether to use a second network, determine to disable the use of secondary networks, and / or can pass some context information to secondary networks.

[0265] In this specification, the term "secondary network" can be interpreted as, or can refer to, the network to which the UE performs secondary registration. For example, after the UE registers with the primary network, it can simultaneously perform additional registration with another network. This other network can be a secondary network. When the UE registers with the secondary network, it can also register with the primary network. For example, the secondary network may have a service agreement with the primary network. For example, the mobility management node of the secondary network may communicate with the mobility management node of the primary network. For example, the UE may be allowed to register with the secondary network and / or be registered with the secondary network while simultaneously registering with the primary network. For example, registering with the secondary network may not result in the UE being deregistered from the primary network. For example, for the UE's configuration in the secondary network, the secondary network may contact the primary network for configuration assistance.

[0266] In this specification, the term "support for secondary networks" can be interpreted as, or may refer to, whether a node supports manipulating / processing one or more pieces of information associated with a secondary network. For example, if a first network supports the features of a secondary network, then the first network may be able to exchange data with a second network (corresponding to the secondary network), configure the UE with information associated with the second network, perform as a primary network, process information associated with the secondary network, act as a primary network, etc. Similarly, if a second network supports the features of a secondary network, then the second network may be able to exchange data with a first network (corresponding to the primary network), configure the UE with information associated with the secondary network, perform as a secondary network, process information associated with the secondary network, etc. Likewise, if a UE can manipulate / process one or more pieces of information associated with a primary network and / or a secondary network, then the UE may support the features of a secondary network. Features supporting secondary networks can be features supporting secondary registration, features supporting primary registration, etc. It should be noted that support for secondary networks may indicate the existence or potential establishment of an association between a first registration with the first network and a secondary registration with the second network. Therefore, if a UE supports multiple USIMs and secondary registration to the second network is completely independent of the first registration, the UE may not indicate support for the feature "Support Secondary Network".

[0267] In this specification, the term "mobility management node" may be interpreted as or may refer to a function and / or node that performs mobility management for the UE. For example, mobility management may be at least one of registration status management, context management, authorization management, registration area management, paging management, etc. For example, a mobility management node may include at least one of MME, AMF, etc.

[0268] In this specification, the term "allowed network" can be interpreted as, or can refer to, one or more networks to which the UE is permitted to perform secondary registration. For example, after registering with a primary network, the UE may be permitted to perform secondary registration with an allowed network. An allowed network may include one or more networks that allow the UE to perform secondary registration. For example, the UE may not be permitted to perform secondary registration with a network that is a non-allowed network. An allowed network can be one or more allowed networks used for secondary registration. An allowed network can be a network selected by the UE for performing secondary registration.

[0269] In one example, the UE may send a first registration request message to a first network. For example, the first registration may request one or more requested network slices. For example, the one or more requested network slices may indicate a first network slice, a second network slice, and / or a third network slice. The first network may not support some of the one or more requested network slices. For example, due to service limitations or resource shortages, the first network may reject the first network slice and / or the second network slice. For example, the first network may send a first registration acceptance message indicating that the first network slice and / or the second network slice is rejected, the third network slice is accepted, and / or network K can support the first network slice, and / or network N can support the second network slice. This can lead to unpredictable UE behavior. For example, if the UE needs both the first and second network slices, the UE may not be able to determine whether to choose network N or network K, resulting in prolonged service interruption time. For example, if the UE needs both the first and third network slices, the UE may not be able to determine whether to perform deregistration of the third network slice and choose network K, resulting in unnecessary registration. Alternatively, if the UE chooses network N, the UE may switch back and forth between network K and network N whenever data is generated for the second network slice. This can lead to ping-pong issues, potentially causing connection instability and possibly preventing proper support of MA-PDU sessions. Therefore, selecting a network associated with a rejected network slice may not improve system performance.

[0270] In another example, a UE may use one or more subscriptions. For instance, a UE may use a first subscription with a first network and / or a second subscription with a second network. While this may prevent the first network from deleting the UE's registration, data exchange in the first network may be incompatible with data exchange in the second network when the UE registers with the second network. For example, a first IP address supported by the first subscription may be different from a second IP address supported by the second subscription. If the QoS allowed by the first subscription differs from the QoS allowed by the second subscription, this may not properly support MA-PDU sessions.

[0271] Figure 22 An example embodiment of this disclosure can be described. In one example, the UE can perform a first registration with a first network via a first access path (e.g., a path from the UE via RAN 1 via AMF 1), can receive a list of secondary networks, can select a network from the list of secondary networks, and / or can perform secondary registration with a network. This can reduce the time required for the UE to access a specific network that supports multiple network services and / or secondary registration. For the sake of brevity, redundant details will be omitted based on other parts of this disclosure.

[0272] In one example, the UE can search for and / or select a first network. For example, the UE can search for one or more networks, and one or more cells within one or more networks. The one or more cells can use one or more 3GPP RATs, can be part of one or more 3GPP RANs, and / or can use 3GPP access types. The UE can select one cell (e.g., a first cell) from the one or more cells, and / or can determine that cell will be used for a first access path. The first access path can be a 3GPP access path, and / or can be associated with a 3GPP access type. For example, the first access path can use a first 3GPP RAN, and / or can be established in a first network. For example, the UE can select a first network after UE is connected, when the UE performs network reselection, and / or when the UE is not registered. For example, the UE can determine to perform a first registration with the first network. For example, the first network can be a home network or a (first) visited network. For example, the first registration can be a primary registration.

[0273] In one example, the UE may support features of secondary registration. Features of secondary registration may be at least one of the following: establishing (e.g., registering, using) one or more access paths via one or more networks, establishing (e.g., registering, using) one or more access paths of access type, exchanging one or more control messages associated with the secondary network via the primary network, identifying one or more registrations via one or more networks, performing primary registration, performing secondary registration, and performing (e.g., processing) multiple registrations to one or more networks.

[0274] In one example, to perform the first registration, the UE may send a first NAS message (e.g., NAS MSG 1) to the first mobility management node of the first network. For example, the UE may send the first NAS message via a first access path. For example, the UE may use a first subscription to register with the first network. For example, the first NAS message may be at least one of a registration request message, a service request message, an attach request, etc. For example, the first NAS message may indicate that the UE supports features of secondary registration, the UE requests primary registration, the UE requests information on one or more candidates of a secondary network, the UE requests service from a network that supports the secondary network (or may exchange signaling with the secondary network), etc. For example, the first mobility management node may be a first AMF, a first MME, etc.

[0275] In one example, the first access path may involve a first RAN (e.g., a first 3GPP RAN). If the UE supports the feature of secondary registration, when the UE is registered for primary registration (e.g., registration with the primary network), the UE may be able to send a second NAS message via a second (e.g., 3GPP) access path (of the secondary network). If the UE supports the feature of secondary registration, when the UE performs secondary registration (e.g., via a second 3GPP RAN and / or via a secondary network) while registering to a first registration (via the first 3GPP RAN), the UE may not overwrite / cancel / delete / remove the first registration and / or may retain the primary registration via the first access path (or the primary network). If the UE supports the feature of secondary registration, the UE may be able to exchange one or more NAS messages with the first core network (of the first network) using the first access path, or exchange one or more NAS messages with the second core network (of the second network) using the second access path, and / or a combination thereof. Similarly, if one or more network nodes are able to use / establish / identify / distinguish between secondary (e.g., second) registration and primary (e.g., first) registration, then one or more network nodes may support the feature of secondary registration.

[0276] In one example, after searching for and / or selecting a first cell for a first network, the UE can determine that the first network (e.g., used as the primary network) will be used for primary registration (connection).

[0277] In one example, the UE may construct a first NAS message (e.g., NAS MSG 1). The first NAS message may include at least one of the following: the UE's identifier (e.g., IMSI, SUPI, SUCI, GUTI, etc.), 5GS registration type, preferred network behavior, last accessed registration TAI, PDU session state, EPS NAS message container, payload container, 5GMM capabilities, requested NSSAI, etc. The UE's identifier may indicate the UE's identity. The 5GS registration type may indicate the type of registration requested. For example, the 5GS registration type may be at least one of the following: initial registration, mobility registration update, periodic registration update, emergency registration, SNPN onboarding registration, disaster roaming mobility registration update, disaster roaming initial registration, initial registration across multiple networks, primary registration, etc. For example, initial registration and / or primary registration across multiple networks may instruct the UE to perform a first (initial, primary, etc.) registration (e.g., not a secondary registration) with the first network. For example, the first NAS message may include a 5GS registration type set as primary registration. For example, preferred network behavior may instruct the UE to request one or more features supported by the network. For example, if a UE wants the network to support the feature of secondary registration, the preferred network behavior can be set to support the feature of secondary (e.g., multiple) registration.

[0278] In one example, the UE may send a first RRC message (e.g., RRC MSG 1) to a first 3GPP RAN (e.g., 3GPP RAN 1). For example, the first 3GPP RAN may include at least one of a first gNB, a first ng-eNB, a first eNB, a first en-gNB, etc. For example, the first RRC message may be at least one of an RRC setup request message, an RRC setup complete message, an RRC recovery request message, an RRC recovery complete message, an RRC UL transmission message, etc. For example, the first RRC message may include at least one of a first NAS message, an RRC establishment reason, etc. The RRC establishment reason may indicate that the RRC connection is used to establish a first access path and / or perform primary registration. The first 3GPP RAN may receive the first RRC message via a first cell of the first 3GPP RAN.

[0279] In one example, the first 3GPP RAN may send a first NG message to the first AMF. The first NG message may be at least one of the following: an initial UE message, an uplink NAS transmission, etc. The first NG message may include at least one of the following: the identifier of the first 3GPP RAN (and / or the first cell) (e.g., gNB ID, TAI, cell ID, 3GPP access RAN type, RAT type), a first NAS message, user location information, and RRC establishment reason. For example, the 3GPP access RAN type may indicate whether the first 3GPP RAN is an NG-RAN, a satellite NG-RAN, an E-UTRAN, etc.

[0280] In one example, the first AMF can receive a first NG message. Based on the first NAS message of the first NG message, the AMF can determine whether the UE requests a feature of secondary registration supported by the first network and / or whether the first NAS message is used for primary registration. For example, if the first NAS message includes a 5GS registration type set as primary registration, the AMF can determine that the UE requests at least one of support (or service) for multiple registrations, features of secondary registration, and / or primary registration.

[0281] In one example, if the first AMF determines that the UE supports the feature of secondary registration, the registration request is for primary registration, the UE requests registration, and / or the UE supports the feature of secondary registration, the first AMF may send a first Nudm message (e.g., Nudm MSG 1) to the data management node (e.g., UDM) of the home network. For example, the first Nudm message may be at least one of the following: Nudm_UECM_Registration request message, Nudm_UECM_Get request message, Nudm_UECM_Update request message, Nudm_SDM_Get request message, Nudm_SDM_Subscribe request message, etc. The first Nudm message may include at least one of the following: the identifier of the first AMF, the UE's SUPI, the UE's GUTI, access type, GUAMI, RAT type, registration type (e.g., indicating primary registration), first access path identifier, the UE's location (e.g., cell ID, TAID associated with the first 3GPP RAN), information of the first 3GPP RAN (e.g., identifier), information of the first network (e.g., identifier), indication of primary registration, etc. For example, GUAMI may include the MNC and / or the MNC of the UE's serving (e.g., first) network (e.g., PLMN, NPN, SNPN). For example, UDM may be a data management node. For example, UDM may be located in the UE's home network. For example, the access type may indicate whether the registration associated with the first Nudm message is for 3GPP access or for N3GPP access. For example, the access type of the first Nudm message may be set to 3GPP access. For example, the registration type may be the 5GS registration type of the first NAS message. For example, the indication of primary registration may indicate whether the first network serves the primary connection and whether the first AMF (and / or the first network, first RAN, first access path) is used for the primary connection (registration).

[0282] In one example, the UDM can receive a first Nudm message. In response to receiving the first Nudm message, the UDM can store the information transmitted via the first Nudm message in its memory (or its storage). In response to the first Nudm message, the UDM can send a second Nudm message (Nudm MSG 2). For example, the second Nudm message can be at least one of the following: Nudm_UECM_Registration response message, Nudm_UECM_Get response message, Nudm_UECM_Update response message, Nudm_SDM_Get response message, Nudm_SDM_Subscribe response message, etc. For example, the second Nudm message can include at least one of the following: a result indication, an identifier of the first AMF, an access type for the first access path, a first access path identifier, subscription data, an indication of the primary connection, etc. For example, the result indication can indicate whether the first Nudm request was successfully processed. For example, if the UDM supports the feature of secondary registration, and / or if the UDM allows the UE (or AMF) to use the feature of secondary registration, the result indication can indicate that the first Nudm request was successfully processed. For example, if the UDM does not support secondary registration (e.g., multiple registrations, first registration, primary registration), if the UDM does not allow the first network to become the primary network, and / or if the UDM does not allow the UE (or AMF) to use the secondary registration feature, the result indication may indicate that the first Nudm request was not successfully processed and / or secondary registration (or multiple registrations, primary registration) is not allowed for the UE. For example, the result indication of the second Nudm message may indicate success. For example, the subscription data of the second Nudm message may indicate that the UE is allowed to use the secondary registration feature. The subscription data in the second Nudm message and / or stored in the UDM (or the associated UDR) and based on which the second Nudm message is constructed may include at least one of the following: information on whether the UE is allowed to use the secondary (e.g., using multiple) registration feature, information on whether the UE is allowed to use an MA PDU session, and / or information on whether the UE is allowed to register on both the primary and secondary networks. The UDM may operate two subscriptions and / or two SUPIs for the same UE, whereby these two subscriptions may be linked and / or indicate support for dual registration / dual connectivity on two different networks. For example, the subscription data in the second Nudm message can indicate that the UE is allowed to use features of secondary registration.

[0283] In one example, the first AMF can receive a second Nudm message. Based on the second Nudm message, the first AMF can determine whether to accept the UE's registration and / or allow primary registration, and whether to send a list of secondary networks. For example, if the subscription data of the second Nudm message indicates that the UE is allowed to use the features of secondary registration, the first AMF can determine that the first (e.g., primary) registration is allowed. For example, if the result of the second Nudm message indicates success, the first AMF can determine that the UE's first registration is allowed. Based on the determination of allowing the first registration, the first AMF can store information received via the first NAS message and / or via the first Nudm message. For example, the first AMF can manage the UE's first context. For example, the first context can be associated with the UE's first access tributary (or path), the first AMF, primary registration, primary (or main) security context (e.g., Kamf, Kgnb, encryption key, integrity key), and / or the first network.

[0284] In one example, the first AMF may determine to send a second NAS message (e.g., NAS MSG 2) to the UE. For example, the second NAS message may be at least one of a registration acceptance message, a service acceptance message, a DL NAS transport message, a PDU session establishment acceptance message, a UE configuration update (configuration update command) message, a PDU session modification command message, etc. The second NAS message may include at least one of 5GS registration result, 5G-GUTI, first access path identifier, TAI list, allowed NSSAI, 5GS network feature support, etc. The 5G-GUTI may indicate a 5G-GUTI assigned to the UE by the first network (or the first AMF). The TAI list may indicate a list of TAIs assigned to the UE for the first access path. Allowed NSSAI may indicate one or more allowed network slices for the UE. 5GS network feature support may indicate whether the network supports the features of the secondary registration. For example, 5GS network feature support may indicate that the features of the secondary registration are supported by the first network (first AMF, SMF, etc.). For example, 5GS network feature support can indicate that the first network is the primary network, the first AMF is the primary AMF, and the features for secondary registration are supported by the first network (first AMF, SMF, etc.). For example, a list of secondary networks (e.g., a secondary network list) can indicate which one or more secondary networks the UE is allowed to select for performing secondary registration. For example, when the UE primarily registers to the first network, the secondary network list can indicate which networks are candidates for secondary registration. For example, the secondary network list can include one or more identifiers of potential / candidate / allowed secondary networks that can be used with the primary network.

[0285] In one example, the list of secondary networks may also include conditional information. For example, the conditional information may indicate one or more frequency bands, one or more radio access network types, and / or at least one of one or more RATs permitted for secondary registration, duration, and location area for each of the one or more secondary networks. For example, if the list of secondary information indicates FR1, satellite RAN of network 6, then if the cell of network 6 uses FR1, satellite RAN, etc., the UE may perform secondary registration with network 6. For example, the list of secondary networks may include one or more identifiers of one or more secondary networks (e.g., PLMN ID, SNPN ID, CAG ID, etc.).

[0286] In one example, the AMF may send a second NG message (e.g., NG MSG 2) to the first 3GPP RAN. For example, the second NG message may be at least one of an Initial Context Setup Request message, a UE Context Modification Request message, a Downlink NAS Transmission message, a Path Switching Response message, a Path Switching message, etc. The second NG message may include at least one of the following: AMF UE NGAP ID, GUAMI, First Access Path Identifier, Primary Connection Indication, PDU Session Resource Setup Request List, UE Radio Capabilities, Mobility Restriction List, NAS PDU, etc. For example, the NAS PDU may be a second NAS message.

[0287] In one example, the first 3GPP RAN may receive the second NG message. The first 3GPP RAN may store information transmitted via the second NG message and / or may send a second RRC message (e.g., RRC MSG 2) to the UE. For example, the second RRC message may include a second NAS message of the second NG message.

[0288] In one example, the UE may receive a second RRC message and / or a second NAS message. The UE may determine whether the first registration (e.g., primary registration, registration to a first network, registration to a primary network) was successful. For example, if the second NAS message indicates successful registration, registration acceptance, support for features of secondary registration, etc., the UE may determine that the first (e.g., primary) registration was successful, allow the UE to perform secondary registration, and / or that the registration was successful.

[0289] In one example, based on this determination, the UE can decide to perform secondary registration. For example, the UE can search for one or more second networks, and one or more second cells within one or more second networks. One or more second cells can use one or more 3GPP RATs, can be part of one or more 3GPP RANs, and / or can be part of a 3GPP access type. For example, one or more second cells can belong to a second 3GPP RAN (e.g., 3GPP RAN 2) and / or can belong to a second network in the secondary network list. For example, the UE can select a second cell from one or more second cells. The second cell can be a second access path for 3GPP access and / or can be associated with a 3GPP access type. For example, the second cell and / or the second 3GPP RAN (e.g., using the FR2 band, using satellite, etc.) can be different from the first cell and / or the first 3GPP RAN (e.g., using the FR1 band, using terrestrial, etc.). For example, the second network can be a permitted network for secondary registration and / or can be in the list of secondary networks. For example, the second network can be a network permitted for secondary registration to a first (e.g., primary) network.

[0290] In other examples, based on this determination, the UE can decide whether to perform secondary registration. For example, the UE can detect one or more third networks, and one or more third cells within those third networks. The one or more third cells may use one or more 3GPP RATs, may be part of one or more 3GPP RANs, and / or may be part of a 3GPP access type. For example, the one or more third cells may belong to a third 3GPP RAN (e.g., 3GPP RAN 3) and / or may belong to a second network. The third network may not be in the list of secondary networks. For example, because the third cell in one or more third cells is not in the list of secondary networks, the UE may not select that third cell. For example, the third network may not be a permitted network for secondary registration. For example, the third network may not be a network permitted for secondary registration to a first (e.g., primary) network. The UE may not select a third cell and / or the UE may not perform secondary registration with the third cell and / or the third network.

[0291] In another example, the AMF or RAN may send a request as part of a second NAS message or as part of an intermediate RRC or NAS message (e.g., before / after the second NAS message) to allow the UE to provide a list of discovered networks (e.g., cell IDs and / or PLMN IDs of the networks from which the UE receives SIB information) and / or information about which networks in the list of secondary networks (which may be provided to the UE by the AMF or RAN) are available to the UE (e.g., can be discovered by the UE), possibly along with measurement information of the discovered networks (e.g., signal quality, signal strength), and / or provide the UE's location information (e.g., GNSS location). The UE may respond to such a request by sending one / another intermediate RRC or NAS message containing one or more of the requested information (e.g., before sending the third NAS message as described below). Based on information provided by the UE, the network (e.g., RAN, AMF, SoR-AF) can determine a subset of the list of (preferred) secondary networks and / or select the (preferred) secondary network to which the UE needs to register from the list of candidate secondary networks, and / or determine additional networks to be added to the list of secondary networks, and based on this determination, send an updated list of candidate networks (possibly including rules / conditions for accessing them) in a response to the UE (e.g., a second message or another intermediate message). Based on the response received from the network, the UE can determine whether to perform secondary registration and / or can determine which second network to use / search for to perform secondary registration. Alternatively or additionally, a network function that receives information related to which networks the UE has discovered and / or measurements related to the discovered networks can forward that information or a summary / subset thereof and / or provide a determined subset of the list of (preferred) secondary networks and / or the selected (preferred) secondary networks to one or more discovered networks (e.g., via the AMF of a first network communicating with the AMF of the discovered network, or via the NF of a first network communicating with the NF of the second network via NEF or SBI).Alternatively, the network functions of the first network (e.g., AMF) to which the UE is registered can provide one or more other networks with information about the UE (e.g., a set of identifiers associated with the UE (e.g., a list of one or more SUPI subscriptions for the UE), the PDU session ID or associated ID used by the UE to communicate with the first network (e.g., identifiers indicating / associating multiple PDU sessions from the UE on the first and / or second networks), a set of network slices that the UE is using or is allowed or not allowed for secondary registration, a list of the UE's capabilities (e.g., indicating support for dual registration and / or service splitting / handover / switching on both networks, a list of supported frequency bands), and a list of services that the UE can use through primary and / or secondary connections), such as going to one or more networks registered for dual connectivity / dual registration (e.g., secondary networks linked to the first and / or second subscription data for the UE in the UDM) and / or one or more networks to which the UE has provided information that the UE has discovered. This enables the discovered networks to prepare for incoming connections from the UE for secondary registration. For example, based on information received from the first network, the second network may add or remove one or more slices from the UE's allowed slice list, update RAN policies, reserve or schedule some resources for the UE, perform beam control of one or more cells toward the UE's location, and send (e.g., via broadcast (updated) SIBs) some information to one or more UEs, such as information about the UE's registration with the first network (e.g., the network ID of the first network) or information about one or more candidate second networks that the UE wants to register with, based on information received from the first network.

[0292] In one example, after searching for and / or selecting a second cell (of the second 3GPP RAN and the second network), the UE can construct a third NAS message (e.g., NAS MSG 3). The third NAS message can be at least one of the following: a registration request message, a service request message, a UL NAS transport message, a deregistration request message, a PDU session establishment request message, a PDN session modification request message, a PDU session release request message, etc. The third NAS message can include at least one of the following: the UE's identifier (e.g., IMSI, SUPI, SUCI, GUTI, etc.), 5GS registration type, preferred network behavior, second access path identifier, last accessed registration TAI, PDU session state, EPS NAS message container, payload container, 5GMM capability, requested NSSAI, second access path identifier, access type, etc. The UE's identifier can be the UE's identity. This can be an identity different from the identity used in the first NAS message of the first registration (e.g., a SUCI based on a SUPI different from the first registration). The network can link the two identities used in the first and second registrations. The 5GS registration type of the third NAS message can indicate secondary registration, multiple registrations, etc. For example, a 5G registration type can indicate a second registration (or a third NAS message) for secondary registration, and / or an additional (subsequent and / or similar) registration following the primary registration. For instance, preferred network behavior can be set as a feature that supports secondary registration. Preferred network behavior helps radio access nodes and / or core network nodes select nodes that support preferred network behavior (e.g., secondary registration, multiple / additional registration).

[0293] In one example, the UE can send a third RRC message (e.g., RRC MSG 3) to the second 3GPP RAN (e.g., 3GPP RAN 2) of the second network. For example, the second 3GPP RAN may include at least one of a second gNB, a second ng-eNB, a second eNB, a second en-gNB, etc. For example, the third RRC message may be at least one of an RRC setup request message, an RRC setup complete message, an RRC recovery request message, an RRC recovery complete message, an RRC UL transmission message, etc. For example, the third RRC message may include at least one of a third NAS message, an RRC establishment reason, etc. The RRC establishment reason may indicate that the RRC connection is for establishing a second access path and / or that the RRC connection is for secondary registration. The second 3GPP RAN can receive the third RRC message via the second cell of the second 3GPP RAN of the second network.

[0294] In one example, the second 3GPP RAN may send a third NG message to the second mobility management node of the second network. For example, the second mobility management node may be the second AMF of the second network. For example, the second 3GPP RAN may determine to send a third NG message. The third NG message may be at least one of the following: an initial UE message, an uplink NAS transmission, etc. The third NG message may include at least one of the following: the identifier of the second 3GPP RAN (e.g., gNB ID, TAI, cell ID, 3GPP access RAN type, RAT type), a third NAS message, user location information, RRC establishment reason, etc.

[0295] In one example, the second AMF can receive a third NG message. Based on the third NAS message following the third NG message, the second AMF can determine whether the UE requests secondary registration. For example, if the third NAS message includes a 5GS registration type set to secondary registration, the second AMF can determine that the UE is requesting secondary registration from the second network. For example, if the second AMF does not support the features of secondary registration, the second AMF can reject the (second) registration request and / or the second AMF can request the first AMF and / or UDM to cancel / release the UE's first (e.g., primary) registration.

[0296] In one example, if the second AMF determines that the UE requests secondary registration, and / or a third NAS message is used for secondary (e.g., additional, multiple) registration, the second AMF may send a third Nudm message (e.g., Nudm MSG 3) to the UDM. For example, the third Nudm message may be at least one of the following: Nudm_UECM_Registration request message, Nudm_UECM_Get request message, Nudm_UECM_Update request message, Nudm_SDM_Get request message, Nudm_SDM_Subscribe request message, etc. The third NUDM message may include at least one of the following: the identifier of the second AMF, the UE's SUPI, the UE's GUTI (e.g., a 5G GUTI used in the first network and / or the second network), the access type (e.g., a 3GPP access type), the second GUAMI of the second AMF, the RAT type, the registration type (e.g., secondary registration), the second access path identifier, the UE's location (e.g., cell ID, TA ID associated with the second 3GPP RAN), an indicator indicating that the second AMB (network) supports secondary registration, and information of the second 3GPP RAN (e.g., identifier). For example, the registration type may be the 5GS registration type of the third NAS message.

[0297] In one example, the UDM can receive a third Nudm message. In response to receiving the third Nudm message, the UDM can store the information conveyed via the third Nudm message in its memory (or its storage). For example, the UDM can store at least one of the following: an identifier of the second AMF used for secondary registration by the second network, an identifier of the second network, an indication of secondary registration, etc. In response to the third Nudm message, the UDM can send a fourth Nudm message (e.g., Nudm MSG 4). For example, the fourth Nudm message can be at least one of the following: a Nudm_UECM_Registration response message, a Nudm_UECM_Get response message, a Nudm_UECM_Update response message, a Nudm_SDM_Get response message, a Nudm_SDM_Subscribe response message, etc. For example, the fourth Nudm message can include at least one of the following: a result indication, an identifier of the second AMF, an access type, a second access path identifier, subscription data, etc. For example, the result indication can indicate whether the third Nudm request was successfully processed. For example, if the UDM supports secondary registration features, if a second network (or second AMF) is allowed for secondary registration of the UE, if a second network is allowed to be used in addition to the first network, and / or if the UDM allows the UE (or second AMF) to use secondary registration features, then the result indication can indicate that the third Nudm request was successfully processed. For example, if the UDM does not support secondary registration features, if a second network is not allowed for secondary registration, if the first network does not support secondary registration, if the second network does not support secondary registration, if the second network is not allowed to be used with the first network, and / or if the UDM does not allow the UE (or second AMF, second network) to use secondary network features, then the result indication can indicate at least one of the following: the third Nudm request was not successfully processed, the third Nudm request was successfully processed even though secondary registration was not allowed, etc. For example, the result indication of the fourth Nudm message can indicate success. For example, the subscription data of the fourth Nudm message can indicate that the UE is allowed to use secondary registration features, the second AMF (network) is registered in the UDM, and / or the UE is allowed to use the second (additional) access path of the second network.

[0298] In one example, the second AMF can receive a fourth Nudm message. Based on the fourth Nudm message, the second AMF can determine whether to accept the UE's second registration and / or whether to allow registration of a second access path through a second network for that access type. For example, if the subscription data of the fourth Nudm message indicates that the UE is allowed to use the features of secondary registration, the second AMF can determine that secondary registration of the second access path and / or the second network is allowed. For example, if the result of the fourth Nudm message indicates success, the second AMF can determine that secondary registration of the second access path and / or the second network is allowed. Based on the determination that registration of the second access path, secondary registration, and / or the second network is allowed, the second AMM can store information received via a third NAS message and / or via the fourth Nudm message. For example, the second AMF can manage the UE's second context. For example, the second context can be associated with the UE's second access tributary (path), the second AMF, secondary registration, subordinate (secondary) security contexts (e.g., Kamf2, Kgnb2, encryption key 2, integrity key 2), and / or the second network. For example, a subordinate security context can be associated with a second network and the UE and / or with a second access tributary. For example, a subordinate security context can be derived from a primary security context (which resides in the first / primary network / AMF).

[0299] In one example, the second AMF may determine to send a fourth NAS message (e.g., NAS MSG 4) to the UE. For example, the fourth NAS message may be at least one of a registration acceptance message, a service acceptance message, a DL NAS transport message, a PDU session establishment acceptance message, a UE configuration update (configuration update command) message, a PDU session modification command message, etc. The fourth NAS message may include at least one of a 5GS registration result, a 5G-GUTI, a TAI list, allowed NSSAIs, 5GS network feature support, a second access path identifier, etc. The 5G-GUTI may indicate a 5G-GUTI assigned to the UE by the first network and / or the second network. The TAI list may indicate a list of TAIs assigned to the UE for the second access path. The 5GS registration result may indicate whether the (secondary) registration was successful.

[0300] In one example, the second AMF may send a fourth NG message (e.g., NG MSG 4) to the second 3GPP RAN. For example, the fourth NG message may be at least one of an Initial Context Setup Request message, a UE Context Modification Request message, a Downlink NAS Transmission message, a Path Handover Response message, etc. The fourth NG message may include at least one of the following: AMF UE NGAP ID, a second GUAMI associated with the second AMF, a second access path identifier, a PDU session resource setup request list, UE radio capabilities, a mobility restriction list, a NAS PDU, etc. For example, the NAS PDU may be a fourth NAS message. For example, the UE radio capabilities may be the radio capabilities of the UE associated with the second access path. For example, the mobility restriction list may be associated with the second access path.

[0301] In one example, the second 3GPP RAN can receive a fourth NG message. The second 3GPP RAN can store information transmitted via the fourth NG message and / or can send a fourth RRC message (e.g., RRC MSG 4) to the UE. For example, the fourth RRC message may include a fourth NAS message of the fourth NG message.

[0302] In one example, the UE may receive a fourth RRC message and / or a fourth NAS message. The UE may determine whether secondary registration via the second access path was successful. For example, if the fourth NAS message indicates successful registration (for the second access path, multiple access paths of the access type, and / or additional access paths), registration acceptance, features supporting secondary registration, successful secondary registration, second access path identifier, etc., then the UE may determine that secondary registration via the second network was successful, the UE registered for the second access path of the access type, the UE registered via the second access path, and / or secondary registration was successful. In one example, the access type of the second access path may be the access type of the first access path.

[0303] In one example, based on primary registration via a first network and / or secondary registration via a second network, the UE can continue to establish / update MA PDU sessions by using a first access path and / or a second access path of a 3GPP access type with one or more SMFs.

[0304] Figure 22 The example shown can help a UE register multiple networks that support 3GPP access types, while reducing unnecessary registration attempts to unsupported networks. For example, this could support two separate 3GPP RANs (e.g., NG-RAN plus NG-RAN, NG-RAN plus E-UTRAN, etc.) with NG-C connectivity to one or more core networks.

[0305] Figure 23 An example embodiment of this disclosure can be described. Similar to... Figure 22 The UE can perform primary and / or secondary registration based on a list of secondary networks. Figure 23 In the example, the first AMF can receive auxiliary information from one or more network nodes. This helps the first AMF determine the list. For the sake of brevity, redundant details will be omitted based on other parts of this disclosure.

[0306] In one example, a first AMF can receive a first NAS message from a UE. In response to receiving the first NAS message, the first AMF can send a first Nudm message to a UDM. For example, the UDM can be in the UE's home network. The first Nudm message may also include at least one of the following indications: an indication of whether the first AMF supports secondary registration features, an indication that the first AMF is a primary network, an indication that the UE requests primary registration, and an indication that the first AMF requests information about candidate (potential, permitted) secondary networks, etc. In response to receiving the first Nudm message, the UDM can send a second Nudm message to the first AMF. Because the first Nudm message includes this indication, the second Nudm message may also include information about a list of secondary networks. For example, the UDM may have information about a stored list of secondary networks. For example, an operator may store a list of secondary networks in the UDM. For example, using the UE's subscription information and / or using a service agreement between one or more networks, an operator can determine which networks can be used as secondary networks of which network. In one example, the first AMF can receive a second Nudm message from the UDM, which includes a list of secondary networks.

[0307] In another example, the AMF can send a first Npcf message to the policy management node. For example, the policy management node can be a policy control function (PCF). The first Npcf message can include at least one of an Npcf_AMPolicyControl_Create request message, an Npcf_UEPolicyControl_Create request, etc. The first Npcf message can include at least one of the following: the UE's identifier, the identifier of a first network, the UE's capabilities (e.g., support for features of secondary networks), an indication of primary registration, a request for a list of secondary networks, etc. In response to receiving the first Npcf message, the PCF can send a second Npcf message to the first AMF. For example, the second Npcf message can include at least one of an Npcf_AMPolicyControl_Create response message, an Npcf_UEPolicyControl_Create response, etc. The second Npcf message can include a list of secondary networks. For example, the PCF may have network policy information and may be able to determine one or more networks permitted for secondary registration. In one example, the first AMF can receive a second Npcf message from the PCF that includes a list of secondary networks.

[0308] In one example, the AMF may use a list of secondary networks received from other nodes (e.g., PCF, UDM) and / or may send the list of secondary networks to the UE.

[0309] Figure 23 The example shown can help the first AMF know one or more candidate networks for secondary registration.

[0310] Figure 24 An example embodiment of this disclosure can be described. (and) Figure 22 , 23 Similarly, the UE can perform primary and / or secondary registration based on a list of secondary networks. Figure 24 In the example, the AMF can receive auxiliary information from one or more network nodes. This helps the AMF determine the list. For the sake of brevity, redundant details will be omitted based on other parts of this disclosure.

[0311] In one example, the first AMF can receive a first NAS message from the UE. In response to receiving the first NAS message, the first AMF can send a first Nudm message to the UDM. For example, the UDM can be in the UE's home network. The first Nudm message may also include at least one of the following: an indication of whether the first AMF supports secondary registration features, an indication that the first AMF is the primary network, or an indication that the UE requests primary registration.

[0312] In one example, the UDM can receive a first Nudm message. In response to receiving the first Nudm message, the UDM can send a first Nsoraf message to the roaming management node. For example, the roaming management node can be a SoR (Roaming Turnaround) Application Function (AF). For example, the SoR AF can collect information about one or more networks, the capabilities of one or more networks, and the service protocols of one or more networks. For example, the first Nsoraf message can be at least one of an Nsoraf_SoR_Get request message, an Nsoraf_SoR_Provision request message, etc. For example, the first Nsoraf message can include at least one of the following: the UE's identifier, the identifier of a first network, the UE's capabilities (e.g., support for features of secondary networks), an indication of primary registration, a request for information on one or more secondary networks, etc. In response to receiving the first Nsoraf message, the SoR-AF can send a second Nsoraf message to the UDM. For example, the second Nsoraf message can be at least one of an Nsoraf_SoR_Get response message, an Nsoraf_SoR_Provision response message, etc. For example, the second Nsoraf can include a list of secondary networks. In response to receiving a second Nsoraf message, the UDM can send a second Nudm message to the first AMF. The second Nudm message may also include information about a list of secondary networks. In one example, the first AMF can receive a second Nudm message from the UDM containing a list of secondary networks.

[0313] In one example, the AMF can send a list of secondary networks to the UE.

[0314] Figure 24 The example shown can help the first AMF know one or more candidate networks for secondary registration.

[0315] Figure 25 An example embodiment of this disclosure can be described. Similar to... Figure 22 The UE can perform primary and / or secondary registration based on a list of secondary networks. Figure 25 In the example, the UE can receive information about a list of compatible networks. Based on the list of compatible networks, the UE can select one or more networks. For the sake of brevity, redundant details will be omitted based on other parts of this disclosure.

[0316] In one example, the UE can register with a network. This network can be a home network and / or an access network. For instance, when the UE is within the coverage area of ​​a home network, it can register with that network.

[0317] In one example, the UE may send an 0A NAS message (e.g., NAS MSG0A) to the network's mobility management node. For example, the UE may register to the network using a subscription to its home network. This may help the mobility management node verify the UE and / or related information. For example, the 0A NAS message may be at least one of a registration request message, a service request message, an attach request, etc. For example, the 0A NAS message may indicate that the UE supports secondary registration features, the UE requests information about one or more secondary networks, the UE requests service from a network that supports secondary networks (or can exchange signaling with secondary networks), etc. For example, the mobility management node may be an AMF (e.g., AMF 0), an MME, etc. In one example, the UE may construct an 0A NAS message (e.g., NAS MSG 0A). The 0A NAS message may resemble a first NAS message.

[0318] In one example, the UE may send an 0A RRC message (e.g., RRC MSG 0A) to 3GPP RAN 0. For example, 3GPP RAN 0 may include at least one of the zeroth gNB, zeroth ng-eNB, zeroth eNB, zeroth en-gNB, etc. For example, the 0A RRC message may be at least one of an RRC setup request message, an RRC setup complete message, an RRC recovery request message, an RRC recovery complete message, an RRC UL transmission message, etc. For example, the 0A RRC message may include at least one of an 0A NAS message, an RRC establishment reason, etc. The RRC establishment reason may indicate that the RRC connection is for establishing a first access path and / or performing primary registration. The zeroth 3GPP RAN may receive the 0A RRC message.

[0319] In one example, the zeroth 3GPP RAN can send an 0A NG message to the AMF. The 0A NG message can be at least one of an initial UE message, an uplink NAS transmission, etc. The 0A NG message can include information elements similar to those in the first NG message. The 0A NG message can also include an 0A NAS message.

[0320] In one example, the AMF can receive an 0A NG message. Based on the 0A NAS message from the 0A NG message, the AMF can determine whether the UE requests features that support secondary registration, whether the UE indicates features that support secondary registration, whether the UE requests information about a secondary network, whether the UE requests information about a compatible network, whether the UE indicates features that support secondary registration, and / or whether the 0A NAS message is used for primary registration.

[0321] In one example, the AMF can send a 0A Nudm message (e.g., Nudm MSG 0A) to the data management node (e.g., UDM) of the home network. For example, the 0A Nudm message can be similar to the first Nudm message.

[0322] In one example, the UDM can send an 0A Nsoraf message to the SoR AF. For example, the 0A Nsoraf message can be similar to the first Nsoraf message. For example, the 0A Nsoraf message can indicate whether the UE supports features of secondary registration, and / or whether the UE requests features of secondary registration. In response to receiving an 0A Nsoraf message (which indicates whether the UE supports features of secondary registration, and / or whether the UE requests features of secondary registration), the SoR AF can construct a list of compatible networks.

[0323] In one example, for each network in the list of compatible networks, the list of compatible networks may indicate at least one of the following: whether each network is allowed for primary registration, whether each network is allowed for secondary registration, one or more networks that can be used as secondary networks for each network, one or more networks that can be additionally registered when registering each network, etc. For example, the list of compatible networks may indicate that when registering a first network for a UE, a second network can be used as a secondary network for the UE. For example, the list of compatible networks may indicate that when registering a first network for a UE, a third network cannot be used as a secondary network for the UE.

[0324] In one example, the SoR AF can send an 0B Nsoraf message to the UDM. For example, the 0B Nsoraf message may include a list of compatible networks. In response to receiving an 0B Nsoraf message including a list of compatible networks and / or based on locally available information (e.g., a list of compatible networks), the UDM can send an 0B Nudm message to the AMF (e.g., Nudm MSG 0B). For example, the 0B Nudm message may include a list of compatible networks. For example, the 0B Nudm message may resemble a second Nudm message.

[0325] In one example, the AMF can receive 0B Nudm messages. Because 0B Nudm messages include a list of compatible networks, the AMF can send this list to the UE. For example, 0B NAS messages (e.g., NAS message 0B) can include a list of compatible networks. For example, 0B NAS messages can resemble second NAS messages. For example, 0B NAS messages can be registration acceptance messages, UE configuration update messages, UE parameter update messages, DL NAS messages specified in Annex C of 3GPP TS 23.122, etc.

[0326] In one example, the AMF can send an 0B NG message (e.g., NG MSG 0B) to the 3GPP RAN. For example, an 0B NG message can resemble a second NG message. For instance, an 0B NG message can include an 0B NAS message.

[0327] In one example, the 3GPP RAN can receive 0B NG messages. The 3GPP RAN can store information transmitted via 0B NG messages and / or can send 0B RRC messages (e.g., RRC MSG 0B) to the UE. For example, an 0B RRC message may include an 0B NAS message of the 0B NG message. For example, an 0B RRC message may resemble a second RRC message. The UE can receive 0B NAS messages and can store the information in the 0B NAS messages in its local memory.

[0328] In one example, the SoR information provided by a network (e.g., by a SoR AF) may include a set of network combinations (e.g., tuples consisting of (primary network identifier, secondary network identifier) ​​that are allowed for use by a UE capable of secondary registration. The UE can use this information to initiate secondary registration to a second network after successfully registering with a first network, thereby selecting the second network based on whether the SoR information contains a valid combination of the second and first networks.

[0329] In one example, the SoR information contains one or more conditions for selecting secondary networks and / or allowing secondary registration (generally or for specific secondary networks), where the conditions may be associated with a list of secondary networks, a list of compatible networks, or a combination of networks, as previously described. Examples of such conditions may include location-related conditions (e.g., valid only in certain tracking areas, geographic areas), signal quality-related conditions (e.g., registration to a specific network (a specific combination of networks) is allowed only if the signal strength (of one or more networks) is above a certain threshold), QoS-related conditions (e.g., registration to a secondary network is allowed if the PDU session requires certain QoS parameters / values ​​(e.g., 5QI value, sustained data rate, or a maximum error rate), time-related conditions (e.g., valid only during certain time periods), availability conditions (e.g., certain networks are available / disabled or unavailable / disabled), emergency conditions (e.g., establishing a PDU session across multiple networks if it involves the UE and / or the UE needs to establish emergency communications), etc.

[0330] In one example, SoR information may not be requested by the UE from the network or provided by the network (e.g., after primary registration), but may have been pre-configured on the UE before primary registration (e.g., stored as part of the (e)SIM profile).

[0331] In one example, the UE can search for and / or select a network for registration. For instance, the UE can find the first cell of the first network. Because the list of compatible networks indicates that the first network is allowed for primary registration, and / or the first network is the primary network, the UE can perform primary registration with the first network (e.g., by using...). Figure 22 (Example).

[0332] In another example, the UE can search for and / or select a network for registration. For instance, the UE can find a second cell in a second network. Because the list of compatible networks or one or more combinations of networks indicates that the second network is allowed for secondary registration, such as when the UE primarily registers to the first network, and / or when the second network is a secondary network, the UE can perform secondary registration to the second network (e.g., using...). Figure 22 (Example).

[0333] In another example, the UE can search for and / or select a network for registration. For instance, the UE can detect a third cell within a third network. Because the list of compatible networks or a combination of one or more networks indicates that a third network is not permitted for secondary registration, for example, when the UE is primarily registered to the first network, the UE may not perform secondary registration with a third network.

[0334] Figure 25 Examples can assist the primary network and / or the UE. For instance, if the service agreement between the home network and the secondary network is unknown, the primary network may not have details of one or more networks permitted for the secondary network. For example, the UE may not know which network can be used for primary registration before performing registration to the primary network. Figure 25 Examples can help the first network and / or UE.

[0335] exist Figure 25 In the example, the action of RAN 0 can be performed by the first RAN and / or the action of AMF 0 can be performed by the first AMF. In other words, information (e.g., a list of compatible networks) can be passed to the UE by accessing the network. Figure 22 , 23 In the examples 2 and 24, the list of compatible networks may be used alternatively and / or additionally for the list of secondary networks.

[0336] Figure 26 An example embodiment of this disclosure can be described. The UE can receive information from the cell regarding whether the network supports secondary registration. This can help the UE determine whether to perform primary registration and / or secondary registration. For the sake of brevity, redundant details will be omitted based on other parts of this disclosure.

[0337] In one example, the UE can search for / detect one or more cells available at its location. For one or more detected cells, the UE can receive system information (e.g., SIB, System Information Block). For example, the one or more cells can include at least one of a first cell, a second cell, and a third cell. For example, the first cell can be a cell of a first network, the second cell can be a cell of a second network, and / or the third cell can be a cell of a third network. For example, the first cell can broadcast a first SIB, and the first SIB can indicate that the first network supports features of the secondary network. For example, the second cell can broadcast a second SIB, and the second SIB can indicate that the second network supports features of the secondary network. For example, the third cell can broadcast a third SIB, and the third SIB can indicate that the third network does not support features of the secondary network.

[0338] In one example, the UE can receive a first SIB from a first cell. Because the first SIB indicates features supporting secondary registration, the UE can determine to perform primary registration with the first network. For example, with... Figure 22 Similarly, the UE can send a first NAS message, the first AMF can receive the first NAS message, the first AMF can send a first Nudm message, the first AMF can receive a second Nudm message, the first AMF can send a second NAS message to the UE, and / or the UE can receive the second NAS message.

[0339] In one example, return to Figure 26 In response to receiving a second NAS message, the UE can determine to perform secondary registration. For example, the UE may receive a second SIB from a second cell and / or a third SIB from a third cell. Because the second SIB indicates features supporting secondary registration, the UE can determine to perform secondary registration with the second network. Because the third SIB does not indicate features supporting secondary registration, the UE can determine not to perform secondary registration with the third network and / or can determine not to select the third network. For example, with... Figure 22 Similarly, the UE can send a third NAS message, the second AMF can receive the third NAS message, the second AMF can send a third Nudm message, the second AMF can receive a fourth Nudm message, the second AMF can send a fourth NAS message to the UE, and / or the UE can receive a fourth NAS message.

[0340] Figure 27 An example embodiment of this disclosure can be described. Similar to... Figure 26 The UE can receive information from the cell indicating whether the network supports secondary registration. (Back to...) Figure 27 This can help the UE determine how to manage the registration status. For the sake of brevity, redundant details will be omitted based on other parts of this disclosure.

[0341] In one example, after registering to the first network, the UE can receive a third SIB from a third cell. In another example, the UE may not be able to detect a second cell and / or may not be able to detect one or more cells (from networks other than the first network) that indicate support for secondary registration. Alternatively, after registering to the first network, the UE may move to an area where cells in the first network are unavailable.

[0342] In one example, the UE may determine that the registration process is performed through a third cell of a third network. The UE may send a sixth RRC message (e.g., RRC MSG 6) to the third cell (or third RAN) of the third network. For example, the sixth RRC message may include a sixth NAS message (e.g., NAS MSG 6). For example, the sixth NAS message may resemble the third NAS message. For example, the sixth NAS message may or may not indicate that the UE requests secondary registration, features that the UE supports for secondary registration, etc.

[0343] In response to receiving the sixth NAS message, the third AMF (e.g., AMF 3) of the third network may send a sixth Nudm message (e.g., Nudm MSG 6) and / or may receive a seventh Nudm message from the UDM. The seventh Nudm message may or may not be similar to the fourth Nudm message. For example, the seventh Nudm message may indicate that the third network is not allowed for secondary registration of the UE.

[0344] In one example, a third network (such as AMF 3) may not support the features of secondary registration and may not allow it for secondary registration. AMF 3 may send a seventh NAS message to the UE. For example, the seventh NAS message may instruct the UE to register with the third network, may not instruct the third network to support secondary registration, and / or may not instruct the UE's secondary registration with the third network to be accepted.

[0345] In one example, the UE may receive a seventh NAS message. Because the seventh NAS message indicates acceptance of registration, because the third network does not support the features of secondary registration, and / or because the third SIB does not indicate support for secondary registration, the UE can determine to change the registration status associated with the first network. For example, the UE may determine that primary registration with the first network has ended (deletion, release, deregistration), the UE has not registered with the first network, and / or secondary registration is not used / suspended, etc. For example, the UE may delete / discard information associated with the first network (e.g., identifiers assigned by the first network, security contexts associated with the first network, configuration parameters associated with the first network (e.g., registration area, PDU session state), etc.).

[0346] Figure 27Examples can help UEs manage unrelated connections.

[0347] Figure 28 An example embodiment of this disclosure can be described. Similar to... Figure 22 The UE can perform primary registration and / or attempt secondary registration. Figure 28 In the example, the UE may attempt to register with a secondary cell of a network from which the UE may not be able to obtain service. For the sake of brevity, redundant details will be omitted based on other parts of this disclosure.

[0348] In one example, when performing registration to the first network (such as...) Figure 22 Following the example shown, the UE can perform a registration process to a fourth network (e.g., network 4). For example, when the UE cannot detect a cell in the first network and / or when the UE cannot detect a cell in the list of secondary networks, the UE can detect a fourth cell in the fourth network.

[0349] In one example, the UE may send a 26th NAS message (e.g., NASMSG 26) to the fourth AMF of the fourth network. For example, the 26th NAS message may be similar to the 6th NAS message.

[0350] In response to receiving the 26th NAS message, the fourth AMF may send a 26th Nudm message (e.g., NudmMSG 26) and / or may receive a 27th Nudm message (e.g., Nudm MSG 27) from the UDM. The 27th Nudm message may or may not be similar to the 7th Nudm message. For example, the 27th Nudm message may indicate that the fourth network is not permitted for secondary registration of the UE.

[0351] In one example, the fourth network (e.g., AMF 4) may not support secondary registration features and may not be allowed for secondary registration. AMF 4 can send a 27th NAS message to the UE. For example, the 27th NAS message can indicate that the UE's registration request to the fourth network is rejected, that the UE's secondary registration to the fourth network is rejected, or that the fourth network does not support secondary registration, etc.

[0352] In one example, the UE may receive a 27th NAS message. Because the 27th NAS message indicates at least one of the following: registration rejection, lack of secondary registration support, and / or disallowed secondary registration, the UE can determine that secondary registration to the fourth network is unsuccessful and can add the fourth network to the list of networks rejected for secondary registration. For example, for a network in the list of networks rejected for secondary registration, the UE may not select that network for secondary registration, may not use that network for secondary registration, may not send a registration request for secondary registration to that network, may use that network for other registrations besides secondary registration, and so on. For example, because the UE requested secondary registration and / or because the UE received an indication of registration rejection, the UE can determine that the network does not allow secondary registration. Based on this determination, the UE may not trigger another secondary registration process to a network in the list of networks rejected for secondary registration, and / or the UE may trigger a registration process for a network in the list of networks rejected for secondary registration (e.g., not for secondary registration). This can help the UE reduce unnecessary requests to the fourth network.

[0353] Figure 29 An example embodiment of this disclosure may be depicted. For example, a network (e.g., in the preceding figures) may send a list of secondary networks and / or a list of compatible networks to the UE. For the sake of brevity, redundant details will be omitted based on other parts of this disclosure.

[0354] In one example, the UE can receive one or more lists of secondary networks from one or more networks. For example, the one or more lists of secondary networks may include a first list of secondary networks and / or a tenth list of secondary networks. For example, the UE can receive a first list of secondary networks from a first network and / or the UE can receive a tenth list of secondary networks from a tenth network.

[0355] In one example, each of one or more lists of secondary networks may include one or more identifiers of one or more secondary networks and / or (for each secondary network) one or more conditions allowing the UE to use each secondary network. For example, the first list of secondary networks may include one or more identifiers of the first one or more secondary networks. For example, the first one or more identifiers may include a first network ID (e.g., network ID 1, PLMN1), a second network ID (e.g., network ID 2, PLMN 2), and / or a third network ID (e.g., network ID 3, SNPN 3), etc. For example, the first list of secondary networks may include one or more conditions for the first one or more secondary networks. For example, one or more conditions may include a first condition for the first network ID, a second condition for the second network ID, and / or a third condition for the third network ID. For example, the first condition may include information about a first time (e.g., 2:00 PM, lasting 30 minutes, etc.) and / or a first location (e.g., city A, T A B).

[0356] For example, for each network in the secondary network list, the UE can determine whether to allow each network for secondary registration. For example, based on a first condition, if the time is 2:00 PM, and / or if the UE is in city A, the UE can determine that it is allowed to perform secondary registration with the network (e.g., the first network ID). For example, based on the first condition, if the time is not 2:00 PM, and / or based on the UE not being in city A, the UE can determine that it is not allowed to perform secondary registration with the network (e.g., the first network ID) and / or may not send a request for secondary registration.

[0357] For example, if the UE (primarily) registers to the first network, the UE can determine the first list of secondary networks to use. For example, if the UE (primarily) registers to the first network, the UE can determine the tenth list of secondary networks not to use.

[0358] Figure 30 An example embodiment of this disclosure may be described. For the sake of brevity, redundant details will be omitted based on other parts of this disclosure.

[0359] In one example, the list of compatible networks may include information indicating network combinations permitted for primary / secondary registration and / or network combinations permitted for multiple (coordinated, dual, etc.) registrations. For example, the list of compatible networks may indicate:

[0360] – For the first network (e.g., network ID 1, PLMN 1), the second network (e.g., network ID 2, PLMN 2) and / or the third network (e.g., network ID 3, SNPN 3) can be used as secondary networks. That is, when the UE registers to the first network, the UE is allowed to perform secondary registration to the second network and / or the first network.

[0361] – For the second network (e.g., network ID 2, PLMN 2), the first network and / or the fourth network (e.g., network ID 4, SNPN 4) can be used as secondary networks. That is, when the UE registers to the second network, the UE is allowed to perform secondary registration to the first network and / or the fourth network.

[0362] In one example, the UE can receive a list of compatible networks from its home network and / or access network. For instance, the UE can receive the list of compatible networks from the UDM via the AMF (of the home network and / or access network). When the UE registers for a particular network, the list of compatible networks can indicate which one or more target networks are available for secondary registration. In this case, if a network might not send information about candidate networks for secondary registration, the UE can select / determine a network from the list of compatible networks and perform secondary registration with that network.

[0363] In one example, the list of compatible networks may also include information based on one or more conditions (e.g., similar to...). Figure 29 (Example shown). Figure 30 In the examples, one or more conditions may also include information about one or more network slices. For example, one or more network slices may be allowed for network combination and / or when the UE registers for a primary / secondary network. For example, the UE may subscribe to one or more network slices through a home network. Since home network management determines which network services the UE is allowed to use, the home network (e.g., UDM, SoR-AF, etc.) may be able to determine which network slices are available when the UE registers with one or more networks for secondary registration.

[0364] In one example, for a combination of a first network and a second network, the list of compatible networks may indicate that slice A, slice B, and / or slice C are allowed. For example, for a combination of a first network and a third network, the list of compatible networks may indicate that slice A and / or slice B are allowed. For example, based on the list of compatible networks, the UE can determine which networks it should perform primary and / or secondary registration with. For example, if the UE wants to use network slice A, it can determine to perform primary registration with the first network and / or the UE can determine to perform secondary registration with the second network. For example, if the UE wants to use network slice E, and if there is no network combination for network slice E in the list of compatible networks, the UE can determine not to perform secondary registration for network slice E. In another example, the UE may primarily register with the first network and / or secondarily register with the second network. In this case, because the list of compatible networks indicates that network slice B is allowed, the UE may request registration (or PDU session) for network slice B with the first network and / or with the second network. In this case, since the list of compatible networks does not indicate that network slice D is allowed, the UE may not request registration (or PDU session) for network slice D from the first network and / or the second network.

[0365] Figure 31 An example embodiment of this disclosure can be described. (and) Figure 29 and / or Figure 30 Similarly, a list of secondary networks and / or compatible networks can indicate one or more pairs of networks permitted for primary / secondary registration. Figure 31 In the example, the list of secondary networks can indicate the associated network slices. For the sake of brevity, redundant details will be omitted based on other parts of this disclosure.

[0366] In one example, the list of secondary networks can indicate one or more network slices. For example, one or more network slices can be one or more configured network slices and / or a home (subscribed) network slice. For each of the one or more network slices, the list of secondary networks can indicate one or more networks that are allowed for secondary registration. For example, after primary registration with a first network, the UE can receive a list of secondary networks. For example, the list of secondary networks can indicate that a second network (e.g., network ID 2) is allowed for secondary registration and / or for slice A. For example, the list of secondary networks can indicate that a second network (e.g., network ID 2) is allowed for secondary registration and / or for slice B. For example, after registering with a first network, if the UE needs to register for slice A, because the list of secondary networks indicates that slice A is allowed from a secondary network (e.g., the second network), the UE can perform secondary registration to the second network. For example, after primary registration with the first network and / or secondary registration with the second network, since the list of secondary networks indicates that slice A is allowed from the secondary network (e.g., the second network), the UE can send a request for slice A to the second network.

[0367] Figure 32 An example embodiment of this disclosure can be described. (and) Figure 27 Similarly, the UE can perform primary registration with the first network. Figure 32 In the example, the UE may register with a third network that does not support secondary registration and / or may notify the first network. For the sake of brevity, redundant details will be omitted based on other parts of this disclosure.

[0368] In one example, the UE may send a first NAS message and / or may receive a second NAS message from a first network. For example, the second NAS message may indicate that the first AMF and / or the first network supports features of secondary registration.

[0369] In one example, after primary registration with a first network, the UE may determine to perform additional registration. For example, the UE may search for other available networks and / or the UE may not find a network that supports secondary registration. In one example, the UE may detect a third cell in a third network that does not support secondary registration. For example, the UE may send a sixth NAS message to the third AMF and / or may receive a seventh (seventh) NAS message from the third AMF. For example, the seventh NAS message may indicate that the third network (or the third AMF) does not support the feature of secondary registration.

[0370] In one example, because the UE is primarily registered to a first network and / or because the UE is registered to a third network that does not support secondary registration, the UE may send an eleventh NAS message to the first AMF. For example, the eleventh NAS message may be at least one of a registration request, a service request, etc. For example, the eleventh NAS message may indicate at least one of the following: suspension of primary registration, cancellation of primary registration, cancellation request, unavailability of a secondary network, registration to a network that does not support secondary networks, etc.

[0371] In one example, the first AMF can receive an eleventh NAS message. Because the eleventh NAS message indicates at least one of the following: suspension of primary registration, deregistration of primary registration, request for deregistration, unavailability of secondary network, registration to a network that does not support secondary network, etc., the first AMF can perform at least one of the following: deregistration of UE, suspension of service to UE, notification to one or more SMFs handling one or more PDU sessions of UE, suspension of functions supporting secondary registration, suspension of functions associated with primary registration, deregistration of AMF from UDM, cancellation of resource allocation for UE in the first network, and not sending any signaling to UE before UE performs second registration.

[0372] When the UE cannot use the features registered in the secondary registration Figure 32 Examples of this approach can reduce unnecessary activity in the first network to manage the UE's context.

[0373] Figure 33 An example embodiment of this disclosure can be described. Similar to... Figure 32 The UE can then register with a third network that does not support secondary registration. Figure 33 In the example, the secondary registration status is notified to the first AMF. For the sake of brevity, redundant details will be omitted based on other parts of this disclosure.

[0374] In one example, after initial registration with a first network, the UE can perform registration with a third network. For instance, in response to receiving a sixth NAS message, the third AMF can register with the UDM by sending a sixth Nudm message. For example, the sixth Nudm message may not indicate that the third AMF and / or the third network support features for secondary registration.

[0375] In one example, the UDM can receive a sixth Nudm message. Because the sixth Nudm message does not indicate features supporting secondary registration, requests for secondary registration, etc., the UDM can determine that the third network does not support features supporting secondary registration. The UDM can determine whether a network / AMF exists for the UE's primary registration. For example, because the first AMF sends a first Nudm message to the UDM, and / or because the UDM has the stored information of the first AMF, the UDM determines that a registered AMF / network exists for the UE's primary registration. Because the first AMF / network is registered for primary registration and / or because the third AMF / network does not support features supporting secondary registration, the UDM can determine to send a notification to the first AMF / network. For example, this notification could instruct the UE to register to a network that does not support secondary registration, that the first network / AMF needs to discard / delete / unregister the UE from the first AMF / network, or that the first network / AMF suspends the UE's primary registration, etc.

[0376] In one example, in response to a received notification, the first AMF / network may determine to deregister the UE and / or may send an eighth NAS message to the UE. For example, the eighth NAS message may instruct the UE to deregister from the first network, suspend the UE's registration / activity in the first network, or at least one of the following:

[0377] Figure 34 An example embodiment of this disclosure can be described. (and) Figure 22 Similarly, the UE can use a list of secondary networks to select a network. For the sake of brevity, redundant details will be omitted based on other parts of this disclosure.

[0378] In one example, the UE may send a first message (e.g., a registration request message) to the first node of the first network (e.g., the AMF). For example, the first message may indicate support for features of secondary registration, a request for primary registration, a request for features to support secondary registration, etc.

[0379] In one example, the UE may receive a second message (e.g., a registration acceptance message, a UE configuration update, etc.) from the first node. For example, the second message may indicate at least one of the following: features supporting secondary registration, successful registration, acceptance of primary registration, permission to use a secondary network, permission to perform secondary registration, and a list of secondary networks (e.g., a list of network selections for secondary (multiple, supplementary, dual, etc.) registration).

[0380] In one example, the UE may determine to perform secondary registration. In another example, the UE may determine whether a network selection list is available. For example, if the network selection list is available, the UE may determine to perform secondary registration and / or may begin searching for one or more networks in the network selection list. For example, the network selection list may be a list of secondary networks.

[0381] In one example, the UE can determine whether one or more networks in the network selection list are detected / available. If one or more networks are available and / or if the UE detects cells of one or more networks, the UE can select a second network from the one or more networks and / or can perform secondary registration. For example, the UE can send a third message (e.g., registration request, service request) to the second network (or second AMF). For example, the third message can indicate at least one of the requests for secondary registration.

[0382] In one example, the UE may send a first message to a first mobility management node of a first network, indicating support for secondary registration with a secondary network associated with the first network. For example, the first mobility management node may be at least one of AMF, MME, SMF, UDM, SoR-AF, etc. For example, the first network may be at least one of PLMN, SNPN, PNI-NPN, etc. For example, the first network may be at least one of home network and first access network. For example, the first message may be at least one of registration request message, attach request message, service request, etc. For example, the first message may include at least one of the following: the UE's identifier, one or more identifiers of one or more requested network slices, an indication that the UE requests network support for secondary registration, an indication that the UE requests primary registration, and an indication of information regarding one or more networks that the UE requests support for (or permission for) secondary registration. For example, the UE may send the first message via a first access type.

[0383] In one example, support for secondary registration can be at least one of the following: support for features of secondary(multiple) registrations, and support for multiple (attached, dual, subsequent, concurrent, simultaneous, etc.) registrations performed through multiple networks with subscriptions. For example, support for secondary registration can instruct the UE to perform at least one of the following secondary registrations: For example, the UE can instruct the UE to support secondary registration to a secondary network; For example, the UE can perform secondary registration to a secondary network; For example, the secondary network can be associated with a first network; For example, the secondary network may be able to exchange signaling with the first network; For example, when the UE registers to a first (e.g., primary) network, the secondary network can allow the UE to register to the secondary network; For example, the UE can register to the secondary network using a first access type (e.g., 3GPP RAN, 3GPP RAT, NG-RAN, NR), while the UE registers to the first network using the first access type.

[0384] In one example, the UE may receive a second message from a first mobility management node, the second message including information about one or more candidate networks for secondary registration. For example, the second message may be at least one of a UE configuration update message, a registration acceptance message, a service acceptance message, a DL NAS delivery message, etc. For example, the information about one or more candidate networks may include identifiers for one or more networks for the primary network. For example, one or more networks may be one or more secondary networks. For example, one or more networks may be one or more networks that allow the UE to perform secondary registration. For example, one or more candidate networks may include an allowed network. For example, an allowed network may be a second network. For example, secondary registration may be at least one of the following: the UE registers with an allowed network for an access type, and the UE registers with a first network for that access type; the UE registers with more than one network using that access type; the UE is served by more than one network for that access type; more than one mobility management node serves the UE for that access type; or the UE registers with more than one mobility management node for that access type (e.g., 3GPP access). For example, the second message may indicate whether the first network supports features of secondary registration and / or whether it allows the UE to perform secondary registration. For example, the second message may indicate one or more network slices supported by and / or permitted for secondary registration by a secondary network. For instance, the second message may contain a policy container with a set of URSP rules that indicate to a set of applications which slice to use to establish a PDU session via primary and / or secondary registration. For example, one or more network slices may be supported by a primary network and / or a secondary network. For example, each secondary network may be at least one of a PLMN, SNPN, PNI-NPN, etc. URSP rules may indicate that PDU sessions on secondary networks require the same PDU session ID as PDU sessions on the primary network. URSP rules may include conditions indicating minimum signal strength, or conditions indicating whether certain networks (e.g., networks indicated by PLMN IDs) are available to the UE and / or which SUPI the URSP rules apply to, and the UE can only use the corresponding URSP rules if these conditions are met. Please note that policy updates (e.g., using the UCU procedure to include updated URSP rules) can be performed before requesting / establishing PDU sessions on both the primary and secondary networks, or a set of related PDU sessions. Therefore, after receiving the second message, the UE can (re)perform primary registration to the first network and / or (re-establish) a PDU session on the first network. This means that there may be a significant time interval between the second and third messages described below.

[0385] In one example, the UE can search, measure, and / or detect one or more cells. The one or more cells may be available at the UE's location. For example, the one or more cells may include one or more second cells of a second network and / or one or more third cells of a third network. For example, one or more candidate networks for secondary registration may include the second network and / or may not include the third network. Based on information from one or more candidate networks (e.g., because one or more candidate networks include the second network), and because the UE detects a second cell of the second network, the UE can select the second cell and / or the second network. In one example, the UE can receive one or more SIBs from one or more cells. For example, each of the one or more SIBs may indicate whether the network associated with the cell supports the features of secondary registration.

[0386] In one example, the UE may send a third message requesting secondary registration to a second mobility management node of a second network (e.g., an allowed network). For example, the third message may be at least one of a registration request, a service request, etc. For example, the third message may instruct the UE to request secondary registration and / or the UE to support secondary registration at least one of these. For example, the UE may send the third message via a first access type (e.g., a 3GPP access type).

[0387] In one example, the UE may primarily register to a first network and / or secondarily register to a second network. The UE may use resource requests from the first and / or second networks to establish multiple access PDU sessions.

[0388] In one example, alternatively and additionally, the first network may be a second network. For example, information about one or more candidate networks may include information indicating one or more RAT types (e.g., NR, LTE, E-UTRA, 6G radio, etc.), one or more RAN types (E-UTRAN, NG-RAN, 6G-RAN, satellite RAN, terrestrial RAN, etc.), and / or one or more core networks (EPC, 5GC, 6GC, etc.). For secondary registration and / or for the selection of secondary networks (e.g., access tributary, RAT, RAN), the UE may use information about one or more candidate networks. For example, if information about one or more candidate networks indicates at least one of a first RAT type (e.g., NR), a first RAN type (e.g., satellite RAN), etc., the UE may select a cell (or network) of the first RAT type, first RAN category, etc. Based on the selection of that cell (or network), the UE may send a third message. For example, the UE may use a first subscription to access the second network. For example, the UE may use a first subscription to access the first network. For example, the first subscription may be associated with the UE's home network (used and allocated with the UE's home network).

[0389] In one example, the network's first mobility management node can receive a registration request message from a wireless device, indicating support for secondary registration with a secondary network associated with that network. The first mobility management node can also receive configuration information from a second control plane node, indicating permitted networks for secondary registration. The first mobility management node can then send a registration acceptance message to the wireless device, including information about the permitted networks.

[0390] In one example, the mobility management node of the primary network can receive a first Non-Access Stratum (NAS) message from the wireless device instructing the wireless device to support secondary registration. The mobility management node can also receive information from the data (policy) management node regarding one or more secondary networks permitted for secondary registration and / or an indication of whether the use of a secondary network (or secondary registration) is permitted. The mobility management node can then send a second NAS message to the wireless device, including information about one or more secondary networks.

[0391] In one example, a wireless device may receive a message from a mobility management node (of a home network) instructing one or more first networks and one or more second networks associated with at least one of the one or more first networks. While registering with at least one first network, the wireless device may also be allowed to register with at least one of the one or more second networks. The wireless device may send a registration request message to at least one second network.

[0392] In one example, a wireless device (e.g., a UE) can receive a first RRC message (e.g., an SIB) from a base station (e.g., a gNB, cell, eNB) indicating that the network supports secondary registration. The wireless device can then send a second RRC message to the base station. For example, the second RRC message may include an indication that the UE requests to connect to the secondary network. For example, the second RRC message may include a registration request message requesting secondary registration.

Claims

1. A method comprising: A first message is sent by a wireless device to a first mobility management node of the network, the first message indicating support for secondary registration to a secondary network associated with the network; The wireless device receives a second message from the first mobility management node, the second message including information about allowed networks for the secondary registration; as well as The wireless device sends a third message to the second mobility management node of the permitted network, the third message requesting the secondary registration.

2. The method of claim 1, further comprising the allowed network selected by the wireless device for the secondary registration.

3. A method comprising: A wireless device receives a first message from a first mobility management node of the network, the first message including information about one or more secondary networks that allow secondary registration to the network; as well as The wireless device sends a second message to a second mobility management node of an authorized network in one or more secondary networks, the second message requesting secondary registration.

4. The method according to any one of the preceding claims, wherein, The first mobility management node is at least one of an access and mobility management function (AMF) or a mobility management entity (MME).

5. The method according to any one of the preceding claims, wherein, The first message is at least one of the UE configuration update message and the registration acceptance message.

6. The method according to any one of the preceding claims, wherein, The second message is at least one of a registration request or a service request message.

7. The method according to any one of the preceding claims further includes the wireless device sending a message indicating support for secondary registration to the first mobility management node of the network.

8. The method according to any one of the preceding claims, wherein, Sub-registration includes at least one of the following: - The wireless device is registered to the allowed network for the access type, and the wireless device is registered to the network for the access type. - The wireless device registers with more than one network using the access type. - More than one network serves the wireless device for the access type. - More than one mobility management node serves the wireless device for the access type, or - The wireless device is registered to more than one mobility management system for the access type.

9. The method according to any one of the preceding claims further includes the wireless device selecting the allowed network (target network) among the one or more secondary networks.

10. The method according to any one of the preceding claims further includes measuring one or more cells of one or more networks by the wireless device.

11. The method according to claim 9, wherein, The wireless device selects the target network based on measuring the cells of the target network.

12. The method according to any one of the preceding claims further includes receiving a system information block (SIB) from the target network by the wireless device.

13. The method according to claim 12, wherein, The SIB indicates whether the target network supports the secondary registration.

14. The method according to any one of the preceding claims, wherein, The second message also includes an indication of whether the primary network supports secondary registration.

15. The method according to any one of the preceding claims, wherein, The wireless device sends the second message based on the primary network supporting secondary registration.

16. The method according to any one of the preceding claims, wherein, The second message also includes an indication of one or more network slices supported by networks in the one or more secondary networks.

17. The method according to claim 16, wherein, The network slices in the one or more network slices are supported by the primary network and the secondary network.

18. The method according to any one of the preceding claims, wherein, Each of the one or more secondary networks is at least one of PLMN, SNPN, and PNI-NPN.

19. The method according to claim 18, wherein, The second message indicates the identifier of each of the one or more networks.

20. The method according to any one of the preceding claims further includes establishing a Protocol Data Unit (PDU) session by the wireless device using resources of the main network and resources of the target network.

21. The method according to any one of the preceding claims further includes establishing a first Protocol Data Unit (PDU) session by the wireless device using resources of the main network, and establishing a second Protocol Data Unit session using resources of the target network.

22. The method of claim 21, further comprising receiving a policy container containing a set of URRSP rules, the set of URRSP rules indicating at least one of the following: - For a set of applications used for PDU session establishment, - The PDU sessions on the target network need to use the same PDU session ID as the PDU sessions on the main network, and - Minimum signal strength or whether a specific network is unavailable or available to the UE.

23. The method of claim 20, wherein, The wireless device establishes the PDU session after receiving a registration acceptance from the target network.

24. The method according to any one of the preceding claims, wherein, The wireless device accesses the target network via a 3GPP access type.

25. The method according to any one of the preceding claims, wherein, The wireless device accesses the main network via a 3GPP access type.

26. The method according to claims 24 and 25, wherein, The wireless device accesses the main network via the 3GPP access type and also accesses the target network via the 3GPP access type.

27. The method according to any one of the preceding claims, wherein, The wireless device uses a first subscription to access the main network.

28. The method according to claim 27, wherein, The wireless device uses the first subscription to access the target network.

29. The method according to claims 27 and 28, wherein, The first subscription is associated with the home network of the wireless device.

30. The method according to any one of the preceding claims, wherein, The wireless device uses a first access type to access the main network.

31. The method according to claim 30, wherein, The wireless device uses the first access type to access the target network.

32. A method comprising: The first mobility management node of the network receives a registration request message from the wireless device, the registration request message indicating support for secondary registration to a secondary network associated with the network; The first mobility management node receives configuration information from the second control plane node, the configuration information indicating the allowed networks for the secondary registration; as well as The first mobility management node sends a registration acceptance message to the wireless device, the registration acceptance message including information about the allowed network.

33. A method comprising: The mobility management node of the main network receives a first non-access stratum (NAS) message from the wireless device, the first non-access stratum (NAS) message indicating that the wireless device supports secondary registration; The mobility management node receives information from the data (policy) management node regarding one or more secondary networks that allow the secondary registration; as well as The mobility management node sends a second NAS message to the wireless device, the second NAS message including the information from the one or more secondary networks.

34. A method comprising: The mobility management node receives information from the data (policy) management node regarding one or more secondary networks that are permitted to perform secondary registration; as well as The mobility management node sends a second NAS message to the wireless device, the second NAS message including the information from the one or more secondary networks.

35. A method comprising: The mobility management node sends an instruction to the roaming application function to indicate that the wireless device supports secondary registration.

36. A method comprising: A message is received by the wireless device from the mobility management node (of the home network), the message indicating: - One or more first networks; as well as - One or more second networks for at least one of the one or more first networks, wherein the wireless device is allowed to register with at least one of the one or more second networks; as well as The wireless device sends a registration request message to the at least one second network.

37. A method comprising: A message is received from the network by a wireless device, the message indicating that the network does not support secondary (multiple) registrations; as well as The wireless device is deregistered from the main registry.

38. A method comprising: The wireless device receives an RRC message from the network's base station, the RRC message indicating that the network supports secondary (multiple) registrations; as well as The wireless device sends a registration request message to the base station requesting secondary registration.

39. A method comprising: The wireless device receives a message from the network indicating that secondary (multiple) registrations have been rejected.

40. A method comprising: A message is received from the network by a wireless device, the message indicating that the network does not support secondary (multiple) registrations; as well as The wireless device sends a deregistration message to the main network.

41. A method comprising: The core network node receives a registration request for a wireless device from the second AMF; wherein the registration request is associated with multiple access paths of an access type; and The core network node sends a message to the first AMF indicating that the first AMF has been deregistered.

42. A method comprising: A first message is sent by a wireless device to a first mobility management node of the main network, the first message indicating support for secondary registration to at least one secondary network associated with the main network; The wireless device receives a second message from the first mobility management node, the second message including information about one or more secondary networks that allow the secondary registration; The wireless device selects a target network from the one or more secondary networks; as well as The wireless device sends a third message to the second mobility management node of the target network, the third message requesting the secondary registration.

43. An apparatus comprising: transmitter, Receiver, and A controller coupled to the transmitter and the receiver is configured to perform the following steps: The transmitter sends a first message to a first mobility management node of the network, the first message indicating support for secondary registration to a secondary network associated with the network; The second message received from the first mobility management node is decoded, the second message including information about allowed networks for the secondary registration; as well as The transmitter sends a third message to the second mobility management node of the permitted network, the third message requesting the secondary registration.

44. An apparatus comprising: transmitter Receiver A controller coupled to the transmitter and the receiver is configured to perform the following steps: Decode a first message received from a first mobility management node of the network, the first message including information about one or more secondary networks that allow secondary registration to the network; as well as The transmitter sends a second message to a second mobility management node of an authorized network in one or more secondary networks, the second message requesting secondary registration.

Images