Support of multicast and broadcast services in independent non-public networks

Abstract

Various aspects described herein generally relate to supporting multicast and broadcast services (MBS) in a standalone non-public network (SNPN). Some aspects are more particularly directed to providing information associated with a network identifier (NID) of an SNPN in a temporary mobile group identifier (TMGI) to implement an MBS in the SNPN. In some aspects, a user equipment (UE) can receive a configuration indicating a TMGI corresponding to an MBS session identifier (ID) associated with an MBS session provided by an SNPN, where the TMGI includes an NID index value or a unique service ID. The UE can then receive a communication associated with the MBS session based at least in part on the NID to which the NID index value is mapped or based at least in part on the unique service ID.

Description

[0001] Cross - Reference to Related Applications

[0002] This patent application claims the priority of Greek Patent Application No. 20220100926, entitled "SUPPORTING MULTICAST AND BROADCAST SERVICES IN A STAND - ALONE NON - PUBLIC NETWORK", filed on November 10, 2022 and assigned to the assignee of this application. The disclosure of the prior application is regarded as part of this patent application and is incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure generally relate to wireless communication, and more particularly, to techniques and apparatus for supporting multicast and broadcast services (MBS) in a stand - alone non - public network (SNPN). Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ multiple access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth or transmit power). Examples of such multiple access techniques 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 / Advanced LTE is an enhanced set of the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the 3rd Generation Partnership Project (3GPP).

[0005] The above multi-access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at the urban, national, regional, or global level. New Radio (NR) (which may be referred to as 5G) is an enhanced set of the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink, CP-OFDM or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technology, and carrier aggregation to improve spectral efficiency, reduce costs, improve services, utilize new spectra, and better integrate with other open standards. With the continuous increase in the demand for mobile broadband access, further improvements to LTE, NR, and other radio access technologies are still useful.

[0006] A Standalone Non-Public Network (SNPN) is a Non-Public Network (NPN) that does not rely on network functions provided by a Public Land Mobile Network (PLMN). The SNPN identifier (ID) is defined by a combination of a PLMN identifier (PLMN ID) and a Network identifier (NID). A Multicast and Broadcast Service (MBS) session is a session that enables point-to-multipoint services, meaning that a single transmitter can broadcast or multicast the same content for multiple UEs to receive. A Temporary Mobile Group Identifier (TMGI) can be used to identify an MBS session. The TMGI is defined by a combination of a PLMNID and a Service ID. The TMGI is not defined to include an SNPNID, so the TMGI does not provide any indication of the NID associated with an SNPN. Conventional techniques for supporting MBS in an SNPN are insufficient. For example, techniques based on the UE for the UE to determine the NID associated with an MBS session provided by an SNPN are insufficient in a Radio Access Network (RAN) sharing scenario. As another example, techniques for signaling a complete list of NIDs to the UE via Radio Resource Control (RRC) signaling in an MBS broadcast configuration significantly increase the signaling overhead. Summary of the Invention

[0007] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include at least one memory and at least one processor communicatively coupled to the at least one memory. The at least one processor may be operable to cause the UE to receive a configuration indicating a temporary mobile group identifier (TMGI) corresponding to an MBS session identifier associated with an MBS session provided by a standalone non-public network (SNPN), the TMGI including a network identifier (NID) index value. The at least one processor may be operable to cause the UE to map the NID index value to an NID associated with the SNPN providing the MBS session. The at least one processor may be operable to cause the UE to receive communications associated with the MBS session based at least in part on the NID.

[0008] Some aspects described herein relate to a network node for wireless communication. The network node may include at least one memory and at least one processor communicatively coupled to the at least one memory. The at least one processor may be operable to cause the network node to send a configuration indicating a TMGI associated with an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value corresponding to an NID associated with the MBS session. The at least one processor may be operable to cause the network node to send communications associated with the MBS session for reception by a UE.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include at least one memory and at least one processor communicatively coupled to the at least one memory. The at least one processor may be operable to cause the UE to receive a configuration indicating a TMGI corresponding to an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including a service identifier that is unique across a radio access network (RAN) shared network set including one or more SNPNs or one or more public land mobile networks (PLMNs). The at least one processor may be operable to cause the UE to receive communications associated with the MBS session based at least in part on the service identifier being unique across the RAN shared network set.

[0010] Some aspects described herein relate to a network node for wireless communication. The network node may include at least one memory and at least one processor communicatively coupled to the at least one memory. The at least one processor may be operable to cause the network node to assign a service identifier to an MBS session provided by an SNPN, the service identifier being unique across a RAN shared network set including one or more SNPNs or one or more PLMNs. The at least one processor may be operable to cause the network node to send a configuration of a TMGI indicating an MBS session identifier associated with the MBS session, the TMGI including the service identifier. The at least one processor may be operable to cause the network node to send communications associated with the MBS session for reception by a UE.

[0011] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a configuration of a TMGI indicating an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value. The method may include mapping the NID index value to an NID associated with the SNPN providing the MBS session. The method may include receiving communications associated with the MBS session at least in part based on the NID.

[0012] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include sending a configuration of a TMGI indicating an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value corresponding to an NID associated with the MBS session. The method may include sending communications associated with the MBS session for reception by a UE.

[0013] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a configuration of a TMGI indicating an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including a service identifier, the service identifier being unique across a RAN shared network set including one or more SNPNs or one or more PLMNs. The method may include receiving communications associated with the MBS session at least in part based on the service identifier being unique across the RAN shared network set.

[0014] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include assigning a service identifier to an MBS session provided by an SNPN, the service identifier being unique across a RAN shared network set including one or more SNPNs or one or more PLMNs. The method may include sending a configuration of a TMGI indicating an MBS session identifier corresponding to the MBS session associated with the MBS session, the TMGI including the service identifier. The method may include sending communication associated with the MBS session for reception by a UE.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a configuration of a TMGI indicating an MBS session identifier corresponding to an MBS session provided by an SNPN, the TMGI including an NID index value. The set of instructions, when executed by one or more processors of the UE, may cause the UE to map the NID index value to an NID associated with the SNPN providing the MBS session. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive communication associated with the MBS session at least in part based on the NID.

[0016] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to send a configuration of a TMGI indicating an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value corresponding to an NID associated with the MBS session. The set of instructions, when executed by one or more processors of the network node, may cause the network node to send communication associated with the MBS session for reception by a UE.

[0017] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a configuration of a TMGI indicating an MBS session identifier corresponding to an MBS session provided by an SNPN, the TMGI including a service identifier, the service identifier being unique across a RAN shared network set including one or more SNPNs or one or more PLMNs. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive communication associated with the MBS session at least in part based on the service identifier being unique across the RAN shared network set.

[0018] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to assign a service identifier to an MBS session provided by an SNPN, the service identifier being unique across a RAN shared network set including one or more SNPNs or one or more PLMNs. The instruction set, when executed by one or more processors of the network node, may cause the network node to send a configuration of a TMGI indicating an MBS session identifier corresponding to the MBS session associated with the MBS session, the TMGI including the service identifier. The instruction set, when executed by one or more processors of the network node, may cause the network node to send communications associated with the MBS session for reception by a UE.

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a configuration of a TMGI indicating an MBS session identifier corresponding to an MBS session associated with an MBS session provided by an SNPN, the TMGI including an NID index value. The apparatus may include means for mapping the NID index value to an NID associated with the SNPN providing the MBS session. The apparatus may include means for receiving communications associated with the MBS session at least in part based on the NID.

[0020] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a configuration of a TMGI indicating an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value corresponding to an NID associated with the MBS session. The apparatus may include means for sending communications associated with the MBS session for reception by a UE.

[0021] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a configuration of a TMGI indicating an MBS session identifier corresponding to an MBS session associated with an MBS session provided by an SNPN, the TMGI including a service identifier, the service identifier being unique across a RAN shared network set including one or more SNPNs or one or more PLMNs. The apparatus may include means for receiving communications associated with the MBS session at least in part based on the service identifier being unique across the RAN shared network set.

[0022] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for assigning a service identifier to an MBS session provided by an SNPN, the service identifier being unique across a set of RAN shared networks including one or more SNPNs or one or more PLMNs. The apparatus may include means for transmitting a configuration indicating a TMGI corresponding to an MBS session identifier associated with the MBS session, the TMGI including the service identifier. The apparatus may include means for transmitting communications associated with the MBS session for reception by a UE.

[0023] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices, or processing systems as fully described with reference to the accompanying drawings and the specification and as illustrated in the accompanying drawings and the specification.

[0024] The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the present disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics (both their organization and method of operation) of the concepts disclosed herein, as well as the associated advantages, will be better understood. Each of the drawings provided is for the purpose of illustration and description only and is not a definition of the limits of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] To obtain a more particular description of the inventive subject matter briefly outlined above, reference may be made to the aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the drawings illustrate only some typical aspects of the present disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. Like reference numerals in different drawings may identify the same or similar elements.

[0026] Figure 1 is a diagram illustrating an example of a wireless network in accordance with the present disclosure.

[0027] Figure 2 is a diagram illustrating communication between an example network node and a user equipment (UE) in a wireless network in accordance with the present disclosure.

[0028] Figure 3 is a diagram illustrating an example split base station architecture in accordance with the present disclosure.

[0029] Figure 4Is a diagram illustrating an example associated with supporting multicast and broadcast services (MBS) in a standalone non-public network (SNPN) according to the present disclosure.

[0030] Figure 5 Is a diagram illustrating an example associated with supporting MBS in an SNPN according to the present disclosure.

[0031] Figure 6 Is a flowchart illustrating an example process of supporting MBS in an SNPN, for example, performed by a UE according to the present disclosure.

[0032] Figure 7 Is a flowchart illustrating an example process of supporting MBS in an SNPN, for example, performed by a network node according to the present disclosure.

[0033] Figure 8 Is a flowchart illustrating an example process of supporting MBS in an SNPN, for example, performed by a UE according to the present disclosure.

[0034] Figure 9 Is a flowchart illustrating an example process of supporting MBS in an SNPN, for example, performed by a network node according to the present disclosure.

[0035] Figure 10 Is a diagram of an example apparatus for wireless communication supporting MBS in an SNPN according to the present disclosure.

[0036] Figure 11 Is a diagram of an example apparatus for wireless communication supporting MBS in an SNPN according to the present disclosure. Detailed Description

[0037] Aspects of the present disclosure are described more fully hereinafter with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the present disclosure. For example, an apparatus may be implemented or a method may be practiced using any amount of the aspects set forth herein. Additionally, the scope of the present disclosure is intended to cover such apparatus or methods implemented using other structures, functionality, or a combination of structures and functionality in addition to or different from the aspects of the present disclosure set forth herein. Any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim.

[0038] Aspects of a telecommunications system will now be presented with reference to various apparatus and techniques. These apparatus and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the particular application and the design constraints imposed on the overall system.

[0039] Aspects generally relate to supporting multicast and broadcast services (MBS) in a standalone non-public network (SNPN). Some aspects more particularly relate to providing information associated with a network identifier (NID) of the SNPN in a temporary mobile group identifier (TMGI) to enable MBS in the SNPN. In some aspects, a network node may send a configuration of a TMGI indicating a MBS session identifier (ID) corresponding to a MBS session provided by the SNPN, and a user equipment (UE) may receive the configuration, where the TMGI includes a NID index value. Here, the UE may map the NID index value to the NID associated with the SNPN. The network node may send communications associated with the MBS session at least in part based on the NID, and the UE may receive the communications. Additionally or alternatively, the network node may assign a service ID to a MBS session provided by the SNPN, where the service ID is unique across a network set of a radio access network (RAN). Here, the network node may send a configuration of a TMGI indicating a MBS session identifier corresponding to the MBS session, and the UE may receive the configuration, where the TMGI includes the service ID. The network node may send communications associated with the MBS session at least in part based on the service ID, and the UE may receive the communications.

[0040] Specific aspects of the subject matter described in this disclosure may be implemented to realize one or more of the following potential advantages. In some examples, the described techniques may be used to enable supporting MBS in an SNPN, thereby providing the advantages of MBS for the SNPN (e.g., increased network efficiency or increased resource utilization efficiency). Additionally, the described techniques may enable supporting MBS in an SNPN without significantly increasing signaling overhead (e.g., compared to techniques that signal the full NID). Further, the described techniques may enable reliably supporting MBS in an SNPN in a RAN sharing scenario.

[0041] Figure 1FIG. is a diagram illustrating an example of a wireless network according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d), one UE 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The network node 110 is an entity that communicates with the UE 120. As shown, the network node 110 may include one or more network nodes. For example, the network node 110 may be an aggregated network node, which means that the aggregated network node is configured to utilize a radio protocol stack physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), which means that the network node 110 is configured to utilize a protocol stack physically or logically distributed between two or more nodes, such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs).

[0042] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, or one or more DUs. For example, the network node 110 may include an NR network node, an LTE network node, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, an RU, a CU, a mobility element of the network, a core network node, a network element, network equipment, or a RAN node. In some examples, the network nodes 110 may be interconnected with each other or with one or more other network nodes 110 in the wireless network 100 using any suitable transport network via various types of fronthaul interfaces, midhaul interfaces, or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.

[0043] Each network node 110 can provide communication coverage for a specific geographical area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" can refer to the coverage area of network node 110 or the network node subsystem serving that coverage area.

[0044] Network node 110 can provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell can cover a relatively large geographical area (e.g., with a radius of several kilometers) and can allow unrestricted access by a UE 120 with a service subscription. A pico cell can cover a relatively small geographical area and can allow unrestricted access by a UE 120 with a service subscription. A femto cell can cover a relatively small geographical area (e.g., a residence) and can allow restricted access by a UE 120 associated with that femto cell (e.g., a UE 120 in a Closed Subscriber Group (CSG)). The network node 110 for a macro cell can be referred to as a macro network node. The network node 110 for a pico cell can be referred to as a pico network node. The network node 110 for a femto cell can be referred to as a femto network node or a home network node.

[0045] The wireless network 100 can be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 can have different transmit power levels, different coverage areas, or different impacts on interference in the wireless network 100. For example, a macro network node can have a high transmit power level (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes can have lower transmit power levels (e.g., 0.1 watt to 2 watts). In Figure 1 the example shown, network node 110a can be a macro network node for macro cell 102a, network node 110b can be a pico network node for pico cell 102b, and network node 110c can be a femto network node for femto cell 102c. A network node can support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographical area of a cell can move according to the location of a moving network node 110 (e.g., a mobile network node).

[0046] In some aspects, the term "base station" or "network node" may refer to a centralized base station, a distributed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, the "base station" or "network node" may refer to a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a near real-time (near-RT) Radio Access Network (RAN) Intelligent Controller (RIC), or a non-real-time (non-RT) RIC. In some aspects, the term "base station" or "network node" may refer to a single device configured to perform one or more functions, such as those described herein in connection with network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located at the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeat at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function among base station functions, rather than another base station function. In this way, a single device may include more than one base station.

[0047] The network controller 130 may be coupled to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link. The network nodes 110 may also communicate directly with each other, or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or the network controller 130 may include a CU or a core network device.

[0048] In some examples, a cell may not necessarily be stationary, and the geographical area of the cell may move according to the location of a moving network node 110 (e.g., a mobile network node). In some examples, the network nodes 110 may be interconnected with each other or with one or more other network nodes 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network via various types of backhaul interfaces, such as a direct physical connection or a virtual network.

[0049] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive a data transmission from an upstream station (e.g., network node 110 or UE 120) and forward the data transmission to a downstream station (e.g., UE 120 or network node 110). A relay station can be a UE 120 that is capable of relaying transmissions for other UEs 120. In Figure 1 the example shown in, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. A network node 110 that relays communication may be referred to as a relay station, a relay network node, or a relay.

[0050] UEs 120 may be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. A UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. A UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, a superbook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, or any other suitable device configured to communicate via a wireless medium.

[0051] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. An MTC UE or an eMTC UE may include, for example, robots, drones, remote devices, sensors, meters, monitors, or location tags, which may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices, or may be implemented as narrowband IoT (NB-IoT) devices. Some UEs 120 may be considered customer premise equipment. A UE 120 may be included inside a housing that houses components of the UE 120, such as processor components or memory components. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0052] Generally, any amount of wireless network 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. The RAT can also be referred to as radio technology or air interface. The frequency can also be referred to as a carrier or frequency channel. Each frequency in a given geographical area can support a single RAT to avoid interference between wireless networks of different RATs. In some cases, an NR or 5G RAT network can be deployed.

[0053] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary for communicating with each other). For example, UE 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which can include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, or vehicle-to-pedestrian (V2P) protocol), or a mesh network. In such examples, UE 120 can perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by network node 110.

[0054] Devices of wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices of wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the “sub-6 GHz” band. Similar naming issues sometimes arise with respect to FR2, although different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunication Union (ITU) as the “millimeter wave” band, FR2 is generally (interchangeably) referred to as the “millimeter wave” band in various documents and articles.

[0055] The frequency between FR1 and FR2 is generally referred to as the mid-band frequency. Recent 5G NR studies have identified the operating bands for these mid-band frequencies as frequency range designations FR3 (7.125 GHz – 24.25 GHz). Bands falling within FR3 can inherit FR1 characteristics or FR2 characteristics, and thus the features of FR1 or FR2 can be effectively extended to the mid-band frequencies. Additionally, higher bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz – 71 GHz), FR4 (52.6 GHz – 114.25 GHz), and FR5 (114.25 GHz – 300 GHz). Each of these higher bands falls within the EHF band.

[0056] Considering the above examples, unless otherwise specifically stated, if the term "below 6 GHz" is used herein, it can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. Additionally, unless otherwise specifically stated, if the term "millimeter wave" is used herein, it can broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a, or FR4-1, or FR5, or can be within the EHF band. It is conceivable that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) can be modified, and the techniques described herein apply to those modified frequency ranges.

[0057] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, in some aspects, the communication manager 140 may receive a configuration indicating a TMGI corresponding to an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value; map the NID index value to an NID associated with the SNPN providing the MBS session; and receive communications associated with the MBS session at least in part based on the NID. Additionally or alternatively, as described in more detail elsewhere herein, the communication manager 140 may receive a configuration indicating a TMGI corresponding to an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including a service identifier that is unique across a RAN shared network set including one or more SNPNs or one or more PLMNs; and receive communications associated with the MBS session at least in part based on the service identifier being unique across the RAN shared network set. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0058] In some aspects, network node 110 may include a communication manager 150. As described in more detail elsewhere herein, in some aspects, communication manager 150 may send a configuration of a TMGI indicating an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value corresponding to an NID associated with the MBS session; and send communications associated with the MBS session for UE 120 to receive. Additionally or alternatively, as described in more detail elsewhere herein, communication manager 150 may assign a service identifier to an MBS session provided by an SNPN, the service identifier being unique across a RAN shared network set including one or more SNPNs or one or more PLMNs; send a configuration of a TMGI indicating the TMGI corresponding to the MBS session identifier associated with the MBS session, the TMGI including the service identifier; and send communications associated with the MBS session for UE 120 to receive. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0059] Figure 2 is a diagram illustrating example network node and UE communication in a wireless network according to the present disclosure. The network node may correspond to Figure 1 network node 110. Similarly, the UE may correspond to Figure 1 UE 120. Network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R≥1). Figure 2 The network node 110 depicted in includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, network node 110 may include an interface, a communication component, or another component that facilitates communication with UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with UE 120, such as one or more CUs or one or more DUs.

[0060] At network node 110, transmit processor 220 may receive data destined for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCSs) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or upper layer signaling) and may provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRSs) or demodulation reference signals (DMRSs)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on data symbols, control symbols, overhead symbols, or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 may process the corresponding output symbol stream (e.g., for OFDM) using the corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, or up-convert) the output sample stream using the corresponding modulator component to obtain a downlink signal. Modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0061] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 or other network nodes 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may condition (e.g., filter, amplify, down-convert, or digitize) the received signal using the corresponding demodulator component to obtain input samples. Each modem 254 may further process the input samples (e.g., for OFDM) using the demodulator component to obtain received symbols. The MIMO detector 256 may obtain the received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide the detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide the decoded data for the UE 120 to the data sink 260, and may provide the decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers or one or more processors. The 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, or a CQI parameter, etc. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0062] 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 network node 110 via the communication unit 294.

[0063] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or may be included within one or more of the following: one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. The antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled to one or more transmit or receive components (such as Figure 2 one or more components) of.

[0064] 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, or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. Symbols from the transmit processor 264 may be pre-coded by a TX MIMO processor 266, if applicable, further processed by a modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to a network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, an MIMO detector 256, a receive processor 258, a transmit processor 264, or a TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller / processor 280) and a memory 282 to perform aspects of any of the methods described herein.

[0065] At the network node 110, an uplink signal from the UE 120 or another UE may be received by an antenna 234, processed by a modem 232 (e.g., a demodulator component of the modem 232, shown as DEMOD), detected by an MIMO detector 236, if applicable, and further processed by a receive processor 238 to obtain decoded data and control information transmitted via the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with a network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of an antenna 234, a modem 232, an MIMO detector 236, a receive processor 238, a transmit processor 220, or a TX MIMO processor 230. The transceiver may be used by a processor (e.g., the controller / processor 240) and a memory 242 to perform aspects of any of the methods described herein.

[0066] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or Figure 2Any other component may perform one or more techniques associated with supporting MBS in an SNPN, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, or Figure 2 any other component may perform or direct, for example Figure 6 process 600 of Figure 7 process 700 of Figure 8 process 800 of Figure 9 process 900 of, or the operation of other processes as described herein. The memories 242 and 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, the memory 242 or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code or program code) for wireless communication. For example, when executed by one or more processors of network node 110 or UE 120 (e.g., executed directly, or after compilation, transformation, or interpretation), the one or more instructions may cause the one or more processors, UE 120, or network node 110 to perform or direct Figure 6 process 600 of Figure 7 process 700 of Figure 8 process 800 of Figure 9 process 900 of, or the operation of other processes as described herein. In some examples, executing the instructions may include running the instructions, transforming the instructions, compiling the instructions, or interpreting the instructions, and so on.

[0067] In some aspects, UE 120 includes means for receiving configuration of a TMGI indicating an MBS session identifier corresponding to an MBS session associated with an MBS session provided by an SNPN, the TMGI including an NID index value; means for mapping the NID index value to an NID associated with the SNPN providing the MBS session; or means for receiving communications associated with the MBS session at least in part based on the NID. In some aspects, the UE includes means for receiving configuration of a TMGI indicating an MBS session identifier corresponding to an MBS session associated with an MBS session provided by an SNPN, the TMGI including a service identifier that is unique across a RAN shared network set including one or more SNPNs or one or more PLMNs; or means for receiving communications associated with the MBS session at least in part based on the service identifier being unique across the RAN shared network set. The means for the UE to perform the operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TXMIMO processor 266, controller / processor 280, or memory 282.

[0068] In some aspects, network node 110 includes components for sending a configuration of a TMGI indicating an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value corresponding to an NID associated with the MBS session; or components for sending communications associated with the MBS session for UE 120 to receive. In some aspects, the network node includes components for assigning a service identifier to an MBS session provided by an SNPN, the service identifier being unique across a RAN shared network set including one or more SNPNs or one or more PLMNs; components for sending a configuration of a TMGI indicating the TMGI corresponding to an MBS session identifier associated with the MBS session, the TMGI including the service identifier; or components for sending communications associated with the MBS session for UE 120 to receive. Components for the network node to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0069] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as a stand-alone base station or monolithic base station) or a disaggregated base station. A "network entity" or "network node" can refer to a disaggregated base station or one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, or one or more RUs).

[0070] A centralized base station (e.g., a centralized network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A split base station (e.g., a split network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), etc.

[0071] Base station types of operations or network designs may consider the aggregation characteristics of base station functionality. For example, a split base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A split base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Each unit of a split base station may be configured for wired or wireless communication with at least one other unit of the split base station.

[0072] Figure 3 FIG. is an illustration of an example split base station architecture 300 in accordance with the present disclosure. The split base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more split control units (such as a near RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links such as through an F1 interface. Each DU among the DUs 330 may communicate with one or more RUs 340 via a respective fronthaul link. Each RU among the RUs 340 may communicate with one or more UEs 120 via a respective radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0073] Each unit in the unit (including CU 310, DU 330, RU 340) and the near RT RIC 325, non-RT RIC 315, and SMO framework 305 may include one or more interfaces or be coupled to the one or more interfaces, and the one or more interfaces are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each unit in the unit or the associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more units in other units via the transmission medium. In some examples, each unit in the unit may include a wired interface and a wireless interface. The wired interface is configured to receive signals or transmit signals to one or more units in other units via a wired transmission medium. The wireless interface may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), and the receiver, transmitter, or transceiver is configured to receive signals or transmit signals to one or more units in other units via a wireless transmission medium or perform both.

[0074] In some aspects, CU 310 may host one or more higher-layer control functions. Such control functions may include RRC functions, packet data convergence protocol (PDCP) functions, service data adaptation protocol (SDAP) functions, and so on. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user-plane functionality (e.g., central unit-user plane (CU-UP) functionality) or control-plane functionality (e.g., central unit-control plane (CU-CP) functionality). In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0075] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of the radio link control (RLC) layer, the media access control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to a functional split (such as the functional split defined by 3GPP). In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, which may be implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0076] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions, or low PHY layer functions (such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc.), based on a functional split (e.g., the lower layer functional split defined by 3GPP). In such an architecture, each RU 340 may be operated to handle over-the-air (OTA) communication with one or more UEs 120. In some embodiments, the real-time aspects and non-real-time aspects of communicating with the control plane and user plane of the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0077] The SMO framework 305 can be configured to support the RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and these dedicated physical resources can be managed via operation and maintenance interfaces (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 can communicate with the hardware aspect of the 4G RAN (such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 can directly communicate with each RU in one or more RUs 340 via the corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0078] The non-RT RIC 315 can be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, an artificial intelligence / machine learning (AI / ML) workflow including model training and update, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325 (such as via the A1 interface). The near-RT RIC 325 can be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources through interfaces (such as via the E2 interface) via data collection and actions, and this interface connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB to the near-RT RIC 325.

[0079] In some specific implementations, to generate the AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or from network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune the RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0080] A non-public network (NPN) is a network that enables the deployment of radio access technologies (such as 5G) for private use. The NPN can be deployed as a stand-alone NPN (SNPN) or a public network integrated NPN (PNI-NPN). An SNPN is an NPN that does not rely on network functions provided by a public land mobile network (PLMN). A PNI-NPN is an NPN that is deployed under the support of a PLMN. The SNPN identifier (ID) is defined by a combination of a PLMN identifier (PLMN ID) and a network identifier (NID). A UE supporting an SNPN can be configured with a subscriber ID and credentials for each subscription of the SNPN identified by a combination of the PLMN ID and the NID.

[0081] A multicast and broadcast service (MBS) session is a session that enables point-to-multipoint services, meaning that a single transmitter can broadcast or multicast the same content for multiple UEs to receive. A temporary mobile group identifier (TMGI) can be used to identify an MBS session. For example, the TMGI can be used in association with configuring a multicast radio bearer (MRB) associated with a multicast service. As another example, the TMGI can be used as the MBS session ID for a broadcast service. The TMGI is defined by a combination of a PLMN ID and a service ID. Traditionally, the TMGI is not defined to include the SNPN ID, so the TMGI does not provide any indication of the NID associated with the SNPN.

[0082] In some systems, UE-based techniques can be deployed to support MBS in an SNPN. For example, a network node can broadcast System Information Block 1 (SIB1) including one or more NIDs associated with one or more SNPNs. The network node can establish an F1 interface based on the NID information included in, for example, an MBS session ID defined in the NG Application Protocol (AP), Xn AP, F1 AP, or E1 AP. A UE registered to an SNPN knows the network it is registered to, and when the UE is registered to an SNPN, the UE may not be permitted to register to a non-NPN (e.g., a PLMN 5G core network). In addition, the UE knows the cell to which the UE is connected / camped. Therefore, the UE can determine the MBS Control Channel (MCCH) from the cell of the SNPN and determine the service ID (within the TMGI) to start receiving MBS services from the cell of the SNPN. It is worth noting that according to this UE-based technique, there is no need for the UE to access or otherwise determine the NID from the TMGI.

[0083] However, the above UE-based technique may not be sufficient to support RAN sharing. That is, the UE-based technique for supporting MBS in an SNPN may be insufficient in scenarios where the SNPN shares the RAN with one or more other networks, such as one or more other SNPNs or one or more PLMNs. In such a scenario, a cell can provide MBS services for the SNPN, but can also provide the same or different MBS services for one or more other SNPNs or one or more other PLMNs. However, in the RAN sharing scenario, the network can use the same TMGI for multiple SNPNs or PLMNs. Therefore, the UE may not be able to associate the TMGI with a specific SNPN or PLMN (when the same TMGI is used for multiple SNPNs or PLMNs).

[0084] One technique to solve this problem is to include a list of NIDs in the MBS broadcast configuration provided to the UE via RRC signaling, such that the complete NID corresponding to the MBS session ID is indicated in the MBS broadcast configuration. However, including a list of complete NIDs in the MBS broadcast configuration may significantly increase the signaling overhead (e.g., an NID can have a length of 44 bits, and up to 1024 MBS sessions can be configured).

[0085] Aspects described herein generally relate to supporting MBS in an SNPN. Some aspects more particularly relate to providing information associated with an NID of an SNPN in a TMGI to enable MBS in the SNPN. In some aspects, a network node may send a configuration of a TMGI indicating a TMGI corresponding to an MBS session ID associated with an MBS session provided by the SNPN, and a UE may receive the configuration, where the TMGI includes an NID index value. Here, the UE may map the NID index value to an NID associated with the SNPN. The network node may send a communication associated with the MBS session based at least in part on the NID associated with the NID index value, and the UE may receive the communication. Additionally or alternatively, the network node may assign a service ID to an MBS session provided by the SNPN, where the service identifier is unique across a set of RAN shared networks. Here, the network node may send a configuration of a TMGI indicating a TMGI corresponding to an MBS session identifier associated with the MBS session, and the UE may receive the configuration, where the TMGI includes the service ID. The network node may send a communication associated with the MBS session, and the UE may receive the communication.

[0086] Certain aspects of the subject matter described in this disclosure may be implemented to realize one or more of the following potential advantages. In some examples, the techniques described may be used to enable supporting MBS in an SNPN, thereby providing the advantages of MBS for the SNPN (e.g., increased network efficiency or increased resource utilization efficiency). Additionally, the techniques described may enable supporting MBS in an SNPN without significantly increasing signaling overhead (e.g., compared to the above techniques of signaling the full NID). Further, the techniques described may enable reliably supporting MBS in an SNPN in a RAN sharing scenario. Additional details are provided below.

[0087] Figure 4 is a diagram illustrating example 400 associated with supporting MBS in an SNPN according to the present disclosure. As Figure 4 shown, example 400 includes communication between network node 110 and UE 120. In some aspects, network node 110 and UE 120 may be included in a wireless network (such as wireless network 100). Network node 110 and UE 120 may communicate via a wireless access link (which may include an uplink and a downlink).

[0088] As Figure 4 shown, in a first operation 402, network node 110 may send a configuration of a TMGI indicating a TMGI corresponding to an MBS session ID associated with an MBS session provided by the SNPN, and UE 120 may receive the configuration, where the TMGI includes an NID index value.

[0089] In some aspects, the configuration includes a list of MBS session information that indicates one or more TMGIs associated with one or more corresponding MBS session identifiers, where each TMGI of the one or more TMGIs includes one or more NID index values. For example, the configuration may include a list of MBS session information (mbs-SessionInfoList-vRRxy) that indicates one or more MBS session IDs (mbs-sessionId-vRRxy), where each MBS session ID includes a TMGI (TMGI-vRRxy) and includes an NID index (nid-Index) or a plurality of NID indexes (nid-IndexList).

[0090] In some aspects, the list of MBS session information is a first list of MBS session information, and the configuration includes a second list of MBS session information. In some aspects, the second list of MBS session information indicates one or more TMGIs associated with one or more corresponding PLMN IDs and one or more service IDs. That is, in some aspects, the configuration includes another list of MBS session information (mbs-SessionInfoList-r17) that indicates one or more MBS session IDs (mbs-sessionId-r17), where each MBS session ID includes a TMGI (TMGI-r17) and includes a PLMN ID (plmn-ID-r17) and a service ID (serviceId-r17). In some aspects, the number and order of the MBS session identifiers included in the first list of MBS session information match the number and order of the MBS session identifiers included in the second list of MBS session information. That is, in some aspects, the number and order of the MBS session IDs in the first list of MBS session information (mbs-SessionInfoList-vRRxy) match the number and order of the MBS session IDs in the second list of MBS session information (mbs-SessionInfoList-r17).

[0091] In some aspects, the first list of MBS session information is separate from the second list of MBS session information. That is, in some aspects, within the configuration, the first list of MBS session information is provided in parallel with or separately from the second list of MBS session information.

[0092] Alternatively, in some aspects, the first MBS session information list is an extension of the second MBS session information list. That is, in some aspects, within this configuration, the first MBS session information list is an extension of or appended to the second MBS session information list. In some aspects, the first MBS session information list being an extension of the second MBS session information list solves the backward compatibility problem. For example, when interpreting a configuration that includes multiple MBS session information lists (which include the same TMGI), legacy UEs that are not configured for MBS in an SNPN may experience errors. Generating the configuration such that the first MBS session information list is an extension of the second MBS session information list solves this problem because the second MBS session information list would be invisible from the perspective of a legacy UE. As an alternative, any UE that supports MBS (including legacy UEs) may need to be configured to interpret multiple MBS session information lists. Alternatively, network node 110 may be configured to provide the first MBS session information list only in an RAN sharing scenario (such that legacy UEs can receive MBS via an SNPN without RAN sharing).

[0093] In a second operation 404, UE 120 may map the NID index value to the NID associated with the SNPN that provides the MBS session. That is, UE 120 may map the NID index value included in the TMGI to the NID of the SNPN.

[0094] In some aspects, UE 120 maps the NID index value to the NID by mapping the NID index value to the NID indicated in an NPN identity information list (npn-IdentityInfoList). In some aspects, the NPN identity information list includes one or more NIDs associated with one or more SNPNs. In some aspects, network node 110 may send the NPN identity information list in a system information block (SIB) (such as SIB1), and UE 120 may receive the NPN identity information list.

[0095] In some aspects, a given element in the NPN identity information list includes an NPN identity list (npn-IdentityList), where each element in the NPN identity list may be set to a PIN-NPN or an SNPN, and each SNPN may have one or more NIDs. An example of the NPN identity information list is as follows:

[0096]

[0097]

[0098] In this example, the NPN identification information list includes two NPN identification lists: npn-IdentityList[0] and npn-IdentityList[1]. npn-IdentityList[0] includes three NPN identifications: npn-Identity[0], npn-Identity[1], and npn-Identity[2]. Regarding npn-IdentityList[0], npn-Identity[0] is set as an SNPN and is associated with an NID list including two NIDs (NID_x and NID_y), npn-Identity[1] is set as a PNI-NPN, and npn-Identity[2] is set as an SNPN and is associated with an NID list including three NIDs (NID_a, NID_x, and NID_b). npn-IdentityList[1] includes two NPN identifications: npn-Identity[0] and npn-Identity[1]. Regarding npn-IdentityList[1], npn-Identity[0] is set as a PNI-NPN, and npn-Identity[1] is set as an SNPN and is associated with an NID list including one NID (NID_b).

[0099] In some aspects, the UE 120 maps the NID index value to the NID included in the NPN identity information list according to a mapping scheme. For example, the mapping scheme may indicate that the NID index value 1 indicates the first NID in the first NPN identity in the first NPN identity list included in the NPN identity information list received in SIB1. The mapping scheme may further indicate that the NID index value 2 indicates the second NID in the same NPN identity to which the value 1 is mapped, or if there is no additional NID in the same NPN identity, the value 2 indicates the NID listed first in the subsequent NPN identities within the same NPN identity list within the same SIB1, and so on. Applying this mapping scheme to the example NPN identity information list provided above, the UE 120 may map the NID index value 1 to the NID_x in npn-Identity[0] in npn-IdentityList[0], map the NID index value 2 to the NID_y in npn-Identity[0] in npn-IdentityList[0], map the NID index value 3 to the NID_a in npn-Identity[2] in npn-IdentityList[0], map the NID index value 4 to the NID_x in npn-Identity[2] in npn-IdentityList[0], map the NID index value 5 to the NID_b in npn-Identity[2] in npn-IdentityList[0], and map the NID index value 6 to the NID_b in npn-Identity[1] in npn-IdentityList[1].

[0100] In this way, the UE 120 can map the NID index value included in the TMGI to the NID at least partially based on the NPN identity information list received in the system information, thereby reducing the signaling overhead (compared to communicating the complete NID in the configuration provided to the UE 120).

[0101] In the third operation 406, the network node 110 may send the communication associated with the MBS session at least partially based on the NID, and the UE 120 may receive the communication. For example, after mapping the NID index value included in the TMGI to the NID associated with the SNPN providing the MBS session, the UE 120 may start receiving the MBS service via the MBS session at least partially based on the NID.

[0102] Figure 5 is a diagram illustrating an example 500 associated with supporting MBS in an SNPN according to the present disclosure. As Figure 5As shown, Example 500 includes communication between network node 110 and UE 120. In some aspects, network node 110 and UE 120 may be included in a wireless network (such as wireless network 100). Network node 110 and UE 120 may communicate via a wireless access link, which may include an uplink and a downlink).

[0103] As Figure 5 shown, in a first operation 502, network node 110 may assign a service ID to an MBS session provided by an SNPN. As Figure 5 indicated, in some aspects, network node 110 may assign a service ID such that the service ID is unique across a RAN shared network set that includes one or more SNPNs or one or more PLMNs.

[0104] In some aspects, network node 110 assigns the service ID at least in part based on communicating with one or more other network nodes 110 to ensure that the service ID is unique across the RAN shared network set. That is, in some aspects, network nodes 110 across the RAN shared network set may communicate with each other to ensure that the service ID assigned to the MBS session is unique across the RAN shared network set.

[0105] In some aspects, network node 110 assigns the service ID at least in part based on a specific set of bits from the NID associated with the SNPN providing the MBS session. That is, in some aspects, network node 110 may ensure that the service ID assigned to the MBS session is unique by using a specific set of bits from the NID value as part of the service ID. In some aspects, the specific set of bits may include one or more most significant bits (MSBs) of the NID or the NID value field of the NID. Additionally or alternatively, the specific set of bits may include one or more least significant bits (LSBs) of the NID or the NID value field of the NID.

[0106] For example, the NID may be defined by 44 bits, where 4 bits indicate the assignment mode and the remaining 40 bits indicate the NID value. Here, the network node 110 across the RAN shared network set may be configured to assign a 40-bit value in the NID value field of the NID such that the combination of a given NID and PLMN ID is globally unique. However, within a local area where the PLMN can be shared (e.g., within a country or region), fewer than 40 bits may be sufficient to uniquely identify the NID. Here, the MBS service ID included in the TMGI consists of three octets (six hexadecimal digits or 24 bits). In an example, if it is desired that the same TMGI is possible across different NIDs within the same SNPN rather than across different SNPNs and PLMNs, the MSB of the NID value can be used to distinguish the NID groups for each different SNPN or PLMN. As a specific example, if there are eight RAN shared networks, three MSBs in the NID value can be assigned such that the three MSBs uniquely identify each network, and the three MSBs of the NID value can be included in the service ID in the TMGI. This method ensures that the same TMGI will not be used across different SNPNs or PLMNs sharing the same RAN. Similarly, if 32 NID values are sufficient in a region and it is desired that the TMGI is unique across different NIDs (even within the same SNPN), five LSBs can be used to define the NID, and these five LSBs can be included in the service ID of the TMGI. This method ensures that the same TMGI will not be used across different NIDs. In this way, the coordination between the network nodes 110 of the RAN shared network can be utilized to ensure that the network nodes 110 assign unique service IDs to MBS sessions, thereby implementing MBS in the SNPN.

[0107] In a second operation 504, the network node 110 may send a configuration indicating the TMGI corresponding to the MBS session ID associated with the MBS session, and the UE 120 may receive the configuration, where the TMGI includes the service ID. That is, the network node 110 may send a configuration including the service ID that is unique across the RAN shared network set, and the UE 120 may receive the configuration.

[0108] In a third operation 506, the network node 110 may send communications associated with the MBS session, and the UE 120 may receive the communications. For example, the UE 120 may start receiving MBS services via the MBS session based at least in part on a unique service ID. In some aspects, the UE 120 may receive communications based at least in part on the service ID being unique across the RAN shared network set. That is, because the service ID is unique across the RAN shared network set, the TMGI is unique across the RAN shared network set. Accordingly, the same TMGI may not be used across the RAN shared network set, which enables the UE 120 to associate the TMGI with a particular SNPN or PLMN and thus start receiving MBS services via the MBS session based at least in part on the (unique) service ID.

[0109] Figure 6 FIG. is a flowchart illustrating an example process 600 for supporting MBS in an SNPN, such as performed by a UE in accordance with the present disclosure. The example process 600 is an example in which a UE (e.g., UE 120) performs operations associated with supporting MBS in an SNPN.

[0110] As Figure 6 shown, in some aspects, process 600 may include receiving a configuration indicating a TMGI corresponding to an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value (block 610). For example, the UE (such as by using the Figure 10 communication manager 140 or receiving component 1002 depicted in ) may receive a configuration indicating a TMGI corresponding to an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value, as described above.

[0111] As Figure 6 further shown, in some aspects, process 600 may include mapping the NID index value to an NID associated with the SNPN providing the MBS session (block 620). For example, the UE (such as by using the Figure 10 communication manager 140 or mapping component 1008 depicted in ) may map the NID index value to an NID associated with the SNPN providing the MBS session, as described above.

[0112] As Figure 6 further shown, in some aspects, process 600 may include receiving communications associated with the MBS session based at least in part on the NID (block 630). For example, the UE (such as by using the Figure 10 communication manager 140 and / or receiving component 1002 depicted in ) may receive communications associated with the MBS session based at least in part on the NID, as described above.

[0113] The process 600 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.

[0114] In a first additional aspect, the configuration includes a list of MBS session information that indicates one or more TMGIs associated with one or more corresponding MBS session identifiers, where each TMGI of the one or more TMGIs includes one or more NID index values.

[0115] In a second additional aspect, either alone or in combination with the first aspect, the list of MBS session information is a first list of MBS session information, and the configuration includes a second list of MBS session information that indicates one or more TMGIs associated with one or more corresponding PLMN identifiers and one or more service identifiers.

[0116] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, the number and order of MBS session identifiers included in the first list of MBS session information match the number and order of MBS session identifiers included in the second list of MBS session information.

[0117] In a fourth additional aspect, either alone or in combination with one or more of the first to third aspects, the first list of MBS session information is separate from the second list of MBS session information.

[0118] In a fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, the first list of MBS session information is an extension of the second list of MBS session information.

[0119] In a sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, mapping the NID index value to an NID includes mapping the NID index value to an NID indicated in a non-public network (NPN) identification information list that includes one or more NIDs associated with one or more SNPNs.

[0120] In a seventh additional aspect, either alone or in combination with one or more of the first to sixth aspects, the process 600 includes receiving the NPN identification information list in the SIB.

[0121] Although Figure 6 example boxes of the process 600 are shown, in some aspects, the process 600 may include Figure 6fewer boxes, different boxes, or boxes arranged in a different manner than the boxes depicted therein. Additionally or alternatively, two or more boxes of process 600 may be performed in parallel.

[0122] Figure 7 is a flowchart illustrating an example process 700 for supporting MBS in an SNPN, such as performed by a network node in accordance with the present disclosure. Example process 700 is an example in which a network node (e.g., network node 110) performs operations associated with supporting MBS in an SNPN.

[0123] As Figure 7 shown, in some aspects, process 700 may include transmitting a configuration of a TMGI indicating an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value corresponding to an NID associated with the MBS session (block 710). For example, a network node (such as by using Figure 11 the communication manager 150 or the transmitting component 1104 depicted therein) may transmit a configuration of a TMGI indicating an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value corresponding to an NID associated with the MBS session, as described above.

[0124] As Figure 7 further shown, in some aspects, process 700 may include transmitting communications associated with the MBS session for reception by a UE (block 720). For example, a network node (such as by using Figure 11 the communication manager 150 or the transmitting component 1104 depicted therein) may transmit communications associated with the MBS session for reception by a UE, as described above.

[0125] Process 700 may include additional aspects, such as any individual aspect or any combination of aspects described below or in combination with one or more other processes described elsewhere herein.

[0126] In a first additional aspect, the configuration includes an MBS session information list that indicates one or more TMGIs associated with one or more corresponding MBS session identifiers, wherein each TMGI of the one or more TMGIs includes one or more NID index values.

[0127] In a second additional aspect, separately or in combination with the first aspect, the MBS session information list is a first MBS session information list, and the configuration includes a second MBS session information list that indicates one or more TMGIs associated with one or more corresponding PLMN identifiers and one or more service identifiers.

[0128] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, the number and order of MBS session identifiers included in the first MBS session information list match the number and order of MBS session identifiers included in the second MBS session information list.

[0129] In a fourth additional aspect, either alone or in combination with one or more of the first to third aspects, the first MBS session information list is separate from the second MBS session information list.

[0130] In a fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, the first MBS session information list is an extension of the second MBS session information list.

[0131] In a sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, process 700 includes transmitting, in an SIB, a list of NPN identification information that includes one or more NIDs associated with one or more SNPNs.

[0132] Although Figure 7 example boxes of process 700 are shown, in some aspects, process 700 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner compared to the boxes depicted in Figure 7 . Additionally or alternatively, two or more boxes of process 700 may be executed in parallel.

[0133] Figure 8 is a flowchart illustrating an example process 800 for supporting MBS in an SNPN, for example, performed by a UE according to the present disclosure. Example process 800 is an example in which a UE (e.g., UE 120) performs operations associated with supporting MBS in an SNPN.

[0134] As Figure 8 shown, in some aspects, process 800 may include receiving a configuration of a TMGI indicating an MBS session identifier corresponding to an MBS session associated with an MBS session provided by an SNPN, the TMGI including a service identifier that is unique across a set of RAN shared networks including one or more SNPNs or one or more PLMNs (block 810). For example, a UE (such as by using Figure 10 the communication manager 140 or the receiving component 1002 depicted in

[0135] As Figure 8 Further shown, in some aspects, process 800 may include receiving communications associated with an MBS session (block 820) at least in part based on the service identifier being unique across a set of RAN shared networks. For example, a UE (such as by using the Figure 10 communication manager 140 and / or the receiving component 1002 depicted in) may receive communications associated with an MBS session at least in part based on the service identifier being unique across a set of RAN shared networks, as described above.

[0136] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below or in combination with one or more other processes described elsewhere herein.

[0137] In a first additional aspect, the service identifier includes a set of specific bits from the NID associated with the SNPN providing the MBS session.

[0138] In a second additional aspect, either alone or in combination with the first aspect, the set of specific bits includes one or more MSBs of the NID or the NID value field of the NID.

[0139] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, the set of specific bits includes one or more LSBs of the NID or the NID value field of the NID.

[0140] Although Figure 8 example blocks of process 800 are shown, in some aspects, process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner compared to the blocks depicted in Figure 8 . Additionally or alternatively, two or more blocks of process 800 may be executed in parallel.

[0141] Figure 9 is a flowchart illustrating an example process 900 for supporting MBS in an SNPN, performed by a network node, for example, in accordance with the present disclosure. Example process 900 is an example where a network node (e.g., network node 110) performs operations associated with supporting MBS in an SNPN.

[0142] As Figure 9 shown, in some aspects, process 900 may include assigning a service identifier to an MBS session provided by the SNPN, the service identifier being unique across a set of RAN shared networks including one or more SNPNs or one or more PLMNs (block 910). For example, a network node (such as by using Figure 11The communication manager 150 or the assignment component 1108 depicted in [above] may assign a service identifier to an MBS session provided by an SNPN, where the service identifier is unique across a set of RAN shared networks including one or more SNPNs or one or more PLMNs, as described above.

[0143] As Figure 9 Further shown, in some aspects, process 900 may include sending a configuration of a TMGI indicating an MBS session identifier corresponding to an MBS session, where the TMGI includes a service identifier (block 920). For example, a network node (such as by using Figure 11 the communication manager 150 or the sending component 1104 depicted in [above]) may send a configuration of a TMGI indicating an MBS session identifier corresponding to an MBS session, where the TMGI includes a service identifier, as described above.

[0144] As Figure 9 Further shown, in some aspects, process 900 may include sending communications associated with an MBS session for reception by a UE (block 930). For example, a network node (such as by using Figure 11 the communication manager 150 or the sending component 1104 depicted in [above]) may send communications associated with an MBS session for reception by a UE, as described above.

[0145] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below or in combination with one or more other processes described elsewhere herein.

[0146] In a first additional aspect, assigning a service identifier includes communicating with one or more other network nodes to ensure that the service identifier is unique across the set of RAN shared networks.

[0147] In a second additional aspect, either alone or in combination with the first aspect, assigning a service identifier includes assigning the service identifier at least in part based on a specific set of bits from the NID associated with the SNPN providing the MBS session.

[0148] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, the specific set of bits includes one or more MSBs of the NID or the NID value field of the NID.

[0149] In a fourth additional aspect, either alone or in combination with one or more of the first through third aspects, the specific set of bits includes one or more LSBs of the NID or the NID value field of the NID.

[0150] Although Figure 9 example blocks of process 900 are shown, in some aspects, process 900 may includeFigure 9 fewer boxes, different boxes, or boxes arranged in a different manner than the boxes depicted in []. Additionally or alternatively, two or more boxes of process 900 may be performed in parallel.

[0151] Figure 10 is a diagram of an example apparatus 1000 for wireless communication that supports MBS in an SNPN according to the present disclosure. Apparatus 1000 may be a UE, or a UE may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002, a transmitting component 1004, and a communication manager 140 that may communicate with each other (e.g., via one or more buses). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a network node, or another wireless communication device) using receiving component 1002 and transmitting component 1004.

[0152] In some aspects, apparatus 1000 may be configured to perform one or more operations described herein in connection with Figure 4 and Figure 5 . Additionally or alternatively, apparatus 1000 may be configured to perform one or more processes described herein, such as process 600 of Figure 6 or process 800 of Figure 8 . In some aspects, apparatus 1000 may include one or more components of the UE described above in connection with Figure 2 .

[0153] Receiving component 1002 may receive communications from apparatus 1006, such as reference signals, control information, or data communications. Receiving component 1002 may provide the received communications to one or more other components of apparatus 1000, such as communication manager 140. In some aspects, receiving component 1002 may perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components. In some aspects, receiving component 1002 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, or memories of the UE described above in connection with Figure 2 .

[0154] The transmitting component 1004 may send communications, such as reference signals, control information, or data communications, to the device 1006. In some aspects, the communication manager 140 may generate a communication and may send the generated communication to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communication and may send the processed signal to the device 1006. In some aspects, the transmitting component 1004 may include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, or memories of the UE described above in connection with Figure 2 the UE. In some aspects, the transmitting component 1004 may be co-located with the receiving component 1002 in a transceiver.

[0155] In some aspects, the communication manager 140 may receive or may cause the receiving component 1002 to receive a configuration indicating a TMGI corresponding to an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value. In some aspects, the communication manager 140 may map the NID index value to an NID associated with the SNPN providing the MBS session. In some aspects, the communication manager 140 may receive communications associated with the MBS session at least partially based on the NID, or may cause the receiving component 1002 to receive communications associated with the MBS session at least partially based on the NID.

[0156] In some aspects, the communication manager 140 may receive or may cause the receiving component 1002 to receive a configuration indicating a TMGI corresponding to an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including a service identifier that is unique across a RAN shared network set including one or more SNPNs or one or more PLMNs. In some aspects, the communication manager 140 may receive communications associated with the MBS session at least partially based on the service identifier being unique across the RAN shared network set, or may cause the receiving component 1002 to receive communications associated with the MBS session at least partially based on the service identifier being unique across the RAN shared network set. In some aspects, the communication manager 140 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 140.

[0157] The communication manager 140 may include those described above in connection with Figure 2The controller / processor or memory of the described UE. In some aspects, the communication manager 140 includes a set of components, such as the mapping component 1008. Alternatively, the set of components can be separate and distinct from the communication manager 140. In some aspects, one or more of the components in the set of components can include, or can be implemented within, the controller / processor or memory of the UE described above in connection with Figure 2 or can be implemented within the controller / processor or memory of the described UE, or can be implemented within it. Additionally or alternatively, one or more of the components in the set of components can be at least partially implemented as software stored in the memory. For example, a component (or a part of a component) can be implemented as instructions or code stored in a non-transitory computer-readable medium and capable of being executed by a controller or processor to perform the functions or operations of the component.

[0158] In some aspects, the receiving component 1002 can receive a configuration indicating a TMGI corresponding to an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value. In some aspects, the mapping component 1008 can map the NID index value to an NID associated with the SNPN providing the MBS session. In some aspects, the receiving component 1002 can receive communications associated with the MBS session at least partially based on the NID. In some aspects, the receiving component 1002 can receive a list of NPN identification information in the SIB.

[0159] In some aspects, the receiving component 1002 can receive a configuration indicating a TMGI corresponding to an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including a service identifier that is unique across a RAN shared network set including one or more SNPNs or one or more PLMNs. In some aspects, the receiving component 1002 can receive communications associated with the MBS session at least partially based on the service identifier being unique across the RAN shared network set.

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

[0161] Figure 11FIG. is a diagram of an example apparatus 1100 for wireless communication supporting MBS in an SNPN according to the present disclosure. The apparatus 1100 may be a network node, or a network node may include the apparatus 1100. In some aspects, the apparatus 1100 includes a receiving component 1102, a transmitting component 1104, and a communication manager 150 that may communicate with each other (e.g., via one or more buses). As shown, the apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a network node, or another wireless communication device) using the receiving component 1102 and the transmitting component 1104.

[0162] In some aspects, the apparatus 1100 may be configured to perform one or more operations described herein in connection with Figure 4 and Figure 5 Additional or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Figure 7 process 700 of Figure 9 process 900 of. In some aspects, the apparatus 1100 may include one or more components of the network node described above in connection with Figure 2

[0163] The receiving component 1102 may receive communications from the apparatus 1106, such as reference signals, control information, or data communications. The receiving component 1102 may provide the received communications to one or more other components of the apparatus 1100, such as the communication manager 150. In some aspects, the receiving component 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components. In some aspects, the receiving component 1102 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, or memories of the network node described above in connection with Figure 2

[0164] The transmitting component 1104 may transmit communications to the apparatus 1106, such as reference signals, control information, or data communications. In some aspects, the communication manager 150 may generate communications and may send the generated communications to the transmitting component 1104 for transmission to the apparatus 1106. In some aspects, the transmitting component 1104 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.), and may send the processed signals to the apparatus 1106. In some aspects, the transmitting component 1104 may include one or more of the above-described antennas, modems, demodulators, MIMO detectors, transmitting processors, controllers / processors, or memories of the network node in connection with Figure 2One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, or memories of the network node described. In some aspects, the transmit component 1104 may be co-located with the receive component 1102 in a transceiver.

[0165] In some aspects, the communication manager 150 may send or may cause the transmit component 1104 to send a configuration of a TMGI indicating an MBS session identifier associated with an MBS session provided by the SNPN, the TMGI including an NID index value corresponding to an NID associated with the MBS session. In some aspects, the communication manager 150 may send or may cause the transmit component 1104 to send communications associated with the MBS session for reception by the UE.

[0166] In some aspects, the communication manager 150 may assign a service identifier to an MBS session provided by the SNPN, the service identifier being unique across a shared network set of a RAN including one or more SNPNs or one or more PLMNs. In some aspects, the communication manager 150 may send or may cause the transmit component 1104 to send a configuration of a TMGI indicating an MBS session identifier corresponding to an MBS session, the TMGI including the service identifier. In some aspects, the communication manager 150 may send or may cause the transmit component 1104 to send communications associated with the MBS session for reception by the UE. In some aspects, the communication manager 150 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 150.

[0167] The communication manager 150 may include a controller / processor, a memory, a scheduler, or a communication unit of the network node described above in connection with Figure 2 In some aspects, the communication manager 150 includes a set of components, such as an assignment component 1108. Alternatively, the set of components may be separate and distinct from the communication manager 150. In some aspects, one or more components of the set of components may include a controller / processor, a memory, a scheduler, or a communication unit of the network node described above in connection with Figure 2 or may be implemented therein. Additionally or alternatively, one or more components of the set of components may be at least partially implemented 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 and executable by a controller or processor to perform the functions or operations of the component.

[0168] In some aspects, the sending component 1104 may send a configuration of a TMGI indicating an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value corresponding to an NID associated with the MBS session. In some aspects, the sending component 1104 may send communications associated with the MBS session for reception by a UE. In some aspects, the sending component 1104 may send a list of non-public network (NPN) identification information in a system information block (SIB), the list of NPN identification information including one or more NIDs associated with one or more SNPNs.

[0169] In some aspects, the assignment component 1108 may assign a service identifier to an MBS session provided by an SNPN, the service identifier being unique across a set of RAN shared networks including one or more SNPNs or one or more public land mobile networks (PLMNs). In some aspects, the sending component 1104 may send a configuration of a TMGI indicating a TMGI corresponding to an MBS session identifier associated with the MBS session, the TMGI including the service identifier. In some aspects, the sending component 1104 may send communications associated with the MBS session for reception by a UE.

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

[0171] An overview of some aspects of the present disclosure is provided below:

[0172] Aspect 1: A method of wireless communication performed by a UE, the method comprising: receiving a configuration of a TMGI indicating a TMGI corresponding to an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value; mapping the NID index value to an NID associated with the SNPN providing the MBS session; and receiving communications associated with the MBS session at least in part based on the NID.

[0173] Aspect 2: The method according to aspect 1, wherein the configuration includes a list of MBS session information, the list of MBS session information indicating one or more TMGIs associated with one or more corresponding MBS session identifiers, wherein each TMGI of the one or more TMGIs includes one or more NID index values.

[0174] Aspect 3: The method according to aspect 2, wherein the list of MBS session information is a first list of MBS session information, and the configuration includes a second list of MBS session information, the second list of MBS session information indicating one or more TMGIs associated with one or more corresponding PLMN identifiers and one or more service identifiers.

[0175] Aspect 4: The method according to aspect 3, wherein the number and order of MBS session identifiers included in the first list of MBS session information match the number and order of MBS session identifiers included in the second list of MBS session information.

[0176] Aspect 5: The method according to aspect 3, wherein the first list of MBS session information is separate from the second list of MBS session information.

[0177] Aspect 6: The method according to aspect 3, wherein the first list of MBS session information is an extension of the second list of MBS session information.

[0178] Aspect 7: The method according to any one of aspects 1 to 6, wherein mapping the NID index value to the NID includes mapping the NID index value to an NID indicated in a non-public network (NPN) identification information list, the NPN identification information list including one or more NIDs associated with one or more SNPNs.

[0179] Aspect 8: The method according to aspect 7, the method further comprising receiving the NPN identification information list in an SIB.

[0180] Aspect 9: A method of wireless communication performed by a network node, the method comprising: transmitting a configuration indicating a TMGI associated with an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including an NID index value corresponding to an NID associated with the MBS session; and transmitting communication associated with the MBS session for reception by a UE.

[0181] Aspect 10: The method according to aspect 9, wherein the configuration includes a list of MBS session information, the list of MBS session information indicating one or more TMGIs associated with one or more corresponding MBS session identifiers, wherein each TMGI of the one or more TMGIs includes one or more NID index values.

[0182] Aspect 11: The method according to aspect 10, wherein the list of MBS session information is a first list of MBS session information, and the configuration includes a second list of MBS session information, the second list of MBS session information indicating one or more TMGIs associated with one or more corresponding PLMN identifiers and one or more service identifiers.

[0183] Aspect 12: The method according to aspect 11, wherein the number and order of MBS session identifiers included in the first list of MBS session information match the number and order of MBS session identifiers included in the second list of MBS session information.

[0184] Aspect 13: The method according to aspect 11, wherein the first list of MBS session information is separate from the second list of MBS session information.

[0185] Aspect 14: The method according to aspect 11, wherein the first list of MBS session information is an extension of the second list of MBS session information.

[0186] Aspect 15: The method according to any one of aspects 9 to 14, the method further comprising sending, in the SIB, a list of non-public network (NPN) identification information, the list of NPN identification information including one or more NIDs associated with one or more SNPNs.

[0187] Aspect 16: A method of wireless communication performed by a UE, the method comprising: receiving a configuration indicating a TMGI corresponding to an MBS session identifier associated with an MBS session provided by an SNPN, the TMGI including a service identifier that is unique across a RAN shared network set including one or more SNPNs or one or more PLMNs; and receiving communications associated with the MBS session at least in part based on the service identifier being unique across the RAN shared network set.

[0188] Aspect 17: The method according to aspect 16, wherein the service identifier includes a specific set of bits from an NID associated with the SNPN providing the MBS session.

[0189] Aspect 18: The method according to aspect 17, wherein the set of specific bits includes one or more most significant bits (MSBs) of the NID or the NID value field of the NID.

[0190] Aspect 19: The method according to aspect 17, wherein the set of specific bits includes one or more least significant bits (LSBs) of the NID or the NID value field of the NID.

[0191] Aspect 20: A method of wireless communication performed by a network node, the method comprising: assigning a service identifier to an MBS session provided by an SNPN, the service identifier being unique across a RAN shared network set including one or more SNPNs or one or more public land mobile networks (PLMNs); transmitting a configuration of a traffic management and grooming identifier (TMGI) indicating an MBS session identifier associated with the MBS session, the TMGI including the service identifier; and transmitting communications associated with the MBS session for reception by a user equipment (UE).

[0192] Aspect 21: The method according to aspect 20, wherein assigning the service identifier includes communicating with one or more other network nodes to ensure that the service identifier is unique across the RAN shared network set.

[0193] Aspect 22: The method according to any one of aspects 20 to 21, wherein assigning the service identifier includes assigning the service identifier at least partially based on a set of specific bits of an NID associated with the SNPN providing the MBS session.

[0194] Aspect 23: The method according to aspect 22, wherein the set of specific bits includes one or more MSBs of the NID or the NID value field of the NID.

[0195] Aspect 24: The method according to aspect 22, wherein the set of specific bits includes one or more LSBs of the NID or the NID value field of the NID.

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

[0197] Aspect 26: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more of aspects 1 to 24.

[0198] Aspect 27: An apparatus for wireless communication, the apparatus including at least one component for performing the method according to one or more of Aspects 1 to 24.

[0199] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to one or more of Aspects 1 to 24.

[0200] Aspect 29: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set including one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of Aspects 1 to 24.

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

[0202] As used herein, the term "component" is intended to be broadly construed as hardware or a combination of hardware and software. "Software" should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, execution threads, processes, or functions, etc., regardless of whether it is referred to in terms of software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a "processor" is implemented with hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software. The actual specific control hardware or software code used to implement these systems or methods does not limit the aspects. Accordingly, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods at least in part based on the description herein.

[0203] As used herein, depending on the context, "meeting a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc.

[0204] Although a particular combination of features is recited in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of each aspect includes each dependent claim in combination with every other claim in the set of claims. As used herein, the phrase referring to a list of items “at least one of” refers to any combination of those items (which includes a single member). By way of example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiple identical elements (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0205] Any element, act, or instruction used herein should not be construed as critical or essential unless expressly so stated. Further, as used herein, the article “a” is intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more of the item(s) mentioned in connection with the article “the” and may be used interchangeably with “one or more.” Further, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” If only one item is intended, the phrase “only one” or similar language will be used. Also, as used herein, the terms “having,” “containing,” “including,” and similar terms are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “including” A may also contain B). Further, the phrase “based on” is intended to mean “at least partially based on” unless otherwise expressly stated. Further, as used herein, the term “or” when used in series is intended to be inclusive and may be used interchangeably with “and / or” unless otherwise expressly stated (e.g., if used in combination with “either of” or “only one of”).

Claims

1. A user equipment (UE) for wireless communication, the UE comprises: at least one memory; and at least one processor communicatively coupled to the at least one memory, the at least one processor operative to cause the UE to: receive a configuration indicating a temporary mobile group identifier (TMGI) corresponding to an MBS session identifier associated with a multicast and broadcast service (MBS) session provided by a standalone non - public network (SNPN), the TMGI including a network identifier (NID) index value; map the NID index value to an NID associated with the SNPN providing the MBS session; and receive communications associated with the MBS session at least in part based on the NID.

2. The UE according to claim 1, wherein the configuration includes an MBS session information list indicating one or more TMGIs associated with one or more corresponding MBS session identifiers, wherein each TMGI of the one or more TMGIs includes one or more NID index values.

3. The UE according to claim 2, wherein the MBS session information list is a first MBS session information list, and the configuration includes a second MBS session information list indicating one or more TMGIs associated with one or more corresponding public land mobile network (PLMN) identifiers and one or more service identifiers.

4. The UE according to claim 3, wherein the number and order of MBS session identifiers included in the first MBS session information list match the number and order of MBS session identifiers included in the second MBS session information list.

5. The UE according to claim 3, wherein the first MBS session information list is separate from the second MBS session information list.

6. The UE according to claim 3, wherein the first MBS session information list is an extension of the second MBS session information list.

7. The UE according to claim 1, wherein, to cause the UE to map the NID index value to the NID, the at least one processor is operative to cause the UE to map the NID index value to an NID indicated in a non - public network (NPN) identification information list including one or more NIDs associated with one or more SNPNs.

8. The UE according to claim 7, wherein the at least one processor is further operative to cause the UE to receive the NPN identification information list in a system information block (SIB).

9. A network node for wireless communication, the network node comprises: at least one memory; and at least one processor communicatively coupled to the at least one memory, the at least one processor operative to cause the network node to: Send a configuration of a Temporary Mobile Group Identifier (TMGI) indicating an MBS session identifier associated with a multicast and broadcast service (MBS) session provided by a Standalone Non-Public Network (SNPN), the TMGI including an NID index value corresponding to a Network Identifier (NID) associated with the MBS session; and Send communications associated with the MBS session for a User Equipment (UE) to receive.

10. The network node according to claim 9, wherein the configuration includes a list of MBS session information indicating one or more TMGIs associated with one or more corresponding MBS session identifiers, each of the one or more TMGIs including one or more NID index values.

11. The network node according to claim 10, wherein the list of MBS session information is a first list of MBS session information, and the configuration includes a second list of MBS session information indicating one or more TMGIs associated with one or more corresponding Public Land Mobile Network (PLMN) identifiers and one or more service identifiers.

12. The network node according to claim 11, wherein the number and order of MBS session identifiers included in the first list of MBS session information match the number and order of MBS session identifiers included in the second list of MBS session information.

13. The network node according to claim 11, wherein the first list of MBS session information is separate from the second list of MBS session information.

14. The network node according to claim 11, wherein the first list of MBS session information is an extension of the second list of MBS session information.

15. The network node according to claim 9, wherein the at least one processor is further operable to cause the network node to send, in a System Information Block (SIB), a list of Non-Public Network (NPN) identification information including one or more NIDs associated with one or more SNPNs.

16. A User Equipment (UE) for wireless communication, the UE comprising: at least one memory; and at least one processor communicatively coupled to the at least one memory, the at least one processor being operable to cause the UE to: Receive a configuration of a Temporary Mobile Group Identifier (TMGI) indicating an MBS session identifier corresponding to a multicast and broadcast service (MBS) session provided by a Standalone Non-Public Network (SNPN), the TMGI including a service identifier that is unique across a network set shared by a Radio Access Network (RAN) including one or more SNPNs or one or more Public Land Mobile Networks (PLMNs); and Receive communications associated with the MBS session at least in part based on the service identifier being unique across the RAN shared network set.

17. The UE according to claim 16, wherein the service identifier comprises a set of specific bits from a network identifier (NID) associated with the SNPN providing the MBS session.

18. The UE according to claim 17, wherein the set of specific bits comprises one or more most significant bits (MSBs) of the NID or the NID value field of the NID.

19. The UE according to claim 17, wherein the set of specific bits comprises one or more least significant bits (LSBs) of the NID or the NID value field of the NID.

20. A network node for wireless communication, the network node comprising: at least one memory; and at least one processor communicatively coupled to the at least one memory, the at least one processor operable to cause the network node to: assign a service identifier to a multicast and broadcast service (MBS) session provided by a stand-alone non-public network (SNPN), the service identifier being unique across a radio access network (RAN) shared network set comprising one or more SNPNs or one or more public land mobile networks (PLMNs); send a configuration indicating a temporary mobile group identifier (TMGI) corresponding to an MBS session identifier associated with the MBS session, the TMGI comprising the service identifier; and send communications associated with the MBS session for reception by a user equipment (UE).

21. The network node according to claim 20, wherein, to cause the network node to assign the service identifier, the at least one processor is operable to cause the network node to communicate with one or more other network nodes to ensure that the service identifier is unique across the RAN shared network set.

22. The network node according to claim 20, wherein, to cause the network node to assign the service identifier, the at least one processor is operable to cause the network node to assign the service identifier based at least in part on a set of specific bits from a network identifier (NID) associated with the SNPN providing the MBS session.

23. The network node according to claim 22, wherein the set of specific bits comprises one or more most significant bits (MSBs) of the NID or the NID value field of the NID.

24. The network node according to claim 22, wherein the set of specific bits comprises one or more least significant bits (LSBs) of the NID or the NID value field of the NID.

25. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a configuration indicating a temporary mobile group identifier (TMGI) corresponding to an MBS session identifier associated with a multicast and broadcast service (MBS) session provided by a stand-alone non-public network (SNPN), the TMGI comprising a network identifier (NID) index value; Map the NID index value to an NID associated with the SNPN that provides the MBS session; and Receive communications associated with the MBS session, at least in part based on the NID.

26. The method according to claim 25, wherein the configuration includes a list of MBS session information, the list of MBS session information indicating one or more TMGIs associated with one or more corresponding MBS session identifiers, wherein each TMGI of the one or more TMGIs includes one or more NID index values.

27. The method according to claim 26, wherein the list of MBS session information is a first list of MBS session information, and the configuration includes a second list of MBS session information, the second list of MBS session information indicating one or more TMGIs associated with one or more corresponding public land mobile network (PLMN) identifiers and one or more service identifiers.

28. The method according to claim 27, wherein the number and order of MBS session identifiers included in the first list of MBS session information match the number and order of MBS session identifiers included in the second list of MBS session information.

29. The method according to claim 27, wherein the first list of MBS session information is separate from the second list of MBS session information.

30. The method according to claim 27, wherein the first list of MBS session information is an extension of the second list of MBS session information.

31. The method according to claim 25, wherein mapping the NID index value to the NID includes mapping the NID index value to an NID indicated in a non-public network (NPN) identification information list, the NPN identification information list including one or more NIDs associated with one or more SNPNs.

32. The method according to claim 31, the method further comprising receiving the NPN identification information list in a system information block (SIB).

33. A method of wireless communication performed by a network node, the method comprising: Sending a configuration of a temporary mobile group identifier (TMGI) indicating an MBS session identifier associated with a multicast and broadcast service (MBS) session provided by a stand-alone non-public network (SNPN), the TMGI including an NID index value corresponding to a network identifier (NID) associated with the MBS session; and Sending communications associated with the MBS session for reception by a user equipment (UE).

34. The method according to claim 33, wherein the configuration includes a list of MBS session information, the list of MBS session information indicating one or more TMGIs associated with one or more corresponding MBS session identifiers, wherein each TMGI of the one or more TMGIs includes one or more NID index values.

35. The method according to claim 34, wherein the MBS session information list is a first MBS session information list, and the configuration includes a second MBS session information list, the second MBS session information list indicating one or more TMGIs associated with one or more corresponding public land mobile network (PLMN) identifiers and one or more service identifiers.

36. The method according to claim 35, wherein the number and order of MBS session identifiers included in the first MBS session information list match the number and order of MBS session identifiers included in the second MBS session information list.

37. The method according to claim 35, wherein the first MBS session information list is separate from the second MBS session information list.

38. The method according to claim 35, wherein the first MBS session information list is an extension of the second MBS session information list.

39. The method according to claim 33, the method further comprising sending, in a system information block (SIB), a non-public network (NPN) identification information list, the NPN identification information list including one or more NIDs associated with one or more SNPNs.

40. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a configuration indicating a temporary mobile group identifier (TMGI) corresponding to an MBS session identifier associated with a multicast and broadcast service (MBS) session provided by a standalone non-public network (SNPN), the TMGI including a service identifier that is unique across a network set shared by a radio access network (RAN) including one or more SNPNs or one or more public land mobile networks (PLMNs); and receiving communications associated with the MBS session at least in part based on the service identifier being unique across the RAN shared network set.

41. The method according to claim 40, wherein the service identifier includes a specific set of bits from a network identifier (NID) associated with the SNPN providing the MBS session.

42. The method according to claim 41, wherein the specific set of bits includes one or more most significant bits (MSBs) of the NID or the NID value field of the NID.

43. The method according to claim 41, wherein the specific set of bits includes one or more least significant bits (LSBs) of the NID or the NID value field of the NID.

44. A method of wireless communication performed by a network node, the method comprising: assigning a service identifier to a multicast and broadcast service (MBS) session provided by a standalone non-public network (SNPN), the service identifier being unique across a network set shared by a radio access network (RAN) including one or more SNPNs or one or more public land mobile networks (PLMNs); Configuring to send a Temporary Mobile Group Identifier (TMGI) indicating an MBS session identifier associated with the MBS session, the TMGI including the service identifier; and Sending communications associated with the MBS session for reception by a User Equipment (UE).

45. The method according to claim 44, wherein assigning the service identifier includes communicating with one or more other network nodes to ensure that the service identifier is unique across the set of RAN shared networks.

46. The method according to claim 44, wherein assigning the service identifier includes assigning the service identifier at least in part based on a set of specific bits from a Network Identifier (NID) associated with the SNPN providing the MBS session.

47. The method according to claim 46, wherein the set of specific bits includes one or more Most Significant Bits (MSBs) of the NID or the NID value field of the NID.

48. The method according to claim 46, wherein the set of specific bits includes one or more Least Significant Bits (LSBs) of the NID or the NID value field of the NID.

49. 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 User Equipment (UE), cause the UE to: Receive configuration of a Temporary Mobile Group Identifier (TMGI) indicating an MBS session identifier associated with a Multicast and Broadcast Service (MBS) session provided by a Standalone Non-Public Network (SNPN), the TMGI including a Network Identifier (NID) index value; Map the NID index value to an NID associated with the SNPN providing the MBS session; and Receive communications associated with the MBS session at least in part based on the NID.

50. The non-transitory computer-readable medium according to claim 49, wherein the configuration includes an MBS session information list indicating one or more TMGIs associated with one or more corresponding MBS session identifiers, wherein each TMGI of the one or more TMGIs includes one or more NID index values.

51. The non-transitory computer-readable medium according to claim 50, wherein the MBS session information list is a first MBS session information list, and the configuration includes a second MBS session information list indicating one or more TMGIs associated with one or more corresponding Public Land Mobile Network (PLMN) identifiers and one or more service identifiers.

52. The non-transitory computer-readable medium according to claim 51, wherein the number and order of MBS session identifiers included in the first MBS session information list match the number and order of MBS session identifiers included in the second MBS session information list.

53. The non-transitory computer-readable medium according to claim 51, wherein the first MBS session information list is separate from the second MBS session information list.

54. The non-transitory computer-readable medium according to claim 51, wherein the first MBS session information list is an extension of the second MBS session information list.

55. The non-transitory computer-readable medium according to claim 49, wherein the one or more instructions that cause the UE to map the NID index value to the NID cause the UE to map the NID index value to an NID indicated in a non-public network (NPN) identification information list, the NPN identification information list including one or more NIDs associated with one or more SNPNs.

56. The non-transitory computer-readable medium according to claim 55, wherein the one or more instructions further cause the UE to receive the NPN identification information list in a system information block (SIB).

57. 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 network node, cause the network node to: send a configuration of a temporary mobile group identifier (TMGI) indicating an MBS session identifier associated with a multicast and broadcast service (MBS) session provided by a stand-alone non-public network (SNPN), the TMGI including an NID index value corresponding to a network identifier (NID) associated with the MBS session; and send communications associated with the MBS session for reception by a user equipment (UE).

58. The non-transitory computer-readable medium according to claim 57, wherein the configuration includes an MBS session information list that indicates one or more TMGIs associated with one or more corresponding MBS session identifiers, wherein each TMGI of the one or more TMGIs includes one or more NID index values.

59. The non-transitory computer-readable medium according to claim 58, wherein the MBS session information list is a first MBS session information list, and the configuration includes a second MBS session information list that indicates one or more TMGIs associated with one or more corresponding public land mobile network (PLMN) identifiers and one or more service identifiers.

60. The non-transitory computer-readable medium according to claim 59, wherein the number and order of MBS session identifiers included in the first MBS session information list match the number and order of MBS session identifiers included in the second MBS session information list.

61. The non-transitory computer-readable medium according to claim 59, wherein the first MBS session information list is separate from the second MBS session information list.

62. The non-transitory computer-readable medium according to claim 59, wherein the first MBS session information list is an extension of the second MBS session information list.

63. The non-transitory computer-readable medium according to claim 57, wherein the one or more instructions further cause the network node to send a non-public network (NPN) identifier information list in a system information block (SIB), the NPN identifier information list including one or more NIDs associated with one or more SNPNs.

64. A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive a configuration of a temporary mobile group identifier (TMGI) indicating an MBS session identifier corresponding to a multicast and broadcast service (MBS) session provided by a stand-alone non-public network (SNPN), the TMGI including a service identifier that is unique across a radio access network (RAN) shared network set including one or more SNPNs or one or more public land mobile networks (PLMNs); and receive communications associated with the MBS session at least in part based on the service identifier being unique across the RAN shared network set.

65. The non-transitory computer-readable medium according to claim 64, wherein the service identifier includes a specific set of bits from a network identifier (NID) associated with the SNPN providing the MBS session.

66. The non-transitory computer-readable medium according to claim 65, wherein the specific set of bits includes one or more most significant bits (MSBs) of the NID or the NID value field of the NID.

67. The non-transitory computer-readable medium according to claim 65, wherein the specific set of bits includes one or more least significant bits (LSBs) of the NID or the NID value field of the NID.

68. A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: one or more instructions that, when executed by one or more processors of a network node, cause the network node to: assign a service identifier to a multicast and broadcast service (MBS) session provided by a stand-alone non-public network (SNPN), the service identifier being unique across a radio access network (RAN) shared network set including one or more SNPNs or one or more public land mobile networks (PLMNs); send a configuration of a temporary mobile group identifier (TMGI) indicating an MBS session identifier corresponding to the MBS session, the TMGI including the service identifier; and send communications associated with the MBS session for reception by a user equipment (UE).

69. The non-transitory computer-readable medium according to claim 68, wherein the one or more instructions that cause the network node to assign the service identifier cause the network node to communicate with one or more other network nodes to ensure that the service identifier is unique across the RAN shared network set.

70. The non-transitory computer-readable medium according to claim 68, wherein the one or more instructions that cause the network node to assign the service identifier cause the network node to assign the service identifier at least in part based on a set of specific bits from a network identifier (NID) associated with the SNPN providing the MBS session.

71. The non-transitory computer-readable medium according to claim 70, wherein the set of specific bits includes one or more most significant bits (MSBs) of the NID or the NID value field of the NID.

72. The non-transitory computer-readable medium according to claim 70, wherein the set of specific bits includes one or more least significant bits (LSBs) of the NID or the NID value field of the NID.

73. An apparatus for wireless communication, the apparatus comprising: means for receiving a configuration indicating a temporary mobile group identifier (TMGI) corresponding to an MBS session identifier associated with a multicast and broadcast service (MBS) session provided by a stand-alone non-public network (SNPN), the TMGI including a network identifier (NID) index value; means for mapping the NID index value to an NID associated with the SNPN providing the MBS session; and means for receiving communications associated with the MBS session at least in part based on the NID.

74. The apparatus according to claim 73, wherein the configuration includes an MBS session information list indicating one or more TMGIs associated with one or more corresponding MBS session identifiers, wherein each TMGI of the one or more TMGIs includes one or more NID index values.

75. The apparatus according to claim 74, wherein the MBS session information list is a first MBS session information list, and the configuration includes a second MBS session information list indicating one or more TMGIs associated with one or more corresponding public land mobile network (PLMN) identifiers and one or more service identifiers.

76. The apparatus according to claim 75, wherein the number and order of MBS session identifiers included in the first MBS session information list match the number and order of MBS session identifiers included in the second MBS session information list.

77. The apparatus according to claim 75, wherein the first MBS session information list is separate from the second MBS session information list.

78. The apparatus according to claim 75, wherein the first MBS session information list is an extension of the second MBS session information list.

79. The apparatus according to claim 73, wherein the component for mapping the NID index value to the NID includes a component for mapping the NID index value to an NID indicated in a non-public network (NPN) identification information list, the NPN identification information list including one or more NIDs associated with one or more SNPNs.

80. The apparatus according to claim 79, the apparatus further including a component for receiving the NPN identification information list in a system information block (SIB).

81. An apparatus for wireless communication, the apparatus comprising: a component for transmitting a configuration of a temporary mobile group identifier (TMGI) indicating a multicast and broadcast service (MBS) session identifier associated with an MBS session provided by a standalone non-public network (SNPN), the TMGI including an NID index value corresponding to a network identifier (NID) associated with the MBS session; and a component for transmitting communications associated with the MBS session for reception by a user equipment (UE).

82. The apparatus according to claim 81, wherein the configuration includes an MBS session information list indicating one or more TMGIs associated with one or more corresponding MBS session identifiers, wherein each TMGI of the one or more TMGIs includes one or more NID index values.

83. The apparatus according to claim 82, wherein the MBS session information list is a first MBS session information list, and the configuration includes a second MBS session information list indicating one or more TMGIs associated with one or more corresponding public land mobile network (PLMN) identifiers and one or more service identifiers.

84. The apparatus according to claim 83, wherein the number and order of MBS session identifiers included in the first MBS session information list match the number and order of MBS session identifiers included in the second MBS session information list.

85. The apparatus according to claim 83, wherein the first MBS session information list is separate from the second MBS session information list.

86. The apparatus according to claim 83, wherein the first MBS session information list is an extension of the second MBS session information list.

87. The apparatus according to claim 81, the apparatus further including a component for transmitting a non-public network (NPN) identification information list in a system information block (SIB), the NPN identification information list including one or more NIDs associated with one or more SNPNs.

88. An apparatus for wireless communication, the apparatus comprising: A component for receiving a configuration of a Temporary Mobile Group Identifier (TMGI) indicating an MBS session identifier corresponding to an MBS session associated with a multicast and broadcast service (MBS) provided by a Standalone Non-Public Network (SNPN), the TMGI including a service identifier that is unique across a shared network set of a Radio Access Network (RAN) including one or more SNPNs or one or more Public Land Mobile Networks (PLMNs); and A component for receiving communications associated with the MBS session at least in part based on the service identifier being unique across the shared network set of the RAN.

89. The apparatus according to claim 88, wherein the service identifier includes a specific bit set from a Network Identifier (NID) associated with the SNPN providing the MBS session.

90. The apparatus according to claim 89, wherein the specific bit set includes one or more Most Significant Bits (MSBs) of the NID or an NID value field of the NID.

91. The apparatus according to claim 89, wherein the specific bit set includes one or more Least Significant Bits (LSBs) of the NID or an NID value field of the NID.

92. An apparatus for wireless communication, the apparatus comprising: A component for assigning a service identifier to a multicast and broadcast service (MBS) session provided by a Standalone Non-Public Network (SNPN), the service identifier being unique across a shared network set of a Radio Access Network (RAN) including one or more SNPNs or one or more Public Land Mobile Networks (PLMNs); A component for transmitting a configuration of a Temporary Mobile Group Identifier (TMGI) indicating an MBS session identifier corresponding to the MBS session, the TMGI including the service identifier; and A component for transmitting communications associated with the MBS session for reception by a User Equipment (UE).

93. The apparatus according to claim 92, wherein the component for assigning the service identifier includes a component for communicating with one or more other network nodes to ensure that the service identifier is unique across the shared network set of the RAN.

94. The apparatus according to claim 92, wherein the component for assigning the service identifier includes a component for assigning the service identifier at least in part based on a specific bit set from a Network Identifier (NID) associated with the SNPN providing the MBS session.

95. The apparatus according to claim 94, wherein the specific bit set includes one or more Most Significant Bits (MSBs) of the NID or an NID value field of the NID.

96. The apparatus according to claim 94, wherein the specific bit set includes one or more Least Significant Bits (LSBs) of the NID or an NID value field of the NID.

97. A method, apparatus, device, computer program product, non-transitory computer-readable medium, user equipment, base station, network node, wireless communication device, or processing system as substantially described herein with reference to the accompanying drawings and specification and as illustrated by the accompanying drawings and specification.

Images