Multicast and Broadcast Services in Shared Radio Access Network Deployments

Abstract

The present disclosure relates to techniques for providing multicast and broadcast services in a wireless communication system with wireless access network sharing. A cellular base station associated with a plurality of public land mobile networks may receive multicast and broadcast service session setup information for a multicast and broadcast service session. The cellular base station may determine that the session is associated with a plurality of public land mobile networks. The cellular base station may configure a multicast and broadcast service session associated with the plurality of public land mobile networks.

Description

[Technical Field]

[0001] The present application relates to wireless communications, and more particularly to systems, apparatus, and methods for providing multicast and broadcast services in wireless communication systems with wireless access network sharing. [Background technology]

[0002] The use of wireless communication systems is rapidly increasing. In recent years, wireless devices such as smartphones and tablet computers have become increasingly sophisticated. Many mobile devices (i.e., user equipment devices, or UEs) now not only support telephony, but also provide access to the Internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of running sophisticated applications that utilize these capabilities. In addition, many different wireless communication technologies and standards exist. Some examples of wireless communication standards include GSM, UMTS (e.g., associated with a WCDMA or TD-SCDMA air interface), LTE, LTE Advanced (LTE-A), NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), BLUETOOTH™, and the like.

[0003] The ever-increasing number of features and functionality being introduced into wireless communication devices also creates a continuing need to improve both wireless communication and wireless communication devices. In particular, it is important to ensure the accuracy of transmitted and received signals via user equipment (UE) devices, e.g., wireless devices such as cellular telephones, base stations, and relay stations used in wireless cellular communications. In addition, increasing the functionality of UE devices can place a significant strain on the battery life of the UE devices. Therefore, it is also very important to reduce the power requirements of UE device designs while enabling the UE devices to maintain good transmission and reception capabilities for improved communications. Therefore, improvements in this area are desirable. Summary of the Invention

[0004] SUMMARY OF THE INVENTION Embodiments of an apparatus, system, and method for providing multicast and broadcast services in a wireless communication system with radio access network sharing are presented herein.

[0005] The techniques described herein may support the provision of multicast and broadcast service sessions associated with multiple cellular networks by a cellular base station in a radio access network sharing deployment. Such provision may be more efficient than separate provision of multicast and broadcast service sessions for the same service to different cellular networks associated with the cellular base station, for example, because at least some duplication of content and signaling may be avoided in this manner.

[0006] Providing multicast and broadcast service sessions associated with multiple cellular networks may be achieved at least in part by providing a mechanism for identifying that multiple cellular networks wish to perform session setup for the same multicast or broadcast service, which may then enable a cellular base station to configure one session for the multicast or broadcast service instead of separately configuring sessions for the multicast or broadcast service for each cellular network that wishes to perform session setup for the multicast or broadcast service.

[0007] Several such possible mechanisms are described herein, including techniques for establishing a shared / unified temporary mobile group identifier framework across multiple network operators, as well as various techniques for allowing multiple temporary mobile group identifiers to be associated with one multicast and broadcast service session.

[0008] It should be noted that the techniques described herein may be implemented in and / or used in conjunction with many different types of devices, including, but not limited to, base stations, access points, cellular telephones, portable media players, tablet computers, wearable devices, unmanned aerial vehicles, unmanned aerial controllers, automobiles and / or motor vehicles, cellular core network infrastructure devices, and various other computing devices.

[0009] This Summary is intended to provide a brief overview of some of the subject matter described in this document. Accordingly, it should be understood that the above features are merely examples and should not be construed as narrowing the scope or spirit of the subject matter described herein. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following Detailed Description, the drawings, and the claims. [Brief explanation of the drawings]

[0010] A better understanding of the present subject matter may be obtained from the following detailed description of various embodiments when considered in conjunction with the following drawings.

[0011] [Figure 1] FIG. 1 illustrates an exemplary (and simplified) wireless communication system according to some embodiments.

[0012] [Figure 2] FIG. 1 illustrates an exemplary base station in communication with an exemplary wireless user equipment (UE) device, according to some embodiments.

[0013] [Figure 3] 1 is an example block diagram of a UE, in accordance with some embodiments.

[0014] [Figure 4] 1 is an exemplary block diagram of a base station, according to some embodiments.

[0015] [Figure 5] FIG. 1 is an exemplary block diagram of a cellular network element, according to some embodiments.

[0016] [Figure 6] 1 is a flow chart diagram illustrating aspects of an exemplary possible method for providing multicast and broadcast services in a wireless communication system with radio access network sharing, according to some embodiments.

[0017] [Figure 7] 1 illustrates aspects of a possible RAN sharing scenario in which the same multicast / broadcast service is provided by multiple operators, according to some embodiments.

[0018] [Figure 8]1A-1C illustrate exemplary aspects of possible TMGI structures, according to some embodiments.

[0019] [Figure 9] 1 illustrates aspects of possible scenarios in which a shared / unified TMGI is used across different PLMNs, according to some embodiments.

[0020] [Figure 10] 10 is a signal flow diagram illustrating exemplary network communication aspects of the scenario of FIG. 9, according to some embodiments.

[0021] [Figure 11] FIG. 10 illustrates aspects of another possible scenario in which a shared / unified TMGI is used across different PLMNs, according to some embodiments.

[0022] [Figure 12] 12 is a signal flow diagram illustrating exemplary network communication aspects of the scenario of FIG. 11, according to some embodiments.

[0023] [Figure 13] 1 is a signal flow diagram illustrating network communication aspects of an example scenario in which multiple TMGIs may be associated with one MBS service / session, according to some embodiments.

[0024] [Figure 14] FIG. 10 is a signal flow diagram illustrating further details of an example scenario in which the MBS Service ID field in the TMGI may be unified across shared operators / PLMNs, according to some embodiments.

[0025] [Figure 15] FIG. 10 is a signal flow diagram illustrating further details of an example scenario in which associations between multiple TMGIs may be configured for a gNB that is part of a RAN sharing deployment via OAM or other means, according to some embodiments.

[0026] [Figure 16] A signal flow diagram showing further details of an example scenario in which a new global MBS service ID may be introduced to associate multiple TMGIs with the same MBS service, according to some embodiments.

[0027] [Figure 17] 1 is a signal flow diagram illustrating further details of an exemplary scenario in which a particular carrier may be configured to provide one MBS service, according to some embodiments.

[0028] [Figure 18] 10 is a signal flow diagram illustrating further details of possible UE behavior in a scenario where multiple TMGIs may be associated with one MBS multicast service / session, according to some embodiments.

[0029] While the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description are not intended to limit the invention to the particular forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present subject matter as defined by the appended claims. DETAILED DESCRIPTION OF THE INVENTION

[0030] acronym Various acronyms are used throughout this disclosure. Definitions of the most prominently used acronyms that may appear throughout this disclosure are provided below. UE: User Equipment RF: Radio Frequency · BS: Base station GSM: Global System for Mobile Communications · UMTS: Universal Mobile Telecommunications System LTE: Long Term Evolution · NR: New Radio TX: Send / Transmit RX: Receive / Receive RAT: Radio Access Technology RAN: Radio Access Network TRP: Transmit / Receive Point PLMN: Public Land Mobile Network MBS: Multicast and Broadcast Service TMGI: Temporary Mobile Group Identifier term Below is a description of terms that may appear in this disclosure.

[0031] Memory medium—any of various types of non-transitory memory or storage devices. The term “storage medium” is intended to include, for example, installation media such as CD-ROMs, floppy disks, or tape drives; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM; non-volatile memory such as magnetic media such as flash, hard drives, or optical storage; registers, or other similar types of memory elements. A storage medium may also include other types of non-transitory memory, or a combination thereof. Additionally, a memory medium may be located in a first computer system on which a program is executed, or in a second, different computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system can provide the first computer system with program instructions for execution. The term “storage medium” may include two or more storage media that can reside in different locations, for example, in different computer systems connected via a network. A storage medium may store program instructions (e.g., embodied as a computer program) that can be executed by one or more processors.

[0032] Carrier Medium - Memory media as described above, as well as physical transmission media such as buses, networks, and / or other physical transmission media that carry signals, such as electrical, electromagnetic, or digital signals.

[0033] Computer system (or computer) - any of various types of computing or processing systems, including a personal computer system (PC), a mainframe computer system, a workstation, a network device, an Internet appliance, a personal digital assistant (PDA), a television system, a grid computing system, or any other device or combination of devices. In general, the term "computer system" may be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0034] User Equipment (UE) (or "UE device") - Any of various types of computer systems or devices that are mobile or portable and perform wireless communications. Examples of UE devices include mobile phones or smartphones (e.g., iPhone™, Android™-based phones), tablet computers (e.g., iPad™, Samsung Galaxy™), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), wearable devices (e.g., smart watches, smart glasses), laptops, PDAs, portable Internet devices, music players, data storage devices, other handheld devices, automobiles and / or motor vehicles, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. In general, the term "UE" or "UE device" may be broadly defined to encompass any electronic, computing, and / or telecommunications device (or combination of devices) that is easily carried by a user and capable of wireless communications.

[0035] Wireless Device—Any of various types of computer systems or devices that perform wireless communications. A wireless device can be portable (or mobile) or may be stationary or fixed to a location. A UE is an example of a wireless device.

[0036] Communications Device - Any of various types of computer systems or devices that perform communications, which may be wired or wireless. A communications device may be portable (or mobile), or may be stationary or fixed to a particular location. A wireless device is one example of a communications device. A UE is another example of a communications device.

[0037] Base Station (BS) - The term "base station" has all of its ordinary meanings and includes at least a wireless communication station that is installed at a fixed location and used for communication as part of a wireless telephone system or wireless system.

[0038] Processing Element (or Processor)—refers to various elements or combinations of elements capable of performing functions within a device, e.g., within a user equipment device or within a cellular network device. A processing element may include, for example, a processor and associated memory, a portion or circuitry of an individual processor core, an entire processor core, a processor array, a circuit such as an Application Specific Integrated Circuit (ASIC), a programmable hardware element such as a Field Programmable Gate Array (FPGA), and various combinations of the above.

[0039] Wi-Fi - The term "Wi-Fi" has the full scope of its ordinary meaning and includes at least a wireless communication network or RAT that is served by wireless LAN (WLAN) access points and provides connectivity to the Internet through those access points. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name "Wi-Fi." Wi-Fi (WLAN) networks are distinct from cellular networks.

[0040] Automatically—refers to an action or operation being performed by a computer system (e.g., software executed by a computer system) or device (e.g., circuitry, programmable hardware element, ASIC, etc.) without user input directly specifying or executing the action or operation. Thus, the term “automatically” is in contrast to an operation that is manually performed or specified by a user, in which the user provides input to directly perform the operation. An automatic procedure may be initiated by input provided by a user, but subsequent actions performed “automatically” are not specified by the user; that is, they are not performed “manually,” with the user specifying each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting checkboxes, selecting radio selections, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user actions. A form may also be filled out automatically by a computer system, in which the computer system (e.g., software executed by the computer system) analyzes the form's fields and fills out the form without user input specifying answers to the fields. As noted above, a user can invoke automatic form filling but is not involved in the actual filling of the form (e.g., the user does not manually specify answers in fields, but rather the answers are completed automatically). This specification provides various examples of actions that are automatically performed in response to actions taken by a user.

[0041] Configured to—Various components may be described as being “configured to” perform a task. In this context, “configured to” is a broad description that generally means “having a structure” to perform a task or tasks during operation. Thus, a component may be configured to perform a task even when the component is not currently performing the task (e.g., a set of conductors may be configured to electrically connect a module to another module even when the two modules are not connected). In some contexts, “configured to” may be a broad description of a structure that generally means “having circuitry” to perform a task or tasks during operation. Thus, a component may be configured to perform a task even when the component is not currently on. Generally, the circuitry forming the structure corresponding to “configured to” may include hardware circuitry.

[0042] In the description herein, for convenience, various components may be described as performing a task or tasks. Such descriptions should be construed to include the phrase "configured to." It is expressly intended that a description of a component as being configured to perform one or more tasks does not apply to the interpretation of that component under 35 U.S.C. § 112, sixth paragraph. Figures 1 and 2 - Exemplary Communication System

[0043] 1 illustrates an exemplary (and simplified) wireless communication system in which aspects of the present disclosure may be implemented, according to some embodiments. It should be noted that the system of FIG. 1 is merely one example of a possible system, and that embodiments may be implemented in a variety of systems, as desired.

[0044] As shown, the exemplary wireless communication system includes a base station 102 that communicates with one or more (e.g., any number) user devices 106A, 106B, etc. through 106N over a transmission medium. Each of the user devices may be referred to herein as a "user equipment" (UE) or a UE device. Accordingly, the user devices 106 are referred to as UEs or UE devices.

[0045] The base station 102 may be a base transceiver station (BTS) or cell site and may include hardware and / or software that enables wireless communication with the UEs 106A-106N. If the base station 102 is implemented in the context of LTE, it may alternatively be referred to as an "eNodeB" or "eNB." If the base station 102 is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB." The base station 102 may also be equipped to communicate with the network 100 (e.g., a cellular service provider's core network, a telecommunications network such as the Public Switched Telephone Network (PSTN), and / or the Internet, among other possibilities). Thus, the base station 102 may facilitate communications between user devices and / or between the user devices and the network 100. The communication area (or coverage area) of a base station may be referred to as a "cell." Also, as used herein, from the perspective of a UE, the base station may be considered to represent the network as far as the UE's uplink and downlink communications are concerned. Thus, a UE that communicates with one or more base stations in a network may be interpreted as a UE that communicates with the network.

[0046] The base stations 102 and user devices may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), also referred to as wireless communication technologies, or telecommunications standards, such as GSM, UMTS (WCDMA), LTE, LTE-Advanced (LTE-A), LAA / LTE-U, 5G NR, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, etc.

[0047] Thus, base station 102 and similar other base stations operating according to the same or different cellular communication standards may be provided as one or more networks of cells that may provide continuous or near-continuous overlapping service to UE 106 and similar devices over a geographic area via one or more cellular communication standards.

[0048] It should be noted that the UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using either or both of the 3GPP or 3GPP2 cellular communication standards. In some embodiments, the UE 106 may be configured to perform techniques for receiving multicast and broadcast services in a wireless communication system with radio access network sharing in accordance with various methods described herein. The UE 106 may also or alternatively be configured to communicate using WLAN, BLUETOOTH™, one or more Global Navigation Satellite Systems (GNSS, e.g., GPS or GLONASS), one and / or more mobile television broadcast standards (e.g., ATSC-M / H), etc. Other combinations of wireless communication standards (including three or more wireless communication standards) are also possible.

[0049] FIG. 2 illustrates an exemplary user equipment 106 (e.g., one of devices 106A-106N) in communication with a base station 102, according to some embodiments. The UE 106 may be a device with wireless network connectivity, such as a mobile phone, a handheld device, a wearable device, a computer or tablet, an unmanned aerial vehicle (UAV), an unmanned aircraft controller (UAC), or virtually any type of wireless device. The UE 106 may include a processor (processing element) configured to execute program instructions stored in a memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or additionally, the UE 106 may include a programmable hardware element, such as a field programmable gate array (FPGA), an integrated circuit, and / or any of various other possible hardware components configured to perform any of the method embodiments described herein, or any portion of any of the method embodiment embodiments described herein (e.g., individually or in combination). The UE 106 may be configured to communicate using any of a number of wireless communication protocols. For example, the UE 106 may be configured to communicate using two or more of CDMA2000, LTE, LTE-A, 5G NR, WLAN, or GNSS. Other combinations of wireless communication standards are possible.

[0050] The UE 106 may include one or more antennas for communicating using one or more wireless communication protocols according to one or more RAT standards. In some embodiments, the UE 106 may share one or more portions of a receive chain and / or transmit chain between multiple wireless communication standards. A shared radio may include a single antenna or may include multiple antennas (e.g., in the case of multiple-input multiple-power, or "MIMO") to perform wireless communication. In general, a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, a radio may implement one or more receive and transmit chains using the above hardware. For example, the UE 106 may share one or more portions of a receive and / or transmit chain between multiple wireless communication technologies, such as those described above.

[0051] In some embodiments, the UE 106 may include any number of antennas and may be configured to transmit and / or receive directional wireless signals (e.g., beams) using the antennas. Similarly, the BS 102 may include any number of antennas and may be configured to transmit and / or receive directional wireless signals (e.g., beams) using the antennas. To receive and / or transmit such directional signals, the antennas of the UE 106 and / or the BS 102 may be configured to apply different "weights" to different antennas. The process of applying these different weights may be referred to as "precoding."

[0052] In some embodiments, the UE 106 may include a separate transmit and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol over which the UE 106 is configured to communicate. As a further possibility, the UE 106 may include one or more radios shared among multiple wireless communication protocols and one or more radios used exclusively by a single wireless communication protocol. For example, the UE 106 may include a shared radio for communicating using either LTE or CDMA2000 1xRTT (or LTE or NR or LTE or GSM) and a separate radio for communicating using each of Wi-Fi and BLUETOOTH™. Other configurations are possible. Figure 3 - Block diagram of an exemplary UE device

[0053] FIG. 3 illustrates a block diagram of an exemplary UE 106, according to some embodiments. As illustrated, the UE 106 may include a system-on-chip (SOC) 300, which may include portions for various purposes. For example, as shown, the SOC 300 may include a processor(s) 302, which may execute program instructions for the UE 106, and a display circuit 304, which may perform graphics processing and provide display signals to a display 360. The SOC 300 may also include a sensor circuit 370, which may include components for sensing or measuring any of a variety of possible characteristics or parameters of the UE 106. For example, the sensor circuit 370 may include a motion sensing circuit configured to detect movement of the UE 106, e.g., using a gyroscope, an accelerometer, and / or any of a variety of other motion sensing components. As another possibility, the sensor circuit 370 may include one or more temperature sensing components, e.g., for measuring the temperature of one or more antenna panels and / or each of the other components of the UE 106. Any of a variety of other possible types of sensor circuitry may additionally or alternatively be included in the UE 106, as desired. The processor(s) 302 may be coupled to a memory management unit (MMU) 340, which receives addresses from the processor(s) 302 and translates those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310), and / or the processor(s) 302 may be configured to couple to other circuits or devices, such as a display circuit 304, a radio 330, a connector I / F 320, and / or a display 360. The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor(s) 302.

[0054] As shown, the SOC 300 may be coupled to various other circuits of the UE 106. For example, the UE 106 may include various types of memory (including, e.g., NAND flash 310), a connector interface 320 (e.g., for coupling to a computer system, dock, charging station, etc.), a display 360, and wireless communication circuitry 330 (e.g., for LTE, LTE-A, NR, CDMA2000, BLUETOOTH™, Wi-Fi, GPS, etc.). The UE device 106 may include or be coupled to at least one antenna (e.g., 335a), and possibly multiple antennas (e.g., as illustrated by antennas 335a and 335b), for performing wireless communication with base stations and / or other devices. Antennas 335a and 335b are shown by way of example, and the UE device 106 may include fewer or more antennas. Generally, the one or more antennas are collectively referred to as antenna 335. For example, the UE device 106 may use an antenna 335 to perform wireless communications using radio circuitry 330. The communications circuitry may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration. As mentioned above, in some embodiments, the UE may be configured to communicate wirelessly using multiple wireless communications standards.

[0055] The UE 106 may include hardware and software components for executing methods by which the UE 106 performs techniques for receiving multicast and broadcast services in a wireless communication system with radio access network sharing, as described further hereinafter. The processor(s) 302 of the UE device 106 may be configured to perform some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). In other embodiments, the processor(s) 302 may be configured as a programmable hardware element, such as a field programmable gate array (FPGA), or as an application-specific integrated circuit (ASIC). Furthermore, the processor(s) 302 may be coupled to and / or interoperate with other components, as shown in FIG. 3, to perform techniques for receiving multicast and broadcast services in a wireless communication system with radio access network sharing according to various embodiments disclosed herein. The processor(s) 302 may also execute various other applications and / or end-user applications running on the UE 106.

[0056] In some embodiments, the radio 330 may include separate controllers dedicated to controlling communications for each of the various RAT standards. For example, as shown in FIG. 3 , the radio 330 may include a Wi-Fi controller 352, a cellular controller (e.g., an LTE and / or LTE-A controller) 354, and a BLUETOOTH™ controller 356, where, in at least some embodiments, one or more or all of these controllers may be implemented as respective integrated circuits (ICs or chips, for short) that communicate with each other and with the SOC 300 (more specifically, with the processor(s) 302). For example, the Wi-Fi controller 352 may communicate with the cellular controller 354 via a cellular-ISM link or WCI interface, and / or the BLUETOOTH™ controller 356 may communicate with the cellular controller 354 via a cellular-ISM link, etc. Although three separate controllers are shown within the radio 330, other embodiments have fewer or more similar controllers for the various different RATs that may be implemented in the UE device 106.

[0057] Further, embodiments are contemplated in which the controller is capable of performing functions related to multiple radio access technologies. For example, according to some embodiments, the cellular controller 354 may include hardware and / or software components for performing one or more Wi-Fi related activities, such as Wi-Fi preamble detection and / or Wi-Fi physical layer preamble signal generation and transmission, in addition to hardware and / or software components for performing cellular communications. Figure 4 - Exemplary base station block diagram

[0058] 4 illustrates a block diagram of an exemplary base station 102, according to some embodiments. Note that the base station of FIG. 4 is merely one example of a possible base station. As shown, the base station 102 may include a processor(s) 404 capable of executing program instructions for the base station 102. The processor(s) 404 may also be coupled to a memory management unit (MMU) 440, which may be configured to receive addresses from the processor(s) 404 and translate those addresses to locations in memory (e.g., memory 460 and read-only memory (ROM) 450) or other circuits or devices.

[0059] The base station 102 may include at least one network port 470. The network port 470 may be configured to couple to a telephone network and provide multiple devices, such as the UE device 106, with access to the telephone network as described above in FIGS. 1 and 2. The network port 470 (or additional network ports) may also, or alternatively, be configured to couple to a cellular network, e.g., a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as the UE device 106. In some cases, the network port 470 may be coupled to the telephone network via the core network, and / or the core network may provide the telephone network (e.g., to and from other UE devices serviced by the cellular service provider).

[0060] In some embodiments, the base station 102 may be a next-generation base station, e.g., a 5G New Radio (5G NR) base station, or "gNB." In such embodiments, the base station 102 may be connected to a conventional evolved packet core (EPC) network and / or an NR core (NRC) network. In addition, the base station 102 may be considered a 5G NR cell and may include one or more transmit and receive points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs in one or more gNBs.

[0061] The base station 102 may include at least one antenna 434, and possibly multiple antennas. The antenna(s) 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with the UE device 106 via a radio 430. The antenna(s) 434 communicate with the radio 430 via a communication chain 432. The communication chain 432 may be a receive chain, a transmit chain, or both. The radio 430 may be designed to communicate via various wireless communication standards, including, but not limited to, 5G NR, 5G NR SAT, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0062] The base station 102 can be configured to communicate wirelessly using multiple wireless communication standards. In some cases, the base station 102 can include multiple radios, which can enable the base station 102 to communicate according to multiple wireless communication technologies. For example, in one possibility, the base station 102 can include an LTE radio for performing communications according to LTE and a 5G NR radio for performing communications according to 5G NR. In such a case, the base station 102 may be capable of operating as both an LTE base station and a 5G NR base station. In another possibility, the base station 102 can include a multimode radio, which can perform communications according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, 5G NR SAT and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0063] As described further herein below, the BS 102 may include hardware and software components for implementing or supporting the implementation of the features described herein. The processor 404 of the base station 102 may be configured to perform and / or support the execution of some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element, such as a field programmable gate array (FPGA), or as an application-specific integrated circuit (ASIC), or a combination thereof. For a given RAT, e.g., Wi-Fi, the base station 102 may be designed as an access point (AP), in which case the network port 470 may be implemented to provide access to a wide area network and / or local area network(s) and may include, for example, at least one Ethernet port, and the radio 430 may be designed to communicate according to the Wi-Fi standard.

[0064] Additionally, as described herein, the processor(s) 404 may include one or more processing elements. Accordingly, the processor(s) 404 may include one or more integrated circuits (ICs) configured to perform the functions of the processor(s) 404. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the processor(s) 404.

[0065] Further, as described herein, radio 430 may include one or more processing elements. Thus, radio 430 may include one or more integrated circuits (ICs) configured to perform the functions of radio 430. In addition, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio 430. Figure 5 - Example block diagram of a network element

[0066] Figure 5 illustrates an exemplary block diagram of a network element 500, according to some embodiments. According to some embodiments, the network element 500 may implement one or more logical functions / entities of a cellular core network, such as a mobility management entity (MME), a serving gateway (S-GW), an access and management function (AMF), a session management function (SMF), etc. It should be noted that the network element 500 of Figure 5 is merely one example of a possible network element 500. As shown, the core network element 500 may include a processor(s) 504, which may execute program instructions for the core network element 500. The processor(s) 504 may also be coupled to a memory management unit (MMU) 540, which may be configured to receive addresses from the processor(s) 504 and translate those addresses to locations in memory (e.g., memory 560 and read-only memory (ROM) 550) or other circuits or devices.

[0067] Network element 500 may include at least one network port 570. Network port 570 may be configured to couple to one or more base stations and / or other cellular network entities and / or devices. Network element 500 may communicate with base stations (e.g., eNB / gNB) and / or other network entities / devices using any of a variety of communication protocols and / or interfaces.

[0068] As described further herein, the network element 500 may include hardware and software components for performing and / or supporting the execution of the functions described herein. The processor(s) 504 of the core network element 500 may be configured to perform or support the execution of some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 504 may be configured as a programmable hardware element, such as a field programmable gate array (FPGA), or as an application specific integrated circuit (ASIC), or as a combination thereof. Figure 6 - Multicast and broadcast services in a shared radio access network deployment

[0069] Network sharing may include the practice of sharing network equipment among multiple network operators. Network sharing may be implemented at the Radio Access Network (RAN) level, including, for example, deploying one or more cellular base stations capable of providing services associated with any of multiple Public Land Mobile Networks (PLMNs) to wireless devices, as at least one possible aspect of a network sharing deployment. In at least some examples, such deployment may have the potential to reduce network capital expenditures by network operators, provide services to wireless devices more efficiently, and / or provide other benefits.

[0070] To realize such possibilities, it may be beneficial to introduce new techniques and / or features to support enhanced network resource utilization efficiency in conjunction with such network sharing deployments. For example, it may be possible to introduce techniques for providing multicast and broadcast services in wireless communication systems with RAN sharing that may provide such improved efficiency. Figure 6 is a flowchart diagram illustrating aspects of such a method, according to at least some embodiments.

[0071] 6 may be performed, as desired, by one or more wireless devices and / or other cellular network elements, such as, for example, the UE 106, the BS 102, and the cellular network elements 500 shown and described with respect to the various figures herein, or more generally, by a cellular base station in conjunction with any of the computer circuits, systems, devices, elements, or components shown in the figures above, among others. For example, the processor (and / or other hardware) of such a device may be configured to cause the device to perform any combination of the method elements shown in the figures and / or other method elements.

[0072] It should be noted that, although at least some elements of the method of FIG. 6 are described as relating to the use of communication techniques and / or features associated with 3GPP and / or NR standard documents, such description is not intended to limit the present disclosure, and aspects of the method of FIG. 6 may be used in any suitable wireless communication system, as desired. In various embodiments, some of the method elements shown in the figures may be performed simultaneously, may be performed in a different order than shown in the figures, may be replaced by other method elements, or may be omitted, as desired. Additional method elements may be performed, as shown. As shown, the method of FIG. 6 may operate as follows.

[0073] At 602, the wireless device may establish a wireless link with a cellular base station. According to some embodiments, the wireless link may include a 5G NR cellular link. For example, the wireless device may establish a session with an AMF entity of the cellular network via one or more gNBs that provide wireless access to the cellular network. As another possibility, the wireless link may include an LTE cellular link. For example, the wireless device may establish a session with a mobility management entity of the cellular network via an eNB that provides wireless access to the cellular network. Other types of cellular links are possible, and the cellular network may additionally or alternatively operate according to another cellular communication technology (e.g., UMTS, CDMA2000, GSM, etc.) according to various embodiments.

[0074] In some embodiments, a cellular base station may be part of a shared radio access network (RAN) deployment and may be associated with multiple public land mobile networks (PLMNs), e.g., including at least a first PLMN and a second PLMN. In such a scenario, the cellular base station may be able to provide home PLMN (HPLMN) service to wireless devices associated with either the first PLMN or the second PLMN. In other words, the cellular base station may be able to provide service to (at least) a first wireless device associated with a first PLMN and (at least) a second wireless device associated with a second PLMN without either the first wireless device or the second wireless device having to roam to access the service. It should be noted that, at least in some examples, it may also be possible for a cellular base station to be associated with more than two PLMNs.

[0075] Establishing the radio link may include, according to at least some embodiments, establishing an RRC connection with a serving cellular base station. Establishing a first RRC connection may include configuring various parameters for communication between the wireless device and the cellular base station, establishing context information for the wireless device, and / or any of various other possible features related to, for example, establishing an air interface for the wireless device to perform cellular communication with a cellular network associated with the cellular base station. After establishing the RRC connection, the wireless device may operate in an RRC connected state. In some instances, the RRC connection may also be released (e.g., after a certain inactivity period with respect to data communication), in which case the wireless device may operate in an RRC idle state or an RRC inactive state. In some instances, the wireless device may perform a handover (e.g., while in an RRC connected mode) or perform cell reselection to a new serving cell (e.g., in an RRC idle or RRC inactive mode) due to wireless device mobility and / or any of various other possible reasons that change wireless medium conditions.

[0076] In at least some instances, establishing a wireless link(s) may include the wireless device providing wireless device capability information. Such capability information may include information related to any of various types of wireless device capabilities.

[0077] At 604, a cellular base station may receive MBS session setup information for a multicast and broadcast service (MBS) session. The cellular base station may determine that the MBS session is associated with multiple PLMNs. The association of the MBS session with multiple PLMNs may be identified in any of a variety of ways.

[0078] In some embodiments, association of an MBS session with multiple PLMNs may be identified based at least in part on the cellular base station receiving MBS session setup information for the MBS session from each of the multiple PLMNs. For example, the cellular base station may receive MBS session setup information for the MBS session from a network entity (e.g., an AMF and / or a Multicast Broadcast Session Management Function (MB-SMF)) associated with a first PLMN and may receive MBS session setup information for the MBS session from a network entity (e.g., an AMF and / or MB-SMF) associated with a second PLMN. In such a scenario, the MBS session setup information may include information that can be used by the cellular base station (e.g., by itself or in conjunction with other information available to the cellular base station) to determine that multiple PLMNs have requested that the same MBS service be provided in the MBS session.

[0079] As one such possibility, some or all of the networks with a RAN sharing deployment may cooperate to pre-configure cellular base stations with information indicating that particular Temporary Mobile Group Identifiers (TMGIs) are associated. For example, the cellular base station may receive an indication, e.g., by operation, administration, and maintenance (OAM) configuration, that particular TMGIs are associated (e.g., they are used by different PLMNs to refer to the same MBS service). Thus, the cellular base station may receive an indication that a first TMGI and a second TMGI are associated. In such a scenario, MBS session setup information received from a network entity associated with the first PLMN may indicate the first TMGI for the MBS session, and MBS session setup information received from a network entity associated with the second PLMN may indicate the second TMGI for the MBS session. Based on the indicated TMGIs for the MBS session and the pre-configured association between the TMGIs, the cellular base station may be able to identify that both PLMNs are configuring the same MBS service and, therefore, associate the MBS session with both the first PLMN and the second PLMN.

[0080] As another such possibility, some or all of the networks with RAN sharing deployments may coordinate to unify their use of the MBS service identification (ID) field of their TMGIs across multiple PLMNs. For example, in such a scenario, MBS session setup information received from a network entity associated with a first PLMN may indicate a first TMGI for the MBS session, and MBS session setup information received from a network entity associated with a second PLMN may indicate a second TMGI for the MBS session, and the MBS service ID fields for the first TMGI and the second TMGI may be identical. Based on the TMGI indicated for the MBS session including the same MBS service ID field, the cellular base station can identify that both PLMNs have configured the same MBS service and can therefore associate the MBS session for that MBS service with both the first PLMN and the second PLMN.

[0081] As a further possibility, some or all of networks with RAN sharing deployments may be able to coordinate to use a separate, unified MBS service identification framework, even if the MBS service ID fields of their TMGIs are not unified across multiple PLMNs. For example, it may be the case that MBS session setup information received from a network entity associated with a first PLMN includes an MBS service identification (e.g., separate from the TMGI) that uniquely identifies the MBS session across multiple PLMNs, and MBS session setup information received from a network entity associated with a second PLMN also includes such an MBS service identification that uniquely identifies the MBS session across the multiple PLMNs, and the MBS service identification information in the MBS session setup information received from both network entities is identical. In such a scenario, the cellular base station may identify that both PLMNs are configuring the same MBS service based, at least in part, on the MBS service identification information indicated for the MBS session being identical, and therefore associate the MBS session for that MBS service with both the first PLMN and the second PLMN.

[0082] As yet a further possibility, a particular component carrier and / or service area may be configured to provide one MBS session. For example, MBS session setup information received from a network entity associated with a first PLMN may indicate setting up the MBS session using a component carrier configured (e.g., by a cellular base station) to provide one MBS session. MBS session setup information may also be received by the cellular base station for the MBS session from a network entity associated with a second PLMN indicating setting up the MBS session using a component carrier configured to provide one MBS session. In such a scenario, the cellular base station may determine that the MBS session is associated with both the first PLMN and the second PLMN based at least in part on the MBS session setup information received from both PLMNs indicating setting up the MBS session using a component carrier configured to provide one MBS session. As another example, MBS session setup information received from a network entity associated with the first PLMN may indicate setting up the MBS session using a service area configured (e.g., by a cellular base station) to provide one MBS session. MBS session setup information may also be received by the cellular base station for the MBS session from a network entity associated with the second PLMN indicating that the MBS session is to be set up using a service area configured to provide one MBS session. In such a scenario, the cellular base station may determine that the MBS session is associated with both the first PLMN and the second PLMN based at least in part on the MBS session setup information received from both PLMNs indicating that the MBS session is to be set up using a service area configured to provide one MBS session.

[0083] As yet another possibility, some or all of the networks with RAN-sharing deployments may be able to coordinate shared / unified TMGI designs between their PLMNs so that they can identify MBS services being set up in cellular base stations that are part of the RAN-sharing deployment between them. In other words, it may be possible to coordinate TMGI designs so that a shared TMGI can be designed to uniquely identify an MBS service across multiple PLMNs. For example, a shared Mobile Network Code (MNC) for the coordinated combination of PLMNs may be defined, and the MBS session setup information for the MBS session may include a shared MNC value in the MNC field of the TMGI for the MBS service. In at least some examples, the MBS service ID field of the TMGI may also be unified across multiple PLMNs for the same MBS service. In such a scenario, the cellular base station may be able to associate an MBS session for the MBS service with both a first PLMN and a second PLMN based on the TMGI for the MBS session associated with both the first PLMN and the second PLMN.

[0084] It should be noted that, in at least some embodiments, in such a scenario, the cellular base station may be able to identify that the MBS session is associated with both the first PLMN and the second PLMN, even if the MBS session setup information is received from only one or the other of the first PLMN or the second PLMN. It may also be possible for the cellular base station to receive MBS session setup information for the MBS session from both the first PLMN and the second PLMN. In such a scenario, it may be the case that the same shared TMGI is indicated for the MBS session by both PLMNs, and the cellular base station may be able to determine that both MBS session setup requests refer to the same MBS service based, at least in part, on the TMGI in both MBS session setup requests being identical.

[0085] It should be noted that other mechanisms for determining to associate an MBS session with multiple PLMNs are also possible, in addition to or alternative to the mechanisms described herein.

[0086] At 606, according to various embodiments, the cellular base station can configure MBS sessions associated with multiple PLMNs and can provide associated MBS services potentially including wireless devices served by the cellular base station and other wireless devices, which may include wireless devices associated with either the first PLMN or the second PLMN or both.

[0087] Configuring the MBS session may be performed in a manner that may depend at least in part on how the cellular base station identifies that the MBS session is identified with multiple PLMNs. For example, in various scenarios in which different TMGIs are configured by different PLMNs when performing MBS session setup (e.g., associated with different PLMNs), the cellular base station may configure the MBS session with multiple different TMGIs (e.g., at least a first TMGI and a second TMGI). This may enable a wireless device served by the cellular base station to identify that the MBS session is associated with each of the PLMNs associated with the TMGI configured for the MBS session. In at least some examples, this may enable the wireless device to receive content for the MBS session identified via a TMGI associated with a PLMN not associated with the wireless device. For example, a first TMGI indicated for the MBS session may be associated with a PLMN associated with the wireless device, and a second TMGI indicated for the MBS session may be associated with a PLMN not associated with the wireless device. In this example scenario, the wireless device may be able to receive content for an MBS session identified via the second TMGI, and the wireless device may identify the content as being for the MBS session based at least in part on the second TMGI. As another example, if the MBS session is a multicast MBS session, and a first TMGI for the MBS session is associated with a PLMN associated with the wireless device and a second TMGI for the MBS session is associated with a PLMN not associated with the wireless device, the wireless device may receive a paging for the multicast MBS session for the second TMGI and may be able to trigger a connection to receive the multicast MBS session based at least in part on the second TMGI.

[0088] As another possibility, in a scenario where a unified / shared TMGI framework is established between cooperative networks and such a shared TMGI is provided when performing an MBS session setup, the cellular base station may configure the MBS session using the shared TMGI. In such a scenario, the wireless device may be able to identify that the MBS session is associated with at least one PLMN associated with the wireless device, and therefore, the wireless device may be able to join the MBS session and receive content for the MBS session.

[0089] Note that in some embodiments, if MBS service identification information that uniquely identifies an MBS session across multiple PLMNs is provided to a cellular base station (and potentially used to identify that an MBS session is associated with multiple PLMNs), such MBS service identification information may be provided as part of the MBS session configuration, as needed. Such information may be used to identify the MBS service provided by the MBS session. Additionally, or alternatively, in the case of a multicast use case, the network may be able to use such information to indicate MBS multicast activation in notification paging for the MBS session. Alternatively, even if such MBS service identification information is provided to the cellular base station, it may be possible for the information to be transparent (e.g., not provided) to the wireless device (e.g., during MBS session configuration). In such a scenario, an existing mechanism for identifying the service(s) of interest, such as an MBS service ID field included in the TMGI(s) for the MBS session, may be used by the wireless device.

[0090] Thus, according to at least some embodiments, the method of FIG. 6 may, in at least some examples, be used to provide a framework by which a shared RAN may provide broadcast and multicast services in a resource-efficient manner. For example, using the techniques described herein, when the same broadcast or multicast service is provided from an application function (e.g., via one or more cellular core networks) to a shared cellular base station and to wireless devices served by the cellular base station (e.g., including devices associated with multiple networks that share the cellular base station), it may be possible to utilize a network sharing configuration to avoid duplicate provision of the service from the cellular base station to wireless devices associated with different networks. This, according to at least some embodiments, may result in more efficient network resource usage than if the broadcast or multicast service were provided separately for each of the networks sharing the cellular base station. Figures 7 to 18 and additional information

[0091] Figures 7-18 illustrate further embodiments that may be used, if desired, in conjunction with the method of Figure 6. It should be noted, however, that the exemplary details shown in and described with respect to Figures 7-18 are not intended to limit the disclosure as a whole, and that numerous variations and substitutions to the details provided herein below are possible and should be considered within the scope of the disclosure.

[0092] In the 3GPP Release 17 NR Multicast and Broadcast Service (MBS) design, an MBS service / session may be identified by a Temporary Mobile Group Identifier (TMGI), which may be assigned by the 5G Core (5GC) network. The TMGI may be different for different Public Land Mobile Networks (PLMNs) and network operators (e.g., even for the same service). At the 5GC-Radio Access Network (RAN) interface, an MBS broadcast / multicast sharing session may be set up for each MBS session. With respect to the RAN, the gNB may provide configuration and transmission for the MBS multicast / broadcast service using an MBS radio bearer. In some examples, one MRB may be allowed to be associated with at most one MBS session and TMGI. According to at least some embodiments, further aspects and details of the 3GPP Release 17 NR MBS design can be found in 3GPP TS 23.003 v.17.5.0, 3GPP TS 38.331 v.17.0.0, and 3GPP TS 38.413 v.17.0.0.

[0093] Network sharing may be a practice involving sharing cellular network infrastructure equipment among multiple network operators, for example, to reduce network capital expenditures. In a RAN-sharing deployment, if the same multicast / broadcast service is separately provided by two (or more) operators, the service may potentially be recognized as separate TMGIs, which may result in overlapping point-to-multipoint (PTM) radio resource consumption in the same cell for transmission of the same content. Figure 7 illustrates aspects of such a possible scenario, according to some embodiments. As shown, for an MBS service ("MBS service #x"), an application function (AF) 702 may provide MBS service to one 5GC 704 operated by one operator ("Operator 1") using TMGI #1 and to another 5GC 706 operated by another operator ("Operator 2") using TMGI #2. The services may be provided in an overlapping manner to the shared RAN / gNB 708, which may then overlap the provision of MBS service #x from the same serving cell (shared by Operator 1 and Operator 2) to the UE 710 served by that cell. This separate / overlapping PTM resource allocation for different operators may be a relatively inefficient use of resources.

[0094] Therefore, in at least some examples, it may be beneficial to provide techniques that may more efficiently manage MBS resources in RAN sharing scenarios. There may be various possible approaches to improving resource utilization efficiency for MBS sessions in RAN sharing scenarios, including approaches in which a shared / unified TMGI design may be supported across different PLMNs and approaches in which multiple TMGIs may be associated with one MBS service / session, among other possibilities.

[0095] FIG. 8 illustrates an exemplary aspect of a possible TMGI structure, according to some embodiments. As shown, the structure may include a six-digit MBMS service ID field 802, a three-digit MCC field 804, and a two- or three-digit MNC field 806. In approaches where a shared TMGI design is supported, operators may be able to adjust TMGI allocations, for example, so that the same TMGI can be used by multiple PLMNs to identify the same MBS service. Operators adopting such approaches may cooperate to ensure that the same MBMS service ID is used for the same MBMS service by each of the operators with RAN shared deployments. Furthermore, according to at least some embodiments, a shared PLMN ID may be defined for each combination of network operators with RAN shared deployments, which may be used to ensure that the MNC field of the TMGI may be uniform across each set of network operators with RAN shared deployments.

[0096] 9 illustrates aspects of a possible scenario in which a shared / unified TMGI is used across different PLMNs, according to some embodiments. As shown, in the illustrated scenario, for an MBS service (“MBS service #x”), an AF 902 may provide the MBS service to one 5GC 904 operated by one operator (“Operator 1”) using TMGI #x and may provide the MBS service to another 5GC 906 operated by another operator (“Operator 2”) using TMGI #x. The services may be provided redundantly to a shared RAN / gNB 908, which may recognize that the same MBS service #x is received from both 5GCs and may set up a single MBS session for MBS service #x from the serving cell to a UE 910 served by that cell.

[0097] 10 is a signal flow diagram illustrating example network communication aspects of the scenario of FIG. 9 , according to some embodiments. The illustrated scenario may include communications between a UE 1002, a gNB 1004, an AMF-1 / MB-SMF-1 1006, and an AMF-2 / MB-SMF-2 1008. As shown, at 1010, the gNB 1004 may establish a broadcast configuration with the UE 1002, where PLMN#1 and PLMN#2 have RAN sharing. At 1012, the AMF-1 / MB-SMF-1 1006 may perform MBS broadcast setup with the gNB 1004 for TMGI#x. At 1014, the gNB 1004 may provide a broadcast MBS session configuration for MBS session #1 using TMGI#x. At 1016, the AMF-2 / MB-SMF-2 1008 may perform MBS broadcast setup with the gNB 1004 for TMGI#x. At 1018, the gNB 1004 may recognize that the MBS session setup requests are for the same MBS service (from different 5GCs). According to at least some embodiments, for overlapped requests from different 5GCs / operators, the gNB may not need to set up another MBS session or declare a failure.

[0098] 11 illustrates aspects of another possible scenario in which a shared / unified TMGI is used across different PLMNs, according to some embodiments. As shown, in the illustrated scenario, for an MBS service (“MBS service #x”), the AF 1102 may provide MBS service to one 5GC 1106 operated by Operator 2 using TMGI #x. In the illustrated scenario, the AF may be aware of the inter-operator RAN sharing configuration and may not provide MBS service to the 5GC 1104 operated by Operator 1. Service may be provided to the shared RAN / gNB 1108, which may set up a single MBS session for MBS service #x from a serving cell to a UE 1110 served by that cell.

[0099] Figure 12 is a signal flow diagram illustrating example network communication aspects of the scenario of Figure 11, according to some embodiments. The illustrated scenario may include communication between a UE 1202, a gNB 1204, an AMF-1 / MB-SMF-1 1206, an AMF-2 / MB-SMF-2 1208, and an AF 1210. As shown, at 1212, the gNB 1204 may establish a broadcast configuration with the UE 1202, where PLMN#1 and PLMN#2 have RAN sharing. At 1214, the AF may recognize that the two MB-SMFs have a RAN sharing deployment. According to at least some embodiments, the AF may be pre-configured with which operators share the RAN deployment on the Uu interface. At 1216, the AF 1210 may provide a TMGI allocation (TMGI#x) to the AMF-2 / MF-SMF-2 1208. At 1218, AMF-2 / MB-SMF-2 1208 may perform MBS broadcast setup with gNB 1204 for TMGI#x. At 1220, gNB 1204 may provide broadcast MBS session configuration for MBS session #1 using TMGI#x.

[0100] At 1222, the AF 1210 may determine to switch service to the AMF-1 / MB-SMF-1 1206. Note that such triggering of an MBS session setup via another operator after a previous setup of an MBS session has already been performed may not generally be required, but may be performed if necessary in case of failure of the previous setup and / or based on other events (e.g., network congestion as one possibility). At 1224, the AF may provide a TMGI allocation (TMGI#x) to the AMF-1 / MB-SMF-1 1206. At 1226, the AMF-1 / MB-SMF-1 1206 may perform an MBS broadcast setup with the gNB 1204 for TMGI#x.

[0101] As previously mentioned herein, an approach in which multiple TMGIs can be associated with one MBS service / session may be another possibility for efficiently providing multicast and broadcast services in a RAN sharing deployment. FIG. 13 is a signal flow diagram illustrating network communication aspects of one such example scenario, according to some embodiments. The illustrated scenario may include communication between a UE 1302, a gNB 1304, an AMF-1 1306, and an AMF-2 1308. As shown, at 1310, the gNB 1304 may establish a broadcast configuration with the UE 1302, where PLMN#1 and PLMN#2 have RAN sharing. At 1312, the AMF-1 1306 may perform MBS broadcast setup with the gNB 1304 for TMGI#x. At 1314, the gNB 1304 may provide a broadcast MBS session configuration for MBS session#1 using TMGI#x. At 1316, the AMF-2 1308 may perform MBS broadcast setup with the gNB 1304 for TMGI#y. At 1318, the gNB may recognize that the MBS service for TMGI#y is the same as that for TMGI#x. The gNB may provide an MBS traffic channel (MTCH) configuration for each MBS service, for example, so that an MBS can be associated with multiple TMGIs. Thus, at 1320, the gNB 1304 may provide a broadcast MBS session configuration for MBS session #1 using both TMGI#x and TMGI#y. Note that the AMF may be able to configure the gNB for RAN sharing operation or for a particular MBS service to apply only on a particular carrier, as needed, for example, via an MBS Service Area Information IE in the 5GC-RAN interface.

[0102] For UE operation, it may be possible that the UE may be configured with one MRB / MTCH associated with multiple TMGIs. The UE may be able to identify the MBS service not only via its own TMGI but also via other TMGIs associated with the same MRB / MTCH. For MBS multicast activation notification, it may be possible for the UE to activate an MBS multicast session when any associated TMGI is indicated in paging.

[0103] In the centralized unit (CU)-distributed unit (DU) interface, an MBS service / MRB setup can also be mapped onto multiple TMGIs configured for the same MBS service.

[0104] For such an approach, there may further be various possible techniques for making the gNB aware of the association between TMGIs. One possibility is that the MBS service ID field in the TMGI may be uniform across shared operators / PLMNs, which may be used to identify multicast / broadcast services as the same for different TMGIs. Another possibility is that the association of multiple TMGIs with each other may be configured for the gNB via operations, administration, and maintenance (OAM) means or other means. A further possibility is that a new global MBS service ID may be introduced to associate an MBS service that may be linked to multiple TMGIs. Yet another possibility is that an MBS service may be associated with a particular carrier, which may be designated or defined such that all TMGIs delivered on the particular carrier refer to the same MBS session.

[0105] Figure 14 is a signal flow diagram showing further details of an example scenario in which the MBS service ID field in a TMGI may be unified across shared operators / PLMNs, according to some embodiments. The illustrated scenario may include communication between a UE 1402, a gNB 1404, an AMF-1 / MB-SMF-1 1406, an AMF-2 / MB-SMF-2 1408, and an AF 1410. As shown, at 1412, the AF may recognize that MB-SMF-1 / PLMN#1 and MB-SMF-2 / PLMN#2 are shared and may allocate a unified MBS service ID#A for the MBS service. At 1414, the gNB 1404 may be configured to allocate MBS resources per MB service ID (e.g., rather than per TMGI). At 1416, the gNB 1404 may establish a broadcast configuration with the UE 1402, in which PLMN#1 and PLMN#2 have RAN sharing. At 1418, the AF 1410 may create an MBS broadcast context with the AMF-1 / MB-SMF-1 1406 using TMGI#x having MBS service ID=A. At 1420, the AMF-1 / MB-SMF-1 1406 may perform MBS broadcast setup with the gNB 1404 for TMGI#x. At 1422, the gNB 1404 may provide a broadcast MBS session configuration for MBS session #1 using TMGI#x. At 1424, the AF 1410 may create an MBS broadcast context with the AMF-2 / MB-SMF-2 1408 using TMGI#y having MBS service ID=A. At 1426, the AMF-2 / MB-SMF-2 1408 may perform MBS broadcast setup with the gNB 1404 for TMGI#y. At 1428, the gNB may recognize that the MBS service for TMGI#y is the same as that for TMGI#x based on the MBS service ID in both TMGIs being set to A.Thus, at 1430, gNB1404 may provide a broadcast MBS session configuration for MBS session #1 using both TMGI#x and TMGI#y.

[0106] 15 is a signal flow diagram illustrating further details of an example scenario in which an association between multiple TMGIs may be configured for a gNB that is part of a RAN sharing deployment via OAM or other means, according to some embodiments. The illustrated scenario may include communication between a UE 1502, a gNB 1504, an AMF-1 / MB-SMF-1 1506, an AMF-2 / MB-SMF-2 1508, and an AF 1510. As shown, at 1512, the gNB may recognize that there is an association between TMGI#x and TMGI#y. At 1514, the gNB 1504 may establish a broadcast configuration with the UE 1502, where PLMN#1 and PLMN#2 have RAN sharing. At 1516, the AF 1510 may create an MBS broadcast context with the AMF-1 / MB-SMF-1 1506 using TMGI#x. At 1518, the AMF-1 / MB-SMF-1 1506 may perform MBS broadcast setup with the gNB 1504 for TMGI#x. At 1520, the gNB 1504 may provide a broadcast MBS session configuration for MBS session #1 using TMGI#x. At 1522, the AF 1510 may create an MBS broadcast context with the AMF-2 / MB-SMF-2 1508 using TMGI#y. At 1524, the AMF-2 / MB-SMF-2 1508 may perform MBS broadcast setup with the gNB 1504 for TMGI#y. Based on the pre-configured association between TMGI#x and TMGI#y, gNB1504 may recognize that the MBS service for TMGI#y is the same as that for TMGI#x, and therefore, at 1526, gNB1504 may provide a broadcast MBS session configuration for MBS session #1 using both TMGI#x and TMGI#y.

[0107] 16 is a signal flow diagram illustrating further details of an example scenario in which a new global MBS service ID may be introduced to associate multiple TMGIs with the same MBS service, according to some embodiments. The illustrated scenario may include communication between a UE 1602, a gNB 1604, an AMF-1 / MB-SMF-1 1606, an AMF-2 / MB-SMF-2 1608, and an AF 1610. At 1612, the gNB 1604 may be configured to allocate MBS resources per global MBS service ID (e.g., rather than per TMGI). At 1614, the gNB 1604 may establish a broadcast configuration with the UE 1602, in which PLMN#1 and PLMN#2 have RAN sharing. At 616, the AF 1610 may create an MBS broadcast context with the AMF-1 / MB-SMF-1 1606 using TMGI#x with global MBS ID=A. At 1618, the AMF-1 / MB-SMF-1 1606 may perform MBS broadcast setup with the gNB 1604 for TMGI#x, including indicating that the MBS service has a global MBS ID=A. At 1620, the gNB 1604 may provide a broadcast MBS session configuration for MBS session #1 using TMGI#x. At 1622, the AF 1610 may create an MBS broadcast context with the AMF-2 / MB-SMF-2 1608 using TMGI#y, which has a global MBS ID=A. At 1624, the AMF-2 / MB-SMF-2 1608 may perform MBS broadcast setup with the gNB 1604 for TMGI#y, including indicating that the MBS service has a global MBS ID=A. The gNB may recognize that the MBS service for TMGI#y is the same as that for TMGI#x based on the global MBS ID associated with both TMGIs being set to A. Thus, at 1626, gNB 1604 may provide a broadcast MBS session configuration for MBS session #1 using both TMGI#x and TMGI#y.

[0108] As shown, Figure 16 also illustrates possible MBS Session ID and Global MBS ID information element descriptions that may be included in 3GPP technical specifications as part of defining how such Global MBS ID parameters may be used in 3GPP-based communication systems, according to at least some embodiments. Note that the illustrated description sections are exemplary only, and variations or alternatives are possible.

[0109] It should be noted that, according to various embodiments, such a new global MBS service ID may be transparent to the UE (e.g., as shown in the scenario of Figure 16) or may be configured together with the TMGI for the UE. The UE may be able to use the global MBS ID information to identify the MBS service in which the UE is interested on the Uu interface. The network may be able to use the global MBS ID to indicate MBS multicast activation in notification paging (e.g., in the case of multicast).

[0110] FIG. 17 is a signal flow diagram illustrating further details of an example scenario in which a particular carrier may be configured to provide one MBS service, according to some embodiments. The illustrated scenario may include communications between a UE 1702, a gNB 1704, an AMF-1 / MB-SMF-1 1706, an AMF-2 / MB-SMF-2 1708, and an AF 1710. As shown, at 1712, the gNB may configure a carrier ("Component Carrier 1" or "CC#1") and / or a particular service area as providing only one MBS service. Thus, all TMGIs delivered on CC#1 and / or within the configured service area may be known to refer to the same MBS session. At 1714, the gNB 1704 may establish a broadcast configuration with the UE 1702, in which PLMN#1 and PLMN#2 have RAN sharing. At 1716, the AF 1710 may provide a TMGI allocation to the AMF-1 / MB-SMF-1 1706 using TMGI#x and using the service area configured as "A". At 1718, the AMF-1 / MB-SMF-1 1706 may perform an MBS broadcast setup with the gNB 1704 for TMGI#x, and an MBS session is configured for CC#1 based on the service area configured as A. At 1720, the gNB 1704 may provide a broadcast MBS session configuration for MBS session #1 using TMGI#x on CC#1. At 1722, the AF 1710 may provide a TMGI allocation to the AMF-2 / MB-SMF-2 1708 using TMGI#y and using the service area configured as "A". At 1724, AMF-2 / MB-SMF-2 1708 may perform MBS broadcast setup with gNB 1704 for TMGI#y, and an MBS session is configured for CC#1 based on the service area configured as A.Because gNB1704 may recognize that the MBS service for TMGI#y is the same as that for TMGI#x based on its association with the particular carrier CC#1, at 1726 gNB1704 may provide a broadcast MBS session configuration for MBS session #1 using both TMGI#x and TMGI#y on CC#1.

[0111] 18 is a signal flow diagram illustrating further details of possible UE behavior in a scenario in which multiple TMGIs may be associated with one MBS multicast service / session, according to some embodiments. The illustrated scenario may include communications between a UE 1802, a gNB 1804, an AMF-1 / MB-SMF-1 1806, and an AMF-2 / MB-SMF-2 1808. As shown, at 1810, the gNB 1804 may establish a broadcast configuration with the UE 1802, where PLMN#1 and PLMN#2 have RAN sharing. At 1812, the AMF-1 / MB-SMF-1 1806 may perform MBS multicast setup with the gNB 1804 for TMGI#x. At 1814, the gNB 1804 may provide a multicast MBS session configuration for MBS session#1 using TMGI#x. At 1816, AMF-2 / MB-SMF-2 1808 may perform MBS multicast setup with gNB 1804 for TMGI#y. At 1818, gNB 1804 may recognize that the MBS service for TMGI#y is the same as that for TMGI#x. Thus, at 1820, gNB 1804 may provide multicast MBS session configuration for MBS session #1 using both TMGI#x and TMGI#y.

[0112] At 1822, the UE 1802 may join multicast session TMGI#x. The UE 1802 may recognize, for example, from at least the multicast MBS session configuration, that TMGI#x and TMG#y are associated with the same MBS service. At 1824, the UE may receive a paging including a notification for TMGI#y. At 1826, the UE 1802 may trigger a connection to receive the MBS service based on the paging notification for TMGI#y and the knowledge that TMGI#x and TMG#y are associated. Thus, in such a scenario, according to at least some embodiments, the UE may be able to activate the MBS multicast session when any TMGI associated with its MBS service of interest is indicated in the paging.

[0113] Further exemplary embodiments are provided below.

[0114] One set of embodiments includes receiving, by a cellular base station associated with at least a first public land mobile network (PLMN) and a second PLMN, MBS session setup information for a multicast and broadcast service (MBS) session from a network entity associated with the first PLMN, determining that the MBS session is associated with both the first PLMN and the second PLMN, and configuring the MBS session associated with both the first PLMN and the second PLMN.

[0115] According to some embodiments, the method further includes receiving MBS session setup information for the MBS session from a network entity associated with the second PLMN, and determining that the MBS session is associated with both the first PLMN and the second PLMN is based at least in part on receiving the MBS session setup information for the MBS session from both the network entity associated with the first PLMN and the network entity associated with the second PLMN.

[0116] According to some embodiments, the method further includes receiving an indication that the first Temporary Mobile Group Identifier (TMGI) and the second TMGI are associated with each other, wherein the MBS session setup information received from the network entity associated with the first PLMN indicates the first TMGI for the MBS session and the MBS session setup information received from the network entity associated with the second PLMN indicates the second TMGI for the MBS session.

[0117] According to some embodiments, the MBS session setup information received from a network entity associated with a first PLMN indicates a first Temporary Mobile Group Identifier (TMGI) for the MBS session, and the MBS session setup information received from a network entity associated with a second PLMN indicates a second TMGI for the MBS session, and the MBS service identification fields for the first TMGI and the second TMGI are identical.

[0118] According to some embodiments, the MBS session setup information received from the network entity associated with the first PLMN includes an MBS service identification information that uniquely identifies the MBS session across multiple PLMNs, the MBS session setup information received from the network entity associated with the second PLMN includes an MBS service identification information that uniquely identifies the MBS session across the multiple PLMNs, and the MBS service identification information in the MBS session setup information received from the network entity associated with the first PLMN and the MBS service identification information in the MBS session setup information received from the network entity associated with the second PLMN are identical.

[0119] According to some embodiments, determining that the MBS session is associated with both the first PLMN and the second PLMN is based at least in part on a temporary mobile group identifier (TMGI) for the MBS session.

[0120] According to some embodiments, the TMGI for the MBS session is a shared TMGI associated with both the first PLMN and the second PLMN.

[0121] According to some embodiments, the method further includes configuring a component carrier to provide one MBS session, wherein the MBS session associated with both the first PLMN and the second PLMN is configured on the component carrier.

[0122] According to some embodiments, the MBS session setup information received from a network entity associated with a first PLMN indicates setting up the MBS session using a component carrier configured to provide one MBS session, and the method further includes receiving MBS session setup information for the MBS session from a network entity associated with a second PLMN, wherein the MBS session setup information received from the network entity associated with the second PLMN indicates setting up the MBS session using a component carrier configured to provide one MBS session, and determining that the MBS session is associated with both the first PLMN and the second PLMN is based at least in part on the MBS session setup information received from both the network entity associated with the first PLMN and the network entity associated with the second PLMN indicating setting up the MBS session using a component carrier configured to provide one MBS session.

[0123] According to some embodiments, the method further includes configuring the service area to provide one MBS session, wherein an MBS session associated with both the first PLMN and the second PLMN is configured for the service area.

[0124] According to some embodiments, the MBS session setup information received from a network entity associated with a first PLMN indicates setting up the MBS session using a service area configured to provide one MBS session, and the method further includes receiving MBS session setup information for the MBS session from a network entity associated with a second PLMN, wherein the MBS session setup information received from the network entity associated with the second PLMN indicates setting up the MBS session using a service area configured to provide one MBS session, and determining that the MBS session is associated with both the first PLMN and the second PLMN is based at least in part on the MBS session setup information received from both the network entity associated with the first PLMN and the network entity associated with the second PLMN indicating setting up the MBS session using a service area configured to provide one MBS session.

[0125] Another set of embodiments may include a cellular base station, the cellular base station comprising one or more processors and a memory having stored thereon instructions that, when executed by the one or more processors, perform the steps of the method of any of the foregoing examples.

[0126] Yet another set of embodiments may include a method that includes establishing, by a wireless device, a wireless link with a cellular base station and receiving multicast and broadcast service (MBS) session configuration information from the cellular base station, the MBS session configuration information configuring an MBS session associated with a plurality of public land mobile networks (PLMNs).

[0127] According to some embodiments, the MBS session configuration information indicates that at least a first Temporary Mobile Group Identifier (TMGI) and a second TMGI are associated with the MBS session.

[0128] According to some embodiments, the first TMGI is associated with a PLMN associated with the wireless device and the second TMGI is associated with a PLMN not associated with the wireless device, and the method further includes receiving content for an MBS session identified via the second TMGI and identifying the content as being for the MBS session based at least in part on the second TMGI.

[0129] According to some embodiments, the MBS session is a multicast MBS session, the first TMGI is associated with a PLMN associated with the wireless device, and the second TMGI is associated with a PLMN not associated with the wireless device, and the method further includes receiving a paging of the multicast MBS session for the second TMGI and triggering a connection to receive the multicast MBS session based at least in part on the second TMGI.

[0130] According to some embodiments, the MBS session configuration information includes an MBS service identity that uniquely identifies the MBS session across multiple PLMNs.

[0131] According to some embodiments, the Temporary Mobile Group Identifier (TMGI) for the MBS session is a shared TMGI associated with multiple PLMNs.

[0132] Yet another set of embodiments may include a wireless device comprising one or more processors and a memory having stored thereon instructions that, when executed by the one or more processors, perform the steps of the method of any of the foregoing examples.

[0133] A further set of embodiments may include a computer program product including computer instructions that, when executed by one or more processors, perform the steps of the method of any of the foregoing examples.

[0134] Further exemplary embodiments may include methods, the methods including performing, by a device, any or all parts of the preceding examples.

[0135] Another example embodiment may include a device comprising an antenna, a radio coupled to the antenna, and a processor operably coupled to the radio, the device configured to implement any or all portions of the foregoing examples.

[0136] A further exemplary set of embodiments may include a non-transitory computer-accessible memory medium containing program instructions that, when executed on a device, cause the device to perform any or all portions of any of the foregoing examples.

[0137] A still further exemplary set of embodiments may include a computer program including instructions for carrying out any or all portions of any of the foregoing examples.

[0138] Yet another exemplary set of embodiments may include an apparatus comprising means for performing any or all of the elements of any of the foregoing examples.

[0139] A further example set of embodiments may include an apparatus comprising a processor configured to cause a wireless device to perform any or all elements of any of the preceding examples.

[0140] It is well understood that the use of personal information should comply with generally recognized privacy policies and practices that meet or exceed industry or government requirements for maintaining user privacy. In particular, personal information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized uses should be clearly indicated to users.

[0141] Any of the methods described herein for operating a user equipment (UE) may be the basis for a corresponding method for operating a base station by interpreting each message / signal X received by the UE on the downlink as a message / signal X transmitted by the base station, and each message / signal Y transmitted by the UE on the uplink as a message / signal Y received by the base station.

[0142] Embodiments of the present disclosure may be implemented in any of a variety of forms. For example, in some embodiments, the subject matter may be implemented as a computer-implemented method, a computer-readable storage medium, or a computer system. In other embodiments, the subject matter may be implemented using one or more custom-designed hardware devices, such as an ASIC. In other embodiments, the subject matter may be implemented using one or more programmable hardware elements, such as an FPGA.

[0143] In some embodiments, a non-transitory computer-readable memory medium (e.g., a non-transitory memory element) may store program instructions and / or data that, when executed by a computer system, may cause the computer system to perform a method, such as any of the method embodiments described herein, or a combination of the method embodiments described herein, or a subset of the method embodiments described herein, or a combination of such subsets.

[0144] In some embodiments, a device (e.g., a UE) may be configured to include a processor (or set of processors) and a memory medium (or memory element), where the memory medium stores program instructions, and the processor is configured to read and execute the program instructions from the memory medium, and the program instructions are executable to perform any of the various method embodiments described herein (or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets). The device may be embodied in any of a variety of forms.

[0145] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated, and it is intended that the following claims be interpreted to embrace all such variations and modifications.

Claims

Claim 1: A method performed by a cellular base station associated with both a first public land mobile network (PLMN) and a second PLMN, comprising: receiving, from a network entity associated with the first PLMN, MBS session setup information for a Multicast and Broadcast Service (MBS) session associated with the first PLMN using Radio Access Network (RAN) sharing; receiving MBS session setup information for the MBS session from a network entity associated with the second PLMN using the RAN sharing; determining, based at least in part on receiving MBS session setup information for the MBS session from both the network entity associated with the first PLMN and the network entity associated with the second PLMN, that the MBS session should be associated with both the first PLMN and the second PLMN using the RAN sharing; configuring a single MBS session associated with both the first PLMN and the second PLMN; A method comprising:

2. The method comprises: receiving notification that a first temporary mobile group identifier (TMGI) and a second TMGI are associated with each other; Further comprising: the MBS session setup information received from the network entity associated with the first PLMN indicates the first TMGI for the MBS session; the MBS session setup information received from the network entity associated with the second PLMN indicates the second TMGI for the MBS session; The method of claim 1.

3. the MBS session setup information received from the network entity associated with the first PLMN indicates a first Temporary Mobile Group Identifier (TMGI) for the MBS session; the MBS session setup information received from the network entity associated with the second PLMN indicates a second TMGI for the MBS session; the MBS service identification fields for the first TMGI and the second TMGI are identical; The method of claim 1.

4. the MBS session setup information received from the network entity associated with the first PLMN includes an MBS service identity that uniquely identifies the MBS session across multiple PLMNs; the MBS session setup information received from the network entity associated with the second PLMN includes an MBS service identity that uniquely identifies the MBS session across multiple PLMNs; the MBS service identification information in the MBS session setup information received from the network entity associated with the first PLMN and the MBS service identification information in the MBS session setup information received from the network entity associated with the second PLMN are identical; The method of claim 1.

5. determining that the single MBS session should be associated with both the first PLMN and the second PLMN is based at least in part on a Temporary Mobile Group Identifier (TMGI) for the MBS session; The method of claim 1.

6. the TMGI for the single MBS session is a shared TMGI associated with both the first PLMN and the second PLMN. The method of claim 5.

7. The method comprises: configuring a component carrier to provide one MBS session; the single MBS session to be associated with both the first PLMN and the second PLMN is configured on the component carrier; The method of claim 1.

8. the MBS session setup information received from the network entity associated with the first PLMN indicates setting up the MBS session using the component carrier configured to provide one MBS session; the MBS session setup information received from the network entity associated with the second PLMN indicates setting up the MBS session using the component carrier configured to provide one MBS session; determining that the single MBS session is associated with both the first PLMN and the second PLMN is based at least in part on the MBS session setup information received from both the network entity associated with the first PLMN and the network entity associated with the second PLMN, the MBS session setup information indicating that the single MBS session is to be set up using the component carrier configured to provide one MBS session; The method of claim 7.

9. The method comprises: configuring a service area to provide one MBS session; the single MBS session associated with both the first PLMN and the second PLMN is configured for the service area; The method of claim 1.

10. the MBS session setup information received from the network entity associated with the first PLMN indicates setting up the MBS session using the service area configured to provide one MBS session; the MBS session setup information received from the network entity associated with the second PLMN indicates setting up the MBS session using the service area configured to provide one MBS session; determining that the single MBS session is associated with both the first PLMN and the second PLMN is based at least in part on the MBS session setup information received from both the network entity associated with the first PLMN and the network entity associated with the second PLMN, the MBS session setup information indicating that the single MBS session is to be set up using the service area configured to provide one MBS session; 10. The method of claim 9. When the MBS session setup information for the MBS session associated with the first PLMN is received, the MBS session associated with the first PLMN is configured, and when the MBS session setup information for the MBS session associated with the second PLMN is subsequently received, the single MBS session is associated with both the first PLMN and the second PLMN. The method of claim 1.

12. The network entity associated with the first PLMN and the network entity associated with the second PLMN are an access and management function or a multicast broadcast session management function. The method of claim 1.

13. A method performed in a wireless device, comprising: communicating over wireless links with cellular base stations associated with both a first public land mobile network (PLMN) and a second PLMN in connection with radio access network (RAN) sharing; receiving multicast and broadcast service (MBS) session configuration information from the cellular base station, the MBS session configuration information configuring a single MBS session associated with both the first PLMN and the second PLMN; and determining that the single MBS session should be associated with both the first PLMN and the second PLMN using the RAN sharing based at least in part on the cellular base station receiving MBS session information for the MBS session from both a network entity associated with the first PLMN and a network entity associated with the second PLMN. method.

14. the single MBS session configuration information indicating that at least a first Temporary Mobile Group Identifier (TMGI) and a second TMGI are associated with the MBS session; The method of claim 13.

15. the first TMGI is associated with a PLMN associated with the wireless device and the second TMGI is associated with a PLMN not associated with the wireless device, and the method further comprises: receiving content for the single MBS session identified via the first TMGI; Identifying the content as being for the single MBS session based at least in part on the first TMGI; The method of claim 14 further comprising:

16. the MBS session is a multicast MBS session; the first TMGI is associated with a PLMN associated with the wireless device and the second TMGI is associated with a PLMN not associated with the wireless device, and the method further comprises: receiving a paging of the multicast MBS session for the first TMGI; triggering a connection to receive the multicast MBS session based at least in part on the first TMGI; The method of claim 14 further comprising:

17. the MBS session configuration information includes an MBS service identity that uniquely identifies the MBS session across multiple PLMNs; 15. The method of claim 14.

18. a Temporary Mobile Group Identifier (TMGI) for the MBS session is a shared TMGI associated with the first PLMN and the second PLMN; The method of claim 13.

19. A cellular base station device, comprising: A cellular base station device comprising a processor configured to perform the method of any one of claims 1 to 12 when executing instructions stored in a memory.

20. a radio operably coupled to said processor; 20. The cellular base station device of claim 19, further comprising:

21. A wireless device, comprising:

19. A wireless device comprising a processor configured to perform the method of any one of claims 13 to 18 when executing instructions stored in a memory.

22. A radio operably coupled to the processor.

22. The wireless device of claim 21, further comprising:

23. 13. A computer readable storage medium containing program instructions, the program instructions being configured to perform the method of any one of claims 1 to 12 when executed by a computer in a cellular base station device.

24. A computer-readable storage medium containing program instructions, the program instructions being configured, when executed by a computer in a wireless device, to perform a method according to any one of claims 13 to 18.

Images