Provides configuration information for accessing standalone, non-public networks.

Abstract

The techniques described herein enable the provision of configuration information between one or more network entities of a home service provider (SP) and one or more network entities of a network, such as a standalone non-public network (SNPN), to support a user equipment (UE) associated with the home SP visiting the SNPN. For example, the configuration information can enable the UE to access or use services provided by the home SP. In some aspects, the configuration information can include a proxy call session control function address, tunneling information, etc. In this manner, the functionality is supported for a UE visiting an SNPN, even though the home SP providing the functionality does not have a session management function (SMF) for signaling of configuration information supporting the functionality. Hence, the interconnection between the SNPN and the home SP network is improved.

Description

Technical Field

[0001] Cross - reference to Related Applications

[0001] This patent application claims priority to Greek Patent Application No. 20210100100, titled "PROVIDING CONFIGURATION INFORMATION FOR ACCESSING A STANDALONE NON - PUBLIC NETWORK", filed on February 17, 2021 and assigned to the assignee of this application. The disclosure of the prior application is considered part of this patent application and is incorporated herein by reference.

[0002]

[0002] Aspects of the present disclosure generally relate to wireless communication, and to techniques and apparatus for providing configuration information for accessing a standalone non - public network.

Background Art

[0003]

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcast. Typical wireless communication systems can employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long-Term Evolution (LTE®). LTE / LTE Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard published by the Third Generation Partnership Project (3GPP®).

[0004]

[0004] A wireless network may include several base stations (BS) capable of supporting communication for several user equipment (UEs). UEs can communicate with BSs via downlinks and uplinks. A "downlink" (or forward link) refers to a communication link from a BS to a UE, and an "uplink" (or reverse link) refers to a communication link from a UE to a BS. As will be described in more detail herein, BSs may also be called node Bs, gNBs, access points (APs), radio heads, transmit / receive points (TRPs), 5G BSs, 5G node Bs, etc.

[0005]

[0005] The above-mentioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables various wireless communication devices to communicate at local, national, regional, and even global levels. 5G, sometimes referred to as New Radio (NR), is a set of extensions to the LTE mobile standards published by 3GPP. 5G is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, utilizing new spectrum, and by using orthogonal frequency division multiplexing (OFDM) with cyclic prefixes (CP-OFDM) on the downlink (DL) and CP-OFDM and / or SC-FDM (also known as, for example, discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), as well as by supporting beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. However, as the demand for mobile broadband access continues to grow, there is a need for further improvements in LTE and 5G technologies. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunications standards that employ them. [Overview of the Initiative]

[0006]

[0006] Standalone non-public networks (SNPNs) can provide wireless access connectivity for user equipment (UEs) using wireless access technologies such as 5G. SNPNs can be useful in a variety of applications, including industrial automation (e.g., industrial internet of things), public spaces, and public transportation.

[0007]

[0007] The UE may be associated with a home service provider (SP). The home SP may include an SNPN operator, a public land mobile network (PLMN) operator, a credential provider (such as an entity operating an authentication, authorization, and accounting (AAA) server without wireless access functionality), etc.

[0008]

[0008] In some cases, a UE may access an SNPN using credentials provided by its home SP, even if the SNPN is not associated with that home SP (for example, not provided by that home SP). Accessing an SNPN not provided by its home SP is referred to herein as visiting an SNPN. The communication protocol may provide authentication of the UE by the home SP's AAA server (for example, via the SNPN) or by one or more network entities of the home SP, such as an authentication server function (AUSF), unified data management (UDM) function, etc. However, some forms of configuration information may be handled by the session management function (SMF) of a given 5G system (5GS), such as an SNPN. If the UE's home SP does not have an SMF, signaling of such forms of configuration information may be prevented for the purpose of visiting an SNPN not associated with that home SP. Examples of such configuration information include the P-CSCF address related to the home SP's proxy call session control function (P-CSCF), and tunneling information used to connect to the home SP's IP multimedia subsystem (IMS). If such configuration information cannot be signaled to the UE visiting the SNPN, the UE may be unable to access the IMS services provided by the home SP.

[0009]

[0009] Some technologies and devices described herein enable the provision of configuration information between one or more network entities of a home SP and one or more network entities of the SNPN in order to support a UE associated with a home SP visiting the SNPN. For example, the configuration information can enable the UE to access or use IMS services provided by the home SP. In some embodiments, the configuration information may include P-CSCF addresses, tunneling information, etc. In some embodiments, the configuration information may be provided by the home SP's AAA server to an AAA proxy or another function in the SNPN, and the AAA proxy may forward the configuration information to an SMF which can signal the configuration information to the UE or to a user plane function (UPF) associated with the UE. In some embodiments, the configuration information may be provided from the home SP's UDM to an SMF which can signal the configuration information to the UE or to a UPF associated with the UE. In this approach, the IMS functionality is supported for UEs visiting the SNPN, even though the home SP providing the IMS functionality does not have an SMF for signaling configuration information that supports the IMS functionality. Therefore, the interconnection between the SNPN and the home SP network is improved.

[0010]

[0010] In some embodiments, a method of wireless communication performed by a first network entity includes identifying a protocol data unit (PDU) session with a UE, obtaining configuration information associated with a first service provider, at least in part on having identified the PDU session, and the first network entity transmitting the configuration information to a UE associated with a standalone non-public network provided by a second service provider, or to a second network entity associated with a standalone non-public network.

[0011]

[0011] In some embodiments, a method of wireless communication performed by a first network entity includes receiving a request from a second network entity for configuration information associated with a first service provider, obtaining configuration information from a proxy entity associated with a standalone non-public network, at least in part on the request for configuration information, wherein the first and second network entities are associated with a standalone non-public network provided by the second service provider, and wherein the configuration information is associated with a UE associated with a first service provider accessing the standalone non-public network, and transmitting the configuration information to the second network entity.

[0012]

[0012] In some embodiments, a method of wireless communication performed by a first network entity includes receiving configuration information relating to a UE accessing a standalone non-public network associated with the first network entity from a network entity associated with a first service provider, wherein the standalone non-public network receives a request from a second network entity associated with the standalone non-public network for at least a portion of the configuration information relating to a second service provider, and transmitting the configuration information to the second network entity based at least in part on the request.

[0013]

[0013] In some embodiments, a first network entity for wireless communication includes a memory and one or more processors coupled to the memory, wherein one or more processors are configured to identify a PDU session with a UE, obtain configuration information associated with a first service provider at least in part on having identified the PDU session, and transmit the configuration information to a UE associated with a standalone non-public network provided by a second service provider, or to a second network entity associated with a standalone non-public network.

[0014]

[0014] In some embodiments, a first network entity for wireless communication includes a memory and one or more processors coupled to the memory, wherein one or more processors are configured to receive a request from a second network entity for configuration information associated with a first service provider, wherein the first and second network entities are associated with a standalone non-public network provided by the second service provider, wherein the configuration information is associated with a UE associated with the first service provider accessing the standalone non-public network, and to obtain configuration information from a proxy entity associated with the standalone non-public network, at least in part on the request for configuration information, and to transmit the configuration information to the second network entity.

[0015]

[0015] In some embodiments, a first network entity for wireless communication includes a memory and one or more processors coupled to the memory, wherein one or more processors are configured to receive configuration information relating to a UE accessing a standalone non-public network associated with the first network entity from a network entity associated with a first service provider, wherein the standalone non-public network is associated with a second service provider and receives a request from a second network entity associated with the standalone non-public network for at least a portion of the configuration information, and transmits the configuration information to the second network entity based at least in part on the request.

[0016]

[0016] In some embodiments, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions, and when one or more instructions are executed by one or more processors of a first network entity, the first network entity causes the first network entity to identify a PDU session with a UE, to obtain configuration information associated with a first service provider, at least in part on having identified the PDU session, and to transmit the configuration information to a UE associated with a standalone non-public network provided by a second service provider, or to a second network entity associated with a standalone non-public network.

[0017]

[0017] In some embodiments, a non-temporary computer-readable medium storing a set of instructions for wireless communication includes one or more instructions, and when one or more instructions are executed by one or more processors of the first network entity, the first network entity receives a request from a second network entity for configuration information associated with a first service provider, and the first network entity obtains configuration information from a proxy entity associated with a standalone non-public network, at least in part, based on the request for configuration information, where the first and second network entities are associated with a standalone non-public network provided by the second service provider, where the configuration information is associated with a UE associated with a first service provider accessing the standalone non-public network, and transmits the configuration information to the second network entity.

[0018]

[0018] In some embodiments, a non-temporary computer-readable medium storing a set of instructions for wireless communication includes one or more instructions, and when one or more instructions are executed by one or more processors of the first network entity, the first network entity receives from a network entity associated with a first service provider configuration information relating to a UE accessing a standalone non-public network associated with the first network entity, thereby causing the first network entity to receive from a second network entity associated with the standalone non-public network a request for at least a portion of the configuration information relating to a second service provider, and to transmit the configuration information to the second network entity based at least in part on the request.

[0019]

[0019] In some embodiments, the device for wireless communication includes means for identifying a PDU session with a UE, means for obtaining configuration information associated with a first service provider, at least in part on having identified a PDU session, and means for the first network entity to transmit the configuration information to a UE associated with a standalone non-public network provided by a second service provider, or to a second network entity associated with a standalone non-public network.

[0020]

[0020] In some embodiments, the device for wireless communication includes means for receiving a request from a second network entity for configuration information associated with a first service provider, means for obtaining configuration information from a proxy entity associated with a standalone non-public network, at least in part on the request for configuration information, wherein the first and second network entities are associated with a standalone non-public network provided by the second service provider, and wherein the configuration information is associated with a UE associated with the first service provider accessing the standalone non-public network, and means for transmitting the configuration information to the second network entity.

[0021]

[0021] In some embodiments, the device for wireless communications includes means for receiving configuration information relating to a UE accessing a standalone non-public network associated with a first network entity from a network entity associated with a first service provider, wherein the standalone non-public network is associated with a second service provider, and means for receiving a request from a second network entity associated with the standalone non-public network for at least a portion of the configuration information, wherein the standalone non-public network is associated with a second service provider, and means for transmitting the configuration information to the second network entity based at least in part on the request.

[0022]

[0022] The embodiments are generally described substantially with reference to the drawings and specification, and include methods, apparatus, systems, computer program products, non-temporary computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems shown in the drawings and specification.

[0023]

[0023] The foregoing content has outlined rather roughly the functional and technical advantages of the examples according to the present disclosure, for the purpose that the subsequent detailed description can be better understood. Further functions and advantages will be described hereinafter. The disclosed concepts and specific examples can be readily utilized as a basis for making modifications or for designing other structures to perform the same purpose of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The features of the concepts disclosed herein, both their composition and the manner of operation, will be better understood from the following description when considered in association with the advantages associated therewith and in connection with the accompanying drawings. Each of those drawings is provided for the purpose of illustration and explanation, rather than as a definition of the limitations of the claims.

Brief Description of the Drawings

[0024] [Figure 1]

[0024] A diagram showing an example of a wireless network. [Figure 2]

[0025] A diagram showing an example of a base station in a communication state with a UE in a wireless network. [Figure 3]

[0026] A diagram of an exemplary environment of a stand-alone non-public network (SNPN) and a network associated with a home service provider (SP) of a UE. [Figure 4]

[0027] A diagram of an exemplary environment of an SNPN and a network associated with a home SP of a UE according to the present disclosure. [[ID=二十一]] [[ID=二十二]] [Figure 5] [[ID=二十三]]

[0028] [[ID=二十四]] A diagram showing an example of providing configuration information from a home SP for a UE accessing an SNPN. [[ID=二十五]] [[ID=二十六]] [Figure 6] [[ID=二十七]] A diagram showing an example of providing configuration information from a home SP for a UE accessing an SNPN. [[ID=二十八]] [[ID=二十九]] [Figure 7] [[ID=三十]] A diagram showing an example of providing configuration information from a home SP for a UE accessing an SNPN. [[ID=三十一]] [[ID=三十二]] [Figure 8]A diagram illustrating an example of providing configuration information from a home SP to a UE accessing SNPN. [Figure 9]

[0029] A flowchart illustrating an exemplary method of wireless communication. [Figure 10] A flowchart illustrating an exemplary method of wireless communication. [Figure 11] A flowchart illustrating an exemplary method of wireless communication. [Figure 12]

[0030] Block diagram of an exemplary device for wireless communication. [Figure 13]

[0031] A diagram showing an example of a hardware embodiment for a device employing a processing system. [Figure 14]

[0032] Block diagram of an exemplary device for wireless communication. [Figure 15]

[0033] A diagram showing an example of a hardware embodiment for a device employing a processing system. [Figure 16]

[0034] Block diagram of an exemplary device for wireless communication. [Figure 17]

[0035] A diagram showing an example of a hardware embodiment for a device employing a processing system. [Modes for carrying out the invention]

[0025]

[0036] The detailed descriptions provided hereafter in connection with the attached drawings are intended to describe various configurations and are not intended to represent configurations in which the concepts described herein can be put into practice. These detailed descriptions include specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be put into practice without these specific details. In some cases, well-known structures and components are shown in the form of block diagrams to avoid obscuring such concepts.

[0026]

[0037] Here, several embodiments of telecommunications systems are presented with reference to various devices and methods. These devices and methods are described in the following detailed explanation and are illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0027]

[0038] For example, an element, or any part of an element, or any combination of elements, may be implemented together with a “processing system” comprising one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system are capable of executing software. Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or by other names.

[0028]

[0039] Accordingly, in one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on a computer-readable medium or encoded on a computer-readable medium as one or more instructions or codes. The computer-readable medium includes computer storage media. The storage media can be any available media that can be accessed by a computer. Such computer-readable media may include, but are not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM®), compact disk ROM (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, combinations of the computer-readable media of the aforementioned types, or any other media that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0029]

[0040] In this specification, embodiments may be described using terms generally associated with 5G or NR radio access technology (RAT), but it should be noted that embodiments of this disclosure may apply to other RATs, such as 3G RAT, 4G RAT, and / or RATs following 5G (e.g., 6G).

[0030]

[0041] Figure 1 shows a wireless network 100 in which an aspect of this disclosure may be put into practice. The wireless network 100 may be, or may include, elements of a 5G(NR) network and / or an LTE network, among many other examples. The wireless network 100 may include several base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UE) and may also be called a 5G BS, node B, gNB, 5G NB, access point, transmit / receive point (TRP), etc. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” may refer to the coverage area of ​​a BS and / or the BS subsystem that serves this coverage area, depending on the context in which the term is used.

[0031]

[0042] A Broadcast Station (BS) can provide communication coverage for macrocells, picocells, femtocells, and / or other types of cells. Macrocells can cover relatively large geographical areas (e.g., a radius of several kilometers) and can allow unrestricted access by UEs with service subscriptions. Picocells can cover relatively small geographical areas and can allow unrestricted access by UEs with service subscriptions. Femtocells can cover relatively small geographical areas (e.g., a residential area) and can allow restricted access by UEs associated with that femtocell (e.g., UEs in a closed subscriber group (CSG)). A BS for macrocells is sometimes called a macroBS. A BS for picocells is sometimes called a picoBS. A BS for femtocells is sometimes called a femtoBS or homeBS. In the example shown in Figure 1, BS110a can be a macroBS for macrocell 102a, BS110b can be a picoBS for picocell 102b, and BS110c can be a femtoBS for femtocell 102c. A BS can support one or more (for example, three) cells. The terms “eNB”, “base station”, “5G BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB”, and “cell” may be used interchangeably herein.

[0032]

[0043] In some cases, cells may not necessarily be stationary, and the geographical area of ​​a cell may move according to the location of the mobile BS. In some cases, BSs may be interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0033]

[0044] The wireless network 100 may also include relay stations. A relay station is an entity capable of receiving data transmissions from upstream stations (e.g., BS or UE) and sending those data transmissions to downstream stations (e.g., UE or BS). A relay station may also be a UE capable of relaying transmissions for other UEs. In the example shown in Figure 1, relay BS110d can communicate with macro BS110a and UE120d to facilitate communication between BS110a and UE120d. Relay BS may also be called relay stations, relay base stations, or relays.

[0034]

[0045] The wireless network 100 can be a heterogeneous network including different types of BS, such as macro BS, pico BS, femto BS, relay BS, etc. These different types of BS may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, macro BS may have high transmit power levels (e.g., 5-40 watts), while pico BS, femto BS, and relay BS may have lower transmit power levels (e.g., 0.1-2 watts).

[0035]

[0046] The network controller 130 can be coupled to a set of BSs and can provide coordination and control for these BSs. The network controller 130 can communicate with the BSs via backhaul. The BSs can also communicate with each other, for example, directly or indirectly via wireless or wired backhaul.

[0036]

[0047] UE120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be fixed or mobile. UEs may also be called access terminals, terminals, mobile stations, subscriber units, stations, etc. UEs can be cellular phones (e.g., smartphones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablets, cameras, gaming devices, netbooks, smartbooks, ultrabooks, medical devices or equipment, biometric sensors / devices, wearable devices (smartwatches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), entertainment devices (e.g., music or video devices, or satellite radios), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, global positioning system devices, or any other suitable device configured to communicate via wireless or wired media.

[0037]

[0048] Some UEs may be considered machine-type communications (MTC) or advanced or enhanced machine-type communications (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that are capable of communicating with base stations, other devices (e.g., remote devices), or any other entities. Wireless nodes may provide connectivity or network access for a network (e.g., a wide area network such as the Internet or a cellular network) via, for example, wired or wireless communication links. Some UEs may be considered Internet of Things (IoT) devices and / or implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs may be considered customer premises equipment (CPE). UE120 may be contained within a housing that accommodates the components of UE120, such as processor components, memory components, etc.

[0038]

[0049] Generally, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. RATs are sometimes called wireless technologies or air interfaces. Frequencies are sometimes called carriers or frequency channels. To avoid interference between wireless networks of different RATs, each frequency can support a single RAT in a given geographical area. In some cases, 5G RAT networks can be deployed.

[0039]

[0050] In some embodiments, two or more UE120s (for example, shown as UE120a and UE120e) can communicate directly (for example, without using base station 110 as an intermediary for communication with each other) using one or more sidelink channels. For example, UE120s can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (for example, this can include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), and / or mesh networks. In this case, UE120s can perform scheduling operations, resource selection operations, and / or other operations described elsewhere in this specification as being performed by base station 110.

[0040]

[0051] Devices in wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various classes, bands, channels, etc., based on frequency or wavelength. For example, devices in wireless network 100 can communicate using an operating band having a first frequency range (FR1) that may range from 410 MHz to 7.125 GHz, and / or using an operating band having a second frequency range (FR2) that may range from 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 are sometimes called midband frequencies. Part of FR1 is greater than 6 GHz, but FR1 is often referred to as the “sub-6 GHz” band. Similarly, FR2 is often referred to as the “millimeter wave” band, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) which is identified by the International Telecommunication Union (ITU) as the “millimeter wave” band. Therefore, unless otherwise specified, terms such as "sub-6GHz" can broadly refer to frequencies below 6GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125GHz) when used herein. Similarly, unless otherwise specified, terms such as "millimeter wave" can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25GHz) when used herein. The frequencies included in FR1 and FR2 may be modified, and the technologies described herein are considered applicable to those modified frequency ranges.

[0041]

[0052] In some embodiments, radio access may be provided using an open radio access network (O-RAN) architecture. An O-RAN architecture may include control units (CUs) that communicate with the core network via backhaul links. Furthermore, each CU may communicate with one or more distributed units (DUs) via their respective midhaul links. Each DU may communicate with one or more radio units (RUs) via their respective fronthaul links, and each RU may communicate with its respective UE via a radio frequency (RF) access link. DUs and RUs are sometimes referred to as O-RAN DUs (O-DUs) and O-RAN RUs (O-RUs), respectively.

[0042]

[0053] In some embodiments, the DU and RU may be implemented according to a functional partitioning architecture in which the functionality of the base station 110 (e.g., eNB or gNB) is provided by the DU and one or more RUs communicating via a fronthaul link. Thus, as described herein, the base station 110 may include a DU and one or more RUs that may be located in the same location or geographically distributed. In some embodiments, the DU and associated RU may communicate via a fronthaul link to exchange real-time control plane information via a lower layer partitioning (LLS-C) interface, to exchange non-real-time management information via an LLS management plane (LLS-M) interface, and / or to exchange user plane information via an LLS user plane (LLS-U) interface.

[0043]

[0054] Therefore, a DU can correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs. For example, in some embodiments, a DU can host, at least partially based on lower-layer functional partitioning, the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and one or more higher physical (PHY) layers (e.g., Forward Error Correction (FEC) encoding and decoding, scrambling, and / or modulation and demodulation). Higher-layer control functions such as Packet Data Convergence Protocol (PDCP), Radio Resource Control (RRC), and / or Service Data Adaptation Protocol (SDAP) may be hosted by a CU. RUs controlled by a DU can correspond to logical nodes that host RF processing functions and lower PHY layer functions (e.g., Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (iFFT), Digital Beamforming, and / or Physical Random Access Channel (PRACH) extraction and filtering), at least partially based on lower-layer functional partitioning. Therefore, in the O-RAN architecture, the RU handles all over-the-air (OTA) communication with the UE120, while the real-time and non-real-time aspects of control and user plane communication with the RU are controlled by the corresponding DU, which allows the DU and CU to be implemented in a cloud-based RAN architecture. Other examples of functional partitioning can be implemented.

[0044]

[0055] In some embodiments, one or more of the CU, DU, or RU can perform operations described herein as being performed by network nodes. For example, one or more of the CU, DU, or RU can include a communications manager, as described above.

[0045]

[0056] As shown above, Figure 1 is provided as an example. Other examples may differ from those described with respect to Figure 1.

[0046]

[0057] Figure 2 shows an example of a base station 110 200 in communication with a UE 120 in a wireless network 100. The base station 110 may have T antennas 234a to 234t, and the UE 120 may have R antennas 252a to 252r, in which case T ≥ 1 and R ≥ 1.

[0047]

[0058] At base station 110, the transmitting processor 220 is capable of receiving data from data source 212 for one or more UEs, selecting a modulation and coding scheme (MCS) for each UE at least partially based on the channel quality indicator (CQI) received from the UE, processing (e.g., encoding and modulating) the data for each UE at least partially based on the selected MCS for the UE, and providing data symbols for all UEs. The transmitting processor 220 is also capable of processing system information (e.g., about semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling), and providing overhead symbols and control symbols. The transmitting processor 220 is also capable of generating reference signals (e.g., cell-specific reference signals (CRS), phase-tracking reference signals (PTRS), and / or demodulated reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can, where applicable, perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, and can provide T output symbol streams to T modulators (MODs) 232a-232t. Each modulator 232 can process its respective output symbol stream (e.g., relating to OFDM) to obtain an output sample stream. Each modulator 232 can further process the output sample stream (e.g., convert to analog, amplify, filter, and upconvert) to obtain a downlink signal. The T downlink signals from modulators 232a-232t can be transmitted via T antennas 234a-234t, respectively.

[0048]

[0059] In UE120, antennas 252a-252r are capable of receiving downlink signals from base station 110 and / or other base stations, and providing the received signals to demodulators (DEMOD) 254a-254r, respectively. Each demodulator 254 can adjust the received signal (e.g., by filtering, amplifying, downconverting, and digitizing) to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., relating to OFDM) to obtain a received symbol. The MIMO detector 256 can obtain the received symbols from all R demodulators 254a-254r, and, where applicable, perform MIMO detection on the received symbols and provide the detected symbols. The receiving (RX) processor 258 can process the detected symbols (e.g., demodulate and decode), provide the decoded data relating to UE120 to the data sink 260, and provide the decoded control and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may, among many other things, determine the Reference Signal Received Power (RSRP) parameter, the Received Signal Strength Indicator (RSSI) parameter, the Reference Signal Received Quality (RSRQ) parameter, and / or the CQI parameter. In some embodiments, one or more components of the UE120 may be included in the housing 284.

[0049]

[0060] The network controller 130 may include a communication unit 294, a controller / processor 290, and memory 292. The network controller 130 may include, for example, one or more devices in the core network. The network controller 130 can communicate with the base station 110 via the communication unit 294.

[0050]

[0061] An antenna (for example, antennas 234a-234t and / or antennas 252a-252r) may include, or be included in, one or more antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays, among many other examples. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include sets of coplanar antenna elements and / or sets of non-coplanar antenna elements. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include antenna elements in a single housing and / or antenna elements in multiple housings. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements coupled to one or more transmitting and / or receiving components, such as one or more components in Figure 2.

[0051]

[0062] On the uplink, the UE120's transmit processor 264 can receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., regarding reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 can also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 can be precoded by the TX MIMO processor 266 where applicable, further processed by modulators 254a-254r (e.g., regarding DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some embodiments, the modulators and demodulators of the UE120 (e.g., MOD / DEMOD 254) may be included in the modem of the UE120. In some embodiments, the UE120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modulator and / or demodulator 254, a MIMO detector 256, a receiving processor 258, a transmitting processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (e.g., a controller / processor 280) and memory 282 to perform any aspect of the methods described herein.

[0052]

[0063] At base station 110, uplink signals from UE 120 and other UEs are received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 where applicable, and further processed by receiving processor 238 to obtain decoded data and control information transmitted by UE 120. The receiving processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 includes a communication unit 244 and can communicate with network controller 130 via the communication unit 244. Base station 110 may include a scheduler 246 for scheduling UE 120 for downlink and / or uplink communication. In some embodiments, the modulator and demodulator of base station 110 (e.g., MOD / DEMOD 232) may be included in the modem of base station 110. In some embodiments, base station 110 includes a transceiver. The transceiver may include any combination of an antenna 234, a modulator and / or demodulator 232, a MIMO detector 236, a receiving processor 238, a transmitting processor 220, and / or a TX MIMO processor 230. The transceiver may be used by a processor (e.g., a controller / processor 240) and memory 242 to perform any aspect of the methods described herein. A scheduler 246 may schedule the UE for data transmission on the downlink and / or uplink.

[0053]

[0064] The controller / processor 240 of base station 110, the controller / processor 280 of UE120, and / or any other components in Figure 2 are capable of performing one or more techniques associated with providing configuration information for accessing a standalone non-public network, as described in more detail elsewhere in this specification. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE120, and / or any other components in Figure 2 are capable of performing or directing operations of, for example, method 900 in Figure 9, method 1000 in Figure 10, method 1100 in Figure 11, and / or other processes described herein. Memories 242 and 282 are capable of storing data and program code for BS110 and UE120, respectively. In some embodiments, memory 242 and / or memory 282 may include non-temporary computer-readable media for storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when one or more of those instructions are executed by one or more processors of the base station 110 and / or UE 120 (for example, directly or after compilation, translation, and / or interpretation), it is possible to cause one or more of those processors, UE 120, and / or base station 110 to perform or direct operations of, for example, method 900 in Figure 9, method 1000 in Figure 10, method 1100 in Figure 11, and / or other processes described herein. In some embodiments, executing an instruction can include, among many examples, bringing the instruction to life, translating the instruction, compiling the instruction, and / or interpreting the instruction.

[0054]

[0065] As shown above, Figure 2 is provided as an example. Other examples may differ from those described with respect to Figure 2.

[0055]

[0066] Figure 3 is a diagram of an exemplary environment 300 with an SNPN and the network associated with the home SP of UE120. This SNPN is labeled as the visited SNPN (V-SNPN) because UE120 visits this SNPN in exemplary environment 300. An SNPN is a network that provides wireless access using wireless access technologies such as 5G. An SNPN is a private network deployed separately from public networks such as Public Land Mobile Networks (PLMNs). In some embodiments, an SNPN can have no dependency on public networks. An SNPN can provide network services to a defined user organization or group of organizations. Network entities associated with an SNPN are shown to the left of the dashed line. Network entities associated with the home SP are shown to the right of the dashed line. Interfaces between network entities are labeled (e.g., N1, N2, etc.). The term "network entity" is used interchangeably with "network function" in this specification. The functions and / or networks in exemplary environment 300 can be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0056]

[0067] An SNPN can broadcast system information that a UE120 can use to access the SNPN. Information broadcast by an SNPN can include a PLMN identifier (which can be a private PLMN identifier from the Mobile Country Code (MCC) 999 range), a Network Identifier (NID), and optionally, a human-readable network name. A UE120 can consist of one or more SNPN subscriptions. In SNPN access mode, a UE120 can only register with networks that broadcast both a PLMN identifier and an NID and for which the UE120 has credentials. In some deployments, SNPNs may not support interconnection or roaming. For example, a UE120 may not be able to access a first SNPN using credentials associated with a second SNPN. Another example is a UE120 not being able to access an SNPN using credentials associated with a PLMN.

[0057]

[0068] Several technologies described herein enable the UE120 to access non-public networks (e.g., SNPNs) using third-party credentials, such as those provided by the UE120's home SP. For example, the UE120 can successfully select and register an SNPN that supports access to the UE120's home SP subscription. Supported home SP types may include PLMNs, SNPNs, and other credential providers. The UE120 may be able to access SNPN services such as local IP access and internet access, as well as home SP services such as voice services.

[0058]

[0069] As shown, the SNPN includes an access and mobility management function (AMF) 305, an SMF 310, an access node 315 (shown as (R)AN to indicate that this access node may or may not be a wireless access node), a UPF 320, a UDM 325, an AUSF 330, an AAA proxy (AAA-P) 335, a policy billing function (PCF) 340 (shown as a destination PCF (vPCF)), a network slice selection function (NSSF) 345, and a data network 350. Further as shown, the home SP is associated with an AAA server 355, a proxy call session control function (P-CSCF) 360, a serving call session control function (S-CSCF) 365, and an IMS home subscriber server (IMS-HSS) 370. Further as shown, functions 360, 365, and 370 may be considered part of the home SP domain associated with the home SP. The home SP can be a credential provider. The network functions 305, 310, 315, 320, 325, 330, 335, 340, 345, 355, 360, 365, and 370 described above can be implemented as devices, logical functions, or combinations thereof. For example, each of the functional elements shown in Figure 3 may be implemented on one or more devices associated with a wireless telecommunications system. In some embodiments, one or more of the functional elements may be implemented on physical devices such as access points, base stations, servers, and / or gateways. In some embodiments, one or more of the functional elements may be implemented on computing devices in a cloud computing environment.

[0059]

[0070] Among the many examples, the AMF305 includes one or more devices that serve as a termination point for non-access tier (NAS) signaling and / or mobility management.

[0060]

[0071] The SMF310 includes one or more devices that support the establishment, modification, and release of communication sessions in a wireless telecommunications system. For example, the SMF310 can configure traffic steering policies on the UPF320 and / or enforce UE network address allocation and policies. In some embodiments, the SMF310 can provide protocol configuration option (PCO) messaging to the UE120 based at least in part on information received from one or more other network entities.

[0061]

[0072] The access node 315 can provide the UE120 with access to the SNPN, for example, via a wireless interface. For example, the access node 315 may include the BS110, a wireless unit (RU), a distributed unit (DU), or a central unit (CU), as described in relation to Figures 1 and 2.

[0062]

[0073] The UPF320 includes one or more devices that act as anchor points for mobility within and / or between RATs. The UPF320 can apply rules to packets, among many others, regarding packet routing, traffic reporting, and / or user plane quality of service (QoS). In some embodiments, the UPF320 can handle the establishment and management of tunnels with networks provided by home SPs, as described in more detail elsewhere in this specification.

[0063]

[0074] The UDM325 includes one or more devices for storing user data and profiles. The UDM325 can be used for fixed access and / or mobile access.

[0064]

[0075] The AUSF330 includes one or more devices that act as an authentication server in a wireless telecommunications system and support the process of authenticating the UE120. In some embodiments, as described in more detail elsewhere in this specification, the AUSF330 can communicate with an AAA server 355 (for example, via an AAA proxy 335) to authenticate the UE120.

[0065]

[0076] The AAA proxy 335 includes one or more devices that interface with the AAA server 355. In some embodiments, the AAA proxy 335 can be the AUSF 330, as shown in the exemplary environment 300. In some embodiments, the AAA proxy 335 can be separate from the AUSF 330. In some embodiments, the SNPN can be implemented without the AAA proxy. For example, the AAA proxy 335 may be considered optional.

[0066]

[0077] Among many examples, the PCF340 includes one or more devices that provide a policy framework incorporating network slicing, roaming, packet processing, and / or mobility management.

[0067]

[0078] The NSSF345 includes one or more devices that select network slice instances for the UE120. Network slicing allows an operator to deploy multiple substantially independent end-to-end networks (called slices) using potentially the same infrastructure. In some embodiments, each slice can be customized for different services.

[0068]

[0079] The data network 350 includes one or more wired and / or wireless data networks. For example, the data network 350 can include IMS, PLMN, local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), private networks such as corporate intranets, ad hoc networks, the internet, fiber optic-based networks, cloud computing networks, third-party service networks, operator service networks, SNPNs, and / or combinations of these or other types of networks. In some embodiments, the UE 120 can access services provided in the home SP domain via the data network 350, such as via the “open internet” or via a tunnel to the home SP. The tunnel may be configured using configuration information provided from the AAA server 355 to the UPF 320 via one or more network entities, as described elsewhere in this specification.

[0069]

[0080] The AAA server 355 includes one or more devices that provide functionality to support authentication, authorization, accounting, etc. In some embodiments, the AAA server 355 can use communication protocols such as Remote Authentication Dial-In User Service (RADIUS), Diameter, etc. In some embodiments, the AAA server 355 may be associated with a data network (DN), such as a data network 350. For example, the AAA server 355 can be DN-AAA.

[0070]

[0081] P-CSCF360 and S-CSCF365 can provide central control functions in IMS for setting up, establishing, modifying, and destroying multimedia sessions. P-CSCF360 can be an edge access function, which can be an entry point for UE120s to request services from the IMS network. P-CSCF360 can function as a proxy by accepting incoming requests and forwarding them to entities capable of servicing the incoming requests. S-CSCF365 can handle registration and session control for registered UE120s. S-CSCF365 can function as a registrar, which can make the network location information of UE120s available in IMS-HSS370. S-CSCF365 can decide whether to allow or deny service to UE120s. In some embodiments, S-CSCF can provide services such as assigning application servers to sessions, executing session requests by finding destination endpoints and signaling toward those destination endpoints, coordinating with media resource functions, and maintaining session state. The IMS-HSS370 can manage home location registration, user subscription information, user profile information, inter-network terminal authentication, wireless path encryption, integrity protection, and more.

[0071]

[0082] Communication between the AAA server 355 and the AUSF 330 or AAA proxy 335 can enable SNPN access for a UE 120 associated with the credential provider of the AAA server 355 (e.g., the entity operating the AAA server 355). This scenario may be reasonable because the functionality of the AAA server is typically already available or easily deployable within an enterprise. In some embodiments, the UE 120 can use roaming with a local breakout architecture as defined in the wireless telecommunications standard. Accessing a visited SNPN can enable access to the services of the visited SNPN. The UE 120 can be authenticated using the credential provider's AAA server 355. In some cases, subscription information is not provided by the credential provider. Therefore, a template subscription may be configured at the visited SNPN and used for visiting UEs authenticated using an external AAA server such as the AAA server 355. The template subscription may include, for example, an allowed data network name (DNN), an allowed bitrate, etc.

[0072]

[0083] Certain problems may arise when providing configuration information for accessing services provided by the home SP, such as via IMS. For example, to access services provided by the home SP, the UE120 can use configuration information, which may include the P-CSCF360 address (e.g., P-CSCF address such as an IP address, DNN, Single Network Slice Selection Assistance Information (S-NSSAI), etc.), tunnel configuration (e.g., DNN, S-NSSAI, tunneling type (e.g., Layer 2 tunneling protocol (L2TP) or IP Security (IPSec)), tunnel server address, credentials, and an indication of whether a dedicated tunnel or a shared tunnel should be established). The P-CSCF360 address can typically be provided to the UE120 via a Protocol Configuration Options (PCO) sent by the UE120's home SMF. However, in the exemplary environment 300, the home SP is not associated with an SMF. Therefore, the UE120 is unable to receive the P-CSCF360 address, which prevents the UE120 from accessing services provided by the home SP. Furthermore, if a mechanism is not provided for providing tunnel configuration from the AAA server to the 5G system, it may be difficult or impossible to configure a tunnel from a device connected to the SNPN to the home SP's domain. Also, due to the absence of an SMF associated with the home SP, tunneling between the SNPN and the home SP domain may not be possible for the UPF. If tunneling is not possible, privacy may be reduced and the use of secure tunneling protocols such as L2TP and IPSec may be prevented.With respect to Figures 5 and 6, the technologies and apparatus described herein enable the provision of such configuration information to the UE120 or UPF320, which enables the use of services provided by the IMS associated with the home SP and tunneling to the home SP's network or IMS.

[0073]

[0084] The number and arrangement of devices and networks shown in Figure 3 are provided as an example. In practice, there may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or devices and / or networks arranged differently compared to those shown in Figure 3. Furthermore, two or more devices shown in Figure 3 may be implemented within a single device, or a single device shown in Figure 3 may be implemented as multiple distributed devices. Additionally or alternatively, a set of devices in the exemplary environment 300 (e.g., one or more devices) may perform one or more functions described as being performed by another set of devices in the exemplary environment 300.

[0074]

[0085] Figure 4 shows an exemplary environment 400 with an SNPN and the network associated with the UE120's home SP. This SNPN is labeled as V-SNPN because the UE120 visits it in exemplary environment 400. Network entities associated with the SNPN are shown to the left of the dashed line. Network entities associated with the home SP are shown to the right of the dashed line. Interfaces between network entities are labeled (e.g., N1, N2). The functions and / or networks in exemplary environment 400 can be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0075]

[0086] As shown, V-SNPN includes an AMF (e.g., AMF305), an access node (e.g., access node 315), a UPF (e.g., UPF320), a PCF (e.g., vPCF340), an NSSF (e.g., NSSF345), and a data network (e.g., data network 350). These network functions and networks are described in relation to Figure 3.

[0076]

[0087] In exemplary environment 400, the home SP is associated with AUSF405 (e.g., AUSF330) and UDM410 (e.g., UDM325). Exemplary environment 400 can be considered a local breakout architecture, and a roaming architecture can be used to enable interconnection between the SNPN and the home SN network. For example, the AUSF405 and UDM410 can enable access to SNPN services (e.g., local data services or internet access). The architecture of exemplary environment 400 can be applied to home SPs implementing AUSF and UDM, such as PLMN providers, SNPN providers, etc. As shown, the AUSF405 can interface with the AMF, the UDM410 can interface with the AMF and SMF, and the AUSF405 and UDM410 can interface with each other. Furthermore, the home SP is associated with an IMS, which includes P-CSCF (e.g., P-CSCF360) and S-CSCF (e.g., S-CSCF365). In some embodiments, IMS may include IMS-HSS (e.g., IMS-HSS370).

[0077]

[0088] Specific problems can arise when providing configuration information for accessing services provided by the home SP, such as via IMS. For example, to access services provided by the home SP, UE120 can use configuration information, which may include P-CSCF addresses (e.g., P-CSCF addresses such as IP addresses, DNN, Single Network Slice Selection Assistance Information (S-NSSAI), etc.), tunnel configurations (e.g., DNN, S-NSSAI, tunneling type (e.g., Layer 2 Tunneling Protocol (L2TP) or IP Security (IPSec)), tunnel server addresses, credentials, and indications of whether a dedicated or shared tunnel should be established). The P-CSCF address can typically be provided to UE120 via a PCO sent by the UE120's home SMF. However, in exemplary environment 400, the home SP is not involved in establishing a session over the SNPN. Therefore, UE120 is unable to receive the P-CSCF address, which prevents UE120 from accessing services provided by the home SP. Furthermore, there may be no mechanism to provide tunnel configuration from the AAA server to the 5G system. Therefore, tunneling between the SNPN and the home SP domain may not be possible for the UPF, which reduces privacy and hinders the use of secure tunneling protocols such as L2TP and IPSec. The technologies and apparatus described herein with respect to Figures 7 and 8 enable the provision of such configuration information by the AUSF or UDM to the UE120 or UPF, which enables the use of services provided by the IMS associated with the home SP and tunneling to the home SP's network or IMS.

[0078]

[0089] The number and arrangement of devices and networks shown in Figure 4 are provided as an example. In practice, there may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or devices and / or networks arranged differently compared to those shown in Figure 4. Furthermore, two or more devices shown in Figure 4 may be implemented within a single device, or a single device shown in Figure 4 may be implemented as multiple distributed devices. Additionally or alternatively, a set of devices in the exemplary environment 400 (e.g., one or more devices) may perform one or more functions described as being performed by another set of devices in the exemplary environment 400.

[0079]

[0090] Figure 5 shows an example 500 of the provision of configuration information from a home SP for a UE visiting an SNPN. Example 500 includes a UE (e.g., UE120), an SMF (e.g., SMF310), a UDM (e.g., UDM325), an AAA proxy (e.g., AUSF330 and / or AAA proxy335), and an AAA server (e.g., AAA server355). Functions associated with the SNPN are shown to the left of the vertical dashed line, and functions associated with the home SP are shown to the right of the vertical dashed line. In some embodiments, the operations of Example 500 may be performed by one or more devices in an exemplary environment 300. In the example shown in Figure 5, a P-CSCF address is passed from the third-party AAA server to the 5GS when authenticating the UE, and the SMF at the visited SNPN uses that P-CSCF address to create a PCO and signals that PCO to the UE.

[0080]

[0091] In 505, the AAA server (for example, the home SP associated with the AAA server) can configure a set of configuration information. In some embodiments, the AAA server can receive configuration information. The configuration information can include any information that can be signaled to the UE via the PCO component of a message. In Example 500, the configuration information includes at least one of the following: an address, DNN, or S-NSSAI relating to a P-CSCF (for example, P-CSCF360). In some embodiments, the configuration information can indicate an association between the DNN and S-NSSAI (DNN / S-NSSAI) and the address relating to the P-CSCF. In some embodiments, the configuration information can include a tunnel configuration, as described elsewhere in this specification. This configuration information can be used by the UE120 to access services provided by the IMS of the home SP. In some embodiments, if the AAA server uses the RADIUS protocol, the configuration information can be configured using vendor-specific attribute parameters.

[0081]

[0092] In 510, the UE can be authenticated with respect to the SNMP. For example, the UE can attempt to establish a connection with the SNMP (for example, it can register with the SNMP). To establish a connection with the SNMP, the SNMP's 5G system (5GS) (for example, one or more of the SNMP's network entities in Example 300) can authenticate the UE using an AAA server. For example, an authentication procedure can be in operation between the 5GS and the AAA server. In some embodiments, an AAA proxy can handle interaction with the AAA server for the purpose of authentication.

[0082]

[0093] In 515, the AAA server can provide configuration information to the AAA proxy. In Example 500, as shown by the provision of configuration information within the dashed box, the AAA server provides configuration information to the AAA proxy during UE authentication. In some embodiments, the AAA server can provide configuration information to the AAA proxy after UE authentication (e.g., successful authentication) or before UE authentication. In some embodiments, the AAA server can provide configuration information based at least in part on UE authentication. For example, the AAA server can provide configuration information related to the UE and / or related to the services provided by the home SP that the UE is attempting to access. Additionally, or alternatively, authentication can trigger the AAA server to provide configuration information.

[0083]

[0094] In 520, the UE and SMF can identify PDU sessions. For example, the UE and SMF can attempt to establish a PDU session, or can successfully establish a PDU session. The UE can establish a PDU session related to a DNN / S-NSSAI indicated by its configuration information. For example, a PDU session may be associated with a DNN / S-NSSAI. The UE can establish a PDU session to use services provided by the home SP. For example, the UE may have a subscription to that service, and thus the DNN / S-NSSAI may become known to the UE.

[0084]

[0095] In 525, the SMF can request a subscription for the UE from the UDM. For example, the SMF in SNPN can query the UDM for that subscription. In some embodiments, the UDM can provide a template subscription based at least in part on the request for the subscription. As mentioned above, the template subscription can be used for all visiting UEs authenticated by an AAA server outside of SNPN.

[0085]

[0096] In 530, the UDM may decide to request configuration information. For example, the UDM may decide to request at least a portion of the configuration information (e.g., the address relating to the P-CSCF corresponding to the DNN / S-NSSAI associated with the PDU session). In some embodiments, the UDM may decide to request configuration information based at least in part on an explicit indication in the subscription. For example, the subscription may contain information indicating that configuration information is being requested. In some embodiments, the UDM may decide to request configuration information based at least in part on the local configuration. For example, the UDM's configuration may cause the UDM to request configuration information.

[0086]

[0097] In 535, the UDM can request configuration information from the AAA proxy. For example, the UDM can query the AAA proxy for at least a portion of the configuration information. In Example 500, the UDM queries the AAA proxy to determine whether an address for the P-CSCF has been provided to the AAA proxy (for example, by the AAA server) with respect to the DNN / S-NSSAI associated with the PDU session (for example, whether it is available to the AAA proxy). For example, the UDM can provide a request for an address for the P-CSCF, which can identify the DNN / S-NSSAI. Alternatively, the UDM can provide a request for any available configuration information for this UE. In 540, the AAA proxy can provide the UDM with the address for the P-CSCF based at least partially on the request. For example, the AAA proxy can determine that an address for the P-CSCF corresponding to the DNN / S-NSSAI is available and provide that address based at least partially on the request. Alternatively, the AAA proxy can provide all available configuration information based at least partially on the request.

[0087]

[0098] In some embodiments, the AAA proxy may provide the address relating to the P-CSCF to the SNPN's AMF, and the AMF may provide the address relating to the P-CSCF to the SMF. For example, the AAA proxy may provide the address to the AMF based at least in part on a request from the UDM (e.g., as part of the authentication procedure shown by reference number 510).

[0088]

[0099] In 545, the UDM can provide the address of the P-CSCF to the SMF in the visited SNMP. In some embodiments, the UDM can provide the address of the P-CSCF along with subscription information related to the UE and / or SMF. In 550, the SMF in the visited SNMP can provide the address of the P-CSCF to the UE. For example, the SMF can provide the address of the P-CSCF in the PCO component of a message, such as a Non-Access Layer (NAS) message. In such a case, the SMF can create a PCO, embed the address of the P-CSCF into the PCO, and deliver the PCO to the UE. The UE can use the address of the P-CSCF to access services provided by the home SP, at least partially based on the DNN / S-NSSAI. In this way, a UE visiting an SNMP can obtain the address of the P-CSCF associated with a home SNMP that does not have an SMF, thereby enabling the UE to access subscribed services provided by the IMS of the home SNMP.

[0089]

[0100] As shown above, Figure 5 is provided as an example. Other examples may differ from those described with respect to Figure 5.

[0090]

[0101] Figure 6 shows an example 600 of the provision of configuration information from a home SP for a UE accessing an SNPN, as described in this disclosure. Example 600 includes a UE (e.g., UE120), an SMF (e.g., SMF310), a UDM (e.g., UDM325), an AAA proxy (e.g., AUSF330 and / or AAA proxy335), and an AAA server (e.g., AAA server355). Functions associated with the SNPN are shown to the left of the vertical dashed line, and functions associated with the home SP are shown to the right of the vertical dashed line. In some embodiments, the operations of Example 600 may be performed by one or more devices in an exemplary environment 300. Example 600 shows how tunnel configuration may be passed from a third-party AAA server to a 5GS associated with the SNPN when authenticating the UE, and how the UPF may establish a tunnel based at least in part on the tunnel configuration received from the AAA server. Example 600 relates to a data network provider, which is referred to as a home service provider (SP) in relation to Example 600. In some aspects, a data network provider can be a company.

[0091]

[0102] In 605, the AAA server (for example, the home data network provider associated with the AAA server) can configure a set of configuration information. In some embodiments, the AAA server can receive configuration information. In Example 600, the configuration information includes a tunnel configuration. The tunnel configuration may include, for example, information indicating the DNN, S-NSSAI, tunneling type (e.g., L2TP, IPSec), tunnel server addresses (e.g., the address of the L2TP network server, the address of the IPSec network server), one or more credentials (e.g., a tunnel password), and an indication of whether a dedicated or shared tunnel should be established. In some embodiments, the configuration information may indicate an association between the DNN / S-NSSAI and one or more elements of the tunnel configuration. This configuration information may be used by the UPF to establish a tunnel associated with enabling the UE to access services provided by the home SP's IMS. In some embodiments, if the AAA server uses the RADIUS protocol, the configuration information may be configured using vendor-specific attribute parameters.

[0092]

[0103] In 610, the UE can be authenticated with respect to the SNMP. For example, the UE can attempt to establish a connection with the SNMP. To establish a connection with the SNMP, the SNMP's 5GS (for example, one or more of the SNMP's network entities in Example 300) can authenticate the UE using an AAA server. For example, an authentication procedure can be in operation between the 5GS and the AAA server. In some embodiments, an AAA proxy can handle interaction with the AAA server for the purpose of authentication.

[0093]

[0104] In 615, the AAA server can provide configuration information to the AAA proxy. In Example 600, as shown by the provision of configuration information within the dashed box, the AAA server provides configuration information to the AAA proxy during UE authentication. In some embodiments, the AAA server can provide configuration information to the AAA proxy after UE authentication (e.g., successful authentication) or before UE authentication. In some embodiments, the AAA server can provide configuration information based at least partially on UE authentication. For example, the AAA server can provide configuration information related to the UE and / or related to services provided by the home SP that the UE is attempting to access. Additionally, or alternatively, authentication can trigger the AAA server to provide configuration information. Note that the AAA proxy is optional, and in some embodiments, the AAA server can communicate with another network function of the SNPN.

[0094]

[0105] In 620, the SMF can identify PDU sessions. For example, the UE and SMF can attempt to establish a PDU session, or can successfully establish a PDU session. The SMF can establish a PDU session related to the DNN / S-NSSAI indicated by the configuration information. For example, a PDU session may be associated with the DNN / S-NSSAI. The UE and / or SMF can establish a PDU session to use services provided by the home SP.

[0095]

[0106] In 625, the SMF can request a subscription from the UDM for a UE. For example, the SMF in an SNPN can query the UDM for that subscription. In some embodiments, the subscription can be a template subscription. As mentioned above, a template subscription can be used for all visiting UEs authenticated by an AAA server outside the SNPN. In 630, the UDM can decide to request configuration information. For example, the UDM can decide to request at least some of the configuration information (e.g., the tunnel configuration associated with the DNN / S-NSSAI associated with the PDU session). In some embodiments, the UDM can decide to request configuration information based at least in part on an explicit indication in the subscription. For example, the subscription can include information indicating that configuration information is being requested. In some embodiments, the UDM can decide to request configuration information based at least in part on a local configuration. For example, the UDM's configuration can cause the UDM to request configuration information.

[0096]

[0107] In 635, the UDM can request configuration information from the AAA proxy. For example, the UDM can query the AAA proxy for at least a portion of the configuration information. In Example 600, the UDM queries the AAA proxy to determine whether a tunnel configuration is provided to the AAA proxy (e.g., made available to the AAA proxy) (e.g., made available to the AAA proxy) with respect to the DNN / S-NSSAI associated with the PDU session (e.g., by the AAA server). For example, the UDM can provide a request for the tunnel configuration, which can identify the DNN / S-NSSAI. Alternatively, the UDM can provide a request for any available configuration information for this UE. In 640, the AAA proxy can provide the tunnel configuration to the UDM based at least partially on the request. For example, the AAA proxy can determine that a tunnel configuration corresponding to the DNN / S-NSSAI is available and provide that tunnel configuration based at least partially on the request. Alternatively, the AAA proxy can provide all available configuration information based at least partially on the request. In some embodiments, the AAA proxy can be optional or not implemented in the SNPN.

[0097]

[0108] In some embodiments, the AAA proxy may provide the tunnel configuration to the SNPN's AMF, and the AMF may provide the tunnel configuration to the SMF. For example, the AAA proxy may provide the tunnel configuration to the AMF at least in part based on an authentication request from the AMF (for example, as part of the authentication procedure shown by reference number 610).

[0098]

[0109] In 645, the UDM can provide tunnel information to the SMF in the visited SNPN. In some embodiments, the UDM can provide tunnel information along with subscription information related to the UE and / or SMF. In some embodiments, the subscription information can include representations for the SMF to authenticate the UE using an AAA server. In 650, the SMF in the visited SNPN can provide tunnel information to the UPF. In some embodiments, the SMF can authenticate the UE using an AAA server, such as in connection with establishing a PDU session and based at least in part on representations in the subscription information. In such examples, the SMF can receive tunnel information from the AAA server. In some embodiments, the SMF can communicate with the AAA server via the UPF (for example, the AAA proxy and the UPF can be the same entity). In some other embodiments, the SMF can communicate directly with the AAA server. In 655, the UPF can establish a tunnel, or configure a tunnel, at least in part on configuration information. For example, if the tunnel configuration indicates the use of a shared tunnel, the UPF can configure a previously established tunnel, at least partially based on the tunnel configuration. If the tunnel configuration does not indicate the use of a shared tunnel, the UPF can establish a tunnel, at least partially based on the tunnel configuration. In this way, a third-party AAA server may provide the tunnel configuration to the UPF associated with the UE visiting the SNMP, which allows the UPF to establish a tunnel to the network associated with the home SP associated with the AAA server, thereby facilitating and improving security access to home SP services via SNMP when the home SP does not implement SMF.

[0099]

[0110] As shown above, Figure 6 is provided as an example. Other examples may differ from those described with respect to Figure 6.

[0100]

[0111] Figure 7 shows an example 700 of the provision of configuration information from a home SP for a UE visiting an SNPN, as described in this disclosure. Example 700 includes a UE (e.g., UE120), an SMF (e.g., SMF310), and a UDM (e.g., UDM410). Functions associated with the SNPN are shown to the left of the vertical dashed line, and functions associated with the home SP are shown to the right of the vertical dashed line. In some embodiments, the operation of Example 700 may be performed by one or more devices in an exemplary environment 400. Example 700 shows how an address relating to a P-CSCF may be configured in a third-party UDM (e.g., associated with a home SP and outside of the SNPN) and signaled to a visited SMF, and how the visited SMF may provide an address relating to a P-CSCF to the UE, such as by creating a PCO using the address relating to the P-CSCF and signaling that PCO to the UE.

[0101]

[0112] In 705, the UDM (for example, the home SP associated with the UDM) can configure a set of configuration information. In some embodiments, the UDM can receive configuration information. The configuration information can include any information that can be signaled to the UE via the PCO component of the message. In Example 700, the configuration information includes at least one of the following: an address, DNN, or S-NSSAI relating to a P-CSCF (for example, P-CSCF360). In some embodiments, the configuration information can indicate an association between the DNN / S-NSSAI and the address relating to the P-CSCF. This configuration information can be used by the UE120 to access services provided by the IMS of the home SP.

[0102]

[0113] In 710, the UE can be authenticated with respect to the SNMP. For example, the UE can attempt to establish a connection with the SNMP. To establish a connection with the SNMP, the SNMP's 5GS (for example, one or more of the SNMP's network entities in Example 400) can authenticate the UE using the AUSF associated with the home SP (for example, AUSF405, not shown in Figure 7). For example, an authentication procedure can be in operation between the 5GS and the AUSF.

[0103]

[0114] In section 715, the UE and SMF can identify PDU sessions. For example, the UE and / or SMF can attempt to establish a PDU session, or can successfully establish a PDU session. The UE can establish a PDU session related to a DNN / S-NSSAI indicated by its configuration information. For example, a PDU session may be associated with a DNN / S-NSSAI. The UE can establish a PDU session to use services provided by the home SP. For example, the UE may have a subscription to that service, and thus the DNN / S-NSSAI may become known to the UE.

[0104]

[0115] In 720, the SMF can request session management subscription information from the UDM. Session management subscription information (also called session management subscription data) includes data used for PDU session establishment associated with one or more subscriptions associated with the UE. In some embodiments, the SMF can request session management subscription information based at least partially on DNN / S-NSSAI (such as DNN / S-NSSAI identified by configuration information), supported features, PLMN identifiers, etc. In some embodiments, the SMF can request configuration information (implicitly or explicitly, for example, based at least partially on having requested session management subscription information).

[0105]

[0116] In 725, the UDM can provide the address of the P-CSCF to the SMF in the visited SNPN. In some embodiments, the UDM can provide the address of the P-CSCF together with, or as part of, the session management subscription information requested by the SMF. In 730, the SMF in the visited SNPN can provide the address of the P-CSCF to the UE. For example, the SMF can provide the address of the P-CSCF in the PCO component of a message, such as a NAS message. In such a case, the SMF can create a PCO, embed the address of the P-CSCF into the PCO, and deliver the PCO to the UE. The UE can use the address of the P-CSCF to access services provided by the home SP, at least in part, based on the DNN / S-NSSAI. In this way, a UE visiting an SNPN can obtain the address of the P-CSCF associated with a home SN that does not have an SMF, thereby enabling the UE to access subscribed services provided by the home SN's IMS.

[0106]

[0117] As shown above, Figure 7 is provided as an example. Other examples may differ from those described with respect to Figure 7.

[0107]

[0118] Figure 8 shows an example 800 of the provision of configuration information from a home SP for a UE visiting an SNPN, as described in this disclosure. Example 800 includes a UE (e.g., UE120), an SMF (e.g., SMF310), and a UDM (e.g., UDM410). Functions associated with the SNPN are shown to the left of the vertical dashed line, and functions associated with the home SP are shown to the right of the vertical dashed line. In some embodiments, the operation of Example 800 may be performed by one or more devices in an exemplary environment 400.

[0108]

[0119] In 805, the UDM (for example, the home SP associated with the UDM) can configure a set of configuration information. In some embodiments, the UDM can receive configuration information. In Example 800, the configuration information includes a tunnel configuration. The tunnel configuration may include, for example, information indicating the DNN, S-NSSAI, tunneling type (e.g., L2TP, IPSec), tunnel server address, one or more credentials, and an indication of whether a dedicated tunnel or a shared tunnel should be established. In some embodiments, the configuration information may indicate an association between the DNN / S-NSSAI and one or more elements of the tunnel configuration. This configuration information may be used by the UPF to establish a tunnel associated with enabling the UE to access services provided by the home SP's IMS.

[0109]

[0120] In 810, the UE can be authenticated with respect to the SNMP. For example, the UE can attempt to establish a connection with the SNMP. To establish a connection with the SNMP, the SNMP's 5GS (for example, one or more of the SNMP's network entities in Example 400) can authenticate the UE using the AUSF associated with the home SP (for example, AUSF405, not shown in Figure 8). For example, an authentication procedure can be in operation between the 5GS and the AUSF.

[0110]

[0121] In section 815, the UE and SMF can identify PDU sessions. For example, the UE and SMF can attempt to establish a PDU session, or can successfully establish a PDU session. The UE can establish a PDU session related to a DNN / S-NSSAI indicated by its configuration information. For example, a PDU session may be associated with a DNN / S-NSSAI. The UE can establish a PDU session to use services provided by the home SP. For example, the UE may have a subscription to that service, and thus the DNN / S-NSSAI may become known to the UE.

[0111]

[0122] In 820, the SMF can request session management subscription information from the UDM. Session management subscription information includes data used for PDU session establishment associated with one or more subscriptions associated with the UE. In some embodiments, the SMF can request session management subscription information based at least partially on DNN / S-NSSAI (such as DNN / S-NSSAI identified by configuration information), supported features, PLMN identifiers, etc. In some embodiments, the SMF can request configuration information (implicitly or explicitly, for example, based at least partially on having requested session management subscription information).

[0112]

[0123] In 825, the UDM can provide the tunnel configuration to the SMF in the visited SNPN. In some embodiments, the UDM can provide the tunnel configuration together with, or as part of, the session management subscription information requested by the SMF. In 830, the SMF in the visited SNPN can provide the tunnel configuration to the UPF. In 835, the UPF can establish a tunnel based at least partially on the configuration information, or configure a tunnel based at least partially on the configuration information. For example, if the tunnel configuration indicates the use of a shared tunnel, the UPF can configure a previously established tunnel based at least partially on the tunnel configuration. If the tunnel configuration does not indicate the use of a shared tunnel, the UPF can establish a tunnel based at least partially on the tunnel configuration. In this manner, the tunnel configuration may be provided from the UDM associated with the home SP of a UE visiting the SNPN to the UPF in the SNPN, which enables the UPF to establish a tunnel to the network associated with the home, thereby facilitating access to home SP services over the SNPN when the home SP does not implement an SMF.

[0113]

[0124] As shown above, Figure 8 is provided as an example. Other examples may differ from those described with respect to Figure 8.

[0114]

[0125] Figure 9 is a flowchart of an exemplary wireless communication method 900. Method 900 can be performed, for example, by a first network entity (e.g., SMF310, SMF in Figure 4, AMF305, AMF in Figure 4).

[0115]

[0126] In 910, the first network entity can identify a PDU session with the UE. For example, the first network entity can identify a PDU session with the UE (e.g., UE120) as described above in relation to Figure 5 in 520, Figure 6 in 620, Figure 7 in 715, and Figure 8 in 815, for example, using the session establishment component 1208 shown in Figure 12. In some embodiments, the first network entity may be associated with a second data network provider, such as a second service provider. The second data network provider may provide a network, such as an SNPN or a public network (and the first network entity may be associated with that network). Configuration information may be associated with a first data network provider, such as a first service provider. In some embodiments, the first network entity is an authentication, authorization, and accounting server (e.g., AAA server 355), and configuration information is obtained through one or more third network entities (e.g., AUSF330, AAA proxy 335, UDM325, AMF305) associated with a standalone non-public network. In some embodiments, the network entity associated with the first service provider is a unified data management function (e.g., UDM410) for the network associated with the first service provider. The configuration information may include tunnel configurations relating to tunnels between a second network entity associated with the first network and a second network associated with the first data network provider.

[0116]

[0127] In 920, the first network entity can obtain configuration information associated with a first data network provider, where the first network entity is associated with a network provided by a second data network provider. For example, the first network entity (using, for example, the receiving component 1202 shown in Figure 12) can obtain configuration information associated with a first data network provider (e.g., a service provider), at least in part on identifying a PDU session, as described above in relation to, for example, Figures 5 in 525 and 545, Figure 6 in 625 and 645, Figure 7 in 720 and 725, and Figure 8 in 820 and 825, where the first network entity is associated with a network (e.g., an SNPN or public network) provided by a second data network provider (e.g., a service provider). In some embodiments, obtaining configuration information further comprises requesting a template subscription indicating the request for configuration information from a third network entity (e.g., AMF305, UDM325) associated with a standalone non-public network, where the third network entity is an access and mobility management function or an integrated data management function. In some embodiments, requesting a template subscription indicating the request for configuration information is at least in part based on successful authentication of the UE. In some embodiments, obtaining configuration information further comprises obtaining configuration information from a network entity (e.g., AAA server 355, UDM410) associated with a first service provider.

[0117]

[0128] At 930, the first network entity can transmit configuration information to the UE or to a second network entity associated with a standalone non-public network. For example, the first network entity can transmit configuration information to the UE or to a second network entity associated with a standalone non-public network (e.g., UPF320, UPF in Figure 4) as described above in relation to Figure 5 at 550, Figure 6 at 650, Figure 7 at 730, and Figure 8 at 830, for example, using the transmit component 1204 shown in Figure 12. In some embodiments, transmitting configuration information to the UE further comprises transmitting configuration information to the UE in the PCO component of the message. In some embodiments, the configuration information transmitted to the UE includes a proxy call session control function address relating to a proxy call session control function associated with the first service provider. In some embodiments, the configuration information transmitted to the second network entity includes a tunnel configuration relating to a tunnel between the second network entity and the network associated with the first service provider, where the second network entity is a user plane function associated with a UE (e.g., UPF320, UPF in Figure 4). In some embodiments, the tunnel configuration relates to a shared tunnel between multiple UEs and the network associated with the first service provider.

[0118]

[0129] Figure 9 shows an exemplary block of Method 900, but in some embodiments, Method 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to the block shown in Figure 9. Additionally or alternatively, two or more blocks of Method 900 may be executed in parallel.

[0119]

[0130] Figure 10 is a flowchart of an exemplary wireless communication method 1000. Method 1000 can be performed, for example, by a first network entity (e.g., UDM325, UDM410, AMF305, AMF in Figure 4).

[0120]

[0131] In 1010, the first network entity is capable of receiving requests from the second network entity for configuration information associated with the first service provider, where the first and second network entities are associated with a standalone, non-public network provided by the second service provider. For example, the first network entity is capable of receiving requests from the second network entity (e.g., AMF305, SMF310, AMF in Figure 4, SMF in Figure 4) for configuration information associated with the first service provider, as described above in relation to Figure 5 in 525 and Figure 6 in 625, where the first and second network entities are associated with a standalone, non-public network provided by the second service provider. In some embodiments, the requests are received at least in part on a PDU session established (e.g., identified) between the UE and the second network entity. In some embodiments, the configuration information includes a proxy call session control function address relating to a proxy call session control function (P-CSCF360, P-CSCF in Figure 4) associated with the first service provider. In some embodiments, the configuration information includes a tunnel configuration relating to a tunnel between a second network entity and the network associated with the first service provider.

[0121]

[0132] In 1020, the first network entity can determine (for example, using the decision component 1408 shown in Figure 14) that configuration information will be obtained from the proxy entity based at least in part on a request for that configuration information, or at least in part on the configuration of the first network entity. The dashed edge of the block shown by 1020 indicates that the action shown by 1020 is optional.

[0122]

[0133] In 1030, the first network entity can obtain configuration information from a proxy entity associated with a standalone non-public network, at least in part, based on a request for configuration information. For example, the first network entity (using, for example, the receiving component 1402 shown in Figure 14) can obtain configuration information from a proxy entity associated with a standalone non-public network (e.g., AUSF330, AAA proxy 335), at least in part, based on a request for configuration information, as described above in relation to Figure 5 in 535 and 540, and Figure 6 in 635 and 640.

[0123]

[0134] In some embodiments, obtaining configuration information further comprises requesting configuration information from a proxy entity, wherein the configuration information is available to the proxy entity at least in part on the authentication of the UE with respect to a standalone non-public network, wherein the configuration information is related to network slice selection assistance information (e.g., S-NSSAI) or to a data network name (e.g., DNN) associated with network slice selection assistance information (cumulatively, DNN / S-NSSAI).

[0124]

[0135] In 1040, the first network entity can transmit configuration information to the second network entity. For example, the first network entity can transmit configuration information to the second network entity (for example, using the transmitting component 1404 shown in Figure 14) as described above in relation to Figure 5 in 545 and Figure 6 in 645. In some embodiments, the configuration information is transmitted to the second network entity as part of the subscription information associated with the second network entity.

[0125]

[0136] In some embodiments, the first network entity is an integrated data management function (UDM325, UDM410) or an access and mobility management function (AMF305), and the second network entity is a session management function (SMF310, SMF in Figure 4).

[0126]

[0137] Figure 10 shows an exemplary block of Method 1000, but in some embodiments, Method 1000 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to the block shown in Figure 10. Additionally or alternatively, two or more blocks of Method 1000 may be executed in parallel.

[0127]

[0138] Figure 11 is a flowchart of an exemplary wireless communication method 1100. Method 1100 can be performed, for example, by a first network entity (e.g., AUSF330, AAA proxy 335).

[0128]

[0139] In 1110, the first network entity can receive configuration information relating to a UE accessing a standalone non-public network associated with the first network entity from a network entity associated with the first service provider. For example, the first network entity can receive configuration information relating to a UE accessing a standalone non-public network associated with the first network entity from a network entity associated with the first service provider (e.g., AAA server 355), for example, using the receiving component 1602 shown in Figure 16, as described above in relation to Figure 5 in 515 and Figure 6 in 615, where the standalone non-public network is associated with the second service provider. In some embodiments, receiving the configuration information is at least in part based on the UE being authenticated on the standalone non-public network. In some embodiments, the configuration information includes at least one of the following: a P-CSCF address relating to a proxy call session control function (P-CSCF) associated with the first service provider, networking slice selection assistance information associated with the first service provider, or a data network name associated with the first service provider.

[0129]

[0140] In some embodiments, the configuration information includes a tunnel configuration relating to a tunnel between a second network entity and a network associated with a first service provider, wherein the tunnel configuration includes at least one of the following: a data network name associated with the first service provider, networking slice selection assistance information associated with the first service provider, a tunneling type associated with the tunnel, a tunnel server address associated with the tunnel, credentials associated with the tunnel, or an indication of whether the tunnel is a shared or dedicated tunnel.

[0130]

[0141] In 1120, the first network entity can receive requests for at least some of the configuration information from a second network entity associated with a standalone non-public network. For example, the first network entity can receive requests for at least some of the configuration information from a second network entity associated with a standalone non-public network (e.g., AMF305, SMF310, UDM325) (for example, using the receiving component 1602 shown in Figure 16) as described above in relation to Figure 5 in 535 and Figure 6 in 635.

[0131]

[0142] In 1130, the first network entity can send configuration information to the second network entity based at least partially on the request. For example, the first network entity can send configuration information to the second network entity based at least partially on the request, for example, using the sending component 1604 shown in Figure 16.

[0132]

[0143] In some embodiments, the first network entity is an authentication server function, and the second network entity is an access and mobility management function or an integrated data management function.

[0133]

[0144] Figure 11 shows an exemplary block of Method 1100, but in some embodiments, Method 1100 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to the block shown in Figure 11. Additionally or alternatively, two or more blocks of Method 1100 may be executed in parallel.

[0134]

[0145] Figure 12 is a block diagram of an exemplary device 1200 for wireless communication. Device 1200 can be a first network entity (e.g., SMF310, SMF in Figure 4, AMF305, AMF in Figure 4), or a first network entity can include device 1200. In some embodiments, device 1200 includes a receiving component 1202 and a transmitting component 1204, and the receiving component 1202 and the transmitting component 1204 can be in a state of communication with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1200 can communicate with another device 1206 (such as a UE, base station, or another wireless communication device) using the receiving component 1202 and the transmitting component 1204. As further shown, device 1200 can include a session establishment component 1208, among many other examples.

[0135]

[0146] In some embodiments, the apparatus 1200 may be configured to perform one or more operations described herein in relation to Figures 3 to 8. Additionally, or alternatively, the apparatus 1200 may be configured to perform one or more processes, or combinations thereof, described herein, such as method 900 in Figure 9. In some embodiments, the apparatus 1200, and / or one or more components shown in Figure 12, may include one or more components of the first network entity described above in relation to Figure 2. Additionally, or alternatively, one or more components shown in Figure 12 may be implemented within one or more components described above in relation to Figure 2. Additionally, or alternatively, one or more components of that set of components may be implemented at least partially as software stored in memory. For example, a component (or part of a component) may be implemented as instructions or code stored in a non-temporary computer-readable medium, executable by a controller or processor to perform the function or operation of that component.

[0136]

[0147] The receiving component 1202 is capable of receiving communications from the device 1206, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1202 is capable of providing the received communications to one or more other components of the device 1200. In some embodiments, the receiving component 1202 is capable of performing signal processing on the received communications (among many examples, filtering, amplification, demodulation, analog / digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference rejection, or decoding) and providing the processed signals to one or more other components of the device 1206. In some embodiments, the receiving component 1202 may include one or more antennas, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof of the first network entity described above in relation to Figure 2.

[0137]

[0148] The transmitting component 1204 is capable of transmitting communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some embodiments, one or more other components of the device 1206 are capable of generating communications and providing the generated communications to the transmitting component 1204 for transmission to the device 1206. In some embodiments, the transmitting component 1204 is capable of performing signal processing on the generated communications (among many examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) and transmitting the processed signals to the device 1206. In some embodiments, the transmitting component 1204 may include one or more antennas, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or combinations thereof of the first network entity described above in relation to Figure 2. In some embodiments, the transmitting component 1204 may be located in the same place as the receiving component 1202 in the transceiver. In some embodiments, the transmitting component 1204 can interface with a radio unit, which may or may not be located in the same location as the transmitting component 1204. For example, the transmitting component 1204 may be associated with a distributed unit (DU) in a discrete radio access network deployment.

[0138]

[0149] The session establishment component 1208 is capable of identifying a PDU session with the UE. The receiving component 1202 is capable of obtaining configuration information associated with a first service provider, at least in part, based on having identified the PDU session, where the first network entity is associated with a standalone, non-public network provided by a second service provider. The transmitting component 1204 is capable of transmitting the configuration information to the UE or to a second network entity associated with a standalone, non-public network.

[0139]

[0150] The number and arrangement of components shown in Figure 12 are provided as an example. In practice, there may be additional components, fewer components, different components, or components arranged differently compared to those shown in Figure 12. Furthermore, two or more components shown in Figure 12 may be implemented within a single component, or a single component shown in Figure 12 may be implemented as multiple distributed components. Additionally, or alternatively, a set of (one or more) components shown in Figure 12 may perform one or more functions described as being performed by another set of components shown in Figure 12.

[0140]

[0151] Figure 13 shows an example of a hardware embodiment 1300 for a device 1305 employing the processing system 1310. The device 1305 can be a first network entity.

[0141]

[0152] The processing system 1310 may be implemented with a bus architecture collectively represented by bus 1315. Bus 1315 can include any number of interconnected buses and bridges depending on the specific application of the processing system 1310 and the overall design constraints. Bus 1315 links together various circuits, including the processor 1320, the indicated components, and one or more processors and / or hardware components represented by the computer-readable medium / memory 1325. Bus 1315 can also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0142]

[0153] The processing system 1310 may be coupled to a transceiver 1330. The transceiver 1330 may be coupled to one or more antennas 1335. The transceiver 1330 provides means for communicating with various other devices via a transmission medium. The transceiver 1330 receives signals from one or more antennas 1335, extracts information from the received signals, and provides the extracted information to the processing system 1310, specifically to the receiving component 1202. In addition, the transceiver 1330 receives information from the processing system 1310, specifically to the transmitting component 1204, and generates signals that will be applied to one or more antennas 1335 based at least in part on the received information. In some examples, the device 1305 may include an interface for communication with one or more network nodes, such as via a backhaul, midhaul, or fronthaul link. In some embodiments, the interface may include a transceiver 1330 and / or one or more antennas 1335. In some other embodiments, the device 1305 may not include the transceiver 1330 and / or one or more antennas 1335.

[0143]

[0154] The processing system 1310 includes a processor 1320 coupled to a computer-readable medium / memory 1325. The processor 1320 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1325. When executed by the processor 1320, the software causes the processing system 1310 to perform various functions described herein with respect to any particular device. The computer-readable medium / memory 1325 may also be used to store data manipulated by the processor 1320 when the software is executed. The processing system further includes at least one of the components shown. These components may be software modules residing in / stored in the computer-readable medium / memory 1325 that run on the processor 1320, one or more hardware modules coupled to the processor 1320, or any combination thereof.

[0144]

[0155] In some embodiments, the processing system 1310 can be a component of the base station 110 and can include memory 242, and / or at least one of the TX MIMO processor 230, RX processor 238, and / or controller / processor 240. In some embodiments, the processing system 1310 can be a component of the CU. In some embodiments, the processing system 1310 can be a component of the DU. In some embodiments, the processing system 1310 can be a component of the RU. In some embodiments, the processing system 1310 can be a component of the RU. In some embodiments, the processing system 1310 can be one or more components of a 5G system as shown in Figures 3 and 4, and can include memory and one or more processors. In some embodiments, the device for wireless communication 1305 includes means for identifying a PDU session with the UE, means for obtaining configuration information associated with a first service provider, and means for the first network entity to transmit the configuration information to a UE associated with a standalone non-public network provided by the second service, or to a second network entity associated with a standalone non-public network. The aforementioned means may be one or more of the aforementioned components of the apparatus 1200 and / or the processing system 1310 of the apparatus 1305, which are configured to perform the functions enumerated by the aforementioned means. As in some embodiments described elsewhere in this specification, the processing system 1310 may include a TX MIMO processor 230, a receiving processor 238, and / or a controller / processor 240. In one configuration, the aforementioned means may be a TX MIMO processor 230, a receiving processor 238, and / or a controller / processor 240, which are configured to perform the functions and / or operations enumerated herein.

[0145]

[0156] Figure 13 is provided as an example. Other examples may differ from those described with respect to Figure 13.

[0146]

[0157] Figure 14 is a block diagram of an exemplary device 1400 for wireless communication. Device 1400 can be a first network entity (e.g., UDM325, UDM410, AMF305, AMF in Figure 4), or a first network entity can include device 1400. In some embodiments, device 1400 includes a receiving component 1402 and a transmitting component 1404, and the receiving component 1402 and the transmitting component 1404 can be in communication with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1400 can communicate with another device 1406 (such as a UE, base station, or another wireless communication device) using the receiving component 1402 and the transmitting component 1404. Further shown, device 1400 can include a determination component 1408, among many other examples.

[0147]

[0158] In some embodiments, the device 1400 may be configured to perform one or more operations described herein in relation to Figures 3 to 8. Additionally, or alternatively, the device 1400 may be configured to perform one or more processes, or combinations thereof, described herein, such as method 1000 in Figure 10. In some embodiments, the device 1400, and / or one or more components shown in Figure 14, may include one or more components of the first network entity described above in relation to Figure 2. Additionally, or alternatively, one or more components shown in Figure 14 may be implemented within one or more components described above in relation to Figure 2. Additionally, or alternatively, one or more components of that set of components may be implemented at least partially as software stored in memory. For example, a component (or part of a component) may be implemented as instructions or code stored in a non-temporary computer-readable medium, executable by a controller or processor to perform the function or operation of that component.

[0148]

[0159] The receiving component 1402 is capable of receiving communications from the device 1406, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1402 is capable of providing the received communications to one or more other components of the device 1400. In some embodiments, the receiving component 1402 is capable of performing signal processing on the received communications (among many examples, filtering, amplification, demodulation, analog / digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference rejection, or decoding) and providing the processed signals to one or more other components of the device 1406. In some embodiments, the receiving component 1402 may include one or more antennas, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof of the first network entity described above in relation to Figure 2.

[0149]

[0160] The transmitting component 1404 is capable of transmitting communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1406. In some embodiments, one or more other components of the device 1406 are capable of generating communications and providing the generated communications to the transmitting component 1404 for transmission to the device 1406. In some embodiments, the transmitting component 1404 is capable of performing signal processing on the generated communications (among many examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) and transmitting the processed signals to the device 1406. In some embodiments, the transmitting component 1404 may include one or more antennas, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or combinations thereof of the first network entity described above in relation to Figure 2. In some embodiments, the transmitting component 1404 may be located in the same place as the receiving component 1402 in the transceiver.

[0150]

[0161] The receiving component 1402 is capable of receiving a request from a second network entity for configuration information associated with a first service provider, where the first and second network entities are associated with a standalone non-public network provided by the second service provider, where the configuration information is associated with a UE associated with the first service provider accessing the standalone non-public network. The receiving component 1402 is capable of obtaining configuration information from a proxy entity associated with the standalone non-public network, at least in part, based on the request for configuration information. The transmitting component 1404 is capable of transmitting configuration information to the second network entity.

[0151]

[0162] The decision component 1408 can determine that configuration information will be obtained from the proxy entity at least in part on a request for that configuration information, or at least in part on the configuration of the first network entity.

[0152]

[0163] The number and arrangement of components shown in Figure 14 are provided as an example. In practice, there may be additional components, fewer components, different components, or components arranged differently compared to those shown in Figure 14. Furthermore, two or more components shown in Figure 14 may be implemented within a single component, or a single component shown in Figure 14 may be implemented as multiple distributed components. Additionally, or alternatively, a set of (one or more) components shown in Figure 14 may perform one or more functions described as being performed by another set of components shown in Figure 14.

[0153]

[0164] Figure 15 shows an example of a hardware embodiment 1500 for a device 1505 employing the processing system 1510. The device 1505 can be a first network entity.

[0154]

[0165] The processing system 1510 may be implemented with a bus architecture, which is collectively represented by bus 1515. Bus 1515 can include any number of interconnected buses and bridges, depending on the specific application of the processing system 1510 and the overall design constraints. Bus 1515 links together various circuits, including the processor 1520, the indicated components, and one or more processors and / or hardware components represented by the computer-readable medium / memory 1525. Bus 1515 can also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0155]

[0166] The processing system 1510 may be coupled to a transceiver 1530. The transceiver 1530 is coupled to one or more antennas 1535. The transceiver 1530 provides means for communicating with various other devices via a transmitting medium. The transceiver 1530 receives signals from one or more antennas 1535, extracts information from the received signals, and provides the extracted information to the processing system 1510, specifically to the receiving component 1402. In addition, the transceiver 1530 receives information from the processing system 1510, specifically to the transmitting component 1404, and generates signals that will be applied to one or more antennas 1535 based at least in part on the received information.

[0156]

[0167] The processing system 1510 includes a processor 1520 coupled to a computer-readable medium / memory 1525. The processor 1520 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1525. When executed by the processor 1520, the software causes the processing system 1510 to perform various functions described herein with respect to any particular device. The computer-readable medium / memory 1525 may also be used to store data manipulated by the processor 1520 when the software is executed. The processing system further includes at least one of the components shown. These components may be software modules residing in / stored in the computer-readable medium / memory 1525 that run on the processor 1520, one or more hardware modules coupled to the processor 1520, or any combination thereof.

[0157]

[0168] In some embodiments, the processing system 1510 can be a component of the base station 110 and can include memory 242 and / or at least one of the TX MIMO processor 230, RX processor 238, and / or controller / processor 240. In some embodiments, the processing system 1510 can be one or more components of a 5G system as shown in Figures 3 and 4 and can include memory and one or more processors. In some embodiments, the device for wireless communications 1505 includes means for receiving a request from a second network entity for configuration information associated with a first service provider, thereby means for the first and second network entities to obtain configuration information from a proxy entity associated with a standalone non-public network, at least in part on the basis of the request for configuration information, which is associated with a standalone non-public network provided by the second service provider, and means for transmitting the configuration information to the second network entity. The aforementioned means may be one or more of the aforementioned components of the apparatus 1400 and / or the processing system 1510 of the apparatus 1505, which are configured to perform the functions enumerated by the aforementioned means. As in some embodiments described elsewhere in this specification, the processing system 1510 may include a TX MIMO processor 230, a receiving processor 238, and / or a controller / processor 240. In one configuration, the aforementioned means may be a TX MIMO processor 230, a receiving processor 238, and / or a controller / processor 240, which are configured to perform the functions and / or operations enumerated herein.

[0158]

[0169] Figure 15 is provided as an example. Other examples may differ from those described with respect to Figure 15.

[0159]

[0170] Figure 16 is a block diagram of an exemplary device 1600 for wireless communication. Device 1600 can be a first network entity, or a first network entity can include device 1600. In some embodiments, device 1600 includes a receiving component 1602 and a transmitting component 1604, and the receiving component 1602 and the transmitting component 1604 can be in communication with each other (for example, via one or more buses and / or one or more other components). As shown, device 1600 can communicate with another device 1606 (such as a UE, base station, or another wireless communication device) using the receiving component 1602 and the transmitting component 1604. Further shown, device 1600 can include a communication component 1608, among many other examples.

[0160]

[0171] In some embodiments, the device 1600 may be configured to perform one or more operations described herein in relation to Figures 3 to 8. Additionally, or alternatively, the device 1600 may be configured to perform one or more processes, or combinations thereof, described herein, such as method 1100 in Figure 11. In some embodiments, the device 1600, and / or one or more components shown in Figure 16, may include one or more components of the first network entity described above in relation to Figure 2. Additionally, or alternatively, one or more components shown in Figure 16 may be implemented within one or more components described above in relation to Figure 2. Additionally, or alternatively, one or more components of that set of components may be implemented at least partially as software stored in memory. For example, a component (or part of a component) may be implemented as instructions or code stored in a non-temporary computer-readable medium, executable by a controller or processor to perform the function or operation of that component.

[0161]

[0172] The receiving component 1602 is capable of receiving communications from the device 1606, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1602 is capable of providing the received communications to one or more other components of the device 1600. In some embodiments, the receiving component 1602 is capable of performing signal processing on the received communications (among many examples, filtering, amplification, demodulation, analog / digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference rejection, or decoding) and providing the processed signals to one or more other components of the device 1606. In some embodiments, the receiving component 1602 may include one or more antennas, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof of the first network entity described above in relation to Figure 2.

[0162]

[0173] The transmitting component 1604 is capable of transmitting communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1606. In some embodiments, one or more other components of the device 1606 are capable of generating communications and providing the generated communications to the transmitting component 1604 for transmission to the device 1606. In some embodiments, the transmitting component 1604 is capable of performing signal processing on the generated communications (among many examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) and transmitting the processed signals to the device 1606. In some embodiments, the transmitting component 1604 may include one or more antennas, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or combinations thereof of the first network entity described above in relation to Figure 2. In some embodiments, the transmitting component 1604 may be located in the same place as the receiving component 1602 in the transceiver.

[0163]

[0174] The receiving component 1602 or the communication component 1608 can receive configuration information relating to a UE accessing a standalone non-public network associated with a first network entity, from a network entity associated with a first service provider, where the standalone non-public network is associated with a second service provider. For example, the communication component 1608 can handle communication with a network entity associated with the first service provider. The receiving component 1602 can receive a request from a second network entity associated with a standalone non-public network for at least a portion of the configuration information. The transmitting component 1604 can send the configuration information to the second network entity based at least in part on the request.

[0164]

[0175] The number and arrangement of components shown in Figure 16 are provided as an example. In practice, there may be additional components, fewer components, different components, or components arranged differently compared to those shown in Figure 16. Furthermore, two or more components shown in Figure 16 may be implemented within a single component, or a single component shown in Figure 16 may be implemented as multiple distributed components. Additionally, or alternatively, a set of (one or more) components shown in Figure 16 may perform one or more functions described as being performed by another set of components shown in Figure 16.

[0165]

[0176] Figure 17 shows an example of a hardware embodiment 1700 for a device 1705 employing the processing system 1710. The device 1705 can be a first network entity.

[0166]

[0177] The processing system 1710 may be implemented with a bus architecture, which is collectively represented by bus 1715. Bus 1715 can include any number of interconnected buses and bridges, depending on the specific application of the processing system 1710 and the overall design constraints. Bus 1715 links together various circuits, including the processor 1720, the indicated components, and one or more processors and / or hardware components represented by the computer-readable medium / memory 1725. Bus 1715 can also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0167]

[0178] The processing system 1710 may be coupled to a transceiver 1730. The transceiver 1730 is coupled to one or more antennas 1735. The transceiver 1730 provides means for communicating with various other devices via a transmitting medium. The transceiver 1730 receives signals from one or more antennas 1735, extracts information from the received signals, and provides the extracted information to the processing system 1710, specifically to the receiving component 1602. In addition, the transceiver 1730 receives information from the processing system 1710, specifically to the transmitting component 1604, and generates signals that will be applied to one or more antennas 1735 based at least in part on the received information.

[0168]

[0179] The processing system 1710 includes a processor 1720 coupled to a computer-readable medium / memory 1725. The processor 1720 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1725. When executed by the processor 1720, the software causes the processing system 1710 to perform various functions described herein with respect to any particular device. The computer-readable medium / memory 1725 may also be used to store data manipulated by the processor 1720 when the software is executed. The processing system further includes at least one of the components shown. These components may be software modules residing in / stored in the computer-readable medium / memory 1725 that run on the processor 1720, one or more hardware modules coupled to the processor 1720, or any combination thereof.

[0169]

[0180] In some embodiments, the processing system 1710 can be a component of the base station 110 and can include memory 242, and / or at least one of the TX MIMO processor 230, RX processor 238, and / or controller / processor 240. In some embodiments, the processing system 1710 can be one or more components of a 5G system as shown in Figures 3 and 4, and can include memory and one or more processors. In some embodiments, the device for wireless communications 1705 includes means for receiving configuration information relating to a UE visiting a standalone non-public network associated with a first network entity from a network entity associated with a first service provider, means for receiving a request for at least a portion of the configuration information from a second network entity associated with a standalone non-public network, and means for transmitting the configuration information to the second network entity based at least in part on the request. The aforementioned means can be one or more of the aforementioned components of the device 1600 and / or the processing system 1710 of the device 1705 configured to perform the functions enumerated by the aforementioned means. As in some embodiments described elsewhere in this specification, the processing system 1710 may include a TX MIMO processor 230, a receiving processor 238, and / or a controller / processor 240. In one configuration, the aforementioned means may be a TX MIMO processor 230, a receiving processor 238, and / or a controller / processor 240 configured to perform the functions and / or operations enumerated herein.

[0170]

[0181] Figure 17 is provided as an example. Other examples may differ from those described with respect to Figure 17.

[0171]

[0182] The following sections provide an overview of several aspects of this disclosure.

[0172]

[0183] Embodiment 1: A method for wireless communication performed by a first network entity, comprising: identifying a protocol data unit (PDU) session with a user device (UE); obtaining configuration information associated with a first service provider, at least in part, based on the identification of the PDU session; and thereby transmitting the configuration information to a UE associated with a standalone non-public network provided by a second service provider, or to a second network entity associated with a standalone non-public network.

[0173]

[0184] Embodiment 2: The method according to Embodiment 1, wherein obtaining configuration information further comprises requesting a subscription indicating that configuration information is to be requested from a third network entity associated with a standalone non-public network, wherein the third network entity requests configuration information at least in part based on the subscription, which is an integrated data management function.

[0174]

[0185] Embodiment 3: The method of Embodiment 2, wherein requesting a subscription indicating that configuration information is requested is at least partially based on successful authentication of the UE.

[0175]

[0186] Embodiment 4: The method according to Embodiment 1, wherein obtaining configuration information further comprises obtaining configuration information from a network entity associated with a first service provider.

[0176]

[0187] Embodiment 5: The method according to Embodiment 4, wherein the network entity associated with the first service provider is an authentication, authorization, and accounting server, wherein configuration information is obtained through one or more third network entities associated with a standalone non-public network.

[0177]

[0188] Embodiment 6: The method according to Embodiment 4, wherein the network entity associated with the first service provider is an integrated data management function for the network associated with the first service provider.

[0178]

[0189] Embodiment 7: The method according to any one of Embodiments 1 to 6, wherein transmitting configuration information to the UE further comprises transmitting configuration information to the UE in the protocol configuration options component of the message.

[0179]

[0190] Embodiment 8: The method according to any one of Embodiments 1 to 7, wherein the configuration information transmitted to the UE includes a proxy call session control function address relating to a proxy call session control function associated with a first service provider.

[0180]

[0191] Embodiment 9: The method according to any one of Embodiments 1 to 8, wherein the configuration information transmitted to a second network entity includes a tunnel configuration relating to a tunnel between the second network entity and a network associated with a first service provider, wherein the second network entity is a user plane function associated with a UE.

[0181]

[0192] Embodiment 10: The method according to Embodiment 9, wherein the tunnel configuration indicates whether the tunnel is a shared tunnel or a private tunnel.

[0182]

[0193] Embodiment 11: The method according to any one of Embodiments 1 to 10, wherein configuration information is obtained from access and mobility management functions.

[0183]

[0194] Embodiment 12: A method for wireless communication performed by a first network entity, comprising: receiving a request from a second network entity for configuration information associated with a first service provider, wherein the first and second network entities are associated with a standalone non-public network provided by the second service provider, wherein the configuration information is associated with user equipment (UE) associated with the first service provider accessing the standalone non-public network, at least in part on the request for configuration information, and transmitting the configuration information to the second network entity.

[0184]

[0195] Embodiment 13: The method according to Embodiment 12, wherein the request is received at least in part on a protocol data unit (PDU) session established between the UE and a second network entity.

[0185]

[0196] Embodiment 14: The method of any one of embodiments 12 to 12, further comprising determining that configuration information will be obtained from a proxy entity on at least partly based on a request for such configuration information, or on at least partly based on the configuration of a first network entity.

[0186]

[0197] Embodiment 15: The method of Embodiment 14, wherein obtaining configuration information further comprises requesting configuration information from a proxy entity, wherein the configuration information is available to the proxy entity at least in part on authentication of the UE with respect to a standalone non-public network, wherein the configuration information is related to network slice selection assistance information or to a data network name associated with network slice selection assistance information.

[0187]

[0198] Embodiment 16: The method according to any one of embodiments 12 to 15, wherein configuration information is transmitted to a second network entity as part of subscription information associated with the second network entity.

[0188]

[0199] Embodiment 17: The method according to any one of Embodiments 12 to 16, wherein the first network entity is an integrated data management function and the second network entity is a session management function.

[0189]

[0200] Embodiment 18: The method according to any one of embodiments 12 to 17, wherein the configuration information includes a proxy call session control function address relating to a proxy call session control function associated with a first service provider.

[0190]

[0201] Embodiment 19: The method according to any one of embodiments 12 to 18, wherein the configuration information includes a tunnel configuration relating to a tunnel between a second network entity and a network associated with a first service provider.

[0191]

[0202] Embodiment 20: A method for wireless communication performed by a first network entity, comprising: receiving configuration information relating to user equipment (UE) accessing a standalone non-public network associated with the first network entity from a network entity associated with a first service provider; the standalone non-public network receiving a request from a second network entity associated with the standalone non-public network for at least a portion of the configuration information relating to a second service provider; and transmitting the configuration information to the second network entity based at least in part on the request.

[0192]

[0203] Embodiment 21: The method according to Embodiment 20, wherein receiving configuration information is at least in part based on the UE being authenticated on a standalone non-public network.

[0193]

[0204] Embodiment 22: The method according to any one of Embodiments 20 to 21, wherein the configuration information includes at least one of the following: a proxy call session control function (P-CSCF) address relating to a P-CSCF associated with a first service provider, network slice selection support information associated with the first service provider, or a data network name associated with the first service provider.

[0194]

[0205] Embodiment 23: The method according to Embodiments 20 to 22, wherein the configuration information includes a tunnel configuration relating to a tunnel between a second network entity and a network associated with a first service provider, wherein the tunnel configuration includes at least one of the following: a data network name associated with the first service provider, network slice selection support information associated with the first service provider, a tunneling type associated with the tunnel, a tunnel server address associated with the tunnel, credentials associated with the tunnel, or an indication that the tunnel is a shared tunnel or a dedicated tunnel.

[0195]

[0206] Embodiment 24: The method according to any one of embodiments 20 to 23, wherein the first network entity is an authentication server function and the second network entity is an access and mobility management function or an integrated data management function.

[0196]

[0207] Embodiment 25: A method for wireless communication performed by a first network entity, comprising: identifying a protocol data unit (PDU) session with a user device (UE); obtaining configuration information associated with a first data network provider, at least in part on having identified the PDU session; and transmitting the configuration information to the UE or to the second network entity associated with the first network, wherein the first network entity is associated with a first network provided by a second data network provider, and the configuration information includes a tunnel configuration relating to a tunnel between a second network entity associated with the first network and a second network associated with the first data network provider.

[0197]

[0208] Embodiment 26: The method according to Embodiment 25, wherein the first network is a standalone, non-public network.

[0198]

[0209] Embodiment 27: The method according to any one of embodiments 25 to 26, wherein obtaining configuration information further comprises requesting a subscription from a third network entity associated with a first network indicating that it requests configuration information, and requesting configuration information at least in part on the basis of the subscription.

[0199]

[0210] Embodiment 28: The method of any one of Embodiments 25 to 27, wherein requesting a subscription indicating that configuration information is to be requested is at least in part based on successful authentication of the UE.

[0200]

[0211] Embodiment 29: The method according to any one of embodiments 25 to 28, wherein obtaining configuration information further comprises obtaining configuration information from a network entity associated with a first data network provider.

[0201]

[0212] Embodiment 30: The method according to Embodiment 29, wherein the network entity associated with the first data network provider is an authentication, authorization, and accounting server.

[0202]

[0213] Embodiment 31: The method according to Embodiment 29, wherein the network entity associated with the first data network provider is an integrated data management function for the network associated with the first data network provider.

[0203]

[0214] Embodiment 32: The method according to any one of embodiments 25 to 31, further comprising transmitting configuration information to the UE in a protocol configuration option component of the message.

[0204]

[0215] Embodiment 33: The method according to any one of Embodiments 25 to 32, wherein the tunnel configuration indicates whether the tunnel is a shared tunnel or a dedicated tunnel.

[0205]

[0216] Embodiment 34: The method according to any one of Embodiments 25 to 33, wherein configuration information is obtained from access and mobility management functions.

[0206]

[0217] Embodiment 35: The method according to any one of embodiments 25 to 34, wherein the tunnel is associated with enabling a UE to access a service provided by the Internet Protocol media subsystem of a first data network provider.

[0207]

[0218] Embodiment 36: The method according to any one of Embodiments 25 to 35, wherein the tunnel configuration indicates at least a tunnel server address or one or more credentials relating to the tunnel.

[0208]

[0219] Embodiment 37: The method according to any one of embodiments 25 to 36, wherein the tunnel is associated with a Layer 2 tunneling protocol or an Internet Protocol security protocol.

[0209]

[0220] Embodiment 38: A device for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory that can be executed by the processor to cause the device to perform one or more of the methods of Embodiments 1 to 37.

[0210]

[0221] Embodiment 39: A network entity for wireless communication, comprising memory and one or more processors coupled to the memory, wherein the one or more processors are configured to perform a method of one or more embodiments of embodiments 1 to 37.

[0211]

[0222] Embodiment 40: An apparatus for wireless communication comprising at least one means for performing a method of one or more embodiments from Embodiments 1 to 37.

[0212]

[0223] Embodiment 41: A non-temporary computer-readable medium storing code for wireless communication, wherein the code comprises instructions executable by a processor to perform a method of one or more embodiments of Embodiments 1 to 37.

[0213]

[0224] Embodiment 42: A non-temporary computer-readable medium storing a set of instructions for wireless communication, wherein the set of instructions comprises one or more instructions, and when one or more instructions are executed by one or more processors of the device, the device causes the device to execute a method of one or more embodiments of embodiments 1 to 37.

[0214]

[0225] While the foregoing disclosures provide examples and explanations, they are not intended to be exhaustive or to limit the embodiments to the exact forms disclosed. Modified and transformed forms may be created in light of the foregoing disclosures or derived from the practice of the embodiments.

[0215]

[0226] As used herein, the term “component” is intended to be interpreted broadly as hardware, firmware, and / or combinations of hardware and software. As used herein, a processor is implemented as hardware, firmware, and / or combinations of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented in various forms of hardware, firmware, and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not a limitation of the embodiment. Therefore, although the operation and behavior of the systems and / or methods are described herein without reference to specific software code, it will be understood that software and hardware can be designed to implement the systems and / or methods based at least in part on the descriptions herein.

[0216]

[0227] In the context of this specification, "meeting a threshold" can mean, depending on the context, that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, or not equal to a threshold.

[0217]

[0228] Even if specific combinations of features are enumerated in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure of various embodiments. In practice, many of these features can be combined in ways not specifically enumerated in the claims and / or disclosed herein. Each dependent claim listed herein may depend directly on only one claim, but the disclosure of various embodiments includes each dependent claim in combination with any other claims in the claim set. Where used herein, the phrase “at least one of” a list of items refers to any combination of those items, including a single member. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0218]

[0229] The elements, actions, or commands used herein should not be construed as important or essential unless explicitly stated otherwise. Furthermore, the articles “a” and “an” as used herein are intended to include one or more items and may be interchangeable with “one or more.” Additionally, the article “the” as used herein is intended to include one or more items referred to in conjunction with the article “the” and may be interchangeable with “the one or more.” Furthermore, the terms “set” and “group” as used herein are intended to include one or more items (for example, related items, unrelated items, or a combination of related and unrelated items) and may be interchangeable with “one or more.” When only one item is intended, the phrase “only one” or a similar expression is used. Furthermore, as used herein, terms such as "has," "have," and "having" are intended to be unrestricted terms. In addition, the phrase "based on" is intended to mean "based, at least in part, on," unless explicitly stated otherwise. Also, as used herein, the term "or" is intended to be inclusive when used in a series and may be interchangeable with "and / or," unless explicitly stated otherwise (for example, when used in combination with "either" or "only one of"). The invention described in the original claims of this application is listed below. [C1] A first network entity for wireless communication, Memory and The system comprises one or more processors coupled to the memory, and the one or more processors Identifying a protocol data unit (PDU) session with the user device (UE), Based at least in part on the identification of the PDU session, the configuration information associated with a first data network provider is obtained, wherein the first network entity is associated with a first network provided by a second data network provider, and wherein the configuration information includes a tunnel configuration relating to a tunnel between a second network entity associated with the first network and a second network associated with the first data network provider. A first network entity configured to transmit the configuration information to the UE or to the second network entity associated with the first network. [C2] The first network entity described in C1 is a standalone, non-public network. [C3] The one or more processors, in order to obtain the configuration information, Requesting a subscription indicating that the configuration information is to be requested from the third network entity associated with the first network, A first network entity as described in C1, configured to request the configuration information based at least in part on the said subscription. [C4] A first network entity as described in C3 requests the subscription indicating that it requests the aforementioned configuration information, at least in part, based on the successful authentication of the UE. [C5] The one or more processors, in order to obtain the configuration information, A first network entity as described in C1, configured to obtain the configuration information from a network entity associated with the first data network provider. [C6] The first network entity described in C5 is an authentication, authorization, and accounting server, which is associated with the first data network provider. [C7] The first network entity described in C5, wherein the network entity associated with the first data network provider is an integrated data management function for the network associated with the first data network provider. [C8] The one or more processors transmit the configuration information to the UE, A first network entity as described in C1, configured in the message protocol configuration option component to transmit the configuration information to the UE. [C9] The tunnel configuration is a first network entity as described in C1, indicating whether the tunnel is a shared tunnel or a dedicated tunnel. [C10] The configuration information is obtained from the access and mobility management function, and is the first network entity described in C1. [C11] The first network entity described in C1, wherein the tunnel is associated with enabling the UE to access services provided by the Internet Protocol Media Subsystem of the first data network provider. [C12] The tunnel configuration is a first network entity as described in C1, which represents at least a tunnel server address or one or more credentials relating to the tunnel. [C13] The first network entity described in C1, wherein the tunnel is associated with the Layer 2 Tunneling Protocol or the Internet Protocol Security Protocol. [C14] A method of wireless communication performed by a first network entity, Identifying a protocol data unit (PDU) session with the user device (UE), Based at least in part on the identification of the PDU session, the configuration information associated with a first data network provider is obtained, wherein the first network entity is associated with a first network provided by a second data network provider, and wherein the configuration information includes a tunnel configuration relating to a tunnel between a second network entity associated with the first network and a second network associated with the first data network provider. A method comprising transmitting the configuration information to the UE or to the second network entity associated with the first network. [C15] The method according to C14, wherein the first network is a standalone, non-public network. [C16] Furthermore, obtaining the aforementioned configuration information is possible. Requesting a subscription indicating that the configuration information is to be requested from the third network entity associated with the first network, The method of C14, comprising requesting the configuration information based at least in part on the said subscription. [C17] The method of C16, wherein requesting the subscription indicating that it requests the configuration information is at least partially based on the successful authentication of the UE. [C18] Furthermore, obtaining the aforementioned configuration information is possible. The method of C14, comprising obtaining the configuration information from a network entity associated with the first data network provider. [C19] The method according to C18, wherein the network entity associated with the first data network provider is an authentication, authorization, and accounting server. [C20] The method according to C18, wherein the network entity associated with the first data network provider is an integrated data management function for the network associated with the first data network provider. [C21] Furthermore, transmitting the configuration information to the aforementioned UE is further, The method of C14, comprising sending the configuration information to the UE in the message protocol configuration option component. [C22] The method according to C14, which indicates whether the tunnel configuration is a shared tunnel or a dedicated tunnel. [C23] The method of C14, wherein the configuration information is obtained from the access and mobility management function. [C24] The method of C14, wherein the tunnel is associated with enabling the UE to access services provided by the Internet Protocol Media Subsystem of the first data network provider. [C25] The method according to C14, wherein the tunnel configuration indicates at least a tunnel server address or one or more credentials relating to the tunnel. [C26] The method according to C14, wherein the tunnel is associated with the Layer 2 Tunneling Protocol or the Internet Protocol Security Protocol. [C27] A non-temporary computer-readable medium storing a set of instructions for wireless communication, wherein the set of instructions is The system comprises one or more instructions, and when the one or more instructions are executed by one or more processors of a first network entity, Identifying a protocol data unit (PDU) session with the user device (UE), Based at least in part on the identification of the PDU session, the configuration information associated with a first data network provider is obtained, wherein the first network entity is associated with a first network provided by a second data network provider, and wherein the configuration information includes a tunnel configuration relating to a tunnel between a second network entity associated with the first network and a second network associated with the first data network provider. A non-temporary computer-readable medium that causes the first network entity to transmit the configuration information to the UE or to the second network entity associated with the first network. [C28] The first network is a standalone, non-public network, as described in C27, for non-temporary computer-readable media. [C29] A device for wireless communication, Means for identifying a protocol data unit (PDU) session with a user device (UE), Means for obtaining configuration information associated with a first data network provider, at least in part on having identified the PDU session, wherein the device is associated with a first network provided by a second data network provider, wherein the configuration information includes a tunnel configuration relating to a tunnel between a second network entity associated with the first network and the second network associated with the first data network provider. An apparatus comprising means for transmitting the configuration information to the UE or to the second network entity associated with the first network. [C30] The apparatus described in C29, wherein the first network is a standalone, non-public network.

Claims

1. A method of wireless communication performed by a session management function, Identifying a protocol data unit (PDU) session with the user device (UE), Based at least in part on the identification of the PDU session, configuration information associated with a home service provider is obtained, wherein the configuration information is obtained from an access and mobility management function, wherein the session management function is associated with a first network provided by a standalone non-public network provider, wherein the configuration information includes a tunnel configuration relating to a tunnel between a user plane function associated with the first network and a second network associated with the home service provider, wherein the tunnel is associated with enabling the UE to access services provided by the home service provider's Internet Protocol Media subsystem. A method comprising transmitting the configuration information to the UE or to the user plane function associated with the first network.

2. The method according to claim 1, wherein the first network is a standalone, non-public network.

3. Furthermore, obtaining the aforementioned configuration information is possible. Requesting a subscription to the integrated data management function associated with the first network, which indicates that it requests the configuration information, The method according to claim 1, further comprising requesting the configuration information based at least partially on the subscription.

4. The method according to claim 3, wherein requesting the subscription indicating that it requests the configuration information is at least partially based on the successful authentication of the UE.

5. Furthermore, obtaining the aforementioned configuration information is possible. The method according to claim 1, further comprising obtaining the configuration information from a network entity associated with the home service provider.

6. The method according to claim 5, wherein the network entity associated with the home service provider is an authentication, authorization, and accounting server.

7. The method according to claim 5, wherein the network entity associated with the home service provider is an integrated data management function for the network associated with the home service provider.

8. Furthermore, transmitting the configuration information to the aforementioned UE is further, The method according to claim 1, further comprising transmitting the configuration information to the UE in the message protocol configuration option component.

9. The method according to claim 1, wherein the tunnel configuration indicates whether the tunnel is a shared tunnel or a dedicated tunnel.

10. The method according to claim 1, wherein the tunnel configuration indicates at least a tunnel server address or one or more credentials relating to the tunnel.

11. The method according to claim 1, wherein the tunnel is associated with a Layer 2 tunneling protocol or an Internet Protocol Security Protocol.

12. A non-temporary computer-readable medium storing a set of instructions for wireless communication, wherein the set of instructions is It comprises one or more instructions, and when the one or more instructions are executed by one or more processors of the session management function, Identifying a protocol data unit (PDU) session with the user device (UE), Based at least in part on the identification of the PDU session, configuration information associated with a home service provider is obtained, wherein the configuration information is obtained from an access and mobility management function, wherein the session management function is associated with a first network provided by a standalone non-public network provider, wherein the configuration information includes a tunnel configuration relating to a tunnel between a user plane function associated with the first network and a second network associated with the home service provider, wherein the tunnel is associated with enabling the UE to access services provided by the home service provider's Internet Protocol Media subsystem. A non-temporary computer-readable medium that causes the session management function to transmit the configuration information to the UE or to the user plane function associated with the first network.

13. The non-temporary computer-readable medium according to claim 12, wherein the first network is a standalone non-public network.

14. A device for wireless communication, Means for identifying a protocol data unit (PDU) session with a user device (UE), Means for obtaining configuration information associated with a home service provider, at least in part on the identification of the PDU session, wherein the device is associated with a first network provided by a standalone non-public network provider, wherein the configuration information is obtained from an access and mobility management function, wherein the configuration information includes a tunnel configuration relating to a tunnel between a user plane function associated with the first network and a second network associated with the home service provider, wherein the tunnel is associated with enabling the UE to access services provided by the home service provider's Internet Protocol Media subsystem. An apparatus comprising means for transmitting the configuration information to the UE or to the user plane function associated with the first network.

Images