WO2018144081A1 - Capability and coverage determination for multimedia broadcast multicast service - Google Patents

Capability and coverage determination for multimedia broadcast multicast service Download PDF

Info

Publication number
WO2018144081A1
WO2018144081A1 PCT/US2017/057967 US2017057967W WO2018144081A1 WO 2018144081 A1 WO2018144081 A1 WO 2018144081A1 US 2017057967 W US2017057967 W US 2017057967W WO 2018144081 A1 WO2018144081 A1 WO 2018144081A1
Authority
WO
WIPO (PCT)
Prior art keywords
capability
targeted
indication
base station
broadcast
Prior art date
Application number
PCT/US2017/057967
Other languages
English (en)
French (fr)
Inventor
Alberto Rico Alvarino
Miguel Griot
Kapil Bhattad
Haris Zisimopoulos
Lenaig Genevieve CHAPONNIERE
Mungal Dhanda
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to CN201780085547.8A priority Critical patent/CN110249587B/zh
Priority to US16/476,160 priority patent/US11019602B2/en
Priority to KR1020197022556A priority patent/KR20190110557A/ko
Priority to BR112019015810-3A priority patent/BR112019015810A2/pt
Priority to KR1020227017461A priority patent/KR102670603B1/ko
Priority to EP17795139.9A priority patent/EP3577856B1/en
Publication of WO2018144081A1 publication Critical patent/WO2018144081A1/en
Priority to US17/326,235 priority patent/US11690082B2/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0205Traffic management, e.g. flow control or congestion control at the air interface
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/30Resource management for broadcast services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/51Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/54Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • the following relates generally to wireless communication, and more specifically to capability and coverage determination for multimedia broadcast multicast services.
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power).
  • multiple- access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, and orthogonal frequency division multiple access (OFDMA) systems, (e.g., a Long Term
  • a wireless multiple-access communications system may include a number of base stations or access network nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE).
  • UE user equipment
  • different UEs may have various capabilities, such as being able to support a certain bandwidth or maximum transport block (TB) size over a radio interface with a base station.
  • TB transport block
  • the newly added UE may not support the same capabilities as are being used by other connected UEs.
  • the described techniques relate to improved methods, systems, devices, or apparatuses that support determining UE capabilities, such as a category or a coverage level for broadcast or multicast content (e.g., content provided using a Multimedia Broadcast Multicast Service (MBMS)).
  • MBMS Multimedia Broadcast Multicast Service
  • the described techniques provide for configuring a radio interface to account for an indicated capability of a target UE.
  • a base station may receive an indication of a capability of a particular targeted UE.
  • the capability of the targeted UE may be specified by a service provider to deliver MBMS content, and subsequently associated with a radio interface between the base station and the target UE.
  • the radio interface may then be configured based at least in part on the indicated capability of the target UE, for example, by configuring a transport block size or bandwidth.
  • the base station may then transmit broadcast or multicast content to the UE using the configured radio interface.
  • a method of wireless communication may include receiving an indication of a targeted UE capability, the targeted UE capability specified by a service provider for the delivery of broadcast or multicast content and associated with a radio interface between the base station and a UE, configuring the radio interface based at least in part on the received indication of the targeted UE capability, and transmitting the broadcast or multicast content to the UE using the configured radio interface.
  • the apparatus may include means for receiving an indication of a targeted UE capability, the targeted UE capability specified by a service provider for the delivery of broadcast or multicast content and associated with a radio interface between the base station and a UE, means for configuring the radio interface based at least in part on the received indication of the targeted UE capability, and means for transmitting the broadcast or multicast content to the UE using the configured radio interface.
  • the apparatus may include a processor, memory in electronic communication with the processor, and
  • the instructions may be operable to cause the processor to receive an indication of a targeted UE capability, the targeted UE capability specified by a service provider for the delivery of broadcast or multicast content and associated with a radio interface between the base station and a UE, configure the radio interface based at least in part on the received indication of the targeted UE capability, and transmit the broadcast or multicast content to the UE using the configured radio interface.
  • a non-transitory computer readable medium for wireless communication may include instructions operable to cause a processor to receive an indication of a targeted UE capability, the targeted UE capability specified by a service provider for the delivery of broadcast or multicast content and associated with a radio interface between the base station and a UE, configure the radio interface based at least in part on the received indication of the targeted UE capability, and transmit the broadcast or multicast content to the UE using the configured radio interface.
  • Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for receiving, from a network node, a category of the UE, the indication of the targeted UE capability comprising the category.
  • the network node comprises a broadcast multicast service center (BMSC), or a MBMS gateway, or a combination thereof.
  • BMSC broadcast multicast service center
  • MBMS gateway a MBMS gateway
  • the indication of the targeted UE capability comprises a quality of service (QoS) class identifier (QCI).
  • QoS quality of service
  • QCI quality of service class identifier
  • Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for identifying a mapping between the QCI and a maximum bandwidth, or a maximum transport block size, or a combination thereof. Some examples of the method, apparatus, and non- transitory computer-readable medium described above may further include processes, features, means, or instructions for configuring the radio interface based at least in part on the identified mapping.
  • Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for receiving, from a network node, one or more temporary mobile group identities (TMGIs), the one or more TMGIs comprising the indication of the targeted UE capability.
  • Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for determining a category of the UE based at least in part on the received TMGI, the targeted UE capability comprising the determined category.
  • configuring the radio interface based at least in part on the received indication of the targeted UE capability comprises: determining a maximum bandwidth, or a maximum transport block size, or a combination thereof to be used to transmit the broadcast or multicast content.
  • Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for transmitting UE reports to a network node. Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for receiving an updated indication of a targeted UE capability from the network node, the radio interface modified based at least in part on the updated targeted UE capability.
  • the method may include receiving an indication of a targeted UE capability for the delivery of broadcast or multicast content and associated with a radio interface between the UE and a base station, identifying a supported capability of the UE, and receiving broadcast or multicast content using the radio interface based at least in part on the identified supported capability of the UE and on the targeted UE capability.
  • the apparatus may include means for receiving an indication of a targeted UE capability for the delivery of broadcast or multicast content and associated with a radio interface between the UE and a base station, means for identifying a supported capability of the UE, and means for receiving broadcast or multicast content using the radio interface based at least in part on the identified supported capability of the UE and on the targeted UE capability.
  • the apparatus may include a processor, memory in electronic communication with the processor, and
  • the instructions may be operable to cause the processor to receive an indication of a targeted UE capability for the delivery of broadcast or multicast content and associated with a radio interface between the UE and a base station, identify a supported capability of the UE, and receive broadcast or multicast content using the radio interface based at least in part on the identified supported capability of the UE and on the targeted UE capability.
  • the non-transitory computer-readable medium may include instructions operable to cause a processor to receive an indication of a targeted UE capability for the delivery of broadcast or multicast content and associated with a radio interface between the UE and a base station, identify a supported capability of the UE, and receive broadcast or multicast content using the radio interface based at least in part on the identified supported capability of the UE and on the targeted UE capability.
  • the indication of the targeted UE capability may be received from a service provider.
  • the targeted UE capability may be a UE category or a UE coverage enhancement level.
  • receiving the indication of the targeted UE capability comprises: receiving the indication of the targeted UE capability in one or more of a user service description (USD), a single cell multipoint control channel (SC-MCCH), or a system information block (SIB).
  • USD user service description
  • SC-MCCH single cell multipoint control channel
  • SIB system information block
  • Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for monitoring for a downlink control information (DCI) format based at least in part on the SC- MCCH.
  • DCI downlink control information
  • receiving the indication of the targeted UE capability comprises: receiving the indication of the targeted UE capability in a transmission formatted based at least in part on a minimum supported capability of the UE.
  • the targeted UE capability comprises a maximum supported capability of the UE targeted by a service provider, or a minimum supported capability of the UE targeted by a service provider, or an actual supported capability of the UE targeted by the service provider, or a combination thereof.
  • Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for transmitting, by the UE, a request for content to a content provider, the request for content including a category of the UE, wherein the received indication of the targeted UE capability may be based at least in part on the category of the UE.
  • Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for transmitting, a report indicating successful receipt of the broadcast or multicast content.
  • the method may include determining a set of radio access parameters to be used to deliver broadcast or unicast content, transmitting the set of radio access parameters to a network node, receiving messages from at least one UE, the messages indicating successful reception of the broadcast or unicast content at the at least one UE, and modifying the set of radio access parameters based at least in part on the received messages.
  • the apparatus may include means for determining a set of radio access parameters to be used to deliver broadcast or unicast content, means for transmitting the set of radio access parameters to a network node, means for receiving messages from at least one UE, the messages indicating successful reception of the broadcast or unicast content at the at least one UE, and means for modifying the set of radio access parameters based at least in part on the received messages.
  • the apparatus may include a processor, memory in electronic communication with the processor, and
  • the instructions may be operable to cause the processor to determine a set of radio access parameters to be used to deliver broadcast or unicast content, transmit the set of radio access parameters to a network node, receive messages from at least one UE, the messages indicating successful reception of the broadcast or unicast content at the at least one UE, and modify the set of radio access parameters based at least in part on the received messages.
  • the non-transitory computer-readable medium may include instructions operable to cause a processor to determine a set of radio access parameters to be used to deliver broadcast or unicast content, transmit the set of radio access parameters to a network node, receive messages from at least one UE, the messages indicating successful reception of the broadcast or unicast content at the at least one UE, and modify the set of radio access parameters based at least in part on the received messages.
  • the set of radio access parameters comprises one or more of a coverage enhancement level, a UE category, a maximum bandwidth, or a maximum transport block size.
  • FIG. 1 illustrates an example of a wireless communications system that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • FIG. 2 illustrates an example of a wireless communications system that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • FIGs. 3 and 4 illustrate examples of process flows in wireless communications systems that support capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • FIGs. 5 and 6 show block diagrams of a wireless device that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • FIG. 7 shows a block diagrams of a base station capability and coverage manager that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • FIG. 8 illustrates a block diagram of a system including a device that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • FIGs. 9 and 10 show block diagrams of wireless devices that support capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • FIG. 11 shows a block diagrams of a UE capability and coverage manager that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • FIG. 12 illustrates a block diagram of a system including a device that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • FIGs. 13 through 17 show flowcharts illustrating methods for capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • broadcast or multicast content provided by a service provider may be transmitted from a broadcast multicast service center (BMSC) to a base station for distribution to one or more user equipments (UEs) using, for example, single-cell point-to-multipoint (SC-PTM) techniques.
  • Broadcast or multicast distribution may allow for flexible scheduling and efficient utilization of resources while limiting the complexity of operations and hardware necessary to receive the data. This, in turn, may allow for efficient narrowband communications, such as narrowband-internet of things (NB-IoT) or enhanced machine type communication (MTC) (eMTC), within a network.
  • NB-IoT narrowband-internet of things
  • MTC enhanced machine type communication
  • UEs e.g., IoT or MTC devices
  • TB transport block
  • Each UE may belong to a category based on its capabilities.
  • the service provider may accordingly inform the base station through the BMSC of a configuration supported by the UE.
  • a service provider may explicitly indicate to a BMSC the category for a base station to use for a radio interface with a UE. Additionally or
  • the category may be implicitly determined by the base station from signaling received from the BMSC.
  • a range of service identifiers e.g., temporary mobile group identities (TMGIs)
  • TMGIs temporary mobile group identities
  • a maximum UE capability may correspondingly be indicated in a user service description (USD) in a transmission, in a single cell multipoint control channel (SC- MCCH), or in a system information block (SIB).
  • USD user service description
  • SC- MCCH single cell multipoint control channel
  • SIB system information block
  • different UEs in a deployment of multiple UEs may prefer or use different levels of coverage enhancement.
  • the service provider may correspondingly indicate to the BMSC an expected coverage enhancement for the services.
  • the BMSC may set a target for a level of successful reception of transmissions, and adjust the level of coverage enhancement to reach the set target based on reports from a UE indicating whether the UE successfully received the transmissions.
  • aspects of the disclosure are initially described in the context of a wireless communications system. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to capability and coverage determination for multimedia broadcast multicast services.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • the wireless communications system 100 includes base stations 105, UEs 115, and a core network 130.
  • the wireless communications system 100 may be a Long Term Evolution (LTE) (or LTE- Advanced (LTE- A)) network, or a New Radio (NR) network.
  • LTE Long Term Evolution
  • LTE- A LTE- Advanced
  • NR New Radio
  • wireless communications system 100 may support enhanced broadband communications, ultra- reliable (i.e., mission critical) communications, low latency communications, and
  • Wireless communications system 100 may support indication of UE categories to enable the efficient implementation of radio resources for UEs 115 which have not yet communicated with a BMSC.
  • Base stations 105 may wirelessly communicate with UEs 115 via one or more base station antennas. Each base station 105 may provide communication coverage for a respective geographic coverage area 110.
  • Communication links 125 shown in wireless communications system 100 may include uplink (UL) transmissions from a UE 115 to a base station 105, or downlink (DL) transmissions, from a base station 105 to a UE 115.
  • Control information and data may be multiplexed on an uplink channel or downlink according to various techniques. Control information and data may be multiplexed on a downlink channel, for example, using time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • TTI transmission time interval
  • the control information transmitted during a transmission time interval (TTI) of a downlink channel may be distributed between different control regions in a cascaded manner (e.g., between a common control region and one or more UE-specific control regions).
  • UEs 115 may be dispersed throughout the wireless communications system 100, and each UE 115 may be stationary or mobile.
  • a UE 115 may also be referred to as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
  • a UE 115 may also be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a personal electronic device, a handheld device, a personal computer, a wireless local loop (WLL) station, an Internet of things (IoT) device, an Internet of Everything (IoE) device, a MTC device, an appliance, an automobile, or the like.
  • PDA personal digital assistant
  • WLL wireless local loop
  • IoT Internet of things
  • IoE Internet of Everything
  • a UE 115 may also be able to communicate directly with other UEs (e.g., using a peer-to-peer (P2P) or device-to-device (D2D) protocol).
  • P2P peer-to-peer
  • D2D device-to-device
  • One or more of a group of UEs 115 utilizing D2D communications may be within the coverage area 110 of a cell. Other UEs 115 in such a group may be outside the coverage area 110 of a cell, or otherwise unable to receive transmissions from a base station 105.
  • groups of UEs 115 communicating via D2D communications may utilize a one-to-many (1 :M) system in which each UE 115 transmits to every other UE 115 in the group.
  • a base station 105 facilitates the scheduling of resources for D2D communications.
  • D2D communications are carried out independent of a base station 105.
  • Some UEs 115 may be low cost or low complexity devices, and may provide for automated communication between machines, i.e., Machine-to- Machine (M2M) communication.
  • M2M or MTC may refer to data communication
  • M2M or MTC may refer to communications from devices that integrate sensors or meters to measure or capture information and relay that information to a central server or application program that can make use of the information or present the information to humans interacting with the program or application.
  • Some UEs 115 may be designed to collect information or enable automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
  • an MTC device may operate using half-duplex (one-way) communications at a reduced peak rate. MTC devices may also be configured to enter a power saving "deep sleep" mode when not engaging in active communications. In some cases, MTC or IoT devices may be designed to support mission critical functions and wireless communications system may be configured to provide ultra-reliable communications for these functions.
  • Base stations 105 may communicate with the core network 130 and with one another.
  • base stations 105 may interface with the core network 130 through backhaul links 132 (e.g., SI, etc.).
  • Base stations 105 may communicate with one another over backhaul links 134 (e.g., X2, etc.) either directly or indirectly (e.g., through core network 130).
  • Base stations 105 may perform radio configuration and scheduling for communication with UEs 115, or may operate under the control of a base station controller (not shown).
  • base stations 105 may be macro cells, small cells, hot spots, or the like.
  • Base stations 105 may also be referred to as eNodeBs (e Bs) 105.
  • a base station 105 may be connected by an SI interface to the core network 130.
  • the core network may be an evolved packet core (EPC), which may include at least one mobility management entity (MME), at least one S-GW, and at least one P-GW.
  • the MME may be the control node that processes the signaling between the UE 115 and the EPC. All user Internet Protocol (IP) packets may be transferred through the S-GW, which itself may be connected to the P-GW.
  • the P-GW may provide IP address allocation as well as other functions.
  • the P-GW may be connected to the network operators IP services.
  • the operators IP services may include the Internet, the Intranet, an IP Multimedia Subsystem (IMS), and a Packet- Switched (PS) Streaming Service (PSS).
  • IMS IP Multimedia Subsystem
  • PS Packet- Switched
  • PSS Packet- Switched
  • the core network 130 may provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions.
  • the network devices such as base station 105-a may include subcomponents such as an access network entity 105-b, which may be an example of an access node controller (ANC) 105.
  • Each access network entity 105-b may communicate with a number of UEs 115 through a number of other access network transmission entities 105-c, each of which may be an example of a smart radio head, or a transmission/reception point (TRP).
  • TRP transmission/reception point
  • each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or consolidated into a single network device (e.g., a base station 105).
  • network devices 105 may include a base station capability and coverage manager 101, which may receive an indication of a targeted UE capability, where the targeted UE capability may be specified by a service provider for the delivery of broadcast or multicast content and associated with a radio interface between the network device 105 and a UE 115.
  • base station capability and coverage manager 101 may configure the radio interface based on the received indication of the targeted UE capability and transmit the broadcast or multicast content to the UE using the configured radio interface.
  • UEs 115 may include a UE capability and coverage manager 102, which may receive an indication of a targeted UE capability for the delivery of broadcast or multicast content and associated with a radio interface between the UE 115 and a base station 105.
  • UE capability and coverage manager 102 may identify a supported capability of the UE 115 and receive broadcast or multicast content using the radio interface based on an identified supported capability of the UE 115 and the targeted UE capability.
  • Wireless communications system 100 may be a packet-based network that operate according to a layered protocol stack.
  • PDCP Packet Data Convergence Protocol
  • a radio link control (RLC) layer may in some cases perform packet segmentation and reassembly to communicate over logical channels.
  • RLC radio link control
  • a medium access control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer may also use hybrid automatic repeat request (HARQ) to provide retransmission at the MAC layer to improve link efficiency.
  • HARQ hybrid automatic repeat request
  • the radio resource control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network device, such as a base station 105 (or component of a base station 105), or core network 130 supporting radio bearers for user plane data.
  • RRC radio resource control
  • PHY physical
  • Wireless communications system 100 may include a RLC layer that connects higher layers (e.g., RRC and PDCP) to the lower layers (e.g., the MAC layer).
  • the RLC layer may be located between the PDCP layer and the MAC layer in the user plane protocol stack.
  • the RLC layer may perform segmentation and reassembly of upper layer packets in order to adapt them to the size which can actually be transmitted over the radio interface.
  • the RLC layer also performs retransmission to recover from packet losses.
  • the RLC layer may perform reordering to compensate for out-of-order reception due to HARQ operation in the MAC layer. There may be one RLC entity defined per radio bearer.
  • a base station 105 may broadcast or multicast data to a UE 115.
  • Wireless communications system 100 may include a BMSC, which may be a server defined for evolved MBMS (eMBMS) or MBMS, and configured to transmit multicast data files to the UE 1 15 through the base station 105 and an MBMS-GW.
  • the MBMS-GW may be a network entity used for forwarding packets in the core network 130. That is, the MBMS-GW may forward packets to addresses set for different ANCs 105 by an MME (e.g., via an MCE).
  • Broadcast or multicast data may be transmitted on a control channel using, for example, single-cell point-to-multipoint (SC-PTM) or eMBMS techniques. These techniques may allow a network to flexibly schedule resources and provide broadcast or multicast services, and may also allow UEs 115 (e.g., IoT devices or MTC devices) to receive services of interest without undue complexity or overhead.
  • SC-PTM single-cell point-to-multipoint
  • eMBMS eMBMS
  • SC-PTM may be associated with a fewer number of resources used for communication in certain geographic areas (e.g., as compared to a multicast-broadcast single frequency network (MBSFN) transmissions), flexible resource allocation (e.g., due to dynamic scheduling), and may be multiplexed in the frequency domain with unicast transmissions for enhanced spectral efficiency.
  • a broadcast area may be dynamically adjusted to fit a geographic area for certain services (e.g., group calls) without a pre-establishment of MBMS bearers over a predefined geographic area.
  • eMBMS or SC-PTM services may be associated with or identified by a TMGI.
  • a server within core network 130 may provide a TMGI to identify an eMBMS or SC-PTM session within wireless
  • a TMGI may be a combination of a network or system identity, such as a public land mobile network (PLMN) and a service identity.
  • PLMN public land mobile network
  • UEs 115 in wireless communication system may be associated with various UE categories that are representative of capabilities of a UE 115, where a UE category may define a combined uplink and downlink capability of the UE 115.
  • a UE capability may indicate a maximum transport block size (e.g., a number of bits supported) and/or bandwidth supported by the UE 115.
  • the UE 115 may communicate its capability to the network through RRC or non-access stratus (NAS) signaling to ensure that downlink transmissions are supported by the UE 115.
  • the UE 115 may transmit a UE capability information message to the core network 130 when the UE 115 initially registers with the core network 130.
  • Downlink transmissions to the UE 115 by an ANC 105 may be based on respective UE categories for different UEs 115.
  • Wireless communications system 100 may support determining UE 115 capabilities, such as a category or a coverage level for broadcast or multicast content (e.g., content provided using MBMS).
  • the described techniques provide for configuring a radio interface to account for an indicated capability of a target UE 115.
  • a base station may receive an indication of a capability of a particular targeted UE 115.
  • the capability of the targeted UE 115 may be specified by a service provider to deliver MBMS content, and subsequently associated with a radio interface between the base station and the target UE 115.
  • the radio interface may then be configured based on the indicated capability of the target UE 115, for example, by configuring a transport block size or bandwidth.
  • the base station may then transmit broadcast or multicast content to the UE 115 using the configured radio interface.
  • FIG. 2 illustrates an example of a wireless communications system 200 that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • Wireless communications system 200 may include base station 105-a and ones or more UEs 115 which may be examples of the corresponding devices as described with reference to FIG. 1.
  • UE 115-a and UE 115-b may be examples of different types of NB-IoT devices, or different types of eMTC devices.
  • UE 115-a and UE 115-b may receive data from base station 105-a via communication links 125-a and 125-b, respectively.
  • Wireless communications system 200 may further include a service provider 205 (i.e., a content provider), a BMSC 210, and a MBMS gateway (MBMS-GW) 215, or a combination thereof.
  • a service provider 205 i.e., a content provider
  • BMSC 210 i.e., a BMSC 210
  • MBMS-GW MBMS gateway
  • wireless communications system 200 may support broadcasting or multicasting data.
  • Service provider 205 may communicate with BMSC 210 to negotiate quality of service (QoS) requirements, for example, to broadcast multimedia content (e.g., a video stream).
  • QoS requirements may include metrics such as a delay, an error rate, and a maximum bit rate that may be supported.
  • BMSC 210 may then set up a MBMS service (e.g., a MBMS bearer service) with base station 105-a through MBMS-GW 215.
  • BMSC 210 may send to base station 105-a the negotiated QoS requirements through MBMS-GW 215, and, based on the received QoS requirements, base station 105-a may then apply a radio configuration to a radio interface with the one or more UEs 115.
  • the radio configuration may include, for example, a modulation and coding scheme (MCS) including a modulation order and a code rate which may describe the information data rate for transmission. If, for example, a higher data rate is preferred, a relatively higher MCS scheme may be used.
  • MCS modulation and coding scheme
  • different UEs 115 may have different capabilities, for example, being able to support a larger TB size or a larger bandwidth (e.g., as compared to the TB size of bandwidth that other UEs 115 are capable of supporting).
  • a UE 115 may belong to a particular category, where the category may include other UEs 115 having similar capabilities.
  • the NB-IoT device may belong to a category of categories defining a maximum TB size (e.g., a first category Nl may define a maximum TB size of 680 bits, a second category N2 may define a maximum TB size of 2,536 bits, and a third category may define a maximum TB size of 1,352 bits).
  • a first category Nl may define a maximum TB size of 680 bits
  • a second category N2 may define a maximum TB size of 2,536 bits
  • a third category may define a maximum TB size of 1,352 bits.
  • the MTC device may belong to a category that may define a bandwidth and a maximum TB size (e.g., a first category Ml may define a bandwidth of 1.4 MHz and a maximum TB size of 1,000 bits, a second category M2 may define a bandwidth of 5 MHz and a maximum TB size of 4,008 bits, and a third category M32 may define a bandwidth of 20 MHz and a maximum TB size of 31,704 bits).
  • a first category Ml may define a bandwidth of 1.4 MHz and a maximum TB size of 1,000 bits
  • a second category M2 may define a bandwidth of 5 MHz and a maximum TB size of 4,008 bits
  • a third category M32 may define a bandwidth of 20 MHz and a maximum TB size of 31,704 bits.
  • BMSC 210 may establish a SC-PTM configuration with a UE 115 when the UE 115 is in a connected mode (i.e., when the UE 115 may send and receive data) according to the category in which the capabilities of the UE 115 are supported.
  • the UE 115 may have a functionality different than that of the already-connected UEs 115.
  • service provider 205 may inform base station 105-a, via BMSC 210 and MBMS-GW 215, of a configuration including a category supporting the capabilities of the new UE 115.
  • a method to efficiently optimize radio resources for a UE 115 that has not yet established a connection with a corresponding BMSC 210 may be desirable.
  • service provider 205 may first determine a respective category for the UE 115.
  • Service provider 205 may know a type of UE 115 to which the services of service provider 205 are targeted (e.g., to UEs 115-a for a metering service, to UEs 115-b that are smartwatches, etc.), in which case service provider 205 may determine the category of the UE 115 accordingly. Additionally or alternatively, service provider 205 may determine the category of the UE 115 based on over- the-top signaling from the UE 115. That is, the UE 115 may signal directly to service provider 205 the category corresponding to the capabilities of the UE 115.
  • service provider 205 may transmit information including the category to base station 105-a through BMSC 210 and MBMS-GW 215. Based on the information received from service provider 205 through BMSC 210 and MBMS-GW 215, base station 105-a may determine parameters for communication with the UE 115 corresponding the capabilities of the UE 115 including, for example, a bandwidth and a maximum TB size.
  • service provider 205 may explicitly indicate to BMSC 210 the category for BMSC 210 to use for a radio interface with the UE 115.
  • the category may be indicated in a field in an interface between service provider 205 and BMSC 210.
  • the indicated category may indicate a maximum category to be used. That is, while the indicated category may indicate a category that supports a relatively greater maximum TB size, a category that supports a relatively smaller maximum TB size may still be used.
  • a category M2 (defining, e.g., a maximum TB size of 4008 bits)
  • a category Ml (defining, e.g., a maximum TB size of 1000 bits) may be used.
  • the category may be included in the QoS requirements, as may have been negotiated between service provider 205 and BMSC 210.
  • the indicated category may, however, be overridden by BMSC 210, or BMSC 210 may reject the QoS requirements, if BMSC 210 determines that another category may be more suitable.
  • the interface between service provider 205 and BMSC 210 may not provide a category to be used.
  • BMSC 210 may, on its own, determine a category to be used for a radio interface between the BMSC 210 and the UE 115.
  • the category may be implicitly determined from signaling from BMSC 210 to base station 105-a.
  • a range of service identifiers e.g., TMGIs
  • BMSC 210 may determine a corresponding service identifier based on the category to be used.
  • BMSC 210 may then transmit the determined service identifier to base station 105-a via MBMS-GW 215.
  • base station 105-a may then determine parameters for communication with UE 115 corresponding to the capabilities of the UE 115 including, for example, a maximum bandwidth and a maximum TB size.
  • parameters for communication with the UE 115 including, for example, a maximum bandwidth and a maximum TB size.
  • QCI QoS class identifier
  • the QoS e.g., a QCI
  • a certain QoS may be associated with a UE or a category of UEs using a certain TB size, or maximum TB size.
  • the QoS (or QCI) may be associated with a UE or group of UEs with capabilities associated with a certain combination of bandwidths and TB size (or maximum values of these).
  • the BMSC may define the QCI such that the QCI is an operator defined QCI, for example, a non-standardized value that may be pre-arranged between the operator and service provider 205.
  • Capabilities of a UE 115 may be indicated in a USD in a transmission, in a SC- MCCH, or in a SIB. That is, the USD may contain an indication of a maximum capability, or an actual capability, of the UE 115, as may be received via MBMS or another broadcast channel.
  • a service identifier e.g., a TMGI
  • included in a transmission from a BMSC 210 to the UE 115 may include a field for a category that indicates a maximum capability for UEs 115 of the category. Then, if the UE 115 supports the category indicated in the received transmission, the UE 115 may successfully receive the transmission.
  • the USD may be transmitted using a default or pre-configured service identifier (e.g., a TMGI) indicating a reference category corresponding to a minimum capability of the UE 115 (e.g., for a B-IoT device, a TMGI X, or, for an eMTC device, a TMGI Y, where each of the TMGI X and TMGI Y may correspond to a relatively small minimum TB size).
  • a maximum capability, or a reference capability, of a UE 115 may be transmitted in radio access network (RAN) signaling, such as in a SC-MCCH or a SIB. The received maximum capability or reference capability may then be used to determine a downlink control information (DCI) format.
  • RAN radio access network
  • different UEs 115 in a deployment of multiple UEs 115 may use different levels of coverage enhancement.
  • a software update for a UE 115 that may be subject to higher path loss e.g., UE 115-a for a metering service in a basement
  • a software update for a UE 115 that may be subject to less path loss e.g., for audio streaming services to UE 115-b that is a smartwatch
  • Service provider 205 may accordingly indicate to BMSC 210 an expected coverage enhancement for the services in, for example, the QoS requirements.
  • service provider 205 may transmit a signal with a level of coverage enhancement selected from the set ⁇ c 0 , c , c 2 , c 3 ⁇ , where c 0 may represent no coverage enhancement, c x may represent a small coverage enhancement, c 2 may represent a medium coverage enhancement, and c 3 may represent a large coverage enhancement, each representing, for example, a dB value.
  • BMSC 210 may set a target for a level of successful reception and adjust the level of coverage enhancement to reach the set target based on received responses from UEs 115. For example, BMSC 210 may set a target of 99% reception of service. After announcing the service, each UE 115 in communication with BMSC 210 may report to BMSC 210 whether the UE 115 received the service. If BMSC 210 determines that the target level of successful reception was not met, BMSC 210 may then increase its coverage enhancement level to attempt to reach its target level of successful reception.
  • Service provider 205 may similarly apply this technique to adjust the level of coverage enhancement in the QoS requirements based on BMSC 210 reporting a level of successful reception to service provider 205. For example, if BMSC 210 determines that the target level of successful reception was not met, BMSC 210 may relay this information to service provider 205, and service provider 205 may then increase the level of coverage enhancement in the QoS requirements (e.g., from c x to c 2 ).
  • FIG. 3 illustrates an example of a process flow 300 in a wireless communications system that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • Process flow 300 includes UE 115-c and base station 105-b, which may be respective examples of a UE 115 and a base station 105 as described with reference to FIGs. 1 and 2.
  • Process flow 300 further includes service provider 205-a and BMSC 210-a, which may be respective examples of a service provider 205 and a BMSC 210 as described with reference to FIG. 2.
  • Process flow 300 may be an example of identifying and transmitting an indication of a UE capability and accordingly transmitting MBMS content based on the UE capability.
  • UE 115-c may optionally transmit to service provider 205-a, and service provider 205-a may receive from UE 115-c, a request for MBMS content.
  • UE 115-c may further indicate in the request for MBMS content a category corresponding to the capabilities of UE 115-c, where the category may define parameters (e.g., a bandwidth and maximum TB size) for UEs 115 having similar capabilities to UE 115-c.
  • the request for content may be transmitted via over-the-top signaling from UE 115-c to service provider 205-a. That is, UE 115-c may signal directly to service provider 205-a the category corresponding to the capabilities of UE 115-c.
  • service provider 205-a may determine a targeted UE capability for UE 115-c.
  • Service provider 205-a may determine the capability based on a category to which UE 115-c belongs. To determine the capability, or category defining a corresponding capability, service provider 205-a may already know a type of UE 115 to which the services of service provider 205-a are targeted (e.g., to UEs 115 for a metering service, to UEs 115 that are smartwatches, etc.) and to which UE 115-c belongs. In this case, service provider 205-a may determine the category of UE 115-c accordingly.
  • service provider 205-c may determine the category of UE 115-c based on over-the-top signaling from UE 115-c, for example, the request for MBMS content (e.g., via the request sent at 305).
  • service provider 205-a may transmit to BMSC 210-a, and BMSC 210-a may receive from service provider 205-a, an indication of the targeted UE capability.
  • the indication of the capability for UE 115-c may be included in a USD, SC-MCCH, or SIB within the transmission.
  • BMSC 210-a may transmit to base station 105-b, and base station 105-b may receive from BMSC 210-a, an indication of the capability for targeted UE 115-c.
  • the indication of the capability may be transmitted and received through a network node, where the network node may be, for example a MBMS-GW, or BMSC 210-a as described above.
  • the capability may have been specified by service provider 205-a for the delivery of MBMS content.
  • the indication may further include a category corresponding to UE 115-c.
  • the category may correspond to a set of UEs 115 having similar capabilities.
  • UE 115-c may be an example of an NB-IoT device, and the NB-IoT device may belong to a category that defines a maximum TB size.
  • the MTC device may belong to a category that may define a bandwidth and a maximum TB size.
  • the indication of the capability may include one or more TMGIs (i.e., service identifiers), where the TMGIs may implicitly indicate to the category to which UE 115-c belongs.
  • base station 105-b may identify a capability for the targeted UE 115-c. In one case, the capability may be identified based on an explicit indication received from service provider 205-a through BMSC 210-c and a MBMS-GW.
  • the capability of UE 115-c may be identified based on an indicated category to which UE 115-c belongs.
  • the category may be implicitly determined from the signaling from a network node (e.g., BMSC 210, or a MBMS-GW) to base station 105-b.
  • a range of TMGIs i.e., service identifiers
  • BMSC 210-a may have determined a corresponding service identifier based on the category corresponding to UE 115-c.
  • base station 105-b may then identify the parameters for communication with UE 115-c corresponding the capabilities of the UE 115-c.
  • the parameters for communication with the UE 115 based on a service identifier there may be a mapping between the negotiated QoS (e.g., using a QCI) and the maximum bandwidth and TB size corresponding to the negotiated QoS (e.g., using a QCI) and the maximum bandwidth and TB size corresponding to the negotiated QoS (e.g., using a QCI) and the maximum bandwidth and TB size corresponding to the
  • Base station 105-b may use the identified capability to accordingly configure a radio interface between base station 105-b and UE 115-c.
  • base station 105-b may transmit to UE 115-c, and UE 115-c may receive from base station 105-b, an indication of a targeted UE capability (e.g., a capability of UE 115-c).
  • the targeted UE capability may have been specified by service provider 205-a for the delivery of MBMS content.
  • the capability may be then be associated with and used to configure a radio interface between UE 115-c and base station 105-b.
  • the indication may be based on a minimum supported capability of UE 115-c.
  • the indication may be based on a maximum supported capability of a targeted UE (e.g., UE 115- c), or an actual supported capability of the targeted UE.
  • the indication may include a category corresponding to UE 115-c, where the category may correspond to a set of UEs 115 having similar capabilities.
  • the category may define parameters including, for example, a bandwidth and a maximum TB size.
  • the capability, or corresponding category may be indicated in a USD, SC-MCCH, or SIB within the transmission.
  • UE 115-c may then monitor for MBMS content (e.g., broadcast or multicast content), as UE 1 15-c may receive, illustratively, at 355.
  • the capability may further be used to determine a DCI format. In this case, UE 115-c may accordingly monitor for a DCI format based on the SC-MCCH.
  • base station 105-b may configure a radio interface based on the indicated capability of the targeted UE 115-c received from service provider 205-a through BMSC 210-a and a MBMS-GW.
  • UE 115-c may identify a supported capability of UE 115-c based on the indication of the capability of UE 115-c received at 330. The capability may be included in a category, where the category may define a bandwidth and a maximum TB size supported by UEs of the category to which UE 115-c corresponds.
  • UE 115-c may further determine whether the supported capability is compatible with the capabilities of UE 115-c. If the supported capability is compatible with the capabilities of UE 115-c, UE 115-c may then monitor for MBMS content (e.g., broadcast or multicast content), as UE 115-c may receive, illustratively, at 355.
  • MBMS content e.g., broadcast or multicast content
  • service provider 205-a may transmit to BMSC 210-a, and BMSC 210-a may receive from service provider 205-a, broadcast or multicast content (such as MBMS content).
  • BMSC 210-a may transmit to base station 105-b, and base station 105-b may receive from BMSC 210-a, MBMS content.
  • the MBMS content may be transmitted and received through a network node, where the network node may be, for example a MBMS-GW, or BMSC 210-a as stated.
  • base station 105-b may transmit to UE 115-c, and UE 115-c may receive from base station 105-b, MBMS content using the radio interface previously configured based on the identified supported capability of UE 115-c.
  • FIG. 4 illustrates an example of a process flow 400 in a wireless communications system that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • Process flow 400 includes UE 115-d and base station 105-c, which may be respective examples of a UE 115 and a base station 105 as described with reference to FIGs. 1 and 2.
  • Process flow 400 further includes service provider 205-b and BMSC 210-b, which may be respective examples of a service provider 205 and a BMSC 210 as described with reference to FIG. 2.
  • Process flow 400 may be an example of identifying and adjusting a coverage enhancement level for a UE.
  • service provider 205-b may determine a coverage enhancement level (i.e., an expected coverage level) expected to provide the desired coverage enhancement to one or more connected UEs, including, for example, UE 115-d.
  • a coverage enhancement level i.e., an expected coverage level
  • service provider 205-b may transmit to BMSC 210-b, and BMSC 210-b may receive from service provider 205-b, an indication specifying the coverage enhancement level determined at 405.
  • BMSC 210-b may receive from service provider 205-b, an indication specifying the coverage enhancement level determined at 405.
  • Different UEs 115 in a deployment of multiple UEs 115 may use different levels of coverage enhancement. For example, a software update for a UE 115 that may be subject to higher path loss (e.g., a UE 115 for a metering service in a basement) may use a relatively larger coverage enhancement, whereas a software update for a UE 115 that may be subject to less path loss (e.g., for audio streaming services to a UE 115 that is a smartwatch) may use a relatively small coverage enhancement.
  • Service provider 205-b may accordingly indicate to BMSC 210 an expected coverage enhancement for the services in, for example, the QoS requirements.
  • service provider 205-b may transmit a signal with a level of coverage enhancement selected from the set ⁇ c 0 , c , c 2 , c 3 ⁇ , where c 0 may represent no coverage enhancement, c x may represent a small coverage enhancement, c 2 may represent a medium coverage enhancement, and c 3 may represent a large coverage enhancement, each representing, for example, a dB value.
  • BMSC 210-b may transmit to base station 105-c, and base station 105-c may receive from BMSC 210-b, an indication specifying the determined coverage enhancement level. Additionally alternatively, the indication specifying the determined coverage enhancement level may be transmitted and received through a network node, where the network node may be, for example a MBMS-GW, or BMSC 210-b as stated.
  • base station 105-c may identify a coverage enhancement level.
  • the identified coverage enhancement level may be identified based on the coverage enhancement level determined by service provider 205-b at 405.
  • base station 105-c may transmit to UE 115-d, and UE 115-d may receive from base station 105-c, an indication of a targeted UE capability including the determined coverage enhancement level.
  • base station 105-c may configure a radio interface based on the received indication of the expected coverage level.
  • An indication of the capability of UE 115-d may include the indication of the expected coverage level.
  • service provider 205-b may transmit to BMSC 210-b, and BMSC 210-b may receive from service provider 205-b, broadcast or multicast content (such as MBMS content).
  • BMSC 210-b may transmit to base station 105-c, and base station 105-c may receive from BMSC 210-b, MBMS content. Additionally alternatively, the MBMS content may be transmitted and received through a network node, where the network node may be, for example a MBMS-GW, or BMSC 210-b as stated.
  • base station 105-c may transmit to UE 115-d, and UE 115-d may receive from base station 105-c, MBMS content using the radio interface previously configured based on the identified coverage enhancement level.
  • UE 115-d may transmit to base station 105-c, and base station 105-c may receive from UE 115-d, a report indicating whether UE 115-d successfully received the transmitted MBMS content.
  • Base station 105-c may receive a plurality of such reports from multiple UEs.
  • base station 105-c may transmit to BMSC 210-b, and BMSC 210-b may receive from base station 105-c, a report indicating whether UE 115-d successfully received the transmitted MBMS content. Additionally alternatively, the report indicating whether the UEs successfully received the transmitted MBMS content may be transmitted and received through a network node, where the network node may be, for example a MBMS-GW, or BMSC 210-b as stated. BMSC 210-b may receive one or more of such reports from multiple UEs, from which BMSC 210-b may determine a proportion of the total amount of UEs that successfully received the transmitted MBMS content.
  • BMSC 210-b may determine an updated coverage enhancement level based on the received one or more reports indicating whether UEs 115 (including, e.g., UE 115-d) successfully received the transmitted MBMS content.
  • BMSC 210-b may have set a target for a level of successful reception and adjust the level of coverage enhancement to reach the set target based on received responses from UEs 115. For example, BMSC 210-b may set a target of 99% reception of service. After announcing the service, each UE 115 in communication with BMSC 210-b may report to BMSC 210-b whether the UE 115 received the service.
  • BMSC 210-b may determine an updated coverage enhancement level to enable the respective UEs 115 to successfully receive the MBMS content at the desired rate. If BMSC 210 determines that the target level of successful reception was not met, BMSC 210 may then increase its coverage enhancement level to attempt to reach its target level of successful reception.
  • BMSC 210 may modify other radio access parameters based on the received one or more reports indicating whether UEs 115 (including, e.g., UE 115-d) successfully received the transmitted MBMS content.
  • BMSC 210-b may accordingly determine other parameters based on the capabilities of the responding UEs 115. For example, in addition modifying the coverage enhancement level, BMSC 210 may modify a category for a UE 115, a maximum bandwidth, or a maximum TB size.
  • BMSC 210-b may transmit to base station 105-c, and base station 105-c may receive from BMSC 210-b, an updated indication specifying the updated coverage enhancement level determined at 460. Additionally or alternatively, the updated indication specifying the updated coverage enhancement level may be transmitted and received through a network node, where the network node may be, for example a MBMS-GW, or BMSC 210- b as stated. Further, as discussed with reference to 460, BMSC 210-b may further transmit an updated indication of parameters including, for example, a category for a UE 115, a maximum bandwidth, or a maximum TB size.
  • base station 105-c may modify the radio interface based on the received updated indication of the updated coverage enhancement level.
  • Base station 105-c may further modify the radio interface based on updated parameters received in the updated indication at 465, including, for example, a category for a UE 115, a maximum bandwidth, or a maximum TB size.
  • Base station 105-c may then use the modified radio interface to transmit MBMS data to one or more UEs, including, for example, UE 115-d. This process may be iterated, thus providing for repeated adjustments of the coverage enhancement level, until the desired ratio of connected UEs have successfully received the MBMS data.
  • FIG. 5 shows a block diagram 500 of a wireless device 505 that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • Wireless device 505 may be an example of aspects of a base station 105 as described with reference to FIG. 1.
  • wireless device 505 may include receiver 510, base station capability and coverage manager 515, and transmitter 520.
  • wireless device 505 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).
  • Receiver 510 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to capability and coverage determination for multimedia broadcast multicast services, etc.). Information may be passed on to other components of the device.
  • the receiver 510 may be an example of aspects of the transceiver 835 as described with reference to FIG. 8.
  • Base station capability and coverage manager 515 may be an example of aspects of the base station capability and coverage manager 815 as described with reference to FIG. 8.
  • Base station capability and coverage manager 515 and/or at least some of its various sub- components may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions of the base station capability and coverage manager 515 and/or at least some of its various sub-components may be executed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • the base station capability and coverage manager 515 and/or at least some of its various sub-components may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical devices.
  • base station capability and coverage manager 515 and/or at least some of its various sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • base station capability and coverage manager 515 and/or at least some of its various sub-components may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.
  • Base station capability and coverage manager 515 may receive an indication of a targeted UE capability, the targeted UE capability specified by a service provider for the delivery of broadcast or multicast content and associated with a radio interface between the base station 105 and a UE 115, configure the radio interface based on the received indication of the targeted UE capability, and transmit the broadcast or multicast content to the UE 115 using the configured radio interface.
  • the indication of the targeted UE capability may include a QCI.
  • base station capability and coverage manager 515 may identify a mapping between the QCI and a maximum bandwidth, or a maximum transport block size, or a combination thereof, and configure the radio interface based on the identified mapping.
  • Base station capability and coverage manager 515 may also determine a set of radio access parameters to be used to deliver broadcast or unicast content, transmit the set of radio access parameters to a network node, receive messages from at least one UE 115, the messages indicating successful reception of the broadcast or unicast content at the at least one UE 115, and modify the set of radio access parameters based on the received messages.
  • Transmitter 520 may transmit signals generated by other components of the device.
  • the transmitter 520 may be collocated with a receiver 510 in a transceiver module.
  • the transmitter 520 may be an example of aspects of the transceiver 835 as described with reference to FIG. 8.
  • the transmitter 520 may include a single antenna, or it may include a set of antennas.
  • FIG. 6 shows a block diagram 600 of a wireless device 605 that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • Wireless device 605 may be an example of aspects of a wireless device 505 or a base station 105 as described with reference to FIGs. 1 and 5.
  • wireless device 605 may include receiver 610, base station capability and coverage manager 615, and transmitter 620.
  • wireless device 605 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).
  • Receiver 610 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to capability and coverage determination for multimedia broadcast multicast services, etc.). Information may be passed on to other components of the device.
  • the receiver 610 may be an example of aspects of the transceiver 835 as described with reference to FIG. 8.
  • Base station capability and coverage manager 615 may be an example of aspects of the base station capability and coverage manager 815 as described with reference to FIG. 8.
  • Base station capability and coverage manager 615 may also include targeted UE capability manager 625, radio interface manager 630, broadcast/multicast content component 635, radio access parameter manager 640, messaging component 645, and radio access parameter modifier 650.
  • Targeted UE capability manager 625 may receive an indication of a targeted UE capability, the targeted UE capability specified by a service provider for the delivery of broadcast or multicast content and associated with a radio interface between the base station 105 and a UE 115 and receive an updated indication of a targeted UE capability from the network node, the radio interface modified based on the updated targeted UE capability.
  • the indication of the targeted UE capability may include a QCI.
  • the indication of the targeted UE capability may be received from a service provider.
  • Radio interface manager 630 may configure the radio interface based on the received indication of the targeted UE capability and configure the radio interface based on the received indication of the expected coverage level, the received indication of the targeted UE capability including the indication of the expected coverage level.
  • configuring the radio interface based on the received indication of the targeted UE capability includes: determining a maximum bandwidth, or a maximum transport block size, or a combination thereof to be used to transmit the broadcast or multicast content.
  • Broadcast/multicast content component 635 may transmit the broadcast or multicast content to the UE 115 using the configured radio interface.
  • Radio access parameter manager 640 may determine a set of radio access parameters to be used to deliver broadcast or unicast content and transmit the set of radio access parameters to a network node.
  • the set of radio access parameters includes one or more of a coverage enhancement level, a UE category, a maximum bandwidth, or a maximum transport block size.
  • Messaging component 645 may receive messages from at least one UE 115, the messages indicating successful reception of the broadcast or unicast content at the at least one UE 115.
  • Radio access parameter modifier 650 may modify the set of radio access parameters based on the received messages.
  • Transmitter 620 may transmit signals generated by other components of the device.
  • the transmitter 620 may be collocated with a receiver 610 in a transceiver module.
  • the transmitter 620 may be an example of aspects of the transceiver 835 as described with reference to FIG. 8.
  • the transmitter 620 may include a single antenna, or it may include a set of antennas.
  • FIG. 7 shows a block diagram 700 of a base station capability and coverage manager 715 that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • the base station capability and coverage manager 715 may be an example of aspects of a base station capability and coverage manager 515, a base station capability and coverage manager 615, or a base station capability and coverage manager 815 as described with reference to FIGs. 5, 6, and 8.
  • the base station capability and coverage manager 715 may include targeted UE capability manager 720, radio interface manager 725, broadcast/multicast content component 730, radio access parameter manager 735, messaging component 740, radio access parameter modifier 745, UE category component 750, TMGI component 755, coverage level component 760, and UE report manager 765. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).
  • Targeted UE capability manager 720 may receive an indication of a targeted UE capability, the targeted UE capability specified by a service provider for the delivery of broadcast or multicast content and associated with a radio interface between the base station 105 and a UE 115 and receive an updated indication of a targeted UE capability from the network node, the radio interface modified based on the updated targeted UE capability.
  • the indication of the targeted UE capability may include a QCI.
  • the indication of the targeted UE capability may be received from a service provider.
  • Radio interface manager 725 may configure the radio interface based on the received indication of the targeted UE capability and configure the radio interface based on the received indication of the expected coverage level, the received indication of the targeted UE capability including the indication of the expected coverage level.
  • configuring the radio interface based on the received indication of the targeted UE capability includes determining a maximum bandwidth, or a maximum transport block size, or a combination thereof to be used to transmit the broadcast or multicast content.
  • Broadcast/multicast content component 730 may transmit the broadcast or multicast content to the UE 115 using the configured radio interface.
  • Radio access parameter manager 735 may determine a set of radio access parameters to be used to deliver broadcast or unicast content and transmit the set of radio access parameters to a network node.
  • the set of radio access parameters includes one or more of a coverage enhancement level, a UE category, a maximum bandwidth, or a maximum transport block size.
  • Messaging component 740 may receive messages from at least one UE 115, the messages indicating successful reception of the broadcast or unicast content at the at least one UE 115.
  • Radio access parameter modifier 745 may modify the set of radio access parameters based on the received messages.
  • UE category component 750 may receive, from a network node, a category of the UE 115, the indication of the targeted UE capability including the category.
  • the network node includes a BMSC, or a MBMS-GW, or a combination thereof.
  • TMGI component 755 may receive, from a network node, one or more TMGIs, the one or more TMGIs including the indication of the targeted UE capability and determine a category of the UE based on the received TMGI, the targeted UE capability including the determined category.
  • Coverage level component 760 may receive, from a network node, an indication of an expected coverage level specified by the service provider.
  • UE report manager 765 may transmit UE reports to a network node.
  • FIG. 8 illustrates a block diagram of a system 800 including a device 805 that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • Device 805 may be an example of or include the components of wireless device 505, wireless device 605, or a base station 105 as described above, e.g., with reference to FIGs. 1, 5 and 6.
  • Device 805 may include
  • components for bi-directional voice and data communications including components for transmitting and receiving communications, including base station capability and coverage manager 815, processor 820, memory 825, software 830, transceiver 835, antenna 840, network communications manager 845, and base station communications manager 850.
  • Device 805 may communicate wirelessly with one or more UEs 115.
  • Processor 820 may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof).
  • processor 820 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into processor 820.
  • Processor 820 may be configured to execute computer- readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting capability and coverage determination for multimedia broadcast multicast services).
  • Memory 825 may include random access memory (RAM) and read only memory (ROM).
  • the memory 825 may store computer-readable, computer-executable software 830 including instructions that, when executed, cause the processor to perform various functions described herein.
  • the memory 825 may contain, among other things, a basic input/output system (BIOS) which may control basic hardware and/or software operation such as the interaction with peripheral components or devices.
  • BIOS basic input/output system
  • Software 830 may include code to implement aspects of the present disclosure, including code to support capability and coverage determination for multimedia broadcast multicast services.
  • Software 830 may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, the software 830 may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • Transceiver 835 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 835 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 835 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
  • the wireless device may include a single antenna 840. However, in some cases the device may have more than one antenna 840, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the communications manager 845 may manage communications with the core network (e.g., via one or more wired backhaul links). For example, the network communications manager 845 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • Base station communications manager 850 may manage communications with other base station 105, and may include a controller or scheduler for controlling
  • the base station communications manager 850 may coordinate scheduling for transmissions to UEs 115 for various interference mitigation techniques such as beamforming or joint transmission.
  • base station communications manager 850 may provide an X2 interface within a LTE or LTE-A wireless communication network technology to provide communication between base stations 105.
  • FIG. 9 shows a block diagram 900 of a wireless device 905 that supports that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • Wireless device 905 may be an example of aspects of a UE 115 as described with reference to FIG. 1.
  • wireless device 905 may include receiver 910, UE capability and coverage manager 915, and transmitter 920.
  • wireless device 905 may also include a processor. Each of these components may be in
  • Receiver 910 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to capability and coverage determination for multimedia broadcast multicast services, etc.). Information may be passed on to other components of the device.
  • the receiver 910 may be an example of aspects of the transceiver 1235 as described with reference to FIG. 12.
  • UE capability and coverage manager 915 may be an example of aspects of the UE capability and coverage manager 1215 as described with reference to FIG. 12.
  • UE capability and coverage manager 915 and/or at least some of its various sub-components may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions of the UE capability and coverage manager 915 and/or at least some of its various sub-components may be executed by a general-purpose processor, a DSP, an ASIC, an FPGA or other
  • the UE capability and coverage manager 915 and/or at least some of its various sub -components may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical devices.
  • UE capability and coverage manager 915 and/or at least some of its various sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • UE capability and coverage manager 915 and/or at least some of its various sub-components may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.
  • UE capability and coverage manager 915 may receive an indication of a targeted UE capability for the delivery of broadcast or multicast content and associated with a radio interface between the UE 115 and a base station 105, identify a supported capability of the UE 115, and receive broadcast or multicast content using the radio interface based on the identified supported capability of the UE 115 and on the targeted UE capability.
  • the indication of the targeted UE capability may include a QCI.
  • the indication of the targeted UE capability may be received from a service provider.
  • Transmitter 920 may transmit signals generated by other components of the device.
  • the transmitter 920 may be collocated with a receiver 910 in a transceiver module.
  • the transmitter 920 may be an example of aspects of the transceiver 1235 as described with reference to FIG. 12.
  • the transmitter 920 may include a single antenna, or it may include a set of antennas.
  • FIG. 10 shows a block diagram 1000 of a wireless device 1005 that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • Wireless device 1005 may be an example of aspects of a wireless device 905 or a UE 115 as described with reference to FIGs. 1 and 9.
  • wireless device 1005 may include receiver 1010, UE capability and coverage manager 1015, and transmitter 1020.
  • wireless device 1005 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).
  • Receiver 1010 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to capability and coverage determination for multimedia broadcast multicast services, etc.). Information may be passed on to other components of the device.
  • the receiver 1010 may be an example of aspects of the transceiver 1235 as described with reference to FIG. 12.
  • UE capability and coverage manager 1015 may be an example of aspects of the UE capability and coverage manager 1215 as described with reference to FIG. 12. UE capability and coverage manager 1015 may also include UE capability manager 1025, supported capability component 1030, and UE broadcast/multicast content component 1035.
  • UE capability manager 1025 may receive an indication of a targeted UE capability for the delivery of broadcast or multicast content and associated with a radio interface between the UE 115 and a base station 105.
  • the indication of the targeted UE capability is received from a service provider.
  • the targeted UE capability is a UE category or a UE coverage enhancement level.
  • receiving the indication of the targeted UE capability includes: receiving the indication of the targeted UE capability in one or more of a USD, a SC-MCCH, or a SIB.
  • receiving the indication of the targeted UE capability includes: receiving the indication of the targeted UE capability in a transmission formatted based on a minimum supported capability of the UE 115.
  • the targeted UE capability includes one or more of a maximum supported capability of the UE 115 targeted by a service provider or an actual supported capability of the UE 115 targeted by the service provider.
  • Supported capability component 1030 may identify a supported capability of the UE 115 and determine if the supported capability is compatible with the targeted UE capability.
  • UE broadcast/multicast content component 1035 may receive broadcast or multicast content using the radio interface based on the identified supported capability of the UE 115 and on the targeted UE capability.
  • Transmitter 1020 may transmit signals generated by other components of the device.
  • the transmitter 1020 may be collocated with a receiver 1010 in a transceiver module.
  • the transmitter 1020 may be an example of aspects of the transceiver 1235 as described with reference to FIG. 12.
  • the transmitter 1020 may include a single antenna, or it may include a set of antennas.
  • FIG. 11 shows a block diagram 1100 of a UE capability and coverage manager 1115 that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • the UE capability and coverage manager 1 115 may be an example of aspects of a UE capability and coverage manager 1215 as described with reference to FIGs. 9, 10, and 12.
  • the UE capability and coverage manager 1115 may include UE capability manager 1120, supported capability component 1125, UE broadcast/multicast content component 1130, broadcast/multicast monitoring component 1135, content request component 1140, and reporting component 1 145. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).
  • UE capability manager 1120 may receive an indication of a targeted UE capability for the delivery of broadcast or multicast content and associated with a radio interface between the UE 115 and a base station 105.
  • the indication of the targeted UE capability is received from a service provider.
  • the targeted UE capability is a UE category or a UE coverage enhancement level.
  • receiving the indication of the targeted UE capability includes: receiving the indication of the targeted UE capability in one or more of a USD, a SC-MCCH, or a SIB.
  • receiving the indication of the targeted UE capability includes: receiving the indication of the targeted UE capability in a transmission formatted based on a minimum supported capability of the UE 115.
  • the targeted UE capability includes one or more of a maximum supported capability of the UE targeted by a service provider or an actual supported capability of the UE 115 targeted by the service provider.
  • Supported capability component 1125 may identify a supported capability of the UE 115 and determine if the supported capability is compatible with the targeted UE capability.
  • UE broadcast/multicast content component 1130 may receive broadcast or multicast content using the radio interface based on the identified supported capability of the UE 115 and on the targeted UE capability.
  • Broadcast/multicast monitoring component 1135 may determine to monitor for the broadcast or multicast content based on determining that the supported capability is compatible with the targeted UE capability and monitor for a DCI format based on the SC-MCCH.
  • Content request component 1140 may transmit, by the UE 115, a request for content to a content provider, the request for content including a category of the UE 115, where the received indication of the targeted UE capability is based on the category of the UE 115.
  • Reporting component 1145 may transmit a report indicating successful receipt of the broadcast or multicast content.
  • FIG. 12 illustrates a block diagram of a system 1200 including a device 1205 that supports capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • Device 1205 may be an example of or include the components of UE 115 as described above, e.g., with reference to FIG. 1.
  • Device 1205 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including UE capability and coverage manager 1215, processor 1220, memory 1225, software 1230, transceiver 1235, antenna 1240, and I/O controller 1245. These components may be in electronic
  • Device 1205 may communicate wirelessly with one or more base stations 105.
  • Processor 1220 may include an intelligent hardware device, (e.g., a general- purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof).
  • processor 1220 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into processor 1220.
  • Processor 1220 may be configured to execute computer- readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting capability and coverage determination for multimedia broadcast multicast services).
  • Memory 1225 may include RAM and ROM.
  • the memory 1225 may store computer-readable, computer-executable software 1230 including instructions that, when executed, cause the processor to perform various functions described herein.
  • the memory 1225 may contain, among other things, a BIOS which may control basic hardware and/or software operation such as the interaction with peripheral components or devices.
  • Software 1230 may include code to implement aspects of the present disclosure, including code to support capability and coverage determination for multimedia broadcast multicast services.
  • Software 1230 may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, the software 1230 may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • Transceiver 1235 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 1235 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1235 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
  • the wireless device may include a single antenna 1240. However, in some cases the device may have more than one antenna 1240, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • I/O controller 1245 may manage input and output signals for device 1205. I/O controller 1245 may also manage peripherals not integrated into device 1205. In some cases, I/O controller 1245 may represent a physical connection or port to an external peripheral. In some cases, I/O controller 1245 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In other cases, I/O controller 1245 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, I/O controller 1245 may be implemented as part of a processor. In some cases, a user may interact with device 1205 via I/O controller 1245 or via hardware components controlled by I/O controller 1245.
  • I/O controller 1245 may be implemented as part of a processor. In some cases, a user may interact with device 1205 via I/O controller 1245 or via hardware components controlled by I/O controller 12
  • FIG. 13 shows a flowchart illustrating a method 1300 for capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • the operations of method 1300 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 1300 may be performed by a base station capability and coverage manager as described with reference to FIGs. 5 through 8.
  • a base station 105 may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the base station 105 may perform aspects of the functions described below using special-purpose hardware.
  • the base station 105 may receive an indication of a targeted UE capability, the targeted UE capability specified by a service provider for the delivery of broadcast or multicast content and associated with a radio interface between the base station 105 and a UE 115.
  • the operations of block 1305 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1305 may be performed by a targeted UE capability manager as described with reference to FIGs. 5 through 8.
  • the base station 105 may configure the radio interface based at least in part on the received indication of the targeted UE capability.
  • the operations of block 1310 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1310 may be performed by a radio interface manager as described with reference to FIGs. 5 through 8.
  • the base station 105 may transmit the broadcast or multicast content to the UE 115 using the configured radio interface.
  • the operations of block 1315 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1315 may be performed by a
  • FIG. 14 shows a flowchart illustrating a method 1400 for capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • the operations of method 1400 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 1400 may be performed by a base station capability and coverage manager as described with reference to FIGs. 5 through 8.
  • a base station 105 may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the base station 105 may perform aspects of the functions described below using special-purpose hardware.
  • the base station 105 may receive, from a network node, a category of the UE 115.
  • the operations of block 1405 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1405 may be performed by a UE category component as described with reference to FIGs. 5 through 8.
  • the base station 105 may receive an indication of a targeted UE capability, where the indication of the targeted UE capability may include the category, and the targeted UE capability specified by a service provider for the delivery of broadcast or multicast content and associated with a radio interface between the base station 105 and a UE 115.
  • the indication of the targeted UE capability may include a QCI.
  • the base station 105 may identify a aping between the QCI and a maximum bandwidth, or a maximum transport block size, or a combination thereof, and configure the radio interface based on the identified mapping.
  • the operations of block 1410 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1410 may be performed by a targeted UE capability manager as described with reference to FIGs. 5 through 8.
  • the base station 105 may configure the radio interface based at least in part on the received indication of the targeted UE capability.
  • the operations of block 1415 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1415 may be performed by a radio interface manager as described with reference to FIGs. 5 through 8.
  • the base station 105 may transmit the broadcast or multicast content to the UE 115 using the configured radio interface.
  • the operations of block 1420 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1420 may be performed by a
  • FIG. 15 shows a flowchart illustrating a method 1500 for capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • the operations of method 1500 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 1500 may be performed by a base station capability and coverage manager as described with reference to FIGs. 5 through 8.
  • a base station 105 may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the base station 105 may perform aspects of the functions described below using special-purpose hardware.
  • the base station 105 may receive a QCI, the QCI including an indication of a targeted UE capability.
  • the operations of block 1505 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1505 may be performed by a base station capability and coverage manager as described with reference to FIGs. 5 through 8.
  • the base station 105 may identify a mapping between the QCI and a maximum bandwidth, or a maximum transport block size, or a combination thereof. In some cases, the base station 105 may derive the maximum bandwidth and the maximum transport block size based on the mapping with the QCI.
  • the operations of block 1510 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1510 may be performed by a base station capability and coverage manager as described with reference to FIGs. 5 through 8.
  • the base station 105 may configure the radio interface based on the identified mapping.
  • the operations of block 1515 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1515 may be performed by a radio interface manager as described with reference to FIGs. 5 through 8.
  • the base station 105 may transmit broadcast or multicast content to a UE 115 using the configured radio interface.
  • the operations of block 1520 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1520 may be performed by a
  • FIG. 16 shows a flowchart illustrating a method 1600 for capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • the operations of method 1600 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 1600 may be performed by a UE capability and coverage manager as described with reference to FIGs. 9 through 12.
  • a UE 115 may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or
  • the UE 115 may perform aspects of the functions described below using special-purpose hardware.
  • the UE 115 may receive an indication of a targeted UE capability for the delivery of broadcast or multicast content and associated with a radio interface between the UE 115 and a base station 105.
  • the indication of the targeted UE capability may include a QCI.
  • the operations of block 1605 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1605 may be performed by a UE capability manager as described with reference to FIGs. 9 through 12.
  • the UE 115 may identify a supported capability of the UE 115.
  • the operations of block 1610 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1610 may be performed by a supported capability component as described with reference to FIGs. 9 through 12.
  • the UE 115 may determine if the supported capability is compatible with the targeted UE capability.
  • the operations of block 1615 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1615 may be performed by a supported capability component as described with reference to FIGs. 9 through 12.
  • the UE 115 may determine to monitor for the broadcast or multicast content based on determining that the supported capability is compatible with the targeted UE capability.
  • the operations of block 1620 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1620 may be performed by a broadcast/multicast monitoring component as described with reference to FIGs. 9 through 12.
  • the UE 115 may receive broadcast or multicast content using the radio interface based at least in part on the identified supported capability of the UE 115 and on the targeted UE capability.
  • the operations of block 1625 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1625 may be performed by a UE broadcast/multicast content component as described with reference to FIGs. 9 through 12.
  • FIG. 17 shows a flowchart illustrating a method 1700 for capability and coverage determination for multimedia broadcast multicast services in accordance with aspects of the present disclosure.
  • the operations of method 1700 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 1700 may be performed by a base station capability and coverage manager as described with reference to FIGs. 5 through 8.
  • a base station 105 may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the base station 105 may perform aspects of the functions described below using special-purpose hardware.
  • the base station 105 may transmit the set of radio access parameters to a network node.
  • the operations of block 1710 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1710 may be performed by a radio access parameter manager as described with reference to FIGs. 5 through 8.
  • the base station 105 may receive messages from at least one UE 115, the messages indicating successful reception of the broadcast or unicast content at the at least one UE 115.
  • the operations of block 1715 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1715 may be performed by a messaging component as described with reference to FIGs. 5 through 8.
  • the base station 105 may modify the set of radio access parameters based at least in part on the received messages.
  • the operations of block 1720 may be performed according to the methods as described with reference to FIGs. 1 through 4. In certain examples, aspects of the operations of block 1720 may be performed by a radio access parameter modifier as described with reference to FIGs. 5 through 8.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • a CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc.
  • CDMA2000 covers IS-2000, IS-95, and IS-856 standards.
  • IS- 2000 Releases may be commonly referred to as CDMA2000 IX, IX, etc.
  • IS-856 (TIA-856) is commonly referred to as CDMA2000 lxEV-DO, High Rate Packet Data (HRPD), etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • WCDMA Wideband CDMA
  • a TDMA system may implement a radio technology such as Global System for Mobile
  • An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc.
  • UMB Ultra Mobile Broadband
  • E-UTRA Evolved UTRA
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • UTRA and E-UTRA are part of Universal Mobile Telecommunications system (UMTS).
  • 3 GPP LTE and LTE-A are releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A, R, and GSM are described in documents from the organization named "3rd Generation Partnership Project" (3GPP).
  • CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • 3GPP2 3rd Generation Partnership Project 2
  • the techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies. While aspects an LTE or an NR system may be described for purposes of example, and LTE or R terminology may be used in much of the description, the techniques described herein are applicable beyond LTE or NR applications.
  • Base stations may include or may be referred to by those skilled in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, eNodeB (eNB), next generation NodeB (gNB), Home NodeB, a Home eNodeB, or some other suitable terminology.
  • the geographic coverage area for a base station may be divided into sectors making up only a portion of the coverage area.
  • the wireless communications system or systems described herein may include base stations of different types (e.g., macro or small cell base stations).
  • the UEs described herein may be able to communicate with various types of base stations and network equipment including macro eNBs, small cell eNBs, gNBs, relay base stations, and the like. There may be overlapping geographic coverage areas for different technologies.
  • the wireless communications system or systems described herein may support synchronous or asynchronous operation.
  • the base stations may have similar frame timing, and transmissions from different base stations may be
  • the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time.
  • the techniques described herein may be used for either synchronous or asynchronous operations.
  • each carrier may be a signal made up of multiple sub- carriers (e.g., waveform signals of different frequencies).
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope and spirit of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • the term "and/or,” when used in a list of two or more items, means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed.
  • the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.
  • "at least one of: A, B, or C” is intended to cover A, B, C, A-B, A- C, B-C, and A-B-C, as well as any combination with multiples of the same element (e.g., A- A, A-A-A, A-A-B, A-A-C, A-B-B, A-C-C, B-B, B-B-B, B-B-C, C-C, and C-C-C or any other ordering of A, B, and C).
  • the phrase "based on” shall not be construed as a reference to a closed set of conditions.
  • an exemplary step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure.
  • the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Multimedia (AREA)
PCT/US2017/057967 2017-02-06 2017-10-24 Capability and coverage determination for multimedia broadcast multicast service WO2018144081A1 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
CN201780085547.8A CN110249587B (zh) 2017-02-06 2017-10-24 针对多媒体广播多播服务的能力和覆盖确定
US16/476,160 US11019602B2 (en) 2017-02-06 2017-10-24 Capability and coverage determination for multimedia broadcast multicast service
KR1020197022556A KR20190110557A (ko) 2017-02-06 2017-10-24 멀티미디어 브로드캐스트 멀티캐스트 서비스를 위한 성능 및 커버리지 결정
BR112019015810-3A BR112019015810A2 (pt) 2017-02-06 2017-10-24 Determinação de capacidade e cobertura para serviço de difusão e multidifusão de multimídia
KR1020227017461A KR102670603B1 (ko) 2017-02-06 2017-10-24 멀티미디어 브로드캐스트 멀티캐스트 서비스를 위한 성능 및 커버리지 결정
EP17795139.9A EP3577856B1 (en) 2017-02-06 2017-10-24 Capability and coverage determination for multimedia broadcast multicast service
US17/326,235 US11690082B2 (en) 2017-02-06 2021-05-20 Capability and coverage determination for multimedia broadcast multicast service

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN201741004261 2017-02-06
IN201741004261 2017-02-06

Related Child Applications (3)

Application Number Title Priority Date Filing Date
US16/476,160 A-371-Of-International US11019602B2 (en) 2017-02-06 2017-10-24 Capability and coverage determination for multimedia broadcast multicast service
US16476160 A-371-Of-International 2017-10-24
US17/326,235 Continuation US11690082B2 (en) 2017-02-06 2021-05-20 Capability and coverage determination for multimedia broadcast multicast service

Publications (1)

Publication Number Publication Date
WO2018144081A1 true WO2018144081A1 (en) 2018-08-09

Family

ID=60269952

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/057967 WO2018144081A1 (en) 2017-02-06 2017-10-24 Capability and coverage determination for multimedia broadcast multicast service

Country Status (6)

Country Link
US (2) US11019602B2 (zh)
EP (1) EP3577856B1 (zh)
KR (2) KR102670603B1 (zh)
CN (2) CN110249587B (zh)
BR (1) BR112019015810A2 (zh)
WO (1) WO2018144081A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111586594A (zh) * 2019-02-15 2020-08-25 大众汽车有限公司 系统、车辆、用于移动通信系统中的用户装备和基站的装置、方法和计算机程序
CN111836311A (zh) * 2019-08-09 2020-10-27 维沃移动通信有限公司 能力协商方法、终端及网络设备
WO2020243255A1 (en) * 2019-05-31 2020-12-03 Qualcomm Incorporated Broadcast relay method in new radio
WO2021046798A1 (zh) * 2019-09-12 2021-03-18 北京小米移动软件有限公司 Ue能力信息的传输方法、装置和存储介质
CN112567815A (zh) * 2019-06-18 2021-03-26 Oppo广东移动通信有限公司 一种终端设备的能力确定方法、设备及存储介质
US11418926B2 (en) 2018-08-14 2022-08-16 Nokia Technologies Oy Method of multicast data delivery in 5G supporting cloud architecture

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11019602B2 (en) * 2017-02-06 2021-05-25 Qualcomm Incorporated Capability and coverage determination for multimedia broadcast multicast service
EP3677087B1 (en) * 2017-08-31 2023-03-15 Nokia Technologies Oy Method for operating a network entity for a cellular radio communications network and network entity for a cellular radio communications network
JP7237983B2 (ja) * 2018-04-05 2023-03-13 ノキア テクノロジーズ オサケユイチア 早期データ伝送のためのプロトコル・データ・ユニットの作成
US11671822B2 (en) * 2018-04-10 2023-06-06 Apple Inc. UE capabilities provisioning and retrieval in cellular networks
WO2020140290A1 (zh) * 2019-01-04 2020-07-09 株式会社Ntt都科摩 无线通信方法及设备
CN111601303B (zh) * 2019-04-29 2022-09-23 维沃移动通信有限公司 一种协议数据单元会话处理的方法、装置和电子设备
BR112021021688A2 (pt) * 2019-05-01 2021-12-21 Nokia Technologies Oy Sinalização de capacidades de equipamento de usuário otimizada incluindo recuperação de falha de banco de dados
GB2591499A (en) * 2020-01-30 2021-08-04 Samsung Electronics Co Ltd Informing changes in coverage enhancement usage
CN114079869A (zh) * 2020-08-13 2022-02-22 维沃移动通信有限公司 上报能力的方法、终端设备和网络设备
WO2022047753A1 (zh) * 2020-09-04 2022-03-10 北京小米移动软件有限公司 传输块大小配置方法、装置及存储介质
CN116193376B (zh) * 2021-10-15 2023-12-29 华为技术有限公司 一种通信方法及装置

Family Cites Families (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI20021755A0 (fi) * 2002-10-02 2002-10-02 Nokia Corp Menetelmä ja järjestely yleislähetyksen vastaanottoedellytysten ilmaisemiseksi
US8644205B2 (en) * 2004-07-27 2014-02-04 Telecom Italia S.P.A. Transmission of multimedia contents to a plurality of mobile users
US20090185522A1 (en) * 2005-01-07 2009-07-23 Nortel Networks Limited Systems and methods for distributing content in wireless networks
KR20070073076A (ko) * 2006-01-03 2007-07-10 엘지전자 주식회사 무선 통신 시스템의 자원 제어 방법
US9438436B2 (en) 2006-08-14 2016-09-06 Alcatel Lucent Broadcast anchor availability indication
CN101193342B (zh) 2006-11-29 2011-04-06 华为技术有限公司 在Iub接口传输MBMS业务数据的方法和系统
EP1978762A1 (en) * 2007-04-05 2008-10-08 Matsushita Electric Industrial Co., Ltd. Service content synchronization of multicast data for mobile nodes moving between networks with different radio access technologies
EP2281402B1 (en) 2008-06-06 2012-03-07 Telefonaktiebolaget LM Ericsson (publ) Methods and apparatuses relating to multimedia broadcast multicast services
TW201114303A (en) * 2009-08-14 2011-04-16 Interdigital Patent Holdings MCCH notification scheduling and contents
CN107370979B (zh) * 2009-11-09 2020-11-10 三星电子株式会社 支持在切换期间的单一无线视频呼叫连续性的方法及系统
US9491735B2 (en) * 2010-12-19 2016-11-08 Motorola Solutions, Inc. System and method in a communication network of dynamically assigning a multimedia broadcast/multicast service bearer to a multicast channel
US9173192B2 (en) 2011-03-17 2015-10-27 Qualcomm Incorporated Target cell selection for multimedia broadcast multicast service continuity
US9072005B2 (en) 2011-04-20 2015-06-30 Qualcomm Incorporated Quality of service control in a multicast transmission
US9143901B2 (en) * 2011-05-27 2015-09-22 Qualcomm Incorporated Group ID and QOS group identification for stream multiplexing in multicast and broadcast systems
CN102932744B (zh) 2011-08-12 2014-07-09 华为技术有限公司 一种重选或切换到广播组播小区的方法、基站和系统
CN104025475B (zh) * 2011-10-03 2018-04-13 英特尔公司 装置到装置(d2d)通信机制
WO2014053073A1 (en) * 2012-10-03 2014-04-10 Qualcomm Incorporated Broadcast/multicast used for m2m/mtc
US9820259B2 (en) * 2012-05-04 2017-11-14 Qualcomm Incorporated Smooth transition between multimedia broadcast multicast service (MBMS) and unicast service by demand
WO2013170425A1 (zh) * 2012-05-14 2013-11-21 华为技术有限公司 上报业务指示消息的方法、装置及系统
US9197358B2 (en) * 2012-05-18 2015-11-24 Dali Systems Co., Ltd. Method and system for soft frequency reuse in a distributed antenna system
WO2014032291A1 (en) * 2012-08-31 2014-03-06 Telefonaktiebolaget L M Ericsson(Publ) Methods and devices for switching between peer-to-peer and multimedia broadcast multicast service
TW201807961A (zh) * 2012-09-27 2018-03-01 內數位專利控股公司 在噓擬網路中端對端架構、api框架、發現及存取
US20140098745A1 (en) * 2012-10-04 2014-04-10 Qualcomm Incorporated Method and system for compressing data packets in lte evolved multicast broadcast multimedia service
US9479321B2 (en) * 2012-11-02 2016-10-25 Telefonaktiebolaget L M Ericsson (Publ) Flexible spectrum support in cellular wireless communications
US9326270B2 (en) * 2013-01-17 2016-04-26 Industrial Technology Research Institute Data transmission method through point to multi-point transmission service
WO2014166071A1 (zh) * 2013-04-09 2014-10-16 华为技术有限公司 数据传输方法、装置及系统
US9674251B2 (en) * 2013-06-17 2017-06-06 Qualcomm Incorporated Mediating content delivery via one or more services
EP3017616B1 (en) * 2013-07-01 2018-12-05 NEC Corporation Method for providing multicast/broadcast service continuity for mobile terminals
CN104471895B (zh) * 2013-07-02 2018-11-13 华为技术有限公司 一种支持流媒体进行组播的方法和相关装置及系统
US9307487B2 (en) * 2013-08-30 2016-04-05 Qualcomm Incorporated Methods and systems for improved utilization of a wireless medium
US9674674B2 (en) * 2013-10-23 2017-06-06 Qualcomm Incorporated Unicast and broadcast reception policy and enforcement
US9351149B2 (en) * 2013-10-24 2016-05-24 Qualcomm Incorporated Evolved multimedia broadcast multicast service network sharing and roaming support
CN103561389A (zh) * 2013-10-25 2014-02-05 电信科学技术研究院 一种mbms测量方法、系统及基站、用户设备
US20160323846A1 (en) * 2014-01-06 2016-11-03 Lg Electronics Inc. Method and apparatus for providing group communication service enabler (gcse) service in wireless communication system
US9503990B2 (en) * 2015-01-30 2016-11-22 Innovative Technology Lab Co., Ltd. Apparatus and method for performing uplink power control in wireless communication system supporting carrier aggregation
KR101853670B1 (ko) * 2015-03-01 2018-05-02 엘지전자 주식회사 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법
EP3295591B1 (en) * 2015-05-15 2021-12-15 Nokia Technologies Oy Quality of service driven receiver selective hybrid automatic repeat request for point-to-multipoint communication
US10123226B2 (en) * 2015-12-02 2018-11-06 At&T Intellectual Property I, L.P. Detection of active listeners and dynamic provisioning of cell sites for broadcast
EP4007414A1 (en) * 2016-01-07 2022-06-01 Huawei Technologies Co., Ltd. Data scheduling method, base station, and system
EP3443789B1 (en) * 2016-04-11 2020-10-28 Telefonaktiebolaget LM Ericsson (publ) Checking capacity for a multimedia session
JP6741969B2 (ja) * 2016-09-30 2020-08-19 京セラ株式会社 移動通信システム
US10498551B2 (en) * 2016-11-21 2019-12-03 Qualcomm Incorporated Data multicast or broadcast on control channel for narrowband communication
CN114900797A (zh) * 2016-12-30 2022-08-12 英特尔公司 用于无线电通信的方法和设备
US11019602B2 (en) * 2017-02-06 2021-05-25 Qualcomm Incorporated Capability and coverage determination for multimedia broadcast multicast service

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS INC: "MBMS Access Based on Required UE Radio Access Capability", 3GPP DRAFT; R2-030909 MBMS ACCESS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Paris, France; 20030513, 13 May 2003 (2003-05-13), XP050141564 *
SAMSUNG: "Solution for Key issue #6: Exposure of eMBMS service and transport capabilities to 3rd party", vol. SA WG2, no. Vienna, Austria; 20160711 - 20160715, 13 July 2016 (2016-07-13), XP051118361, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/SA2/Docs/> [retrieved on 20160713] *
SIEMENS: "Considerations on minimum UE capabilities for MBMS", 3GPP DRAFT; R2-040041, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Sophia Antipolis, France; 20040119, 19 January 2004 (2004-01-19), XP050125057 *

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11418926B2 (en) 2018-08-14 2022-08-16 Nokia Technologies Oy Method of multicast data delivery in 5G supporting cloud architecture
CN111586594A (zh) * 2019-02-15 2020-08-25 大众汽车有限公司 系统、车辆、用于移动通信系统中的用户装备和基站的装置、方法和计算机程序
US11290853B2 (en) 2019-02-15 2022-03-29 Volkswagen Aktiengesellschaft System, transportation vehicle, apparatuses, methods, and computer programs for user equipment and for a base station in a mobile communication system
CN111586594B (zh) * 2019-02-15 2022-05-27 大众汽车有限公司 系统、车辆、用于移动通信系统中的用户装备和基站的装置、方法和计算机可读存储介质
WO2020243255A1 (en) * 2019-05-31 2020-12-03 Qualcomm Incorporated Broadcast relay method in new radio
US11375364B2 (en) 2019-05-31 2022-06-28 Qualcomm Incorporated Broadcast relay method in new radio
US11991784B2 (en) 2019-05-31 2024-05-21 Qualcomm Incorporated Broadcast relay method in new radio
CN112567815A (zh) * 2019-06-18 2021-03-26 Oppo广东移动通信有限公司 一种终端设备的能力确定方法、设备及存储介质
CN112567815B (zh) * 2019-06-18 2023-09-15 Oppo广东移动通信有限公司 一种终端设备的能力确定方法、设备及存储介质
CN111836311A (zh) * 2019-08-09 2020-10-27 维沃移动通信有限公司 能力协商方法、终端及网络设备
CN111836311B (zh) * 2019-08-09 2024-03-19 维沃移动通信有限公司 能力协商方法、终端及网络设备
WO2021046798A1 (zh) * 2019-09-12 2021-03-18 北京小米移动软件有限公司 Ue能力信息的传输方法、装置和存储介质

Also Published As

Publication number Publication date
KR20220076531A (ko) 2022-06-08
CN114143888A (zh) 2022-03-04
US20190349892A1 (en) 2019-11-14
BR112019015810A2 (pt) 2020-03-31
US11019602B2 (en) 2021-05-25
EP3577856A1 (en) 2019-12-11
CN110249587A (zh) 2019-09-17
EP3577856B1 (en) 2023-07-26
KR102670603B1 (ko) 2024-05-30
US11690082B2 (en) 2023-06-27
US20210274469A1 (en) 2021-09-02
KR20190110557A (ko) 2019-09-30
CN110249587B (zh) 2022-01-04

Similar Documents

Publication Publication Date Title
US11690082B2 (en) Capability and coverage determination for multimedia broadcast multicast service
CN109983789B (zh) 用于窄带通信的控制信道上的数据多播或广播
CN112567679B (zh) 用于配置和触发探测参考信号的控制元素
EP3753285B1 (en) Network-assisted scheduling for packet duplication in vehicle-based sidelink communication
EP4023031A1 (en) Delivery of broadcast services using different broadcast/multicast radio bearer modes
CN110326346B (zh) 用于低等待时间无线通信的指示信道技术
EP4039017B1 (en) Physical resource and transmission parameter configuration without a radio resource control connection
US10972876B2 (en) Local broadcast for group calls
CN111295912A (zh) 定向波束环境中的功率控制
CN110832932A (zh) 分布式无线网络中的用户设备能力发现
CN110583086B (zh) 对共享信道的免准许准入控制
WO2022086736A1 (en) Multicast/broadcast service alert
EP3874801B1 (en) Channel quality reporting using random access messages
CN112771804A (zh) 用于低等待时间通信的快速激活和停用
WO2020154508A1 (en) Preconfigured uplink resource techniques in wireless communications
CN113615263B (zh) 使用公共标识符来监测唤醒信号
CN116762469A (zh) 用于由于中继用户设备移动性而导致的远程用户设备切换的技术
WO2021207322A1 (en) Indication of system information update via a downlink shared channel
WO2021055764A1 (en) Message configuration for two-step random access procedure
WO2022021134A1 (en) Multicast grants to user equipment of different capabilities using a single downlink control information
TW202231109A (zh) 快速scell啟用

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17795139

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20197022556

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019015810

Country of ref document: BR

WWE Wipo information: entry into national phase

Ref document number: 2017795139

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 112019015810

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190731