Systems and methods for signaling

Abstract

A system and method for multiplexing one or more uplink messages. The system and method include receiving, by a wireless communication device, a transport block of a multicast and broadcast service (MBS) session on a physical downlink shared channel (PDSCH); determining, by the wireless communication device, overlap in the time domain between a PUCCH corresponding to the PDSCH and an uplink channel (e.g., a second PUCCH, a PUSCH, etc.); and / or transmitting, by the wireless communication device, another PUCCH in response to determining the overlap.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications and, more particularly, to systems and methods for multiplexing one or more uplink messages. Background Art

[0002] In wireless communication systems, the network configures physical uplink control channel (PUCCH) resources for UEs. The PUCCH resource configuration includes, for example, at least time domain resources (e.g., the number and location of PUCCH orthogonal frequency division multiplexing (OFDM) symbols), frequency domain resources (e.g., the number and location of PUCCH physical resource blocks (PRBs) or resource elements (REs)), and code domain resources (e.g., cyclic shifts or orthogonal cover codes). Summary of the Invention

[0003] The exemplary embodiments disclosed herein are intended to address issues related to one or more problems presented in the prior art, as well as to provide additional features that will become apparent when reference is made to the following detailed description in conjunction with the accompanying drawings. According to various embodiments, example systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and not limitation, and it will be apparent to those of ordinary skill in the art who read this disclosure that various modifications may be made to the disclosed embodiments while remaining within the scope of this disclosure.

[0004] In one aspect, the present disclosure relates to a method for multiplexing one or more uplink messages. In some embodiments, the method includes, by a wireless communication device (e.g., Figure 1 A UE 104 in a wireless communication system receives a transport block of a multicast and broadcast service (MBS) session on a physical downlink shared channel (PDSCH). In some embodiments, the method includes determining, by the wireless communication device, an overlap in the time domain between a PUCCH corresponding to the PDSCH and an uplink channel (e.g., a second PUCCH, a PUSCH, etc.). In some embodiments, the method includes transmitting, by the wireless communication device, another PUCCH in response to determining the overlap.

[0005] In another aspect, the present disclosure relates to a method for multiplexing one or more uplink messages. In some embodiments, the method includes receiving, by a wireless communication device, one or more transport blocks of one or more multicast and broadcast service (MBS) sessions on one or more physical downlink shared channels (PDSCHs). In some embodiments, the method includes determining, by the wireless communication device, a first overlap in the time domain between one or more first PUCCHs and a second uplink channel. In some embodiments, the method includes generating, by the wireless communication device, first information in response to determining the first overlap. In some embodiments, the method includes sending, by the wireless communication device, the first information on a second uplink channel.

[0006] In another aspect, the present disclosure relates to a method for multiplexing one or more uplink messages. In some embodiments, the method includes sending, by a wireless communication node, a transport block for a multicast and broadcast service (MBS) session on a physical downlink shared channel (PDSCH) to a wireless communication device. In some embodiments, the transport block causes the wireless communication device to determine an overlap in the time domain between a PUCCH corresponding to the PDSCH and an uplink channel, and / or, in response to determining the overlap, to send another PUCCH to the wireless communication node. In some embodiments, the method includes receiving, by the wireless communication node, the another PUCCH.

[0007] In another aspect, the present disclosure relates to a method for multiplexing one or more uplink messages. In some embodiments, the method includes sending, by a wireless communication node, one or more transport blocks of one or more multicast and broadcast service (MBS) sessions on one or more physical downlink shared channels (PDSCHs) to a wireless communication device. In some embodiments, the one or more transport blocks cause the wireless communication device to determine a first overlap in the time domain between one or more first PUCCHs and a second uplink channel, generate first information in response to determining the first overlap; and / or send the first information on the second uplink channel. In some embodiments, the method includes receiving, by the wireless communication node, the first information.

[0008] The above and other aspects and embodiments thereof are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Various exemplary embodiments of the present solution are described in detail below with reference to the accompanying drawings. The drawings are for illustrative purposes only and are intended only to depict exemplary embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be construed as limiting the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, the drawings are not necessarily drawn to scale.

[0010] Figure 1An example cellular communication network is illustrated in which the techniques disclosed herein may be implemented according to an embodiment of the present disclosure.

[0011] Figure 2 Illustrated is a block diagram of example base station and user equipment apparatus according to some embodiments of the present disclosure.

[0012] Figure 3 A block diagram illustrating an example PUCCH transmission according to some embodiments of the present disclosure is illustrated.

[0013] Figure 4 An example diagram illustrating the overlap of PUCCH and uplink transmissions according to some embodiments of the present disclosure is shown.

[0014] Figure 5 An example diagram of additionally generated first information bits according to some embodiments of the present disclosure is illustrated.

[0015] Figure 6 An example diagram illustrating the overlap of PUCCH and uplink transmissions according to some embodiments of the present disclosure is shown.

[0016] Figure 7 An example diagram illustrating the overlap of PUCCH and uplink transmissions according to some embodiments of the present disclosure is shown.

[0017] Figure 8 is a flow chart depicting a method for multiplexing one or more uplink messages according to some embodiments of the present disclosure.

[0018] Figure 9 is a flow chart depicting a method for multiplexing one or more uplink messages according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0019] Various example embodiments of the present solution are described below in conjunction with the accompanying drawings to enable those of ordinary skill in the art to make and use the present solution. It will be apparent to those of ordinary skill in the art that, after reading this disclosure, various changes or modifications can be made to the examples described herein without departing from the scope of the present solution. Therefore, the present solution is not limited to the example embodiments and applications described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein are merely example methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be modified while remaining within the scope of the present solution. Therefore, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or actions in an example order, and the present solution is not limited to the specific order or hierarchy presented unless otherwise expressly stated.

[0020] The following acronyms are used throughout this disclosure:

[0021] 3GPP Third Generation Partnership Project

[0022] 5G fifth-generation mobile network

[0023] 5G-AN 5G Access Network

[0024] 5G gNB Next Generation Node B

[0025] CCA Idle Channel Access

[0026] CCE Control Channel Element

[0027] CE Control Elements

[0028] CG configuration authorization

[0029] COT Channel Occupancy Time

[0030] DCI Downlink Control Information

[0031] DG Dynamic Authorization

[0032] DL Downlink or Downlink

[0033] eMBB Enhanced Mobile Broadband

[0034] eNB Evolved Node B

[0035] ETSI European Telecommunications Standards Institute

[0036] LBT Listen Before Talk / Listen Before Send

[0037] LTE Long Term Evolution

[0038] MAC Medium Access Control

[0039] MBMS Multimedia Broadcast Multicast Service

[0040] MBS Multicast and Broadcast Services

[0041] MSC Mobile Switching Center

[0042] NACK Negative Acknowledgement

[0043] NAS Non-Access Stratum

[0044] NR Next Generation RAN

[0045] OFDM Orthogonal Frequency Division Multiplexing

[0046] OFDMA Orthogonal Frequency Division Multiple Access

[0047] OSI Open Systems Interconnection

[0048] PDCP Packet Data Convergence Protocol

[0049] PDCCH Physical Downlink Control Channel

[0050] PDSCH Physical Downlink Shared Channel

[0051] PUCCH Physical Uplink Control Channel

[0052] PUSCH Physical Uplink Shared Channel

[0053] RAN Radio Access Network

[0054] RLC Radio Link Control

[0055] RNTI Radio Network Temporary Identifier

[0056] RRC Radio Resource Control

[0057] RV Redundancy Version

[0058] TB Transfer Block

[0059] UE User Equipment

[0060] UL Uplink or Uplink

[0061] In wireless communication systems (e.g. Figure 1 In the environment 100), a UE (eg, Figure 1 A UE 104 in a wireless communication system receives or is interested in receiving one or more multicast services, such as a Multicast and Broadcast Service (MBS) or a Multimedia Broadcast Multicast Service (MBMS). In other words, the UE receives or is interested in receiving data for one or more MBS sessions or MBMS sessions, where an MBS session represents a multicast service. When a receiver does not successfully decode data from a transmitter, the receiver sends a negative acknowledgement (NACK) message (sometimes referred to as an "aNACK message" or "NACK-only feedback") to the transmitter.

[0062] However, the transmission of a NACK-only message by a UE may cause the NACK-only message to overlap (e.g., coexist, coincide, intersect, etc.) with other transmissions (e.g., other NACK-only messages and / or other uplink transmissions) in the time domain. Therefore, a mechanism is needed to determine how to multiplex one or more uplink messages (e.g., NACK-only messages).

[0063] Thus, the systems and methods discussed herein provide a mechanism for multiplexing one or more uplink messages (eg, only NACK messages).

[0064] In the "first" example, as discussed in more detail below, when there is overlap between two PUCCHs in the time domain, another PUCCH is sent. In some embodiments, the two PUCCHs may be used for NACK-only feedback. In some embodiments, sending another PUCCH may indicate that the UE will send two PUCCHs.

[0065] In a "second" example, also discussed in more detail below, when there is an overlap between one or more PUCCHs in the time domain and another uplink transmission, first information is generated and piggybacked on the other uplink transmission. In some embodiments, the PUCCH is used for one or more MBS sessions. In some embodiments, the PUCCH is used for NACK-only feedback. In some embodiments, the first information indicates that the UE will transmit one or more PUCCHs or will not transmit any PUCCHs. In some embodiments, the first information is generated in the order of the PUCCH resources and the corresponding MBS sessions. In some embodiments, the length of the first information is Where k is the number of PUCCHs that overlap with other uplink transmissions. In some embodiments, the length of the first information is k, where k is the number of PUCCHs that overlap with other uplink transmissions. In some embodiments, the time interval between PDCCH monitoring and the corresponding PUCCH is configured by RRC signaling, MAC CE, or DCI.

[0066] 1. Mobile communication technology and environment

[0067] Figure 1 An example wireless communication network and / or system 100 is illustrated in which the techniques disclosed herein may be implemented in accordance with an embodiment of the present disclosure. In the discussion that follows, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as "network 100." Such an example network 100 includes a base station 102 (hereinafter referred to as "BS 102"; also referred to as a wireless communication node) and a user equipment device 104 (hereinafter referred to as "UE 104"; also referred to as a wireless communication device) that may communicate with each other via a communication link 110 (e.g., a wireless communication channel), and cell clusters 126, 130, 132, 134, 136, 138, and 140 that cover a geographic area 101. Figure 11 , BS 102 and UE 104 are contained within the respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating on its allocated bandwidth to provide adequate radio coverage to its intended users.

[0068] For example, BS 102 may operate on an allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 may communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 may also be divided into subframes 120 / 127 that may include data symbols 122 / 128. In the present disclosure, BS 102 and UE 104 are generally described herein as non-limiting examples of "communication nodes" that may practice the methods disclosed herein. According to various embodiments of the present solution, such communication nodes may be capable of wireless and / or wired communication.

[0069] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to some embodiments of the present solution is illustrated. The system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, the system 200 may be used in wireless communication environments such as Figure 1 The wireless communication environment 100 of FIG. 1 may be used to transmit (eg, send and receive) data symbols, as described above.

[0070] System 200 generally includes a base station 202 (hereinafter referred to as "BS 202") and a user equipment device 204 (hereinafter referred to as "UE 204"). BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each of which is coupled to and interconnected with each other via a data communication bus 220 as needed. UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each of which is coupled to and interconnected with each other via a data communication bus 240 as needed. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for the transmission of data as described herein.

[0071] As will be understood by those skilled in the art, the system 200 may also include Figure 2. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. In order to clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps are generally described in terms of their functions. Whether such functionality is implemented as hardware, firmware, or software depends on the specific application and the design constraints imposed on the overall system. Persons familiar with the concepts described herein may implement such functionality in an appropriate manner for each specific application, but such implementation decisions should not be construed as limiting the scope of the present disclosure.

[0072] According to some embodiments, the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230, which includes a radio frequency (RF) transmitter and an RF receiver, each including circuitry coupled to an antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time duplexing manner. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210, which includes an RF transmitter and an RF receiver, each including circuitry coupled to an antenna 212. The downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time duplexing manner. The operation of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmit link 250 while the downlink transmitter is coupled to the downlink antenna 212. Instead, the operation of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 at the same time as the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is tight time synchronization with minimal guard times between changes in duplex direction.

[0073] The UE transceiver 230 and the base station transceiver 210 are configured to communicate via a wireless data communication link 250 and to cooperate with appropriately configured RF antenna arrangements 212 / 232 capable of supporting specific wireless communication protocols and modulation schemes. In some illustrative embodiments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards (such as Long Term Evolution (LTE) and emerging 5G standards, etc.). However, it should be understood that the present disclosure is not necessarily limited to application of specific standards and associated protocols. Instead, the UE transceiver 230 and the base station transceiver 210 can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0074] According to various embodiments, BS 202 can be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, UE 204 can be implemented in various types of user equipment, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, a wearable computing device, etc. Processor modules 214 and 236 can be implemented or realized using 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, intended to perform the functions described herein. In this manner, the processor can be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor can also be implemented as a combination of computing devices, for example, a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a digital signal processor core, or any other such configuration.

[0075] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly in hardware, in firmware, in software modules executed by the processor modules 214 and 236, respectively, or any practical combination thereof. The memory modules 216 and 234 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, the memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processor modules 210 and 230 may read information from and write information to the memory modules 216 and 234, respectively. The memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, each of the memory modules 216 and 234 may include a cache memory for storing temporary variables or other intermediate information during the execution of instructions to be executed by the processor modules 210 and 230, respectively. Memory modules 216 and 234 may each also include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0076] The network communication module 218 generally represents the hardware, software, firmware, processing logic and / or other components of the base station 202 that support bidirectional communication between the base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, the network communication module 218 can be configured to support Internet or WiMAX traffic. In a typical deployment, but not limited to, the network communication module 218 provides an 802.3 Ethernet interface so that the base station transceiver 210 can communicate with a traditional Ethernet-based computer network. In this manner, the network communication module 218 can include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). As used herein with respect to a particular operation or function, the terms "configured for," "configured to," and variations thereof refer 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.

[0077] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical arrangement that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) that are open to interconnection and communication with other systems. The model is divided into seven subcomponents or layers, each of which represents a conceptual set of services provided to the layers above and below it. The OSI model also defines a logical network and effectively describes computer packet transmission by using different layer protocols. The OSI model may also be referred to as a seven-layer OSI model or a seven-layer model. In some embodiments, the first layer may be a physical layer. In some embodiments, the second layer may be a medium access control (MAC) layer. In some embodiments, the third layer may be a radio link control (RLC) layer. In some embodiments, the fourth layer may be a packet data convergence protocol (PDCP) layer. In some embodiments, the fifth layer may be a radio resource control (RRC) layer. In some embodiments, the sixth layer may be a non-access stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer is another layer.

[0078] 2. Example(s): Group 1

[0079] In some embodiments, a network (e.g., Figure 1The BS 102 in the UE configures (e.g., initializes, allocates, assigns, etc.) one or more PUCCH resources for the UE. Each PUCCH resource may correspond to one MBS session or a combination of MBS sessions. For an MBS session, if the UE does not correctly decode the transport block carried on the PDSCH, the UE may send the corresponding PUCCH. For an MBS session, if the UE correctly decodes the transport block carried on the PDSCH, the UE does not send the corresponding PUCCH. In some embodiments, for an MBS session, if more than one transport block is carried by the PDSCH and the UE does not correctly decode at least one transport block, the UE sends the corresponding PUCCH. For an MBS session, if more than one transport block is carried by the PDSCH and the UE correctly decodes all transport blocks, the UE does not send the corresponding PUCCH. The PUCCH resources are indicated by the DCI that schedules the PDSCH for the MBS session.

[0080] The time interval (e.g., time offset) between a PDSCH and a corresponding PUCCH is configured by radio resource control (RRC) signaling or a medium access control (MAC) layer control element (CE) or indicated by a DCI that schedules the PDSCH. In some embodiments, the time slot or subslot used for PUCCH transmission of the PDSCH is indicated by the DCI that schedules the PDSCH. In some embodiments, the time interval between a PDSCH and a corresponding PUCCH is a time unit offset between a time unit in which the PDSCH is received and a time unit in which the PUCCH is transmitted. A time unit is an OFDM symbol, a subslot, a minislot, a time slot, a subframe, or a frame.

[0081] In some embodiments, the time interval (e.g., time offset) between the PDCCH and the PUCCH corresponding to the PDSCH scheduled by the PDCCH is configured by RRC signaling or MAC CE. In some embodiments, the time interval between the PDCCH and the corresponding PUCCH is the time unit offset between the time unit in which the PDCCH is received and the time unit in which the PUCCH is transmitted.

[0082] In some embodiments, the time interval (e.g., time offset) between the PDCCH and the PUCCH corresponding to the PDSCH scheduled by the PDCCH is configured by the DCI carried on the PDCCH. The PUCCH is not allowed to overlap with other uplink transmissions in the time domain. Another uplink transmission is used for unicast transmission, such as a PUSCH carrying unicast data or a PUCCH for unicast transmission. From the perspective of the UE, when the PUCCH resources are indicated by the DCI, the UE does not expect the PUCCH resources to overlap with other uplink transmissions in the time domain. From the perspective of the network, the network should configure different time resources for the PUCCH and other uplink transmissions without overlapping in the time domain.

[0083] In some embodiments, the UE does not correctly decode a transport block for more than one MBS session. The UE will send more than one PUCCH and each PUCCH resource corresponds to an MBS session. If there is overlap in the time domain between these PUCCHs or if these PUCCHs are sent on the same time slot or sub-time slot, the UE sends a second PUCCH, where the second PUCCH resource corresponds to the combination of these MBS sessions. In some embodiments, the second PUCCH and these PUCCHs have the same time domain resources, for example, they have the same number and position of OFDM symbols. In some embodiments, the second PUCCH and these PUCCHs are on the same time slot or sub-time slot. In some embodiments, a transport block for a multicast and broadcast service (MBS) session is received by a wireless communication device on a physical downlink shared channel (PDSCH). In some embodiments, the wireless communication device determines the overlap in the time domain between the PUCCH corresponding to the PDSCH and the uplink channel. In some embodiments, the wireless communication device sends another PUCCH in response to determining the overlap. In some embodiments, the wireless communication device receives a second transport block for a second MBS session on a second PDSCH, and the second PUCCH corresponds to the second PDSCH. In some embodiments, the wireless communication device determines a failure to decode a transport block of an MBS session.In some embodiments, the wireless communication device determines a failure to decode a second transport block of a second MBS session.

[0084] Figure 3 A block diagram illustrating an example PUCCH transmission according to some embodiments of the present disclosure is shown. Figure 1 UE 104 in FIG receives three MBS services represented by MBS 0, MBS 1, and MBS 2, respectively. Figure 3As shown, PDSCH 0, PDSCH 1, and PDSCH 2 carry data for MBS sessions 0, 1, and 2, respectively. There may be seven PUCCH resources, represented by PUCCHs 0 to 7, respectively. In some embodiments, PUCCHs 0 to 7 may occupy different time domain resources, and / or frequency domain resources, and / or code domain resources. PUCCH resource 0 corresponds to MBS session 0 (e.g., PDSCH 0). PUCCH resource 1 corresponds to MBS session 1 (e.g., PDSCH 1). PUCCH resource 2 corresponds to MBS session 2 (e.g., PDSCH 2). PUCCH resource 3 corresponds to the combination of MBS session 0 and MBS session 1 (e.g., PDSCH 0 and 1). PUCCH resource 4 corresponds to the combination of MBS session 0 and MBS session 2 (e.g., PDSCH 0 and 2). PUCCH resource 5 corresponds to the combination of MBS session 1 and MBS session 2 (e.g., PDSCH 1 and 2). PUCCH resource 6 corresponds to the combination of MBS session 0, MBS session 1, and MBS session 2 (e.g., PDSCH 0, 1, and 2). In some embodiments, if the UE does not correctly decode the transport block carried on PDSCH 0, the UE transmits PUCCH 0. In some embodiments, if the UE correctly decodes the transport block carried on PDSCH 0, the UE does not transmit PUCCH 0. In some embodiments, if the UE does not correctly decode the transport block carried on PDSCH 1, the UE transmits PUCCH 1. In some embodiments, if the UE correctly decodes the transport block carried on PDSCH 1, the UE does not transmit PUCCH 1. In some embodiments, if the UE does not correctly decode the transport block carried on both PDSCH 0 and PDSCH 1, the UE transmits both PUCCH 0 and PUCCH 1. PUCCH 0 and PUCCH 1 overlap in the time domain, so the UE only transmits PUCCH 3 because PUCCH 3 corresponds to PDSCH 0 and 1. In some embodiments, if the UE does not correctly decode the transport block carried on PDSCH 0, 1, and 2, the UE will transmit PUCCH 0, PUCCH 1, and 2. PUCCH 0, PUCCH 1, and PUCCH 2 overlap in the time domain, so the UE only transmits PUCCH 6 because PUCCH 6 corresponds to PDSCH 0, PDSCH 1, and PDSCH 2.

[0085] In some embodiments, parameters or configurations are used to identify the transmission of an MBS session, such as a radio network temporary identifier (RNTI), a logical channel identifier, a search space, a control resource set, a physical downlink control channel (PDCCH) monitoring opportunity, a downlink control information (DCI) format, a PDCCH candidate or a control channel element (CCE) index, a multicast traffic channel (MTCH), a temporary mobile group identifier (TMGI), etc. One PUCCH resource corresponds to one MBS session. That is, the PUCCH resource may correspond to a parameter or configuration used to identify the transmission of an MBS session. In some embodiments, a transport block of an MBS session corresponds to a parameter including at least one of the following: a radio network temporary identifier (RNTI), a logical channel identifier, a search space, a control resource set, a PDCCH monitoring opportunity, a downlink control information (DCI) format, a PDCCH candidate, a control channel element (CCE) index of a PDCCH, and a multicast traffic channel (MTCH).

[0086] Taking RNTI as an example, one RNTI value corresponds to one MBS session. The PDSCH (or transport block) scheduled by the DCI format with the RNTI value carries the data of the corresponding MBS session. Each PUCCH resource corresponds to a DCI format with a special RNTI or a combination of a DCI format and its corresponding RNTI. In some embodiments, if the UE does not correctly decode the transport block scheduled by the DCI format with the special RNTI, the UE sends the PUCCH corresponding to the RNTI. In some embodiments, if the UE correctly decodes the transport block scheduled by the DCI format with the special RNTI, the UE does not send the PUCCH corresponding to the RNTI. Figure 3 As shown, if a first RNTI is configured for MBS session 0, PDSCH 0 may be scheduled using a DCI format with the first RNTI. In some embodiments, if a second RNTI is configured for MBS session 1, PDSCH 1 may be scheduled using a DCI format with the second RNTI. In some embodiments, if a third RNTI is configured for MBS session 2, PDSCH 2 may be scheduled using a DCI format with the third RNTI.

[0087] 3. Example(s): Group 2

[0088] In some embodiments, the third PUCCH is configured by the network for the UE. If the UE does not correctly decode the transport block, the UE sends the third PUCCH. In some embodiments, if the UE correctly decodes the transport block, the UE does not send the third PUCCH. In some embodiments, if the third PUCCH will overlap with the fourth uplink transmission in the time domain, the UE generates code bits for the third PUCCH and additionally sends a fourth uplink transmission carrying the generated code bits, and in some embodiments, the UE does not send the third PUCCH. In some embodiments, the generated code bits can be referred to as "first information". The value of the code bit for the first information indicates (e.g., indicates, means) that the UE will or will not send the third PUCCH. For example, a first information bit value of 0 indicates that the UE will not send the third PUCCH. A first information bit value of 1 indicates that the UE will send the third PUCCH.

[0089] In some embodiments, multiple PUCCH resources are configured by the network for the UE. Multiple PUCCH resources correspond to one MBS session. Multiple PUCCH resources correspond to multiple PDCCH monitoring opportunities with a one-to-one mapping. Each PUCCH resource corresponds to a PDCCH monitoring opportunity. In some embodiments, if the UE does not correctly decode the transport block scheduled by the DCI format (or PDCCH) sent on the PDCCH monitoring opportunity, the UE sends the PUCCH corresponding to the PDCCH monitoring opportunity. In some embodiments, if the UE correctly decodes the transport block scheduled by the DCI format (or PDCCH) sent on the PDCCH monitoring opportunity, the UE does not send the corresponding PUCCH. One or more transport blocks are scheduled by the DCI format (or PDCCH). In some embodiments, the time interval (e.g., time offset) between the PDCCH monitoring opportunity and the corresponding PUCCH resource is configured by RRC signaling, MAC CE, or DCI (e.g., PDCCH) sent on PDCCH monitoring.

[0090] In some embodiments, multiple PDCCH monitoring opportunities are configured to schedule the same data for an MBS session. In other words, the transport blocks scheduled by the DCI (or PDCCH) sent on these PDCCH monitoring opportunities can carry the same data (e.g., MAC PDU). If the UE does not correctly decode all transport blocks scheduled by the DCI (or PDCCH) sent on these PDCCH monitoring opportunities, the UE sends one or more PUCCHs corresponding to these PDCCH monitoring opportunities. In some embodiments, this depends on the UE selecting one or more PUCCHs among these PUCCHs for transmission. In some embodiments, the UE selects one or more PUCCHs corresponding to the reference signal (RS) with the highest signal quality (e.g., reference signal received power (RSRP)). The RS corresponding to the PUCCH is the spatial relationship configured for the PUCCH. If the UE correctly decodes at least one of the transport blocks scheduled by the DCI (or PDCCH) sent on these PDCCH monitoring opportunities, the UE will not send any PUCCH corresponding to these PDCCH monitoring opportunities.

[0091] In some embodiments, the multiple PUCCHs will overlap with the fourth uplink transmission in the time domain. The UE generates one or more code bits (referred to as first information) and additionally transmits a fourth uplink transmission carrying the generated code bits. In some embodiments, the UE does not transmit multiple PUCCHs. In some embodiments, the length of the generated first information bits is Where k is the number of PUCCH resources that overlap with the fourth uplink transmission. The value of the code bit for the first information bit represents (e.g., indicates, means) that the UE will transmit one of the multiple PUCCHs or that the UE will not transmit any PUCCH in the multiple PUCCHs. For example, the all-zero value 0...000 for the first information bit (e.g., ) indicates that the UE will not send any PUCCH. The first information indicates that the UE will send one of the multiple PUCCHs in the order of the time domain resources (such as the starting time or the starting symbol) of the PUCCH resources (such as ascending or descending order). For example, the value of the first information is 0...001 (such as ) indicates that the UE will send PUCCH resources at the earliest start time. The value of the first information is 0...010 (for example ) indicates that the UE will send the PUCCH resource at the second earliest start time, and so on. In some embodiments, the first information indicates that the UE will send one of the multiple PUCCHs in the order (e.g., ascending or descending order) of the frequency domain resources (e.g., starting PRB or starting RE) of the PUCCH resources. In some embodiments, the first information indicates that the UE will send one of the multiple PUCCHs in the order (e.g., ascending or descending order) of the code domain resources (e.g., cyclic shift index or OCC index) of the PUCCH resources. In some embodiments, the first information indicates that the UE will send one of the multiple PUCCHs in the order (e.g., ascending or descending order) of any combination of the time domain resources, frequency domain resources, and code domain resources of the PUCCH. For example, the first information indicates that the UE will send one of the multiple PUCCHs in the order (e.g., ascending or descending order) of first the time domain resources (e.g., starting time or starting symbol), then the frequency domain resources (e.g., starting PRB or starting RE), and then the code domain resources (e.g., cyclic shift index or OCC index) of the PUCCH resources.

[0092] In some embodiments, a wireless communication device receives one or more transport blocks for one or more multicast and broadcast service (MBS) sessions on one or more physical downlink shared channels (PDSCHs), determines a first overlap in the time domain between one or more first PUCCHs and a second uplink channel, generates first information in response to determining the first overlap, and transmits the first information on the second uplink channel. In some embodiments, the wireless communication device determines a failure to decode a transport block for the MBS session, transmits one of the PUCCHs in response to the failure to decode the transport block, wherein the PUCCH corresponds to the transport block. In some embodiments, the wireless communication device determines a success to decode a transport block for the MBS session, and transmits one of the PUCCHs in response to the success to decode the transport block, wherein the PUCCH corresponds to the transport block. In some embodiments, the wireless communication device determines a failure to decode downlink control information (DCI) at a PDCCH monitoring opportunity for the MBS session, transmits one of the PUCCHs in response to the failure to decode the DCI at the PDCCH monitoring opportunity, wherein the PUCCH resource corresponds to the PDCCH monitoring opportunity. In some embodiments, the wireless communication device determines success in decoding downlink control information (DCI) at a PDCCH monitoring opportunity of an MBS session, and the wireless communication device does not transmit one of the PUCCHs in response to the success in decoding the DCI at the PDCCH monitoring opportunity, wherein the PUCCH resource corresponds to the PDCCH monitoring opportunity. In some embodiments, the length of the first information is In some embodiments, the value of the first information indicates that the wireless communication device will transmit one of the PUCCHs overlapping with the second uplink channel, or the value of the first information indicates that the wireless communication device will not transmit any of the PUCCHs overlapping with the second uplink channel.

[0093] Figure 4 An example diagram of the overlap of PUCCH and uplink transmissions according to some embodiments of the present disclosure is illustrated. There are a total of 4 PUCCH resources, represented by PUCCH 0 to 3, which overlap with the fourth uplink transmission accordingly. The 4 PUCCH resources correspond to 4 PDCCH monitoring opportunities (represented by MO 0 to 3 accordingly). PUCCH 0 corresponds to MO 0, PUCCH 1 corresponds to MO 1, and so on. The PDCCH sent on MO 0 to 3 schedules PDSCH 0 to 3 accordingly. In some embodiments, if the UE does not correctly decode the transport block scheduled by MO 0 (i.e., the transport block carried on PDSCH 0), the UE will send PUCCH 0. If the UE correctly decodes the transport block scheduled by MO 0 (i.e., the transport block carried on PDSCH 0), the UE will not send PUCCH 0.

[0094] In some embodiments, if MOs 0 to 3 are configured to schedule the same data, PDSCHs 0 to 3 may carry the same data (e.g., transport blocks or MAC PDUs). In some embodiments, if the UE correctly decodes at least one of PDSCHs 0 to 3 (e.g., transport blocks carried on PDSCHs 0 to 3), the UE will not transmit PUCCHs 0 to 3. In some embodiments, if the UE does not correctly decode all of PDSCHs 0 to 3 (e.g., transport blocks carried on PDSCHs 0 to 3), the UE will transmit one or more of PUCCHs 0 to 3.

[0095] Since the PUCCH overlaps with the fourth uplink transmission, the UE generates the first information and does not transmit any PUCCH in PUCCH0 to 3. Since the number of PUCCH resources overlapping with the fourth uplink transmission is 4, the length of the first information bit is In some embodiments, if the UE will not transmit any of the four PUCCHs, a first information bit value of '000' is generated. In some embodiments, if the UE will transmit PUCCH 0, a first information bit value of '001' is generated. In some embodiments, if the UE will transmit PUCCH 1, a first information bit value of '010' is generated. In some embodiments, if the UE will transmit PUCCH 2, a first information bit value of '011' is generated. In some embodiments, if the UE will transmit PUCCH 3, a first information bit value of '100' is generated. In some embodiments, the first information bit will be carried by a fourth uplink transmission and the UE will transmit the fourth uplink transmission.

[0096] In some embodiments, the length of the first information bit is k, where k is the number of PUCCH resources overlapping with the fourth transmission. The value used for the first information bit represents (e.g., indicates) that the UE will send one or more PUCCHs of the plurality of PUCCHs or that the UE will not send any PUCCH. In some embodiments, the plurality of PUCCHs are arranged in the order of one or any combination of the time resources, frequency resources, and code resources of the PUCCH (e.g., ascending or descending order). The first information bit has an ordered one-to-one mapping with k PUCCH resources, such that the most significant bit corresponds to the first PUCCH resource, the second bit corresponds to the second PUCCH resource, and so on. The bit value in the first information bit indicates that the UE will or will not send the corresponding PUCCH resource. For example, a first information bit value of 0 indicates that the UE will not send the corresponding PUCCH. A first information bit value of 1 indicates that the UE will send the corresponding PUCCH. In some embodiments, the length of the first information corresponds to k, and where k corresponds to the number of PUCCH resources overlapping with the uplink transmission. In some embodiments, each bit of the first information corresponds to a PUCCH of a PUCCH overlapping with the second uplink channel, wherein a value of the bit of the first information indicates that the wireless communication device will transmit the corresponding PUCCH, or a value of the bit of the first information indicates that the wireless communication device will not transmit the corresponding PUCCH. In some embodiments, the first information is generated by the wireless communication device in a sequence of one or more PUCCHs and corresponding MBS sessions.

[0097] Still refer to Figure 4, since the number of PUCCH resources overlapping with the fourth uplink transmission is 4, the length of the first information bit is 4. In some embodiments, if the UE will transmit PUCCH 0, a first information bit value of '1000' is generated. In some embodiments, if the UE will transmit PUCCH 1, a first information bit value of '0100' is generated. In some embodiments, if the UE will transmit PUCCH 2, a first information bit value of '0010' is generated. In some embodiments, if the UE will transmit PUCCH 3, a first information bit value of '0001' is generated. In some embodiments, if the UE will transmit PUCCH 0 and PUCCH 1, a first information bit value of '1100' is generated.

[0098] In some embodiments, the fourth uplink transmission is a physical uplink shared channel (PUSCH). In some embodiments, the PUSCH carries only the uplink shared channel (UL-SCH). The generated first information bits are multiplexed with the code bits for the UL-SCH. The PUSCH carrying the multiplexed code bits is then transmitted by the UE. In some embodiments, the PUSCH carries uplink control information (UCI) and the UL-SCH. The generated first information bits are attached (e.g., concatenated) to the code bits for the UCI. The new code bits (attached code bits) are multiplexed with the code bits for the UL-SCH. The PUSCH carrying the multiplexed code bits is then transmitted by the UE. In some embodiments, the code bits for the UCI include code bits for more than one part, such as code bits for a hybrid automatic repeat request acknowledgment (HARQ-ACK), code bits for channel state information (CSI), etc. The generated first information bits are attached (e.g., concatenated) to the code bits for the HARQ-ACK in the UCI.

[0099] In some embodiments, the fourth uplink transmission is a PUCCH (referred to as a fourth PUCCH). The PUCCH carries code bits for UCI. The generated first information is attached (e.g., concatenated) to the code bits for UCI. A second PUCCH carrying new code bits (attached code bits) is sent by the UE. In some embodiments, the first information bits and the uplink shared channel (UL-SCH) are multiplexed by the wireless communication device; and the uplink channel carrying the multiplexed code bits is sent by the wireless communication device. In some embodiments, the first information bits and uplink control information (UCI) bits initially carried by the second uplink channel are concatenated by the wireless communication, and the concatenated bits and the uplink shared channel (UL-SCH), if any, are multiplexed by the wireless communication device, and the uplink channel carrying the multiplexed code bits is sent by the wireless communication device.

[0100] Figure 5 FIG1 illustrates an example diagram of first information bits generated by attaching according to some embodiments of the present disclosure. The generated first information bits are b1, b2, ..., b S In some embodiments, the code bits for UCI are a1, a2, ..., a N After appending, the new code bits are a1, a2, ..., a N ,b1,b2,...,b S In some embodiments, the code bits for UCI are a1, a2, ..., a M , a M+1 ,...,a N , where the code bits for HARQ-ACK are a1, a2, ..., a M After the generated first information bit is attached to the code bits for HARQ-ACK, the new code bits are a1, a2, ..., a M , a M+1 ,...,a N ,b1,b2,...,b S .

[0101] In some embodiments, the third PUCCH is used for a multicast service. Multiple PUCCH resources are used for a multicast service. In some embodiments, the fourth uplink transmission is used for a unicast service.

[0102] 4. Example(s): Group 3

[0103] In some embodiments, the network configures multiple groups of PUCCH resources for the UE. A group of PUCCH resources includes one or more PUCCH resources for an MBS session. Each PUCCH resource in a group corresponds to a PDCCH monitoring opportunity.

[0104] In some embodiments, multiple groups of PUCCH resources will overlap with the fifth uplink transmission in the time domain. The UE generates one or more HARQ-ACK information bits and sends a fifth uplink transmission carrying the generated HARQ-ACK information bits. The UE first generates HARQ-ACK information bits for each group according to the scheme in some embodiments (e.g., the embodiments disclosed in Group 2 as discussed herein). The HARQ-ACK information bits generated for each group are then concatenated. In some embodiments, the concatenation is performed in the order (e.g., ascending or descending) of the group index, MBS session index, or the parameters or configurations for identifying the transmission of the MBS session (e.g., RNTI, search space index, control resource set index, etc.). According to the scheme in some embodiments (e.g., the embodiments disclosed in Group 2 as discussed herein), the code bits after the HARQ-ACK information bits are concatenated are carried by the fifth uplink transmission.

[0105] Figure 6 An example diagram of the overlap of PUCCH and uplink transmissions according to some embodiments of the present disclosure is illustrated. Three groups of PUCCH resources, represented by groups 0 to 2, are configured for three MBS sessions. Group 0 includes four PUCCH resources, represented by PDSCH 0-0, PUCCH 0-1, PUCCH 0-2, and PUCCH 0-3. Group 1 includes two PUCCH resources, represented by PDSCH 1-0 and PUCCH 1-1. Group 2 includes three PUCCH resources, represented by PDSCH 2-0, PUCCH 2-1, and PUCCH 2-2. In some embodiments, if the UE is to transmit PUCCH 0-1 and PUCCH 2-2, HARQ-ACK information bit values ​​'010', '00', and '11' are generated for groups 0 to 2, respectively. The generated HARQ-ACK information bits are concatenated in group index order as '0100011'. The concatenated code bits '0100011' will be carried by the fifth uplink transmission. In some embodiments, if the UE intends to transmit PUCCH 0-0, PUCCH 0-3, and PUCCH 2-2, HARQ-ACK information bit values ​​'1001', '00', and '001' are generated for groups 0-2, respectively. The generated HARQ-ACK information bits are concatenated as "100100001" in group index order. The concatenated code bits '100100001' will be carried by the fifth uplink transmission.

[0106] 5. Example(s): Group 4

[0107] In some embodiments, the sixth PUCCH resource is configured by the network for the UE. The sixth PUCCH corresponds to one or more PDCCH monitoring opportunities for an MBS session. If the UE does not successfully detect (e.g., decode, receive) any DCI (PDCCH) sent on one or more PDCCH monitoring opportunities for the UE, the UE will send the sixth PUCCH. If the UE successfully detects at least one DCI (PDCCH) sent on one or more PDCCH monitoring opportunities for the UE, the UE will not send the sixth PUCCH. The time interval between the sixth PUCCH resource and the corresponding PDCCH monitoring opportunity is configured by RRC signaling, MAC CE, or DCI.

[0108] In some embodiments, multiple PUCCH resources are configured by the network for the UE. Multiple PUCCH resources correspond to one MBS session. Multiple PUCCH resources correspond to multiple PDCCH monitoring opportunities with a one-to-one mapping. Each PUCCH resource corresponds to a PDCCH monitoring opportunity. If the UE does not correctly decode the transport block scheduled by the DCI format (or PDCCH) sent on the PDCCH monitoring opportunity, the UE sends the PUCCH corresponding to the PDCCH monitoring opportunity. If the UE correctly decodes the transport block scheduled by the DCI format (or PDCCH) sent on the PDCCH monitoring opportunity, the UE does not send the corresponding PUCCH.

[0109] In some embodiments, the sixth PUCCH resource and at least one of the multiple PUCCH resources overlap with the uplink transmission in the time domain. The UE generates one or more code bits (referred to as first information) and additionally transmits an uplink transmission carrying the generated code bits. In some embodiments, the UE does not transmit multiple PUCCHs. The first information is generated according to the scheme in some embodiments (e.g., as disclosed in Group 2 discussed herein), taking into account all PUCCH resources that overlap in the time domain, including the sixth PUCCH resource. In some embodiments, the uplink transmission is for unicast transmission.

[0110] Figure 7An example diagram of the overlap of PUCCH and uplink transmission according to some embodiments of the present disclosure is illustrated. There are a total of 5 PUCCH resources, represented by PUCCH 0 to 4, which overlap with the fourth uplink transmission accordingly. The 4 PUCCH resources (PUCCH 0 to 3) correspond to the 4 PDCCH monitoring opportunities (represented by MO 0 to 3 accordingly). PUCCH 0 corresponds to MO 0, PUCCH 1 corresponds to MO 1, and so on. The PDCCH sent on MO 0 to 3 schedules PDSCH 0 to 3 accordingly. In some embodiments, if the UE does not correctly decode the transport block scheduled by MO 0 (i.e., the transport block carried on PDSCH 0), the UE will send PUCCH 0. In some embodiments, if the UE correctly decodes the transport block scheduled by MO 0 (i.e., the transport block carried on PDSCH 0), the UE will not send PUCCH 0. PUCCH 4 corresponds to MO 0 to 3. In some embodiments, if the UE does not successfully detect any DCI (PDCCH) sent for the UE on MO 0-3, the UE will send PUCCH 4. In some embodiments, if the UE successfully detects at least one DCI (PDCCH) sent for the UE on MO 0-3, the UE will not send PUCCH 4.

[0111] Due to the overlap between the PUCCH and the uplink transmission, the UE generates the first information and does not transmit any of PUCCHs 0 to 4. In some embodiments, since the number of PUCCH resources overlapping with the fourth uplink transmission is 5, the length of the first information bit is 3. In some embodiments, if the UE will not transmit any of the 5 PUCCHs, a first information bit value of '000' is generated. If the UE will transmit PUCCH 0, a first information bit value of '001' is generated. In some embodiments, if the UE will transmit PUCCH 1, a first information bit value of '010' is generated. In some embodiments, if the UE will transmit PUCCH 2, a first information bit value of '011' is generated. If the UE will transmit PUCCH 3, a first information bit value of '100' is generated. In some embodiments, if the UE will transmit PUCCH 4, a first information bit value of '101' is generated. The first information bit will be carried by the fourth uplink transmission and the UE will transmit the fourth uplink transmission. In some embodiments, because the number of PUCCH resources overlapping with the fourth uplink transmission is 5, the length of the first information bit is 5. In some embodiments, if the UE will transmit PUCCH 0, a first information bit value of '10000' is generated. In some embodiments, if the UE will transmit PUCCH 1, a first information bit value of '01000' is generated. In some embodiments, if the UE will transmit PUCCH 2, a first information bit value of '00100' is generated. In some embodiments, if the UE will transmit PUCCH 3, a first information bit value of '00010' is generated. In some embodiments, if the UE will transmit PUCCH 4, a first information bit value of '00001' is generated. In some embodiments, if the UE will transmit PUCCH 0 and PUCCH 1, a first information bit value of '11000' is generated.

[0112] In some embodiments, the network configures a seventh PUCCH resource for the UE. The seventh PUCCH resource corresponds to an MBS session. For an MBS session, if the UE does not correctly decode a transport block carried on the PDSCH, the UE transmits the seventh PUCCH. For an MBS session, if the UE correctly decodes a transport block carried on the PDSCH, the UE does not transmit the seventh PUCCH.

[0113] In some embodiments, the eighth PUCCH resource is configured by the network for the UE. If the UE is to transmit the sixth and seventh PUCCHs and there is a time domain overlap between the sixth and seventh PUCCHs, or the sixth and seventh PUCCHs are to be transmitted in the same time slot or subslot, the UE only transmits the eighth PUCCH. In some embodiments, the eighth PUCCH has the same time domain resources as the seventh or sixth PUCCH. In some embodiments, the eighth PUCCH is in the same time slot or subslot as the sixth or seventh PUCCH. The generated first information is carried by an uplink transmission.

[0114] In some embodiments, there is more than one MBS session for UE to receive. The MBS session is configured to be sent on one or more cells. The UE receives the PDCCH and / or PDSCH for the MBS session only on these cells. That is, one MBS session corresponds to one or more cells. The UE receives the PDCCH and / or PDSCH of the MBS session in the corresponding cell. For example, two cells are configured for the UE, represented by cell 0 and cell 1 respectively. The UE is configured to receive three MBS services, represented by MBS 1, MBS 2 and MBS 3 respectively. MBS 2 is configured to be sent only on cell 0, and MBS 1 and MBS 3 are sent on cell 1. Therefore, the UE monitors (e.g., detects, receives) the PDCCH and / or PDSCH for MBS 2 on cell 0, and monitors (e.g., detects, receives) the PDCCH and / or PDSCH for MBS 1 and MBS 3 on cell 1.

[0115] In some embodiments, a wireless device determines a downlink control information (DCI) format that schedules transmissions on multiple frequency bandwidths. In some embodiments, the number of information bits of the DCI format determined by the wireless device in response to scheduled transmissions on different frequency bandwidths is different. In some embodiments, the wireless device aligns the sizes of the DCI formats. In some embodiments, the DCI format schedules transmissions for multiple services on the multiple frequency bandwidths. In some embodiments, the multiple services include at least a unicast service and a multicast service. In some embodiments, the multicast service includes one or more MBS sessions. In some embodiments, the services correspond to frequency bandwidths, wherein the DCI format schedules transmissions for the services sent on the corresponding frequency bandwidths. In some embodiments, aligning the sizes of the DCI formats includes appending zero bits to the smaller DCI format until the payload size equals the payload size of the larger DCI format. In some embodiments, aligning the sizes of the DCI formats includes truncating the first few most significant bits of a frequency domain resource allocation (FDRA) field in the larger DCI format so that the payload sizes of the DCI formats are the same.

[0116] In some embodiments, there are multiple frequency ranges (e.g., frequency bandwidths) configured for a UE for frequency domain resource allocation. The multiple frequency ranges have different or identical sizes (e.g., the number of RBs or REs). The size of the frequency domain resource allocation (FDRA) field in the DCI format is based on the frequency range (e.g., the size of the frequency domain). The DCI format schedules PDSCH or PUSCH transmitted on different frequency ranges. Based on the sizes of the different frequency ranges, the sizes of the DCI formats used to schedule PDSCH or PUSCH transmitted on different frequency ranges may be different. That is, the DCI formats have different sizes. A first DCI format schedules PDSCH or PUSCH transmitted on a first frequency range. A second DCI format schedules PDSCH or PUSCH transmitted on a second frequency range. The first DCI format and the second DCI format may be the same DCI format. If the number of information bits in the first DCI format (e.g., the size of the first DCI format) is not equal to the number of information bits in the second DCI format, multiple zero padding bits are generated (e.g., attached to, or concatenated to) the smaller DCI format until the payload size equals the payload of the larger DCI format. If the number of information bits in the first DCI format is less than the payload size of the second DCI format, multiple zero padding bits are generated for the first DCI format until the payload size is equal to the payload size of the second DCI format. If the number of information bits in the first DCI format is greater than the payload size of the second DCI format, the bandwidth of the FDRA field in the first DCI format is reduced by truncating the first few most significant bits so that the size of the first DCI format is equal to the size of the second DCI format. After appending or truncation, the DCI formats have one size.

[0117] One frequency range among multiple frequency ranges is used for unicast service. One frequency range among multiple frequency ranges is used for multiple multicast services. That is, one frequency range among multiple frequency ranges corresponds to one service. Multiple frequency ranges have different or the same sizes (for example, the number of RBs or REs). The DCI format can schedule PDSCH / PUSCH for unicast service and schedule PDSCH / PUSCH for multicast service. The size of the frequency domain resource allocation (FDRA) field in the DCI format is based on the frequency range (for example, the size of the frequency domain). When the DCI format schedules PDSCH / PUSCH for a service, PUSCH or PUSCH is sent within the corresponding frequency range, and the size of the FDAI field in the DCI format is based on the size of the corresponding frequency range. When the DCI format schedules different services, the size of the FDRA field in the DCI format may be different based on different frequency ranges. This causes the size of the DCI format to be possibly different. If the number of information bits in the DCI format used to schedule the first service is not equal to the number of information bits in the DCI format used to schedule the second service, multiple zero padding bits are generated (e.g., attached or concatenated) for the smaller DCI format until the payload size equals the payload size of the larger DCI format. If the number of information bits in the DCI format used to schedule the first service is less than the payload size of the DCI format used to schedule the second service, multiple zero padding bits are generated for the DCI format used to schedule the first service until the payload size equals the payload size of the DCI format used to schedule the second service. If the number of information bits in the DCI format used to schedule the first service is greater than the payload size of the DCI format used to schedule the second service, the bit width of the FDRA field in the DCI format used to schedule the first service is reduced by truncating the first few most significant bits so that the size of the DCI format used to schedule the first service equals the size of the DCI format used to schedule the second service. In some embodiments, the DCI format used to schedule a unicast service is scrambled by a first RNTI (e.g., C-RNTI). The DCI format used to schedule a multicast service is scrambled by a second RNTI (e.g., G-RNTI). Different multicast services have different RNTIs. In some embodiments, there is a field in the DCI format to indicate the service scheduled by the DCI format (eg, unicast, multicast, MBS index). After attachment or truncation, the DCI format has one size regardless of the service scheduled by the DCI format.

[0118] For example, there are two frequency bandwidths, Bandwidth 0 and Bandwidth 1. Bandwidth 0 is used for PDSCH / PUSCH transmission of multicast services. Bandwidth 1 is used for PDSCH / PUSCH transmission of unicast services. The DCI format scrambled by G-RNTI schedules the PDSCH / PUSCH for multicast services. Based on Bandwidth 0, the number of information bits in the DCI format scrambled by G-RNTI is Y (Y>0). Based on Bandwidth 1, the number of bits in the DCI format scrambled by C-RNTI is Z (Z>0). If it is assumed that Y<Z, then (Z-Y) padding bits should be appended to the information bits of the DCI format scrambled by G-RNTI. In some embodiments, Z-Y bits are truncated from the most significant bits of the FDRA field for the DCI format scrambled by C-RNTI. In some embodiments, Bandwidth 0 is used for the first multicast service and Bandwidth 1 is used for the second multicast service. The same operation is performed to align the DCI format size.

[0119] 6. Method for implementing exemplary embodiments from Groups 1-4

[0120] Figure 8 is a flowchart depicting a method for multiplexing one or more uplink messages according to some embodiments of the present disclosure. Depending on the particular embodiment, additional, fewer, or different operations may be performed in the method. In some embodiments, some or all of the operations of method 800 may be performed by a wireless communication node, such as Figure 1 BS 102 in. In some operations, some or all of the operations of method 800 may be performed by a wireless communication device, such as Figure 1 UE 104 in. Each operation may be reordered, added, removed, or repeated.

[0121] As shown, in some embodiments, method 800 includes an operation 802 of receiving, by a wireless communication device, a transport block of a multicast and broadcast service (MBS) session on a physical downlink shared channel (PDSCH). In some embodiments, the method includes an operation 804 of determining, by the wireless communication device, an overlap in time domain between a PUCCH corresponding to the PDSCH and an uplink channel. In some embodiments, the method includes an operation 806 of sending, by the wireless communication device, another PUCCH in response to determining the overlap.

[0122] Figure 9 is a flowchart depicting a method for multiplexing one or more uplink messages according to some embodiments of the present disclosure. Depending on the particular embodiment, additional, fewer, or different operations may be performed in the method. In some embodiments, some or all of the operations of method 900 may be performed by a wireless communication node, such as Figure 1 BS 102 in. In some operations, some or all of the operations of method 900 may be performed by a wireless communication device, such as Figure 1 UE 104 in. Each operation can be reordered, added, removed, or repeated.

[0123] As shown, in some embodiments, method 900 includes an operation 902 of receiving, by a wireless communication device, one or more transport blocks of one or more multicast and broadcast service (MBS) sessions on one or more physical downlink shared channels (PDSCHs). In some embodiments, the method includes an operation 904 of determining, by the wireless communication device, a first overlap in the time domain between one or more first PUCCHs and a second uplink channel. In some embodiments, the method includes an operation 906 of generating, by the wireless communication device, first information in response to determining the first overlap. In some embodiments, the method includes an operation 908 of transmitting, by the wireless communication device, the first information on a second uplink channel.

[0124] Although various embodiments of the present solution have been described above, it should be understood that they are presented by way of example only, and not by way of limitation. Similarly, various figures may describe example architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the example features and functionality of the present solution. However, such persons will understand that the solution is not limited to the example architectures or configurations shown, but may be implemented using various alternative architectures and configurations. In addition, as will be understood by those of ordinary skill in the art, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.

[0125] It should also be understood that any reference to an element using names such as "first," "second," etc. herein generally does not limit the quantity or order of those elements. Instead, these names can be used herein as a convenient way to distinguish between two or more elements or instances of elements. Thus, reference to a first and a second element does not mean that only two elements can be used, or that the first element must precede the second element in some manner.

[0126] Additionally, persons of ordinary skill in the art will appreciate that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols, such as may be referenced in the above description, may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0127] Those of ordinary skill in the art will further understand that any of the various illustrative logical blocks, modules, processors, components, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of both), firmware, various forms of programs (e.g., computer program products), or design code containing instructions (for convenience, referred to herein as "software" or "software modules"), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, software, or a combination of these technologies depends on the particular application and the design constraints imposed on the overall system. A skilled person may implement the described functionality in varying ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure.

[0128] In addition, it will be understood by those of ordinary skill in the art that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented within or performed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, or any combination thereof. The logic blocks, modules, and circuits may also include antennas and / or transceivers to communicate with various components within a network or within a device. A general-purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.

[0129] If implemented in software, the functions may be stored as one or more instructions or codes on a computer-readable medium. Thus, the steps of the methods or algorithms disclosed herein may be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, including any medium capable of transferring a computer program or code from one place to another. A storage medium may be any available medium that a computer can access. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0130] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. In addition, for ease of discussion, various modules are described as discrete modules; however, it is obvious to those skilled in the art that two or more modules can be combined to form a single module that performs the associated functions according to embodiments of the present solution.

[0131] In addition, memory or other storage and communication components may be employed in embodiments of the present solution. It will be understood that, for purposes of clarity, the above description has described embodiments of the present solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements, or domains may be used without affecting the present solution. For example, functions illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable accessories for providing the described functionality, and do not indicate a strict logical or physical structure or organization.

[0132] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, the present disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. A method comprising: receiving, by a wireless communication device, one or more transport blocks of a multicast and broadcast service (MBS) session on at least one physical downlink shared channel (PDSCH); transmitting, by the wireless communication device, one of at least one PUCCHs based on a first decoding status of at least one transport block of the one or more transport blocks of the multicast and broadcast service MBS session, the first decoding status comprising a failure to correctly decode the at least one transport block, wherein each PUCCH corresponds one-to-one to a combination of first decoding statuses of the at least one transport block of the multicast and broadcast service MBS session received on the at least one physical downlink shared channel (PDSCH); as well as A PUCCH is not transmitted by the wireless communication device according to a second decoding status of all the one or more transport blocks of the multicast and broadcast service MBS session, the second decoding status comprising success in correctly decoding all of the one or more transport blocks.

2. The method according to claim 1 , wherein the combination of the first decoding status of the at least one transport block of the Multicast and Broadcast Service (MBS) session received on the at least one Physical Downlink Shared Channel (PDSCH) comprises: The at least one transport block of the Multicast and Broadcast Service, MBS, session received on at least one Physical Downlink Shared Channel, PDSCH, is not correctly decoded.

3. The method according to claim 1, characterized in that The at least one PUCCH has the same time domain resource.

4. The method according to claim 1, further comprising: determining, by the wireless communication device, the failure to correctly decode the at least one transport block of the MBS session; as well as One of the at least one PUCCH is sent by the wireless communication device in response to the failure to decode the at least one transport block. 5 . The method of claim 1 , wherein the transport block of the MBS session corresponds to a parameter including a Radio Network Temporary Identifier (RNTI).

6. A method comprising: sending, by a wireless communication node to a wireless communication device, one or more transport blocks of a multicast and broadcast service (MBS) session on at least one physical downlink shared channel (PDSCH); receiving, by the wireless communication node, one of the at least one PUCCHs sent by the wireless communication device based on a first decoding status of at least one transport block of the one or more transport blocks of the multicast and broadcast service MBS session, the first decoding status comprising a failure to correctly decode the at least one transport block, wherein each PUCCH corresponds one-to-one to a combination of the first decoding status of the at least one transport block of the multicast and broadcast service MBS session received on the at least one physical downlink shared channel (PDSCH); as well as The PUCCH is not received by the wireless communication node if all of the one or more transport blocks of the multicast and broadcast service MBS session have a second decoding status comprising success in correctly decoding all of the one or more transport blocks.

7. The method according to claim 6, wherein the combination of the first decoding status of the at least one transport block of the Multicast and Broadcast Service (MBS) session received on the at least one Physical Downlink Shared Channel (PDSCH) comprises: The at least one transport block of the Multicast and Broadcast Service, MBS, session received on at least one Physical Downlink Shared Channel, PDSCH, is not correctly decoded.

8. The method according to claim 6, characterized in that The at least one PUCCH has the same time domain resource.

9. The method according to claim 6, characterized in that The first decoding status of the transport blocks of the Multicast and Broadcast Service MBS session comprises: determining, by the wireless communication device, a failure to decode the at least one transport block of the MBS session; and The one of the at least one PUCCH is sent by the wireless communication device in response to the failure to decode the transport block.

10. The method of claim 6, wherein the transport block of the MBS session corresponds to a parameter including a Radio Network Temporary Identifier (RNTI).

11. A wireless communication device comprising a processor and a memory, wherein the processor is configured to read a code from the memory and implement the method according to any one of claims 1 to 10.

12. A computer program product comprising computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the method of any one of claims 1 to 10.

Images