Multicast and Broadcast Configuration Signaling

Abstract

To allow transport blocks associated with multicast broadcast services to be received.SOLUTION: A wireless communication method performed by user equipment (UE) comprises steps of: receiving configuration parameters of a semi-persistent scheduling (SPS) configuration associated with one or more multicast broadcast services; and receiving, based on an SPS resource associated with the SPS configuration, one or more transport blocks associated with the one or more multicast broadcast services.SELECTED DRAWING: Figure 17

Description

[Technical Field]

[0001] The present disclosure relates to a wireless communication method. [Background technology]

[0002] Generally, computing devices and communication networks can be used to exchange information. In typical applications, computing devices can request / send data to other computing devices via a communication network. More specifically, computing devices can use wireless communication networks to exchange information or establish communication channels.

[0003] A wireless communication network may include various types of devices that include components for accessing the wireless communication network or that access the wireless communication network, and such devices may utilize the wireless communication network to facilitate interaction with other devices that have access to the wireless communication network or to facilitate interaction through the wireless communication network with devices that utilize other communication networks. Summary of the Invention [Means for solving the problem]

[0004] One embodiment of the present invention is a wireless communication method, including the steps of receiving, by a user equipment (UE), one or more messages including configuration parameters indicating that one or more multicast broadcast services are associated with at least one of a first control resource set (CORESET) and a first bandwidth part (BWP), and one or more first Radio Network Temporary Identifiers (RNTIs) associated with the one or more multicast broadcast services, receiving, by the UE, downlink control information associated with the one or more first RNTIs, and receiving, based on the downlink control information, one or more transport blocks associated with the one or more multicast broadcast services. [Brief explanation of the drawings]

[0005] [Figure 1] 1 illustrates an example of a mobile communication system in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 2] 2A-2B illustrate example radio protocol stacks for the user plane and control plane, respectively, in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 3] 3A-3C illustrate example mappings between logical channels and transmission channels for the downlink, uplink, and sidelink, respectively, in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 4] 4A-4C illustrate example mappings between transmission channels and physical channels for the downlink, uplink, and sidelink, respectively, in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 5] 5A-5D illustrate example radio protocol stacks for NR sidelink communications in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 6]1 illustrates exemplary physical signals for downlink, uplink, and sidelink in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 7] 1 illustrates examples of Radio Resource Control (RRC) states and transitions between different RRC states in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 8] 1 illustrates an example frame structure and physical resources in accordance with some aspects of one or more example embodiments of the present disclosure. [Figure 9] 1 illustrates exemplary component carrier configurations for different carrier aggregation scenarios in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 10] 1 illustrates exemplary bandwidth portion configurations and switching in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 11] 1 illustrates an exemplary four-stage collision-based and non-collision-based random access process in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 12] 1 illustrates an exemplary two-stage collision-based and non-collision-based random access process in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 13] 1 illustrates an example time-frequency structure of a synchronization signal / physical broadcast channel (PBCH) block (SSB) in accordance with some aspects of one or more example embodiments of the present disclosure. [Figure 14] 1 illustrates an exemplary SSB burst transmission in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 15] 1 illustrates exemplary components of a user terminal and a base station for transmission and / or reception in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 16] 1 illustrates an exemplary Multicast Broadcast Service (MBS) Interest Indication process in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 17]1 illustrates exemplary MBS control signaling and traffic channel transmissions in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 18] 1 illustrates an exemplary process for MBS delivery according to some aspects of one or more exemplary embodiments of the present disclosure. [Figure 19] 1 illustrates exemplary MBS control signaling and traffic channel transmissions in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 20] 1 illustrates an example process according to some aspects of one or more example embodiments of the present disclosure. [Figure 21] 1 illustrates an example process according to some aspects of one or more example embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0006] 1 illustrates an example of a mobile communication system 100 according to some aspects of one or more exemplary embodiments of the present disclosure. The mobile communication system 100 may be operated by a wireless communication system operator, such as a Mobile Network Operator (MNO), a private network operator, a Multiple System Operator (MSO), an Internet of Things (IoT) network operator, etc., and may provide services such as voice, data (e.g., wireless Internet access), messaging, automotive communication services such as vehicle-to-vehicle / vehicle-to-everything (V2X) communication services, safety services, mission-critical services, IoT, industrial IoT (IIOT), and other services in residential, commercial, or industrial environments.

[0007] The mobile communication system 100 may support various types of applications with different requirements in terms of latency, reliability, throughput, etc. Examples of supported applications include enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine Type Communication (mMTC). eMBB supports high peak data rates and stable connections with reasonable rates for cell edge users. URLLC can support applications with stringent latency and reliability requirements and moderate data rate requirements. An example mMTC application includes a network of thousands of IoT devices that are only sporadically active and transmit only small data payloads.

[0008] The mobile communication system 100 may include a Radio Access Network (RAN) portion and a core network portion. The example shown in FIG. 1 illustrates a Next Generation RAN (NG-RAN) 105 and a 5G Core Network (5GC) 110 as examples of the RAN and core network, respectively. Other examples of the RAN and core network may also be implemented without departing from the scope of this disclosure. Other examples of the RAN include the Evolved Universal Terrestrial Radio Access Examples of core networks include the Universal Terrestrial Radio Access Network (UTRAN), the Evolved Packet Core (EPC), and the UMTS Core Network (UCN). A RAT implements a Radio Access Technology (RAT) and is located between user equipments (UEs) 125 (e.g., UEs 125A-125E) and a core network. Such RATs include New Radio (NR), Long Term Evolution (LTE), also known as Evolved Universal Terrestrial Radio Access (EUTRA), and Universal Mobile Telecommunication System (UMTS). The RAT in the exemplary mobile communication system 100 may be NR. The core network is located between the RAN and one or more external networks (e.g., data networks) and is responsible for functions such as mobility management, authentication, session management, bearer setup, and applications of different Quality of Services (QoS). The functional layer between the UEs 125 and the RAN (e.g., NG-RAN 105) may be referred to as an Access Stratum (AS), and the functional layer between the UEs 125 and the core network (e.g., 5GC 110) may be referred to as a Non-Access Stratum (NAS).

[0009] The UEs 125 may include wireless transmit and receive components for communicating with one or more nodes in the RAN, one or more relay nodes, or one or more other UEs. Examples of UEs 125 include, but are not limited to, smartphones, tablets, laptops, computers, in-vehicle wireless transmit and / or receive units, V2X or vehicle-to-vehicle (V2V) devices, wireless sensors, IoT devices, IIOT devices, etc. Other names for UEs 125 may be used, such as mobile stations (MS), terminal equipment, terminal nodes, client devices, mobile devices, etc. Furthermore, the UEs 125 may also include components or subcomponents embedded in other devices, such as automobiles, that provide wireless communication capabilities with nodes in the RAN as described herein. Such other devices may have other functionality or multiple functionalities in addition to wireless communication.

[0010] The RAN may include nodes (e.g., base stations) for communicating with UEs. For example, the NG-RAN 105 of the mobile communication system 100 may include nodes for communicating with the UEs 125. The RAN nodes may be referred to by various names depending, for example, on the RAT used for the RAN. The RAN nodes may be referred to as Node-Bs (NBs) in a RAN using a UMTS RAT. The RAN nodes may be referred to as evolved Node Bs in a RAN using an LTE / EUTRA RAT. In the example mobile communication system 100 of FIG. 1, the nodes of the NG-RAN 105 may be referred to as Next Generation Node Bs (gNBs) 115 (e.g., gNB 115A, gNB 115B) or Next Generation Evolved Node Bs (ng-eNBs). The gNB 115 may be either a RAN node (RAN node) or a UE node (NG-eNB) 120 (e.g., ng-eNB 120A, ng-eNB 120B). The terms base station, RAN node, gNB, and ng-eNB may be used interchangeably herein. The gNB 115 may provide NR user plane and control plane protocol termination toward the UE 125. The ng-eNB 120 may provide E-UTRA user plane and control plane protocol termination toward the UE 125. The interface between the gNB 115 and the UE 125 or between the ng-eNB 120 and the UE 125 may be referred to as a Uu interface. The Uu interface may be established with a user plane protocol stack and a control plane protocol stack. For the Uu interface, the direction from the base station (e.g., gNB 115 or ng-eNB 120) to the UE 125 may be referred to as the downlink, and the direction from the UE 125 to the base station (e.g., gNB 115 or ng-eNB 120) may be referred to as the uplink.

[0011] The gNBs 115 and the ng-eNBs 120 may be interconnected by an Xn interface. The Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The transport network layer of the Xn-U interface may be built based on Internet Protocol (IP) transport and may support General Packet Radio Service (GPRS). The Radio Service Tunneling Protocol (GTP) can be used over User Datagram Protocol (UDP) / IP to carry user plane protocol data units (PDUs). Xn-U can provide unguaranteed delivery of user plane PDUs and support data forwarding and flow control. The transport network layer of the Xn-C interface can be built on the Stream Control Transport Protocol (SCTP) over IP. The application layer signaling protocol is XnAP (Xn The SCTP layer may be referred to as the QoS Application Protocol (SCTP). The SCTP layer may provide guaranteed delivery of application layer messages. At the transport IP layer, point-to-point transmission may be used to carry signaling PDUs. The Xn-C interface may support Xn interface management, UE mobility management including context transfer and RAN paging, and dual connectivity.

[0012] The gNBs 115 and ng-eNBs 120 may also be connected to the 5GC 110 via an NG interface, more specifically to the Access and Mobility Management Function (AMF) 130 (e.g., AFM 130A, AMF 130B) of the 5GC 110 via an NG-C interface, and to the User Plane Function (UPF) 135 (e.g., UPF 135A, UPF 135B) of the 5GC 110 via an NG-U interface. The transport network layer of the NG-U interface may be built based on IP transport, and the GTP protocol may be used on top of UDP / IP to carry user plane PDUs between the NG-RAN node (e.g., gNB 115 or ng-eNB 120) and the UPF 135. The NG-U may provide unguaranteed delivery of user plane PDUs between the NG-RAN node and the UPF. The transport network layer of the NG-C interface may be built based on IP transport. For reliable transfer of signaling messages, SCTP may be added on top of IP. The application layer signaling protocol may be called NGAP (NG Application Protocol). The SCTP layer may provide guaranteed delivery of application layer messages. For transport, IP layer point-to-point transmission may be used to carry signaling PDUs. The NG-C interface may provide the following functions: NG interface management, UE context management, UE mobility management, transfer of NAS messages, paging, PDU session management, configuration transfer, and alert message transmission.

[0013] gNB 115 or ng-eNB 120 may host one or more of the following functions: radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UEs in both uplink and downlink (e.g., scheduling), IP and Ethernet header compression, ciphering, and data integrity protection, selection of an AMF at UE attachment if routing to the AMF cannot be determined from information provided by the UE, routing of user plane data towards the UPF, routing of control plane information towards the AMF, connection setup and release, scheduling and transmission of paging messages, scheduling and transmission of system broadcast information (e.g., originating from the AMF), measurement and measurement report configuration for mobility and scheduling, transport level packet marking in the uplink, session management, support for network slicing, QoS flow management and mapping to data radio bearers, support for UEs in RRC inactive state, distribution functions for NAS messages, radio access network sharing, dual connectivity, close interworking between NR and E-UTRA, security and radio configuration for user plane 5G system (5GS) Cellular IoT (CIoT) optimization.

[0014] The AMF 130 may host one or more of the following functions: NAS signal termination, NAS signaling security, AS security control, CN inter-node signaling for mobility between 3GPP access networks, idle mode UE reachability (including control and execution of paging retransmissions), registration area management, support for intra-system and inter-system mobility, access authentication, access authorization including checking roaming rights, mobility management control (subscriptions and policies), support for network slicing, selection of Session Management Function (SMF), selection of 5GS CIoT optimization.

[0015] The UPF 135 may host one or more of the following functions: anchor points for Intra- / Inter-RAT mobility (if applicable), external PDU session points for interconnection with data networks, packet routing and forwarding, packet inspection and policy rule enforcement for the user plane part, traffic utilization reporting, uplink classifier to support routing of traffic flows to the data network, branching points to support multi-homed PDU sessions, QoS handling for the user plane, e.g., packet filtering, gating, UL / DL rate enforcement, uplink traffic validation (mapping of Service Data Flows (SDF) to QoS flows), downlink packet buffering and downlink data notification triggering.

[0016] As shown in FIG. 1, the NG-RAN 105 includes two UEs 125 (e.g., UE The NG-RAN 105 may support a PC5 interface between two UEs (UE 125A and UE 125B). In the PC5 interface, the communication direction between two UEs (e.g., from UE 125A to UE 125B or vice versa) may be referred to as a sidelink. Sidelink transmission and reception over the PC5 interface may be supported when the UE 125 is within NG-RAN 105 coverage, regardless of the RRC state the UE is in, and when the UE 125 is outside NG-RAN 105 coverage. Support for V2X services over the PC5 interface may be provided by NR sidelink communication and / or V2X sidelink communication.

[0017] PC5-S signaling can be used to establish a unicast link via a direct communication request / accept message. The UE can self-generate its source Layer-2 ID for the PC5 unicast link, for example, based on the V2X service type. During the unicast link establishment procedure, the UE can self-generate its source Layer-2 ID for the PC5 unicast link. The PC5 unicast link establishment procedure may send a PC5-2 ID to a peer UE, e.g., a UE for which a destination ID has been received from a higher layer. The pair of source Layer-2 ID and destination Layer-2 ID may uniquely identify a unicast link. The receiving UE may verify that the destination ID belongs to it and may accept the unicast link establishment request from the sending UE. During the PC5 unicast link establishment procedure, PC5-RRC procedures at the access stratum may be performed for the purpose of establishing a UE sidelink context, as well as for AS layer configuration, capability exchange, etc. PC5-RRC signaling may enable UE capability exchange and AS layer configuration, such as sidelink radio bearer configuration, between a pair of UEs for which a PC5 unicast link has been established.

[0018] NR sidelink communication may support one of three transmission modes (e.g., unicast transmission, groupcast transmission, and broadcast transmission) for a pair of source and destination Layer-2 IDs within an AS. The unicast transmission mode may be characterized by supporting one PC5-RRC connection between peer UEs for the pair, transmitting and receiving control information and user traffic between peer UEs in the sidelink, supporting sidelink HARQ feedback, supporting sidelink transmit power control, supporting RLC Acknowledged Mode (AM), and detecting radio link failures for the PC5-RRC connection. The groupcast transmission is characterized by transmitting and receiving user traffic between UEs belonging to the group in the sidelink, and supporting sidelink HARQ feedback. The broadcast transmission may be characterized by transmitting and receiving user traffic between UEs in the sidelink.

[0019] The source Layer-2 ID, destination Layer-2 ID, and PC5 link identifier may be used for NR sidelink communications. The source Layer-2 ID may identify the sender of data in NR sidelink communications. The source Layer-2 ID may be 24 bits long and may be split into two-bit strings at the media access control (MAC) layer, where one bit string is the least significant 8-bit portion of the source Layer-2 ID and is transmitted to the sender's physical layer. This may identify the intended data source in the sidelink control information and may be used for packet filtering at the receiver's physical layer. In this case, the second bit string may be the most significant 16-bit portion of the source Layer-2 ID and is carried in the media access control (MAC) header. This may be used for packet filtering at the receiver's MAC layer. The destination Layer-2 ID may identify the target of data in NR sidelink communications. For NR sidelink communications, the destination Layer-2 ID may be 24 bits long and may be split into two bit strings at the MAC layer, where one bit string is the least significant 16-bit portion of the destination Layer-2 ID and is sent to the sender's physical layer. This may identify the intended data target in the sidelink control information and may be used for packet filtering at the receiver's physical layer, while the second bit string is the most significant 8-bit portion of the destination Layer-2 ID and is carried in the MAC header. This may be used for packet filtering at the receiver's MAC layer. The PC5 link identifier may uniquely identify a PC5 unicast link within a UE for the lifetime of the PC5 unicast link. The PC5 link identifier may be used to identify a PC5 unicast link for which a sidelink Radio Link Failure (RLF) has been declared and the PC5-RRC connection has been released.

[0020] 2A and 2B illustrate example radio protocol stacks for the user plane and control plane, respectively, in accordance with some aspects of one or more exemplary embodiments of the present disclosure. As shown in FIG. 2A, the user plane protocol stack for the Uu interface (between the UE 125 and the gNB 115) includes Service Data Adaptation Protocol (SDAP) 201 and SDAP 211, Packet Data Convergence Protocol (PDCP) 202 and PDCP 213. 12, Radio Link Control (RLC) 203 and RLC 213, Layer 2 MAC 204 and MAC 214, and Physical Layer (PHY) 205 and PHY 215 (Layer 1 also referred to as L1).

[0021] The PHY 205 and PHY 215 provide transport channels 244 to the MAC 204 and MAC 214 sublayers. The MAC 204 and MAC 214 sublayers provide logical channels 243 to the RLC 203 and RLC 213 sublayers. The RLC 203 and RLC 213 sublayers provide RLC channels 242 to the PDCP 202 and PDCP 212 sublayers. The PDCP 202 and PDCP 212 sublayers provide radio bearers 241 to the SDAP 201 and SDAP 211 sublayers. Radio bearers can be classified into two groups: data radio bearers (DRBs) for user plane data and signaling radio bearers (SRBs) for control plane data. The SDAP 201 and SDAP 211 sublayers provide QoS flows 240 to the 5GC.

[0022] The main services and functions of the MAC 204 or MAC 214 sublayer include: mapping between logical channels and transport channels, multiplexing / demultiplexing of MAC Service Data Units (SDUs) belonging to one or different logical channels to / from Transport Blocks (TB) conveyed on transport channels to / from the physical layer, scheduling of information reports, error correction through Hybrid Automatic Repeat Request (HARQ) (one HARQ entity per cell in case of Carrier Aggregation (CA)), priority handling between UEs by dynamic scheduling, priority handling between logical channels of one UE by Logical Channel Prioritization (LCP), priority handling between overlapping resources of one UE, and padding. One MAC entity may support multiple numerologies, transmission timings, and cells. The mapping of priority decisions within a logical channel controls which numerology, cell, and transmission timing a logical channel may use.

[0023] The HARQ function may ensure communication between peer entities at Layer 1. One HARQ process may support one TB if the physical layer is not configured for downlink / uplink spatial multiplexing, and one or more TBs if the physical layer is configured for downlink / uplink spatial multiplexing.

[0024] The RLC 203 or RLC 213 sublayer may support three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC configuration may be according to the logical channel, independent of the numerology and / or transmission time, and Automatic Repeat Request (ARQ) may operate with either the numerology and / or transmission time for which the logical channel is configured.

[0025] The main services and functions of the RLC 203 or RLC 213 sublayer depend on the transmission mode (e.g., TM, UM, or AM) and may include: transmission of higher layer PDUs; independent sequence numbering within PDCP (UM and AM); error correction through ARQ (AM only); segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; reassembly of SDUs (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment and protocol error detection (AM only).

[0026] An automatic repeat request in the RLC 203 or RLC 213 sublayer may have the following properties: ARQ retransmits RLC SDUs or RLC SDU segments based on an RLC status report; polling of RLC status reports may be used by the RLC as needed; the RLC receiver may also trigger an RLC status report after detecting a missed RLC SDU or RLC SDU segment.

[0027] The main services and functions of the PDCP 202 or PDCP 212 sublayer include: transmission of data (user plane or control plane), preservation of PDCP sequence numbers (SNs), header compression and decompression using the Robust Header Compression (ROHC) protocol, encryption and decryption, integrity protection and integrity verification, timer-based SDU discard, routing for split bearers, duplication, reordering and in-order delivery, out-of-order delivery, and duplicate discard.

[0028] The main services and functions of the SDAP 201 or SDAP 211 include: mapping between QoS flows and data radio bearers, marking of QoS Flow ID (QFI) in both downlink and uplink. One protocol entity of the SDAP can be configured for each individual PDU session.

[0029] As shown in FIG. 2B, the control plane protocol stack of the Uu interface (between the UE 125 and the gNB 115) includes the PHY layer (Layer 1) as described above, and the MAC, RLC, and PDCP sublayers of Layer 2, as well as the RRC 206 and RRC 216 sublayers. The main services and functions of the RRC 206 and RRC 216 sublayers on the Uu interface include: broadcasting system information about the AS and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance, and release of the RRC connection between the UE and NG-RAN (including adding, modifying, and releasing carrier aggregation and adding, modifying, and releasing dual connectivity within the NR or between E-UTRA and NR); security functions including key management; establishment, configuration, maintenance, and release of SRBs and DRBs; mobility functions (including handover and context transfer, UE cell selection and reselection, and cell selection and reselection control, and inter-RAT mobility); QoS management functions; UE measurement result reporting and reporting control; detection and recovery from radio link failure; and transmission of NAS messages from the NAS to the UE and from the UE to the NAS. The NAS 207 and NAS 227 layers are control protocols (terminated in the AMF on the network side) that perform functions such as authentication, mobility management, and security control.

[0030] Sidelink specific services and functions of the RRC sublayer on the Uu interface include: configuration of sidelink resource allocation via system information or dedicated signaling, reporting of UE sidelink information, configuration and reporting of sidelink related measurements, reporting of UE assistance information for SL traffic patterns.

[0031] 3A, 3B, and 3C illustrate example mappings between logical channels and transport channels in the downlink, uplink, and sidelink, respectively, in accordance with some aspects of one or more example embodiments of the present disclosure. Different types of data transmission services may be provided by the MAC. Each logical channel type may be defined by the type of information transmitted. Each logical channel may be classified into two groups: control channels and traffic channels. Control channels may be used for transmission of control plane information only. Broadcast Control Channel (BCCH) A Control Channel (CCCH) is a downlink channel for broadcasting system control information. A Paging Control Channel (PCCH) is a downlink channel that carries paging messages. A Common Control Channel (CCCH) is a channel for transmitting control information between UEs and the network. This channel may be used for UEs that do not have an RRC connection with the network. A Dedicated Control Channel (DCCH) is a point-to-point bidirectional channel that transmits dedicated control information between a UE and the network and may be used by UEs that have an RRC connection. A Traffic Channel (SCCH) may be used for transmitting user plane information only. A Dedicated Traffic Channel (DTCH) is a point-to-point channel dedicated to one UE for transmitting user information. A DTCH may exist in both the uplink and downlink. A Sidelink Control Channel (SCCH) is a point-to-point channel dedicated to one UE for transmitting user information. A Sidelink Traffic Channel (STCH) is a sidelink channel for transmitting control information (e.g., PC5-RRC and PC5-S messages) from one UE to another. The Sidelink Broadcast Control Channel (SBCCH) is a sidelink channel for transmitting user information from one UE to other UEs. The Sidelink Broadcast Control Channel (SBCCH) is a sidelink channel for broadcasting sidelink system information from one UE to other UEs.

[0032] Types of downlink transport channels include the Broadcast Channel (BCH), the Downlink Shared Channel (DL-SCH), and the Paging Channel (PCH). The BCH may be characterized by a fixed, predefined transport format and the requirement to be broadcast throughout the coverage area of ​​a cell either as a single message or by beamforming different BCH instances. The DL-SCH may be characterized by support for HARQ, support for dynamic link modulation adaptation by varying modulation, coding, and transmit power, the possibility of cell-wide broadcast, the possibility of using beamforming, support for both dynamic and semi-static resource allocation, and support for UE discontinuous reception (DRX) to reduce UE power consumption. The DL-SCH may be characterized by support for HARQ, support for dynamic link modulation adaptation by varying modulation, coding, and transmit power, the possibility of cell-wide broadcasting, the possibility of using beamforming, support for both dynamic and semi-static resource allocation, and support for UE Discontinuous Reception (DRX) to reduce UE power consumption. The PCH may be characterized by support for UE Discontinuous Reception (DRX) to reduce UE power consumption (the DRX cycle is indicated to the UE by the network), requirements broadcast throughout the coverage area of ​​the cell either as a standalone message or by beamforming different BCH instances, and mapping to physical resources that can also be used dynamically for traffic / other control channels.

[0033] In the downlink, the following connections between logical channels and transport channels may exist: BCCH may be mapped to BCH, BCCH may be mapped to DL-SCH, PCCH may be mapped to PCH, CCCH may be mapped to DL-SCH, DCCH may be mapped to DL-SCH, and DTCH may be mapped to DL-SCH.

[0034] Types of uplink transport channels include the Uplink Shared Channel (UL-SCH) and the Random Access Channel (RACH). The UL-SCH may be characterized by the availability of beamforming, support for dynamic link modulation adaptation by varying transmit power and possibly modulation and coding, support for HARQ, and support for both dynamic and semi-static resource allocation. The RACH may be characterized by limited control information and collision risk.

[0035] In the uplink, the following connections may exist between logical channels and transport channels: CCCH may be mapped to UL-SCH, DCCH may be mapped to UL-SCH, and DTCH may be mapped to UL-SCH.

[0036] Types of sidelink transport channels include: Sidelink Broadcast Channel (SL-BCH) and Sidelink Shared Channel (SL-SCH). The SL-BCH may be characterized by a predefined transport format. The SL-SCH may be characterized by supporting unicast, groupcast, and broadcast transmissions, supporting both UE automatic resource selection and scheduled resource allocation by the NG-RAN, supporting both dynamic and semi-static resource allocation when the UE is assigned resources by the NG-RAN, supporting HARQ, and supporting dynamic link modulation adaptation by varying transmit power, modulation, and coding.

[0037] In the sidelink, the following connections may exist between logical channels and transport channels: SCCH may be mapped to SL-SCH, STCH may be mapped to SL-SCH, and SBCCH may be mapped to SL-BCH.

[0038] 4A, 4B, and 4C illustrate example mappings between transport channels and physical channels in the downlink, uplink, and sidelink, respectively, in accordance with some aspects of one or more exemplary embodiments of the present disclosure. The downlink physical channels include a Physical Downlink Shared Channel (PDSCH), a Physical Downlink Control Channel (PDCCH), and a Physical Broadcast Channel (PBCH). The PCH and DL-SCH transport channels are mapped to the PDSCH. The BCH transport channel is mapped to the PBCH. Although no transport channels are mapped to the PDCCH, downlink control information (DCI) is transmitted via the PDCCH.

[0039] Uplink physical channels include the Physical Uplink Shared Channel (Physical Uplink Control Channel), the Physical Uplink Control Channel (PUCCH), and the Physical Random Access Channel (Physical Random Access Channel). The UL-SCH transport channel can be mapped to the PUSCH, and the RACH transport channel can be mapped to the PRACH. The transport channels are not mapped to the PUCCH, but uplink control information (UCI) is transmitted via the PUCCH.

[0040] The physical channels of the sidelink are the Physical Sidelink Shared Channel (PSSCH) and the Physical Sidelink Control Channel (PSCCH). The Physical Sidelink Control Channel (PSCCH) includes the Physical Sidelink Control Channel (PSCCH), the Physical Sidelink Feedback Channel (PSFCH), and the Physical Sidelink Broadcast Channel (PSBCH). The Physical Sidelink Control Channel (PSCCH) may indicate the resources and other transmission parameters that the UE uses for the PSSCH. The Physical Sidelink Shared Channel (PSSCH) may transmit TBs of data itself, as well as control information and Channel State Information (CSI) feedback triggers for the HARQ procedure. At least six Orthogonal Frequency Division Multiplexing (OFDM) symbols within a slot may be used for PSSCH transmission. The Physical Sidelink Feedback Channel (PSFCH) may carry HARQ feedback on the sidelink from the UE that is the intended recipient of a PSSCH transmission to the UE that transmitted it. The PSFCH sequence may be transmitted in one PRB repeated in two OFDM symbols near the end of the sidelink resources within the slot. The SL-SCH transport channel may be mapped to the PSSCH. The SL-BCH may be mapped to the PSBCH. None of the transport channels may be mapped to the PSFCH, but Sidelink Feedback Control Information (SFCI) may be mapped to the PSFCH. None of the transport channels may be mapped to the PSCCH, but Sidelink Control Information (SCI) may be mapped to the PSCCH.

[0041] 5A, 5B, 5C, and 5D illustrate example radio protocol stacks for NR sidelink communications in accordance with some aspects of one or more exemplary embodiments of the present disclosure. The AS protocol stack for the user plane (i.e., for the STCH) in the PC5 interface may consist of the SDAP, PDCP, RLC, and MAC sublayers and a physical layer. The user plane protocol stack is shown in FIG. 5A. The AS protocol stack for the SBCCH in the PC5 interface may consist of the RRC, RLC, and MAC sublayers and a physical layer shown below in FIG. 5B. To support the PC5-S protocol, PC5-S resides above the PDCP, RLC, and MAC sublayers and a physical layer in the control plane protocol stack for the SCCH for PC5-S, as shown in FIG. 5C. The AS protocol stack for the control plane of the SCCH for RRC in the PC5 interface consists of the RRC, PDCP, RLC, and MAC sublayers and a physical layer. The control plane protocol stack for the SCCH for RRC is shown in FIG. 5D.

[0042] Sidelink Radio Bearers (SLRBs) can be classified into two groups: Sidelink Data Radio Bearers (SL DRBs) for user plane data and Sidelink Signaling Radio Bearers (SL SRBs) for control plane data. Separate SLSRBs using different SCCHs can be configured for PC5-RRC and PC5-S signaling, respectively.

[0043] The MAC sublayer may provide the following services and functions over the PC5 interface: radio resource selection, packet filtering, priority handling between uplink and sidelink transmissions for a UE, and sidelink CSI reporting. Due to the constraints of logical channel priority determination within MAC, only sidelink logical channels belonging to the same destination may be multiplexed into a MAC PDU for each unicast, groupcast, and broadcast transmission that may be associated with that destination. For packet filtering, the SL-SCH M, which contains both the source Layer-2 ID and the destination Layer-2 ID parts, is used. An AC header may be added to the MAC PDU. A Logical Channel Identifier (LCID) contained within the MAC subheader may uniquely identify a logical channel within a combination of source Layer-2 ID and destination Layer-2 ID.

[0044] The services and functions of the RLC sublayer may be supported for the sidelink. Both RLC Unacknowledged Mode (UM) and Acknowledged Mode (AM) may be used for unicast transmission, but only UM may be used for groupcast or broadcast transmission. In the case of UM, only one-way transmission may be supported for groupcast and broadcast.

[0045] The services and functions of the PDCP sublayer of the Uu interface can be supported for the sidelink with some restrictions: out-of-order delivery can only be supported for unicast transmission, and duplexing is not supported on the PC5 interface.

[0046] The SDAP sublayer may provide the following services and functions over the PC5 interface: mapping between QoS flows and sidelink data radio bearers. For one destination, there may be one SDAP entity for one of unicast, groupcast, and broadcast associated with that destination.

[0047] The RRC sublayer may provide the following services and functions over the PC5 interface: transmission of PC5-RRC messages between peer UEs, maintenance and release of a PC5-RRC connection between two UEs, and detection of sidelink radio link failure for a PC5-RRC connection based on indications from MAC or RLC. A PC5-RRC connection may be a logical connection between two UEs for a pair of source and destination Layer-2 IDs that can be considered established after the corresponding PC5 unicast link is established. There may be a one-to-one correspondence between PC5-RRC connections and PC5 unicast links. A UE may have multiple PC5-RRC connections with one or more UEs for different pairs of source and destination Layer-2 IDs. Separate PC5-RRC procedures and messages may be used for a given UE to transmit UE capabilities and sidelink configurations, including SL-DRB configurations, to a peer UE. Both peer UEs may exchange their respective UE capabilities and sidelink configurations using separate bidirectional procedures for both sidelink directions.

[0048] FIG. 6 illustrates exemplary physical signals for the downlink, uplink, and sidelink in accordance with some aspects of one or more exemplary embodiments of the present disclosure. Demodulation Reference Signals (DM-RSs) may be used in the downlink, uplink, and sidelink and may be used for channel estimation. DM-RSs are UE-specific reference signals that may be transmitted in the downlink, uplink, or sidelink along with physical channels and may be used for channel estimation and coherent detection of physical channels. Phase Tracking Reference Signals (PT-RSs) may be used in the downlink, uplink, and sidelink and may be used for phase tracking and mitigating performance loss due to phase noise. PT-RSs may be primarily used to estimate and minimize the impact of Common Phase Error (CPE) on system performance. Due to phase noise characteristics, PT-RS signals may be sparse in the frequency domain and dense in the time domain. PT-RS can occur in combination with DM-RS and when the network is configured to have PT-RS present. Positioning Reference Signals (PRS) can be used in the downlink for positioning using different positioning technologies. PRSs are used to align received signals from the base station with the local area network (LOI) in the receiver. By correlating with a local replica, it can be used to measure the delay of the downlink transmission. The CSI-RS may be used in the downlink and sidelink. CSI-RS may be used for channel state estimation, Reference Signal Received Power (RSRP) measurements for mobility and beam management, time / frequency tracking for modulation, and more. While CSI-RS may be configured for individual UEs, multiple users may share the same CSI-RS resources. A UE may specify CSI reports and transmit them to the base station in the uplink using the PUCCH or PUSCH. CSI reports may be carried in the sidelink MAC control element (CE). The Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS) may be used for radio frame synchronization. The PSS and SSS may be used for cell search procedures during initial attach or for mobility purposes. The Sounding Reference Signal (SRS) may be used in the uplink for uplink channel estimation. Similar to the CSI-RS, the SRS can also serve as a QCL reference for other physical channels, which can be configured and transmitted in a quasi-colocated relationship with the SRS. The Sidelink PSS (S-PSS) and Sidelink SSS (S-SSS) can be used in the sidelink for sidelink synchronization.

[0049] 7 illustrates example Radio Resource Control (RRC) states and transitions between different RRC states in accordance with some aspects of one or more example embodiments of the present disclosure. A UE may be in one of three RRC states: an RRC connected state 710, an RRC idle state 720, and an RRC inactive state 730. After power-up, the UE may be in the RRC idle state 720, and the UE may use initial access to establish a connection with the network via an RRC connection establishment procedure to transmit / receive data and / or voice calls. Once the RRC connection is established, the UE may be in the RRC connected state 710. The UE may transition from the RRC idle state 720 to the RRC connected state 710 or from the RRC connected state 710 to the RRC idle state 720 using an RRC connection establishment / release procedure 740.

[0050] The RRC inactive state 730 may be used to reduce signaling load and latency resulting from frequent transitions from the RRC connected state 710 to the RRC idle state 720 when the UE transmits frequent small data. In the RRC inactive state 730, the AS context may be preserved by both the UE and the gNB. As a result, a fast state transition from the RRC inactive state 730 to the RRC connected state 710 may occur. The UE may transition from the RRC inactive state 730 to the RRC connected state 710 or from the RRC connected state 710 to the RRC inactive state 730 using an RRC connection resume / deactivation procedure 760. The UE may transition from the RRC inactive state 730 to the RRC idle state 720 using an RRC connection release procedure 750.

[0051] FIG. 8 illustrates an example frame structure and physical resources in accordance with some aspects of one or more example embodiments of the present disclosure. Downlink, uplink, or sidelink transmissions may be organized into frames having ten (0-9) 1 ms subframes. Each subframe may consist of k slots (k=1, 2, 4, ...), where the number of slots per subframe, k, may depend on the subcarrier spacing of the carrier on which the transmission occurs. The slot duration may be 14 (0-13) symbols for the normal cyclic prefix (CP) and 12 symbols for the extended CP, and time may be scaled so that there are an integer number of slots within a subframe depending on the subcarrier spacing used. FIG. 8 illustrates the time Figure 1 shows a resource grid in the time and frequency domains. Each element of the resource grid, which contains one symbol in time and one subcarrier in frequency, is called a resource element (RE). A resource block (RB) can be defined as 12 consecutive subcarriers in the frequency domain.

[0052] In some examples, non-slot-based scheduling allows transmission of packets over a portion of a slot, e.g., 2, 4, or 7 OFDM symbols, which may also be referred to as minislots. Minislots may be used for low-latency applications such as URLLC and operation in unlicensed bands. In some embodiments, minislots may also be used for fast flexible scheduling of services (e.g., prioritized connections for URLLC in eMBB).

[0053] FIG. 9 illustrates exemplary component carrier configurations in different carrier aggregation scenarios in accordance with some aspects of one or more exemplary embodiments of the present disclosure. In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. A UE may simultaneously transmit and receive on one or more CCSs depending on its capabilities. CA may be supported for both contiguous and non-contiguous CCs within the same band or in different bands, as shown in FIG. 9. The gNG and the UE may communicate using a serving cell. The serving cell may be associated with at least one downlink CC (e.g., associated with only one downlink CC or associated with a downlink CC and an uplink CC). The serving cell may be a primary cell (PCell) or a secondary cell (SCell).

[0054] A UE may adjust the timing of its uplink transmission using an uplink timing control procedure. A timing advance (TA) may be used to adjust the uplink frame timing relative to the downlink frame timing. The gNB may specify a desired timing advance setting and provide it to the UE. The UE may use the provided TA to specify the uplink transmission timing relative to the observed downlink receive timing for the UE.

[0055] In the RRC connected state, the gNB may be responsible for maintaining the timing advance to keep L1 synchronized. Serving cells with the same timing advance applied to the uplink and the same timing reference cell are grouped into a timing advance group (TAG). A TAG may contain at least one serving cell with an uplink configured. The mapping of serving cells to TAGs may be configured by RRC. For a primary TAG, the UE may use the PCell as the timing cell, with the exception of shared spectrum channel access, where an SCell may also be used as a timing reference cell in certain cases. For a secondary TAG, the UE may use any of the activated SCells of this TAG as the timing reference cell and cannot change it unless necessary.

[0056] Timing advance updates may be signaled by the gNB to the UE via MAC CE commands. Such a command may restart a per-TAG timer, which may indicate whether L1 can be synchronized or not. That is, if the timer is running, L1 may be considered synchronized; otherwise, L1 may be considered not synchronized (in which case uplink transmissions may only occur on the PRACH).

[0057] A UE with one timing advance capability for CA may simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells (multiple serving cells are grouped into one TAG) that share the same timing advance. A UE with multiple timing advance capabilities may simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells (multiple serving cells grouped into multiple TAGs) with different timing advances. NG-RAN may ensure that each TAG contains at least one serving cell. A non-CA UE may receive on and transmit on one CC corresponding to only one serving cell (one serving cell in one TAG).

[0058] The multi-carrier nature of the physical layer in the case of CA may be exposed to the MAC layer, and one HARQ entity may be required per serving cell. When CA is configured, the UE may have one RRC connection with the network. During RRC connection establishment / re-establishment / handover, one serving cell (e.g., PCell) may provide NAS mobility information. Depending on the UE capabilities, SCells may be configured to form a serving cell set together with the PCell. The configured serving cell set for a UE may consist of one PCell and one or more SCells. Reconfiguration, addition, and removal of SCells are performed by RRC.

[0059] In a dual connectivity scenario, a UE may be configured with multiple cells including a Master Cell Group (MCG) for communication with a master base station, a Secondary Cell Group (SCG) for communication with secondary base stations, and two MAC entities, i.e., one MAC entity for the MCG for communication with the master base station and one MAC entity for the SCG for communication with the secondary base stations.

[0060] FIG. 10 illustrates exemplary bandwidth portion configuration and switching in accordance with some aspects of one or more exemplary embodiments of the present disclosure. A UE may be configured with one or more bandwidth portions (BWPs) 1010 (e.g., 1010A, 1010B) on a component carrier. In some examples, one of the one or more bandwidth portions may be active at a time. The active bandwidth portion may define the UE's operating bandwidth within the cell's operating bandwidth. During initial access, an initial bandwidth portion 1020 identified from system information may be used until the UE's configuration within the cell is received. Through bandwidth adaptation (BA), e.g., via BWP switching 1040, the UE's reception and transmission may be adjusted, rather than being as large as the cell's bandwidth. For example, the width may be commanded to change (e.g., to shrink during periods of low activity to conserve power), the location in the frequency domain may be moved (e.g., to increase scheduling flexibility), or the subcarrier spacing may be commanded to change (e.g., to enable different services). The first active BWP 1030 may be the active BWP at the time of RRC (re)configuration for the PCell or activation of the SCell.

[0061] For each downlink BWP or uplink BWP in a set of downlink BWPs or uplink BWPs, the UE may be provided with the following configuration parameters: subcarrier spacing (SCS), cyclic prefix, number of common RBs and consecutive RBs, index within the set of downlink BWPs or uplink BWPs by their respective BWP-Ids, BWP-common parameter set, and BWP-individual parameter set. A BWP may be associated with an OFDM numerology according to the subcarrier spacing and cyclic prefix configured for that BWP. For a serving cell, the UE may be provided with a default downlink BWP among the configured downlink BWPs. If the UE is not provided with a default downlink BWP, the default downlink BWP may be the initial downlink BWP.

[0062] A downlink BWP may be associated with a BWP inactivity timer. If a BWP inactivity timer associated with an active downlink BWP expires and a default downlink BWP is configured, the UE may perform a BWP switch to the default BWP. If a BWP inactivity timer associated with an active downlink BWP expires and a default downlink BWP is not configured, the UE may perform a BWP switch to the initial downlink BWP.

[0063] 11 illustrates an exemplary four-stage contention-based random access (CBRA) and contention-free random access (CFRA) process in accordance with some aspects of one or more exemplary embodiments of the present disclosure. FIG. 12 illustrates an exemplary two-stage contention-based random access (CBRA) and contention-free random access (CFRA) process in accordance with some aspects of one or more exemplary embodiments of the present disclosure. The random access procedure can be triggered by various events, such as initial access from an RRC idle state, an RRC connection re-establishment procedure, arrival of downlink or uplink data while in the RRC connected state when the uplink synchronization state is "unsynchronized", arrival of uplink data while in the RRC connected state when no PUCCH resources are available for a Scheduling Request (SR), an SR failure, a request by RRC during synchronization reconfiguration (e.g., handover), a transition from an RRC inactive state, a request for more system information (SI) to establish time alignment for a secondary TAG, Beam Failure Recovery (BFR), and a sustained uplink Listen-Before-Talk (LBT) failure on the PCell.

[0064] Two types of random access (RA) procedures can be supported: four-stage RA with MSGA and two-stage RA with MSGA. Both types of RA procedures can support contention-based random access (CBRA) and contention-free random access (CFRA), as shown in Figures 11 and 12.

[0065] When initiating a random access procedure, the UE may select a random access type based on the network configuration. If CFRA resources are not configured, the UE may use the RSRP threshold to select between a two-stage RA type or a staged RA type. If CFRA resources for a four-stage RA type are configured, the UE may perform random access with the four-stage RA type. If CFRA resources for a two-stage RA type are configured, the UE may perform random access with the two-stage RA type.

[0066] MSG1 for the 4-step RA type may consist of a preamble for the PRACH (step 1 of CBRA in FIG. 11). After transmitting MSG1, the UE may monitor a response from the network within a configured window (step 2 of CBRA in FIG. 11). In the case of CFRA, a dedicated preamble for MSG1 transmission may be allocated by the network (step 0 of CFRA in FIG. 11), and upon receiving a random access response (RAR) from the network, the UE may terminate the random access procedure as shown in FIG. 11 (steps 1 and 2 of CFRA in FIG. 11). In the case of CBRA, upon receiving a random access response (step 2 of CBRA in FIG. 11), the UE may transmit MSG3 using the uplink grant scheduled in the random access response (step 3 of CBRA in FIG. 11) and monitor contention resolution as shown in FIG. 11. If contention resolution is unsuccessful after MSG3 (re)transmission, the UE may revert to MSG1 transmission.

[0067] The MSGA for the two-step RA type may include a preamble on the PRACH and a payload on the PUSCH (e.g., step A of the CBRA in Figure 12). After transmitting the MSGA, the UE may monitor for a response from the network within a configured window. For the CFRA, A separate preamble and PUSCH resource may be configured for MSGA transmission (steps 0 and A of CFRA in FIG. 12), and upon receiving a network response (step B of CFRA in FIG. 12), the UE may terminate the random access procedure as shown in FIG. 12. In the case of CBRA, if contention resolution is successful upon receiving a network response (step B of CBRA in FIG. 12), the UE may terminate the random access procedure shown in FIG. 12; however, if a fallback indication is received in MSGB, the UE may perform transmission of MSG3 using the uplink grant scheduled in the fallback indication and monitor contention resolution. If contention resolution is unsuccessful after MSG3 (re)transmission, the UE may revert to MSGA transmission.

[0068] FIG. 13 illustrates an exemplary time and frequency structure of a synchronization signal and physical broadcast channel (PBCH) block (SSB) according to some aspects of one or more exemplary embodiments of the present disclosure. An SS / PBCH block (SSB) may consist of primary and secondary synchronization signals (PSS, SSS), each occupying one symbol and 127 subcarriers (e.g., subcarrier numbers 56 through 182 in FIG. 13 ), and a PBCH spanning three OFDM symbols and 240 subcarriers, with one symbol remaining unused in the center for the SSS, as shown in FIG. 13 . The possible time locations of the SSBs within a half-frame may be specified by the subcarrier spacing, and the period of the half-frame during which the SSBs are transmitted may be configured by the network. During a half-frame, different SSBs may be transmitted in different spatial directions (i.e., using different beams and across the entire cell coverage area).

[0069] The PBCH may be used to carry a Master Information Block (MIB) that the UE uses during cell search and initial access procedures. The UE may first decode the PBCH / MIB to receive other system information. The MIB may provide the UE with the parameters necessary to acquire System Information Block 1 (SIB1), more specifically, the information necessary to monitor the PDCCH to schedule the PDSCH carrying SIB1. In addition, the MIB may indicate Cell Barred status information. The MIB and SIB1 may be collectively referred to as Minimum System Information (SI), and SIB1 may be referred to as Remaining Minimum System Information (RMSI). The other System Information Blocks (SIBs) (e.g., SIB2, SIB3, ..., SIB10, and SIBpos) may be referred to as other SIs. Other SI may be broadcast periodically on the DL-SCH, broadcast on demand on the DL-SCH (e.g., upon request from UEs in RRC idle, RRC inactive, or RRC connected states), or sent individually on the DL-SCH to UEs in RRC connected state (e.g., upon request from UEs in RRC connected state if configured by the network, or when the UE has an active BWP and no common search space is configured).

[0070] FIG. 14 illustrates an exemplary SSB burst transmission according to some aspects of one or more exemplary embodiments of the present disclosure. The SSB burst may include N SSBs (e.g., SSB_1, SSB_2, . . . SSB_N), where each SSB of the N SSBs may correspond to a beam (e.g., Beam_1, Beam_2, . . . Beam_N). The SSB burst may be transmitted according to a periodicity (e.g., SSB burst duration). During a contention-based random access process, the UE may perform a random access resource selection process, in which the UE first selects an SSB and then selects an RA preamble. The UE may select an SSB with an RSRP higher than a configured threshold. In some embodiments, the UE may select any SSB if an SSB with an RSRP higher than the configured threshold is not available. A set of random access preambles may be associated with the SSB. After selecting an SSB, the UE selects a random access preamble from the set of random access preambles associated with that SSB. A random access preamble may be selected and obtained, and the selected random access preamble may be transmitted to initiate the random access process.

[0071] In some embodiments, a beam among the N beams may be associated with a CSI-RS resource (e.g., CSI-RSA_1, CSI-RS_2, ..., CSI-RS_N). The UE may measure the CSI-RS resource and select a CSI-RS with an RSRP higher than a configured threshold. The UE may select a random access preamble corresponding to the selected CSI-RS and may transmit the selected random access preamble to initiate the random access process. If there is no random access preamble associated with the selected CSI-RS, the UE may select a random access preamble corresponding to an SSB that is quasi-colocated with the selected CSI-RS.

[0072] In some embodiments, based on the UE's measurements of CSI-RS resources and the UE's CSI reporting, the base station may identify a Transmission Configuration Indication (TCI) state and indicate the TCI state to the UE, which may use the indicated TCI state for receiving downlink control information (e.g., via a PDCCH) or data (e.g., via a PDSCH). The UE may use the indicated TCI state to use an appropriate beam for receiving data or control information. The indication of the TCI state may use an RRC configuration or a combination of RRC signaling and dynamic signaling (e.g., via a MAC Control Element (MAC CE) and / or based on the value of a field in the downlink control information that schedules downlink transmissions). The TCI state may indicate a quasi-co-location (QCL) relationship between a downlink reference signal, such as a CSI-RS, and a DM-RS associated with a downlink control or data channel (e.g., a PDCCH or a PDSCH, respectively).

[0073] In some embodiments, a UE can be configured with a list of up to M TCI states using physical downlink shared channel (PDSCH) configuration parameters to decode the PDSCH according to the PDCCH detected in the DCI intended for the UE and a serving cell, where M may depend on the UE's capabilities. Each TCI-state can include parameters for configuring a QCL relationship between one or two downlink reference signals and a DM-RS port of the PDSCH, a DM-RS port of the PDCCH, or a CSI-RS port of a CSI-RS resource. The quasi-collocation relationship can be configured by one or more RRC parameters. The type of quasi-collocation corresponding to each DL RS can take one of the following values: 'QCL-TypeA': {Doppler shift, Doppler extension, mean delay, delay extension}, 'QCL-TypeB': {Doppler shift, Doppler extension}, 'QCL-TypeC': {Doppler shift, mean delay}, 'QCL-TypeD': {Spatial Rx parameters}. The UE may receive an activation command (eg, MAC CE) used to map the TCI state to a codepoint in the DCI field.

[0074] 15 illustrates example components of a user terminal and a base station in accordance with some aspects of one or more example embodiments of the present disclosure. In one embodiment, the example components of FIG. 15 may be all or a subset of the blocks, and the functionality of FIG. 15 may be considered to illustrate functional blocks of an example base station 1505. In other embodiments, the example components of FIG. 15 may be considered to illustrate functional blocks of an example user terminal 1500. Thus, the components illustrated in FIG. 15 are not necessarily limited to either a user terminal or a base station.

[0075] With reference to FIG. 15, antenna 1510 can be used to transmit or receive electromagnetic signals. The antenna 1510 may include one or more antenna elements, which may enable various input-output antenna configurations, including multiple-input multiple-output (MIMO), multiple-input single-output (MISO), and single-input multiple-output (SIMO) configurations. In some embodiments, the antenna 1510 may implement a massive MIMO configuration using tens or hundreds of antenna elements. The antenna 1510 may also use other multi-antenna techniques, such as beamforming. In some embodiments, depending on the capabilities of the UE 1500 and the type of the UE 1500 (e.g., a low-complexity UE), the UE 1500 may only support a single antenna.

[0076] The transceiver 1520 may communicate bidirectionally over a wireless link as described herein via the antenna 1510. For example, the transceiver 1520 may represent a wireless transceiver at a UE and may communicate bidirectionally with a wireless transceiver at a base station, or vice versa. The transceiver 1520 may include a modem for modulating packets and providing the modulated packets to the antenna 1510 for transmission, and for modulating packets received from the antenna 1510.

[0077] The memory 1530 may include RAM and ROM. The memory 1530 may store computer-readable, computer-executable code 1535, which includes instructions that, when executed, cause the processor to perform various functions described herein. In some examples, the memory 1530 may include, among other things, a Basic Input / Output System (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0078] The processor 1540 may include a hardware device having processing capabilities (e.g., a general-purpose processor, a digital signal processor (DSP), a central processing unit (CPU), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some examples, the processor 1540 may be configured to operate a memory using a memory controller. In other examples, the memory controller may be incorporated into the processor 1540. The processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1530) to cause the UE 1500 or the base station 1505 to perform various functions.

[0079] The CPU 1550 may perform basic arithmetic, logic, control, and input / output (I / O) operations specified by computer instructions in the memory 1530. The UE 1500 and / or base station 1505 may include other peripheral components, such as a graphics processing unit (GPU) 1560 and a global positioning system (GPS) 1570. The GPU 1560 is specialized circuitry that manipulates and modifies the memory 1530 at high speed to accelerate the processing performance of the UE 1500 and / or base station 1505. The GPS 1570 may be used to enable location-based services and other services based, for example, on the geographic location of the UE 1500.

[0080] In some examples, MBS services may be realized via single-cell transmission. MBS may be transmitted within the coverage of a single cell. One or more multicast / broadcast control channels (e.g., MCCHs) and one or more multicast / broadcast data channels (e.g., MTCHs) may be mapped on the DL-SCH. Scheduling may be performed by the gNB. Transmission of the multicast control channel and the multicast / broadcast data channel may be indicated by a per-logical-channel RNTI on the PDCCH. In some examples, a one-to-one mapping between a service identifier, such as a temporary mobile group identifier (TMGI), and a RAN-level identifier, such as a group identifier (G-RNTI), may be used for reception of the DL-SCH to which the multicast / broadcast data channel may be mapped. In some examples, a DL-SCH associated with the multicast / broadcast control channel and / or multicast / broadcast data channel transmission may be used, and HARQ or RLC retransmissions may not be used, and / or RLC Unacknowledged Mode (RLC UM) may be used. In other examples, some feedback (e.g., HARQ feedback or RLC feedback) may be used for transmissions over the multicast / broadcast control channel and / or multicast / broadcast data channel.

[0081] In some examples, the following scheduling information may be provided on the multicast / broadcast control channel for the multicast / broadcast data channel: scheduling cycle for the multicast / broadcast data channel, reception period for the multicast / broadcast data channel (e.g., the period the UE waits to receive PDCCHs after waking up from DRX), multicast / broadcast data channel inactivity timer (e.g., the period the UE waits to successfully decode a PDCCH indicating the DL-SCH to which this multicast / broadcast data channel is mapped, failing which it will re-enter DRX).

[0082] In some examples, one or more UE identifiers may be associated with the MBS transmission. The one or more identifiers may include at least one of one or more first RNTIs identifying a multicast / broadcast control channel transmission and one or more second RNTIs identifying a multicast / broadcast data channel transmission. The one or more first RNTIs identifying a multicast / broadcast control channel transmission may include a single-cell RNTI (SC-RNTI, although other names may be used). The one or more second RNTIs identifying a multicast / broadcast data channel transmission may include a G-RNTI (nG-RNTI or other names may be used).

[0083] In some examples, one or more logical channels may be associated with MBS transmission. The one or more logical channels may include a multicast / broadcast control channel. The multicast / broadcast control channel may be a point-to-multipoint downlink channel used to transmit MBS control information from the network to the UEs. This channel may be used by UEs that receive or are interested in receiving the MBS. The one or more logical channels may include a multicast / broadcast data channel. This channel may be a point-to-multipoint downlink channel for transmitting MBS traffic data from the network.

[0084] In some examples, a UE may use a procedure to inform the RAN that the UE is receiving or interested in receiving MBS service via an MBS radio bearer, and if so, inform the 5G RAN about the priority of MBS versus unicast reception or reception of the MBS service. An example is shown in FIG. 16. The UE may send a message (e.g., an MBS Interest Indication message) to inform the RAN that the UE is receiving / interested in receiving, or no longer receiving / not interested in receiving, the MBS service. The UE may transmit the message, e.g., to the RAN on the current and / or neighboring carriers. The transmission may be based on receiving one or more messages from the network (eg, a SIB message or a unicast RRC message) indicating one or more MBS service area identifiers for the frequency band.

[0085] In some examples, the UE may determine if the UE is capable of receiving MBS service (e.g., via a single-cell point-to-multipoint mechanism) and / or if the UE is An MBS service may be considered to be part of an MBS service of interest if the UE is receiving or is interested in receiving this service via a bearer associated with the MBS service, and / or if one session of this service is ongoing or about to be started, and / or if at least one of one or more MBS service identifiers indicated by the network is of interest to the UE.

[0086] In some examples, control information for receiving MBS services may be provided on a specific logical channel (e.g., the MCCH). The MCCH may carry one or more configuration messages indicating ongoing MBS sessions, as well as (corresponding to) information regarding when each session is scheduled, such as the scheduling period, scheduling window, and starting offset. The one or more configuration messages may provide information regarding neighboring cells transmitting MBS sessions that may be ongoing on the current cell. In some examples, a UE may receive one MBS service at a time or multiple MBS services in parallel.

[0087] In some examples, MCCH information (e.g., information sent in messages transmitted on the MCCH) may be transmitted periodically using a configurable repetition period, and the MCCH transmission (and its associated radio resources and MCS) may be indicated on the PDCCH.

[0088] In some examples, modification of MCCH information may be performed in a specific radio frame / subframe / slot and / or a modification period may be used. For example, within a modification period, the same MCCH information may be transmitted multiple times as defined by its scheduling (which is based on a recurrence period). The boundaries of the modification period may be defined by an SFN value of SFN mod m=0, where m is the number of radio frames that comprise the modification period. The modification period may be configured by SIB or by RRC signaling.

[0089] In some examples, when the network changes (part of) the MCCH information, it may notify UEs about the change in the first subframe / slot that can be used for MCCH transmission within a recurrence period. Upon receiving the change notification, UEs interested in receiving MBS services may acquire the new MCCH information starting from the same subframe / slot. The UE may apply the previously acquired MCCH information until the UE acquires the new MCCH information.

[0090] In an example, the system information block (SIB) may include information necessary to acquire transmissions related to the control information of the MBS, such as one or more discontinuous reception (DRX) parameters for monitoring scheduling information for transmissions related to the control information of the MBS, a scheduling period and offset for scheduling information for transmissions related to the control information of the MBS, a modification period for modifying content of communications related to the control information of the MBS, repetition information for repetition of transmissions related to the control information of the MBS, etc.

[0091] In one example, an information element (IE) may provide configuration parameters indicating, for example, a list of ongoing MBS sessions transmitted over one or more bearers for each MBS session, one or more associated RNTIs (e.g., G-RNTI, although other names may be used), and scheduling information. X) (e.g., an Inactivity Timer or an On Duration Timer), an RNTI for scrambling the scheduling and transmission of a multicast / broadcast traffic channel (e.g., MTCH, although other names may be used), one or more power management control parameters, one or more scheduling periodicity and / or offset values ​​for one or more MBS traffic channels, information regarding a list of neighboring cells, etc.

[0092] In an exemplary embodiment, broadcast / multicast RAN functionality for UEs in the RRC_CONNECTED, RRC_IDLE, and RRC_INATIVE states may be implemented. A group scheduling mechanism may be used to enable UEs to receive broadcast / multicast services. In some examples, broadcast / multicast services may be performed simultaneously with unicast reception. In some examples, broadcast / multicast service delivery may be dynamically changed between multicast (PTM) and unicast (PTP) with service continuity for a given UE. In some examples, the coordination function may be within the gNB-CU. In some examples, the reliability of broadcast / multicast services may be improved through UL feedback. The level of reliability may be based on the requirements of the application / service being provided. In some examples, the broadcast / multicast transmission area may be dynamically controlled within a single gNB-DU.

[0093] In some examples, the MAC entity may be configured by RRC with a DRX function that controls the UE's PDCCH monitoring activity for a number of RNTIs at the MAC entity. The RNTIs may include C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, and AI-RNTI. When RRC_CONNECTED, for an activated serving cell, if DRX is configured, the MAC entity may monitor PDCCH discontinuity using DRX operation; otherwise, the MAC entity may monitor the PDCCH.

[0094] RRC can control the DRX operation by setting several parameters, including drx-onDurationTimer, the duration at the start of a DRX cycle; drx-SlotOffset, the delay before the drx-onDurationTimer starts; drx-InactivityTimer, the duration after a PDCCH occasion where a PDCCH indicates a new UL or DL ​​transmission for the MAC entity; and drx-RetransmissionTimerDL (DL transmissions except for broadcast processes). DRx-HARQ-RTT-TimerDL (by DL HARQ process excluding broadcast process), the minimum duration before a DL retransmission is received, drx-RetransmissionTimerUL (by UL HARQ process), the maximum duration before a grant for UL retransmission is received, drx-LongCycleStartOffset, the Long DRX cycle and drx-StartOffset defining the subframe at which the Long and Short DRX Cycles start, drx-ShortCycle (optional), the Short DRX cycle, drx-ShortCycleTimer (optional), the duration the UE may follow the Short DRX cycle, drx-HARQ-RTT-TimerDL (by DL HARQ process excluding broadcast process), the minimum duration before a DL allocation for HARQ retransmission is expected by the MAC entity, drx-HARQ-RTT-TimerUL (by UL HARQ process), the minimum duration before a UL HARQ retransmission grant is expected by the MAC entity.

[0095] In some examples, an information element (e.g., an SPS-Config IE) may be used to configure downlink semi-persistent transmission. Multiple downlink SPS configurations may be configured in one BWP of a serving cell. The SPS configuration parameters may include a periodicity parameter indicating the periodicity or DL ​​SPS resource, and an sps-ConfigIndex indicating an index of one of the multiple SPS configurations.

[0096] The UE may use one or more configured CONTROLLERS according to the corresponding search space configuration. A set of PDCCH candidates for configured monitoring occasions may be monitored in REsource SETs (CORESETs). A CORESET may include a set of physical resource blocks (PRBs), each of which is 1 to 3 OFDM symbols in length. Resource units, Resource Element Groups (REGs), and Control Channel Elements (CCEs) may be defined within a CORESET, with each CCE including a set of REGs. A control channel may be formed by a collection of CCEs. Different code rates for the control channel may be achieved by aggregating different numbers of CCEs. Interleaved and non-interleaved CCE-REG mapping may be supported within a CORESET.

[0097] In some examples, semi-persistent scheduling (SPS) can be configured by RRC per serving cell and per BWP. Multiple assignments can be active simultaneously within the same BWP. DL SPS activation and deactivation can be independent between serving cells. For DL ​​SPS, DL assignments are provided by the PDCCH and can be saved or cleared based on L1 signaling indicating SPS activation or deactivation.

[0098] The RRC may be configured with the following parameters when configuring the SPS: cs-RNTI, the CS-RNTI for activation, deactivation, and retransmission; nrofHARQ-Processes, the number of HARQ processes configured for the SPS; harq-ProcID-Offset, the offset of the HARQ processes for the SPS; periodicity, the periodicity of the configured downlink assignment for the SPS.

[0099] In some examples, with semi-persistent scheduling (SPS), the nNB may allocate downlink resources to the UE for initial HARQ transmission, the RRC may define the periodicity of the configured downlink assignment, and the PDCCH designated by the CS-RNTI may signal, activate, or deactivate the configured downlink assignment. The PDCCH designated by the CS-RNTI may be implicitly reused until the downlink assignment is deactivated according to the periodicity defined by the RRC.

[0100] In some examples, MBS transmissions may be constrained to one or more BWPs of a cell, such as the initial BWP of a cell. Some pre-configured / configurable MBS services may be broadcast via BWPs other than the initial BWP. In some examples, MBS services may be broadcast via one or more beams, where not all beams are associated with a cell. In some examples, the same MBS message may be repeated in all of the transmitted beams in multi-beam operation.

[0101] In some examples, on-demand system information transmission may be provided, which may improve efficiency, especially when considering low activity on the control channel, such as at night.

[0102] In some examples, a UE in RRC_IDLE / RRC_INATIVE state may C It is possible to receive a multicast session without entering the connected state.

[0103] In some examples, a UE may identify active MBS services on a cell based on a list of supported services signaled as part of multicast control information within a transmission area. UEs interested in a service may perform procedures to initiate PTM reception for the service of interest. UEs in RRC IDLE or RRC INATIVE state may be mobile and may perform cell reselection to a neighboring cell. For UEs interested in receiving MBS services, the UE may learn of MBS service support in neighboring cells for cell reselection. The availability and support of the MBS service of interest in neighboring cells may be learned by a UE receiving PTM services in RRC_IDLE or RRC_INACTIVE state. Knowing the availability of the MBS service of interest in neighboring cells may allow the UE to prioritize these cells or frequencies in cell reselection.

[0104] In some examples, upon cell reselection, the UE may acquire multicast control information for the target cell before it begins listening for multicast data transmissions.

[0105] In some examples, a system information block (SIB) may be used to signal the configuration necessary to receive periodically transmitted multicast / broadcast control information. A multicast / broadcast control message may be introduced to signal the configuration necessary to receive a multicast / broadcast session on a multicast traffic channel.

[0106] In some cases, not all MBS services supported within a transmission area are available to UEs in all RRC states, and some MBS transmissions within a cell may be reserved for reception in a specific RRC state, such as the RRC CONNECTED state. Based on the nature of the MBS services, it can be observed that some of these services may be efficiently received in an idle or inactive state, such as IPTV, while some, such as mission-critical services, are more efficiently provided in the RRC CONNECTED state. For services that can be received in the IDLE or INACTIVE state, the control information required to receive the multicast session may be available to the UE before PTM reception. However, for services provided by the gNB that are only received in the RRC CONNECTED state, some control information may be transmitted in the CONNECTED state. In some instances, some MBS services may only be supported in the RRC CONNECTED state. For services available to UEs in the RRC CONNECTED state, some multicast / broadcast control information may be provided using unicast signaling.

[0107] In some examples, resources may be flexibly allocated between unicast and broadcast / multicast services. A network may deploy MBS services on a portion of a carrier bandwidth, rather than across the entire carrier bandwidth. For example, some portions of a cell's BWPs may support MBS services, while other portions may support unicast services. BWPs are associated with a subcarrier spacing (SCS) / numerology, and different services may require different SCSs. Services across BWPs supporting different MBSs within a cell may differ. MBS services, such as public safety, mission critical, etc., may have different scheduling requirements, e.g., different SCSs, than other transmission areas. In such cases, the network may prefer to provide these services in separate BWPs. In some examples, MBS services may be supported per carrier or per bandwidth portion. Different BWPs within a cell may provide different MBS services.

[0108] In some examples, PTM transmission may be based on DL-SCH, e.g., receiving MBS PTM bearers through monitoring the PDCCH scheduling group RNTI on the PDSCH. UEs may be provided with the associated MBSMRB / DRB configuration via separate RRC signaling.

[0109] In some examples, multicast / broadcast services may be provided by DRB or MRB (C-RNTI / G-RNTI), and the actual dynamic switch and selection may be visible to the UE. The decision to dynamically switch between multicast (PTM) and unicast (PTP / DRB) may be visible to the UE. In some examples, by providing physical layer enhancements such as HARQ / feedback and including PDCP functions for reordering and duplicate detection (e.g., duplicate discard), even higher reliability may be provided using unicast bearers, if needed (e.g., RLC AM). The use of HARQ retransmissions and HARQ feedback may also be beneficial for PTM.

[0110] In existing point-to-multipoint solutions, one control channel is configured through SIB2, and one or more traffic channels are configured by the control channel. The SIB, control channel, and all traffic channels may be on the same carrier. The traffic channels may have different scheduling cycles, receive periods, and inactivity timers, and may not perform any retransmissions, but one control channel is configured and used to schedule all traffic channels. Existing point-to-multipoint solutions lack flexibility, which can result in duplicate transmissions of control information and inefficient delivery of multicast broadcast services. Exemplary embodiments provide improved signaling and configuration of multicast broadcast services.

[0111] Example embodiments may enable initial RAN-level configuration of multicast and broadcast service (MBS)-related control information. MBS mechanisms may be used to provide multicast and broadcast services and may also be used for Mission Critical Push-to-Talk (MCPTT), Internet of Things (IoT), and Vehicle-to-Everything (V2X). In some embodiments, a cell may transmit multicast / broadcast data and control information to a group of mobile communication devices using a physical downlink shared channel (PDSCH). In some examples, multicast / broadcast service data may be transmitted on the PDSCH using a group-specific radio network temporary identifier (e.g., G-RNTI, although other names may be used), and control information may be transmitted on the PDSCH using an SC-PTM radio network temporary identifier (e.g., SC-RNTI, although other names may be used).

[0112] In some exemplary embodiments, to receive an MBS transmission, a mobile communication device may receive one or more of three items: system information (e.g., provided by a System Information Block (SIB)); a control channel for receiving multicast / broadcast control information (e.g., via a Multicast / Broadcast Control Channel (MCCH) logical channel, although other names may be used); and multicast / broadcast data (e.g., via a Multicast / Broadcast Traffic Channel (MTCH) logical channel, although other names may be used).

[0113] In some example embodiments, such as that shown in FIG. 17, the system information provided by the SIB determines how to provide multicast / broadcast control information (e.g., The system information may indicate whether the multicast / broadcast control information is to be received (e.g., via the MTCH channel). The system information may indicate, for example, a modification period during which the control information may be modified, a repetition period / offset during which the multicast / broadcast control information may be repeated, etc. In some examples, the above SIB information may be transmitted via unicast RRC signaling. The control information (e.g., MCCH) may indicate available multicast / broadcast services and how to receive multicast / broadcast data (e.g., via the MTCH) via associated service identifiers (e.g., temporary mobile group identifiers (TMGIs), although other names may also be used). A logical channel (e.g., the MTCH) for transmitting multicast / broadcast data may be used to transmit data of one multicast / broadcast service. In some examples, the control information (e.g., MCCH) may include a configuration message for configuring MBS-related parameters. The configuration message may indicate ongoing multicast / broadcast sessions. The configuration message may further indicate information based on which each session may be scheduled and may also include a neighbor cell list for neighbor cells that may provide the same service (e.g., the same service identifier, such as the same TMGI).

[0114] In some example embodiments, UEs in a 5G network may initially discover and subscribe to MBS services through application layer signaling or other means, such as pre-provisioning within the device. Such service discovery signaling / provisioning may provide the UE with several service identifiers for the subscribed MBS services. These identifiers may include one or more temporary mobile group identifiers (TMGIs). Other names for such identifiers, such as nTMGIs, may also be used.

[0115] In some example embodiments, one or more MBS content channels with similar radio transmission and / or QoS configuration requirements may be bundled and assigned the same MBS service identifier, e.g., the same nTMGI. In some examples, a UE receiving multiple MBS services may be provided with multiple nTMGIs, one for each bundled service.

[0116] In some examples, service flows may be mapped to MBS radio bearers (MBRs) using a 1:1 or N:1 mapping to service identifiers.

[0117] In some examples, a UE that detects a service identifier for its target MBS service may request the RAN to provide the UE with a RAN-level configuration for the MBS service. In some examples, an MBS server in the network may trigger the RAN to send an MBS RAN-level configuration to the UE after application layer registration of the UE with the server.

[0118] In some examples, the UE may transition to an RRC connected state (e.g., from an RRC inactive state or an RRC idle state) and exchange RRC signaling with the RAN to obtain an initial MCCH configuration. The UE or MBS server may provide the RAN with a list of target nTMGIs for the UE. This MCCH configuration message signaling may be carried on the UE's default BWP / carrier and may also be carried on an LTE carrier.

[0119] In some example embodiments shown in FIG. 18, the configuration of the multicast / broadcast control channel associated with the UE's target MBS service (e.g., identified by nTMGIs) may be provided to the UE at the UE's request or initiated by an MBS server in the UE's default active BWP network on an NR or LTE carrier.

[0120] In some examples, UEs may obtain one or more service level identifiers, e.g., nTMGIs, for their target MBS services as part of service discovery through application layer signaling or by other means, such as pre-provisioning of equipment.

[0121] In some examples, a network may use MBS capabilities for various transmission areas, including multimedia broadcasting and multicasting of content such as video, public safety group communications, and some Internet of Things (IoT) applications. In some examples, multiple simultaneous MBS services with different traffic patterns, bandwidth, and latency requirements may be configured. The network may provide MBS data using a mix of MCCH / MTCH configurations that differ in terms of PHY numerology, bandwidth portions (BWPs), periodicity, and QoS requirements, including, but not limited to, range and reliability.

[0122] In some examples, UEs receiving MBS services may be in an RRC connected, idle, or inactive state and may have different active or default bandwidth portions on the NR or LTE carrier. In some examples, UEs receiving MBS data may be on different active or default BWPs for each unicast service. Exemplary embodiments may enable MBS configuration signaling to avoid instructing UEs to track and process MBS information unrelated to their target service.

[0123] In some examples, to support various MBS transmission areas, a UE may be configured and / or scheduled with a mix of different, possibly simultaneous, multicast / broadcast control and traffic channels (e.g., MCCH / MTCHs) having different PHY numerologies, bandwidth portions (BWPs), periodicity, and QoS requirements and / or reliability.

[0124] In some examples, UEs in a group receiving an MBS service may be in different RRC states and / or on different NR carriers / BWPs or other, e.g., LTE carriers for unicast services.

[0125] In some examples, MBS RAN configuration signaling may enable delivery of MBS control information for one of multiple MBS services delivered over multiple numerologies, BWPs, periodicities, and with different reliability requirements.

[0126] In some examples, MBS RAN configuration signaling may enable efficient delivery of relevant MBS control information for target UEs that may be in different RRC states on different NR carriers / BWPs or LTE carriers.

[0127] In some examples, MBS configuration signaling may allow for UE power consumption savings by ensuring that UEs only track and process information related to each target service.

[0128] In some examples, the MBS RAN level configuration information may consist of two parts: a configuration for control channel (eg, MCCH) transmission and a configuration for associated data channel (eg, MTCH) transmission.

[0129] In some examples, a multicast / broadcast control channel (e.g., MC The SIB indication information for receiving the multicast / broadcast control channel may be requested by the UE as needed. The UE may initiate a random access process to indicate a request for on-demand delivery of an SIB containing information for receiving the multicast / broadcast control channel.

[0130] In some examples, a multicast / broadcast control channel (eg, MCCH) configuration may be indicated to UEs using unicast RRC signaling.

[0131] In some exemplary embodiments shown in FIG. 19 , the configuration parameters of the multicast / broadcast control channel (e.g., MCCH) may indicate a BWP (e.g., which may include one or more BWP IDs) and / or a cell / carrier (e.g., which may include one or more cell IDs) and / or a CORESET (e.g., which may include one or more CORESET IDs) for which the multicast / broadcast control channel is scheduled (e.g., via a DCI that schedules the multicast / broadcast control channel) and / or transmitted. The configuration parameters of the multicast / broadcast control channel (e.g., MCCH) may further indicate a modification period, a repetition period, and an offset. In some exemplary embodiments, the UE may be configured with one or more RNTIs for repetition of the multicast / broadcast control channel (e.g., MCCH). In one example, the RNTI(s) of the one or more RNTIs may be used to identify a DCI within the configured CORESET / BWP and to point to a PDSCH that carries the multicast / broadcast control channel messages.

[0132] In some exemplary embodiments, a base station may configure periodic resources (e.g., semi-persistent scheduling (SPS) or configured scheduling (CS) resources) for downlink transmission of a multicast / broadcast control channel (e.g., MCCH). The periodic resources for transmission of the multicast / broadcast control channel may be pre-configured by RRC and activated or deactivated with DCI signaling. In some examples, the configuration parameters may indicate that the periodic resources are configured on a BWP / carrier different from the BWP / carrier on which the multicast / broadcast control channel is received.

[0133] In some examples, a RAN may provide different MBS services with different radio and QoS configuration requirements across overlapping or disjoint groups of member UEs. Using one MCCH configuration for scheduling all multicast / broadcast data channels (e.g., MTCHs) carrying MBS services with different numerologies, BWPs, latency, periodicity, and reliability requirements may be limiting and may also negatively impact power savings for UEs monitoring such MCCH transmissions. In some exemplary embodiments, MBS configuration signaling may enable configuration of multiple multicast / broadcast channels (e.g., MCCHs) with the same or different BWPs to schedule MBSs with different transmission frequencies, periodicity / timing, and reliability requirements.

[0134] In some examples, a group identifier (e.g., nG-RNTI) at the RAN level may be assigned to an MBS bundled service, for example, associated with nTMGI. This nG-RNTI may be used within the RAN for DCI signaling related to multicast / broadcast data channel (e.g., MTCH) scheduling for the associated MBS service. This nG-RNTI may be used by UEs to track and locate MTCHs associated with the target MBS service.

[0135] In some examples, the multicast / broadcast control channel (e.g., MCCH) may include a RAN level identifier, e.g., nG-RNTI, used in DCI signaling for UEs to keep track of multicast / broadcast data channel (e.g., MTCH) transmissions for that MBS bundle.

[0136] In some examples, a multicast / broadcast control channel (e.g., MCCH) may include scheduling information for one or more c. The UE may switch to a BWP / carrier if a multicast / broadcast control channel is configured to be present, decode the multicast / broadcast control channel to obtain information regarding the transmission of MBS data on the multicast / broadcast data channel, or receive the multicast / broadcast data channel data, and then switch to a default BWP as needed.

[0137] In some examples, a multicast / broadcast control channel (eg, MCCH) may be used to schedule one or more multicast / broadcast control channels (eg, MCCH) on the same or different BWPs.

[0138] In some examples, UEs that receive MBS data on a different BWP may be configured to switch back to their default / active BWP after they receive the MBS information within a configurable time period.

[0139] FIG. 20 shows an example process according to some aspects of one or more example embodiments of the present disclosure. By way of illustration, FIG. 20 illustrates a method implemented in the UE 125 and the gNB 115 for configuring or implementing a multicast broadcast message. In the example embodiment shown in FIG. 20, the UE may receive one or more messages including configuration parameters from a RAN node, illustratively the gNB 115 or the ng_eNB 120. In some examples, the one or more messages may include one or more RRC messages. In some examples, the one or more messages may include system information transmitted via one or more system information blocks (SIBs). In some examples, the gNB may transmit, and the UE may receive, one or more messages based on initiation of a random access process for on-demand system information reception. The UE may initiate a random access process by transmitting a random access preamble to the gNB for on-demand reception of system information. The gNB may transmit, and the UE may receive, one or more messages based on initiation of the random access process. In some examples, the UE may perform a service discovery process to identify one or more multicast and broadcast services that are of interest to the UE. In some examples, the gNB may transmit, and the UE may receive, one or more messages over a default BWP (e.g., the default BWP of the primary cell).

[0140] In some examples, the UE may receive one or more messages based on a transition from an RRC idle state to an RRC connected state or a transition from an RRC inactive state to an RRC connected state. The UE may transition from an RRC idle state to an RRC connected state or from an RRC inactive state to an RRC connected state based on a service discovery process that indicates that one or more multicast broadcast services are of interest to the UE.

[0141] In some examples, the configuration parameters may indicate that one or more multicast / broadcast services are associated with one or more first CORESETs. In some examples, the configuration parameters may indicate that one or more multicast broadcast services are associated with one or more first BWPs. In some examples, the configuration parameters may indicate that one or more multicast broadcast services are associated with at least one of one or more first CORESETs and first bandwidth portions (BWPs). In some examples, the one or more messages may include configuration parameters for one or more first CORESETs on one or more first BWPs. One or more multicast broadcast services may be associated with one or more first CORESETs based on receiving scheduling information for multicast broadcast control information associated with the one or more multicast broadcast services via the one or more first CORESETs. One or more multicast broadcast services may be associated with one or more first BWPs based on receiving scheduling information for multicast broadcast control information associated with the one or more multicast broadcast services via the one or more first BWPs.

[0142] The one or more messages may further include first RNTIs associated with the one or more multicast / broadcast services. Cyclic redundancy check (CRC) bits of downlink control information indicating scheduling information for the one or more downlink transport blocks may be scrambled with an RNTI of the one or more first RNTIs. The one or more transport blocks may include control information for the one or more multicast / broadcast services.

[0143] The UE may receive one or more downlink control information associated with one or more first RNTIs. In some examples, the one or more multicast broadcast services may be associated with service identifiers (e.g., TMGIs, etc.), and the one or more RNTIs may be associated with the one or more service identifiers. CRC bits of the one or more downlink control information may be scrambled with the one or more first RNTIs. The UE may receive the one or more downlink control information via one or more first CORESETs and / or one or more first BWPs. In some examples, the UE may identify that the one or more downlink control information is associated with one or more multicast broadcast services based on receiving the one or more downlink control information via one or more first CORESETs and / or one or more first BWPs. In some examples, the UE may determine that the one or more downlink control information are associated with one or more multicast broadcast services based on the one or more downlink control information being associated with one or more first RNTIs.

[0144] The UE may receive one or more transport blocks based on scheduling information indicated by one or more downlink control information. The scheduling information may indicate radio resources for reception of the one or more transport blocks. The one or more transport blocks may be associated with one or more multicast / broadcast services. The one or more transport blocks may include control information for receiving one or more traffic / data channels associated with the one or more multicast / broadcast services.

[0145] In the example embodiment shown in Figure 21, a UE may receive configuration parameters for a semi-persistent scheduling (SPS) configuration. The SPS configuration parameters may be used by the UE to identify SPS resources. The UE may identify SPS resources as SPS resources. The SPS configuration may be determined based on the configuration and based on an activation DCI indicating activation of the SPS configuration. The UE may receive an activation DCI indicating SPS configuration activation. The SPS configuration may be associated with one or more multicast broadcast services. The SPS configuration parameter may indicate that the SPS configuration is associated with one or more multicast broadcast services. In some examples, the SPS configuration parameter may include an SPS configuration identifier indicating that the SPS configuration is associated with one or more multicast broadcast services.

[0146] The wireless device may identify SPS resources based on SPS configuration parameters (e.g., in combination with an activated DCI). The wireless device may receive one or more transport blocks via the SPS resources. The one or more transport blocks may be associated with one or more multicast / broadcast services. The one or more transport blocks may include control information for receiving one or more traffic / data channels associated with the one or more multicast / broadcast services.

[0147] In some examples, one or more transport blocks associated with one or more multicast broadcast services and containing control information for the one or more multicast broadcast services may include one or more of the following information: one or more service identifiers for the one or more multicast broadcast services (e.g., one or more TMGIs or identifiers associated with one or more TMGIs or other identifiers), one or more second RNTIs for receiving downlink data associated with the one or more service identifiers, e.g., for receiving multicast broadcast service traffic channels associated with the one or more multicast broadcast services, one or more BWP identifiers of one or more BWPs for receiving the one or more multicast broadcast services, one or more numerologies for receiving the one or more multicast broadcast services (e.g., one or more BWPs), one or more quality of service requirements (e.g., latency, jitter, throughput, etc.) for the one or more multicast broadcast services; one or more periodicities (e.g., periodicity of reception of one or more multicast broadcast control information or periodicity of reception of one or more multicast broadcast traffic channels) associated with the one or more multicast broadcast services; one or more cell identifiers of one or more cells for reception of the one or more multicast broadcast services; one or more discontinuous reception (DRX) parameters for monitoring one or more Radio Network Temporary Identifiers (RNTIs) associated with the one or more multicast broadcast services (e.g., a first DRX parameter, e.g., a value of a first inactivity timer or a value of a first reception period associated with the first multicast broadcast traffic channel, and a second DRX parameter;a second inactivity timer value or a second receive period timer value associated with the second multicast broadcast traffic channel), and a neighboring cell information list indicating one or more neighboring cells for reception of one or more multicast broadcast services, e.g., neighboring cells in which one or more multicast broadcast services are available, etc.

[0148] In some examples, the UE may switch to a first BWP for reception of one or more multicast broadcast services (e.g., switch from a currently active BWP to a first BWP). The first BWP may be a BWP for which multicast broadcast services are available (e.g., a BWP for which a multicast broadcast traffic channel is transmitting). In some examples, the UE may switch to a second BWP (e.g., a previously active BWP or a default BWP) after a certain time (e.g., a configurable time) has elapsed since switching to the first BWP. The UE may start a timer upon switching to the first BWP and may switch to the second BWP upon the expiration of the timer. The configuration parameter may indicate the value of the timer.

[0149] In an embodiment, a UE may receive one or more messages including configuration parameters indicating that one or more multicast broadcast services are associated with at least one of a first control resource set (CORESET) and a first bandwidth portion (BWP), and one or more first radio network temporary identifiers (RNTIs) associated with the one or more multicast broadcast services. The UE may receive one or more downlink control information associated with the one or more first RNTIs via the first CORESET or the first BWP. The UE may receive one or more transport blocks associated with the one or more multicast broadcast services based on the one or more downlink control information. In some embodiments, the configuration parameters may include first configuration parameters for the first CORESET in the first BWP.

[0150] In an embodiment, a UE may receive semi-persistent scheduling (SPS) configuration parameters associated with one or more multicast broadcast services. The UE may receive one or more transport blocks associated with the one or more multicast broadcast services based on SPS resources associated with the SPS configuration.

[0151] In some embodiments, the configuration parameters may include a first identifier indicating that the SPS configuration is associated with one or more multicast / broadcast services. In some embodiments, the UE may receive downlink control information indicating activation of the SPS configuration.

[0152] In some embodiments, one or more transport blocks may include control information associated with one or more multicast broadcast services. In some embodiments, the control information includes at least one of the following: one or more service identifiers for the one or more multicast broadcast services, one or more second RNTIs for receiving downlink data associated with the one or more service identifiers, one or more BWP identifiers of one or more BWPs for reception of the one or more multicast broadcast services, one or more numerologies for reception of the one or more multicast broadcast services, one or more quality of service requirements for the one or more multicast broadcast services, one or more periodicities associated with the one or more multicast broadcast services, one or more cell identifiers of one or more cells for reception of the one or more multicast broadcast services, one or more discontinuous reception (DRX) parameters for monitoring one or more radio network temporary identifiers (RNTIs) associated with the one or more multicast broadcast services, and a neighbor cell information list indicating one or more neighboring cells for reception of the one or more multicast broadcast services. In some embodiments, the one or more DRX parameters may include a first DRX parameter associated with a first multicast broadcast traffic channel and a second DRX parameter associated with a second multicast broadcast traffic channel. In some embodiments, the first DRX parameter may be one or more of a value of a first inactivity timer and a value of a first receive period timer. The second DRX parameter may be a value of a second inactivity timer. The value of the second receive period timer may be one or more of the value of the rate timer and the value of the second receive period timer.

[0153] In some embodiments, the control information may be associated with a Multicast Broadcast Control Logical Channel.

[0154] In some embodiments, one or more BWPs are associated with one or more numerologies, and one or more multicast broadcast services are associated with one or more numerologies.

[0155] In some embodiments, the configuration parameters may further indicate one or more first service identifiers associated with the one or more multicast / broadcast services and one or more first RNTIs associated with the first service identifiers.

[0156] In some embodiments, the one or more messages may include one or more radio resource control (RRC) messages.

[0157] In some embodiments, the one or more messages may include a system information block (SIB) associated with the multicast broadcast service.

[0158] In some embodiments, receiving the one or more messages may be based on a random access procedure for on-demand system information reception.

[0159] In some embodiments, receiving the one or more messages may be based on a service discovery process that indicates one or more multicast / broadcast services that are of interest to the UE.

[0160] In some embodiments, the UE may receive, during a service discovery process, one or more service identifiers for one or more multicast / broadcast services that are of interest to the UE.

[0161] In some embodiments, receiving the one or more messages may be done via a default BWP.

[0162] In some embodiments, receiving the one or more messages may occur via a default BWP of the primary cell.

[0163] In some embodiments, receiving the one or more messages may be based on a transition from an RRC idle state to an RRC connected state or a transition from an RRC inactive state to an RRC connected state.

[0164] In some embodiments, the transition from an RRC idle state to an RRC connected state or from an RRC inactive state to an RRC connected state may be based on a service discovery process that indicates one or more multicast / broadcast services that are of interest to the UE.

[0165] In some embodiments, a UE may switch to a first BWP to receive one or more broadcast-multicast services, and the UE may switch to a second BWP after a first time has elapsed since switching to the first BWP.

[0166] In some embodiments, the second BWP may be a default BWP.

[0167] In some embodiments, the second BWP may be the active BWP before switching to the first BWP.

[0168] In some embodiments, the UE may start a timer upon switching to the first BWP.

[0169] In some embodiments, the switch to the second BWP may be based on a timer expiring.

[0170] The example blocks and modules described in connection with various example embodiments in this disclosure may be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a 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 herein. Examples of a general-purpose processor include, but are not limited to, a microprocessor, any conventional processor, controller, microcontroller, or state machine. In some examples, a processor may be implemented using a combination of devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors using a DSP core, or any other such configuration).

[0171] The functions described in this disclosure may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. Instructions or code may be stored on or transmitted from a computer-readable medium for execution of these functions. Other examples of implementation of the functions disclosed herein are also within the scope of this disclosure. Performance of the functions may be via physically co-located elements or distributed elements (e.g., at various locations), including distribution such that portions of the functions are executed at different physical locations.

[0172] Computer-readable media include, but are not limited to, non-transitory computer storage media. Non-transitory storage media can be accessed by a general-purpose or special-purpose computer. Examples of non-transitory storage media include, but are not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices. Non-transitory media can be used to carry or store desired program code means (e.g., instructions and / or data structures) and can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. In some examples, software / program code can be transmitted from a remote resource (e.g., a website, a server, etc.) using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave. In such examples, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of media. Combinations of the above examples are also included within the scope of computer-readable media.

[0173] As used in this disclosure, the use of the term "or" in a list of items indicates an inclusive list. The list of items may include "at least one of" or "one or more of." Phrases such as "a plurality of" and "multiple" may be used in combination. For example, a list of at least one of A, B, or C includes A or B or C or AB (i.e., A and B) or AC or BC or ABC (i.e., A, B, and C). Also, as used in this disclosure, when a list of conditions is used in conjunction with the phrase "based on," it should be understood to be "based at least in part" on that set of conditions, rather than "based only on" those conditions. For example, a result described as "based on condition A" could also be based on both condition A and condition B without departing from the scope of this disclosure.

[0174] As used herein, the terms "comprise," "include," or "contain" are used interchangeably, may have the same meaning, and are intended to be inclusive and open-ended. The term "comprise," "include," or "contain" may be used in conjunction with a list of elements to indicate that at least all of the elements listed in the list are present, but that other elements not in the list may also be present. For example, if A contains B and C, then both {B, C} and {B, C, D} are within the scope of A.

[0175] The present disclosure describes exemplary configurations in connection with the accompanying drawings, which do not necessarily represent all possible implementations or all configurations falling within the scope of the present disclosure. The term "exemplary" should not be interpreted as "preferred" or "advantageous over other examples," but rather as "an example, instance, or example." Upon reading this disclosure, including the description of the embodiments and the drawings, those skilled in the art will recognize that the technology disclosed herein may be implemented using alternative embodiments. Those skilled in the art will recognize that specific features of these embodiments, or of the embodiments described herein, may be combined to arrive at yet another embodiment for practicing the technology described in the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0176] 1. Radio communication methods: The user equipment (UE) One or more multicast broadcast services The first control resource set (CORESET) and First Bandwidth Part (BWP) a configuration parameter indicating that the device is associated with at least one of: one or more first Radio Network Temporary Identifiers (RNTIs) associated with one or more multicast / broadcast services; receiving one or more messages including: receiving, by the UE, downlink control information associated with one or more first RNTIs; receiving one or more transport blocks associated with one or more multicast / broadcast services based on the downlink control information; Includes:

[0177] Clause 2. In the wireless communication method of clause 1, the configuration parameters include first configuration parameters of a first CORESET or a first BWP.

[0178] Clause 3. The wireless communication method of clause 1, wherein one or more transport blocks include control information associated with one or more multicast / broadcast services.

[0179] Clause 4. In the wireless communication method of clause 1, the configuration parameters are: one or more first service identifiers associated with one or more multicast / broadcast services; one or more first RNTIs associated with the first service identifier; The data further includes data indicating:

[0180] Clause 5. The wireless communication method of clause 1, wherein the one or more messages include one or more radio resource control (RRC) messages.

[0181] Clause 6. The wireless communication method of clause 1, wherein the one or more messages include a system information block (SIB) associated with a multicast broadcast service.

[0182] Clause 7. In the wireless communication method of clause 1, receiving one or more messages is based on a random access procedure for receiving on-demand system information.

[0183] Clause 8. The wireless communication method of clause 1, wherein receiving one or more messages is based on a service discovery process that identifies one or more of the multicast / broadcast services.

[0184] Clause 9. The wireless communication method of clause 8 further comprises receiving, during the service discovery process, one or more service identifiers of one or more multicast / broadcast services.

[0185] Clause 10. The wireless communication method of clause 1, wherein receiving one or more messages occurs via a default BWP.

[0186] Clause 11. In the wireless communication method of clause 10, receiving one or more messages includes receiving one or more messages via a default BWP of the primary cell.

[0187] Clause 12. In the wireless communication method of clause 1, receiving one or more messages includes receiving one or more messages based on at least one of a transition from an RRC idle state to an RRC connected state or a transition from an RRC inactive state to an RRC connected state.

[0188] Clause 13. In the wireless communication method of clause 12, the transition from an RRC idle state to an RRC connected state or from an RRC inactive state to an RRC connected state is based on a service discovery process that indicates one or more multicast / broadcast services that are of interest to the UE.

[0189] 14. The wireless communication method of paragraph 1 is switching to a first BWP to receive one or more broadcast-multicast services; switching to a second BWP after a first time has elapsed since switching to the first BWP; Further includes:

[0190] Clause 15. In the wireless communication method of clause 14, the second BWP is a default BWP.

[0191] Clause 16: In the wireless communication method of clause 14, the second BWP is switched to the first BWP. This is the active BWP before the

[0192] Clause 17: The wireless communication method of clause 14 further includes starting a timer based on switching to the first BWP.

[0193] Clause 18. In the wireless communication method of clause 17, the step of switching to the second BWP is based on a timer expiring.

[0194] Section 19: Wireless communication methods are receiving configuration parameters for a semi-persistent scheduling (SPS) configuration associated with one or more multicast / broadcast services; receiving one or more transport blocks associated with one or more multicast / broadcast services based on SPS resources associated with the SPS configuration; Includes:

[0195] Clause 20: In the wireless communication method of clause 19, the configuration parameters include a first identifier indicating that the SPS configuration is associated with one or more multicast / broadcast services.

[0196] Clause 21: The wireless communication method of clause 19 further includes receiving downlink control information indicating activation of an SPS configuration.

[0197] Clause 22: The wireless communication method of clause 19, wherein one or more transport blocks include control information associated with one or more multicast / broadcast services.

[0198] Clause 23. The wireless communication method of clause 22, wherein the control information is associated with one or more multicast broadcast control logical channels.

[0199] Clause 24. In the wireless communication method of clause 22, the control information comprises: one or more service identifiers for one or more multicast / broadcast services; one or more second RNTIs for receiving downlink data associated with the one or more service identifiers; one or more numerologies for receiving one or more multicast broadcast services; one or more quality of service requirements for one or more multicast / broadcast services; one or more periodicities associated with one or more multicast / broadcast services; one or more cell identifiers of one or more cells for receiving one or more multicast broadcast services; and a neighboring cell information list indicating one or more neighboring cells for receiving one or more multicast broadcast services; At least one of the following is shown.

[0200] Clause 25. The wireless communication method of clause 22, wherein the control information indicates one or more discontinuous reception (DRX) parameters for monitoring one or more radio network temporary identifiers (RNTIs) associated with one or more multicast / broadcast services. vinegar.

[0201] Clause 26 In the wireless communication method of clause 25, the one or more DRX parameters include a first DRX parameter associated with a first multicast broadcast traffic channel and a second DRX parameter associated with a second multicast broadcast traffic channel.

[0202] Clause 27 In the wireless communication method of clause 26, the first DRX parameter is one or more of a value of a first inactivity timer and a value of a first reception period timer, and the second DRX parameter is one or more of a value of a second inactivity timer and a value of a second reception period timer.

[0203] Clause 28. In the wireless communication method of clause 22, the control information indicates one or more BWP identifiers of one or more BWPs for receiving one or more multicast broadcast services.

[0204] Clause 29. In the wireless communication method of clause 22, the control information indicates one or more BWP identifiers of one or more BWPs for receiving one or more multicast broadcast services.

[0205] Clause 30. In the wireless communication method of clause 29, one or more BWPs are associated with one or more numerologies, and one or more multicast broadcast services are associated with one or more numerologies.

[0206] Article 31 - Equipment for use in radio communication an antenna used in transmitting electromagnetic signals; a memory for holding computer readable code; Executing the computer readable code causes the device to: One or more multicast broadcast services The first control resource set (CORESET) and First Bandwidth Part (BWP) a configuration parameter indicating that the device is associated with at least one of: one or more first Radio Network Temporary Identifiers (RNTIs) associated with one or more multicast / broadcast services; receiving one or more messages including receiving downlink control information associated with one or more first RNTIs; a processor for causing reception of one or more transport blocks associated with one or more multicast / broadcast services based on the downlink control information; Includes:

[0207] Clause 32. In the apparatus of clause 31, the configuration parameters include a first configuration parameter of the first CORESET or the first BWP.

[0208] Clause 33. The apparatus of clause 31, wherein one or more transport blocks include control information associated with one or more multicast / broadcast services.

[0209] Clause 34. In the device of clause 31, the configuration parameters are: one or more first service identifiers associated with one or more multicast / broadcast services; one or more first RNTIs associated with the first service identifier; The data further includes data indicating:

[0210] Clause 35. In the apparatus of clause 31, the one or more messages include one or more radio resource control (RRC) messages.

[0211] Clause 36. The apparatus of clause 31, wherein the one or more messages include a system information block (SIB) associated with a multicast broadcast service.

[0212] Clause 37. In the apparatus of clause 31, receiving the one or more messages is based on a random access procedure for receiving on-demand system information.

[0213] Clause 38. In the apparatus of clause 31, receiving the one or more messages is based on a service discovery process that identifies one or more of the multicast broadcast services.

[0214] Clause 39. The apparatus of clause 38 further includes receiving, during the service discovery process, one or more service identifiers of the one or more multicast / broadcast services.

[0215] Section 40: Wireless communication methods are The Radio Access Node (RAN) One or more multicast broadcast services The first control resource set (CORESET) and First Bandwidth Part (BWP) a configuration parameter indicating that the device is associated with at least one of: one or more first Radio Network Temporary Identifiers (RNTIs) associated with one or more multicast / broadcast services; sending one or more messages including: transmitting, by the RAN, downlink control information associated with the one or more first RNTIs; transmitting one or more transport blocks associated with one or more multicast / broadcast services based on the downlink control information; Includes:

[0216] Clause 41. In the wireless communication method of clause 40, the configuration parameters include first configuration parameters of the first CORESET or the first BWP.

[0217] Clause 42: The wireless communication method of clause 40, wherein one or more transport blocks include control information associated with one or more multicast / broadcast services.

[0218] Clause 43. In the wireless communication method of clause 40, the configuration parameters are: one or more first service identifiers associated with one or more multicast / broadcast services; one or more first RNTIs associated with the first service identifier; The data further includes data indicating:

[0219] Clause 44. In the wireless communication method of clause 40, the one or more messages include one or more radio resource control (RRC) messages.

[0220] Clause 45: In the wireless communication method of clause 40, the one or more messages include a system information block (SIB) associated with a multicast broadcast service.

[0221] Clause 46. The wireless communication method of clause 40, wherein the step of transmitting one or more messages is based on a random access procedure for receiving on-demand system information.

[0222] Clause 47. The wireless communication method of clause 40, wherein the step of transmitting one or more messages is based on a service discovery process that identifies one or more multicast / broadcast services.

[0223] Clause 48: The wireless communication method of clause 47 further comprises transmitting, during the service discovery process, one or more service identifiers of the one or more multicast / broadcast services.

[0224] Clause 49. The wireless communication method of clause 40, wherein the step of transmitting one or more messages is performed via a default BWP.

[0225] Clause 50. In the wireless communication method of clause 49, transmitting one or more messages includes transmitting the one or more messages over a default BWP of the primary cell.

[0226] Clause 51. In the wireless communication method of clause 40, the step of transmitting one or more messages includes the step of transmitting one or more messages based on at least one of a transition from an RRC idle state to an RRC connected state or a transition from an RRC inactive state to an RRC connected state.

[0227] Clause 52. In the wireless communication method of clause 51, the transition from an RRC idle state to an RRC connected state or from an RRC inactive state to an RRC connected state is based on a service discovery process that indicates one or more multicast / broadcast services for the UE.

[0228] Clause 53: The wireless communication method of clause 40 is switching to a first BWP for transmitting one or more broadcast-multicast services; switching to a second BWP after a first time has elapsed since switching to the first BWP; Further includes:

[0229] Clause 54. In the wireless communication method of clause 53, the second BWP is a default BWP.

[0230] Clause 55. In the wireless communication method of clause 53, the second BWP is the active BWP before switching to the first BWP.

[0231] Clause 56: The wireless communication method of clause 53 further includes starting a timer based on switching to the first BWP.

[0232] Clause 57. The wireless communication method of clause 55, wherein the step of switching to the second BWP is based on a timer expiring.

[0233] Section 58: Wireless communication methods are transmitting configuration parameters of a semi-persistent scheduling (SPS) configuration associated with one or more multicast / broadcast services; transmitting one or more transport blocks associated with one or more multicast / broadcast services based on SPS resources associated with the SPS configuration; Includes:

[0234] Clause 59: The wireless communication method of clause 58, wherein the configuration parameters include a first identifier indicating that the SPS configuration is associated with one or more multicast / broadcast services.

[0235] Clause 60: The wireless communication method of clause 58 further includes transmitting downlink control information indicating activation of the SPS configuration.

[0236] Clause 61: In the wireless communication method of clause 58, one or more transport blocks include control information associated with one or more multicast / broadcast services.

[0237] Clause 62. The wireless communication method of clause 61, wherein the control information is associated with one or more multicast broadcast control logical channels.

[0238] Clause 63. In the wireless communication method of clause 61, the control information comprises: one or more service identifiers for one or more multicast / broadcast services; one or more second RNTIs for receiving downlink data associated with the one or more service identifiers; one or more numerologies for receiving one or more multicast broadcast services; one or more quality of service requirements for one or more multicast / broadcast services; one or more periodicities associated with one or more multicast / broadcast services; one or more cell identifiers of one or more cells for receiving one or more multicast broadcast services; and a neighboring cell information list indicating one or more neighboring cells for receiving one or more multicast broadcast services; At least one of the following is shown.

[0239] Clause 64: In the wireless communication method of clause 61, the control information indicates one or more discontinuous reception (DRX) parameters for monitoring one or more radio network temporary identifiers (RNTIs) associated with one or more multicast broadcast services.

[0240] Clause 65: In the wireless communication method of clause 64, the one or more DRX parameters include a first DRX parameter associated with a first multicast broadcast traffic channel and a second DRX parameter associated with a second multicast broadcast traffic channel.

[0241] Clause 66 In the wireless communication method of clause 65, the first DRX parameter is one or more of a value of a first inactivity timer and a value of a first reception period timer, and the second DRX parameter is one or more of a value of a second inactivity timer and a value of a second reception period timer.

[0242] Clause 67. In the wireless communication method of clause 61, the control information indicates one or more BWP identifiers of one or more BWPs for receiving one or more multicast broadcast services.

[0243] Clause 68. In the wireless communication method of clause 61, the control information indicates one or more BWP identifiers of one or more BWPs for receiving one or more multicast broadcast services.

[0244] Clause 69. In the wireless communication method of clause 68, one or more BWPs are associated with one or more numerologies, and one or more multicast broadcast services are associated with one or more numerologies.

[0245] Article 70: Equipment used in wireless communication an antenna used in transmitting electromagnetic signals; a memory for holding computer readable code; Executing the computer readable code causes the device to: One or more multicast broadcast services The first control resource set (CORESET) and First Bandwidth Part (BWP) a configuration parameter indicating that the device is associated with at least one of: one or more first Radio Network Temporary Identifiers (RNTIs) associated with one or more multicast / broadcast services; sending one or more messages including transmitting downlink control information associated with the one or more first RNTIs; transmitting one or more transport blocks associated with the one or more multicast / broadcast services based on the downlink control information; a processor; Includes:

[0246] Clause 71. In the apparatus of clause 70, the configuration parameters include a first configuration parameter of the first CORESET or the first BWP.

[0247] Clause 72. The apparatus of clause 70, wherein one or more transport blocks include control information associated with one or more multicast / broadcast services.

[0248] Clause 73. In the device of clause 70, the configuration parameters are: one or more first service identifiers associated with one or more multicast / broadcast services; one or more first RNTIs associated with the first service identifier; The data further includes data indicating:

[0249] Clause 74. In the apparatus of clause 70, the one or more messages include one or more radio resource control (RRC) messages.

[0250] 75. In the apparatus of paragraph 70, one or more messages are transmitted via a multicast broadcast. Contains a System Information Block (SIB) associated with the broadcast service.

[0251] Clause 76. In the apparatus of clause 70, transmitting the one or more messages is based on a random access procedure for receiving on-demand system information.

[0252] Clause 77. In the apparatus of clause 70, transmitting the one or more messages is based on a service discovery process that identifies one or more of the multicast / broadcast services.

[0253] Clause 78. The apparatus of clause 77, wherein the apparatus is further operative to transmit one or more service identifiers of the one or more multicast / broadcast services during the service discovery process.

[0254] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 073,732, entitled "SYSTEM AND METHOD FOR MAINTAINING MULTICAST BROADCAST SERVICE," filed September 2, 2020. U.S. Provisional Patent Application No. 63 / 073,732 is incorporated herein by reference.

Claims

1. 1. A wireless communication method performed by a user equipment (UE), comprising: receiving semi-persistent scheduling (SPS) configuration parameters associated with one or more multicast / broadcast services and configured by a radio resource control (RRC) per bandwidth portion (BWP); receiving a downlink control signal indicating activation of the SPS-based assignment; receiving data associated with the one or more multicast / broadcast services based on the assignments activated by the downlink control signal; Multiple assignments may be active simultaneously within one bandwidth portion (BWP); Wireless communication method. receiving a downlink control signal indicating deactivation of the assignment based on the SPS; based on a downlink control signal indicating deactivation of the assignment, ceasing to receive data associated with the one or more multicast / broadcast services; The wireless communication method of claim 1 , comprising:

3. 1. An apparatus for use in wireless communication, comprising: an antenna for use in transmitting electromagnetic signals, a memory for holding computer readable code, and a processor; The processor: Executing the computer readable code, the device receiving semi-persistent scheduling (SPS) configuration parameters associated with one or more multicast / broadcast services and configured by a radio resource control (RRC) on a per bandwidth portion (BWP) basis; receiving a downlink control signal indicating activation of the SPS-based assignment; receiving data associated with one or more multicast / broadcast services based on the assignments activated by the downlink control signal; Multiple assignments may be active simultaneously within one bandwidth portion (BWP); Device.

4. 1. A wireless communication method performed by a radio access node (RAN), comprising: transmitting semi-persistent scheduling (SPS) configuration parameters associated with one or more multicast / broadcast services and configured by a radio resource control (RRC) per bandwidth portion (BWP); transmitting a downlink control signal indicating activation of the SPS-based assignment; transmitting data associated with one or more multicast / broadcast services based on the assignments activated by the downlink control signal; Including, Within one bandwidth portion (BWP), multiple assignments can be active at the same time. Wireless communication method.

5. 1. An apparatus for use in wireless communication, comprising: an antenna for use in transmitting electromagnetic signals, a memory for holding computer readable code, and a processor; The processor: Executing the computer readable code, the device transmitting semi-persistent scheduling (SPS) configuration parameters associated with one or more multicast / broadcast services and configured by a radio resource control (RRC) per bandwidth portion (BWP); transmitting downlink control signals indicating activation of the SPS-based assignment; transmitting data associated with one or more multicast / broadcast services based on the assignments activated by the downlink control signal; Within one bandwidth portion (BWP), multiple assignments can be active at the same time. Device.

Images