WO2023050138A1 - Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil - Google Patents

Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil Download PDF

Info

Publication number
WO2023050138A1
WO2023050138A1 PCT/CN2021/121676 CN2021121676W WO2023050138A1 WO 2023050138 A1 WO2023050138 A1 WO 2023050138A1 CN 2021121676 W CN2021121676 W CN 2021121676W WO 2023050138 A1 WO2023050138 A1 WO 2023050138A1
Authority
WO
WIPO (PCT)
Prior art keywords
wireless communication
sps
mbs
communication device
pdsch
Prior art date
Application number
PCT/CN2021/121676
Other languages
English (en)
Inventor
Xing Liu
Peng Hao
Xingguang WEI
Shuaihua KOU
Tao Qi
Original Assignee
Zte Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zte Corporation filed Critical Zte Corporation
Priority to PCT/CN2021/121676 priority Critical patent/WO2023050138A1/fr
Priority to CN202180102822.9A priority patent/CN118020361A/zh
Publication of WO2023050138A1 publication Critical patent/WO2023050138A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1848—Time-out mechanisms
    • H04L1/1851—Time-out mechanisms using multiple timers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H04W68/025—Indirect paging
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0093—Point-to-multipoint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/11—Semi-persistent scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • the present implementations relate generally to wireless communications, and more particularly to systems, methods, apparatuses, and non-transitory computer-readable media for managing multicast communications in wireless communication networks.
  • channels carrying Multicast Broadcast Service can be configured to transmit within a Common Frequency Range (CFR) .
  • CFR Common Frequency Range
  • the CFR is restricted within an active unicast Downlink (DL) Bandwidth Part (BWP) .
  • BWP-InactivityTimer a User Equipment (UE) switches its active unicast DL BWP to a default DL BWP in response to the BWP inactivity timer expiring regardless of whether the UE is receiving MBS.
  • the default DL BWP may not contain the CFR.
  • receiving of the MBS is interrupted or terminated. This seriously affects user experience.
  • Example implementations relate to a wireless communication method, including determining, by a wireless communication device, a first timer for multicast, determining, by the wireless communication device, a second timer for BWP inactivity, and receiving, by the wireless communication device from a network, multicast transmission based on the first timer and the second timer.
  • Example implementations relate to a wireless communication method, including configuring, by network for a wireless communication device, a first timer for multicast, configuring, by the network for the wireless communication device, a second timer for Bandwidth Part (BWP) inactivity, and sending, by the network to the wireless communication device, multicast transmission based on the first timer and the second timer.
  • BWP Bandwidth Part
  • Example implementations also include a wireless communication apparatus including at least one processor and a memory, wherein the at least one processor is configured to read code from the memory and implement methods in accordance with present implementations.
  • Example implementations also include a computer program product comprising a computer-readable program medium code stored thereupon, the code, when executed by at least one processor, causing the at least one processor to implement methods in accordance with present implementations.
  • FIG. 1A is a schematic diagram illustrating an example of SPS PDSCH selection, according to various arrangements.
  • FIG. 1B is a diagram illustrating an example wireless communication network, according to various arrangements.
  • FIG. 1C is a diagram illustrating a block diagram of an example wireless communication system for transmitting and receiving downlink and uplink communication signals, according to various arrangements.
  • FIG. 2 is a diagram illustrating an active BWP and an CFR, according to various arrangements.
  • FIG. 3 is a flowchart diagram illustrating an example method for managing multicast communication, according to various arrangements.
  • FIG. 4 is a flowchart diagram illustrating an example method for managing multicast communication, according to various arrangements.
  • FIG. 5 is a flowchart diagram illustrating an example method for managing multicast communication, according to various arrangements.
  • FIG. 6 is a flowchart diagram illustrating an example method for managing multicast communication, according to various arrangements.
  • FIG. 7 is a flowchart diagram illustrating an example method for managing multicast communication, according to various arrangements.
  • FIG. 8 is a diagram illustrating a DCI format for a paging PDCCH, according to various arrangements.
  • FIG. 9 is a table illustrating the mapping between the bit field and the indication of a short message indicator in the paging PDCCH, according to various arrangements.
  • FIG. 10 is a diagram illustrating the mapping between the bits and the short messages of the short message in the paging PDCCH, according to various arrangements.
  • FIG. 11 is a diagram illustrating an active BWP, a default BWP, and an CFR, according to various arrangements.
  • FIG. 12 is a diagram illustrating an active BWP, a default BWP, and CFRs, according to various arrangements.
  • Implementations described as being implemented in software should not be limited thereto, but can include implementations implemented in hardware, or combinations of software and hardware, and vice-versa, as will be apparent to those skilled in the art, unless otherwise specified herein.
  • an implementation showing a singular component should not be considered limiting. Rather, the present disclosure is intended to encompass other implementations including a plurality of the same component, and vice-versa, unless explicitly stated otherwise herein.
  • the present implementations encompass present and future known equivalents to the known components referred to herein by way of illustration.
  • a UL transmission and a DL transmission are based on an active unicast UL BWP and an active unicast DL BWP, respectively.
  • a UE is configured by a network (e.g., a base station) with one or more BWPs based on a predefined maximum BWP number (e.g., 4) per cell. Only one of the configured BWPs can be activated to communicate data or information at a time in NR Rel-15 and Rel-16. Therefore, energy can be conserved by allowing UEs to operate on part of the bandwidth rather than the entire carrier.
  • a BWP inactivity timer (e.g., BWP-InactivityTimer) may be configured by the network (e.g., a base station) for the UE.
  • the BWP inactivity timer is reset upon reception of a Downlink Control Information (DCI) format with Cyclic Redundancy Check (CRC) scrambled by Radio Network Temporary Identity (RNTI) such as a Cell-RNTI (C-RNTI) or a Configured Scheduling RNTI (CS-RNTI) .
  • DCI Downlink Control Information
  • CRC Cyclic Redundancy Check
  • RNTI Radio Network Temporary Identity
  • the UE can switch the active unicast DL BWP to the default DL BWP in response to determining the BWP-InactivityTimer expiring.
  • the same transmission mechanism can be used by a network node (e.g. a base station) for transmitting the same information to a group of UEs or all UEs in a cell.
  • the MBS transmission can be carried on a PDSCH, which is received by the group of UEs or all UEs.
  • PDSCH carrying MBS information can be referred to as a GC-PDSCH or an MBS PDSCH.
  • Different UEs may encounter various different network environments (e.g. channel condition) .
  • the transmission mechanism selected can be better matched to the network environment of each UE in the UE group.
  • a group of UEs receiving a same PDSCH for MBS information there are different implementations for scheduling the PDSCH for the group of UEs.
  • One example includes using a GC-PDCCH to schedule the GC-PDSCH dynamically, where all UEs in the group can detect the same PDCCH, and the PDSCH can be scheduled by the PDCCH.
  • the CRC of DCI carried on GC-PDCCH is scrambled with a Group RNTI (G-RNTI) .
  • G-RNTI Group RNTI
  • Discontinuous Reception (DRX) operation is applied to GC-PDCCH monitoring.
  • the DRX pattern for a G-RNTI can be configured via RRC signaling (including, at least one of period, offset, drx-onDurationTimer, drx-InactivityTimer, etc. ) .
  • the UE can determine DRX-on and DRX-off phases according to the configuration parameters.
  • the DRX pattern can be same or different for different G-RNTIs. More specifically, the GC-PDCCH carrying DCI format with CRC scrambled by a G-RNTI can only be monitored during DRX-on phase corresponding to the G-RNTI.
  • the UE-specific DRX pattern can be determined according to C-RNTI. Then, a UE can be configured whether a Point-to-Point (PTP) retransmission can be used for a MBS TB. In other words, the UE can be configured whether unicast PDCCH (or UE-specific PDCCH) can be used for retransmission scheduling of a MBS TB.
  • the configuration signaling can be, such as, RRC signaling, MAC layer signaling, or DCI. If PTP retransmission of a MBS TB is enabled, the UE can also monitor DCI format with CRC scrambled by C-RNTI during DRX-on phase corresponding to G-RNTI.
  • the GC-PDSCH is transmitted according to the SPS configuration and the activation command. That is, the SPS configuration is transmitted via RRC signaling, including at least one of the periodicity, the number of HARQ process, PUCCH resource corresponding to the SPS PDSCH, HARQ ID offset, PDSCH aggregation factor, SPS index etc.
  • the SPS can be further activated or deactivated by a DCI indicating more configurations for the SPS PDSCH. After a DCI activating the SPS, a plurality of periodic SPS PDSCHs are used for transmitting the data from the network to the UE.
  • the activated or deactivated DCI can be transmitted by either a GC activation PDCCH or a UE-specific activation PDCCH.
  • the CRC of DCI carried on group-common activation PDCCH is scrambled with a G-CS-RNTI.
  • the CRC of DCI carried on a UE-specific activation PDCCH is scrambled with CS-RNTI.
  • a UE can be configured with a plurality of SPS configurations. Some of the SPS configurations are for unicast service. Some of the SPS configurations are for MBS. Each SPS configuration is identified by (or associated with) a SPS index. A UE can receives at most N PDSCH in a slot, where at most M PDSCH can overlaps in the time domain based on UE capability.
  • the UE receives the SPS PDSCHs according to the following rules: starting from the SPS PDSCH with the lowest (or largest) SPS index, The UE determines whether a SPS PDSCH is survivor PDSCH one-by-one in the ascending (or descending) order of the SPS index until the number of the survivor PDSCH is equal to the maximum number of PDSCH that a UE can receives in the slot or there is no SPS PDSCH left to be determined in the slot.
  • a SPS PDSCH is determined to be a survivor PDSCH if the number of SPS PDSCHs that overlaps in the time domain is not larger than M by taking the SPS PDSCH into account (assuming the SPS PDSCH to be determined is survivor PDSCH) .
  • the UE receives only the selected survivor PDSCHs.
  • Step 1 select the SPS PDSCH with the lowest SPS (or largest) index in the candidate set.
  • the selected PDSCH is excluded from the candidate set.
  • Step 2 if (1) the number of the survivor PDSCHs is equal to N, or (2) there is no SPS PDSCH left in the candidate set, Stop; Else (the number of the survivor PDSCHs is smaller than N and there are PDSCHs left in the candidate set) , go to Step 1.
  • the SPS PDSCH is dropped first. This results in the SPS PDSCH not being included in the candidate set. If there is a PDSCH scheduled by a DCI in the slot, the UE receives the PDSCH, and the PDSCH should be taken into account when selecting the SPS PDSCH. This results in the conditions in step 2 being changed to “the total number of the survivor PDSCH and the PDSCH scheduled by downlink control information is equal to N” and “the total number of the survivor PDSCHs and the PDSCHs scheduled by downlink control information is smaller than N, ” respectively.
  • two PDSCHs overlapping in the time domain refers to the two PDSCHs overlap in the time domain only and does not overlap in the frequency domain.
  • FIG. 1A is a schematic diagram illustrating an example of SPS PDSCH selection, according to various arrangements.
  • SPS PDSCH 0 with SPS index 0
  • PDSCH 1 with SPS index 1
  • PDSCH 2 with SPS index 2
  • PDSCH 3 with SPS index 3
  • PDSCH 4 with SPS index 4
  • PDSCH 5 with SPS index 6.
  • the first PDSCH to be determined is the PDSCH 0 due to the lowest index (i.e., SPS 0) .
  • SPS 0 the lowest index
  • the maximum number of PDSCHs that overlap in the time domain is 1, which is less than M. Therefore, PDSCH 0 is determined as survivor PDSCH.
  • the survivor PDSCH includes PDSCH 0.
  • the number of the survivor PDSCHs is 1 in the slot and smaller than N, and there is SPS PDSCH left in the slot. Therefore, the selection of the SPS PDSCHs continues.
  • the next PDSCH to be determined is PDSCH 1.
  • PDSCH 1 overlaps with PDSCH 0 in the time domain.
  • the maximum number of overlapping PDSCHs in the time domain is 2, which is not larger than M. Therefore, PDSCH 1 is determined as survivor PDSCH.
  • the survivor PDSCHs include PDSCH 0 and PDSCH 1.
  • the number of survivor PDSCHs is 2 in the slot, and smaller than N, and there is SPS PDSCH left in the slot. Therefore, the selection of the SPS PDSCHs continues.
  • the next PDSCH to be determined is PDSCH 2.
  • PDSCH 2 By taking PDSCH 2 into account, PDSCH 2, PDSCH 1 and PDSCH 0 overlap with each other.
  • the maximum number of overlapped PDSCH in the time domain is 3, which is larger than M. Therefore, PDSCH 2 is not determined to be a survivor PDSCH.
  • the survivor PDSCHs include PDSCH 0 and PDSCH 1.
  • the number of survivor PDSCHs is 2 in the slot and smaller than N, and there is SPS PDSCH left in the slot. Therefore, the selection of the SPS PDSCHs continues.
  • the next PDSCH to be determined is PDSCH 3.
  • PDSCH 3 overlaps only with PDSCH 0 in the time domain.
  • the maximum number of overlapped PDSCH in the time domain is 2, which is not larger than M. Therefore, PDSCH 3 is determined to be a survivor PDSCH.
  • the survivor PDSCHs include PDSCH 0, PDSCH 1 and PDSCH 3. Then the number of survivor PDSCHs is 3 in the slot and smaller than N, and there is SPS PDSCH left in the slot. Therefore, the selection of the SPS PDSCHs continues.
  • the next PDSCH to be determined is PDSCH 4.
  • PDSCH 4 By taking PDSCH 4 into account, PDSCH 4 only overlaps with PDSCH 3 in the time domain.
  • the maximum number of overlapped PDSCH in the time domain is 2, which is not larger than M. Therefore, PDSCH 4 is determined to be a survivor PDSCH.
  • the survivor PDSCHs include PDSCH 0, PDSCH 1, PDSCH 3 and PDSCH 4.
  • the number of survivor PDSCHs is 4 in the slot and equal to N. Therefore, Stop the selection of the SPS PDSCHs stops, and the survivor PDSCHs include PDSCH 0, PDSCH 1, PDSCH 3 and PDSCH 4.
  • the UE receives PDSCH 0, PDSCH 1, PDSCH 3 and PDSCH 4 in the slot.
  • a UE can receive at most N PDSCHs in a slot, where at most O PDSCHs for MBS can overlap in the time domain, at most P PDSCHs for unicast service can overlap in the time domain, and at most Q PDSCHs for unicast service and MBS can overlap in the time domain based on the UE capability. If there are a plurality of SPS PDSCHs for MBS or unicast service in a slot, the UE receives the SPS PDSCHs in the following rules.
  • the UE starts from the SPS PDSCH with the lowest (or largest) SPS index and determines whether a SPS PDSCH is survivor PDSCH one by one in the ascending (or descending) order of the SPS index until the number of the survivor PDSCH is equal to the maximum number of PDSCH that a UE can receive in the slot or there is no SPS PDSCH left in the slot.
  • a SPS PDSCH is determined to be a survivor PDSCH if, among the survivor PDSCHs, the number of overlapped PDSCHs for MBS is not larger than O, and the number of overlapped PDSCHs in the time domain for unicast service is not larger than P, and the number of overlapped PDSCH in the time domain for MBS and unicast service is not larger than Q, by taking the SPS PDSCH into account (assuming the SPS PDSCH to be determined is survivor PDSCH) .
  • the following can be used to select the SPS PDSCH that the UE receives in the slot. All the SPS PDSCHs to be determined in the slot are seen as the candidate PDSCH set.
  • Step 1 select the SPS PDSCH with the lowest (or largest) SPS index in the candidate set.
  • the selected PDSCH is excluded from the candidate set.
  • the selected SPS PDSCH is determined as a survivor PDSCH. Otherwise, it cannot be determined as a survivor PDSCH.
  • Step 2 if (1) the number of the survivor PDSCHs is equal to N or (2) there is no SPS PDSCH left in the candidate set, stop; else (e.g., the number of the survivor PDSCHs is smaller than N and there are PDSCHs left in the candidate set) , go to Step 1.
  • SPS 1, SPS 3, SPS 6 are used for transmitting MBS, and SPS 0, SPS 2 and SPS 4 are used for transmitting unicast service.
  • the first SPS PDSCH to be determined is PDSCH 0.
  • PDSCH 0 is determined as a survivor PDSCH.
  • the survivor PDSCH includes PDSCH 0.
  • the number of the survivor PDSCH is 1, and there are still SPS PDSCH left in the slot. Therefore, the selection of the SPS PDSCH continues.
  • the next SPS PDSCH to be determined is PDSCH 1.
  • the number of overlapped PDSCH for MBS and unicast service in the time domain i.e., PDSCH 0 and PDSCH 1 is 2, which is equal to Q.
  • the number of overlapped SPS PDSCH in the time domain for MBS is 1, which is smaller than O.
  • the number of overlapped SPS PDSCH in the time domain for unicast service is 1, which is not larger than P. So PDSCH 1 is determined as a survivor PDSCH.
  • the survivor PDSCHs include PDSCH 0 and PDSCH 1.
  • the number of the survivor PDSCHs is 2 and smaller than N, and there are still SPS PDSCH left in the slot. Therefore, the selection of the SPS PDSCH continues.
  • the next SPS PDSCH to be determined is PDSCH 2.
  • the number of overlapped PDSCH for unicast service in the time domain e.g., PDSCH 0 overlapping with PDSCH 2
  • P the number of overlapped PDSCH for unicast service in the time domain
  • P the number of overlapped PDSCH for unicast service in the time domain
  • P the number of overlapped PDSCH for unicast service in the time domain
  • P PDSCH 2 cannot be determined as a survivor PDSCH.
  • the number of the survivor PDSCHs is 2 and smaller than N, and there are still SPS PDSCH left in the slot. Therefore, the selection of the SPS PDSCH continues.
  • the next SPS PDSCH to be determined is PDSCH 3.
  • the number of overlapped PDSCH for MBS and unicast service in the time domain i.e., PDSCH 0 overlaps with PDSCH 1, PDSCH 0 overlaps with PDSCH 3 is 2, which is not larger than Q.
  • the number of overlapped SPS PDSCH in the time domain for MBS is 1, which is smaller than O.
  • the number of overlapped SPS PDSCH in the time domain for unicast service is 1, which is not larger than P.
  • So PDSCH 3 is determined as a survivor PDSCH.
  • the survivor PDSCHs include PDSCH 0, PDSCH 1 and PDSCH 3.
  • the number of the survivor PDSCHs is 3 and equal to than N. Therefore, the selection of SPS PDSCH is stopped.
  • the survivor PDSCHs include PDSCH 0, PDSCH 1 and PDSCH 3.
  • the UE receives only these three PDSCHs and does not receive the other PDSCHs (e.g., PDSCH 2, 4, 5) .
  • the UE After the selection of the SPS PDSCHs, the UE does not receive one or more SPS PDSCH. If the UE does not receive a SPS PDSCH for MBS, the UE generates NACK or ACK for the SPS PDSCH for MBS. Whether to generate NACK or ACK for the SPS PDSCH that the UE does not receive is configured by the network. For example, the UE does not receive PDSCH 5 carrying MBS data. If the network configures the UE to generate NACK for the SPS PDSCH for MBS the UE does not receive, NACK is generates for PDSCH 5. If the network configures the UE to generate ACK for the SPS PDSCH for MBS the UE does not receive, ACK is generated for PDSCH 5.
  • a SPS configuration includes a first SPS index and a second SPS index. Both the first SPS index and the second SPS index are configured by the network.
  • the first SPS index is used to identify the SPS configuration when a GC PDCCH activates or deactivates the SPS configuration.
  • the GC PDCCH or GC MAC CE activating or deactivating SPS indicates the first SPS index of the activated or deactivated SPS configuration.
  • the second SPS index is used to identify the SPS configuration when a UE-specific PDCCH or UE-specific MAC CE activates or deactivates the SPS configuration.
  • the UE-specific PDCCH or UE-specific MAC CE activating or deactivating SPS indicates the second SPS index of the activated or deactivated SPS configuration.
  • the network configures the first SPS index and the second SPS index of the SPS A to be 1 and 3, respectively.
  • the first SPS index and the second SPS index of SPS B is 3 and 1, respectively.
  • a GC PDCCH or group common MAC CE activates or deactivates a SPS configuration with SPS index 1
  • SPS A is activated or deactivated accordingly.
  • a GC PDCCH or group common MAC CE activates or deactivates a SPS configuration with SPS index 3
  • SPS B is activated or deactivated accordingly.
  • a UE-specific PDCCH or UE-specific MAC CE activates or deactivates a SPS with SPS index 1
  • SPS B is activated or deactivated accordingly.
  • a UE-specific PDCCH or UE-specific MAC CE activates or deactivates a SPS with SPS index 3
  • SPS A is activated or deactivated accordingly.
  • the SPS index can be the first SPS index or the second SPS index.
  • a SPS configuration can be configured with a priority index by the network.
  • the priority index is used for selection of the SPS PDSCH in a slot according to the methods above.
  • the UE receives the SPS PDSCHs in the following rules. Starting from the SPS PDSCH with the lowest (or largest) priority index, the UE determines whether a SPS PDSCH is survivor PDSCH one by one in the ascending (or descending) order of the priority index until the number of the survivor PDSCH is equal to the maximum number of PDSCH that a UE can receives in the slot or there is no SPS PDSCH left in the slot.
  • the frequency range for MBS transmission can also be called a CFR .
  • a CFR can be defined as an BWP for MBS transmission, or an MBS-specific frequency region within the unicast DL BWP.
  • the size of DCI carried on GC-PDCCH should be aligned with the size of DCI format 1_0 monitored in Common Search Space (CSS) .
  • the size of Frequency Domain Resource Allocation (FDRA) field in DCI format 1_0 monitored in CSS is determined according the bandwidth of Control Resource SET (CORESET) #0 if CORESET#0 is configured for the cell. Otherwise, if CORESET#0 is not configured for the cell, the size of FDRA field in DCI format 1_0 monitored in CSS is determined according the bandwidth of initial DL BWP.
  • the size of FDRA field in DCI carried on GC-PDCCH can be determined according to the bandwidth of CFR.
  • the granularity of frequency domain resource allocation will be K, which is the maximum value from set ⁇ 1, 2, 4, 8 ⁇ and satisfies:
  • the value of P equals to 2 n , and n is number of reserved bits in the DCI format or n is configured via signaling (such as, DCI, MAC layer signaling or RRC signaling) .
  • the value of P is configured via signaling (such as, DCI, MAC layer signaling or RRC signaling) .
  • the value of P is determined according to some predefined rules.
  • FIG. 1B shows an example wireless communication network 100.
  • the wireless communication network 100 corresponds to a group communication within a cellular network.
  • a network side communication node or a base station can include one or more of a next Generation Node B (gNB) , an E-Utran Node B (also known as Evolved Node B, eNodeB or eNB) , a pico station, a femto station, a Transmission/Reception Point (TRP) , an Access Point (AP) , or the like.
  • gNB next Generation Node B
  • E-Utran Node B also known as Evolved Node B, eNodeB or eNB
  • TRP Transmission/Reception Point
  • AP Access Point
  • a terminal side node or a user equipment can include a long range communication system (such as but not limited to, a mobile device, a smart phone, a Personal Digital Assistant (PDA) , a tablet, a laptop computer) or a short range communication system (such as but not limited to, a wearable device, a vehicle with a vehicular communication system, or the like) .
  • a network side communication node is represented by a BS 102
  • a terminal side communication node is represented by a UE 104a or 104b.
  • the BS 102 is sometimes referred to as a “wireless communication node
  • the UE 104a/104b is sometimes referred to as a “wireless communication device. ”
  • the BS 102 can provide wireless communication services to the UEs 104a and 104b within a cell 101.
  • the UE 104a can communicate with the BS 102 via a communication channel 103a.
  • the UE 104b can communicate with the BS 102 via a communication channel 103b.
  • the communication channels (e.g., 103a and 103b) can be through interfaces such as but not limited to, an Uu interface which is also known as Universal Mobile Telecommunication System (UMTS) air interface.
  • the BS 102 is connected to a Core Network (CN) 108 through an external interface 107, e.g., an Iu interface.
  • CN Core Network
  • FIG. 1C illustrates a block diagram of an example wireless communication system 150 for transmitting and receiving downlink and uplink communication signals, in accordance with some arrangements of the present disclosure.
  • data symbols can be transmitted and received in a wireless communication environment such as the wireless communication network 100 of FIG. 1B.
  • the system 150 generally includes the BS 102 and UEs 104a and 104b.
  • the BS 102 includes a BS transceiver module 110, a BS antenna 112, a BS memory module 116, a BS processor module 114, and a network communication module 118.
  • the modules/components are coupled and interconnected with one another as needed via a data communication bus 120.
  • the UE 104a includes a UE transceiver module 130a, a UE antenna 132a, a UE memory module 134a, and a UE processor module 136a.
  • the modules/components are coupled and interconnected with one another as needed via a data communication bus 140a.
  • the UE 104b includes a UE transceiver module 130b, a UE antenna 132b, a UE memory module 134b, and a UE processor module 136b.
  • the modules/components are coupled and interconnected with one another as needed via a data communication bus 140b.
  • the BS 102 communicates with the UEs 104a and 104b via communication channels 155, which can be any wireless channel or other medium known in the art suitable for transmission of data as described herein.
  • the system 150 can further include any number of modules/elements other than the modules/elements shown in FIG. 1C.
  • the various illustrative blocks, modules, elements, circuits, and processing logic described in connection with the arrangements disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof.
  • various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionalities. Whether such functionalities are implemented as hardware, firmware, or software depends upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionalities in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.
  • a wireless transmission from an antenna of each of the UEs 104a and 104b to an antenna of the BS 102 is known as an uplink transmission
  • a wireless transmission from an antenna of the BS 102 to an antenna of each of the UEs 104a and 104b is known as a downlink transmission.
  • each of the UE transceiver modules 130a and 130b may be referred to herein as an uplink transceiver, or UE transceiver.
  • the uplink transceiver can include a transmitter circuitry and receiver circuitry that are each coupled to the respective antenna 132a and 132b.
  • a duplex switch may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion.
  • the BS transceiver module 110 may be herein referred to as a downlink transceiver, or BS transceiver.
  • the downlink transceiver can include RF transmitter circuitry and receiver circuitry that are each coupled to the antenna 112.
  • a downlink duplex switch may alternatively couple the downlink transmitter or receiver to the antenna 112 in time duplex fashion.
  • the operations of the transceivers 110, 130a, and 130b are coordinated in time such that the uplink receiver is coupled to the antenna 132a and 132b for reception of transmissions over the wireless communication channels 155 at the same time that the downlink transmitter is coupled to the antenna 112.
  • the UEs 104a and 104b can use the UE transceivers 130a and 130b through the respective antennas 132a and 132b to communicate with the BS 102 via the wireless communication channels 155.
  • the wireless communication channel 155 can be any wireless channel or other medium suitable for downlink (DL) and/or uplink (UL) transmission of data as described herein.
  • the UE transceiver 130a/130b and the BS transceiver 110 are configured to communicate via the wireless data communication channel 155, and cooperate with a suitably configured antenna arrangement that can support a particular wireless communication protocol and modulation scheme.
  • the UE transceiver 130a/130b and the BS transceiver 110 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, or the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 130a/130b and the BS transceiver 110 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.
  • LTE Long Term Evolution
  • 5G 5G
  • the processor modules 136a and 136b and 114 may be each implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein.
  • a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.
  • the memory modules 116, 134a, 134b can be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or another suitable form of storage medium.
  • the memory modules 116, 134a, and 134b may be coupled to the processor modules 114, 136a, and 136b, respectively, such that the processors modules 114, 136a, and 136b can read information from, and write information to, the memory modules 116, 134a, and 134b, respectively.
  • the memory modules 116, 134a, and 134b may also be integrated into their respective processor modules 114, 136a, and 136b.
  • the memory modules 116, 134a, and 134b may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 114, 136a, and 136b, respectively.
  • Memory modules 116, 134a, and 134b may also each include non-volatile memory for storing instructions to be executed by the processor modules 114, 136a, and 136b, respectively.
  • the network interface 118 generally represents the hardware, software, firmware, processing logic, and/or other components of the BS 102 that enable bi-directional communication between BS transceiver 110 and other network components and communication nodes configured to communication with the BS 102.
  • the network interface 118 may be configured to support internet or WiMAX traffic.
  • the network interface 118 provides an 802.3 Ethernet interface such that BS transceiver 110 can communicate with a conventional Ethernet based computer network.
  • the network interface 118 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) .
  • MSC Mobile Switching Center
  • the terms “configured for” or “configured to” as used herein with respect to a specified operation or function refers to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed, formatted and/or arranged to perform the specified operation or function.
  • the network interface 118 can allow the BS 102 to communicate with other BSs or core network over a wired or wireless connection.
  • the BS 102 can communicate with a plurality of UEs (including the UEs 104a and 104b) using multicast or broadcast, collectively referred to as MBS.
  • the plurality of UEs can each receive MBS channel (e.g., MBS PDSCH, MBS PDCCH, and so on) via multicast and/or broadcast.
  • MBS channel e.g., MBS PDSCH, MBS PDCCH, and so on
  • the plurality of UEs have a common understanding on the configurations of the MBS channel, including but not limited to, frequency resource range for resource allocation, scramble identifier (ID) , and so on.
  • ID scramble identifier
  • reception of a DCI format with CRC scrambled by G-RNTI is enabled to reset the BWP inactivity timer. This mechanism partially defeats the motivation for having a default DL BWP and results in unnecessary power consumption given that the UE continues to monitor PDCCH for detection of unicast DCI formats according to search space sets that are configured for unicast DL traffic.
  • a CFR 220 for GC PDCCH and/or GC-PDSCH is confined within the frequency resource of a dedicated unicast BWP (also referred to as an active BWP 210) to support simultaneous reception of unicast and multicast in the same slot.
  • a dedicated unicast BWP also referred to as an active BWP 210
  • Two options can be used for the CFR 220 for GC-PDCCH and/or GC-PDSCH.
  • BWP refers to a portion of contiguous frequency resource in a cell.
  • a BWP is a continuous range of frequencies that can be used for communications between a BS and UEs.
  • Some transmission parameters and channel configurations are BWP-specific. Different UEs can have different BWP configurations.
  • at most one of multiple configured BWPs can be activated due to lack of time, although at most four BWPs can be configured for a UE.
  • at most one active DL BWP and at most one active UL BWP at a given time can be activated for a given serving cell.
  • the CFR is defined as an MBS-specific BWP, which is associated with the dedicated unicast BWP and uses the same numerology (e.g., Subcarrier Spacing (SCS) and Cyclic Prefix (CP) ) .
  • SCS Subcarrier Spacing
  • CP Cyclic Prefix
  • the CFR is defined as an “MBS frequency region” with a number of contiguous Physical Resource Blocks (PRBs) , which are configured within the dedicated unicast BWP.
  • PRBs Physical Resource Blocks
  • the starting PRB and the length of PRBs of the MBS frequency region are indicated using a suitable mechanism.
  • a MBS frequency region e.g., a MBS BWP
  • MBS BWP and unicast BWP can be used for the MBS PDSCH and unicast PDSCH transmission simultaneously (which need simultaneous activation of two BWPs) , without BWP switching.
  • the arrangements disclosed herein relate to both options.
  • Various arrangements disclosed herein define mechanisms of one or more timers used in MBS related operation. More specifically, UE behaviors are defined at the expiration of the MBS timer and for waking up to perform MBS-related operations after MBS timer expires. Conditions for MBS timer validation are also disclosed herein. The arrangements disclosed herein improves stability of MBS related operation, and UE power-on GC-PDCCH monitoring can be conversed, therefore improving UE experience.
  • FIG. 3 is a flowchart diagram illustrating an example method 300 for managing multicast communication, according to various arrangements.
  • the method 300 can be performed by the BS 102 and a UE (e.g., the UE 104a) .
  • the UE 104a determines a first timer for multicast.
  • the first timer is a timer for MBS-related operations.
  • the timer for MBS-related operations is a dedicated timer defined for MBS-related operations or for the CFR (e.g., the CFR 220) .
  • Such dedicated timer can be referred to as the first timer, the timer for MBS-related operations, a MBS timer, a CFR timer, or a GC-PDCCH monitoring timer.
  • the network configures the first timer for multicast for the UE 104a, at 305.
  • the network e.g., the BS 102 communicates the first timer or parameters thereof to the UE 104a via suitable signaling or indication.
  • the UE 104a receives the first timer or parameters thereof as part of the determining at 310.
  • the network e.g., the BS 102 does not configure the first timer for the UE 104a, and instead the UE 104a determines the first timer at 310 based on another suitable mechanism.
  • the UE 104a determines a second timer for BWP inactivity.
  • the second timer can be referred to as an BWP inactivity timer, or BWP-inactivityTimer, for example.
  • the network e.g., the BS 102 configures the second timer for BWP inactivity for the UE 104a, at 315.
  • the network e.g., the BS 102 communicates the second timer or parameters thereof to the UE 104a via suitable signaling or indication.
  • the UE 104a receives the second timer or parameters thereof as part of the determining at 320.
  • the network e.g., the BS 102 does not configure the second timer for the UE 104a, and instead the UE 104a determines the second timer at 320 based on another suitable mechanism.
  • the network (e.g., the BS 102) sends multicast transmission based on the first timer and the second timer.
  • the UE 104a receives the multicast transmission based on the first timer and the second timer.
  • FIG. 4 is a flowchart diagram illustrating an example method 400 for managing multicast communication, according to various arrangements.
  • the method 400 can be performed by the BS 102 and a UE (e.g., the UE 104a) .
  • block 330 includes at least one of blocks 410, 420, 430, 440, 450, and 460 and block 325 includes at least one of blocks 425, 435, 452, and 454.
  • the UE determines that the first timer expires (e.g., is no longer running, has expired, and so on) and that the second timer is running (e.g., remains running, has yet to be expired, has not expired, and so on) . That is, the MBS timer (the first timer) is configured by the network 102 to the UE 104a for receiving MBS and expires, but the BWP inactivity timer has not yet expired.
  • the UE 104a can perform one or more of 420, 430, 440, 450, or 460.
  • the UE 104a stops MBS-related operations in response to 410. For example, the UE stops to monitor DCI format with CRC scrambled by G-RNTI, stops to monitor DCI format with CRC scrambled by a group-common RNTI (e.g., G-CS-RNTI) , stops to receive a SPS PDSCH scrambled with a group-common RNTI (which can be the same as or different from the G-CS-RNTI) , stop to receive all transmissions related to MBS, disables related operations configured under CFR, or so on.
  • the network e.g., the BS 102
  • the UE stop receiving a DCI with CRC scrambled by a RNTI for the multicast.
  • the BS 102 continues to send an SPS downlink transmission for the multicast to the UE 104a.
  • the UE continues to receive the SPS downlink transmission (e.g., PDSCH) for the multicast. Then, the BS 102 sends to the UE 104a a UE-specific downlink control channel (e.g., a PDCCH carrying DCI format with CRC scrambled with C-RNTI or CS-RNTI) to activate or deactivate the SPS transmission for MBS.
  • a UE-specific downlink control channel e.g., a PDCCH carrying DCI format with CRC scrambled with C-RNTI or CS-RNTI
  • the UE receives signaling corresponding to activating, deactivating, or modifying transmission parameters for the SPS downlink transmission.
  • the BS 102 sends the signaling corresponding to activating, deactivating, or modifying transmission parameters for the SPS downlink transmission.
  • the signaling includes, for example, Media Access Layer (MAC) layer signaling (e.g., MAC Control Element (CE) ) .
  • MAC Media Access Layer
  • CE MAC Control Element
  • the MAC layer signaling can be carried on one of SPS PDSCH, and the activation, deactivation, and/or modification command takes effect in the next SPS PDSCH or at a specified time point (e.g., a time offset after the PDSCH carrying the MAC layer signaling) .
  • the UE 104a continues to provide feedback (e.g., Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) for MBS Transport Blocks (TBs) carried on the SPS PDSCHs.
  • feedback e.g., Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) for MBS Transport Blocks (TBs) carried on the SPS PDSCHs.
  • HARQ-ACK Hybrid Automatic Repeat Request Acknowledgement
  • the BS 102 sends to the BS 102 feedback for the SPS downlink transmission for the multicast, and the BS 102 receives the same at 452.
  • the BS 102 in response to receiving the feedback at 452, the BS 102 sends at least one retransmission of SPS downlink transmission for the multicast, and the UE 104a receives the same at 460.
  • the UE can provide feedback ACK or Negative Acknowledgement (NACK) in UE-specific resources according to reception of MBS TBs.
  • NACK Negative Acknowledgement
  • the UE 104a sends the NACK feedback to the BS 102.
  • the BS 102 can retransmit the MBS TB in a dynamic scheduling mode. That is, the retransmission of the MBS TB is scheduled by a UE-specific PDCCH, which carries a DCI format with CRC scrambled with C-RNTI or CS-RNTI.
  • the UE 104a in response to sending the feedback with NACK for the SPS downlink transmission for the multicast, the UE 104a starts receiving the DCI with CRC scrambled by the RNTI for the multicast, the DCI being used for scheduling the at least one retransmission of the SPS downlink transmission for the multicast.
  • the BS 102 in response to receiving the feedback with NACK for the SPS downlink transmission for the multicast, the BS 102 starts sending to the UE 104a the DCI with CRC scrambled by the RNTI for the multicast, the DCI being used for scheduling the at least one retransmission of the SPS downlink transmission for the multicast.
  • the UE stops providing feedback for MBS TBs carried on the SPS PDSCHs in response to the UE determining that the first timer expires and that the second timer is running.
  • the UE may continue to provide the NACK feedback in a feedback resource shared by a group of UEs receiving a same MBS TB in response to determining that the UE has failed to receive the MBS TB in a SPS PDSCH occasion.
  • the UE resumes monitoring the DCI format with CRC scrambled with G-RNTI or G-CS-RNTI. In other words, the monitoring of GC-PDCCH is triggered by the NACK feedback from UE.
  • the BS 102 can retransmit the MBS TB scheduled by either UE-specific PDCCH or GC-PDCCH.
  • the UE switches to the default DL BWP.
  • FIG. 5 is a flowchart diagram illustrating an example method 500 for managing multicast communication, according to various arrangements.
  • the method 500 can be performed by the BS 102 and a UE (e.g., the UE 104a) .
  • block 330 includes one or more of blocks 510, 520, 530, 540, 550, and 560 and block 325 includes one or more of blocks 515, 525, 535, 552, and 554.
  • the UE determines that the first timer is running (e.g., remains running, has yet to be expired, has not expired, and so on) and that the second timer expires (e.g., is no longer running, has expired, and so on) . That is, the MBS timer (the first timer) is configured by the network 102 to the UE 104a for receiving MBS and has not yet expired, but the BWP inactivity timer has expired.
  • the UE 104a can perform one or more of 520, 530, 540, 550, or 560.
  • the UE 104a switches a frequency range for information reception from an active BWP (e.g., the active BWP 220) to a CFR (e.g., the CFR 210) .
  • a CFR e.g., the CFR 210 .
  • the second timer e.g., the BWP inactivity timer
  • the UE 104a switches from the active BWP to the CFR to conserve power as the bandwidth of the CFR is no larger than the active BWP. Then, some delay will be introduced by bandwidth modification from the active BWP to the CFR.
  • the BS 102 communicates, with UE, information transmission using the frequency range of the CFR (instead of the active BWP) .
  • the UE 104a continues to use the frequency range of the active BWP for the information reception instead of switching. In other words, the UE 104a does not switch to the CFR after the BWP inactivity timer expires. In such examples, no bandwidth switching is needed.
  • the BS 102 communicates, with the UE 104a, information transmission using the frequency range of the active BWP.
  • the UE 104a receives an SPS downlink transmission (e.g., an SPS PDSCH) for the unicast, and at 535, the BS 102 sends the SPS downlink transmission for the unicast.
  • SPS downlink transmission include a SPS PDSCH scrambled by C-RNTI or CS-RNTI.
  • the UE 104a stops monitoring the DCI format with CRC scrambled by C-RNTI or CS-RNTI, but still receives SPS PDSCH for unicast.
  • the BS 102 In response to determining that the transmission parameters of SPS PDSCH change, the BS 102 indicate the updated transmission parameters via suitable signaling such as a MAC layer signaling (e.g., MAC CE) .
  • suitable signaling such as a MAC layer signaling (e.g., MAC CE)
  • the MAC layer signaling can be carried on one of SPS PDSCH.
  • the updated transmission parameters takes effect for the next SPS PDSCH, the next modification period, or a specified time point (e.g., a time offset) after the PDSCH carrying the MAC layer signaling.
  • the deactivation of the SPS transmission can be indicated via a suitable signaling (e.g., MAC layer signaling) .
  • a suitable signaling e.g., MAC layer signaling
  • the UE 104a will deactivate the SPS transmission for the next SPS PDSCH, the next modification period, or a specified time point (e.g., a time offset) after the PDSCH carrying the MAC layer signaling.
  • the UE 104a stops providing feedback (e.g., HARQ-ACK) for unicast TBs carried on SPS downlink transmissions. In some arrangements, the UE 104a continues to provide feedback (e.g., ACK/NACK) in UE-specific resources according to reception of unicast TBs. For example, at 550, the UE 104a sends to the BS 102 feedback for the SPS downlink transmission for the unicast, and at 552, the BS 102 receives the feedback for the SPS downlink transmission for the unicast. In that regard, at 554, in response to receiving the feedback at 552, the BS 102 sends at least one retransmission of SPS downlink transmission for the unicast, and the UE 104a receives the same at 560.
  • feedback e.g., HARQ-ACK
  • the UE 104a in response to determining the UE has failed to receive a unicast TB in a SPS PDSCH occasion, the UE 104a sends the NACK feedback to the BS 102. Then, the UE 104a resumes monitoring the DCI format with CRC scrambled with C-RNTI or CS-RNTI. In other words, in response to sending the feedback with NACK for the SPS downlink transmission for the unicast, the UE 104a starts monitoring GC-PDCCH. The BS 102 can retransmit the unicast TB in a dynamic scheduling mode.
  • the BS 102 schedules the retransmission of the unicast TB using a UE-specific PDCCH, which carries a DCI format with CRC scrambled with C-RNTI or CS-RNTI.
  • the UE 104a in response to sending the feedback with NACK for the SPS downlink transmission for the unicast, the UE 104a start receiving the DCI with CRC scrambled by the RNTI for the unicast, where the DCI is used for scheduling the at least one retransmission of the SPS downlink transmission for the unicast.
  • the BS 102 in response to receiving the feedback with NACK for the SPS downlink transmission for the unicast, the BS 102 start sending the DCI with CRC scrambled by the RNTI for the multicast, where the DCI is used for scheduling the at least one retransmission of the SPS downlink transmission for the unicast.
  • FIG. 6 is a flowchart diagram illustrating an example method 600 for managing multicast communication, according to various arrangements.
  • the method 600 can be performed by the BS 102 and a UE (e.g., the UE 104a) .
  • block 330 includes one or more of blocks 610 and 620, and block 325 includes block 615.
  • the UE determines that the first timer expires (e.g., is no longer running, has expired, and so on) and that the second timer is running (e.g., remains running, has yet to be expired, has not expired, and so on) . That is, the MBS timer (the first timer) is configured by the network 102 to the UE 104a for receiving MBS and expires, but the BWP inactivity timer has not yet expired.
  • the UE 104a stops MBS-related operations. For example, the UE 104a stops to monitor DCI format with CRC scrambled by G-RNTI, stops to monitor DCI format with CRC scrambled by a group-common RNTI (e.g., G-CS-RNTI) , stops to receive a SPS PDSCH scrambled with a group-common RNTI (which can be the same as or different from the G-CS-RNTI) , stop to receive all transmissions related to MBS, disables related operations configured under CFR, or so on.
  • G-RNTI e.g., G-CS-RNTI
  • a group-common RNTI which can be the same as or different from the G-CS-RNTI
  • the network (e.g., the BS 102) can wakes the UE 104a up to perform the MBS-related operations which have been halted.
  • the UE 104a can perform 620.
  • the UE receives a UE-specific downlink control channel (e.g., PDCCH) that schedules a downlink physical channel (e.g., MBS TB PDSCH) corresponding to the multicast.
  • the BS 102 sends the UE-specific downlink control channel that schedules the downlink physical channel corresponding to the multicast.
  • the network side schedules a PDSCH carrying a MBS TB using a UE-specific PDCCH, which carries a DCI format with CRC scrambled by C-RNTI or CS-RNTI.
  • the MBS TB is identified by a higher layer, e.g., MAC layer of the UE 104a.
  • the MBS TB is identified via the indication in the DCI carried on the UE-specific PDCCH. For example,
  • the MBS timer will be restarted, and the UE 104a resumes the MBS-related operations.
  • the restoration of the MBS-related operations starts after a certain time point.
  • the time point can be a time offset after the UE 104a receives the PDSCH carrying the MBS TB.
  • the time offset can be defined according to UE capability in some examples. Accordingly, at 630, in response to receiving the UE-specific downlink control channel that schedules the downlink physical channel corresponding to multicast or the paging downlink control channel, the UE 104a performs at least one of recovering the MBS operations or resetting the first timer.
  • FIG. 7 is a flowchart diagram illustrating an example method 700 for managing multicast communication, according to various arrangements.
  • the method 700 can be performed by the BS 102 and a UE (e.g., the UE 104a) .
  • block 330 includes one or more of blocks 710, 720, and 730, and block 325 includes block 715.
  • the UE determines that the first timer expires (e.g., is no longer running, has expired, and so on) and that the second timer is running (e.g., remains running, has yet to be expired, has not expired, and so on) . That is, the MBS timer (the first timer) is configured by the network 102 to the UE 104a for receiving MBS and expires, but the BWP inactivity timer has not yet expired.
  • the UE 104a stops MBS-related operations. For example, the UE 104a stops to monitor DCI format with CRC scrambled by G-RNTI, stops to monitor DCI format with CRC scrambled by a group-common RNTI (e.g., G-CS-RNTI) , stops to receive a SPS PDSCH scrambled with a group-common RNTI (which can be the same as or different from the G-CS-RNTI) , stop to receive all transmissions related to MBS, disables related operations configured under CFR, or so on.
  • G-RNTI e.g., G-CS-RNTI
  • a group-common RNTI which can be the same as or different from the G-CS-RNTI
  • the network can wakes the UE 104a up to perform the MBS-related operations which have been halted.
  • the UE 104a can perform 720.
  • the UE receives a paging downlink control channel (e.g., a paging PDCCH) indicating recovery of MBS operations.
  • the BS 102 sends the paging downlink control channel indicating recovery of MBS operations.
  • Blocks 715 and 720 allows the UE 104a to recover MBS related operation.
  • the paging transmission (including at least one of the paging PDCCH and a paging PDSCH) can be used to indicate MBS related operation recovery.
  • the MBS timer will be restarted, and the UE 104a resumes the MBS-related operations.
  • the restoration of the MBS-related operations starts after a certain time point.
  • the time point can be a time offset after the UE 104a receives the PDSCH carrying the MBS TB.
  • the time offset can be defined according to UE capability in some examples. Accordingly, at 730, in response to receiving the paging downlink control channel indicating recovery of MBS related operations, the UE 104a performs at least one of recovering the MBS related operations or resetting the first timer.
  • the paging downlink control channel (e.g., a paging PDCCH) can indicate the recovery of MBS related operations can be implemented using fields of the packing PDCCH.
  • FIG. 8 is a diagram illustrating a DCI format for a paging PDCCH 800, according to various arrangements.
  • the DCI format 1_0 with CRC scrambled by P-RNTI is shown in FIG. 8 as an example of the paging PDCCH 800.
  • the DCI format of the paging PDCCH 800 includes fields such as a short message indicator field 810, a short message field 820, scheduling information for paging field 830, and a reserved field 840.
  • the reserved field 840 has one or more bits (e.g., 8 bits) .
  • a code point of an information field represents a specific value or bits of the information field.
  • the short message indicator field 810 has one or more bits (e.g., 2 bits) in the DCI format.
  • the short message indicator field 810 is used to indicate validity of the remaining information fields 820, 830, and 840 in the DCI format, as showed in FIG. 9, which illustrates the mapping 900 between the bit field and the indication.
  • a bit field or code point of “01” represents that only the scheduling information for paging field 830 in the DCI is valid, and the bits in short message field 820 are reserved.
  • a bit field or code point of “10” represents only the short message field 820 in the DCI is valid, and the bits in scheduling information for paging field 830 are reserved.
  • a bit field or code point of “11” represents both the short message field 820 and the scheduling information for paging field 830 are valid in the DCI. As shown, a bit field or code point of “00” is reserved.
  • the short message field 820 has one or more bits (e.g., 8 bits) in the DCI format.
  • the short message field 820 contains one or more short messages therein.
  • FIG. 10 is a diagram illustrating the mapping 1000 between the bits and the short messages of the short message field 820 in the paging PDCCH, according to various arrangements. As shown, bit or code point of “1” corresponds to the short message of systemInfoModification. A bit or code point of “2” corresponds to the short message of etwsAndCmasIndication. A bit or code point of 3 corresponds to the short message of stopPagingMonitoring. Bits or code points 4-8 are currently not used.
  • the scheduling information for paging field 830 has one or more bits and contains bandwidth related information.
  • the scheduling information for paging field 830 is used to indicate scheduling information of paging PDSCH.
  • the scheduling information includes for example frequency-domain resource assignment information, time-domain resource assignment, Virtual Resource Blocks (VRB) -to-PRB mapping, Modulation and Coding Scheme (MCS) , TB scaling, and so on.
  • VRB Virtual Resource Blocks
  • MCS Modulation and Coding Scheme
  • a code point of the short message indicator field 810 indicates the recovery of the MBS related operations.
  • the reserved value or codepoint of the short message indicator field 810 is used for the indication.
  • the value or codepoint “00” of the short message indicator field 810 is defined as MBS related operation recover indication. More specifically, for the UE 104a stop to perform MBS related operation as the MBS timer expires, in response to the UE 104a receiving a paging PDCCH in its paging occasion indicating that the value of short message field is “00. ” The UE 104a recovers the MBS-related operations.
  • At least one reserved bit in the short message field 820 indicates the recovery of the MBS related operations.
  • one or more reserved bits or code points corresponding thereto in the short message field 820 are used for the indication.
  • one or more bits (e.g., bits 4-8) in the short message field 820 are reserved as shown in FIG. 10.
  • One or more bits from the reserved bits can be used for MBS related operation recover indication.
  • 1 bit from the reserved bits is used for MBS related operation recover indication.
  • the UE 104a recovers the MBS-related operations.
  • more than one bits of reserved bits in the short message field 820 are used for MBS related operation recover indication.
  • Each bit corresponds to a specific MBS or a specific MBS group.
  • the above mapping relationship is configured via signaling or defined in the specification. Then, in response to determining that the value of one of bits is set to a predefined value, e.g., 1, the UE 104a recovers the specific MBS service or the specific MBS service group corresponding to or mapped to this bit.
  • MBS-related operations are divided into different types.
  • Each bit of reserved bits in the short message field 820 corresponds to a type of MBS related operations.
  • the above mapping relationship is configured via signaling or defined in the specification. Then, in response to determining that the value of one of bits is set to a predefined value, e.g., 1, the UE 104a recovers the type of the MBS corresponding to or mapped to this bit.
  • mapping relationship between at least one reserved bit in the short message field and UE IDs are preconfigured , e.g., via RRC signaling. Then, the value of one of bits set to a predefined value, e.g., 1, indicates that the MBS related operation should be recovered by UE corresponding to this bit.
  • a combination of at least one reserved bit in the short message field 820 and at least one reserved bit in the reserved portion 840 in the DCI format indicates the recovery of the MBS related operations.
  • several bits, e.g., 4-8 bits in the short message field 820 are reserved.
  • another 8 bits in the DCI format e.g., in the reserved portion 840
  • One or more bits from each of the reserved bits in the short message filed 820 and the reserved portion 840 can be used for MBS related operation recover indication.
  • 1 bit from the reserved bits in short message field 820 is used for indicating MBS related operation needs to be recovered.
  • the UE 104a further determines which type of MBS related operation is to be recovered according to the indication of at least one or all of the reserved bits in the reserved portion 840 of the DCI format.
  • each bit of at least one or all of the reserved bits in the reserved portion 840 of the DCI format corresponds to a specific MBS service or a specific MBS service group.
  • the above mapping relationship is configured via signaling or defined in the specification. Then, in response to determining that the value of one of bits is set to a predefined value, e.g., 1, the UE 104a recovers the specific MBS service or the specific MBS service group corresponding to or mapped to this bit.
  • MBS-related operations are divided into different types.
  • Each bit of at least one or all of the reserved bits in the reserved portion 840 of the DCI format corresponds to a type of MBS related operations.
  • the above mapping relationship is configured via signaling or defined in the specification. Then, in response to determining that the value of one of bits is set to a predefined value, e.g., 1, the UE 104a recovers the type of the MBS corresponding to or mapped to this bit.
  • mapping relationship between at least one reserved bit in the DCI format and UE IDs are preconfigured , e.g., via RRC signaling. Then, the value of one of bits being set to a predefined value, e.g., 1, indicates that the MBS related operation should be recovered by UE corresponding to this bit.
  • a combination of at least one reserved bit in the short message field 820 and at least one bit in the scheduling information field 830 indicates the recovery of the MBS related operations.
  • several bits, e.g., 4-8 bits in the short message field 820 are reserved.
  • the value of short message indicator field 810 is set to “10, ” all bits used for the scheduling information for paging field 830 indication are reserved.
  • One or more bits from these bits of the scheduling information for paging field 830 can be used for MBS related operation recover indication.
  • 1 bit from the reserved bits in short message field 820 is used for indicating MBS related operation needs to be recovered.
  • the UE 104a further determines which type of MBS related operation is to be recovered according to the indication of at least one or all of the reserved bits in the scheduling information for paging field 830 that are originally used for scheduling information indication.
  • each bit of at least one or all of the reserved bits in the scheduling information for paging field 830 that are originally used for scheduling information indication corresponds to a specific MBS service or a specific MBS service group.
  • the above mapping relationship is configured via signaling or defined in the specification. Then, in response to determining that the value of one of bits is set to a predefined value, e.g., 1, the UE 104a recovers the specific MBS service or the specific MBS service group corresponding to or mapped to this bit.
  • MBS-related operations are divided into different types.
  • Each bit of at least one or all of the reserved in the scheduling information for paging field 830 that are originally used for scheduling information indication corresponds to a type of MBS related operations.
  • the above mapping relationship is configured via signaling or defined in the specification. Then, in response to determining that the value of one of bits is set to a predefined value, e.g., 1, the UE 104a recovers the type of the MBS corresponding to or mapped to this bit.
  • 1 bit from the reserved bits in short message field is used for indicating there are MBS related operation needs to be recovered.
  • the value of this bit being set to a predefined value, e.g., 1, indicates whether the UE should recover to perform the MBS related operation.
  • the mapping relationship between bits originally used for scheduling information indication and UE IDs are preconfigured , e.g., via RRC signaling. Then, the value of one of bits being set to a predefined value, e.g., 1, indicates that the MBS related operation should be recovered by UE corresponding to this bit.
  • a combination of at least one reserved bit in the short message field 820, at least one bit in the scheduling information field 830, and at least one reserved bit in the reserved portion 840 in the DCI format indicates the recovery of the MBS related operations.
  • several bits, e.g., 4-8 bits in the short message field 820 are reserved.
  • all bits used for the scheduling information for paging field 830 indication are reserved.
  • One or more bits from these bits of the scheduling information for paging field 830 can be used for MBS related operation recover indication.
  • 1 bit from the reserved bits in short message field 820 is used for indicating that some MBS related operation needs to be recovered.
  • the UE 104a further determines which type of MBS related operation is to be recovered according to the indication of at least one or all of the reserved bits in the scheduling information for paging field 830 that are originally used for scheduling information indication as well as the indication of at least one or all of the reserved bits in the reserved portion 840 of the DCI format.
  • each bit of at least one or all of the reserved bits in the scheduling information for paging field 830 that are originally used for scheduling information indication and each bit of the at least one or all of the reserved bits in the reserved portion 840 of the DCI format correspond to a specific MBS service or a specific MBS service group.
  • the above mapping relationship is configured via signaling or defined in the specification. Then, in response to determining that the value of one of these bits is set to a predefined value, e.g., 1, the UE 104a recovers the specific MBS service or the specific MBS service group corresponding to or mapped to this bit.
  • MBS-related operations are divided into different types.
  • Each bit of at least one or all of the reserved bits in the scheduling information for paging field 830 that are originally used for scheduling information indication and each bit of the at least one or all of the reserved bits in the reserved portion 840 of the DCI format correspond to a type of MBS related operations.
  • the above mapping relationship is configured via signaling or defined in the specification. Then, in response to determining that the value of one of the bits is set to a predefined value, e.g., 1, the UE 104a recovers the type of the MBS corresponding to or mapped to this bit.
  • 1 bit from the reserved bits in short message field is used for indicating there are MBS related operation needs to be recovered.
  • the value of this bit being set to a predefined value, e.g., ‘1’ indicates whether the UE should recover to perform the MBS related operation.
  • the mapping relationship between bits originally used for scheduling information indication and reserved bits in the DCI format and UE IDs are preconfigured , e.g., via RRC signaling. Then, the value of one of bits being set to a predefined value, e.g., ‘1’ , indicates that the MBS related operation should be recovered by UE corresponding to this bit.
  • a combination of a reserved value or codepoint in the short message indicator field 810 and a paging PDSCH scheduled by the paging downlink control channel are used to indicate the recovery of the MBS related operations.
  • the value or codepoint “00” of the short message indicator field 810 is defined as MBS related operation recover indication.
  • the UE 104a In response to the UE 104a receiving a paging PDCCH in its paging occasion with the short message indicator field 810 sets to “00, ” the UE 104a receives the paging PDSCH according to the indication of the scheduling information for paging field 830 in the DCI format. The UE 104a further determines which type of MBS related operation is to be recovered according to the indication in paging PDSCH. For example, each bit of the part or all reserved bits in the paging PDSCH corresponds to a specific MBS service or a specific MBS service group. Then, in response to determining that the value of one of bits is set to a predefined value, e.g., 1, the UE 104a determines that the specific MBS service or the specific MBS service group corresponding to this bit is to be recovered.
  • a predefined value e.g., 1, the UE 104a determines that the specific MBS service or the specific MBS service group corresponding to this bit is
  • the UE 104a receives a paging PDSCH according to the indication of the scheduling information for paging field 830 in the DCI format.
  • the UE 104a further determines which UE needs to recover the MBS-related operations. More specifically, the UE ID of UEs which should recover the MBS related operation are included in the paging PDSCH.
  • the mapping relationship between bits in paging PDSCH and UE IDs are preconfigured, e.g., via RRC signaling. The value of one of bits being set to a predefined value, e.g., “1, ” indicates that the MBS-related operation is to be recovered by a UE (e.g., the UE ID) corresponding to or mapped to this bit.
  • a combination of a reserved bit in the short message field 820 and a paging PDSCH scheduled by the paging downlink control channel (received at 720) are used to indicate the recovery of the MBS related operations.
  • several bits, e.g., 4-8 bits in the short message field 820 are reserved.
  • One or more bits from the reserved bits in the short message field 820 can be used for MBS related operation recover indication.
  • the UE 104a receives paging PDSCH according to the indication of scheduling information for paging filed 830 in the DCI format.
  • the UE 104a further determines which type of MBS related operation is to be recovered according to the indication in paging PDSCH. For example, each bit of the part or all reserved bits in the paging PDSCH corresponds to a specific MBS service or a specific MBS service group.
  • the UE 104a determines that the specific MBS service or the specific MBS service group corresponding to this bit is to be recovered.
  • the UE 104a further determines The UE 104a further determines which UE needs to recover the MBS-related operations. More specifically, the UE ID of UEs which should recover the MBS related operation are included in the paging PDSCH. Alternatively, the mapping relationship between bits in paging PDSCH and UE IDs are preconfigured, e.g., via RRC signaling. The value of one of bits being set to a predefined value, e.g., “1, ” indicates that the MBS-related operation is to be recovered by a UE (e.g., the UE ID) corresponding to or mapped to this bit.
  • a UE e.g., the UE ID
  • a combination of a code point in the short message indicator field and at least one bit of the remaining bits in the DCI format indicates the recovery of the MBS related operations.
  • the code point “00” of the short message indicator field is defined as MBS related operation recover indication.
  • a UE receives a paging PDCCH in its paging occasion with short message indicator field sets to “00, ” the UE further determines which type of MBS related operation should be recovered according to the indication of part or all reserved bits in the DCI format.
  • Each bit of the part or all reserved bits in the DCI format corresponds to a specific MBS service or a specific MBS service group.
  • the above mapping relationship is configured via signaling or defined in the specification. Then, the value of one of bits set to a predefined value, e.g., 1, indicates that the receiving of the MBS service corresponding to this bit needs to be recovered.
  • MBS related operations are divided into different types.
  • Each bit of the part or all reserved bits in the DCI format corresponds to a type of MBS related operation.
  • the above mapping relationship is configured via signaling or defined in the specification. Then, the value of one of bits being set to a predefined value, e.g., 1, indicates that the MBS related operation corresponding to this bit needs to be recovered.
  • a UE receives a paging PDCCH in its paging occasion with short message indicator field sets to “00, ” the UE further determines whether it should recover the MBS-related operation or not. More specifically, the mapping relationship between reserved bits in the DCI format and UE IDs are preconfigured , e.g., via RRC signaling. Then the value of one of bits being set to a predefined value, e.g., 1, indicates that the MBS related operation should be recovered by UE corresponding to this bit.
  • the validation conditions of the first timer are defined.
  • the UE 104a determines that the MBS timer is deemed to be invalid.
  • a CFR for the multicast transmission is entirely contained within a default downlink BWP; or 2) a CFR for the multicast transmission is entirely contained in the default downlink BWP, and the CFR of the default BWP contains the multicast transmission.
  • the CFR is entirely contained within the default DL BWP.
  • the CFR can be the same as the CFR associated with the active BWP, as shown in FIG. 11.
  • a CFR 1120 for GC PDCCH and/or GC-PDSCH is confined within the frequency resource of a dedicated unicast BWP (also referred to as an active BWP 1110) to support simultaneous reception of unicast and multicast in the same slot.
  • a default BWP 1130 (or a default DL BWP) is entirely within the active BWP 1110.
  • the CFR 1120 can be the same as the CFR associated with the active BWP 1110.
  • the CFR can be different from the CFR associated with the active BWP, as shown in FIG. 12.
  • a CFR 1220 for GC PDCCH and/or GC-PDSCH is confined within the frequency resource of a dedicated unicast BWP (also referred to as an active BWP 1210) to support simultaneous reception of unicast and multicast in the same slot.
  • a default BWP 1230 (or a default DL BWP) is entirely outside of the active BWP 1210.
  • the CFR 1240 is different from the CFR 1220 associated with the active BWP 1210.
  • CFR is contained within the default DL BWP and the CFR associated with default BWP contains the MBS service that the UE is to receive.
  • the CFR 1240 is different from the CFR 1220 associated with the active BWP 1210 as shown in FIG. 12.
  • any two components so associated can also be viewed as being “operably connected, " or “operably coupled, " to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable, " to each other to achieve the desired functionality.
  • operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation donnés à titre d'exemple comprennent un procédé de communication sans fil comprenant la détermination, par un dispositif de communication sans fil, d'un premier temporisateur pour la multidiffusion, la détermination, par le dispositif de communication sans fil, d'un second temporisateur pour l'inactivité de la partie de bande passante (BWP), et la réception, par le dispositif de communication sans fil en provenance d'un réseau, d'une transmission en multidiffusion sur la base du premier temporisateur et du second temporisateur.
PCT/CN2021/121676 2021-09-29 2021-09-29 Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil WO2023050138A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2021/121676 WO2023050138A1 (fr) 2021-09-29 2021-09-29 Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil
CN202180102822.9A CN118020361A (zh) 2021-09-29 2021-09-29 用于管理无线通信网络中的组播通信的方法与系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/121676 WO2023050138A1 (fr) 2021-09-29 2021-09-29 Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil

Publications (1)

Publication Number Publication Date
WO2023050138A1 true WO2023050138A1 (fr) 2023-04-06

Family

ID=85780995

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/121676 WO2023050138A1 (fr) 2021-09-29 2021-09-29 Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil

Country Status (2)

Country Link
CN (1) CN118020361A (fr)
WO (1) WO2023050138A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112789935A (zh) * 2018-08-06 2021-05-11 三星电子株式会社 在未授权频带中的小区和带宽部分操作
US20210168815A1 (en) * 2018-08-10 2021-06-03 Lg Electronics Inc. Method for configuring bandwidth part in wireless communication system and device for supporting same
WO2021139747A1 (fr) * 2020-01-10 2021-07-15 FG Innovation Company Limited Procédé et équipement d'utilisateur permettant la réception de données de service de diffusion/multidiffusion
CN113411888A (zh) * 2020-03-17 2021-09-17 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112789935A (zh) * 2018-08-06 2021-05-11 三星电子株式会社 在未授权频带中的小区和带宽部分操作
US20210168815A1 (en) * 2018-08-10 2021-06-03 Lg Electronics Inc. Method for configuring bandwidth part in wireless communication system and device for supporting same
WO2021139747A1 (fr) * 2020-01-10 2021-07-15 FG Innovation Company Limited Procédé et équipement d'utilisateur permettant la réception de données de service de diffusion/multidiffusion
CN113411888A (zh) * 2020-03-17 2021-09-17 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
MODERATOR (CMCC): "Summary#3 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS", 3GPP DRAFT; R1-2108359, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210816 - 20210827, 19 August 2021 (2021-08-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052042159 *
MODERATOR (CMCC): "Summary#5 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS", 3GPP DRAFT; R1-2108428, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210816 - 20210827, 20 August 2021 (2021-08-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052042624 *
MODERATOR (CMCC): "Summary#8 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS", 3GPP DRAFT; R1-2108574, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210816 - 20210827, 27 August 2021 (2021-08-27), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052042719 *

Also Published As

Publication number Publication date
CN118020361A (zh) 2024-05-10

Similar Documents

Publication Publication Date Title
US11363626B2 (en) Method and apparatus for scheduling multiple transmission in a wireless communication system
US11968623B2 (en) Method and apparatus having a discontinuous reception configuration
CN113906789B (zh) 下一代无线网络中用于省电状态下的用户设备的调度方法和用户设备
EP3716697A1 (fr) Opérations d'économie d'énergie pour systèmes de communication
EP3949542B1 (fr) Procédés de configuration de signal de réveil (wus) basés sur un canal de commande physique de liaison descendante (pdcch)
EP2995025B1 (fr) Procedes et appareils pour signalisation dans des systemes duplex par repartition dans le temps dynamique
US9648599B2 (en) System and method for avoiding collisions between open discovery and cellular resources
WO2020191740A1 (fr) Procédé et dispositif de réception ou de transmission de signal, et système
US20230345370A1 (en) System and method for pdcch monitoring
WO2022027618A1 (fr) Techniques d'économie d'énergie
US10103828B2 (en) Multi-stage reception monitoring
CN114450909A (zh) 用调度下行链路控制信息触发功率节省模式
WO2020220342A1 (fr) Procédé et appareil d'envoi de signal de référence et système de communication
US20220132544A1 (en) Reduced downlink control information (dci) feedback for semi-persistent scheduling (sps)
WO2023050138A1 (fr) Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil
US20230199749A1 (en) Configured grant enhancements in unlicensed band
US20230232418A1 (en) Piggybacking downlink control information (dci) for semi-persistent scheduling
CN116848911A (zh) 用于控制信道监测程序的方法、装置与系统
US11979885B2 (en) Extended physical downlink control channel monitoring
WO2022205301A1 (fr) Procédé et système de configuration de ressources
WO2023077418A1 (fr) Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil
US20230247717A1 (en) Discontinuous reception alignment grouping for sidelink and cellular communication
US20240187202A1 (en) Systems and methods for managing frequency resource group based service transmissions
US20240114525A1 (en) Systems and methods of group common transmission
WO2023132912A1 (fr) Commutation entre des groupements d'ensembles d'espaces de recherche

Legal Events

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

Ref document number: 21958728

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE