Systems, methods, and devices for indirect network sharing

Abstract

A solution for indirect network sharing is described herein. A user equipment (UE) may receive a Public Land Mobile Network (PLMN) Identifier (ID) corresponding to a hosted operator network and one or more participating operator networks. The UE may select a PLMN ID for a participating operator network and communicate with the hosted operator network to perform one or more procedures based on the PLMN ID for the participating operator network. Examples of such procedures may include an authentication procedure, a registration procedure, a protocol data unit (PDU) session establishment procedure, and subsequent data transfer to an external network. An access and mobility management function (AMF) of the hosted operator network acts as a serving AMF, and one or more functions in the hosted operator network and the participating operator network may be selected to complete the procedures.

Description

Cross Reference to Related Applications

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 703,697, filed October 4, 2024, and U.S. Patent Application No. 19 / 342,391, filed September 26, 2025, the contents of which are incorporated by reference herein in their entirety for all purposes. TECHNICAL FIELD

[0002] The present disclosure relates to wireless communication networks and mobile device capabilities. BACKGROUND

[0003] Wireless communication networks and wireless communication services are becoming increasingly dynamic, complex, and ubiquitous. For example, some wireless communication networks can be developed to implement fifth generation (5G) or new radio (NR) technology, sixth generation (6G) technology, and the like. Such technologies can include solutions for enabling user equipment (UE) and network devices, such as base stations and satellites, to communicate with one another. SUMMARY

[0004] Some aspects of the present disclosure relate to a baseband circuitry comprising: one or more processors configured to: process a plurality of public land mobile network (PLMN) identifiers (IDs) including at least one PLMN ID of a hosting carrier network and at least one PLMN ID of a participating carrier network; select the at least one PLMN ID of the participating carrier network; and generate information including the at least one PLMN ID of the participating carrier network for communication to the participating carrier network via the hosting carrier network. BRIEF DESCRIPTION OF DRAWINGS

[0005] The present disclosure will be readily understood by the following detailed description in conjunction with the accompanying drawings. Like reference numerals can designate like structural and functional elements. The accompanying drawings and corresponding description are provided to illustrate aspects, implementations, and the like, of the present disclosure, and are not intended to be limiting of the aspects, implementations, and the like, of the present disclosure. Reference to “one” or “an” aspect, implementation, or the like, can not necessarily mean the same aspect, implementation, or the like, and can mean at least one, one or more, and the like.

[0006] Figure 1 is a diagram of an example overview of one or more of the techniques described herein.

[0007] Figure 2 is a diagram of an example network in accordance with one or more implementations described herein.

[0008] Figure 3 is a diagram of an example network architecture in accordance with one or more implementations described herein.

[0009] Figure 4 is a diagram of an example of a hosting carrier network and a participating carrier network in accordance with one or more implementations described herein.

[0010] Figure 5 is a diagram of an example process for an indirect network in accordance with one or more implementations described herein.

[0011] Figure 6 is a diagram of an example of a session management function (SMF) interface between a hosting carrier network and a participating carrier network in accordance with one or more implementations described herein.

[0012] Figure 7 is a diagram of an example of a network slice selection function (Nssf) interface between a hosting carrier network and a participating carrier network in accordance with one or more implementations described herein.

[0013] Figure 8 is a diagram of an example process for an indirect network in accordance with one or more implementations described herein.

[0014] Figure 9 is a diagram of an example of components of a device in accordance with one or more implementations described herein.

[0015] Figure 10 is a diagram of an example interface of baseband circuitry in accordance with one or more implementations described herein.

[0016] Figure 11 is a block diagram illustrating an example of a component that is capable of reading instructions from a machine- or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and executing any one or more of the methods discussed herein in accordance with one or more implementations described herein.

[0017] Figure 12 is a diagram of an example process for an indirect network in accordance with one or more implementations described herein. DETAILED DESCRIPTION

[0018] The following detailed description references the drawings. Like reference numerals can refer to like features throughout different drawings. Additionally, the disclosure is not limited to the following description as other implementations can utilize other specific embodiments and structural or logical changes can be made without departing from the scope of the disclosure.

[0019] A wireless communication network can include user equipment (UE) capable of communicating with base stations and / or other network access devices. A base station can provide the UE with access to a core network (CN) and additional external networks, such as the Internet. The wireless communication network can implement various technologies and standards that enable wireless communication. Examples of these technologies can include allocating time and frequency resources to enable UEs and base stations to communicate with each other.

[0020] A wireless communication network can be managed and operated by an operator. The wireless communication network can include UEs connected to base stations or other radio access network (RAN) devices, which in turn are connected to a CN. The wireless communication network can implement one or more types of communication standards, including the fifth generation (5G) communication standard of the Third Generation Partnership Project (3GPP). A wireless communication network implementing the 5G communication standard can be referred to as a 5G system (5GS).

[0021] Currently, the 5GS only allows sharing of radio access networks (RANs) across multiple operator networks (e.g., multiple operator CNs). This is done through a multi-operator CN (MOCN) sharing mechanism, where RAN resources are shared by multiple participating operators. 5G MOCN support for 5GS (including UEs, RANs, and access and mobility management functions (AMFs)) supports the use of more than one public land mobile network (PLMN) identifier (ID) (i.e., with the same or different mobile country code (MCC) and different mobile network code (MNC)) or a combination of PLMN ID and network OD (NID). 5G MOCN supports next generation RAN (NG-RAN) sharing with or without multiple cell identities broadcast.

[0022] Limitations of the 5G MOCN can include the following. For 5G MOCN, a challenge for network operators is the maintenance resulting from the direct interface between the shared RAN and two or more core networks of different operators (e.g., a large number of N2 (RAN-AMF) and N3 (RAN-UPF (user plane function)) interfaces), especially for a large number of shared 5G base stations, as each of these BSs is connected to an AMF and UPF in the participating networks. Therefore, it can be beneficial to introduce a new network sharing mechanism with less maintenance overhead based on operator agreements.

[0023] One or more of the techniques described herein include a solution to address these deficiencies by providing indirect network sharing. Indirect network sharing can occur between a hosting operator network and one or more participating operator networks. The hosting operator network can include one or more RANs (e.g., base stations) connected to a portion of the CN of the hosting operator network. The CN components of the hosting operator network can be connected to the CN of the participating operator network. The RAN of the hosting operator network can be shared among the participating operator networks.

[0024] A base station in the shared RAN can broadcast multiple PLMN IDs, including a PLMN ID of the hosting operator network and several PLMN IDs of the participating operator networks. The serving AMF (i.e., an AMF in the CN of the hosting operator network) can support multiple PLMN IDs. A UE with a subscription from a participating operator (HPLMN or equivalent PLMN) can select a PLMN ID representing a participating operator in the shared RAN area. The serving AMF can select CN functions in the PLMN of the participating operator for the UE based on home routed roaming principles. In addition, the serving AMF can select a session management function (SMF) of the participating operator network, optionally taking into account UE location information, and can also select a visited SMF (V-SMF) in the hosting operator network during a protocol data unit (PDU) session establishment procedure. If the hosting operator network (e.g., the serving AMF) determines that the UE is not from (e.g., registered to) the participating operator network of the selected PLMN ID, the hosting operator network can reject the UE with an existing cause value, a reject message, and the like.

[0025] An AMF of the hosting operator network can determine whether a UE is registered to a participating operator network of a selected PLMN ID. The AMF will be configured with identifiers (PLMN IDs) of all participating network operators based on an agreement between the hosting network operator and the corresponding participating network operators. If the UE does not use one of these identifiers, the AMF can be configured to determine that the registration request is invalid. These and other features and examples of indirect network sharing are discussed below with reference to the following figures.

[0026] Figure 1is a diagram of an example overview 100 of one or more implementations described herein. As shown, the overview 100 can include a UE 110, a base station 120, a hosting CN 130, and a participating CN 140. The hosting CN 130 can be a visited PLMN (VPLMN) with respect to the UE 110, and one or more participating CNs 140 can be a home PLMN (HPLMN) with respect to the UE 110. The UE 110 can receive, from the base station 120, PLMN IDs corresponding to the hosting CN 130 and the participating CN 140. The UE 110 can select a PLMN ID based on a PLMN in which the UE 110 subscribes to services. The UE 110 can communicate with the hosting CN 130 based on the selected PLMN ID to perform one or more procedures. The hosting CN 130’s functionality can be identified via different types of interfaces (e.g., interfaces N8, N9, N12, and N16), select, and / or communicate with the functionality of the participating CN 140 to complete the one or more procedures. Examples of such procedures can include an authentication procedure, a registration procedure, a PDU session establishment procedure, and the like. Additional examples of these and many other techniques, features, and implementations are described below with reference to the following drawings.

[0027] Figure 2 is an example network 200 in accordance with one or more implementations described herein. The example network 200 can include UEs 210-1, 210-2, and so on (collectively referred to as “UEs 210,” and individually as “UE 210”), a radio access network (RAN) 220, a core network (CN) 230, an application server 240, an external network 250. Systems and devices of the example network 200 can operate according to one or more communication standards, such as third generation partnership project (3GPP) second generation (2G), third generation (3G), fourth generation (4G) (e.g., long term evolution (LTE)) and / or fifth generation (5G) (e.g., new radio (NR)) communication standards. Additionally, or alternatively, one or more of the systems and devices of the example network 200 can operate according to other communication standards and protocols as discussed herein, including future releases of 3GPP standards or generations (e.g., sixth generation (6G) standards, seventh generation (7G) standards, and the like), Institute of Electrical and Electronics Engineers (IEEE) standards (e.g., wireless metropolitan area networks (WMANs)), and the like.

[0028] As illustrated, UE 210 can comprise a smartphone (e.g., a handheld touchscreen mobile computing device capable of connecting to one or more wireless communication networks). Additionally or alternatively, UE 210 can comprise other types of mobile or non-mobile computing devices capable of wireless communication, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handset, or the like. In some implementations, UE 210 can comprise an Internet of Things (IoT) device (or IoT UE), which can comprise an access layer of a network that is designed to enable a wide range of IoT applications, including smart home and connected home, smart cities, and connected cars, among other applications. An IoT UE can utilize one or more types of technology, such as machine-to-machine (M2M) communication, machine-type communication (MTC), or Internet of Things (IoT) over Public Land Mobile Network (PLMN) technology, neighbor awareness networking (ProSe) or device-to-device (D2D) communication, sensor networks, IoT networks, and the like. Depending on the scenario, M2M or MTC data exchange can be machine- initiated exchange, and IoT networks can comprise interconnected IoT UEs (which can comprise uniquely identifiable embedded computing devices within the Internet infrastructure) with short-lived connections. In some scenarios, an IoT UE can perform background applications (e.g., keep-alive messages, status updates, and the like) to facilitate connectivity of the IoT network.

[0029] UE 210 can communicate with and establish a connection to one or more other UEs 210 via one or more wireless channels 212, each of which can comprise a physical communication interface / layer. The connection can comprise a M2M connection, a MTC connection, a D2D connection, a SL connection, or the like. The connection can involve a PC5 interface. In some implementations, UEs 210 can be configured to discover one another, negotiate wireless resources among one another, and establish a connection among one another without the need for intervention or communication involving RAN node 222 or another type of network node. In some implementations, discovery, authentication, resource negotiation, registration, or the like can involve communication with RAN node 222 or another type of network node.

[0030] The UE 210 can communicate with and establish a connection with a RAN 220, which can involve one or more wireless channels 214-1 and 214-2, each of which can comprise a physical communication interface / layer. In some implementations, the UE can be configured with dual connectivity (DC) as multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC), where a multi-receive and transmit (Rx / Tx) capable UE can use resources provided by different network nodes (e.g., 222-1 and 222-2), which can be connected via a non-ideal backhaul (e.g., where one network node provides NR access, while the other network node provides E-UTRA for LTE or NR for 5G access). The network nodes can be referred to herein as base stations 222. In such scenarios, one network node can operate as a master node (MN) and the other node can operate as a secondary node (SN). The MN and SN can be connected via a network interface, and at least the MN can be connected to the CN 230. In some implementations, a base station (as described herein) can be an example of a network node 222. In some scenarios, the RAN 220 can coordinate with the core network 230 via interfaces 224, 226, and / or 228.

[0031] As shown, the UE 210 can additionally or alternatively connect to an access point (AP) 216 via a connection interface 218, which can include an over-the-air interface that enables the UE 210 to be communicatively coupled with the AP 216. The AP 216 can comprise a wireless local area network (WLAN), a WLAN node, a WLAN terminal point, etc. The connection interface 218 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, and the AP 216 can comprise a wireless fidelity (Wi-Fi ® ) router or other AP. While in Figure 2The AP 216 can not be explicitly depicted, but the AP 216 can be connected to another network (e.g., the Internet) without connecting to the RAN 220 or the CN 230. In some scenarios, the UE 210, the RAN 220, and the AP 216 can be configured to utilize LTE-WLAN aggregation (LWA) technology or LTE WLAN radio level technology integrated with IPsec tunnel (LWIP). LWA can involve the RAN 220 configuring the UE 210 in an RRC CONNECTED state to utilize radio resources of LTE and WLAN. LWIP can involve the UE 210 using WLAN radio resources (e.g., the connectivity interface 218) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) communicated via the connectivity interface 218. IPsec tunneling can include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0032] The RAN 220 can include one or more RAN nodes 222-1 and 222-2 (which are collectively referred to as RAN nodes 222, and individually as RAN node 222) that enable the establishment of a channel 214-1 and a channel 214-2 between the UE 210 and the RAN 220. The RAN nodes 222 can comprise network access points configured to provide radio baseband functions for data and / or voice connectivity between users and a network. As ® The RAN nodes can be E-UTRAN Node Bs (e.g., enhanced Node Bs, eNodeBs, eNBs, 4G base stations, etc.), next generation base stations (e.g., 5G base stations, NR base stations, next generation eNBs (gNBs), etc.). The RAN nodes 222 can include a road side unit (RSU), a transmission reception point (TRxP or TRP), and one or more other types of ground stations (e.g., ground access points). In some scenarios, the RAN nodes 222 can be dedicated physical devices such as macrocell base stations and / or low power (LP) base stations for providing femocells, picocells, and / or the like with smaller coverage areas, smaller user capacity, or the like compared with macrocells. The RAN nodes can be generally referred to herein as base stations 222.

[0033] Some or all or parts of the RAN nodes 222 can be implemented as one or more software entities running on a server computer as part of a virtual network, which can be referred to as a centralized RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In these implementations, the CRAN or vBBUP can enable RAN function splitting, such as a packet data convergence protocol (PDCP) split, where radio resource control (RRC) and PDCP layers can be operated by the CRAN / vBBUP and other layer 2 (L2) protocol entities can be operated by individual RAN nodes 222; a medium access control (MAC) / physical (PHY) split, where RRC, PDCP, radio link control (RLC), and MAC layers can be operated by the CRAN / vBBUP and the PHY layer can be operated by individual RAN nodes 222; or a“lower PHY” split, where RRC, PDCP, RLC, MAC layers, and upper parts of the PHY layer can be operated by the CRAN / vBBUP and lower parts of the PHY layer can be operated by individual RAN nodes 222. This virtualized framework can allow for offloading of processing cores of the RAN nodes 222 or performing other virtualized applications.

[0034] In some implementations, individual RAN nodes 222 can represent individual gNB distributed units (DUs) that are connected to a gNB central unit (CU) via individual F1 or other interfaces. In such implementations, the gNB-DUs can include one or more remote radio heads or radio frequency (RF) front end modules (RFEMs), and the gNB-CU can be operated by a server (not shown) located in the RAN 220 or by a pool of servers, for example, a group of servers configured to share resources, in a similar manner as the CRAN / vBBUP. Additionally, or alternatively, one or more of the RAN nodes 222 can be next generation e Bs (i.e., gNBs), which can provide evolved universal terrestrial radio access (E-UTRA) user and control plane protocol terminations and can be connected to a 5G core network (5GC) 230 through an NG interface.

[0035] Any of the RAN nodes 222 can terminate the air interface protocols and can be the first point of contact for the UEs 210. In some implementations, any of the RAN nodes 222 can perform RAN 220 functions that are not terminated at the base station, such as radio network controller (RNC) functions, such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. The UEs 210 can be configured to communicate with any of the RAN nodes 222 or with other network nodes using Orthogonal Frequency Division Multiplexing (OFDM) communication signals, using various

[0036] In some implementations, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 222 to the UEs 210, while uplink transmissions can utilize a similar approach. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is composed of multiple resource blocks (RBs) in the frequency domain and multiple subframes in the time domain. Each resource block contains multiple subcarriers in the frequency domain and multiple symbols in the time domain, and can be the smallest unit of resources that can be allocated to a UE. There can be several resource blocks in a subframe. The resulting grid can be used to convey various types of data, such as user data, control information, and reference signals, to the UEs. Each element of the time-frequency grid is referred to as a resource element (RE). An RB can contain a number of consecutive REs in the frequency domain and one subframe in the time domain.

[0037] In addition, the RAN nodes 222 can be configured to wirelessly communicate with the UEs 210 and / or with each other through a licensed medium (also referred to as a “licensed spectrum” and / or a “licensed band”) and / or an unlicensed shared medium (also referred to as an “unlicensed spectrum” and / or an “unlicensed band”). The licensed spectrum can correspond to a channel or band of frequencies that is chosen, reserved, regulated, and / or managed by a government agency, such as the Federal Communications Commission (FCC) in the United States, for certain types of wireless activity, such as wireless telecommunications network activity, while the unlicensed spectrum can correspond to one or more bands of frequencies not restricted by the government agency for certain types of wireless activity.

[0038] A physical downlink shared channel (PDSCH) can carry user data and higher layer signaling to the UEs 210. A physical downlink control channel (PDCCH) can carry information about the resources allocated to each UE 210 for the downlink shared channel. The PDCCH can also notify the UEs 210 about the delivery format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. In general, downlink scheduling (e.g., assigning control and shared channel resource blocks to the UEs 210 within a cell) can be performed at any of the RAN nodes 222 based on channel quality information fed back from any of the UEs 210. The downlink resource assignments can be transmitted on the PDCCHs to each of the UEs 210.

[0039] One or more of the techniques described herein can include solutions for indirect network sharing. For example, a UE 210 can receive, from a base station 222, a PLMN ID corresponding to a hosting operator network and at least one participating operator network. The UE 210 can select a PLMN ID of a participating operator network to which the UE 210 is subscribed. The UE 210 can communicate with the hosting operator network based on the PLMN ID of the participating operator network to perform one or more procedures. Examples of such procedures can include an authentication procedure, a registration procedure, a PDU session establishment procedure, and the like. One or more functions of the CN 230 of the hosting operator network can select and communicate with one or more functions of the participating operators to complete the procedures. Numerous other aspects and examples are described herein as well.

[0040] The RAN nodes 222 can be configured to communicate with one another via interface 223. In implementations where the system is an LTE system, the interface 223 can be an X2 interface. In an NR system, the interface 223 can be an Xn interface. The X2 interface can be defined between two or more RAN nodes 222 (e.g., two or more eNBs, or eNBs and gNBs, or gNBs, or combinations of them) that connect to a Evolved Packet Core (EPC) or CN 230, or between two eNBs connecting to an EPC.

[0041] As illustrated, the RAN 220 can be connected (e.g., communicatively coupled) to a CN 230. The CN 230 can comprise a plurality of network elements 232 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UEs 210) connecting to the CN 230 via the RAN 220. In some implementations, the CN 230 can include an evolved packet core (EPC), a 5G CN (5GC), and / or one or more additional or alternative types of CNs. The components of the CN 230 can be implemented in one physical node or in separate physical nodes, including components to read and execute instructions stored on a machine-readable or computer- readable medium (e.g., a non-transitory machine-readable storage medium). In some implementations, network function virtualization (NFV) can be employed to virtualize any or all of the above-described network node roles or functions via executable instructions stored in one or more computer-readable storage media.

[0042] Logical instantiation of the CN 230 can be referred to as a network slice, and logical instantiation of a portion of the CN 230 can be referred to as a network sub-slice. Network Function Virtualization (NFV) architectures and infrastructures can be used to virtualize one or more network functions on physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches, alternatively executed by proprietary hardware. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components / functions.

[0043] As illustrated, the CN 230, application servers 240, and external networks 250 can be connected with each other through interfaces 234, 236, and 238, which can include IP network interfaces. Application servers 240 can comprise one or more server devices or network elements (e.g., virtual network functions (VNFs)) that provide applications that use IP bearer resources with the CN 230 (e.g., General Packet Radio Service (GPRS) PS domain, LTE PS data services, etc.). The application servers 240 can also or alternatively be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, Push-to-Talk (PTT) sessions, group communication sessions, social networking services, etc.) for UEs 210 via the CN 230. Similarly, external networks 250 can comprise one or more of various networks, including the Internet, thus providing mobile

[0044] Figure 3is a diagram of an example network architecture 300 in accordance with one or more implementations described herein. As shown, the example network architecture 300 can include a UE 210, a RAN 220, a CN 230, and an external network 250. The RAN 220 can include a base station 222 and / or one or more other types of APs 216. The CN 230 can include an Access and Mobility Management Function (AMF) 310, a Session Management Function (SMF) 320, a User Plane Function (UPF) 330, a Policy Control Function (PCF) 340, an Application Function (AF) 350, and a Unified Data Management (UDM) function 360. The CN 230 can include one or more additional or alternative functions, some of which are described herein with reference to other figures.

[0045] The AMF 310, SMF 320, UPF 330, PCF 340, AF 350, and UDM function 360 can be functions of the CN 230 and can be implemented by one or more servers in a centralized or distributed networking environment, which can include one or more network virtualization functions (NVF). The external network 250 can include a data network that includes one or more application servers, the Internet, another telecommunications network, and / or another type of network. In some implementations, the network architecture 300 can include additional, alternative, and / or different arrangements of functions, interfaces, or other features than those shown in FIG. 3. Figure 3

[0046] The AMF 310 can communicate with the RAN 220 via an N2 interface and with the UE 210 via an N1 interface. The AMF 310 can manage authentication, registration, and other functions related to UEs 210 accessing a telecommunications mobile network. The AMF 310 can handle handovers, paging, and other functionality related to mobility and communication of UEs 210. The AMF 310 can also provide security functionality for authenticating and authorizing UEs 210. The AMF 310 can communicate with the SMF via an N11 interface, with the PCF 340 via an N15 interface, and with the UPF 330 via an N4 interface.

[0047] As described below with reference to the figures, the AMF 310 can enable indirect network sharing by communicating with one or more of the UE 210, the base station 222, one or more functions of the CN 230 that host an operator network, and one or more functions of the CN 230 that participate in an operator network. This can include performing or otherwise participating in the performance of one or more procedures. Examples of such procedures can include an authentication procedure, a registration procedure, a PDU session establishment procedure, and the like.

[0048] ​The SMF 320 can provide PDU session management. To do so, the SMF 320 can collect information related to managing PDU sessions from various network components (e.g., UPF 330, PCF 340, AF 350, etc.) and control or orchestrate the network components based on requests from the AMF 310. The SMF 320 can be responsible for establishing, maintaining, and terminating user sessions in the CN 230. The SMF 320 can manage user plane (UP) resources and interact with the UPF 330 to ensure that data packets are correctly routed and forwarded.

[0049] The SMF 320 can receive a PDU session establishment and / or session modification request from the UE 210. The request can include an indication to assist in identifying the UL PDU set. The request can also indicate a real-time transport protocol (RTP) header extension and / or a transport layer protocol corresponding to the requested assistance. The SMF 320 can determine whether a protocol description corresponding to the requested assistance has been provided by the PCF 340 and / or the AF 350. The protocol description can include information about the RTP header extension and / or other protocol features used by the application and, in turn, enable the UE 210 to identify the PDU set from the UL packets. The protocol description can also or alternatively include information about one or more other types of transport layer protocols and / or protocol features used by the application, such that the UE 210 can identify the PDU set from the UL packets based on how the application uses the transport layer protocol.

[0050] The SMF 320 can include a PDU set protocol description, a QoS profile and parameters, a quality flow identifier (QFI), and / or one or more additional or alternative types of information to, for example, enable UL PDU sets for a given application or service to be properly identified. For example, the AF 350 can include protocol descriptions for different types of applications and services supported by the network, such as XR applications and / or XRM applications and services. The protocol descriptions can include information that enables the UE 210, base stations 222, and other devices to identify PDU sets within a service data flow. The SMF 320 can receive the protocol descriptions from the AF 350 via the PCF 340 and can provide the protocol descriptions to the UE 210, the RAN 220, the UPF 330, and / or one or more of the devices or entities described herein. In some implementations, the protocol descriptions provided by the SMF 320 can be based at least in part on rules received from the PCF 340.

[0051] UPF 330 can communicate with RAN 220 via an N3 interface, with PCF 340 via an N7 interface, and with SMF 320 via an N11 interface, which can be routed through RAN 220. UPF 330 can operate as a connection point between RAN 220 and an external data network 250 (e.g., the Internet, another telecommunication network, and / or the like) for a PDU session via an interface N6. UPF 330 can also provide support for packet routing, forwarding, and inspection. UPF 330 can provide user plane rule enforcement, QoS handling, UL / DL rate enforcement, and service data flow (SDF) to QoS flow mapping. UPF 330 can communicate with SMF 320 via an N4 interface and with RAN 220 via an N3 interface.

[0052] PCF 340 can provide policy control and flow-based control functionality. PCF 340 can include and provide policy charging and control (PCC) rules for application, data flow, PDU set, gating, QoS, and / or the like to SMF 320. PCF 340 can also provide access and mobility management policies to AMF 310. PCF 340 can communicate with SMF 320 via an N7 interface and with AMF 310 via an N15 interface.

[0053] UE 210 can transmit and receive information to and from RAN 220 via an access stratum (AS) interface. UE 210 can also transmit and receive PDU set information (e.g., a protocol description of PDU set information) from SMF 320. QoS flow profiles and PDU set protocol descriptions can also be configured to RAN 220 and UE 210 from SMF 320. Each QoS flow profile and / or PDU set protocol description can be associated with a set of QoS parameters, which can be part of a QoS profile stored by RAN 220 and updated by AMF 310. Examples of QoS parameters can include resource type, packet delay budget (PDB), quality flow identifier (QFI), packet error rate (PER), mean window, and / or the like. AMF 310 can provide QoS rules to UE 210 during a PDU session via a non-access stratum (NAS) protocol or interface.

[0054] The AF 350 can include network functions configured to manage traffic and QoS allocation through interaction with policy elements. The AF 350 can expose an application layer for interaction with 5G network functions (NFs) and network resources. The AF 350 can reside in the control plane of a 5G service-based architecture (SBA), and the AF 350 can be used to access a network repository function (NRF) to retrieve resources, interact with the PCF 340 via an N5 interface, implement policy control, route traffic for applications, and provide application services to subscribers.

[0055] The UDM node 360 can handle subscription-related information to support handling of communication sessions. The UDM node 360 can store subscription data for the UE 210, which can be communicated between the UDM node 360 and the AMF 310 via an N8 interface (not shown). The UDM node 360 can communicate with the SFM 320 via an N10 interface. The UDM node 360 can include two parts, an application function entity (FE) and a unified data repository (UDR). The UDR can store subscription data and policy data for the UDM node 360 and the PCF 340, as well as structured data for exposure and application data, including packet flow descriptions (PFDs) for application detection and requested information. The UDM node 360 can include a UDM-FE, which can process credentials, perform location management, subscription management, and the like. The UDM-FE can also access subscription information stored in the UDR and perform authentication credential handling, user identification handling, access authorization, registration / mobility management, and subscription management.

[0056] The network slice selection function (NSSF) 370 can help implement network slicing to enhance the performance of network functions and procedures. Network slicing can utilize software-defined networking (SDN) technology, network function virtualization (NFV) technology, and the like, to use physical network infrastructure (e.g., physical components of the UE 210, the RAN 220, and the like) to create multiple virtual instances of a network scenario corresponding to a target network procedure and cause different portions of each network slice to perform (e.g., multiplex) those network procedures such that, when the results from each portion are combined or otherwise processed (e.g., demultiplexed), the optimized performance of the procedure is achieved, which is equivalent to the procedure being completed as a whole. Thus, in some scenarios, network slicing can include network architectures and technologies that can achieve device and / or network performance enhancements or optimizations by creating multiple logical instances of a given network scenario and causing different portions of a network process, function, or procedure to be performed by different instances of the network scenario using physical infrastructure resources.

[0057] Each network slice can be an independent end-to-end 5G network (which can be logical or physical). Each network slice can span multiple or all network functions and can be isolated from other slices.Figure 3 Several components and functions of network architecture 300 can have specific behaviors related to network slice configuration. For example, UDM 360 can store subscriptions of users (e.g., of UE 210), such as whether the user has purchased a subscription to a high definition (HD) streaming slice. PCF 340 can provide rules to UE 210 to identify which slice to send which traffic via. For slice-related configuration, AMF 310 can act as a single point of contact with UE 210. UE 210 can establish slice-specific sessions and route packets over the appropriate slice. Independence of network slices can allow customization of RAN 220 and / or CN 230 configuration per network slice. From an AS perspective, slice traffic can be part of separate DRBs. From a NAS perspective, slice traffic can be part of separate PDU sessions.

[0058] NSSF 370 can help enable network architecture 300 to implement network slice selection assistance information (NSSAI) and single-NSSAI (S-NSSAI) for efficient and dynamic network slicing. NSSAI can include a set of parameters that identify and describe a network slice. Examples of these parameters can include a slice-differentiator (SD), which can be a globally unique identifier, and a slice-service type (SST), which can indicate a particular service or application type associated with the network slice. NSSF 370 participating in an operator network can use the N22 interface to communicate with AMF 310.

[0059] S-NSSAI can be an extension of NSSAI, specifically designed to support single network slice selection. S-NSSAI can provide additional information to assist UEs 210 and the network in selecting the most suitable network slice based on the context and requirements of a communication session. S-NSSAI can involve one or more NSSAI, each containing a pair of SD and SST. Multiple NSSAI can be included to represent a set of available network slices, or to provide fallback options if a primary slice is not available.

[0060] When UE 210 initiates a connection with a 5G network, UE 210 can include S-NSSAI information in an initial signaling message (e.g., a registration request). The S-NSSAI can reflect desired network slice preferences. The network can match the S-NSSAI to available network slice instances and select the most suitable slice that meets one or more corresponding requirements. The selection process can consider one or more factors, such as network resources, quality of service (QoS) policies, and network conditions. S-NSSAI can also participate in dynamic switching between network slices.

[0061] Figure 4is a diagram of an example 400 of a hosting operator network and a participating operator network in accordance with one or more implementations described herein. As shown, the example 400 can include a UE 210, a RAN 220, a hosting operator network 410, a participating operator network 420, an authentication server function (AUSF) 430, and other network functions 310-340 and 370. One or more of the functions of the example 400 can correspond to the functions described above with reference to Figure 3 The one or more functions described. Additionally, some of the functions of the example 400 can be configured to operate with respect to the UE 210 as a visited network function or a home network function or with respect to the UE 210 as a visited network function or a home network function. For example, the NSSF 370 of the hosting operator network 410 can operate with respect to the UE 210 as a V-NSSF 370, while the NSSF 370 of the participating operator network 420 can operate with respect to the UE 210 as a H-NSSF 370. The RAN 220 can include a base station 222 or another type of access network node. The network functions can communicate with each other using the specified interfaces (e.g., interface N8, interface N9, interface N12, interface N16, etc.). Each interface can be a reference point for communication between the indicated functions.

[0062] The AUSF 430 can help implement authentication and authorization procedures. When a subscriber attempts to connect to a 5G network, the AUSF 430 can help verify the subscriber identity to ensure that the UE 210 has authorization to access the network. The AUSF 430 can interact with several other network functions. For example, the AUSF 430 can communicate with the AMF 310 via the N12 interface to manage subscriber mobility and handover procedures, and with the UDM function 360 to manage subscriber data and profiles. The AUSF 430 can also help provide robust security features, including encryption and authentication mechanisms, to prevent unauthorized access and data breaches.

[0063] The base station 222 can broadcast a plurality of PLMN IDs, including a PLMN ID of a hosting operator network and a PLMN ID of a participating operator network. Examples of PLMN IDs that can be involved in indirect network sharing can include a serving PLMN ID, a home PLMN (HPLMN) ID, and a selected PLMN ID. The serving PLMN ID can include a PLMN ID supported by the AMF 310 of the hosting operator network. The home PLMN ID can be derived from a subscription permanent identifier (SUPI), which can be associated with a participating operator network (e.g., a home PLMN) of the UE 210. The selected PLMN ID can be a PLMN ID selected by the UE 210 from the broadcast information base station 222, which can be associated with the participating operator network.

[0064] In one example, the UE 210 can be subscribed to a first operator network corresponding to a HPLMN of the UE 210. The second operator network can correspond to a hosting or serving PLMN by providing the base station 222. The third operator network can correspond to a participating operator network with respect to the second (or hosting) operator network. The third operator network can have an agreement with the second operator network such that the UE 210 can connect to the third operator network via the second operator network using the base station 222. The third operator network can also have an agreement with the first operator such that the UE 210 can connect to the third operator network as if the third operator network is the HPLMN of the UE 210. In this scenario, the UE 210 can select a PLMN of a participating operator network, in which case the selected PLMN is actually the PLMN of the third operator network.

[0065] The participating operator network can be treated as a HPLMN, and the hosting operator network can be treated as a visited PLMN (VPLMN). The serving AMF 310 can be an AMF in the CN 230 of the hosting operator network. The serving AMF 310 can select a visited SMF (V-SMF) 320 in the hosting operator network. The V-SMF 320 in the hosting operator network (as a control plane (CP) network function (NF)) can support a PLMN ID representing the participating operator network. The CP NFs of the hosting operator network can register a NF profile including the PLMN ID representing the participating operator network.

[0066] Accordingly, the PLMN ID of the participating operator network can be used to discover NFs of the hosting operator network. The UE 210 can select the PLMN ID representing the participating operator network of the base station 222. The UE 210 can not be aware of the PLMN ID representing the hosting operator network. The network (e.g., the AMF 310, an authentication server function (AUSF) 430, and the UDM 360) and the UE 210 can use the same serving network (SN) identifier (SN ID) of the serving network to derive keys during authentication. Accordingly, the serving network identifier ID used by the UE 210, the AMF 310, the AUSF, and the UDM 360 in the primary authentication can be set to the PLMN ID of the selected participating operator network. The HPLMN can include the PLMN ID representing the participating operator network in the equivalent PLMN list in the indirect network sharing and communicate it to the UE 210.

[0067] The UE 210 can be subscribed to a participating operator network (e.g., which can be the HPLMN of the UE 210). The UE 210 can select a PLMN ID representing the participating operator network. The selected PLMN can be the HPLMN ID, an Equivalent HPLMN (EHPLMN) ID in an EHPLMN list stored on a Universal Subscriber Identity Module (USIM), or a PLMN ID in an Equivalent PLMN (EPLMN) list provided by the HPLMN and stored in a non-volatile memory of the UE 210. The coverage of the operator can not be much, so the participating operator networks can cooperate with each other such that roaming will not be applied. Such networks can be referred to as EPLMNs or EHPLMNs.

[0068] The UE 210 with a subscription from a participating operator network can select a PLMN ID of the participating operator network via the base station 222. During a registration procedure, the UE 210 can include a service single-network slice selection assistance information (S-NSSAI) of the participating operator network in a requested NSSAI. The serving AMF 310 (of the hosting operator network) can determine a S-NSSAI of the hosting operator network (e.g., a VPLMN S-NSSAI) based on a S-NSSAI mapping configuration between the hosting operator network and the participating operator network. The serving AMF 310 can obtain the S-NSSAI mapping from a network slice selection function (NSSF) 370 of the hosting operator network.

[0069] The serving AMF 310 can also check whether the base station 222 supports a corresponding S-NSSAI of the hosting operator network. If none of the corresponding S-NSSAIs of the hosting operator network are supported, the serving AMF 310 can reject the registration request. The AMF 310 of the hosting operator network can determine which existing cause value to use based on a configuration agreement between the hosting operator network and the participating operator network. The cause values as referred to herein can include cause #13 - roaming not allowed in this tracking area; cause #15 - no suitable cell in tracking area; cause #12 - tracking area not allowed; cause #62 - no available network slice; cause #65 - maximum number of PDU sessions reached; cause #67 - insufficient resources for specific slice and DNN.

[0070] Otherwise, the serving AMF 310 can continue the registration procedure and / or can transmit the allowed NSSAI, the partially allowed NSSAI, the rejected S-NSSAI, and the configured NSSAI to the UE 210, which only includes the S-NSSAI of the hosting operator network participating in the operator network. During the UE configuration update procedure, the serving AMF 310 hosting the operator network can determine the S-NSSAI of the hosting operator corresponding to the S-NSSAI of the participating operator network and can transmit the NSSAI (e.g., the allowed NSSAI, the partially allowed NSSAI, the rejected NSSAI, the partially rejected NSSAI, and the configured NSSAI) to the UE 210 including only the S-NSSAI representing the PLMN ID of the participating operator network.

[0071] During the PDU session establishment procedure, the UE 210 can include the S- NSSAI of the participating operator network in the PDU session establishment request. Upon receiving the S-NSSAI of the participating operator network from the UE 210, the serving AMF 310 can determine the S-NSSAI of the hosting operator network to be used as the S-NSSAI belonging to the allowed NSSAI using the list of the S-NSSAI of the hosting operator network corresponding to the S-NSSAI of the participating operator (e.g., VPLMN S-NSSAI). The serving AMF 310 can use the VPLMN S-NSSAI and the HPLMN S-NSSAI for the PDU session establishment procedure.

[0072] The AMF 310 of the hosting operator network can determine the S-NSSAI of the hosting operator network corresponding to the S-NSSAI of the participating operator network included in the requested NSSAI, and the AMF 310 of the hosting operator network can provide the network slice related information (e.g., the configured NSSAI, the allowed NSSAI, the partially allowed NSSAI, the rejected NSSAI, and the partially rejected NSSAI including only the S-NSSAI representing the PLMN ID of the participating operator network). If none of the S-NSSAI of the hosting operator network corresponding to the S-NSSAI of the participating operator network included in the requested NSSAI is allowed, the AMF 310 of the hosting operator network can transmit the registration message (e.g., “no available network slice”).

[0073] The AMF 310 of the hosting operator network can determine the S-NSSAI of the hosting operator network that corresponds to the S-NSSAI of the participating operator network that is included in the requested NSSAI, and the AMF 310 of the hosting operator network can provide the network slice related information (e.g., configured NSSAI, allowed NSSAI, partially allowed NSSAI, rejected NSSAI, and partially rejected NSSAI that includes only S-NSSAI representing the PLMN ID of the participating operator network). In the case of indirect network sharing, if none of the S-NSSAI of the hosting operator network that corresponds to the S-NSSAI of the participating operator network that is included in the requested NSSAI is allowed, the AMF 310 of the hosting operator network can transmit a registration reject message (e.g., “no available network slice”).

[0074] During a UE configuration update (UCU) procedure, in the case of indirect network sharing, the AMF 310 of the hosting operator network can determine the S-NSSAI of the hosting operator network that corresponds to the S-NSSAI of the participating operator network, and the AMF 310 of the hosting operator network can transmit the NSSAI (e.g., allowed NSSAI, partially allowed NSSAI, rejected NSSAI, partially rejected NSSAI, and configured NSSAI) that includes only S-NSSAI representing the PLMN ID of the participating operator network UE 210.

[0075] During a protocol data unit (PDU) procedure, the UE 210 can include S-NSSAI representing the PLMN ID of the participating operator network. The AMF 310 of the hosting operator network can determine the S-NSSAI of the hosting operator network that corresponds to the S-NSSAI provided by the UE 210 of the participating operator network, and the AMF 310 of the hosting operator network can use the S-NSSAI of the hosting operator network. When the UE 210 is not allowed to access the selected PLMN associated with the participating operator network, the AMF 310 of the hosting operator network can transmit a registration reject message with an existing cause value, and the AMF 310 of the hosting operator network can determine to use the existing cause value that is configured based on an agreement between the hosting operator network and the participating operator network.

[0076] Figure 5 is an example process 500 for indirect network sharing in accordance with one or more implementations described herein. As shown, process 500 can be implemented by a UE 210, a base station 222, a hosting operator network 410, and one or more participating operator networks 420. In some implementations, some or all of process 500 can be performed by one or more other systems or devices, including Figure 2 to Figure 4one or more devices in the apparatus) are performed. Additionally, process 500 can include one or more operations fewer, additional, differently ordered, and / or arranged than those shown in FIG. 5. In some implementations, some or all of the operations of process 500 can be performed independently, sequentially, concurrently, and / or the like. Thus, the techniques described herein are not limited to the specific order and / or sequence of operations illustrated in FIG. 5. Figure 5 one or more operations fewer, additional, differently ordered, and / or arranged than those shown in FIG. 5. In some implementations, some or all of the operations of process 500 can be performed independently, sequentially, concurrently, and / or the like. Thus, the techniques described herein are not limited to the specific order and / or sequence of operations illustrated in FIG. 5. Figure 5 As mentioned herein, the serving AMF can include the AMF 310 hosting the operator network 410.

[0077] As shown, process 500 can include communicating a PLMN ID to the UE 210 (at 510). The PLMN ID can be communicated by the base station 222 and / or the hosting operator network 410. For example, the hosting operator network 410 can provide the PLMN ID to the base station 222, and the base station 222 can provide the PLMN ID to the UE 210. The PLMN ID can include a PLMN ID of the hosting operator network and one or more PLMN IDs of participating operator networks. The PLMN ID can be supported by the AMF 310 of the CN 230 of the hosting operator network. The base station 222 can broadcast a plurality of PLMN IDs, including the PLMN ID of the hosting operator network and the PLMN IDs of participating operator networks. Examples of PLMN IDs that can be involved in indirect network sharing can include a serving PLMN ID and a home PLMN (HPLMN) ID. The serving PLMN ID can include a PLMN ID supported by the AMF 310 of the hosting operator network. The home PLMN ID can be derived from a subscription permanent identifier (SUPI), which can be associated with a participating operator network (e.g., a home PLMN) of the UE 210.

[0078] Process 500 can include the UE 210 selecting a PLMN ID associated with a participating operator network from the PLMN IDs (at 520). The UE 210 can also determine an S-NSSAI associated with the selected PLMN ID. The UE 210 can select the PLMN ID based on the UE 210 subscribing to the participating operator network. The selected PLMN ID can be a home PLMN (HPLMN) of the UE 210. Process 500 can include the UE 210 responding to the shared network using the selected PLMN ID and the S-NSSAI (at 530). As mentioned herein, the shared network or shared RAN can include the hosting operator network. The UE 210 can communicate a registration request message, which can include an indication that the UE 210 has requested to register to the participating operator network and become connected to the participating operator network.

[0079] The process 500 can include the serving AMF 310 mapping the S-NSSAI participating in the operator network 420 and performing a registration procedure (block 540). The AMF 310 can map the S-NSSAI participating in the operator network 420 to one or more S-NSSAIs hosted by the operator network 410. The AMF 310 can also determine whether the UE 210 is subscribed to the participating operator network associated with the selected PLMN ID.

[0080] The selected PLMN ID can be a PLMN ID selected by the UE 210 from broadcast information base station 222, which can be associated with a participating operator network. The participating operator network can be treated as a HPLMN, and the hosting operator network can be treated as a visited PLMN (VPLMN). The serving AMF 310 can be an AMF in the CN 230 of the hosting operator network. The serving AMF 310 can select a visited SMF (V-SMF) 320 in the hosting operator network. The V-SMF 320 in the hosting operator network (as a control plane (CP) network function (NF)) can support a PLMN ID representing the participating operator network. The CP NF of the hosting operator network can register a NF profile including the PLMN ID representing the participating operator network.

[0081] The process 500 can include the AMF 310 of the hosting operator network transmitting a registration response to the UE 210 (at 550). The registration response can include an indication of whether the UE has been registered. When the UE 210 is subscribed to the participating operator network, the registration response message can indicate that the UE 210 is registered. When the UE 210 is not subscribed to the participating operator network, the registration response message can indicate that the UE 210 is not registered.

[0082] The process 500 can include the serving AMF 310 of the hosting operator network 410 performing a UE configuration update (UCU) procedure (at 560). This can include the serving AMF 310 determining one or more S-NSSAIs of the hosting operator network 410 and / or the participating operator network 420 based on the selected PLMN ID and / or S-NSSAI from the UE 210. Examples of S-NSSAI can include an allowed NSSAI, a partially allowed NSSAI, a rejected NSSAI, a partially rejected NSSAI, and a configured NSSAI of the hosting operator network 410 and / or the participating operator network 420.

[0083] The process 500 can include the UE 210 transmitting a PDU session establishment request to the AMF 310 of the hosting operator network 410 (at 570). The PDU session establishment request can include one or more S-NSSAIs of the participating operator network 420. Examples of S-NSSAIs can include allowed NSSAI, partially allowed NSSAI, rejected NSSAI, partially rejected NSSAI, and configured NSSAI. The UE 210 can determine which type of S-NSSAI is appropriate for the PDU session establishment request. In some implementations, the UE 210 can transmit the PDU session establishment request using any S-NSSAI received from the hosting operator network 410.

[0084] The process 500 can include the hosting operator network 410 communicating with the participating operator network 420 to establish a PDU session (at 580). The AMF 310 of the hosting operator network 410 can map S-NSSAIs of the participating operator network 420 (e.g., one or more HPLMN S-NSSAIs) to S-NSSAIs of the hosting operator network 410 (e.g., one or more VPLMN S-NSSAIs). The PDU session establishment procedure can include the AMF 310 of the hosting operator network 420 selecting CN functions according to a selected PLMN ID of the participating operator network 410. The AMF 310 of the hosting operator network 410 can select the CN functions based on the home routed roaming architecture principles as described herein. For example, the serving AMF 310 can select the SMF 320 of the participating operator network 420. In doing so, the AMF 310 of the hosting operator network 410 can select the SMF 320 based at least in part on UE location information. The AMF 310 of the hosting operator network 410 can also select a V-SMF 320 in its own CN 230 during the PDU session establishment procedure. Although not shown, the AMF 310 of the hosting operator network 410 and / or the AMF 310 of the participating operator network 420 can transmit a message or notification to the UE 210 that the PDU session has been established when establishing the PDU session.

[0085] Figure 6 is a diagram of an example 600 of a session management function (SMF) interface between a hosting operator network 410 and a participating operator network 420, in accordance with one or more implementations described herein.

[0086] As shown, example 600 can include AMF 310, SMF 320, and / or the like. One or more of the functions of example 600 can correspond to one or more of the functions described above with reference to the figures described herein. Additionally, some of the functions of example 600 can be configured to operate as a visited network function or a home network function with respect to UE 210 or to operate as a visited network function or a home network function with respect to UE 210. For example, SMF 320 hosting operating network 410 can operate as a V-SMF 320 with respect to UE 210, while SMF 320 of participating operating network 420 can operate as a H-SMF 320 with respect to UE 210. The network functions can communicate with each other using the specified interfaces (e.g., interface N11, interface N16, interface N16a, interface N38, and / or the like). Each interface can be a reference point for communication between the indicated functions.

[0087] In an indirect network sharing deployment, the N16 interface can be used between a visited SMF (V-SMF) 320 of a hosting operator network and a SMF 320 of a participating operator network. The N16 interface can be a reference point between a V-SMF and a home SMF 320 (H-SMF) in a home routed (HR) roaming case, or can be a reference point between a V-SMF 320 (in a network of a hosting operator) and a H-SMF (in a network of a participating operator). The N16a interface can be a reference point between a SMF 320 and an I-SMF 320. The N38 interface can be a reference point between a direct SMF 320 (I-SMF) or a V-SMF 320. The I-SMF 320 can help manage UE sessions as the UE 210 moves between different SMF service areas. The AMF can use the N11 interface as a reference point to communicate with a V-SMF 320. As shown, a network SMF interface (Nsmf) can be used to identify, access, and communicate with different network slices of a communication session. The Nsmf interface can be configured between a V-SMF 320 and a H-SMF 320 and can include interfaces N16, N16a, and / or N38.

[0088] Figure 7is a diagram of an example 700 of a network slice selection function (NSSF) interface between a hosting operator network 410 and a participating operator network 420 according to one or more implementations described herein. As shown, example 700 can include an AMF 310, an NSSF 370, a network data analytics function (NWDAF) 710, an SMF 320, and / or the like. One or more of the functions of example 700 can correspond to one or more functions described above with reference to the various figures described herein. Additionally, some of the functions of example 700 can be configured to operate with respect to a UE 210 as a visited network function or a home network function or with respect to the UE 210 as a visited network function or a home network function. For example, the NSSF 370 of the hosting operator network 410 can operate with respect to the UE 210 as a V-NSSF 370, while the NSSF 370 of the participating operator network 420 can operate with respect to the UE 210 as a H-NSSF 370. The RAN 220 can include a base station 222 or another type of access network node. The network functions can communicate with each other using the indicated interfaces (e.g., interface N22, interface N31, interface N34, and / or the like). Each interface can be a reference point for communication between the indicated functions.

[0089] The NWDAF 710 can be configured to provide analytics functions in the network for automation or reporting, addressing major customization interface or format challenges. The NWDAF 710 can collect and process statistics, metrics, and events from 5G network functions. The NWDAF 710 can retrieve management statistics from an operations, administration, and maintenance (OAM) system, provide network function discovery and identification, and perform machine learning (ML) modeling, and help develop ML models based on collected statistics.

[0090] During a registration procedure, a requested network slice selection function (NSSF) (including S-NSSAIs of the participating operator network) can be received from the UE 210. After receiving the registration request including the above information, the serving AMF 310 can determine the corresponding S-NSSAI (e.g., VPLMN S-NSSAI) of the hosting operator network based on the S-NSSAI mapping configuration between the hosting operator network and the participating operator network, or can obtain the S-NSSAI mapping from the NSSF 370 of the hosting operator network.

[0091] This may involve information elements (IEs) and / or parameters, such as the esNssaiForMapping and requestMapping attributes in the SliceInfoForRegistration data. In the case of indirect network sharing, the esNssaiForMapping IE may include the S-NSSAI of the HPLMN or EHPLMN. In the case of indirect network sharing, a requestMapping IE may exist, and it may be set to true by the service AMF of the managed operator network to retrieve the S-NSSAI of the managed operator. In this case, the NSSAI in the sNssaiForMapping IE may include the S-NSSAI of the participating operator network. The NSSF 370 of the participating operator network can communicate with the AMF 310 of the managed operator network using the N22 interface, with the NSSF 370 of the managed operator network using the N31 interface, with the Network Data Analysis Function (NWDAF) 710 of the managed operator network using the N34 interface, and with the SMF 320 of the managed operator network using another interface.

[0092] Figure 8 This is a diagram illustrating an example process 800 for real-time accurate ionospheric correction according to one or more specific embodiments described herein. As shown, process 800 can be implemented by I&D server 280. In some embodiments, some or all of process 800 can be implemented by one or more other systems or devices (including...). Figure 2 The process is performed by one or more of the devices. Additionally, process 800 may include processes relative to... Figure 8 The examples shown include one or more operations that are fewer in number, additional, differently ordered, and / or arranged. In some specific implementations, some or all of the operations of process 800 may be performed independently, sequentially, or simultaneously with one or more other operations of process 800. Therefore, the techniques described herein are not limited to those described herein. Figure 8 The number, sequence, arrangement, timing, etc. of the operations or processes described.

[0093] As shown, process 800 can include generating and / or communicating, to a base station of a host operator network, a plurality of public land mobile network (PLMN) identifiers (IDs) including at least one PLMN ID of the host operator network and at least one PLMN ID of a participating operator network (block 810). Process 800 can include receiving and / or processing, from a user equipment (UE), information including at least one PLMN ID of the participating operator network (block 820). Process 800 can include selecting and / or determining, based on the at least one PLMN ID of the participating operator network, at least one core network function of the participating operator network (block 830). One or more of the examples described herein can also or alternatively be part of process 800.

[0094] Figure 9 is a diagram illustrating an example of components of a device in accordance with one or more implementations described herein. In some implementations, device 900 can include application circuitry 902, baseband circuitry 904, RF circuitry 906, front-end module(s) (FEMs) 908, one or more antennas 910, and power management circuitry (PMC) 912, coupled together as shown in the example of Figure 9. In some implementations, device 900 can include fewer elements (e.g., a RAN node can not utilize application circuitry 902, but rather can include a processor / controller to process

[0095] Application circuitry 902 can include one or more application processors. For example, application circuitry 902 can include a single-core or multi-core processor(s) such as one or more single-threaded or multi-threaded processors or cores. Processors of

[0096] The baseband circuitry 904 can include circuitry such as, but not limited to, one or more single-core or multi-core processors, and / or one or more hardware or firmware components known as a multimedia integrated circuit (IC). The baseband circuitry 904 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 906 and to generate baseband signals for a transmit signal path of the RF circuitry 906. The baseband processing circuitry 904 can interface with the application circuitry 902 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 906. For example, in some implementations, the baseband circuitry 904 can include a 3G baseband processor 904A, a 4G baseband processor 904B, a 5G baseband processor 904C, or other baseband processor(s) 904D for other existing generations, generations in development or to be developed in the future (e.g., 5G, 6G, 7G, etc.). The baseband circuitry 904 (e.g., one or more of the baseband processors 904A-D) can handle various radio control functions, implementing the radio control functions in accordance with a new radio (NR) standard. In other implementations, some or all of the functionality of the baseband processors 904A-D can be included in modules stored in the memory 904G and executed via a Central Processing Unit (CPU) 904E. The radio control functions can include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some implementations, modulation / demodulation circuitry of the baseband circuitry 904 can include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functionality. In some implementations, encoding / decoding circuitry of the baseband circuitry 904 can include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functionality. The implementations of the modulation / demodulation and encoder / decoder functionality are not limited to these examples and can include other suitable functionality in other implementations.

[0097] In some implementations, the memory 904G can receive and / or store information and instructions for indirect network sharing. The UE 210 and / or the baseband circuitry 904 can receive, from the base station 222, a PLMN ID corresponding to the hosting operator network 410 and at least one participating operator network 420. The UE 210 can select a PLMN ID of a participating operator network 420 and communicate with the hosting operator network 410 based on the PLMN ID of the participating operator network 420 to perform one or more procedures. Examples of such procedures can include an authentication procedure, a registration procedure, a protocol data unit (PDU) session establishment procedure, etc. The AMF 310 of the hosting operator network 410 can select one or more functions of the hosting operator network 420 and the participating operator network 420 to complete these procedures. These and many other features and examples are described herein.

[0098] In some implementations, the baseband circuitry 904 can include one or more audio digital signal processors (DSP) 904F. The audio DSP(s) 904F can be hardware or software-f aced implementations configured to process audio signals. In some implementations, the audio DSP(s) 904F can include elements for compression / decompression and echo cancellation, among other things, and can include other suitable processing elements in other implementations. In some implementations, components of baseband circuitry 904 can be combined in a single chip or set of chips with other components of wireless device 800 or implemented as a separate element.

[0099] In some implementations, the baseband circuitry 904 can provide for communication compatible with one or more radio technologies. For example, in some implementations, the baseband circuitry 904 can support communication with a NG-RAN, an evolved universal terrestrial radio access network (EUTRAN), or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN), etc. Implementations in which the baseband circuitry 904 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.

[0100] The RF circuitry 906 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various implementations, the RF circuitry 906 can include switches, filters, amplifiers, etc. to facilitate the communication with wireless networks. RF circuitry 906 can include a receive signal path, which can include circuitry to down-convert and filter received RF signals and provide baseband signals to the baseband circuitry 904. RF circuitry 906 can also include a transmit signal path, which can include circuitry to up-convert and filter baseband signals provided by the baseband circuitry 904 and provide RF output signals to FEM circuitry 908 for transmission.

[0101] In some implementations, the receive signal path of the RF circuitry 906 can include mixer circuitry 906A, amplifier circuitry 906B and filter circuitry 906C. In some implementations, the transmit signal path of the RF circuitry 906 can include filter circuitry 906C and mixer circuitry 906A. The RF circuitry 906 can also include synthesizer circuitry 906D for synthesizing a frequency for use by the mixer circuitry 906A of the receive signal path and the transmit signal path. In some implementations, the mixer circuitry 906A of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry 908 based on the synthesized frequency provided by synthesizer circuitry 906D. The amplifier circuitry 906B can be configured to amplify the down-converted signals, and the filter circuitry 906C can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals can be provided to the baseband circuitry 904 for further processing. In some implementations, the output baseband signals can be zero-frequency baseband signals, although this can not be a requirement. In some implementations, the mixer circuitry 906A of the receive signal path can include passive mixers, although the scope of the implementations is not limited in this respect.

[0102] In some implementations, the mixer circuitry 906A of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 906D to generate RF output signals for the FEM circuitry 908. The baseband signals can be provided by the baseband circuitry 904 and can be filtered by filter circuitry 906C. In some implementations, the mixer circuitry 906A of the receive signal path and the mixer circuitry 906A of the transmit signal path can include two or more mixers and can be arranged for quadrature downconversion and upconversion, respectively. In some implementations, the mixer circuitry 906A of the receive signal path and the mixer circuitry 906A of the transmit signal path can include two or more mixers and can be arranged for image rejection in some implementations, the mixer circuitry 906A of the receive signal path and the mixer circuitry 906A of the transmit signal path can be arranged for direct downconversion and direct upconversion, respectively. In some implementations, the mixer circuitry 906 of the receive signal path and the mixer circuitry 906A of the transmit signal path can be configured for super-heterodye operation.

[0103] In some implementations, the output baseband signals and the input baseband signals can be analog baseband signals, although the scope of the implementations is not limited in this respect. In some alternative implementations, the output baseband signals and the input baseband signals can be digital baseband signals. In these alternative implementations, the RF circuitry 906 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 904 can include a digital baseband interface to communicate with the RF circuitry 906.

[0104] In some dual-mode implementations, separate radio integrated circuits can be provided to process the signals for each spectrum, although the scope of the implementations is not limited in this respect. In some implementations, the synthesizer circuitry 906D can be a fractional-N synthesizer or a fractional N / N+1 synthesizer, although the scope of the implementations is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry 906D can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0105] The synthesizer circuitry 906D can be configured to synthesize an output frequency for use by the mixer circuitry 906A of the RF circuitry 906 based on a frequency input and a divider control input. In some implementations, synthesizer circuitry 906D can be a fractional N / N+1 synthesizer. In some implementations, frequency input can be provided by a voltage controlled oscillator (VCO). The divider control input can be provided by the baseband circuitry 904 or the application circuitry 902 based on a desired output frequency. In some implementations, the divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the application circuitry 902.

[0106] The synthesizer circuitry 906D of the RF circuitry 906 can include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some implementations, the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some implementations, the DMD can be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example implementations, the DLL can include a set of cascaded, delay

[0107] In some implementations, synthesizer circuitry 906D can be configured to generate a carrier frequency as the output frequency, while in other implementations, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some implementations, the output frequency can be a LO frequency (fLO). In some implementations, the RF circuitry 906 can include a

[0108] FEM circuitry 908 can include a receive signal path, which can include circuitry configured to operate on RF signals received from one or more antennas 910, amplify the received signals and provide the amplified versions of the received signals as an output (for example, to the RF circuitry 906 for further processing). FEM circuitry 908 can also include a transmit signal path, which can include circuitry configured to amplify signals for transmission provided as an input (for example, from RF circuitry 906), and provide the amplified signals as an output (for example, to one or more of the one or more antennas 910 for transmission).

[0109] In some implementations, FEM circuitry 908 can include a transmit / receive switch to switch between transmit mode and receive mode operation. FEM circuitry 908 can include a receive signal path and a transmit signal path. The receive signal path of FEM circuitry 908 can include a low-noise amplifier to amplify received RF signals and provide the amplified received RF signals as an output (for example, to RF circuitry 906). The transmit signal path of FEM circuitry 908 can include a power amplifier to amplify signals for transmission provided as an input (for example, from RF circuitry 906), and one or more filters to generate RF signals for subsequent transmission (for example, by one or more of the one or more antennas 910).

[0110] In some implementations, the PMC 912 can manage power provided to the baseband circuitry 904. In particular, the PMC 912 can control power selection, voltage scaling, battery charging, or direct current (DC-to-DC) conversion. The PMC 912 can be included when the device 900 has a power management requirement so that the device 900 can receive power from the battery or other power source. The PMC 912 can increase the efficiency of the power conversion while providing a desirable form factor and heat dissipation characteristics.

[0111] While Figure 9The PMC 912 is shown to be coupled to the baseband circuitry 904 only. However, in other implementations, the PMC 912 can be additionally or alternatively coupled to other components such as, but not limited to, the application circuitry 902, the RF circuitry 906, or the FEM circuitry 908, and perform similar power management operations for those components.

[0112] In some implementations, the PMC 912 can control, or otherwise be part of, various power saving mechanisms of the device 900. For example, if the device 900 is in an RRC_Connected state, where it remains connected to the RAN node because it expects

[0113] If there is no data traffic activity for an extended period of time, then the device 900 can transition off to an RRCJdle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 900 can enter a very low power state and it

[0114] An additional power saving mode can be used when the device is unable to use the network for an extended period of time. In this mode, the device 900 can power down to a very low power state, where it is unable to connect to the network. Any data communication must occur after the device 900 has powered up again. In some implementations, the device 900 can not wake up from this mode until it has a new message to transmit or an anticipated data reception. In some implementations, the device 900 can wake up from the mode at preconfigured times of the day, in response to external stimuli, or in response to environmental changes. The device 900 can wake up periodically to listen to the network to determine whether it has acquired new data.

[0115] The processors of application circuitry 902 and the processors of baseband circuitry 904 can be used to execute elements of one or more instances of a protocol stack. For example, processors of baseband circuitry 904 can be used, alone or in combination, to perform Layer 3, Layer 2, or Layer 1 functionality, while processors of baseband circuitry 904 can utilize data (e.g., packet data) received from these layers and further perform Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 can include a radio resource control layer. As referred to herein, Layer 2 can include a medium access control layer, a radio link control layer, and a packet data convergence protocol layer, which are described in further detail below. As referred to herein, Layer 1 can include a physical layer of the UE / RAN node.

[0116] Figure 10is a diagram of an example interface 1000 of baseband circuitry according to one or more implementations described herein. One or more components or features of example interface 1000 can correspond to one or more components or features described above or elsewhere. Baseband circuitry 1004 can include processors 1004A, 1004B, 1004C, 1004D, and 1004E, and memory 1004G utilized by the processors. Each of processors 1004A, 1004B, 1004C, 1004D, and 1004E can include a memory interface 1006A, 1006B, 1006C, 1006D, and 1006E, respectively, to transfer data to and from memory 1004G. Baseband circuitry can be a component of UE and / or another type of device or system able to transmit and / or receive wireless signals.

[0117] Baseband circuitry 1004 can further include one or more interfaces to communicate with other circuitries / devices, such as a memory interface 1012 (e.g., an interface to send / receive data to / from memory external to baseband circuitry 1004), an application circuitry interface 1014 (e.g., an interface to send / receive data to / from application circuitry as described herein), an RF circuitry interface 1016, a wireless hardware connectivity interface 1018 (e.g., an interface to send / receive data to / from near-field communication components, Bluetooth ® components (e.g., Bluetooth ® low energy), Wi-Fi ® components, and other communication components to communicate with such devices / wireless networks, and a power management interface 1020 (e.g., an interface to send / receive power or control signals to / from a PMC).

[0118] Figure 11 is a block diagram illustrating components of a machine, apparatus, or device for reading instructions from a machine-readable or computer-readable medium (for example, a non-transitory machine-readable storage medium) and executing any one or more of the methodologies discussed herein, according to some example implementations. Specifically, Figure 11 a diagrammatic representation of hardware resources 1100 including one or more processors 1110 (or processor cores), one or more memory / storage devices 1120, and one or more communication resources 1130, each of which can be communicatively coupled via a bus 1140. For implementations in which node virtualization or network function virtualization is utilized, a hypervisor 1102 can be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1100. The hardware resources 1100 can interact with the hypervisor 1102. For example, the hypervisor 1102 can schedule or otherwise manage the hardware resources 1100.

[0119] The processor 1110 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application-specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) can include, for example, a processor 1112 and a processor 1114.

[0120] The memory / storage 1120 can include a main memory, a disk storage, or any suitable combination thereof. The memory / storage 1120 can include, but is not limited to, any type of volatile or nonvolatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

[0121] In some implementations, the memory / storage 1120 receives and / or stores information and instructions 1155 for indirect network sharing. The UE 210 can receive, from the base station 222, PLMN IDs corresponding to the hosting operator network 410 and the at least one participating operator network 420. The UE 210 can select a PLMN ID of the participating operator network 420 and communicate with the hosting operator network 410 based on the PLMN ID of the participating operator network 420 to perform one or more procedures. Examples of such procedures can include an authentication procedure, a registration procedure, a protocol data unit (PDU) session establishment procedure, etc. The AMF 310 of the hosting operator network 410 can select one or more functions in the hosting operator network 420 and the participating operator network 420 to complete these procedures. These and many other features and examples are described herein.

[0122] The communication resources 1130 can include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1104 or one or more database 1106 over a network 1108. For example, the communication resources 1130 can include wired communication components (e.g., for coupling via a universal serial bus), cellular communication components, near-field communication components, Bluetooth ® components (e.g., Bluetooth ® low energy), Wi-Fi ® components, and other communication components.

[0123] Instructions 1150A, 1150B, 1150C, 1150D, and / or 1150E can include software, programs, applications, applets, application-specific processes, or other executable code for causing at least any of the processors 1110 to implement any one or more of the methods discussed herein. The instructions 1150 can reside entirely within at least one of the processors 1110 (e.g., within cache memory), the memory / storage devices 1120, or any suitable combination thereof. Further, any portion of the instructions 1150A to 1150E can be transferred from any combination of the peripheral devices 1104 or databases 1106 to the hardware resources 1100. Accordingly, the memory of processors 1110, the memory / storage devices 1120, the peripheral devices 1104, and the databases 1106 are examples of computer- and machine-readable media.

[0124] Figure 12 is a diagram of an example process 1200 for real-time precise ionospheric corrections in accordance with one or more implementations described herein. As shown, process 1200 can be implemented by a UE 210, baseband circuitry 904, and / or one or more other components of the UE 210. In some implementations, some or all of process 1200 can be performed by one or more other systems or devices, including one or more of the devices of Figure 2 FIG. 13A. Additionally, process 1200 can include fewer, additional, differently ordered, and / or arranged operations than those shown in Figure 12 FIG. 13A. In some implementations, some or all of the operations of process 1200 can be performed independently, sequentially, concurrently, and / or in different orders than shown, and / or with different timing than shown. Accordingly, the techniques described herein are not limited to the number, sequence, arrangement, timing, and / or the like of the operations or processes depicted. Figure 12

[0125] As shown, process 1200 can include receiving and / or processing a plurality of public land mobile network (PLMN) identifiers (IDs) including at least one PLMN ID of a hosting carrier network and a plurality of PLMN IDs of participating carrier networks (block 1210). Process 1200 can include selecting and / or determining at least one PLMN ID of the participating carrier networks (block 1220). Process 1200 can include generating and / or communicating information including the at least one PLMN ID of the participating carrier networks for communication to the participating carrier networks via the hosting carrier network (block 1230). One or more of the examples described herein can also or alternatively be part of process 1200.

[0126] ​Embodiments herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor with memory, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like) cause the machine to perform acts of a method or of an apparatus or system for concurrent communication using multiple communication technologies according to the described embodiments and implementations.

[0127] In Example 1, which can also include one or more of the embodiments described herein, the baseband circuitry can include one or more processors configured to: process a plurality of public land mobile network (PLMN) identifiers (IDs) including at least one PLMN ID of a hosting carrier network and at least one PLMN ID of a participating carrier network; select the at least one PLMN ID of the participating carrier network; and generate information including the at least one PLMN ID of the participating carrier network for communication to the participating carrier network via the hosting carrier network.

[0128] In Example 2, which can also include one or more of the embodiments described herein, the at least one PLMN ID of the hosting carrier network includes a visited PLMN (VPLMN) ID and the at least one PLMN ID of the participating carrier network includes a home PLMN (HPLMN) ID.

[0129] In Example 3, which can also include one or more of the embodiments described herein, the HPLMN ID is derived from a subscription permanent identifier (SUPI) associated with the participating carrier network.

[0130] In Example 4, which can also include one or more of the embodiments described herein, the one or more processors are further configured to: derive a key for authentication to the participating carrier network using a serving network identifier (SN ID) of the participating carrier network.

[0131] In Example 5, which can also include one or more of the embodiments described herein, the at least one PLMN ID of the participating carrier network is selected based on a subscription to a service associated with the participating carrier network.

[0132] In Example 6, which can also include one or more of the embodiments described herein, the information includes a registration request and the one or more processors are further configured to: receive a registration response from the hosting carrier network in response to the registration request.

[0133] In an embodiment 7, which can also include one or more of the embodiments described herein, the registration request is communicated to a radio access network (RAN) of the hosting operator network.

[0134] In an embodiment 8, which can also include one or more of the embodiments described herein, the one or more processors are further configured to determine a single network slice selection assistance information (S-NSSAI) of the participating operator network, the information including the S-NSSAI of the participating operator network, and the S-NSSAI of the participating operator network being associated with an S-NSSAI of the hosting operator network.

[0135] In an embodiment 9, which can also include one or more of the embodiments described herein, the at least one PLMN ID of the participating operator network and the S-NSSAI are used in a registration procedure.

[0136] In an embodiment 10, which can also include one or more of the embodiments described herein, the at least one PLMN ID of the participating operator network and the S-NSSAI are used in a protocol data unit (PDU) session establishment procedure.

[0137] In an embodiment 11, which can also include one or more of the embodiments described herein, the plurality of PLMNs further includes at least one equivalent PLMN ID of the at least one PLMN ID of the participating operator network.

[0138] In an embodiment 12, which can also include one or more of the embodiments described herein, a server device configured to operate as an access and mobility management function (AMF) can include one or more processors configured to provide, to a base station of a hosting operator network, a plurality of public land mobile network (PLMN) identifiers (IDs) including at least one PLMN ID of the hosting operator network and at least one PLMN ID of a participating operator network, receive, from a user equipment (UE), information including the at least one PLMN ID of the participating operator network, and select at least one core network function of the participating operator network based on the at least one PLMN ID of the participating operator network.

[0139] In Example 13, which can also include one or more of the embodiments described herein, the AMF comprises a serving AMF of the host operator network, the base station comprises a shared radio access network of the host operator network and the participating operator network, and the serving AMF communicates with an AMF of the participating operator network, and a user plane function (UPF) of the host operator network communicates with a UPF in the participating operator network.

[0140] In Example 14, which can also include one or more of the embodiments described herein, the one or more processors are further configured to determine, as part of a registration procedure, that the UE is registered to the participating operator network based at least in part on the at least one PLMN ID of the participating operator network.

[0141] In Example 15, which can also include one or more of the embodiments described herein, the one or more processors are further configured to select, as part of a protocol data unit (PDU) session establishment procedure for the UE, a session management function (SMF) of the participating operator network and a visited SMF (V-SMF) of the host operator network based at least in part on the at least one PLMN ID of the participating operator network.

[0142] In Example 16, which can also include one or more of the embodiments described herein, the at least one PLMN ID of the host operator network comprises a visited PLMN (VPLMN) ID, and the at least one PLMN ID of the participating operator network comprises a home PLMN (HPLMN) ID.

[0143] In Example 17, which can also include one or more of the embodiments described herein, the one or more processors are further configured to perform an authentication procedure associated with the UE using a serving network identifier (SN ID) based on the at least one PLMN ID of the participating operator network, the authentication procedure comprising key derivation based on the SN ID.

[0144] In Example 18, which can also include one or more of the embodiments described herein, the one or more processors are further configured to receive, from the UE, single network slice selection assistance information (S-NSSAI) of the participating operator network, and determine, based on a configuration agreement between the host operator network and the participating operator network, that an S-NSSAI of the participating operator network corresponds to an S-NSSAI of the host operator network.

[0145] In Example 19, which can also include one or more of the embodiments described herein, the at least one PLMN ID of the participating operator network comprises an equivalent PLMN identifier (EPLMN ID).

[0146] In Example 20, which can also include one or more of the embodiments described herein, a method performed by a user equipment (UE), the method comprising: receiving, from a base station of a hosted operator network, a plurality of public land mobile network (PLMN) identifiers (IDs) including at least one PLMN ID of the hosted operator network and at least one PLMN ID of a participating operator network; selecting the at least one PLMN ID of the participating operator network; and communicating, to the base station of the hosted operator network, information including the at least one PLMN ID of the participating operator network.

[0147] The above description of illustrative examples, implementations, aspects, etc. of the disclosed subject matter, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed subject matter to the precise forms disclosed. While specific examples, implementations, aspects, etc. are described herein for illustrative purposes, various modifications are possible within the scope of such examples, implementations, aspects, etc. as such modifications will be apparent to those skilled in the relevant art.

[0148] In this regard, while the disclosed subject matter has been described in terms of various examples, implementations, aspects, etc. and corresponding illustrative drawings, it should be understood that the disclosed subject matter is not limited to those examples, implementations, aspects, etc. Rather, the disclosed subject matter is intended to encompass many alternatives, modifications and variations from the examples, implementations, aspects, etc. disclosed. Accordingly, the examples, implementations, aspects, etc. disclosed herein are illustrative only and are not limiting of the disclosed subject matter.

[0149] In particular, with respect to the various functions performed by the above-described components or structures (assemblies, devices, circuits, systems, etc.), the terms used in connection with describing such components (including references to “means” for performing a specified function) are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component — that is, performing the function of an example implementation of the disclosed structure for which the function is exemplified in the examples set forth herein — even if the structure is not structurally identical to the disclosed structure performing the function in the exemplified example implementation. In addition, although a particular feature can have been disclosed in only one of several examples, for any given application, such a feature can be combined with one or more other features of the other examples, as can be desired and advantageous.

[0150] As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Moreover, where the use of the term “including” or “having” or variants thereof is stated in the detailed description or in the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open term with the inclusion of items listed thereafter and any additional items. Additionally, where discussion of one or more numbered items (e.g., “a first X,” “a second X,” etc.) is made, generally the one or more numbered items can be different or they can be the same, but in some cases the context can indicate that they are different or that they are the same.

[0151] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled in a manner that minimizes risks from unauthorized or unintended access or use, and that is consistent with industry or governmental requirements.

Claims

1. A baseband circuit, the baseband circuit comprising: One or more processors, said one or more processors being configured to: Processing multiple PLMN IDs, including at least one Public Land Mobile Network (PLMN) identifier (ID) of the hosting operator network and at least one PLMN ID of the participating operator network; Select at least one PLMN ID from the participating operator network; as well as Information including the at least one PLMN ID of the participating operator network is generated for transmission to the participating operator network via the hosting operator network.

2. The baseband circuit according to claim 1, wherein: The at least one PLMN ID of the hosted operator network includes a Visited PLMN (VPLMN) ID, and The at least one PLMN ID of the participating operator network includes a Home PLMN (HPLMN) ID.

3. The baseband circuit of claim 2, wherein the HPLMN ID is derived from a subscription permanent identifier (SUPI) associated with the participating operator network.

4. The baseband circuit of claim 1, wherein the one or more processors are further configured to: Use the Service Network Identifier (SN ID) of the participating operator network to derive the key used for authentication to the participating operator network.

5. The baseband circuit of claim 1, wherein the at least one PLMNID of the participating operator network is selected based on a subscription to a service associated with the participating operator network.

6. The baseband circuit according to claim 1, wherein: The information includes a registration request, and The one or more processors are further configured to: In response to the registration request, a registration response is received from the hosting operator network.

7. The baseband circuit of claim 6, wherein the registration request is transmitted to the radio access network (RAN) of the hosting operator network.

8. The baseband circuit according to claim 1, wherein: The one or more processors are further configured to: Determine the Single Network Slice Selection Auxiliary Information (S-NSSAI) for the participating operator's network. The information includes the S-NSSAI of the participating operator network, and The S-NSSAI of the participating operator network is associated with the S-NSSAI of the managed operator network.

9. The baseband circuit of claim 8, wherein the at least one PLMNID of the participating operator network and the S-NSSAI are used in the registration procedure.

10. The baseband circuit of claim 8, wherein the at least one PLMNID of the participating operator network and the S-NSSAI are used in the Protocol Data Unit (PDU) session establishment procedure.

11. The baseband circuit of claim 1, wherein the plurality of PLMNs further includes at least one equivalent PLMN ID of the at least one PLMN ID of the participating operator network.

12. A server device configured to operate as an Access and Mobility Management Function (AMF), the server device comprising: One or more processors, said one or more processors being configured to: Provide the base stations of the managed operator network with multiple PLMN IDs, including at least one Public Land Mobile Network (PLMN) identifier (ID) of the managed operator network and at least one PLMN ID of the participating operator network; Receive information including the at least one PLMN ID of the participating operator network from the user equipment (UE); as well as At least one core network function of the participating operator network is selected based on at least one PLMN ID of the participating operator network.

13. The server device according to claim 12, wherein: The AMF includes the service AMF of the managed operator network. The base station includes the managed operator network and the shared radio access network of the participating operator network, and The serving AMF communicates with the AMF of the participating operator network, and the user plane function (UPF) of the managed operator network communicates with the UPF in the participating operator network.

14. The server device of claim 12, wherein the one or more processors are further configured to: The UE's registration with the participating operator network is determined at least in part based on the at least one PLMN ID of the participating operator network as part of the registration procedure.

15. The server device of claim 12, wherein the one or more processors are further configured to: The Session Management Function (SMF) of the participating operator network and the Visiting SMF (V-SMF) of the managed operator network are selected, at least in part, based on the at least one PLMN ID of the participating operator network, as part of the UE's Protocol Data Unit (PDU) session establishment procedure.

16. The server device according to claim 12, wherein: The at least one PLMN ID of the hosted operator network includes a Visited PLMN (VPLMN) ID, and The at least one PLMN ID of the participating operator network includes a Home PLMN (HPLMN) ID.

17. The server device of claim 12, wherein the one or more processors are further configured to: An authentication procedure associated with the UE is performed using a Service Network Identifier (SN ID) based on the at least one PLMN ID of the participating operator network, the authentication procedure including key derivation based on the SN ID.

18. The server device of claim 12, wherein the one or more processors are further configured to: The UE receives Single Network Slice Selection Assist Information (S-NSSAI) from the participating operator network; and The S-NSSAI of the participating operator network is determined to correspond to the S-NSSAI of the hosting operator network based on the configuration agreement between the hosting operator network and the participating operator network.

19. The server device of claim 12, wherein the at least one PLMN ID of the participating operator network includes an equivalent PLMN identifier (EPLMN ID).

20. A method performed by a user equipment (UE), the method comprising: Receive multiple PLMN IDs from base stations in the managed operator network, including at least one Public Land Mobile Network (PLMN) identifier (ID) of the managed operator network and at least one PLMN ID of the participating operator network; Select at least one PLMN ID from the participating operator network; and The information, including the at least one PLMN ID of the participating operator network, is communicated to the base station of the managed operator network.

Images