Technique for indirect network sharing

Abstract

To provide a device, method and program for indirect network sharing.SOLUTION: A method to be executed by a device receives a first message for registering a UE with a participating networks associated with a hosting network, and transmits a second message including support information based on the received first message. The support information includes a permission NSSAI for the UE, a partial permission NSSAI for the UE, or both of them, and is associated with the permission NSSAI or a corresponding partial permission NSSAI associated with the hosting network. The method also transmits a third message to a second network entity of the hosting network. The third message includes the permission NSSAI or the partial permission NSSAI for the UE, a permission NSSAI or partial permission NSSAI associated with the hosting network corresponding to both of them, or both of them.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present disclosure relates to wireless communications, and more particularly to techniques for indirect network sharing. [Background technology]

[0002] A wireless communication system may include one or more network communication devices, such as base stations (BSs), which may support wireless communication for one or more user communication devices, which may also be known as user equipment (UEs) or other suitable terminology. A wireless communication system may support wireless communication with one or more user communication devices by utilizing wireless communication system resources (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Furthermore, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] TS 38.331 [Non-patent document 2] 3GPP TS 23.501, V18.5.0, 2024-03 [Non-patent document 3] 3GPP TS 23.502, V18.5.0, 2024-03 Summary of the Invention [Means for solving the problem]

[0004] The article "a" before an element is understood to refer, without limitation, to "at least one" of those elements or "one or more" of those elements. The terms "a," "at least one," "one or more," and "at least one of one or more" may be interchangeable. As used herein, including the claims, "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of" or "one or both of") indicates an inclusive list, such as, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase "based on" should not be construed as referring to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the disclosure. In other words, as used herein, the phrase "based on" shall be interpreted similarly to the phrase "based at least in part on." Furthermore, as used herein, including the claims, a "set" may include one or more elements.

[0005] In one embodiment, an apparatus receives a first message for registering a UE with a participating network associated with a hosting network, and transmits a second message including assistance information based at least in part on the received first message, wherein the assistance information is an allowed Network Slice Selection Assistance Information (NSSAI) for the UE or a partial allowed NSSAI for the UE. and sending a third message to a second network entity of the hosting network, the third message including the authorization NSSAI or partial authorization NSSAI for the UE, or both the authorization NSSAI for the UE and the partial authorization NSSAI for the UE, wherein each of the authorization NSSAI or partial authorization NSSAI, or both the authorization NSSAI and the partial authorization NSSAI, is associated with a corresponding authorization NSSAI or partial authorization NSSAI related to the hosting network that corresponds to the authorization NSSAI or partial authorization NSSAI for the UE, or both the authorization NSSAI and partial authorization NSSAI for the UE. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 illustrates an example of a wireless communication system according to aspects of the present disclosure. [Figure 2] FIG. 1 illustrates an example architecture of a 5G Multi-Operator Core Network (5G MOCN) sharing the same next generation radio access network (NG-RAN), according to aspects of the present disclosure. [Figure 3] FIG. 1 illustrates an example architecture for 5G indirect network sharing, according to an aspect of the present disclosure. [Figure 4] FIG. 1 illustrates an example 5G system roaming architecture for a home routed scenario with a service-based interface representation in accordance with an aspect of the present disclosure. [Figure 5] FIG. 10 illustrates an example signal flow of a UE registration procedure with a hosting network operator in case of indirect network sharing, according to an aspect of the present disclosure. [Figure 6] FIG. 1 illustrates an example signal flow for protocol data unit (PDU) session establishment for indirect network sharing, according to an aspect of the present disclosure. [Figure 7] FIG. 1 illustrates an example of a UE according to an aspect of the present disclosure. [Figure 8] FIG. 1 illustrates an example processor according to aspects of the present disclosure. [Figure 9] FIG. 1 illustrates an example of network equipment (NE) according to an aspect of the present disclosure. [Figure 10] 1 is a flow diagram of a method performed by a device according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0007] Wireless communication systems, such as 5G network systems, may implement network slicing, a concept that allows network operators to divide ("slice") their networks at finer granularities of the complete network, called network slices, to provide customized network connectivity (or network features) for customers or application service providers.

[0008] A network slice is a logical network consisting of a set of network functions and corresponding resources (e.g., computing, storage, networking) required to provide specific network capabilities and characteristics. A network slice may include the control and user plane network functions (NFs) of a core network (e.g., a 5G core network, 5GC) and an access network (e.g., a 5G radio access network or a fixed access network).

[0009] A UE may be configured with network slice-related information called an NSSAI, which may consist of one or more single NSSAIs (S-NSSAIs).

[0010] A UE requests registration to a network slice by sending a NAS Registration Request message to a 5GC (e.g., an access and mobility management function (AMF)) including a Requested NSSAI, which includes a list of one or more S-NSSAIs to which the UE wishes to register. The 5GC (e.g., an AMF) may send one or more of the following elements related to the UE's network slice configuration in a Registration Accept message or a UE Configuration Update Command message: 1) Allowed NSSAI, 2) optionally, in the case of roaming, a mapping of the Allowed NSSAI to the S-NSSAI value of the home public land mobile network (HPLMN), 3) Configured NSSAI, 4) optionally, in the case of roaming, a mapping of the Configured NSSAI to the S-NSSAI value of the HPLMN, 5) Rejected NSSAI, or 6) Reserved NSSAI. The NSSAI may include a list of one or more S-NSSAIs.

[0011] One aspect of the network slicing configuration of the UE is that a serving operator (e.g., a visited PLMN (VPLMN)) can control, per access type, which NSSAI the UE includes in the Access Stratum (AS) when establishing a connection in response to a service request, a periodic registration update, or a registration procedure used to update the UE's capabilities. Furthermore, the HPLMN and VPLMN can also instruct the UE not to include the NSSAI in the AS, regardless of the procedure causing the radio resource control (RRC) connection to be established, e.g., to enable privacy with respect to the NSSAI. The AMF sends an access stratum connection establishment NSSAI inclusion mode parameter to the UE indicating whether and when the UE includes NSSAI information in the AS connection establishment (e.g., the RRC connection establishment defined in TS 38.331, incorporated herein by reference) according to one of these modes.

[0012] Mode a: The UE includes the NSSAI set to the Authorized NSSAI, if available, in a service request used to update the UE capabilities, a periodic registration update, or an AS connection establishment triggered by a registration procedure.

[0013] Mode b: In the case of AS connection establishment triggered by a service request, the UE includes an NSSAI containing the S-NSSAI of the network slice that triggers the AS connection establishment, for example, the S-NSSAI of the PDU session that causes the user plane to be reactivated by the service request, or an NSSAI containing the S-NSSAI of the network slice to which the control plane interaction that triggers the service request is related. For example, for session management (SM), it would be the S-NSSAI of the PDU session to which the SM message is associated.

[0014] Furthermore, for mode b, the UE includes an NSSAI with the NSSAI set to the Authorized NSSAI in case of a periodic registration update or an AS connection establishment triggered by a registration procedure used to update the UE's capabilities.

[0015] Mode c: The UE does not include the NSSAI in AS connection establishments triggered by service requests, periodic registration updates, or registration procedures used to update the UE's capabilities.

[0016] Mode d: The UE does not provide an NSSAI in the AS, for example, to exclude an NSSAI, refrain from sending an NSSAI, etc.

[0017] Further information about network slicing and 5GS can be found in 3GPP TS 23.501, V18.5.0, 2024-03 (incorporated herein by reference), and 3GPP TS 23.502, V18.5.0, 2024-03 (incorporated herein by reference).

[0018] In a specific embodiment, indirect network sharing is based on a roaming architecture. In other words, the hosting network acts as a VPLMN, and the participating network acts like a HPLMN. UE traffic is forwarded to the participating network by using a home-routed PDU session. However, because the hosting network acts like a VPLMN, but the UE acts as if it is connected and registered to the home network, the network slicing configuration of the roaming network is not configured for this purpose. Therefore, the current framework for supporting network slicing for roaming cannot be applied as is, and an extension of the VPLMN behavior is required.

[0019] Aspects of the present disclosure are described in the context of a wireless communication system.

[0020] 1 illustrates an example of a wireless communication system 100 according to an aspect of the present disclosure. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be an NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G, such as 6G. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0021] One or more NEs 102 may be distributed throughout a geographic region to form the wireless communication system 100. One or more of the NEs 102 described herein may be, include, or be referred to as a network node, base station, network element, network function, network entity, radio access network (RAN), NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terminology. The NEs 102 and UEs 104 may communicate via communication links that may be wireless or wired. For example, the NEs 102 and UEs 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0022] An NE 102 may provide a geographic coverage area in which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, the NE 102 and the UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the NE 102, e.g., a satellite associated with a non-terrestrial network (NTN), may be mobile. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, although different geographic coverage areas may be associated with different NEs 102.

[0023] One or more UEs 104 may be dispersed throughout the geographic region of the wireless communication system 100. The UEs 104 may include or be referred to as remote units, mobile devices, wireless devices, remote devices, subscriber devices, transmitter devices, receiver devices, or some other suitable terminology. In some implementations, the UEs 104 may be referred to as units, stations, terminals, or clients, among other examples. Additionally or alternatively, the UEs 104 may be referred to as Internet-of-Things (IoT) devices, Internet-of-Everything (IoE) devices, or machine-type communication (MTC) devices, among other examples.

[0024] The UE 104 may be capable of supporting direct wireless communication with other UEs 104 via a communication link. For example, the UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as a vehicle-to-vehicle (V2V) deployment, a vehicle-to-everything (V2X) deployment, or a cellular-V2X deployment, the communication link 114 may be referred to as a sidelink. The UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0025] An NE 102 may support communication with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NEs 102 or the CN 106 through one or more backhaul links (e.g., S1, N2, N2, or network interfaces). In some implementations, the NEs 102 may communicate directly with each other. In some other implementations, the NEs 102 may communicate indirectly with each other (e.g., via the CN 106). In some implementations, one or more NEs 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio head, smart radio head, or transmit-receive point (TRP).

[0026] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC) or 5G core (5GC) that may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)), and user plane entities that route packets or interconnect to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more NEs 102 associated with the CN 106.

[0027] The CN 106 may communicate with a packet data network via one or more backhaul links (e.g., via S1, N2, N3, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. The UE 104 may establish a session (e.g., a PDU session, etc.) with the CN 106 via the NE 102. The CN 106 may route traffic (e.g., control information, data, etc.) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0028] In the wireless communication system 100, the NEs 102 and UEs 104 may perform various operations (e.g., wireless communications) using resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). In some implementations, the NEs 102 and UEs 104 may support different resource structures. For example, the NEs 102 and UEs 104 may support different frame structures. In some implementations, such as 4G, the NEs 102 and UEs 104 may support a single frame structure. In some other implementations, such as 5G, among other suitable radio access technologies, the NEs 102 and UEs 104 may support different frame structures (i.e., multiple frame structures). The NEs 102 and UEs 104 may support different frame structures based on one or more numerologies.

[0029] One or more numerologies may be supported in the wireless communication system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth carrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0030] Time intervals of resources (e.g., communication resources) may be organized by frames (also called radio frames). Each frame may have a duration, e.g., 10 milliseconds (ms). In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, e.g., 1 ms. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0031] Additionally or alternatively, time intervals of resources (e.g., communication resources) may be organized by slots. For example, a subframe may include a certain number (e.g., amount) of slots. The number of slots in each subframe may also depend on one or more numerologies supported in the wireless communication system 100. For example, first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz, respectively, may utilize 1 slot per subframe, 2 slots per subframe, 4 slots per subframe, 8 slots per subframe, and 16 slots per subframe, respectively. Each slot may include a certain number (e.g., amount) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., amount) of slots in a subframe may depend on the numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to 60 kHz subcarrier spacing), a slot may contain 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for normal cyclic prefix and extended cyclic prefix may depend on the numerology. It should be understood that references to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframe and slot.

[0032] In the wireless communication system 100, the electromagnetic (EM) spectrum may be divided into various classes, frequency bands, frequency channels, etc. based on frequency or wavelength. By way of example, the wireless communication system 100 may support one or more operating frequency bands, such as frequency range designations FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications on one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices, for cellular communication traffic (e.g., control information, data). In some implementations, FR2 may be used by NEs 102 and UEs 104, among other equipment or devices, for its short-range, high-data-rate capabilities.

[0033] FR1 may be associated with one or more numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., μ=0) including a subcarrier spacing of 15 kHz, a second numerology (e.g., μ=1) including a subcarrier spacing of 30 kHz, and a third numerology (e.g., μ=2) including a subcarrier spacing of 60 kHz. FR2 may be associated with one or more numerologies (e.g., at least two numerologies). For example, FR2 may be associated with a third numerology (e.g., μ=2) including a subcarrier spacing of 60 kHz, and a fourth numerology (e.g., μ=3) including a subcarrier spacing of 120 kHz.

[0034] FIG. 2 illustrates an example architecture of a 5G MOCN sharing the same NG-RAN, according to aspects of the present disclosure. In one embodiment, 5GS enables the sharing of resources or functions among different network operators 202a-c. 5GS provides that multiple participating network operators 202a-c (referred to as mobile network operators (MNOs)) can share resources of a single shared network according to an agreed-upon allocation scheme. The shared network, in one embodiment, includes a radio access network 204. An example is shown in FIG. 2, where CNs (e.g., 5GCs) of operators A 202a, B 202b, and C 202c share RAN resources. This is known as a 5G MOCN network sharing architecture, where each core network (CN) of the participating operators is directly connected to the shared RAN.

[0035] FIG. 3 illustrates an example architecture for 5G indirect network sharing according to aspects of the present disclosure. In one embodiment, an indirect network sharing deployment between a hosting operator 304 (e.g., a shared network operator) and one or more participating operators 302 a-c may be supported. This is illustrated in FIG. 3, where hosting operator "H" 304 shares its RAN and 5GC 306 to participating operators "L" 302 a, "M" 302 b, and "N" 302 c. Communications between the shared RAN 306 and the core networks of participating operators "L" 302 a, "M" 302 b, and "N" 302 c are routed through the core network of hosting operator "H" 304, which connects to the shared RAN 306.

[0036] For indirect network sharing, the shared RAN 306 broadcasts multiple PLMN IDs, including a PLMN ID representing the hosting operator 304 and a PLMN ID representing the participating operators 302a-c. Multiple PLMN IDs are supported by the serving AMF (e.g., the AMF of the core network of the PLMN representing the hosting operator 304).

[0037] A UE from a participating operator 302a-c can select a PLMN ID representing the participating operator 302a-c within the area of ​​the shared RAN 306 according to existing procedures. The serving AMF selects a core network function in the participating operator's PLMN for the UE based on the principles of home routed roaming architecture, see e.g., 3GPP TS 23.501, V18.5.0, 2024-03. Furthermore, the serving AMF selects a session management function (SMF) of the participating operator 302a-c, possibly taking into account the UE's location information, and also selects a V-SMF in its own network during the PDU session establishment procedure.

[0038] 4 illustrates an example of a 5G system roaming architecture for a home-routed scenario in a service-based interface representation according to an aspect of the present disclosure. A UE 402 registers with a (serving) AMF 404 in a VPLMN 401. The AMF 404 retrieves the UE's 402 subscription data from a UDM 406 in a HPLMN 403. When a home-routed PDU session is established, the AMF 404 in the VPLMN 401 selects both a) an SMF 408 in the VPLMN 401, referred to as the V-SMF, and b) an SMF 410 in the HPLMN 403, referred to as the H-SMF. The AMF 404 forwards the PDU session establishment request from the UE 402 to the V-SMF 408, which selects a UPF 412 in the VPLMN 401 and forwards the PDU session establishment request to the H-SMF 410. The H-SMF 410 retrieves the PDU session subscription data from the UDM 406, establishes an SM policy association with the H-PCF 414, selects an anchor UPF 416, and sends a PDU session establishment response (e.g., accept) message to the V-SMF 408.

[0039] In one embodiment for indirect network sharing, from the UE side, a UE in the area of ​​a shared RAN selects a participating operator, and the UE registers with the participating operator. The intermediate 5GC of the hosting operator is transparent to the UE. Correspondingly, the procedure from the UE side is the same as when the UE registers with and communicates directly with the participating operator. The participating operator can be either the HPLMN or VPLMN of the UE. The AMF of the hosting operator (e.g., the serving AMF) needs to mimic the behavior of the AMF of the participating operator's 5GC toward the UE; e.g., the network slice configuration toward the UE is configured as if it came from the 5GC of the participating operator. In one example, the authorized NSSAI created and sent to the UE includes the S-NSSAI value of the participating operator. However, the serving AMF needs to behave similarly to the AMF of the VPLMN toward the hosting operator's network function (NF) and toward the shared RAN. The subject matter of this specification describes, for example, how the AMF of a hosting MNO behaves and what information it provides to the shared RAN, the hosting operator's 5GC entities and NFs, and the participating operators' 5GC NFs.

[0040] In one embodiment, the following is based on the above Figures 3 and 4. In one embodiment, the present disclosure describes how the AMF of the hosting network 1) applies a specific mode of operation as the serving AMF of the hosting network operator to act as the AMF of the participating network towards the UE (e.g., create a network configuration for the UE as if the UE were registered in the participating network, e.g., HPLMN), and 2) the AMF acts as the AMF in the VPLMN towards the NFs of the hosting network and towards the RAN of the 5GC (e.g., as if the UE were registered in the VPLMN).

[0041] Generally, the AMF of a hosting operator may assume the role of serving AMF of a hosting network. In one embodiment, the AMF determines that a UE is registered with a participating operator (e.g., based on a service level agreement (SLA) between the hosting network and the participating network). The AMF may support "functioning as serving AMF of a hosting network," and thus may register itself with a network repository function (NRF) or a neighboring AMF, or may advertise a specific profile (or capability) in the NRF or a neighboring AMF that the AMF supports to act as serving AMF of a hosting network. Such a function may be referred to as the serving AMF function of the hosting network.

[0042] In one embodiment, the AMF does not provide the UE with a configuration NSSAI for the hosting network (e.g., a configuration NSSAI that includes the S-NSSAI of the hosting operator), for example, based at least in part on or in response to a registration request message that excludes, does not provide, does not include, etc. an NSSAI. Even if the UE does not send a request NSSAI, the AMF does not create and provide a configuration NSSAI to the UE. Instead, the AMF provides an authorization NSSAI. The AMF may provide a configuration NSSAI for a participating operator (i.e., a configuration NSSAI that includes the S-NSSAI of the participating operator) if it is supplied with such information.

[0043] In one embodiment, the AMF (or together with the Network Slice Selection Function (NSSF) of the hosting network) uses the Subscribed S-NSSAI (e.g., received from the UDM, or received from the source AMF, or stored from a previous registration), the hosting network's mapping / corresponding S-NSSAI to S-NSSAI from the participating network, and locally available S-NSSAI from the hosting network to determine, for example, an allowed NSSAI for the UE including the participating operator's S-NSSAI and / or a partially allowed NSSAI for the UE to be sent to the UE. Furthermore, the AMF may create a rejected S-NSSAI for the participating operator if part of the UE's requested S-NSSAI is not supported in the hosting network (e.g., there is no available corresponding S-NSSAI of the hosting network).

[0044] In one embodiment, the AMF uses the subscription S-NSSAI (e.g., received from the UDM, or received from the source AMF, or stored from a previous registration), the hosting network's mapping / corresponding S-NSSAI to S-NSSAI from the participating network, and a locally available S-NSSAI from the hosting network to determine an authorized NSSAI for the hoster (or a partially authorized NSSAI for the hoster), e.g., including the hoster's S-NSSAI value mapped to the participating operator's S-NSSAI value. The authorized NSSAI for the hoster (or the partially authorized NSSAI for the hoster) is used only internally to the hosting network. The authorized NSSAI for the hoster may correspond to a "mapping of authorized NSSAIs" stored locally in the AMF and including a mapping of each S-NSSAI of a participating MNO to the hosting MNO's S-NSSAI.

[0045] In one embodiment, the AMF configures mode "d" (described above) for operator-controlled inclusion of the NSSAI in AS signaling, which means that the UE does not provide the NSSAI in the AS.

[0046] In one embodiment, where Network Slice AS Groups (NSAGs) are used in the NG-RAN and configured in the AMF, and the UE has indicated support for NSAGs, the AMF provides NSAG information to the UE. As used herein, NSAG identifies a network slice or a set of network slices within a tracking area (TA). In one embodiment, the AMF provides NSAG identifiers from the hosting operator corresponding to the hosting operator's S-NSSAI, and each NSAG identifier is associated with one or more S-NSSAIs of the participating operators included in the authorized NSSAI for the UE and / or the partially authorized NSSAI for the UE. The AMF internally creates a mapping between the participating operators' S-NSSAIs and the hosting operator's S-NSSAI so that the AMF can determine which NSAG identifiers of the hosting operator are associated with the participating operators' S-NSSAIs.

[0047] In one embodiment, the AMF uses the authorization NSSAI for the hoster in signaling to the PCF for AM policy establishment. In one embodiment, the AMF sends the authorization NSSAI for the hoster to the RAN in an N2 signal, while sending the authorization NSSAI for the UE and / or the partial authorization NSSAI for the UE to the UE in a registration accept message.

[0048] In one embodiment, during a PDU session establishment procedure initiated by the UE, the AMF inserts the S-NSSAI of the hosting operator (corresponding to the S-NSSAI of the participating operator included in the NAS request message by the UE) into a request message to the SMF for the creation of an SM.

[0049] It is noted that although the description uses the term PLMN for public network, the solution may also be applied to non-public networks, for example standalone non-public networks (SNPNs). It is also noted that a hosting operator is identified by its PLMN ID and a participating operator is identified by its PLMN ID.

[0050] 5 illustrates an example signal flow of a UE registration procedure with a hosting network operator in the case of indirect network sharing according to an embodiment of the present disclosure. In particular, FIG. 5 illustrates a signal flow of how the AMF derives and stores an authorized NSSAI for the hosting operator and how the AMF provides this information to the PCF, the RAN, or other entities of the hosting network.

[0051] At 1 (see messaging 502), in one embodiment, the UE 501 selects a PLMN ID broadcasted by a cell of the shared RAN 503. The UE 501 creates and sends a registration request message to be included in access stratum RRC signaling to the RAN node. The UE 501 also indicates the selected PLMN ID to the RAN node. The registration request message may include a Subscription Concealed Identifier (SUCI) and a Request NSSAI. In one example, the Request NSSAI may include, for example, the S-NSSAI values ​​S1, S2, and S3 of the participating operators. The UE 501 uses a locally stored configured NSSAI for the participating operator's PLMN ID. In one embodiment, the RAN node (e.g., gNB) selects an AMF 505, creates an N2 message, and sends the N2 message to the selected AMF 505. The AN parameter may include the selected PLMN ID indicated by the UE 501.

[0052] In 2a (see block 504), in one embodiment, the AMF 505 determines, based on the indicated selected PLMN ID, that the UE 501 registers with the participating network operator identified by the indicated selected PLMN ID. The AMF 505 determines to apply specific functionality to act as a serving AMF of the hosting operator network. In one embodiment, the subscriber concealed identifier (SUCI) includes a Home Network Identifier (HNI) and, optionally, a routing indicator, which the AMF 505 uses to identify which is the HPLMN and where the UDM 509 holding the UE credentials is located. The HNI and the selected PLMN ID may identify different networks. If the UE 501 is not yet authenticated, the AMF 505 may perform a primary authentication and authorization procedure.

[0053] In one embodiment, if the AMF 505 selected by the RAN 503 does not support the request NSSAI or does not support functionality for the serving AMF function of the hosting network, the AMF 505 may use an AMF redirection (reassignment) procedure to another AMF 505 that supports the serving AMF function of the hosting network. It is noted that the AMF 505 that supports functionality for the AMF of the hosting network may register this functionality in its profile in the NRF so that other AMFs can discover the AMF 505. Optionally, the AMF 505 that supports functionality for the AMF of the hosting network may configure neighboring AMFs 505 with this information via direct signaling.

[0054] At 2b (see signaling 506), in one embodiment, if the AMF 505 does not have the subscription data for the UE, the AMF 505 selects the UDM 509 of the participating network, and the AMF 505 requests the UE subscription data from the UDM 509. The AMF 505 may use a service operation Nudm_SDM_Get request and include the SUPI. The AMF 505 may obtain the SUPI from the primary authentication and authorization procedure.

[0055] At 2c (see message 508), in one embodiment, the UDM 509 determines, e.g., based on the hosting PLMN ID, that the UE 501 has registered with the hosting network and that indirect network sharing may be used. The UDM 509 sends a response message including the UE subscription data. The UDM 509 may derive a list of subscribed S-NSSAIs and / or subscribed data network names (DNNs) applicable in the case of indirect network sharing and / or in the particular hosting network. The UDM 509 may take into account the SLAs between the participating operators and the hosting operator to derive the subscribed S-NSSAIs and / or DNNs to be sent in the UE subscription data.

[0056] Additionally, the UDM 509 may transmit other subscribed parameter values ​​applicable to the current hosting network, such as a UE-aggregate maximum bit rate (AMBR) lower than the UE-AMBR used in the participating network operators, and / or services excluded from the UE subscribed services provided during indirect network sharing (e.g., multicast-broadcast service (MBS), location service, ProSe service, etc.).

[0057] In step 3 (see block 510), in one embodiment, the AMF 505 applies the following functions specific to the serving AMF 505 of the hosting network: Note that although step 3 only shows the AMF 505, in one embodiment, the AMF 505 can also use NSSF services. In one embodiment, the subscribed S-NSSAI sent in the UE subscription data may differ from the configured NSSAI that the participating operator may have configured for the UE. In such a case, the AMF 505 needs to create the allowed NSSAI and rejected S-NSSAI (either alone or in interaction with the NSSF of the hosting network) based on the list of subscribed S-NSSAIs and the requested NSSAI by the UE 501, but without sending a configuration NSSAI for the hosting network.

[0058] In one embodiment, the AMF 505 does not provide the UE 501 with a configuration NSSAI for the hosting MNO. Even if the UE 501 does not send a request NSSAI, the AMF 505 does not create and provide a configuration NSSAI to the UE 501. However, the AMF 505 provides an authorization NSSAI that has the participating operators' S-NSSAIs. In one embodiment, the AMF 505 uses the subscription S-NSSAI (e.g., received from the UDM 509, or received from the source AMF 505, or stored from a previous registration) to determine the value of the hosting operator's S-NSSAI to be mapped to the subscription S-NSSAI. The AMF 505 further determines which of the hosting operator's S-NSSAIs are available and / or supported in the current TA and potential registration area. The AMF 505 considers the available and / or supported S-NSSAIs of the hosting operator and considers the corresponding S-NSSAIs of the participating operators to be included in the authorized NSSAI for the UE 501 and / or the partially authorized NSSAI for the UE 501. In other words, the AMF 505 includes the S-NSSAI of the participating operator (e.g., intended to be the S-NSSAI value of the HPLMN) in the authorized NSSAI for the UE 501 and / or the partially authorized NSSAI for the UE 501. In such an embodiment, the AMF 505 may create a list of rejected S-NSSAIs of the participating operators to be sent to the UE 501 if some of the UE requested S-NSSAIs are not supported in the hosting network (e.g., there is no available corresponding S-NSSAI of the hosting network). An example of how the authorized NSSAI for the UE and / or the partially authorized NSSAI for the UE are created is shown in step 5.

[0059] In one embodiment, the AMF 505 determines an authorized NSSAI for the hosting network operator that includes the hosting operator's S-NSSAI value that is mapped to the participating operator's S-NSSAI value included in the authorized NSSAI for the UE 501 and / or the partial authorized NSSAI for the UE 501. When the AMF 505 creates the partial authorized NSSAI for the UE 501, the AMF 505 may also create a corresponding partial authorized NSSAI for the hosting network. The authorized NSSAI for the hosting network or the partial authorized NSSAI for the hosting network is stored locally in the AMF 505 and can be similar to the "mapping of authorized NSSAI" information derived in the AMF 505 of the VPLMN in case of roaming. The "Mapping of Authorized NSSAIs" information is derived to be sent to the UE 501 and includes a mapping of each S-NSSAI of the VPLMN to an S-NSSAI of the HPLMN, whereas the Authorized NSSAI for the hosting network (or the Partially Authorized NSSAI for the hosting network) is used only within the hosting network domain. The Authorized NSSAI for the hosting network (or the Partially Authorized NSSAI for the hosting network) may include a list of S-NSSAIs that are valid in the hosting network and correspond to the list of S-NSSAIs included in the Authorized NSSAI for the UE 501 and / or the Partially Authorized NSSAI for the UE 501.

[0060] In other words, the AMF 505 stores in the context of the UE 501 two types of authorization NSSAIs: an authorization NSSAI for the UE 501 and / or a partial authorization NSSAI for the UE 501 that is sent to the UE 501, and an authorization NSSAI for the hosting network that is used in signaling to other NFs of the hosting network and the shared RAN 503.

[0061] In one example of the present disclosure, it is assumed that the shared RAN 503 is configured with network slicing (e.g., NSSAI) information of the hosting network, while the UE 501 is configured with NSSAI information of the participating networks. In one embodiment, the RAN 503 uses the NSSAI information from AS signaling to select the AMF 505 or to apply congestion or overload handling within the RAN, but the NSSAI information provided by the UE 501 is for the participating networks. Thus, in such an embodiment, the AMF 505 configures the UE 501 to not provide NSSAI information in AS signaling. In other words, the AMF 505 configures mode "d" for operator-controlled inclusion of NSSAI in AS signaling, e.g., as described in section 5.15.9 of 3GPP TS 23.501, V18.5.0, 2024-03.

[0062] In one embodiment, the shared RAN 503 may apply NSAGs for cell (re)selection or random access control, for example, as described in section 5.15.14 of 3GPP TS 23.501, V18.5.0, 2024-03. In such an embodiment, the RAN 503 configured the hosting network's AMF 505 with NSAG information. The serving AMF 505 creates and provides an NSAG value corresponding to the Hosting S-NSSAI value that is mapped to the S-NSSAI value of the participating MNO's HPLMN to the UE 501 that supports NSAGs (e.g., the UE 501 indicated support for NSAGs in the 5GMM information element in step 1).

[0063] At 4 (see messaging 512), in one embodiment, the AMF 505 establishes an access and mobility (AM) policy association with the PCF 507. The AMF 505 sends an Establish AM Policy Association Request message to the PCF 507, including the hoster's authorized NSSAI (e.g., not the UE 501's authorized NSSAI) and other parameters such as a subscribed RAT / Frequency Selection Priority (RFSP) or a subscribed UE-AMBR.

[0064] In one embodiment, the PCF 507 uses the authorized NSSAI for the hosting operator to derive the applicable RFSP for the shared RAN 503 based on the hosting operator's slice, but the network slice sent to the UE 501 includes the values ​​of the participating operators' network slices.

[0065] At 5 (see messaging 514), in one embodiment, the AMF 505 creates and sends a NAS registration accept message to the UE 501. The NAS registration accept message is encapsulated in an N2 message to the RAN 503. In one embodiment, the AMF 505 creates the N2 message and includes an authorization NSSAI for the hosting network of the RAN 503. This allows the RAN 503 to apply policies for cell selection and steering according to the S-NSSAI of the hosting network.

[0066] In one embodiment, the NAS registration accept message includes an authorized NSSAI for the UE 501 and / or a partially authorized NSSAI for the UE 501, both of which have the S-NSSAI of the participating network. The AMF 505 may provide a configured NSSAI for the participating operator (i.e., a configured NSSAI that includes the S-NSSAI of the participating operator) if it has been supplied with such information. The NAS registration accept message may also include a list of rejected S-NSSAIs, where the S-NSSAI value is the S-NSSAI of the participating network. Each rejected S-NSSAI is associated with a rejection cause value that indicates the reason for the rejection, for example, rejected in the entire PLMN, rejected in the registration area, or partially rejected for a portion of a TA in the registration area. In certain scenarios of indirect network sharing, the AMF 505 of the hosting network may apply a different logic for the rejection cause, for example, instead of "rejected for the entire PLMN," the AMF 505 may use "rejected in the registration area." In this way, from the UE 501's perspective, the registered PLMN is the participating operator's PLMN, and the UE 501 may leave the shared RAN 503 and move to a participating network's RAN where a Reject S-NSSAI may be available.

[0067] In one example, the UE may have requested to use network slices S-NSSAI#S1, S-NSSAI#S2, and S-NSSAI#S3 (which may be part of the configuration NSSAI for the participating network). The AMF 505 may receive a subscription S-NSSAI indicating S-NSSAI#S1 and S-NSSAI#S2, which means that the AMF 505 may only authorize S-NSSAI#S1 and S-NSSAI#S2 for the UE 501. The AMF 505 may include S-NSSAI#S1 and S-NSSAI#S2 in the authorized NSSAI for the UE 501 and / or the partially authorized NSSAI for the UE 501. The AMF 505 rejects the requested S-NSSAI#S3 with a cause value indicating that the requested S-NSSAI#S3 is not supported in the registration area. Furthermore, the AMF 505 determines the S-NSSAI of the hosting network that corresponds to the S-NSSAI of the participating network included in the authorized NSSAI for the UE 501 and / or the partially authorized NSSAI for the UE 501. For example, the S-NSSAI#S1 corresponds to the S-NSSAI#S11, and the S-NSSAI#S2 corresponds to the S-NSSAI#S12. Thus, the AMF 505 creates an authorized NSSAI for the hosting network operator that includes the S-NSSAI#S11 (corresponding to / mapped to the S-NSSAI#S1) and the S-NSSAI#S12 (corresponding to / mapped to the S-NSSAI#S2).

[0068] In one embodiment, another reason for the serving AMF 505 to reject the request S-NSSAI#S3 may be that there is no corresponding S-NSSAI available in the hosting network that can be mapped to S-NSSAI#S3.

[0069] In one embodiment, in the NAS registration accept message, the AMF 505 may include the NSAG information as described in step 3. The AMF 505 creates the NSAG information using the NSAG identifiers used / configured by the shared RAN 503 and the corresponding S-NSSAI list of the NSAG identifiers, where the S-NSSAI list includes one or more S-NSSAIs with values ​​of the participating networks that are mapped to the S-NSSAI of the hosting network configured in the AMF 505.

[0070] In one embodiment, the NSAG information parameter may be formatted as shown in Table 1, which shows multiple NSAG elements, eg, NSAG 1, NSAG 2, etc.

[0071] [Table 1]

[0072] In one embodiment, each NSAG element may contain the information shown in Table 2. Table 2 shows the NSAG element format in which an NSAG identifier may be associated with one or more S-NSSAIs of a hosting network operator.

[0073] [Table 2]

[0074] In a specific scenario of indirect network sharing, the AMF 505 creates an NSAG element having the value of the NSAG identifier of the hosting network (e.g., as configured from the RAN 503 to the AMF 505), and the S-NSSAI list includes the S-NSSAIs of the participating operators included in the authorized NSSAI for the UE 501 and / or the partial authorized NSSAI for the UE 501 to be sent to the UE 501.

[0075] In this way, the AMF 505 of the hosting network plays two roles - towards the UE 501, the AMF 505 acts as the AMF 505 of the participating network (e.g., HPLMN), and towards the NFs and RAN of the hosting network, the AMF 505 similarly acts as the AMF 505 of the VPLMN.

[0076] 6 illustrates an example signal flow of PDU session establishment for indirect network sharing according to an aspect of the present disclosure. In one embodiment, network slice availability information is provided to the PCF by the UDR. The UDR is configured to maintain and store the network slice availability information per S-NSSAI. For example, the UDR may store the network slice availability information in policy control requirements related to the network slice (e.g., values ​​of the (Remaining) Maximum Slice Data Rate for UL and DL may be stored in the UDR).

[0077] At 1 (see Messaging 602), in one embodiment, UE 601 sends a NAS uplink message including at least the following parameters: S-NSSAI = S-NSSAI of participating NW, DNN, PDU session ID, and / or N1 SM container (PDU session establishment request message).

[0078] At 2 (see block 604), in one embodiment, the AMF 605 discovers the H-SMF 609 of the participating network using the received S-NSSAI of the participating network, and the AMF 605 determines the S-NSSAI of the hosting network that is mapped to the S-NSSAI of the participating network. The AMF 605 inserts the determined (or selected) S-NSSAI of the hosting network into the request message sent to the V-SMF 607 over the N11 interface. The AMF 605 may use the service operation Nsmf_PDUSession_CreateSMContext.

[0079] At 3 (see Messaging 606), the AMF 605 initiates the establishment of a PDU session towards the V-SMF 607 using the service operation Nsmf_PDUSession_CreateSMContext. The AMF 605 sends a request message containing at least the following parameters: PDU session ID, S-NSSIA of the VPLMN = S-NSSAI of the hosting NW, S-NSSAI of the HPLMN = S-NSSAI of the participating NWs, selected DNN, and / or N1 SM container (PDU session establishment request).

[0080] In one embodiment, the AMF 605 includes both network slice values—the S-NSSAI of the hosting network used by the V-SMF 607 (e.g., as the value of the S-NSSAI of the VPLMN) and the S-NSSAI of the participating network used by the H-SMF 609 (e.g., as the value of the S-NSSAI of the HPLMN).

[0081] At 4 (see Messaging 608), in one embodiment, the V-SMF 607 processes the request to select a UPF in the hosting network for the PDU session and further forwards the PDU session request to the H-SMF 609. The V-SMF 607 uses the Nsmf_PDUSession_CreateSMContext service operation and includes at least the following parameters in the request message: PDU session ID, S-NSSAI of the HPLMN = S-NSSAI of the participating NW, selected DNN, and / or N1 SM container (PDU session establishment request).

[0082] At 5 (see block 610), the H-SMF 609 retrieves SM subscription data for the UE 601 and for the S-NSSAI and DNN combination of the participating networks. The H-SMF 609 performs SM policy establishment with the H-PCF. The H-SMF 609 selects a UPF and performs user plane resource configuration with the selected UPF of the participating networks.

[0083] At 6 (see Messaging 612), in one embodiment, the H-SMF 609 sends a response message to the V-SFM 607 using the Nsmf_PDUSession_CreateSMContext service operation. The response message includes an N1 SM container to be sent to the UE 601.

[0084] At step 7 (see Messaging 614), in one embodiment, the V-SMF 607 creates an N2 SM information container and updates the configuration of the UPF of the hosting network. The V-SMF 607 uses the Namf_Communication_N1N2MessageTransfer service operation to the AMF 605 to send a request message to send the N2 SM information to the RAN 603 and to send the N1 SM container to the UE 601. In one embodiment, the N2 SM information includes at least the following parameters: a PDU Session ID, CN Tunnel Info for the N3 tunnel, one or more quality of service (QoS) profiles and corresponding QoS flow identifiers (QFIs), and / or H = the S-NSSAI of the hosting network. In one embodiment, the S-NSSAI of the hosting network is the S-NSSAI received in step 3 as the S-NSSAI of the hosting network used by the V-SMF 607 (e.g., as the value of the S-NSSAI of the VPLMN).

[0085] At 8 (see Messaging 616), in one embodiment, the AMF 605 sends an N2 Downlink message to the RAN 603, including an N2 SM Information message and an N1 SM container to be sent to the UE 601. In one embodiment, the N1 SM container sent from the RAN 603 to the UE 601 includes a PDU Session Establishment Accept message that includes at least the PDU Session ID, the S-NSSAI of the participating network to be used by the H-SMF 609 (e.g., as the value of the S-NSSAI of the HPLMN), one or more QoS rules, etc.

[0086] In this way, the PDU session is established as a home routed PDU session to the participating network, but from the UE's perspective, it is a PDU session in the non-roaming case (e.g., as if the UE were establishing a PDU session to the HPLMN).

[0087] 7 illustrates an example of a UE 700 according to aspects of the present disclosure. The UE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations or components thereof, may be examples of means for performing various aspects of the present disclosure described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0088] The processor 702, memory 704, controller 706, or transceiver 708, or various combinations or components thereof, may be implemented in hardware (e.g., circuitry), which may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device configured as or otherwise supporting means for performing the functions described in this disclosure, or any combination thereof.

[0089] The processor 702 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the UE 700 to perform various functions of the present disclosure.

[0090] The memory 704 may include volatile or nonvolatile memory. The memory 704 may store computer-readable and computer-executable code, including instructions that, when executed by the processor 702, cause the UE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as the memory 704 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0091] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the UE 700 to perform one or more of the functions described herein (e.g., by the processor 702 executing instructions stored in the memory 704). For example, the processor 702 may support wireless communication in the UE 700 in accordance with examples disclosed herein.

[0092] The controller 706 may manage input and output signals for the UE 700. The controller 706 may also manage peripheral devices not integrated into the UE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.

[0093] In some implementations, the UE 700 may include at least one transceiver 708. In some other implementations, the UE 700 may have two or more transceivers 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

[0094] The receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 710 may include one or more antennas for receiving signals over the air or wireless medium. The receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 710 may include at least one demodulator configured to demodulate the received signal by reversing the modulation technique applied during transmission of the signal to obtain transmitted data. The receiver chain 710 may include at least one decoder for decoding and processing the demodulated signal to receive transmitted data.

[0095] The transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or a digital modulation scheme such as phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 712 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 712 may also include one or more antennas for transmitting the amplified signal over the air or wireless medium.

[0096] FIG. 8 illustrates an example processor 800 according to aspects of the present disclosure. The processor 800 may be an example of a processor configured to perform various operations in accordance with examples described herein. The processor may include a controller 802 configured to perform various operations in accordance with examples described herein. The processor 800 may optionally include at least one memory 804, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, the processor 800 may optionally include one or more arithmetic-logic units (ALUs) 806. One or more of these components may electronically communicate or otherwise be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0097] Processor 800 may be a processor chipset and may include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, obtain, retrieve, send, output, transfer, store, determine, identify, access, write, read) in accordance with examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., processor 800)), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), etc.).

[0098] Controller 802 may be configured to manage and coordinate various operations of processor 800 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, transferring, storing, determining, identifying, accessing, writing, reading) to cause processor 800 to support various operations in accordance with examples described herein. For example, controller 802 may act as a control unit for processor 800, generating control signals that manage the operation of various components of processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0099] Controller 802 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from memory 804 and determine subsequent instructions to be executed to cause processor 800 to support various operations in accordance with examples described herein. Controller 802 may be configured to track memory addresses of instructions associated with memory 804. Controller 802 may be configured to decode instructions to determine operations to be performed and associated operands. For example, controller 802 may be configured to interpret instructions and determine control signals to be output to other components of processor 800 to cause processor 800 to support various operations in accordance with examples described herein. Additionally or alternatively, controller 802 may be configured to manage the flow of data within processor 800. Controller 802 may be configured to control the transfer of data between registers, an arithmetic logic unit (ALU), and other functional units of processor 800.

[0100] Memory 804 may include one or more caches (e.g., memory local to or included with processor 800) or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 804 may reside within or on a processor chipset (e.g., local to processor 800). In some other implementations, memory 804 may reside outside of the processor chipset (e.g., remote from processor 800).

[0101] The memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 800, cause the processor 800 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. The controller 802 and / or the processor 800 may be configured to execute the computer-readable instructions stored in the memory 804 to cause the processor 800 to perform various functions. For example, the processor 800 and / or the controller 802 may be coupled to or to the memory 804, and the processor 800, the controller 802, and the memory 804 may be configured to perform various functions described herein. In some examples, the processor 800 may include multiple processors, and the memory 804 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured, individually or collectively, to perform various functions herein.

[0102] The one or more ALUs 806 may be configured to support various operations according to the examples described herein. In some implementations, the one or more ALUs 806 may reside within or on a processor chipset (e.g., processor 800). In some other implementations, the one or more ALUs 806 may reside external to the processor chipset (e.g., processor 800). The one or more ALUs 806 may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, the one or more ALUs 806 may receive input operands and an operation code that determines the operation to be performed. The one or more ALUs 806 may be comprised of various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, for processing and manipulating data through operations. Additionally or alternatively, one or more ALUs 806 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), which allows one or more ALUs 806 to handle conditional operations, comparisons, and bit operations.

[0103] The processor 800 may support wireless communication according to examples disclosed herein. In an embodiment, the processor 800 may be configured or operable to support means for receiving a first message for registering a UE with a participating network associated with a hosting network; transmitting a second message including assistance information based at least in part on the received first message, wherein the assistance information includes an authorized NSSAI for the UE or a partial authorized NSSAI for the UE, or both, and wherein each of the authorized NSSAI or partial authorized NSSAI, or both, is associated with a corresponding authorized NSSAI or corresponding partial authorized NSSAI associated with the hosting network; and transmitting a third message to a second network entity of the hosting network, wherein the third message includes the authorized NSSAI or partial authorized NSSAI, or both, associated with the hosting network corresponding to the authorized NSSAI or partial authorized NSSAI for the UE, or both.

[0104] In one embodiment, the network entity includes an AMF, and the second network entity includes one or more of a base station, a PCF, a unified data management, or a unified data repository.

[0105] In one embodiment, the corresponding authorized NSSAI or the corresponding partial authorized NSSAI associated with the hosting network includes a single NSSAI (S-NSSAI) associated with the hosting network and is mapped to at least one S-NSSAI associated with the participating network, and the authorized NSSAI for the UE includes at least one S-NSSAI associated with the participating network.

[0106] In an embodiment, the processor 800 may be configured to support means for determining whether the network entity supports functionality based at least in part on the hosting network, the functionality including providing a service to the UE.

[0107] In an embodiment, the processor 800 may be configured to support means for determining whether to provide the UE with a configuration NSSAI related to the hosting network or determining NSAG information for the UE, the NSAG information including a mapping of NSAG identifiers for the hosting network to respective NSSAIs for participating networks.

[0108] In one embodiment, the NSAG identifier corresponds to a single NSSAI (S-NSSAI) for the hosting network, and the S-NSSAI is mapped to respective S-NSSAIs for the participating networks.

[0109] In an embodiment, the processor 800 may be configured to support means for outputting a configuration for the UE to exclude the NSSAI in the AS signaling.

[0110] In an embodiment, the processor 800 may be configured to support means for refraining from outputting a configuration NSSAI for the hosting network to the UE based at least in part on the first message excluding the NSSAI.

[0111] In an embodiment, the processor 800 may be configured to support means for rejecting a requested single NSSAI (S-NSSAI) associated with the participating network in response to non-support in the hosting network of the S-NSSAI.

[0112] In an embodiment, the processor 800 may be configured to support means for rejecting the request S-NSSAI in response to an inability to map the request S-NSSAI to a corresponding S-NSSAI associated with the hosting network.

[0113] In one embodiment, during the PDU session establishment procedure, the NE 900 may be configured to support means for determining the S-NSSAI of the hosting network that is mapped to the S-NSSAI of the participating network and including the determined S-NSSAI of the hosting network in a message to the SMF of the hosting network.

[0114] In one embodiment, the first message comprises a registration request message and the second message comprises a registration acceptance message.

[0115] 9 illustrates an example of a NE 900 according to an aspect of the disclosure. The NE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations or components thereof, may be examples of means for performing various aspects of the disclosure described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0116] The processor 902, memory 904, controller 906, or transceiver 908, or various combinations or components thereof, may be implemented in hardware (e.g., circuitry), which may include a processor, digital signal processor (DSP), application specific integrated circuit (ASIC), or other programmable logic device configured as or otherwise supporting means for performing the functions described in this disclosure, or any combination thereof.

[0117] The NE 900 may be configured to support means for determining an NES mode of the NE, where the NES mode includes a DU-specific mode or an RU-specific mode of a distributed architecture; determining an NES class and an NES configuration of a traffic flow associated with the NE based on the NES mode, where the NES class is related to the QoS class of the traffic flow; mapping the traffic flow to a DU, RU, or a combination thereof based on the NES class associated with the traffic flow, and transmitting the NES configuration to the DU, RU, or combination thereof mapped to the traffic flow.

[0118] In one embodiment, the NE 900 may be configured to support means for receiving a first message for registering the UE in a participating network associated with a hosting network; transmitting a second message including assistance information based at least in part on the received first message, wherein the assistance information includes an authorized NSSAI for the UE or a partial authorized NSSAI for the UE, or both, and wherein each of the authorized NSSAIs or partial authorized NSSAIs, or both, is associated with a corresponding authorized NSSAI or corresponding partial authorized NSSAI associated with the hosting network; and transmitting a third message to a second network entity of the hosting network, wherein the third message includes an authorized NSSAI or partial authorized NSSAI associated with the hosting network, or both, corresponding to the authorized NSSAI or partial authorized NSSAI for the UE, or both.

[0119] In one embodiment, the network entity includes an AMF, and the second network entity includes one or more of a base station, a PCF, a unified data management, or a unified data repository.

[0120] In one embodiment, the corresponding authorized NSSAI or the corresponding partial authorized NSSAI associated with the hosting network includes a single NSSAI (S-NSSAI) associated with the hosting network and is mapped to at least one S-NSSAI associated with the participating network, and the authorized NSSAI for the UE includes at least one S-NSSAI associated with the participating network.

[0121] In one embodiment, the NE 900 may be configured to support means for determining whether the network entity supports functionality based at least in part on the hosting network, the functionality including providing a service to the UE.

[0122] In one embodiment, the NE 900 may be configured to support means for determining whether to provide a configuration NSSAI related to the hosting network to the UE or determining NSAG information for the UE, where the NSAG information includes a mapping of NSAG identifiers for the hosting network to respective NSSAIs for participating networks.

[0123] In one embodiment, the NSAG identifier corresponds to a single NSSAI (S-NSSAI) for the hosting network, and the S-NSSAI is mapped to respective S-NSSAIs for the participating networks.

[0124] In one embodiment, the NE 900 may be configured to support means for outputting a configuration for the UE to exclude the NSSAI in the AS signaling.

[0125] In one embodiment, the NE 900 may be configured to support means for refraining from outputting a configuration NSSAI for the hosting network to the UE based at least in part on the first message excluding the NSSAI.

[0126] In one embodiment, the NE 900 may be configured to support means for rejecting a requested single NSSAI (S-NSSAI) associated with a participating network in response to non-support in the hosting network of the S-NSSAI.

[0127] In one embodiment, the NE 900 may be configured to support means for rejecting the request S-NSSAI in response to an inability to map the request S-NSSAI to a corresponding S-NSSAI associated with the hosting network.

[0128] In one embodiment, during the PDU session establishment procedure, the NE 900 may be configured to support means for determining the S-NSSAI of the hosting network that is mapped to the S-NSSAI of the participating network and including the determined S-NSSAI of the hosting network in a message to the SMF of the hosting network.

[0129] In one embodiment, the first message comprises a registration request message and the second message comprises a registration acceptance message.

[0130] The processor 902 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 902 may be configured to operate the memory 904. In some other implementations, the memory 904 may be integrated into the processor 902. The processor 902 may be configured to execute computer-readable instructions stored in the memory 904 to cause the NE 900 to perform various functions of the present disclosure.

[0131] The memory 904 may include volatile or nonvolatile memory. The memory 904 may store computer-readable and computer-executable code, including instructions that, when executed by the processor 902, cause the NE 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as the memory 904 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0132] In some implementations, the processor 902 and the memory 904 coupled to the processor 902 may be configured to cause the NE 900 to perform one or more of the functions described herein (e.g., by the processor 902 executing instructions stored in the memory 904). For example, the processor 902 may support wireless communication in the NE 900 in accordance with examples disclosed herein.

[0133] The controller 906 may manage input and output signals for the NE 900. The controller 906 may also manage peripheral devices not integrated into the NE 900. In some implementations, the controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 906 may be implemented as part of the processor 902.

[0134] In some implementations, the NE 900 may include at least one transceiver 908. In some other implementations, the NE 900 may have two or more transceivers 908. The transceiver 908 may represent a wireless transceiver. The transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.

[0135] The receiver chain 910 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 910 may include one or more antennas for receiving signals over the air or wireless medium. The receiver chain 910 may include at least one amplifier (e.g., a low noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 910 may include at least one demodulator configured to demodulate the received signal by reversing the modulation technique applied during transmission of the signal to obtain transmitted data. The receiver chain 910 may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0136] The transmitter chain 912 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 912 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or a digital modulation scheme like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 912 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 912 may also include one or more antennas for transmitting the amplified signal over the air or wireless medium.

[0137] 10 illustrates a flow diagram of a method according to an aspect of the present disclosure. The operations of the method may be performed by an NE as described herein. In some implementations, the NE may execute a set of instructions to control functional elements of the NE to perform the described functions.

[0138] At 1002, the method may receive a first message for registering a UE with a participating network associated with a hosting network. The operations of 1002 may be performed according to examples described herein. In some implementations, aspects of the operations of 1002 may be performed by an NE as described with reference to FIG. 9.

[0139] At 1004, the method may transmit a second message including assistance information based at least in part on the received first message, the assistance information including an authorized NSSAI for the UE or a partial authorized NSSAI for the UE, or both, wherein each of the authorized NSSAIs or partial authorized NSSAIs, or both, is associated with a corresponding authorized NSSAI or corresponding partial authorized NSSAI related to the hosting network. The operation of 1004 may be performed according to examples described herein. In some implementations, aspects of the operation of 1004 may be performed by an NE as described with reference to FIG. 9.

[0140] At 1006, the method may send a third message to a second network entity of the hosting network, the third message including an authorized NSSAI or partial authorized NSSAI, or both, associated with the hosting network corresponding to the authorized NSSAI or partial authorized NSSAI, or both, for the UE. The operations of 1006 may be performed according to examples described herein. In some implementations, aspects of the operations of 1006 may be performed by an NE as described with reference to FIG. 9.

[0141] It should be noted that the methods described herein describe possible implementations, and that the acts and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0142] The description herein is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. [Explanation of symbols]

[0143] 100 Wireless Communication System 102 NE 104UE 106CN 112 Geographic Coverage Area 114 Communication Links 202a~c Network operators 204 Wireless Access Network 302a~c Participating businesses 304 Hosting Provider 306 RAN and 5GC 401 VPLMN 402UE 403 HPLMN 404 (servings) AMF 406 UDM 408 SMF, V-SMF 410 SMF, H-SMF 412 UPF 414 H-PCF 416 Anchor UPF 501 UE 503 RAN 505 AMF 509 UDM 601UE 605 AMF 607 V-SMF 609 H-SMF 700 UE 702 processor 704 memory 706 Controller 708 Transceiver 710 Receiver Chain 712 Transmitter Chain 800 processors 802 Controller 804 memory 806 ALU 900 NE 902 processor 904 memory 906 Controller 908 Transceiver 910 Receiver Chain 912 Transmitter Chain

Claims

1. At least one memory; a network entity coupled to the at least one memory, receiving a first message for registering a user equipment (UE) with a participating network associated with a hosting network; transmitting a second message including assistance information based at least in part on the received first message, the assistance information including an authorized network slice selection assistance information (NSSAI) for the UE or a partial authorized NSSAI for the UE, or both the authorized NSSAI for the UE and the partial authorized NSSAI for the UE, wherein each of the authorized NSSAI or the partial authorized NSSAI, or both the authorized NSSAI and the partial authorized NSSAI, is associated with a corresponding authorized NSSAI or corresponding partial authorized NSSAI related to the hosting network; sending a third message to a second network entity of the hosting network, the third message including the authorization NSSAI or the partial authorization NSSAI for the UE, or an authorization NSSAI or partial authorization NSSAI related to the hosting network corresponding to both the authorization NSSAI and the partial authorization NSSAI for the UE, or both the authorization NSSAI and the partial authorization NSSAI related to the hosting network; at least one processor configured to cause A network entity, including

2. 2. The network entity of claim 1, wherein the network entity includes an Access and Mobility Management Function (AMF), and the second network entity includes one or more of a base station, a Policy Control Function (PCF), a unified data management, or a unified data repository.

3. the corresponding authorized NSSAI or the corresponding partial authorized NSSAI associated with the hosting network comprises a single NSSAI (S-NSSAI) associated with the hosting network and is mapped to at least one S-NSSAI associated with the participating network; The network entity of claim 1 , wherein the authorized NSSAI for the UE includes the at least one S-NSSAI associated with the participating network.

4. The at least one processor may cause the network entity to: determining whether the network entity supports functionality based at least in part on the hosting network, the functionality including providing a service to the UE; The network entity of claim 1 , configured to:

5. The at least one processor may cause the network entity to: determining whether to provide the UE with a configuration NSSAI associated with the hosting network; or determining Network Slice Access Stratum Group (NSAG) information for the UE, the NSAG information including a mapping of NSAG identifiers for the hosting network to respective NSSAIs for the participating networks; The network entity of claim 4, configured to:

6. 6. The network entity of claim 5, wherein the NSAG identifier corresponds to a single NSSAI (S-NSSAI) for the hosting network, and the S-NSSAI is mapped to respective S-NSSAIs for the participating networks.

7. The at least one processor may cause the network entity to:

2. The network entity of claim 1, configured to output a configuration for the UE to exclude an NSSAI in access stratum (AS) signaling.

8. The at least one processor may cause the network entity to:

10. The network entity of claim 1, configured to refrain from outputting a configuration NSSAI for the hosting network to the UE based at least in part on the first message excluding an NSSAI.

9. The at least one processor may cause the network entity to:

2. The network entity of claim 1, configured to cause a Requested Single NSSAI (S-NSSAI) associated with the participating network to be rejected in response to non-support in the hosting network of the Requested S-NSSAI.

10. The at least one processor may cause the network entity to:

10. The network entity of claim 9, configured to cause the request S-NSSAI to be rejected in response to an inability to map the request S-NSSAI to a corresponding S-NSSAI associated with the hosting network.

11. During a protocol data unit (PDU) session establishment procedure, the at least one processor may send to the network entity: determining a single NSSAI (S-NSSAI) of the hosting network that maps to an S-NSSAI of the participating network; including the determined S-NSSAI of the hosting network in a message to a Session Management Function (SMF) of the hosting network; The network entity of claim 1 , configured to:

12. 2. The network entity of claim 1, wherein the first message comprises a registration request message and the second message comprises a registration accept message.

13. 1. A processor for wireless communications, comprising: coupled to at least one memory, and configured to: receiving a first message for registering a user equipment (UE) with a participating network associated with a hosting network; transmitting a second message including assistance information based at least in part on the received first message, the assistance information including an authorized network slice selection assistance information (NSSAI) for the UE or a partial authorized NSSAI for the UE, or both the authorized NSSAI for the UE and the partial authorized NSSAI for the UE, wherein each of the authorized NSSAI or the partial authorized NSSAI, or both the authorized NSSAI and the partial authorized NSSAI, is associated with a corresponding authorized NSSAI or corresponding partial authorized NSSAI related to the hosting network; sending a third message to a second network entity of the hosting network, the third message including the authorization NSSAI or the partial authorization NSSAI for the UE, or an authorization NSSAI or partial authorization NSSAI related to the hosting network corresponding to both the authorization NSSAI and the partial authorization NSSAI for the UE, or both the authorization NSSAI and the partial authorization NSSAI related to the hosting network; a processor including at least one controller configured to:

14. 14. The processor of claim 13, wherein the network entity includes an Access and Mobility Management Function (AMF), and the second network entity includes one or more of a base station, a Policy Control Function (PCF), a unified data management, or a unified data repository.

15. the corresponding authorized NSSAI or the corresponding partial authorized NSSAI associated with the hosting network comprises a single NSSAI (S-NSSAI) associated with the hosting network and is mapped to at least one S-NSSAI associated with the participating network; 14. The processor of claim 13, wherein the authorized NSSAI for the UE includes the at least one S-NSSAI associated with the participating network.

16. The at least one controller may cause the processor to: determining whether a network entity supports functionality based at least in part on the hosting network, the functionality including providing a service to the UE; The processor of claim 13 configured to:

17. The at least one controller may cause the processor to: determining whether to provide the UE with a configuration NSSAI associated with the hosting network; or determining Network Slice Access Stratum Group (NSAG) information for the UE, the NSAG information including a mapping of NSAG identifiers for the hosting network to respective NSSAIs for the participating networks; 17. The processor of claim 16, configured to:

18. 18. The processor of claim 17, wherein the NSAG identifier corresponds to a single NSSAI (S-NSSAI) for the hosting network, and the S-NSSAI is mapped to respective S-NSSAIs for the participating networks.

19. The at least one controller may cause the processor to:

14. The processor of claim 13, configured to output a configuration for the UE to exclude an NSSAI in access stratum (AS) signaling.

20. 1. A method performed by a network entity, comprising: receiving a first message for registering a user equipment (UE) with a participating network associated with a hosting network; transmitting a second message including assistance information based at least in part on the received first message, wherein the assistance information includes an authorized network slice selection assistance information (NSSAI) for the UE or a partial authorized NSSAI for the UE, or both the authorized NSSAI for the UE and the partial authorized NSSAI for the UE, and each of the authorized NSSAI or the partial authorized NSSAI, or both the authorized NSSAI and the partial authorized NSSAI, is associated with a corresponding authorized NSSAI or corresponding partial authorized NSSAI related to the hosting network; sending a third message to a second network entity of the hosting network, the third message including the authorization NSSAI or the partial authorization NSSAI for the UE, or an authorization NSSAI or partial authorization NSSAI related to the hosting network corresponding to both the authorization NSSAI and the partial authorization NSSAI for the UE, or both the authorization NSSAI and the partial authorization NSSAI related to the hosting network; A method comprising:

Images