Techniques for indirect network sharing

Abstract

Aspects of the present disclosure relate to techniques for indirect network sharing. An apparatus is configured to: receive a first message for registering a UE with a participating network associated with a hosted network; transmitting a second message comprising assistance information based at least in part on the received first message, where the assistance information comprises an allowed NSSAI for the UE, or a partially allowed NSSAI for the UE, or both, and where each of the allowed NSSAI or the partially allowed NSSAI or both is associated with a corresponding allowed NSSAI or a corresponding partially allowed NSSAI associated with the hosted network; and sending a third message to a second network entity of the hosted network, the third message including a permitted NSSAI, or a partially permitted NSSAI, or both associated with the hosted network, corresponding to the permitted NSSAI, or the partially permitted NSSAI, or both for the UE.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to wireless communication, and more particularly to techniques for indirect network sharing. BACKGROUND

[0002] A wireless communication system can include one or more network communication devices, such as a base station (BS), that can support wireless communication for one or more user communication devices, which can also be referred to as user equipment (UE) or other suitable terminology. A wireless communication system can support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system, e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.). Moreover, a wireless communication system can support wireless communication across various radio access technologies, including third generation (3G) radio access technologies, fourth generation (4G) radio access technologies, fifth generation (5G) radio access technologies, and other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)). SUMMARY

[0003] The article “a” preceding an element does not, without the context of further limitations, and should not be interpreted to exclude other elements of a similar or different nature. The terms “a,” “at least one,” “one or more,” and “at least one of” can be used interchangeably. As used herein, including in the claims “or” as used in a list of items (for example, a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, 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” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” can be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.” Moreover, as used herein, including in the claims “set” can include one or more elements.

[0004] In one embodiment, an apparatus can be configured to receive a first message for registering a UE with a participating network associated with a hosting network; transmit a second message including assistance information based at least in part on the received first message, wherein the assistance information includes an allowed network slice selection assistance information (NSSAI) for the UE, or a partial allowed NSSAI for the UE, or both, and wherein each of the allowed NSSAI or the partial allowed NSSAI or both is associated with a corresponding allowed NSSAI or a corresponding partial allowed NSSAI associated with the hosting network; and transmit a third message to a second network entity of the hosting network including an allowed NSSAI or a partial allowed NSSAI or both associated with the hosting network corresponding to the allowed NSSAI or the partial allowed NSSAI or both for the UE. BRIEF DESCRIPTION OF DRAWINGS

[0005] Figure 1 FIG. illustrates an example of a wireless communication system, in accordance with aspects of the present disclosure.

[0006] Figure 2 FIG. illustrates an example architecture of a 5G multi-operator core network (5G MOCN) sharing the same next generation radio access network (NG-RAN), in accordance with aspects of the present disclosure.

[0007] Figure 3 FIG. illustrates an example architecture of inter-5G network sharing, in accordance with aspects of the present disclosure.

[0008] Figure 4 FIG. illustrates an example of a 5G system roaming architecture for a home routing scenario in a service-based interface representation, in accordance with aspects of the present disclosure.

[0009] Figure 5 FIG. illustrates an example signal flow of a registration procedure of a UE with a hosting network operator in case of indirect network sharing, in accordance with aspects of the present disclosure.

[0010] Figure 6 FIG. illustrates an example signal flow of a protocol data unit (PDU) session establishment for indirect network sharing, in accordance with aspects of the present disclosure.

[0011] Figure 7 FIG. illustrates an example of a UE, in accordance with aspects of the present disclosure.

[0012] Figure 8 FIG. illustrates an example of a processor, in accordance with aspects of the present disclosure.

[0013] Figure 9 FIG. illustrates an example of a network equipment (NE), in accordance with aspects of the present disclosure.

[0014] Figure 10FIGURE illustrates a flow diagram of a method performed by a device, in accordance with aspects of the present disclosure. DETAILED DESCRIPTION

[0015] Wireless communication systems, such as 5G network systems, can implement network slicing. The concept of network slicing enables a network operator to divide a network in finer complete network granularity (“slice”) the network, referred to as a network slice, to provide customized network connectivity (or network features) to customers or application service providers.

[0016] A network slice is a logical network that includes a set of network functions and corresponding resources (e.g., compute, storage, networking) needed to provide certain network capabilities and network characteristics. A network slice can include core network (e.g., 5G core network 5GC) control plane and user plane network functions (NFs), as well as access network (e.g., 5G radio access network or fixed access network).

[0017] A UE can be configured with network slice related information, referred to as NSSAI. The NSSAI can include one or more single NSSAI (S-NSSAI).

[0018] A UE requests registration for a network slice by sending a NAS registration request message to a 5GC (e.g., access and mobility management function (AMF)), which includes a requested NSSAI containing a list of one or more S-NSSAIs that the UE wants to register for. The 5GC (e.g., AMF) can send one or more of the following elements related to the UE’s network slice configuration to the UE in a registration accept message or a UE configuration update command message: 1) allowed NSSAI, 2) optionally, in case of roaming, mapping of allowed NSSAI to home public land mobile network (HPLMN) S-NSSAI values, 3) configured NSSAI; 4) optionally, in case of roaming, mapping of configured NSSAI to HPLMN S-NSSAI values, 5) rejected NSSAI; or 6) pending NSSAI. The NSSAI can include a list of one or more S-NSSAIs.

[0019] One aspect of network slice configuration for a UE is that a service operator (e.g., a visited PLMN (VPLMN)) can control which NSSAI the UE includes in the access stratum (AS) by access type when a connection is established in response to a service request for updating UE capabilities, periodic registration update, or a registration procedure. In addition, the HPLMN and VPLMN can also indicate that the UE does not include NSSAI in the AS regardless of the procedure that caused the radio resource control (RRC) connection to be established, e.g., to enable privacy for NSSAI. The AMF sends an access stratum connection establishment NSSAI inclusion mode parameter to the UE that indicates whether and when the UE includes NSSAI information in AS connection establishment (e.g., RRC connection establishment defined in TS 38.331 (incorporated by reference herein)) according to one of these modes:

[0020] Mode a: The UE includes NSSAI set to allowed NSSAI (if available) in AS connection establishment caused by a service request for updating UE capabilities, periodic registration update, or a registration procedure.

[0021] Mode b: The UE includes NSSAI, for the case of AS connection establishment caused by a service request, the NSSAI includes the NSSAI comprising the S-NSSAI(s) of the network slice(s) that triggered the AS connection establishment (e.g., the S-NSSAI with a PDU session reactivated by the service request of the control plane interaction related to the network slice that triggered the service request). For example, for session management (SM), the SM message will be associated with the S-NSSAI of the PDU session.

[0022] In addition, for mode b, the UE includes NSSAI, for the case of AS connection establishment caused by a periodic registration update or a registration procedure for updating UE capabilities, the NSSAI includes the NSSAI set to allowed NSSAI.

[0023] Mode c: The UE does not include NSSAI in AS connection establishment caused by a service request for updating UE capabilities, periodic registration update, or a registration procedure.

[0024] Mode d: The UE does not provide NSSAI in the AS, e.g., does not include NSSAI, avoids sending NSSAI, etc.

[0025] More information on network slices and 5GS can be found in 3GPP TS 23.501 V18.5.0 2024-03 (incorporated by reference herein) and 3GPP TS 23.502 V18.5.0 2024-03 (incorporated by reference herein).

[0026] In certain embodiments, indirect network sharing is based on roaming architecture. In other words, the hosting network acts as a VPLMN and the participating network acts as a HPLMN. Traffic of the UE is forwarded to the participating network using the home routed PDU session(s). However, network slice configuration for roaming networks is not configured for this application, as the UE acts in the role of connecting and registering to the home network, although the hosting network behaves like a VPLMN. Therefore, the network slice framework currently supporting roaming cannot be applied as-is, and the VPLMN behavior needs to be enhanced.

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

[0028] Figure 1 An example of a wireless communication system 100 is illustrated in accordance with aspects of the present disclosure. The wireless communication system 100 can include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 can support various radio access technologies. In some implementations, the wireless communication system 100 can be a 4G network, such as an LTE network or a LTE-Advanced (LTE-A) network. In some other implementations, the radio communication system 100 can be a NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G-Ultra Wideband (5G-UWB) network. In other implementations, the wireless communication system 100 can be a combination of 4G networks 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), IEEE 802.20. The wireless communication system 100 can support radio access technologies beyond 5G (e.g., 6G). Additionally, the wireless communication system 100 can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

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

[0030] NE 102 can provide a geographic coverage area, and NE 102 can support services for one or more UEs 104 within that geographic coverage area. For example, NE 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, NE 102 can be mobile, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas can be associated with different NEs 102.

[0031] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable term. In some implementations, among other examples, UE 104 may be referred to as a unit, station, terminal, or client. Additionally or alternatively, UE 104 may also be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, etc.

[0032] UE 104 may be able to wirelessly communicate directly with other UE 104 via a communication link. For example, UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0033] NE 102 can support communication with CN 106 or with another NE 102, or both. For example, NE 102 can interface with other NE 102 or CN 106 via one or more backhaul links (e.g., S1, N2, N2, or network interfaces). In some implementations, NE 102 can communicate directly with each other. In some other implementations, NE 102 can communicate with each other or indirectly (e.g., via CN 106). In some implementations, one or more NE 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). The ANC can communicate with one or more UE 104s via one or more other access network transport entities (which may be referred to as radio headends, smart radio headends, or transmit / receive points (TRPs)).

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

[0035] The CN 106 can communicate with the packet data network using one or more backhaul links (e.g., via SI, N2, N3, or another network interface). The packet data network can include application servers. In some implementations, the one or more UEs 104 can communicate with the application servers via the CN 106. The UEs 104 can establish a session (e.g., a PDU session, etc.) with the CN 106 via the NE 102. The CN 106 can route traffic (e.g., control information, data, etc.) between the UEs 104 and the application servers using the established session (e.g., the established PDU session). The PDU session can 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).

[0036] In the wireless communication system 100, the NEs 102 and the UEs 104 can use resources (e.g., time resources or frequency resources) of the wireless communication system 100 to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 can support different resource structures. For example, the NEs 102 and the UEs 104 can support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the NEs 102 and the UEs 104 can support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 can support various frame structures based on one or more numerologies.

[0037] One or more numerologies can be supported in the wireless communications system 100, and the numerologies can include subcarrier spacing and cyclic prefix. A first numerology (e.g., m=0) can be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., m=0) associated with the first subcarrier spacing (e.g., 15 kHz) can utilize one slot per subframe. A second numerology (e.g., m=l) can be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., m=2) can 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., m=3) can be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., m=4) can be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0038] Intervals of resources (e.g., communication resources) can be organized as frames, which can also be referred to as radio frames. Each frame can have a duration of, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration of, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

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

[0040] In the wireless communications system 100, the electromagnetic (EM) spectrum can be split into various classes, bands, frequency channels, and / or the like based on frequency or wavelength. For example, the wireless communications system 100 can support one or more operating bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 can perform wireless communication on one or more of the operating bands. In some implementations, the NEs 102 and the UEs 104 can use FR1 in addition to devices or apparatuses used for cellular communications traffic (e.g., control information, data). In some implementations, the NEs 102 and the UEs 104 can use FR2 in addition to devices or apparatuses used for short range, high data rate capabilities.

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

[0042] Figure 2 An example architecture of a 5G MOCN sharing the same NG-RAN is illustrated, in accordance with aspects of the present disclosure. In one embodiment, the 5GS allows sharing of resources or functions between different network operators 202a-c. The 5GS specifies 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 allocation scheme. In one embodiment, the shared network includes a radio access network 204. Figure 2 An example is shown in which the CNs (e.g., 5GCs) of Operator A 202a, Operator B 202b, and Operator C 202c share RAN resources. This is referred to as a 5G MOCN network sharing architecture in which each core network (CN) of a participating operator is directly connected to the shared RAN.

[0043] Figure 3 An example architecture of inter-5G indirect network sharing is illustrated, in accordance with aspects of the present disclosure. In one embodiment, indirect network sharing deployments between a hosting operator 304 (e.g., a shared network operator) and one or more participating operators 302a-c can be supported. This is illustrated as Figure 3 is shown in which a hosting operator “H” 304 shares its RAN and 5GC 306 to participating operators “L” 302a, “M” 302b, and “N” 302c. Communication between the shared RAN 306 and the core networks of participating operators “L” 302a, “M” 302b, and “N” 302c is routed through the core network of the hosting operator “H” 304 connected to the shared RAN 306.

[0044] 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. The serving AMF (e.g., an AMF in the core network representing the PLMN of the hosting operator 304) supports multiple PLMN IDs.

[0045] UEs from participating operators 302a-c can select a PLMN ID representing the participating operators 302a-c in the shared RAN 306 area based on existing procedures. The serving AMF selects core network functions in the PLMN of the participating operator for the UE based on home routing roaming architecture principles, see e.g. 3GPP TS 23.501 V18.5.0 2024-03. In addition, the serving AMF can consider UE location information to select a session management function (SMF) of the participating operators 302a-c and select a V-SMF in its own network during a PDU session establishment procedure.

[0046] Figure 4 An example of a 5G system roaming architecture for home routing scenarios in a service-based interface representation is illustrated according to aspects of the present disclosure. A UE 402 is registered with a (serving) AMF 404 in a VPLMN 401. The AMF 404 retrieves UE 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 a V-SMF and b) an SMCF 410 in the HPLMN 403 referred to as a H-SMF. The AMF 404 forwards a PDU session establishment request from the UE 402 to the V-SMF 408, which selects a UPF 412 in the VPLMN 401, and to the H-SMF 410. The H-SMF 410 retrieves PDU session subscription data from the UDM 406, establishes an SM policy association with a H-PCF 414, selects an anchor UPF 416, and sends a PDU session establishment response (e.g., accept) message to the V-SMF 408.

[0047] In one embodiment for indirect network sharing, from the UE side, a UE in the shared RAN area selects a participating operator and the UE registers with the participating operator. The hosting operator’s intermediate 5GC is transparent to the UE. Correspondingly, the procedure from the UE side is the same as if the UE registers with the participating operator and directly communicates with the participating operator. The participating operator can be the HPLMN or VPLMN for the UE. The hosting operator’s AMF (e.g., the serving AMF) needs to mimic the 5GC of the participating operator’s AMF behavior for the UE, e.g., the network slice configuration for the UE is set as if it comes from the 5GC of the participating operator. In one example, the allowed NSSAI created and sent to the UE contains the S-NSSAI values of the participating operator. However, for the network functions (NFs) in the hosting operator and the shared RAN, the serving AMF needs to behave similar to the AMF in the VPLMN. The subject matter herein describes how the AMF behaves, e.g., in the hosting MNO, and what information it provides to the shared RAN, entities and NFs in the 5GC of the hosting operator, and NFs in the 5GC of the participating operator.

[0048] In one embodiment, the following is based on the above Figure 3 and Figure 4 In one embodiment, the disclosure describes how an AMF in the hosting network acting as a serving AMF in the hosting network operator applies specific operational modes: 1) for the UE, acts as an AMF in the participating network (e.g., creates network configuration for the UE as if the UE is registering with the participating network (e.g., HPLMN)); and 2) the AMF acts as an NF in the 5GC of the hosting network and for the RAN, acts as an AMF in the VPLMN (e.g., as if the UE is registered in the VPLMN).

[0049] Generally, an AMF in the hosting operator can apply the functionality of a serving AMF in the hosting network. In one embodiment, the AMF determines (e.g., based on a service level agreement (SLA) between the hosting network and the participating network) that the UE is registering with the participating operator. The AMF can support the functionality of a serving AMF in the hosting network and, as such, the AMF can register itself or announce a specific profile (or functionality) in the network repository function (NRF) or neighbor AMFs that the AMF supports the functionality of a serving AMF in the hosting network. This functionality can be referred to as a serving AMF functionality in the hosting network.

[0050] In one embodiment, the AMF does not provide the UE with a configured NSSAI for the hosting network (e.g., a configured NSSAI containing S-NSSAIs of the hosting operator), e.g., excludes, does not provide, does not include the NSSAI, etc., based at least in part on or in response to the registration request message. The AMF does not create and provide the UE with a configured NSSAI even if the UE sent a request NSSAI. Instead, the AMF provides an allowed NSSAI. If the AMF is provided with such information, the AMF can provide a configured NSSAI for the participating operator (i.e., a configured NSSAI containing S-NSSAIs of the participating operator).

[0051] In one embodiment, the AMF (or together with a network slice selection function (NSSF) in the hosting network) determines an allowed NSSAI for the UE and / or a partial allowed NSSAI for the UE, including S-NSSAIs of the participating operator, e.g., sent to the UE, using the subscribed S-NSSAIs (e.g., received from the UDM or from a source AMF, or stored from a previous registration), the mapping / corresponding S-NSSAIs of the hosting network to S-NSSAIs from the participating network, and locally available S-NSSAIs from the hosting network. Further, the AMF can create a rejected S-NSSAI(s) of the participating operator if some of the S-NSSAI(s) requested by the UE are not supported in the hosting network (e.g., there is no corresponding S-NSSAI available in the hosting network).

[0052] In one embodiment, the AMF determines an allowed NSSAI for the hosting operator (or a partial allowed NSSAI for the hosting operator), e.g., containing S-NSSAI values of the hosting operator that map to S-NSSAI values of the participating operator, using the subscribed S-NSSAIs (e.g., received from the UDM or from a source AMF, or stored from a previous registration), the mapping / corresponding S-NSSAIs of the hosting network to S-NSSAIs from the participating network, and locally available S-NSSAIs from the hosting network. The allowed NSSAI for the hosting operator (or the partial allowed NSSAI for the hosting operator) is used only within the hosting network. The allowed NSSAI for the hosting operator is stored locally in the AMF and can correspond to a “mapping of allowed NSSAI” that includes a mapping of each S-NSSAI of the participating MNO to an S-NSSAI of the hosting MNO.

[0053] In one embodiment, the AMF configures mode “d” (as described above) for operator-controlled inclusion of NSSAI in AS signaling, which indicates that the UE should not provide NSSAI in AS.

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

[0055] In one embodiment, in the signaling to the PCF for AM policy establishment, the AMF uses the allowed NSSAI for the hosting operator. In one embodiment, the AMF sends the allowed NSSAI for the hosting operator to the RAN in the N2 signal, while the AMF sends the allowed NSSAI for the UE and / or the partial allowed NSSAI for the UE to the UE in the registration accept message.

[0056] 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 by the UE in the NAS request message) in the request message to the SMF for SM creation.

[0057] It should be noted that the description uses the term PLMN as the public network, but the solution can also apply to non-public networks, such as standalone non-public networks (SNPN). It should also be noted that the hosting operator is identified by a hosting operator PLMN ID and the participating operator is identified by a participating operator PLMN ID.

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

[0059] At 1 (see messaging 502), in one embodiment, the UE 501 selects a PLMN ID that is broadcast by a cell of the shared RAN 503. The UE 501 creates and sends a Registration Request message 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 can include a subscription concealed identifier (SUCI) and a Requested NSSAI. In one example, the Requested NSSAI can contain S-NSSAI values S1, S2, and S3 of the participating operator. The UE 501 uses a locally stored configured NSSAI of the participating operator 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 parameters can include the selected PLMN ID indicated by the UE 501.

[0060] At 2a (see block 504), in one embodiment, the AMF 505 determines that the UE 501 is registering with the participating network operator identified by the indicated selected PLMN ID based on the indicated selected PLMN ID. The AMF 505 determines to apply specific functions to act as a serving AMF in the hosting operator network. In one embodiment, a 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 can identify different networks. If the UE 501 has not been authenticated, the AMF 505 can perform a primary authentication and authorization procedure.

[0061] In one embodiment, if the AMF 505 selected by the RAN 503 does not support the Requested NSSAI, or does not support the functions for serving AMF functions in the hosting network, the AMF 505 can use an AMF redirection (re-allocation) procedure to another AMF 505 that supports the serving AMF functions in the hosting network. It should be noted that an AMF 505 that supports AMF functions in the hosting network can register the function in its NRF in a profile so that other AMFs can discover the AMF 505. Alternatively, an AMF 505 that supports AMF functions in the hosting network can configure neighbor AMFs 505 with this information via direct signaling.

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

[0063] At 2c (see messaging 508), in one embodiment, the UDM 509 determines that the UE 501 is registered to a hosting network in which indirect network sharing can be used, e.g., based on the hosting PLMN ID. The UDM 509 sends a response message including the UE subscription data. The UDM 509 can derive a list of subscribed S-NSSAIs and / or subscribed data network names (DNNs) that are applicable to indirect network sharing and / or the specific hosting network. The UDM 509 can take into account the SLA between the participating operator and the hosting operator to derive the subscribed S-NSSAIs and / or DNNs to send in the UE subscription data.

[0064] In addition, the UDM 509 can send other subscription parameter values that are applicable to the current hosting network, e.g., a UE aggregate maximum bit rate (AMBR) (the value is lower than the UE-AMBR that would be used in the participating network operator), and / or services that are not included in the UE subscription services to be provided during indirect network sharing (e.g., multicast broadcast service (MBS), location services, ProSe services, etc.).

[0065] At 3 (see block 510), in one embodiment, the AMF 505 applies the following functions that are specific to the serving AMF 505 in the hosting network. Note that step 3 shows only the AMF 505, but in one embodiment, the AMF 505 can also use the NSSF service. In one embodiment, the subscribed S-NSSAIs sent within the UE subscription data can be different from the configured NSSAI that the participating operator can configure in the UE. In this case, the AMF 505 needs to create (alone or interacting with the NSSF in the hosting network) the allowed NSSAI and the rejected S-NSSAIs based on the list of subscribed S-NSSAIs of the UE 501 and the requested NSSAI, but not send the configured NSSAI for the hosting network.

[0066] In one embodiment, the AMF 505 does not provide a configured NSSAI to the UE 501 for the hosting MNO. The AMF 505 does not create and provide a configured NSSAI to the UE 501 even if the UE 501 does not send a request NSSAI. But the AMF 505 will provide an allowed NSSAI with the S-NSSAIs of the hosting operator. In one embodiment, the AMF 505 uses the subscribed S-NSSAIs (e.g., received from the UDM 509, or from the source AMF 505, or stored from a previous registration) to determine the values of the S-NSSAIs of the hosting operator that map to the subscribed S-NSSAIs. The AMF 505 also determines which S-NSSAIs of the hosting operator 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 includes the corresponding S-NSSAIs of the hosting operator in the allowed NSSAI for the UE 501 and / or in the partial allowed NSSAI for the UE 501. In other words, the AMF 505 includes the S-NSSAIs of the hosting operator (e.g., intended to be HPLMN S-NSSAI values) in the allowed NSSAI for the UE 501 and / or in the partial allowed NSSAI for the UE 501. In such an embodiment, if some of the S-NSSAI(s) requested by the UE are not supported in the hosting network (e.g., there are no corresponding S-NSSAI(s) available in the hosting network), the AMF 505 can create a list of rejected S-NSSAI(s) of the hosting operator to be sent to the UE 501. One example of how to create the allowed NSSAI for the UE and / or the partial allowed NSSAI for the UE is shown in step 5.

[0067] In one embodiment, the AMF 505 determines an allowed NSSAI for the hosting network operator, which contains the hosting operator’s S-NSSAI values that map to the participating operator’s S-NSSAI values included in the allowed NSSAI for the UE 501 and / or the partial allowed NSSAI for the UE 501. If the AMF 505 creates a partial allowed NSSAI for the UE 501, the AMF 505 can also create a corresponding partial allowed NSSAI for the hosting network. The allowed NSSAI for the hosting network or the partial allowed NSSAI for the hosting network is stored locally in the AMF 505 and can be similar to the “allowed NSSAI mapping” information derived in the AMF 505 in the VPLMN in roaming cases. While the “allowed NSSAI mapping” information is derived to be sent to the UE 501 and includes the mapping of each S-NSSAI of the VPLMN to an S-NSSAI of the HPLMN, the allowed NSSAI for the hosting network (or the partial allowed NSSAI for the hosting network) is only used in the hosting network domain. The allowed NSSAI for the hosting network (or the partial allowed NSSAI for the hosting network) can include a list of S-NSSAIs that are valid in the hosting network and correspond to the list of S-NSSAIs included in the allowed NSSAI for the UE 501 and / or the partial allowed NSSAI for the UE 501.

[0068] In other words, the AMF 505 stores two types of allowed NSSAI in the UE 501 context: the allowed NSSAI for the UE 501 and / or the partial allowed NSSAI for the UE 501 sent to the UE 501, and the allowed NSSAI for the hosting network used in signaling to other NFs in the hosting network and to the shared RAN 503.

[0069] In one example of the disclosure, assume that the shared RAN 503 is configured with network slice (e.g., NSSAI) information for the hosting network, while the UE 501 is configured with NSSAI information for the participating network. In one embodiment, the RAN 503 uses the NSSAI information from AS signaling to select the AMF 505 or apply RAN internal congestion or overload handling; however, the NSSAI information provided by the UE 501 is for the participating network. Therefore, in such an embodiment, the AMF 505 configures the UE 501 not to provide NSSAI information in AS signaling. In other words, the AMF 505 configures mode “d” for operator control inclusion of NSSAI in AS signaling, e.g., as described in clause 5.15.9 of 3GPP TS 23.501, V18.5.0, 2024-03.

[0070] In one embodiment, the shared RAN 503 can apply NSAG for cell (re)selection or for random access control, e.g., as described in clause 5.15.14 of 3GPP TS 23.501, V18.5.0, 2024-03. In such an embodiment, the RAN 503 has configured the AMF 505 hosting network with NSAG information. The serving AMF 505 creates and provides to the NSAG capable UE 501 (e.g., the UE 501 has indicated support for NSAG in the 5GMM information element at step 1) a NSAG value corresponding to the hosting S-NSSAI value that maps to the participating MNO’s HPLMN S-NSSAI value.

[0071] At 4 (see messaging 512), in one embodiment, the AMF 505 establishes access and mobility (AM) policy association with the PCF 507. The AMF 505 sends a request message for AM policy association establishment to the PCF 507, which includes the allowed NSSAI for the hosting operator (e.g., not the allowed NSSAI for the UE 501) and other parameters such as the subscribed RAT / frequency selection priority (RFSP) or UE-AMBR.

[0072] In one embodiment, the PCF 507 derives the RFSP applicable to the shared RAN 503 using the allowed NSSAI for the hosting operator, based on the hosting operator’s slices. However, the network slices sent to the UE 501 include the values for the participating operator’s network slices.

[0073] 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 a N2 message to the RAN 503. In one embodiment, the AMF 505 creates the N2 message and includes the allowed 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.

[0074] In one embodiment, the NAS registration accept message includes an allowed NSSAI for the UE 501 and / or a partial allowed NSSAI for the UE 501, any of which have S-NSSAIs that are participating networks. If the AMF 505 is provided with such information, the AMF 505 can provide a configured NSSAI for a participating operator (e.g., a configured NSSAI containing S-NSSAIs of the participating operator). The NAS registration accept message can also include a list of rejected S-NSSAIs, where the S-NSSAI values are S-NSSAIs that are participating networks. Each rejected S-NSSAI is associated with a rejection cause value that indicates the reason for the rejection, e.g., rejected in the entire PLMN, or rejected in the registration area, or partially rejected for a certain TA part of the registration area. In the specific scenario of indirect network sharing, the AMF 505 in the hosting network can apply different logic for the rejection cause, e.g., the AMF 505 can use “rejected in the registration area” instead of “rejected for the entire PLMN”. In this way, from the perspective of the UE 501, the registered PLMN is the participating operator PLMN, and the UE 501 can leave the shared RAN 503 and move to a RAN of a participating network, where the rejected S-NSSAI can be available.

[0075] In one example, the UE can have requested the use of network slices S-NSSAI#S1, S-NSSAI#S2, and S-NSSAI#S3 (which can be part of a configured NSSAI for the participating network). The AMF 505 can receive a subscription S-NSSAI indicating S-NSSAI#S1, S-NSSAI#S2, which indicates that the AMF 505 can only allow S-NSSAI#S1, S-NSSAI#S2 for the UE 501. The AMF 505 can include S-NSSAI#S1, S-NSSAI#S2 in the allowed NSSAI for the UE 501 and / or the partial allowed NSSAI for the UE 501. The AMF 505 rejects the requested S-NSSAI#S3 with a cause value indicating that it is not supported in the registration area. Further, the AMF 505 determines the S-NSSAI of the hosting network corresponding to the participating network's S-NSSAI included in the allowed NSSAI for the UE 501 and / or the partial allowed NSSAI for the UE 501. For example, S-NSSAI#S1 corresponds to S-NSSAI#S11 and S-NSSAI#S2 corresponds to S-NSSAI#S12. Accordingly, the AMF 505 creates an allowed NSSAI for the hosting network operator including S-NSSAI#S11 (corresponding / mapped to S-NSSAI#S1) and S-NSSAI#S12 (corresponding / mapped to S-NSSAI#S2).

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

[0077] In one embodiment, in the NAS registration accept message, the AMF 505 can include the NSAG information as described in step 3. The AMF 505 creates the NSAG information using the NSAG identifier used / configured by the shared RAN 503 and the corresponding list of S-NSSAI for the NSAG identifier, where the list of S-NSSAI contains one or more S-NSSAI that has a value of the participating network mapped to the S-NSSAI of the hosting network configured in the AMF 505.

[0078] In one embodiment, the NSAG information parameter can be formatted as shown in Table 1, which shows a number of NSAG elements, e.g., NSAG 1, NSAG 2, etc.

[0079]

[0080] Table 1: NSAG information parameter

[0081] In one embodiment, each NSAG element can contain information as shown in Table 2. Table 2 illustrates the NSAG element format, where the NSAG identifier can be associated with one or more S-NSSAI of the hosting network operator.

[0082]

[0083] Table 2: NSAG element format

[0084] In the specific scenario of indirect network sharing, the AMF 505 will create a NSAG element with the NSAG identifier value of the hosting network (e.g., configured from the RAN 503 to the AMF 505), and the S-NSSAI list will include the S-NSSAI of the participating operator included in the allowed NSSAI for the UE 501 and / or the partial allowed NSSAI for the UE 501 sent to the UE 501.

[0085] In this way, the AMF 505 in the hosting network plays two roles - for the UE 501, the AMF 505 behaves as an AMF 505 in the participating network (e.g., HPLMN), while for the NFs and RAN of the hosting network, the AMF 503 behaves as an AMF 505 in a VPLMN.

[0086] Figure 6 An example signal flow for PDU session establishment for indirect network sharing is illustrated, in accordance with aspects of the present disclosure. In one embodiment, network slice availability information is provided by the UDR to the PCF. The UDR is configured to maintain and store network slice availability information per S-NSSAI. For example, the UDR can store network slice availability information in network slice related policy control requirements (e.g., (remaining) maximum slice data rate values for UL and DL can be stored in the UDR).

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

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

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

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

[0091] 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, HPLMN S-NSSAI = participating NW S-NSSAI, selected DNN, and / or N1 SM container (PDU session establishment request).

[0092] At 5 (see block 610), the H-SMF 609 retrieves the SM subscription data for the UE 601 and for the combination of S-NSSAI and DNN of the participating network. 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 in the participating network.

[0093] 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 the N1 SM container to be sent to the UE 601.

[0094] At 7 (see messaging 614), in one embodiment, the V-SMF 607 creates a N2 SM information container and updates the configuration of the UPF in the hosting network. The V-SMF 607 sends a request message to the AMF 605 using the Namf_Communication_N1N2MessageTransfer service operation to send the N2 SM information to the RAN 603 and the N1 SM container to the UE 601. In one embodiment, the N2 SM information includes at least the following parameters: PDU Session ID, CN tunnel information for N3 tunnel, one or more Quality of Service (QoS) profiles and corresponding QoS Flow Identifiers (QFIs), and / or H = 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 to be used by the V-SMF 607 (e.g., as the value of the VPLMN S-NSSAI).

[0095] At 8 (see messaging 616), in one embodiment, the AMF 605 sends a N2 downlink message to the RAN 603, which includes the N2 SM information message and the 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 contains 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 HPLMN S-NSSAI), one or more QoS rules, etc.

[0096] In this way, the PDU session is established as a home-routed PDU session to the participating network; however, from the UE side, this is a PDU session in a non-roaming case (e.g., as if the UE established the PDU session to the HPLMN).

[0097] Figure 7An example of a UE 700 is illustrated in accordance with aspects of the present disclosure. The UE 700 can 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 thereof or various components thereof, can be examples of means for performing various aspects of the present disclosure described herein. These components can be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

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

[0099] The processor 702 can 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 can be configured to operate the memory 704. In some other implementations, the memory 704 can be integrated into the processor 702. The processor 702 can 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.

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

[0101] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 can 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 can support wireless communication at the UE 700 in accordance with examples disclosed herein.

[0102] The controller 706 can manage inputs and outputs for the UE 700. The controller 706 also can manage a peripheral device not integrated to the UE 700. In some implementations, the controller 706 can utilize an operating system, such as Windows® Mobile, Windows® Phone OS, iOS, Android® OS, BSD, LINUX®, Fedora™, or other operating system. In some implementations, the controller 706 can be implemented as part of a processor 702.

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

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

[0105] The transmitter chain 712 can be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 can include at least one modulator to modulate data onto carrier signals to prepare signals for transmission over a wireless medium. The at least one modulator can be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes, like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 712 can also include at least one power amplifier configured to amplify the modulated signals to a proper power level for transmission over a wireless medium. The transmitter chain 712 can also include one or more antennas to transmit amplified signals into the air or wireless medium.

[0106] Figure 8An example of a processor 800 is illustrated in accordance with aspects of the present disclosure. The processor 800 can be an example of a processor configured to perform various operations in accordance with examples described herein. The processor 800 can include a controller 802 configured to perform various operations in accordance with examples described herein. The processor 800 can optionally include at least one memory 804, which can be, for example, a LI / L2 / L3 cache. Additionally or alternatively, the processor 800 can optionally include one or more arithmetic logic units (ALUs) 806. One or more of these components can be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces, such as buses.

[0107] The processor 800 can be a processor chipset and include a protocol stack (e.g., software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples described herein. The processor chipset can 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.).

[0108] The controller 802 can be configured to manage and coordinate the various operations (e.g., signaling, receiving, obtaining, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 800 such that the processor 800 supports various operations in accordance with examples described herein. For example, the controller 802 can operate as a control unit of the processor 800 to generate control signals that manage the operation of the various components of the processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operational timing.

[0109] The controller 802 can be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 804 and determine subsequent instruction(s) to execute to cause the processor 800 to support various operations in accordance with the examples described herein. The controller 802 can be configured to track memory addresses of instructions associated with the memory 804. The controller 802 can be configured to decode instructions to determine operations to perform and operands involved. For example, the controller 802 can be configured to interpret instructions and determine control signals to output to other components of the processor 800 to cause the processor 800 to support various operations in accordance with the examples described herein. Additionally or alternatively, the controller 802 can be configured to manage data flow within the processor 800. The controller 802 can be configured to control data transfers between registers, arithmetic logic units (ALUs), and other functional units of the processor 800.

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

[0111] The memory 804 can 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 can 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 can be configured to execute 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 can be coupled with or coupled to the memory 804, and the processor 800, the controller 802, and the memory 804 can be configured to perform the various functions described herein. In some examples, the processor 800 can include multiple processors, and the memory 804 can include multiple memories. One or more of the multiple processors can be coupled with one or more of the multiple memories, which can be individually or collectively configured to perform the various functions herein.

[0112] According to examples described herein, the one or more ALUs 806 can be configured to support various operations. In some implementations, the one or more ALUs 806 can reside within or on a processor chipset (e.g., the processor 800). In some other implementations, the one or more ALUs 806 can reside outside of a processor chipset (e.g., the processor 800). The one or more ALUs 806 can perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, the one or more ALUs 806 can receive input operands and an operation code that determines the operation to be performed. The one or more ALUs 806 are configured with various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, the one or more ALUs 806 can support logical operations such as AND, OR, exclusive OR (XOR), NOT OR (NOR), and NOT AND (NAND) to enable the one or more ALUs 806 to handle conditional operations, comparisons, and bitwise operations.

[0113] According to examples disclosed herein, the processor 800 can support wireless communications. In one embodiment, the processor 800 can be configured as 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 allowed NSSAI for the UE, or a partial allowed NSSAI for the UE, or both, and wherein each of the allowed NSSAI or the partial allowed NSSAI or both is associated with a corresponding allowed NSSAI or a corresponding partial allowed NSSAI associated with the hosting network; and transmitting a third message to a second network entity of the hosting network including an allowed NSSAI or a partial allowed NSSAI or both associated with the hosting network corresponding to the allowed NSSAI or the partial allowed NSSAI or both for the UE.

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

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

[0116] In one embodiment, the processor 800 can be configured to support a means for determining, based at least in part on the hosting network, whether a network entity supports a function, wherein the function comprises serving a UE.

[0117] In one embodiment, the processor 800 can be configured to support a means for determining whether to provide a configured NSSAI associated with the hosting network to the UE or determining NSAG information for the UE, wherein the NSAG information comprises a mapping of an NSAG identifier for the hosting network to a corresponding NSSAI for a participating network.

[0118] In one embodiment, the NSAG identifier corresponds to a single NSSAI (S-NSSAI) for the hosting network; and the S-NSSAI of the hosting network maps to a corresponding S-NSSAI of the participating network.

[0119] In one embodiment, the processor 800 can be configured to support a means for outputting a configuration for the UE to not include NSSAI in AS signaling.

[0120] In one embodiment, the processor 800 can be configured to support a means for refraining from outputting, to the UE, a configured NSSAI for the hosting network based at least in part on the first message not including the NSSAI.

[0121] In one embodiment, the processor 800 can be configured to support a means for rejecting a requested single NSSAI (S-NSSAI) associated with the participating network in response to the requested S-NSSAI not being supported in the hosting network.

[0122] In one embodiment, the processor 800 can be configured to support a means for rejecting a requested S-NSSAI in response to the requested S-NSSAI being unable to map to a corresponding S-NSSAI associated with the hosting network.

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

[0124] In one embodiment, the first message comprises a registration request message, and wherein the second message comprises a registration accept message.

[0125] Figure 9An example of a NE 900 is illustrated in accordance with aspects of the present disclosure. The NE 900 can 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, can be examples of means for performing various aspects of the present disclosure described herein. These components can be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

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

[0127] The NE 900 can be configured to support means for determining a NES mode for the NE, the NES mode comprising a DU-specific mode or a RU-specific mode of a distributed architecture; determining, based on the NES mode, a NES class and a NES configuration for a traffic flow associated with the NE, the NES class being associated with a QoS class for the traffic flow; mapping the traffic flow to a DU, a RU, or a combination thereof based on the NES class associated with the traffic flow; and transmitting the NES configuration to the DU, the RU, or the combination thereof to which the traffic flow is mapped.

[0128] In one embodiment, the NE 900 can be configured 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 comprising assistance information based at least in part on the received first message, wherein the assistance information comprises an allowed NSSAI for the UE, or a partial allowed NSSAI for the UE, or both, and wherein each of the allowed NSSAI or the partial allowed NSSAI or both is associated with a corresponding allowed NSSAI or a corresponding partial allowed NSSAI associated with the hosting network; and transmitting a third message to a second network entity of the hosting network, the third message comprising an allowed NSSAI or a partial allowed NSSAI or both associated with the hosting network corresponding to the allowed NSSAI or the partial allowed NSSAI or both for the UE.

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

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

[0131] In one embodiment, the NE 900 can be configured to support means for determining, based at least in part on the hosting network, whether a network entity supports a function, where the function includes serving the UE.

[0132] In one embodiment, the NE 900 can be configured to support means for determining whether to provide a configured NSSAI associated with the hosting network to the UE or determining NSAG information for the UE, where the NSAG information includes a mapping of an NSAG identifier for the hosting network to a corresponding NSSAI for the participating network.

[0133] In one embodiment, the NSAG identifier corresponds to a single NSSAI (S-NSSAI) for the hosting network; and the S-NSSAI of the hosting network is mapped to a corresponding S-NSSAI for the participating network.

[0134] In one embodiment, the NE 900 can be configured to support means for outputting a configuration for the UE to not include NSSAI in AS signaling.

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

[0136] In one embodiment, the NE 900 can be configured to support means for rejecting a requested single NSSAI (S-NSSAI) associated with the participating network in response to the requested S-NSSAI not being supported in the hosting network.

[0137] In one embodiment, the NE 900 can be configured to support means for rejecting a requested S-NSSAI in response to the requested S-NSSAI being unable to be mapped to a corresponding S-NSSAI associated with the hosting network.

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

[0139] In one embodiment, the first message comprises a registration request message, and wherein the second message comprises a registration accept message.

[0140] The processor 902 can 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 can be configured to operate the memory 904. In some other implementations, the memory 904 can be integrated into the processor 902. The processor 902 can 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.

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

[0142] In some implementations, the processor 902 and the memory 904 coupled with the processor 902 can 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 can support wireless communication at the NE 900 in accordance with examples disclosed herein.

[0143] The controller 906 can manage inputs and outputs for the NE 900. The controller 906 also can manage peripherals not integrated into the NE 900. In some implementations, the controller 906 can utilize an operating system, such as or other operating system, in some implementations, the controller 906 can be implemented as part of the processor 902.

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

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

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

[0147] Figure 10 A flow diagram illustrating a method in accordance with aspects of the disclosure is shown. The operations of the method can be implemented by an NE described herein. In some implementations, an NE can execute a set of instructions to control the functional elements of the NE to perform the described functions.

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

[0149] At 1004, the method can transmit a second message including assistance information based at least in part on the received first message, where the assistance information includes an allowed NSSAI for the UE, or a partial allowed NSSAI for the UE, or both, and where each of the allowed NSSAI or the partial allowed NSSAI or both is associated with a corresponding allowed NSSAI or a corresponding partial allowed NSSAI associated with the hosting network. The operations of 1004 can be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1004 can be performed by an NE as described with reference to Figure 9The NE described to perform.

[0150] At 1006, the method can transmit, to a second network entity hosting the network, a third message including allowed NSSAI, or partial allowed NSSAI, or both, associated with the hosting network corresponding to the allowed NSSAI, or partial allowed NSSAI, or both for the UE. The operations of 1006 can be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1006 can be performed by a network entity as described with reference to FIGs. 1 through 8. Figure 9 The NE described to perform.

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

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

Claims

1. A network entity for wireless communication, configured to: receive a first message for registering a user equipment (UE) with a participating network associated with a hosting network; and transmit a second message comprising assistance information based at least in part on the received first message, wherein the assistance information comprises an allowed network slice selection assistance information (NSSAI) for the UE, or a partial allowed NSSAI for the UE, or both, and wherein each of the allowed NSSAI or the partial allowed NSSAI or both is associated with a corresponding allowed NSSAI or a corresponding partial allowed NSSAI associated with the hosting network; and transmit a third message to a second network entity of the hosting network comprising an allowed NSSAI or a partial allowed NSSAI or both associated with the hosting network corresponding to the allowed NSSAI or the partial allowed NSSAI or both for the UE.

2. The network entity of claim 1, wherein the network entity comprises an access and mobility management function (AMF), and wherein the second network entity comprises one or more of: a base station, a policy control function (PCF), a unified data management, or a unified data repository.

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

4. The network entity of claim 1, further configured to determine whether the network entity supports a function based at least in part on the hosting network.

5. The network entity of claim 4, further configured to: determine whether to provide a configured NSSAI associated with the hosting network to the UE; or determine network slice access layer group (NSAG) information for the UE, wherein the NSAG information comprises a mapping of an NSAG identifier for the hosting network to a corresponding NSSAI for the participating network.

6. The network entity of claim 5, wherein the NSAG identifier corresponds to a single NSSAI (S-NSSAI) for the hosting network.

7. The network entity of claim 1, further configured to output a configuration for the UE to not include NSSAI in access stratum (AS) signaling.

8. The network entity of claim 1, further configured to refrain from outputting a configured NSSAI for the hosting network based at least in part on the first message not including NSSAI.

9. The network entity of claim 1, further configured to reject a requested single NSSAI (S-NSSAI) associated with the participating network in response to the requested S-NSSAI not being supported in the hosting network.

10. The network entity of claim 1, further configured to: ​ ​ ​ ​ ​ ​ ​ determining a single NSSAI (S-NSSAI) of the hosting network, the S-NSSAI of the hosting network mapping to an S-NSSAI of the participating network; and including the determined S-NSSAI of the hosting network in a message to a session management function (SMF) of the hosting network.

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

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

13. The method of claim 12, wherein the network entity comprises an access and mobility management function (AMF), and wherein the second network entity comprises one or more of: a base station, a policy control function (PCF), a unified data management, or a unified data repository.

14. The method of claim 12, wherein the first message comprises a registration request message, and wherein the second message comprises a registration accept message.

15. A processor for wireless communication, comprising: at least one controller coupled with the at least one memory and configured to cause the processor to: receive a first message, the first message being for registering a user equipment (UE) with a participating network associated with a hosting network; send a second message, the second message comprising assistance information based at least in part on the received first message, wherein the assistance information comprises an allowed network slice selection assistance information (NSSAI) for the UE, or a partial allowed NSSAI for the UE, or both, and wherein each of the allowed NSSAI or the partial allowed NSSAI or both is associated with a corresponding allowed NSSAI or a corresponding partial allowed NSSAI associated with the hosting network; and send a third message to a second network entity of the hosting network, the third message comprising an allowed NSSAI or a partial allowed NSSAI or both associated with the hosting network corresponding to the allowed NSSAI or the partial allowed NSSAI or both for the UE.

Images