CN117616729A

CN117616729A - User equipment and method for handling physical downlink shared channel reception

Info

Publication number: CN117616729A
Application number: CN202280044948.XA
Authority: CN
Inventors: 汪海瀚; 魏嘉宏; 陈宏镇
Original assignee: FG Innovation Co Ltd
Current assignee: FG Innovation Co Ltd
Priority date: 2021-08-06
Filing date: 2022-08-05
Publication date: 2024-02-27

Abstract

A method of handling PDSCH reception by a UE includes receiving, from a BS, a first PDSCH configuration in a CFR configuration for a multicast PDSCH, a second PDSCH configuration in a BWP configuration for a unicast PDSCH, the first PDSCH configuration including a first aperiodic resource set configuration, the second PDSCH configuration including a resource configuration and a second aperiodic resource set configuration, the resource configuration for configuring one or more ZP CSI-RS resources, and the first DCI including a first field for triggering the first aperiodic ZP CSI-RS; and determining, based on the first field, a first set of ZP CSI-RS resources determined from a first list of ZP CSI-RS resource sets configured by the first aperiodic resource set configuration that are unavailable to receive the multicast PDSCH. There is no resource configuration in the first PDSCH configuration.

Description

User equipment and method for handling physical downlink shared channel reception

Technical Field

The present application relates to wireless communications, and more particularly, to a User Equipment (UE) and a method for handling physical downlink shared channel (physical downlink shared channel, PDSCH) reception in a next generation wireless communication network.

Background

With the tremendous increase in the number of connected devices and the rapid increase in user/network traffic, various efforts have been made to improve various aspects of wireless communication of next generation wireless communication systems, such as fifth generation (5G) New Radio (NR), by increasing data rates, delays, reliability, and mobility.

The 5G NR system aims to provide flexibility and configurability to optimize network services and types, adapting to various use cases, such as enhanced mobile broadband (eMBB), large-scale Machine-type communication (emtc), and Ultra-Reliable and Low-delay communication (URLLC).

However, as the demand for radio access continues to increase, further improvements in wireless communication of the next wireless communication system are needed.

Disclosure of Invention

The present application relates to a method of handling PDSCH reception by a UE.

According to a first aspect of the present application, there is provided a method performed by a UE of processing PDSCH reception. The method comprises receiving a first PDSCH configuration from a base station BS among common frequency resource, CFR, configurations for multicast PDSCH, the first PDSCH configuration comprising a first aperiodic resource set configuration; receiving a second PDSCH configuration from the BS in a bandwidth portion, BWP, configuration for unicast PDSCH, the second PDSCH configuration including a resource configuration for configuring one or more zero-power ZP channel state information-reference signal, CSI-RS, resources and a second aperiodic resource set configuration; receiving first downlink control information, DCI, scheduling the multicast PDSCH from the BS, the first DCI including a first field for triggering a first aperiodic ZP CSI-RS; and determining, based on the first field, a first set of ZP CSI-RS resources that are unavailable to receive the multicast PDSCH from a first list of ZP CSI-RS resource sets configured by the first aperiodic resource set configuration, wherein: the resource configuration is absent from the first PDSCH configuration and each of the first list of ZP CSI-RS resource sets includes at least one of one or more ZP CSI-RS resources.

According to a first aspect of the present application, the method further comprises receiving a second DCI scheduling the unicast PDSCH from the BS, the second DCI comprising a second field for triggering a second aperiodic ZP CSI-RS; and determining a second set of ZP CSI-RS resources based on the second field, the second set of ZP CSI-RS resources not being available to receive the unicast PDSCH from a second list of ZP CSI-RS resources configured by the second aperiodic resource set configuration, wherein each of the second list of ZP CSI-RS resource sets comprises at least one of one or more ZP CSI-RS resources.

According to a second aspect of the present application, there is provided a user equipment, UE, for handling physical downlink shared channel, PDSCH, reception, the UE comprising one or more non-transitory computer-readable media embodying computer-executable instructions; and at least one processor coupled to the one or more non-transitory computer-readable media, the at least one processor configured to execute the computer-executable instructions to cause the UE to receive a first PDSCH configuration from a base station BS among common frequency resource CFR configurations for multicast PDSCH, the first PDSCH configuration including a first aperiodic resource set configuration; receiving a second PDSCH configuration from the BS in a bandwidth portion, BWP, configuration for unicast PDSCH, the second PDSCH configuration including a resource configuration for configuring one or more zero-power ZP channel state information-reference signal, CSI-RS, resources and a second aperiodic resource set configuration; receiving first downlink control information, DCI, scheduling the multicast PDSCH from the BS, the first DCI including a first field for triggering a first aperiodic ZP CSI-RS; and determining, based on the first field, a first set of ZP CSI-RS resources that are unavailable to receive the multicast PDSCH from a first list of ZP CSI-RS resource sets configured by the first aperiodic resource set configuration, wherein: the resource configuration is absent from the first PDSCH configuration and each of the first list of ZP CSI-RS resource sets includes at least one of one or more ZP CSI-RS resources.

According to a third aspect of the present application, there is provided a method performed by a base station BS for handling physical downlink shared channel, PDSCH, transmissions, the method comprising: transmitting a first PDSCH configuration among common frequency resource CFR configurations for a multicast PDSCH to a user equipment UE, the first PDSCH configuration including a first aperiodic resource set configuration; transmitting, to the UE, a second PDSCH configuration of the bandwidth part BWP configurations for unicast PDSCH, the second PDSCH configuration including a resource configuration for configuring one or more zero-power ZP channel state information-reference signal CSI-RS resources and a second aperiodic resource set configuration; and transmitting first downlink control information, DCI, to the UE, scheduling the multicast PDSCH, the first DCI including a first field for triggering a first aperiodic ZP CSI-RS, wherein: the first field enables the UE to determine a first set of ZP CSI-RS resources unavailable to receive the multicast PDSCH from a first list of ZP CSI-RS resource sets configured by the first aperiodic resource set configuration, the resource configuration is absent from the first PDSCH configuration, and each of the first list of ZP CSI-RS resource sets includes at least one of one or more ZP CSI-RS resources.

According to a fourth aspect of the present application, there is provided a base station, BS, for processing PDSCH transmissions, the BS comprising: one or more non-transitory computer-readable media embodying computer-executable instructions; and at least one processor coupled to the one or more non-transitory computer-readable media, the at least one processor configured to execute the computer-executable instructions to cause the BS to transmit a first PDSCH configuration of the common frequency resource CFR configurations for multicast PDSCH to a user equipment UE, the first PDSCH configuration including a first aperiodic resource set configuration; transmitting, to the UE, a second PDSCH configuration of the bandwidth part BWP configurations for unicast PDSCH, the second PDSCH configuration including a resource configuration for configuring one or more zero-power ZP channel state information-reference signal CSI-RS resources and a second aperiodic resource set configuration; and transmitting first downlink control information, DCI, to the UE, scheduling the multicast PDSCH, the first DCI including a first field for triggering a first aperiodic ZP CSI-RS, wherein: the first field enables the UE to determine a first set of ZP CSI-RS resources unavailable to receive the multicast PDSCH from a first list of ZP CSI-RS resource sets configured by the first aperiodic resource set configuration, the resource configuration is absent from the first PDSCH configuration, and each of the first list of ZP CSI-RS resource sets includes at least one of one or more ZP CSI-RS resources.

Drawings

Aspects of the present exemplary disclosure are best understood from the following detailed description when read with the accompanying drawing figures. The various features are not drawn to scale for clarity of discussion and the dimensions of the various features may be arbitrarily increased or reduced.

Fig. 1 is a flow diagram for performing an SDT procedure performed by a UE, shown according to one of the exemplary embodiments of the present application.

Fig. 2 is a flowchart of a method 200 performed by a UE for processing PDSCH reception according to one of the example embodiments of the present application.

Fig. 3 is a flowchart of a method performed by a BS for processing PDSCH transmissions according to one of the exemplary embodiments of the present application.

Fig. 4 is a flowchart of a method performed by a BS for processing PDSCH transmissions according to one of the exemplary embodiments of the present application.

Fig. 5 is a block diagram of a node for wireless communication according to one of the exemplary embodiments of the present application.

Detailed Description

The abbreviations in this application are defined as follows, with the following meanings unless otherwise indicated: abbreviation full scale

Third generation partnership project (3^rd Generation Partnership Project,3GPP)

Fifth generation (5th Generation,5G)

5G core network (5G core,5 GC)

Acknowledgement (ACK)

Automatic repeat request (Automatic Repeat Request, ARQ)

Bandwidth adaptation (Bandwidth Adaptation, BA)

Base Station (Base Station, BS)

Base station Controller (BS Controller, BSC)

Bandwidth portion (Bandwidth portion, BWP)

Cell radio network temporary identity (Cell-Radio Network Temporary Identifier, C-RNTI)

Carrier aggregation (Carrier Aggregation, CA)

Public frequency resource (Common Frequency Resource, CFR)

Core Network (Core Network, CN)

Control resource set (Control Resource Set, CORESET)

Cyclic Prefix (CP)

Cyclic redundancy check (Cyclic Redundancy Check, CRC)

Configuring a scheduling radio network temporary identity (Configured Scheduling-RNTI, CS-RNTI)

Channel state information reference signal (Channel State Information Reference Signal, CSI-RS)

Public search space (Common Search Space, CSS)

Downlink allocation index (Downlink Assignment Index, DAI)

Double connection (Dual Connectivity DC)

Downlink control information (Downlink Control Information, DCI)

Downlink (DL)

Data radio bearer (Data Radio Bearer, DRB)

Evolved universal terrestrial radio Access (Network) (Evolved Universal Terrestrial Radio Access, E-UTRA (N))

Enhanced mobile broadband (enhanced Mobile Broadband, eMBB)

Evolution Node B (evolved Node B, eNB)

Double ligation E-UTRA NR (E-UTRA NR Dual Connectivity, EN-DC)

Evolved packet core network (Evolved Packet Core, EPC)

Frequency domain resource allocation (Frequency Domain Resource Assignment, FDRA)

Forward error correction (Forward Error Correction, FEC)

Radio network temporary identifier (Group-Radio Network Temporary Identifier, G-RNTI)

Next generation node B (Next Generation Node B, gNB)

Global system for mobile communications (Global System for Mobile communications, GSM)

Hybrid automatic repeat request (Hybrid Automatic Repeat request, HARQ)

Hybrid automatic repeat request acknowledgement (Hybrid Automatic Repeat request acknowledgement, HARQ-ACK) Identity (ID)

Information element (Information Elements, IE)

Logical channel identification (Logical Channel Identifier, LCID)

Low Density Parity Check code (LDPC)

Long Term Evolution (LTE)

Advanced long term evolution (LTE-Advanced, LTE-A)

Least significant bit (Least Significant Bit, LSB)

Media access control (Medium Access Control, MAC)

Media access control element (Medium Access Control Control Element, MAC CE)

Multicast broadcast service (Multicast Broadcast Service, MBS)

Multicast control channel (Multicast Control Channel, MCCH)

Main cell group (Master Cell Group, MCG)

Modulation and coding strategy (Modulation and Coding Scheme, MCS)

MCS radio network temporary identifier (MCS Common-Radio Network Temporary Identifier, MCS-C-RNTI)

Main eNB (Master eNB, meNB)

Large Scale Machine communication (massive Machine-Type Communication, mMTC)

Main Node (Master Node, MN)

Multi-RAT dual connectivity (Multi-RAT Dual Connectivity, MR-DC)

Most significant bit (Most Significant Bit, MSB)

Message B (Message B, MSGB)

Negative acknowledgement (Negative Acknowledgment, NACK)

Node B (Node, NB)

Next-Generation (NG)

Next-generation eNB (Next-generation eNB, ng-eNB)

Next-Generation Core (NGC)

Non-Public Network (Non-Public Network, NPN)

New air port (New Radio, NR)

Normal Uplink (NUL)

Orthogonal frequency division multiplexing (Orthogonal Frequency-Division Multiplexing, OFDM)

Paging radio network temporary identifier (Paging-Radio Network Temporary Identifier, P-RNTI)

Physical broadcast channel (Physical Broadcast Channel, PBCH)

Main Cell (primary Cell, PCell)

Physical downlink control channel (Physical Downlink Control Channel, PDCCH)

Physical downlink shared channel (Physical Downlink Shared Channel, PDSCH)

Public land mobile network (Public Land Mobile Network PLMN)

Physical random access channel (Physical Random Access Channel PRACH)

Physical resource block (Physical Resource Block PRB)

Proximity services (Proximity Service, proSe)

Main SCG Cell (Primary SCG Cell, PScell)

Physical uplink control channel (Physical Uplink Control Channel, PUCCH)

Quasi Co-Location (QCL)

Random Access radio network temporary identifier (RA-RNTI), random Access-Radio Network Temporary Identifier

Random access network (Radio Access Network, RAN)

Random access technology (Radio Access Technology, RAT)

Radio Bearer (Radio Bearer, RB)

Resource block group (Resource Block Group RBG)

Third Generation partnership project version 15 (3GPP Release 15,Rel-15)

Third generation partnership project version 16 (3GPP Release 16,Rel-16)

Third generation partnership project version 17 (3GPP Release 17,Rel-17)

Resource identifier value (Resource Indication Value, RIV)

Wireless network controller (Radio Network Controller RNC)

Radio network temporary identifier (Radio Network Temporary Identifier, RNTI)

Radio resource control (Radio Resource Control, RRC)

Reference Signal (Reference Signal, RS)

Secondary Cell (second Cell, scell)

Secondary cell group (Secondary Cell Group, SCG)

Subcarrier Spacing (Sub-Carrier Spacing, SCS)

System frame number (System Frame Number SFN)

Auxiliary gNB (second gNB)

System information (System Information, SI)

System information block (System Information Block, SIB)

System information block type 1 (System Information Block Type 1, SIB 1)

Side link (Sidelink, SL)

Sequence Number (SN)

Independent Non-Public Network (SNPN) of independent networking

Special Cell (SpCell)

Semi-persistent scheduling physical downlink shared channel (Semi-Persistent Scheduling Physical Downlink Shared Channel, SPS-PDSCH)

Sounding reference signals (Sounding Reference Signal, SRS)

Synchronization signal (Synchronization Signal, SS)

Synchronous signal block (Synchronization Signal Block, SSB)

Supplementary uplink (Supplementary Uplink, SUL)

Timing Advance/Alignment (TA)

Transport Block (Transport Block, TB)

Transmission configuration indication (Transmission Configuration Indicator, TCI)

Transmit power control (Transmit Power Control, TPC)

Technical specification (Technical Specification, TS)

User Equipment (User Equipment, UE)

Uplink (UL)

Universal mobile telecommunication system (Universal Mobile Telecommunications System, UMTS)

Ultra-Reliable Low-latency communication (URLLC)

User equipment specific search space (UE-specific Search Space, USS)

Universal terrestrial radio access network (Universal Terrestrial Radio Access Network, UTRAN)

Internet of vehicles (Vehicle to Everything, V2X)

Virtual resource block (Virtual Resource Block, VRB)

Work Item (Working Item, WI)

Zero Power (Zero-Power, ZP)

The following description contains specific information pertaining to exemplary embodiments in the present application. The drawings in the present application and their accompanying detailed description are directed to merely exemplary embodiments. However, the present application is not limited to such exemplary embodiments. Other variations and embodiments of the present application will occur to those skilled in the art.

Unless otherwise indicated, identical or corresponding components in the figures may be indicated by identical or corresponding reference numerals. Moreover, the drawings and illustrations in the present application are not generally drawn to scale and are not intended to correspond to actual relative dimensions.

For consistency and ease of understanding, like features are labeled with like reference numerals in the exemplary figures (although not so labeled in some examples). However, features in different embodiments may differ in other respects and therefore should not be narrowly limited to features shown in the drawings.

The terms "one embodiment" or "some embodiments" may each be considered one or more of the same or different embodiments. Descriptions using the phrases "one embodiment" or "some embodiments" may each be viewed as one or more of the same or different embodiments. The term "coupled" is defined as directly or indirectly joined by intervening components and is not necessarily limited to physical joining. The term "comprising" when used means "including but not necessarily limited to"; it specifically indicates members of the open ended group, family, and equivalents that are encompassed or described. The phrase "at least one of A, B and C" or "at least one of: A. b and C "means" any combination of a alone, or B alone, or C alone, or A, B and C ".

The terms "system" and "network" may be used interchangeably. The term "and/or" is merely an association relationship for disclosing an associated object, and means that three relationships may exist, and a and/or B may mean that a exists alone, a and B exist together, or B exists alone. "A and/or B and/or C" may mean at least one of A, B and C is present. The character "/" generally indicates a relationship in which the associated object is "or".

The terms "if," "in this case," "simultaneously," "when," "after," "when," and "once" are used interchangeably. The terms "according," "based on," "passing" and "via" may be used interchangeably.

The terms "determine," "decide," and "select" may be used interchangeably. The terms "determine," "define," "configure," "given," "predetermined," "predefined," "preconfigured" and "pre-given" may be used interchangeably. The terms "operation," "implementation," and "performing" may be used interchangeably.

For purposes of explanation and not limitation, specific details are set forth such as functional entities, techniques, protocols, standards, etc. to provide an understanding of the described techniques. In other instances, detailed descriptions of well-known methods, techniques, systems, architectures, etc. are omitted so as not to obscure the description with unnecessary detail.

Those skilled in the art will immediately recognize that any of the network functions or algorithms of the present disclosure can be implemented by hardware, software, or a combination of software and hardware. The described functions may correspond to modules, which may be software, hardware, firmware, or any combination thereof.

The software implementation may include computer-executable instructions stored on a computer-readable medium such as memory or other type of storage device. One or more microprocessors or general purpose computers with communication processing capabilities may be programmed with corresponding executable instructions and perform the described network functions or algorithms.

The microprocessor or general purpose computer may include an application specific integrated circuit (Applications Specific Integrated Circuitry, ASIC), a programmable logic array, and/or use one or more digital signal processors (Digital Signal Processor, DSP). While several exemplary embodiments described in this specification are directed to software installed and executed on computer hardware, alternative exemplary embodiments implemented as firmware or as hardware or a combination of hardware and software are also within the scope of the disclosure.

The computer-readable medium may include, but is not limited to, random access Memory (Random Access Memory, RAM), read Only Memory (ROM), erasable programmable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable programmable Read Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), flash Memory, compact disc Read Only Memory (Compact Disc Read-Only Memory, CD-ROM), magnetic cassettes, magnetic tape, magnetic disk storage devices, or any other equivalent medium capable of storing computer-readable instructions.

A wireless communication network architecture, such as a long term evolution (Long Term Evolution, LTE) system, an LTE-advanced (LTE-a) system, an LTE-advanced Pro system, or a 5G NR radio access network (Radio Access Network, RAN)), typically includes at least one base station, at least one UE, and one or more optional network components that provide connectivity to the network. The UE communicates with a Network such as a Core Network (CN), evolved packet Core (Evolved Packet Core, EPC) Network, evolved universal terrestrial radio access Network (Evolved Universal Terrestrial Radio Access Network, E-UTRAN), NGC, 5G Core (5G Core,5 gc), or the internet through a RAN established by one or more base stations.

The UE may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal. For example: the UE may be a portable radio, including but not limited to a mobile phone, tablet computer, wearable device, sensor, vehicle, or personal digital assistant (Personal Digital Assistant, PDA) with wireless communication capability. The UE is configured to receive signals over an air interface and transmit the signals to one or more cells in the RAN.

The BS may be configured to provide communication services at least according to radio access technologies (Radio Access Technology, RAT), such as worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, wiMAX), global system for mobile communications (Global System for Mobile communications, GSM) commonly referred to as 2G, enhanced data rates for GSM evolution (Enhanced Data rates for GSM Evolution, EDGE) radio access network (GERAN), general packet radio services (General Packet Radio Service, GPRS), universal mobile system for mobile communications (Universal Mobile Telecommunication System, UMTS), commonly referred to as basic wideband code division multiple access (W-CDMA) based 3G), high speed packet access (high-speed packet access, HSPA), LTE-a, evolved LTE (elete), i.e. LTE connected to 5GC, NR (commonly referred to as 5G) and/or LTE-a Pro. However, the scope of the present application is not limited to these protocols.

The BS may include, but is not limited to, a Node B (NB) in UMTS, AN evolved node B (eNB) in LTE or LTE-a, a radio network controller (radio network controller, RNC) in UMTS, a BS controller (BSC) in GSM/GERAN, a ng-eNB in AN evolved universal terrestrial radio access (E-UTRA) BS connected to 5GC, a 5G-RAN (or a next generation node B (gNB) in a 5G access network (5G-AN)), or any other device capable of controlling radio communications to manage radio resources within a cell. The BS may serve one or more UEs via the radio interface.

A base station may be operable to provide radio coverage to a particular geographic area using a plurality of cells included in the RAN. The BS may support operation of the cell. Each cell may be operable to provide service to at least one UE within its radio coverage area.

Each cell (commonly referred to as a serving cell) may provide service to serve one or more UEs within its radio coverage area, whereby each cell schedules Downlink (DL) resources and optional Uplink (UL) resources to at least one UE within its radio coverage area for DL and optional UL packet transmissions. The BS may communicate with one or more UEs in a radio communication system through a plurality of cells.

The cell may allocate Side Link (SL) resources to support proximity services (Proximity Service, proSe), LTE SL services, and/or LTE/NR internet of vehicles (Vehicle to Everything, V2X) services. Each cell may have a coverage area that overlaps with other cells.

In the MR-DC case, the primary cell of the MCG or SCG may be referred to as the SpCell. PCell may refer to the SpCell of MCG. PSCell may refer to SpCell of SCG. MCG may refer to a set of serving cells associated with the MN, including SpCell and optionally one or more scells. SCG may refer to a set of serving cells associated with an SN, including a SpCell and optionally one or more scells.

As described above, the frame structure of the NR supports flexible configuration to accommodate various next generation (e.g., 5G) communication requirements, such as: enhanced mobile broadband (enhanced Mobile Broadband, emmbb), large-scale machine type communication (Massive Machine Type Communication, mctc), and Ultra-Reliable and Low-delay communication (URLLC), while meeting high reliability, high data rate, and Low-delay requirements. As agreed in 3GPP, orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing, OFDM) techniques can be used as a baseline for NR waveforms. An extensible OFDM parameter set may also be used, such as: adaptive subcarrier spacing, channel bandwidth and Cyclic Prefix (CP).

Two coding schemes of NR are considered, specifically Low-Density Parity-Check (LDPC) and polarization codes. Coding scheme adaptation may be configured based on channel conditions and/or service applications.

In the transmission time interval (transmission time interval, TTI) of a single NR frame, at least Downlink (DL) transmission data, guard interval and Uplink (UL) transmission data should be included. The DL transmission data, guard interval, and various portions of UL transmission data should also be configurable (e.g., NR based network dynamics). In addition, SL resources may also be provided in NR frames to support ProSe services, V2X services (e.g., E-UTRA V2X SL communication services), or side-link services (e.g., NR SL communication services). Conversely, SL resources may also be provided in E-UTRA frames to support ProSe services, V2X services (e.g., E-UTRA V2X SL communication services), or SL services (e.g., NR SL communication services).

Multiple PLMNs may operate on unlicensed spectrum. Multiple PLMNs may share the same unlicensed carrier. PLMNs may be public or private. The public PLMN may be provided by, but is not limited to, an operator or virtual operator providing radio services to public users. The public PLMN may have licensed spectrum and support RATs on the licensed spectrum. The private PLMN may be provided, but is not limited to, by a mini-operator, factory, or enterprise that provides radio services to its private users (e.g., employees or machines). The public PLMN may support more deployment scenarios (e.g., carrier aggregation between licensed bands NR (PCell) and NR-U (SCell), dual connectivity between licensed bands LTE (PCell) and NR-U (PSCell), independent NR-U, NR cells with DL in unlicensed bands and UL in licensed bands, dual connectivity DC between licensed bands NR (PCell) and NR-U (PSCell). The private PLMN may support, but is not limited to, a separate unlicensed RAT (e.g., a separate NR-U).

Any two or more of the following sentences, paragraphs, (sub) bullets, gist, actions, behaviors, terms, alternatives, aspects, examples, or claims described in the following application may be logically, reasonably, and appropriately combined to form a specific method.

Any sentence, paragraph, (sub) bullets, gist, action, behavior, term, substitution, aspect, example, or claim described in the following application may be independently and individually implemented to form a specific method.

Dependencies (e.g., "based on", "more specifically", "preferably", "in one embodiment", "in some implementations", "in one alternative", "in one example", "in one aspect", etc.) are only one possible example in the context of the following applications and do not limit a particular method.

An example description of some selected terms, examples, embodiments, implementations, actions, and/or behaviors used in the present application is given below.

The terms "network", "RAN", "cell", "camping cell", "serving cell", "BS", "gNB", "eNB" and "ng-eNB" may be used interchangeably. In some implementations, some of these items may refer to the same network entity.

Cell: a cell may be a radio network object that may be uniquely identified by a (cell) identity broadcast by the UE over a geographical area from a UTRAN access point. The cell may be in FDD or TDD mode.

The serving cell: for a UE that is not configured with an RRC connection state (e.g., rrc_connected state) of CA or DC, there may be only one serving cell, which may be referred to as PCell. For a UE in rrc_connected state configured with CA or DC, the term "serving cell" may be used to denote a set of cells including SpCell and all scells. For example, the serving cell may be a PCell, PSCell, or SCell described in TS 38.331.

The UE (operation) in the rrc_connected state may be an rrc_connected UE. The UE (operation) in the RRC IDLE state (e.g., rrc_idle state) may be an rrc_idle UE. The UE (operation) in the RRC INACTIVE state (e.g., rrc_inactive state) may be an rrc_inactive UE.

SpCell: for DC operation, the term SpCell may refer to the PCell of MCG or the PSCell of SCG. Otherwise, the term SpCell may refer to PCell.

MR-DC: the MR-DC may be DC between E-UTRA and NR nodes, or DC between two NR nodes. MR-DCs may include EN-DCs, NR-E-UTRA dual connectivity (NE-DCs), NG-RAN E-UTRA-NR dual connectivity (NGEN-DCs), and NR-NR dual connectivity (NR-DCs) (modes).

MCG: in MR-DC, the MCG may be a set of serving cells associated with the MN, including a SpCell (e.g., PCell) and optionally one or more scells.

MN: in MR-DC, the MN may be a radio access node providing control plane connectivity for the CN. The MN may be a master eNB (in EN-DC), a master ng-eNB (in NGEN-DC), or a master gNB (in NR-DC and NE-DC).

SCG: in MR-DC, the SCG may be a set of serving cells associated with the SN, including a SpCell (e.g., PSCell) and optionally one or more scells.

SN: in MR-DC, the SN may be a radio access node that has no control plane connection with the CN, providing additional resources to the UE. The SN may be EN-gNB (in EN-DC), an auxiliary ng-eNB (in NE-DC), or an auxiliary gNB (in NR-DC and NGEN-DC).

MeNB: the MeNB may be an eNB that is a master node associated with an MCG in MR-DC (scenario).

SgNB: the SgNB may be a gNB that is an auxiliary node associated with an SCG in MR-DC (scenario).

BWP: in some embodiments, BWP may be a subset of the total cell bandwidth of the cell. The BA may be implemented by configuring one or more BWP to the UE and informing the UE of which of the configured BWP is the currently activated BWP. To enable the BA mechanism on the PCell, the gNB may configure one or more UL and DL BWP for the UE. In the case of CA, to enable the BA mechanism on the Scell, the gNB may configure at least one or more DL BWP for the UE (which means that no UL BWP may be configured for the UE). For PCell, the initial BWP may be a BWP for initial access. For the SCell, the initial BWP may be a BWP configured for the UE to operate first during the SCell activation procedure. In some embodiments, the UE may be configured with a first active UL BWP through a "first actionbwp" IE/field. If the first active UL BWP is configured for SpCell, the "first actionbwp" IE/field may include an ID of the UL BWP to be activated when performing RRC (re) configuration. If this field does not exist, the RRC (re) configuration may not trigger a BWP handover. If the first active UL BWP is configured for the SCell, the "first actionuplinkbwp" IE/field may include an ID of the UL BWP to be used when MAC of the SCell is active.

HARQ-ACK: in some embodiments, HARQ may be a scheme combining an ARQ error control mechanism and FEC encoding, where the scheme uses unsuccessful attempts in FEC decoding instead of being discarded. In some embodiments, HARQ-ACK feedback may be used to indicate whether the HARQ process was successfully performed.

PDSCH-Config: in some embodiments, the "PDSCH-Config" IE may be a configuration/parameter for configuring (or indicating) PDSCH parameters to the UE.

DCI format 1_0: in some embodiments, DCI format 1_0 may be used to schedule PDSCH in one DL cell. DCI format 1_0 with CRC scrambled by C-RNTI/CS-RNTI/MCS-C-RNTI may include at least one of the following information/fields:

-identifier of DCI format: 1 bit. The value of this bit field may (always) be set to 1 to indicate the DL DCI format.

-frequency domain resource allocation:bits. If the CRC of DCI format 1_0 is scrambled by the C-RNTI and the "frequency domain resource allocation" field is all 1, DCI format 1_0 may be used for a random access procedure initiated by a PDCCH command.

If the CRC of DCI format 1_0 is scrambled by the C-RNTI and the "frequency domain resource allocation" field is all 1, all remaining information/fields may be set as follows:

-random access preamble index: 6 bits set according to ra-preambieindex as described in TS 38.321.

UL/SUL indicator: 1 bit. If the value of the "random access preamble index Random Access Preamble index" is not all zero, and if the UE configures "supplementaryUplink" in the "ServingCellConfig" of the cell, this field may indicate which UL carrier in the cell should be used for transmission of the PRACH; otherwise, the field may be reserved.

-SS/PBCH index: 6 bits. If the value of the "random access preamble index" is not all zero, this field may indicate SS/PBCH that should be used to determine RACH occasions for PRACH transmission; otherwise, the field may be reserved.

PRACH mask index: 4 bits. If the value of the "random access preamble index" is not all zero, this field may indicate the RACH occasion associated with the SS/PBCH indicated by the "SS/PBCH index" for PRACH transmission as described in TS 38.321; otherwise, the field may be reserved.

Reserved bits: 12 bits for operation in a cell with shared spectrum channel access; otherwise 10 bits.

Otherwise, all remaining information/fields may be set as follows:

-time domain resource allocation: as described in TS 38.214, 4 bits.

-VRB-to-PRB mapping:1 bit.

-modulation and coding scheme: as described in TS 38.214, 5 bits.

-a new data indicator: 1 bit.

Redundancy version: 2 bits.

HARQ process number: 4 bits.

-downlink allocation index: as described in TS 38.213, 2 bits as counter DAI.

TPC commands for scheduled PUCCH: as described in TS 38.213, 2 bits.

PUCCH resource indicator: as described in TS 38.213 5.

PDSCH-to-harq_feedback timing indicator: as described in TS 38.213, 3 bits.

-ChannelAccess-CPext:2 bits. If "ChannelAccessMode-r16" = "semi-static" is provided for operation in a cell with shared spectrum channel access, this field may be used to indicate a combination of channel access type and CP extension; otherwise 0 bit.

DCI format 1_0 with CRC scrambled by P-RNTI may include at least one of the following information/fields:

-a short message indicator: 2 bits as described in TS 38.212 or table 1 below.

-short message: 8 bits as described in TS 38.331. The bit field may be reserved if only paging scheduling information is carried.

-frequency domain resource allocation:bits. If only short messages are carried, the bit field may be reserved. />Possibly the size of CORESET 0.

-time domain resource allocation: as described in TS 38.214, 4 bits. If only short messages are carried, the bit field may be reserved.

-VRB-to-PRB mapping:1 bit. If only short messages are carried, the bit field may be reserved.

-modulation and coding scheme: as described in TS 38.214, 5 bits. If only short messages are carried, the bit field may be reserved.

-TB scaling: as described in TS 38.214, 2 bits. If only short messages are carried, the bit field may be reserved.

Reserved bits: 8 bits are used to operate in a cell with shared spectrum channel access; otherwise 6 bits.

Table 1 shows an example short message indicator.

TABLE 1

Bit field	Short message indicator
		00	Reservation of
01	Scheduling information for paging only in DCI
		10	Only short messages exist in DCI
11	Paging scheduling information and short message are both present in DCI

DCI format 1_0 with CRC scrambled by SI-RNTI may include at least one of the following information/fields:

-frequency domain resource allocation:bits. />May be the size of CORESET 0.

-time domain resource allocation: 4 bits as described in TS 38.214.

-VRB-to-PRB mapping:1 bit.

-modulation and coding scheme: 5 bits as described in TS 38.214.

Redundancy version: 2 bits.

-a system information indicator: 1 bit, as shown in table 2 below.

Reserved bits: 17 bits for operation in a cell with shared spectrum channel access; otherwise 15 bits.

Table 2 shows an example system information indicator. Details of SIB1 and SI messages may be described in TS 38.331.

TABLE 2

Bit field	System information indicator
		0	SIB1
1	SI message

DCI format 1_0 with CRC scrambled by RA-RNTI or MsgB-RNTI may include at least one of the following information/fields:

-frequency domain resource allocation:bits. />May be the size of CORESET 0 if CORESET 0 is configured for the cell. />May be the size of the initial DL BWP if CORESET 0 is not configured for the cell.

-time domain resource allocation: 4 bits as described in TS 38.214.

-VRB-to-PRB mapping:1 bit.

-modulation and coding scheme: 5 bits as described in TS 38.214.

-TB scaling: 2 bits as described in TS 38.214.

-LSBs in SFN: if "msgB-response window" is configured to be greater than 10ms, DCI format 1_0 is 2 bits and the CRC is scrambled by msgB-RNTI, as described in TS 38.213; or if "RA-ResponseWindow" or "RA-ResponseWindow-v1610" is configured to be greater than 10ms, DCI format 1_0 is 2 bits and CRC is scrambled by RA-RNTI for operation in a cell with shared spectrum channel access as described in TS 38.213; otherwise, it is 0 bit.

Reserved bits: (16-a) bits for operation in cells without shared spectrum access; or (18-a) bits for operation in cells with shared spectrum access. The value of a may be the number of bits of the LSB field of the SFN.

DCI format 1_0 with CRC scrambled by TC-RNTI may include at least one of the following information/fields:

-identifier of DCI format: 1 bit. The value of the bit field may be (always) set to 1 to indicate the DL DCI format.

-frequency domain resource allocation:bits. />May be the size of CORESET 0.

-time domain resource allocation: 4 bits as described in TS 38.214.

-VRB-to-PRB mapping:1 bit.

-modulation and coding scheme: 5 bits as described in TS 38.214.

-a new data indicator: 1 bit.

Redundancy version: 2 bits.

HARQ process number: 4 bits.

-downlink allocation index: 2 bits, reserved.

TPC commands for scheduled PUCCH: 2 bits as described in TS 38.213.

PUCCH resource indicator: 3 bits as described in TS 38.213.

PDSCH-to-harq_feedback timing indicator: 3 bits as described in TS 38.213.

-ChannelAccess-CPext:2 bits. If "ChannelAccessMode-r16" =' semi static "is provided for operation in a cell with shared spectrum channel access, this field may be used to indicate a combination of channel access type and CP extension; otherwise 0 bit.

A configuration associated with rate matching (e.g., a resource pattern for configuring PDSCH reception rate matching) may be included in the "PDSCH-Config" IE. Table 3 illustrates the configuration related to rate matching.

TABLE 3 Table 3

Table 4 shows an example "RateMatchPatternGroup".

TABLE 4 Table 4

Table 5 shows an example "RateMatchPattern".

TABLE 5

SI may refer to MIB, SIB1 and other SIs. The minimum SI may include MIB and SIB1. Other SIs may refer to SIB3, SIB4, SIB5, and other SIBs (e.g., SNPN-specific SIB, PNI-NPN-specific SIB).

Dedicated signaling may refer to (but is not limited to) RRC messages. For example, the RRC message may include an RRC (connection) setup request message, an RRC (connection) setup complete message, an RRC (connection) reconfiguration message, an RRC connection reconfiguration message including mobile control information, an RRC connection reconfiguration message internally containing no mobile control information, an RRC reconfiguration message containing synchronous configuration, an RRC reconfiguration message internally containing no synchronous configuration, an RRC (connection) reconfiguration complete message, an RRC (connection) restoration request message, an RRC (connection) restoration complete message, an RRC (connection) reestablishment request message, an RRC (connection) reestablishment complete message, an RRC (connection) rejection message, an RRC (connection) release message, an RRC system information request message, a UE assistance information message, a UE capability query message, and a UE capability information message. The RRC message may be a dedicated signaling. The UE may receive an RRC message from the network through unicast/broadcast/multicast.

The disclosed mechanisms may be applied to any RAT. The RAT may be, but is not limited to, NR-U, LTE, E-UTRA connected to 5GC, LTE connected to 5GC, E-UTRA connected to EPC, and LTE connected to EPC. The disclosed mechanisms may be applied to UEs in public or private networks (e.g., NPN, SNPN, and PNI-NPN).

The disclosed mechanisms may be used for authorized frequencies and/or unauthorized frequencies.

In general, the disclosed mechanisms may be applied to, but are not limited to, PCell and UE. In addition, the mechanisms described in this application may be applied to PSCell and UE.

In this application, the terms "IE" and "field" may be used interchangeably.

In Rel-15 and Rel-16 NR, the characteristics of NR supported broadcast and multicast have not been specified. It is beneficial to enable broadcast and/or multicast services (e.g., generic MBS services) over 5GS, considering that broadcast and/or multicast may provide substantial improvements for important use cases, particularly in terms of system efficiency and user experience. Examples of uses that may benefit from this functionality include public safety, mission critical, and V2X applications, among others. In 3GPP RAN#88-e, the goal of the new WI MBS is to specify a group scheduling mechanism to allow the UE to receive broadcast and/or multicast services.

In some embodiments, broadcast and/or multicast services may be provided to a group of UEs through dynamic PDSCH(s) or SPS PDSCH(s). To provide broadcast and/or multicast services, the gNB may schedule a group common PDSCH receivable by the group of UEs via the group common PDCCH receivable by the group of UEs. In some other embodiments, the gNB may schedule unicast PDSCH receivable by each UE in the group of UEs separately via dedicated PDCCHs receivable by each UE in the group of UEs. In some other embodiments, the gNB may schedule the group common PDSCH receivable by the group of UEs via a separate dedicated PDCCH receivable by each UE of the group of UEs. Using the group common PDCCH or the group common PDSCH has an advantage of improving resource efficiency because the same information needs to be transmitted only once. On the other hand, using a dedicated PDCCH or a dedicated PDSCH has an advantage of scheduling flexibility because the gNB can schedule a specific UE based on UE capabilities and channel conditions of the specific UE.

In some embodiments, a narrow beam or more accurate precoding may be used for the dedicated PDCCH or dedicated PDSCH. A combined use of these implementations may also be beneficial. For example, when the gNB schedules the group common PDSCH for a UE group other than some UEs having relatively poor channel conditions compared to other UEs in the group of UEs through the group common PDCCH, resource efficiency may be improved because MCS selection of the group common PDCCH and the group common PDSCH may not be required based on worse channel conditions.

To enable scheduling of group common PDSCH, CFR may be configured. CFR may be configured within an active DL BWP of the UE. That is, the frequency resources of the activated DL BWP may include frequency resources of the CFR. In this application, the active DL BWP may include CFR, and the frequency resources corresponding to the active DL BWP may include frequency resources of CFR. The configuration of CFR may be provided to the UE through SI or through dedicated signaling (e.g., RRC signaling). The configuration of the CFR may be provided together with related configurations of PDCCH, PDSCH, and PUCCH for the CFR. For example, the CFR configuration (IE) may include at least one of PDCCH-Config, PDSCH-Config, or "PUCCH-ConfigurationList" (IE). The PDCCH-configuration, PDSCH-configuration, and PUCCH-configuration list in the CFR configuration may be different from the PDCCH-configuration, PDSCH-configuration, and PUCCH-configuration list in the dedicated BWP configuration of the UE.

The group common PDCCH transmitted in the CFR may be transmitted based on a configuration provided in the PDCCH-Config associated with the CFR. Similar to PDCCH-Config for DL BWP, PDCCH-Config associated with CFR may include configuration of CORESET and search space associated with CORESET within CFR. The group common PDSCH transmitted within the CFR may be transmitted based on a configuration provided in the PDSCH-Config associated with the CFR.

The group common PDCCH may be transmitted in a search space configured for a group of UEs. The search space may be a type 3CSS or a type 4CSS based on the configuration in PDCCH-Config associated with CFR. The group common PDCCH may include a specific DCI format configured or defined for the group common PDCCH. For example, the DCI format may be DCI format 1_0, DCI format 1_1, or DCI format 1_2 with G-RNTI scrambled CRC. Alternatively, the DCI format may be a new DCI format (e.g., DCI format 1_3).

In the present application, two new DCI formats may be used to schedule a group common PDSCH. The first new DCI format may be referred to as DCI format m_0. The second new DCI format may be referred to as DCI format m_1.

In Rel-15 NR, in order to reduce UE complexity, a DCI size budget has been specified to limit the total number of different DCI sizes that a UE needs to monitor a cell. The total number of DCI formats of different DCI sizes that the UE needs to monitor for a cell may not exceed 4. The total number of different DCI formats with C-RNTI scrambled CRCs that the UE needs to monitor may not exceed 3. Procedures for DCI size alignment have been specified to handle DCI size budgets.

The procedure for DCI size alignment may include, but is not limited to, the following steps.

Step 1: the sizes of DCI format 0_0 and DCI format 1_0 monitored in all CSSs may be aligned by determining the length of the FDRA field based on the size of the initial DL BWP or the size of CORESET 0 (if CORESET 0 is configured), and the size of the initial UL BWP for DCI format 1_0 and DCI format 0_0, respectively. If the DCI sizes for the two DCI formats are different, zeros may be padded to DCI format 0_0 until the two DCI formats have the same size (e.g., if the size of DCI format 0_0 is smaller than the size of DCI format 1_0). If the size of DCI format 0_0 is greater than the size of DCI format 1_0, the MSB bit of the FDRA field may be truncated until both DCI formats have the same size.

Step 2: the sizes of DCI format 0_0 and DCI format 1_0 monitored in one CSS may be aligned by determining the length of the FDRA field based on the size of the active DL BWP and the size of the active UL BWP for DCI format 1_0 and DCI format 0_0, respectively. If the DCI sizes of the two DCI formats are different, zeros may be padded to DCI formats having smaller sizes until the two DCI formats have the same size.

Step 3-1: the sizes of DCI format 0_1 and DCI format 1_1 monitored in USS may be determined by the RRC configuration and based on the size of the active DL BWP and the size of the active ULBWP for DCI format 1_1 and DCI format 0_1, respectively. To avoid DCI format ambiguity, if the size of DCI format 0_1 or DCI format 1_1 is equal to the size of DCI format 0_0 or DCI format 1_0 in another USS, zero bits may be padded to DCI format 0_1 or DCI format 1_1.

Step 3-2: the sizes of DCI format 0_2 and DCI format 1_2 monitored in USS may be determined by RRC configuration and based on the size of active DL BWP and the size of active UL BWP for DCI format 0_2 and DCI format 1_2, respectively.

Step 4: it is determined whether the DCI size budget is met. If the DCI size budget is not met, please perform step 5-1.

Step 5-1: deleting the zero filled in the step 3-1. The sizes of DCI format 0_0 and DCI format 1_0 monitored in the CSS may be aligned by determining the length of the FDRA field based on the size of the initial DL BWP or the size of CORESET 0 (if CORESET 0 is configured), and the size of the initial UL BWP for DCI format 1_0 and DCI format 0_0, respectively. If the DCI sizes of the two DCI formats are different, zeros may be padded to DCI format 0_0 until the two DCI formats have the same size (e.g., if the size of DCI format 0_0 is smaller than the size of DCI format 1_0). If the size of DCI format 0_0 is greater than the size of DCI format 1_0, the MSB bit of the FDRA field may be truncated until both DCI formats have the same size.

Step 5-2: if the DCI size budget is not met, zero padding may be performed on the smaller sized DCI formats 0_2 and DCI formats 1_2 until both DCI formats have the same size.

Step 5-3: if the DCI size budget is not met, zero padding may be performed on the smaller sized DCI formats 0_1 and 1_1 until both DCI formats have the same size.

The PUCCH resources for HARQ-ACK feedback for the group common PDSCH may be configured in a "PUCCH-configuration list" different from the "PUCCH-configuration list" of the PUCCH resources for HARQ-ACK feedback for the configuration of the dedicated PDSCH, CSI, and SR. In other words, the UE may be configured with two PUCCH-configurations lists, each of which may include at most two PUCCH-configurations. The first PUCCH-configuration in the "PUCCH-configuration list" may include a configuration of PUCCH resources having a lower physical layer priority. The second PUCCH-configuration in the PUCCH-configuration list may include a configuration of PUCCH resources of a higher physical layer priority. The PUCCH-ConfigurationList for the group common PDSCH may be configured as part of the CFR configuration or may be configured with other PUCCH-configurationlists for the dedicated PDSCH, CSI, and SR.

In this application, PUCCH resources configured by "PUCCH-ConfigurationList" for the group common PDSCH may be referred to as a multicast PUCCH. The PUCCH resources of the "PUCCH-ConfigurationList" configuration for dedicated PDSCH, CSI and SR may be referred to as unicast PUCCH. In addition, the dedicated PDCCH and the dedicated PDSCH may be referred to as a unicast PDCCH and a unicast PDSCH, respectively.

In Rel-15 NR, two types of resource allocation are specified for PDSCH. For resource allocation type 0, a bitmap may be used to indicate VRBs allocated for PDSCH. Each bit of the bitmap may correspond to an RBG. The RBG may include one or more VRBs. For resource allocation type 1, the riv may be used to (co) indicate the starting VRB (RB _start ) And a total length L in units of consecutively allocated resource blocks _RBs . The RIV can be determined by definition as shown in table 6.

TABLE 6

To determine RIV, L _RBs 1 or more and not more than

The problem regarding DCI size alignment for unicast and multicast reception/transmission may be described as follows.

Content of DCI format m_0 and DCI format m_1

For UEs without dedicated RRC configuration, DCI format m_0 may be receivable. The field length of the DCI format may not depend on the dedicated RRC configuration. The DCI format may be used for a broadcast service or may be used for a multicast service with low scheduling flexibility. DCI format m_1 may be intended for a UE with a dedicated RRC configuration. DCI formats may provide more scheduling flexibility and may be used for multicast services. The content of the DCI format may need to be defined in consideration of functions required for broadcast and multicast services and in consideration of size alignment with legacy DCI formats (e.g., DCI format 1_0, DCI format 1_1 and/or DCI format 1_2).

Implementations for processing the content of DCI format m_0 and/or DCI format m_1 may be described as follows.

In some embodiments, DCI format m_0 may include at least one field of DCI format 1_0 with CRC scrambled by a C-RNTI. DCI format m_0 may not include at least one of the following fields:

- "DCI format identifier" field;

- "TPC command for PUCCH scheduled" field.

In some embodiments, DCI format m_0 may not include at least one of a "downlink allocation index" field, a "PUCCH resource indicator" field, or a "PDSCH-to-harq_feedback timing indicator" field when at least one specific condition is satisfied. The specific conditions may include, but are not limited to, at least one of:

DCI format m_0 is used to schedule a group common PDSCH for a broadcast service.

DCI format m_0 is used to schedule a group common PDSCH for a multicast service and disable HARQ-ACK feedback for the multicast service.

DCI format m_0 is used to schedule a group common PDSCH for a multicast service and an explicit RRC parameter is configured to indicate the presence of a field in DCI format m_0.

In some embodiments, if DCI format m_0 is used to invoke a group common PDSCH for a multicast service, a "HARQ-ACK enable/disable" field may be included in DCI format m_0.

In some embodiments, HARQ-ACK feedback for multicast services may be enabled/disabled through RRC configuration. When an "HARQ-ACK enable/disable" field for indicating enablement/disablement of HARQ-ACK feedback for a multicast service is RRC configured to be included in DCI, HARQ-ACK feedback for the multicast service may be enabled/disabled through DCI (e.g., DCI indication). The RRC configuration may be included in PDSCH-Config associated with CFR. The presence of the "HARQ-ACK enable/disable" field may be configured according to CFR or multicast service. The UE may not expect the "HARQ-ACK enabled/disabled" field to exist for a first multicast service associated with a DCI format and may not expect the "HARQ-ACK enabled/disabled" field to exist for a second multicast service associated with a DCI format in the same CFR. When there is a "HARQ-ACK enabled/disabled" field for a first multicast service associated with a DCI format and there is no "HARQ-ACK enabled/disabled" field for a second multicast service associated with a DCI format in the same CFR, the UE may determine the number of reserved bits present in the DCI format for scheduling the second multicast service. The number of reserved bits is equal to the number of bits of the "HARQ-ACK enable/disable" field in the DCI format used to schedule the first multicast service.

In some embodiments, if DCI format m_0 is used to schedule a group common PDSCH for a broadcast service, an "SC-MCCH change notification" field may be included in DCI format m_0.

An implementation of determining whether DCI format m_0 is used to schedule a group common PDSCH for a broadcast service or a group common PDSCH for a multicast service may be described as follows.

In some embodiments, if at least one specific condition is satisfied, a DCI format m_0 for scheduling a group common PDSCH for a broadcast service may be determined. The specific conditions may include, but are not limited to, at least one of:

DCI format m_0 is detected in the search space associated with CORESET 0 or in the search space associated with CORESET configured "common control resource" in SIB 1.

DCI format m_0 has a CRC scrambled by MCCH-RNTI.

DCI format m_0 has a CRC scrambled by a G-RNTI included in the MTCH configuration.

DCI format m_0 has a CRC scrambled by RNTI for MCCH change notification.

In some embodiments, if at least one specific condition is met, a DCI format m_0 for scheduling a group common PDSCH for a multicast service may be determined. The specific conditions may include, but are not limited to, at least one of:

-detecting DCI format m_0 in a search space configured by PDCCH-Config associated with CFR provided via dedicated RRC signaling.

DCI format m_0 has a CRC scrambled by G-RNTI for a multicast service provided through dedicated signaling.

In some embodiments, the total length of the "frequency domain resource allocation" field may be determined based on the total number of PRBs for the CFR of the broadcast service or the multicast service. Specifically, the length of the "frequency domain resource allocation" field may beBits. />The total number of PRBs, which may be CFR. For broadcast services, if no CFR configuration is provided for broadcast services, +.>Is determined to be equal to the total number of PRBs in CORESET 0. The CFR configuration may not (explicitly) indicate the total number of PRBs of the CFR. CFR configuration the total number of PRBs of the CFR may be (implicitly) indicated by the presence of the CFR configuration. For example, when there is a CFR configuration, the total number of PRBs of the CFR may be the same as the total number of PRBs of the initial DL BWP of the SIB1 configuration. If the initial DL BWP is configured by SIB1, then CFR configuration may (only) exist. An example form of CFR configuration is shown in table 7.

TABLE 7

CommonFrequenctResource ENUMERATED{true}

In some embodiments, DCI format m_1 may include at least one of the fields of DCI format 1_1 and/or DCI format 1_2 with a CRC scrambled by a C-RNTI. DCI format m_1 may not include at least one of the following fields:

- "DCI format identifier" field;

- "TPC command for scheduling PUCCH" field;

-a carrier indicator field;

-a bandwidth part indicator field;

- "SRS request" field;

- "SCell sleep indication" field.

In some embodiments, the presence of a field and the total length of the field of DCI format m_1 transmitted in a CFR may depend on a configuration included in a PDSCH-Config associated with the CFR or may depend on a configuration included in a PDCCH-Config associated with the CFR. These fields may include, but are not limited to, a "frequency domain resource allocation" field, a "time domain resource allocation" field, a "VRB-to-PRB mapping" field, a "PRB bundling size indicator" field, a "rate matching indicator" field, a "ZP CSI-RS trigger" field, an "antenna port" field, a "transmission configuration indication" field, a "CBG transmission information (CBG transmission information, CBGTI)" field, a "CBG refresh information (CBG flushing out information, CBGFI)" field, or a "priority indicator" field.

In some embodiments, when at least one specific condition is satisfied, DCI format m_1 may not include at least one of a "downlink allocation index" field, a "PUCCH resource indicator" field, or a "PDSCH-to-harq_feedback timing indicator" field. The specific conditions may include, but are not limited to, at least one of:

DCI format m_1 is used to schedule a group common PDSCH for a multicast service and disable HARQ-ACK feedback for the multicast service.

DCI format m_1 is used to schedule a group common PDSCH for a multicast service and is configured with explicit RRC parameters indicating the presence of fields in DCI format m_0.

In some embodiments, if DCI format m_1 is used to schedule a group common PDSCH for a multicast service, a "HARQ-ACK enable/disable" field may be included in DCI format m_1.

In some embodiments, the total length of the "frequency domain resource allocation" field may be determined based on the total number of PRBs for the CFR of the broadcast service or the multicast service. Specifically, the total length of the "frequency domain resource allocation" field may beBits. />The total number of PRBs, which may be CFR.

In some embodiments, the total length of the "time domain resource allocation" field may be determined based on the "PDSCH-timedomainalllocation list" field in PDSCH-Config associated with the CFR. The total length of the "time domain resource allocation" field may be determined asBits. I may be the total number of entries in the "PDSCH-timedomainalllocation list" field in PDSCH-Config associated with CFR.

In some embodiments, the presence of the "VRB-to-PRB mapping" field may be determined based on whether the "VRB-ToPRB-interlace" field is included in the PDSCH-Config associated with the CFR. If the "vrb-ToPRB-Interleaver" field is included in the PDSCH-Config associated with the CFR, this field may be present. Otherwise, this field may not exist.

In some implementations, the presence of the "transmission configuration indication" field may be determined based on whether the "tci-presentingii" field is included in the CORESET configuration associated with the CFR.

In some embodiments, a "CBG transmission information (CBGTI)" field or a "CBG refresh information (CBGFI)" field may not be present in the DCI format m_1 (e.g., whether the "codeblockgrouptansmsision" field or the "PDSCH-codeblockgrouptansrissionlist-r 16" field is included in the PDSCH-ServingCellConfig of the serving cell of the CFR).

DCI size alignment

The same DCI size budget (e.g., as discussed in Rel-15 NR) may be maintained to avoid increasing UE complexity. Thus, the procedure of DCI size alignment should be defined in consideration of DCI format m_0 and DCI format m_1.

Implementations of DCI size alignment for handling unicast DCI formats and multicast DCI formats may be described as follows. The unicast DCI format may include at least one of DCI format 0_0, DCI format 1_0, DCI format 0_1, DCI format 1_1, DCI format 0_2 or DCI format 1_2. The multicast DCI format may include DCI format m_0 and DCI format m_1.

In some embodiments, to align the sizes of DCI format m_0 and DCI format 1_0 in the CSS, DCI format m_0 may be padded with zeros until the size of DCI format m_0 is the same as the size of DCI format 1_0 (e.g., if the size of DCI format m_0 is smaller than the size of DCI format 1_0). In some other embodiments, if the size of DCI format m_0 is greater than the size of DCI format 1_0, the MSB bit of the FDRA field in DCI format m_0 may be truncated until the size of DCI format m_0 is the same as the size of DCI format 1_0.

In some embodiments, the gNB may configure the total number of PRBs of the CFR associated with DCI format m_0 such that truncation of the FDRA field does not occur. For example, if the "identifier for DCI format" field and the "TPC command for PUCCH for scheduling" field are not included in DCI format m_0, there may be a 3-bit budget for configuring the total number of PRBs of CFR. If the cell is configured with CORESET 0 having 24 PRBs, 48 PRBs, or 96 PRBs, the length of the FDRA field of the DCI format 1_0 may be 9 bits, 11 bits, and 13 bits, respectively. Thus, with a 3-bit budget, the maximum length of the FDRA field of DCI format m_0 may be 12 bits, 14 bits, and 16 bits, which corresponds to 90 PRBs, 180 PRBs, and other PRBs that may be configured for CFR.

In some implementations, the type 1 resource allocation can be based on resource block groups when truncation of the FDRA field occurs (e.g., to better utilize PRBs configured in CFR). In other words, the starting VRB RB indicated by RIV _start Can be interpreted as RB _start K, and indicated consecutive allocated resource blocks L _RBs Can be interpreted as L _RBs K. K can be determined to be satisfied in the set {1,2,4,8}Is a maximum value of (a). Otherwise, k=1. N (N) ^CCR The total number of PRBs, which may be CFR. In some embodiments, N ^Ref May be a reference number of PRBs, which may be defined as the minimum number of PRBs resulting in the length of the FDRA field being equal to the length of the truncated FDRA field. For example, if the truncated FDRA field has 9 bits, N ^Ref It may be equal to 23 because +.>Is n=23. In some other embodiments, N ^Ref Can be defined as resulting in the length of the FDRA field being equal to the truncatedMaximum number of PRBs of length of broken FDRA field. In some other embodiments, N ^Ref May be a configuration value or may be a configuration value selected from a set of values.

In some embodiments, aligning the size of DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 with the size of DCI format m_1 or with the size of DCI format m_0 in the search space of the PDCCH-Config configuration associated with the CFR may fill DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 with zeros until the size of DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 is the same as the size of DCI format m_1 or the size of DCI format m_0 (e.g., if the size of DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 is smaller than the size of DCI format m_1 or the size of DCI format m_0). In some other embodiments, if the size of DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 is greater than the size of DCI format m_1 or DCI format m_0, the MSB bit of the FDRA field in DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 may be truncated until the size of DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 is the same as the size of DCI format m_1 or DCI format m_0. In some other embodiments, if the size of DCI format 11, DCI format 01, DCI format 12, or DCI format 02 is greater than the size of DCI format m_1 or DCI format m_0, the MSB bits in DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2, or all bits of one or more particular DCI fields (e.g., a "time-domain resource allocation" field, a "modulation and coding scheme 2" field, a "new data indicator 2" field, a "redundancy version" field, a "CBG transmission information (CBGTI)" field, or a "CBG refresh information (CBGFI)" field) may be truncated until the size of DCI format 1_1, DCI format 1_2, or DCI format 0_2 is the same as the size of DCI format m_1 or DCI format m_0.

In some implementations, when truncation of the FDRA field occurs (e.g., to better utilize PRBs configured within the active DL BWP), and when type 1 resource allocation is used to activate DL BWP, the type 1 resource allocation may be based on the resource block group. In other words, by RIVIndicated start VRB RB _start Can be interpreted as RB _start K, and indicated consecutive allocated resource blocks L _RBs Can be interpreted as L _RBs K. K can be determined to be satisfied in the set {1,2,4,8}Is a maximum value of (a). Otherwise, go (L)>May be the number of PRBs that activate DL BWP. In some embodiments, N ^Ref May be a reference number of PRBs, which may be defined as the minimum number of PRBs resulting in the length of the FDRA field being equal to the length of the truncated FDRA field. For example, if the truncated FDRA field has 9 bits, N ^Ref Then it may be equal to 23 because of the fact that Is n=23. In some other embodiments, N ^Ref May be defined as the maximum number of PRBs resulting in the length of the FDRA field being equal to the length of the truncated FDRA field. In some other embodiments, N ^Ref May be a configuration value or may be a configuration value selected from a set of values.

In some other embodiments, when type 0 resource allocation is used to activate DL BWP, the type 0 resource allocation may be based on resource block groups, each including a second number of consecutive VRBs, denoted P'. The second number of resource blocks may be different from the first number of consecutive VRBs, denoted P, which is the number of (nominal) consecutive VRBs in the RBG for activating BWP. Table 8 may be used to determine a nominal RBG size P. P may be determined based on RRC parameters (e.g., a "rbg-Size" field) and the Size of the active DL BWP, as shown in table 8.

TABLE 8

Bandwidth portion size	Configuration 1	Configuration 2
			1–36	2	4
37–72	4	8
			73–144	8	1 6
145–275	1 6	1 6

P' may be determined to satisfy Table 8Is a minimum of (2). />Common resource block index and L, which may be the starting RB of an activated BWP _FDRA May be the length of the truncated FDRA field. In some embodiments, the FDRA field of the DCI format may not be expected by the UE to be truncated when type 0 resources are allocated for activating DL BWP.

In some other embodiments, in the search space of PDCCH-Config configuration associated with CFR, aligning the size of DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 with the size of DCI format m_1 or with the size of DCI format m_0, when determining the DCI field length of DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2, some configurations of PDSCH-Config, PDCCH-Config, or PUCCH-Config in the activated DL BWP and activated UL BWP may be replaced with configurations of PDSCH-Config, PDCCH-Config, or PUCCH-Config associated with CFR. For example, the length of the "time domain resource allocation" field of DCI format 1_1 may be determined by the "PDSCH-timedomainalllocation list" field in PDSCH-Config associated with the CFR.

DCI format ambiguity

DCI format ambiguity may occur when DCI format m_0 and DCI format m_1 have the same size. Since the UE may need to interpret the fields of the DCI format based on the assumption of the DCI format, DCI format ambiguity should be avoided.

An implementation for distinguishing DCI format m_0 from DCI format m_1 may be described as follows.

In some embodiments, the MSB bits of DCI format m_0 and DCI format m_1 may be the "identifier of DCI format" field. A value of 0 may indicate that the DCI is DCI format m_0. A value of 1 may indicate that the DCI is DCI format m_1.

In some embodiments, the UE may not (desirably) be configured with (both) DCI format m_0 and DCI format m_1 for CFR.

In some embodiments, the UE may not expect DCI format m_0 and DCI format m_1 to have the same size in CFR or in a cell.

In some embodiments, when DCI format m_0 and DCI format m_1 have the same size in CFR or in a cell, DCI format m_1 may be padded with one zero bit.

In some embodiments, the UE may not (desirably) be configured with DCI format m_0 and DCI format m_1 for the search space configured in PDCCH-Config associated with the CFR.

In some implementations, one or more G-RNTIs may be configured to be associated with a search space. Each G-RNTI may be associated with a DCI format. The UE may determine a DCI format of the detected DCI through a G-RNTI for scrambling a CRC of the DCI. For example, the UE may be configured with a first G-RNTI and a second G-RNTI. Each G-RNTI may be associated with a particular MBS session. Since the UE can only be configured with DCI format m_0 or DCI format m_1 to be applied to an MBS session, the UE may determine the DCI format from the G-RNTI of the CRC applied to the scrambling schedule DCI.

To enable scheduling of group common PDSCH, CFR may be configured. CFR may be configured within an active DL BWP of the UE. The configuration of the CFR may be provided to the UE via SI or via dedicated signaling (e.g., RRC signaling). The configuration of the CFR may be provided together with related configurations of PDCCH, PDSCH, and PUCCH for the CFR. For example, the CFR configuration (IE) may include at least one of PDCCH-Config, PDSCH-Config, or "PUCCH-ConfigurationList" (IE). It should be noted that PDCCH-Config, PDSCH-Config, and PUCCH-ConfigurationList in the CFR configuration may be different from those in the dedicated BWP configuration of the UE.

The group common PDCCH may be transmitted based on a configuration provided in PDCCH-Config associated with the CFR. Similar to PDCCH-Config for DL BWP, PDCCH-Config associated with CFR may include configuration of CORESET and search space associated with CORESET within CFR. The group common PDSCH transmitted within the CFR may be transmitted based on a configuration provided in PDCCH-Config associated with the CFR.

The group common PDCCH may be transmitted in a search space configured for a group of UEs. The search space may be a type 3CSS or a type 4CSS based on the configuration in PDCCH-Config associated with the CFR. The group common PDCCH may include a specific DCI format configured or defined for the group common PDCCH. For example, the DCI format may be DCI format 1_0 with G-RNTI scrambled CRC, DCI format 1_1, or DCI format 1_2 with G-RNTI scrambled CRC. Alternatively, the DCI format may be a new DCI format (e.g., DCI format 1_3) with CRC scrambled by the G-RNTI.

In order to receive the PDCCH or PDSCH, a reception beam for receiving the PDCCH or PDSCH may be (need to) determined. QCL information for PDCCH or PDSCH may be used to determine the receive beam. In Rel-15NR, TCI state may be used to provide QCL information for receiving PDCCH or PDSCH. For example, the TCI state for receiving the PDCCH or PDSCH may indicate that the PDCCH or PDSCH is a QCL with SSB or CSI-RS. The UE may (then) receive the PDCCH or PDSCH by using a reception beam for receiving the SSB or CSI-RS.

The configuration of the TCI state for the PDCCH may be provided by at least one configuration/parameter of CORESET (e.g., TCI-statepdcch-ToAddList and/or TCI-statepdcch-todeleaselist) for transmitting the PDCCH therein. When at least one configuration (e.g., TCI-statepdcch-ToAddList and/or TCI-statepdcch-torrelease list) provides more than one TCI state for CORESET, the MAC CE command may (need to) activate one TCI state from the TCI states. The TCI state is provided by at least one configuration (e.g., TCI-statepdcch-ToAddList and/or TCI-statepdcch-torrelease list).

When the UE receives a MAC CE activation command for one of the TCI states, the UE may be in the UL slot The activation command is applied in the first DL slot thereafter. For example, when the SCS of the UL slot is equal to the SCS of the DL slot, the first DL slot may be slot +>k may be an UL slot in which the UE may transmit PUCCH with HARQ-ACK information for the PDSCH providing the activation command. μ may be SCS configuration for PUCCH.May be the total number of slots per subframe μ for SCS configuration. It should be noted that the configuration (e.g., TCI-StatesPDCCH-ToAddList) may configure (e.g., include) a list of indices or IDs (e.g., indicated by "TCI-StateId") corresponding to a TCI status list configured by a configuration n PDSCH-Config (e.g., TCI-StatesToAddModList) for the same active DL BWP as PDCCH-Config including the CORESET configuration.

The configuration of the TCI state for the PDSCH may be configured by at least one of DL BWP transmitting the PDSCH (e.g., TCI-States-ToAddModList and/or tci-States-ToReleaseList). The MAC CE activation command may be used to map up to 8 TCI states to a code point of a DCI field (e.g., a "transmission configuration indication" field) in one DL BWP. When the UE receives a MAC CE activation command for mapping between the TCI state and the code points of the DCI field, the UE may be in the slot The activation command is applied in the first time slot thereafter. k may be a slot in which the UE may transmit a PUCCH with HARQ-ACK information for the PDSCH providing the activation command. μ may be SCS configuration for PUCCH.May be the total number of slots per subframe μ for SCS configuration. The TCI state of the PDSCH may be determined based on a code point indicated in a DCI field (e.g., a "transmission configuration indication" field) of the scheduled PDSCH.

In Rel-15 NR, to receive PDSCH, some resource elements in PDSCH may be used by the gNB for other purposes, which may be considered unavailable to the UE when receiving PDSCH. The configuration (or indication) of resource elements not available for (receiving) PDSCH has been discussed. The "rateMatchPatterToAddModList" indicating the list of rate matching modes may be included in the PDSCH-Config associated with DL BWP. Each rate matching pattern in the list of rate matching patterns may be indicated by a "RateMatchPattern" included in a "RateMatchPattern toaddmodlist". When the DCI of the scheduled PDSCH is DCI format 1_1 or DCI format 1_2, the DCI may indicate which rate matching mode should be applied (e.g., which resource elements indicated by the rate matching mode should be considered as unavailable).

The UE may be configured with one or more ZP CSI-RS resource set configurations for aperiodic, semi-static, and periodic time domain behavior in DL BWP. Each ZP CSI-RS resource set may include a maximum of 16 ZP CSI-RS resources. The periodic ZP CSI-RS resource set may be configured by "p-ZP-CSI-RS-resource set" in PDSCH-Config associated with DL BWP. The semi-static ZP CSI-RS resource set may be configured by "sp-ZP-CSI-RS-ResourceSetsToAddModList" in PDSCH-Config associated with DL BWP. The aperiodic ZP CSI-RS resource set may be configured by "adaptive-ZP-CSI-RS-resource sets toaddmodlist" in PDSCH-Config associated with DL BWP. The resource elements indicated by the periodic ZP CSI-RS resource sets may be considered unavailable for (receive) PDSCH. When triggering and activation of PDSCH is applied, the resource elements indicated by the semi-static ZP CSI-RS resource set may be considered unavailable for (receiving) PDSCH. When triggering and activation of PDSCH is applied, the resource elements indicated by the aperiodic ZP CSI-RS resource set may be considered unavailable for (receiving) PDSCH.

For aperiodic ZP CSI-RS, the UE may be configured with a "ZP CSI-RS trigger" field (for use in triggering aperiodic ZP CSI-RS (e.g., an aperiodic ZP CSI-RS resource set comprising one or more ZP CSI-RS resources) in DCI format 1_1 or DCI format 1_2. Each non-zero code point of the "ZP CSI-RS trigger" field in DCI format 1_1 may trigger one aperiodic ZP CSI-RS resource set (e.g., "ZP-CSI-RS-resource set") in "aperiodic-ZP-CSI-RS-resourcesettoadmodlist" by indicating a corresponding aperiodic ZP CSI-RS resource set ID. The DCI code point "01" of the "ZP CSI-RS trigger" field may trigger a resource set with "ZP-CSI-RS-ResourceSID" set to "1". The DCI code point "10" of the "ZP CSI-RS trigger" field may trigger a resource set with "ZP-CSI-RS-resource estid" set to "2". The DCI code point "11" of the "ZP CSI-RS trigger" field may trigger a resource set with "ZP-CSI-RS-resource estid" set to "3". The DCI code point "00" of the "ZP CSI-RS trigger" field may be reserved for non-triggering (e.g., disabling) aperiodic ZP CSI-RS. Each non-zero code point of the "ZP CSI-RS trigger" field in DCI format 1_2 may trigger one of the non-periodic ZP CSI-RS resource sets (e.g., "ZP-CSI-RS-resource set") in "aperiodic-ZP-CSI-RS-resource estto addmodlistdi-1-2" by indicating a corresponding non-periodic ZP CSI-RS resource set ID.

For semi-static ZP CSI-RS, when the UE transmits PDSCH with the MAC CE carrying the activation command for (activating) ZP CSI-RS resources in slot nIn PUCCH of corresponding HARQ-ACK information, UE hypothesis of PDSCH RE mapping corresponding to activated ZP CSI-RS resource can be obtained from time slot n+The first time slot after that starts the application. μ may be SCS configuration for PUCCH. On the other hand, when the UE transmits PUCCH with HARQ-ACK information corresponding to PDSCH carrying a deactivation command MAC CE for activated ZP CSI-RS resources in slot n, the UE hypothesis corresponding to PDSCH RE mapping of deactivated ZP CSI-RS resources may be derived from slot->The first time slot after that starts the application. μ may be SCS configuration for PUCCH.

The PUCCH resources for HARQ-ACK feedback of the group common PDSCH may be configured in a "PUCCH-configuration list" that is different from the "PUCCH-configuration list" of the PUCCH resources for HARQ-ACK feedback of the dedicated PDSCH, CSI, and SR. In other words, the UE may be configured with two "PUCCH-configurationlists", each of which may include a maximum of two PUCCH-configs. The first PUCCH-configuration in the "PUCCH-configuration list" may include a configuration of PUCCH resources having a lower physical layer priority. The second PUCCH-configuration in the "PUCCH-configuration list" may include a configuration of PUCCH resources having a higher physical layer priority. The "PUCCH-ConfigurationList" for the group common PDSCH may be configured as part of the CFR configuration, or may be configured together with other "PUCCH-configurationlists" for the dedicated PDSCH, CSI, and SR.

In this application, PUCCH resources configured by "PUCCH-ConfigurationList" for the group common PDSCH may be referred to as a multicast PUCCH. The PUCCH resources configured by the "PUCCH-ConfigurationList" for dedicated PDSCH, CSI, and SR may be referred to as unicast PUCCH. In addition, the dedicated PDCCH and the dedicated PDSCH may be referred to as a unicast PDCCH and a unicast PDSCH, respectively.

The problem regarding multicast reception/transmission of PDCCH/PDSCH may be described as follows.

TCI status indication for group common PDCCH and group common PDSCH

PDCCH-Config associated with CFR and PDSCH-Config associated with CFR may include TCI status configuration. Thus, it may be necessary to define whether the configuration (or activation) of the TCI state for the group common PDCCH is based on PDCCH-Config associated with CFR or PDCCH-Config associated with activated DL BWP including CFR. In addition, it may be desirable to define whether the configuration (or activation) of the TCI state for the group common PDSCH is based on PDSCH-Config associated with CFR or PDSCH-Config associated with activated DL BWP including CFR.

An implementation of TCI status indication for processing a group common PDCCH and/or a group common PDSCH may be described as follows.

In some embodiments, PDSCH-Config associated with the first DL BWP (e.g., in a first DL BWP configuration configuring the first DL BWP) may include at least one configuration (e.g., a "TCI-stateto addmodlist" field and/or a "TCI-stateto releaselist" field) configuration (or indication) TCI state list.

In some embodiments, PDSCH-Config associated with a CFR (e.g., in a CFR configuration configuring the CFR) may not include at least one first configuration (e.g., a "tci-statestoadmodlist" field and/or a "tci-statestorelealist" field). Thus, signaling overhead may be reduced. The configuration of CORESET configured by PDCCH-Config associated with CFR may include at least one second configuration (e.g., a "tci-statepdcch-ToAddList" field and/or a "tci-statepdcch-todeleaselist" field). Each of the at least one second configuration may include an index or ID (e.g., indicated by "TCI-StateId") list corresponding to a TCI state configured by a configuration in PDSCH-Config associated with the first DL BWP (e.g., a "TCI-statestoadmodlist" field).

In some embodiments, the first DL BWP may be determined as a DL BWP including a CFR. In some embodiments, when more than one DL BWP comprises a CFR, the first DL BWP may be determined to activate the DL BWP. In some other embodiments, when more than one DL BWP includes a CFR, the first DL BWP may be determined as a DL BWP having the same number as the CFR.

In some other embodiments, the first DL BWP may be determined as a DL BWP having at least one specific configuration ("BWP-DownlinkCommon" field and/or "BWP-downlinklinked" field) including the configuration of the CFR.

In some other embodiments, the first DL BWP may be determined as a DL BWP indicated by a specific configuration (e.g., "BWP-Id") included in the configuration of the CFR.

In some other embodiments, the first DL BWP may be determined as a DL BWP indicated by a specific configuration (e.g., "BWP-Id") included in the CORESET configuration of the CFR.

In some other embodiments, the first DL BWP may be a current active DL BWP or an active DL BWP when a PDSCH configuration associated with the CFR is received.

In some embodiments, the activation command MAC CE may be carried in a dedicated PDSCH or a group public PDSCH to indicate the TCI state applied to CORESET. When the activation command MAC CE is carried in the group common PDSCH, the timing at which the activation command should be applied may be aligned among a group of UEs receiving the group common PDSCH. The activation command may be applied using a fixed timeline related to the end of the group common PDSCH. The timeline for the end of PUCCH transmission with HARQ-ACKs corresponding to the group common PDSCH may not be used to apply the activate command, as PUCCH transmission may be different for different UEs. For example, a fixed timeline may be defined asm may correspond to UL slots overlapping the end of the group common PDSCH. max { dl-DataToUL-ACK } may be the maximum value configured in a particular configuration/parameter (e.g., "dl-DataToUL-ACK") in PUCCH-Config associated with CFR. / >May be the total number of slots per subframe μ for SCS configuration. For another example, a fixed timeline may be defined asm+m may correspond to UL slots overlapping the end of the group common PDSCH. K (K) _1,max May be the maximum configured in a particular configuration/parameter (e.g., "dl-DataToUL-ACK") in PUCCH-Config associated with CFR. />May be the total number of slots per subframe μ for SCS configuration. It should be noted that the computation of the fixed time line under NTN and TN networks may be different.

In some embodiments, for an activation command carried in the group common PDSCH, the gNB may (needs) align the ID of the TCI state (e.g., indicated by "TCI-StateId") included in the configuration of the CORESET configuration of CFR for a group of UEs (e.g., the "TCI-statepdcch-ToAddList" field). For example, when a UE is configured with a TCI state with an ID (e.g., indicated by "TCI-StateId") for unicast service and the UE determines to join the multicast service after other UEs have joined the multicast service, the gNB may (need) reconfigure the TCI state of the UE if the ID (e.g., indicated by "TCI-StateId") is included in the configuration of CORESET configuration of CFR of other UEs (e.g., the "TCI-statepdcch-ToAddList" field). In some embodiments, a field (e.g., a "TCI State ID" field) in an activation command received in the group common PDSCH may be used to indicate a sequence number position of the TCI State indicated in the CORESET configuration indicated by the activation command (e.g., a "TCI-statepdcch-ToAddList" field). For example, when a field in an activate command (e.g., the "TCI State ID" field) indicates 0, a first TCI State in the configuration of CORESET indicated by the activate command (e.g., the "TCI-statepdcch-ToAddList" field) may be activated. For another example, when a field in the activate command (e.g., the "TCI State ID" field) indicates 1, a second TCI State in the CORESET configuration indicated by the activate command (e.g., the "TCI-statepdcch-ToAddList" field) may be activated. The gNB may (need) align with the ID of the CORESET configured for the CFR of the UE group (e.g., indicated by "control ResourceSetid"). The x value in a field in the activate command (e.g., the "CORESET ID" field) may be used to indicate CORESET configured for CFR, with the (x+1) th lowest ID of the serving cell indicated by the activate command (e.g., indicated by the "control resource ID"). Therefore, configuration flexibility can be improved.

In some other embodiments, PDSCH-Config associated with CFR may include at least one configuration (e.g., a "tci-statestoadmodlist" field and/or a "tci-statestorelealist" field). The configuration of CORESET configured by PDCCH-Config associated with CFR may include at least one second configuration (e.g., a "tci-statepdcch-ToAddList" field and/or a "tci-statepdcch-todeleaselist" field). Each of the at least one second configuration may include an index or list of IDs (e.g., indicated by "TCI-StateId") corresponding to TCI states configured by configurations in PDSCH-Config associated with CFR (e.g., the "TCI-stateto addmodlist" field). The field (e.g., "TCI State ID" field) in the activate command MAC CE may indicate a TCI State, where ID (e.g., indicated by "TCI-StateId") is equal to the value of the field, the TCI State being configured by the configuration in PDCCH-Config associated with the CFR (e.g., "TCI-stateto addmodlist" field), when the field (e.g., "CORESET ID" field) of the activate command MAC CE indicates CORESET configured by PDCCH-Config associated with the CFR. Benefits of these implementations may include, but are not limited to, that the configuration of CFR is not affected by the (re) configuration of dedicated PDSCH or dedicated PDCCH.

In some embodiments, when the PDSCH-Config associated with the CFR does not include at least one configuration (e.g., the "TCI-stateto addmodlist" field and/or the "TCI-stateto release list" field), each ID (e.g., indicated by the "TCI-StateId") included in at least one configuration (e.g., the "TCI-statepdcch-to addlist" field and/or the "TCI-statepdcch-to release list" field) in the CORESET configuration associated with the CFR may be an index of the TCI state corresponding to the configuration (e.g., the "TCI-stateto addmodlist" field) in the PDSCH-Config by the first DL BWP.

In some other embodiments, the first DL BWP may be determined as a DL BWP having at least one configuration ("BWP-downlinked communication" field and/or "BWP-downlinked" field) including the configuration of the CFR.

In some embodiments, an ID of a TCI state configured in at least one of PDSCH-Config associated with the CFR (e.g., a "TCI-stateto addmodlist" field and/or a "TCI-stateto releaselist" field) (e.g., indicated by a "TCI-StateId") may be different from an ID of a TCI state configured in at least one of PDSCH-Config associated with the first DL BWP (e.g., a "TCI-stateto addmodlist" field and/or a "TCI-stateto releaselist" field). Thus, the number of TCI states that need UE processing may be reduced. The configuration of CORESET configured by PDCCH-Config associated with CFR may include at least one configuration (e.g., a "tci-statepdcch-ToAddList" field and/or a "tci-statepdcch-todeleaselist" field). Each of the at least one configuration may include a list of indexes or IDs (e.g., indicated by "TCI-StateId") corresponding to TCI states configured by a configuration in PDSCH-Config associated with the CFR (e.g., the "TCI-statestoadmodlist" field), or each of the at least one configuration may include a list of indexes or IDs (e.g., indicated by "TCI-StateId") corresponding to TCI states configured by a configuration in PDSCH-Config associated with the first DL BWP (e.g., the "TCI-statestoadmodlist" field).

In some embodiments, the activation command MAC CE may be carried in a dedicated PDSCH or a group public PDSCH to indicate the TCI state applied to CORESET. When the activation command MAC CE is carried in the group common PDSCH, the timing at which the activation command should be applied may be aligned among a group of UEs receiving the group common PDSCH. The activation command may be applied using a fixed timeline related to the end of the group common PDSCH. The timeline for the end of PUCCH transmission with HARQ-ACKs corresponding to the group common PDSCH may not be used to apply the activate command, as PUCCH transmission may be different for different UEs. For example, a fixed timeline may be defined asm may correspond to UL slots overlapping the end of the group common PDSCH. max { dl-DataToUL-ACK } may be the maximum value configured in a particular configuration/parameter (e.g., "dl-DataToUL-ACK") in PUCCH-Config associated with CFR. />May be the total number of slots per subframe μ for SCS configuration. For another example, a fixed timeline may be defined as m+m may correspond to UL slots overlapping the end of the group common PDSCH. K (K) _1,max May be the maximum configured in a particular configuration/parameter (e.g., "dl-DataToUL-ACK") in PUCCH-Config associated with CFR. / >May be the total number of slots per subframe μ for SCS configuration. It should be noted that the computation of the fixed time line under NTN and TN networks may be different.

In some embodiments, PDSCH-Config associated with a CFR (e.g., in a CFR configuration configuring the CFR) may include at least one configuration (e.g., a "tci-stateto addmodlist" field and/or a "tci-stateto releaselist" field). The activate/deactivate command MAC CE may be used to map a TCI state configured by at least one configuration to a code point of a first field (e.g., "transmission configuration indication"), the DCI format being used to schedule a group common PDSCH in the CFR. If there is a TCI state with a configured ID (e.g., indicated by "TCI-StateId" = 'i'), a second field (e.g., "Ti") in the activate/deactivate command MAC CE may indicate an activated/deactivated state of the TCI state with the ID (e.g., indicated by "TCI-StateId" = 'i'). Otherwise, the MAC entity of the UE may ignore the second field.

In some embodiments, the activation/deactivation command MAC CE may be carried in a dedicated PDSCH or a group public PDSCH. In order to distinguish an activation/deactivation command MAC CE from a second activation/deactivation command MAC CE, a first LCID for the activation/deactivation command MAC CE may be different from a second LCID for the second activation/deactivation command MAC CE. The second activation/deactivation command MAC CE may be used to map a TCI state configured by at least one configuration (e.g., a "TCI-statestoadmodlist" field and/or a "TCI-statestorelease list" field) in the PDSCH-Config associated with the DL BWP to a code point (e.g., a "transmission configuration indication") of a DCI format for scheduling a dedicated PDSCH (e.g., a legacy activation/deactivation command MAC CE).

In some implementations, a field (e.g., a "CFR ID") may be included in the activation/deactivation command MAC CE to indicate the CFR to which the activation/deactivation command is applied. The length of this field may be 2 bits, 3 bits or 4 bits. In some embodiments, a legacy activation/deactivation command MAC CE may be transmitted in a group common PDSCH in a CFR to map TCI states configured by at least one of the fields in PDSCH-Config associated with the CFR (e.g., a "TCI-stateto addmodlist" field and/or a "TCI-stateto release list" field) to code points of fields of a DCI format (e.g., a "transmission configuration indication") used to schedule the group common PDSCH in the CFR. In other words, the interpretation of the MAC CEs received in the group common PDSCH may be different from the interpretation of the MAC CEs received in the dedicated PDSCH. The UE may ignore a field (e.g., "BWP ID") in the activation/deactivation command MAC CE. In some embodiments, a legacy activation/deactivation command MAC CE may be transmitted in a dedicated PDSCH in a CFR to map a TCI state configured by at least one configuration (e.g., a "TCI-stateto addmodlist" field and/or a "TCI-stateto release list" field) in a DCI format (e.g., a "transmission configuration indication") for scheduling a group common PDSCH in the CFR in a dedicated PDSCH. In other words, the interpretation of MAC CEs received in dedicated PDSCH within CFR may be different from the interpretation of MAC CEs received in dedicated PDSCH outside CFR. The UE may ignore a field (e.g., "BWP ID") in the activation/deactivation command MAC CE.

In some embodiments, when the PDSCH-Config associated with the CFR does not include at least one configuration (e.g., the "TCI-stateto addmodlist" field and/or the "TCI-stateto releaselist" field), if there is a TCI state (e.g., indicated by "TCI-StateId" = 'i') with an ID configured in the PDSCH-Config of the first DL BWP, a second field (e.g., "Ti") in the activate/deactivate command MAC CE may indicate an activation/deactivation state of the TCI state with the ID (e.g., indicated by "TCI-StateId" = 'i').

In some other embodiments, the first DL BWP may be determined as a DL BWP indicated by a specific configuration (e.g., "BWP-Id") included in the PDSCH-Config associated with the CFR.

In some embodiments, the ID of the TCI state configured in at least one configuration in the PDSCH (e.g., the "TCI-StatesToAddModList" field and/or the "TCI-StatesToReleaseList" field) (e.g., indicated by the "TCI-StateId") -the configuration associated with the CFR may be located in the PDSCH-Config associated with the first DL BWP with the ID of the TCI state configured in at least one configuration (e.g., the "TCI-StatesToAddModList" field and/or the "TCI" (e.g., indicated by the "TCI-StateId") field. Thus, the number of TCI states that need UE processing may be reduced. In some embodiments, if there is a TCI state with an ID (e.g., indicated by "TCI-StateId" = 'i') configured in PDSCH-Config associated with CFR or in PDSCH-Config of the first DL BWP, a second field (e.g., "Ti") in the activate/deactivate command MAC CE may indicate an activation/deactivation state of the TCI state with the ID (e.g., indicated by "TCI-StateId" = 'i').

Rate matching mode indication for group common PDSCH

PDSCH-Config associated with CFR may include rate matching mode configuration. Thus, it may be desirable to determine a configuration (or indication) defining a rate matching pattern for the group common PDSCH, whether based on PDSCH-Config for CFR or PDSCH-Config for activated DL BWP including CFR.

An implementation for handling rate matching mode indication for the group common PDSCH may be described as follows.

In some embodiments, PDSCH-Config associated with the first DL BWP (e.g., configuring the first DL BWP in its configuration) may include at least one configuration (e.g., a "rateetchpattern toaddmodlist" field) that configures (or indicates) the rate matching mode list.

In some embodiments, PDSCH-Config associated with a CFR (e.g., in a CFR configuration configuring the CFR) may not include at least one configuration (e.g., a "rateetchpatterntoaddmodlist" field and/or a "rateetchpatterntorrelease list" field) that configures (or indicates) a rate matching pattern list. Thus, signaling overhead may be reduced. In some embodiments, PDSCH-Config associated with CFR may be included in at least one configuration. The at least one configuration may include, but is not limited to, a "rateMatchPattern Group1" field and/or a "rateMatchPattern Group2" field. When an ID (e.g., indicated by "ratematchpattern ID") is indicated by a first configuration (e.g., "bwpLevel"), each of the at least one configuration may configure (or indicate) a list of indexes or IDs (e.g., indicated by "ratematchpattern ID") corresponding to a rate matching pattern configured by PDSCH-Config associated with the first DL BWP. Each ID may be indicated by a second configuration (e.g., "cellLevel" or "bwpLevel").

In some other embodiments, the first DL BWP may be determined to be DL BWP having at least one configuration (e.g., a "BWP-DownlinkCommon" field and/or a "BWP-downlinklinked" field) including the configuration of CFR.

In some other embodiments, the first DL BWP may be determined as a DL BWP indicated by a configuration (e.g., "BWP-Id") included in the configuration of the CFR.

In some other embodiments, the first DL BWP may be determined as a DL BWP indicated by a configuration (e.g., "BWP-Id") included in the PDSCH-Config associated with the CFR. In some other embodiments, the configuration (e.g., "BWP-Id") may be at least one configuration (e.g., "rateetchpatterngroup 1" field and/or "rateetchpatterngroup 2" field) included in the PDSCH-Config associated with the CFR.

In some implementations, the rate matching pattern group may be dynamically configured by at least one configuration (e.g., a "rateMatchPattern group1" field and/or a "rateMatchPattern group2" field) in the PDSCH-Config associated with the CFR. If the corresponding bit of a field (e.g., a "rate matching indicator") of the DCI format of the scheduled group common PDSCH in the CFR is equal to 1, the rate matching pattern group may include an index (list) of rate matching patterns forming a union of resource sets not available for the group common PDSCH in the CFR.

In some other embodiments, PDSCH-Config associated with a CFR (e.g., in configuring CFR configuration of the CFR) may include at least one configuration (e.g., a "rateMatchPatternToAddModList" field and/or a "ratematchpatterntorrelease list" field) that configures (or indicates) a rate matching pattern list. In some embodiments, PDSCH-Config associated with CFR may include at least one configuration. The at least one configuration may include, but is not limited to, a "rateMatchPattern Group1" field and/or a "rateMatchPattern Group2" field. When an ID (e.g., indicated by "ratematchpattern ID") is indicated by a first configuration (e.g., "bwpLevel"), each of the at least one configuration may configure (or indicate) an index or ID (e.g., indicated by "ratematchpattern ID") corresponding to a rate matching pattern configured by a PDSCH-Config associated with the first DL BWP (list). Each ID may be indicated by a second configuration (e.g., "cellLevel" or "bwpLevel"). Benefits of these implementations may include, but are not limited to, CORESET configured for CFR may not be configured as rate matching patterns in the PDSCH-Config of DL BWP (e.g., the "rateMatchPatternToAddModList" field), or the configuration of CFR is not affected by the (re) configuration of dedicated PDSCH.

In some implementations, PDSCH-Config associated with CFR may include at least one configuration (e.g., a "rateetchpatternto addlist" field and/or a "rateetchpatternto release list" field). Each of the at least one configuration may include an index or ID (e.g., indicated by a "RateMatchPatternId") list corresponding to a rate matching mode configured by a configuration (e.g., a "rateMatchPatternToAddModList") in the PDSCH-Config associated with the first DL BWP.

In some other embodiments, the first DL BWP may be determined as a DL BWP having at least one configuration (e.g., a "BWP-downlinked communication" field and/or a "BWP-downlinked communication"), the at least one configuration including a CFR configuration.

In some other embodiments, the first DL BWP may be determined as a DL BWP indicated by a configuration (e.g., "BWP-Id") included in the CFR configuration.

In some embodiments, when the rate matching mode is configured by a configuration of CORESET indicated as CFR configuration (e.g., a "control resource" field), for a rate matching mode configured by at least one of PDSCH-Config associated with CFR (e.g., a "rateetchpatterntoaddmodlist" field and/or a "rateetchpattetterto release list" field), resource elements in CFR that are not available for group common PDSCH may be determined by monitoring opportunities for search space of CFR configuration associated with CORESET. In some implementations, resource elements determined by monitoring opportunities for search spaces associated with CORESET that are not configured for CFR may not be considered unavailable for the group common PDSCH in CFR.

In some implementations, a rate matching pattern configured in a first configuration (e.g., a "rateetchpatterntoaddmodlist" field) in PDSCH-Config associated with CFR, a resource block level bitmap configured by a second configuration (e.g., "resource blocks") may be used to indicate the rate matching pattern in the frequency domain. A symbol level bitmap configured by a third configuration (e.g., "symbol inresourceblock") may be used to indicate symbols to which a rate matching pattern configured by the second configuration (e.g., "resourceblock") applies. The bitmap configured by the second configuration (e.g., "resourceBlocks") may identify PRBs within the CFR. The first/leftmost bit may correspond to the PRB with the lowest PRB index in the CFR.

In some implementations, when an ID is indicated by a first configuration (e.g., "cfrLevel") (e.g., indicated by "RateMatchPatternId"), each of at least one configuration (e.g., "rateMatchPatternGroup1" field and/or "rateMatchPatternGroup2" field) may configure (or indicate) an index or list of IDs (e.g., indicated by "RateMatchPatternId") corresponding to a rate matching pattern configured by a configuration (e.g., "rateMatchPatternToAddModList") in PDSCH-Config associated with the CFR. Each ID may be indicated by a second configuration (e.g., "cellLevel" or "cfrLevel"). At least one configuration may indicate "RateMatchPatternGroup" as shown in table 9.

TABLE 9

In some implementations, when an ID is indicated by a first configuration (e.g., "bwpLevel") (e.g., indicated by "RateMatchPatternId"), each of the at least one configuration (e.g., "rateMatchPatternGroup1" field and/or "rateMatchPatternGroup2" field) can configure (or indicate) an index or ID (e.g., "ratematchpatternmodlist" field) corresponding to a rate matching mode configured by a PDSCH-Config (e.g., "ratematchpattettrimlist") associated with the first DL BWP. Each ID may be indicated by a second configuration (e.g., "cellLevel", "bwpLevel", or "cfrLevel").

In some other embodiments, the first DL BWP is determined to be a DL BWP having at least one configuration (e.g., a "BWP-downlinked communication" field and/or a "BWP-downlinked" field) including the configuration of the CFR.

In some other embodiments, the first DL BWP may be determined as a DL BWP indicated by a configuration (e.g., "BWP-Id") included in the PDSCH-Config associated with the CFR. In some other embodiments, the configuration (e.g., a "BWP-Id" IE) may be at least one configuration (e.g., a "rateetchpatterngroup 1" field and/or a "rateetchpatterngroup 2" field) included in the PDSCH-Config associated with the CFR.

The at least one configuration may indicate "RateMatchPatternGroup" as shown in table 10.

Table 10

In some implementations, an ID of a rate matching mode (e.g., indicated by a "RateMatchPatternId") configured in at least one configuration (e.g., a "rateMatchPatternToAddModList" field and/or a "ratematchpatterntorrelease list" field) in a PDSCH-Config associated with the CFR may be different from an ID of a rate matching mode (e.g., indicated by a "RateMatchPatternId") configured in at least one configuration (e.g., a "rateMatchPatternToAddModList" field and/or a "ratematchpatterntorrelease list" field) in a PDSCH-Config associated with the first DL BWP. Thus, the number of rate matching modes that need to be handled by the UE may be reduced. In some implementations, when the ID (e.g., by the "rateetchpatternid") is indicated by the first configuration (e.g., "bwpLevel"), each of the at least one configuration (e.g., "rateetchpatterngroup 1" field and/or "rateetchpatterngroup 2" field) may include an index (list) corresponding to a rate matching pattern configured by a configuration in PDSCH-Config associated with CFR (e.g., "rateetchpattetterto addmodlist" field) or a rate matching pattern configured by a configuration in PDSCH-Config associated with the first DL BWP (e.g., "rateetchpatternodadlist" field). Each ID may be indicated by a second configuration (e.g., "cellLevel" or "bwpLevel").

ZP CSI-RS indication for group common PDSCH

PDSCH-Config associated with CFR may include ZP CSI-RS configuration. Thus, a configuration (or indication) of ZP CSI-RS for the group common PDSCH may need to be defined based on PDSCH-Config for CFR or PDSCH-Config for activated DL BWP including CFR.

An implementation of ZP CSI-RS indication for handling group common PDSCH may be described as follows.

In some embodiments, PDSCH-Config associated with (e.g., in a first DL BWP configuration configuring) the first DL BWP may include at least one list of specific configuration (e.g., a "ZP-CSI-RS-resource toaddmodlist" field) configuration (or indication) ZP CSI-RS resources.

In some embodiments, PDSCH-Config associated with the CFR (e.g., in a CFR configuration configuring the CFR) may not include at least one specific configuration (e.g., a "ZP-CSI-RS-ResourceToAddModList" field and/or a "ZP-CSI-RS-resourcetorelease list" field) configuration (or indication) list of ZP CSI-RS resources. Thus, signaling overhead may be reduced. In some embodiments, PDSCH-Config associated with CFR may include at least one configuration. The at least one configuration may include, but is not limited to, an "apidic-ZP-CSI-RS-ResourceSetsToAddModList" field, an "apidic-ZP-CSI-RS-resourcesetstorrelease list" field, an "sp-ZP-CSI-RS-ResourceSetsToAddModList" field, or an "sp-ZP-CSI-RS-resourcesetstorrelease list" field. Each of the at least one configuration may configure (or indicate) a list of ZP CSI-RS resource sets. The list of ZP CSI-RS resource sets configured by each of the at least one configuration may be a list of aperiodic or semi-static ZP CSI-RS resource sets that are configured or (configured) released. The ZP CSI-RS resources in each of the list of ZP CSI-RS resource sets may be indicated (or identified) by a list of indices or IDs (e.g., indicated by "ZP-CSI-RS-resource ID") corresponding to CSI-RS resources ZP configured by a particular configuration (e.g., a "ZP-CSI-RS-ResourceToAddModList" field) in PDSCH-Config associated with the first DL BWP.

In some other embodiments, PDSCH-Config associated with a CFR (e.g., in a CFR configuration configuring the CFR) may include at least one particular configuration (e.g., a "ZP-CSI-RS-ResourceToAddModList" field and/or a "ZP-CSI-RS-resourcetorelease list" field) configuration (or indication) list of ZP CSI-RS resources. In some embodiments, PDSCH-Config associated with CFR may include at least one configuration. The at least one configuration may include, but is not limited to, an "adaptive-ZP-CSI-RS-ResourceESetsToAddModList" field, an "adaptive-ZP-CSI-RS-ResourceESetsToReleaseList" field, an "sp-ZP-CSI-RS-ResourceESetsToAddModList" field, or an "sp-ZP-CSI-RS-ResourceESetsToReleaseList" field. Each of the at least one configuration may configure (or indicate) a list of ZP CSI-RS resource sets. The list of ZP CSI-RS resource sets configured by each of the at least one configuration may be a list of aperiodic or semi-static ZP CSI-RS resource sets that are configured or (configured) released. The ZP CSI-RS resources in each of the lists of ZP CSI-RS resource sets may be indicated (or identified) by an index or ID list (e.g., indicated by "ZP-CSI-RS-resource ID") corresponding to ZP CSI-RS resources configured by a particular configuration in PDSCH-Config associated with the CFR (e.g., the "ZP-CSI-RS-resource to addmodlist" field).

In some embodiments, the ID of the ZP CSI-RS resource configured in at least one specific configuration (e.g., the "ZP-CSI-RS-ResourceToAddModList" and/or the "ZP-CSI-RS-resourcetorelease list" field) in the PDSCH-Config associated with the CFR may be different from the ID of the ZP CSI-RS resource configured in at least one specific configuration (e.g., the "ZP-CSI-RS-ResourceToAddModList" field and/or the "ZP-CSI-RS-resourcetorelease list" field) in the PDSCH-Config associated with the first DL BWP (e.g., indicated by "ZP-CSI-RS-ResourceId"). Accordingly, the number of ZP CSI-RS resources that the UE needs to process may be reduced. In some embodiments, PDSCH-Config associated with CFR may include at least one configuration. The at least one configuration may include, but is not limited to, an "adaptive-ZP-CSI-RS-ResourceLetsToAddModList" field, an "adaptive-ZP-CSI-RS-ResourceLetsToReleaseList" field, an "sp-ZP-CSI-RS-ResourceLetsToAddModList" field, or an "sp-ZP-CSI-RS-ResourceLetsToReleaseList" field. Each of the at least one configuration may configure (or indicate) a list of ZP CSI-RS resource sets. The list of ZP CSI-RS resource sets configured by each of the at least one configuration may be a list of aperiodic or semi-static ZP CSI-RS resource sets that are configured or (configured) released. The ZP CSI-RS resources in each of the lists of ZP CSI-RS resource sets may be indicated (or identified) by an index or ID list (e.g., indicated by "ZP-CSI-RS-resource eid") corresponding to ZP CSI-RS resources configured by a particular configuration in PDSCH-Config associated with the CFR (e.g., the "ZP-CSI-RS-resource to addmodlist" field), or by ZP CSI-RS resources configured by a particular configuration in PDSCH-Config associated with the CFR (e.g., the "ZP-CSI-RS-resource to addmodlist" field).

In some embodiments, DCI (e.g., DCI format) for scheduling a group common PDSCH in a CFR may be configured with (e.g., include) a DCI field for triggering an aperiodic ZP CSI-RS (e.g., an aperiodic ZP CSI-RS resource set including one or more ZP CSI-RS resources). The DCI format may be DCI format 1_0 of CRC scrambled by G-RNTI, DCI format 1_1, or DCI format 1_2 of CRC scrambled by G-RNTI. In some other embodiments, the DCI format may be a new DCI format with CRC scrambled by G-RNTI. The DCI field for triggering the aperiodic ZP CSI-RS resource set may be a "ZP CSI-RS trigger" field. Each non-zero code point of the DCI field in the DCI format may trigger one of the set of PDSCH-Config configured ZP CSI-RS resource sets associated with the CFR (e.g., aperiodic "ZP-CSI-RS-resource set" in the list "apidic-ZP-CSI-RS-resource setto addmodlist") by indicating an ID of one of the set of ZP CSI-RS resource sets. For example, DCI code point "01" of the DCI field may trigger a resource set of "ZP-CSI-RS-ResourceSetId" set to "1", DCI code point "10" of the DCI field may trigger a resource set of "ZP-CSI-RS-ResourceSetId" set to "2", and DCI code point "11" of the DCI field may trigger a resource set of "ZP-CSI-RS-ResourceSetId" set to "3". The DCI code point "00" of the DCI field may be reserved to disable (e.g., not) triggering any aperiodic ZP CSI-RS. When the DCI triggers the aperiodic ZP CSI-RS resource set, the resource elements of one or more ZP CSI-RS resources included in the indicated aperiodic ZP CSI-RS resource set may not receive the group common PDSCH scheduled by the DCI. The maximum number of configured resource sets (e.g., aperiodic ZP-CSI-RS-ResourceSet(s) per BWP configuration) may be 3.

In some embodiments, a first activation/deactivation command MAC CE (e.g., a legacy activation/deactivation command MAC CE) for activating or deactivating a first semi-static ZP CSI-RS resource set may be carried in a dedicated PDSCH or in a group common PDSCH carried in a CFR. The first semi-static ZP CSI-RS resource set may (be considered) not be available for receiving dedicated PDSCH in CFR. In some embodiments, the second activation/deactivation command MAC CE for activating or deactivating the second semi-static ZP CSI-RS resource set may be carried in a dedicated PDSCH or a group common PDSCH in the CFR. The second semi-static ZP CSI-RS resource set may (be considered) not be available in the group common PDSCH in the receiving CFR. In some implementations, when the first activation/deactivation command MAC CE is carried in the dedicated PDSCH, the first LCID of the first activation/deactivation command MAC CE may be different from the second LCID for the second activation/deactivation command MAC CE in order to distinguish the first activation/deactivation command MAC CE from the second activation/deactivation command MAC CE.

In some embodiments, when a new activation/deactivation command MAC CE having a different LCID (e.g., different from the first LCID) is carried in the dedicated PDSCH, it may be determined that the CFR of the new activation/deactivation command should be applied (implicitly) as the CFR contained within the DL BWP receiving the dedicated PDSCH. Thus, a specific field (e.g., "BWP ID") of the new activation/deactivation command MAC CE may be ignored. In some other embodiments, the CFR to which the new activation/deactivation command should be applied may be (implicitly) determined as a CFR included in the DL BWP indicated by a specific field (e.g., "BWP ID") of the new activation/deactivation command MAC CE. In some other embodiments, the CFR to which the new activation/deactivation command should be applied may be determined (explicitly) by a specific field (e.g., "BWP ID") of the new activation/deactivation command MAC CE. For example, the value of the "BWP ID" field may indicate the "CFR ID" of the CFR. In some embodiments, a "CFR ID" field may be defined in the new activation/deactivation command MAC CE for (explicitly) indicating the CFR to which the new activation/deactivation command should be applied.

In some embodiments, when a new activation/deactivation command MAC CE having a different LCID (e.g., different from the first LCID) is carried in the group common PDSCH, it may be determined that the CFR of the new activation/deactivation command should be applied (implicitly) as the CFR included in the DL BWP receiving the group common PDSCH. Thus, a specific field (e.g., "BWP ID") of the new activation/deactivation command MAC CE may be ignored. In some other embodiments, the CFR to which the new activation/deactivation command should be applied may be (implicitly) determined as a CFR included in the DL BWP indicated by a specific field (e.g., "BWP ID") of the new activation/deactivation command MAC CE. In some other embodiments, the CFR to which the new activation/deactivation command should be applied may be determined (explicitly) by a specific field (e.g., "BWP ID") of the new activation/deactivation command MAC CE. For example, the value of the "BWP ID" field may indicate the "CFR ID" of the CFR. In some embodiments, a "CFR ID" field may be defined in the new activation/deactivation command MAC CE for (explicitly) indicating the CFR to which the new activation/deactivation command should be applied.

In some embodiments, when the activation/deactivation command MAC CE is carried in the group common PDSCH, the CFR to which the activation/deactivation command should be applied may be (implicitly) determined as the CFR to receive the group common PDSCH. Thus, a specific field (e.g., "BWP ID") of the new activation/deactivation command MAC CE may be ignored.

In some embodiments, when the activation command MAC CE is carried in the group common PDSCH, the timing at which the activation command should be applied may be aligned among a group of UEs receiving the group common PDSCH. A fixed time relative to the end of the group common PDSCH may be usedThe active command is applied across lines. The timeline for the end of PUCCH transmission with HARQ-ACKs corresponding to the group common PDSCH may not be used to apply the activate command, as PUCCH transmission may be different for different UEs. For example, a fixed timeline may be defined as m may correspond to UL slots overlapping the end of the group common PDSCH. max { dl-DataToUL-ACK } may be the maximum value configured in a particular configuration/parameter (e.g., "dl-DataToUL-ACK") in the PUCCH-configuration associated with the CFR. />May be the total number of slots per subframe μ for SCS configuration. For another example, a fixed timeline may be defined as m may correspond to UL slots overlapping the end of the group common PDSCH. K (K) _1,max May be the maximum value configured in a particular configuration/parameter (e.g., "dl-DataToUL-ACK") in the PUCCH-configuration associated with the CFR. />May be the total number of slots per subframe μ for SCS configuration.

In some embodiments, PDSCH-Config associated with CFR may include at least one specific configuration (e.g., a "zp-CSI-RS-ResourceToAddModList" field and/or a "zp-CSI-RS-ResourceToReleaseList" field). PDSCH-Config associated with CFR may include a configuration (e.g., a "p-ZP-CSI-RS-resource set" field) to configure periodic ZP CSI-RS resources. The periodic ZP CSI-RS resources may be indicated (or identified) by a list of indices or IDs (e.g., indicated by "ZP-CSI-RS-ResourceId") corresponding to ZP CSI-RS resources configured by at least one particular configuration (e.g., the "ZP-CSI-RS-resourcedoaddmodlist" field) in the PDSCH-Config associated with the CFR.

In some embodiments, periodic ZP CSI-RS resources configured by the configuration in PDSCH-Config associated with CFR may be (considered) unavailable to receive the group common PDSCH in CFR. When the configuration is not configured, ZP CSI-RS resources configured by the configuration in PDSCH-Config associated with the first DL BWP may be (considered) unavailable for receiving the group common PDSCH in CFR.

In some implementations, the gNB may not configure the configuration in PDSCH-Config associated with the CFR (e.g., a "p-ZP-CSI-RS-resource set" field) if the configuration in PDSCH-Config associated with the first DL BWP is configured.

Fig. 1 is a flowchart illustrating a method 100 performed by a UE for processing PDSCH reception according to an example embodiment of the present application. In act 102, the UE may receive a first PDSCH configuration (e.g., "CFR-config multicast (-r 17)") from the BS among CFR configurations for the multicast PDSCH. The first PDSCH configuration may include a first aperiodic resource set configuration (e.g., "adaptive-ZP-CSI-RS-resource estdstoaddmodlist"). In act 104, the UE may receive a second PDSCH configuration from the BS among the BWP configurations for the unicast PDSCH. The second PDSCH configuration may include a resource configuration (e.g., "zp-CSI-RS-resource toaddmodlist") and a second aperiodic resource set configuration. The resource configuration may configure one or more ZP CSI-RS resources. In act 106, the UE may receive a first DCI scheduling a multicast PDSCH from the BS. The first DCI may include a first field to trigger an aperiodic ZP CSI-RS. In act 108, the UE may determine a first set of ZP CSI-RS resources from a first list of ZP CSI-RS resources configured by the first aperiodic resource set configuration based on the first field. The first set of ZP CSI-RS resources is not available for receiving the multicast PDSCH. There may be no resource configuration in the first PDSCH configuration. Each of the first list of ZP CSI-RS resource sets may include at least one of the one or more ZP CSI-RS resources.

Fig. 2 is a flowchart of a method 200 for processing PDSCH reception performed by a UE (e.g., a UE performing the method 100 of fig. 1) according to one of the example embodiments of the present application. In act 202, the UE may receive a second DCI scheduling a unicast PDSCH from the BS. The second DCI may include a second field to trigger the aperiodic ZP CSI-RS. In act 204, the UE may determine a second set of ZP CSI-RS resources from a second list of ZP CSI-RS resources configured by a second aperiodic resource set configuration based on the second field. The second set of ZP CSI-RS resources is not available for receiving unicast PDSCH. Each of the second list of ZP CSI-RS resource sets may include at least one of the one or more ZP CSI-RS resources.

In some embodiments, the second field of the second DCI may indicate a resource set ID of the second ZP CSI-RS resource set.

In some embodiments, the CFR configuration may be included in a BWP configuration.

In some embodiments, the first field of the first DCI may indicate a resource set ID of the first ZP CSI-RS resource set.

In some implementations, each of the one or more ZP CSI-RS resources may be associated with a resource ID. At least one of the one or more ZP CSI-RS resources included in each of the first list of ZP CSI-RS resource sets may be indicated by a list of resource IDs configured by the first aperiodic resource set configuration. The resource ID list may be associated with at least one of the one or more ZP CSI-RS resources.

Fig. 3 is a flowchart of a method 300 performed by a BS for processing PDSCH transmissions according to one of the exemplary embodiments of the present application. In act 302, the BS may transmit a first PDSCH configuration (e.g., "CFR-ConfigMulticast (-r 17)") among CFR configurations for the multicast PDSCH to the UE. The first PDSCH configuration may include a first aperiodic resource set configuration (e.g., "adaptive-ZP-CSI-RS-resource estdstoaddmodlist"). In act 304, the BS may transmit a second PDSCH configuration among BWP configurations for the unicast PDSCH to the UE. The second PDSCH configuration may include a resource configuration (e.g., "zp-CSI-RS-resource toaddmodlist") and a second aperiodic resource set configuration. The resource configuration may configure one or more ZP CSI-RS resources. In act 306, the BS may transmit a first DCI scheduling a multicast PDSCH to the UE. The first DCI may include a first field to trigger an aperiodic ZP CSI-RS. The first field may enable the UE to determine a first set of ZP CSI-RS resources from a first list of ZP CSI-RS resources configured by the first aperiodic resource set configuration. The first set of ZP CSI-RS resources is not available for receiving the multicast PDSCH. There may be no resource configuration in the first PDSCH configuration. Each of the first list of ZP CSI-RS resource sets may include at least one of the one or more ZP CSI-RS resources.

Fig. 4 is a flowchart of a method 400 performed by a BS for processing PDSCH transmissions according to one of the exemplary embodiments of the present application. In act 402, the BS may transmit a first PDSCH configuration (e.g., "CFR-ConfigMulticast (-r 17)") among CFR configurations for the multicast PDSCH to the UE. The first PDSCH configuration may include a first aperiodic resource set configuration (e.g., "adaptive-ZP-CSI-RS-resource estdstoaddmodlist"). In act 404, the BS may transmit a second PDSCH configuration from among BWP configurations for the unicast PDSCH to the UE. The second PDSCH configuration may include a resource configuration (e.g., "zp-CSI-RS-resource toaddmodlist") and a second aperiodic resource set configuration. The resource configuration may configure one or more ZP CSI-RS resources. In act 406, the BS may transmit a first DCI scheduling a multicast PDSCH to the UE. The first DCI may include a first field to trigger an aperiodic ZP CSI-RS. The first field may enable the UE to determine a first set of ZP CSI-RS resources from a first list of ZP CSI-RS resources configured by a first aperiodic resource set configuration. The first set of ZP CSI-RS resources is not available for receiving the multicast PDSCH. There may be no resource configuration in the first PDSCH configuration. Each of the first list of ZP CSI-RS resource sets may include at least one of the one or more ZP CSI-RS resources. In act 408, the BS may send a second DCI scheduling a unicast PDSCH to the UE. The second DCI may include a second field to trigger the aperiodic ZP CSI-RS. The second field may enable the UE to determine a second set of ZP CSI-RS resources from a second list of ZP CSI-RS resources configured by a second aperiodic resource set configuration. The second set of ZP CSI-RS resources is not available for receiving unicast PDSCH. Each of the second list of ZP CSI-RS resource sets may include at least one of the one or more ZP CSI-RS resources.

In some implementations, the first field of the first DCI may indicate a resource set ID of the first ZP CSI-RS resource set.

It should be noted that the order in which the process is described is not intended to be construed as a limitation, and any number of the described acts may be combined in any order to implement the method or an alternative method. Further, one or more of the acts illustrated in fig. 1-4 may be omitted in some embodiments.

Fig. 5 illustrates a block diagram of a node for wireless communication, shown according to one of the exemplary embodiments of the present application. As shown in fig. 5, node 500 may include a transceiver 520, a processor 528, a memory 534, one or more presentation elements 538, and at least one antenna 536. Node 500 may also include Radio Frequency (RF) band modules, base station communication modules, network communication modules, system communication management modules, input/output (I/O) ports, I/O components, and power supplies (not explicitly shown in fig. 5).

The components may communicate with each other directly or indirectly through one or more buses 540. The node 500 may be a UE or BS performing various functions disclosed herein with reference to fig. 1-4.

Transceiver 520 has a transmitter 522 (e.g., transmitting circuitry/transmitting circuitry) and a receiver 524 (e.g., receiving circuitry/receiving circuitry), and transceiver 520 may be configured to transmit and/or receive time and/or frequency resource partition information. In some embodiments, transceiver 520 may be configured to transmit in different types of subframes and slots, including but not limited to usable, unusable, and flexibly usable subframe and slot formats. Transceiver 520 may be configured to receive data and control channels.

Node 500 may include a variety of computer-readable media. Computer readable media can be any available media that can be accessed by node 500 and includes both volatile and nonvolatile media, removable and non-removable media.

Computer readable media may include computer storage media and communication media. Computer storage media may include volatile (and/or nonvolatile) and removable (and/or non-removable) media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or data.

Computer storage media includes RAM, ROM, EEPROM, flash memory (or other storage technology), CD-ROM, digital versatile disks (DVD: digital Versatile Disk) (or other optical disk storage), magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices), and the like. Computer storage media does not include propagated data signals. Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media.

The term "modulated data signal" may mean a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired NW or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.

Memory 534 may include computer storage media in the form of volatile and/or nonvolatile memory. The memory 534 may be removable, non-removable, or a combination thereof. For example, memory 534 may include solid state memory, a hard disk drive, an optical disk drive, and the like. As shown in fig. 5, the memory 534 may store computer readable and/or computer executable instructions 532 (e.g., software code or a computer executable program) that, when executed, are configured to cause the processor 528 to perform the various functions described herein, for example, with reference to fig. 2 and 3. Alternatively, the computer-executable instructions 532 may not be directly executable by the processor 528 but are configured to cause the node 500 (e.g., when compiled and executed) to perform the various functions described herein.

The processor 528 (e.g., with processing circuitry) may include intelligent hardware devices, such as a central processing unit (central processing unit, CPU), microcontroller, ASIC, or the like. The processor 528 may include a memory. Processor 828 may process data 530 and instructions 532 received from memory 534, and information via transceiver 520, a baseband communication module, and/or a network communication module. The processor 528 may also process information to be transmitted to the transceiver 520 for transmission through the antenna 536, and to the network communication module for transmission to the CN.

The one or more presentation components 538 may present data indications to a person or other device. Exemplary one or more presentation components 838 include a display device, speakers, a printing component, a vibrating component, and the like.

From the foregoing, the concepts recited in the application can be implemented using a variety of techniques without departing from the scope of these concepts. Furthermore, while these concepts have been described with specific reference to certain embodiments, those of ordinary skill in the art will recognize that changes may be made in form and detail without departing from the scope of the concepts. As such, the described embodiments are to be considered in all respects as illustrative and not restrictive, it being understood that the application is not limited to the particular embodiments described above, and that many rearrangements, modifications, and substitutions are possible without departing from the scope of the disclosure.

Claims

1. A method performed by a user equipment, UE, for handling physical downlink shared channel, PDSCH, reception, the method comprising:

receiving a first PDSCH configuration from a base station BS among common frequency resource CFR configurations for multicast PDSCH, the first PDSCH configuration including a first aperiodic resource set configuration;

receiving a second PDSCH configuration from the BS in a bandwidth portion, BWP, configuration for unicast PDSCH, the second PDSCH configuration including a resource configuration for configuring one or more zero-power ZP channel state information-reference signal, CSI-RS, resources and a second aperiodic resource set configuration;

receiving first downlink control information, DCI, scheduling the multicast PDSCH from the BS, the first DCI including a first field for triggering a first aperiodic ZP CSI-RS; and

determining a first set of ZP CSI-RS resources based on the first field, the first set of ZP CSI-RS resources not being available to receive the multicast PDSCH from a first list of ZP CSI-RS resource sets configured by the first aperiodic resource set configuration, wherein:

the resource configuration is absent from the first PDSCH configuration, and

each of the first list of ZP CSI-RS resources sets includes at least one of one or more ZP CSI-RS resources.

2. The method of claim 1, wherein the method further comprises:

receiving a second DCI scheduling the unicast PDSCH from the BS, the second DCI including a second field for triggering a second aperiodic ZP CSI-RS; and

determining a second set of ZP CSI-RS resources based on the second field, the second set of ZP CSI-RS resources not being available for receiving the unicast PDSCH from a second list of ZP CSI-RS resource sets configured by the second aperiodic resource set configuration,

wherein each of the second list of ZP CSI-RS resources sets includes at least one of one or more ZP CSI-RS resources.

3. The method of claim 2, wherein the second field of the second DCI indicates a resource set identification, ID, of the second ZP CSI-RS resource set.

4. The method of claim 1, wherein the CFR configuration is included in a BWP configuration.

5. The method of claim 1, wherein the first field of the first DCI indicates a resource set identification, ID, of the first ZP CSI-RS resource set.

6. The method of claim 1, wherein:

each of the one or more ZP CSI-RS resources is associated with a resource identification, ID; and

At least one of the one or more ZP CSI-RS resources included in each of the first list of ZP CSI-RS resource sets is indicated by a resource ID list configured by a first aperiodic resource set configuration, the resource ID list being associated with at least one of the one or more ZP CSI-RS resources.

7. A user equipment, UE, for handling physical downlink shared channel, PDSCH, reception, the UE comprising:

one or more non-transitory computer-readable media embodying computer-executable instructions; and

at least one processor coupled to one or more non-transitory computer-readable media, the at least one processor configured to execute the computer-executable instructions to cause the UE to perform the method of any one of claims 1-6.

8. A method performed by a base station BS for handling physical downlink shared channel, PDSCH, transmissions, the method comprising:

transmitting a first PDSCH configuration among common frequency resource CFR configurations for a multicast PDSCH to a user equipment UE, the first PDSCH configuration including a first aperiodic resource set configuration;

Transmitting, to the UE, a second PDSCH configuration of the bandwidth part BWP configurations for unicast PDSCH, the second PDSCH configuration including a resource configuration for configuring one or more zero-power ZP channel state information-reference signal CSI-RS resources and a second aperiodic resource set configuration; and

transmitting first Downlink Control Information (DCI) for scheduling the multicast PDSCH to the UE, wherein the first DCI comprises a first field for triggering a first aperiodic ZP (channel state information) -RS, and the first field comprises:

the first field enables the UE to determine, from a first list of ZP CSI-RS resource sets configured by the first aperiodic resource set configuration, a first set of ZP CSI-RS resource sets unavailable for receiving the multicast PDSCH,

the resource configuration is absent from the first PDSCH configuration, and

9. The method of claim 8, wherein the method comprises:

transmitting, to the UE, a second DCI scheduling the unicast PDSCH, the second DCI including a second field for triggering a second aperiodic ZP CSI-RS, wherein:

The second field enables the UE to determine a second set of ZP CSI-RS resources unavailable for receiving the unicast PDSCH from a second list of ZP CSI-RS resources configured by a second aperiodic resource set configuration, and

each of the second list of ZP CSI-RS resources sets includes at least one of the one or more ZP CSI-RS resources.

10. The method of claim 9, wherein the second field of the second DCI indicates a resource set identification, ID, of the second ZP CSI-RS resource set.

11. The method of claim 8, wherein the CFR configuration is included in a BWP configuration.

12. The method of claim 8, wherein the first field of the first DCI indicates a resource set identification, ID, of the first ZP CSI-RS resource set.

13. The method as recited in claim 8, wherein:

14. A base station, BS, for handling physical downlink shared channel, PDSCH, transmissions, the BS comprising:

at least one processor coupled to one or more non-transitory computer-readable media, the at least one processor configured to execute the computer-executable instructions to cause the BS to perform the method of any one of claims 8-13.