Multicast and broadcast service enhancements in new radios

Abstract

A wireless device may receive a radio resource control (RRC) configuration message on a first component carrier (CC) from a serving base station (BS). The RRC configuration message may include multicast and broadcast service (MBS) scheduling information or configuration information. The wireless device may also receive a transmission including additional MBS information from the MBS BS on the first CC. The wireless device may determine a conflict between a unicast transmission and a broadcast transmission, and send an interest indication to the MBS BS. The wireless device may receive, from the MBS BS and on a second CC, an RRC reconfiguration message including adjusted scheduling information or configuration information corresponding to the unicast transmission. The wireless device may receive the broadcast transmission from the MBS BS and the unicast transmission from the serving BS based at least in part on the adjusted scheduling information or configuration information.

Description

Technical Field

[0001] The present application relates to wireless communications, and more particularly, to systems, apparatuses, and methods for multicast and broadcast service enhancement in wireless communication systems.

[0002] Related technical description

[0003] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices (i.e., user equipment devices or UEs) now also provide access to the Internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating complex and sophisticated applications that utilize these capabilities. In addition, there are many different wireless communication technologies and wireless communication standards. Some examples of wireless communication standards include GSM, UMTS (e.g., associated with WCDMA or TD-SCDMA air interfaces), LTE, Advanced LTE (LTE-A), NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), Bluetooth ™ wait.

[0004] The introduction of an ever-increasing number of features and functionalities in wireless communication devices has also created a continuing need for improved wireless communications and improved wireless communication devices. In particular, it is important to ensure the accuracy of signals transmitted and received by user equipment (UE) devices (e.g., by wireless devices such as cellular phones, base stations, and relay stations used in wireless cellular communications). In addition, increasing the functionality of UE devices may put a great strain on the battery life of UE devices. Therefore, it is also very important to reduce the power requirements in UE device design while allowing the UE device to maintain good transmission and reception capabilities to improve communications. Therefore, improvements are expected in this area. Summary of the invention

[0005] Embodiments of apparatus, systems, and methods for providing multicast and broadcast service enhancements in wireless communication systems are presented herein.

[0006] In some embodiments, a wireless device may perform a method, the method comprising: receiving a radio resource control (RRC) configuration message from a serving base station (BS) on a first component carrier (CC), wherein the RRC configuration message may include at least one of multicast and broadcast service (MBS) scheduling information or configuration information. The method may also include: receiving a transmission including additional MBS information from the MBS BS on the first CC. In addition, the method may include: determining a conflict between a unicast transmission and a broadcast transmission based on at least one of the received MBS scheduling information or configuration information. Additionally or alternatively, the wireless device may perform: sending an interest indication related to the MBS to the MBS BS, and receiving an RRC reconfiguration message from the MBS BS on a second CC. According to some embodiments, the RRC reconfiguration message may include at least one of the adjusted scheduling information or configuration information corresponding to the unicast transmission. The method performed by the wireless device may also include receiving a broadcast transmission from the MBS BS. In addition, according to some embodiments, the method performed by the wireless device may also include: receiving a unicast transmission from the serving BS based at least in part on the at least one of the adjusted scheduling information or configuration information.

[0007] According to some embodiments, unicast transmissions and broadcast transmissions may be received simultaneously. In some embodiments, the interest indication may be reported via dedicated signaling and may include MBS interest information, user equipment (UE) assistance information, layer 3 (L3) signaling, layer 2 (L2) medium access control-control element (MAC-CE) signaling, or layer 1 (L1) signaling. Additionally or alternatively, the interest indication may include transmission duration information about at least one of the unicast transmission or the broadcast transmission, and also include information related to at least one of a preferred discontinuous reception (DRX) configuration, periodicity, offset, duration, switching time, or switching gap.

[0008] In some embodiments, the interest indication may include frequency information about at least one of a unicast transmission or a broadcast transmission, and also include information related to at least one of a frequency location, a bandwidth, or a subcarrier spacing. Additionally or alternatively, the interest indication may include frequency information about at least one of a unicast transmission or a broadcast transmission, and information related to a preferred bandwidth part (BWP) corresponding to the first CC. According to some embodiments, the interest indication may include frequency information about at least one of a unicast transmission or a broadcast transmission, and also include information related to a preferred serving cell frequency corresponding to a second CC.

[0009] In some embodiments, the interest indication may include frequency information about at least one of the unicast transmission or the broadcast transmission, and further include information related to a preferred bandwidth part (BWP) corresponding to the first CC. Additionally or alternatively, the interest indication may include frequency information about at least one of the unicast transmission or the broadcast transmission, and further include information related to a preferred exclusion of a frequency position corresponding to a range of physical resource blocks (PRBs) from a configured bandwidth (BW) of the first CC.

[0010] According to further embodiments, the interest indication may include spatial information about at least one of a unicast transmission or a broadcast transmission, and further include information related to a preferred list of quasi-co-located (QCL) antenna ports of the first CC. Additionally or alternatively, the interest indication may include information about the unicast transmission, and further include information related to a preference for deactivating a secondary cell (SCell) or deconfiguring the SCell. In some embodiments, the interest indication may include MBS information about at least one of a unicast transmission or a broadcast transmission, and further include information related to at least one of an MBS broadcast frequency or bandwidth.

[0011] In some embodiments, a base station (BS) may be configured to perform a method comprising: sending a capability request including multicast and broadcast service (MBS) specific information to a user equipment (UE). The method may also include: receiving a message including at least one of a capability report or MBS interest information from the UE. Additionally or alternatively, the method may include: sending a radio resource control (RRC) reconfiguration message to the UE, wherein the RRC reconfiguration message includes at least one of adjusted scheduling information or configuration information corresponding to a unicast transmission. According to some embodiments, the method may also include: using the at least one of the adjusted scheduling information or configuration information to send a broadcast transmission to the UE.

[0012] In some embodiments, the capability report may include at least one of one or more frequency band combination parameters or one or more feature set combination parameters. Additionally or alternatively, the MBS interest information may include at least one of one or more preferred frequency band combinations or one or more preferred feature set combinations.

[0013] According to some embodiments, a user equipment (UE) may perform a method comprising:

[0014] A radio resource control (RRC) configuration message is received from a serving base station (BS), the RRC configuration message including a request for a UE to report multicast and broadcast service (MBS) service information of one or more inter-public land mobility network (inter-PLMN) cells. The method may also include: receiving a transmission including MBS configuration information corresponding to an inter-PLMN cell in the one or more inter-PLMN cells from the MBS BS. Additionally or alternatively, the method may include: reporting MBS broadcast information corresponding to the inter-PLMN cell to the serving BS in response to receiving the request. In some embodiments, the method may include: receiving signaling on a multicast control channel (MCCH) from the MBS BS, the signaling including a change in mapping between a temporary mobile group identity (TMGI) and a cell identifier (ID) of the inter-PLMN cell. Additionally or alternatively, the method may include: sending MBS broadcast information corresponding to the inter-PLMN cell to the serving BS, the MBS broadcast information including a change in mapping between the TMGI and the cell ID of the inter-PLMN cell.

[0015] In some embodiments, reporting of MBS broadcast information may be performed according to a single reporting mode corresponding to the UE reporting once. Additionally or alternatively, reporting of MBS broadcast information may be performed according to a periodic reporting mode corresponding to the UE reporting multiple times based on a configured periodicity or MCCH modification period. According to some embodiments, reporting of MBS broadcast information may be performed according to a change reporting mode corresponding to the UE reporting one or more times in response to one or more changes in the mapping between the TMGI and the cell ID of the inter-PLMN cell.

[0016] It should be noted that the techniques described herein may be implemented in and / or used with a number of 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 flight controllers, automobiles and / or motor vehicles, and various other computing devices.

[0017] This summary is intended to provide a brief overview of some of the topics described in this document. Therefore, it should be understood that the above features are only examples and should not be construed as narrowing the scope or essence of the topics described herein in any way. Other features, aspects, and advantages of the topics described herein will become apparent through the following detailed description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] A better understanding of the present subject matter can be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0019] Figure 1 An example (and simplified) wireless communication system is shown according to some embodiments;

[0020] Figure 2 illustrates an example base station in communication with an example wireless user equipment (UE) device according to some embodiments;

[0021] Figure 3 shows an example block diagram of a UE according to some embodiments;

[0022] Figure 4 shows an example block diagram of a base station according to some embodiments;

[0023] Figure 5 shows an example block diagram of a cellular network element according to some embodiments;

[0024] Fig. 6A is a block diagram illustrating aspects of decoupled processing for multicast and broadcast services in a wireless communication system according to some embodiments;

[0025] Figure 6B is a block diagram illustrating aspects of shared processing capabilities for multicast and broadcast services in a wireless communication system according to some embodiments;

[0026] Figure 7 is a communication flow diagram illustrating aspects of an example method for a base station (BS) to coordinate multicast and broadcast service delivery based on specific UE capabilities according to some embodiments;

[0027] Figure 8 is a communication flow diagram illustrating aspects of an example method for a UE for conflict avoidance / mitigation related to multicast and broadcast services in a wireless communication system according to some embodiments; and

[0028] Figures 9 to 17 Additional example aspects and various possible approaches to conflict avoidance / mitigation related to multicast and broadcast services in wireless communication systems according to some embodiments are shown.

[0029] Although 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 described in detail herein. However, it should be understood that the drawings and detailed description thereof are not intended to be limited to the specific forms disclosed, but on the contrary, are intended to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0030] Acronyms

[0031] Various acronyms are used throughout this disclosure. Definitions of the most commonly used acronyms that may appear throughout this disclosure are provided below:

[0032] •UE: User Equipment

[0033] •RF: Radio Frequency

[0034] •BS: Base Station

[0035] •GSM: Global System for Mobile Communications

[0036] •UMTS: Universal Mobile Telecommunications System

[0037] • LTE: Long Term Evolution

[0038] •NR: New Radio

[0039] •TX: Send

[0040] •RX: Receive

[0041] • RAT: Radio Access Technology

[0042] •TRP: Transmit Receive Point

[0043] •gNB: Next Generation Node B

[0044] •PRB: Physical Resource Block

[0045] •DL: Downlink

[0046] •NW: Network

[0047] •RRC: Radio Resource Control

[0048] •CC: Component Carrier

[0049] •DC: Dual Connection

[0050] •SCG: Secondary Cell Group

[0051] •MBS: Multicast and Broadcast Service

[0052] •SCell: Secondary cell

[0053] • PCell: Primary cell

[0054] • SIB: System Information Block

[0055] •MCCH: Multicast Control Channel

[0056] •MTCH: Multicast Traffic Channel

[0057] •MBMS: Multimedia Broadcast Multicast Service

[0058] •TMGI: Temporary Mobility Group Identifier

[0059] •TDM: Time Domain Multiplexing

[0060] •FDM: Frequency Domain Multiplexing

[0061] •PLMN: Public Land Mobility Network

[0062] • BW: Bandwidth

[0063] •BWP: Bandwidth Part

[0064] • SCS: Subcarrier Spacing

[0065] •DRX: Discontinuous Reception

[0066] • L1: Layer 1

[0067] • L2: Layer 2

[0068] • L3: Layer 3

[0069] •MAC-CE: Medium Access Control – Control Element

[0070] •QCL: Quasi Co-sited

[0071] • NID: Network Identifier

[0072] •UAI: UE Assistance Information

[0073] the term

[0074] The following is a glossary of terms that may appear in this disclosure:

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

[0076] Carrier Media—Memory media as described above, and physical transmission media such as a bus, network, and / or other physical transmission media that convey signals such as electrical, electromagnetic, or digital signals.

[0077] 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 appliance, an Internet appliance, a personal digital assistant (PDA), a television system, a grid computing system, or other devices or combinations of devices. In general, the term "computer system" may be broadly defined as any device (or combination of devices) that includes at least one processor that executes instructions from a memory medium.

[0078] User Equipment (UE) (or "UE device") - any of various types of computer systems or devices that are mobile or portable and that perform wireless communications. Examples of UE devices include mobile phones or smart phones (e.g., iPhone ™ , based on Android ™ 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" can be broadly defined to cover any electronic device, computing device, and / or telecommunication device (or combination of these devices) that is easily transportable by a user and capable of wireless communication.

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

[0080] Communication device - any of various types of computer systems or devices that perform communication, where the communication can be wired or wireless. A communication device can be portable (or mobile), or can be stationary or fixed at a location. A wireless device is an example of a communication device. A UE is another example of a communication device.

[0081] Base Station (BS)—The term “base station” has the full breadth of its ordinary meaning and includes at least a wireless communication station installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

[0082] Processing element (or processor) - refers to any element or combination of elements that is capable of performing functions in a device (e.g., a user equipment device or a cellular network device). Processing elements may include, for example, processors and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as ASICs (application specific integrated circuits), programmable hardware elements such as field programmable gate arrays (FPGAs), and any of the above combinations.

[0083] 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 these 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.

[0084] Automatically—refers to an action or operation being performed by a computer system (e.g., software executed by a computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without the action or operation being directly specified or performed by a user input. Thus, the term "automatically" is in contrast to an operation being manually performed or specified by a user, where the user provides input to directly perform the operation. An automatic process may be initiated by input provided by a user, but subsequent actions performed "automatically" are not specified by the user, i.e., are not performed "manually," where the user specifies 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 in information, selecting check boxes, radio selections, etc.) is manually filling out the form, even though the computer system must update the form in response to user actions. The form may be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills out the form without any user input specifying the answers to the fields. As indicated above, a user may invoke automatic filling out of a form, but not participate in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields but they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions that a user has taken.

[0085] Configured to—Various components may be described as being “configured to” perform one or more tasks. In such contexts, “configured to” is a broad statement that generally means “having a structure” that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently performing the task (e.g., a collection of electrical conductors can 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 statement that generally means “having a circuit” that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently turned on. Typically, circuits that form a structure corresponding to “configured to” may include hardware circuits.

[0086] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted to include the phrase "configured to". The statement that a component is configured to perform one or more tasks is expressly intended not to invoke the interpretation of 35 U.S.C. § 112, sixth paragraph, for that component.

[0087] Figure 1 and Figure 2 —Example Communication System

[0088] Figure 1 An example (and simplified) wireless communication system is shown in which various aspects of the present disclosure may be implemented according to some embodiments. Note that Figure 1The system is only one example of a possible system, and the embodiments may be implemented in any of a variety of systems as desired.

[0089] As shown, the example 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 via a transmission medium. Each user device may be referred to herein as a "user equipment" (UE) or a UE device. Therefore, the user device 106 is referred to as a UE or a UE device.

[0090] The base station 102 may be a base transceiver station (BTS) or a cell site, and may include hardware and / or software that implements wireless communication with the UEs 106A to 106N. If the base station 102 is implemented in the context of LTE, it may 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 a network 100 (e.g., a core network of a cellular service provider, a telecommunications network such as a public switched telephone network (PSTN), and / or the Internet, as well as various possible networks). Thus, the base station 102 may facilitate communication between user devices and / or between 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, with respect to a UE, sometimes a base station may be considered to represent a network in consideration of the uplink and downlink communications of the UE. Therefore, a UE that communicates with one or more base stations in a network may also be understood as a UE that communicates with a network.

[0091] The base station 102 and the user equipment 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 telecommunication standards, such as GSM, UMTS (WCDMA), LTE, Advanced LTE (LTE-A), LAA / LTE-U, 5G NR, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, and the like.

[0092] Base station 102 and other similar base stations operating according to the same or different cellular communication standards may thus be provided as one or more cell networks that may provide continuous or nearly continuous overlapping service to UE 106 and similar devices over a geographic area via one or more cellular communication standards.

[0093] Note that UE 106 is capable of communicating using multiple wireless communication standards. For example, UE 106 may be configured to communicate using either or both of the 3GPP cellular communication standard or the 3GPP2 cellular communication standard. In some embodiments, UE 106 may be configured to perform techniques for receiving multicast and broadcast services in a wireless communication system with radio access network sharing, such as according to the various methods described herein. UE 106 may also or alternatively be configured to use WLAN, Bluetooth, or other wireless communication standards. ™ , one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one and / or more mobile television broadcast standards (e.g., ATSC-M / H), etc. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0094] Figure 2 An example user equipment 106 (e.g., one of devices 106A to 106N) is shown in communication with a base station 102 according to some embodiments. 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 computer, an unmanned aerial vehicle (UAV), an unmanned flight controller (UAC), a car, or virtually any type of wireless device. UE 106 may include a processor (processing element) configured to execute program instructions stored in a memory. UE 106 may perform any method implementation in the method implementation described herein by executing such stored instructions. Alternatively or in addition, UE 106 may include a programmable hardware element, such as an FPGA (field programmable gate array), an integrated circuit, and / or any of a variety of other possible hardware components configured to perform (e.g., individually or in combination) any method implementation in the method implementation described herein or any part of any method implementation in the method implementation described herein. UE 106 may be configured to communicate using any of a plurality of wireless communication protocols. For example, 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 also possible.

[0095] 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, UE 106 may share one or more parts of a receive chain and / or a transmit chain between multiple wireless communication standards. The shared radio component may include a single antenna, or may include multiple antennas (e.g., for a multiple-input, multiple-output or "MIMO" antenna system) for performing wireless communications. Typically, the radio component may include any combination of a baseband processor, an analog RF signal processing circuit (e.g., including filters, mixers, oscillators, amplifiers, etc.), or a digital processing circuit (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more parts of a receive chain and / or a transmit chain between multiple wireless communication technologies such as those discussed above.

[0096] In some embodiments, UE 106 may include any number of antennas and may be configured to use the antennas to send and / or receive directional wireless signals (e.g., beams). Similarly, BS 102 may also include any number of antennas and may be configured to use the antennas to send and / or receive directional wireless signals (e.g., beams). In order to receive and / or send such directional signals, the antennas of UE 106 and / or BS 102 may be configured to apply different "weights" to different antennas. The process of applying these different weights may be referred to as "pre-coding".

[0097] In some embodiments, the UE 106 may include a separate transmit chain and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As another possibility, the UE 106 may include one or more radio components shared between multiple wireless communication protocols, and one or more radio components used uniquely by a single wireless communication protocol. For example, the UE 106 may include a shared radio component for communicating using any of LTE or CDMA2000 1xRTT (or LTE or NR, or LTE or GSM), and a shared radio component for communicating using Wi-Fi and Bluetooth. ™ Each of the radio components communicates with each other. Other configurations are also possible.

[0098] Figure 3 —Block diagram of an example UE device

[0099] Figure 3A block diagram of an example UE 106 according to some embodiments is shown. As shown, the UE 106 may include a system on chip (SOC) 300, which may include parts for various purposes. For example, as shown, the SOC 300 may include a processor 302 that may execute program instructions for the UE 106, and a display circuit 304 that 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 various possible characteristics or parameters of the UE 106. For example, the sensor circuit 370 may include a motion sensing circuit that is configured to detect the motion of the UE 106, for example, using a gyroscope, an accelerometer, and / or any of various other motion sensing components. As another possibility, the sensor circuit 370 may include one or more temperature sensing components, for example, for measuring the temperature of each of one or more antenna panels and / or other components of the UE 106. Any of the various other possible types of sensor circuits may also or alternatively be included in the UE 106, as desired. Processor 302 may also be coupled to a memory management unit (MMU) 340, which may be configured to receive addresses from processor 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310) and / or other circuits or devices, such as display circuit 304, radio 330, connector I / F 320, and / or display 360. MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, MMU 340 may be included as part of processor 302.

[0100] As shown, SOC 300 can be coupled to various other circuits of UE 106. For example, UE 106 may include various types of memory (e.g., including NAND flash memory 310), connector interface 320 (e.g., for coupling to a computer system, a docking station, a charging station, etc.), 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 may include multiple antennas (e.g., illustrated by antennas 335a and 335b) for performing wireless communications 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. In general, one or more antennas are collectively referred to as antennas 335. For example, the UE device 106 may use antennas 335 with the aid of radio circuits 330 to perform wireless communications. The wireless communication circuit 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 perform wireless communications using multiple wireless communication standards.

[0101] The UE 106 may include hardware and software components for implementing the method for the UE 106 to perform techniques such as those described further below in this document for receiving multicast and broadcast services in a wireless communication system with radio access network sharing. The processor 302 of the UE device 106 may be configured to implement part 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 302 may be configured as a programmable hardware element, such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit). In addition, as Figure 3 As shown, the processor 302 can be coupled to other components and / or can interoperate with other components to perform the technology for receiving multicast and broadcast services in a wireless communication system with radio access network sharing according to various embodiments disclosed herein. The processor 302 can also implement various other applications and / or end-user applications running on the UE 106.

[0102] In some embodiments, radio 330 may include a separate controller dedicated to controlling communications for each corresponding RAT standard. Figure 3 As shown, the radio component 330 may include a Wi-Fi controller 352, a cellular controller (eg, an LTE and / or LTE-A controller) 354, and a Bluetooth ™ Controller 356, and in at least some embodiments, one or more or all of these controllers may be implemented as respective integrated circuits (referred to as ICs or chips) that communicate with each other and with SOC 300 (more specifically, with processor 302). For example, Wi-Fi controller 352 may communicate with cellular controller 354 via a cell-ISM link or WCI interface, and / or Bluetooth controller 354 may communicate with the cellular controller 354 via a cell-ISM link or WCI interface.™ The controller 356 may communicate with the cellular controller 354 via a cell-ISM link, etc. Although three separate controllers are shown within the radio 330, other embodiments may be implemented in the UE device 106 having fewer or more similar controllers for various different RATs.

[0103] Additionally, embodiments are contemplated in which the controller may implement functionality associated with multiple radio access technologies. For example, according to some embodiments, in addition to hardware and / or software components for performing cellular communications, the cellular controller 354 also includes hardware and / or software components for performing one or more activities associated with Wi-Fi, such as Wi-Fi preamble detection, and / or generation and transmission of Wi-Fi physical layer preamble signals.

[0104] Figure 4 —Block diagram of an example base station

[0105] Figure 4 1 shows a block diagram of an example base station 102 according to some embodiments. Note that Figure 4 The base station of is only one example of a possible base station. As shown, the base station 102 may include a processor 404 that may execute program instructions for the base station 102. The processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuit or device, which may be configured to receive addresses from the processor 404 and convert these addresses to locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0106] Base station 102 may include at least one network port 470. Network port 470 may be configured to couple to a telephone network and provide access to the telephone network described above. Figure 1 and Figure 2 The network port 470 may be configured to couple to a plurality of devices such as the UE device 106 of the telephone network described in the foregoing. The network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to a plurality of 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., in other UE devices served by the cellular service provider).

[0107] In some embodiments, 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, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transmit and receive points (TRPs). Furthermore, a UE capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

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

[0109] The base station 102 may be configured to perform wireless communications using multiple wireless communication standards. In some examples, the base station 102 may include multiple radio components that enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio component for performing communications according to LTE and a 5G NR radio component for performing communications according to 5G NR. In this case, the base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 may include a multi-mode radio component that can perform communications according to any one 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.).

[0110] As further described later herein, BS 102 may include hardware and software components for implementing or supporting a specific implementation of the features described herein. The processor 404 of the base station 102 may be configured to implement and / or support a specific implementation of part 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 an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit) or a combination thereof. In the case of certain RATs (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 one or more local area networks, for example, it may include at least one Ethernet port, and the radio component 430 may be designed to communicate according to the Wi-Fi standard.

[0111] Furthermore, as described herein, processor 404 may include one or more processing elements. Thus, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 404.

[0112] Additionally, 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. Additionally, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio 430.

[0113] Figure 5 — Example block diagram of network elements

[0114] Figure 5 An example block diagram of a network element 500 according to some embodiments is shown. 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. Note that, Figure 5 The network element 500 is only one example of a possible network element 500. As shown, the core network element 500 may include a processor 504 that may execute program instructions of the core network element 500. The processor 504 may also be coupled to a memory management unit (MMU) 540 or other circuit or device that may be configured to receive addresses from the processor 504 and translate those addresses into locations in memory (e.g., memory 560 and read-only memory (ROM) 550).

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

[0116] As further described later herein, network element 500 may include hardware and software components for implementing or supporting implementations of the features described herein. Processor 504 of core network element 500 may be configured to implement or support implementations of part 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, processor 504 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit), or a combination thereof.

[0117] Multicast and Broadcast Service (MBS) simultaneous reception of broadcast and unicast

[0118] In some scenarios, a multicast and broadcast service (MBS) broadcast mechanism of a cellular network may provide a downlink (DL)-only MBS delivery mode for all UEs in all radio resource control (RRC) states. Additionally or alternatively, in some scenarios, a connected (e.g., in a connected state) UE may be configured to receive unicast and MBS broadcast simultaneously. However, the network (NW) may not be aware of all situations or scenarios and may require further information in order to provide unicast and MBS broadcast simultaneously.

[0119] For example, the NW may realize or determine that the UE is interested in receiving the simultaneous MBS broadcast service according to at least two methods. According to a first method, the connected UE may report UE capabilities (e.g., such as broadcast-SCell-r17 ) to indicate whether the UE supports MBS broadcast reception on the secondary cell (SCell). Therefore, if the MBS broadcast service that the UE is interested in is on the SCell supported by the UE ( broadcast-SCell-r17 ), the serving base station (e.g., gNB) may deliver a system information block of a certain format (e.g., SIBx) of the SCell to the UE. According to some embodiments, SIBx may provide a multicast control channel (MCCH) configuration on the same cell. In addition, the UE may be able to receive MBS broadcast services on the primary cell (PCell), and SIBx may be obtained by the UE itself.

[0120] According to the second method, the connected UE may report or indicate to the NW that the UE is interested in receiving simultaneous MBS broadcast information (e.g., for service continuity purposes). Therefore, the serving base station (e.g., gNB) may configure the UE (or provide configuration information) in a manner that allows the UE to use MBS broadcast to receive services of interest to the UE. For example, the UE may send an MBS interest indication to the base station for a broadcast session consisting of various information. Additionally or alternatively, the information may include a list of MBS frequencies, which may also be sorted in descending order of interest. In other words, the UE may be able to indicate a preferred MBS frequency to receive MBS transmissions on it. Additionally or alternatively, the information may include a priority between the reception of all listed Multimedia Broadcast Multicast Service (MBMS) frequencies and the reception of any unicast bearer. In addition, the information may include a list of MBS services that the UE is receiving or is interested in receiving. Enhancements to Uu signaling may be introduced to enable simultaneous unicast / MBS broadcast reception. For example, MBS-related UE capability enhancements or MBS broadcast-related auxiliary information enhancements may be made to reflect shared processing capabilities so that the UE can receive unicast / MBS broadcasts simultaneously.

[0121] FIG. 6A to FIG. 6B —Decoupling and shared processing for multicast and broadcast services

[0122] Fig. 6A is a block diagram illustrating aspects of decoupled processing for multicast and broadcast services in a wireless communication system according to some embodiments. Figure 6B is a block diagram illustrating aspects of shared processing for multicast and broadcast services in a wireless communication system according to some embodiments.

[0123] According to some scenarios, the broadcast and unicast processing units can be decoupled. Fig. 6A As shown, unicast services may be transmitted using component carrier 1 (CC1), CC2, and additional CCx, while MBS broadcast services may be transmitted using CCy. Therefore, decoupled processing will be independent for unicast (CC1, CC2, and CCx) and broadcast (CCy). Therefore, independent reception of MBS broadcast and unicast on their respective CCs may not affect each other with respect to processing capabilities.

[0124] Alternatively, for Figure 6B With the shared processing design for MBS broadcast and unicast shown, MBS broadcast reception in one CC may impact unicast processing capabilities in other CCs. For example, if the UE reports UE capabilities to reflect the shared processing design, the network may be able to optimize unicast scheduling and transmission performance in the case of simultaneous broadcast reception.

[0125] In some scenarios, the broadcast service continuity mechanism may be applicable to the same operator deployment, and the current serving base station (e.g., gNB) may be able to obtain the details of the MBS broadcast information from the MBS broadcast session context based on the reported MBS carrier or temporary mobile group identity (TMGI) information. In addition, if the MBS broadcast service of interest to the UE is from another operator or a third-party base station or gNB, the current serving base station (e.g., gNB) may not be able to obtain information from the stored context to select an appropriate serving cell / node that can provide the MBS service of interest to the UE (for service continuity purposes). According to some scenarios, if the base station knows or has determined the details of the MBS broadcast information of interest to the UE directly from the UE side, the network may be able to provide or formulate certain coordination actions between unicast and MBS broadcast in order to avoid conflict situations between broadcast transmission and unicast transmission, and also avoid degradation in performance of both transmissions.

[0126] Figure 7 —Communication of conflict avoidance / mitigation of multicast and broadcast services using MBS broadcast-specific UE capabilities flow chart

[0127] In some embodiments, MBS broadcast specific UE capability design can be contemplated for MBS broadcast transmission coordination by utilizing a specific MBS broadcast UE capability design. For example, within a band combination or feature set combination, at least one entry can be used to indicate for MBS broadcast purposes. Thus, for a carrier or feature set entry with an MBS broadcast indication, it can be used to indicate the UE capability to receive MBS broadcast there.

[0128] It may be beneficial to specify techniques for network and UE coordination as part of supporting multicast and broadcast services in wireless communication systems. To illustrate a set of such possible techniques, Figure 7 is a flow chart illustrating aspects of an example method for a base station involving communication coordination using MBS broadcast specific UE capability design and relating to multicast and broadcast services in a wireless communication system according to some embodiments.

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

[0130] Note that although the present invention is described in a manner involving the use of communication techniques and / or features associated with 3GPP and / or NR specification documents, Figure 7 However, this description is not intended to limit the present disclosure and may be used in any suitable wireless communication system as needed. Figure 7 In various embodiments, some of the elements of the method shown may be performed simultaneously in an order different from that shown, may be replaced by other method elements, or may be omitted. Additional method elements may also be performed as needed. As shown in the figure, Figure 7 The method can be operated as follows.

[0131] In 702, the BS may send a capability request to a user equipment (UE). Additionally or alternatively, the UE capability request may include MBS specific information. For example, according to some embodiments, the BS may request specific information from the UE regarding the UE's ability to receive MBS broadcast transmissions using a specific frequency band combination or feature set combination.

[0132] In 704, the BS may receive a capability report from the UE. Additionally or alternatively, the UE capability report may include an indication of supported frequency band combinations or feature set combinations that the UE may utilize to receive the MBS broadcast transmission. Furthermore, according to some embodiments, the UE may indicate a preferred frequency band combination or feature set combination to utilize for receiving the MBS broadcast transmission. For example, the capability report may include a frequency band combination and / or a feature set combination, such as BC-1 (B1 / SET1, B2 / SET2) and / or MBS BC-2 (B1 / SET3, B2 / MBS / SET4), such as Figure 7 shown.

[0133] In 706, the UE may also send MBS interest information. Additionally or alternatively, according to some embodiments, the MBS interest information may include an indication that the UE is capable of and / or prefers to use a carrier in B2 to receive MBS broadcasts. In other words, the UE may indicate to the network that the UE is capable of and will prefer to use MBS BC-2 to receive MBS broadcast transmissions.

[0134] In 708, the BS may adjust the unicast scheduling / configuration according to MBS BC-2. For example, having received the UE capability report and MBS interest information, the network (e.g., serving gNB) may adjust the unicast scheduling and / or configuration to incorporate the capabilities and / or preferred band combination / feature set indicated by the UE.

[0135] In 710, the BS may send a radio resource control (RRC) reconfiguration message to the UE. For example, in the case where the unicast scheduling and / or configuration has been adjusted, the network may need to transmit a reconfiguration control command to the UE in order for the UE to receive the broadcast. More specifically, according to some embodiments, the RRC command may indicate that the unicast should utilize a specific frequency band combination and / or feature set combination, such as B1 / SET3 as previously indicated by the UE and corresponding to MBS BC-2.

[0136] The BS may send a broadcast transmission to the UEs at 712. For example, according to some embodiments, the MBS broadcast transmission may include data associated with a particular session (eg, Session #X).

[0137] In some embodiments, Figure 7 The method may involve an MBS-specific frequency band combination or an MBS-specific feature set combination. More specifically, the frequency band combination may include N frequency bands for unicast and M frequency bands for MBS broadcast. In some embodiments, the MBS frequency band may be indicated by an MBS-specific frequency in the NR band parameter. Additionally or alternatively, the feature set combination may include N feature sets for unicast and M feature sets for MBS broadcast. In some embodiments, the MBS-specific feature set may be indicated in a DL feature set level or a DL feature set per CC level. Therefore, the MBS-specific feature set (per CC) may be used for UEs receiving MBS broadcast data.

[0138] In some embodiments, when the network (NW) is aware of MBS reception on one carrier belonging to one band combination / feature set combination, the NW may be able to use the feature set for unicast in the same band combination / feature set combination. Additionally or alternatively, for MBS specific band combinations, the UE may be able to indicate the MBS band / CC information, and thus may not need to provide parameters in further detail.

[0139] According to some embodiments, dynamic UE capability reporting may be considered, such that the dynamic reporting can be triggered by the NW or the UE itself. Additionally or alternatively, according to some embodiments, UE reporting may be able to be based on MBS broadcast carrier changes.

[0140] Thus, at least according to some embodiments, Figure 7 The method may be used to provide a framework according to which, at least in some cases, a base station may be configured to perform coordination tasks for multicast and broadcast services in a wireless communication system.

[0141] Figure 8 — Conflict avoidance / reduction of multicast and broadcast services using UE assistance information associated with MBS broadcast Light communication flow chart

[0142] It may be further beneficial to specify techniques for conflict avoidance / mitigation as part of supporting multicast and broadcast services in wireless communication systems. To illustrate a set of such possible techniques, Figure 8 is a flow chart illustrating aspects of an example method for a user equipment involving conflict avoidance / mitigation designed using UE assistance information associated with MBS broadcasts and relating to multicast and broadcast services in a wireless communication system, according to some embodiments.

[0143] Figure 8 Various aspects of the method may be implemented by a wireless device, for example, in conjunction with one or more cellular base stations and / or other cellular network elements (such as UE 106, BS 102, and cellular network element 500 shown in and described with respect to the various figures herein), or more generally, in conjunction with any of the computer circuits, systems, devices, elements, or components shown in the above figures, etc., as desired. For example, a processor (and / or other hardware) of such a device may be configured to cause the device to perform any combination of the illustrated method elements and / or other method elements.

[0144] It is noted that although the present invention is described in a manner involving the use of communication techniques and / or features associated with 3GPP and / or NR specification documents, Figure 8 However, this description is not intended to limit the present disclosure and may be used in any suitable wireless communication system as needed. Figure 8 In various embodiments, some of the elements of the method shown may be performed simultaneously in an order different from that shown, may be replaced by other method elements, or may be omitted. Additional method elements may also be performed as needed. As shown in the figure, Figure 8 The method can be operated as follows.

[0145] In 802, the UE may receive a radio resource control (RRC) configuration message from a serving base station on a first component carrier (CC1). Additionally or alternatively, according to some embodiments, the RRC configuration message may include an indication or information about the transmission or reception of MBS transmission. In other words, the network may indicate to the UE that CC1 configured for the UE is used for MBS reception. Therefore, the UE may follow the NW indication to perform MBS configuration acquisition and data reception there (e.g., using CC1).

[0146] At 804, the UE may receive a transmission from a multicast and broadcast service (MBS) BS. In addition, the transmission from the MBS BS may be on CC1 and may also include information about the MBS unicast and / or broadcast transmission. For example, according to some embodiments, the transmission may include one or more system information blocks (SIBs) (e.g., SIBX), information corresponding to a multicast control channel (MCCH), and / or configuration information corresponding to a multicast traffic channel (MTCH).

[0147] In 806, the UE may determine a conflict between the unicast transmission and the broadcast transmission. For example, according to some embodiments, the UE may utilize information from the transmissions of 802 and 804 of the serving gNB and the MBS gNB to determine that a resource conflict may occur between the unicast transmission and the broadcast transmission. Furthermore, the conflict may result in degraded transmission performance corresponding to both the unicast transmission and the broadcast transmission. Therefore, according to some embodiments, the UE may seek to avoid the degradation.

[0148] In 808, the UE may send an indication of interest to the MBS BS. For example, according to some embodiments, the UE may send information including the indication of interest to the MBS BS and also include an indication of a preference corresponding to a preferred MBS carrier (e.g., CC1), a preferred bandwidth (e.g., BW=X), a preferred subcarrier spacing (e.g., SCS=Y), or a preferred discontinuous reception (DRX) mode. Additionally or alternatively, according to some embodiments, these indications of preference may be copied from the MTCH configuration received by the UE in 804.

[0149] In 810, the network may realize or determine that the UE is capable of operating on CC1 for MBS and CC2 for unicast. For example, according to some embodiments, the MBS BS may utilize the provided information of 808 to configure unicast to utilize CC2 and / or configure MBS broadcast to use CC1.

[0150] The UE may receive an RRC reconfiguration on a second CC (eg, CC2) from an MBS BS corresponding to the serving cell at 812. Thus, according to some embodiments, the UE may utilize an RRC reconfiguration command so that the UE may receive unicast on CC2 and MBS broadcast on CC1.

[0151] In some embodiments, UE assistance information enhancement (e.g., MBS broadcast associated UE assistance information design) may include details of the UE reporting the MBS broadcast information of interest to the network. For example, the UE may report the information via UE-specific signaling. In addition, the information may include MBS interest information, UE assistance information, layer 3 (L3) signaling, layer 2 (L2) medium access control-control element (MAC-CE) signaling, and / or layer 1 (L1) signaling.

[0152] According to some embodiments, details of the MBS broadcast information of interest may include MBS broadcast information such as MBS carriers, MBS broadcast information for third-party broadcast reception and / or transmission resources (from MTCH configuration in the MBS carrier / cell) such as frequency location, bandwidth (BW), subcarrier spacing (SCS) and / or discontinuous reception (DRX) or data service mode.

[0153] Additionally or alternatively, the MBS broadcast information of interest may include a preferred unicast scheduling / transmission configuration (to avoid conflicts with MBS broadcasts). In some embodiments, the MBS broadcast information of interest may include UE preferred BWP, serving cell activation / deactivation, transmission mode and / or dual connectivity (DC) configuration.

[0154] In addition, when the UE is able to predict the conflict between unicast and broadcast based on the configuration, the UE may be able to report information. Additionally or alternatively, for the unicast part, the conflict prediction may be based on the activated or configured bandwidth part (BWP), secondary cell (SCell) or secondary cell group (SCG). In some embodiments, the UE may also report information without such conflict prediction. Additionally or alternatively, the process may be implemented by the network via explicit signaling (e.g., explicit signaling in a SIB or dedicated RRC configuration). According to some embodiments, the report may be retriggered when the MBS broadcast service of interest to the UE is changed. Additionally or alternatively, according to some embodiments, a prohibition timer may be configured to control the reporting frequency.

[0155] Thus, at least according to some embodiments, Figure 8 The method may be used to provide a framework according to which, at least in some cases, user equipment can be configured to perform conflict avoidance / mitigation related tasks for multicast and broadcast services in a wireless communication system.

[0156] Figures 9 to 17 —Additional information and implementation schemes for conflict avoidance / mitigation of multicast and broadcast services

[0157] Figures 9 to 17 Example aspects of various possible approaches to conflict avoidance / mitigation related to multicast and broadcast services in a wireless communication system are shown in accordance with some embodiments.

[0158] Figures 9 to 17Aspects of the methods of can be implemented by a wireless device, for example, in conjunction with one or more cellular base stations and / or other cellular network elements (such as UE 106, BS 102, and cellular network element 500 shown in and described with respect to the various figures herein), or more generally, in conjunction with any of the computer circuits, systems, devices, elements, or components shown in the above figures, etc., as desired. For example, a processor (and / or other hardware) of such a device can be configured to cause the device to perform any combination of the illustrated method elements and / or other method elements.

[0159] Note that although the present invention is described in a manner involving the use of communication techniques and / or features associated with 3GPP and / or NR specification documents, Figures 9 to 17 However, such description is not intended to limit the present disclosure and may be used in any suitable wireless communication system as required. Figures 9 to 17 In various embodiments, some of the elements of the method shown may be performed simultaneously in an order different from that shown, may be replaced by other method elements, or may be omitted. Additional method elements may also be performed as needed. As shown in the figure, Figures 9 to 17 The method can be operated as follows.

[0160] Fig. 9 is a communication flow diagram illustrating various aspects of multicast and broadcast service broadcasts based on a UE assistance information design associated with an MBS broadcast. More specifically, Fig. 9 It is shown how the described collision avoidance / mitigation of unicast and broadcast transmissions may be performed using time domain multiplexing (TDM) scheduling based on a preferred DRX configuration.

[0161] For example, in 902, a UE in a connected state may receive a radio resource control (RRC) configuration message from a serving base station (gNB) on a first component carrier (CC1). Additionally or alternatively, according to some embodiments, the RRC configuration message may include an indication or information about the transmission or reception of MBS transmission. In other words, the network may indicate to the UE that CC1 configured for the UE is used for MBS reception. Therefore, the UE may follow the NW indication to perform MBS configuration acquisition and data reception there (e.g., using CC1).

[0162] At 904, the UE may receive a transmission from a multicast and broadcast service (MBS) BS. In addition, the transmission from the MBS BS may be on CC1 and may also include information about the MBS unicast and / or broadcast transmission. For example, according to some embodiments, the transmission may include one or more system information blocks (SIBs) (e.g., SIBX), information corresponding to a multicast control channel (MCCH), and / or configuration information corresponding to a multicast traffic channel (MTCH).

[0163] At 906, the UE may determine a conflict between the unicast transmission and the broadcast transmission. For example, according to some embodiments, the UE may utilize information from the transmissions of 902 and 904 of the serving gNB and the MBS gNB to determine that a resource conflict may occur between the unicast transmission and the broadcast transmission. Furthermore, the conflict may result in degraded transmission performance corresponding to both the unicast transmission and the broadcast transmission. Therefore, according to some embodiments, the UE may seek to avoid the degradation.

[0164] In 908, the UE may send an indication of interest to the MBS BS. For example, according to some embodiments, the UE may send information including the indication of interest to the MBS BS, and also include an indication of the following: a preference corresponding to a preferred MBS carrier (e.g., CC1), an MTCH DRX configuration (including periodicity, offset, and duration), and a switching time / gap corresponding to unicast and broadcast transmissions. Additionally or alternatively, according to some embodiments, these indications of preference and / or information may be copied from the MTCH configuration received by the UE in 904.

[0165] In 910, the UE may receive an RRC reconfiguration message including information corresponding to the DRX configuration from the serving gNB. Thus, according to some embodiments, the UE may utilize the RRC reconfiguration and DRX configuration information so that the UE may expect to receive unicast from the serving gNB and MBS broadcast from the MBS gNB according to a certain schedule.

[0166] In 912, according to some embodiments, the network may perform time domain multiplexing (TDM) scheduling according to the DRX configuration provided in 910 so that conflicts are avoided and the UE receives unicast from the serving gNB and MBS broadcast corresponding to the appropriate scheduling from the MBS gNB.

[0167] Fig.10 An example scenario is shown in which a UE can use a UE assistance information design associated with an MBS broadcast to implement collision avoidance / mitigation for MBS. More specifically, Fig.10 It is shown how the described collision avoidance / mitigation of unicast and broadcast transmissions may be performed using frequency domain multiplexing (FDM) scheduling based on a preferred MTCH configuration.

[0168] For example, in 1002, a UE in a connected state may receive a radio resource control (RRC) configuration message from a serving base station (gNB) on a component carrier (CC3). Additionally or alternatively, according to some embodiments, the RRC configuration message may include an indication or information about the transmission or reception of MBS transmission. In other words, the network may indicate to the UE that CC3 configured for the UE is used for MBS reception. Therefore, the UE may follow the NW indication to perform MBS configuration acquisition and data reception there (e.g., using CC3).

[0169] At 1004, the UE may receive a transmission from a multicast and broadcast service (MBS) BS. In addition, the transmission from the MBS BS may be on a different component carrier (e.g., CC1) than the transmission of 1002 (e.g., CC3) and also include information about the MBS unicast transmission and / or the broadcast transmission. For example, according to some embodiments, the transmission may include one or more system information blocks (SIBs) (e.g., SIBX), information corresponding to a multicast control channel (MCCH), and / or configuration information corresponding to a multicast traffic channel (MTCH).

[0170] In 1006, the UE may determine or know that it cannot receive unicast on CC3 and broadcast data on CC1. For example, the information provided in 1002 and 1004 may indicate that unicast will be received on CC3 and broadcast data will be received on CC1, but the UE may lack the radio frequency (RF) capability to receive unicast and broadcast using these indicated CCs. However, according to some embodiments, the UE may support different CC configurations to receive unicast and broadcast transmissions. For example, according to some embodiments, the UE may support receiving broadcast on CC1 and receiving unicast on CC2.

[0171] Thus, in 1008, the UE may send an indication of interest to the serving BS (e.g., gNB). For example, according to some embodiments, the UE may send information including the indication of interest to the serving gNB, and also include an indication of the following: a preference corresponding to a preferred MBS carrier (e.g., CC1), and an MTCH configuration (including frequency, bandwidth, and subcarrier spacing) corresponding to unicast and broadcast transmissions. Additionally or alternatively, according to some embodiments, these indications of preferences and / or information may be copied from the MTCH configuration received by the UE in 1004.

[0172] At 1010, the UE may receive an RRC reconfiguration message from the serving gNB on a second CC (e.g., CC2). The RRC reconfiguration message may include information corresponding to a configuration based on the indication provided from the UE to the serving gNB at 1008 and corresponding to receiving a broadcast transmission on CC1 and receiving a unicast transmission on CC2.

[0173] In 1012, the network may determine or know the capabilities of the UE based on the received indication provided by the UE in 1008. Therefore, according to some embodiments, the UE may also receive unicast from the serving gNB on CC2 and MBS broadcast from the MBS gNB on CC1. In other words, when the NW receives the indicated information as detailed in 1008, the NW may be able to reconfigure the serving cell from CC3 to CC2 so that the transmission of unicast and broadcast can be properly received by the UE, because the UE supports CC1 and CC2 instead of CC1 and CC3.

[0174] Fig.11 Another example scenario is shown in which a UE can use the UE assistance information design associated with the MBS broadcast to achieve collision avoidance / mitigation for MBS. More specifically, Fig.11 It is shown how the described collision avoidance / mitigation with respect to unicast and broadcast transmissions may be performed using time domain multiplexing (TDM) scheduling based on a preferred DRX configuration.

[0175] For example, in 1102, a UE in a connected state may receive a radio resource control (RRC) configuration message from a serving base station (gNB) on a first component carrier (CC1). Additionally or alternatively, according to some embodiments, the RRC configuration message may include an indication or information about the transmission or reception of MBS transmission. In other words, the network may indicate to the UE that CC1 configured for the UE is used for MBS reception. Therefore, the UE may follow the NW indication to perform MBS configuration acquisition and data reception there (e.g., using CC1).

[0176] At 1104, the UE may receive a transmission from a multicast and broadcast service (MBS) BS. In addition, the transmission from the MBS BS may be on CC1 and may also include information about the MBS unicast and / or broadcast transmission. For example, according to some embodiments, the transmission may include one or more system information blocks (SIBs) (e.g., SIBX), information corresponding to a multicast control channel (MCCH), and / or configuration information corresponding to a multicast traffic channel (MTCH).

[0177] In 1106, the UE may determine a conflict between the unicast transmission and the broadcast transmission. For example, according to some embodiments, the UE may utilize information from the transmissions of 1102 and 1104 of the serving gNB and the MBS gNB to determine that a resource conflict may occur between the unicast transmission and the broadcast transmission. Furthermore, the conflict may result in degraded transmission performance corresponding to both the unicast transmission and the broadcast transmission. Therefore, according to some embodiments, the UE may seek to avoid the degradation.

[0178] In 1108, the UE may send UE assistance information (UAI) to the MBS BS. For example, according to some embodiments, the UE may send information including: a preference corresponding to a preferred MBS carrier (e.g., CC1), a preferred DRX configuration (for unicast transmissions), and a switching time / slot corresponding to unicast and broadcast transmissions. Additionally or alternatively, according to some embodiments, these indications of preferences and / or information may be copied from the MTCH configuration received by the UE in 1104.

[0179] In 1110, the UE may receive an RRC reconfiguration message including information corresponding to a specific DRX configuration from the serving gNB. Thus, according to some embodiments, the UE may utilize the RRC reconfiguration and DRX configuration information such that the UE may expect to receive unicast from the serving gNB and MBS broadcast from the MBS gNB according to a certain schedule.

[0180] In 1112, according to some embodiments, the network may perform time domain multiplexing (TDM) scheduling according to the DRX configuration provided in 1110 such that conflicts are avoided and the UE receives unicast from the serving gNB and MBS broadcast corresponding to the appropriate scheduling from the MBS gNB. In other words, when the network (NW) receives appropriate UAI information from the UE, the NW may be able to perform unicast scheduling in a TDM manner such that resource conflicts corresponding to the MBS broadcast and unicast transmissions are avoided.

[0181] Fig.12 Another example scenario in which a UE can use the UE assistance information design associated with the MBS broadcast to achieve collision avoidance / mitigation for MBS is shown. More specifically, Fig.12 It is shown how the network can perform frequency domain multiplexing (FDM) scheduling according to the specified and preferred serving cell frequency configuration in order to achieve collision avoidance / mitigation for unicast and broadcast transmissions.

[0182] For example, in 1202, a UE in a connected state may receive a radio resource control (RRC) configuration message from a serving base station (gNB) on a component carrier (CC3). Additionally or alternatively, according to some embodiments, the RRC configuration message may include an indication or information about the transmission or reception of MBS transmission. In other words, the network may indicate to the UE that CC3 configured for the UE is used for MBS reception. Therefore, the UE may follow the NW indication to perform MBS configuration acquisition and data reception there (e.g., using CC3).

[0183] At 1204, the UE may receive a transmission from a multicast and broadcast service (MBS) BS. In addition, the transmission from the MBS BS may be on a different component carrier (e.g., CC1) than the transmission of 1202 (e.g., CC3) and also include information about the MBS unicast and / or broadcast transmission. For example, according to some embodiments, the transmission may include one or more system information blocks (SIBs) (e.g., SIBX), information corresponding to a multicast control channel (MCCH), and / or configuration information corresponding to a multicast traffic channel (MTCH).

[0184] In 1206, the UE may determine or know that it cannot receive unicast on CC3 and broadcast data on CC1. For example, the information provided in 1202 and 1204 may indicate that unicast will be received on CC3 and broadcast data will be received on CC1, but the UE may lack the radio frequency (RF) capability to receive unicast and broadcast using these indicated CCs. However, according to some embodiments, the UE may support different CC configurations to receive unicast and broadcast transmissions. For example, according to some embodiments, the UE may support receiving broadcast on CC1 and receiving unicast on CC2.

[0185] Thus, in 1208, the UE may send UE assistance information (UAI) to the serving BS (e.g., gNB). In addition, according to some embodiments, the UAI may include a preference corresponding to a preferred MBS carrier (e.g., CC1) and a preferred serving cell configuration or frequency (e.g., CC) corresponding to unicast transmission. For example, the UAI may indicate that the preferred serving cell frequency is CC2.

[0186] In 1210, the UE may receive an RRC Reconfiguration message from the serving gNB on a second CC (e.g., CC2). The RRC Reconfiguration message may include information corresponding to a configuration based on the UAI provided from the UE to the serving gNB in ​​1208 and corresponding to receiving broadcast transmissions on CC1 and receiving unicast transmissions on CC2 instead of CC3. Thus, according to some embodiments, the UE may use the RRCReconfiguration information to appropriately receive unicast from the serving gNB on CC2 and MBS broadcast from the MBS gNB on CC1. In other words, when the NW receives the indicated information as detailed in 1208, the NW may be able to reconfigure the serving cell from CC3 to CC2 such that conflicts of unicast and broadcast transmissions are avoided.

[0187] Fig.13 An example scenario is shown in which a UE can use a UE assistance information design associated with an MBS broadcast to implement collision avoidance / mitigation for MBS. More specifically, Fig.13It is shown how the network can perform frequency domain multiplexing (FDM) scheduling according to a specified and preferred BWP configuration in order to achieve collision avoidance / mitigation for unicast and broadcast transmissions.

[0188] For example, in 1302, a UE in a connected state may receive a radio resource control (RRC) configuration message from a serving base station (gNB) on a first component carrier (CC1). In addition, the RRC message may include information about using certain bandwidth parts (e.g., BWP#1, BWP#2) to receive unicast and broadcast data. Additionally or alternatively, according to some embodiments, the RRC configuration message may include an indication or information about the transmission or reception of MBS transmissions. In other words, the network may indicate to the UE that CC1 configured for the UE is used for MBS reception. Therefore, the UE may follow the NW indication to perform MBS configuration acquisition and data reception there (e.g., using CC1).

[0189] At 1304, the UE may receive a transmission from a multicast and broadcast service (MBS) BS. In addition, the transmission from the MBS BS may be on CC1 and may also include information about the MBS unicast and / or broadcast transmission. For example, according to some embodiments, the transmission may include one or more system information blocks (SIBs) (e.g., SIBX), information corresponding to a multicast control channel (MCCH), and / or configuration information corresponding to a multicast traffic channel (MTCH).

[0190] In 1306, the UE may determine or know that it cannot receive broadcast data on CC1 and use BWP#2 to receive unicast on CC1. For example, the information provided in 1302 and 1304 may indicate that BWP#1 or BWP#2 will be used to receive unicast on CC1, and broadcast data will also be received on CC1. In addition, according to some embodiments, the UE may lack the radio frequency (RF) capability to receive unicast on CC1 using BWP#2. However, the UE may support different CC configurations to receive unicast and broadcast transmissions. For example, according to some embodiments, the UE may support receiving broadcast on CC1 and using BWP#1 to receive unicast on CC1.

[0191] In 1308, the UE may send UE assistance information (UAI) to the MBS BS. For example, according to some embodiments, the UE may send information including a preference corresponding to a preferred MBS carrier (e.g., CC1), and a preferred BWP configuration (for unicast transmission). For example, according to some embodiments, the UAI may indicate that the UE prefers and / or supports BWP#1 for receiving unicast on CC1.

[0192] In 1310, the UE may receive signaling including information about the deconfiguration or deactivation of BWP#2 from the serving gNB. Thus, according to some embodiments, in the case where BWP#2 is deactivated or deconfigured, the UE may use the indicated and preferred BWP#1 (rather than the unsupported BWP#2) to receive unicast from the serving gNB on CC1 and MBS broadcast from the MBS gNB on CC1. In other words, according to some embodiments, the network may perform frequency domain multiplexing (FDM) scheduling according to the specified and preferred BWP configuration provided in 1308 (e.g., using BWP#1) so that conflicts are avoided, and the UE receives unicast from the serving gNB and MBS broadcast corresponding to the appropriate scheduling from the MBS gNB. In other words, when the network (NW) receives appropriate UAI information from the UE, the NW may be able to perform unicast scheduling in an FDM manner so that resource conflicts corresponding to MBS broadcast and unicast transmissions are avoided.

[0193] Fig.14 An example scenario is shown in which a UE can use a UE assistance information design associated with an MBS broadcast to implement collision avoidance / mitigation for MBS. More specifically, Fig.14 It is shown how the collision avoidance / mitigation may be performed utilizing frequency domain multiplexing (FDM) of preferred unicast information of the MBS broadcast information.

[0194] For example, in 1402, a UE in a connected state may receive a radio resource control (RRC) configuration message from a serving base station (gNB) on a component carrier (CC2). Additionally or alternatively, according to some embodiments, the RRC configuration message may include an indication or information about the transmission or reception of MBS transmission. In other words, the network may indicate to the UE that CC2 configured for the UE is used for MBS reception. Therefore, the UE may follow the NW indication to perform MBS configuration acquisition and data reception there (e.g., using CC2).

[0195] At 1404, the UE may receive a transmission from a multicast and broadcast service (MBS) BS. In addition, the transmission from the MBS BS may be on a different component carrier (e.g., CC1) than the transmission of 1402 (e.g., CC2) and also include information about the MBS unicast and / or broadcast transmission. For example, according to some embodiments, the transmission may include one or more system information blocks (SIBs) (e.g., SIBX), information corresponding to a multicast control channel (MCCH), and / or configuration information corresponding to a multicast traffic channel (MTCH).

[0196] In 1406, the UE may determine or know that it cannot receive unicast on CC2 (under certain conditions) and broadcast data on CC1. For example, the information provided in 1402 and 1404 may indicate that broadcast data will be received on CC1 and that certain physical resource blocks (PRBs) will be used to receive unicast on CC2. However, the UE may lack the radio frequency (RF) capability to receive unicast using a specific number or range (e.g., XY) of PRBs. In addition, according to some embodiments, the UE may support different CC2 configurations to receive unicast and broadcast transmissions by excluding unsupported PRBs.

[0197] Therefore, the UE may send UE assistance information (UAI) to the serving BS (e.g., gNB) in 1408. In addition, according to some embodiments, the UAI may include a preference corresponding to a preferred MBS carrier (e.g., CC1) and a preference to exclude a certain number or range of PRBs (e.g., PRB XY) from the configured bandwidth.

[0198] In 1410, the UE may receive an RRC Reconfiguration message from the serving gNB on a second CC (e.g., CC2). The RRC Reconfiguration message may include information corresponding to the reconfiguration of CC2 based on the UAI provided from the UE to the serving gNB in ​​1408 and corresponding to the exclusion of PRB XY from CC2. Thus, according to some embodiments, the UE may use the RRCReconfiguration information to properly receive unicast (without using PRB XY) from the serving gNB on CC2 and MBS broadcast from the MBS gNB on CC1. For example, when the NW receives the indicated information as detailed in 1408, the serving gNB may be able to reconfigure the serving cell CC2 to exclude the unsupported PRB XY so that unicast and broadcast transmissions may be successfully received.

[0199] In other words, if unicast is scheduled / configured in the PRB range (xy) of CC2, the UE may not be able to receive MBS and unicast on CC1. In addition, the UE may then provide the network with non-preferred PRBs for unicast information (or equivalent information about preferred PRB frequency locations). Therefore, according to some embodiments, when the network receives the information, the NW may be able to reconfigure CC2 so as to exclude the frequency location of the PRB range (xy) from the configured BW, and thus avoid conflicts between unicast transmissions and broadcast transmissions from occurring.

[0200] Fig.15 Another example scenario in which a UE can use the UE assistance information design associated with the MBS broadcast to achieve collision avoidance / mitigation for MBS is shown. More specifically, Fig.15It is shown how the collision avoidance / mitigation can be performed using the spatial level preferred unicast information of the MBS broadcast information.

[0201] For example, in 1502, a UE in a connected state may receive a radio resource control (RRC) configuration message from a serving base station (gNB) on a component carrier (CC2). Additionally or alternatively, according to some embodiments, the RRC configuration message may include an indication or information about the transmission or reception of MBS transmission. In other words, the network may indicate to the UE that CC2 configured for the UE is used for MBS reception. Therefore, the UE may follow the NW indication to perform MBS configuration acquisition and data reception there (e.g., using CC2).

[0202] At 1504, the UE may receive a transmission from a multicast and broadcast service (MBS) BS. In addition, the transmission from the MBS BS may be on a different component carrier (e.g., CC1) than the transmission of 1502 (e.g., CC2) and also include information about the MBS unicast and / or broadcast transmission. For example, according to some embodiments, the transmission may include one or more system information blocks (SIBs) (e.g., SIBX), information corresponding to a multicast control channel (MCCH), and / or configuration information corresponding to a multicast traffic channel (MTCH).

[0203] In 1506, the UE may determine or know that it cannot receive unicast on CC2 (under certain conditions) and broadcast data on CC1. For example, the information provided in 1502 and 1504 may indicate that broadcast data will be received on CC1 and certain quasi-co-located (QCL) antenna ports will be used to receive unicast on CC2. In addition, according to some embodiments, the UE may lack the ability to receive unicast on CC2 on QCL antenna ports X, Y and / or Z. In other words, if unicast is scheduled / configured with some special or specific QCL antenna ports (e.g., X, Y, Z), the UE may not be able to receive MBS and unicast. However, in some scenarios, the UE may support different CC2 configurations (e.g., using preferred QCL antenna ports, such as A, B, C and / or D) to receive unicast.

[0204] Therefore, the UE may send UE assistance information (UAI) to the serving BS (e.g., gNB) in 1508. In addition, according to some embodiments, the UAI may include a preference corresponding to a preferred MBS carrier (e.g., CC1) and a list of preferred QCL antenna ports for unicast.

[0205] In 1510, the serving gNB may send a reconfiguration message to the UE to update the QCL configuration for CC2. In other words, according to some embodiments, the network may be able to adjust the QCL list configured / activated for unicast to avoid conflicts between unicast transmissions and broadcast transmissions.

[0206] Fig.16 An example scenario is shown in which a UE can use a UE assistance information design associated with an MBS broadcast to implement collision avoidance / mitigation for MBS. More specifically, Fig.16 It is shown how an assistance information trigger based on an activated serving cell set can be utilized to avoid conflicts between unicast and broadcast transmissions.

[0207] For example, in 1602, a UE in a connected state may receive a radio resource control (RRC) configuration message about a primary cell (PCell) from a serving base station (gNB) on CC1, and receive an RRC configuration message about a deactivated secondary cell (SCell) from a gNB on a component carrier (CC2). Additionally or alternatively, according to some embodiments, the RRC configuration message may include an indication or information about the transmission or reception of MBS transmission. In other words, the network may indicate to the UE that the PCell associated with CC1 configured for the UE is used for MBS reception. Therefore, the UE may follow the NW indication to perform MBS configuration acquisition and data reception there (e.g., using the PCell associated with CC1).

[0208] At 1604, the UE may receive a transmission from a multicast and broadcast service (MBS) BS. In addition, the transmission from the MBS BS may be on a different component carrier (e.g., CC3) than the transmission of 1602 and also include information about the MBS unicast and / or broadcast transmission. For example, according to some embodiments, the transmission may include one or more system information blocks (SIBs) (e.g., SIBX), information corresponding to a multicast control channel (MCCH), and / or configuration information corresponding to a multicast traffic channel (MTCH).

[0209] In 1606, the UE may determine or know that it can support receiving broadcast data on CC3 and receiving unicast using PCell. However, the UE may not be able to receive unicast on SCell in addition to PCell. In other words, the UE may be able to support receiving MBS on PCell and CC, but not on CC and SCell. Therefore, in 1608, the UE may formulate deactivation of SCell in order to receive broadcast data on CC3 and receive unicast on CC1 corresponding to PCell.

[0210] In some embodiments, the serving gNB may then also activate the SCell in 1610. Thus, the UE may also detect a conflict in 1612 and proceed to 1614 to provide certain information to the serving gNB in ​​response to the conflict detection. For example, as an option, the UE may provide unicast information to the serving gNB that also includes an indication that the UE prefers to deactivate or deconfigure the SCell. Additionally or alternatively, according to some embodiments, the UE may provide MBS information, such as MBS broadcast frequency and / or bandwidth, to the serving gNB.

[0211] Therefore, in 1616, the SCell may be deactivated again to avoid (as in 1618) unicast and broadcast conflicts. In addition, in 1620, the UE may then provide assistance information to the serving gNB and also indicate that no conflict occurred.

[0212] Fig.17 An example scenario is shown in which a UE may use the UE's inter-PLMN MBS broadcast service report to implement conflict avoidance / mitigation for MBS. More specifically, Fig.17 It shows how the network can establish and update the mapping between TMGI and cell ID based on the request report of MBS broadcast service information of inter-PLMN cells from the UE.

[0213] For example, in 1702, the network (e.g., gNB) may request one or more UEs to report MBS broadcast service information of inter-PLMN cells. The request may be in the form of an RRC configuration transmission and include information about the request, such as a specific or special PLMN X that may belong to a different PLMN or operator. In addition, the RRC configuration message may include information about a reporting mode to be implemented by the UE. For example, in some embodiments, according to some embodiments, the network (NW) may trigger reporting in various modes, including a single reporting mode, a periodic reporting mode, or a reporting mode when changed. Additionally or alternatively, the network may request reporting for some specific PLMNs and / or some specific NIDs. In addition, according to some embodiments, in 1704, the UE may receive another transmission on CC1, the other transmission including one or more system information blocks (SIBs) (e.g., SIBX), information corresponding to a multicast control channel (MCCH) and / or configuration information corresponding to a multicast traffic channel (MTCH), and related information related to PLMN X.

[0214] Thus, the UE may perform additional operations upon receiving the request. For example, according to some embodiments, when a connected UE receives or intends to receive an MBS broadcast service on a non-serving cell belonging to a different PLMN / operator, the UE may report the SIBx and MBSBroadcastConfiguration (delivered via MCCH) to the current serving gNB via dedicated signaling in 1706. Additionally or alternatively, the MBS broadcast information may include a preferred CC for the MBS broadcast (e.g., CC1), information about PLMN X, and a cell identifier (ID). Furthermore, if the UE is in a single reporting mode, the UE may be configured to report once. Additionally or alternatively, according to some embodiments, if the UE is in a periodic reporting mode, the UE may be configured to report the latest configuration as indicated or configured with a certain periodicity (or according to the MCCH modification period). In some embodiments, if the UE is in a reporting-on-change mode, the UE may report when the MCCH changes.

[0215] In 1708, the network may establish a mapping between a temporary mobile group identity (TMGI) and a cell ID based on the information received in 1706. In 1710, the MBS gNB may also send via the MCCH to indicate a change in the mapping of the cell ID. Thus, in 1712, the UE may send the updated information to the serving gNB so that the serving gNB may update the mapping in 1714.

[0216] Thus, in some embodiments, a wireless device may perform a method comprising: receiving a radio resource control (RRC) configuration message from a serving base station (BS) on a first component carrier (CC), wherein the RRC configuration message may include at least one of multicast and broadcast service (MBS) scheduling information or configuration information. The method may also include: receiving a transmission including additional MBS information from the MBS BS on the first CC. In addition, the method may include: determining a conflict between a unicast transmission and a broadcast transmission based on at least one of the received MBS scheduling information or configuration information. Additionally or alternatively, the wireless device may perform: sending an interest indication related to the MBS to the MBS BS, and receiving an RRC reconfiguration message from the MBS BS on a second CC. According to some embodiments, the RRC reconfiguration message may include at least one of the adjusted scheduling information or configuration information corresponding to the unicast transmission. The method performed by the wireless device may also include receiving a broadcast transmission from the MBS BS. In addition, according to some embodiments, the method performed by the wireless device may also include: receiving a unicast transmission from the serving BS based at least in part on the at least one of the adjusted scheduling information or configuration information.

[0217] According to some embodiments, the interest indication may be reported via dedicated signaling and may include MBS interest information, user equipment (UE) assistance information, layer 3 (L3) signaling, layer 2 (L2) medium access control-control element (MAC-CE) signaling, or layer 1 (L1) signaling. Additionally or alternatively, the interest indication may include MBS transmission duration information about at least one of unicast transmission or broadcast transmission, and also include information related to at least one of preferred discontinuous reception (DRX) configuration, periodicity, offset, duration, switching time, or switching gap.

[0218] In some embodiments, the interest indication may include frequency information about at least one of a unicast transmission or a broadcast transmission, and also include information related to at least one of a frequency location, a bandwidth, or a subcarrier spacing. Additionally or alternatively, the interest indication may include frequency information about at least one of a unicast transmission or a broadcast transmission, and information related to a preferred bandwidth part (BWP) corresponding to the first CC. According to some embodiments, the interest indication may include frequency information about at least one of a unicast transmission or a broadcast transmission, and also include information related to a preferred serving cell frequency corresponding to a second CC.

[0219] In some embodiments, the interest indication may include frequency information about at least one of the unicast transmission or the broadcast transmission, and further include information related to a preferred bandwidth part (BWP) corresponding to the first CC. Additionally or alternatively, the interest indication may include frequency information about at least one of the unicast transmission or the broadcast transmission, and further include information related to a preferred exclusion of a frequency position corresponding to a range of physical resource blocks (PRBs) from a configured bandwidth (BW) of the first CC.

[0220] According to further embodiments, the interest indication may include spatial information about at least one of a unicast transmission or a broadcast transmission, and further include information related to a preferred list of quasi-co-located (QCL) antenna ports of the first CC. Additionally or alternatively, the interest indication may include information about the unicast transmission, and further include information related to a preference for deactivating a secondary cell (SCell) or deconfiguring the SCell. In some embodiments, the interest indication may include MBS information about at least one of a unicast transmission or a broadcast transmission, and further include information related to at least one of an MBS broadcast frequency or bandwidth.

[0221] In some embodiments, a base station (BS) may be configured to perform a method comprising: sending a capability request including multicast and broadcast service (MBS) specific information to a user equipment (UE). The method may also include: receiving a message including at least one of a capability report or MBS interest information from the UE. Additionally or alternatively, the method may include: sending a radio resource control (RRC) reconfiguration message to the UE, wherein the RRC reconfiguration message includes at least one of adjusted scheduling information or configuration information corresponding to a unicast transmission. According to some embodiments, the method may also include: using the at least one of the adjusted scheduling information or configuration information to send a broadcast transmission to the UE.

[0222] In some embodiments, the capability report may include at least one of one or more frequency band combination parameters or one or more feature set combination parameters. Additionally or alternatively, the MBS interest information may include at least one of one or more preferred frequency band combinations or one or more preferred feature set combinations.

[0223] According to some embodiments, a user equipment (UE) may perform a method, the method comprising: receiving a radio resource control (RRC) configuration message from a serving base station (BS), the RRC configuration message comprising a request for the UE to report multicast and broadcast service (MBS) service information of one or more inter-public land mobility network (inter-PLMN) cells. The method may also include: receiving a transmission including MBS configuration information corresponding to an inter-PLMN cell in the one or more inter-PLMN cells from the MBS BS. Additionally or alternatively, the method may include: reporting MBS broadcast information corresponding to the inter-PLMN cell to the serving BS in response to receiving the request. In some embodiments, the method may include: receiving signaling on a multicast control channel (MCCH) from the MBS BS, the signaling comprising a change in mapping between a temporary mobile group identity (TMGI) and a cell identifier (ID) of the inter-PLMN cell. Additionally or alternatively, the method may include: sending MBS broadcast information corresponding to the inter-PLMN cell to the serving BS, the MBS broadcast information comprising a change in mapping between the TMGI and the cell ID of the inter-PLMN cell.

[0224] In some embodiments, reporting of MBS broadcast information may be performed according to a single reporting mode corresponding to the UE reporting once. Additionally or alternatively, reporting of MBS broadcast information may be performed according to a periodic reporting mode corresponding to the UE reporting multiple times based on a configured periodicity or MCCH modification period. According to some embodiments, reporting of MBS broadcast information may be performed according to a change reporting mode corresponding to the UE reporting one or more times in response to one or more changes in the mapping between the TMGI and the cell ID of the inter-PLMN cell.

[0225] Yet another example implementation may include a method comprising performing, by a wireless device, any or all of the foregoing examples.

[0226] Another example embodiment may include a device comprising: an antenna; a radio coupled to the antenna; and a processing element operably coupled to the radio, wherein the device is configured to implement any or all of the foregoing examples.

[0227] Yet another set of example embodiments may include a non-transitory computer-accessible storage medium including program instructions that, when executed at a device, cause the device to implement any or all portions of any of the foregoing examples.

[0228] Still another set of example embodiments may include a computer program comprising instructions for performing any or all portions of any of the foregoing examples.

[0229] Still another set of example embodiments may include an apparatus comprising means for performing any or all elements of any of the preceding examples.

[0230] Yet another set of example embodiments may include an apparatus comprising a processing element configured to cause a wireless device to perform any or all elements of any of the foregoing examples.

[0231] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0232] By interpreting each message / signal X received by a user equipment (UE) in the downlink as a message / signal X sent by the base station, and interpreting each message / signal Y sent by the UE in the uplink as a message / signal Y received by the base station, any of the methods for operating a UE described herein may become the basis for the corresponding method for operating a base station.

[0233] The 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, one or more custom-designed hardware devices such as ASICs may be used to implement the subject matter. In other embodiments, one or more programmable hardware elements such as FPGAs may be used to implement the subject matter.

[0234] In some embodiments, a non-transitory computer-readable storage medium (e.g., a non-transitory storage element) may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system is caused to perform a method, such as any method implementation of the method embodiments described herein, or any combination of the method implementations described herein, or any subset of any method implementation of the method embodiments described herein, or any combination of such subsets.

[0235] In some embodiments, a device (e.g., a UE) may be configured to include a processor (or a group of processors) and a memory medium (or a memory element), wherein the memory medium stores program instructions, wherein the processor is configured to read and execute these program instructions from the memory medium, wherein these program instructions are executable to implement any method implementation in the various method implementations described herein (or any combination of the method implementations described herein, or any subset of any method implementation in the method implementations described herein, or any combination of such subsets). The device may be implemented in any of various forms.

[0236] 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. It is intended that the following claims be interpreted to include all such variations and modifications.

Claims

1. A method, comprising: By wireless device: receiving a radio resource control (RRC) configuration message from a serving base station (BS) on a first component carrier (CC), wherein the RRC configuration message includes at least one of multicast and broadcast service (MBS) scheduling information or configuration information; receiving, on the first CC, from the MBS BS a transmission including additional MBS information; determining a conflict between unicast transmission and broadcast transmission based on at least one of the received MBS scheduling information or configuration information; sending an interest indication related to the MBS to the MBS BS; receiving an RRC reconfiguration message from the MBS BS on a second CC, wherein the RRC reconfiguration message includes at least one of adjusted scheduling information or configuration information corresponding to the unicast transmission; receiving the broadcast transmission from the MBS BS; as well as The unicast transmission is received from the serving BS based at least in part on the at least one of adjusted scheduling information or configuration information. The method of claim 1 , wherein the interest indication is reported via dedicated signaling.

3. The method of claim 1 , wherein the interest indication comprises at least one of: MBS Interested Information, User Equipment (UE) assistance information, Layer 3 (L3) signaling, Layer 2 (L2) Medium Access Control - Control Element (MAC-CE) signaling, or Layer 1 (L1) signaling.

4. The method of claim 1 , wherein the interest indication comprises transmission duration information about at least one of the unicast transmission or the broadcast transmission, and further comprises information related to at least one of: Periodicity, Offset, Duration, Switching time, or Switch gap.

5. The method of claim 1 , wherein the interest indication comprises frequency information about at least one of the unicast transmission or the broadcast transmission, and further comprises information related to at least one of: Frequency position, Bandwidth, or Subcarrier spacing.

6. The method of claim 1 , wherein the interest indication comprises scheduling information about at least one of the unicast transmission or the broadcast transmission, and further comprises information related to at least one of: Prefer discontinuous reception (DRX) configuration, Switching time, or Switch gap. 7 . The method of claim 1 , wherein the interest indication includes frequency information about at least one of the unicast transmission or the broadcast transmission, and further includes information related to a preferred serving cell frequency corresponding to the second CC. 8 . The method of claim 1 , wherein the interest indication comprises frequency information about at least one of the unicast transmission or the broadcast transmission, and further comprises information related to a preferred bandwidth part (BWP) corresponding to the first CC.

9. The method of claim 1, wherein the interest indication comprises frequency information about at least one of the unicast transmission or the broadcast transmission, and further comprises information related to preferred exclusion of frequency locations corresponding to a range of physical resource blocks (PRBs) in a configured bandwidth (BW) of the first CC.

10. The method of claim 1, wherein the interest indication comprises spatial information about at least one of the unicast transmission or the broadcast transmission and further comprises information related to a preferred list of quasi co-located (QCL) antenna ports of the first CC. 11 . The method of claim 1 , wherein the interest indication includes information about the unicast transmission and further includes information related to a preference for deactivating or deconfiguring a secondary cell (SCell).

12. The method of claim 1, wherein the interest indication comprises information about at least one of the unicast transmission or the broadcast transmission, and further comprises information related to at least one of an MBS broadcast frequency or bandwidth.

13. A method comprising: By Base Station (BS): Sending a capability request including multicast and broadcast service (MBS) specific information to a user equipment (UE); receiving a message including at least one of a capability report or MBS interest information from the UE; sending a radio resource control (RRC) reconfiguration message to the UE, wherein the RRC reconfiguration message includes at least one of adjusted scheduling information or configuration information corresponding to unicast transmission; and A broadcast transmission is sent to the UE using the at least one of the adjusted scheduling information or configuration information.

14. The method of claim 13, wherein the capability report comprises at least one of: One or more band combination parameters, or One or more feature set combination parameters. 15 . The method according to claim 14 , wherein the MBS interest information comprises at least one of one or more preferred frequency band combinations or one or more preferred feature set combinations.

16. A method comprising: By User Equipment (UE): receiving a radio resource control (RRC) configuration message from a serving base station (BS), the RRC configuration message including a request for the UE to report multicast and broadcast service (MBS) service information of one or more inter-public land mobility network (inter-PLMN) cells; receiving, from the MBS BS, a transmission including configuration information corresponding to an inter-PLMN cell of the one or more inter-PLMN cells; reporting MBS broadcast information corresponding to the inter-PLMN cell to the serving BS in response to receiving the request; receiving signaling on a multicast control channel (MCCH) from the MBS BS, the signaling comprising a change in mapping between a temporary mobile group identity (TMGI) and a cell identifier (ID) of the inter-PLMN cell; as well as The MBS broadcast information corresponding to the inter-PLMN cell is transmitted to the serving BS, the MBS broadcast information including the change of the mapping between the TMGI and the cell ID of the inter-PLMN cell.

17. The method according to claim 16, wherein the reporting of the MBS broadcast information is performed according to at least one of the following modes: a single reporting mode corresponding to the UE reporting once, a periodic reporting mode corresponding to the UE reporting multiple times based on a configured periodicity or MCCH modification period, or A changed reporting mode corresponds to the UE reporting one or more times in response to one or more changes in the mapping between the TMGI and the cell ID of the inter-PLMN cell.

18. An apparatus comprising at least one processor configured to cause a user equipment (UE) to perform the steps of the method according to any one of claims 1 to 12.

19. An apparatus comprising one or more processors configured to cause a base station (BS) to perform the steps of the method according to any one of claims 13 to 17.

20. A computer program product comprising computer instructions which, when executed by one or more processors, perform the steps of the method according to any one of claims 1 to 17.

Images