Multicast and broadcast configuration signaling

Abstract

A system, method, and apparatus for mobile communications are provided. A user equipment (UE) receives one or more messages including configuration parameters indicating that one or more multicast broadcast services are descriptively associated with a first control resource set (CORESET) and a first portion bandwidth (BWP). The message also includes one or more first radio network temporary identifiers (RNTIs) associated with the one or more multicast broadcast services. The UE then receives downlink control information associated with the one or more first RNTIs via the first CORESET or the first BWP. The UE then receives one or more transport blocks associated with the one or more multicast broadcast services.

Description

Technical Field

[0001] This 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, a computing device can request / transmit data to another computing device via a communication network. More specifically, computing devices can use wireless communication networks to exchange information or establish communication channels.

[0003] Wireless communication networks can include a variety of devices that include or connect to components for accessing the wireless communication network. Such devices can utilize the wireless communication network to facilitate interaction with other devices capable of accessing the wireless communication network, or to facilitate interaction with devices utilizing other communication networks. Summary of the Invention

[0004] One embodiment of the present invention is a wireless communication method. The wireless communication method includes: a user equipment (UE) receiving one or more messages, the 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); a first bandwidth part (BWP); and one or more first radio network temporary identifiers (RNTIs) associated with the one or more multicast broadcast services; the UE receiving downlink control information associated with the one or more first RNTIs; and based on the downlink control information, receiving one or more transport blocks associated with the one or more multicast broadcast services. Attached Figure Description

[0005] [ Figure 1 ] Figure 1 Examples of mobile communication systems are shown, illustrating some aspects of a mobile communication system according to one or more exemplary embodiments of this disclosure.

[0006] [Figure 2] Figure 2A and Figure 2B Examples of radio protocol stacks for the user plane and control plane, respectively, are shown according to one or more exemplary embodiments of this disclosure.

[0007] [Figure 3] Figure 3A , Figure 3B and Figure 3CExemplary mappings between logical channels and transport channels in downlink, uplink, and sidelink according to one or more exemplary embodiments of this disclosure are shown respectively.

[0008] [Figure 4] Figure 4A , Figure 4B and Figure 4C Exemplary mappings between transport channels and physical channels in downlink, uplink, and sidelink according to one or more exemplary embodiments of this disclosure are shown respectively.

[0009] [Figure 5] Figure 5A , Figure 5B , Figure 5C and Figure 5D Examples of radio protocol stacks for NR-side link communication are shown, representing some aspects of one or more exemplary embodiments of this disclosure.

[0010] [ Figure 6 ] Figure 6 Example physical signals in the downlink, uplink, and sidelink of some aspects according to one or more exemplary embodiments of this disclosure are shown.

[0011] [ Figure 7 ] Figure 7 Examples of Radio Resource Control (RRC) states and transitions between different RRC states are shown, representing some aspects of one or more exemplary embodiments of this disclosure.

[0012] [ Figure 8 ] Figure 8 Example frame structures and physical resources are shown, representing some aspects of one or more exemplary embodiments according to this disclosure.

[0013] [ Figure 9 ] Figure 9 Exemplary member carrier configurations in different carrier aggregation scenarios are shown in accordance with one or more exemplary embodiments of this disclosure.

[0014] [ Figure 10 ] Figure 10 Example portions of bandwidth configuration and switching are shown, representing some aspects of one or more exemplary embodiments according to this disclosure.

[0015] [ Figure 11 ] Figure 11 Example four-step contention-based random access procedures and contention-free random access procedures are shown, illustrating some aspects of one or more exemplary embodiments of this disclosure.

[0016] [ Figure 12 ] Figure 12Examples of two-step contention-based random access procedures and contention-free random access procedures are shown, illustrating some aspects of one or more exemplary embodiments of the present disclosure.

[0017] [ Figure 13 ] Figure 13 Example time and frequency structures of a Synchronization Signal and PBCH Block (SSB) are shown, representing some aspects of one or more exemplary embodiments of the present disclosure.

[0018] [ Figure 14 ] Figure 14 Example SSB burst transmissions are shown, illustrating some aspects of one or more exemplary embodiments according to this disclosure.

[0019] [ Figure 15 ] Figure 15 Example components of user equipment and base stations for transmission and / or reception are shown, representing some aspects of one or more exemplary embodiments of this disclosure.

[0020] [ Figure 16 ] Figure 16 An example multicast broadcast service (MBS) interest indication process is shown, illustrating some aspects of one or more exemplary embodiments according to this disclosure.

[0021] [ Figure 17 ] Figure 17 Example MBS control signaling and traffic channel transmissions are shown, illustrating some aspects of one or more exemplary embodiments according to this disclosure.

[0022] [ Figure 18 ] Figure 18 An example process in MBS transmission is shown, illustrating some aspects of one or more exemplary embodiments according to this disclosure.

[0023] [ Figure 19 ] Figure 19 Example MBS control signaling and traffic channel transmissions are shown, illustrating some aspects of one or more exemplary embodiments according to this disclosure.

[0024] [ Figure 20 ] Figure 20 Example processes are shown that illustrate some aspects of one or more exemplary embodiments according to this disclosure.

[0025] [ Figure 21 ] Figure 21 Example processes are shown that illustrate some aspects of one or more exemplary embodiments according to this disclosure. Detailed Implementation

[0026] Figure 1 Examples of mobile communication systems 100 according to one or more exemplary embodiments of the present disclosure are shown. 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 (DMO), a Multiple System Operator (MSO), or an Internet of Things (IoT) network operator, and may provide services such as voice, data (e.g., wireless Internet access), messaging, vehicle communication services such as Vehicle to Everything (V2X) communication services, security services, mission-critical services, and services in residential, commercial, or industrial environments such as IoT and Industrial IoT (IIOT).

[0027] Mobile communication system 100 can support various types of applications with different requirements in terms of latency, reliability, and throughput. Examples of supported applications include enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC). eMBB can support stable connections with high peak data rates as well as medium rates for cell-edge users. URLLC can support applications with stringent requirements for latency and reliability and medium requirements for data rates. Example mMTC applications include networks of numerous IoT devices that are only occasionally active and send small data payloads.

[0028] The mobile communication system 100 may include a radio access network (RAN) portion and a core network portion. Figure 1The examples shown illustrate a Next-Generation RAN (NG-RAN) 105 and a 5G Core Network (5GC) 110 as examples of RAN and core network, respectively. Other examples of RAN and core network may be implemented without departing from the scope of this disclosure. Other examples of RAN include Evolved Universal Terrestrial Radio Access Network (EUTRAN), Universal Terrestrial Radio Access Network (UTRAN), etc. Other examples of core network include Evolved Packet Core (EPC), UMTS Core Network (UCN), etc. The RAN implements Radio Access Technology (RAT) and resides between User Equipment (UE) 125 (e.g., UE 125A to UE 125E) and the core network. Examples of 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 of the example mobile communication system 100 could be NR. The core network resides 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, establishing bearers and applications with different Quality of Service (QoS) levels. The functional layer between UE 125 and the RAN (e.g., NG-RAN 105) can be referred to as the Access Stratum (AS), and the functional layer between UE 125 and the core network (e.g., 5GC 110) can be referred to as the Non-access Stratum (NAS).

[0029] UE 125 may include wireless transmission and reception components for communicating with one or more nodes, one or more relay nodes, or one or more other UEs in the RAN. Examples of UE 125 include, but are not limited to, smartphones, tablets, laptops, computers, wireless transmission and / or reception units in vehicles, V2X or vehicle-to-vehicle (V2V) devices, wireless sensors, IoT devices, IIoT devices, etc. Other names may be used for UE 125, such as Mobile Station (MS), Terminal Equipment, Terminal Node, Client Equipment, Mobile Equipment, etc. Furthermore, UE 125 may also include components or sub-components integrated into other devices such as vehicles to provide wireless communication capabilities with nodes in the RAN as described herein. In addition to wireless communication, such other devices may also have other functions or multiple functions.

[0030] The RAN may include nodes (e.g., base stations) for communicating with the UE. For example, the NG-RAN 105 of mobile communication system 100 may include nodes for communicating with the UE 125. Depending on the RAT used by the RAN, different names may be used for the RAN nodes. In a RAN using the UMTS RAT, the RAN node may be referred to as Node B (NB). In a RAN using the LTE / EUTRA RAT, the RAN node may be referred to as an evolved Node B (eNB). Figure 1In the illustrative example of the mobile communication system 100, the nodes of NG-RAN 105 can be next-generation node B (gNB) 115 (e.g., gNB 115A, gNB 115B) or next-generation evolved node B (ng-eNB) 120 (e.g., ng-eNB 120A, ng-eNB 120B). In this specification, the terms base station, RAN node, gNB, and ng-eNB are used interchangeably. gNB 115 can provide NR user plane and control plane protocol terminals to UE 125. NG-eNB 120 can provide E-UTRA user plane and control plane protocol terminals to UE 125. The interface between gNB 115 and UE 125 or between ng-eNB 120 and UE 125 can be referred to as the Uu interface. The Uu interface can be established together with the user plane protocol stack and the 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 can 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) can be referred to as the uplink.

[0031] gNB 115 and ng-eNB 120 can interconnect via the Xn interface. The Xn interface can 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 can be built on Internet Protocol (IP) transport and can use the General Packet Radio Service (GPRS) Tunneling Protocol (GTP) over User Datagram Protocol (UDP) / IP to carry User Plane Protocol Data Units (PDUs). Xn-U can provide non-guaranteed delivery of User Plane PDUs and can 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 can be referred to as XnAP (Xn Application Protocol). The SCTP layer can provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission can be used to deliver signaling PDUs. The Xn-C interface can support Xn interface management, UE mobility management including context transmission and RAN paging, and dual connectivity.

[0032] The gNB 115 and ng-eNB 120 can also connect to the 5GC 110 via the NG interface. More specifically, they connect to the Access and Mobility Management Function (AMF) 130 (e.g., AMF 130A, AMF 130B) of the 5GC 110 via the NG-C interface, and to the User Plane Function (UPF) 135 (e.g., UPF 135A, UPF 135B) of the 5GC 110 via the NG-U interface. The transport network layer of the NG-U interface can be built on IP transport and can use the GTP protocol over UDP / IP to carry user plane PDUs between the NG-RAN node (e.g., gNB115 or ng-eNB 120) and the UPF 135. NG-U can provide non-guaranteed delivery of user plane PDUs between the NG-RAN node and the UPF. The transport network layer of the NG-C interface can be built on IP transport. To ensure reliable transmission of signaling messages, SCTP can be added on top of IP. The application layer signaling protocol can be called NGAP (NG Application Protocol). The SCTP layer provides guaranteed delivery of application layer messages. During transmission, IP layer point-to-point transmission can be used to deliver signaling PDUs. The NG-C interface can provide the following functions: NG interface management; UE context management; UE mobility management; NAS message transmission; paging; PDU session management; configuration delivery; and warning message transmission.

[0033] The gNB 115 or ng-eNB 120 can host one or more of the following functions: radio resource management functions, such as radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to the UE in the uplink and downlink (e.g., scheduling); IP and Ethernet header compression, encryption, and integrity protection of data; selection of the AMF at the UE's attachment device when it can be determined from information provided by the UE that there is no route to the AMF; routing user plane data to one or more UPFs; routing control plane information to the AMF; connection establishment and release; scheduling and transmission of paging messages; scheduling and transmission of system broadcast information (e.g., originating from the AMF); mobility and scheduling measurement and measurement report configuration; transport layer packet marking in the uplink; session management; network slicing support; QoS flow management and mapping to data radio bearers; support for UEs in RRC inactive state; NAS message distribution function; radio access network sharing; dual connectivity; tight interoperability between NR and E-UTRA; and maintaining the 5G system for user plane (5G System, 5GS) Cellular IoT (CIoT) optimized security and radio configuration.

[0034] The AMF 130 can host one or more of the following functions: NAS signaling 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 retransmission); registration area management; support for intra-system and inter-system mobility; access authentication; access authorization including checking roaming rights; mobility management control (subscription and policy); network slicing support; Session Management Function (SMF) selection; and selection of 5GS CIoT optimization.

[0035] UPF 135 can host one or more of the following functions: anchor points for intra / inter-RAT mobility (where applicable); external PDU session points for interconnection with data networks; packet routing and forwarding; user plane portion of packet inspection and policy rule enforcement; traffic usage reporting; uplink classifiers to support routing traffic flows to data networks; branch points to support multihomed PDU sessions; QoS processing for user plane, such as packet filtering, gating, UL / DL rate enforcement; uplink traffic authentication (Service Data Flow (SDF) to QoS flow mapping); downlink packet buffering and downlink data notification triggering.

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

[0037] PC5-S signaling can be used for unicast link establishment with direct communication request / accept messages. The UE can, for example, self-assign its source stratum 2 ID for the PC5 unicast link based on the V2X service type. During the unicast link establishment process, the UE can send its source stratum 2 ID for the PC5 unicast link to a peer UE (e.g., a UE that has already received the destination ID from the upper layer). A pair of source stratum 2 IDs and destination stratum 2 IDs can uniquely identify the unicast link. The receiving UE can verify that the destination ID belongs to it and can accept the unicast link establishment request from the source UE. During the PC5 unicast link establishment process, the PC5-RRC procedure on the access layer can be invoked for UE-sidelink context establishment and AS layer configuration, capability exchange, etc. PC5-RRC signaling enables the exchange of UE capabilities and AS layer configurations, such as sidelink radio bearer configuration, between a pair of UEs that have established a PC5 unicast link.

[0038] NR sidelink communication can support one of three transmission modes (e.g., unicast, multicast, and broadcast) for a pair of source layer 2IDs and destination layer 2IDs in the AS. Unicast transmission mode is characterized by: support for a PC5-RRC connection between the peer UEs in the pair; transmission and reception of control information and user traffic between peer UEs in the sidelink; support for sidelink HARQ feedback; support for sidelink transmission power control; support for RLC Acknowledged Mode (AM); and detection of radio link failures in the PC5-RRC connection. Multicast transmission is characterized by: transmission and reception of user traffic between a group of UEs in the sidelink; and support for sidelink HARQ feedback. Broadcast transmission is characterized by: transmission and reception of user traffic between UEs in the sidelink.

[0039] Source Layer 2ID, Destination Layer 2ID, and PC5 Link Identifier can be used in NR-side walkway communication. The Source Layer 2ID identifies the sender of data in NR-side walkway communication. The Source Layer 2ID can be 24 bits long and can be split into two bit strings at the Medium Access Control (MAC) layer: one bit string can be the LSB portion (8 bits) of the Source Layer 2ID and is forwarded to the sender's physical layer. This identifies the source of the expected data in the walkway control information and can be used to filter packets at the receiver's physical layer. The second bit string can be the MSB portion (16 bits) of the Source Layer 2ID and can be carried within the Medium Access Control (MAC) header. This can be used to filter packets at the receiver's MAC layer. The Destination Layer 2ID identifies the destination of data in NR-side walkway communication. For NR-side walkway communication, the Destination Layer 2ID can be 24 bits long and can be split into two bit strings at the MAC layer: one bit string can be the LSB portion (16 bits) of the Destination Layer 2ID and is forwarded to the sender's physical layer. This can identify the target of the intended data in the sidelink control information and can be used to filter packets at the physical layer of the receiver. The second bit string can be the MSB portion (8 bits) of the destination layer 2ID and can be carried in the MAC header. This can be used to filter packets at the MAC layer of the receiver. The PC5 link identifier can uniquely identify the PC5 unicast link in the UE during the lifetime of the PC5 unicast link. The PC5 link identifier can be used to indicate a PC5 unicast link that has made a sidelink radio link failure (RLF) declaration and whose PC5-RRC connection has been released.

[0040] Figure 2A and Figure 2B Examples of radio protocol stacks for the user plane and control plane, respectively, are shown, representing some aspects of one or more exemplary embodiments according to this disclosure. Figure 2A As shown, the protocol stack for the user plane of the Uu interface (between UE 125 and gNB115) includes Service Data Adaptation Protocol (SDAP) 201 and SDAP 211, Packet Data Convergence Protocol (PDCP) 202 and PDCP 212, Radio Link Control (RLC) 203 and RLC 213, Layer 2 MAC 204 and MAC 214 sublayers, and Physical (PHY) 205 and PHY 215 layers (Layer 1 is also referred to as L1).

[0041] 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 streams 240 to 5GC.

[0042] The main services and functions of the MAC 204 or MAC 214 sublayer include: mapping between logical channels and transport channels; multiplexing MAC Service Data Units (SDUs) belonging to one or different logical channels into / demultiplexing them from transport blocks (TBs) passed to the physical layer on the transport channel; scheduling of information reports; error correction via Hybrid Automatic Repeat Request (HARQ) (one HARQ entity per cell in the case of Carrier Aggregation (CA)); priority handling among UEs using dynamic scheduling; priority handling among logical channels of a UE via Logical Channel Prioritization (LCP); priority handling among overlapping resources of a UE; and padding. A single MAC entity can support multiple parameter sets (numerology), transmission timings, and cells. Mapping constraints in logical channel priorities control which parameter set(s), cells(s), and transmission timings(s) a logical channel can use.

[0043] The HARQ function ensures delivery between peer entities at Layer 1. When the physical layer is not configured for downlink / uplink spatial multiplexing, a single HARQ process can support one TB, and when the physical layer is configured for downlink / uplink spatial multiplexing, a single HARQ process can support one or more TBs.

[0044] The RLC 203 or RLC 213 sublayer can support three transmission modes: Transparent Mode (TM); Unacknowledged Mode (UM); and Acknowledged Mode (AM). RLC configuration can be applied to each logical channel, regardless of the parameter set and / or transmission duration, and Automatic Repeat Request (ARQ) can operate on any parameter set and / or transmission duration configured for the logical channel.

[0045] The primary services and functions of the RLC 203 or RLC 213 sublayer depend on the transport mode (e.g., TM, UM, or AM) and may include: transmission of upper-layer PDUs; sequence numbering independent of sequence numbering in PDCP (UM and AM); error correction via ARQ (AM only); segmentation (AM and UM) and resegmentation (AM only) of RLC SDUs; reassembly of SDUs (AM and UM); duplicate detection (AM only); RLC SDU discarding (AM and UM); RLC reconstruction; and protocol error detection (AM only).

[0046] Automatic repeat requests within the RLC 203 or RLC 213 sublayer may have the following features: ARQ retransmits RLC SDUs or RLC SDU segments based on RLC status reports; polling of RLC status reports can be used when needed by the RLC; and the RLC receiver can also trigger an RLC status report after detecting a lost RLC SDU or RLC SDU segment.

[0047] The main services and functions of the PDCP 202 or PDCP 212 sublayer may include: data transmission (user plane or control plane); maintenance of PDCP sequence numbers (SN); header compression and decompression using the Robust Header Compression (ROHC) protocol; header compression and decompression using the EHC protocol; encryption and decryption; integrity protection and integrity verification; timer-based SDU discarding; routing of split bearers; duplication; reordering and ordered delivery; out-of-order delivery; and duplicate discarding.

[0048] The main services and functions of SDAP 201 or SDAP 211 include: mapping between QoS flows and data radio bearers; and marking QoS flow IDs (QFIs) in downlink and uplink packets. A single protocol entity for SDAP can be configured for each individual PDU session.

[0049] like Figure 2B As shown, the protocol stack of the control plane of the Uu interface (between UE 125 and gNB 115) includes the PHY layer (layer 1), and the MAC, RLC and PDCP sublayers of layer 2 as described above, as well as the RRC 206 sublayer and RRC 216 sublayer. The main services and functions of the RRC 206 and RRC 216 sublayers on the Uu interface include: broadcasting system information related to AS and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance, and release of RRC connections between UE and NG-RAN (including the addition, modification, and release of carrier aggregation; and the addition, modification, and release of dual connections in NR or between E-UTRA and NR); security functions including key management; establishment, configuration, maintenance, and release of SRB and DRB; mobility functions (including handover and context transfer; UE cell selection and reselection and control of cell selection and reselection; and inter-RAT mobility); QoS management functions; UE measurement reporting and control of such reporting; detection and recovery from radio link failures; and NAS message transmission from UE to NAS and from NAS to UE. NAS 207 and NAS 227 layers are control protocols that perform functions such as authentication, mobility management, and security control (terminating at the network-side AMF).

[0050] The specific services and functions of the sidelink in 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; and reporting of UE auxiliary information for (one or more) SL service modes.

[0051] Figure 3A , Figure 3B and Figure 3CExample mappings between logical channels and transport channels in the downlink, uplink, and sidelink according to one or more exemplary embodiments of this disclosure are shown respectively. Different types of data transmission services can be provided by MAC. Each logical channel type can be defined by what type of information is transmitted. Logical channels can be classified into two groups: control channels and traffic channels. Control channels can be used only for the transmission of control plane information. The Broadcast Control Channel (BCCH) is a downlink channel used for broadcasting system control information. The Paging Control Channel (PCCH) is a downlink channel carrying paging messages. The Common Control Channel (CCCH) is a channel used for transmitting control information between the UE and the network. This channel can be used by UEs without a network RRC connection. The Dedicated Control Channel (DCCH) is a point-to-point bidirectional channel for transmitting dedicated control information between the UE and the network and can be used by UEs with an RRC connection. Traffic channels can be used only for the transmission of user plane information. A Dedicated Traffic Channel (DTCH) is a point-to-point channel dedicated to a single UE for transmitting user information. DTCHs can exist in both the uplink and downlink. A Sidelink Control Channel (SCCH) is a sidelink channel used to transmit control information (e.g., PC5-RRC and PC5-S messages) from one UE to another (or more) UEs. A Sidelink Traffic Channel (STCH) is a sidelink channel used to transmit user information from one UE to another (or more) UEs. A Sidelink Broadcast Control Channel (SBCCH) is a sidelink channel used to broadcast sidelink system information from one UE to another (or more) UEs.

[0052] Downlink transport channel types include Broadcast Channel (BCH), Downlink Shared Channel (DL-SCH), and Paging Channel (PCH). BCH is characterized by: a fixed, predefined transmission format; and the requirement to broadcast as a single message or through beamforming of different BCH instances throughout the cell's coverage area. DL-SCH is characterized by: support for HARQ; support for dynamic link adaptation by changing modulation, coding, and transmission power; the possibility of broadcasting throughout the cell; the possibility of using beamforming; support for dynamic and semi-static resource allocation; and support for Discontinuous Reception (DRX) to achieve UE power savings. PCH is characterized by: support for Discontinuous Reception (DRX) to achieve UE power savings (DRX period is indicated to the UE by the network); the requirement to broadcast as a single message or through beamforming of different BCH instances throughout the cell's coverage area; and mapping to physical resources that can also be dynamically used for traffic / other control channels.

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

[0054] Uplink transport channel types include Uplink Shared Channel (UL-SCH) and (one or more) Random Access Channels (RACH). UL-SCH is characterized by: the possibility of beamforming; support for dynamic link adaptation through variations in transmission power and possible modulation and coding; support for HARQ; and support for dynamic and semi-static resource allocation. RACH can be characterized by limited control information and collision risk.

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

[0056] Sidelink transmission channel types include: Sidelink broadcast channel (SL-BCH) and Sidelink shared channel (SL-SCH). SL-BCH can be characterized by a predefined transmission format. SL-SCH features include: support for unicast, multicast, and broadcast transmission; support for UE-autonomous resource selection and scheduling by NG-RAN; support for dynamic and semi-static resource allocation when NG-RAN allocates resources to the UE; support for HARQ; and support for dynamic link adaptation by changing transmission power, modulation, and coding.

[0057] In a side link, the following connections can exist between logical channels and transport channels: SCCH can be mapped to SL-SCH; STCH can be mapped to SL-SCH; and SBCCH can be mapped to SL-BCH.

[0058] Figure 4A , Figure 4B and Figure 4C Example mappings between transport channels and physical channels in the downlink, uplink, and sidelink according to one or more exemplary embodiments of this disclosure are shown respectively. The physical channels in the downlink include the Physical Downlink Shared Channel (PDSCH), the Physical Downlink Control Channel (PDCCH), and the 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. The transport channels are not mapped to the PDCCH but instead transmit downlink control information (DCI) via the PDCCH.

[0059] The physical channels in the uplink include the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), and the Physical Random Access Channel (PRACH). 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; instead, uplink control information (UCI) is transmitted via the PUCCH.

[0060] The physical channels in the sidelink include the Physical Sidelink Shared Channel (PSSCH), the Physical Sidelink Control Channel (PSCCH), the Physical Sidelink Feedback Channel (PSFCH), and the Physical Sidelink Broadcast Channel (PSBCH). The PSCCH indicates the resources and other transmission parameters used by the UE for the PSSCH. The PSSCH transmits the data's TB itself, as well as control information for the HARQ process and Channel State Information (CSI) feedback triggers. At least six Orthogonal Frequency Division Multiplexing (OFDM) symbols within a time slot can be used for PSSCH transmission. The Physical Sidelink Feedback Channel (PSFCH) can carry HARQ feedback on the sidelink from the UE intended to receive the PSSCH transmission to the UE performing the transmission. The PSFCH sequence can be transmitted in a PRB (Physical Backlink Buffer) repeated on two OFDM symbols near the end of the sidelink resource within a time slot. The SL-SCH transport channel can be mapped to the PSSCH. The SL-BCH can be mapped to the PSBCH. No transport channels are mapped to the PSFCH, but Sidelink Feedback Control Information (SFCI) can be mapped to the PSFCH. No transport channels are mapped to the PSCCH, but Sidelink Control Information (SCI) can be mapped to the PSCCH.

[0061] Figure 5A , Figure 5B , Figure 5C and Figure 5D Examples of radio protocol stacks for NR-side link communication are shown, illustrating some aspects of one or more exemplary embodiments of this disclosure. The AS protocol stack for the user plane (i.e., for STCH) in the PC5 interface may consist of SDAP, PDCP, RLC, and MAC sublayers, as well as a physical layer. The user plane protocol stack in... Figure 5A As shown in the diagram, the SBCCH AS protocol stack in the PC5 interface can consist of RRC, RLC, MAC sublayer, and physical layer, as follows: Figure 5BAs shown in the diagram. To support the PC5-S protocol, PC5-S sits above the PDCP, RLC, and MAC sublayers and the physical layer in the control plane protocol stack of the SCCH used for PC5-S, as shown in the diagram. Figure 5C As shown in the diagram, the AS protocol stack of the control plane for the SCCH of RRC in the PC5 interface consists of RRC, PDCP, RLC, and MAC sublayers, as well as the physical layer. The protocol stack of the control plane for the SCCH of RRC is shown in... Figure 5D As shown in the image.

[0062] 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 SL SRBs with different SCCHs can be configured for PC5-RRC and PC5-S signaling respectively.

[0063] The MAC sublayer can provide the following services and functions through the PC5 interface: radio resource selection; packet filtering; prioritization of processing between uplink and sidelink transmissions for a given UE; and sidelink CSI reporting. With logical channel prioritization constraints in the MAC, for each unicast, multicast, and broadcast transmission that may be associated with a destination, only sidelink logical channels belonging to the same destination can be multiplexed as a MAC PDU. For packet filtering, an SL-SCH MAC header including portions of the source 2ID and destination 2ID can be added to the MAC PDU. The Logical Channel Identifier (LCID) included in the MAC subheader can uniquely identify logical channels within the range of the source 2ID and destination 2ID combination.

[0064] Services and functions of the RLC sublayer can be supported for sidelinks. RLC unacknowledged mode (UM) and acknowledged mode (AM) can be used in unicast transmissions, while only UM can be used in multicast or broadcast transmissions. For UM, only unidirectional transmissions of multicast and broadcast can be supported.

[0065] The services and functions of the PDCP sublayer for the Uu interface can be supported for sidelinks with the following limitations: out-of-order delivery can be supported only for unicast transmission; and duplication can not be supported on the PC5 interface.

[0066] The SDAP sublayer can provide the following services and functions through the PC5 interface: mapping between QoS flows and sidelink data radio bearers. For each destination, there can be one SDAP entity, representing one of the unicast, multicast, or broadcast traffic types associated with it.

[0067] The RRC sublayer can provide the following services and functions through the PC5 interface: transmission of PC5-RRC messages between peer UEs; maintenance and release of PC5-RRC connections between two UEs; and detection of sidelink radio link failures of PC5-RRC connections based on indications from the MAC or RLC. A PC5-RRC connection can be a logical connection between two UEs for a pair of source 2IDs and destination 2IDs, which can be considered to be established after the corresponding PC5 unicast link is established. There can be a one-to-one correspondence between PC5-RRC connections and PC5 unicast links. For different source 2ID and destination 2ID pairs, a UE can have multiple PC5-RRC connections with one or more UEs. Separate PC5-RRC procedures and messages can be used by a UE to transmit UE capabilities and sidelink configurations, including SL-DRB configuration, to its peer UE. Two peer UEs can use separate bidirectional procedures in both sidelink directions to exchange their own UE capabilities and sidelink configurations.

[0068] Figure 6Example physical signals in the downlink, uplink, and sidelink according to one or more exemplary embodiments of this disclosure are illustrated. A demodulation reference signal (DM-RS) can be used in the downlink, uplink, and sidelink and can be used for channel estimation. The DM-RS is a UE-specific reference signal and can be transmitted along with the physical channel in the downlink, uplink, or sidelink, and can be used for channel estimation and coherent detection of the physical channel. A phase tracking reference signal (PT-RS) can be used in the downlink, uplink, and sidelink and can be used to track the phase and mitigate performance loss due to phase noise. PT-RS is primarily used to estimate and minimize the impact of common phase error (CPE) on system performance. Due to phase noise characteristics, the PT-RS signal may have low density in the frequency domain and high density in the time domain. PT-RS can occur in combination with DM-RS and occurs when the network configures PT-RS to be present. Positioning Reference Signal (PRS) can be used in the downlink for positioning using different positioning techniques. PRS can be used to measure downlink transmission delay by correlating the received signal from the base station with a local copy in the receiver. Channel State Information Reference Signal (CSI-RS) can be used in both the downlink and sidelink. Among other uses, CSI-RS can be used for channel state estimation, Reference Signal Received Power (RSRP) measurement for mobility and beam management, and time / frequency tracking for demodulation. CSI-RS can be specifically configured for the UE, but multiple users can share the same CSI-RS resource. The UE can determine CSI reports and transmit them to the base station in the uplink using PUCCH or PUSCH. CSI reports can be carried in the sidelink MAC control element (CE). Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS) can be used for radio frame synchronization. PSS and SSS can be used during the initial access process for cell search or for mobility purposes.Sounding Reference Signals (SRS) can be used in the uplink for uplink channel estimation. Similar to CSI-RS, SRS can be used as a QCL reference for other physical channels, allowing them to be configured and transmitted quasi-co-located with the SRS. Sidelink PSS (S-PSS) and Sidelink SSS (S-SSS) can be used for sidelink synchronization.

[0069] Figure 7 Examples of Radio Resource Control (RRC) states and transitions between different RRC states are illustrated according to one or more exemplary embodiments of this disclosure. The UE can be in one of three RRC states: RRC connected state 710, RRC idle state 720, and RRC inactive state 730. After power-on, the UE can be in RRC idle state 720, and the UE can use initial access and establish a connection with the network via the RRC connection establishment procedure to perform data transmission and / or make / receive voice calls. Once the RRC connection is established, the UE can be in RRC connected state 710. The UE can use the RRC connection establishment / release procedure 740 to transition from RRC idle state 720 to RRC connected state 710 or from RRC connected state 710 to RRC idle state 720.

[0070] To reduce signaling load and latency caused by frequent transitions from RRC connected state 710 to RRC idle state 720 when the UE transmits frequent small data, RRC inactive state 730 can be used. In RRC inactive state 730, both the UE and gNB can store the AS context. This can result in a faster state transition from RRC inactive state 730 to RRC connected state 710. The UE can use RRC connection recovery / inactivity procedure 760 to transition from RRC inactive state 730 to RRC connected state 710 or from RRC connected state 710 to RRC inactive state 730. The UE can use RRC connection release procedure 750 to transition from RRC inactive state 730 to RRC idle state 720.

[0071] Figure 8Example frame structures and physical resources are shown for some aspects of one or more exemplary embodiments according to this disclosure. Downlink, uplink, or sidelink transmissions can be organized into frames with 10 (0 to 9) 1ms subframes. Each subframe can consist of k time slots (k = 1, 2, 4…), where the number of time slots k in each subframe can depend on the subcarrier spacing of the carriers transmitted over it. The time slot duration can be 14 symbols (0 to 13) with a normal cyclic prefix (CP) and 12 symbols with an extended CP, and can be time-scaled as a function of the subcarrier spacing used, such that an integer number of time slots exist in the subframe. Figure 8 The resource grid is shown in the time and frequency domains. Each element of the resource grid, which consists of a time symbol and a frequency subcarrier, is called a resource element (RE). A resource block (RB) can be defined as 12 consecutive subcarriers in the frequency domain.

[0072] In some examples, and in the case of non-slot-based scheduling, packet transmission can occur on a portion of a time slot, such as during two, four, or seven OFDM symbols; this can also be referred to as a time slot. Time slots can be used for low-latency applications, such as URLLC and operation in unlicensed frequency bands. In some embodiments, time slots can also be used for fast and flexible scheduling of services (e.g., preemption of URLLC over eMBB).

[0073] Figure 9 Example component carrier configurations in different carrier aggregation scenarios are illustrated according to one or more exemplary embodiments of this disclosure. In carrier aggregation (CA), two or more component carriers (CCs) can be aggregated. The UE can receive or transmit simultaneously on one or more CCs depending on its capabilities. Figure 9 As shown, CA can be supported for consecutive and non-consecutive CCs on the same or different frequency bands. The gNB and UE can communicate using the serving cell. The serving cell can be associated with at least one downlink CC (e.g., it can be associated with only one downlink CC, or it can be associated with both downlink and uplink CCs). The serving cell can be a primary cell (PCell) or a secondary cell (SCell).

[0074] The UE can use the uplink timing control procedure to adjust the timing of its uplink transmissions. Timing Advance (TA) can be used to adjust the uplink frame timing relative to the downlink frame timing. The gNB can determine the required timing advance setting and provide it to the UE. The UE can use the provided TA to determine its uplink transmission timing relative to the downlink receive timing observed by the UE.

[0075] In RRC connected state, the gNB is responsible for maintaining timing advance to keep L1 synchronized. Serving cells with uplinks applying the same timing advance and using the same timing reference cell are grouped into Timing Advance Groups (TAGs). A TAG can contain at least one serving cell with a configured uplink. The mapping from serving cell to TAG can be configured by RRC. For a primary TAG, the UE can use the PCell as the timing reference cell, except for those with shared spectrum channel access, where the SCell can also be used as the timing reference cell in some cases. In a secondary TAG, the UE can use any active SCell of that TAG as the timing reference cell, and can leave it unchanged unless necessary.

[0076] Pre-updates can be signaled to the UE by the gNB via a MAC CE command. Such a command can restart a TAG-specific timer that indicates whether L1 can be synchronized: when the timer is running, L1 can be considered synchronized; otherwise, L1 can be considered asynchronous (in which case, uplink transmissions may occur only on PRACH).

[0077] A UE with a single timing advance capability for CA can simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells (multiple serving cells in a group) sharing the same timing advance. A UE with multiple timing advance capabilities for CA can simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells (multiple serving cells in multiple groups). NG-RAN can ensure that each TAG contains at least one serving cell. A UE without CA capability can receive on a single CC and can transmit on a single CC corresponding to only one serving cell (one serving cell in a TAG).

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

[0079] In a dual-connectivity scenario, a UE can be configured with multiple cells, including a Master Cell Group (MCG) for communicating with the master base station, a Secondary Cell Group (SCG) for communicating with the secondary base station, and two MAC entities: a MAC entity for the MCG for communicating with the master base station, and a MAC entity for the SCG for communicating with the secondary base station.

[0080] Figure 10 Example partial bandwidth configurations and handovers are illustrated according to one or more exemplary embodiments of this disclosure. A UE may be configured with one or more partial bandwidths (BWPs) 1010 (e.g., 1010A, 1010B) on a given member carrier. In some examples, one of the one or more partial bandwidths is active at any given time. The active partial bandwidth may define the UE's operating bandwidth within the cell's operating bandwidth. For initial access, and until the UE's configuration in the cell is received, an initial partial bandwidth 1020 determined based on system information may be used. Utilizing bandwidth adaptation (BA), such as through BWP handover 1040, the UE's receive and transmit bandwidths may not be as large as the cell's bandwidth and can be adjusted. For example, the width may be commanded to change (e.g., shrinking during periods of low activity to save power); the location may be moved in the frequency domain (e.g., to increase scheduling flexibility); and the subcarrier spacing may be commanded to change (e.g., to allow different services). The first active BWP 1030 may be an active BWP for active RRC (re)configuration for a PCell or SCell.

[0081] For each downlink BWP or uplink BWP in the set of downlink or uplink BWPs, the following configuration parameters can be provided to the UE: Subcarrier Spacing (SCS); Cyclic Prefix; Common RB and multiple consecutive RBs; the index of the corresponding BWP-Id in the set of downlink or uplink BWPs; the set of BWP common parameters and the set of BWP specific parameters. Based on the configured subcarrier spacing and the cyclic prefix of the BWP, the BWP can be associated with an OFDM parameter set. For the serving cell, a default downlink BWP from the configured downlink BWPs can be provided to the UE. If the UE is not provided with a default downlink BWP, the default downlink BWP can be the initial downlink BWP.

[0082] A downlink BWP can be associated with a BWP inactivity timer. If the BWP inactivity timer associated with the active downlink BWP expires, and if a default downlink BWP is configured, the UE can perform a BWP handover to the default BWP. If the BWP inactivity timer associated with the active downlink BWP expires, and if no default downlink BWP is configured, the UE can perform a BWP handover to the initial downlink BWP.

[0083] Figure 11 The following examples illustrate a four-step contention-based random access (CBRA) procedure and a contention-free random access (CFRA) procedure, representing some aspects of one or more exemplary embodiments of this disclosure. Figure 12Examples of two-step contention-based random access (CBRA) and contention-free random access (CFRA) procedures are shown, illustrating some aspects of one or more exemplary embodiments of this disclosure. The random access procedure may be triggered by multiple events, such as: initial access from an RRC idle state; RRC connection reconstruction process; arrival of downlink or uplink data during an RRC connected state when the uplink synchronization state is “asynchronous”; arrival of uplink data during an RRC connected state when no PUCCH resource is available for a scheduling request (SR); SR failure; a request from the RRC during synchronization reconfiguration (e.g., handover); transition from an RRC inactive state; time alignment for establishing a second TAG; request for additional system information (SI); beam failure recovery (BFR); and consistent uplink listen-before-talk (LBT) failure.

[0084] It supports two types of random access (RA) procedures: a 4-step RA type with MSG1 and a 2-step RA type with MSGA. Both types of RA procedures can support, for example, Figure 11 and Figure 12 The examples shown are contention-based random access (CBRA) and contention-free random access (CFRA).

[0085] The UE can select the type of random access at the start of the random access procedure based on network configuration. When no CFRA resources are configured, the UE can use the RSRP threshold to select between the 2-step RA type and the 4-step RA type. When CFRA resources are configured for the 4-step RA type, the UE can perform random access using the 4-step RA type. When CFRA resources are configured for the 2-step RA type, the UE can perform random access using the 2-step RA type.

[0086] A 4-step RA type MSG1 can be composed of a preamble on a PRACH ( Figure 11 Step 1 of CBRA (in the context of MSG1 transmission). After MSG1 transmission, the UE can monitor the response from the network within the configured window ( Figure 11 Step 2 of CBRA). For CFRA, the dedicated preamble for MSG1 transmission can be allocated by the network ( Figure 11 In step 0 of the CFRA, and upon receiving a Random Access Response (RAR) from the network, the UE can terminate the process as follows: Figure 11 The random access procedure shown in the figure Figure 11Steps 1 and 2 of CFRA). For CBRA, upon receiving the random access response ( Figure 11 During step 2 of the CBRA, the UE can use the uplink grant scheduled in the random access response to send MSG3 ( Figure 11 Step 3 of the CBRA, and can be as follows Figure 11 The ground monitoring contention resolution shown in the figure ( Figure 11 (Step 4 of CBRA). If contention resolution fails after (one or more) MSG3 (re)transmissions, the UE can return to MSG1 transmission.

[0087] A 2-step RA type MSGA can include a preamble on the PRACH and a payload on the PUSCH (e.g., Figure 12 Step A of CBRA. After MSGA transmission, the UE can monitor the response from the network within a configured window. For CFRA, dedicated preamble and PUSCH resources can be configured for MSGA transmission ( Figure 12 In CFRA steps 0 and A), and upon receiving the network response ( Figure 12 During step B) of CFRA, the UE can end as follows: Figure 12 The random access procedure is shown below. For CBRA, if contention is successfully resolved upon receiving a network response ( Figure 12 If step B) of the CBRA is completed, the UE can end as follows: Figure 12 The random access procedure is shown in the diagram. If a backoff indication is received in the MSGB, the UE can use the uplink grant scheduled in the backoff indication to perform an MSG3 transmission and can monitor contention resolution. If contention resolution fails after (one or more) MSG3 (re)transmissions, the UE can return to an MSGA transmission.

[0088] Figure 13 Example time and frequency structures of synchronization signals and Physical Broadcast Channel (PBCH) blocks (SSBs) according to one or more exemplary embodiments of this disclosure are shown. An SS / PBCH block (SSB) may consist of a primary synchronization signal and a secondary synchronization signal (PSS, SSS), each occupying one symbol and 127 subcarriers (e.g., Figure 13 The subcarriers are numbered 56 to 182, and the PCBH spans 3 OFDM symbols and 240 subcarriers, but leaves an unused portion in the middle of one symbol for the SSS, such as... Figure 13 As shown in the diagram, the possible temporal location of the SSB within a half-frame can be determined by the subcarrier spacing, and the period of the half-frame for transmitting the SSB can be configured by the network. During the half-frame, different SSBs can be transmitted in different spatial directions (i.e., using different beams that span the coverage area of ​​the cell).

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

[0090] Figure 14 Example SSB burst transmissions are illustrated according to one or more exemplary embodiments of this disclosure. An SSB burst may include N SSBs (e.g., SSB_1, SSB_2…SSB_N), and each of the N SSBs may correspond to a beam (e.g., beam_1, beam_2…beam_N). SSB bursts may be transmitted according to a period (e.g., SSB burst periods). During a contention-based random access procedure, the UE may perform a random access resource selection procedure, whereby the UE first selects an SSB before selecting an RA preamble. The UE may select an SSB with an RSRP higher than a configured threshold. In some embodiments, if no SSB with an RSRP higher than the configured threshold is available, the UE may select any SSB. A set of random access preambles may be associated with an SSB. After selecting an SSB, the UE may select a random access preamble from the set of random access preambles associated with the SSB, and may transmit the selected random access preamble to initiate the random access procedure.

[0091] In some embodiments, beams among the N beams may be associated with CSI-RS resources (e.g., CSI-RS_1, CSI-RS_2, ..., CSI-RS_N). The UE can measure the CSI-RS resources and select CSI-RSs with RSRP higher than a configured threshold. The UE can select a random access preamble corresponding to the selected CSI-RS and can transmit the selected random access preamble to initiate the random access procedure. If there is no random access preamble associated with the selected CSI-RS, the UE can select a random access preamble corresponding to an SSB that is quasi-in-line with the selected CSI-RS.

[0092] In some embodiments, based on UE measurements and UE CSI reports using CSI-RS resources, the base station can determine the Transmission Configuration Indication (TCI) state and can indicate the TCI state to the UE, whereby the UE can use the indicated TCI state to receive downlink control information (e.g., via PDCCH) or data (e.g., via PDSCH). The UE can use the indicated TCI state to receive data or control information using an appropriate beam. The TCI state indication can use RRC configuration or a combination of RRC signaling and dynamic signaling (e.g., via MAC Control Element (MAC CE) and / or based on field values ​​in downlink control information that schedules downlink transmissions). The TCI state can indicate a quasi-colocation (QCL) relationship between a downlink reference signal such as CSI-RS and a DM-RS associated with a downlink control or data channel (e.g., PDCCH or PDSCH, respectively).

[0093] In some embodiments, the UE can configure itself using a list of up to M TCI states configured with Physical Downlink Shared Channel (PDSCH) configuration parameters to decode the PDSCH based on the detected PDCCH, where the DCI is intended for both the UE and a given serving cell, and M may depend on the UE's capabilities. Each TCI state may contain parameters for configuring the QCL relationship between one or two downlink reference signals and the DM-RS port of the PDSCH, the DM-RS port of the PDCCH, or the CSI-RS port of the CSI-RS resource. This quasi-correspondence relationship may be configured by one or more RRC parameters. The quasi-correspondence type corresponding to each DL RS may take one of the following values: "QCL-TypeA": {Doppler shift, Doppler spread, average delay, delay spread}; "QCL-TypeB": {Doppler shift, Doppler spread}; "QCL-TypeC": {Doppler shift, average delay}; "QCL-type": {spatial reception parameters}. The UE can receive activation commands (e.g., MAC CE) for mapping TCI states to code points in the DCI field.

[0094] Figure 15 Example components of a user equipment and base station for transmission and / or reception are shown, representing some aspects of one or more exemplary embodiments according to this disclosure. In one embodiment, Figure 15 The illustrative component may be Figure 15 All or a subset of the blocks and functions in the illustrative base station 1505 can be considered as illustrative examples of functional blocks of the illustrative base station 1505. In another embodiment, Figure 15 The illustrative components can be considered as illustrative examples of the functional blocks of the illustrative user equipment 1500. Therefore, Figure 15 The components shown are not necessarily limited to user equipment or base stations.

[0095] refer to Figure 15Antenna 1510 can be used for the transmission or reception of electromagnetic signals. Antenna 1510 may include one or more antenna elements and can implement different 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, antenna 150 can implement a large number of MIMO configurations with dozens or hundreds of antenna elements. Antenna 1510 can implement other multi-antenna techniques such as beamforming. In some embodiments, depending on the capabilities of UE 1500 or the type of UE 1500 (e.g., a low-complexity UE), UE 1500 may support only a single antenna.

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

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

[0098] Processor 1540 may include hardware devices with 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, processor 1540 may be configured to operate memory using a memory controller. In other examples, the memory controller may be integrated into processor 1540. Processor 1540 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1530) to cause UE 1500 or base station 1505 to perform various functions.

[0099] CPU 1550 can execute basic arithmetic, logic, control, and input / output (I / O) operations specified by computer instructions stored in memory 1530. UE 1500 and / or base station 1505 may include additional peripheral components such as a Graphics Processing Unit (GPU) 1560 and a Global Positioning System (GPS) 1570. GPU 1560 is dedicated circuitry for rapidly manipulating and modifying memory 1530 to accelerate the processing performance of UE 1500 and / or base station 1505. GPS 1570 can be used, for example, to enable location-based services or other services based on the geographic location of UE 1500.

[0100] In some examples, MBS service can be enabled via a single cell transmission. MBS can be transmitted within the coverage of a single cell. One or more multicast / broadcast control channels (e.g., MCCH) and one or more multicast / broadcast data channels (e.g., MTCH) can be mapped on the DL-SCH. Scheduling can be performed by the gNB. Transmissions of multicast / broadcast control channels and multicast / broadcast data channels can be indicated by logical channel-specific RNTIs on the PDCCH. In some examples, a one-to-one mapping between service identifiers such as Temporary Mobile Group Identifiers (TMGI) and RAN-level identifiers such as Group Identifiers (G-RNTIs) can be used to receive DL-SCHs to which multicast / broadcast data channels can be mapped. In some examples, a single transmission can be used for the DL-SCH associated with multicast / broadcast control channel and / or multicast / broadcast data channel transmissions, and can be used without HARQ or RLC retransmission and / or with RLC unacknowledged mode (RLC UM). In other examples, some feedback (e.g., HARQ feedback or RLC feedback) may be used for transmission via multicast / broadcast control channels and / or multicast / broadcast data channels.

[0101] In some examples, for multicast / broadcast data channels, the following scheduling information can be provided on the multicast / broadcast control channel: multicast / broadcast data channel scheduling period, multicast / broadcast data channel open duration (e.g., the duration for which the UE waits to receive a PDCCH after being woken up from DRX), and multicast / broadcast data channel inactivity timer (e.g., the time for the UE to wait for successful decoding of the PDCCH, starting from the most recent successful decoding of the PDCCH indicating the DL-SCH mapped by the multicast / broadcast data channel, and re-entering DRX if it fails).

[0102] In some examples, one or more UE identifiers may be associated with MBS transmissions. These identifiers may include at least one of the following: one or more first RNTIs identifying the transmission of a multicast / broadcast control channel; and one or more second RNTIs identifying the transmission of a multicast / broadcast data channel. The one or more first RNTIs identifying the transmission of a multicast / broadcast control channel may include a Single Cell RNTI (SC-RNTI, or other names may be used). The one or more second RNTIs identifying the transmission of a multicast / broadcast data channel may include a G-RNTI (nG-RNTI, or other names may be used).

[0103] In some examples, one or more logical channels may be associated with MBS transmission. One or more logical channels may include multicast / broadcast control channels. A multicast / broadcast control channel can be a point-to-multipoint downlink channel used to transmit MBS control information from the network to the UE for one or more multicast / broadcast data channels. This channel can be used by a UE that is receiving or interested in receiving MBS. One or more logical channels may include multicast / broadcast data channels. This channel can be a point-to-multipoint downlink channel used to transmit MBS service data from the network.

[0104] In some examples, the UE may use a procedure to notify the RAN that the UE is receiving or is interested in receiving MBS services via the MBS radio bearer, and if so, to notify the 5G RAN about the priority of MBS for unicast reception or MBS service reception in receive-only mode. Figure 16 An example is shown below. The UE can transmit messages (e.g., MBS Interest Indication messages) to notify the RAN that the UE is receiving / interested in receiving or no longer receiving / no longer interested in receiving MBS services. The UE can transmit messages based on one or more messages received from the network (e.g., SIB messages or unicast RRC messages), such as one or more MBS service area identifiers indicating the current and / or adjacent carrier frequencies.

[0105] In some examples, if the UE is able to receive MBS services (e.g., via a single cell point-to-multipoint mechanism); and / or the UE is receiving or is interested in receiving MBS services via a bearer associated with the MBS service; and / or a session of the MBS service is in progress or about to begin; and / or at least one of one or more MBS service identifiers indicated by the network is of interest to the UE, then the UE may consider the MBS service to be part of the MBS service of interest.

[0106] In some examples, control information for receiving MBS services can be provided on a specific logical channel (e.g., MCCH). The MCCH can carry one or more configuration messages indicating the ongoing MBS session and (corresponding) information about when each session can be scheduled, such as the scheduling period, scheduling window, and start offset. These one or more configuration messages can provide information about neighboring cells transmitting the MBS session, which can take place on the current cell. In some examples, the UE can receive a single MBS service at a time, or receive more than one MBS service in parallel.

[0107] In some examples, MCCH information (e.g., information transmitted in messages sent via the MCCH) can be transmitted periodically using configurable repetition periods. MCCH transmission (along with associated radio resources and MCS) can be indicated on the PDCCH.

[0108] In some examples, changes to MCCH information can occur within a specific radio frame / subframe / slot and / or a modification period can be used. For example, within a modification period, the same MCCH information can be transmitted multiple times, as defined by its scheduling (which is based on repeating periods). The modification period boundary can be defined by an SFN value of SFN mod m = 0, where m is the number of radio frames including the modification period. The modification period can be configured by SIB or RRC signaling.

[0109] In some examples, when the network changes (some) MCCH information, it can notify the UE of the change in the first subframe / slot, which can then be used for MCCH transmission during a recurring period. Upon receiving the change notification, a UE interested in receiving MBS services can begin acquiring the new MCCH information from the same subframe / slot. The UE can apply the previously acquired MCCH information until it acquires the new MCCH information.

[0110] In one example, the System Information Block (SIB) may contain information required to obtain control information associated with the transmission of the MBS. This information may include at least one of the following parameters: one or more Discontinuous Receive (DRX) parameters for scheduling information used to monitor the control information associated with the transmission of the MBS; a scheduling period and offset for scheduling the control information associated with the transmission of the MBS; a modification period for modifying the content of the control information associated with the transmission of the MBS; and repetition information for repeating the control information associated with the transmission of the MBS.

[0111] In one example, the Information Element (IE) can provide configuration parameters indicating, for example, a list of ongoing MBS sessions transmitted via one or more bearers for each MBS session, one or more associated RNTIs (e.g., G-RNTIs, which may use other names), and scheduling information. Configuration parameters may include at least one of the following: one or more timer values ​​for Discontinuous Reception (DRX) (e.g., inactive timers or on-duration timers), RNTIs for scrambling the scheduling and transmission of multicast / broadcast traffic channels (e.g., MTCHs, which may use other names), ongoing MBS sessions, one or more power control parameters, one or more scheduling periods and / or offset values ​​for one or more MBS traffic channels, information about neighboring cell lists, etc.

[0112] Example implementations can enable RAN functions for broadcast / multicast for UEs in RRC connected (RRC_CONNECTED), RRC idle (RRC_IDLE), and RRC inactive (RRC_INACTIVE) states. Group scheduling mechanisms can be used to allow UEs to receive broadcast / multicast services. In some examples, broadcast / multicast services can be enabled to operate concurrently with unicast reception. In some examples, broadcast / multicast service delivery can be dynamically changed between multicast (PTM) and unicast (PTP) with service continuity for a given UE. In some examples, coordination functions can reside in the gNB-CU. In some examples, the reliability of broadcast / multicast services can be improved through UL feedback. The reliability level can be based on the requirements of the provided application / service. In some examples, the broadcast / multicast transmission area can be dynamically controlled within a gNB-DU.

[0113] In some examples, MAC entities can be configured by an RRC with DRX functionality, which controls the UE's PDCCH to monitor the RNTI activity of multiple MAC entities. RNTIs can 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 in an RRC connection, if DRX is configured, the MAC entity can use DRX operations to discontinuously monitor the PDCCH for the active serving cell; otherwise, the MAC entity can monitor the PDCCH directly.

[0114] RRC can control DRX operation through configuration of several parameters, including: drx-onDurationTimer: the duration at the start of the DRX cycle; drx-SlotOffset: the delay before drx-onDurationTimer is started; drx-InactivityTimer: the duration after the PDCCH timing, where the PDCCH indicates a new UL or DL ​​transmission for the MAC entity; drx-RetransmissionTimerDL (per DL HARQ process, except for broadcast processes): the maximum duration until a DL retransmission is received; and drx-RetransmissionTimerUL (per UL). HARQ process): The maximum duration until permission for UL retransmission is received; drx-LongCycleStartOffset: The long DRX cycle and the drx-startOffset of the subframe that defines where the long DRX cycle and short DRX cycle begin; drx-ShortCycle (optional): The short DRX cycle; drx-ShortCycleTimer (optional): The duration for which the UE can follow the short DRX cycle; drx-HARQ-RTT-TimerDL (per DL HARQ process, except for broadcast processes): The minimum duration expected by the MAC entity before the DL allocation for HARQ retransmission; drx-HARQ-RTT-TimerUL (per UL HARQ process): The minimum duration expected by the MAC entity before UL HARQ retransmission permission is granted.

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

[0116] The UE can monitor a set of PDCCH candidates in one or more configured control resource sets (CORESETs) at configured monitoring times, based on the corresponding search space configuration. A CORESET can include a set of Physical Resource Blocks (PRBs) with a duration of 1 to 3 OFDM symbols. Resource Element Groups (REGs) and Control Channel Elements (CCEs) can be defined within a CORESET, where each CCE includes a set of REGs. Control channels can be formed by aggregating CCEs. Different code rates for control channels can be achieved by aggregating different numbers of CCEs. Interleaved and non-interleaved CCE-to-REG mappings are supported within a CORESET.

[0117] In some examples, semi-persistent scheduling (SPS) can be configured by the RRC of each serving cell and each BWP. Multiple allocations can be activated simultaneously within the same BWP. Activation and deactivation of DL SPS can be independent between serving cells. For DL ​​SPS, DL allocations can be provided by the PDCCH, and DL allocations can be stored or cleared based on L1 signaling indicating SPS activation or deactivation.

[0118] When SPS is configured, RRC can be configured with the following parameters: cs-RNTI: CS-RNTI used for activation, deactivation and retransmission; nrofHARQ-Processes: the number of HARQ processes configured for SPS; harq-Process-Offset: the offset of the HARQ process for SPS; periodicity: the period of downlink allocation configured for SPS.

[0119] In some examples, utilizing semi-persistent scheduling (SPS), the gNB can allocate downlink resources to the UE for initial HARQ transmission: the RRC can define the period of the configured downlink allocation, and the PDCCH addressed to the CS-RNTI can signal and activate, or deactivate, the configured downlink allocation. The PDCCH addressed to the CS-RNTI can indicate that the downlink allocation can be implicitly reused according to the period defined by the RRC until it is deactivated.

[0120] In some examples, MBS transmissions may be limited to one or more BWPs of a cell, such as the cell's initial BWP. Some pre-configured / configurable MBS services may be broadcast via non-initial BWPs. In some examples, MBS services may be broadcast via one or more beams associated with the cell, rather than all beams. In some examples, the same MBS message may be repeated in all transmitted beams in multi-beam operations.

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

[0122] In some examples, a UE in an RRC idle / RRC inactive state can receive multicast sessions without entering an RRC connected state.

[0123] In some examples, the UE can identify active MBS services on a cell based on a list of supported services signaled as part of multicast control information in the transport area. A UE interested in a service can perform a procedure to begin PTM reception for that service. A UE in an RRC idle or RRC inactive state can be mobile and can perform cell reselection to a neighboring cell. For a UE interested in receiving MBS services, and for cell reselection, knowledge of the MBS service support in neighboring cells can be available to the UE. In an RRC idle or RRC inactive state, the availability and support of the MBS service of interest on neighboring cells is available to the UE receiving the PTM service. If the availability of the MBS service of interest on neighboring cells is known, the UE can prioritize those cells or frequencies for cell reselection.

[0124] In some examples, during cell reselection, the UE can obtain multicast control information about the target cell before it begins listening for multicast data transmission.

[0125] In some examples, System Information Blocks (SIBs) can be used to signal the configuration required to receive periodically transmitted multicast / broadcast control information. Multicast / broadcast control messages can be introduced to signal the configuration required to receive multicast / broadcast sessions on multicast traffic channels.

[0126] In some cases, not all supported MBS services in the transmission area are available to UEs in all RRC states, and some MBS transmissions in a cell may be reserved for reception in specific RRC states (e.g., in RRC connected states). Based on the characteristics of MBS services, it can be observed that some of these services can be effectively received in idle or inactive states (e.g., IPTV), while others can be served more effectively in RRC connected states (e.g., mission-critical services). For services that can be received in idle or inactive states, the UE can obtain the control information required to receive the multicast session before PTM reception. However, for services specified by the gNB as being received only in RRC connected states, some control information can be signaled in the connected state. In some examples, some MBS services may be supported only in RRC connected states. For services available to UEs in RRC connected states, unicast signaling can be used to provide some multicast / broadcast control information.

[0127] In some examples, resources can be flexibly allocated between unicast and broadcast / multicast services. The network can deploy MBS services on a subset of the carrier bandwidth, rather than across the entire carrier bandwidth. For example, a subset of BWPs in a cell can support MBS services, while others can support unicast services. Because BWPs are associated with subcarrier spacing (SCS) / parameter sets, and different services may require different SCSs, the services supported by BWPs across different MBSs within a cell can be different. MBS services such as those for public safety, mission-critical purposes, etc., may have different scheduling requirements than other use cases (e.g., different SCSs). In such cases, the network may prefer to have these services in separate BWPs. In some examples, MBS services can be supported for each carrier or each portion of the bandwidth. Different BWPs within a cell can provide different MBS services.

[0128] In some examples, PTM transmissions can be based on DL-SCH, for example, by receiving MBS PTM bearers through monitoring the PDCCH scheduling group RNTI on the PDSCH. The associated MBS MRB / DRB configuration can be provided to the UE via dedicated RRC signaling.

[0129] In some examples, multicast / broadcast services can be provided by DRB or MRB (C-RNTI / G-RNTI), and the actual dynamic handover and selection can be transparent to the UE. Decisions regarding dynamic handover between multicast (PTM) and unicast (PTP / DRB) can also be transparent to the UE. In some examples, physical layer enhancements such as HARQ / feedback are provided, and PDCP functionality for reordering and duplicate detection (e.g., duplicate drop) is included. Unicast bearers can be used to provide additional reliability if needed (e.g., RLC AM). The use of HARQ retransmission and HARQ feedback is also beneficial for PTM.

[0130] In existing point-to-multipoint solutions, a single control channel is configured via SIB2, and this control channel configures one or more service channels. The SIB, control channel, and all service channels can be on the same carrier. Although service channels can have different scheduling periods, activation durations, and inactivity timers without any retransmission, a single control channel is configured and used to schedule all service channels. Existing point-to-multipoint solutions lack flexibility and may result in duplicate transmissions of control information and inefficiencies in delivering multicast services. The example implementation enhances multicast signaling and configuration.

[0131] Example implementations can enable initial RAN-level configuration of control information related to Multicast and Broadcast Service (MBS). The MBS mechanism can be used to provide multicast and broadcast services, and also for Mission Critical Push-to-Talk (MCPTT), Internet of Things (IoT), and Vehicle-to-Everything (V2X). In some embodiments, a cell can use the Physical Downlink Shared Channel (PDSCH) to send multicast / broadcast data and control information to a group of mobile communication devices. In some examples, multicast / broadcast service data can be sent on the PDSCH using a group-specific radio network temporary identifier (e.g., G-RNTI, which may use other names), and control information can be sent on the PDSCH using an SC-PTM radio network temporary identifier (e.g., SC-RNTI, which may use other names).

[0132] In some example embodiments, in order to receive MBS transmissions, a mobile communication device may receive one or more of the following 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, which may use other names) and multicast / broadcast data (e.g., via a Multicast / Broadcast Traffic Channel (MTCH) logical channel, which may use other names).

[0133] In such Figure 17 In some example embodiments shown, system information provided by the SIB can indicate how to receive multicast / broadcast control information (e.g., via the MCCH channel). The system information can indicate modification periods (e.g., where control information can be changed), repetition periods / offsets (where multicast / broadcast control information can be repeated), etc. In some examples, the aforementioned SIB information can be transmitted via unicast RRC signaling. The control information (e.g., MCCH) can indicate available multicast / broadcast services and how to receive multicast / broadcast data (e.g., via MTCH) via an associated service identifier (e.g., Temporary Mobile Group Identifier (TMGI), which may use other names). A logical channel (e.g., MTCH) used for transmitting multicast / broadcast data can be used to transmit data for a multicast / broadcast service. In some examples, the control information (e.g., MCCH) can include configuration messages for configuring MBS-related parameters. The configuration message can indicate an ongoing multicast / broadcast session. The configuration message can also indicate information that each session can be scheduled and can also include a list of neighboring cells of potential neighbors providing the same service (e.g., the same service identifier, such as the same TMGI).

[0134] In some example implementations, a UE in a 5G network can initially discover and subscribe to MBS services via application-layer signaling or other means, such as pre-configuration within the device. Such service discovery signaling / configuration can provide the UE with some service identifiers for the MBS services to be subscribed to. These identifiers may include one or more Temporary Mobile Group Identifiers (TMGIs). Other names, such as nTMGI, may be used for these identifiers.

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

[0136] In some examples, a 1:1 or N:1 mapping to the service identifier can be used to map the service flow to the MBS Radio Bearer (MBR).

[0137] In some examples, a UE that has already identified a service identifier for its target MBS service can request the RAN to provide the UE with RAN-level configuration for that MBS service. In some examples, after the UE has registered with the server at the application layer, the MBS server in the network can trigger the RAN to send the MBS RAN-level configuration to the UE.

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

[0139] In such Figure 18 In some example embodiments shown, the configuration of the multicast / broadcast control channel (e.g., MCCH) associated with the UE's target MBS service (e.g., identified by nTMGI) can be provided to the UE as requested by the UE or initiated by the MBS server in the network on the UE's default active BWP on an NR or LTE carrier.

[0140] In some examples, UEs may obtain one or more service level identifiers for their target MBS services, such as nTMGI, as part of service discovery, either through application layer signaling or through other means such as device provisioning.

[0141] In some examples, the network can utilize MBS capabilities for different use cases, including multimedia broadcasting and multicast of content such as video, public safety group communications, and some Internet of Things (IoT) applications. In some examples, multiple concurrent MBS services with different service patterns, bandwidth, and latency requirements can be configured. Depending on the PHY parameter set, partial bandwidth (BWP), periodicity, and QoS requirements (including but not limited to range and reliability), the network can provide MBS data by using a mixture of different MCCH / MTCH configurations.

[0142] In some examples, the UE receiving MBS services can be in an RRC connected, idle, or inactive state, and can have different active or default partial bandwidths on NR or LTE carriers. In some examples, the UE receiving MBS data can be in different active or default BWPs for its corresponding unicast service. Example embodiments can enable MBS configuration signaling to avoid guiding the UE to track and process MBS information unrelated to its target service.

[0143] In some examples, to support different MBS use cases, the UE can be configured and / or scheduled using a mix of different and potentially concurrent multicast / broadcast control and traffic channels (e.g., MCCH / MTCH) with different PHY parameter sets, partial bandwidth (BWP), periodicity and QoS requirements and / or reliability.

[0144] In some examples, UEs within a group receiving MBS services may be in different RRC states and / or on different NR carriers / BWPs, or on LTE carriers, for their other services, such as unicast services.

[0145] In some examples, MBS RAN configuration signaling can allow the delivery of MBS control information for one of multiple MBS services delivered with multiple parameter sets, BWPs, cycles, and different reliability requirements.

[0146] In some examples, MBS RAN configuration signaling can allow for the efficient delivery of relevant MBS control information to target UEs that may be on different NR carriers / BWP or LTE carriers and in different RRC states.

[0147] In some examples, MBS configuration signaling can account for UE power savings by ensuring that the UE only tracks and processes information relevant to its target service.

[0148] In some examples, MBS RAN-level configuration information may include two parts: configuration of control channel (e.g., MCCH) transmission and configuration of scheduling of associated data channel (e.g., MTCH) transmission.

[0149] In some examples, the UE can request, on demand, an SIB indicating information for receiving the multicast / broadcast control channel (e.g., MCCH). The UE can initiate a random access procedure and can indicate a request for on-demand delivery of an SIB including information for receiving the multicast / broadcast control channel.

[0150] In some examples, unicast RRC signaling can be used to instruct the UE on multicast / broadcast control channel (e.g., MCCH) configuration.

[0151] In such Figure 19In some example embodiments shown, 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), wherein 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 example embodiments, the UE may be configured with one or more RNTIs for receiving the multicast / broadcast control channel (e.g., MCCH). In one example, one or more RNTIs may be used to identify a DCI in a configured CORESET / BWP to point to a PDSCH carrying the multicast / broadcast control channel message.

[0152] In some example embodiments, the base station may configure periodic resources (e.g., semi-persistent scheduling (SPS) or configured scheduling (CS) resources) for downlink transmission of multicast / broadcast control channels (e.g., MCCH). The periodic resources used for transmitting multicast / broadcast control channels may be pre-configured by RRC and may be activated or deactivated using DCI signaling. In some examples, configuration parameters may instruct the periodic resources to be configured on a different BWP / carrier than the one used to receive the multicast / broadcast control channels.

[0153] In some examples, the RAN can provide different MBS services with different radio and QoS configuration requirements on overlapping or disjoint groups of member UEs. Using a single MCCH configuration to schedule all multicast / broadcast data channels (e.g., MTCH) carrying MBS services with different parameter sets, BWPs, delays, periods, and reliability requirements can be limiting and negatively impact power savings for UE monitoring of such MCCH transmissions. In some example embodiments, MBS configuration signaling can allow multiple multicast / broadcast channels (e.g., MCCHs) to be configured on the same or different BWPs for scheduling MBS with different transmission frequencies, periods / timings, and reliability requirements.

[0154] In some examples, a RAN-level group identifier (e.g., nG-RNTI) can be assigned to an MBS bundle service, such as one associated with nTMGI. This nG-RNTI can be used within the RAN for DCI signaling related to multicast / broadcast data channel (e.g., MTCH) scheduling for association with an MBS service. The UE can use this nG-RNTI to track and locate the MTCH associated with the target MBS service.

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

[0156] In some examples, the multicast / broadcast control channel (e.g., MCCH) may include scheduling information for one or more channels. The UE may switch to the BWP / carrier configured in the multicast / broadcast control channel and decode the multicast / broadcast control channel to obtain information about MBS data transmission on the multicast / broadcast data channel, or receive multicast / broadcast data channel data and then switch to the default BWP if necessary.

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

[0158] In some examples, a UE that receives MBS data on different BWPs can be configured to switch back to its default / active BWP after receiving MBS information for a configurable period of time.

[0159] Figure 20 Example processes are illustrated according to one or more exemplary embodiments of this disclosure. Exemplarily, Figure 20 This illustrates methods for configuring or implementing multicast broadcast messages in UE 125 and gNB 115 implementations. (The text repeats itself here, so the translation will only include the first instance.) Figure 20 In the example embodiments shown, the UE can receive one or more messages including configuration parameters from the RAN node (exemplarily gNB 115 or 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, based on the start of a random access procedure for receiving on-demand system information, the gNB may transmit one or more messages, and the UE may receive such one or more messages. The UE can start a random access procedure by transmitting a random access preamble for receiving on-demand system information to the gNB. Based on the start of the random access procedure, the gNB may transmit one or more messages, and the UE may receive such one or more messages. In some examples, the UE may perform a service discovery procedure and may determine one or more multicast services of interest to the UE. In some examples, via a default BWP (e.g., the default BWP of the primary cell), the gNB may transmit one or more messages, and the UE may receive such one or more messages.

[0160] In some examples, a UE may receive one or more messages based on a transition from an RRC idle state to an RRC connected state or from an RRC inactive state to an RRC connected state. A UE may also 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 procedure that indicates one or more multicast services of interest to the UE.

[0161] In some examples, configuration parameters may indicate that one or more multicast broadcast services are associated with one or more first cores. In some examples, configuration parameters may indicate that one or more multicast broadcast services are associated with one or more first bandwidth windows (BWPs). In some examples, configuration parameters may indicate that one or more multicast broadcast services are associated with at least one of the following: one or more first cores and a first portion bandwidth (BWP). In some examples, one or more messages may include configuration parameters of one or more first cores on one or more first BWPs. One or more multicast broadcast services may be associated with one or more first cores based on scheduling information received via one or more first cores to receive multicast broadcast control information associated with one or more multicast broadcast services. One or more multicast broadcast services may be associated with one or more first BWPs based on scheduling information received via one or more first BWPs to receive multicast broadcast control information associated with one or more multicast broadcast services.

[0162] One or more messages may also include one or more first RNTIs associated with one or more multicast services. Cyclic Redundancy Check (CRC) bits of downlink control information indicating scheduling information for one or more downlink transport blocks may be scrambled using RNTIs from one or more first RNTIs. One or more transport blocks may include control information for one or more multicast services.

[0163] The UE can receive one or more downlink control messages associated with one or more first RNTIs. In some examples, one or more multicast broadcast services can be associated with service identifiers (e.g., TMGI, etc.), and one or more RNTIs can be associated with one or more service identifiers. The CRC bits of one or more downlink control messages can be scrambled using one or more first RNTIs. The UE can receive one or more downlink control messages via one or more first CORESETs and / or via one or more first BWPs. In some examples, the UE can determine that one or more downlink control messages are associated with one or more multicast broadcast services based on receiving one or more downlink control messages via one or more first CORESETs and / or one or more first BWPs. In some examples, the UE can determine that one or more downlink control messages are associated with one or more multicast broadcast services based on one or more downlink control messages associated with one or more first RNTIs.

[0164] The UE can 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 receiving the one or more transport blocks. The one or more transport blocks may be associated with one or more multicast services. The one or more transport blocks may include control information for receiving one or more service / data channels associated with one or more multicast services.

[0165] In such Figure 21 In the example embodiment shown, the UE may receive configuration parameters for a semi-persistent scheduling (SPS) configuration. The UE may use the SPS configuration parameters to determine SPS resources. The UE may determine SPS resources based on the SPS configuration and based on an activation DCI indicating the activation of the SPS configuration. The UE may receive an activation DCI indicating the activation of the SPS configuration. The SPS configuration may be associated with one or more multicast services. The SPS configuration parameters may indicate that the SPS configuration is associated with one or more multicast services. In some examples, the SPS configuration parameters may include an SPS configuration identifier indicating that the SPS configuration is associated with one or more multicast services.

[0166] Wireless devices can determine SPS resources based on SPS configuration parameters (e.g., in conjunction with activated DCI). Wireless devices can receive one or more transport blocks via SPS resources. One or more transport blocks can be associated with one or more multicast / broadcast services. One or more transport blocks can include control information for receiving one or more service / data channels associated with one or more multicast / broadcast services.

[0167] In some examples, one or more transport blocks associated with one or more multicast broadcast services and including control information for one or more multicast broadcast services may include one or more of the following: one or more service identifiers for 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 one or more service identifiers, such as for receiving multicast broadcast traffic channels associated with one or more multicast broadcast services; one or more BWP identifiers for receiving one or more BWPs for one or more multicast broadcast services; one or more parameter sets for receiving one or more multicast broadcast services (e.g., subcarrier spacing or cyclic prefixes associated with one or more BWPs); one or more quality of service requirements for one or more multicast broadcast services (e.g., delay, jitter, throughput, etc.); and related information. One or more periods associated with one or more multicast broadcast services (e.g., periods for receiving the one or more multicast broadcast control information or periods for receiving the one or more multicast broadcast service channels); one or more cell identifiers for one or more cells for receiving 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 one or more multicast broadcast services (e.g., a first DRX parameter, such as a first inactivity timer value or a first on-duration value associated with a first multicast broadcast service channel, and a second DRX parameter, such as a second inactivity timer value or a second on-duration timer value associated with a second multicast broadcast service channel); and a list of neighboring cell information indicating one or more neighboring cells (e.g., neighboring cells where one or more multicast broadcast services are available) for receiving the one or more multicast broadcast services, etc.

[0168] In some examples, the UE can switch to a first BWP (e.g., from the currently active BWP to the first BWP) to receive one or more multicast broadcast services. The first BWP can be a BWP where multicast broadcast services are available (e.g., a multicast broadcast service channel is being transmitted). In some examples, the UE can switch to a second BWP (e.g., the previous active BWP or the default BWP) after a certain period (e.g., a configurable time) since switching to the first BWP. The UE can start a timer based on the switch to the first BWP and can switch to the second BWP based on the timer expiring. Configuration parameters can indicate the timer value.

[0169] In one embodiment, the 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 the following: a first control resource set (CORESET) and a first portion bandwidth (BWP); and one or more first radio network temporary identifiers (RNTIs) associated with one or more multicast broadcast services. The UE may receive one or more downlink control information associated with one or more first RNTIs via the first CORESET or the first BWP. The UE may receive one or more transport blocks associated with 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 of the first CORESET on the first BWP.

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

[0171] 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 the activation of the SPS configuration.

[0172] 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 indicates at least one of the following: one or more service identifiers for one or more multicast broadcast services; one or more second RNTIs for receiving downlink data associated with one or more service identifiers; one or more BWP identifiers for receiving one or more BWPs for one or more multicast broadcast services; one or more parameter sets 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 periods associated with one or more multicast broadcast services; one or more cell identifiers for receiving one or more cells for 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 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. In some embodiments, 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 first inactivity timer value and a first on-duration timer value. The second DRX parameter may be one or more of a second inactivity timer value and a second on-duration timer value.

[0173] In some embodiments, control information may be associated with a multicast control logic channel.

[0174] In some embodiments, one or more BWPs are associated with one or more parameter sets; and one or more multicast broadcast services are associated with one or more parameter sets.

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

[0176] In some embodiments, one or more messages may include one or more Radio Resource Control (RRC) messages.

[0177] In some embodiments, one or more messages may include a System Information Block (SIB) associated with a multicast broadcast service.

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

[0179] In some embodiments, receiving one or more messages may be based on a service discovery process that indicates one or more multicast broadcast services that the UE is interested in.

[0180] In some embodiments, the UE may receive one or more service identifiers of one or more multicast broadcast services that the UE is interested in during the service discovery process.

[0181] In some embodiments, receiving one or more messages can be done via the default BWP.

[0182] In some embodiments, receiving one or more messages may be done via the primary cell's default BWP.

[0183] In some embodiments, receiving 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.

[0184] 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 can be based on a service discovery process that indicates one or more multicast broadcast services that the UE is interested in.

[0185] In some embodiments, the UE may switch to a first BWP for receiving one or more broadcast multicast services. The UE may switch to a second BWP after a first duration following the switch to the first BWP.

[0186] In some embodiments, the second BWP can be the default BWP.

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

[0188] In some embodiments, the UE may start a timer based on switching to the first BWP.

[0189] In some embodiments, switching to a second BWP can be based on the expiration of a timer.

[0190] The exemplary blocks and modules described in this disclosure with respect to various example embodiments 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 devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Examples of general-purpose processors include, but are not limited to, microprocessors, any conventional processor, controllers, microcontrollers, or state machines. 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 combined with a DSP core, or any other such configuration).

[0191] The functions described in this disclosure can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. Instructions or code can be stored or transmitted on a computer-readable medium for implementing these functions. Other examples of implementing the functions disclosed herein are also within the scope of this disclosure. Implementation of functions can be via physically co-located or distributed elements (e.g., in different locations), including distributions such that partial functions are implemented in different physical locations.

[0192] 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 disk (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 source (e.g., a website, 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 within the scope of the media definition. The combinations of the above examples are also within the scope of computer-readable media.

[0193] As used in this disclosure, the use of the term "or" in a list of items indicates a comprehensive list. A list of items may be prefixed with phrases such as "at least one" or "one or more." 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 and B and C). Furthermore, as used in this disclosure, a list of conditions prefixed with the phrase "based on" should not be interpreted as "based only on" the set of conditions, but rather as "at least partially based on" the set of conditions. For example, a result described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure.

[0194] In this specification, the terms "comprising," "containing," or "including" are used interchangeably and have the same meaning, and are interpreted as inclusive and open-ended. The terms "comprising," "containing," or "including" may precede a list of elements and indicate that at least all listed elements are present, but other elements not listed may also be present. For example, if A includes B and C, then {B, C} and {B, C, D} are both within the scope of A.

[0195] With reference to the accompanying drawings, this disclosure describes example configurations that do not represent all possible examples or all configurations within the scope of this disclosure. The term "exemplary" should not be construed as "preferred" or "advantageous compared to other examples," but rather as "illustration, instance, or example." By reading this disclosure, including the description of embodiments and accompanying drawings, those skilled in the art will understand that alternative embodiments can be used to implement the techniques disclosed herein. Those skilled in the art will appreciate that the embodiments described herein or certain features of the embodiments can be combined to obtain other embodiments for practicing the techniques described in this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0196] Clause 1. Wireless communication methods, including:

[0197] The user equipment (UE) receives one or more messages, the one or more messages including:

[0198] Configuration parameters that indicate one or more multicast broadcast services are associated with at least one of the following:

[0199] First control resource set (CORESET); and

[0200] First-part bandwidth (BWP); and

[0201] One or more first radio network temporary identifiers (RNTIs) associated with the one or more multicast broadcast services;

[0202] The UE receives downlink control information associated with one or more first RNTIs; and

[0203] Based on the downlink control information, one or more transport blocks associated with the one or more multicast broadcast services are received.

[0204] Clause 2. The wireless communication method as described in Clause 1, wherein the configuration parameters include the first configuration parameters of the first CORESET or the first BWP.

[0205] Clause 3. The wireless communication method as described in Clause 1, wherein the one or more transport blocks include control information associated with the one or more multicast broadcast services.

[0206] Clause 4. The wireless communication method as described in Clause 1, wherein the configuration parameters further include data indicating the following:

[0207] One or more first service identifiers associated with the one or more multicast broadcast services; and

[0208] One or more first RNTIs associated with the first service identifier.

[0209] Clause 5. The wireless communication method as described in Clause 1, wherein the one or more messages include one or more Radio Resource Control (RRC) messages.

[0210] Clause 6. The wireless communication method as described in Clause 1, wherein the one or more messages include a System Information Block (SIB) associated with the multicast broadcast service.

[0211] Clause 7. The wireless communication method as described in Clause 1, wherein receiving the one or more messages is based on a random access procedure for receiving on-demand system information.

[0212] Clause 8. The wireless communication method as described in Clause 1, wherein receiving the one or more messages is performed based on a service discovery process that identifies one or more multicast broadcast services among the multicast broadcast services.

[0213] Clause 9. The wireless communication method as described in Clause 8 further includes: during the service discovery process, receiving one or more service identifiers of the one or more multicast broadcast services.

[0214] Clause 10. The wireless communication method as described in Clause 1, wherein the reception of the one or more messages is performed via a default BWP.

[0215] Clause 11. The wireless communication method as described in Clause 10, wherein receiving the one or more messages includes receiving the one or more messages via the default BWP of the primary cell.

[0216] Clause 12. The wireless communication method as described in Clause 1, wherein receiving the one or more messages comprises receiving the 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.

[0217] Clause 13. The wireless communication method as described in Clause 12, wherein 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 of interest to the UE.

[0218] Clause 14. The wireless communication method as described in Clause 1 further includes:

[0219] Switch to the first BWP for receiving the one or more broadcast multicast services; and

[0220] Switch to the second BWP after a first duration following the switch to the first BWP.

[0221] Clause 15. The wireless communication method as described in Clause 14, wherein the second BWP is the default BWP.

[0222] Clause 16. The wireless communication method as described in Clause 14, wherein the second BWP is an active BWP before switching to the first BWP.

[0223] Clause 17. The wireless communication method as described in Clause 14, further comprising starting a timer based on switching to the first BWP.

[0224] Clause 18. The wireless communication method as described in Clause 17, wherein the switching to the second BWP is performed based on the expiration of the timer.

[0225] Clause 19. Wireless communication methods, including:

[0226] Receive configuration parameters for a semi-persistent scheduling (SPS) configuration associated with one or more multicast broadcast services; and

[0227] Based on the SPS resources associated with the SPS configuration, receive one or more transport blocks associated with the one or more multicast broadcast services.

[0228] Clause 20. The wireless communication method as described in Clause 19, wherein the configuration parameters include a first identifier indicating that the SPS configuration is associated with the one or more multicast broadcast services.

[0229] Clause 21. The wireless communication method as described in Clause 19 further includes receiving downlink control information indicating activation of the SPS configuration.

[0230] Clause 22. The wireless communication method as described in Clause 19, wherein the one or more transport blocks include control information associated with the one or more multicast broadcast services.

[0231] Clause 23. The wireless communication method as described in Clause 22, wherein the control information is associated with one or more multicast broadcast control logic channels.

[0232] Clause 24. The wireless communication method as described in Clause 22, wherein the control information indicates at least one of the following:

[0233] One or more service identifiers used for the one or more multicast broadcast services;

[0234] One or more second RNTIs are used to receive downlink data associated with the one or more service identifiers;

[0235] One or more parameter sets for receiving the one or more multicast broadcast services;

[0236] One or more Quality of Service (QoS) requirements for the one or more multicast broadcast services;

[0237] One or more periods associated with the one or more multicast broadcast services;

[0238] One or more cell identifiers for one or more cells to receive the one or more multicast broadcast services; and

[0239] This indicates a list of neighboring cell information for one or more neighboring cells used to receive the one or more multicast broadcast services.

[0240] Clause 25. The wireless communication method as described in 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 the one or more multicast broadcast services.

[0241] Clause 26. The wireless communication method as described in Clause 25, wherein the one or more DRX parameters include a first DRX parameter associated with a first multicast broadcast service channel and a second DRX parameter associated with a second multicast broadcast service channel.

[0242] Clause 27. The wireless communication method as described in Clause 26, wherein the first DRX parameter is one or more of a first inactivity timer value and a first on-duration timer value; and the second DRX parameter is one or more of a second inactivity timer value and a second on-duration timer value.

[0243] Clause 28. The wireless communication method as described in Clause 22, wherein the control information indicates one or more BWP identifiers for receiving one or more BWPs of the one or more multicast broadcast services.

[0244] Clause 29. The wireless communication method as described in Clause 22, wherein the control information indicates one or more BWP identifiers for receiving one or more BWPs of the one or more multicast broadcast services.

[0245] Clause 30. The wireless communication method as described in Clause 29, wherein the one or more BWPs are associated with the one or more parameter sets; and the one or more multicast broadcast services are associated with the one or more parameter sets.

[0246] Clause 31. A device for use in wireless communication, comprising:

[0247] An antenna, used to transmit electromagnetic signals;

[0248] Memory, which is used to hold computer-readable code; and

[0249] A processor for executing the computer-readable code, the computer-readable code causing the device to:

[0250] Receive one or more messages, the one or more messages including:

[0251] Configuration parameters that indicate one or more multicast broadcast services are associated with at least one of the following:

[0252] First control resource set (CORESET); and

[0253] First-part bandwidth (BWP); and

[0254] One or more first radio network temporary identifiers (RNTIs) associated with the one or more multicast broadcast services;

[0255] Receive downlink control information associated with the one or more first RNTIs; and

[0256] Based on the downlink control information, one or more transport blocks associated with the one or more multicast broadcast services are received.

[0257] Clause 32. The apparatus as described in Clause 31, wherein the configuration parameters include the first configuration parameters of the first CORESET or the first BWP.

[0258] Clause 33. The apparatus as described in Clause 31, wherein the one or more transport blocks include control information associated with the one or more multicast broadcast services.

[0259] Clause 34. The apparatus as described in Clause 31, wherein the configuration parameters further include data indicating the following:

[0260] One or more first service identifiers associated with the one or more multicast broadcast services; and

[0261] One or more first RNTIs associated with the first service identifier.

[0262] Clause 35. The apparatus as described in Clause 31, wherein the one or more messages include one or more Radio Resource Control (RRC) messages.

[0263] Clause 36. The apparatus as described in Clause 31, wherein the one or more messages include a System Information Block (SIB) associated with the multicast broadcast service.

[0264] Clause 37. The apparatus as described in Clause 31, wherein receiving the one or more messages is based on a random access procedure for receiving on-demand system information.

[0265] Clause 38. The apparatus as described in Clause 31, wherein receiving the one or more messages is based on a service discovery process that identifies one or more multicast broadcast services among the multicast broadcast services.

[0266] Clause 39. The apparatus as described in Clause 38 further includes receiving one or more service identifiers of the one or more multicast broadcast services during the service discovery process.

[0267] Clause 40. Wireless communication methods, including:

[0268] One or more messages are transmitted by the radio access node (RAN), the one or more messages including:

[0269] Configuration parameters that indicate one or more multicast broadcast services are associated with at least one of the following:

[0270] First control resource set (CORESET); and

[0271] First-part bandwidth (BWP); and

[0272] One or more first radio network temporary identifiers (RNTIs) associated with the one or more multicast broadcast services;

[0273] The RAN transmits downlink control information associated with the one or more first RNTIs; and

[0274] Based on the downlink control information, one or more transport blocks associated with the one or more multicast broadcast services are transmitted.

[0275] Clause 41. The wireless communication method as described in Clause 40, wherein the configuration parameters include the first configuration parameters of the first CORESET or the first BWP.

[0276] Clause 42. The wireless communication method as described in Clause 40, wherein the one or more transport blocks include control information associated with the one or more multicast broadcast services.

[0277] Clause 43. The wireless communication method as described in Clause 40, wherein the configuration parameters further include data indicating the following:

[0278] One or more first service identifiers associated with the one or more multicast broadcast services; and

[0279] One or more first RNTIs associated with the first service identifier.

[0280] Clause 44. The wireless communication method as described in Clause 40, wherein the one or more messages include one or more Radio Resource Control (RRC) messages.

[0281] Clause 45. The wireless communication method as described in Clause 40, wherein the one or more messages include a System Information Block (SIB) associated with the multicast broadcast service.

[0282] Clause 46. The wireless communication method as described in Clause 40, wherein the transmission of the one or more messages is based on a random access procedure for receiving on-demand system information.

[0283] Clause 47. The wireless communication method as described in Clause 40, wherein the transmission of the one or more messages is based on a service discovery process that identifies one or more multicast broadcast services among the multicast broadcast services.

[0284] Clause 48. The wireless communication method as described in Clause 47 further includes transmitting one or more service identifiers of the one or more multicast broadcast services during the service discovery process.

[0285] Clause 49. The wireless communication method as described in Clause 40, wherein the transmission of the one or more messages is performed via a default BWP.

[0286] Clause 50. The wireless communication method as described in Clause 49, wherein the transmission of the one or more messages includes transmitting the one or more messages via the default BWP of the primary cell.

[0287] Clause 51. The wireless communication method as described in Clause 40, wherein transmitting the one or more messages comprises transmitting the 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.

[0288] Clause 52. The wireless communication method as described in Clause 51, wherein 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 instructs one or more multicast broadcast service UEs.

[0289] Clause 53. The wireless communication method as described in Clause 40 further includes:

[0290] Switch to the first BWP for transmitting the one or more broadcast multicast services; and

[0291] Switch to the second BWP after a first duration following the switch to the first BWP.

[0292] Clause 54. The wireless communication method as described in Clause 53, wherein the second BWP is the default BWP.

[0293] Clause 55. The wireless communication method as described in Clause 53, wherein the second BWP is an active BWP before switching to the first BWP.

[0294] Clause 56. The wireless communication method as described in Clause 53 further includes starting a timer based on switching to the first BWP.

[0295] Clause 57. The wireless communication method as described in Clause 55, wherein the switching to the second BWP is performed based on the expiration of the timer.

[0296] Clause 58. Wireless communication methods, including:

[0297] Configuration parameters for transmitting semi-persistent scheduling (SPS) configurations associated with one or more multicast broadcast services; and

[0298] Based on the SPS resources associated with the SPS configuration, transmit one or more transport blocks associated with the one or more multicast broadcast services.

[0299] Clause 59. The wireless communication method as described in Clause 58, wherein the configuration parameters include a first identifier indicating that the SPS configuration is associated with the one or more multicast broadcast services.

[0300] Clause 60. The wireless communication method as described in Clause 58 further includes transmitting downlink control information indicating the activation of the SPS configuration.

[0301] Clause 61. The wireless communication method as described in Clause 58, wherein the one or more transport blocks include control information associated with the one or more multicast broadcast services.

[0302] Clause 62. The wireless communication method as described in Clause 61, wherein the control information is associated with one or more multicast broadcast control logic channels.

[0303] Clause 63. The wireless communication method as described in Clause 61, wherein the control information indicates at least one of the following:

[0304] One or more service identifiers used for the one or more multicast broadcast services;

[0305] One or more second RNTIs are used to receive downlink data associated with the one or more service identifiers;

[0306] One or more parameter sets for receiving the one or more multicast broadcast services;

[0307] One or more Quality of Service (QoS) requirements for the one or more multicast broadcast services;

[0308] One or more periods associated with the one or more multicast broadcast services;

[0309] One or more cell identifiers for one or more cells to receive the one or more multicast broadcast services; and

[0310] This indicates a list of neighboring cell information for one or more neighboring cells used to receive the one or more multicast broadcast services.

[0311] Clause 64. The wireless communication method as described in Clause 61, wherein the control information indicates 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.

[0312] Clause 65. The wireless communication method as described in Clause 64, wherein the one or more DRX parameters include a first DRX parameter associated with a first multicast broadcast service channel and a second DRX parameter associated with a second multicast broadcast service channel.

[0313] Clause 66. The wireless communication method as described in Clause 65, wherein the first DRX parameter is one or more of a first inactive timer value and a first on-duration timer value; and the second DRX parameter is one or more of a second inactive timer value and a second on-duration timer value.

[0314] Clause 67. The wireless communication method as described in Clause 61, wherein the control information indicates one or more BWP identifiers for receiving one or more BWPs of the one or more multicast broadcast services.

[0315] Clause 68. The wireless communication method as described in Clause 61, wherein the control information indicates one or more BWP identifiers for receiving one or more BWPs of the one or more multicast broadcast services.

[0316] Clause 69. The wireless communication method as described in Clause 68, wherein the one or more BWPs are associated with the one or more parameter sets; and the one or more multicast broadcast services are associated with the one or more parameter sets.

[0317] Clause 70. A device for use in wireless communication, comprising:

[0318] An antenna, used to transmit electromagnetic signals;

[0319] Memory, which is used to hold computer-readable code; and

[0320] A processor for executing the computer-readable code, the computer-readable code causing the device to:

[0321] Transmit one or more messages, the one or more messages including:

[0322] Configuration parameters that indicate one or more multicast broadcast services are associated with at least one of the following:

[0323] First control resource set (CORESET); and

[0324] First-part bandwidth (BWP); and

[0325] One or more first radio network temporary identifiers (RNTIs) associated with the one or more multicast broadcast services;

[0326] Transmitting downlink control information associated with the one or more first RNTIs; and

[0327] Based on the downlink control information, one or more transport blocks associated with the one or more multicast broadcast services are transmitted.

[0328] Clause 71. The apparatus as described in Clause 70, wherein the configuration parameters include the first configuration parameters of the first CORESET or the first BWP.

[0329] Clause 72. The apparatus as described in Clause 70, wherein the one or more transport blocks include control information associated with the one or more multicast broadcast services.

[0330] Clause 73. The apparatus as described in Clause 70, wherein the configuration parameters further include data indicating the following:

[0331] One or more first service identifiers associated with the one or more multicast broadcast services; and

[0332] One or more first RNTIs associated with the first service identifier.

[0333] Clause 74. The apparatus as described in Clause 70, wherein the one or more messages include one or more Radio Resource Control (RRC) messages.

[0334] Clause 75. The apparatus as described in Clause 70, wherein the one or more messages include a System Information Block (SIB) associated with a multicast broadcast service.

[0335] Clause 76. The apparatus as described in Clause 70, wherein the transmission of the one or more messages is based on a random access procedure for receiving on-demand system information.

[0336] Clause 77. The apparatus as described in Clause 70, wherein the transmission of the one or more messages is based on a service discovery process that identifies one or more multicast broadcast services among the multicast broadcast services.

[0337] Clause 78. The apparatus as described in Clause 77, wherein the apparatus is further operated to transmit one or more service identifiers of the one or more multicast broadcast services during the service discovery process.

[0338] This application claims the benefit of U.S. Provisional Application No. 63 / 073,732, filed September 2, 2020, entitled “SYSTEM AND METHOD FOR MAINTAININGMULTICAST BROADCAST SERVICE”. U.S. Provisional Application No. 63 / 073,732 is incorporated herein by reference.

Claims

1. A method of wireless communication performed by a user equipment, the method comprising: receiving one or more configuration parameters of a semi-persistent scheduling, the one or more configuration parameters of the semi-persistent scheduling being associated with one or more multicast broadcast services and configured per partial bandwidth by radio resource control; receiving a downlink control information indicating an activation of an allocation based on the semi-persistent scheduling; and receiving data associated with the one or more multicast broadcast services based on the allocation activated by the downlink control information, wherein a plurality of allocations can be activated simultaneously in the partial bandwidth.

2. The method of wireless communication of claim 1, further comprising: receiving a downlink control signal indicating a deactivation of the allocation based on the semi-persistent scheduling, stopping reception of data associated with the one or more multicast broadcast services based on the downlink control signal indicating the deactivation of the allocation.

3. A method of wireless communication performed by a radio access node, comprising: transmitting one or more configuration parameters of a semi-persistent scheduling, the one or more configuration parameters of the semi-persistent scheduling being associated with one or more multicast broadcast services and configured per partial bandwidth by radio resource control; transmitting a downlink control information indicating an activation of an allocation based on the semi-persistent scheduling; and transmitting data associated with the one or more multicast broadcast services based on the allocation activated by the downlink control information, wherein a plurality of allocations can be activated simultaneously in the partial bandwidth.

4. A user equipment comprising a controller comprising one or more processors that perform: receiving one or more configuration parameters of a semi-persistent scheduling, the one or more configuration parameters of the semi-persistent scheduling being associated with one or more multicast broadcast services and configured per partial bandwidth by radio resource control; receiving a downlink control information indicating an activation of an allocation based on the semi-persistent scheduling; and receiving data associated with the one or more multicast broadcast services based on the allocation activated by the downlink control information, wherein a plurality of allocations can be activated simultaneously in the partial bandwidth.

5. A radio access node comprising a controller comprising one or more processors that perform: transmitting one or more configuration parameters of a semi-persistent scheduling, the one or more configuration parameters of the semi-persistent scheduling being associated with one or more multicast broadcast services and configured per partial bandwidth by radio resource control; transmitting a downlink control information indicating an activation of an allocation based on the semi-persistent scheduling; and transmitting data associated with the one or more multicast broadcast services based on the allocation activated by the downlink control information, wherein a plurality of allocations can be activated simultaneously in the partial bandwidth.

Images