Baseband processor, base station and method for wireless communication

Abstract

A user equipment device (UE) can receive multimedia broadcast and multicast service (MBMS) transmissions on a bandwidth part (BWP) that is specifically allocated for MBMS point-to-multipoint (PTM) transmissions or on MBMS-specific resources configured for PTM transmissions within a UE-specific BWP. A network (e.g., a base station) can configure a MBMS-specific BWP for the UE for the PTM transmissions of each serving cell. The MBMS-specific BWP can be for downlink transmissions and can be cell-specific or UE-specific for each serving cell. The base station can provide the UE with MBMS PTM scheduling information for each BWP, can indicate whether a UE-specific BWP can be used for PTM scheduling and transmissions, and can provide the corresponding scheduling configuration when applicable. The UE can communicate to the base station various capabilities of the UE related to MBMS reception and simultaneous reception of PTM and point-to-point (PTP) transmissions to assist the base station in scheduling communications for the UE.

Description

Technical Field

[0001] This application relates to wireless communication, including techniques for transmitting and receiving multimedia broadcast and multicast services (MBMS) in a connected state during wireless communication (e.g., during 3GPP NR communication). Background Technology

[0002] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices (i.e., user equipment or UE) now offer access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating complex applications that utilize these capabilities. Furthermore, many different wireless communication technologies and standards exist. Some examples of wireless communication standards include GSM, UMTS (WCDMA, TD-SCDMA), LTE, LTE Advanced (LTE-A), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), IEEE 802.16 (WiMAX), and BLUETOOTH. TM The proposed telecommunications standard that surpasses the International Mobile Telecommunications Advanced (IMT-Advanced) standard is the 5th generation mobile network or 5th generation wireless system, called 3GPP NR (also known as 5G New Radio (5G-NR), or simply NR). NR provides higher capacity for higher density mobile broadband users, while supporting device-to-device, ultra-reliable and massive machine-type communications, as well as lower latency and lower battery consumption than the LTE standard.

[0003] One aspect of cellular communication systems involves multimedia broadcasting and multicast services and associated transmissions. Improvements in this field are expected. Summary of the Invention

[0004] The aspects presented herein relate in particular to techniques for implementing group scheduling mechanisms that allow user equipment (UE) to receive broadcast and multicast service transmissions during wireless communication, such as during 3GPP New Radio (NR) communication, and further to techniques for enabling simultaneous operation with unicast transmission / reception. This document further provides aspects of wireless communication systems comprising user equipment (UE) and / or base stations communicating with each other within the wireless communication system as presented herein to receive broadcast and multicast service transmissions, and to simultaneously provide broadcast / multicast and unicast services.

[0005] Based on the above, a device (e.g., a UE) can perform wireless communication within a wireless network, and as part of wireless communication within the wireless network, in a connected state, can receive MBMS transmissions on a first bandwidth portion (BWP) specifically allocated for Multimedia Broadcast and Multicast Service (MBMS) transmissions, or on a second BWP using first resources specifically allocated for MBMS transmissions within a second BWP. Furthermore, the UE can receive unicast transmissions on a third BWP different from the first BWP, and can simultaneously receive unicast and MBMS transmissions. MBMS transmissions can be point-to-multipoint (PTM) transmissions. When the device cannot support simultaneous reception of MBMS and unicast transmissions, the UE can receive a second MBMS transmission as a point-to-point (PTP) transmission. MBMS transmissions may include MBMS scheduling information and / or MBMS data.

[0006] In some aspects, the UE can transmit capability information to the base station to indicate whether the UE supports simultaneous reception of MBMS and unicast transmissions. This capability can be defined by frequency band combination, by frequency band, or by UE. In some cases, the first BWP can completely overlap with the third BWP used by the UE to receive unicast transmissions, while in other cases, the first BWP can correspond to a portion of a wider second BWP used by the UE to receive unicast transmissions. The first BWP can correspond to the UE's serving cell. In some aspects, as part of wireless communication within a wireless network, the UE can receive multiple MBMS transmissions in a connected state on respective corresponding BWPs specifically allocated for MBMS transmissions, wherein each of the respective BWPs is associated with a different corresponding serving cell of the UE.

[0007] The first BWP can be cell-specific for each serving cell of the UE, or it can be UE-specific for each serving cell of the UE. In some cases, the UE can start and stop receiving MBMS transmissions based on one or more of the following:

[0008] ● Explicit instructions to start receiving received in a common command, and explicit instructions to stop receiving received in a subsequent common command;

[0009] ● An explicit indication to start receiving received in a UE-specific command, and an explicit indication to stop receiving received in a subsequent UE-specific command; or

[0010] ● The UE can decide whether to receive MBMS data transmission.

[0011] In some cases, the UE can receive unicast transmissions on a third BWP in a time-division multiplexing manner relative to MBMS transmissions on the first BWP. During periods when unicast and MBMS transmissions occur simultaneously, the UE can also receive unicast transmissions on the third BWP and not receive any MBMS transmissions on the first BWP. Furthermore, the UE can only receive MBMS transmissions on the first BWP if no unicast transmission occurs on the third BWP. The UE can also stop receiving MBMS transmissions on the first BWP and receive MBMS transmissions scheduled via PTP transmission. When the second BWP is active for the UE, the UE can receive MBMS transmissions on the second BWP, and when the third BWP is active for the UE, the UE can receive unicast transmissions on the third BWP. When the second BWP is active, MBMS transmissions can be received by the UE on the second BWP based on resource information and scheduling configurations previously transmitted from the base station to the UE and received by the UE.

[0012] It should be noted that the technologies described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to base stations, access points, cellular phones, portable media players, tablets, wearable devices and various other computing devices.

[0013] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0014] Figure 1 An exemplary (and simplified) wireless communication system is shown according to some aspects;

[0015] Figure 2 An exemplary base station is shown that communicates with an exemplary wireless user equipment (UE) device according to some aspects;

[0016] Figure 3 An exemplary block diagram of a UE is shown according to some aspects;

[0017] Figure 4 An exemplary block diagram of a base station is shown according to some aspects;

[0018] Figure 5 An exemplary simplified block diagram illustrating a cellular communication circuit according to some aspects is shown;

[0019] Figure 6A first example of wireless communication based on some aspects is shown, in which an MBMS-specific BWP is allocated for MBMS-PTM transmission;

[0020] Figure 7 A second example of wireless communication based on some aspects is shown, in which an MBMS-specific BWP is allocated for MBMS-PTM transmission;

[0021] Figure 8 A third example of wireless communication based on some aspects is shown, in which an MBMS-specific BWP is allocated for MBMS-PTM transmission;

[0022] Figure 9 A fourth example of wireless communication based on some aspects is shown, in which an MBMS-specific BWP is allocated for MBMS-PTM transmission;

[0023] Figure 10 A fifth example of wireless communication based on some aspects is shown, in which an MBMS-specific BWP is allocated for MBMS-PTM transmission;

[0024] Figure 11 A sixth example of wireless communication based on some aspects is shown, in which an MBMS-specific BWP is allocated for MBMS-PTM transmission;

[0025] Figure 12 A seventh example of wireless communication based on some aspects is shown, in which an MBMS-specific BWP is allocated for MBMS-PTM transmission;

[0026] Figure 13 An eighth example of wireless communication according to some aspects is shown, in which an MBMS-specific BWP is assigned for MBMS-PTM transmission;

[0027] Figure 14 An example of wireless communication based on some aspects is shown, wherein MBMS-specific resources within a specified BWP are allocated for MBMS-PTM transmission; and

[0028] Figure 15 Three examples of resource stacks used by different BWPs during wireless communication are shown, based on several aspects, where MBMS-specific resources within a specified BWP are used for MBMS-PTM transmission.

[0029] While the features described herein are susceptible to various modifications and alternatives, their specific aspects are illustrated by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0030] acronym

[0031] Various acronyms are used throughout this patent application. The definitions of the most prominent acronyms that may appear throughout this patent application are as follows:

[0032] ●ACK: Confirmation

[0033] ●AMF: Access Mobility and Management Functions

[0034] ●APR: Application Processor

[0035] ●AUL: Autonomous Uplink Transmission

[0036] ●BLER: Block Error Rate

[0037] ●BS: Base Station

[0038] ●BSR: Buffer Status Report

[0039] ●BWP: Bandwidth section

[0040] ●CAPC: Channel Access Priority Category

[0041] ●CG: Configuration Authorization

[0042] ●CMR: Change Mode Request

[0043] ●CORESET: Control Channel Resource Set

[0044] ●COT: Channel Occupancy Time

[0045] ●CRC: Cyclic Redundancy Check

[0046] ●CS-RNTI: Configured temporary identifier for the dispatch radio network

[0047] ●CSI: Channel State Information

[0048] ●DCI: Downlink Control Information

[0049] ●DG: Dynamic Licensing

[0050] ●DL: Downlink (from BS to UE)

[0051] ●DMRS: Demodulation Reference Signal

[0052] ●DRB: (User) Data Radio Bearer

[0053] ●DYN: Dynamic

[0054] ●ED: Energy Detection

[0055] ●FDM: Frequency Division Multiplexing

[0056] ●FT: Frame Type

[0057] ●GC-PDCCH: Group Common Physical Downlink Control Channel

[0058] ●GPRS: General Packet Radio Service

[0059] ●GSM: Global System for Mobile Communications

[0060] ●GTP: GPRS Tunneling Protocol

[0061] ●HARQ: Hybrid Automatic Repeat Request

[0062] ●IR: Initialization and refresh status

[0063] ●LAN: Local Area Network

[0064] ●LMF: Location Management Function

[0065] ●LPP: LTE Positioning Protocol

[0066] ●LTE: Long Term Evolution

[0067] ●MAC: Media Access Control

[0068] ●MAC-CE: MAC control element

[0069] ●MBMS: Multimedia Broadcast and Multicast Services

[0070] ●MCS: Modulation and Coding Scheme

[0071] ●MIB: Master Information Block

[0072] ●MIMO: Multiple Input Multiple Output

[0073] ●MRB: MBMS PTM radio carrier

[0074] ●NDI: New Data Indicator

[0075] ●OFDM: Orthogonal Frequency Division Multiplexing

[0076] ●OSI: Open Systems Interconnection

[0077] ●PBCH: Physical Broadcast Channel

[0078] ●PDCCH: Physical Downlink Control Channel

[0079] ●PDCP: Packet Data Convergence Protocol

[0080] ●PDN: Packet Data Network

[0081] ●PDSCH: Physical Downlink Shared Channel

[0082] ●PDU: Protocol Data Unit

[0083] ●PRB: Physical Resource Block

[0084] ●PTM: Point-to-Multipoint

[0085] ●PTP: Point-to-Point

[0086] ●PUCCH: Physical Uplink Control Channel

[0087] ●PUSCH: Physical Uplink Shared (Data) Channel ●QCL: Quasi-Co-address

[0088] ●RACH: Random Access Procedure

[0089] ●RAT: Radio Access Technology

[0090] ●RB: Resource Block

[0091] ●RE: Resource Elements

[0092] ●RF: Radio Frequency

[0093] ●RLC: Radio Link Control

[0094] ●RMSI: Residual Minimum System Information

[0095] ●RNTI: Temporary Identifier for Radio Networks ●ROHC: Robust Header Compression

[0096] ●RRC: Radio Resource Control

[0097] ●RS: Reference signal (symbol)

[0098] ●RSI: Root Sequence Indicator

[0099] ●RTP: Real-time Transport Protocol

[0100] ●RV: Redundant Version

[0101] ●RX: Receive

[0102] ●SDAP: Service Data Adaptation Protocol

[0103] ●SDM: Spatial Division Multiplexing

[0104] ●SID: System Identifier

[0105] ●SGW: Service Gateway

[0106] ●SR: Scheduling Request

[0107] ●SRS: Detection Reference Signal

[0108] ●SS: Search Space

[0109] ●SSB: Synchronization Signal Block

[0110] ●TBS: Transport Block Size

[0111] ●TCI: Transmission Configuration Indicator

[0112] ●TDM: Time Division Multiplexing

[0113] ●TRS: Tracking Reference Signal

[0114] ●TX: Transmission

[0115] ●UCI: Uplink Control Information

[0116] ●UE: User Equipment

[0117] ●UL: Uplink (from UE to BS)

[0118] ●UMTS: Universal Mobile Telecommunication System

[0119] ●Wi-Fi: Wireless Local Area Network (WLAN) RAT based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard.

[0120] ●WLAN: Wireless LAN

[0121] the term

[0122] The following is a glossary of terms that will appear in this application:

[0123] Memory media—any device of any type of memory device or storage device. The term “memory media” is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic 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. Memory media may also include other types of memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In a later example, the second computer system may provide program instructions to the first computer system for execution. The term “memory media” may include two or more memory media that may reside in different locations on different computer systems, for example, connected via a network. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0124] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks, and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals, or digital signals).

[0125] Programmable hardware elements—including a variety of hardware devices comprising multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can vary from fine-grained (combinatorial logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as “configurable logic units.”

[0126] Computer system (or computer) — any of the various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. Generally, the term "computer system" can be broadly defined as any device (or combination of devices) that includes at least one processor that executes instructions from a memory medium.

[0127] User equipment (UE) (or “UE device”) – any of the various types of computer system devices that perform wireless communication. Also known as wireless communication devices, many of which can be mobile and / or portable. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). TMBased on Android TM (phones) and tablets such as iPad TM Samsung Galaxy TM etc., gaming devices (such as Sony PlayStation) TM Microsoft Xbox TM etc.), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPod TM Laptops, wearable devices (e.g., Apple Watch) TM Google Glass TM PDAs, portable internet devices, music players, data storage devices or other handheld devices, unmanned aerial vehicles (e.g., drones) and drone controllers, etc. Various other types of devices that include Wi-Fi communication capabilities or both cellular and Wi-Fi communication capabilities and / or other wireless communication capabilities (e.g., via Short Range Radio Access Technology (SRAT) such as BlueTooth). TM (etc.) would fall into this category. Generally, the term "UE" or "UE device" can be broadly defined to cover any electronic device, computing device, and / or telecommunications device (or combination of devices) capable of wireless communication, and can also be portable / mobile.

[0128] Wireless device (or wireless communication device) – any type of computer system device that performs wireless communication using WLAN communication, SRAT communication, Wi-Fi communication, etc. As used herein, the term “wireless device” can refer to a UE device as defined above or a fixed device such as a fixed wireless client or wireless base station. For example, a wireless device can be a wireless station of any type of 802.11 system, such as an access point (AP) or client site (UE), or a wireless station of any type of cellular communication system that communicates according to cellular radio access technologies (e.g., LTE, CDMA, GSM), such as a base station or cellular phone.

[0129] A communication device is any of various types of computer systems or devices that perform communication, which may be wired or wireless. A communication device may be portable (or mobile), or it may be stationary or fixed in a location. A wireless device is one example of a communication device. A UE is another example of a communication device.

[0130] Base station (BS) — The term “base station” has the full range of its usual meaning and includes at least a wireless communication station that is installed at a fixed location and used for communication as part of a wireless telephone system or radio system.

[0131] A processor is a component (e.g., circuitry) or combination of components capable of performing functions in a device (e.g., in a user equipment device or a cellular network device). A processor may include, for example: a general-purpose processor and associated memory, portions or circuitry of individual processor cores, an entire processor core or processing circuitry core, an array of processing circuitry or a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0132] A channel is a medium used to transmit information from a transmitter to a receiver. It should be noted that because the characteristics of the term "channel" can vary depending on different wireless protocols, the term "channel" as used herein can be considered to be used in a standard manner consistent with the type of device to which the term is referenced. In some standards, the channel width can be variable (e.g., depending on device capabilities, band conditions, etc.). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. In contrast, WLAN channels can be 22 MHz wide, while Bluetooth channels can be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0133] Band (or frequency band) — The term "band" encompasses the full range of its usual meaning and includes at least a segment of the spectrum (e.g., radio frequency spectrum) in which channels are used or reserved for the same purpose. Furthermore, "band" is used to refer to any interval in the frequency domain defined by lower and higher frequencies. The term can refer to radio frequency bands or intervals of some other spectrum. Radio communication signals may occupy a frequency range that carries the signal (or the frequency range in which the signal is carried). Such a frequency range is also called the bandwidth of the signal. Therefore, bandwidth refers to the difference between the upper and lower frequencies in a continuous band. A band can represent a single communication channel, or it can be subdivided into multiple communication channels. The allocation of radio frequency ranges for different purposes is a primary function of radio spectrum allocation.

[0134] Wi-Fi—The term “Wi-Fi” encompasses the full range of its common meaning and includes at least wireless communication networks, or RATs, which are provided by and through wireless LAN (WLAN) access points to provide connectivity to the Internet. 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.

[0135] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatic" contrasts with an action performed or specified manually by a user, where the user provides input to directly perform that action. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input to specify information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0136] Approximately—means a value close to the correct or precise value. For example, approximately can refer to a value within 1% to 10% of the precise (or expected) value. However, it should be noted that the actual threshold (or tolerance) can vary depending on the application. For instance, in some respects, “approximately” may mean within 0.1% of some specified or expected value, while in various other respects, the threshold may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of a particular application.

[0137] Concurrency refers to the parallel execution or implementation of tasks, processes, or programs in a manner that at least partially overlaps. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0138] Site (STA) — The term “site” in this document refers to any device capable of wireless communication (e.g., using the 802.11 protocol). A site can be a laptop, desktop PC, PDA, access point, Wi-Fi phone, or any type of device similar to a UE. An STA can be fixed, mobile, portable, or wearable. Generally, in wireless networking terminology, the term site (STA) broadly encompasses any device with wireless communication capabilities, and the terms site (STA), wireless client (UE), and node (BS) are therefore often used interchangeably.

[0139] "Configured as"—Various components can be described as being "configured as" to perform one or more tasks. In such contexts, "configured as" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently powered on. Typically, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.

[0140] Transmission scheduling refers to the scheduling of transmissions (such as wireless transmissions). In some specific implementations of cellular radio communications, signal and data transmissions can be organized according to designated time units of a specific duration during which a transmission occurs. As used herein, the term "slot" has the full range of its usual meaning and at least refers to the smallest (or shortest) scheduling time unit in wireless communications. For example, in 3GPP LTE, transmissions are divided into radio frames, each with an equal (time) duration (e.g., 10 ms). Radio frames in 3GPP LTE can be further divided into a specified number (e.g., ten) subframes, each with an equal duration, which are designated as the smallest (shortest) scheduling unit, or the designated time unit for transmission. Thus, in the 3GPP LTE example, a "subframe" can be considered an example of a "slot" as defined above. Similarly, the smallest (or shortest) scheduling time unit for 5G NR (or simply NR) transmissions is called a "slot." The smallest (or shortest) scheduling time unit may also be named differently in different communication protocols.

[0141] Resources—The term “resource” has the full range of its usual meaning and can refer to frequency resources and time resources used during wireless communication. As used herein, a resource element (RE) refers to a specific quantity or number of resources. For example, in the context of time resources, a resource element can be a time period of a specific length. In the context of frequency resources, a resource element can be a specific frequency bandwidth centered at a specific frequency or a specific amount of frequency bandwidth. As a concrete example, a resource element can refer to a resource unit with one symbol (reference time resource, such as a specific frequency bandwidth centered at a specific frequency) for every one subcarrier (reference frequency resource). A resource element group (REG) has the full range of its usual meaning and refers to at least a specified number of consecutive resource elements. In some specific implementations, a resource element group may not include resource elements reserved for a reference signal. A control channel element (CCE) refers to a specified number of consecutive REGs. A resource block (RB) refers to a specified number of resource elements consisting of a specified number of subcarriers per specified number of symbols. Each RB may include a specified number of subcarriers. A resource block group (RBG) refers to a unit comprising multiple RBs. The number of RBs within an RBG can vary depending on the system bandwidth.

[0142] A carrier bandwidth portion (BWP) is a contiguous set of physical resource blocks selected from a contiguous subset of common resource blocks on a given carrier with a given set of parameters. For the downlink, a UE can be configured with up to a specified number of carrier BWPs (e.g., four BWPs according to some specifications), with one BWP active per carrier at a given time (according to some specifications). For the uplink, a UE can similarly be configured with up to a number (e.g., four) of carrier BWPs, with one BWP active per carrier at a given time (according to some specifications). If the UE is configured with a supplemental uplink, the UE can additionally be configured with up to a specified number (e.g., four) of carrier BWPs in the supplemental uplink, with one carrier BWP active at a given time (according to some specifications).

[0143] Multi-cell deployment—A primary node is defined as a node (radio access node) that provides control plane connectivity to the core network in the case of Multiple Radio Dual Connectivity (MR-DC). A primary node can be, for example, a primary eNB (3GPP LTE) or a primary gNB (3GPP NR). A secondary node is defined as a radio access node without control plane connectivity to the core network, providing additional resources to the UE in the case of MR-DC. A primary cell group (MCG) is defined as a group of serving cells associated with a primary node, including a primary cell (PCell) and optionally one or more secondary cells (SCells). A secondary cell group (SCG) is defined as a group of serving cells associated with a secondary node, including a special cell, i.e., the primary cell (PSCell) of the SCG, and optionally including one or more SCells. The UE can typically apply radio link monitoring to the PCell. If the UE is configured with an SCG, the UE can also apply radio link monitoring to the PSCell. Radio link monitoring is typically applied to active BWPs, and the UE does not need to monitor inactive BWPs. The PCell is used to initiate initial access, and the UE can communicate with the PCell and SCell via carrier aggregation (CA). The current modified capability means that the UE can receive and / or transmit to and / or from multiple cells. The UE initially connects to the PCell, and once the UE is in a connected state, one or more SCells can be configured for the UE.

[0144] Core Network (CN) — The core network is defined as part of a 3GPP system that is independent of the UE's connectivity technology (e.g., radio access technology, RAT). The UE can connect to the core network via the radio access network (RAN), which can be RAT-specific.

[0145] For ease of description, various components may be described as performing one or more tasks. Such descriptions shall be interpreted as including 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 paragraph 6 of section 112 of title 35 of the United States Code.

[0146] Figure 1 and Figure 2 -Exemplary communication system

[0147] 3GPP LTE / NR defines several downlink (DL) physical channels, classified as transport or control channels, to carry blocks of information received from the MAC and higher layers. 3GPP LTE / NR also defines uplink (UL) physical layer channels. The Physical Downlink Shared Channel (PDSCH) is a DL transport channel and the primary data bearer channel allocated to users on a dynamic and opportunistic basis. The PDSCH carries data in transport blocks (TBs) corresponding to Medium Access Control Protocol Data Units (MAC PDUs), which are passed from the MAC layer to the physical (PHY) layer once every transmission time interval (TTI). The PDSCH is also used to transmit broadcast information such as System Information Blocks (SIBs) and paging messages.

[0148] The Physical Downlink Control Channel (PDCCH) is a DL control channel that carries UE resource allocations contained in Downlink Control Information (DCI) messages. For example, the DCI may include a Transmission Configuration Indication (TCI) related to beamforming, where the TCI includes configurations such as quasi-co-address (QCL) relationships between downlink reference signals (DL-RS) and PDSCH demodulation reference signals (DMRS) ports within a Channel State Information RS (CSI-RS) set. Each TCI state can contain parameters for configuring QCL relationships between one or two downlink reference signals and DMRS ports of the PDSCH, DMRS ports of the PDCCH, or CSI-RS ports of CSI-RS resources. Multiple PDCCHs can be transmitted in the same subframe using Control Channel Elements (CCEs), each of which is a set of resource elements called a Resource Element Group (REG). The PDCCH may employ Quadrature Phase Shift Keying (QPSK) modulation, where a specific number (e.g., four) of QPSK symbols are mapped to each REG. In addition, depending on the channel conditions, the UE can use a specified number (e.g., 1, 2, 4 or 8) of CCEs to ensure sufficient robustness.

[0149] The Physical Uplink Shared Channel (PUSCH) is a UL channel shared by all devices (User Equipment, UE) in a radio cell to transmit user data to the network. Scheduling for all UEs is under the control of the base station (e.g., eNB or gNB). The base station uses uplink scheduling grants (e.g., in DCI) to inform the UE about resource block (RB) allocations and the modulation and coding schemes to be used. PUSCH typically supports QPSK and Quadrature Amplitude Modulation (QAM). In addition to user data, PUSCH carries any control information required for decoding, such as transport format indicators and Multiple-Input Multiple-Output (MIMO) parameters. Control data is multiplexed with information data before Digital Fourier Transform (DFT) expansion.

[0150] Figure 1 An exemplary (and simplified) wireless communication system is shown according to some aspects. It should be noted that... Figure 1 The system described is merely one example of a possible system, and aspects can be implemented in any of the various systems as needed.

[0151] As shown in the figure, the exemplary wireless communication system includes base stations 102A to 102N, also collectively referred to as multiple base stations 102 or base station 102. Figure 1 As shown, base station 102A communicates with one or more user equipments 106A to 106N via a transmission medium. Each user equipment may be referred to herein as a “User Equipment” (UE) or UE device. Therefore, user equipments 106A to 106N are referred to as UEs or UE devices, and are also collectively referred to as multiple UEs 106 or UE 106. The various UE devices within the UE devices can implement solutions for multimedia and broadcast service reception, as well as simultaneous operation with unicast reception, as disclosed herein.

[0152] Base station 102A can be a transceiver base station (BTS) or a cell site, and may include hardware to enable wireless communication with UEs 106A to 106N. Base station 102A may also be configured to communicate with network 100, such as the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN) and / or the Internet, neutral hosts, or various CBRS (Citizen Broadband Radio Service) deployments, and various other possibilities. Therefore, base station 102A facilitates communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various communication capabilities such as voice, SMS, and / or data services. The communication area (or coverage area) of the base station may be referred to as a “cell.” It should also be noted that a “cell” can also refer to a logical identity for a given coverage area at a given frequency. Typically, any independent cellular wireless coverage area can be referred to as a “cell.” In such a case, the base station may be located at a specific intersection of three cells. In this uniform topology, the base station can serve three 120-degree beamwidth areas called cells. Furthermore, for carrier aggregation, small cells, relays, etc., can all represent cells. Therefore, especially in carrier aggregation, there can be primary and secondary cells that serve at least partially overlapping coverage areas but operate on different corresponding frequencies. For example, a base station can serve any number of cells, and the cells served by the base station can be arranged side-by-side or not (e.g., at a remote radio head). Similarly, as used herein, with respect to the UE, sometimes, considering the UE's uplink and downlink communications, the base station can be considered to represent the network. Therefore, a UE communicating with one or more base stations in the network can also be interpreted as a UE communicating with that network, and can also be considered as at least a part of the UE's communication on or through the network.

[0153] Base station 102 and user equipment can be configured to communicate via a transmission medium using any of a variety of radio access technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (WCDMA), LTE, LTE-Advanced (LTE-A), LAA / LTE-U, 5G-NR (abbreviated as NR), 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, WiMAX, etc. It should be noted that if base station 102 is implemented in an LTE environment, it may alternatively be referred to as 'eNodeB' or 'eNB'. It should also be noted that if base station 102A is implemented in a 5G NR environment, it may alternatively be referred to as 'gNodeB' or 'gNB'. In some aspects, base station 102 can implement signaling for supplying location resources requested by the UE via physical layer signaling, as described herein. Depending on the given application or specific considerations, for convenience, several different RATs may be functionally grouped according to their overall defined characteristics. For example, all cellular RATs may be uniformly considered to represent a first (form / type) RAT, while Wi-Fi communication may be considered to represent a second RAT. In other cases, individual cellular RATs may be considered as distinct RATs. For example, when distinguishing between cellular and Wi-Fi communication, "first RAT" may uniformly refer to all cellular RATs under consideration, while "second RAT" may refer to Wi-Fi. Similarly, when applicable, different forms of Wi-Fi communication (e.g., above 2.4 GHz versus above 5 GHz) may be considered to correspond to different RATs. Furthermore, cellular communication performed according to a given RAT (e.g., LTE or NR) may be distinguished from each other based on the spectrum in which those communications are performed. For example, LTE or NR communication may be performed on the primary licensed spectrum as well as on secondary spectrum such as unlicensed spectrum and / or spectrum allocated to Citizens Broadband Radio Service (CBRS). Overall, the use of various terms and expressions will always be clearly indicated in relation to the context of the various applications / aspects under consideration.

[0154] As shown in the figure, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A can facilitate communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various communication capabilities such as voice, SMS, and / or data services. Base station 102A and other similar base stations (such as base stations 102B…102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping services to UE 106A-106N and similar equipment over a geographical area via one or more cellular communication standards.

[0155] Therefore, although base station 102A can act as such Figure 1 The diagram shows the "serving cell" of UEs 106A-106N, but each UE 106 may also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B-102N and / or any other base stations), which may be referred to as "neighboring cells". Such cells may also facilitate communication between user equipments and / or between user equipments and network 100. These cells may include "macro" cells, "micro" cells, "pecimen" cells, and / or any other cells of various other granularities providing a service area size. For example, in Figure 1 Base stations 102A-102B shown can be macro cells, while base station 102N can be a micro cell. Other configurations are also possible.

[0156] In some respects, base station 102A can be a next-generation base station, such as a 5G New Radio (5GNR) base station or a "gNB". In some respects, the gNB can be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, a gNB cell can include one or more transmit and receive points (TRPs). Additionally, a UE capable of operating according to 5G NR can connect to one or more TRPs within one or more gNBs.

[0157] As described above, UE 106 may be able to communicate using multiple wireless communication standards. For example, the UE may be configured to communicate using any or all of the 3GPP cellular communication standards (such as LTE or NR) or 3GPP2 cellular communication standards (such as cellular communication standards in the CDMA2000 series). Base station 102 and other similar base stations operating according to the same or different cellular communication standards can therefore be provided as one or more cell networks that can provide continuous or near-continuous overlapping services to UE 106 and similar devices over a wide geographical area via one or more cellular communication standards.

[0158] UE 106 can also be configured, or alternatively configured, to use WLAN, BLUETOOTH TM BLUETOOTH TM Communication can be made using low-energy, one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one and / or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), etc. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible. Furthermore, UE 106 may also communicate with network 100 via one or more base stations or via other devices, sites, or any apparatus not explicitly shown but considered part of network 100. Therefore, UE 106's communication with the network can be interpreted as UE 106 communicating with one or more network nodes considered part of the network, and interacting with UE 106 to communicate with UE 106, and in some cases affecting at least some communication parameters and / or the use of UE 106's communication resources.

[0159] In addition, such as Figure 1 As shown, at least some of UEs 106 (e.g., UEs 106D and 106E) can represent vehicles communicating with each other and with base station 102A, for example, via cellular communications such as 3GPP LTE and / or 5G-NR. Additionally, UE 106F can similarly represent a pedestrian communicating and / or interacting with the vehicles represented by UEs 106D and 106E. In the context of vehicle-to-everything (V2X) communication (such as communication specified by 3GPP TS22.185V 14.3.0, etc.), the disclosure... Figure 1 Other aspects of vehicles communicating in the network illustrated in the example.

[0160] Figure 2An exemplary user equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 and access point 112 according to some aspects is shown. UE 106 can be cellular communication capable and non-cellular communication capable (e.g., BLUETOOTH). TM Devices such as mobile phones, handheld devices, computers, or tablets, or virtually any type of wireless device (e.g., Wi-Fi, etc.). UE 106 may include a processor configured to execute program instructions stored in memory. UE 106 can perform any of the methods described herein by executing such stored instructions. Alternatively or additionally, UE 106 may include programmable hardware elements, such as FPGAs (Field-Programmable Gate Arrays), configured to perform any of the methods described herein or any portion thereof. 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 CDMA 2000, LTE, LTE-A, NR, WLAN, or GNSS. Other combinations of wireless communication standards are also possible.

[0161] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols according to one or more RAT standards, such as those previously described above. In some aspects, UE 106 may share one or more portions of a receive chain and / or transmit chain among multiple wireless communication standards. The shared radio components may include a single antenna, or may include multiple antennas for performing wireless communication (e.g., for MIMO). Alternatively, UE 106 may include independent transmit chains and / or receive chains (e.g., including independent antennas and other radio components) for each wireless communication protocol configured to communicate using it. As another alternative, UE 106 may include one or more radio components or radio circuits shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 may include shared radio components for communicating using either LTE or CDMA2000 1xRTT or NR, and for communicating using Wi-Fi and BLUETOOTH. TM Each component communicates independently. Other configurations are also possible.

[0162] Figure 3 - Block diagram of an exemplary UE

[0163] Figure 3A block diagram of an exemplary UE 106 according to some aspects is shown. As shown, UE 106 may include a System-on-Chip (SOC) 300, which may include portions for various purposes. For example, as shown, SOC 300 may include a processor 302 capable of executing program instructions for UE 106, and display circuitry 304 capable of performing graphics processing and providing display signals to a display 360. The processor 302 may also be coupled to a memory management unit (MMU) 340, and / or other circuitry or devices (such as display circuitry 304, radio circuitry 330, connector I / F 320, and / or display 360), which may be configured to receive addresses from the processor 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310). MMU 340 may be configured to perform memory protection and page table translation or setup. In some aspects, MMU 340 may be included as part of the processor 302.

[0164] As shown in the figure, the SOC 300 can be coupled to various other circuits of the UE 106. For example, the 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), display 360, and wireless communication circuitry (e.g., for LTE, LTE-A, NR, CDMA2000, BLUETOOTH). TM (e.g., Wi-Fi, GPS, etc.). UE device 106 may include at least one antenna (e.g., 335a) and may include multiple antennas (e.g., shown by antennas 335a and 335b) for performing wireless communication with a base station and / or other devices. Antennas 335a and 335b are shown by way of example, and UE device 106 may include fewer or more antennas. Generally, one or more antennas are collectively referred to as antenna 335. For example, UE device 106 may use antenna 335 to perform wireless communication via radio circuitry 330. As described above, in some aspects, the UE may be configured to use multiple wireless communication standards for wireless communication.

[0165] As further described herein, UE 106 (and / or base station 102) may include hardware and software components for operating control signaling to enhance the reliability of transmission and reception using a physical control channel (e.g., PDSCH), as described in further detail herein. The processor 302 of UE device 106 may be configured to implement some or all of the methods described herein, for example by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). In other respects, 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). Furthermore, processor 302 may be coupled to, for example, Figure 3 The processor 302 may also implement various other applications and / or interoperate with said other components to enable multimedia and broadcast service reception, as well as simultaneous operation with unicast reception, according to the aspects disclosed herein.

[0166] In some aspects, the radio circuit 330 may include a separate controller dedicated to controlling communications for various corresponding RAT standards. For example, such as Figure 3 As shown, the radio circuit 330 may include a Wi-Fi controller 356, a cellular controller (e.g., an LTE and / or NR controller) 352, and a BLUETOOTH controller. TM Controller 354, and in at least some aspects, one or more of these controllers, or all of them, may be implemented as corresponding integrated circuits (referred to as ICs or chips), which communicate with each other and with the SOC 300 (more specifically, with the processor 302). For example, Wi-Fi controller 356 may communicate with cellular controller 352 via a cell-ISM link or WCI interface, and / or BLUETOOTH TM Controller 354 can communicate with cellular controller 352 via a cell-ISM link, etc. Although three independent controllers are shown within radio circuitry 330, other aspects of having fewer or more similar controllers for various different RATs can be implemented in UE device 106. For example, in Figure 5 At least one exemplary block diagram illustrating some aspects of the cellular controller 352 is shown, and will be further described below.

[0167] Figure 4 - Block diagram of an exemplary base station

[0168] Figure 4 A block diagram of an exemplary base station 102 according to some aspects is shown. It should be noted that... Figure 4The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 404 capable of executing program instructions specific to base station 102. Processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuitry or device, which may be configured to receive addresses from processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0169] Base station 102 may include at least one network port 470. Network port 470 may be configured to be coupled to a telephone network and provide access rights as described above. Figure 1 and Figure 2 The telephone network described herein includes multiple devices such as UE device 106. Network port 470 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices such as UE device 106. In some cases, 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).

[0170] Base station 102 may include at least one antenna 434, and may include multiple antennas (e.g., shown by antennas 434a and 434b) for wireless communication with mobile devices and / or other devices. Antennas 434a and 434b are shown as examples, and base station 102 may include fewer or more antennas. Generally, one or more antennas that may include antenna 434a and / or antenna 434b are collectively referred to as antenna 434. Antenna 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE device 106 via radio circuit 430. Antenna 434 may communicate with radio circuit 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. Radio circuit 430 may be designed to communicate via various wireless telecommunication standards, including but not limited to LTE, LTE-A, 5G-NR (or simply NR), WCDMA, CDMA2000, etc. The processor 404 of base station 102 may be configured to implement some or all of the methods described herein, for example by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) to cause base station 102 to implement signaling for supplying location resources requested by a UE via physical layer signaling, as disclosed herein. Alternatively, processor 404 may be configured as a programmable hardware element such as a 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), base station 102 may be designed as an access point (AP), in which case 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 radio component 430 may be designed to communicate according to the Wi-Fi standard. Base station 102 may operate according to various methods and aspects thereof disclosed herein to enable multimedia and broadcast service reception as well as simultaneous operation with unicast reception.

[0171] Figure 5 - Block diagram of an exemplary cellular communication circuit

[0172] Figure 5 An exemplary simplified block diagram of a cellular controller 352, exemplified according to some aspects, is shown. It should be noted that... Figure 5The block diagram of the cellular communication circuit is merely one example of possible cellular communication circuits; other circuits, such as those including or coupled to sufficient antennas for different RATs to perform uplink activities using independent antennas, or those including or coupled to fewer antennas, such as those that can be shared among multiple RATs, are also possible. According to some aspects, the cellular communication circuit 352 may be included in a communication device such as the communication device 106 described above. As mentioned above, among other devices, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop computer, notebook computer, or portable computing device), a tablet computer, and / or a combination of these devices.

[0173] Cellular communication circuitry 352 may be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 335a-b and 336 as shown in the figure. In some aspects, cellular communication circuitry 352 may include dedicated receive chains for multiple RATs (including and / or coupled (e.g., communicatively; directly or indirectly) to dedicated processors and / or radio components (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as... Figure 5 As shown, the cellular communication circuit 352 may include a first modem 510 and a second modem 520. The first modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the second modem 520 may be configured for communication according to a second RAT (e.g., such as 5G NR).

[0174] As shown, the first modem 510 may include one or more processors 512 and a memory 516 communicating with the processors 512. The modem 510 may communicate with a radio frequency (RF) front-end 530. The RF front-end 530 may include circuitry for transmitting and receiving radio signals. For example, the RF front-end 530 may include a receiver circuitry (RX) 532 and a transmitter circuitry (TX) 534. In some aspects, the receiver circuitry 532 may communicate with a downlink (DL) front-end 550, which may include circuitry for receiving radio signals via an antenna 335a.

[0175] Similarly, the second modem 520 may include one or more processors 522 and a memory 526 communicating with the processors 522. The modem 520 may communicate with an RF front-end 540. The RF front-end 540 may include circuitry for transmitting and receiving radio signals. For example, the RF front-end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some aspects, the receiving circuitry 542 may communicate with a DL front-end 560, which may include circuitry for receiving radio signals via an antenna 335b.

[0176] In some aspects, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 336. Therefore, when cellular communication circuitry 352 receives an instruction to transmit according to a first RAT (e.g., supported by first modem 510), switch 570 may be switched to a first state allowing first modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 352 receives an instruction to transmit according to a second RAT (e.g., supported by second modem 520), switch 570 may be switched to a second state allowing second modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).

[0177] As described herein, the first modem 510 and / or the second modem 520 may include hardware and software components for implementing any of the various features and techniques described herein. For example, processors 512, 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or in addition), processors 512, 522 may be configured as programmable hardware elements, such as FPGAs (Field-Programmable Gate Arrays) or as ASICs (Application-Specific Integrated Circuits). Alternatively (or in addition), processors 512, 522 may be configured to implement some or all of the features described herein by combining with one or more of other components 530, 532, 534, 540, 542, 544, 550, 570, 572, 335, and 336.

[0178] Furthermore, as described herein, processors 512 and 522 may include one or more processing elements. Therefore, processors 512 and 522 may include one or more integrated circuits (ICs) configured to perform the functions of processors 512 and 522. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processors 512 and 522.

[0179] In some aspects, the cellular communication circuit 352 may include only one transmit / receive chain. For example, the cellular communication circuit 352 may not include modem 520, RF front-end 540, DL front-end 560, and / or antenna 335b. As another example, the cellular communication circuit 352 may not include modem 510, RF front-end 530, DL front-end 550, and / or antenna 335a. In some aspects, the cellular communication circuit 352 may also not include switch 570, and RF front-end 530 or RF front-end 540 may communicate with UL front-end 572, for example, through direct communication.

[0180] Multimedia broadcasting and multicast services

[0181] Multicast and broadcast service (MBS), or multimedia broadcast and multicast service (MBMS), refers to a point-to-multipoint communication scheme that simultaneously transmits data packets from a single source to multiple destinations. Broadcast is content delivery to all users, while multicast refers to content distribution among a specific group of users who have subscribed to a given multicast service. The geographical area that transmits multicast and broadcast content is called an area. An MBS area is typically a collection of one or more base stations that transmit the same content, and each base station with MBS service capability can belong to one or more MBS areas, each identified by a unique area identifier. When a UE is in a connected state (e.g., RRC connected state), a mobile station (or UE) can receive MBS content within an MBS area. UEs in an MBS area are typically assigned a common multicast site identifier. Conversely, unicast reception refers to a transmission directed to a single device or UE.

[0182] In 3GPP Long Term Evolution (LTE), during MBMS Point-to-Multipoint (PTM) transmissions, the UE receives MBMS services via the same frequency, regardless of the UE's Radio Resource Control (RRC) state. For example, the reception of MBMS PTM transmissions can be the same regardless of whether the UE is in a connected or idle state. In 3GPP New Radio (NR), a cell can be a wideband cell divided into multiple Bandwidth Parts (BWPs) (e.g., 4 BWPs), where the UE communicates on one BWP at a time in each serving cell. Therefore, it is necessary to define how the NW (e.g., the base station) can simultaneously provide MBMS transmissions and possible unicast transmissions to a connected UE (also known as a connected UE) in an NR wideband cell, and how frequencies are allocated and used during MBMS and unicast transmissions.

[0183] MBMS-specific BWP for MBMS-PTM transmission

[0184] In some aspects, the network (e.g., base station; gNB) can configure MBMS-specific BWPs for the UE for PTM transmissions to the UE for each serving cell. For example, in cases where the UE operates using multiple serving cells or multiple cells serve the UE, a corresponding MBMS-specific BWP can be configured for each cell for PTM transmissions to the UE. As previously mentioned, the UE can be configured with up to a specified number (e.g., four) of BWPs, and the allocation of one of these BWPs dedicated to MBMS-specific PTM transmissions may therefore affect the UE's BWP usage. The UE may have several different options to support a specified number (e.g., a maximum number) of BWPs. Three possible options are listed below. It should be noted that the specific number is provided by way of example to reflect the actual specific implementation related to the proposed standard, but the number of BWPs can be adapted according to the various aspects disclosed herein.

[0185] ●Option 1: The UE can support four (4) dedicated BWPs per serving cell plus additional MBMS-specific BWPs;

[0186] ●Option 2: The UE can support four (4) dedicated BWPs per serving cell plus additional MBMS-specific BWPs on the PCell or PSCell; and

[0187] ●Option 3: The UE can support four (4) dedicated BWPs, including MBMS-specific BWPs.

[0188] MBMS-specific BWPs can be used for DL ​​transmissions and can be cell-specific or UE-specific for each serving cell. It should be noted that when a UE is capable of receiving both MBMS and unicast transmissions simultaneously, the unicast BWP and the MBMS-specific BWP assigned to the UE can be active at the same time. In other words, in this sense, a UE can actually operate on two active BWPs simultaneously, but one BWP can be dedicated to unicast transmissions while the other can be dedicated to MBMS transmissions.

[0189] Some aspects of UE operation supporting MBMS-specific BWPs are as follows. The UE can receive all MBMS services via PTM in an MBMS-specific BWP used for a serving cell. The UE can provide information indicating the radio quality of the MBMS-specific BWP to the NW (e.g., to the base station), for example, via Channel State Information (CSI) reports (such as Layer 1 or L1 CSI reports) or via Measurement Reports (such as Layer 3 or L3 Measurement Reports). The network (e.g., the base station) can then adjust resources for subsequent MBMS PTM transmissions as needed based on the information provided by the UE. The UE can stop and start MBMS PTM reception on the MBMS-BWP based on at least one or more of the following scenarios:

[0190] ● The UE receives explicit instructions from the network (e.g., from the base station) to start or stop receiving MBMS PTM transmissions via common commands (e.g., via L1 or L2, i.e., Layer 2 signaling) — the common commands themselves can be transmitted via PTM transmissions and can be received by multiple UEs;

[0191] ● The UE receives explicit instructions from the network (e.g., from the base station) via UE-specific commands to start or stop receiving MBMS PTM transmissions—unlike the common commands described above, UE-specific commands can be used exclusively by the UE; or

[0192] ● The UE can determine which MBMS to receive and can start or stop receiving specific MBMS PTM transmissions accordingly—for example, there may be multiple MBMS provided via PTM transmissions on a specific MBMS BWP, and the UE can autonomously determine which MBMS to receive (if any).

[0193] In some instances, the UE may not have the capability to simultaneously receive unicast transmissions (e.g., via a UE-specific BWP) and MBMSPTM transmissions (e.g., via an MBMS-specific BWP). In such cases, the UE may operate as follows, depending on several aspects:

[0194] ●The UE can perform unicast transmission and PTM transmission reception according to time division multiplexing (TDM), which can be configured by the network (e.g., by the base station);

[0195] ● The UE can prioritize receiving unicast transmissions and can also receive PTM transmissions when no unicast transmission is occurring.

[0196] ●The UE can stop operating on MBMS-specific BWPs (or can stop using MBMS-specific BWPs) and rely on the network (e.g., the base station) to schedule MBMS transmissions via peer-to-peer (PTP) transmissions to the UE; or

[0197] ● The UE can provide the network (e.g., to the base station) with information indicating possible conflicts (between unicast and PTM transmissions) and / or the preferred TDM mode.

[0198] Figure 6 A first example of wireless communication is illustrated, in which an MBMS-specific BWP is assigned to a UE for MBMS-PTM transmission. In this first example, the UE can start and stop receiving MBMS PTM transmissions on an MBMS-specific BWP configured by the network (e.g., by a base station) via RRC. The network (e.g., a base station) can provide MBMS PTM transmission and scheduling configuration on the MBMS-specific BWP, and can also provide the UE with MBMS-related configuration (e.g., L2 configuration) information via RRC signaling. Figure 6 As shown, once the RRC connection between UE 602 and base station 604 has been established (as indicated by 606), base station 604 can configure / assign an MBMS-specific BWP for UE 602, and can also configure / assign BWP#1 for other communications of the UE (e.g., unicast transmissions) (as indicated by 608). UE 602 can notify base station 604 that reconfiguration is complete (as indicated by 610), and can subsequently begin receiving MBMS PTM transmissions via the MBMS-specific BWP (as indicated by 612). Once base station 604 reconfigures UE 602 to remove the MBMS-specific BWP, the UE can stop receiving (as indicated by 614).

[0199] Figure 7 A second example of wireless communication is shown, where an MBMS-specific BWP is allocated for MBMS-PTM transmission. In this second example, the UE can autonomously start and stop receiving MBMS PTM transmissions on the MBMS-specific BWP based on whether it is interested in a particular MBMS. The network (e.g., a base station) can provide the UE with all MBMS information of interest to the UE, and the UE can autonomously start or stop receiving on the MBMS-specific BWP based on its interest. Figure 7As shown, once the RRC connection between UE 702 and base station 704 has been established (as indicated by 706), base station 704 can configure / assign an MBMS-specific BWP for UE 702, and can also configure / assign BWP#1 for other communications of the UE (e.g., unicast transmissions) (as indicated by 708). UE 702 can notify base station 704 that reconfiguration is complete (as indicated by 710). Subsequently, base station 704 can perform MBMS PTM transmissions via the MBMS-specific BWPs (as indicated by 712), which the UE can receive when it is interested in MBMS (as indicated by 720). When the UE is not interested in MBMS, it can choose not to receive MBMS PTM transmissions (as indicated by 722).

[0200] Figure 8 A third example of wireless communication is illustrated, in which an MBMS-specific BWP is allocated for MBMS-PTM transmission. In this third example, the UE can start and stop receiving MBMS PTM transmissions on the MBMS-specific BWP according to a UE-specific command or indication (e.g., an L1 or L2 command / indication) from the network (e.g., from a base station). This contrasts with the fourth example (described in further detail below), in which a common command for multiple UEs is used for this purpose. Information instructing the start and stop of MBMS-PTM transmissions can be provided to the UE by the network (e.g., the base station) based on the UE's radio quality and / or based on conditions associated with the UE's data reception (e.g., the block error rate (BLER) for MBMS-PTM or unicast data reception). Information related to the start and stop of MBMS-PTM transmissions can be transmitted by the base station via an activated unicast BWP or via an MBMS-specific BWP as a UE-specific transmission. Figure 8As shown, once the RRC connection between UE 802 and base station 804 has been established (as indicated in 806), base station 804 can configure / assign an MBMS-specific BWP for UE 802, and can also configure / assign BWP#1 and BWP#2 for other UE-specific unicast communications, for example, at least one of BWP#1 or BWP#2 can be assigned for UE unicast transmissions (as indicated in 808). UE 802 can notify base station 804 that reconfiguration is complete (as indicated in 810). Subsequently, base station 804 can notify UE of the start of MBMS transmission via an MBMS-specific BWP or via one of BWP#1 or BWP#2 via UE-specific signaling (as indicated in 812). Then, base station can perform MBMS PTM transmission via an MBMS-specific BWP (as indicated in 814), and can notify UE of the stop of MBMS transmission via an MBMS-specific BWP or via one of BWP#1 or BWP#2 via UE-specific signaling (as indicated in 816).

[0201] Figure 9 A fourth example of wireless communication is shown, in which an MBMS-specific BWP is allocated for MBMS-PTM transmission. In this fourth example, the UE can start and stop receiving MBMS PTM transmissions on the MBMS-specific BWP according to a common command or instruction from the network (e.g., from a base station), in contrast to the third example (as described above), where a UE-specific command for a single UE is used for this purpose. The network (e.g., a base station) can provide a common command or instruction when the core network suspends or resumes MBMS transmissions. This common command / instruction can be transmitted via the MBMS-specific BWP. Figure 9 As shown, once the RRC connection between UE 902 and base station 904 has been established (as indicated by 906), base station 904 can configure / assign an MBMS-specific BWP for UE 902, and can also configure / assign BWP#1 and BWP#2 for other communications, such as at least one of BWP#1 or BWP#2 being assigned for UE unicast transmissions (as indicated by 908). UE 902 can notify base station 904 that reconfiguration is complete (as indicated by 910). Subsequently, base station 904 can notify UE of the start of MBMS transmission via a common command / signaling on the MBMS-specific BWP (as indicated by 912). Then, the base station can perform MBMS PTM transmission via the MBMS-specific BWP (as indicated by 914), and can notify UE of the stop of MBMS transmission via a common command on the MBMS-specific BWP (as indicated by 916).

[0202] Figure 10A fifth example of wireless communication is shown, in which an MBMS-specific BWP is assigned for MBMS-PTM transmission. In this fifth example, the UE is able to receive simultaneously on two different BWPs, and Figure 10 The communication illustrated includes simultaneous reception on both an MBMS-specific BWP and a unicast BWP. When the UE is able to receive simultaneously on both BWPs, the UE can receive both the MBMS and unicast transmissions simultaneously or at least partially simultaneously, for example, when two different (MBMS and unicast) transmissions partially overlap. The UE can report this capability to the network (e.g., to the base station) and can also report additional information related to this capability. For example, the UE can send information to the base station indicating whether the UE can support simultaneous reception on an MBMS-specific BWP with the same subcarrier spacing or on another BWP with different subcarrier spacings. In some aspects, the UE can provide this additional information in the access stratum (AS) radio quality report transmitted by the UE to the base station. If the UE does not transmit this additional information to the base station, the base station can operate under the assumption that if the subcarrier spacing of the MBMS-specific BWP is different from the subcarrier spacing of another (e.g., UE-dedicated or UE-specific allocated unicast) BWP, the UE cannot receive simultaneously via both the MBMS-specific BWP and the allocated unicast BWP. Figure 10 As shown, once the RRC connection between UE 1002 and base station 1004 has been established (as indicated by 1006), base station 1004 can configure / assign an MBMS-specific BWP for UE 1002, and can also configure / assign BWP#1 and BWP#2 for other communications, such as at least one of BWP#1 or BWP#2 being assigned for unicast transmission of the UE (as indicated by 1008). UE 1002 can notify base station 1004 that reconfiguration is complete (as indicated by 1010). Subsequently, base station 1004 can notify UE of the start of MBMS transmission (as indicated by 1012). Then, the base station can perform MBMS PTM transmission via the MBMS-specific BWP (as indicated by 1014), and can also simultaneously perform unicast transmission to the UE on the BWP (BWP#1 or BWP#2) assigned for unicast transmission (as indicated by 1016).

[0203] Figure 11 A sixth example of wireless communication is shown, where an MBMS-specific BWP is assigned for MBMS-PTM transmission. In this sixth example, the UE cannot receive simultaneously via two different BWPs, and Figure 11The communication illustrated includes prioritizing MBMS transmission over unicast transmission or unicast reception over MBMS transmission in the event of a collision (e.g., simultaneous transmission of MBMS and unicast data). When the UE cannot support simultaneous transmission of MBMS and unicast data, the UE can determine whether to perform MBMS reception or unicast reception first based on prioritization (e.g., according to prioritization configured by the network (e.g., by the base station). In some aspects, the UE can check the corresponding transmission modes corresponding to MBMS and unicast transmissions to determine which transmission to receive first. For example, the UE can check the unicast discontinuous reception (DRX) mode and the MBMS scheduling mode. When MBMS reception takes priority, the UE can perform reception first according to the MBMS scheduling mode. When unicast reception takes priority, the UE can perform unicast reception first following the DRX mode, and then perform MBMS reception when the UE is in a DRX-off state. The UE can also provide collision information to the network (e.g., to the base station). Figure 11 As shown, once the RRC connection between UE 1102 and base station 1104 has been established (as indicated by 1106), base station 1104 can configure / assign an MBMS-specific BWP for UE 1102, and can also configure / assign BWP#1 and BWP#2 for other communications, such as at least one of BWP#1 or BWP#2 being assigned to the UE for unicast transmission (as indicated by 1108). UE 1102 can notify base station 1104 that reconfiguration is complete (as indicated by 1110). Subsequently, base station 1104 can notify UE 1102 of the start of MBMS transmission (as indicated by 1112). Then, the base station can perform MBMS PTM transmission via the MBMS-specific BWP (as indicated by 1114), and can also perform unicast transmission to the UE on the BWP (BWP#1 or BWP#2) assigned for unicast transmission (as indicated by 1116). In some respects, UE 1102 may transmit conflict information (as indicated by 1118) to base station 1104, indicating a possible conflict between MBMS data transmission and unicast data transmission. In response to receiving the conflict information from UE 1002, base station 1004 may schedule unicast transmissions to UE 1002 based on the conflict information to avoid conflicts.

[0204] Figure 12A seventh example of wireless communication is shown, in which an MBMS-specific BWP is allocated for MBMS-PTM transmission. In this seventh example, MBMS and unicast transmissions can be performed using Time Division Multiplexing (TDM). The network (e.g., a base station) can configure TDM modes for MBMS and unicast transmissions for the UE to follow. In some aspects, the UE can also provide a TDM mode suggestion to the base station for the base station to configure the TDM mode. The UE can then receive MBMS and unicast transmissions according to the configured TDM mode. In some cases, MBMS PTM transmissions may be targeted at UEs with different corresponding capabilities, some of which can receive both MBMS and unicast transmissions simultaneously, while others cannot. In such cases, the TDM mode configured by the network (e.g., the base station) may be suitable for some UEs but not for others. When a base station performs MBMS PTM data transmission according to a configured TDM mode to accommodate UEs lacking the ability to continuously receive MBMS PTM data transmission (e.g., because the UE lacks the ability to simultaneously transmit MBMS PTM and unicast data), other UEs also served by the base station and capable of continuously receiving MBMS PTM data transmission may experience gaps or idle periods during the MBMS PTM transmission period when MBMS data is not being transmitted (according to TDM mode). However, when the base station performs continuous MBMS PTM data transmission (e.g., without any gaps) to accommodate UEs capable of continuously receiving MBMS PTM data transmission, other UEs also served by the base station but lacking the ability to continuously receive MBMS PTM data transmission may fail to receive some data transmitted during the MBMS PTM transmission. In such cases, the base station can retransmit the unreceived MBMS data via unicast transmission, as will be described in further detail below. Figure 12As shown, once the RRC connection between UE 1202 and base station 1204 has been established (as indicated by 1206), base station 1204 can configure / assign an MBMS-specific BWP for UE 1202, and can also configure / assign BWP#1 and BWP#2 for other communications. For example, at least one of BWP#1 or BWP#2 can be assigned for UE unicast transmission, and TDM transmission mode can be configured for MBMS transmission and unicast transmission (as indicated by 1208). UE 1202 can notify base station 1204 that reconfiguration is complete (as indicated by 1210). Subsequently, base station 1204 can notify UE 1202 of the start of MBMS transmission (as indicated by 1212). According to the first option (primarily accommodating UEs lacking the ability to continuously receive MBMS PTM data transmissions), base station 1204 can transmit MBMS packets 1230 on an MBMS-specific BWP and transmit unicast packets 1232 on a unicast BWP allocated for unicast transmission according to the configured TDM mode (as indicated by 1214 and 1216, respectively). According to the second option (primarily accommodating UEs capable of continuously receiving MBMS PTM data transmissions), base station 1204 can transmit MBMS packets 1240 on an uninterrupted MBMS-specific BWP and transmit unicast packets 1242 on a unicast BWP allocated for unicast transmission. However, for UEs lacking the ability to continuously receive MBMS PTM data transmissions, base station 1204 can also transmit MBMS packets #3 and #5 (of MBMS packets 1240) on a unicast BWP using PTP unicast transmission, which UE 1202 does not receive via PTM transmission on an MBMS-specific BWP. To some extent, base station 1204 can therefore retransmit MBMS packets #3 and #5 (MBMS packet 1240) on the unicast BWP to identify those packets that the UE did not receive on the MBMS-specific BWP (indicated by 1218 and 1220 respectively).

[0205] Figure 13 An eighth example of wireless communication is shown, in which an MBMS-specific BWP is allocated for MBMS-PTM transmission. In this eighth example, the NW (e.g., a base station) can allocate an MBMS-specific BWP based on the UE's capabilities. In other words, the base station can use information indicating the UE's capabilities to determine on which BWP MBMS packets will be transmitted and whether a separate MBMS-specific BWP can be allocated. In cases where the UE cannot support simultaneous MBMS and unicast reception on different, non-overlapping BWPs, the network can optionally provide one of the following configurations for the corresponding transmission of MBMS and unicast packets.

[0206] ●Option 1: MBMS BWP (BWP that transmits MBMS packets over it) can overlap with unicast BWP;

[0207] ●Option 2: The same BWP can be used for both MBMS and unicast transmissions. In this case, the MBMS BWP can be embedded within or be part of a BWP allocated for unicast transmission; or

[0208] ●Option 3: No MBMS BWP is assigned, and MBMS packets are transmitted via unicast peer-to-peer (PTP) transmission.

[0209] Communication performed according to the above three options Figure 13 As shown in the diagram. First, an RRC connection can be established between UE 1302 and base station 1304 (as indicated in 1306). According to option 1, UE 1302 can signal to base station 1304 that the UE has the capability to simultaneously receive MBMS and unicast transmissions. For example, UE 1302 can send a message to base station 1304 indicating this capability (as indicated in 1308). In response, base station 1304 can reconfigure UE 1302, assigning an MBMS-specific BWP to UE 1302, and also assigning BWP#1 for other communications, such as for unicast transmissions of UE 1302 (as indicated in 1310). According to option 2, UE 1302 can notify base station 1304 that the UE does not have the capability to simultaneously receive MBMS and unicast transmissions (as indicated in 1312). In response, base station 1304 may reconfigure UE 1302, overlapping the MBMS BWP and BWP#1 and allocating the overlapping BWP 1322 to the UE for both MBMS and unicast transmissions (as indicated in 1314). According to option 3, UE 1302 may notify base station 1304 that the UE does not have the capability to simultaneously receive MBMS and unicast transmissions (as indicated in 1316). In response, base station 1304 may reconfigure UE 1302, allocating the MSBM BWP within BWP#1 to use BWP#1 1320 for both MBMS and unicast transmissions (as indicated in 13148).

[0210] MBMS-specific resources for PTM transmission

[0211] In some respects, instead of allocating / configuring additional MBMS-specific BWPs that can be used by the UE, the network (e.g., a base station) can configure MBMS-specific resources, such as MBMS-specific frequency resources, within a UE-specific BWP allocated / configured for the UE. For example, a base station can configure multiple dedicated BWPs for the UE, where specific frequency resources within a given BWP (among the dedicated BWPs for the UE) are configured for MBMS PTM data transmission, thereby configuring the given BWP as an MBMS BWP on which the UE can receive MBMS PTM transmissions. When a given BWP is the active BWP on which the UE communicates, the base station can provide MBMS data transmission on the MBMS BWP. Where applicable, the base station can provide the UE with MBMS PTM scheduling information associated with the MBMS BWP so that the UE can receive MBMS transmissions on the MBMS BWP. For example, the base station can indicate to the UE whether a given UE-specific BWP can be used for PTM data scheduling and transmission, and can provide the UE with corresponding scheduling configuration / resource information, such as CORSET, search space, etc. Once MBMS PTM scheduling has been configured for the active BWP, the UE can monitor the PTM scheduling and receive MBMS data accordingly. Alternatively, the UE may rely on the base station to deliver MBMS data to the UE via the current / active BWP according to the base station's PTP unicast scheduling. It should be noted that the MBMSPTM data transmission start / stop mechanism and PTM / PTP conflict avoidance mechanism described above regarding the specific implementation of MBMS-specific BWPs can be equally applied to MBMS-specific resource allocation for PTM data transmission.

[0212] exist Figure 14The diagram illustrates an example of signaling where MBMS-specific resources (e.g., MBMS-specific frequency resources) are used for PTM transmissions. Once an RRC connection has been established between UE 1402 and base station 1404 (as indicated in 1406), base station 1404 can configure / assign BWP#1 and BWP#2 for UE 1402 (as indicated in 1408). Base station 1404 can indicate that MBMS transmissions can occur in / on BWP#1, while BWP#2 may be intended solely for unicast transmissions. Base station 1404 can also provide UE 1402 with scheduling information regarding MBMS PTM transmissions in BWP#1. UE 1402 can notify base station 1404 that reconfiguration is complete (as indicated in 1410). When BWP#1 is active, base station 1404 can transmit MBMS data on the active BWP#1 (as indicated in 1412) according to the configured schedule for MBMS PTM transmission, and also transmit unicast data on the applicable BWP#1 (as indicated in 1414). When BWP#2 is active, since no dedicated MBMS resources and the schedule for MBMS PTM transmission are configured for BWP#2, both MBMS data and unicast data are transmitted by base station 1404 via PTP transmission (as indicated in 1416). The handover between PTP transmission and PTM transmission can be implemented in various ways. Figure 15 The document shows three options for L2 packet processing when switching between PTP and PTM.

[0213] Figure 15Partial examples of layers (L1 and L2) in a communication architecture are provided. According to the first option 1002, a single channel is configured and associated with RLC, PDCP (Packet Data Convergence Protocol), and SDAP (Service Data Adaptation Protocol). When switching between BWP#1 and BWP#2, the L2 processing of data can be the same, regardless of whether the data is received via PTM transmission on BWP#1 or PTP transmission on BWP#2. According to the second option 1004, RLC can be configured separately for MRB and DRB. That is, different radio bearers can be configured for PTM and PTP transmissions, and therefore the L2 RLC processing can be different for PTM transmissions on BWP#1 and PTP transmissions on BWP#2. For example, a PTM-specific logical channel ID can be used for data transmission / reception in PTM transmissions, and the same PDCP data can be transmitted via different DRB-specific logical channels. According to the third option 1006, completely different resources are configured for PTM and PTP transmissions. Therefore, in addition to the separate RLC logical channels corresponding to MRB and DRB respectively, separate corresponding PDCP stacks are used for receiving data via PTM and receiving data via PTP, as shown in the figure.

[0214] UE capabilities for MBMS and unicast reception

[0215] The network (e.g., a base station) can provide a service cell set configuration (for carrier aggregation, CA and / or dual connectivity, DC) based on the UE's ability to simultaneously receive MBMS-PTM and unicast transmissions. For CA / DC capabilities, the UE can report its ability to simultaneously receive MBMS-PTM and unicast to the network, for example, to the serving base station. This capability can be defined at different granularities, such as per frequency band combination, per frequency band, or per UE. For per-UE capability, the network can assume that for the optimal CA / DC combination supported by all UEs, the UE can support MBMS and unicast transmissions on different serving cells. For non-CA capabilities, such as in a single-cell scenario, at least two options can be implemented:

[0216] ●Option 1: The UE can report whether it supports unicast and MBMS reception on the same cell. Support can be per cell, per frequency band, or a combination of frequency bands. If the UE cannot support unicast and MBMS reception on the same cell, the network may not configure MBMS-PTM and unicast PTP on the same serving cell; and

[0217] ●Option 2: The UE can report whether it supports unicast and MBMS reception on the same or different BWPs, on the same or different frequencies, and / or on the same or different subcarrier spacings within the same serving cell. If the UE cannot support unicast and MBMS reception as listed above, the network may not configure MBMS-PTM and unicast PTP on non-overlapping frequency resources, or the network may provide MBMS-PTM transmission via a BWP activated by the UE.

[0218] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting 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 authorized use should be clearly explained to users.

[0219] Various aspects of this disclosure can be implemented in any of a variety of forms. For example, in some aspects, this disclosure can be implemented as a computer-implemented method, a computer-readable storage medium, or a computer system. In other aspects, this disclosure can be implemented using one or more custom-designed hardware devices such as ASICs. In still other aspects, this disclosure can be implemented using one or more programmable hardware elements such as FPGAs.

[0220] In some aspects, a non-transitory computer-readable storage medium (e.g., a non-transitory memory 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 performs a method, such as any of the methods described herein, or any combination of the methods described herein, or any subset of any methods described herein, or any combination of such subsets.

[0221] In some aspects, a device (e.g., a UE) may be configured to include a processor (or a set of processors) and a memory medium (or memory elements), wherein the memory medium stores program instructions, and the processor is configured to read from and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various methods described herein (or any combination of the methods described herein, or any subset of any methods described herein, or any combination of such subsets). The device may be implemented in any of a variety of forms.

[0222] By interpreting each message / signal X received by a user equipment (UE) or device in the downlink as a message / signal X transmitted by a base station / network node, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by a base station / network node, any method described herein for operating a UE can serve as the basis for a corresponding method for operating the base station or appropriate network node.

[0223] Although the foregoing aspects have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the foregoing disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A baseband processor, the baseband processor comprising: The memory, configured to store information, and A processing circuit coupled to the memory, the processing circuit being configured to: During wireless communication, in a connected state, MBMS messages in a Multimedia Broadcast and Multicast Service (MBMS) transmission are received on a first frequency resource within a second bandwidth portion (BWP), wherein the second BWP is configured as a user equipment (UE) dedicated BWP configuration, and the first frequency resource is specifically allocated for MBMS transmission within the second BWP, wherein the MBMS transmission is a point-to-multipoint data transmission; and When the third BWP is active, unicast transmissions are received on the third BWP, the unicast transmissions including the MBMS data transmitted by the MBMS.

2. The baseband processor according to claim 1, wherein the processing circuit is further configured to: Receive an indication from the second BWP with UE-specific configuration for MBMS transmission; and Receive corresponding scheduling configuration information, including control resource set (CORESET) and search space information.

3. The baseband processor according to claim 1, wherein the processing circuit is further configured to: Receive a second multimedia broadcast message, which is transmitted in a second MBMS transmission as a point-to-point transmission; in, When switching between point-to-point and point-to-multipoint transmission, MBMS data transmission has a common Packet Data Convergence Protocol (PDCP) entity and different corresponding Radio Link Control (RLC) entities.

4. The baseband processor according to claim 1, wherein the processing circuit is further configured to: Capability information is generated for transmission to the base station, wherein the capability information indicates support for simultaneous reception of MBMS transmission and unicast transmission.

5. The baseband processor of claim 4, wherein the capability information includes a first indication of support for receiving temporally overlapping MBMS and unicast transmissions.

6. The baseband processor according to claim 1, wherein the UE-specific BWP configuration is a UE-specific configuration.

7. A base station, comprising: The memory, configured to store information, and A processing circuit coupled to the memory, the processing circuit being configured to: During wireless communication, MBMS messages in Multimedia Broadcast and Multicast Service (MBMS) transmission are transmitted to a connected User Equipment (UE) on a first frequency resource within a second bandwidth portion (BWP), wherein the second BWP is configured as a UE-dedicated BWP configuration, and the first frequency resource is specifically allocated for MBMS transmission within the second BWP, wherein the MBMS transmission is point-to-multipoint data transmission; and When the third BWP is active for the UE, unicast transmission is transmitted on the third BWP, the unicast transmission including the MBMS data transmitted by the MBMS.

8. The base station according to claim 7, wherein the processing circuit is further configured to: Transmit an indication of the second BWP for MBMS transmission with UE-specific configuration; and The transmission includes corresponding scheduling configuration information for control resource sets (CORESET) and search space information.

9. The base station according to claim 7, wherein the processing circuit is further configured to: A second multimedia broadcast message is transmitted in a second MBMS transmission that is a point-to-point transmission. in, When switching between point-to-point and point-to-multipoint transmission, MBMS data transmission has a common Packet Data Convergence Protocol (PDCP) entity and different corresponding Radio Link Control (RLC) entities.

10. The base station according to claim 7, wherein the processing circuit is further configured to: The UE receives capability information indicating that it supports simultaneous reception of MBMS and unicast transmissions.

11. The base station of claim 10, wherein the capability information includes a first indication of support for receiving temporally overlapping MBMS transmissions and unicast transmissions.

12. The base station according to claim 7, wherein the UE-specific BWP configuration is a UE-specific configuration.

13. A method for wireless communication, the method comprising: During wireless communication, in a connected state, MBMS messages in a Multimedia Broadcast and Multicast Service (MBMS) transmission are received on a first frequency resource within a second bandwidth portion (BWP), wherein the second BWP is configured as a user equipment (UE) dedicated BWP configuration, and the first frequency resource is specifically allocated for MBMS transmission within the second BWP, wherein the MBMS transmission is a point-to-multipoint data transmission; and When the third BWP is active, unicast transmissions are received on the third BWP, the unicast transmissions including the MBMS data transmitted by the MBMS.

14. The method of claim 13, further comprising receiving: An indication of the second BWP with UE-specific configuration for MBMS transmission; and This includes the corresponding scheduling configuration information for the control resource set (CORESET) and search space information.

15. The method of claim 13, further comprising receiving a second multimedia broadcast message, the second multimedia broadcast message being transmitted in a second MBMS transmission as a point-to-point transmission, wherein, When switching between point-to-point and point-to-multipoint transmission, MBMS data transmission has a common Packet Data Convergence Protocol (PDCP) entity and different corresponding Radio Link Control (RLC) entities.

16. The method of claim 13, further comprising generating capability information indicating support for simultaneous reception of MBMS transmission and unicast transmission.

17. The method of claim 16, wherein the capability information includes a first indication of support for receiving temporally overlapping MBMS transmissions and unicast transmissions.

Images