Techniques for signaling related to quality of service flow to data radio bearer mapping updates

Abstract

The present disclosure relates to techniques for signaling related to quality of service flow to data radio bearer mapping updates. The present application relates to devices and components, including apparatuses, systems, and methods for techniques for signaling related to quality of service flow to data radio bearer mapping updates in wireless networks.

Description

Background Technology

[0001] The 3GPP Technical Specifications (TS) define the standards for New Radio (NR) wireless networks. These TSs describe aspects related to operation at each layer of the protocol stack. Layer 2 (L2) of NR networks is divided into various sublayers, including: Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Serving Data Adaptation Protocol (SDAP). Attached Figure Description

[0002] Figure 1 A network environment according to some implementation schemes is shown.

[0003] Figure 2 The uplink and downlink SDAP data protocol data units (PDUs) and SDAP control PDUs according to some implementation schemes are shown.

[0004] Figure 3 The diagram illustrates message flows that include Quality of Service (QoS) flow remapping to Data Radio Bearer (DRB) according to some implementation schemes.

[0005] Figure 4 The operational flow / algorithm structure according to some implementation schemes is shown.

[0006] Figure 5 Another operational flow / algorithm structure according to some implementation schemes is shown.

[0007] Figure 6 Another operational flow / algorithm structure according to some implementation schemes is shown.

[0008] Figure 7 User equipment according to some implementation schemes is shown.

[0009] Figure 8 A base station according to some implementation schemes is shown. Detailed Implementation

[0010] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as particular structures, architectures, interfaces, and techniques, are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrases “A / B” and “A or B” refer to (A), (B), or (A and B).

[0011] The following is a glossary of terms that may be used in this disclosure.

[0012] As used herein, the term "circuit" refers to a portion of or includes said hardware component configured to provide the described functionality. Hardware components may include electronic circuitry, logic circuitry, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-a-chip (SoCs)), or digital signal processors (DSPs). In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the said functionality. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functionality (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0013] As used herein, the term "processor circuit" means, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures).

[0014] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, and network interface cards.

[0015] As used herein, the term "user equipment" or "UE" refers to equipment having radio communication capabilities that allow a user to access network resources within a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device. Furthermore, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0016] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to the various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0017] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a particular device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database, and application or workload units. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualized infrastructure to applications, devices, or systems. The terms "network resource" or "communication resource" can refer to resources accessible by a computer device / system via a communication network. The term "system resource" can refer to any kind of shared entity providing a service and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0018] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices used for transmitting and receiving information.

[0019] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0020] The term "connection" can mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0021] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, network hardware, network equipment, network node, or virtualized network function.

[0022] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or the data element that contains that content. An information element may include one or more additional information elements.

[0023] Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include a UE 104, which is communicatively coupled to a base station, such as base station 108. UE 104 and base station 108 may communicate via air interfaces compatible with 3GPP TS, such as those defining fifth-generation (5G) NR system standards. Base station 108 may be a next-generation node B (gNB) to provide one or more 5G air interface (NR) cells, thereby providing NR user plane and control plane protocol terminals to UE 104.

[0024] Network environment 100 may also include a core network (CN) 112. For example, CN 112 may include a 5th generation core network (5GC). CN 112 may be coupled to base station 108 via fiber optic or wireless backhaul. CN 112 may provide functions to UE 104 via base station 108. These functions may include managing subscriber profile information, subscriber location, service authentication, or handover functions for voice and data sessions.

[0025] Base station 108 may have circuitry such as BS L2 116 to implement L2 functions, including SDAP, PDCP, RLC, and MAC sublayer functions. Similarly, UE 104 may have circuitry such as UE L2 120 to implement similar L2 functions, enabling UE 104 and base station 108 to be communicatively coupled via transport channels, logical channels, RLC channels, radio bearers, and Quality of Service (QoS) streams.

[0026] In short, the MAC sublayer manages scheduling / priority handling, (de)multiplexing, and HARQ processes between logical and transport channels. The RLC sublayer manages (re)segmentation and error correction via Automatic Repeat Request (ARQ) between logical and RLC channels. The PDCP sublayer manages robust header (de)compression and security between the Data Radio Bearer (DRB) and RLC channels. The SDAP sublayer manages QoS flow handling between QoS flows and DRBs. In the downlink, the sublayer converts Service Data Units (SDUs) into Protocol Data Units (PDUs) for use with lower sublayers. In the uplink, the sublayer converts PDUs into SDUs for use with upper sublayers.

[0027] Unless otherwise described, the operation of the SDAP sublayer is consistent with that described in 3GPP TS 37.324 v16.3.0 (2021-06).

[0028] In the uplink, the transport SDAP entity can receive SDAP SDUs from the upper layer for a specific QoS flow. The SDAP entity can then map the SDAP SDU to the default DRB if no QoS flow-to-DRB mapping rule exists for the QoS flow, or map it to the DRB indicated by the mapping rule if a QoS flow-to-DRB mapping rule exists. The QoS flow-to-DRB mapping can be reflective (e.g., a UL mapping can be defined as the same as a DL mapping) or configured by the RRC layer.

[0029] TS 37.324 defines SDAP-specific SDAP end-mark control PDUs that are applied to QoS at the access layer. Subclauses 5.3.1 and 5.3.2 of TS 37.324 describe various rules for inserting end-markers into the DRB. Generally, when the QoS flow to DRB mapping rules change, end-markers applicable to both reflection and RRC configuration QoS mappings can be inserted into the DRB.

[0030] Figure 2A downlink (DL) SDAP data PDU 200 with a configured SDAP header is shown according to some implementation schemes. The first octet may be an SDAP header, which includes a Reflect QoS Flow to Data Radio Bearer Mapping Indicator (RDI) field, a Reflect QoS Indicator (RQI) field, and a QoS Flow Indicator (QFI) field. Base station 108 can use the RDI field to redirect a specific QoS flow from one DRB to another. This can be used to enhance QoS handling within a time window.

[0031] When the RDI bit is set in the DL SDAP header, uplink packets belonging to the same QFI can be redirected by UE 104 to the same DRB on which DL packets are received.

[0032] Figure 2 An uplink (UL) SDAP data PDU 202 with a configured SDAP header, according to some implementations, is also shown. The first eight-bit byte may include: a D / C field having bits for indicating whether the UL SDAP PDU is an SDAP data PDU or an SDAP control PDU; a reserved field; and a six-bit QFI field for indicating an identifier of the QoS flow to which the SDAP PDU belongs.

[0033] Figure 2 The End Marking Control PDU 204 is also shown, which includes: a D / C field with bits indicating whether the SDAP PDU is an SDAP data PDU or an SDAP control PDU; a reserved field; and a six-bit QFI field indicating the identifier of the QoS flow to which the SDAP PDU belongs. The UE 104 may send the End Marking Control PDU 204 on the old DRB as the last packet associated with the QFI. This serves as an indication to the base station 108 that no more packets belonging to the (remapped) QFI will be sent forward from that point on the old DRB.

[0034] Figure 3 An exemplary message stream 300, including QoS stream remapping using reflected QoS, is shown according to some implementation schemes.

[0035] At 304, the application (APP) on UE 104 can provide IP packets to the communication stack of UE 104. The communication stack may include various non-access stratum (NAS) and sublayer (e.g., SDAP sublayer) functions. IP packets may be associated with PDU session #1.

[0036] At 308, the communication stack can extract the header to detect the 5-tuple (IP tuple 2) of IP flow 2. Based on the extracted header, the communication stack can determine that the IP flow is classified as a specific QFI (e.g., QFI#2). The communication stack can map one or more QoS flows to a DRB (e.g., QFI 2 with DRB y). This can be done based on configured or default mapping rules.

[0037] At position 312, the communication stack can transmit an uplink (UL) PDU with an IP tuple 2 payload and an SDAP header with QFI=2. The UL PDU can be sent over DRBy.

[0038] At position 316, the communication stack can receive a DL PDU with an IP tuple 2 payload and an SDAP header with QFI=2 on DRBy. Then, the SDAP sublayer can provide IP traffic to the application at position 320 based on the DL PDU.

[0039] At position 324, the communication stack can receive another DL PDU from base station 108. This DL PDU can be received on DRBz and may include the RDI bit set in the SDAP header. The set RDI bit indicates that the mapping of QFI2 has been changed to DRBz.

[0040] The communication stack can transmit IP traffic to the application at position 328 and update the QoS flow to the DRB mapping table of the SDAP sublayer at position 332. The table can be updated to indicate that QFI 2 is now mapped to DRBz.

[0041] At position 336, the communication stack can transmit the SDAP end-of-line control PDU to base station 108. The SDAP end-of-line control PDU may have an SDAP header with QFI=2 and may be transmitted on the old DRB (e.g., DRBy). The SDAP end-of-line control PDU can provide base station 108 with an indication that the SDAP sublayer will no longer transmit PDUs with QFI 2 on the old DRB (DRBy).

[0042] At 340, the communication stack may have additional uplink IP traffic for PDU session #1, at 344 the header is extracted, the traffic is classified as QFI 2, and the traffic is mapped to DRBz based on the updated table.

[0043] At position 348, the communication stack can use the new DRBz to transmit UL PDUs.

[0044] Base station 108 may use the SDAP end mark control PDU received at 336 to assist the reordering function performed by base station 108 to provide ordered delivery of packets.

[0045] When the DRB mapping rules for a QoS flow change, a remapping of the QoS flow from one DRB to another may be required. This can occur during normal data transmission when base station 108 updates the QoS flow mapping rules to the DRB, or during handover when the target base station has a different mapping policy than the source base station. When a QoS flow from the old DRB is remapped to the new DRB, some packets from the QoS flow may still be waiting to be transmitted on the old DRB. After the mapping rules are updated, packets from the QoS flow can therefore arrive at the receiver from both the old and new DRB mappings simultaneously, as long as the old DRB still contains packets from that QoS flow. Ordered delivery may require buffering the latest data on the new DRB, as long as the data remains on the old DRB.

[0046] Although buffered data can occur at the transmitter or receiver, it is typically performed by base station 108 to reduce buffering requirements for UE 104. For example, buffering can be performed at the transmitter for downlink and at the receiver for uplink. Therefore, UE 104 sending an SDAP end-of-line control PDU allows base station 108 to acknowledge that all data from the relocated QoS flow has been transmitted on the old DRB. As shown in message flow 300, the end-of-line mark can be transmitted on the old DRB after updating the QoS flow to DRB mapping rules.

[0047] For the uplink, when base station 108 receives UL data from UE 104, once all packets from the relocated QoS flow have been received on the old DRB and delivered sequentially to the upper layer, the latest data from the new DRB can only be delivered to the upper sublayer (and UPF). This can be transparent to UE 104, but base station 108 may need to buffer the latest data from the QoS flow.

[0048] For the downlink, when base station 108 receives DL data from UPF on the N3 interface, base station 108 can begin transmitting the latest downlink data to UE 104 on the new DRB only after all packets from the relocated QoS flow have already been transmitted on the old DRB. This is also straightforward for UE 104, but base station 108 needs to buffer the latest data from the relocated QoS flow.

[0049] After the QoS flow mapping to the DRB for QFI has been changed from the old DRB to the new DRB, base station 108 can buffer UL SDUs received for a specific QFI flow on the new DRB until it has received an SDAP end-of-process control PDU for the same QFI on the old DRB. Once base station 108 receives and processes the end-of-process control PDU for the QFI, it can forward pending UL SDUs belonging to that QFI to the upper sublayer (and UPF).

[0050] With the DRB configured in RLC Unacknowledged Mode (UM), UE 104 may not know whether base station 108 has successfully received the SDAP End Mark Control PDU. If base station 108 does not receive the SDAP End Mark Control PDU, it may buffer uplink data for an excessively long period, potentially impacting user experience. In contrast to handover, the problem of inappropriate SDAP end mark reception from the network is more pronounced at the QoS flow and DRB mapping point within a base station.

[0051] In DL, SDAP RDI packets from base station 108 may also be lost in RLC UM mode. Therefore, UE 104 can continue to send QFI uplink packets on the old DRB.

[0052] User Datagram Protocol (UDP) with RLC UM mode on a dedicated DRB can be a possible deployment for low-latency communication, such as, for example, Ultra-Reliable Low-Latency Communication (URLCC) and Extended Reality (XR) use cases. These use cases may not tolerate significant latency. Therefore, the implementation described herein describes the procedures involved in transmitting and receiving RDI and SDAP end markers to provide appropriate operation for low-latency communication.

[0053] In some implementations, an enhanced reliability transmission end-of-transmission marker can be used. Two alternative schemes for using an enhanced reliability transmission end-of-transmission marker in RLC UM mode are described. These and other alternative schemes described herein are not mutually exclusive. For example, some aspects from the first alternative scheme can be used in conjunction with the second alternative scheme, and vice versa.

[0054] In a first alternative, UE 104 may retransmit the SDAP end-of-life PDU with enhanced reliability based on Hybrid Automatic Repeat Request (HARQ) Negative Acknowledgment (NACK), retransmission grant, or predefined time intervals. In some implementations, aspects of the lifetime operation (including, for example, triggering conditions for inputting the lifetime) that can be used in Industrial Internet of Things (IoT) applications may be used to retransmit the SDAP end-of-life PDU. The lifetime provides a period of time during which applications consuming communication services can continue without expected messages / bursts. In some implementations, the lifetime may be similar to the lifetime described in 3GPP TS 22.261 v18.3.0 (2021-06-25).

[0055] In the first option of the first alternative scheme, retransmission of the SDAP end-mark PDU may depend on the lifetime. For example, if UE 104 receives a HARQ NACK or retransmission grant for a TB including the end-mark, UE 104 may enter the lifetime and retransmit the end-mark with enhanced reliability. Alternatively, the UE may enter the lifetime using another method for retransmitting the end-mark with enhanced reliability. Retransmitting the end-mark with enhanced reliability can be achieved through PDCP replication (e.g., generating and transmitting replicated PDCP packets including the end-mark) or adaptive L1 / L2 configuration. When transmitting the end-mark with enhanced reliability, the adaptive L1 / L2 configuration may include using a high-reliability PUSCH configuration (e.g., including a more robust modulation and coding scheme, transport block repetition, different redundancy versions, higher power, frequency hopping, modified logical channel prioritization constraints, etc.). The adaptive L1 / L2 configuration with enhanced reliability can be pre-configured. PDUs without the end-mark can be transmitted with non-enhanced reliability settings / configurations.

[0056] Events that trigger a time-to-live (TTL) entry can be constructed upon receiving a HARQ NACK or retransmission grant with an end-of-time (TB) marker, timer expiration, or other similar triggering events. In implementations using HARQ NACK or retransmission grants to enter TTL, the SDAP sublayer can provide an indication to the lower layer that the packet includes an SDAP end-of-time (PDU). The lower layer can use this indication as a marker for transmission indication (failure / success) of the packet to be provided to the SDAP sublayer.

[0057] In some implementations, UE 104 may be configured with liveness in different modes on the DRB. For example, liveness (e.g., for transmissions with enhanced reliability) may be available for: only end-marked PDUs; all PDUs, but any loss of the end-marked control PDU may immediately trigger liveness, regardless of other liveness triggering events for the DRB; or liveness modes.

[0058] In the second option, aspects independent of lifetime can be defined to increase the reliability of PDUs carrying end marks. The network, for example via base station 108, can pre-configure and activate additional resources whenever an SDAP end mark is anticipated from UE 104. Additional resources, which can only be activated for a limited time, allow PDCP replication and mapping to RLC entities, which UE 104 can use to increase the reliability of retransmitted end marks. For example, the reliability of retransmitting end marks can be enhanced by using PDCP replication. Other methods to enhance reliability similar to those discussed above (L1 / L2 adaptive configuration, TB repetition, etc.) can also be used. Additionally / alternatively, the network can activate additional or modified resources based on the detection of unsuccessful uplink transmissions (e.g., for DRBs with anticipated end marks). In some implementations, the additional or modified resources can be activated by base station 108 by setting the RDI bit (e.g., Figure 3 In case 316), the DL transfer is activated at a later time. Attached or modified resources can activate a pre-configured time period.

[0059] In some implementations, the network may activate additional resources when the initial transmission of the end marker is anticipated. In other implementations, the additional resources may not be activated until the network determines that the initial transmission should have been received. Therefore, the network may activate additional or modified radio resources for retransmitting the end marker. In some implementations, UE 104 may retransmit the end marker after a predefined time interval, without even waiting for a lower-layer trigger event. The timing of the network activating the additional resources may be based on a predefined time interval.

[0060] In a second alternative scheme for transmitting end markers with enhanced reliability in RLC UM, each end marker can be transmitted with enhanced reliability. The enhanced reliability options may be similar to those discussed above with respect to the first alternative scheme; however, in this alternative scheme, the enhanced reliability settings can be used for both the initial transmission and retransmission of end markers.

[0061] In the first of the two alternative options, UE104 can immediately enter liveness mode to transmit the end-of-life control PDU with enhanced reliability. For example, UE104 can enter liveness mode while the end-of-life control PDU is constructed and transmitted for DRB.

[0062] In the second option, which selects two additional options, UE 104 can use spurious PDCP replication for end-mark packets on the DRB. Normally, when PDCP replication is activated, all packets on the DRB are expected to be replicated. However, in this implementation, only end-mark packets can be replicated. This enhances the reliability of end-mark transmission by providing frequency diversity. Network resources can be pre-configured to enable this option.

[0063] Additionally / alternatively, other methods to enhance the reliability of the transmission of the end marker, similar to those discussed above with respect to the first alternative scheme, may be used for the initial transmission of the end marker.

[0064] In some implementations, UE 104 may be configured to, or may be allowed to, send one or more end markers. For example, UE 104 may send multiple end markers in the uplink upon receiving an RDI bit for reflected QoS (once), or after a change in the QoS flow mapping with DRB in the RLC UM (e.g., via RRC reconfiguration). In this option, the network may trigger the end marker only once (e.g., by sending the RDI bit), but UE 104 may be allowed to repeat the end marker. 3GPP TSs 38.300 v16.6.0 (2021-06) and 37.324, which currently restrict end marker transmission to a single instance, may be updated to allow multiple end markers to be transmitted based on a single triggering event.

[0065] Although the initial transmission of the end marker can be on the old DRB, retransmission can be on either the old DRB (if it still exists) or the new DRB. When base station 108 receives the end marker (either the initial transmission or the retransmission), base station 108 can release the buffered DRB data.

[0066] UE 104 may send one or more end markers according to one or more of the following seven options.

[0067] In the first option, UE 104 can space multiple end-marker control PDUs to ensure that different end marks do not appear on the same MAC PDU. This prevents the loss of one MAC PDU from causing the loss of multiple end marks.

[0068] In the second option, a disable customizer can be used. For example, UE 104 can start a disable timer during the initial transmission of the end mark. UE 104 can then retransmit the end mark after the disable timer expires, provided that the old DRB still exists. In some implementations, UE 104 can repeat this process until the old DRB is released or a counter tracking the total number of end mark transmissions reaches a predetermined threshold.

[0069] In the third option, the SDAP sublayer can track the delivery of the end-of-transmission mark. For example, the SDAP sublayer can retain a copy of the original SDAP end-of-transmission mark PDU. If the SDAP sublayer receives an indication from a lower layer that the SDAP end-of-transmission mark PDU was not successfully transmitted, the SDAP sublayer can resubmit the SDAP end-of-transmission mark control PDU to the lower sublayer for retransmission. The SDAP sublayer can delete the stored end-of-transmission mark PDU when releasing the old DRB.

[0070] In the fourth option, the PDCP sublayer can track the delivery of the end-marker. For example, the PDCP sublayer can retain a copy of the original PDCP PDU including the end-marker. In some implementations, the SDAP sublayer can provide the PDCP sublayer with an indication that the SDAP PDU is an end-marked PDU, so the PDCP sublayer can mark the PDCP PDU including the end-marker. If the PDCP sublayer receives an indication from a lower layer that the PDCP PDU with the end-marker was not successfully transmitted, the PDCP sublayer can resubmit the PDCP PDU carrying the end-marker to the lower sublayer. The PDCP sublayer can delete the stored PDCP PDU with the end-marker when releasing the old DRB.

[0071] In the fifth option, the RLC sublayer can track the delivery of the end-marker. For example, the RLC sublayer can retain a copy of the original RLC PDU including the end-marker. In some implementations, higher sublayers (e.g., the SDAP and PDCP sublayers) can provide the RLC sublayer with an indication that the PDCP PDU includes the end-marker, so the RLC sublayer can mark the RLCPDU including the end-marker. If the RLC sublayer receives an indication from a lower layer that the RLC PDU including the end-marker was not successfully transmitted, the RLC sublayer can resubmit the RLC PDU carrying the end-marker to the lower layer. The RLC sublayer can delete the stored RLC PDU with the end-marker when releasing the old DRB. In some implementations, the RLC UM operation is extensible to override this option.

[0072] In the sixth option, base station 108 can configure UE 104 in the RLC UM with the number of end-mark transmissions (X). In these implementations, when UE 104 detects the initial trigger event, the UE can then send X end-mark transmissions.

[0073] In the seventh option, the maximum number of times (X) the base station 108 can transmit using the end marker in RLC UM. max Configure UE104. In these implementations, when UE104 detects the initial trigger event, it can send up to X... max An end marker. However, if, for example, UE 104 determines that base station 108 has successfully received the end marker, UE 104 may send a value less than the maximum value.

[0074] In some implementations, UE 104 may use explicit acknowledgment for the end mark. For example, base station 108 may use DL SDAP end mark acknowledgment to explicitly acknowledge the reception of the SDAP end mark PDU for a specific QFI.

[0075] UE 104 can use timer T in the SDAP sublayer. sdap_end_marker_ackThe time period for receiving explicit acknowledgment from base station 108 is defined. The SDAP sublayer may start a timer after submitting the end-of-link marker to a lower sublayer (e.g., the PDCP sublayer) in the uplink. The SDAP sublayer may stop the timer upon receiving the DL SDAP end-of-link marker ACK control PDU. If the timer expires without receiving an ACK, the SDAP sublayer may be triggered to retransmit the end-of-link marker control PDU. In some implementations, the timer value may be greater than or equal to the UE queuing delay used for the uplink plus the product of the HARQ round-trip time (RTT) and the maximum number of RTT retransmissions. In some implementations, the timer value may be configurable by the network.

[0076] If the SDAP end-of-process (SDAP) control PDU is not received by the SDAP sublayer before the timer expires, UE104 may retransmit the SDAP end-of-process (SDAP) control PDU in the uplink and restart the timer. In some implementations, as discussed above, the retransmission of the SDAP end-of-process (SDAP) control PDU can be performed with enhanced reliability.

[0077] In some implementations, the use of the SDAP end tag ACK and related parameters (e.g., timer values) may be configurable by the network. For example, in some implementations, the network may configure only the SDAP end tag ACK used for mapping to the QFI of the RLC UM transport.

[0078] In various implementations, base station 108 may signal the SDAP end mark ACK according to one or more of the following five options.

[0079] In the first option, base station 108 may generate an end-of-segment ACK as an SDAP PDU consisting only of the DL SDAP header. This SDAP PDU may have both an RDI field and an RQI field set to one, as well as a QFI field padded to indicate the actual QFI. Therefore, the end-of-segment ACK can be a single-byte SDAP PDU. If UE 104 receives an SDAP PDU consisting only of a single-byte SDAP header (e.g., without an SDAP data field or as a DL control PDU) with both RDI and RDI bits set to one, UE 104 may interpret the PDU as an SDAP end-of-segment ACK. If base station 108 intends to set both RDI and RQI bits to one simultaneously without signaling an ACK, the SDAP PDU may need to include a data field padded with certain data.

[0080] In the second option, a single byte can be added to the SDAP header to include an acknowledgment. This mitigation option can affect the size of the DLSDAP header because reserved header bits may not currently be available in the DLSDAP header.

[0081] The third option can be an extension of the first and second options to specify the associated PDCP PDU type. For example, a DL SDAP header acting as an acknowledgment can be sent as a payload (PDCP SDU) in a PDCP data PDU. Similarly, a DL SDAP header acting as an acknowledgment can be sent as a parameter in a PDCP control PDU.

[0082] In the fourth option, base station 108 may use a new PDCP control PDU for SDAP end-of-mark feedback. If the PDCP sublayer in UE 104 receives the new PDCP control PDU, the PDCP sublayer may deliver an indication (or corresponding end-of-mark feedback) to the SDAP sublayer in UE 104. The new PDCP control PDU may include, for example, a one-bit acknowledgment or a six-bit QFI (or PC5 QFI (PQFI)) as a parameter, or may only include feedback. In other embodiments, other options may be available for the new PDCP control PDU.

[0083] A fifth option may include extending the PDCP "Control PDU for PDCP Status Reporting" with a new field that can be used to report end-mark acknowledgments (feedback). Upon receiving end-mark feedback, the PDCP layer may deliver an indication (or corresponding end-mark feedback) to the SDAP protocol. The new end-mark feedback may include, for example, a one-bit ACK or a 6-bit QFI / PQFI, or simply "feedback" as a parameter. Other options are not excluded.

[0084] Some of these options facilitate situations where the SDAP end-of-signal feedback does not need to be associated with a sequence number. For example, the third option (where the DL SDAP header is sent as a parameter in the PDCP control PDU), the fourth option, and the fifth option may be particularly useful in these cases.

[0085] In some implementations, the repetition of the end mark can be triggered in UE 104. For example, UE 104 can repeat the SDAP end mark control PDU used in RLC UM mode when certain triggering conditions are detected to increase reliability. These implementations mitigate the situation where RDI bit updates from base station 108 are lost in the downlink during RLC UM.

[0086] According to some implementation schemes, base station 108 may repeat RDI transmission under certain conditions described in the following two alternative schemes.

[0087] In a first alternative, base station 108 may retransmit duplicate RDI transmissions based on buffers in the uplink data path. For example, if the uplink buffer at base station 108 for a specific QFI exceeds a predetermined threshold, base station 108 may retransmit the RDI. The threshold may be configured to base station 108 via operation and maintenance (O&M) functions or may depend on the specific implementation of the base station.

[0088] In a second alternative, base station 108 may repeat the RDI transmission based on the expiration of a timer used to receive the end marker of a specific QFI. The timer at base station 108 may be started when the first uplink packet belonging to the same QFI is received on a new DRB, or alternatively when base station 108 initially transmits the RDI. The expected timer value may be greater than or equal to the UE queuing delay for the uplink plus the product of the HARQ RTT and the maximum number of RTT retransmissions. When the timer expires, base station 108 may re-trigger the RDI transmission. Alternatively, base station 108 may assume the end marker is lost when the timer expires and thus release its buffered DRB data.

[0089] The RDI bit set for the same QFI in the downlink direction re-triggered SDAP header in either of the two alternatives discussed above can be executed according to either of the following two options. In the first option, a single-byte DL PDCP SDU (SDAP PDU) consisting only of the SDAP header can be used. The SDAP header will contain an RDI set to one along with a valid QFI. In the second option, the RDI bit can be set in the SDAP header as part of the next DL SDU belonging to the same QFI received at base station 108. This can be considered an in-band technique at the top of the DL IP packet for the same QFI.

[0090] Retrieved RDI bits for the same QFI setting can be sent on the old DRB (if it still exists) or the new DRB. From an uplink perspective, each SDAP end-of-line control PDU can be associated with a sequence number at the PDCP level. Therefore, base station 108 can link the end-of-line marker to the location of uplink packets from UE 104. Retransmitting the end-of-line marker on the old DRB is generally preferred as long as it still exists. If the end-of-line marker is only received on the new DRB, the base station can infer that the end-of-line marker was lost on the old DRB.

[0091] While 3GPP primarily specifies UE behavior, 3GPP TS (e.g., 3GPP TS 38.300 and 37.324) can be updated to indicate network options for repeating RDI bit settings consistent with the embodiments described herein. In some embodiments, 3GPP TS can be updated to accommodate the handling of re-triggering of SDAP end-mark control PDUs when RDI for the same QFI is detected again. For example, 3GPP TS 37.324 currently instructs the UE to send an end mark only if "the QoS flow to DRB mapping rule stored for the QoS flow is different from the QoS flow to DRB mapping of the DL SDAP data PDU". To accommodate the RDI bit reset described in the alternatives above, TS 37.324 can be updated to indicate that the UE may send one or more end marks based on one or more triggering events from the base station (e.g., RDI transmission).

[0092] In some implementations, base station 108 may set RDI bits for multiple back-to-back packets (or in one or more DL SDAP PDUs) for the same QFI. In some aspects, this may be similar to RQI handling, where the UPF marks back-to-back packets with RQI. UE 104 may generate multiple end-mark control PDUs with identical content and all associated with the old DRB. In some implementations, an SDAP end-mark disable timer may be introduced in the UE in the uplink based on the QFI. This disable timer can be used to avoid sending end marks too frequently in the uplink.

[0093] In some implementations, an SDAP start marker PDU may be introduced. This can be sent on a new DRB. The start marker is a new SDAP control PDU that marks the first sequence number on the new DRB. Upon receiving the start marker, base station 108 may release the packet in its buffer (similar to what happens when receiving the end marker). The probability that the SDAP end marker and SDAP start marker are part of a transport block that may be lost is potentially high. This can be mitigated by using the method described in Scheme 1 above or both, where a start marker is used instead of an end marker.

[0094] Figure 4 An operational flow / algorithm structure 400 according to some implementation schemes is shown. The operational flow / algorithm structure 400 can be executed by a UE such as, for example, UE 104, UE 700; or its components such as baseband circuit 704A.

[0095] Operational flow / algorithm structure 400 may include transmitting a transport block with an end-of-transmission PDU in the RLC UM at 404. The end-of-transmission PDU may be an SDAP PDU generated as an indication of the last packet transmitted on the old (e.g., switched from) DRB associated with the QFI.

[0096] The operation flow / algorithm structure 400 may also include detecting events related to the transmission of a transport block at 408. In some embodiments, the event may be the receipt of a negative acknowledgment, retransmission authorization, or a failure indication corresponding to the transmission of the transport block. Negative acknowledgments or failure indications may be provided from a lower layer to the SDAP sublayer. In another embodiment, the event may be a timer expiration, started when the transport block is initially transmitted, indicating that no successful transmission of the transport block has been received. In some embodiments, the timer may be in the PDCP or SDAP and may be started when the end-mark control PDU is submitted to a lower layer. The indication of successful transmission may be a DL SDAP PDU that acts as or otherwise indicates network acknowledgment of the receipt of the end-mark control PDU. In some embodiments, the successful transmission indication may include, for example, a HARQ ACK or another Tx success indication that a lower layer may provide to an upper layer.

[0097] The operation flow / algorithm structure 400 may further include: retransmitting transport blocks at 412 based on events detected at 408 for enhanced reliability. To transmit transport blocks with enhanced reliability, the UE can configure retransmission using transport block duplication, PDCP replication, or enhanced reliability PUSCH. Note that if PDCP replication is used, there may be two PDUs (each with the same end marker) and two transport blocks. However, the transport block may therefore not be able to be transmitted using PDCP replication, as replication occurs at the PDCP level.

[0098] Figure 5 An operational flow / algorithm structure 500 according to some implementation schemes is shown. The operational flow / algorithm structure 500 can be executed by a UE such as, for example, UE 104, UE 700 or its components such as baseband circuit 704A.

[0099] The operation flow / algorithm structure 500 may include receiving RDI at 504. RDI can be received by processing the SDAP header to detect the value of the RDI field. If a bit in the RDI field is set to one, RDI can be detected.

[0100] The operation procedure / algorithm structure 500 may also include determining an update to the QoS flow to DRB mapping at 508. For example, an SDAP header including RDI may be transmitted on the new (switched-to) DRB and may have a QFI previously associated with the old (switched-from) DRB. The UE can then know that the QoS flow corresponding to the QFI will continue to be transmitted on the new DRB.

[0101] The operation flow / algorithm structure 500 may also include transmitting one or more end or start markers at 512 based on the update determined at 508. If the UE transmits an end marker, the end marker can be transmitted on the old DRB. If the UE transmits a start marker, the start marker can be transmitted on the new DRB.

[0102] In some implementations, the UE may transmit multiple end / start markers. These multiple end / start markers may be transmitted based on the determination of an update at an original trigger event, such as at 508. In other implementations, the initial end / start marker transmission may be based on the original trigger event, and one or more retransmissions of the end / start marker may be performed based on the detection of additional triggering conditions (e.g., receiving a NACK corresponding to the initial end marker transmission or not receiving an ACK).

[0103] Figure 6 An operational flow / algorithm structure 600 according to some embodiments is shown. The operational flow / algorithm structure 600 can be executed by a base station such as, for example, base station 108, UE 800, or its components such as baseband circuit 804A.

[0104] Operational flow / algorithm structure 600 may include receiving an SDAP end marker PDU at 604. The end marker PDU may be received on the old DRB and may indicate the last transmission made by the UE from the DRB from which a given QFI has undergone mapping updates.

[0105] The operation flow / algorithm structure 600 may also include generating an SDAP end-of-signal (ACK) at 608. The ACK can be generated by setting both the RDI and RQI bits in the SDAP PDU (SDAP header-only). In other implementations, the ACK can be generated by: providing an indication in a new field in the SDAP header; as a payload in the PDCP data PDU; as a parameter in the PDCP control PDU; in a PDCP control PDU type specifically designed for transmitting end-of-signal feedback; or as a new field in a PDCP control PDU used for status reporting.

[0106] The operation procedure / algorithm structure 600 may also include transmitting the SDAP end marker ACK. This ACK can be transmitted to the UE on either the old DRB or the new DRB.

[0107] Figure 7 A UE 700 according to some implementation schemes is shown. The UE 700 may be similar to... Figure 1 The UE 104 is essentially interchangeable with it.

[0108] UE 700 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, computer, tablet, XR device, glass, industrial wireless sensor (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, stock sensor, voltmeter / ammeter, or actuator), video surveillance / monitoring device (e.g., camera or camcorder), wearable device (e.g., smartwatch), or Internet of Things device.

[0109] UE 700 may include a processor 704, RF interface circuitry 708, memory / storage device 712, user interface 716, sensor 720, drive circuitry 722, power management integrated circuit (PMIC) 724, antenna structure 726, and battery 728. Components of UE 700 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 7 The block diagram is intended to show a high-level view of some of the components of the UE 700. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0110] The components of UE 700 can be coupled to various other components via one or more interconnects 732, which can represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, or optical connector, allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0111] Processor 704 may include processor circuitry such as baseband processor circuitry (BB) 704A, central processing unit circuitry (CPU) 704B, and graphics processing unit circuitry (GPU) 704C. Processor 704 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 712) to cause UE 700 to perform the operations described herein.

[0112] In some implementations, the baseband processor circuit 704A can access the communication protocol stack 736 in the memory / storage device 712 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 704A can access the communication protocol stack 736 to perform the following operations: user plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, SDAP sublayer, and upper layers; and control plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, RRC layer, and NAS layer. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 708.

[0113] The baseband processor circuit 704A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0114] Memory / storage device 712 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 736) that can be executed by one or more processors in processor 704 to cause UE 700 to perform the various operations described herein. Memory / storage device 712 includes any type of volatile or non-volatile memory that can be distributed throughout UE 700. In some embodiments, some memory / storage devices 712 may be located on processor 704 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 712 may be located external to processor 704 but accessible via a memory interface. Memory / storage device 712 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0115] The RF interface circuit 708 may include transceiver circuitry and a radio frequency front-end module (RFEM), which allows the UE 700 to communicate with other devices via a radio access network. The RF interface circuit 708 may include various components arranged in the transmission or reception path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.

[0116] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna structure 726 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which downconverts the RF signal into a baseband signal that is provided to the baseband processor of processor 704.

[0117] In the transmission path, the transceiver's transmitter upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM amplifies the RF signal using a power amplifier before it is radiated across the air interface via antenna 726.

[0118] In various implementations, the RF interface circuit 708 can be configured to transmit / receive signals in a manner compatible with NR access technology.

[0119] Antenna 726 may include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 726 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input / multiple-output communication. Antenna 726 may include a microstrip antenna, a printed antenna fabricated on the surface of one or more printed circuit boards, a patch antenna, or a phased array antenna. Antenna 726 may have one or more panels designed for a specific frequency band (including bands in FR1 or FR2).

[0120] User interface circuitry 716 includes various input / output (I / O) devices designed to enable users to interact with UE 700. User interface 716 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators such as light-emitting diodes (LEDs) and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), where the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 700.

[0121] Sensor 720 may include devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, or subsystems. Examples of such sensors include: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors); depth sensors; ambient light sensors; ultrasonic transceivers; and microphones or other similar audio capture devices.

[0122] The driving circuit 722 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 700. The driving circuit 722 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 700. For example, the driving circuit 722 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for acquiring sensor readings of sensor circuit 720 and controlling and allowing access to sensor circuit 720; a driver for acquiring actuator positions of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; or an audio driver for controlling and allowing access to one or more audio devices.

[0123] The PMIC 724 manages the power supplied to various components of the UE 700. Specifically, relative to the processor 704, the PMIC 724 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0124] In some implementations, the PMIC 724 may control or otherwise become part of various power-saving mechanisms of the UE 700, including DRX, as discussed herein.

[0125] Battery 728 can power UE 700, but in some examples, UE 700 may be mounted in a fixed location and may have a power source coupled to the grid. Battery 728 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 728 may be a typical lead-acid automotive battery.

[0126] Figure 8 A base station 800 according to some embodiments is shown. The base station 800 may be similar to... Figure 1 The base station 108 is basically interchangeable with it.

[0127] Network device 800 may include processor 804, RF interface circuitry 808 (if implemented as a base station), core network (CN) interface circuitry 812, memory / storage device circuitry 816, and antenna structure 826 (if implemented as a base station).

[0128] The components of network device 800 can be coupled to various other components via one or more interconnectors 828.

[0129] The processor 804, RF interface circuit 808, memory / storage device circuit 816 (including communication protocol stack 810), antenna structure 826, and interconnect 828 are similar to those in the reference. Figure 7 Similar named elements are shown and described. If device 800 is implemented as a base station, the communication protocol stack 810 may include an access layer. If network device 800 is implemented as a device in core network 82, the communication protocol stack 810 may include a NAS layer.

[0130] The CN interface circuit 812 can provide connectivity to a core network (e.g., a 5GC using a 5G core network (5GC) compatible network interface protocol (such as Carrier Ethernet protocol) or some other suitable protocol). Network connectivity can be provided to / from base station 800 via fiber optic or wireless backhaul. The CN interface circuit 812 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 812 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0131] In some implementations, base station 800 may be coupled to transmit receiver point (TRP) using antenna structure 826, CN interface circuitry or other interface circuitry.

[0132] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0133] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, or network element described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0134] Example

[0135] Further exemplary implementations are provided in the following sections.

[0136] Example 1 includes a method comprising: transmitting a transport block having a Service Data Application Protocol (SDAP) End Mark Protocol Data Unit (PDU) in Radio Link Control (RLC) Unacknowledged Mode; detecting an event associated with the transmission of the transport block; and retransmitting the SDAP End Mark PDU with enhanced reliability based on the detected event.

[0137] Example 2 includes the method according to Example 1 or some other embodiment of this document, wherein detecting an event includes receiving a negative acknowledgment or retransmission request corresponding to a transport block.

[0138] Example 3 includes the method according to Example 2 or some other embodiment of this document, the method further comprising: entering a liveness mode based on receiving a negative acknowledgment or retransmission request.

[0139] Example 4 includes the method according to Example 1 or some other embodiment herein, wherein the enhanced reliability retransmission SDAP end mark control PDU includes: configuring the retransmission SDAP end mark PDU using transport block duplication, packet data convergence protocol (PDCP) replication, or enhanced reliability physical uplink shared channel (PUSCH).

[0140] Example 5 includes the method according to Example 1 or some other embodiment of this document, the method further comprising: triggering a timer based on the transmission of an SDAP end marker control PDU; and detecting an event based on the expiration of the timer.

[0141] Example 6 includes a method comprising: generating a first packet and a second packet having SDAP end-mark protocol data units (PDUs), the first packet and the second packet being to be transmitted in Radio Link Control (RLC) unacknowledged mode; transmitting the first packet with enhanced reliability; and transmitting the second packet with non-enhanced reliability.

[0142] Example 7 includes the method according to Example 6 or some other embodiment of this document, the method comprising: transmitting a first packet with enhanced reliability based on a first network configuration; and transmitting a second packet with non-enhanced reliability based on a second network configuration.

[0143] Example 8 includes the method according to Example 6 or some other embodiment of this document, the method comprising: transmitting a first packet with enhanced reliability using Packet Data Convergence Protocol (PDCP) replication; and transmitting a second packet with non-enhanced reliability without using PDCP replication.

[0144] Example 9 includes the method according to Example 6 or some other embodiment of the present invention, the method comprising: transmitting a first packet with enhanced reliability using a first layer 1 or layer 2 configuration; and transmitting a second packet with non-enhanced reliability using a second layer 1 or layer 2 configuration.

[0145] Example 10 includes the method according to Example 6 or some other embodiment herein, wherein transmitting the first packet with enhanced reliability is either the initial transmission of an SDAP end-mark control PDU or a retransmission of an end-mark PDU.

[0146] Example 11 includes a method comprising: receiving a Radio Resource Control (RRC) Reconfiguration or Reflection Quality of Service Flow to Data Radio Bearer Mapping Indication (RDI); determining, based on the RRC reconfiguration or RDI, to update the Quality of Service (QoS) flow to a first Data Radio Bearer (DRB) mapping to a second DRB; and transmitting, based on the RRC reconfiguration or RDI, a plurality of Service Data Adaptation (SDAP) End Mark Protocol Data Units (PDUs).

[0147] Example 12 includes the method according to Example 11 or some other embodiment herein, wherein transmitting a plurality of SDAP end marker PDUs includes: transmitting a first SDAP end marker PDU of a plurality of SDAP end marker PDUs on a first DRB; and transmitting a second SDAP end marker PDU of a plurality of SDAP end marker PDUs on a first DRB or a second DRB.

[0148] Example 13 includes the method according to Example 11 or some other embodiment herein, wherein transmitting a plurality of SDAP end-of-signature PDUs includes: transmitting a first SDAP end-of-signature PDU among a plurality of SDAP end-of-signature PDUs in a first media access control (MAC) PDU; and transmitting a second SDAP end-of-signature PDU among a plurality of SDAP end-of-signature PDUs in a second MAC PDU.

[0149] Example 14 includes the method according to Example 11 or some other embodiment of the present invention, the method further comprising: starting a disable timer based on transmitting a first SDAP end mark PDU among a plurality of SDAP end mark PDUs; and transmitting a second SDAP end mark PDU among a plurality of SDAP end mark PDUs based on the expiration of the disable timer.

[0150] Example 15 includes the method according to Example 11 or some other embodiment herein, the method further comprising: transmitting a first SDAP end-marker PDU among a plurality of SDAP end-marker PDUs in the initial transmission of the SDAP PDU; storing the SDAP PDU at the SDAP sublayer; receiving at the SDAP sublayer an indication that the first SDAP end-marker PDU was not successfully transmitted from a lower layer; and transmitting a second SDAP end-marker PDU among a plurality of end-marker PDUs in the retransmission of the SDAP PDU based on the indication.

[0151] Example 16 includes the method according to Example 11 or some other embodiment herein, the method further comprising: transmitting a first SDAP end-marker PDU among a plurality of end-marker PDUs in the initial transmission of a Packet Data Convergence Protocol (PDCP) PDU; storing the PDCP PDU at a PDCP sublayer; receiving at the PDCP sublayer an indication that the first SDAP end-marker PDU was not successfully transmitted from a lower layer; and transmitting a second SDAP end-marker PDU among a plurality of SDAP end-marker PDUs in a retransmission of the PDCP PDU based on the indication.

[0152] Example 17 includes the method according to Example 16 or some other embodiment herein, the method further comprising: deleting the PDCP PDU based on determining that the first DRB has been released.

[0153] Example 18 includes the method according to Example 11 or some other embodiment herein, the method further comprising: transmitting a first SDAP end-mark PDU among a plurality of SDAP end-mark PDUs in the initial transmission of a Radio Link Control (RLC) PDU; storing the RLC PDU at the RLC sublayer; receiving at the RLC sublayer an indication that the first SDAP end-mark PDU was not successfully transmitted from a lower layer; and transmitting a second SDAP end-mark PDU among a plurality of SDAP end-mark PDUs in a retransmission of the RLC PDU based on the indication.

[0154] Example 19 includes the method according to Example 18 or some other embodiment herein, the method further comprising: deleting the RLC PDU based on determining that the first DRB has been released.

[0155] Example 20 includes the method according to Example 11 or some other embodiment of this document, the method further comprising: receiving from a base station an indication number of end mark transmissions to be sent in Radio Link Control (RLC) Unacknowledged Mode, wherein a plurality of SDAP end mark PDUs are equal to or less than the indication number.

[0156] Example 21 includes a method for operating a base station, the method comprising: receiving a Service Data Adaptation (SDAP) End Mark Control Protocol Data Unit (PDU) from a User Equipment (UE); generating an SDAP End Mark Acknowledgment (ACK) based on the received SDAP End Mark Control PDU; and transmitting the SDAP End Mark ACK to the UE.

[0157] Example 22 includes the method according to Example 21 or some other embodiment herein, the method further comprising: transmitting configuration information to configure the UE to operate based on an end-marker acknowledgment of a Quality of Service Flow Indicator mapped to a data radio bearer that will be transmitted using Radio Link Control (RLC) Unacknowledged Mode.

[0158] Example 23 includes the method according to Example 21 or some other embodiment herein, the method further comprising: transmitting configuration information to configure a timer value for the UE, the timer value being defined as the period during which the UE will wait for confirmation after transmitting an SDAP end mark control PDU and before sending another SDAP end mark control PDU.

[0159] Example 24 includes the method according to Example 21 or some other embodiment herein, wherein generating the SDAP end tag ACK includes: setting both the Reflection Quality of Service Stream to Data Radio Bearer Mapping Indicator (RDI) field and the Reflection Quality of Service Indicator (RQI) field to a bit value of one, wherein the SDAP end tag ACK is a control PDU having a single-byte SDAP header and no data field.

[0160] Example 25 includes the method according to Example 21 or some other embodiment herein, wherein generating the SDAP end marker ACK includes providing an acknowledgment indication in a field of the SDAP header of the control PDU.

[0161] Example 26 includes the method according to Example 21 or some other embodiment herein, the method further comprising: generating Packet Data Convergence Protocol (PDCP) data PDU to include the SDAP end tag ACK.

[0162] Example 27 includes the method according to Example 21 or some other embodiment of this document, the method further comprising: generating a Packet Data Convergence Protocol (PDCP) control PDU to include an SDAP end tag ACK.

[0163] Example 28 includes the method according to Example 27 or some other embodiment herein, wherein the PDCP control PDU includes an acknowledgment bit or a six-bit quality of service flow indicator to provide an SDAP end marker ACK.

[0164] Example 29 includes the method according to Example 27 or some other embodiment herein, wherein the PDCP control PDU is used for status reporting.

[0165] Example 30 includes a method of operating a base station, the method comprising: generating a Serving Data Adaptation (SDAP) header having a Reflection Quality of Service Stream to Data Radio Bearer Mapping Indicator (RDI) field set to one; transmitting the SDAP header; detecting conditions; and transmitting the SDAP header having an RDI field set to one based on the detection conditions.

[0166] Example 31 includes the method according to Example 30 or some other embodiment of this document, wherein the detection condition includes: detecting that the buffer level of the Quality of Service Flow Indicator at the base station is greater than a predetermined threshold.

[0167] Example 32 includes the method according to Example 30 or some other embodiment herein, the method further comprising: starting a timer based on receiving an uplink packet belonging to a Quality of Service Flow Indicator (QFI) mapped to a new data radio bearer; and detecting an expiration condition based on the timer without receiving an end marker of the QFI.

[0168] Example 33 includes a method of operating a base station, the method comprising: generating a plurality of packets having a Reflective Quality of Service Flow to Data Radio Bearer Mapping Indicator (RDI) field set to one for a Quality of Service Flow; and transmitting the plurality of packets to a user equipment.

[0169] Example 34 includes the method according to Example 33 or some other embodiment herein, wherein the plurality of groups are back-to-back groups.

[0170] Example 35 includes the method according to Example 33 or some other embodiment herein, wherein the plurality of packets include one or more Service Data Adaptation Protocol (SDAP) Protocol Data Units (PDUs).

[0171] Example 36 includes a method comprising: receiving a reflected Quality of Service (QoS) Stream to Data Radio Bearer (DRB) Mapping Indication (RDI); determining, based on the RDI, to update the mapping of the QoS Stream to a first Data Radio Bearer (DRB) to a second DRB; and transmitting, based on the RDI, a Start Mark Protocol Data Unit (PDU) on the second DRB, the Start Mark PDU being used to mark the transmission of a first sequence number on the second DRB for the QoS Stream.

[0172] Example 37 includes the method according to Example 36 or some other embodiment herein, the method further comprising: marking the PDU with an enhanced reliability transmission start.

[0173] Example 38 may include an apparatus comprising one or more elements for performing a method or process described or associated with any of Examples 1-37 or any other method or process described herein.

[0174] Example 39 may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein as described or associated with any of Examples 1-37.

[0175] Example 40 may include an apparatus comprising one or more elements of a logic component, module, or circuit for performing a method or process described or associated with any of Examples 1-37 or any other method or process described herein.

[0176] Example 41 may include a method, technique, or process, or a part or component thereof, as described or associated with any of Examples 1-37.

[0177] Example 42 may include an apparatus comprising one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described or associated with any of Examples 1-37.

[0178] Example 43 may include the signal described or associated with any of Examples 1-37, or a portion or component thereof.

[0179] Example 44 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or otherwise in this disclosure, according to any of Examples 1-37.

[0180] Example 45 may include a signal encoded with data, or a portion or component thereof, as described or associated with any of Examples 1-37, or otherwise described in this disclosure.

[0181] Example 46 may include a signal, or a portion or component thereof, encoded as a datagram, IE, packet, frame, segment, PDU, or message, as described or associated with any of Examples 1-37, or otherwise described in this disclosure.

[0182] Example 47 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described or associated with any of Examples 1-37.

[0183] Example 48 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process, or a portion thereof, as described or associated with any of Examples 1-37.

[0184] Example 49 may include signals in a wireless network as shown and described herein.

[0185] Example 50 may include a method for communicating in a wireless network as shown and described herein.

[0186] Example 51 may include a system for providing wireless communication as shown and described herein.

[0187] Example 52 may include a device for providing wireless communication as shown and described herein.

[0188] Unless otherwise expressly stated, any of the examples above may be combined with any other example (or combination of examples). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice of various embodiments.

[0189] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed by one or more processors, cause a device to perform the following operations: In Radio Link Control (RLC) Unacknowledged mode, transport blocks with Service Data Adaptation Protocol (SDAP) End Mark Protocol Data Units (PDUs) are transmitted; Receive the Hybrid Automatic Repeat Request (HARQ) Negative Acknowledgment (NACK) or Retransmission Grant for the transport block; and Based on receiving the HARQ NACK or retransmission grant, the device enters a liveness mode and retransmits the SDAP end marker PDU with enhanced reliability, wherein, in order to retransmit the SDAP end marker PDU with enhanced reliability, the device is configured to: Configure the retransmission of the SDAP end marker PDU using the High Reliability Physical Uplink Shared Channel (PUSCH).

2. The one or more computer-readable media of claim 1, wherein, in order to retransmit the SDAP end marker PDU with enhanced reliability, the device is configured to: The SDAP end marker PDU is retransmitted repeatedly using transport blocks.

3. One or more computer-readable media according to claim 1 or 2, wherein, in order to retransmit the SDAP end marker PDU with enhanced reliability, the device is configured to: The SDAP end marker PDU is copied and retransmitted using the Packet Data Convergence Protocol (PDCP).

4. One or more computer-readable media according to claim 1 or 2, wherein the instructions, when executed, further cause the device to: The SDAP sublayer of the device provides an indication of the packet, including the SDAP end marker PDU, to the lower layers of the device; and At the SDAP sublayer, a fault transmission indication associated with the packet is received from the lower layer of the device.

5. A method for operating a base station, the method comprising: Receive Service Data Adaptation (SDAP) End Mark Control Protocol Data Unit (PDU) from User Equipment (UE); The generation of transport blocks includes Hybrid Automatic Repeat Request (HARQ) negative acknowledgment (NACK) or retransmission grant; and The HARQ NACK or retransmission grant is transmitted to the UE to trigger the UE's lifetime mode and to trigger an enhanced reliability retransmission of the SDAP end marker PDU. The enhanced reliability retransmission of the SDAP end marker PDU includes configuring the retransmission of the SDAP end marker PDU using the High Reliability Physical Uplink Shared Channel (PUSCH).

6. The method of claim 5, wherein retransmitting the SDAP end marker PDU with enhanced reliability includes repeatedly retransmitting the SDAP end marker PDU using transport blocks.

7. The method of claim 5 or 6, wherein retransmitting the SDAP end marker PDU with enhanced reliability includes replicating and retransmitting the SDAP end marker PDU using a Packet Data Convergence Protocol (PDCP).

Images