[go: up one dir, main page]

WO2023004771A1 - Procédé et dispositif de gestion d'unité pdu de commande durant une transmission de petites données - Google Patents

Procédé et dispositif de gestion d'unité pdu de commande durant une transmission de petites données Download PDF

Info

Publication number
WO2023004771A1
WO2023004771A1 PCT/CN2021/109678 CN2021109678W WO2023004771A1 WO 2023004771 A1 WO2023004771 A1 WO 2023004771A1 CN 2021109678 W CN2021109678 W CN 2021109678W WO 2023004771 A1 WO2023004771 A1 WO 2023004771A1
Authority
WO
WIPO (PCT)
Prior art keywords
drb
sdt
control pdu
qos flow
terminal device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2021/109678
Other languages
English (en)
Inventor
Ran YUE
Haiming Wang
Mingzeng Dai
Jie Shi
Lianhai WU
Min Xu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2021/109678 priority Critical patent/WO2023004771A1/fr
Publication of WO2023004771A1 publication Critical patent/WO2023004771A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the subject matter disclosed herein generally relates to wireless communications, and more particularly relates to method and apparatus for handling the control PDU in small data transmission (SDT) .
  • SDT small data transmission
  • 3GPP has developed technologies for SDT to support data transmission without transitioning to an RRC connected state.
  • 3GPP introduced EDT and PUR transmission technologies for 4G LTE in Release 15 and Release16, and SDT technology for 5G new radio (NR) in Release 17.
  • NR 5G new radio
  • the SDT for 5G NR considers an RRC inactive state whose operation is also based on the suspension of an RRC connection and the resumption of an RRC connection. As compared to an RRC idle state, the RRC inactive state has different features such as radio access network (RAN) based notification area (RNA) , RAN paging, etc.
  • RAN radio access network
  • RNA notification area
  • Both data radio bearer (DRB) and signaling radio bearer (SRB) are considered as bearers for SDT.
  • DRB data radio bearer
  • SRB signaling radio bearer
  • 3GPP considers that positioning/location information can be transmitted via the SRB based on the SDT for 5G NR.
  • SDAP Service Data Adaptation Protocol
  • the SDAP sublayer is configured through RRC signaling, and the SDAP sublayer is responsible for mapping the QoS flow to the corresponding DRB.
  • One or more QoS flows can be mapped to the same DRB, and one QoS flow can only be mapped to one DRB.
  • control PDU e.g., end-marker control PDU during SDT according to whether the DRB to which the control PDU is mapped is a SDT DRB or a non-SDT DRB has not been defined clearly.
  • This invention discloses methods and apparatuses for handling control PDU in SDT to solve the above and other technical problems.
  • a method by a terminal device comprises: receiving a downlink (DL) data Packet Data Unit (PDU) from a network device; in response to determining that a control PDU is to be transmitted to the network device while the terminal device is in a non-Radio Resource Control (RRC) _CONNECTED state with the network device, determining whether a Data Radio Bearer (DRB) that carries the control PDU is a Small Data Transmission (SDT) DRB or not; in response to determining that the DRB is not a SDT DRB, constructing the control PDU for a Quality of Service (QoS) flow, mapping the control PDU to the DRB, and transmitting the control PDU via the DRB as SDT.
  • DRB Data Radio Bearer
  • SDT Small Data Transmission
  • control PDU is generated from Access Stratum (AS) layer.
  • AS Access Stratum
  • control PDU is considered as arrival of data for DRB for which SDT is enabled, if it is determined that the control PDU will be transmitted.
  • the method further comprises: in response to determining that the DRB is a SDT DRB, mapping the control PDU to the DRB; and transmitting the control PDU via the DRB as SDT.
  • determining whether the control PDU will be transmitted further comprises: determining that the control PDU will not be transmitted, if the terminal device determines that no out of order transmission will be occurred between DRBs.
  • transmitting the control PDU via the DRB as SDT further comprises multiplexing the control PDU with other data on an ongoing SDT.
  • transmitting the control PDU via the DRB as SDT further comprises: initiating a SDT if there is no ongoing SDT or if there is no other data corresponding to the arrival of SDT data, wherein the trigger condition for initiating the SDT is that the control PDU is constructed.
  • transmitting the control PDU via the DRB as SDT comprises only transmitting the control PDU as SDT.
  • the method further comprises resuming the DRB which carries the control PDU if the DRB is not a SDT DRB.
  • the method further comprises suspending the DRB if the DRB is not a SDT DRB after the control PDU is transmitted.
  • a terminal device comprises a transceiver; and a processor coupled to the transceiver and configured to perform the method disclosed above.
  • a method by a network device comprises: configuring an uplink (UL) Quality of Service (QoS) flow to Data Radio Bearer (DRB) mapping rule for a QoS flow or transmitting a downlink (DL) data Packet Data Unit (PDU) to a terminal device; receiving a control PDU for a QoS flow from the terminal device; delivering the control PDU to upper layer, wherein the control PDU is received as Small Data Transmission (SDT) , wherein the network device in a non-Radio Resource Control (RRC) _CONNECTED state with the terminal device, and wherein the method further comprising: restricting a QoS flow to DRB mapping rule for the QoS flow.
  • SDT Small Data Transmission
  • RRC non-Radio Resource Control
  • restricting the QoS flow to DRB mapping rule for the QoS flow further comprising: the QoS flow to DRB mapping rule is delivered before the terminal device is released to a non-Radio Resource Control (RRC) _CONNECTED state with the network device, or the QoS flow to DRB mapping rule is delivered before the RRC Release message is transmitted to the terminal device, or reflective QoS is not allowed to be applied to SDT DRBs, or the QoS flow to DRB mapping rule is not allowed to be changed during the SDT procedure of the terminal device.
  • RRC Radio Resource Control
  • a RRC_CONNECTED state with the terminal device is resumed if the QoS flow to DRB mapping rule is to be changed.
  • a network device comprises a transceiver; and a processor coupled to the transceiver and configured to perform the method disclosed above.
  • Fig. 1 illustrates the RRC states in NR
  • Fig. 2 illustrates the QoS architecture in 5G system
  • Fig. 3 illustrates the SDAP structure in 5G system
  • Fig. 4 illustrates the format of End-Marker Control PDU
  • Fig. 5 illustrates a flowchart for a UE to handle the control PDU according to an embodiment
  • Fig. 6 is a schematic block diagram illustrating apparatuses according to an embodiment.
  • embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc. ) or an embodiment combining software and hardware aspects that may generally all be referred to herein as a “circuit” , “module” or “system” . Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine-readable code, computer readable code, and/or program code, referred to hereafter as “code” .
  • code computer readable storage devices storing machine-readable code, computer readable code, and/or program code, referred to hereafter as “code” .
  • the storage devices may be tangible, non-transitory, and/or non-transmission.
  • the storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
  • modules may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very-large-scale integration
  • a module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
  • Modules may also be implemented in code and/or software for execution by various types of processors.
  • An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but, may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.
  • a module of code may contain a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
  • operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. This operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices.
  • the software portions are stored on one or more computer readable storage devices.
  • the computer readable medium may be a computer readable storage medium.
  • the computer readable storage medium may be a storage device storing code.
  • the storage device may be, for example, but need not necessarily be, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • a storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, random access memory (RAM) , read-only memory (ROM) , erasable programmable read-only memory (EPROM or Flash Memory) , portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • Code for carrying out operations for embodiments may include any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages.
  • the code may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN) , or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) .
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider an Internet Service Provider
  • the code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices, to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
  • the code may also be loaded onto a computer, other programmable data processing apparatus, or other devices, to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code executed on the computer or other programmable apparatus provides processes for implementing the functions specified in the flowchart and/or block diagram block or blocks.
  • each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function (s) .
  • Fig. 1 illustrates the RRC states in NR.
  • the RRC protocol is used in the air interface. It exists only in the control plane, in the UE and in the gNB.
  • the major functions of the RRC protocol include connection establishment and release functions, broadcast of system information, RB establishment, reconfiguration and release, RRC connection mobility procedures, paging notification and release and outer loop power control.
  • the RRC configures the user and control planes according to the network status and allows for Radio Resource Management strategies to be implemented.
  • RRC The behavior and functions of RRC are governed by the current state of RRC.
  • RRC has three distinct states: RRC_IDLE, RRC_CONNECTED and RRC_INACTIVE.
  • RRC_IDLE Upon power on, UE enters into RRC_IDLE mode. UE may move to this mode from either RRC_CONNECTED mode or RRC_INACTIVE mode.
  • RRC_INACTIVE UE moves to this mode from RRC_CONNECTED mode. It is connected but inactive mode of UE. In this mode, UE maintains RRC connection and at the same time minimizes signaling and power consumption.
  • RRC_CONNECTED UE remains in connection with the 5G-RAN/5GC in this mode.
  • RRC_IDLE to RRC_CONNECTED happens via the RRC Connection Setup procedure. This transition consists of three messages: RRCSetupRequest (UE initiated) , RRCSetup, and RRCSetupComplete.
  • RRC_CONNECTED to RRC_IDLE is via RRC Connection Release procedure with network-initiated RRCRelease message. Upper layers in the UE may also request a release. RRC connection is also released due to radio link failure, handover failure or cell not meeting cell selection criteria.
  • RRC_CONNECTED to RRC_INACTIVE is network initiated. It is entered via RRCRelease message with suspendConfig IE.
  • RRC_INACTIVE to RRC_CONNECTED is triggered by the network via RAN paging.
  • a paged UE will start with RRC Connection Resume procedure consisting of three messages: RRCResumeRequest, RRCResume (or RRCSetup) , RRCResumeComplete (or RRCSetupComplete) .
  • RRCResumeRequest RRCResume (or RRCSetup)
  • RRCResumeComplete or RRCSetupComplete
  • RRC_INACTIVE to RRC_IDLE happens when network responds to RRCResumeRequest with RRCRelease.
  • RRC connection establishment involves the establishment of SRB1.
  • the network completes RRC connection establishment prior to completing the establishment of the NG connection, i.e. prior to receiving the UE context information from the 5GC. Consequently, AS security is not activated during the initial phase of the RRC connection.
  • the network may configure the UE to perform measurement reporting, but the UE only sends the corresponding measurement reports after successful AS security activation. However, the UE only accepts a re-configuration with sync message when AS security has been activated.
  • the release of the RRC connection normally is initiated by the network.
  • the procedure may be used to re-direct the UE to an NR frequency or an E-UTRA carrier frequency.
  • the purpose of this procedure is to release the RRC connection, which includes the release of the established radio bearers, BH RLC channels (an RLC channel between two nodes) as well as all radio resources; or to suspend the RRC connection only if SRB2 and at least one DRB or, for IAB, SRB2, are setup, which includes the suspension of the established radio bearers.
  • the suspension of the RRC connection is initiated by the network.
  • the UE stores the UE Inactive AS context and any configuration received from the network, and transits to RRC_INACTIVE state.
  • the RRC message to suspend the RRC connection is integrity protected and ciphered.
  • the resumption of a suspended RRC connection is initiated by upper layers when the UE needs to transit from RRC_INACTIVE state to RRC_CONNECTED state or by RRC layer to perform a RNA update or by RAN paging from NG-RAN.
  • network configures the UE according to the RRC connection resume procedure based on the stored UE Inactive AS context and any RRC configuration received from the network.
  • the RRC connection resume procedure re-activates AS security and re-establishes SRB (s) and DRB (s) .
  • the purpose of this procedure is to resume a suspended RRC connection, including resuming SRB (s) and DRB (s) or perform an RNA update.
  • Fig. 2 illustrates the QoS architecture in 5G system.
  • the 5G QoS model is based on QoS Flows and supports both QoS Flows that require guaranteed flow bit rate (GBR QoS Flows) and QoS Flows that do not require guaranteed flow bit rate (non-GBR QoS Flows) .
  • the QoS flow is thus the finest granularity of QoS differentiation in a PDU session.
  • a QoS flow is identified within a PDU session by a QoS Flow ID (QFI) carried in an encapsulation header over NG-U.
  • QFI QoS Flow ID
  • the QoS architecture in NG-RAN both for NR connected to 5GC and for E-UTRA connected to 5GC is depicted in the Fig. 2.
  • 5GC For each UE, 5GC establishes one or more PDU Sessions. Except for NB-IoT and IAB-MT in SA mode, for each UE, the NG-RAN establishes at least one DRB together with the PDU Session and additional DRB (s) for QoS flow (s) of that PDU session can be subsequently configured.
  • the NG-RAN may establish DRB together with the PDU Session and one PDU session maps to only one DRB.
  • the NG-RAN maps packets belonging to different PDU sessions to different DRBs.
  • NAS level packet filters in the UE and in the 5GC associate UL and DL packets with QoS Flows.
  • AS-level mapping rules in the UE and in the NG-RAN associate UL and DL QoS Flows with DRBs.
  • NG-RAN and 5GC ensure quality of service (e.g. reliability and target delay) by mapping packets to appropriate QoS Flows and DRBs.
  • quality of service e.g. reliability and target delay
  • a QoS flow is characterized by a QoS profile provided by 5GC to NG-RAN and QoS rule (s) provided by 5GC to the UE.
  • the QoS profile is used by NG-RAN to determine the treatment on the radio interface while the QoS rules dictates the mapping between uplink User Plane traffic and QoS flows to the UE.
  • a QoS flow may either be GBR or Non-GBR depending on its profile.
  • the data radio bearer defines the packet treatment on the radio interface (Uu) .
  • a DRB serves packets with the same packet forwarding treatment.
  • the QoS flow to DRB mapping by NG-RAN is based on QFI and the associated QoS profiles (i.e. QoS parameters and QoS characteristics) .
  • Separate DRBs may be established for QoS flows requiring different packet forwarding treatment, or several QoS Flows belonging to the same PDU session can be multiplexed in the same DRB.
  • the UE performs the classification and marking of UL User plane traffic, i.e. the association of UL traffic to QoS Flows, based on QoS rules.
  • QoS rules may be explicitly provided to the UE, pre-configured in the UE or implicitly derived by the UE by applying Reflective QoS.
  • a QoS rule contains the QFI of the associated QoS Flow, a Packet Filter Set and a precedence value.
  • An explicitly signaled QoS rule contains a QoS rule identifier which is unique within the PDU Session and is generated by SMF.
  • a default QoS rule is required to be sent to the UE for every PDU Session establishment and it is associated with a QoS Flow.
  • the default QoS rule is the only QoS rule of a PDU Session which may contain a Packet Filter Set that allows all UL packets, and in this case, the highest precedence value shall be used for the QoS rule.
  • Fig. 3 illustrates the SDAP structure in 5G system
  • the main services and functions of SDAP include mapping between a QoS flow and a data radio bearer and marking QFI in both DL and UL packets.
  • the SDAP sublayer is configured by RRC.
  • a single protocol entity of SDAP is configured for each individual PDU session.
  • One or more QoS flows may be mapped onto one DRB.
  • One QoS flow is mapped onto only one DRB at a time in the UL.
  • the SDAP entities are located in the SDAP sublayer. Several SDAP entities may be defined for a UE. There is an SDAP entity configured for each individual PDU session for NR Uu. An SDAP entity receives/delivers SDAP SDUs from/to upper layers and submits/receives SDAP data PDUs to/from its peer SDAP entity via lower layers.
  • QoS flow to DRB mapping rule is a mapping rule determining on which DRB packets of a QoS flow shall be carried.
  • Reflective QoS flow to DRB mapping is a QoS flow to DRB mapping scheme where a UE monitors the QoS flow to DRB mapping rule in the DL, and applies it to in the UL. Reflective QoS flow to DRB mapping is performed at UE, if DL SDAP header is configured.
  • the transmitting SDAP entity shall:
  • the receiving SDAP entity shall:
  • the SDAP entity When RRC configures an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity shall:
  • the SDAP entity When RRC releases an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity shall:
  • the SDAP entity For each received DL SDAP data PDU with RDI set to 1, the SDAP entity shall:
  • Fig. 4 illustrates the format of End-Marker Control PDU.
  • the D/C bit (1 bit) indicates whether the SDAP PDU is an SDAP Data PDU or an SDAP Control PDU.
  • Reserved field R (1 bit) shall be set to 0 and be ignored by the receiver.
  • the QFI field (6 bits) indicates the ID of the QoS flow to which the SDAP PDU belongs.
  • the PQFI field (6 bits) indicates the ID of the PC5 QoS flow to which the SDAP PDU belongs.
  • the wireless device when a wireless device in an RRC idle state has UL data, the wireless device should perform procedures for the transmission of the UL data where the procedures comprises: a random access procedure to synchronize uplink timing, a RRC connection establishment procedure to establish an RRC connection; and an initial AS security activation procedure for secured data transmission.
  • the wireless device in an RRC connected state transmits the UL data. After the transmission of the UL data, the wireless device stays in the RRC connected state until receiving an RRC release message from a base station. While staying in the RRC connected state, the wireless device should perform additional procedures. The wireless device transitions back to the RRC idle state when receiving an RRC release message from the base station.
  • the overheads of the overall procedure are inefficient to transmit small amount of data.
  • the overheads become more critical especially for a device requiring low complexity and low power consumption.
  • 3GPP has introduced technologies to reduce the overheads.
  • 3GPP has developed technologies for SDT to support data transmission without transitioning to an RRC connected state.
  • NR SDT in an RRC inactive state is studying in 3GPP.
  • Two SDT technologies are supported: RACH based SDT, and CG based SDT.
  • the RACH based SDT allows SDT using an uplink grant received via a random access procedure for SDT.
  • the CG based SDT allows SDT from an RRC inactive state using a configured grant without performing a random access procedure.
  • the SDAP entity should construct an end-marker control PDU according to the stored UL QoS flow to DRB mapping rule or the configured UL QoS flow to DRB mapping rule. In this case, some specific scenarios need to be considered.
  • the UE stored a mapping rule between QoS flow (#a) and Data Radio Bearer DRB (#1) ; a DL SDAP data PDU with RDI set to 1 which means reflective QoS shall be applied is received by the UE during the MO SDT for DRB (#5) which is mapped with QoS flow (#b) and the QoS flow (#a) is relocated to a SDT DRB (#2) according to the indication from the received DL SDAP PDU; the SDAP entity shall construct an end-marker control PDU, map the end-marker control PDU to the DRB (#1) and submit the end-marker control PDU to the lower layers.
  • Scenario #1 there is no stored QoS flow to DRB mapping rule for the QoS flow (#a) ; a DL SDAP data PDU with RDI set to 1 is received by the UE during the MO SDT and the QoS flow (#a) is mapped to a SDT DRB (#2) according to the indication from the received DL SDAP PDU; the SDAP entity shall construct an end-marker control PDU, map the end-marker control PDU to the default DRB and submit the end-marker control PDU to the lower layers.
  • the end-marker control PDU is mapped to either the default DRB or the DRB (#1) according to the stored QoS flow to DRB (#1) mapping rule. While, the default DRB or the DRB (#1) according to the stored QoS flow to DRB mapping rule may be a non-SDT DRB. According to the agreement, non-SDT radio bearers are only resumed upon receiving RRC Resume. It means non-SDT data can only be transmitted when the UE is in RRC_CONNECTED state. Accordingly even if the NW schedules a grant for UL SDT, the UE cannot transmit the end-marker control PDU which is non-SDT data.
  • the UE stored a mapping rule between QoS flow (#a) and DRB (#3) ; a DL SDAP data PDU with RDI set to 1 is received by the UE during the MT SDT; the QoS flow is relocated to a SDT DRB (#2) by reflective mapping; an end-marker control PDU is constructed and mapped to the DRB (#3) .
  • a DL packet from DRB (#3) is received by the UE during the MT SDT; an EHC or ROHC feedback control PDU corresponding to the DL packet is generated by the PDCP entity for DRB (#3) and shall be transmitted to the NW.
  • NAS generates one of the existing resume causes and AS decides SDT or non-SDT access. It can be understood as the SDT traffic being from the higher layer and the “MO data” being indicated by NAS layer. While the EHC/ROHC feedback or end-marker control PDU is carried by a control PDU and generated from the AS layer. Therefore, whether the control PDU can be transmitted as SDT needs to be clarified.
  • the legacy resume procedure which is used to initiated a SDT can only be initiated by NAS or RNAU. Therefore, it seems that the control PDU generated by the AS layer cannot initiate a RRC resume procedure to transmit the EHC/ROHC feedback as SDT if the UE reselects to a neighbor cell which supports SDT or if DL SPS resources is used for MT SDT (assuming there is not a MO SDT procedure before the DL SDT data transmitted) . Similarly, the end-marker control PDU generated by the AS layer cannot initiate a RRC resume procedure for a SDT if the RRC Release is received before the end-marker control PDU is successfully transmitted. For all the above cases, the UE has to wait for the paging signal again. It is not optimal from the perspective of signaling overhead and power saving.
  • the application proposes the following solutions. It should be noted that the following solutions are not limited to any specific one of the above scenarios, but may be applied individually or in combination to the above and other scenarios.
  • the SDAP entity may construct an end-marker control PDU, and map the end-marker control PDU to a default DRB or a DRB according to the stored QoS flow to DRB mapping rule and submit the end-marker control PDU to the lower layers.
  • the application proposes that if the DRB to which end-marker control PDU is mapped is a non-SDT DRB, it may be configured/allowed/defined that the end-marker control PDU may be transmitted as SDT.
  • non-SDT data can only be transmitted when the UE is in RRC_CONNECTED state, and therefore even if the NW schedules a grant for UL SDT, the UE cannot transmit the end-marker control PDU which is non-SDT data.
  • the application further proposes that it may be configured/allowed/defined that the end-marker control PDU may be transmitted by a UE which is not in RRC_CONNECTED state without transition to RRC_CONNECTED state. More specifically, it may be configured/allowed/defined that the end-marker control PDU may be transmitted by a UE in RRC_IDLE and/or RRC_INACTIVE state (i.e., non-CONNECTED state) .
  • the DRB which carries the end-marker control PDU when UE constructs/generates an end-marker control PDU in SDAP entity, if the DRB which carries the end-marker control PDU is not a SDT DRB according to QoS flow to DRB mapping rule, it may be configured/allowed/defined that the DRB which carries the end-marker control PDU may be a SDT DRB or it may be configured/allowed/defined that the DRB which carries the control PDU may be a SDT DRB upon the control PDU is constructed/generated.
  • the configuration/allowance/definition may be made at RRC layer or agreed in the standard.
  • UE selects CG-SDT.
  • UE selects RA-SDT.
  • the procedure above is started with the arrival of data only for DRB/SRB (s) for which SDT is enabled, but not applicable for the arrival of end-marker control PDU carried on a DRB which is a non-SDT DRB .
  • the arrival of end-marker control PDU may be considered as the arrival SDT data. And therefore, the procedure above may be performed.
  • the DRB which carries the end-marker control PDU may be resumed.
  • the DRB which carries the end-marker control PDU may be resumed.
  • the transmission procedure may comprise transmitting only the end-marker control PDU as SDT.
  • the transmission may be implemented by the SDAP layer only submitting the end-marker control PDU to the lower layers.
  • the transmission may include multiplexing the end-marker control PDU with other data, and initiating a SDT by the end-marker control PDU.
  • the DRB to which end-marker control PDU is mapped is a non-SDT DRB, it may be configured/allowed/defined that the end-marker control PDU may be transmitted as SDT.
  • the existing criteria e.g., CG-SDT criteria or RA-SDRT criteria, should be met when deciding whether a SDT may be initiated upon the end-marker control PDU is constructed/generated.
  • the end-marker control PDU when transmitting the end-marker control PDU, may be multiplexed with other data on an ongoing SDT or a SDT may be initiated by the end-marker control PDU. And other data on the DRB which carries the end-marker control PDU may also be transmitted as SDT.
  • the DRB which carries the end-marker control PDU may be suspended if it is not configured as SDT DRB.
  • the control at network side needs to be defined.
  • NW may configure an UL QoS flow to DRB mapping rule for a QoS flow, or UE may monitor the QoS flow to DRB mapping rule in the DL and apply Reflective QoS flow to DRB mapping in the UL.
  • the QoS flow to DRB mapping rule may be restricted, it can be for the reflective mapping case and/or for the configuration case.
  • the QoS flow to DRB mapping rule should be stored or configured before the UE is released to RRC_INACTIVE or RRC_IDLE state. In other words, no default DRB will be available.
  • the UE shall create a UE derived QoS rule for the uplink traffic based on the received DL traffic if reflective QoS function is used by the 5GC for some traffic flows.
  • the UE shall use the UE derived QoS rules to determine mapping of UL traffic to QoS Flows.
  • the NW may not allow reflective QoS to be applied to SDT DRBs.
  • the QoS flow to DRB mapping rule may not allowed to be changed.
  • the SDAP entity may construct an end-marker control PDU, and map the end-marker control PDU to a DRB, where if the DRB to which end-marker control PDU is mapped is a non- SDT DRB, it may be configured/allowed/defined that the end-marker control PDU may be transmitted as SDT.
  • the UE may not construct an end-marker control PDU if the DRB which would carry the end-marker control PDU is not a SDT DRB.
  • an end-marker control PDU may be constructed.
  • the UE may discard or withdraw or cancel the end-maker control PDU, if there is no other data for the DRB which carries the end-marker control PDU buffered or if the DRB which carries the end-marker control PDU is a non-SDT or the UE can make sure no out of order transmission between two DRBs.
  • out of order transmission means the transmission is not in the order it should be which is caused by the disorder of the sequence of data pieces or missing data pieces (e.g. failure, fallback) .
  • the transmitter can make sure that there is not out of delivery of the data between the two mapping DRBs if the transmitter determines not to transmit the end-marker control PDU.
  • control PDU is only an example of the control PDU, and other control PDUs are also possible.
  • the EHC/ROHC feedback or end-marker control PDU is a control PDU and generated from the AS layer, while the legacy resume procedure which is used to initiated a SDT can only be initiated by NAS or RNAU.
  • control PDU may be the end-marker control PDU, the interspersed ROHC feedback, the EHC feedback, the PDCP status report, the RLC status report, and the like.
  • the transmission may include multiplexing the end-marker control PDU with other data and initiating a SDT upon the control PDU is constructed/generated.
  • the existing criteria e.g., CG-SDT criteria or RA-SDRT criteria, should be met when deciding whether a SDT can be initiated upon the control PDU is constructed/generated.
  • the resuming procedure is for the AS control PDU transmission in non RRC_CONNECTED state. And accordingly, a new resume cause may be introduced and applied when delivering the RRC message.
  • Fig. 5 illustrates a flowchart for a UE to handle the control PDU according to an embodiment.
  • the method (500) starts with receiving a DL data PDU from the NW (S501) .
  • the UE determines whether a control PDU should be transmitted to the NW (S502) .
  • the UE determines whether the DRB which would carry a control PDU is a SDT DRB or not (S503) .
  • the UE Based on the determining result at S503, the UE will perform different procedures.
  • the UE constructs the control PDU for a QoS flow (S504) , maps the control PDU to the DRB (S505) and transmits the control PDU via the DRB as SDT to the NW (S506) .
  • the UE map the control PDU to the DRB (S507) and transmit the control PDU via the DRB as SDT to the NW (S508) .
  • the UE may not transmit control PDU.
  • the UE may not construct a control PDU (S509) .
  • the UE may construct a control PDU (S510) , but discard the transmission of the control PDU (S511) .
  • the alternative procedures are illustrated with dashed blocks.
  • Fig. 6 is a schematic block diagram illustrating apparatuses according to one embodiment.
  • the UE i.e., the terminal device
  • the UE includes a processor, a memory, and a transceiver.
  • the processor implements a function, a process, and/or a method which are described above. The details of the operation of the UE have been described above.
  • Layers of a radio interface protocol may be implemented by the processors.
  • the memories are connected with the processors to store various pieces of information for driving the processors.
  • the transceivers are connected with the processors to transmit and/or receive a radio signal. Needless to say, the transceiver may be implemented as a transmitter to transmit the radio signal and a receiver to receive the radio signal.
  • the memories may be positioned inside or outside the processors and connected with the processors by various well-known means.
  • the gNB (i.e., the network device) includes a processor, a memory, and a transceiver.
  • the processor implements a function, a process, and/or a method which are described above.
  • the operations performed on the gNB side correspond to the operations performed on the UE side.
  • the operations performed on the gNB side correspond to the operations performed on the UE side.
  • the solutions in the present invention in order to optimize the handling of the control PDU triggered from AS layer, the following solutions are provided allowing the control PDU which is carried by a non-SDT DRB to be transmitted as SDT temporarily, allowing the control PDU which is constructed by the AS layer and carried by a SDT DRB to initiate a SDT, restricting the NW behavior to reduce signaling overhead and power consumption and proposing the preconditions for cancellation of the control PDU.
  • each component or feature should be considered as an option unless otherwise expressly stated.
  • Each component or feature may be implemented not to be associated with other components or features.
  • the embodiment may be configured by associating some components and/or features. The order of the operations described in the embodiments may be changed. Some components or features of any embodiment may be included in another embodiment or replaced with the component and the feature corresponding to another embodiment. It is apparent that the claims that are not expressly cited in the claims are combined to form an embodiment or be included in a new claim.
  • the embodiments may be implemented by hardware, firmware, software, or combinations thereof.
  • the exemplary embodiment described herein may be implemented by using one or more application-specific integrated circuits (ASICs) , digital signal processors (DSPs) , digital signal processing devices (DSPDs) , programmable logic devices (PLDs) , field programmable gate arrays (FPGAs) , processors, controllers, micro-controllers, microprocessors, and the like.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays

Landscapes

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

Abstract

La présente invention concerne des procédés et des dispositifs de gestion d'une unité PDU de commande durant une transmission de petites données, SDT. Dans un mode de réalisation, un procédé réalisé par un dispositif terminal comprend : la réception d'une unité de données en paquets (PDU) de données de liaison descendante (DL) en provenance d'un dispositif de réseau; en réponse au fait de déterminer que l'unité PDU de commande doit être transmise au dispositif de réseau pendant que le dispositif terminal n'est pas dans un état connecté de commande de ressources radioélectriques (RRC) avec le dispositif de réseau, le fait de déterminer si un support radioélectrique de données (DRB) qui transporte l'unité PDU de commande est un support DRB de transmission de petites données (SDT) ou non; en réponse au fait de déterminer que le support DRB n'est pas un support DRB de transmission SDT, la construction de l'unité PDU de commande pour un flux de qualité de service (QoS), le mappage de l'unité PDU de commande au support DRB, et la transmission de l'unité PDU de commande via le support DRB en tant que transmission SDT.
PCT/CN2021/109678 2021-07-30 2021-07-30 Procédé et dispositif de gestion d'unité pdu de commande durant une transmission de petites données Ceased WO2023004771A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/109678 WO2023004771A1 (fr) 2021-07-30 2021-07-30 Procédé et dispositif de gestion d'unité pdu de commande durant une transmission de petites données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/109678 WO2023004771A1 (fr) 2021-07-30 2021-07-30 Procédé et dispositif de gestion d'unité pdu de commande durant une transmission de petites données

Publications (1)

Publication Number Publication Date
WO2023004771A1 true WO2023004771A1 (fr) 2023-02-02

Family

ID=85087424

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/109678 Ceased WO2023004771A1 (fr) 2021-07-30 2021-07-30 Procédé et dispositif de gestion d'unité pdu de commande durant une transmission de petites données

Country Status (1)

Country Link
WO (1) WO2023004771A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118019062A (zh) * 2024-01-03 2024-05-10 北京智联安科技有限公司 小包数据传输sdt的实现方法、用户设备及存储介质
WO2024253677A1 (fr) * 2023-06-08 2024-12-12 Dell Products, L.P. Planification d'autorisation configurée adaptative

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109565703A (zh) * 2016-08-01 2019-04-02 三星电子株式会社 用于管理无线通信网络中的数据通信的方法和设备
CN110213799A (zh) * 2016-03-29 2019-09-06 电信科学技术研究院有限公司 一种下行小数据传输方法及装置
WO2021002632A1 (fr) * 2019-07-03 2021-01-07 주식회사 케이티 Procédé et dispositif de commande de charge de petites données
CN112703768A (zh) * 2018-09-20 2021-04-23 高通股份有限公司 在数据无线电承载释放、切换到另一个数据无线电承载或服务质量流增加时避免无序的上行链路数据接收

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110213799A (zh) * 2016-03-29 2019-09-06 电信科学技术研究院有限公司 一种下行小数据传输方法及装置
CN109565703A (zh) * 2016-08-01 2019-04-02 三星电子株式会社 用于管理无线通信网络中的数据通信的方法和设备
CN112703768A (zh) * 2018-09-20 2021-04-23 高通股份有限公司 在数据无线电承载释放、切换到另一个数据无线电承载或服务质量流增加时避免无序的上行链路数据接收
WO2021002632A1 (fr) * 2019-07-03 2021-01-07 주식회사 케이티 Procédé et dispositif de commande de charge de petites données

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024253677A1 (fr) * 2023-06-08 2024-12-12 Dell Products, L.P. Planification d'autorisation configurée adaptative
CN118019062A (zh) * 2024-01-03 2024-05-10 北京智联安科技有限公司 小包数据传输sdt的实现方法、用户设备及存储介质

Similar Documents

Publication Publication Date Title
US12464464B2 (en) Managing a ue preferred configuration
US20240008115A1 (en) Managing ue connectivity with master node and secondary node
US20240365282A1 (en) Managing Paging for a User Device
CN117063596A (zh) 用于处置小数据传输中的srb的方法和设备
US20240237102A9 (en) Managing a cell group in dual connectivity
WO2023004771A1 (fr) Procédé et dispositif de gestion d'unité pdu de commande durant une transmission de petites données
US20250267505A1 (en) Managing Buffer Status Reporting During Small Data Transmission
US20250168919A1 (en) Managing radio configurations for small data transmission
US20250168093A1 (en) Delaying requests for resources related small data transmission
US20250168892A1 (en) Managing data transmission in an inactive state
US20250220763A1 (en) Managing Small Data Transmission Configuration Parameters
US20250254683A1 (en) Managing small data transmission with a radio access network
US20250330284A1 (en) Managing Positioning Measurement for an Inactive State
US20250168874A1 (en) Managing resources for data transmission in an inactive state
US20250220527A1 (en) Managing Small Data Transmission Configuration and Non-Small Data Transmission Configuration
US20250142665A1 (en) Managing radio configurations for a user equipment
US20250247890A1 (en) Managing Small Data Transmission With a Network
US20250142663A1 (en) Managing small data transmission with a configured grant configuration
US20250142554A1 (en) Managing small data transmission for a user equipment
US20250142503A1 (en) Managing uplink synchronization at a user equipment
US20250234412A1 (en) Managing Small Data Transmission With a User Equipment
US20250227765A1 (en) Managing SDT Configuration Parameters When Detecting a Failure
US20250274970A1 (en) Method and Apparatus for Managing Small Data Transmission in Protocol Operations
US20250142664A1 (en) Managing uplink synchronization for a user equipment
US20250234413A1 (en) Managing a Small Data Transmission Configuration

Legal Events

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

Ref document number: 21951363

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 21/05/2024)

122 Ep: pct application non-entry in european phase

Ref document number: 21951363

Country of ref document: EP

Kind code of ref document: A1