Providing configuration information for accessing a standalone non-public network

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, entitled "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 that prior application is considered part of, and is incorporated by reference into, this patent application.

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

[0003]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access technologies capable of supporting 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 promulgated by the 3rd Generation Partnership Project (3GPP).

[0004]

[0004] A wireless network may include several base stations (BSs) that may support communication for several user equipments (UEs). The UEs may communicate with the BSs via a downlink and an uplink. The "downlink" (or forward link) refers to the communication link from the BS to the UE, and the "uplink" (or reverse link) refers to the communication link from the UE to the BS. As described in more detail herein, the BSs may be referred to as Node Bs, gNBs, access points (APs), radio heads, transmit receive points (TRPs), 5G BSs, 5G Node Bs, etc.

[0005]

[0005] The above multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that allows various wireless communication devices to communicate on a local, national, regional, and even global scale. 5G, sometimes called New Radio (NR), is a set of extensions to the LTE mobile standard promulgated by 3GPP. 5G is designed to improve spectrum efficiency, lower costs, improve services, take advantage of new spectrum, and better integrate with other open standards using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink (DL) and CP-OFDM and / or SC-FDM (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM) on the uplink (UL), as well as better support mobile broadband Internet access 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, which should preferably be applicable to other multiple access technologies and the telecommunications standards employing these technologies. Summary of the Invention

[0006] A standalone non-public network (SNPN) may utilize radio access technologies such as 5G to provide radio access connectivity for user equipment (UE). SNPNs may be useful in a variety of applications, such as industrial automation (e.g., Industrial Internet of Things), public places, public transportation, etc.

[0007] A UE may be associated with a home service provider (SP), which may include an SNPN operator, a Public Land Mobile Network (PLMN) operator, a credential provider (such as an entity that operates an authentication, authorization, and accounting (AAA) server without radio access functionality), etc.

[0008]

[0008] In some cases, a UE may be able to access an SNPN using credentials provided by the UE's home SP, even though the SNPN is not associated with (e.g., not provided by) the home SP. The UE's access to an SNPN not provided by the UE's home SP is referred to herein as visiting an SNPN. The communication protocol may provide for authentication of the UE by an AAA server of the home SP (e.g., via the SNPN) or by one or more network entities of the home SP, such as an authentication server function (AUSF), a unified data management (UDM) function, etc. However, some forms of configuration information may be handled by a session management function (SMF) of a given 5G system (5GS), such as the 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 the home SP. Examples of such configuration information include the proxy call session control function (P-CSCF) address for the home SP's P-CSCF and tunneling information used to connect to the home SP's IP Multimedia Subsystem (IMS). If such form of configuration information cannot be signaled to a UE visiting an SNPN, the UE may not be able to access IMS services provided by the home SP.

[0009]

[0009] Some techniques and apparatuses 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 an SNPN 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 aspects, the configuration information can include a P-CSCF address, tunneling information, etc. In some aspects, the configuration information can be provided by an AAA server of the home SP to an AAA proxy or another function in the SNPN, which can 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 aspects, the configuration information can be provided from a UDM of the home SP to the SMF, which can signal the configuration information to the UE or to a UPF associated with the UE. In this manner, the IMS function is supported for a UE visiting the SNPN even though the home SP providing the IMS function does not have an SMF for signaling configuration information supporting the IMS function, thus improving the interconnection between the SNPN and the home SP network.

[0010]

[0010] In some aspects, a method of wireless communication performed by a first network entity includes identifying a protocol data unit (PDU) session with a UE and obtaining configuration information associated with a first service provider based at least in part on identifying the PDU session, wherein the first network entity sends 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 the standalone, non-public network.

[0011]

[0011] In some aspects, a method of wireless communications performed by a first network entity includes receiving a request from a second network entity for configuration information associated with a first service provider, where the first network entity and the second network entity are associated with a stand-alone, non-public network provided by the second service provider, where the configuration information is related to a UE associated with the first service provider that accesses the stand-alone, non-public network, obtaining configuration information from a proxy entity associated with the stand-alone, non-public network based at least in part on the request for configuration information, and transmitting the configuration information to the second network entity.

[0012]

[0012] In some aspects, a method of wireless communications performed by a first network entity includes receiving configuration information related to a UE accessing a stand-alone, non-public network associated with the first network entity from a network entity associated with a first service provider, wherein the stand-alone, non-public network receives a request for at least a portion of the configuration information from a second network entity associated with the stand-alone, non-public network, associated with 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 aspects, a first network entity for wireless communication includes a memory and one or more processors coupled to the memory, where the one or more processors are configured to identify a PDU session with a UE and, based at least in part on identifying the PDU session, obtain configuration information associated with a first service provider, where the first network entity transmits 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 the standalone, non-public network.

[0014]

[0014] In some aspects, a first network entity for wireless communication includes a memory and one or more processors coupled to the memory, where the one or more processors are configured to receive a request from a second network entity for configuration information associated with a first service provider, where the first network entity and the second network entity are associated with a stand-alone, non-public network provided by the second service provider, where the configuration information is related to a UE associated with the first service provider that accesses the stand-alone, non-public network, based at least in part on the request for configuration information, obtain configuration information from a proxy entity associated with the stand-alone, non-public network, and transmit the configuration information to the second network entity.

[0015]

[0015] In some aspects, a first network entity for wireless communications includes a memory and one or more processors coupled to the memory, where the one or more processors are configured to receive configuration information related 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, where the standalone non-public network is associated with a second service provider, a request for at least a portion of the configuration information from a second network entity associated with the standalone non-public network, and transmit the configuration information to the second network entity based at least in part on the request.

[0016]

[0016] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communications includes one or more instructions that, when executed by one or more processors of a first network entity, cause the first network entity to identify a PDU session with the UE, and based at least in part on identifying the PDU session, obtain configuration information associated with a first service provider, wherein the first network entity transmits 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 the standalone, non-public network.

[0017]

[0017] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communications includes one or more instructions that, when executed by one or more processors of a first network entity, cause the first network entity to receive a request from a second network entity for configuration information associated with a first service provider, where the first network entity and the second network entity are associated with a stand-alone, non-public network provided by the second service provider, where the configuration information is related to a UE associated with the first service provider that accesses the stand-alone, non-public network, based at least in part on the request for the configuration information, obtain configuration information from a proxy entity associated with the stand-alone, non-public network, and transmit the configuration information to the second network entity.

[0018]

[0018] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communications includes one or more instructions that, when executed by one or more processors of a first network entity, cause the first network entity to receive configuration information related 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, receive a request for at least a portion of the configuration information from a second network entity associated with the standalone, non-public network, and transmit the configuration information to the second network entity based at least in part on the request.

[0019]

[0019] In some aspects, an apparatus for wireless communications includes means for identifying a PDU session with a UE; means for obtaining configuration information associated with a first service provider based at least in part on identifying the 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 the standalone, non-public network.

[0020]

[0020] In some aspects, an apparatus for wireless communications includes means for receiving a request from a second network entity for configuration information associated with a first service provider, where the first network entity and the second network entity are associated with a standalone, non-public network provided by the second service provider, where the configuration information is related to a UE associated with the first service provider that accesses the standalone, non-public network, and means for obtaining the configuration information from a proxy entity associated with the standalone, non-public network based at least in part on the request for the configuration information, and means for transmitting the configuration information to the second network entity.

[0021]

[0021] In some aspects, an apparatus for wireless communications includes means for receiving configuration information related to a UE accessing a standalone non-public network associated with a first network entity, wherein the standalone non-public network is associated with a second service provider, means for receiving a request for at least a portion of the configuration information from a second network entity associated with the standalone non-public network, 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] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems substantially as described with reference to and as shown in the drawings and specification.

[0023]

[0023] The foregoing has outlined rather broadly the features and technical advantages of the examples according to the present disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The concepts and specific examples disclosed may be readily utilized as a basis for making modifications or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent structures are within the scope of the appended claims. The features of the concepts disclosed herein, both their organization and the method of operation, together with associated advantages, will be better understood from the following description when considered in conjunction with the accompanying figures. Each of the figures is provided for the purpose of illustration and explanation, and not as a definition of the limits of the claims. [Brief description of the drawings]

[0024] [Figure 1] FIG. 1 illustrates an example of a wireless network. [Diagram 2]

[0025] 1 illustrates an example of a base station in communication with a UE in a wireless network. [Diagram 3]

[0026] 1 illustrates an example environment of a standalone non-public network (SNPN) and a network associated with a UE's home service provider (SP). [Figure 4]

[0027] FIG. 2 illustrates an example environment diagram of an SNPN and a network associated with a home SP of a UE in accordance with the present disclosure. [Diagram 5]

[0028] FIG. 1 illustrates an example of provision of configuration information from a home SP for a UE accessing an SNPN. [Figure 6] FIG. 1 illustrates an example of provision of configuration information from a home SP for a UE accessing an SNPN. [Figure 7] FIG. 1 illustrates an example of provision of configuration information from a home SP for a UE accessing an SNPN. [Figure 8]FIG. 1 illustrates an example of provision of configuration information from a home SP for a UE accessing an SNPN. [Figure 9]

[0029] 4 is a flow chart of an exemplary method of wireless communication. [Figure 10] 4 is a flow chart of an exemplary method of wireless communication. [Figure 11] 4 is a flow chart of an exemplary method of wireless communication. [Figure 12]

[0030] 1 is a block diagram of an example apparatus for wireless communication. [Figure 13]

[0031] FIG. 2 illustrates an example of a hardware implementation for an apparatus employing the processing system. [Figure 14]

[0032] 1 is a block diagram of an example apparatus for wireless communication. [Figure 15]

[0033] FIG. 2 illustrates an example of a hardware implementation for an apparatus employing the processing system. [Figure 16]

[0034] 1 is a block diagram of an example apparatus for wireless communication. [Figure 17]

[0035] FIG. 2 illustrates an example of a hardware implementation for an apparatus employing the processing system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025]

[0036] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent configurations in which the concepts described herein may be practiced. The detailed description includes 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 may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0026]

[0037] Several aspects of a telecommunications system will now be presented with reference to various apparatus and methods that will be described in the detailed description that follows and 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 particular application and design constraints imposed on the overall system.

[0027]

[0038] As an example, the elements, or any portion of the elements, or any combination of the elements, may be implemented with a "processing system" including 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 various functionality described throughout this disclosure. The one or more processors in the processing system are capable of executing software. Software shall be construed broadly 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 otherwise.

[0028]

[0039] Thus, 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 or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), compact disc ROM (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium 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] It should be noted that although aspects may be described herein using terminology commonly associated with 5G or NR radio access technologies (RATs), aspects of the disclosure may apply to other RATs, such as 3G RATs, 4G RATs, and / or RATs subsequent to 5G (e.g., 6G).

[0030]

[0041] FIG. 1 illustrates a wireless network 100 in which aspects of the disclosure may be practiced. The wireless network 100 may be or may include elements of a 5G (NR) network and / or an LTE network, among other examples. The wireless network 100 may include several base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UE) and may also be referred to as a 5G BS, Node B, gNB, 5G NB, access point, transmit reception point (TRP), etc. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a BS and / or a BS subsystem serving this coverage area, depending on the context in which the term is used.

[0031]

[0042] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs that have an association with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. 1, BS 110a may be a macro BS for a macro cell 102a, BS 110b may be a pico BS for a pico cell 102b, and BS 110c may be a femto BS for a femto cell 102c. A BS may support one or more (e.g., 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 examples, the cells may not necessarily be stationary and the geographic area of ​​the cells may move according to the location of the mobile BS. In some examples, the BSs may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in 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 that can receive data transmissions from an upstream station (e.g., a BS or a UE) and send the data transmissions to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. In the example shown in FIG. 1, a relay BS 110d may communicate with a macro BS 110a and a UE 120d to facilitate communication between the BS 110a and the UE 120d. A relay BS may also be referred to as a relay station, a relay base station, a relay, etc.

[0034]

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

[0035]

[0046] A network controller 130 may couple to a set of BSs and provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other, e.g., directly or indirectly via a wireless or wired backhaul.

[0036]

[0047] The UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular telephone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless telephone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., music or video device, or satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0037]

[0048] Some UEs may be considered as machine type communication (MTC) or evolved or extended machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, a location tag, etc. that may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as customer premises equipment (CPE). The UE 120 may be included within a housing that houses components of the UE 120, such as a processor component, a memory component, etc.

[0038]

[0049] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular RAT and may operate at one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, etc. A frequency may also be referred to as a carrier, a frequency channel, etc. To avoid interference between wireless networks of different RATs, each frequency may support a single RAT in a given geographic area. In some cases, 5G RAT networks may be deployed.

[0039]

[0050] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using a base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), and / or mesh networks. In this case, the UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.

[0040]

[0051] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various classes, bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using an operating band having a first frequency range (FR1) that may range from 410 MHz to 7.125 GHz and / or 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 may be referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, 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-300 GHz) identified as the "millimeter wave" band by the International Telecommunications Union (ITU). Thus, unless otherwise specifically stated, it should be understood that terms such as "sub-6 GHz," as used herein, can broadly refer to frequencies below 6 GHz, frequencies in FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise specifically stated, it should be understood that terms such as "millimeter wave," as used herein, can broadly refer to frequencies in the EHF band, frequencies in FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). The frequencies included in FR1 and FR2 may be modified, and the techniques described herein are believed to be applicable to those modified frequency ranges.

[0041]

[0052] In some aspects, radio access may be provided using an open radio access network (O-RAN) architecture. The O-RAN architecture may include a control unit (CU) that communicates with a core network via a backhaul link. In addition, the CU may communicate with one or more distributed units (DUs) via respective midhaul links. The DUs may each communicate with one or more radio units (RUs) via respective fronthaul links, and the RUs may each communicate with respective UEs via radio frequency (RF) access links. The DUs and RUs may also be referred to as O-RAN DUs (O-DUs) and O-RAN RUs (O-RUs), respectively.

[0042]

[0053] In some aspects, the DU and RU may be implemented according to a functional split 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 over a fronthaul link. Thus, as described herein, the base station 110 may include a DU and one or more RUs that may be co-located or geographically distributed. In some aspects, the DU and associated RUs may communicate over the fronthaul link to exchange real-time control plane information over a Lower Layer Split (LLS) Control Plane (LLS-C) interface, to exchange non-real-time management information over an LLS Management Plane (LLS-M) interface, and / or to exchange user plane information over an LLS User Plane (LLS-U) interface.

[0043]

[0054] Thus, a DU may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs. For example, in some aspects, a DU may host a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (e.g., forward error correction (FEC) encoding and decoding, scrambling, and / or modulation and demodulation) based at least in part on a lower layer functional division. Upper layer control functions such as a packet data convergence protocol (PDCP), a radio resource control (RRC), and / or a service data adaptation protocol (SDAP) may be hosted by a CU. A RU controlled by a DU may correspond to a logical node hosting RF processing functions and lower PHY layer functions (e.g., fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, and / or physical random access channel (PRACH) extraction and filtering) based at least in part on a lower layer functional division. Thus, in an O-RAN architecture, the RU handles all over-the-air (OTA) communications with the UE 120, and real-time and non-real-time aspects of the control and user plane communications 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 division may be implemented.

[0044]

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

[0045]

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

[0046]

[0057] 2 illustrates an example base station 200 in communication with a UE 120 in wireless network 100. Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0047]

[0058] At the base station 110, the transmit processor 220 may receive data from a data source 212 for one or more UEs, select a modulation and coding scheme (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the selected MCS for the UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or higher layer signaling) and provide overhead and control symbols. The transmit processor 220 may also generate reference signals (e.g., a cell-specific reference signal (CRS), a phase tracking reference signal (PTRS), and / or a demodulation reference signal (DMRS)), as well as synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.

[0048]

[0059] At the UE 120, antennas 252a-252r may receive downlink signals from the base station 110 and / or other base stations and may provide received signals to demodulators (DEMODs) 254a-254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a-254r, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. A receive (RX) processor 258 may process (e.g., demodulate and decode) the detected symbols and provide decoded data for the UE 120 to a data sink 260 and provide 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. A channel processor may determine a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, and / or a CQI parameter, among other examples. In some aspects, one or more components of the UE 120 may be included in the housing 284.

[0049]

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

[0050]

[0061] An antenna (e.g., antennas 234a-t and / or antennas 252a-r) may include or be included in one or more antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays, among 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 a set of coplanar antenna elements and / or a set 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 of FIG. 2.

[0051]

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

[0052]

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

[0053]

[0064] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other components of FIG. 2 may perform one or more techniques associated with providing configuration information for accessing a standalone non-public network, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other components of FIG. 2 may perform or direct operations of, for example, method 900 of FIG. 9, method 1000 of FIG. 10, method 1100 of FIG. 11, and / or other processes described herein. The memories 242 and 282 may store data and program codes for the BS 110 and the UE 120, respectively. In some aspects, the memory 242 and / or the memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after being compiled, translated, and / or interpreted) by one or more processors of the base station 110 and / or the UE 120, may cause the one or more processors, the UE 120, and / or the base station 110 to perform or direct operations of, for example, method 900 of Figure 9, method 1000 of Figure 10, method 1100 of Figure 11, and / or other processes described herein. In some aspects executing instructions may include running the instructions, translating the instructions, compiling the instructions, and / or interpreting the instructions, among other examples.

[0054]

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

[0055]

[0066] FIG. 3 is a diagram of an example environment 300 of an SNPN and a network associated with a home SP of a UE 120. The SNPN is labeled as a visited SNPN (V-SNPN) because the UE 120 is visiting the SNPN in the example environment 300. The SNPN is a network that provides wireless access using a radio access technology such as 5G. The SNPN is a private network that is deployed separately from a public network such as a public land mobile network (PLMN). In some aspects, the SNPN may have no dependency on the public network. The SNPN may provide network services to a defined user organization or group of organizations. 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 the network entities are labeled (e.g., N1, N2, etc.). "Network entity" is used interchangeably herein as "network function." The functions and / or networks of the example environment 300 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0056]

[0067] The SNPN may broadcast system information that the UE 120 may use to access the SNPN. The information broadcast by the SNPN may include a PLMN identifier (which may be a private PLMN identifier from the Mobile Country Code (MCC) 999 range), a network identifier (NID), and optionally a human-readable network name. The UE 120 may be configured with one or more SNPN subscriptions. In the SNPN access mode, the UE 120 may only register with networks that are broadcasting both PLMN identifiers and NIDs and for which the UE 120 has credentials. In some deployments, the SNPN may not support interconnection or roaming. For example, the UE 120 may not be able to access a first SNPN using credentials associated with a second SNPN. As another example, the UE 120 may not be able to access an SNPN using credentials associated with a PLMN.

[0057]

[0068] Some techniques described herein enable UE 120 to access a non-public network (e.g., an SNPN) using third-party credentials, such as those provided by the UE's 120's home SP. For example, UE 120 may successfully select and register with an SNPN that supports access to the UE's 120's home SP subscription. Supported home SP types may include PLMNs, SNPNs, and other credential providers. UE 120 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 (depicted as (R)AN to indicate that this access node may or may not be a radio access node), a UPF 320, a UDM 325, an AUSF 330, an AAA proxy (AAA-P) 335, a policy charging function (PCF) 340 (depicted as a visited PCF (vPCF)), a network slice selection function (NSSF) 345, and a data network 350. As further 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. As further shown, the functions 360, 365, and 370 may be considered part of a home SP domain associated with the home SP. The home SP may be a credential provider. The above network functions 305, 310, 315, 320, 325, 330, 335, 340, 345, 355, 360, 365, and 370 may be implemented as devices, logical functions, or combinations thereof. For example, each of the functional elements illustrated in FIG. 3 may be implemented on one or more devices associated with a wireless telecommunications system. In some aspects, one or more of the functional elements may be implemented on a physical device, such as an access point, a base station, a server, and / or a gateway. In some aspects, one or more of the functional elements may be implemented on a computing device of a cloud computing environment.

[0059]

[0070] The AMF 305 includes one or more devices that serve as termination points for Non-Access Stratum (NAS) signaling and / or mobility management, among other examples.

[0060]

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

[0061]

[0072] The access node 315 may provide access to the SNPN for the UE 120, such as via an air interface. For example, the access node 315 may include a BS 110, a radio unit (RU), a distributed unit (DU), or a central unit (CU) as described in connection with FIGS. 1 and 2.

[0062]

[0073] The UPF 320 includes one or more devices that serve as anchor points for intra-RAT and / or inter-RAT mobility. The UPF 320 may apply rules to the packets, such as rules regarding packet routing, traffic reporting, and / or handling user plane quality of service (QoS), among other examples. In some aspects, the UPF 320 may handle the establishment and management of tunnels with networks provided by the home SP, as described in more detail elsewhere herein.

[0063]

[0074] The UDM 325 includes one or more devices that store user data and profiles. The UDM 325 can be used for fixed and / or mobile access.

[0064]

[0075] The AUSF 330 acts as an authentication server in a wireless telecommunications system and includes one or more devices that support the process of authenticating the UE 120. In some aspects, the AUSF 330 may communicate with an AAA server 355 (e.g., via an AAA proxy 335) to authenticate the UE 120, as described in more detail elsewhere herein.

[0065]

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

[0066]

[0077] The PCF 340 includes one or more devices that provide a policy framework incorporating network slicing, roaming, packet processing, and / or mobility management, among other examples.

[0067]

[0078] The NSSF 345 includes one or more devices that select a network slice instance for the UE 120. Network slicing allows operators to deploy multiple substantially independent end-to-end networks (called slices), potentially using 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 may include an IMS, a PLMN, a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a private network such as an enterprise intranet, an ad-hoc network, the Internet, an optical fiber-based network, a cloud computing network, a third party service network, an operator service network, an SNPN, and / or a combination of these or other types of networks. In some aspects, the UE 120 may access services provided in a 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 to the UPF 320 from an AAA server 355 via one or more network entities, as described elsewhere herein.

[0069]

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

[0070]

[0081] The P-CSCF 360 and the S-CSCF 365 may provide a central control function in the IMS for setting up, establishing, modifying, and tearing down multimedia sessions. The P-CSCF 360 may be an edge access function, which may be an entry point for the UE 120 to request services from the IMS network. The P-CSCF 360 may act as a proxy by accepting incoming requests and forwarding them to an entity that may serve the incoming requests. The S-CSCF 365 may handle registration and session control for the registered UE 120. The S-CSCF 365 may act as a registrar and may enable the network location information of the UE 120 to be available to the IMS-HSS 370. The S-CSCF 365 may decide whether to grant or deny service to the UE 120. In some aspects, the S-CSCF may provide allocation of application servers to sessions, fulfillment of session requests by finding and signaling towards destination endpoints, coordination with media resource functions, maintaining session state, etc. The IMS-HSS370 can manage home location registration, user subscription information, user profile information, inter-network terminal authentication, wireless path encryption, integrity protection, and so on.

[0071]

[0082] Communication between the AAA server 355 and the AUSF 330 or AAA proxy 335 can enable SNPN access for the 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 plausible since the functionality of the AAA server is typically already available or easily deployable in an enterprise. In some aspects, the UE 120 may use roaming with a local breakout architecture as defined in wireless telecommunications standards. Accessing the visited SNPN may enable access to the services of the visited SNPN. The UE 120 may be authenticated using the credential provider's AAA server 355. In some cases, subscription information is not provided by the credential provider. Thus, a template subscription may be configured in the visited SNPN and used for visiting UEs that are 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 bit rate, etc.

[0072]

[0083] Certain problems may arise in providing configuration information for accessing services provided by a home SP, such as via IMS. For example, to access services provided by a home SP, the UE 120 may use configuration information, which may include an address of a P-CSCF 360 (e.g., a P-CSCF address such as an IP address, a DNN, a single network slice selection assistance information (S-NSSAI), etc.), a tunnel configuration (e.g., a DNN, an S-NSSAI, a tunneling type (e.g., Layer 2 tunneling protocol (L2TP) or IP Security (IPSec)), a tunnel server address, credentials, an indication of whether a dedicated or shared tunnel should be established, etc.). The address of the P-CSCF 360 may typically be provided to the UE 120 via a protocol configuration option (PCO) sent by a home SMF of the UE 120. However, in the exemplary environment 300, the home SP is not associated with an SMF. Therefore, the UE 120 is not able to receive the address of the P-CSCF 360, which prevents the UE 120 from accessing the services provided by the home SP. Furthermore, if no mechanism is 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 hindered.The techniques and apparatus described herein with respect to Figures 5 and 6 enable the provision of such configuration information to the UE 120 or UPF 320, 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 differently located devices and / or networks than 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 (e.g., one or more devices) of the exemplary environment 300 may perform one or more functions described as being performed by another set of devices of the exemplary environment 300.

[0074]

[0085] 4 is a diagram of an example environment 400 of an SNPN and a network associated with a home SP of a UE 120. The SNPN is labeled as a V-SNPN because the UE 120 is visiting the SNPN in the example 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 the network entities are labeled (e.g., N1, N2, etc.). The functions and / or networks of the example environment 400 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0075]

[0086] As shown, the V-SNPN includes an AMF (e.g., AMF 305), an access node (e.g., access node 315), a UPF (e.g., UPF 320), a PCF (e.g., vPCF 340), an NSSF (e.g., NSSF 345), and a data network (e.g., data network 350). These network functions and networks are described in connection with FIG.

[0076]

[0087] In the exemplary environment 400, a home SP is associated with an AUSF 405 (e.g., AUSF 330) and a UDM 410 (e.g., UDM 325). The exemplary environment 400 may be considered a local breakout architecture and may enable interconnection between an SNPN and a home SN network using a roaming architecture. For example, the AUSF 405 and UDM 410 may enable access to SNPN services (e.g., local data services or Internet access). The architecture of the exemplary environment 400 may be applicable to a home SP that implements an AUSF and a UDM, such as a PLMN provider, an SNPN provider, etc. As shown, the AUSF 405 may interface with an AMF, the UDM 410 may interface with an AMF and an SMF, and the AUSF 405 and UDM 410 may interface with each other. Additionally, the home SP is associated with an IMS, which includes a P-CSCF (e.g., P-CSCF 360) and an S-CSCF (e.g., S-CSCF 365). In some aspects, the IMS may include an IMS-HSS (eg, IMS-HSS370).

[0077]

[0088] Certain problems may arise in providing configuration information for accessing services provided by a home SP, such as via IMS. For example, to access services provided by a home SP, UE 120 may use configuration information, which may include an address of a P-CSCF (e.g., a P-CSCF address such as an IP address, a DNN, a Single Network Slice Selection Assistance Information (S-NSSAI), etc.), a tunnel configuration (e.g., a DNN, an S-NSSAI, a tunneling type (e.g., Layer 2 Tunneling Protocol (L2TP) or IP Security (IPSec)), a tunnel server address, credentials, an indication of whether a dedicated or shared tunnel should be established, etc.). The address of the P-CSCF may typically be provided to UE 120 via a PCO sent by the home SMF of UE 120. However, in the exemplary environment 400, the home SP is not involved in the session establishment on the SNPN. Therefore, UE 120 is not able to receive the address of the P-CSCF, which prevents UE 120 from accessing services provided by the home SP. Furthermore, there may be no mechanism for providing tunnel configuration from an AAA server to the 5G system, so tunneling between the SNPN and the home SP domain may not be possible for the UPF, which reduces privacy and prevents the use of secure tunneling protocols such as L2TP and IPSec. The techniques 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 UE 120 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 differently located devices and / or networks than 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 (e.g., one or more devices) of the exemplary environment 400 may perform one or more functions described as being performed by another set of devices of the exemplary environment 400.

[0079]

[0090] FIG. 5 illustrates an example 500 of providing configuration information from a home SP for a UE visiting an SNPN. The example 500 includes a UE (e.g., UE 120), an SMF (e.g., SMF 310), a UDM (e.g., UDM 325), an AAA proxy (e.g., AUSF 330 and / or AAA proxy 335), and an AAA server (e.g., AAA server 355). Functionality associated with the SNPN is shown to the left of the vertical dashed line, and functionality associated with the home SP is shown to the right of the vertical dashed line. In some aspects, the operations of the example 500 may be performed by one or more devices of the example environment 300. In the example illustrated in FIG. 5, a P-CSCF address is passed from a third-party AAA server to the 5GS when authenticating the UE, and the SMF in the visited SNPN creates a PCO with the P-CSCF address and signals the PCO to the UE.

[0080]

[0091] At 505, the AAA server (e.g., a home SP associated with the AAA server) may configure a set of configuration information. In some aspects, the AAA server may receive the configuration information. The configuration information may include any information that may be signaled to the UE via a PCO component of a message. In example 500, the configuration information includes at least one of an address for a P-CSCF (e.g., P-CSCF 360), a DNN, or an S-NSSAI. In some aspects, the configuration information may indicate an association between a DNN and S-NSSAI (DNN / S-NSSAI) and an address for the P-CSCF. In some aspects, the configuration information may include a tunnel configuration, as described elsewhere herein. This configuration information may be used by the UE 120 to access services provided by the IMS of the home SP. In some aspects, if the AAA server uses a RADIUS protocol, the configuration information may be configured using a vendor-specific attribute parameter.

[0081]

[0092] At 510, the UE may be authenticated with respect to the SNPN. For example, the UE may attempt to establish a connection with the SNPN (e.g., may register with the SNPN). To establish a connection with the SNPN, a 5G system (5GS) of the SNPN (e.g., one or more of the network entities of the SNPN in example 300) may authenticate the UE with an AAA server. For example, an authentication procedure may run between the 5GS and the AAA server. In some aspects, an AAA proxy may handle the interaction with the AAA server for purposes of authentication.

[0082]

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

[0083]

[0094] At 520, the UE and the SMF may identify a PDU session. For example, the UE and the SMF may attempt to establish a PDU session or may successfully establish a PDU session. The UE may establish a PDU session for a DNN / S-NSSAI indicated by the configuration information. For example, the PDU session may be associated with the DNN / S-NSSAI. The UE may establish a PDU session to utilize a service provided by a home SP. For example, the UE may have a subscription to the service, and thus the DNN / S-NSSAI may be known to the UE.

[0084]

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

[0085]

[0096] At 530, the UDM may determine to request configuration information. For example, the UDM may determine to request at least a portion of the configuration information (e.g., an address for a P-CSCF corresponding to a DNN / S-NSSAI associated with the PDU session). In some aspects, the UDM may determine to request the configuration information based at least in part on an explicit indication in the subscription. For example, the subscription may include information indicating to request the configuration information. In some aspects, the UDM may determine to request the configuration information based at least in part on a local configuration. For example, a configuration of the UDM may cause the UDM to request the configuration information.

[0086]

[0097] At 535, the UDM may request configuration information from the AAA proxy. For example, the UDM may 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 (e.g., made available to the AAA proxy) to the AAA proxy for the DNN / S-NSSAI associated with the PDU session (e.g., by the AAA server). For example, the UDM may provide a request for an address for the P-CSCF, which may identify the DNN / S-NSSAI. Alternatively, the UDM may provide a request for any available configuration information for the UE. At 540, the AAA proxy may provide the UDM with an address for the P-CSCF based at least in part on the request. For example, the AAA proxy may determine that an address for the P-CSCF corresponding to the DNN / S-NSSAI is available and may provide the address based at least in part on the request. Alternatively, the AAA proxy may provide all available configuration information based at least in part on the request.

[0087]

[0098] In some aspects, the AAA proxy may provide an address for the P-CSCF to the AMF of the SNPN, and the AMF may provide an address for 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 an authentication procedure as indicated by reference numeral 510).

[0088]

[0099] At 545, the UDM may provide an address for the P-CSCF to the SMF in the visited SNPN. In some aspects, the UDM may provide the address for the P-CSCF along with subscription information associated with the UE and / or the SMF. At 550, the SMF in the visited SNPN may provide the address for the P-CSCF to the UE. For example, the SMF may provide the address for the P-CSCF in a PCO component of a message, such as a non-access stratum (NAS) message. In such a case, the SMF may create a PCO, embed the address for the P-CSCF in the PCO, and deliver the PCO to the UE. The UE may use the address for the P-CSCF to access services provided by a home SP based at least in part on the DNN / S-NSSAI. In this manner, a UE visiting an SNPN may obtain an address for a P-CSCF associated with a home SN that does not have an SMF, thereby enabling the UE to access subscribed services provided by the IMS of the home SNPN.

[0089]

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

[0090]

[0101] FIG. 6 illustrates an example 600 of providing configuration information from a home SP for a UE accessing an SNPN in accordance with the present disclosure. The example 600 includes a UE (e.g., UE 120), an SMF (e.g., SMF 310), a UDM (e.g., UDM 325), an AAA proxy (e.g., AUSF 330 and / or AAA proxy 335), and an AAA server (e.g., AAA server 355). Functionality associated with the SNPN is shown to the left of the vertical dashed line, and functionality associated with the home SP is shown to the right of the vertical dashed line. In some aspects, the operations of the example 600 may be performed by one or more devices of the example environment 300. The example 600 illustrates how a tunnel configuration may be passed from a third-party AAA server to a 5GS associated with the SNPN when authenticating a UE, and how the UPF may establish a tunnel based at least in part on the tunnel configuration received from the AAA server. The example 600 is associated with a data network provider, which is referred to as a home service provider (SP) in the context of the example 600. In some aspects, the data network provider may be a company.

[0091]

[0102] At 605, an AAA server (e.g., a home data network provider associated with the AAA server) may configure a set of configuration information. In some aspects, the AAA server may receive the configuration information. In example 600, the configuration information includes a tunnel configuration. The tunnel configuration may include, for example, a DNN, an S-NSSAI, information indicating a tunneling type (e.g., L2TP, IPSec), a tunnel server address (e.g., an address of an L2TP network server, an address of an IPSec network server), one or more credentials (e.g., a tunnel password), an indication of whether a dedicated tunnel or a shared tunnel should be established, etc. In some aspects, the configuration information may indicate an association between a 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 IMS of the home SP. In some aspects, if the AAA server uses a RADIUS protocol, the configuration information may be configured using a vendor-specific attribute parameter.

[0092]

[0103] At 610, the UE may be authenticated with respect to the SNPN. For example, the UE may attempt to establish a connection with the SNPN. To establish a connection with the SNPN, a 5GS of the SNPN (e.g., one or more of the network entities of the SNPN in example 300) may authenticate the UE with an AAA server. For example, an authentication procedure may run between the 5GS and the AAA server. In some aspects, an AAA proxy may handle the interaction with the AAA server for purposes of authentication.

[0093]

[0104] At 615, the AAA server may provide configuration information to the AAA proxy. In example 600, as illustrated by the provision of configuration information within the dashed box, the AAA server provides the configuration information to the AAA proxy during authentication of the UE. In some aspects, the AAA server may provide the configuration information to the AAA proxy after authentication of the UE (e.g., successful authentication) or before authentication of the UE. In some aspects, the AAA server may provide the configuration information based at least in part on authentication of the UE. For example, the AAA server may provide configuration information associated with the UE and / or associated with a service provided by a home SP that the UE is attempting to access. Additionally or alternatively, authentication may trigger the AAA server to provide the configuration information. It should be noted that the AAA proxy is optional and that in some aspects the AAA server may communicate with another network function of the SNPN.

[0094]

[0105] At 620, the SMF may identify a PDU session. For example, the UE and the SMF may attempt to establish a PDU session or may successfully establish a PDU session. The SMF may establish a PDU session for a DNN / S-NSSAI indicated by the configuration information. For example, the PDU session may be associated with the DNN / S-NSSAI. The UE and / or the SMF may establish a PDU session to utilize a service provided by the home SP.

[0095]

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

[0096]

[0107] At 635, the UDM may request configuration information from the AAA proxy. For example, the UDM may 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 has been provided (e.g., made available to the AAA proxy) to the AAA proxy for the DNN / S-NSSAI associated with the PDU session (e.g., by an AAA server). For example, the UDM may provide a request for a tunnel configuration, which may identify the DNN / S-NSSAI. Alternatively, the UDM may provide a request for any available configuration information for the UE. At 640, the AAA proxy may provide the tunnel configuration to the UDM based at least in part on the request. For example, the AAA proxy may determine that a tunnel configuration corresponding to the DNN / S-NSSAI is available and may provide the tunnel configuration based at least in part on the request. Alternatively, the AAA proxy may provide all available configuration information based at least in part on the request. In some aspects, the AAA proxy may be optional or may not be implemented in the SNPN.

[0097]

[0108] In some aspects, the AAA proxy may provide the tunnel configuration to the AMF of the SNPN, which in turn may provide the tunnel configuration to the SMF. For example, the AAA proxy may provide the tunnel configuration to the AMF based at least in part on an authentication request from the AMF (e.g., as part of the authentication procedure indicated by reference numeral 610).

[0098]

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

[0099]

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

[0100]

[0111] FIG. 7 illustrates an example 700 of providing configuration information from a home SP for a UE visiting an SNPN in accordance with the present disclosure. The example 700 includes a UE (e.g., UE 120), an SMF (e.g., SMF 310), and a UDM (e.g., UDM 410). Functionality associated with the SNPN is shown to the left of the vertical dashed line, and functionality associated with the home SP is shown to the right of the vertical dashed line. In some aspects, the operations of the example 700 may be performed by one or more devices of the example environment 400. The example 700 illustrates how an address for a P-CSCF may be configured in a third-party UDM (e.g., associated with the home SP and external to the SNPN) and signaled to a visited SMF, and how the visited SMF can provide the address for the P-CSCF to the UE, such as by creating a PCO with the address for the P-CSCF and signaling the PCO to the UE.

[0101]

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

[0102]

[0113] At 710, the UE may be authenticated with respect to the SNPN. For example, the UE may attempt to establish a connection with the SNPN. To establish a connection with the SNPN, a 5GS of the SNPN (e.g., one or more of the network entities of the SNPN in example 400) may authenticate the UE with an AUSF associated with the home SP (e.g., AUSF 405, not shown in FIG. 7). For example, an authentication procedure may be performed between the 5GS and the AUSF.

[0103]

[0114] At 715, the UE and the SMF may identify a PDU session. For example, the UE and / or the SMF may attempt to establish a PDU session or may successfully establish a PDU session. The UE may establish a PDU session for a DNN / S-NSSAI indicated by the configuration information. For example, the PDU session may be associated with the DNN / S-NSSAI. The UE may establish a PDU session to utilize a service provided by a home SP. For example, the UE may have a subscription to the service, and thus the DNN / S-NSSAI may be known to the UE.

[0104]

[0115] At 720, the SMF may request session management subscription information from the UDM. The session management subscription information (also referred to as session management subscription data) includes data used for PDU session establishment related to one or more subscriptions associated with the UE. In some aspects, the SMF may request the session management subscription information based at least in part on a DNN / S-NSSAI (e.g., a DNN / S-NSSAI identified by the configuration information), supported capabilities, a PLMN identifier, etc. In some aspects, the SMF may request the configuration information (e.g., implicitly or explicitly based at least in part on having requested the session management subscription information).

[0105]

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

[0106]

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

[0107]

[0118] 8 illustrates an example 800 of providing configuration information from a home SP for a UE visiting an SNPN in accordance with the present disclosure. The example 800 includes a UE (e.g., UE 120), an SMF (e.g., SMF 310), and a UDM (e.g., UDM 410). Functionality associated with the SNPN is shown to the left of the vertical dashed line, and functionality associated with the home SP is shown to the right of the vertical dashed line. In some aspects, operations of example 800 may be performed by one or more devices of example environment 400.

[0108]

[0119] At 805, the UDM (e.g., a home SP associated with the UDM) may configure a set of configuration information. In some aspects, the UDM may receive the configuration information. In example 800, the configuration information includes a tunnel configuration. The tunnel configuration may include, for example, a DNN, an S-NSSAI, information indicating a tunneling type (e.g., L2TP, IPSec), a tunnel server address, one or more credentials, an indication of whether a dedicated or shared tunnel should be established, etc. In some aspects, the configuration information may indicate an association between a 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 IMS of the home SP.

[0109]

[0120] At 810, the UE may be authenticated with respect to the SNPN. For example, the UE may attempt to establish a connection with the SNPN. To establish a connection with the SNPN, a 5GS of the SNPN (e.g., one or more of the network entities of the SNPN in example 400) may authenticate the UE with an AUSF associated with the home SP (e.g., AUSF 405, not shown in FIG. 8). For example, an authentication procedure may be performed between the 5GS and the AUSF.

[0110]

[0121] At 815, the UE and the SMF may identify a PDU session. For example, the UE and the SMF may attempt to establish a PDU session or may successfully establish a PDU session. The UE may establish a PDU session for a DNN / S-NSSAI indicated by the configuration information. For example, the PDU session may be associated with the DNN / S-NSSAI. The UE may establish a PDU session to utilize a service provided by a home SP. For example, the UE may have a subscription to the service, and thus the DNN / S-NSSAI may be known to the UE.

[0111]

[0122] At 820, the SMF may request session management subscription information from the UDM. The session management subscription information includes data used for PDU session establishment related to one or more subscriptions associated with the UE. In some aspects, the SMF may request the session management subscription information based at least in part on a DNN / S-NSSAI (e.g., a DNN / S-NSSAI identified by the configuration information), supported capabilities, a PLMN identifier, etc. In some aspects, the SMF may request the configuration information (e.g., implicitly or explicitly based at least in part on having requested the session management subscription information).

[0112]

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

[0113]

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

[0114]

[0125] 9 is a flowchart of an example method 900 of wireless communication. The method 900 may be performed, for example, by a first network entity (e.g., the SMF 310, the SMF of FIG. 4, the AMF 305, the AMF of FIG. 4).

[0115]

[0126] At 910, the first network entity may identify a PDU session with the UE. For example, the first network entity may identify a PDU session with the UE (e.g., UE 120) (e.g., using session establishment component 1208 shown in FIG. 12), e.g., as described above in connection with FIG. 5 at 520, FIG. 6 at 620, FIG. 7 at 715, and FIG. 8 at 815. In some aspects, 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 (and the first network entity may be associated with that network), such as a SNPN or public network. Configuration information may be associated with the first data network provider, such as the first service provider. In some aspects, the first network entity is an authentication, authorization, and accounting server (e.g., AAA server 355) and the configuration information is obtained via one or more third network entities (e.g., AUSF 330, AAA proxy 335, UDM 325, AMF 305) associated with the stand-alone non-public network. In some aspects, the network entity associated with the first service provider is a unified data management function (e.g., UDM 410) of the network associated with the first service provider. The configuration information may include a tunnel configuration for a tunnel between a second network entity associated with the first network and a second network associated with the first data network provider.

[0116]

[0127] At 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 can obtain (e.g., using the receiving component 1202 shown in FIG. 12) configuration information associated with the first data network provider (e.g., a service provider) based at least in part on identifying the PDU session, e.g., as described above in connection with FIG. 5 at 525 and 545, FIG. 6 at 625 and 645, FIG. 7 at 720 and 725, and FIG. 8 at 820 and 825, where the first network entity is associated with a network (e.g., an SNPN or a public network) provided by the second data network provider (e.g., a service provider). In some aspects, obtaining the configuration information further comprises requesting a template subscription indicating to request the configuration information from a third network entity (e.g., AMF 305, UDM 325) associated with the stand-alone non-public network, where the third network entity is an access and mobility management function or an integrated data management function. In some aspects, requesting the template subscription indicating to request the configuration information is based at least in part on successful authentication of the UE. In some aspects, obtaining the configuration information further comprises obtaining the configuration information from a network entity (e.g., AAA server 355, UDM 410) associated with the first service provider.

[0117]

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

[0118]

[0129] 9 illustrates example blocks of method 900, in some aspects method 900 may include additional, fewer, different, or differently arranged blocks compared to the blocks illustrated in FIG 9. Additionally or alternatively, two or more of the blocks of method 900 may be performed in parallel.

[0119]

[0130] 10 is a flowchart of an example method 1000 of wireless communication. The method 1000 may be performed, for example, by a first network entity (e.g., the UDM 325, the UDM 410, the AMF 305, the AMF of FIG. 4).

[0120]

[0131] At 1010, the first network entity may receive a request for configuration information associated with a first service provider from a second network entity, where the first network entity and the second network entity are associated with a standalone non-public network provided by the second service provider. For example, the first network entity may receive (e.g., using the receiving component 1402 shown in FIG. 14) a request for configuration information associated with the first service provider from a second network entity (e.g., AMF 305, SMF 310, AMF of FIG. 4, SMF of FIG. 4), where the first network entity and the second network entity are associated with a standalone non-public network provided by a second service, as described above in connection with FIG. 5 at 525 and FIG. 6 at 625. In some aspects, the request is received based at least in part on a PDU session established (e.g., identified) between the UE and the second network entity. In some aspects, the configuration information includes a proxy call session control function address for a proxy call session control function (P-CSCF 360, P-CSCF in FIG. 4) associated with the first service provider. In some aspects, the configuration information includes a tunnel configuration for a tunnel between a second network entity and a network associated with the first service provider.

[0121]

[0132] At 1020, the first network entity may determine (e.g., using the determination component 1408 shown in FIG. 14 ) that configuration information is to be obtained from the proxy entity based at least in part on the request for the configuration information or based at least in part on the configuration of the first network entity. The dashed border of the block indicated by 1020 indicates that the action indicated by 1020 is optional.

[0122]

[0133] At 1030, the first network entity may obtain the configuration information from a proxy entity associated with the stand-alone, non-public network based at least in part on the request for the configuration information. For example, the first network entity may obtain (e.g., using the receiving component 1402 shown in FIG. 14 ) the configuration information from a proxy entity (e.g., AUSF 330, AAA proxy 335) associated with the stand-alone, non-public network based at least in part on the request for the configuration information, e.g., as described above in connection with FIG. 5 at 535 and 540 and FIG. 6 at 635 and 640.

[0123]

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

[0124]

[0135] At 1040, the first network entity may transmit the configuration information to the second network entity. For example, the first network entity may transmit (e.g., using the transmitting component 1404 shown in FIG. 14) the configuration information to the second network entity, e.g., as described above in connection with FIG. 5 at 545 and FIG. 6 at 645. In some aspects, the configuration information is transmitted to the second network entity as part of subscription information associated with the second network entity.

[0125]

[0136] In some aspects, the first network entity is an integrated data management function (UDM 325, UDM 410) or an access and mobility management function (AMF 305), and the second network entity is a session management function (SMF 310, SMF in FIG. 4).

[0126]

[0137] 10 illustrates example blocks of method 1000, in some aspects method 1000 may include additional, fewer, different, or differently arranged blocks compared to the blocks illustrated in FIG 10. Additionally or alternatively, two or more of the blocks of method 1000 may be performed in parallel.

[0127]

[0138] 11 is a flowchart of an example method of wireless communication 1100. The method 1100 may be performed, for example, by a first network entity (e.g., the AUSF 330, the AAA proxy 335).

[0128]

[0139] At 1110, the first network entity may receive configuration information associated with the UE accessing the stand-alone 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 may receive (e.g., using the receiving component 1602 shown in FIG. 16) from a network entity (e.g., AAA server 355) associated with the first service provider, configuration information associated with the UE accessing the stand-alone non-public network associated with the first network entity, where the stand-alone non-public network is associated with a second service provider, as described above in connection with FIG. 5 at 515 and FIG. 6 at 615. In some aspects, receiving the configuration information is based at least in part on the UE being authenticated on the stand-alone non-public network. In some aspects, the configuration information includes at least one of a Proxy Call Session Control Function (P-CSCF) address for a 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 aspects, the configuration information includes a tunnel configuration for a tunnel between the second network entity and a network associated with the first service provider, where the tunnel configuration includes at least one of: 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 tunnel or a dedicated tunnel.

[0130]

[0141] At 1120, the first network entity may receive a request for at least a portion of the configuration information from a second network entity associated with the stand-alone, non-public network. For example, the first network entity may receive (e.g., using the receiving component 1602 shown in FIG. 16 ) a request for at least a portion of the configuration information from a second network entity (e.g., AMF 305, SMF 310, UDM 325) associated with the stand-alone, non-public network, e.g., as described above in connection with FIG. 5 at 535 and FIG. 6 at 635.

[0131]

[0142] At 1130, the first network entity may transmit the configuration information to the second network entity based at least in part on the request. For example, the first network entity may transmit (e.g., using the transmitting component 1604 shown in FIG. 16 ) the configuration information to the second network entity based at least in part on the request, e.g., as described above in connection with FIG. 5 at 540 and FIG. 6 at 640.

[0132]

[0143] In some aspects, 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] 11 illustrates example blocks of method 1100, in some aspects method 1100 may include additional, fewer, different, or differently arranged blocks compared to the blocks illustrated in FIG 11. Additionally or alternatively, two or more of the blocks of method 1100 may be performed in parallel.

[0134]

[0145] FIG. 12 is a block diagram of an example apparatus 1200 for wireless communication. The apparatus 1200 may be a first network entity (e.g., SMF 310, SMF of FIG. 4, AMF 305, AMF of FIG. 4) or the first network entity may include the apparatus 1200. In some aspects, the apparatus 1200 includes a receiving component 1202 and a transmitting component 1204, which may be in communication with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using the receiving component 1202 and the transmitting component 1204. As further shown, the apparatus 1200 may include a session establishment component 1208, among other examples.

[0135]

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

[0136]

[0147] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing on the received communications (such as filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components of the device 1206. In some aspects, the receiving component 1202 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or combinations thereof of a first network entity as described above in connection with FIG. 2.

[0137]

[0148] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1206 may generate communications and provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communications and transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or combinations thereof, of the first network entity described above in connection with FIG. 2. In some aspects, the transmitting component 1204 may be co-located with the receiving component 1202 in a transceiver. In some aspects, the transmitting component 1204 can interface with a radio unit, which can be co-located or non-co-located with the transmitting component 1204. For example, the transmitting component 1204 can be associated with a distributed unit (DU) in a discrete radio access network deployment.

[0138]

[0149] The session establishment component 1208 can identify a PDU session with the UE. The receiving component 1202 can obtain configuration information associated with a first service provider based at least in part on identifying the PDU session, where the first network entity is associated with a stand-alone, non-public network provided by a second service provider. The transmitting component 1204 can transmit the configuration information to the UE or to a second network entity associated with the stand-alone, 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, fewer, different, or differently arranged components than those shown in Figure 12. Furthermore, two or more of the 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 components (or 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] 13 illustrates an example hardware implementation 1300 for a device 1305 employing a processing system 1310. The device 1305 may be a first network entity.

[0141]

[0152] The processing system 1310 may be implemented with a bus architecture, represented generally by bus 1315. The bus 1315 may include any number of interconnecting buses and bridges depending on the particular application of the processing system 1310 and the overall design constraints. The bus 1315 links together various circuits including the processor 1320, the illustrated components, and one or more processors and / or hardware components represented by computer-readable medium / memory 1325. The bus 1315 may 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 a means for communicating with various other devices over 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 the receiving component 1202. In addition, the transceiver 1330 receives information from the processing system 1310, specifically the transmitting component 1204, and generates a signal to be applied to the 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 aspects, the interface may include the transceiver 1330 and / or one or more antennas 1335. In some other aspects, the device 1305 may not include a 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, which when executed by the processor 1320 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 that is manipulated by the processor 1320 when executing the software. The processing system further includes at least one of the components shown, which may be software modules running on the processor 1320, residing / stored on the computer readable medium / memory 1325, one or more hardware modules coupled to the processor 1320, or some combination thereof.

[0144]

[0155] In some aspects, the processing system 1310 may be a component of the base station 110 and may include the memory 242 and / or at least one of the TX MIMO processor 230, the RX processor 238, and / or the controller / processor 240. In some aspects, the processing system 1310 may be a component of a CU. In some aspects, the processing system 1310 may be a component of a DU. In some aspects, the processing system 1310 may be a component of a RU. In some aspects, the processing system 1310 may be one or more components of a 5G system such as shown in FIG. 3 and FIG. 4 and may include a memory and one or more processors. In some aspects, an apparatus 1305 for wireless communication includes means for identifying a PDU session with a UE, means for obtaining configuration information associated with a first service provider, and means for transmitting the configuration information to a UE associated with a standalone non-public network provided by a second service or to a second network entity associated with the 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 configured to perform the functions recited by the aforementioned means. As in certain aspects described elsewhere herein, the processing system 1310 may include the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240. In one configuration, the aforementioned means may be the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240 configured to perform the functions and / or operations recited herein.

[0145]

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

[0146]

[0157] FIG. 14 is a block diagram of an example apparatus 1400 for wireless communication. The apparatus 1400 may be a first network entity (e.g., UDM 325, UDM 410, AMF 305, AMF of FIG. 4) or the first network entity may include the apparatus 1400. In some aspects, the apparatus 1400 includes a receiving component 1402 and a transmitting component 1404, which may be in communication with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device) using the receiving component 1402 and the transmitting component 1404. As further shown, the apparatus 1400 may include a determining component 1408, among other examples.

[0147]

[0158] In some aspects, the apparatus 1400 may be configured to perform one or more operations described herein in conjunction with FIGS. 3-8. Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as the method 1000 of FIG. 10, or a combination thereof. In some aspects, the apparatus 1400 and / or one or more components illustrated in FIG. 14 may include one or more components of a first network entity described above in conjunction with FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 14 may be implemented within one or more components described above in conjunction with FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium executable by a controller or processor to perform the function or operation of that component.

[0148]

[0159] The receiving component 1402 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1406. The receiving component 1402 may provide the received communications to one or more other components of the device 1400. In some aspects, the receiving component 1402 may perform signal processing on the received communications (such as filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components of the device 1406. In some aspects, the receiving component 1402 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or combinations thereof of a first network entity as described above in connection with FIG. 2.

[0149]

[0160] The transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1406. In some aspects, one or more other components of the device 1406 may generate communications and provide the generated communications to the transmitting component 1404 for transmission to the device 1406. In some aspects, the transmitting component 1404 may perform signal processing (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communications and transmit the processed signals to the device 1406. In some aspects, the transmitting component 1404 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or combinations thereof, of the first network entity described above in connection with FIG. 2. In some aspects, the transmitting component 1404 may be co-located with the receiving component 1402 in a transceiver.

[0150]

[0161] The receiving component 1402 can receive a request from a second network entity for configuration information associated with a first service provider, where the first network entity and the second network entity are associated with a stand-alone, non-public network provided by the second service provider, where the configuration information is related to a UE associated with the first service provider that accesses the stand-alone, non-public network. The receiving component 1402 can obtain the configuration information from a proxy entity associated with the stand-alone, non-public network based at least in part on the request for the configuration information. The transmitting component 1404 can transmit the configuration information to the second network entity.

[0151]

[0162] The determination component 1408 may determine that the configuration information is to be obtained from the proxy entity based at least in part on a request for the configuration information or based at least in part on a 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, fewer, different, or differently arranged components than those shown in Figure 14. Furthermore, two or more of the 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 components (or 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] 15 illustrates an example hardware implementation 1500 for a device 1505 employing a processing system 1510. The device 1505 may be a first network entity.

[0154]

[0165] The processing system 1510 may be implemented with a bus architecture, represented generally by bus 1515. The bus 1515 may include any number of interconnecting buses and bridges depending on the particular application of the processing system 1510 and the overall design constraints. The bus 1515 links together various circuits including the processor 1520, the components shown, and one or more processors and / or hardware components represented by computer-readable medium / memory 1525. The bus 1515 may 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 a means for communicating with various other devices over a transmission medium. The transceiver 1530 receives signals from the one or more antennas 1535, extracts information from the received signals, and provides the extracted information to the processing system 1510, specifically the receiving component 1402. In addition, the transceiver 1530 receives information from the processing system 1510, specifically the transmitting component 1404, and generates signals to be applied to the 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, which when executed by the processor 1520 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 that is manipulated by the processor 1520 when executing the software. The processing system further includes at least one of the components shown. The components may be software modules running on the processor 1520, residing / stored on the computer readable medium / memory 1525, one or more hardware modules coupled to the processor 1520, or some combination thereof.

[0157]

[0168] In some aspects, the processing system 1510 may be a component of the base station 110 and may include the memory 242 and / or at least one of the TX MIMO processor 230, the RX processor 238, and / or the controller / processor 240. In some aspects, the processing system 1510 may be one or more components of a 5G system such as shown in FIG. 3 and FIG. 4 and may include the memory and one or more processors. In some aspects, an apparatus 1505 for wireless communication includes means for receiving a request from a second network entity for configuration information associated with a first service provider, where the first network entity and the second network entity are associated with a standalone, non-public network provided by the second service provider, means for obtaining configuration information from a proxy entity associated with the standalone, non-public network based at least in part on the request for configuration information, 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 configured to perform the functions recited by the aforementioned means. As in certain aspects described elsewhere herein, the processing system 1510 may include the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240. In one configuration, the aforementioned means may be the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240 configured to perform the functions and / or operations recited herein.

[0158]

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

[0159]

[0170] FIG. 16 is a block diagram of an example apparatus 1600 for wireless communication. The apparatus 1600 may be a first network entity, or the first network entity may include the apparatus 1600. In some aspects, the apparatus 1600 includes a receiving component 1602 and a transmitting component 1604, which may be in communication with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1600 may communicate with another apparatus 1606 (such as a UE, a base station, or another wireless communication device) using the receiving component 1602 and the transmitting component 1604. As further shown, the apparatus 1600 may include a communication component 1608, among other examples.

[0160]

[0171] In some aspects, the apparatus 1600 may be configured to perform one or more operations described herein in conjunction with FIGS. 3-8. Additionally or alternatively, the apparatus 1600 may be configured to perform one or more processes described herein, such as the method 1100 of FIG. 11, or a combination thereof. In some aspects, the apparatus 1600 and / or one or more components illustrated in FIG. 16 may include one or more components of a first network entity described above in conjunction with FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 16 may be implemented within one or more components described above in conjunction with FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium executable by a controller or processor to perform the function or operation of the component.

[0161]

[0172] The receiving component 1602 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1606. The receiving component 1602 may provide the received communications to one or more other components of the device 1600. In some aspects, the receiving component 1602 may perform signal processing on the received communications (such as filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components of the device 1606. In some aspects, the receiving component 1602 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or combinations thereof of a first network entity as described above in connection with FIG. 2.

[0162]

[0173] The transmitting component 1604 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1606. In some aspects, one or more other components of the device 1606 may generate communications and provide the generated communications to the transmitting component 1604 for transmission to the device 1606. In some aspects, the transmitting component 1604 may perform signal processing (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communications and transmit the processed signals to the device 1606. In some aspects, the transmitting component 1604 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or combinations thereof, of the first network entity described above in connection with FIG. 2. In some aspects, the transmitting component 1604 may be co-located with the receiving component 1602 in a transceiver.

[0163]

[0174] The receiving component 1602 or the communication component 1608 can receive configuration information associated with a UE accessing a stand-alone non-public network associated with a first network entity from a network entity associated with a first service provider, where the stand-alone non-public network is associated with a second service provider. For example, the communication component 1608 can handle communications with a network entity associated with the first service provider. The receiving component 1602 can receive a request for at least a portion of the configuration information from a second network entity associated with the stand-alone non-public network. The transmitting component 1604 can transmit 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, fewer, different, or differently arranged components than those shown in Figure 16. Furthermore, two or more of the 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 components (or 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] 17 illustrates an example hardware implementation 1700 for a device 1705 employing a processing system 1710. The device 1705 may be a first network entity.

[0166]

[0177] The processing system 1710 may be implemented with a bus architecture, represented generally by bus 1715. The bus 1715 may include any number of interconnecting buses and bridges depending on the particular application of the processing system 1710 and the overall design constraints. The bus 1715 links together various circuits including the processor 1720, the depicted components, and one or more processors and / or hardware components represented by computer-readable medium / memory 1725. The bus 1715 may 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 a means for communicating with various other devices over a transmission medium. The transceiver 1730 receives signals from the one or more antennas 1735, extracts information from the received signals, and provides the extracted information to the processing system 1710, specifically the receiving component 1602. In addition, the transceiver 1730 receives information from the processing system 1710, specifically the transmitting component 1604, and generates signals to be applied to the 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, which when executed by the processor 1720 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 that is manipulated by the processor 1720 when executing the software. The processing system further includes at least one of the components shown. Those components may be software modules running on the processor 1720, residing / stored on the computer readable medium / memory 1725, one or more hardware modules coupled to the processor 1720, or some combination thereof.

[0169]

[0180] In some aspects, the processing system 1710 may be a component of the base station 110 and may include the memory 242 and / or at least one of the TX MIMO processor 230, the RX processor 238, and / or the controller / processor 240. In some aspects, the processing system 1710 may be one or more components of a 5G system such as those shown in FIG. 3 and FIG. 4 and may include the memory and one or more processors. In some aspects, an apparatus 1705 for wireless communication includes means for receiving configuration information associated with 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 the 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 may be one or more of the aforementioned components of the apparatus 1600 and / or the processing system 1710 of the apparatus 1705 configured to perform the functions recited by the aforementioned means. As in certain aspects described elsewhere herein, the processing system 1710 may include the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240. In one configuration, the aforementioned means may be the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240 configured to perform the functions and / or operations recited 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 provides an overview of some aspects of the disclosure.

[0172]

[0183] Aspect 1: A method of wireless communications performed by a first network entity, the method comprising: identifying a protocol data unit (PDU) session with a user equipment (UE); and obtaining configuration information associated with a first service provider based at least in part on identifying the PDU session; and wherein the first network entity transmits 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 the standalone, non-public network.

[0173]

[0184] Aspect 2: The method of aspect 1, wherein obtaining the configuration information further comprises requesting a subscription from a third network entity associated with the stand-alone, non-public network indicating requesting the configuration information, and wherein the third network entity is an integrated data management function, and requests the configuration information based at least in part on the subscription.

[0174]

[0185] Aspect 3: The method of aspect 2, wherein requesting a subscription indicating requesting configuration information is based at least in part on successful authentication of the UE.

[0175]

[0186] Aspect 4: The method of aspect 1, wherein obtaining the configuration information further comprises obtaining the configuration information from a network entity associated with the first service provider.

[0176]

[0187] Aspect 5: The method of aspect 4, wherein the network entity associated with the first service provider is an authentication, authorization, and accounting server, and wherein the configuration information is obtained via one or more third network entities associated with a stand-alone, non-public network.

[0177]

[0188] Aspect 6: The method of aspect 4, wherein the network entity associated with the first service provider is a unified data manager for a network associated with the first service provider.

[0178]

[0189] Aspect 7: The method of any of aspects 1-6, wherein sending the configuration information to the UE further comprises sending the configuration information to the UE in a protocol configuration options component of the message.

[0179]

[0190] Aspect 8: The method of any of aspects 1 to 7, wherein the configuration information sent to the UE includes a proxy call session control function address for a proxy call session control function associated with the first service provider.

[0180]

[0191] Aspect 9: The method of any of aspects 1 to 8, wherein the configuration information sent to the second network entity includes a tunnel configuration for a tunnel between the second network entity and a network associated with the first service provider, wherein the second network entity is a user plane function associated with the UE.

[0181]

[0192] Aspect 10: The method of aspect 9, wherein the tunnel configuration indicates whether the tunnel is a shared tunnel or a dedicated tunnel.

[0182]

[0193] Aspect 11: The method of any of aspects 1 to 10, wherein the configuration information is obtained from an access and mobility management function.

[0183]

[0194] Aspect 12: A method of wireless communications performed by a first network entity, the method comprising: receiving a request from a second network entity for configuration information associated with a first service provider, wherein the first network entity and the second network entity are associated with a stand-alone, non-public network provided by the second service provider, wherein the configuration information is associated with a user equipment (UE) associated with the first service provider that accesses the stand-alone, non-public network; obtaining configuration information from a proxy entity associated with the stand-alone, non-public network based at least in part on the request for configuration information; and transmitting the configuration information to the second network entity.

[0184]

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

[0185]

[0196] Aspect 14: The method of any of aspects 12 to 12, further comprising determining that the configuration information is to be obtained from the proxy entity based at least in part on a request for the configuration information or based at least in part on a configuration of the first network entity.

[0186]

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

[0187]

[0198] Aspect 16: The method of any of aspects 12 to 15, wherein the configuration information is sent to the second network entity as part of subscription information associated with the second network entity.

[0188]

[0199] Aspect 17: The method of any of aspects 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] Aspect 18: The method of any of aspects 12 to 17, wherein the configuration information includes a proxy call session control function address for a proxy call session control function associated with the first service provider.

[0190]

[0201] Aspect 19: The method of any of aspects 12-18, wherein the configuration information includes a tunnel configuration for a tunnel between the second network entity and a network associated with the first service provider.

[0191]

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

[0192]

[0203] Aspect 21: The method of aspect 20, wherein receiving the configuration information is based at least in part on the UE being authenticated on a stand-alone, non-public network.

[0193]

[0204] Aspect 22: The method of any of aspects 20 to 21, wherein the configuration information includes at least one of a Proxy Call Session Control Function (P-CSCF) address for a P-CSCF associated with the first service provider, network slice selection assistance information associated with the first service provider, or a data network name associated with the first service provider.

[0194]

[0205] Aspect 23: The method of aspects 20-22, wherein the configuration information includes a tunnel configuration for a tunnel between the second network entity and a network associated with the first service provider, where the tunnel configuration includes at least one of: a data network name associated with the first service provider, network 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 tunnel or a dedicated tunnel.

[0195]

[0206] Aspect 24: The method of any of aspects 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] Aspect 25: A method of wireless communications performed by a first network entity, the method comprising: identifying a protocol data unit (PDU) session with a user equipment (UE); obtaining configuration information associated with a first data network provider based at least in part on identifying the PDU session; and, wherein the first network entity is associated with a first network provided by a second data network provider, transmitting the configuration information to the UE or to a second network entity associated with the first network, the configuration information including a tunnel configuration for a tunnel between a second network entity associated with the first network and the second network associated with the first data network provider.

[0197]

[0208] Aspect 26: The method of aspect 25, wherein the first network is a stand-alone, non-public network.

[0198]

[0209] Aspect 27: The method of any of aspects 25 to 26, wherein obtaining the configuration information further comprises requesting a subscription from a third network entity associated with the first network indicating to request the configuration information; and requesting the configuration information based at least in part on the subscription.

[0199]

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

[0200]

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

[0201]

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

[0202]

[0213] Aspect 31: The method of aspect 29, wherein the network entity associated with the first data network provider is an integrated data management function of a network associated with the first data network provider.

[0203]

[0214]

[0041] Aspect 32: The method of any of aspects 25 to 31, wherein sending the configuration information to the UE further comprises sending the configuration information to the UE in a protocol configuration options component of the message.

[0204]

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

[0205]

[0216] Aspect 34: The method of any of aspects 25 to 33, wherein the configuration information is obtained from an access and mobility management function.

[0206]

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

[0207]

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

[0208]

[0219] Aspect 37: The method of any of aspects 25 to 36, wherein the tunnel is associated with a Layer 2 Tunneling Protocol or an Internet Protocol security protocol.

[0209]

[0220] Aspect 38: An apparatus for wireless communication in a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of one or more of aspects 1 to 37.

[0210]

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

[0211]

[0222] Aspect 40: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of aspects 1 to 37.

[0212]

[0223] Aspect 41: A non-transitory computer-readable medium having stored thereon code for wireless communication, the code comprising instructions executable by a processor to perform a method of one or more of aspects 1 to 37.

[0213]

[0224] Aspect 42: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more of aspects 1 to 37.

[0214]

[0225] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the embodiments to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the embodiments.

[0215]

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

[0216]

[0227] As used herein, satisfying a threshold can refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc., depending on the context.

[0217]

[0228] Even if certain combinations of features are recited in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure of the various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and / or specifically disclosed herein. Although each dependent claim listed below may depend directly on only one claim, the disclosure of the various aspects includes each dependent claim in combination with any other claims in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. By way of 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 multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other permutation of a, b, and c).

[0218]

[0229] No element, act, or instruction used herein should be construed as critical or required unless expressly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." Additionally, as used herein, the article "the" is intended to include one or more items referred to in conjunction with the article "the" and may be used interchangeably with "the one or more." Additionally, as used herein, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with "one or more." When only one item is intended, the phrase "only one" or similar expression is used. Also, as used herein, terms such as "has," "have," "having," and the like, are intended to be open-ended terms. Additionally, the phrase "based on" is intended to mean "based, at least in part, on," unless expressly stated otherwise. Also, as used herein, the term "or" when used in a series is intended to be inclusive and may be used interchangeably with "and / or," unless expressly stated otherwise (e.g., when used in combination with "either" or "only one of").

Claims

1. A method of wireless communication performed by a session management function, comprising: Identifying a protocol data unit (PDU) session with a user equipment (UE); obtaining configuration information associated with a home service provider based at least in part on identifying the PDU session, wherein the session management function is associated with a first network provided by a stand-alone non-public network provider, wherein the configuration information includes a tunnel configuration for 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 an Internet Protocol Media Subsystem of the home service provider. and transmitting the configuration information to the UE or to the user plane function associated with the first network.

2. The method of claim 1 , wherein the first network is a stand-alone, non-public network.

3. obtaining the configuration information further comprises: requesting a subscription from an integrated data management function associated with the first network indicating a request for the configuration information; and requesting the configuration information based at least in part on the subscription.

4. The method of claim 3 , wherein requesting the subscription indicating a request for the configuration information is based at least in part on successful authentication of the UE.

5. obtaining the configuration information further comprises: The method of claim 1 , comprising obtaining the configuration information from a network entity associated with the home service provider.

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

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

8. Sending the configuration information to the UE further comprises: The method of claim 1 , comprising sending the configuration information to the UE in a protocol configuration options component of a message.

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

10. The method of claim 1 , wherein the configuration information is obtained from an access and mobility management function.

11. The method of claim 1 , wherein the tunnel configuration indicates at least a tunnel server address or one or more credentials for the tunnel.

12. The method of claim 1 , wherein the tunnel is associated with a Layer 2 Tunneling Protocol or an Internet Protocol Security Protocol.

13. 1. A non-transitory computer readable medium storing a set of instructions for wireless communication, the set of instructions comprising: one or more instructions, which when executed by one or more processors of a session management facility: Identifying a protocol data unit (PDU) session with a user equipment (UE); obtaining configuration information associated with a home service provider based at least in part on identifying the PDU session, wherein the session management function is associated with a first network provided by a stand-alone non-public network provider, wherein the configuration information includes a tunnel configuration for 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 an Internet Protocol Media Subsystem of the home service provider. and transmitting the configuration information to the UE or to the user plane function associated with the first network.

14. 14. The non-transitory computer-readable medium of claim 13, wherein the first network is a stand-alone, non-public network.

15. 1. An apparatus for wireless communication, comprising: means for identifying a protocol data unit (PDU) session with a user equipment (UE); and means for obtaining configuration information associated with a home service provider based at least in part on identifying the PDU session, wherein the apparatus is associated with a first network provided by a stand-alone non-public network provider, wherein the configuration information includes a tunnel configuration for 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 an Internet Protocol Media Subsystem of the home service provider. and means for transmitting the configuration information to the UE or to the user plane function associated with the first network.

Images