Apply network decoding at one or more multicast radio bearer (MRB) paths in a multicast and broadcast service (MBS) system.

Abstract

A method for wireless communication performed by a user equipment (UE) includes receiving initial transmission parameters and retransmission parameters from a network device. The initial transmission parameters indicate whether a network decoding function is enabled for initial transmissions from a first radio link control (RLC) entity associated with a multicast radio bearer (MRB) of the network device. The retransmission parameters indicate whether the network decoding function is enabled for retransmissions from a second RLC entity associated with the MRB. The method further includes receiving an initial set of data units from the first RLC entity. The method further includes receiving a set of retransmitted data units from the second RLC entity based on a transmission status indicator indicating that the initial set of data units meets a failure condition.

Description

[0001] open field

[0002] This disclosure generally relates to wireless communications, and more particularly to the application of network decoding at one or more multicast radio bearer (MRB) paths in a multicast and broadcast service (MBS) system. Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is an enhancement set of the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0004] Wireless communication networks may include several base stations (BSs) capable of supporting communication between several user equipments (UEs). UEs can communicate with the base stations (BSs) via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the BS to the UE, while an uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail, a BS may be referred to as a B-node, gNB, access point (AP), radio headend, transmit / receive point (TRP), new radio (NR) BS, 5GB node, etc.

[0005] The above multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different user equipment to communicate at the city, country, region, and even global levels. New Radio (NR) (also known as 5G) is an enhancement set to the LTE mobile standard issued by the 3rd Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) on the downlink (DL), and CP-OFDM or SC-FDM (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation to improve spectral efficiency, reduce costs, improve service, utilize new spectrum, and better integrate with other open standards.

[0006] Multicast and broadcast service (MBS) systems can be examples of point-to-multipoint communication systems, where packets can be transmitted from a single source to multiple destinations. In some examples, an MBS system can broadcast packets to all receiving devices (such as user equipment (UEs)) within the MBS area. In other examples, an MBS system can multicast packets to a specific group of UEs selected from all UEs within the MBS area. An MBS area can be an example of a geographical region served by one or more base stations with MBS capabilities. One or more base stations serving an MBS area can transmit the same content to each UE within the MBS area.

[0007] In some systems, forward error correction (FEC) decoding can be specified to... k The original message of each code element is transformed into a message with... n A longer message with 100 code elements, so that it can be read from a message with 100 code elements. n The original message can be recovered from a subset of the source packets. Fountain codes are an example of a type of FEC code. Systems applying fountain codes can generate a potentially infinite sequence of encoded packets from a source packet set. In such examples, the source packet set can be recovered from any subset of the encoded packets when the number of encoded packets exceeds the number of source packets. Fountain codes can be considered rateless codes because the number of packets encoded based on fountain codes can be infinite. In some wireless systems, fountain codes can be called network codes because they can be applied to the network layer. Raptor codes and RaptorQ codes are examples of fountain codes.

[0008] Overview

[0009] In one aspect of this disclosure, a method for wireless communication performed by a user equipment (UE) includes: receiving from a network device a radio resource control (RRC) signaling including initial transmission parameters and retransmission parameters, the initial transmission parameters indicating whether a network decoding function is enabled for an initial transmission from a first radio link control (RLC) entity associated with a multicast radio bearer (MRB), and the retransmission parameters indicating whether the network decoding function is enabled for retransmissions from a second RLC entity associated with the MRB. The method further includes receiving the initial transmission from the first RLC entity of the network device. The method further includes: transmitting status data elements to the network device. The method also includes receiving retransmissions including a set of retransmission data elements from the second RLC entity of the network device.

[0010] Another aspect of this disclosure relates to an apparatus for performing wireless communication at a UE. The apparatus includes: means for receiving RRC signaling from a network device, including initial transmission parameters and retransmission parameters, the initial transmission parameters indicating whether a network decoding function is enabled for an initial transmission from a first Radio Link Control (RLC) entity associated with an MRB, and the retransmission parameters indicating whether a network decoding function is enabled for retransmissions from a second RLC entity associated with the MRB. The apparatus further includes: means for receiving the initial transmission from the first RLC entity of the network device. The apparatus further includes: means for transmitting status data elements including a set of status indicators to the network device. The apparatus also includes: means for receiving retransmissions including a set of retransmission data elements from the second RLC entity of the network device.

[0011] In another aspect of this disclosure, a non-transient computer-readable medium having non-transient program code recorded thereon for wireless communication at a UE is disclosed. The program code is executed by a processor and includes: program code for receiving RRC signaling from a network device, including initial transmission parameters and retransmission parameters, the initial transmission parameters indicating whether a network decoding function is enabled for an initial transmission from a first radio link control (RLC) entity associated with a multicast radio bearer (MRB), and the retransmission parameters indicating whether a network decoding function is enabled for retransmissions from a second RLC entity associated with the MRB. The program code further includes: program code for receiving the initial transmission from the first RLC entity of the network device. The program code further includes: program code for transmitting status data elements including a set of status indicators to the network device. The program code also includes: program code for receiving retransmissions including a set of retransmission data elements from the second RLC entity of the network device.

[0012] Another aspect of this disclosure relates to an apparatus for performing wireless communication at a UE. The apparatus may include a processor; a memory coupled to the processor; and instructions stored in the memory, which, when executed by the processor, are operable to cause the apparatus to: receive RRC signaling from a network device, including initial transmission parameters and retransmission parameters, the initial transmission parameters indicating whether a network decoding function is enabled for an initial transmission from a first RLC entity associated with an MRB, and the retransmission parameters indicating whether a network decoding function is enabled for a retransmission from a second RLC entity associated with the MRB. Execution of these instructions further causes the apparatus to: receive the initial transmission from the first RLC entity of the network device. Execution of these instructions also causes the apparatus to: transmit status data elements including a set of status indicators to the network device. Execution of these instructions further causes the apparatus to: receive retransmissions including a set of retransmission data elements from the second RLC entity of the network device.

[0013] In one aspect of this disclosure, a method for wireless communication performed by a network device includes: transmitting RRC signaling from the network device to a UE, including initial transmission parameters and retransmission parameters, the initial transmission parameters indicating whether a network decoding function is enabled for an initial transmission from a first RLC entity associated with the MRB of the network device, and the retransmission parameters indicating whether a network decoding function is enabled for a retransmission from a second RLC entity associated with the MRB of the network device. The method further includes transmitting an initial data element set associated with the initial transmission from the first RLC entity to the UE. The method further includes receiving a status data element including a set of status indicators from the UE. The method also includes transmitting a retransmission data element set associated with the retransmission from the second RLC entity to the UE.

[0014] Another aspect of this disclosure relates to an apparatus for wireless communication at a network entity. The apparatus includes: means for transmitting RRC signaling, including initial transmission parameters and retransmission parameters, from the network device to a UE, wherein the initial transmission parameters indicate whether an initial transmission of a network decoding function for an initial transmission from a first RLC entity associated with an MRB of the network device is enabled, and the retransmission parameters indicate whether a retransmission of a network decoding function for a second RLC entity associated with the MRB of the network device is enabled. The apparatus further includes: means for transmitting an initial data unit set associated with the initial transmission from the first RLC entity to the UE. The apparatus further includes: means for receiving status data units including a set of status indicators from the UE. The apparatus also includes: means for transmitting a retransmission data unit set associated with the retransmission from the second RLC entity to the UE.

[0015] In another aspect of this disclosure, a non-transient computer-readable medium having non-transient program code recorded thereon for wireless communication at a network device is disclosed. The program code is executed by a processor and includes: program code for transmitting RRC signaling, including initial transmission parameters and retransmission parameters, from the network device to a UE; the initial transmission parameters indicating whether a network decoding function is enabled for an initial transmission from a first RLC entity associated with the MRB of the network device; and the retransmission parameters indicating whether a network decoding function is enabled for a retransmission from a second RLC entity associated with the MRB of the network device. The program code further includes: program code for transmitting an initial set of data elements associated with the initial transmission from the first RLC entity to the UE. The program code further includes: program code for receiving status data elements including a set of status indicators from the UE. The program code also includes: program code for transmitting a set of retransmission data elements associated with the retransmission from the second RLC entity to the UE.

[0016] Another aspect of this disclosure relates to an apparatus for wireless communication at a network entity. The apparatus includes a processor; a memory coupled to the processor; and instructions stored in the memory, which, when executed by the processor, are operable to cause the apparatus to: transmit RRC signaling from the network device to a UE, including initial transmission parameters and retransmission parameters, the initial transmission parameters indicating whether a network decoding function is enabled for an initial transmission from a first RLC entity associated with the MRB of the network device, and the retransmission parameters indicating whether a network decoding function is enabled for a retransmission from a second RLC entity associated with the MRB of the network device. Execution of these instructions further causes the apparatus to: transmit an initial set of data elements associated with the initial transmission from the first RLC entity to the UE. Execution of these instructions further causes the apparatus to: receive status data elements including a set of status indicators from the UE. Execution of these instructions further causes the apparatus to: transmit a set of retransmission data elements associated with retransmission from the second RLC entity to the UE.

[0017] The aspects generally include, as described substantially with reference to the accompanying drawings and description and explained as such, methods, apparatus, systems, computer program products, non-transient computer-readable media, user equipment, base stations, wireless communication devices, and processing systems.

[0018] The foregoing has broadly outlined the features and technical advantages of the examples according to this disclosure in an effort to facilitate a better understanding of the following detailed description. Additional features and advantages will be described. The disclosed concepts and specific examples can be readily used as the basis for modifications or the design of other structures for implementing the same purposes as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the disclosed concepts, in both their organization and manner of operation, and their associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and not for defining limitations on the claims. Brief description of the attached diagram

[0020] To gain a more detailed understanding of the features of this disclosure, reference can be made to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain aspects of this disclosure and should not be considered as limiting its scope, as other equivalent aspects are permissible in this description. Identical reference numerals in different drawings may identify the same or similar elements.

[0021] Figure 1 It is a block diagram that conceptually illustrates examples of wireless communication networks according to various aspects of this disclosure.

[0022] Figure 2This is a block diagram that conceptually illustrates an example of communication between a base station and a user equipment (UE) in a wireless communication network according to various aspects of this disclosure.

[0023] Figure 3A This is an illustration of an example of a wireless communication system that uses a multicast radio bearer (MRB) to deliver multicast services, in accordance with various aspects of this disclosure.

[0024] Figure 3B Examples of wireless communication systems that use MRB to deliver multicast services, supported by various aspects of this disclosure, are explained.

[0025] Figure 4 This is a block diagram illustrating an example architecture for splitting the Radio Link Control (RLC) entity in the MRB, according to various aspects of this disclosure.

[0026] Figure 5A and Figure 5B This is a block diagram illustrating examples of a sender Packet Data Convergence Protocol (PDCP) entity and a receiver PDCP entity according to various aspects of this disclosure.

[0027] Figure 6A This is a block diagram illustrating an example of a process for generating multiple data units from a single data unit according to various aspects of this disclosure.

[0028] Figure 6B This is a block diagram illustrating an example of a process for generating a single data unit from multiple data units according to various aspects of this disclosure.

[0029] Figure 7 This is a block diagram illustrating an example of PDCP Service Data Unit (SDU) level retransmission according to various aspects of this disclosure.

[0030] Figure 8 This is a block diagram illustrating examples of network decoders and decoders according to various aspects of this disclosure.

[0031] Figure 9 This is a block diagram of a wireless communication device according to various aspects of the present disclosure, which receives an initial MBS transmission from a first path of the MRB and receives MBS retransmissions from a second path of the MRB.

[0032] Figure 10 This is a flowchart illustrating, for example, an example process performed by a receiving device according to various aspects of this disclosure.

[0033] Figure 11 This is a block diagram of a wireless communication device according to various aspects of the present disclosure, which transmits initial MBS transmissions from a first path of the MRB and transmits MBS retransmissions from a second path of the MRB.

[0034] Figure 12 This is a flowchart illustrating, for example, an example process performed by a transmitting device according to various aspects of this disclosure.

[0035] Detailed description

[0036] The various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be implemented in many different forms and should not be construed as being limited to any specific structure or function given throughout this disclosure. For example, any number of the aspects set forth may be used to implement an apparatus or method of practice. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods practiced using additional structures, functionalities, or structures and functionalities that complement or supplement the various aspects of this disclosure set forth. It should be understood that any aspect of this disclosure may be implemented by one or more elements of the claims.

[0037] Several aspects of a telecommunications system will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and explained in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0038] It should be noted that while the aspects may be described using terms commonly associated with 5G and next-generation wireless technologies, the aspects of this disclosure may be applied in communication systems based on other generations, such as and including 3G and / or 4G technologies.

[0039] Multicast and broadcast service (MBS) systems are examples of point-to-multipoint communication systems where packets can be transmitted from a single source to multiple destinations. In some examples, an MBS system can broadcast packets to all receiving devices (such as user equipment (UEs)) within an MBS area. In other examples, an MBS system can multicast packets to a specific group of UEs selected from all UEs within the MBS area. An MBS area can be an example of a geographical region served by one or more base stations with MBS capabilities. One or more base stations serving an MBS area can transmit the same content to each UE within the MBS area. Some wireless communication systems, such as some MBS systems, support the retransmission of one or more packets to correct one or more errors in the initial transmission, such as decoding errors or another type of error.

[0040] In some systems, forward error correction (FEC) decoding can be specified to... k The original message of each code element is transformed into a message with...n A longer message with 100 code elements, so that it can be read from a message with 100 code elements. n The original message can be recovered from a subset of the code elements. Fountain codes are an example of a type of FEC code. Systems applying fountain codes can generate a potentially infinite sequence of encoded packets from a source packet set. In such examples, the source packet set can be recovered from any subset of the encoded packets when the number of encoded packets exceeds the number of source packets. Fountain codes can be considered rateless codes because the number of packets encoded based on fountain codes can be infinite. In some wireless systems, fountain codes can be called network codes because they can be applied to the network layer. Raptor codes are another type of network code.

[0041] The aspects of this disclosure generally relate to splitting the initial transmission path and retransmission path of a radio bearer. More specifically, the aspects relate to techniques and processes for applying network decoding functions at one or both of the transmission path or retransmission path of a radio bearer. In such aspects, the radio bearer may be an example of a multicast radio bearer (MRB). Additionally, the radio link control (RLC) entity of the transmission path and the RLC entity of the retransmission path may receive packets from a single packet data convergence protocol (PDCP) entity of the radio bearer. In a particular example, before receiving a transmission from the transmission path or retransmission path, a receiving device (such as a UE) may receive radio resource control (RRC) signaling from the network device, including initial transmission parameters and retransmission parameters. In such examples, the initial transmission parameters indicate whether network decoding functions are enabled for the initial transmission from the initial transmission path. Additionally, in such examples, the retransmission parameters indicate whether network decoding functions are enabled for retransmissions.

[0042] In various aspects, the initial transmission parameters indicate that the network decoding function is enabled for the initial transmission; in some examples, the PDCP entity may encode the initial data unit set based on applying the network decoding function to a first set of source segments associated with a single data unit. The initial data units in the initial data unit set may be examples of encoded packets. In some examples, the UE may determine whether the initial data unit set meets a failure condition. In some such examples, the initial data unit set meets the failure condition based on the total number of the initial data unit set being less than a certain threshold. In other such examples, the initial data unit set may meet the failure condition based on the inability to reconstruct the source segment set. In various aspects, the UE may transmit to the network device a status data unit including a set of status indicators, one or more of which may indicate reception failure based on the initial data unit set meeting the failure condition.

[0043] In various aspects, the UE can receive a set of retransmitted data units from the network device's retransmission path based on one or more status indicators in the status indicator set indicating a reception failure. In some examples, the retransmission parameter indicates that the network decoding function is enabled for this retransmission. In some examples, each retransmitted data unit in the retransmission data unit set is a parity data unit, such as a parity PDCP SDU. In other examples, the retransmission data unit set may correspond to one or more source segments of the network device. In some other examples, the retransmission parameter indicates that the network decoding function is enabled for this retransmission, and the initial transmission parameter indicates that the network decoding function is disabled for this initial transmission.

[0044] Specific implementations of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, by splitting the radio bearer into two paths—an initial transmission path and a retransmission path—some aspects of this disclosure can reduce network overhead and network latency by limiting retransmissions to UEs that send NACKs based on the initial transmission. In some other examples, by applying network decoding to one or both of the initial transmission or retransmissions, aspects of this disclosure can improve the reliability of multicast transmissions (including one or both of the initial transmission or retransmissions).

[0045] Figure 1 This is a block diagram illustrating a wireless network 100 in which various aspects of this disclosure may be practiced. The wireless network 100 may be a 5G or NR network or some other wireless network, such as an LTE network. The wireless network 100 may include several BS 110s (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE) and may also be referred to as a base station, NR BS, B-node, gNB, 5G B-node (NB), access point, transmit / receive point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0046] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. Macrocells can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with a service subscription. Picocells can cover a relatively small geographic area and allow unrestricted access by UEs with a service subscription. Femtocells can cover a relatively small geographic area (e.g., a residential area) and allow restricted access by UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS used for macrocells may be referred to as a macro BS. A BS used for picocells may be referred to as a pico BS. A BS used for femtocells may be referred to as a femto BS or a home BS. Figure 1 In the example shown, BS 110a can be a macro BS for macro cell 102a, BS 110b can be a pico BS for pico cell 102b, and BS 110c can be a femto BS for femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “B node,” “5G NB,” and “cell” are used interchangeably.

[0047] In some respects, the cell may not be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile BS. In some respects, BSs may interconnect with each other and / or interconnect to one or more other BSs or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.).

[0048] The wireless network 100 may also include a relay station. A relay station is an entity capable of receiving data transmissions from an upstream station (e.g., a BS or a UE) and transmitting those data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. Figure 1 In the example shown, relay station 110d can communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay station may also be referred to as a relay BS, relay base station, relay, etc.

[0049] Wireless network 100 can be a heterogeneous network comprising different types of Base Stations (BSs) (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs may have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0050] As an example, BS 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and core network 130 may exchange communication via backhaul link 132 (e.g., S1, etc.). Base station 110 may communicate with each other directly or indirectly (e.g., via core network 130) on other backhaul links (e.g., X2, etc.).

[0051] Core network 130 may be an evolved packet core (EPC), which may include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME may be the control node that handles signaling between UE 120 and the EPC. All user IP packets can be transmitted through the S-GW, which itself can be connected to the P-GW. The P-GW provides IP address allocation and other functions. The P-GW may be connected to the network operator's IP services. The operator's IP services may include the Internet, intranet, IP Multimedia Subsystem (IMS), and packet switching (PS) streaming services.

[0052] Core network 130 provides user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. One or more of base stations 110 or access node controllers (ANCs) can interface with core network 130 via backhaul links 132 (e.g., S1, S2, etc.) and can perform radio configuration and scheduling for communication with UE 120. In some configurations, the various functions of each access network entity or base station 110 can be distributed across various network devices (e.g., radio headends and access network controllers) or combined into a single network device (e.g., base station 110).

[0053] UEs 120 (e.g., 120a, 120b, and 120c) may be distributed throughout the wireless network 100, and each UE may be stationary or mobile. UEs may also be referred to as access terminals, terminals, mobile stations, subscriber units, stations, etc. UEs may be cellular phones (e.g., smartphones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptops, cordless phones, wireless local loop (WLL) stations, tablets, cameras, gaming devices, netbooks, smartbooks, ultrabooks, medical devices or equipment, biometric sensors / devices, wearable devices (smartwatches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), entertainment devices (e.g., music or video devices, or satellite radios), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, GPS devices, or any other suitable device configured to communicate via wireless or wired media.

[0054] One or more UEs 120 can establish Protocol Data Unit (PDU) sessions for network slicing. In some cases, UE 120 can select network slices based on application or subscription services. By serving different network slices for different applications or subscriptions, UE 120 can improve its resource utilization in the wireless network 100 while also meeting the performance specifications of individual applications of UE 120. In some cases, the network slice used by UE 120 may be provided by an AMF (Application-Specific Component) associated with one or both of base station 110 and core network 130. Figure 1 (Not shown in the image) to provide services. In addition, session management for network slices can be performed by the Access and Mobility Management Function (AMF).

[0055] Base station 110 may include network decoding module 142. For simplicity, only one base station 110 is shown as including network decoding module 142. Network decoding module 142 may transmit RRC signaling to UE 120 including initial transmission parameters and retransmission parameters. The initial transmission parameters indicate whether the network decoding function is enabled for initial transmission of a first RLC entity associated with the MRB from the network device, and the retransmission parameters indicate whether the network decoding function is enabled for retransmission of a second RLC entity associated with the MRB from the network device. Network decoding module 142 may also transmit an initial data element set associated with the initial transmission from the first RLC entity to UE 120. Network decoding module 142 may further receive status data elements including a status indicator set from UE 120. In some examples, each initial data element in the initial data element set corresponds to one or more status indicators in the status indicator set. The network decoding module 142 can also transmit a set of retransmission data units associated with retransmission from the second RLC entity to the UE 120 based on the received status data unit.

[0056] UE 120 may include network decoding module 144. For simplicity, only one UE 120 is shown as including network decoding module 144. In some examples, network decoding module 144 may receive RRC signaling from a network device (such as base station 110) including initial transmission parameters and retransmission parameters, wherein the initial transmission parameters indicate whether the network decoding function is enabled for initial transmission of a first RLC entity associated with the MRB from the network device, and the retransmission parameters indicate whether the network decoding function is enabled for retransmission of a second RLC entity associated with the MRB from the network device. Network decoding module 144 may also receive initial transmissions including an initial data element set from the first RLC entity of the network device. Network decoding module 144 may further enable UE 120 to transmit a status data element including a status indicator set to the network device based on the initial data element set meeting a failure condition. Network decoding module 144 may further receive retransmissions including a retransmission data element set from the second RLC entity of the network device based on the transmission of the status data element. Finally, the network decoding module 144 can generate one or more data units based on one or both of the retransmitted data unit set or the initial data unit set.

[0057] Some UEs can be considered Machine-Type Communication (MTC) UEs, or evolved or enhanced Machine-Type Communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a base station, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity to or to a network (e.g., a wide area network such as the Internet) or a cellular network, for example, via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices, or can be implemented as narrowband Internet of Things (NB-IoT) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing that houses the components of UE 120, such as processor components, memory components, etc.

[0058] Generally, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific Radio Access Technology (RAT) and can operate on one or more frequencies. A RAT may also be referred to as a radio technology, air interface, etc. A frequency may also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5GRAT networks can be deployed.

[0059] In some respects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary). For example, UE 120 may use peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, mesh networks, etc.). In this scenario, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere as being performed by base station 110. For example, base station 110 may configure UE 120 via downlink control information (DCI), radio resource control (RRC) signaling, media access control-control element (MAC-CE), or via system information (e.g., system information block (SIB)).

[0060] Figure 2 This is a block diagram of the design of base station 110 and UE 120. Base station 110 and UE 120 can be... Figure 1 One of the base stations and one of the UEs. Base station 110 may be equipped with T antennas 234a to 234t, and UE 120 may be equipped with R antennas 252a to 252r, wherein generally T ≥ 1 and R ≥ 1.

[0061] At base station 110, transmit processor 220 can receive data destined for one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on the Channel Quality Indicator (CQI) received from each UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Reducing the MCS decreases throughput but improves transmission reliability. Transmit processor 220 can also process system information (e.g., semi-static resource partitioning information (SRPI) and other information) and control information (e.g., CQI requests, grants, upper-layer signaling, etc.) and provide overhead symbols and control symbols. Transmit processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can... T Each output symbol stream is provided with T Modulators (MODs) 232a-232t. Each modulator 232 can process its own output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t respectively. According to the aspects described in more detail below, position coding can be used to generate synchronization signals to convey additional information.

[0062] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on these received symbols where applicable, and provide detected symbols. Receiver processor 258 can process (e.g., demodulate and decode) these detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The channel processor can determine the Reference Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Received Quality (RSRQ), Channel Quality Indicator (CQI), and so on. In some respects, one or more components of the UE 120 may be included in the housing.

[0063] On the uplink, at UE 120, transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., reports including RSRP, RSSI, RSRQ, CQI, etc.). Transmit processor 264 can also generate reference symbols for one or more reference signals. Symbols from transmit processor 264 can be pre-encoded by TX MIMO processor 266 where applicable, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to base station 110. At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 254, detected by MIMO detector 236 where applicable, and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. The receiver processor 238 can provide decoded data to the data sink 239 and decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the core network 130 via the communication unit 244. The core network 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0064] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2Any other component may perform one or more techniques associated with transmitting an OAM beam via an OAM antenna comprising several concentric antenna arrays, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component of (such as) can execute or direct, for example Figure 8 The operation of the process or other processes as described. Memory 242 and 282 may store data and program code for base station 110 and UE 120, respectively. Scheduler 246 may schedule the UE for data transmission on downlink and / or uplink.

[0065] Multicast and broadcast service (MBS) systems can be examples of point-to-multipoint communication systems, where packets can be transmitted from a single source to multiple destinations. In some examples, an MBS system can broadcast packets to all receiving devices (such as user equipment (UEs)) within the MBS area. In other examples, an MBS system can multicast packets to a specific group of UEs selected from all UEs within the MBS area. An MBS area can be an example of a geographical region served by one or more base stations with MBS capabilities. One or more base stations serving an MBS area can transmit the same content to each UE within the MBS area.

[0066] In some systems, forward error correction (FEC) decoding can be specified to... k The original message of each code element is transformed into a message with... n A longer message with 100 code elements, so that it can be read from a message with 100 code elements. n The original message can be recovered from a subset of the code elements. Fountain codes are an example of a type of FEC code. Systems applying fountain codes can generate a potentially infinite sequence of encoded packets from a source packet set. In such examples, the source packet set can be recovered from any subset of the encoded packets when the number of encoded packets exceeds the number of source packets. Fountain codes can be considered rateless codes because the number of packets encoded based on fountain codes can be infinite. In some wireless systems, fountain codes can be called network codes because they can be applied to the network layer. Raptor codes are an example of fountain codes. Network decoding can increase the reliability of transmissions (such as multicast transmissions) in MBS systems. Therefore, it may be desirable to apply network decoding to MBS systems.

[0067] Figure 3A This is a diagram illustrating an example of a wireless communication system 300 that supports the use of a multicast radio bearer (MRB) to deliver multicast services according to various aspects of this disclosure. In some examples, the wireless communication system 300 may implement as described in reference... Figure 1The wireless network 100 is described in various aspects. The wireless communication system 300 includes a base station 110 and a UE 120, which can be as described in reference... Figure 1 and Figure 2 Examples of base station 110 and UE 120 are described. Wireless communication system 300 further includes multicast-broadcast user plane function (MB-UPF) 305. MB-UPF 305 can be a core network (such as referenced...) Figure 1 The components of the core network (130) described. Core network ( Figure 3A (Not shown in the image) can provide grouping, sorting, aggregation, forwarding, routing, policy enforcement, data buffering, and other functionalities.

[0068] MB-UPF 305 can provide multicast Quality of Service (QoS) flow indication to base station 110 to transmit multicast data 310 to one or more UEs 120 in MBS area 302 during a multicast Protocol Data Unit (PDU) session. For ease of explanation, Figure 3A Only one UE 120 in MBS area 302 has been described. In some examples, multiple UEs 120 may be located in MBS area 302. In some examples, base station 110 may select a radio bearer for delivering multicast data 310 to one or more UEs 120. The radio bearer may include MRBs and data radio bearers (DRBs). In some such examples, the base station may select the radio bearer based on an indication received from MB-UPF 305. In one such example, the indication may identify the multicast data QoS flow, which may be associated with a QoS level.

[0069] In some implementations, base station 110 (e.g., RAN) selects an MRB or DRB based on a mapping of multicast data 310 to multicast data QoS flows. For example, base station 110 may select an MRB for the transmission of multicast data 310 in response to identifying a group of UEs 120 for multicast data 310 and also based on multicast QoS flow characteristics. In this example, base station 110 selects an MRB to transmit multicast data 310 to UE 120 via multicast channel 315-a. In some other examples, multicast data 310 may be broadcast to all UEs 120 in MBS area 302. In other examples, base station 110 may determine that only one UE 120 or a subset of UEs 120 from a group of UEs 120 should receive multicast data 310; for example, some UEs 120 may not support receiving multicast data via an MRB. In this example, base station 110 selects a DRB for transmitting multicast data 310 to UE 120 via unicast channel 315-b.

[0070] In some implementations, for hybrid multicast and unicast delivery modes, from the core network (e.g., MB-UPF 305) perspective, UE 120 is expected to be in a connected mode (such as 5G Non-Access Stratum (NAS) Connection Management (CM) - Connected mode) to receive downlink (DL) transmissions. From a radio perspective (e.g., from the base station 110's perspective), UE 120 may need to be in a connected state, such as RRC_connected state. In the RRC_connected state, UE 120 can provide hybrid Automatic Repeat Request (HARQ) feedback, PDCP feedback, and RLC status feedback. This feedback can be multicast or unicast feedback. As described, base station 110 can perform retransmissions based on the feedback via unicast channel 315-b or multicast channel 315-a, such as L1 HARQ or L2 Automatic Repeat Request (ARQ) retransmissions.

[0071] Figure 3B Examples of a wireless communication system 350 supporting the use of MRB to deliver multicast services according to various aspects of this disclosure are described. In some examples, the wireless communication system 350 may implement various aspects of a wireless network 100. The wireless communication system 350 includes a RAN node 320 and a UE 120. The RAN node 320 may be as described in relation to... Figure 1 and Figure 2 An example of the described base station 110. The wireless communication system 350 further includes an MB-UPF 355, which may be a reference. Figure 3A An example of the MB-UPF 305 described.

[0072] exist Figure 3B In the example, the wireless communication system 350 may support multicast / broadcast Quality of Service (MB-QoS) streams. In some examples, a Protocol Data Unit (PDU) session may be established between each UE 120 and the corresponding RAN nodes 320-a and 320-b. Each PDU session may be UE-specific (e.g., each UE 120 receives a unique PDU session ID). The PDU session may include UE-specific unicast streams (shown as UE QoS streams 360-a, 360-b, 360-c, and 360-d) and MB-QoS streams (shown as a shared MB-QoS stream 325). The shared MB-QoS stream 325 may be shared with other UEs 120 in the same MBS area 352.

[0073] exist Figure 3BIn the example, MB-UPF 355 includes packet classifier 365 and receives traffic from upstream network components. Packet classifier 365 can determine the appropriate flow to be used to deliver the traffic (e.g., UE QoS flow 360 and / or shared MB-QoS flow 325). This flow can be determined based on the QoS associated with the traffic, the expected recipient of the traffic based on traffic analysis (e.g., one of UE QoS flows 360-a, 360-b, 360-c, and 360-d or shared MB-QoS flow 325).

[0074] Each UE QoS flow 360 and the shared MB-QoS flow 325 can be associated with different communication tunnels. For example, each UE QoS flow 360 can be associated with a single unicast tunnel 335. Additionally, different MB tunnels 340 can be specified between the MB-UPF 355 and each RAN 320-a and 320-b. Furthermore, each tunnel 335-a, 335-b, 335-c, 335-d, 340-a, and 340-b can be associated with a unique tunnel endpoint identifier (TEID). The MB tunnel 340 can be an example of a multicast-broadcast-N3 (MB-N3) shared tunnel with a shared TEID. In some examples, the MB-N3 shared tunnel 340 can be established between RAN 320 and MB-UPF 355 based on a request to provide MB traffic to one or more UEs 120.

[0075] In an example traffic mode for the wireless communication system 350, the MB-UPF 355 can receive traffic intended for a first UE 120-a. The MB-UPF 355 can select a first UE QoS flow 360-a, which routes the traffic to a first RAN node 320-a using a first UE-specific tunnel 335-a. The first RAN node 320-a can then deliver the traffic to the first UE 120-a based on a first DRB 330-a for the first UE 120-a. In another example traffic mode, the MB-UPF 355 receives MB traffic and selects a shared MB-QoS flow 325 for the MB traffic. The MB-UPF 355 can establish a first MB tunnel 340-a (e.g., an MB-N3 tunnel) with the first RAN node 320-a to deliver MB traffic to both the first UE 120-a and the second UE 120-b. In some examples, the MB-UPF 355 can transmit an instruction to the first RAN node 320-a to provide MB traffic to the first UE 120-a and the second UE 120-b. The first RAN node 320-a can then select the radio bearer mode for delivering the MB traffic to the first UE 120-a and the second UE 120-b. The selected mode can be a multicast / broadcast-only mode, a mixed multicast / broadcast and unicast mode, or a unicast mode. In some examples, the selected mode can be based on the QoS associated with the MB traffic and the connection status of each UE 120-a and 120-b. Figure 3B In the example, the first RAN node 320-a can use MB-only mode or a hybrid MB and unicast mode, and deliver traffic to the first UE 120-a and the second UE 120-b via MRB 345. In some examples, the first RAN node 320-a can use MRB 345 based on QoS conditions met at the QoS level (such as traffic volume being less than a traffic threshold).

[0076] In another example, MB-UPF 355 can receive MB traffic and select a shared MB-QoS stream 325 for use with the MB traffic. In this example, MB-UPF 355 can establish a second MB tunnel 340-b (e.g., an MB-N3 tunnel) with the second RAN node 320-b to deliver MB traffic to the third UE 120-c and the fourth UE 120-d. Figure 3B In the example, the second RAN node 320-b can use a hybrid MB and unicast mode or a unicast-only mode. In this example, the QoS level associated with MB traffic can be greater than the traffic threshold. Therefore, the second RAN node 320-b can use different DRBs 330-c and 330-d to deliver MB traffic to the third and fourth UEs 120-c and 120-d.

[0077] For reference Figure 3B As described, the wireless communication system 350 can switch between DRB and MRB. In some examples, the N2 interface can be used from the Access and Mobility Management Function (AMF) ( Figure 3B (Not shown in the image) Signals to RAN node 320 to notify of MB stream settings or MB stream modifications. In some examples, RAN node 320 may use a Group Radio Network Temporary Identifier (G-RNTI) to perform MB transmissions.

[0078] Some MBS systems (such as LTE MBS systems) do not support MB retransmissions from base stations. Other MBS systems (such as NRMBS systems) can support MB retransmissions from base stations to improve reliability and reduce latency. In some systems (such as unicast communication systems), a Radio Link Control (RLC) Acknowledgment mode (AM) can be specified to correct residual errors in lower layers. In such systems, the transmitting device (such as a base station) can receive an acknowledgment (ACK) or a negative acknowledgment (NACK) from the receiving device (such as a UE) based on transmitting data to the receiving device according to the RLC.

[0079] In some examples, the lower layer of the transporter can receive RLC Service Data Units (SDUs) from the upper layer and can segment or concatenate RLC SDUs into RLC Protocol Data Units (PDUs) of predefined sizes. In such examples, the transporter can assign a sequence number to each PDU. In some examples, the receiver can receive one or more RLC PDUs from the transporter and can reassemble RLCP PDUs into SDUs based on the sequence numbers. As described, an RLC AM can be specified for a transmission from the transporter. In such examples, the receiver can transmit an ACK for each RLC PDU that satisfies the decoding conditions. In other examples, the receiver can transmit an ACK for each RLC PDU sequence based on the fact that the decoding conditions are met. In other such examples, the transporter can transmit subsequent RLC PDUs or subsequent RLC PDU sequences based on receiving an ACK from the receiver. In other examples, the receiver can transmit a NACK for each RLC PDU that fails to satisfy the decoding conditions or may not transmit an ACK. In such examples, the transporter can retransmit each RLC PDU that is not associated with an ACK. Lower-level error correction schemes (such as HARQ) used for RLC transmissions can increase data transmission overhead and reduce network efficiency. In some systems, RLC AM can improve the efficiency of the wireless communication system by reducing the number of ACKs specified for RLC transmissions. In some examples, the number of ACKs can be reduced based on the implementation of one or more factors, such as timers or polling requests.

[0080] In some aspects of this disclosure, in an MBS system, retransmission PDUs generated at the upper layer of the MRB can correct one or more residual errors in the lower layers. In some such aspects, network decoding can be applied to the upper layer of the MRB in the MBS system to improve the reliability of multicast transmission.

[0081] In some wireless communication systems, a single MRB path can be used for both initial MBS transmission and MBS retransmission. In some examples, different UEs may not be able to decode different packets. As described, a UE may transmit a NACK based on an undecoded packet. In such examples, the UE can receive the packet corresponding to the NACK from the MRB (e.g., the base station's MRB). However, not all UEs in the MBS area may expect this packet. Therefore, transmitting the packet corresponding to the NACK to all UEs in the MBS area may increase network bandwidth and latency. Aspects of this disclosure relate to defining two distinct RLC entities for the MRB of an MBS system. In such aspects, a first RLC entity can be used for initial MBS transmission, and a second RLC entity can be used for MBS retransmission.

[0082] Figure 4 This is a block diagram illustrating an example architecture 400 for splitting RLC entities in an MRB, according to various aspects of this disclosure. Figure 4 In the architecture 400, there are multiple access layers, such as the Service Data Adaptation Protocol (SDAP) layer, PDCP layer, RLC layer and MAC layer.

[0083] SDAP entity 404 at the SDAP layer can be retrieved from the core network ( Figure 4 Data received (not shown in the image) such as multicast data 402 or unicast data ( Figure 4 (not shown in the image) is mapped to one of the radio bearers, such as the MRB or DRB within the same PDU session. Figure 4 (Not shown in the image). In some examples, it can be obtained from the UPF used for multicast PDU sessions (…). Figure 4 (Not shown in the image) (such as MB-UPF) receives multicast data 402 (e.g., multicast QoS stream data). In Figure 4 In the example, SDAP entity 404 maps multicast data to one of the radio bearers (e.g., MRB). For ease of explanation, Figure 4 Only one radio bearer is shown in the diagram. Aspects of this disclosure are not limited to, for example... Figure 4 The MRB shown is shown.

[0084] PDCP entity 406 at the PDCP layer can perform various functions, such as Robust Header Compression (RoHC), security functions, and other functions. PDCP entity 406 communicates with RLC entity 408 or 410 via the RLC channel. In some implementations, such as... Figure 4 As shown, two distinct RLC entities 408 or 410 can be specified. Each RLC entity 408 and 410 can be associated with different RLC paths 422 and 424. In such an implementation, a first RLC entity 408 can be specified for the initial MBS transmission, and a second RLC entity 410 can be specified for MBS retransmission. Each RLC entity 408 and 410 can segment PDU packets, reassemble segmented PDU packets, and perform ARQ error control procedures. Additionally, each RLC entity 408 and 410 can support different transmission modes, such as Unacknowledged Mode (UM) and Acknowledged Mode (AM). In some examples, data units, such as PDCP PDUs, scheduled for the initial MBS transmission via the first RLC path 422 can be scheduled for all UEs in the MBS area. Additionally, as described, data units (such as PDCP PDUs) scheduled for MBS retransmission can be routed to the second RLC path 424. In some examples, retransmissions from the second RLC path 424 can be scheduled for a subset of UEs from all UEs in the MBS area. In other examples, retransmissions from the second RLC path 424 can be scheduled for all UEs in the MBS area. In such examples, a UE that has not sent a NACK for the initial transmission corresponding to the retransmission may not process the data received in the retransmission from the second RLC path 424.

[0085] exist Figure 4 In some examples, each MAC entity 412 and 414 may include a scheduler for scheduling and prioritizing packets received from RLC layer entities 408 and 410 via logical channels, such as a multicast broadcast traffic channel (MBTCH). In some examples, separate logical channels distinguish multicast data from unicast data. In some such examples, physical layer (PHY) 416 and 418 may encode multicast data 402 for transmission over channels, such as a downlink shared channel. In some examples, the channel may be scrambled using a group radio network temporary identifier (G-RNTI).

[0086] In some implementations, the UE can receive initial transmission parameters and retransmission parameters via RRC signaling. In such implementations, the initial transmission parameters may indicate whether network decoding is enabled for initial MBS transmission, and the retransmission parameters may indicate whether network decoding is enabled for MBS retransmission. Table 1 provides examples of parameter indications and corresponding network decoding (NC) according to various aspects of this disclosure.

[0087]

[0088] As shown in Table 1, in some examples, the initial transmission parameters may indicate that network decoding is disabled for initial transmissions from the first RLC entity, and the retransmission parameters may indicate that network decoding is disabled for retransmissions from the second RLC entity (e.g., option 0). In the present disclosure, retransmission may be an example of MBS retransmission, and the initial transmission may be an example of initial MBS transmission. In such examples, the MRB and the receiving device may handle the initial transmission and retransmission based on conventional techniques. In other examples, the initial transmission parameters may indicate that network decoding is disabled for initial transmissions from the first RLC entity, and the retransmission parameters may indicate that network decoding is enabled for retransmissions from the second RLC entity (e.g., option 1). In such examples, the MRB and the receiving device may handle the initial transmission based on conventional techniques. Additionally, in such examples, the MRB and the receiving device may handle retransmissions based on one or more aspects of this disclosure. In other examples, the initial transmission parameters may indicate that network decoding is enabled for initial transmissions from the first RLC entity, and the retransmission parameters may indicate that network decoding is disabled for retransmissions from the second RLC entity (e.g., option 2). In such examples, the MRB and the receiving device can process the initial transmission based on one or more aspects of this disclosure. Additionally, in such examples, the MRB and the receiving device can process retransmissions based on conventional techniques, such as NACK-enabled PDCP SDU or PDU retransmissions. In yet another example, initial transmission parameters can instruct network decoding to be enabled for initial transmissions from a first RLC entity, and retransmission parameters can instruct network decoding to be enabled for retransmissions from a second RLC entity (e.g., option 3). In such examples, the MRB and the receiving device can process both initial transmissions and retransmissions based on one or more aspects of this disclosure.

[0089] In some implementations, the transporter can apply network decoding functionality within the PDCP entity. In some examples, if network decoding is enabled only for the initial MBS transmission or for both the initial MBS transmission and MBS retransmission, a single data unit (such as a PDC PSDU) can generate multiple data units (such as PDCP PDUs). In some other examples, if network decoding is enabled only for MBS retransmission or for both the initial MBS transmission and MBS retransmission, network decoding can be applied to multiple source segments (such as different PDCP SDUs) to generate network-decoded data units (such as PDCP SDUs) for retransmission. In some still examples, if network decoding is enabled for both the initial MBS transmission and MBS retransmission, the network decoding function can be applied to source packets from a single data unit (e.g., a single PDC PSDU) or different data units (e.g., different PDCP SDUs) to generate one or more network-decoded data units (such as PDCP PDUs) for retransmission.

[0090] Figure 5A This is a block diagram illustrating examples of a transmitting PDCP entity 500 and a receiving PDCP entity 502 according to various aspects of this disclosure. The transmitting PDCP entity 500 may be a component of a transmitting device (such as a first UE or a first base station). The receiving PDCP entity 502 may be a component of a receiving device (such as a second UE or a second base station). The first UE and the second UE may be as described in reference... Figure 1 and Figure 2 The example of UE 120 described. The first base station and the second base station can be as shown in the reference. Figure 1 and Figure 2 The example of base station 110 described. The transmitting PDCP entity 500 can be as shown in the reference. Figure 4 An example of PDCP entity 406 as described. Figure 5A In the example, network decoding is disabled for the initial MBS transfer.

[0091] exist Figure 5A In the example, the transporter PDCP entity 500 can obtain data from an upper-level entity (such as reference 500). Figure 4 The described SDAP entity 404 receives data blocks (such as PDCP SDUs). Figure 5A As shown, the transport PDCP entity 500 can apply various functions to the received data block. In some examples, the transport PDCP entity 500 can temporarily store the data block in a transport buffer and assign a sequence number to the data block. The data block can be associated with the user plane or the control plane. Additionally, as... Figure 5AAs shown, the transport PDCP entity 500 can also compress the header of the data packet. In some examples, if the data packet is associated with a PDCP SDU, the transport PDCP entity 500 can perform security procedures by applying integrity protection and cryptography functions (e.g., encryption functions). The integrity protection and cryptography functions can be based on the sequence number associated with the data block.

[0092] exist Figure 5A In the example, the transmitting PDCP entity 500 may include network decoding functions for encoding data packets. Additionally, the transmitting PDCP entity 500 may include a retransmission buffer. Figure 5A In one example, network decoding is bypassed because it is disabled for the initial MBS transmission. In such examples, a PDCP header can be added to a data packet, and the data packet can be duplicated and routed to the receiver PDCP entity 502. In some other examples, if the data packet is not associated with a PDCP SDU, a PDCP header can be added to the output of the header compression function.

[0093] In some examples, data packets can be transmitted to the receiving PDCP entity 502 over a radio interface (e.g., a Uu interface or a PC5 interface). In such examples, the receiving PDCP entity 502 can receive data packets over the radio interface and can remove the PDCP header from the received data packets. Figure 5A As shown, the receiver PDCP entity 502 may include a network decoder. Figure 5A In some examples, network decoding can be bypassed because it is disabled for the initial MBS transmission. In some examples, the receiver PDCP entity 502 can decode the received data packets and apply integrity verification functions. The receiver PDCP entity 502 can also discard duplicate data packets, reorder data packets, and temporarily store data packets in a receive buffer. In some examples, the receiver PDCP entity 502 may include PDCP control functions for generating one or more status packets (such as PDCP status PDUs) indicating the status (such as the decoding status of the received data packets). The status packets can be transmitted to the sender PDCP entity 500 and stored in the retransmission buffer of the sender PDCP entity 500. The receiver PDCP entity 502 can also perform header decompression on the data packets and deliver the resulting data packets (such as PDCP SDUs) to the upper layer.

[0094] Figure 5BThis is a block diagram illustrating examples of a transmitting PDCP entity 500 and a receiving PDCP entity 502 according to various aspects of this disclosure. The transmitting PDCP entity 500 may be a component of a transmitting device (such as a first UE or a first base station). The receiving PDCP entity 502 may be a component of a receiving device (such as a second UE or a second base station). The first UE and the second UE may be... Figure 1 and Figure 2 The example of UE 120 described. The first base station and the second base station can be referenced. Figure 1 and Figure 2 The example of base station 110 described. The transmitting PDCP entity 500 can be as shown in the reference. Figure 4 An example of the described PDCP entity 406. Figure 5B The example shows the sending PDCP entity 500 and receiving PDCP entity 502 performing and referencing Figure 5A The same functionality as described. However, in Figure 5B In the example, network decoding is enabled for the initial MBS transfer. Therefore, in Figure 5B In the example, network decoding is enabled for the initial MBS transmission, and a network decoder encoder can be applied to data packets at the transport PDCP entity 500. In such examples, the network decoder encoder can generate multiple data packets based on a single data packet. As an example, the network decoder encoder function can be applied to a PDCP SDU to generate multiple PDCP PDUs. In some examples, a PDCP header can be added to each of the multiple data packets generated based on the network decoder encoder function. Additionally, multiple data packets (e.g., PDUs) can be routed to different RLC transport entities.

[0095] Additionally, in Figure 5B In the example, network decoding is enabled for the initial MBS transmission, and the network decoder can be applied to multiple data packets received at the receiver PDCP entity 502. In such an example, the network decoder can recover a single data packet from multiple data packets. As an example, the network decoder function can be applied to multiple PDCP PDUs to recover a PDCP SDU.

[0096] As described, the transporter PDCP entity (such as...) Figure 5A and Figure 5B The transmitting PDCP entity 500 can use network decoding functions to generate multiple data packets (such as PDCP PDUs) from a single packet (such as a single PDCP SDU). Figure 6AThis is a block diagram illustrating an example of a process 600 for generating multiple data packets from a single packet according to various aspects of this disclosure. Process 600 can be performed by a transport PDCP entity (such as referenced in [reference]). Figure 5A and 5B The described transporter PDCP entity 500) performs one or more functions to execute.

[0097] like Figure 6A As shown, process 600 may begin with: the network decoder encoder of the transmitting PDCP entity receiving a single data unit 602, such as a cryptographic PDCP SDU. In this disclosure, the data unit may be an example of a data packet. Additionally, process 600 may segment (e.g., partition) the single data unit 602 into K source segments 604 (1, ..., K). Each of the K source segments 604 (e.g., source packets) may have the same number of bits as the other source segments in the K source segments 604. In some examples, K may be determined based on the size of the single data unit 602 and the generator matrix. Figure 6A In the example, process 600 applies network decoding functionality to K source segments 604 to generate L encoded data units 606 (1,..., L). In some examples, the network decoding functionality can be fountain codes, Raptor codes, RaptorQ codes, or another type of rateless code. For example, in... Figure 6A As shown in the example, the number of L encoded data units 606 can be greater than the number of K source segments 604. In some examples, process 600 may add a header 610 to each encoded packet of the L encoded data units 606 to generate L data units 608 (e.g., L PDCP PDUs). A data unit refers to an encoded data unit that includes a header 610. The header 610 of each data unit in the L data units 608 may include a sequence number (SN) of a single data unit 602. The SN may be associated with a count value of a single data unit 602. Additionally, the header 610 of each data unit in the L data units 608 may include a sub-SN indicating an index value. Each data unit in the L data units 608 may be associated with a different index value. Figure 6A As shown, L data units 608 can be provided to lower layers (such as the RLC layer, MAC layer, and PHY layer) for additional processing. The RLC layer, MAC layer, and PHY layer can be the RLC path associated with the initial transmission (such as reference...). Figure 4 The layers of the first RLC path 422 described.

[0098] Figure 6BThis is a block diagram illustrating an example of a process 650 for generating a single data unit from multiple data units according to various aspects of this disclosure. Process 650 can be performed by a receiving PDCP entity (such as referenced in the diagram). Figure 5A and Figure 5B The described receiver PDCP entity 502) performs one or more functions to perform this function.

[0099] exist Figure 6B In some examples, process 650 may begin by receiving L data units 652 (1, ..., L) from a lower layer of the receiving device. In some examples, the lower layer may include a PHY layer, a MAC layer, and an RLC layer. The L data units 652 may be associated with an initial MBS transmission from the transmitting device. Additionally, in Figure 6B In the example, network decoding is enabled for the initial MBS transmission. In some examples, the receiving device can receive an indication that network decoding is enabled for the initial MBS transmission. This indication can be an RRC parameter. The L data units 652 can be encoded based on a network decoding function (such as fountain decoding or Raptor decoding), as shown in the reference. Figure 6A As described.

[0100] like Figure 6B As shown, after receiving L data units 652 at the receiving PDCP entity, process 650 can remove the header of each data unit (e.g., an encoded data unit) from the L data units 652. Then, process 650 can determine the total number of N received data units 654 (shown as encoded data units 1, ..., encoded data units L) based on the removal of the headers of each encoded data unit from the L data units 652. Figure 6B As shown, the total number of N received data units 654 may be less than the total number of L data units 652 because a subset of one or more data units 656 among the L data units 652 may be unavailable due to an error (such as a communication error) at one or both of the transmitting or receiving devices. In some examples, the total number of subsets of one or more data units 656 among the L data units 652 may be disregarded when determining the total number of N received data units 654. Figure 6B In the example, process 650 can be based on the premise that the total number of N received data units 654 is less than K source packets (such as reference). Figure 6A The total number of K source segments (604) that are segmented from a single data unit (such as a PDCP SDU) at the transmitting PDCP entity is used to identify decoding errors.

[0101] In some examples, such as Figure 6BAs shown, process 650 decodes N received data units 654 based on network decoding functionality to generate a set of K source segments 658. This set of K source segments 658 (e.g., source packets) may correspond to K source segments of a transmitting PDCP entity segmented from a single data unit (such as a PDCP SDU), such as referenced... Figure 6A The described K source segments 604. In some examples, process 650 may fail to recover a set of K source segments 658 due to decoding failure of the network decoding function. In some other examples, process 650 may reassemble a single data unit 660 (such as a PDCP SDU) from the set of K source segments 658 based on successful recovery (e.g., successful decoding). The single data unit 660 may be processed by the upper layers of the protocol stack of the receiving device.

[0102] Different network decoding functions (such as fountain codes, Raptor codes, or RaptorQ codes) can be associated with different estimated probabilities of recovery failure. In some examples, the estimated probability of recovery failure can be 100% based on the total number of N received data units 654 being less than the total number of K source packets. In other examples, the estimated probability of recovery failure can vary depending on the total number of N received data units 654 and the total number of K source packets, based on the total number of N received data units 654 being greater than or equal to the total number of K source packets. In some such examples, for Raptor codes, the estimated probability of recovery failure can be determined as... Where N is greater than or equal to K, N represents the total number of received data units (654), and K represents the total number of K source packets. In some other such examples, for RaptorQ codes, the estimated probability of recovery failure can be determined as... The value of N is greater than or equal to the value of K, where N represents the total number of received data units 654, and K represents the total number of K source packets.

[0103] exist Figure 6BIn the example, process 650 can trigger a retransmission based on an identification failure condition (such as decoding failure). In some such examples, a status packet (such as a PDCP status PDU) can indicate decoding failure. In such examples, the transmitting device can receive a status packet and initiate an MBS retransmission based on the received status packet. As described, a status packet (such as a PDCP status PDU) can be transmitted from the receiving device based on one or more data units satisfying a failure condition at the receiving PDCP entity. The status packet may include one or more parameters. In some examples, the status packet may include a header indicating that the packet is a status PDU. In some such examples, the state packet may also include one or more indications, including: an indication of each initial data unit in the initial data unit set associated with successful transmission (e.g., ACK), an indication of each initial data unit lost from the initial data unit set (e.g., NACK), an indication of the number of additional data units required for the UE to decode the initial data unit set (e.g., Required_NumPDU), an indication of the total number of successfully decoded initial data units from the initial data unit set (e.g., ACKed_NumPDU), an indication of each data unit in the initial data unit set lacking a sub-sequence number (sub-SN) (e.g., NACK_SubSN), or an indication of a rate adjustment command. NACK and ACK may be associated with the SN of a specific data unit. The rate adjustment command may adjust (e.g., increase or decrease) the encoded data units (such as, generated by the network decoder encoder) generated by the network decoder encoder. Figure 6A The number of L data units (606).

[0104] As shown in Table 1, in some examples, an RRC parameter (e.g., initial transmission parameter) can indicate whether network decoding is enabled for initial MBS transmissions, and another RRC parameter (e.g., retransmission parameter) can indicate whether network decoding is enabled for MBS retransmissions. In some examples, network decoding can be disabled for both initial MBS transmissions and MBS retransmissions. In such examples, MBS retransmissions can be regular data unit retransmissions, such as regular PDCP SDU retransmissions. In some other examples, network decoding can be disabled for MBS retransmissions and enabled for initial MBS transmissions. In some such examples, MBS retransmissions can be based on data units associated with NACK, such as PDCP SDUs. In other such examples, MBS retransmissions can be based on data units associated with NACK, such as PDCP PDUs. In other examples, network decoding can be disabled for initial MBS transmissions and enabled for MBS retransmissions. In some such examples, retransmissions can be PDCP SDU-level retransmissions, where the network-decoded data units (such as PDCP SDUs) used for retransmissions can be generated from different PDCP SDUs. In some other examples, network decoding can be enabled for both the initial MBS transmission and MBS retransmission. In some such examples, retransmission can be PDCP SDU-level retransmission, where network-decoded data units (such as PDCP SDUs) used for retransmission can be generated from different PDCP SDUs. In some other such examples, retransmission can be PDCP PDU-level retransmission, where network-decoded data units (such as PDCP PDUs) used for retransmission can be generated from source packets segmented from one data unit (such as a PDCP SDU) or multiple different data units.

[0105] Figure 7 This is a block diagram illustrating an example of PDCP SDU-level retransmission according to various aspects of this disclosure. Figure 7 PDCP SDU-level retransmission can be performed based on network decoding being enabled only for MBS retransmission (e.g., Option 1 in Table 1) or network decoding being enabled for both the initial MBS transmission and MBS retransmission (e.g., Option 3 in Table 1). As described, the transmitting PDCP entity (such as reference) Figure 5A and Figure 5B The described transmitting PDCP entity 500 can be obtained from the receiving PDCP entity (such as reference 500). Figure 5A and Figure 5B The described transmitter PDCP entity 500 receives status packets. In some examples, the status packets may indicate one or more data units, such as PDCP SDUs, associated with a NACK SN. In such examples, as... Figure 7As shown, the network decoder / encoder of the transmitting PDCP entity can treat each data unit (such as a PDCP SDU) associated with a NACK SN as a source packet (e.g., a source segment). Figure 7 In the example, each data unit in a set of K data units 700 (1, ..., K) can be associated with a NACK SN. In this example, the network decoder encoder can treat each data unit in the K data units 700 as a source packet. Additionally, the network decoder encoder can generate each parity data unit in a parity data unit set 702 from one or more data units in the K data units 700 based on network decoding capabilities. This parity data unit set 702 can be used for MBS retransmission from the transmitting device. In some examples, the receiving PDCP entity can recover each data unit associated with the NACK based on one or more parity data units in the parity data unit set 702 and one or more data units associated with the ACK from the initial MBS transmission.

[0106] As described, in some examples, MBS retransmission can be PDCP PDU-level retransmission. In such examples, network-decoded data units (such as PDCP PDUs) can be generated from source packets segmented from one data unit (such as PDCP SDU) or multiple different data units. Network-decoded data units can be retransmitted to the receiving device. In such examples, it can be based on a reference... Figure 6A The described process 600 generates network-decoded data units. However, in such examples, the network decoding function can generate X additional encoded data units (L+1, ..., L+X) based on K source segments 604. The number of X additional encoded data units generated for the initial transmission data unit (such as a PDCP SDU) associated with the NACK SN can be based on parameters of a state packet (e.g., a state PDU). In some examples, the number of X additional encoded data units can be based on a required number parameter of the state packet (such as a Required_NumPDU parameter), which indicates the number of encoded data units required at the receiving PDCP entity to recover the data unit of the initial MBS transmission associated with the NACK SN. In some examples, the X additional encoded data units can be generated from source segments (such as K source segments 604) from a single data unit (such as a single data unit 602). In some other examples, X additional encoded data units can be generated based on source grouping from different data units (such as a single data unit 602 and one or more other data units (e.g., PDCP SDU)). In some examples, the header (such as...) Figure 6AThe header 610 can be added to each encoded packet of X additional encoded data units to generate X additional data units (e.g., X PDCPPDUs). The X additional data units can be transmitted to the receiving device to recover the data units of the initial MBS transmission associated with the NACK SN.

[0107] Figure 8 This is a block diagram illustrating examples of a network decoder 800 according to various aspects of this disclosure. The network decoder 800 may be a receiver PDCP entity (such as referenced in the diagram). Figure 5A and Figure 5B The components of the described receiver PDCP entity 502. For example... Figure 8 As shown in the example, the network decoder 800 can be transmitted from the initial MBS transmission path 802 (such as...) Figure 4 The first RLC path 422) receives encoded packets (such as L data units 806 (e.g., the initial set of data units)) and retransmits them from the MBS retransmission path 804 (such as... Figure 4 The second RLC path 424 receives X data units 808 (e.g., a set of retransmitted data units). Figure 8 As shown, one or more of the received data units 806 and 808 can be associated with NACK (shown as a cross pattern), while other data units can be associated with ACK. In some examples, the network decoder 800 may only know the total number of encoded data units 806 and 808 received from both paths 802 and 804. In some such examples, encoded data units 806 and 808 corresponding to the same SN from both paths 802 and 804 can be aggregated at the network decoder 800 to form a data unit set 810 (p1, ..., p...). n ).exist Figure 8 In the example, a source segment set 812 (s1, ..., s) can be generated from the data unit set 810. n ).

[0108] In some examples, status packets (such as PDCP status PDUs) can be transmitted periodically or aperiodically. In some such examples, the transmission of status packets can be triggered based on the expiration of a periodic timer. In these examples, the transmitting device can configure the periodic timer via an indication transmitted in an RRC message or other type of signaling. In some other examples, aperiodic transmission of status packets can be triggered by a message transmitted from the transmitting PDCP entity.

[0109] In some examples, MBS retransmissions can be scheduled for a subset of UEs across all UEs in the MBS area. As an example, one or more data units associated with a SN can be scheduled only for MBS retransmissions to UEs transmitting a NACK SN corresponding to the SN of that one or more data units. In other examples, MBS retransmissions can be scheduled for a subset of UEs across all UEs in the MBS area. In some such examples, a UE may not process one or more data units associated with a SN in an MBS retransmission (if the UE has not transmitted a NACK SN corresponding to that SN of the one or more data units).

[0110] In some examples, two distinct pointers can be specified in the transport-side PDCP entity. A first pointer can be specified for the initial MBS transmission, and a second pointer can be specified for MBS retransmissions. After transmitting the coded packet associated with the first data unit, the first pointer can be incremented from the first data unit (such as a PDCP SDU) to a second data unit in a series of data units. The first pointer can be incremented after the initial MBS transmission corresponding to a specific data unit. The second pointer can be incremented after an MBS retransmission corresponding to a specific data unit. Additionally or alternatively, the second pointer can be incremented based on receiving an ACK (e.g., ACK_SN) indicating successful reception of a specific data unit. In some examples, after both the first and second pointers have incremented to a data unit with an SN greater than the SN of that specific data unit, the specific data unit can be discarded in the transport-side PDCP entity.

[0111] Figure 9 A block diagram of a wireless communication device 900 according to various aspects of this disclosure is shown. The wireless communication device 900 receives an initial MBS transmission from a first path of the MRB and receives MBS retransmissions from a second path of the MRB. The wireless communication device 900 may be a reference... Figure 1 and Figure 2 Examples of various aspects of the described UE 120. The wireless communication device 900 may include a receiver 910, a communication manager 915, and a transmitter 920, which can communicate with each other (e.g., via one or more buses). In some implementations, the receiver 910 and transmitter 920 may operate in conjunction with an OAM antenna 990. In some examples, the wireless communication device 900 is configured to perform operations including the following references. Figure 10 The described process is the operation of 1000.

[0112] In some examples, the wireless communication device 900 may include a chip, a system-on-a-chip (SoC), a chipset, a package, or a device including at least one processor and at least one modem (e.g., a 5G modem or other cellular modem). In some examples, the communication manager 915 or its sub-components may be separate and distinct components. In some examples, at least some components of the communication manager 915 are at least partially implemented as software stored in memory. For example, portions of one or more components of the communication manager 915 may be implemented as non-transient code executable by a processor to perform the function or operation of the respective component.

[0113] Receiver 910 can receive, via various channels including control channels (e.g., Physical Downlink Control Channel (PDCCH) and data channels (e.g., Physical Downlink Shared Channel (PDSCH))) from one or more other wireless communication devices, such as receiving one or more reference signals (e.g., periodically configured CSI-RS, aperiodically configured CSI-RS, or reference signals varying due to multi-beam configuration), synchronization signals (e.g., synchronization signal blocks (SSBs)), control information, and / or data information in packet form. Other wireless communication devices may include, but are not limited to, reference signals. Figure 1 and Figure 2 The other UE 120 or base station 110 described.

[0114] The received information can be transmitted to other components of the wireless communication device 900. The receiver 910 can be a reference... Figure 2 Examples of various aspects of the described receiver processor 258. Receiver 910 may include a set of antennas coupled to or otherwise utilizing (e.g., the set of antennas may be a reference antenna). Figure 2 Examples of various aspects of antennas 252a to 252r described herein constitute a set of radio frequency (RF) chains.

[0115] Transmitter 920 can transmit signals generated by communication manager 915 or other components of wireless communication device 900. In some examples, transmitter 920 may be co-located with receiver 910 in a transceiver. Figure 2 Examples of various aspects of the described transmit processor 264. Transmitter 920 may be coupled to or otherwise utilize a set of antennas (e.g., this set of antennas may be a reference antenna). Figure 2 Examples of various aspects of the described antennas 252a to 252r may be antenna elements shared with receiver 910. In some examples, transmitter 920 is configured to transmit control information in the Physical Uplink Control Channel (PUCCH) and data in the Physical Uplink Shared Channel (PUSCH).

[0116] Communication Manager 915 can be used as a reference Figure 2 Examples of various aspects of the described controller / processor 280. The communication manager 915 includes a network decoding component 925 and a data unit component 935. In some examples, operating in conjunction with a receiver 910, the network decoding component 925 can receive RRC signaling from the network device, including initial transmission parameters and retransmission parameters. The initial transmission parameters indicate whether the network decoding function is enabled for an initial transmission from a first RLC entity associated with the MRB, and the retransmission parameters indicate whether the network decoding function is enabled for retransmissions from a second RLC entity associated with the MRB. Additionally, operating in conjunction with the receiver 910, the data unit component 935 receives the initial transmission from the first RLC entity of the network device. In some examples, the initial transmission includes an initial set of data units. In some such examples, operating in conjunction with a transmitter 920, the data unit component 935 transmits status data units to the network device, including a set of status indicators. In some examples, one or more status indicators in the status indicator set indicate a reception failure based on the initial data unit set satisfying a failure condition. Furthermore, in some examples, working in conjunction with receiver 910, data unit component 935 receives retransmissions, including a set of retransmitted data units, from a second RLC entity of the network device. In some examples, both retransmissions and sets of retransmitted data units can be received based on one or more indications of reception failure in status indicators.

[0117] Figure 10 This is a flowchart illustrating an example process 1000 performed, for example, by a receiving device according to various aspects of this disclosure. Example process 1000 is an example of receiving an initial MBS transmission from a first path of the MRB and receiving an MBS retransmission from a second path of the MRB according to various aspects of this disclosure. In some implementations, process 1000 may be performed by a receiving device (such as those described above, referred to separately). Figure 1 and Figure 2 The UE 120 described above and (refer to the above respectively) Figure 5A and Figure 5B The described receiver PDCP entity 502 performs this action.

[0118] In some implementations, process 1000 begins at block 1002 with receiving RRC signaling from the network device, including initial transmission parameters and retransmission parameters. The initial transmission parameters indicate whether network decoding is enabled for initial transmissions from a first RLC entity associated with the MRB, and the retransmission parameters indicate whether retransmissions are enabled for retransmissions from a second RLC entity associated with the MRB. At block 1004, process 1000 receives the initial transmission from the first RLC entity of the network device. In some examples, the initial transmission includes an initial set of data units. At block 1006, process 1000 transmits status data units, including a set of status indicators, to the network device. In some examples, one or more status indicators in the status indicator set indicate a reception failure based on the initial data unit set meeting a failure condition. At block 1008, process 1000 receives retransmissions, including a set of retransmitted data units, from the second RLC entity of the network device. In some examples, both retransmissions and the set of retransmitted data units may be received based on one or more of the status indicators indicating a reception failure.

[0119] Figure 11 A block diagram of a wireless communication device 1100 according to various aspects of this disclosure is shown, which transmits initial MBS transmissions from a first path of the MRB and transmits MBS retransmissions from a second path of the MRB. The wireless communication device 1100 may be a reference... Figure 1 and Figure 2 Examples of various aspects of the described base station 110. The wireless communication device 1100 may include a receiver 1110, a communication manager 1115, and a transmitter 1120, which may communicate with each other (e.g., via one or more buses). In some examples, the wireless communication device 1100 is configured to perform operations including the following references. Figure 12 The described process is the operation of 1200.

[0120] In some examples, the wireless communication device 1100 may include a chip, a system-on-a-chip (SoC), a chipset, a package, or a device including at least one processor and at least one modem (e.g., a 5G modem or other cellular modem). In some examples, the communication manager 1115 or its sub-components may be separate and distinct components. In some examples, at least some components of the communication manager 1115 are at least partially implemented as software stored in memory. For example, portions of one or more components of the communication manager 1115 may be implemented as non-transient code executable by a processor to perform the function or operation of the respective component.

[0121] Receiver 1110 can receive, via various channels including control channels (e.g., PDCCH) and data channels (e.g., PDSCH), one or more of the following in packet form: reference signals (e.g., periodically configured CSI-RS, aperiodically configured CSI-RS, or reference signals varying due to multi-beam configuration), synchronization signals (e.g., synchronization signal blocks (SSBs)), control information, and / or data information. Other wireless communication devices may include, but are not limited to, reference signals. Figure 1 and Figure 2 The other base station 110 or UE 120 described.

[0122] The received information can be transmitted to other components of the wireless communication device 1100. The receiver 1110 can be a reference... Figure 2 Examples of various aspects of the described receiver processor 238. Receiver 1110 may include a set of antennas coupled to or otherwise utilizing (e.g., the set of antennas may be a reference antenna). Figure 2 Examples of various aspects of antennas 234a to 234t described herein constitute a set of radio frequency (RF) chains.

[0123] Transmitter 1120 can transmit signals generated by communication manager 1115 or other components of wireless communication device 1100. In some examples, transmitter 1120 may be co-located with receiver 1110 in a transceiver. Transmitter 1120 may be a reference Figure 2 Examples of various aspects of the described transmit processor 220. Transmitter 1120 may be coupled to or otherwise utilize a set of antennas (e.g., this set of antennas may be examples of various aspects of antennas 234a to 234t), which may be antenna elements shared with receiver 1110. In some examples, transmitter 1120 is configured to transmit control information in the Physical Uplink Control Channel (PUCCH) and data in the Physical Uplink Shared Channel (PUSCH).

[0124] Communication Manager 1115 can be a reference Figure 2Examples of various aspects of the described controller / processor 240. The communication manager 1115 includes a network decoding component 1125 and a data unit component 1135. In some examples, operating in conjunction with the transmitter 1120, the network decoding component 1125 transmits RRC signaling from the network device to the UE, including initial transmission parameters and retransmission parameters. The initial transmission parameters indicate whether the network decoding function is enabled for an initial transmission from the network device to a first RLC entity associated with the MRB, and the retransmission parameters indicate whether the network decoding function is enabled for a second RLC entity associated with the MRB from the network device. In some examples, operating in conjunction with the transmitter 1120, the data unit component 1135 transmits an initial set of data units associated with the initial transmission to the UE from the first RLC entity. Additionally, operating in conjunction with the receiver 1110, the data unit component 1135 receives status data units from the UE, including a set of status indicators. In some examples, one or more status indicators in the set of status indicators indicate reception failure. Furthermore, operating in conjunction with transmitter 1120, data unit component 1135 transmits a set of retransmission data units associated with retransmission from the second RLC entity to the UE. In some examples, the set of retransmission data units may be transmitted based on one or more status indicators indicating reception failure.

[0125] Figure 12 This is a flowchart illustrating an example process 1200 performed, for example, by a receiving device according to various aspects of this disclosure. Example process 1200 is an example of transmitting an initial MBS transmission from a first path of the MRB and transmitting an MBS retransmission from a second path of the MRB according to various aspects of this disclosure. In some implementations, process 1200 may be performed by a receiving device (such as those described above, referred to separately). Figure 1 and Figure 2 The described base station) and (refer to the above respectively) Figure 5A and Figure 5B The described PDCP entity 500 is used to execute this.

[0126] In some implementations, process 1200 begins at block 1202 with the transmission of RRC signaling from the network device to the UE, including initial transmission parameters and retransmission parameters. The initial transmission parameters indicate whether the network decoding function is enabled for initial transmissions from a first RLC entity associated with the MRB from the network device, and the retransmission parameters indicate whether the network decoding function is enabled for retransmissions from a second RLC entity associated with the MRB from the network device. At block 1204, process 1200 transmits an initial data element set associated with the initial transmission from the first RLC entity to the UE. At block 1206, process 1200 receives a status data element set including a status indicator set from the UE. In some examples, one or more status indicators in the status indicator set indicate reception failure. At block 1208, process 1200 transmits a retransmission data element set associated with retransmission from the second RLC entity to the UE. In some examples, the retransmission data element set may be transmitted based on the one or more status indicators indicating reception failure.

[0127] The following provides an overview of some aspects of this disclosure: Aspect 1. A wireless communication method performed by a UE, comprising: receiving from a network device RRC signaling including initial transmission parameters and retransmission parameters, the initial transmission parameters indicating whether a network decoding function is enabled for an initial transmission from a first RLC entity associated with an MRB, the retransmission parameters indicating whether a network decoding function is enabled for a retransmission from a second RLC entity associated with the MRB; receiving the initial transmission from the first RLC entity of the network device, the initial transmission including an initial data unit set; transmitting to the network device a status data unit including a status indicator set, one or more status indicators in the status indicator set indicating a reception failure based on the initial data unit set satisfying a failure condition; and receiving from the second RLC entity of the network device a retransmission including a retransmission data unit set, both the retransmission and the retransmission data unit set being received based on the one or more status indicators indicating the reception failure.

[0128] Aspect 2. The method of Aspect 1, wherein one or more data units are reconstructed by decoding and combining one or more retransmitted data units in the set of retransmitted data units and one or more initial data units in the set of initial data units.

[0129] Aspect 3. The method of any one of Aspects 1-2, wherein: the set of status indicators includes one or more of the following: an indication of each initial data unit in the initial data unit set associated with successful reception, an indication of each initial data unit lost from the initial data unit set, an indication of the number of additional data units required for the UE to decode the initial data unit set, an indication of the total number of initial data units successfully decoded from the initial data unit set, an indication of each data unit in the initial data unit set lacking a sub-serial number (sub-SN), or an indication of a rate adjustment command.

[0130] Aspect 4. The method of aspect 3, wherein the total number of the retransmitted data unit set is based on the indication of the number of additional data units.

[0131] Aspect 5. The method of any one of Aspects 1-4, wherein: the initial transmission parameter indicates that the network decoding function is enabled for the initial transmission; based on the network decoding function being enabled for the initial transmission, the initial data unit set includes two or more initial data units; and the method further includes generating a generator matrix associated with the network decoding function based on receiving the initial data unit set.

[0132] Aspect 6. The method of aspect 5 further includes determining a quantity threshold based on the generator matrix, wherein the initial data unit set satisfies a failure condition based on the total number of the initial data unit set being less than the quantity threshold.

[0133] Aspect 7. The method of aspect 5 further includes decoding the initial set of data units based on the generator matrix to reconstruct the source segment set to generate one or more data units, wherein the initial set of data units satisfies the failure condition based on the inability to reconstruct the source segment set.

[0134] Aspect 8. The method of any one of Aspects 5-7 further includes: reconstructing one or more source segments in the source segment set based on the retransmission data unit set and the initial data unit set, wherein: the retransmission parameter indicates that the network decoding function is enabled for the retransmission; and based on the network decoding function being enabled for the retransmission, the retransmission data unit set includes one or more retransmission data units.

[0135] Aspect 9. The method of aspect 8, wherein each retransmitted data unit in the set of retransmitted data units is a parity data unit.

[0136] Aspect 10. The method of aspect 8, wherein the initial data unit set and the retransmitted data unit set include the same sequence number associated with the count value.

[0137] Aspect 11. The method of aspect 10, wherein the set of retransmitted data units corresponds to a set of source segments at the network device, and each source segment in the set of source segments at the network device is associated with a single source data unit.

[0138] Aspect 12. The method of aspect 10, wherein the set of retransmitted data units corresponds to a set of source segments at the network device, and each source segment in the set of source segments at the network device is associated with a plurality of source data units.

[0139] Aspect 13. The method of any one of Aspects 1-3, wherein: the retransmission parameter indicates that the network decoding function is enabled for the retransmission, and the initial transmission parameter indicates that the network decoding function is disabled for the initial transmission; based on the network decoding function being enabled for the retransmission, the set of retransmission data units includes one or more retransmission data units; each retransmission data unit in the set of retransmission data units is a parity data unit; and the method further includes reconstructing one or more source segments in the set of source segments.

[0140] Aspect 14. The method of any one of Aspects 1-13, wherein: the state data unit is one of a plurality of state data units that are periodically transmitted based on a timer.

[0141] Aspect 15. The method of any one of Aspects 1-13, wherein: the state data unit is one of a plurality of state data units, each of the plurality of state data units being transmitted aperiodically based on a corresponding trigger received from the MRB.

[0142] Aspect 16. A method for wireless communication performed by a network device, comprising: transmitting from the network device to a UE an RRC signaling including initial transmission parameters and retransmission parameters, the initial transmission parameters indicating whether an initial transmission of a network decoding function for an initial transmission from a first RLC entity associated with an MRB of the network device is enabled, and the retransmission parameters indicating whether a retransmission of the network decoding function for a second RLC entity associated with the MRB of the network device is enabled; transmitting from the first RLC entity to the UE an initial data element set associated with the initial transmission; receiving from the UE a status data element including a set of status indicators, one or more of the status indicators indicating a reception failure; and transmitting from the second RLC entity to the UE a retransmission data element set associated with the retransmission, the retransmission data element set being transmitted based on the one or more status indicators indicating the reception failure.

[0143] Aspect 17. The method of aspect 16, wherein the set of status indicators includes one or more of the following: an indication of each initial data unit in the initial data unit set associated with successful reception, an indication of each initial data unit lost from the initial data unit set, an indication of the number of additional data units required for the UE to decode the initial data unit set, an indication of the total number of initial data units successfully decoded from the initial data unit set, an indication of each initial data unit in the initial data unit set lacking a sub-sequence number, or an indication of a rate adjustment command.

[0144] Aspect 18. The method of aspect 17, wherein the total number of the retransmitted data unit set is based on an indication of the number of additional data units.

[0145] Aspect 19. The method of any one of Aspects 16-18, wherein: the RRC signaling indicates that the network decoding function is enabled for the transmission parameters; and based on the network decoding function being enabled for the initial transmission, the initial data unit set includes two or more initial data units.

[0146] Aspect 20. The method of Aspect 19 further includes: segmenting source data units at a Packet Data Convergence Protocol (PDCP) entity of the network device; and encoding the initial data unit set at the PDCP entity of the network device based on applying the network decoding function to a first set of source segments associated with the source data unit, wherein: each initial data unit in the initial data unit set includes a sequence number associated with the source data unit and a corresponding distinct sub-sequence number among a plurality of sub-sequence numbers; and the total number of sub-sequence numbers is equal to the total number of the initial data unit set.

[0147] Aspect 21. The method of aspect 20, wherein the total number of the first source segment set is less than the total number of the initial data unit set.

[0148] Aspect 22. The method of aspect 20, wherein: the RRC signaling indicates that the network decoding function is enabled for the retransmission; and based on the network decoding function being enabled for the retransmission, the retransmission data unit set includes one or more retransmission data units.

[0149] Aspect 23. The method of aspect 22 further includes constructing a parity data unit set at the PDCP entity based on one or more source segments in the first source segment set, wherein: each source segment in the one or more source segments corresponding to a negative acknowledgment is associated with a corresponding different status indicator in the status indicator set; and each retransmission data unit in the retransmission data unit set is a corresponding different parity data unit in the parity data unit set.

[0150] Aspect 24. The method of aspect 23 further includes: segmenting one or more source data units at the PDCP entity; and encoding the set of retransmission units at the PDCP entity based on applying the network decoding function to a second set of source segments associated with the one or more source data units.

[0151] Aspect 25. The method of Aspect 19 further includes, at the Packet Data Convergence Protocol (PDCP) entity of the network device, constructing a parity data unit set based on one or more source segments in a source segment set, wherein the RRC signaling indicates that the network decoding function is enabled for the retransmission and the network decoding function is disabled for the initial transmission; based on the network decoding function being enabled for the retransmission, the retransmission data unit set includes one or more retransmission data units; each source segment in the source segment set corresponding to a negative acknowledgment is associated with a corresponding different status indicator in the status indicator set; and each retransmission data unit in the retransmission data unit set is a corresponding different parity data unit in the parity data unit set.

[0152] Aspect 26. The method of any one of Aspects 16-25 further includes: transmitting to the UE a configuration for a periodic feedback timer; and receiving the state data unit based on the expiration of the periodic feedback timer.

[0153] Aspect 27. The method of any one of Aspects 16-25 further includes: transmitting a signal to the UE to trigger the transmission of the state data unit; and receiving the state data unit from the UE based on the transmission of the trigger.

[0154] Aspect 28. The method of any one of Aspects 16-27 further includes: scheduling the retransmission regardless of the received state data unit.

[0155] The foregoing disclosure provides explanations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the foregoing disclosure or may be obtained through practice.

[0156] As used, the term "component" is intended to be interpreted broadly as hardware, firmware, and / or a combination of hardware and software. As used, a processor is implemented using hardware, firmware, and / or a combination of hardware and software.

[0157] Some aspects are described in conjunction with thresholds. As used, depending on the context, satisfying a threshold can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0158] It will be apparent that the described systems and / or methods can be implemented in various forms, including hardware, firmware, and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited in any aspect. Thus, the operation and behavior of these systems and / or methods are described without reference to any specific software code—it is understood that software and hardware can be designed to implement these systems and / or methods, at least in part, based on this description.

[0159] Although specific combinations of features are described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of aspects. In fact, many of these features can be combined in ways not specifically described in the claims and / or disclosed in the specification. Although each dependent claim listed below may be directly subordinated to only one claim, the disclosure of aspects includes each dependent claim being combined with each other claim in this set of claims. The phrase “at least one of” refers to any combination of these items, including single members. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0160] The elements, actions, or instructions used should not be interpreted as critical or necessary unless explicitly stated otherwise. Furthermore, as used, the articles “a” and “a certain” are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and may be used interchangeably with “one or more.” In cases where only one item is intended, the phrase “only one” or similar language is used. Moreover, as used, the terms “have,” “contain,” “include,” etc., are intended to be open-ended terms. Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated.

Claims

1. A method for wireless communication performed by a user equipment (UE), comprising: The network device receives radio resource control (RRC) signaling including initial transmission parameters and retransmission parameters. The initial transmission parameters indicate whether the network decoding function is enabled for initial transmissions from a first radio link control (RLC) entity associated with a multicast radio bearer (MRB), and the retransmission parameters indicate whether the network decoding function is enabled for retransmissions from a second RLC entity associated with the MRB. The initial transmission is received from the first RLC entity of the network device, the initial transmission including an initial set of data units; A status data unit comprising a set of status indicators is transmitted to the network device, wherein one or more status indicators in the set of status indicators indicate reception failure based on the initial data unit set satisfying a failure condition; as well as The retransmission, comprising a set of retransmission data units, is received from the second RLC entity of the network device, both the retransmission and the set of retransmission data units being received based on the one or more status indicators indicating a reception failure.

2. The method as described in claim 1, wherein one or more data units are reconstructed by decoding and combining one or more retransmitted data units in the set of retransmitted data units and one or more initial data units in the set of initial data units.

3. The method of claim 1, wherein the set of status indicators includes one or more of the following: an indication of each initial data unit in the initial data unit set associated with successful reception, an indication of each initial data unit lost from the initial data unit set, an indication of the number of additional data units required by the UE to decode the initial data unit set, an indication of the total number of successfully decoded initial data units from the initial data unit set, an indication of each data unit in the initial data unit set lacking a sub-serial number (sub-SN), or an indication of a rate adjustment command.

4. The method of claim 3, wherein the total number of the retransmitted data unit set is based on the indication of the number of additional data units.

5. The method of claim 1, wherein: The initial transmission parameters indicate that the network decoding function is enabled for the initial transmission; Based on the network decoding function being enabled for the initial transmission, the initial data unit set includes two or more initial data units; and The method further includes generating a generator matrix associated with the network decoding function based on the received initial set of data units.

6. The method of claim 5, further comprising determining a quantity threshold based on the generator matrix, wherein the initial data unit set satisfies the failure condition based on the total number of the initial data unit set being less than the quantity threshold.

7. The method of claim 5, further comprising decoding the initial data unit set based on the generator matrix to reconstruct the source segment set to generate one or more data units, wherein the initial data unit set satisfies the failure condition based on the inability to reconstruct the source segment set.

8. The method of claim 5, further comprising reconstructing one or more source segments in the source segment set based on the retransmitted data unit set and the initial data unit set. in: The retransmission parameter indicates that the network decoding function is enabled for the retransmission; and Based on the network decoding function, retransmission is enabled, and the retransmission data unit set includes one or more retransmission data units.

9. The method of claim 8, wherein each retransmission data unit in the set of retransmission data units is a parity data unit.

10. The method of claim 8, wherein the initial data unit set and the retransmission data unit set include the same sequence number associated with the count value.

11. The method of claim 10, wherein the set of retransmitted data units corresponds to a set of source segments at the network device, and each source segment in the set of source segments at the network device is associated with a single source data unit.

12. The method of claim 10, wherein the set of retransmitted data units corresponds to a set of source segments at the network device, and each source segment in the set of source segments at the network device is associated with a plurality of source data units.

13. The method of claim 1, wherein: The retransmission parameter indicates that the network decoding function is enabled for the retransmission, and the initial transmission parameter indicates that the network decoding function is disabled for the initial transmission; Based on the network decoding function, retransmission is enabled, and the retransmission data unit set includes one or more retransmission data units. Each retransmitted data unit in the set of retransmitted data units is a parity data unit; and The method further includes reconstructing one or more source segments in the source segment set.

14. The method of claim 1, wherein the state data unit is one of a plurality of state data units that are periodically transmitted based on a timer.

15. The method of claim 1, wherein the state data unit is one of a plurality of state data units, each of the plurality of state data units being transmitted non-periodically based on a corresponding trigger received from the MRB.

16. An apparatus for conducting wireless communication at a user equipment (UE), comprising: processor; Memory coupled to the processor; as well as Instructions, which are stored in the memory and, when executed by the processor, are operable to cause the device to: The network device receives radio resource control (RRC) signaling including initial transmission parameters and retransmission parameters. The initial transmission parameters indicate whether the network decoding function is enabled for initial transmissions from a first radio link control (RLC) entity associated with a multicast radio bearer (MRB), and the retransmission parameters indicate whether the network decoding function is enabled for retransmissions from a second RLC entity associated with the MRB. The initial transmission is received from the first RLC entity of the network device, the initial transmission including an initial set of data units; A status data unit comprising a set of status indicators is transmitted to the network device, wherein one or more status indicators in the set of status indicators indicate reception failure based on the initial data unit set satisfying a failure condition; as well as The retransmission, comprising a set of retransmission data units, is received from the second RLC entity of the network device, both the retransmission and the set of retransmission data units being received based on the one or more status indicators indicating a reception failure.

17. A method for wireless communication performed by a network device, comprising: Radio Resource Control (RRC) signaling, including initial transmission parameters and retransmission parameters, is transmitted from the network device to the user equipment (UE). The initial transmission parameters indicate whether the network decoding function is enabled for initial transmissions from a first Radio Link Control (RLC) entity associated with a multicast radio bearer (MRB) of the network device, and the retransmission parameters indicate whether the network decoding function is enabled for retransmissions from a second RLC entity associated with the MRB of the network device. The initial set of data units associated with the initial transmission is transmitted from the first RLC entity to the UE; The UE receives a status data unit including a set of status indicators, wherein one or more status indicators in the set indicate a reception failure; as well as The second RLC entity transmits a set of retransmission data units associated with the retransmission to the UE, the set of retransmission data units being transmitted based on the one or more status indicators indicating the reception failure.

18. The method of claim 17, wherein the set of status indicators includes one or more of the following: an indication of each initial data unit in the initial data unit set associated with successful reception, an indication of each initial data unit lost from the initial data unit set, an indication of the number of additional data units required by the UE to decode the initial data unit set, an indication of the total number of initial data units successfully decoded from the initial data unit set, an indication of each initial data unit in the initial data unit set lacking a sub-serial number (sub-SN), or an indication of a rate adjustment command.

19. The method of claim 18, wherein the total number of the retransmitted data unit set is based on the indication of the number of additional data units.

20. The method of claim 17, wherein: The RRC signaling indicates that the network decoding function is enabled for the initial transmission; and The network decoding function is enabled for the initial transmission, and the initial data unit set includes two or more initial data units.

21. The method of claim 20, further comprising: The source data units are segmented at the Packet Data Convergence Protocol (PDCP) entity of the network device; as well as At the PDCP entity of the network device, the initial data unit set is encoded based on applying the network decoding function to a first source segment set associated with the source data unit. in: Each initial data unit in the initial data unit set includes a sequence number associated with the source data unit and a corresponding distinct sub-sequence number from a plurality of sub-sequence numbers; and The total number of sub-sequence numbers is equal to the total number of the initial data unit set.

22. The method of claim 21, wherein the total number of the first source segment set is less than the total number of the initial data unit set.

23. The method of claim 21, wherein: The RRC signaling indicates that the network decoding function is enabled for the retransmission; and Based on the network decoding function, retransmission is enabled, and the retransmission data unit set includes one or more retransmission data units.

24. The method of claim 23, further comprising constructing a parity data unit set at the PDCP entity based on one or more source segments from the first source segment set. in: Each source segment corresponding to a negative acceptance in the one or more source segments is associated with a different corresponding state indicator in the set of state indicators; and Each retransmitted data unit in the set of retransmitted data units is a corresponding different parity data unit in the set of parity data units.

25. The method of claim 23, further comprising: Segment one or more source data units at the PDCP entity; as well as At the PDCP entity, the set of retransmission units is encoded based on applying the network decoding function to a second set of source segments associated with the one or more source data units.

26. The method of claim 17, further comprising, at the Packet Data Convergence Protocol (PDCP) entity of the network device, constructing a parity data unit set based on one or more source segments from the source segment set. in: The RRC signaling indicates that the network decoding function is enabled for the retransmission and disabled for the initial transmission; Based on the network decoding function, retransmission is enabled, and the retransmission data unit set includes one or more retransmission data units. Each source segment in the source segment set corresponding to a negative acceptance is associated with a different corresponding state indicator in the state indicator set; and Each retransmitted data unit in the set of retransmitted data units is a corresponding different parity data unit in the set of parity data units.

27. The method of claim 17, further comprising: The configuration for the periodic feedback timer is transmitted to the UE; as well as The status data unit is received based on the expiration of the periodic feedback timer.

28. The method of claim 17, further comprising: A signal is transmitted to the UE to trigger the transmission of the status data unit; as well as The status data unit is received from the UE based on the triggering of the transmission.

29. The method of claim 17, further comprising scheduling the retransmission regardless of the received status data unit.

30. An apparatus for wireless communication at a network device, comprising: processor; Memory coupled to the processor; as well as Instructions, which are stored in the memory and, when executed by the processor, are operable to cause the device to: Radio Resource Control (RRC) signaling, including initial transmission parameters and retransmission parameters, is transmitted from the network device to the user equipment (UE). The initial transmission parameters indicate whether the network decoding function is enabled for initial transmissions from a first Radio Link Control (RLC) entity associated with a multicast radio bearer (MRB) of the network device, and the retransmission parameters indicate whether the network decoding function is enabled for retransmissions from a second RLC entity associated with the MRB of the network device. The initial set of data units associated with the initial transmission is transmitted from the first RLC entity to the UE; The UE receives a status data unit including a set of status indicators, wherein one or more status indicators in the set indicate a reception failure; as well as The second RLC entity transmits a set of retransmission data units associated with the retransmission to the UE, the set of retransmission data units being transmitted based on the one or more status indicators indicating the reception failure.

Images