WO2023153997A1 - Alignement de taille de dci pour multidiffusion et monodiffusion sur des parties de bande passante qui se chevauchent - Google Patents

Alignement de taille de dci pour multidiffusion et monodiffusion sur des parties de bande passante qui se chevauchent Download PDF

Info

Publication number
WO2023153997A1
WO2023153997A1 PCT/SE2023/050119 SE2023050119W WO2023153997A1 WO 2023153997 A1 WO2023153997 A1 WO 2023153997A1 SE 2023050119 W SE2023050119 W SE 2023050119W WO 2023153997 A1 WO2023153997 A1 WO 2023153997A1
Authority
WO
WIPO (PCT)
Prior art keywords
dci
size
multicast
unicast
bandwidth part
Prior art date
Application number
PCT/SE2023/050119
Other languages
English (en)
Inventor
Erik Stare
Stefan Parkvall
Ratheesh Kumar MUNGARA
Florent Munier
Jörg Huschke
Rui Fan
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2023153997A1 publication Critical patent/WO2023153997A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • 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/1854—Scheduling and prioritising arrangements
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated

Definitions

  • the present disclosure relates to a cellular communications network and, more specifically, related to Downlink Control Information (DCI) size alignment.
  • DCI Downlink Control Information
  • 3GPP Third Generation Partnership Project
  • NR New Radio
  • UEs User Equipments
  • RAN Radio Access Network
  • a group-common Physical Downlink Control Channel (PDCCH) with Cyclic Redundancy Check (CRC) scrambled by a Group Radio Network Temporary Identifier (G-RNTI) schedules a group-common Physical Downlink Shared Channel (PDSCH) with a CRC scrambled with the same G-RNTI.
  • PDC Point-to-Multipoint
  • a UE-specific PDCCH with CRC scrambled by a Cell Radio Network Temporary Identifier (C-RNTI) schedules a group-common PDSCH with CRC scrambled with a G-RNTI known by all UEs to receive that PDSCH.
  • C-RNTI Cell Radio Network Temporary Identifier
  • One such UE-specific PDCCH is transmitted to each UE to receive the PDSCH. This is referred to as PTM scheme 2 below.
  • a UE-specific PDCCH with CRC scrambled by a G-RNTI schedules a group- common PDSCH with CRC scrambled with the same G-RNTI.
  • the UE-specific PDCCHs are separated in non-overlapping UE-specific Search Spaces (USS). This is referred to as PTM scheme 3, but not further discussed below.
  • a UE-specific PDCCH with CRC scrambled by a C-RNTI schedules a UE-specific PDSCH with CRC scrambled with the same C-RNTI.
  • This is legacy unicast Point- to-Point (PTP) communication, as specified for 3GPP NR, e.g., in Release 15 and 16.
  • PTP Point- to-Point
  • IP Internet Protocol
  • this BWP may be used for both unicast and multicast.
  • the Downlink Control Information (DCI) size of a unicast or multicast PDCCH depends on the size of the BWP.
  • the DCI size of the G-RNTI PDCCH i.e., the PDCCH with CRC scrambled by G-RNTI
  • the C-RNTI PDCCH i.e., the PDCCH with CRC scrambled by C-RNTI
  • BD Blind Decodes
  • a method performed by a User Equipment (UE) configured with a first bandwidth part for unicast reception and a second bandwidth part for multicast reception comprises receiving, from a network node, information that configures the UE with a number of padding bits for a DCI format configured for a particular bandwidth part, wherein the number of padding bits configured for the DCI format for the particular bandwidth part is such that a total DCI size for the DCI format for the particular bandwidth part after the number of padding bits is applied is equal to a common DCI size.
  • UE User Equipment
  • the method further comprises performing blind decoding for reception of a DCI of the DCI format in the particular bandwidth part based on the total DCI size for the DCI format for the particular bandwidth part. In this manner, the UE may receive both unicast and multicast without increasing the number of blind decodes.
  • the common DCI size is a common DCI size for multicast DCIs configured on a multicast bandwidth part and unicast DCIs configured on a unicast bandwidth part.
  • the DCI format is either a multicast DCI format or a unicast DCI format
  • the common DCI size is a common DCI size for DCIs using the multicast DCI format configured on a multicast bandwidth part and DCIs using the unicast DCI format configured on a unicast bandwidth part.
  • the common DCI size is a common DCI size for multicast DCIs and unicast DCIs configured on the same unicast bandwidth part.
  • the DCI format is either a multicast DCI format or a unicast DCI format
  • the common DCI size is a common DCI size for DCIs using the multicast DCI format and DCIs using the unicast DCI format configured on the same unicast bandwidth part.
  • the common DCI size is a common DCI size for multicast DCIs and unicast DCIs for all UEs in a Multicast Broadcast Service (MBS) group.
  • MBS Multicast Broadcast Service
  • the common DCI size is a common DCI size for multicast DCIs and unicast DCIs for all UEs in a MBS group across different bandwidth parts having different bandwidth part sizes.
  • the common DCI size is a common DCI size for multicast DCIs and unicast DCIs.
  • the common DCI size is a common DCI size for DCIs on different bandwidth parts having different bandwidth part sizes.
  • the common DCI size is a common DCI size for DCI formats for unicast downlink and unicast uplink.
  • the common DCI size is for unicast and multicast DCIs within the particular bandwidth part and is such that multicast DCI sizes in different bandwidth parts are always different.
  • the common DCI size is for unicast and multicast DCIs within the particular bandwidth part and is such that multicast DCI sizes across any pair of bandwidth parts are different.
  • receiving the information that configures the UE with the number of padding bits for the DCI format configured for the particular bandwidth part comprises receiving the information via Radio Resource Control (RRC) signaling.
  • RRC Radio Resource Control
  • a UE configured with a first bandwidth part for unicast reception and a second bandwidth part for multicast reception comprises one or more transmitters, one or more receivers, and processing circuitry associated with the one or more transmitters and the one or more receivers.
  • the processing circuitry is configured to cause the UE to receive, from a network node, information that configures the UE with a number of padding bits for a DCI format configured for a particular bandwidth part, wherein the number of padding bits configured for the DCI format for the particular bandwidth part is such that a total DCI size for the DCI format for the particular bandwidth part after the number of padding bits is applied is equal to a common DCI size.
  • the processing circuitry is further configured to cause the UE to perform blind decoding for reception of a DCI of the DCI format in the particular bandwidth part based on the total DCI size for the DCI format for the particular bandwidth part.
  • a method performed by a network node for DCI size alignment for a UE that is configured with a first bandwidth part for unicast reception and a second bandwidth part for multicast reception comprises transmitting, to the UE, information that configures the UE with a number of padding bits for a DCI format configured for a particular bandwidth part, wherein the number of padding bits configured for the DCI format for the particular bandwidth part is such that a total DCI size for the DCI format for the particular bandwidth part after the number of padding bits is applied is equal to a common DCI size.
  • the method further comprises transmitting, to the UE, DCI in the particular bandwidth part using the DCI format and the configured number of padding bits for the DCI format.
  • the common DCI size is a common DCI size for multicast DCIs configured on a multicast bandwidth part and unicast DCIs configured on a unicast bandwidth part.
  • the DCI format is either a multicast DCI format or a unicast DCI format
  • the common DCI size is a common DCI size for DCIs using the multicast DCI format configured on a multicast bandwidth part and DCIs using the unicast DCI format configured on a unicast bandwidth part.
  • the common DCI size is a common DCI size for multicast DCIs and unicast DCIs configured on the same unicast bandwidth part.
  • the DCI format is either a multicast DCI format or a unicast DCI format
  • the common DCI size is a common DCI size for DCIs using the multicast DCI format and DCIs using the unicast DCI format configured on the same unicast bandwidth part.
  • the common DCI size is a common DCI size for multicast DCIs and unicast DCIs for all UEs in a MBS group.
  • the common DCI size is a common DCI size for multicast DCIs and unicast DCIs for all UEs in a MBS group across different bandwidth parts having different bandwidth part sizes.
  • the common DCI size is a common DCI size for multicast
  • the common DCI size is a common DCI size for DCIs on different bandwidth parts having different bandwidth part sizes.
  • the common DCI size is a common DCI size for DCI formats for unicast downlink and unicast uplink.
  • the common DCI size is for unicast and multicast DCIs within the particular bandwidth part and is such that multicast DCI sizes in different bandwidth parts are always different.
  • the common DCI size is for unicast and multicast DCIs within the particular bandwidth part and is such that multicast DCI sizes across any pair of bandwidth parts are different.
  • transmitting the information that configures the UE with the number of padding bits for the DCI format configured for the particular bandwidth part comprises transmitting the information via RRC signaling.
  • a network node for DCI size alignment for a UE that is configured with a first bandwidth part for unicast reception and a second bandwidth part for multicast reception comprises processing circuitry configured to cause the network node to transmit, to the UE, information that configures the UE with a number of padding bits for a DCI format configured for a particular bandwidth part, wherein the number of padding bits configured for the DCI format for the particular bandwidth part is such that a total DCI size for the DCI format for the particular bandwidth part after the number of padding bits is applied is equal to a common DCI size.
  • the processing circuitry is further configured to cause the network node to transmit, to the UE, DCI in the particular bandwidth part using the DCI format and the configured number of padding bits for the DCI format.
  • a method performed by a radio node (e.g., in a New Radio (NR) network) for DCI size alignment comprises determining a DCI format 4_2 monitored in a UE-specific search space, determining that either: (a) a total number of different DCI sizes configured to monitor is more than a first threshold (e.g., 4) for a respective cell or (b) a total number of different DCI sizes with Cell Radio Network Temporary Identifier (C-RNTI) or Group Radio Network Temporary Identifier (G-RNTI) configured to monitor is more than a second threshold (e.g., 3) for the respective cell, and responsive thereto performing one or more of the following: determining whether a number of information bits in DCI format 0_l is less than a payload size of the DCI format 4_2 for scheduling the same serving cell, adding a number of zero padding bits for the DCI format 0_l until the payload size of the DCI format 0_l equals the payload size of
  • Figure 1 is an illustration of the use case and solutions 2A and 2B discussed in 3GPP;
  • Figure 2 illustrates one example of a cellular communications system according to some embodiments of the present disclosure
  • Figure 3 illustrates an example of the padding, for the case where the common size equals that of the largest unicast/PTP DCI;
  • Figure 4 is a flow chart that illustrates the operation of a radio node in accordance with an embodiment of the present disclosure
  • Figure 5 is a schematic block diagram of a radio access node according to some embodiments of the present disclosure.
  • Figure 6 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node of Figure 5 according to some embodiments of the present disclosure
  • Figure 7 is a schematic block diagram of the radio access node of Figure 5 according to some other embodiments of the present disclosure
  • Figure 8 is a schematic block diagram of a wireless communication device (e.g., a User Equipment device (UE)) according to some embodiments of the present disclosure
  • UE User Equipment device
  • Figure 9 is a schematic block diagram of the wireless communication device of Figure 8 according to some other embodiments of the present disclosure.
  • Figure 10 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments of the present disclosure
  • Figure 11 is a generalized block diagram of a host computer communicating via a base station with a UE over a partially wireless connection in accordance with some embodiments of the present disclosure
  • Figure 12 is a flowchart illustrating a method implemented in a communication system in accordance with one embodiment of the present disclosure
  • Figure 13 is a flowchart illustrating a method implemented in a communication system in accordance with one embodiment of the present disclosure
  • Figure 14 is a flowchart illustrating a method implemented in a communication system in accordance with one embodiment of the present disclosure
  • Figure 15 is a flowchart illustrating a method implemented in a communication system in accordance with one embodiment of the present disclosure.
  • Figure 16 illustrate the operation of a base station and a UE in accordance with at least some of the embodiments described herein.
  • Radio Node As used herein, a "radio node” is either a radio access node or a wireless communication device.
  • Radio Access Node As used herein, a “radio access node” or “radio network node” or “radio access network node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals.
  • RAN Radio Access Network
  • a radio access node examples include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.
  • a base station e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B
  • a "core network node” is any type of node in a core network or any node that implements a core network function.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like.
  • MME Mobility Management Entity
  • P-GW Packet Data Network Gateway
  • SCEF Service Capability Exposure Function
  • HSS Home Subscriber Server
  • a core network node examples include a node implementing an Access and Mobility Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.
  • AMF Access and Mobility Function
  • UPF User Plane Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • NSSF Network Slice Selection Function
  • NEF Network Exposure Function
  • NRF Network Exposure Function
  • NRF Network Exposure Function
  • PCF Policy Control Function
  • UDM Unified Data Management
  • a "communication device” is any type of device that has access to an access network.
  • Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC).
  • the communication device may be a portable, hand-held, computer-comprised, or vehiclemounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.
  • One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network).
  • a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (loT) device.
  • UE User Equipment
  • MTC Machine Type Communication
  • LoT Internet of Things
  • Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC.
  • the wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection.
  • Network Node As used herein, a "network node” is any node that is either part of the RAN or the core network of a cellular communications network/system.
  • a common drawback with solution 2A and solution 2B is that it is not possible to maintain the requirement that a UE can only perform blind decoding of up to '3+1' Downlink Control Information (DCI) sizes per cell (4 DCI in total, among which 3 are Cell Radio Network Temporary Identifier (C-RNTI_- based).
  • DCI Downlink Control Information
  • C-RNTI_- based Cell Radio Network Temporary Identifier
  • the UE would thus need to Blind Decode '4+1' different DCI sizes for C-RNTI Physical Downlink Control Channel (PDCCH) and Group Radio Network Temporary Identifier (G-RNTI) PDCCH in order to receive both unicast and multicast PDCCHs. This increases the complexity of the UE, which is undesirable.
  • PDCCH Physical Downlink Control Channel
  • G-RNTI Group Radio Network Temporary Identifier
  • a related drawback of solutions 2A and 2B is that, even if legacy unicast DCI is not reused and new DCI formats are defined, there is still a "default" Bandwidth Part (BWP) size dependency on the DCI size due to the Frequency Domain Resource
  • FDRA FDRA Assignment
  • the DCI size of the multicast BWP and all unicast BWPs need to be aligned, which complicates the solution and may introduce a sensitivity to the case where a new BWP is added that is larger than the pre-existing BWPs.
  • each UE is Radio Resource Control (RRC) configured with a number of padding bits that are added to the DCI bits of the configured DCI format to make sure that the conditions for the completion of DCI size alignment are met: (a) the total number of DCI sizes configured to monitor by the UE does not exceed 4 in the cell and (b) the total number of DCI sizes with C-RNTI for Point-to-Point (PTP) and Point-to- Multipoint (PTM) configured to monitor by the UE is at most 3 in the cell.
  • RRC Radio Resource Control
  • This number may be adjusted so that the transmitted DCI size of all unicast PDCCH DCIs from all UE in MBS group are the same, also when these DCIs are used on BWPs of different size.
  • the number of padding bits may be adjusted so that the transmitted DCI size of the multicast PDCCH DCIs is the same as that of the transmitted unicast PDCCH DCI.
  • all UEs may Blind Decode both unicast and multicast PDCCHs with the same DCI size and can thereby keep the number of Blind Decodes the same as for receiving only unicast or only multicast.
  • This number of bits may be different for different BWP sizes, so that transmitted unicast and/or multicast DCI size is independent of BWP size 3.
  • the number of padding bits may be different for multicast and unicast, so that the transmitted DCI size of unicast and multicast may be the same on all relevant BWPs, also when the amount of information bits are different.
  • Downlink (DL) and uplink (UL) DCI sizes may be aligned using padding bits, allowing for BD with the same size
  • Embodiments of the present disclosure may provide a number of advantages over existing solutions. For example, with embodiments of the present disclosure, UEs may receive both unicast and multicast without increasing the number of Blind Decodes for the 2A and 2B solutions. As another example, embodiments of the present disclosure may allow the transmitted DCI of different unicast BWP sizes to be aligned, which otherwise would make it impossible to align the DCI size of multicast and unicast. As another example, embodiments of the present disclosure may also allow the transmitted DCI size of multicast and unicast to be aligned, which is necessary for avoiding an increase in Blind Decode when receiving both unicast and multicast. With this, the number of specified fields (i.e., without padding) may be different and optimized separately for unicast and multicast, while still allowing the transmitted DCI sizes to be aligned.
  • FIG. 2 illustrates one example of a cellular communications system 200 in which embodiments of the present disclosure may be implemented.
  • the cellular communications system 200 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC).
  • the RAN includes base stations 202-1 and 202-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC), controlling corresponding (macro) cells 204-1 and 204-2.
  • the base stations 202-1 and 202-2 are generally referred to herein collectively as base stations 202 and individually as base station 202.
  • the (macro) cells 204-1 and 204-2 are generally referred to herein collectively as (macro) cells 204 and individually as (macro) cell 204.
  • the RAN may also include a number of low power nodes 206-1 through 206-4 controlling corresponding small cells 208-1 through 208-4.
  • the low power nodes 206-1 through 206-4 can be small base stations (such as pico or femto base stations) or RRHs, or the like.
  • one or more of the small cells 208-1 through 208-4 may alternatively be provided by the base stations 202.
  • the low power nodes 206-1 through 206-4 are generally referred to herein collectively as low power nodes 206 and individually as low power node 206.
  • the cellular communications system 200 also includes a core network 210, which in the 5G System (5GS) is referred to as the 5GC.
  • the base stations 202 (and optionally the low power nodes 206) are connected to the core network 210.
  • the base stations 202 and the low power nodes 206 provide service to wireless communication devices 212-1 through 212-5 in the corresponding cells 204 and 208.
  • the wireless communication devices 212-1 through 212-5 are generally referred to herein collectively as wireless communication devices 212 and individually as wireless communication device 212.
  • the wireless communication devices 212 are oftentimes UEs and as such sometimes referred to herein as UEs 212, but the present disclosure is not limited thereto.
  • Embodiments of the present disclosure target the use case where UEs 212 receiving multicast are configured with different, but partly overlapping BWPs for unicast reception. Each BWP may be used by one or more UEs 212. Multicast is transmitted in the common overlap part of the different BWPs using a single group- common PDCCH scheduling a single group-common PDSCH, see Figure 1.
  • the UE 212 is configured with different BWPs for unicast and multicast (e.g., as in Solution 2A discussed in 3GPP)
  • at least one unicast PDCCH is configured on the unicast BWP and at least one multicast PDCCH is configured on the multicast BWP.
  • At least one unicast PDCCH and at least one multicast PDCCH are configured on the same BWP.
  • each DCI may be extended with one or more padding bits.
  • the number of padding bits may be RRC configured for each relevant DCI, so that a UE 212 knows explicitly from the RRC configuration how many padding bits, if any, to apply for a given DCI.
  • the set of padding bits is either an additional, optional field in the DCI format description (i.e., is part of the DCI format) or is appended to the DCI bits (i.e., padding bits are then not part of the DCI format as such). For the functionality of embodiments of the present disclosure, this distinction does not matter. In the remainder of the description, it is however assumed that the padding bits are part of the DCI format, without restricting the use to this case only.
  • the RRC configuration may include one optional parameter introducing a new optional DCI field which indicates the number of padding bits in the DCI that are introduced in the transmitted DCI over and above the number of bits given by the specified DCI format without such padding.
  • this parameter is set to k bits, the transmitted DCI or the PDCCH will therefore include k padding bits.
  • k may be zero.
  • the PDCCH may be associated with, e.g., DCI format l_0 or 1_1, which both have a defined number of bits that depends on the size of the associated BWP.
  • the parameter is set with value k
  • the actually used DCI size will then be k bits larger.
  • the padding bits may, e.g., be added at the end of the DCI, but any other defined way will work, as long as the padding bits are introduced in a way that is known for the UE 212, e.g. via standardization. From the RRC configuration, the UE 212 will then know, explicitly or implicitly, the DCI size, including any padding bits.
  • This way of adjusting the DCI size may be used to align PDCCH DCIs of different BWPs.
  • the specified DCI format may have a size that is dependent on the BWP size.
  • the sizes of the transmitted DCIs may be aligned to a common size.
  • This common size needs to be at least the size of the unicast DCI (without padding) of the largest BWP with UEs 212 to receive the PTM transmission, or to any other larger size up to the DCI size corresponding to the full carrier bandwidth (BW).
  • BW carrier bandwidth
  • the described functionality may be applied in a type 2A scenario where the DCI size of the multicast PDCCH, configured on the multicast BWP, may be identical to the DCI size of the unicast PDCCH configured on the unicast BWP. Since all unicast PDCCH DCIs can be made to have the same size, via such padding, this means the DCI size of both multicast PDCCH and unicast PDCCH can be identical for all UEs, irrespective of the unicast BWP of a particular UE.
  • Each UE 212 can therefore Blind Decode multicast and unicast PDCCHs with the same DCI size, thereby avoiding an increase in Blind Decode, compared to only the number of blind decodes corresponding to BD either unicast or multicast PDCCH.
  • the DCI sizes of the multicast PDCCH and the unicast PDCCH, configured on the same unicast BWP may be made identical. Since all unicast PDCCH DCIs can also be made to have the same size then this applies to all UEs.
  • each UE 212 can therefore Blind Decode multicast and unicast PDCCHs with the same DCI size, thereby avoiding an increase in Blind Decode, compared to only the number of blind decodes corresponding to BD either unicast or multicast PDCCH.
  • the sizes of DCI formats for unicast Downlink (DL) and unicast Uplink (UL) may be aligned using the same padding mechanism, as described above.
  • a DL DCI with nl DCI bits and an UL DCI with n2 DCI bits may then be aligned to a common DCI size of n bits by using kl padding bits for the DL DCI and k2 padding bits for the UL DCI.
  • the RRC configured padding mechanism may be used to ensure that the multicast DCI sizes of different BWPs are always different.
  • the unicast and multicast DCI sizes may here typically be identical within o e. BWP, to minimize the amount of BDs.
  • padding is used to ensure different multicast DCI sizes across any pair of BWPs. This allows for the use of multiple BWP-specific PDCCHs for multicast, each received by a sub-group of all UEs and used to schedule a single group-common PDSCH, using the same G-RNTI for all PDCCHs and the group-common PDSCH. For each BWP the unicast and multicast DCI sizes may be the same, to minimize BD.
  • the DCI size may depend on the size of the BWP.
  • this DCI difference may in many cases naturally occur but is not guaranteed. If, e.g., the relative difference in BWP size is too limited, two different BWPs may have the same DCI size. When needed, additional padding may therefore be required to ensure that a different DCI size across BWPs is guaranteed, for cases where this is desirable.
  • UEs in one BWP may only receive the PDCCH targeted for this BWP, when the UE BDs PDCCHs with this target size. PDCCHs from other BWPs will then not be detected when the UE uses a BD DCI size matching this targeted DCI.
  • Figure 16 illustrate the operation of a base station 202 and a UE 212 in accordance with at least some of the embodiments described above. These embodiments are fully described above, and Figure 16 is provided as merely an illustration of at least some of the embodiments already described above.
  • the base station 202 e.g., gNB
  • the information may be transmitted to the UE 212 using RRC signaling.
  • the number of padding bits configured for the DCI format for the particular BWP is such that a total DCI size for the DCI format for the particular BWP after the number of padding bits is applied is equal to a common DCI size. Note that while the configuration of a number of padding bits for only one DCI format for one particular BWP is described here, as described above, the UE 212 may be configured with a number of padding bits for each of more than one DCI format and further for more than one BWP.
  • the number of padding bits is such that the DCI size for the DCI format for the particular BWP is a common DCI.
  • the common DCI size is a common DCI size for multicast DCIs configured on a multicast BWP and unicast DCIs configured on a unicast BWP (e.g., in the case of the type 2A scenario).
  • the DCI format is either a multicast DCI format or a unicast DCI format
  • the common DCI size is a common DCI size for multicast DCIs configured on a multicast BWP and unicast DCIs configured on a unicast BWP (e.g., in the case of the type 2A scenario).
  • the common DCI size is a common DCI size for multicast DCIs and unicast DCIs configured on the same unicast bandwidth part (e.g., in the case of the type 2B scenario).
  • the DCI format is either a multicast DCI format or a unicast DCI format
  • the common DCI size is a common DCI size for multicast DCIs and unicast DCIs configured on the same unicast bandwidth part (e.g., in the case of the type 2B scenario).
  • the common DCI size is a common DCI size for multicast DCIs and unicast DCIs for all UEs in a MBS group.
  • the common DCI size is a common DCI size for multicast DCIs and unicast DCIs for all UEs in a MBS group across different bandwidth parts having different bandwidth part sizes.
  • the common DCI size is a common DCI size for multicast DCIs and unicast DCIs.
  • the common DCI size is a common DCI size for DCIs on different bandwidth parts having different bandwidth part sizes.
  • the common DCI size is a common DCI size for DCI formats for unicast downlink and unicast uplink.
  • the common DCI size is for unicast and multicast DCIs within the particular bandwidth part, and is such that multicast DCI sizes in different bandwidth parts are always different.
  • the common DCI size is for unicast and multicast DCIs within the particular bandwidth part, and is such that multicast DCI sizes across any pair of bandwidth parts are different.
  • the base station 202 may then transmit, to the UE, a DCI in the particular BWP using the DCI format and the total DCI size (e.g., by adding the configured number of padding bits to the DCI), as described above (step 1602).
  • the UE 212 performs blind decoding in the particular bandwidth part for the DCI format using the total DCI size (which includes the configured number of padding bits) (step 1604).
  • Step 400 In one embodiment, first, the radio node (e.g., UE 212 or base station 202) determines DCI format 4_2 monitored in a UE-specific search space (according to clause 7.3.1.5.3 of 3GPP TS 38.212 V17.0.0, which is reproduced below in an excerpt from TS 38.212), which can be introduced either as part of existing steps in the procedure (for example in step 2A) or as a new step (for example called Step 2-B) following step 2A within the DCI size alignment procedure of Section 7.3.1.0 in TS 38.212, which is also reproduced below in an excerpt from TS 38.212.
  • a UE-specific search space according to clause 7.3.1.5.3 of 3GPP TS 38.212 V17.0.0, which is reproduced below in an excerpt from TS 38.212
  • the radio node determines if the total number of different DCI sizes configured to monitor is more than 4 for the cell after applying steps 0-3 of the DCI size alignment procedure of Section 7.3.1.0 in TS 38.212, or if the total number of different DCI sizes with C-RNTI or G-RNTI configured to monitor is more than 3 for the cell after applying steps 0-3 of the DCI size alignment procedure of Section 7.3.1.0 in TS 38.212 (step 402). If so, then the following steps are introduced as part of the alignment procedure in step 4, for example as a new step 4-D within the DCI size alignment procedure of Section 7.3.1.0 in TS 38.212:
  • Steps 404 and 406 If the number of information bits in the DCI format 0_l is less than the payload size of the DCI format 4_2 for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0_l until the pay load size equals that of the DCI format 4_2.
  • Steps 408 and 410 If the number of information bits in the DCI format 1_1 is less than the payload size of the DCI format 4_2 for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 1_1 until the pay load size equals that of the DCI format 4_2.
  • the radio node then utilizes the determined DCI formats including any added zero padding bits (not shown). For example, if the radio node is the UE 212, then the UE 212 utilizes the determined DCI formats including any added zero padding bits when monitoring for DCI. As another example, if the radio node is the base station 202, then the base station 202 utilizes the determined DCI formats including any added zero padding bits when transmitting DCI.
  • a DCI transports downlink control information for one or more cells with one RNTI.
  • the following coding steps can be identified:
  • Each field is mapped in the order in which it appears in the description, including the zero-padding bit(s), if any, with the first field mapped to the lowest order information bit a 0 and each successive field mapped to higher order information bits.
  • the most significant bit of each field is mapped to the lowest order information bit for that field, e.g. the most significant bit of the first field is mapped to a 0 .
  • each DCI format is determined by the configuration of the corresponding active bandwidth part of the scheduled cell and shall be adjusted as described in clause 7.3.1.0 if necessary.
  • pdsch-HARQ-ACK-CodebookList-r!6 If a UE is configmed with pdsch-HARQ-ACK-CodebookList-r!6, pdsch-HARQ-ACK-Codebook is replaced by the relevant entry in pdsch-HARQ-ACK-CodebookList-r!6 in this clause.
  • Step 0 - Determine DCI format 0 0 monitored in a common search space according to clause 7.3.1.1.1 where initial UL bandwidth part.
  • DCI format 0 0 is monitored in common search space and if the number of information bits in the DCI format 0 0 prior to padding is less than the payload size of the DCI format 1 0 monitored in common search space for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format
  • the bitwidth of the frequency domain resource assignment field in the DCI format 0 0 is reduced by truncating the first few most significant bits such that the size of DCI format 0 0 equals the size of the DCI format 1 0.
  • PU SCH For a UE configured with supplementaryUplink in ServingCellConflg in a cell, if PU SCH is configured to be transmitted on both the SUL and the non-SUL of the cell and if the number of information bits in DCI format 0 0 in UE-specific search space for the SUL is not equal to the number of information bits in DCI format 0 0 in UE-specific search space for the non-SUL, a number of zero padding bits are generated for the smaller DCI format 0 0 until the payload size equals that of the larger DCI format 0 0.
  • DCI format 0 0 is monitored in UE-specific search space and if the number of information bits in the DCI format 0 0 prior to padding is less than the payload size of the DCI format 1 0 monitored in UE-specific search space for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0 0 until the payload size equals that of the DCI format 1 0.
  • DCI format 1 0 is monitored in UE-specific search space and if the number of information bits in the DCI format 1 0 prior to padding is less than the payload size of the DCI format 0 0 monitored in UE-specific search space for scheduling the same serving cell, zeros shall be appended to the DCI format 1 0 until the pay load size equals that of the DCI format 0 0
  • PU SCH For a UE configured with supplementaryUplink in ServingCellConflg in a cell, if PU SCH is configured to be transmitted on both the SUL and the non-SUL of the cell and if the number of information bits in format 0 1 for the SUL is not equal to the number of information bits in format 0 1 for the non-SUL, zeros shall be appended to smaller format 0 1 until the payload size equals that of the larger format 0 1.
  • DCI format 0 1 monitored in a UE-specific search space If the size of DCI format 0 1 monitored in a UE-specific search space equals that of a DCI format 0 0/1 0 monitored in another UE-specific search space, one bit of zero padding shall be appended to DCI format 0 1.
  • DCI format 1 1 monitored in a UE-specific search space If the size of DCI format 1 1 monitored in a UE-specific search space equals that of a DCI format 0 0/1 0 monitored in another UE-specific search space, one bit of zero padding shall be appended to DCI format 1 1.
  • Step 2A - Determine DCI format 0 2 monitored in a UE-specific search space according to clause 7.3.1.1.3.
  • PU SCH For a UE configured with supplementaryUplink in ServingCellConflg in a cell, if PU SCH is configured to be transmitted on both the SUL and the non-SUL of the cell and if the number of information bits in format 0 2 for the SUL is not equal to the number of information bits in format 0 2 for the non-SUL, zeros shall be appended to smaller format 0 2 until the pay load size equals that of the larger format 0 2.
  • Step 3
  • the total number of different DCI sizes configmed to monitor is no more than 4 for the cell
  • the total number of different DCI sizes with C-RNTI configmed to monitor is no more than 3 for the cell
  • the bitwidth of the frequency domain resomce assignment field in the DCI format 0 0 is reduced by truncating the first few most significant bits such that the size of DCI format 0 0 monitored in a UE-specific search space equals the size of the DCI format 1 0 monitored in a UE-specific search space.
  • Step 4C - If the total number of different DCI sizes configured to monitor is more than 4 for the cell after applying the above steps, or if the total number of different DCI sizes with C-RNTI configured to monitor is more than 3 for the cell after applying the above steps
  • the UE is not expected to handle a configmation that, after applying the above steps, results in
  • the total number of different DCI sizes configmed to monitor is more than 4 for the cell;
  • the total number of different DCI sizes with C-RNTI configmed to monitor is more than 3 for the cell;
  • the size of DCI format 0 0 in a UE-specific search space is equal to DCI format 0 1 in another UE-specific search space;
  • the size of DCI format 1 0 in a UE-specific search space is equal to DCI format 1 1 in another UE-specific search space;
  • the size of DCI format 0 0 in a UE-specific search space is equal to DCI format 0 2 in another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 0 0 and 0 2 are mapped to the same resource;
  • the size of DCI format 1 0 in a UE-specific search space is equal to DCI format 1 2 in another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 1 0 and 1 2 are mapped to the same resource;
  • the size of DCI format 0 1 in a UE-specific search space is equal to DCI format 0 2 in the same or another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 0 1 and 0 2 me mapped to the same resource; or
  • the size of DCI format 1 1 in a UE-specific search space is equal to DCI format 1 2 in the same or another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 1 1 and 1 2 me mapped to the same resource.
  • DCI format 4 2 is used for the scheduling of PDSCH in DL cell.
  • the following information is transmitted by means of the DCI format 4 2 with CRC scrambled by G-RNTI configmed by G-RNTI-Conflg or G-CS-RNTI:
  • N RB CFR is the size of the common frequency resomce as configmed by higher layer parameter locationAndBandwidth- Multicast'.
  • N RBG bits if only resource allocation type 0 is configured, where N RBG is defined in Clause 5.1.2.2.1 of [6, TS38.214],
  • the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1.
  • the N RBG LSBs provide the resource allocation as defined in Clause 5.1.2.2.1 of [6, TS 38.214],
  • the LSBs provide the resource allocation as defined in Clause 5.1.2.2.2 of [6, TS 38.214]
  • Time domain resource assignment - 0, 1, 2, 3, or 4 bits as defined in Clause 5.1.2.1 of [6, TS 38.214].
  • the bitwidth for this field is determined as [log 2 (/)] bits, where I is the number of entries in the higher layer parameter pdsch-TimeDomainAllocationList if the higher layer parameter is configured; otherwise I is the number of entries in the default table.
  • Rate matching indicator - 0, 1, or 2 bits according to higher layer parameters rateMatchPatternGroupl and rateMatchPatternGroup2 in PDSCH-Config-Multicast, where the MSB is used to indicate rateMatchPatternGroupl and the LSB is used to indicate rateMatchPatternGroup2 when there are two groups.
  • the number of serving cells is determined within a PUCCH group.
  • pdsch-HARQ-ACK-Codebook is replaced by pdsch-HARQ- ACK-Codebook-secondaryPUCCHgroup-rl6 if present for the secondary PUCCH group.
  • - PDSCH-to-HARQ feedback timing indicator 0, 1, 2, or 3 bits as defined in Clause 9.2.3 of [5, TS 38.213] .
  • the bitwidth for this field is determined as [log 2 (/)] bits, where I is the number of entries in the higher layer parameter dl-DataToUL-ACK in PUCCH-Conflg-Multicastl if configmed or PUCCH-Conflg-Multicast2 if configured; otherwise, I is the number of entries in the higher layer parameter dl-DataToUL-ACK in PUCCH- Config.
  • Antenna port(s) - 4 5, or 6 bits as defined by Tables 7.3.1.2.2-1/2/3/4, where the number of CDM groups without data of values 1, 2, and 3 refers to CDM groups ⁇ 0 ⁇ , ⁇ 0,1 ⁇ , and ⁇ 0, 1,2 ⁇ respectively.
  • the antenna ports ⁇ p 0 , ... , Pv-i shall be determined according to the ordering of DMRS port(s) given by Tables 7.3.1.2.2- 1/2/3/4.
  • bitwidth of this field equals max ⁇ x A , x B ], where x A is the "Antenna ports” bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeA and x B is the "Antenna ports” bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeB.
  • x A is the "Antenna ports” bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeA
  • x B is the "Antenna ports” bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeB.
  • FIG. 5 is a schematic block diagram of a radio access node 500 according to some embodiments of the present disclosure.
  • the radio access node 500 may be, for example, a base station 202 or 206 or a network node that implements all or part of the functionality of the base station 202 or gNB described herein.
  • the radio access node 500 includes a control system 502 that includes one or more processors 504 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 506, and a network interface 508.
  • the one or more processors 504 are also referred to herein as processing circuitry.
  • the radio access node 500 may include one or more radio units 510 that each includes one or more transmitters 512 and one or more receivers 514 coupled to one or more antennas 516.
  • the radio units 510 may be referred to or be part of radio interface circuitry.
  • the radio unit(s) 510 is external to the control system 502 and connected to the control system 502 via, e.g., a wired connection (e.g., an optical cable).
  • the radio unit(s) 510 and potentially the antenna(s) 516 are integrated together with the control system 502.
  • the one or more processors 504 operate to provide one or more functions of a radio access node 500 as described herein.
  • the function(s) are implemented in software that is stored, e.g., in the memory 506 and executed by the one or more processors 504.
  • FIG. 6 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node 500 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes.
  • a "virtualized" radio access node is an implementation of the radio access node 500 in which at least a portion of the functionality of the radio access node 500 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)).
  • the radio access node 500 may include the control system 502 and/or the one or more radio units 510, as described above.
  • the control system 502 may be connected to the radio unit(s) 510 via, for example, an optical cable or the like.
  • the radio access node 500 includes one or more processing nodes 600 coupled to or included as part of a network(s) 602.
  • Each processing node 600 includes one or more processors 604 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 606, and a network interface 608.
  • processors 604 e.g., CPUs, ASICs, FPGAs, and/or the like
  • memory 606 e.g., RAM, ROM, and/or the like
  • functions 610 of the radio access node 500 described herein are implemented at the one or more processing nodes 600 or distributed across the one or more processing nodes 600 and the control system 502 and/or the radio unit(s) 510 in any desired manner.
  • some or all of the functions 610 of the radio access node 500 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 600.
  • additional signaling or communication between the processing node(s) 600 and the control system 502 is used in order to carry out at least some of the desired functions 610.
  • the control system 502 may not be included, in which case the radio unit(s) 510 communicate directly with the processing node(s) 600 via an appropriate network interface(s).
  • a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of radio access node 500 or a node (e.g., a processing node 600) implementing one or more of the functions 610 of the radio access node 500 in a virtual environment according to any of the embodiments described herein is provided.
  • a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
  • FIG 7 is a schematic block diagram of the radio access node 500 according to some other embodiments of the present disclosure.
  • the radio access node 500 includes one or more modules 700, each of which is implemented in software.
  • the module(s) 700 provide the functionality of the radio access node 500 described herein. This discussion is equally applicable to the processing node 600 of Figure 6 where the modules 700 may be implemented at one of the processing nodes 600 or distributed across multiple processing nodes 600 and/or distributed across the processing node(s) 600 and the control system 502.
  • FIG. 8 is a schematic block diagram of a wireless communication device 800 according to some embodiments of the present disclosure.
  • the wireless communication device 800 includes one or more processors 802 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 804, and one or more transceivers 806 each including one or more transmitters 808 and one or more receivers 810 coupled to one or more antennas 812.
  • the transceiver(s) 806 includes radio-front end circuitry connected to the antenna(s) 812 that is configured to condition signals communicated between the antenna(s) 812 and the processor(s) 802, as will be appreciated by on of ordinary skill in the art.
  • the processors 802 are also referred to herein as processing circuitry.
  • the transceivers 806 are also referred to herein as radio circuitry.
  • the functionality of the wireless communication device 800 described above may be fully or partially implemented in software that is, e.g., stored in the memory 804 and executed by the processor(s) 802.
  • the wireless communication device 800 may include additional components not illustrated in Figure 8 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 800 and/or allowing output of information from the wireless communication device 800), a power supply (e.g., a battery and associated power circuitry), etc.
  • a power supply e.g., a battery and associated power circuitry
  • a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device 800 according to any of the embodiments described herein is provided.
  • a carrier comprising the aforementioned computer program product is provided.
  • the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
  • FIG. 9 is a schematic block diagram of the wireless communication device 800 according to some other embodiments of the present disclosure.
  • the wireless communication device 800 includes one or more modules 900, each of which is implemented in software.
  • the module(s) 900 provide the functionality of the wireless communication device 800 described herein.
  • a communication system includes a telecommunication network 1000, such as a 3GPP- type cellular network, which comprises an access network 1002, such as a RAN, and a core network 1004.
  • the access network 1002 comprises a plurality of base stations 1006A, 1006B, 1006C, such as Node Bs, eNBs, gNBs, or other types of wireless Access Points (APs), each defining a corresponding coverage area 1008A, 1008B, 1008C.
  • Each base station 1006A, 1006B, 1006C is connectable to the core network 1004 over a wired or wireless connection 1010.
  • a first UE 1012 located in coverage area 1008C is configured to wirelessly connect to, or be paged by, the corresponding base station 1006C.
  • a second UE 1014 in coverage area 1008A is wirelessly connectable to the corresponding base station 1006A. While a plurality of UEs 1012, 1014 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1006.
  • the telecommunication network 1000 is itself connected to a host computer 1016, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm.
  • the host computer 1016 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections 1018 and 1020 between the telecommunication network 1000 and the host computer 1016 may extend directly from the core network 1004 to the host computer 1016 or may go via an optional intermediate network 1022.
  • the intermediate network 1022 may be one of, or a combination of more than one of, a public, private, or hosted network; the intermediate network 1022, if any, may be a backbone network or the Internet; in particular, the intermediate network 1022 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 10 as a whole enables connectivity between the connected UEs 1012, 1014 and the host computer 1016.
  • the connectivity may be described as an Over-the-Top (OTT) connection 1024.
  • the host computer 1016 and the connected UEs 1012, 1014 are configured to communicate data and/or signaling via the OTT connection 1024, using the access network 1002, the core network 1004, any intermediate network 1022, and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 1024 may be transparent in the sense that the participating communication devices through which the OTT connection 1024 passes are unaware of routing of uplink and downlink communications.
  • the base station 1006 may not or need not be informed about the past routing of an incoming downlink communication with data originating from the host computer 1016 to be forwarded (e.g., handed over) to a connected UE 1012. Similarly, the base station 1006 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1012 towards the host computer 1016.
  • a host computer 1102 comprises hardware 1104 including a communication interface 1106 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 1100.
  • the host computer 1102 further comprises processing circuitry 1108, which may have storage and/or processing capabilities.
  • the processing circuitry 1108 may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.
  • the host computer 1102 further comprises software 1110, which is stored in or accessible by the host computer 1102 and executable by the processing circuitry 1108.
  • the software 1110 includes a host application 1112.
  • the host application 1112 may be operable to provide a service to a remote user, such as a UE 1114 connecting via an OTT connection 1116 terminating at the UE 1114 and the host computer 1102.
  • the host application 1112 may provide user data which is transmitted using the OTT connection 1116.
  • the communication system 1100 further includes a base station 1118 provided in a telecommunication system and comprising hardware 1120 enabling it to communicate with the host computer 1102 and with the UE 1114.
  • the hardware 1120 may include a communication interface 1122 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 1100, as well as a radio interface 1124 for setting up and maintaining at least a wireless connection 1126 with the UE 1114 located in a coverage area (not shown in Figure 11) served by the base station 1118.
  • the communication interface 1122 may be configured to facilitate a connection 1128 to the host computer 1102.
  • connection 1128 may be direct or it may pass through a core network (not shown in Figure 11) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • the hardware 1120 of the base station 1118 further includes processing circuitry 1130, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.
  • the base station 1118 further has software 1132 stored internally or accessible via an external connection.
  • the communication system 1100 further includes the UE 1114 already referred to.
  • the UE's 1114 hardware 1134 may include a radio interface 1136 configured to set up and maintain a wireless connection 1126 with a base station serving a coverage area in which the UE 1114 is currently located.
  • the hardware 1134 of the UE 1114 further includes processing circuitry 1138, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.
  • the UE 1114 further comprises software 1140, which is stored in or accessible by the UE 1114 and executable by the processing circuitry 1138.
  • the software 1140 includes a client application 1142.
  • the client application 1142 may be operable to provide a service to a human or non-human user via the UE 1114, with the support of the host computer 1102.
  • the executing host application 1112 may communicate with the executing client application 1142 via the OTT connection 1116 terminating at the UE 1114 and the host computer 1102.
  • the client application 1142 may receive request data from the host application 1112 and provide user data in response to the request data.
  • the OTT connection 1116 may transfer both the request data and the user data.
  • the client application 1142 may interact with the user to generate the user data that it provides.
  • the host computer 1102, the base station 1118, and the UE 1114 illustrated in Figure 11 may be similar or identical to the host computer 1016, one of the base stations 1006A, 1006B, 1006C, and one of the UEs 1012, 1014 of Figure 10, respectively.
  • the inner workings of these entities may be as shown in Figure 11 and independently, the surrounding network topology may be that of Figure 10.
  • the OTT connection 1116 has been drawn abstractly to illustrate the communication between the host computer 1102 and the UE 1114 via the base station 1118 without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the network infrastructure may determine the routing, which may be configured to hide from the UE 1114 or from the service provider operating the host computer 1102, or both. While the OTT connection 1116 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 1126 between the UE 1114 and the base station 1118 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1114 using the OTT connection 1116, in which the wireless connection 1126 forms the last segment.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 1116 may be implemented in the software 1110 and the hardware 1104 of the host computer 1102 or in the software 1140 and the hardware 1134 of the UE 1114, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 1116 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which the software 1110, 1140 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1116 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 1118, and it may be unknown or imperceptible to the base station 1118.
  • measurements may involve proprietary UE signaling facilitating the host computer's 1102 measurements of throughput, propagation times, latency, and the like.
  • the measurements may be implemented in that the software 1110 and 1140 causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection 1116 while it monitors propagation times, errors, etc.
  • FIG. 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section.
  • the host computer provides user data.
  • sub-step 1202 (which may be optional) of step 1200, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 1206 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1208 the UE executes a client application associated with the host application executed by the host computer.
  • FIG. 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1304 (which may be optional), the UE receives the user data carried in the transmission.
  • FIG 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section.
  • the UE receives input data provided by the host computer. Additionally or alternatively, in step 1402, the UE provides user data.
  • sub-step 1404 (which may be optional) of step 1400, the UE provides the user data by executing a client application.
  • sub-step 1406 (which may be optional) of step 1402
  • the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in sub-step 1408 (which may be optional), transmission of the user data to the host computer.
  • step 1410 of the method the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG. 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 1504 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

Landscapes

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

Abstract

Sont divulgués des systèmes et procédés associés à l'alignement de taille d'informations de commande de liaison descendante (DCI). Dans un mode de réalisation, un procédé réalisé par un équipement utilisateur (UE) configuré selon une première partie de bande passante pour une réception en monodiffusion et une seconde partie de bande passante pour une réception en multidiffusion comprend la réception, en provenance d'un nœud de réseau, d'informations qui configurent l'UE selon un certain nombre de bits de remplissage pour un format de DCI configuré pour une partie de bande passante particulière, le nombre de bits de remplissage étant tel qu'une taille de DCI totale du format de DCI pour la partie de bande passante particulière une fois le nombre de bits de remplissage appliqué est égale à une taille de DCI commune. Le procédé comprend en outre la réalisation d'un décodage aveugle pour la réception d'une DCI du format de DCI dans la partie de bande passante particulière sur la base de la taille de DCI totale pour le format de DCI pour la partie de bande passante particulière.
PCT/SE2023/050119 2022-02-14 2023-02-14 Alignement de taille de dci pour multidiffusion et monodiffusion sur des parties de bande passante qui se chevauchent WO2023153997A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2022/076242 2022-02-14
CN2022076242 2022-02-14

Publications (1)

Publication Number Publication Date
WO2023153997A1 true WO2023153997A1 (fr) 2023-08-17

Family

ID=87564756

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050119 WO2023153997A1 (fr) 2022-02-14 2023-02-14 Alignement de taille de dci pour multidiffusion et monodiffusion sur des parties de bande passante qui se chevauchent

Country Status (1)

Country Link
WO (1) WO2023153997A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220039103A1 (en) * 2020-07-30 2022-02-03 Qualcomm Incorporated Multicast downlink control information configuration

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210045017A1 (en) * 2019-08-09 2021-02-11 Qualcomm Incorporated Multicast communications for radio resource control modes
WO2022027064A1 (fr) * 2020-07-30 2022-02-03 Qualcomm Incorporated Configuration d'informations de commande de liaison descendante de multidiffusion

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210045017A1 (en) * 2019-08-09 2021-02-11 Qualcomm Incorporated Multicast communications for radio resource control modes
WO2022027064A1 (fr) * 2020-07-30 2022-02-03 Qualcomm Incorporated Configuration d'informations de commande de liaison descendante de multidiffusion

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Mechanisms to support MBS group scheduling for RRC_CONNECTED UEs", 3GPP DRAFT; R1-2202396, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20220221 - 20220303, 14 February 2022 (2022-02-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052114813 *
NTT DOCOMO, INC.: "Discussion on group scheduling mechanism for RRC_CONNECTED UEs", 3GPP DRAFT; R1-2105720, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210510 - 20210527, 12 May 2021 (2021-05-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052011666 *
VIVO: "Remaining issues on DCI formats", 3GPP DRAFT; R1-1803830 REMAINING ISSUES ON DCI FORMATS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Sanya, China; 20180416 - 20180420, 15 April 2018 (2018-04-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051426125 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220039103A1 (en) * 2020-07-30 2022-02-03 Qualcomm Incorporated Multicast downlink control information configuration

Similar Documents

Publication Publication Date Title
US11695497B2 (en) Configurable DCI formatting indicator
US20230216626A1 (en) Pusch multiple trp reliability with ul tci indication
US20230171778A1 (en) Systems and methods related to sub-slot physical uplink control channel (pucch) repetitions
US12003338B2 (en) Systems and methods of HARQ codebook determination for multiple PUCCH
US20230132040A1 (en) Mixed signal dci and multi-dci for pdsch scheduling
EP4311346A2 (fr) Systèmes et procédés pour déterminer et indiquer des ports d'antenne avec un champ de port d'antenne configurable dans une dci
US20230127381A1 (en) Systems and methods for determining tci states for multiple transmission occasions
US20230300834A1 (en) Systems and methods of signaling time domain resource allocation for pdsch transmission
US20220361211A1 (en) Support of enhanced dynamic codebook with different dci formats
US20230299924A1 (en) Coreset enhancement for reduced bandwidth ues initial access
EP4014409A1 (fr) Détermination tbs pour schémas de transmission de pdsch multi-trp
US20240015748A1 (en) Systems and methods for pucch repetition
US20230397183A1 (en) Type-1 harq-ack codebook in pucch for sub-slot harq-ack
US20230224923A1 (en) ACTIVATION OF TWO OR MORE TCI STATES FOR ONE OR MORE CORESETs
US12127190B2 (en) Systems and methods for non-codebook based multi-TRP PUSCH
US20230412316A1 (en) Harq timing for dci scheduling multiple cells
WO2023153997A1 (fr) Alignement de taille de dci pour multidiffusion et monodiffusion sur des parties de bande passante qui se chevauchent
US20230021043A1 (en) HANDLING OVERLAPPING OF MULTIPLE PHYSICAL UPLINK SHARED CHANNELS (PUSCHs)
US20240064730A1 (en) Systems and Methods of Monitoring UL Cancelation Indications
US20240259163A1 (en) Transmission of harq-ack for multiple sps or multiple cgs for transmission alignment

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: 23753289

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE