WO2024087585A1 - Procédé et appareil de transmission de données utilisant des temporisateurs de rejet d'ensemble d'unités de données de protocole - Google Patents

Procédé et appareil de transmission de données utilisant des temporisateurs de rejet d'ensemble d'unités de données de protocole Download PDF

Info

Publication number
WO2024087585A1
WO2024087585A1 PCT/CN2023/093930 CN2023093930W WO2024087585A1 WO 2024087585 A1 WO2024087585 A1 WO 2024087585A1 CN 2023093930 W CN2023093930 W CN 2023093930W WO 2024087585 A1 WO2024087585 A1 WO 2024087585A1
Authority
WO
WIPO (PCT)
Prior art keywords
discard
pdu
pdu set
psi
pdcp
Prior art date
Application number
PCT/CN2023/093930
Other languages
English (en)
Other versions
WO2024087585A9 (fr
Inventor
Mingzeng Dai
Xiaoying Xu
Haiyan Luo
Lianhai WU
Congchi ZHANG
Original Assignee
Lenovo (Beijing) Limited
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) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2023/093930 priority Critical patent/WO2024087585A1/fr
Publication of WO2024087585A1 publication Critical patent/WO2024087585A1/fr
Publication of WO2024087585A9 publication Critical patent/WO2024087585A9/fr

Links

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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames

Definitions

  • Embodiments of the present application generally relate to wireless communication technology, especially to a method and apparatus of data transmission using protocol data unit (PDU) set discard timers.
  • PDU protocol data unit
  • a wireless communication system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • Each network communication devices such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology.
  • the wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, frames, subframes, or the like) or frequency resources (e.g., subcarriers, carriers) .
  • the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) ..
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • XR extended reality
  • AR augmented reality
  • VR virtual reality
  • CG cloud gaming
  • An objective of the embodiments of the present application is at least to provide a technical solution of data transmission, e.g., a method and apparatus of data transmission for XR services or the like, which supports PDU set discard based on PDU set importance (PSI) .
  • PSI PDU set importance
  • Some embodiments of the present application provide an apparatus of data transmission, e.g., a central unit (CU) control plane (CP) (CU-CP) of a radio access network (RAN) node, which includes: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: determine PDU set discard timers based on different PSI levels associated with a data radio bearer (DRB) , wherein each PDU set discard timer is associated with a respective one of the PSI levels; and transmit, to a CU user plane (UP) (CU-UP) of the RAN node, information associated with the PDU set discard timers as determined.
  • DRB data radio bearer
  • UP CU user plane
  • the processor is configured to: receive PSI information of a quality of service (QoS) flow mapped to the DRB from a core network (CN) entity or the CU-UP; and determine the PSI levels associated with the DRB based on the received PSI information, wherein, the PSI information indicates: the number of PSI levels associated with the QoS flow; the PSI levels associated with the QoS flow; information indicating whether the PSI levels are used for user data of the QoS flow; or any combination thereof.
  • QoS quality of service
  • the processor is configured to: receive the PSI information via a next generation core network (NG-C) control plane signalling from the CN entity.
  • N-C next generation core network
  • the processor is configured to: receive PSI information of the DRB from the CU-UP; and determine the PSI levels associated with the DRB based on the received PSI information, wherein, the PSI information indicates: the number of PSI levels associated with the DRB; the PSI levels associated with the DRB; information indicating whether the PSI levels are used for user data of the DRB; or any combination thereof.
  • the processor is configured to: receive the PSI information via an E1 application protocol (E1AP) signaling from the CU-UP.
  • E1AP E1 application protocol
  • the processor is configured to: transmit the information associated with the PDU set discard timers to a UE in the case that the DRB is for uplink transmission.
  • the processor is configured to: transmit, to the CU-UP, the information associated with the PDU set discard timers via E1AP Bearer Context Setup Request or Bearer Context Modification request messages.
  • the PSI levels includes PSI levels associated with all QoS flows mapped to the DRB, and the different PSI levels have different PDU set discard timers.
  • each PDU set discard timer being associated with a corresponding PDU set discard mode
  • the processor is configured to: determine a first PDU set discard mode from the multiple PDU set discard modes; and send an indication to, the CU-UP, indicating the first PDU set discard mode.
  • the processor is configured to: switch from the first PDU set discard mode to a second PDU set discard mode of the multiple PDU set discard modes; and send an indication to, the CU-UP, indicating the second PDU set discard mode.
  • the multiple PDU set discard modes include a PDU set congestion discard mode and a PDU set non-congestion discard mode.
  • the processor is configured to: configure respective PDU set congestion conditions associated with the PDU set congestion discard mode and the PDU set non-congestion PDU set discard mode; and send an indication to, the CU-UP, indicating the configured PDU set congestion conditions.
  • the processor is configured to: send an indication to, the CU-UP, indicating the first PDU set discard mode in an E1AP Bearer Context Setup Request or Bearer Context Modification Request message.
  • the processor is configured to: send an indication to, the CU-UP, indicating the second PDU set discard mode in an E1AP Bearer Context Modification Request message.
  • Some other embodiments of the present application provide another apparatus of data transmission, e.g., a CU-UP of a RAN node, which may include: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: receive, from a CU-CP of the RAN node, information associated with PDU set discard timers for a DRB, wherein each PDU set discard timer is associated with a PSI level associated with the DRB; and transmit a PDU set discard indication, to a DU of the RAN node, indicating user data associated with a PDU set associated with a corresponding PDU set discard timer to be discarded in the case that the corresponding PDU set discard timer expires.
  • the processor is configured to: transmit PSI information of a QoS flow mapped to the DRB to the CU-CP, wherein, the PSI information indicates: the number of PSI levels associated with the QoS flows; the PSI levels associated with the QoS flow; information indicating whether the PSI levels are used for user data of the QoS flow; or any combination thereof.
  • the processor is configured to: transmit PSI information of the DRB to the CU-CP, wherein, the PSI information indicates: the number of PSI levels associated with the DRB; the PSI levels associated with the DRB; information indicating whether the PSI levels are used for user data of the DRB; or any combination thereof.
  • the processor is configured to: identify PSI levels in general packet radio service (GPRS) tunnel protocol user plane (GTP-U) headers or GTP-U extension header of received data from a CN entity; and transmit the PSI Information to the CU-CP via E1AP signalling.
  • GPRS general packet radio service
  • GTP-U tunnel protocol user plane
  • the processor is configured to: receive, from the CU-CP, the information associated with PDU set discard timers via E1AP Bearer Context Setup Request or Bearer Context Modification request messages.
  • the processor is configured to: transmit the PDU set discard indication, to the DU in a F1-U frame in a GTP-U extension header.
  • the PDU set discard indication indicates: user data for at least one PSI level to be discarded at least by including the at least one PSI level in the PDU set discard indication; or user data for at least one PDU set to be discarded at least by including a sequence number of the at least PDU set in the PDU set discard indication; or user data to be discarded at least including a sequence number of the user date in the PDU set discard indication.
  • the processor is configured to: receive discard feedback from the DU, wherein the discard feedback includes: packet data convergence protocol (PDCP) sequence number (SN) information of PDCP PDUs discarded in the DU; or lowest PDCP SN information of PDCP PDUs discarded in the DU.
  • PDCP packet data convergence protocol
  • SN sequence number
  • the processor is configured to assign PDCP SNs of the PDCP PDUs discarded in the DU to PDCP service data units (SDU) s.
  • SDU service data units
  • the processor is configured to: transmit, to the DU, an indication to indicate that PDCP SNs of the PDCP PDUs discarded in the DU are reused for new data; or forward PDCP PDUs using PDCP SNs of the PDCP PDUs discarded in the DU in a GTP-U tunnel dedicated for data transmission with reused PDCP SNs.
  • each PDU set discard timer being associated with a PDU set discard mode
  • the processor is configured to: receive, from the CU-CP, an indication indicating a first PDU set discard mode.
  • the processor is configured to: receive, from the CU-CP, an indication indicating a second PDU set discard mode to which the first PDU set discard mode will be switched.
  • the processor is configured to: receive, from the CU-CP, respective PDU set congestion conditions associated with the PDU set congestion discard mode and the PDU set non-congestion discard mode; and switch between the PDU set congestion discard mode and the PDU set non-congestion PDU set discard mode based on the received PDU set congestion conditions.
  • the processor is configured to: receive, from the CU-CP, the indication indicating the first PDU set discard mode in an E1AP Bearer Context Setup Request or Bearer Context Modification Request message.
  • the processor is configured to: receive, from the CU-CP, the indication indicating the second PDU set discard mode in an E1AP Bearer Context Modification Request message.
  • a DU of a RAN node may include: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: receive, from a CU of the RAN node, a PDU set discard indication, indicating user data associated with a PDU set is to be discarded in the DU; perform responsive to receiving the PDU set discard indication, discard the user data associated with the PDU set; and transmit discard feedback associated with the discarded user data to the CU.
  • the processor is configured to: receive the PDU set discard indication in a F1-U frame in a GTP-U extension header.
  • the processor is configured to: in the case that the PDU set discard indication indicates the user data for at least one PSI level to be discarded, for each PDCP PDU associated with the at least one PSI level, discard the PDCP PDU in the case that neither a radio link control (RLC) SDU nor a segment of the RLC SDU has been submitted to lower layers; or in the case that the PSU set discard indication indicates the user data for at least one PDU set to be discarded, for each PDCP PDU associated with the at least PDU set, discard the PDCP PDU in the case that neither a RLC SDU nor a segment of the RLC SDU has been submitted to lower layers; or in the case that the PSU set discard indication indicates the sequence number of the user date to be discarded, for a PDCP PDU associated with the sequence number, discard the PDCP PDU in the case that neither a RLC SDU nor a segment of the RLC SDU has been submitted to lower layers.
  • RLC radio link control
  • the discard feedback includes: PDCP SN information of PDCP PDUs discarded in the DU; or lowest PDCP SN information of PDCP PDUs discarded in the DU.
  • the processor is configured to: treat received PDCP PDUs with PDCP SNs of the PDCP PDUs discarded in the DU as new data after sending the discard feedback; treat received PDCP PDUs with PDCP SNs of the PDCP PDUs discarded in the DU as new data after receiving an indication from the CU indicating that the PDCP SNs of the PDCP PDUs discarded in the DU are reused for new data; or treat PDCP PDUs with PDCP SNs of the PDCP PDUs discarded in the DU as new data in the case that the PDCP PDUs using the PDCP SNs of the PDCP PDUs discarded in the DU are received in a GTP-U tunnel dedicated for data transmission with reused PDCP SNs.
  • embodiments of the present application provide a technical solution of data transmission, including PSI based discard mechanism and PDU set discard mode switching mechanism between the CU-CP and CU-UP within a RAN node etc. solving issues related to PDU set based discard during data transmission for XR services or the like. Accordingly, the present application can facilitate and improve the implementation of new radio (NR) .
  • NR new radio
  • FIG. 1 illustrates a wireless communication system according to some embodiments of the present application.
  • FIG. 2 is a schematic diagram illustrating an internal structure of a RAN node according to some embodiments of the present application.
  • FIG. 3 is a schematic diagram illustrating an internal structure of a RAN node according to some other embodiments of the present application.
  • FIG. 4 is a flow chart illustrating a method of data transmission using PDU set discard timers according to some embodiments of the present application.
  • FIG. 5 is a flow chart illustrating a method of data transmission using PDU set discard timers according to some other embodiments of the present application.
  • FIG. 6 illustrates a block diagram of an apparatus of data transmission using PDU set discard timers according to some embodiments of the present application.
  • FIG. 7 illustrates a block diagram of an apparatus of data transmission using PDU set discard timers according to some other embodiments of the present application.
  • RAN2 is discussing PDU set based discard mechanism for data transmission of XR service or the like. However, RAN2 will only consider uplink PDU set based discard in the UE side. For downlink PDU set based discard, there are a mass of issues to be solved in the network side, especially in the cases of the CU-DU split RAN architecture (the CU may be further split into CP and UP) .
  • FIG. 1 illustrates a schematic diagram of an exemplary wireless communication system 100 according to some embodiments of the present application.
  • the wireless communication system 100 includes at least one base station (BS) 101 and at least one UE 102.
  • the wireless communication system 100 includes one BS 101 and two terminal device 102 (e.g., a first UE 102a and a second UE 102b) for illustrative purpose.
  • BS base station
  • terminal device 102 e.g., a first UE 102a and a second UE 102b
  • FIG. 1 a specific number of BSs and terminal devices are illustrated in FIG. 1 for simplicity, it is contemplated that the wireless communication system 100 may include more or less BSs and terminal devices in some other embodiments of the present application.
  • the wireless communication system 100 is compatible with any type of network that is capable of sending and receiving wireless communication signals.
  • the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA) -based network, a code division multiple access (CDMA) -based network, an orthogonal frequency division multiple access (OFDMA) -based network, an LTE network, a 3GPP-based network, a 3GPP 5G network, a satellite communications network, a high altitude platform network, and/or other communications networks.
  • TDMA time division multiple access
  • CDMA code division multiple access
  • OFDMA orthogonal frequency division multiple access
  • the BS 101 may communicate with a CN node or entity (not shown) , e.g., a mobility management entity (MME) or a serving gateway (S-GW) , an authentication and mobility management function (AMF) or a user plane function (UPF) etc. via an interface.
  • MME mobility management entity
  • S-GW serving gateway
  • AMF authentication and mobility management function
  • UPF user plane function
  • a BS also be referred to as an access point, an access terminal, a base, a macro cell, a node-B, an enhanced node B (eNB) , a gNB, a home node-B, a relay node, or a device, or described using other terminology used in the art.
  • a BS may also refer to as a RAN node.
  • Each BS may serve a number of UE (s) within a serving area, for example, a cell or a cell sector via a wireless communication link.
  • Neighbor BSs may communicate with each other as necessary, e.g., during a handover procedure for a UE.
  • the terminal device (or remote apparatus) 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , or the like.
  • computing devices such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , or the like.
  • the terminal device may include a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network.
  • the terminal device may include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like.
  • the terminal device may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terminology used in the art.
  • UE is used exemplarily as a classical terminal device for illustrating the terminal device, it should be understood as any type terminal device.
  • FIG. 2 is a schematic diagram illustrating an internal structure of a RAN node, e.g., a BS according to some embodiments of the present application.
  • the internal structure of a RAN node may be split into a CU 200 and at least one DU 202 (e.g., two DUs shown in FIG. 2) .
  • a RAN node e.g., BS 101
  • DU 202 e.g., two DUs shown in FIG. 2
  • FIG. 2 a specific number of DUs 202 are depicted in FIG. 2, it is contemplated that any number of DUs 202 may be included in the BS.
  • the CU 200 e.g., a CU of a gNB (gNB CU, or gNB-CU) and DU 202 e.g., a DU of a gNB (gNB DU, or gNB-DU) are connected with each other by an interface called F1 as specified in 3GPP standard documents.
  • the radio resource control (RRC) layer functionality, service data adaptation protocol (SDAP) functionality, and the PDCP layer functionality are located in the CU 200.
  • the RLC layer functionality, media access control (MAC) layer functionality, and the physical (PHY) layer functionality are located in the DU 202.
  • the CU may be separated into a CU CP unit (also referred to as “CU CP” or “CU-CP” ) and at least one CU UP unit (or also referred to as “CU UP” or “CU-UP” ) .
  • FIG. 3 is a schematic diagram illustrating an internal structure of a BS 300 according to some other embodiments of the present application.
  • the CU of the BS 300 may be separated into a CU-CP 310 and at least one CU-UP 312.
  • the CU-CP 310 and each CU-UP 312 may be connected with each other by an interface called E1 as specified in 3GPP standard documents.
  • the CU-CP 310 and the DU 33 of the BS 300 are connected by an interface called F1-C as specified in 3GPP documents.
  • Each CU-UP 312 and the DU 33 are connected by an interface called F1-U as specified in 3GPP standard documents.
  • a PDU set and PDU set QoS characteristics may be introduced as discussed in TR 23.700-060.
  • a PDU set is composed of one or more PDUs carrying the payload of one unit of information generated at the application level (e.g. a frame or video slice for XR immersion (XRM) services, as used in TR 26.926) .
  • all PDUs in a PDU set are needed by the application layer to use the corresponding information unit.
  • the application layer can still recover part (s) or all of the information unit (s) .
  • PDU sets There are various types of PDU sets. For example, different types of PDU sets can carry different contents, such as intra-coded pictures (also referred to as "I-frame” ) , predictive coded pictures (also referred to as “P-frame” ) , B-predictive coded pictures (also referred to "B-frame” ) . In another example, different types of PDU sets may have different importance or different priority levels.
  • a PDU set may be characterized by a notion of “importance” indicating how important the PDU set (e.g., a video frame) is for an application. For example, an important PDU set may be an I-Frame, while a less important PDU set may be a P-Frame.
  • Importance level of a PDU set may also be referred to as a PSI (or PSI level) , which identifies the relative importance of a PDU set compared to other PDU sets within a QoS flow or cross multiple QoS flows.
  • PSI PSI level
  • the PDU session anchor (PSA) UPF identifies PDUs that belong to PDU sets, determines the PDU set information and sends the PDU set information to the RAN, e.g., NG-RAN in the GTP-U header of a QoS flow.
  • the PDU set information may be different for different PDU sets within a QoS Flow.
  • Exemplary PDU set information may include:
  • Exemplary PSI may include 2 bits importance indication information, wherein the value 0 is to indicate the PDU set with the lowest importance while the value 3 is to indicate the PDU set with the highest importance.
  • PSI may indicate the importance of a PDU within a PDU set.
  • Exemplary PSI may include 2 bits importance indication information, wherein the value 0 is to indicate the PDU in the PDU set with the lowest importance while the value 3 is to indicate the PDU in the set with the highest importance.
  • PDU set based discard mechanism for data transmission with PDU set, e.g., data transmission of XR services or the like
  • PDU set based discard mechanism for data transmission with PDU set, e.g., data transmission of XR services or the like
  • PSI which is also referred to as PSI based discard
  • discard timers associated with PDU set are used (also referred to as PDU set discard timers)
  • PDU set discard timers also referred to as PDU set discard timers
  • one issue is related to how to configure or decide PSI based PDU set discard timer information, e.g., which node configures or decides the value of the PDU set discard timer for each PSI level, especially considering downlink transmission.
  • the PSI is only carried in the GTP-U header of a QoS flow, which means that only the CU-UP can get the PSI after receiving the user data of the QoS flow.
  • the PDU set discard timer is configured (or determined) by the CU-CP, to support PSI based PDU set discard timer configuration for a DRB, the CU-CP needs to be aware of the PSI information associated with the DRB.
  • the PDU set discard timer configuration between the CU-CP and CU-UP within a RAN node should be solved (hereafter, Issue 2) .
  • Another issue is related to discard mode determination (and/or switching) , e.g., determination (and/or switching) of discard mode associated with PDU based discard (also referred to as PDU set discard mode) .
  • PDU based discard also referred to as PDU set discard mode
  • Issue 4 Yet another issue (hereafter, Issue 4) is related to discard indication of user data, e.g., PDU set discard indication. For example, when the CU decides to discard PDU sets for a particular PSI level, how the CU indicates the PDU sets to be discarded to the DU and what information should be provided to the DU.
  • PDU set discard indication For example, when the CU decides to discard PDU sets for a particular PSI level, how the CU indicates the PDU sets to be discarded to the DU and what information should be provided to the DU.
  • an application service flow may contain a video stream for which the UPF performs PDU set detection and determines the GTP-U header markings.
  • the same application service flow may also contain other PDUs such as real-time transport control protocol (RTCP) PDUs (e.g., to control the real-time transport protocol (RTP) flow (s) ) , or PDUs that represent additional media components, such as an audio stream, for which the UPF determines that PDU set classification is not appropriate or not needed.
  • RTCP real-time transport control protocol
  • the PDUs for the non-PDU set traffic are PDU (s) that does not belong to a PDU set based on protocol description.
  • All PDUs that belong to a PDU set based on protocol description or do not belong to a PDU set based on protocol description, may be multiplexed into one application flow, for instance, using the various internet engineering task force (IETF) protocol multiplexing options that cover RTP with multiple media streams, RTCP, simple traversal of UDP over NATs (STUN) , datagram transport layer security (DTLS) -secure real-time transport protocol (SRTP) and web real-time communication (WebRTC) data channel.
  • IETF internet engineering task force
  • STUN simple traversal of UDP over NATs
  • DTLS datagram transport layer security
  • SRTP real-time transport protocol
  • WebRTC web real-time communication
  • embodiments of the present application propose a technical solution of data transmission, e.g., a technical solution of data transmission supporting PDU set based discard based on PSI.
  • an exemplary method of data transmission is provided, which can be performed by a RAN node, e.g., a CU-CP of a gNB.
  • the method includes: determining discard timers, e.g., PDU set discard timers based on different PSI levels associated with a DRB. Each PDU set discard timer is associated with a respective one of the PSI levels.
  • An exemplary PDU set discard timer is a PDCP PDU set discard timer.
  • the transmitting side of an acknowledge mode (AM) RLC entity or the transmitting unacknowledged mode (UM) RLC entity shall discard the indicated RLC SDU, if neither the RLC SDU nor a segment of the RLC SDU has been submitted to the lower layers.
  • the method may further include transmitting information associated with the PDU set discard timers as determined, e.g., to the CU-UP of the gNB via E1AP Bearer Context Setup Request or Bearer Context Modification request messages.
  • another exemplary method of data transmission is provided, which can be performed by a RAN node, e.g., a CU-UP of a gNB.
  • the method includes: receiving information associated with discard timers, e.g., PDU set discard timers for a DRB, e.g., from a CU-CP of the RAN node.
  • Each PDU set discard timer is associated with a PSI level associated with the DRB.
  • An exemplary PDU set discard timer is a PDCP PDU set discard timer.
  • the method may further include transmitting a discard indication, e.g., PDU set discard indication indicating user data associated with a PDU set associated with a corresponding PDU set discard timer to be discarded in the case that a corresponding PDU set discard timer expires, e.g., to a DU of the RAN node in a F1-U frame in a GTP-U extension header.
  • a discard indication e.g., PDU set discard indication indicating user data associated with a PDU set associated with a corresponding PDU set discard timer to be discarded in the case that a corresponding PDU set discard timer expires, e.g., to a DU of the RAN node in a F1-U frame in a GTP-U extension header.
  • yet another exemplary method of data transmission is provided, which can be performed by a RAN node, e.g., a DU of a gNB.
  • the method includes: receiving a discard indication, e.g., PDU set discard indication indicating user data with a PDU set is to be discarded in the DU, e.g., from a CU of the RAN node in a F1-U frame in a GTP-U extension header.
  • the method may further include responsive to receiving the PDU set discard indication, discarding the user data associated with the PDU set.
  • the method may further include transmitting discard feedback associated with the discarded user data to the CU.
  • Embodiments of the present application solve all the above listed issues, e.g., Issues 1 to Issues 6. Accordingly, embodiments of the present application provide an improved data transmission solution, which can support PDU set based discard mechanism considering PSI.
  • the CU-CP of a RAN node e.g., a gNB-CU-CP will be responsible for determining (or configuring) the PDU set discard timer based on PSI information (e.g., deciding the value of the PDU set discard timer for each PSI level) , and send the information associated with the determined PDU set discard timer to the CU-UP of the RAN node, e.g., a gNB-CU-UP.
  • the gNB-CU-CP will get the PSI information either from the CN or from the gNB-CU-UP.
  • the gNB-CU-UP will identify PSI levels in GTP-U headers of received data from the CN, and transmit the PSI Information to the CU-CP via E1AP signalling.
  • the gNB-CU-CP will determine the PSI information, e.g., PSI levels associated with the DRB according to a predefined rule, and then determine (or configure) the PDU set discard timers for each PSI level.
  • the CU-CP of a RAN node e.g., a gNB-CU-CP will decide (or select) a PDU set discard mode from the multiple PDU set discard modes, e.g., an original PDU set discard mode or a PDU set discard mode to be switched to.
  • the gNB-CU-CP will indicate the decided PDU set discard mode to the CU-UP of the RAN node, e.g., a gNB-CU-UP.
  • the gNB-CU-CP will decide (or select) an original PDU set discard mode from the multiple PDU set discard modes, and will indicate the decided original PDU set discard mode to the gNB-CU-UP.
  • the gNB-CU-CP will configure and transmit conditions for switching PDU set discard modes to the CU-UP of a RAN node, e.g., a gNB-CU-UP, so that the gNB-CU-UP can determine switching between different PDU set discard modes based on the conditions for switching PDU set discard modes.
  • the CU of a RAN node (or CU-UP of a RAN node e.g., a gNB-CU-UP) will decide to discard user data according to the PDU set discard timers and send a discard indication to the DU of the RAN node, e.g., a gNB-DU, so that the gNB-DU will perform discard operation based on the discard indication.
  • An exemplary discard indication may indicate user data for at least one PSI level to be discarded at least by including the at least one PSI level in the discard indication.
  • Another exemplary discard indication may indicate user data for at least one PDU set to be discarded at least by including a sequence number of the at least PDU set in the discard indication.
  • Yet another exemplary discard indication may indicate user data to be discarded at least including a sequence number of the user date in the discard indication.
  • the DU may provide discard feedback to the transmitting side, e.g., CU (or CU-UP) of the RAN node (e.g., gNB-CU) , so that the PDCP SNs of the PDCP PDUs discarded in the receiving side can be reused in the transmitting side.
  • Exemplary discard feedback may include PDCP SN information of PDCP PDUs discarded in the receiving side, e.g., the DU.
  • Another exemplary discard feedback may include lowest PDCP SN information of PDCP PDUs discarded in the receiving side, e.g., the DU.
  • the receiving side e.g., the DU can identify the new data with the reused PDCP SNs and will not discard the new data with the reused PDCP SNs is also solved.
  • the receiving side e.g., the DU will treat received PDCP PDUs with PDCP SNs of the PDCP PDUs discarded in the receiving side, e.g., the DU as new data after sending the discard feedback.
  • the DU will treat received PDCP PDUs with PDCP SNs of the PDCP PDUs discarded in the DU as new data after receiving an indication from the CU indicating that the PDCP SNs of the PDCP PDUs discarded in the DU are reused for new data.
  • the DU will treat PDCP PDUs with PDCP SNs of the PDCP PDUs discarded in the DU as new data in the case that the PDCP PDUs using the PDCP SNs of the PDCP PDUs discarded in the DU are received in a GTP-U tunnel dedicated for data transmission with reused PDCP SNs.
  • the UPF if the UPF receives a PDU that does not belong to a PDU set based on protocol description for PDU set identification (which is also referred to as a PDU without PDU set identification information) , the UPF will still map the PDU to a PDU set.
  • a PDU set will be a PDU set only with the PDU without PDU set identification information. Then, the UPF will mark (or insert or the like) the PDU that does not belong to a PDU set with a default PSI (or default PSI level) .
  • An application function may provide 5G CN (5GC) a default PSI for the PDU (s) that does not belong to a PDU set based on protocol description for PDU set identification.
  • 5GC 5G CN
  • the AF may also provide a default PSI.
  • the AF may provide default PSI for different types of PDU that does not belong to a PDU set based on protocol description. e.g., default PSI#1 for RTCP, default PSI#2 for audio packets. That is, the AF provides PDU type (e.g., RTCP, audio) and the associated default PSI instead.
  • the PCF will generate PDU set control information in the policy and charging control (PCC) rule, including the default PSI.
  • PCC policy and charging control
  • the PCF will generate PDU set control information in the PCC rule including PDU set QoS parameters (optional) , protocol description and the default PSI. If the AF request includes both the PDU type and the associated default PSI, then PDU set control information will also contain the PDU type and the associated default PSI.
  • the session management function (SMF) will provide the default PSI associated with a QoS flow for the UPF.
  • the default PSI may be contained in the packet detection rule or other rules provided by the SMF.
  • the default PSI may be contained in the packet detection information similar to the protocol description.
  • a note, e.g., the default PSI is not used for packet detection rule (PDR) matching will be added for the default PSI.
  • the default PSI may be provided to assist PDU set marking when the PDU set identification marking is applied to the PDR. If the PCC rule includes both PDU type and the associated default PSI, then both the PDU type and the associated default PSI will be provided to the UPF.
  • the UPF will map the PDU to a PDU set, wherein the PDU set will only include the PDU that does not belong to a PDU set based on protocol description.
  • the UPF will mark the PDU that does not belong to a PDU set based on protocol description with the default PSI. For example, the UPF will insert the default PSI into the GTP-U header of the PDU that does not belong to a PDU set based on protocol description.
  • the UPF will first identify the PDU type of the PDU that does not belong to a PDU set based on protocol description, e.g., whether it is RTCP or audio or other kinds. Then the UPF will insert the default PSI associated with the identified PDU type into the GTP-U header of the PDU (s) that does not belong to a PDU set.
  • the PCC rules in the SMF have included PDU set QoS parameters and/or protocol description.
  • the SMF may provide the UPF the default PSI associated with the QoS flow based on local configurations. Accordingly, the aforementioned operations in the AF and PCF can be omitted.
  • FIG. 4 is a flow chart illustrating a method of data transmission according to some embodiments of the present application.
  • a split CU of the RAN node e.g., a gNB-CU-CP and gNB-CU-UP
  • a DU coupled to the CU e.g., a gNB-DU
  • the method implemented in the split CU and the DU can be separately implemented and/or incorporated by other apparatus with the like functions.
  • the communication between the CU-UP and DU will be applied to the CU and DU.
  • the CU-CP e.g., a gNB-CU-CP will determine PSI levels associated with a DRB in step 401 in various manners. In some scenarios, there may be multiple QoS flows mapped to a DRB.
  • the gNB-CU-CP will determine the PSI levels associated with (or carried) by all QoS flows mapped to the DRB. For example, QoS flow #1 and QoS flow #2 are mapped to the same DRB, wherein, for QoS flow #1, it has PSI level #1 and PSI level #2; and for QoS flow #2, it has PSI level #1 and PSI level #3.
  • the gNB-CU-CP determines the PSI levels
  • the gNB-CU-CP will determine all PSI levels of QoS flow #1 and QoS flow #2.
  • the gNB-CU-CP will receive PSI information from a CN entity or the CU-UP, e.g., the gNB-CU-UP, and determine the PSI levels associated with the DRB based on the received PSI information.
  • the PSI information may be provided by NG-C control plane signalling, e.g., as a part of PDU set QoS parameters included in PDU session setup request or PDU session modification request related procedure from the SMF to the AMF to the gNB-CU-CP.
  • the gNB-CU-UP will receive the data from the UPF and identify the PSI levels in the GTU-U header or in the GTP-U extension header firstly. Then gNB-CU-UP will send the PSI information to the gNB-CU-CP by E1AP signalling, e.g., in the Bearer Context Modification Required message.
  • the gNB-CU-CP will receive PSI information of each QoS flow mapped to the DRB from a CN entity or the gNB-CU-UP.
  • the PSI information may indicate: the number of PSI levels associated with the QoS flow. For example, there are four PSI levels with 2 bits indication in the PSI information, which means there are 4 PSI levels.
  • the PSI information may indicate: PSI levels associated with the QoS flow. For example, there are four PSI levels with 2 bits indication in the PSI information, explicitly indicating 4 PSI levels, e.g., ⁇ PSI level 0, PSI level 1, PSI level 2 and PSI level 3 ⁇ .
  • the PSI information may include information indicating whether PSI levels are used for user data of the QoS flow, e.g., an indication to indicate whether PSI will be provided in the GTP-U header.
  • the PSI information may indicate any combination of the aforementioned PSI information, e.g., a combination of the number of PSI levels are associated with the QoS, PSI levels associated with the QoS flow and information indicating whether PSI levels are used for user data of the QoS flow.
  • the gNB-CU-CP will receive PSI information of the DRB from the gNB-CU-UP.
  • the PSI information may indicates: the number of PSI levels associated with the DRB; PSI levels associated with the DRB; information indicating whether PSI levels are used for user data of the DRB; or any combination of the number of PSI levels are associated with the DRB; PSI levels associated with the DRB and information indicating whether PSI levels are used for user data of the DRB.
  • the gNB-CU-CP will determine the PSI levels associated with the DRB according to a predefined rule.
  • the PSI levels are fixed or configured to the gNB-CU-CP by default.
  • the gNB-CU-CP may consider only two PSI levels by default, e.g., high importance and low importance. If there is no PSI information is provided by the CN or by the gNB-CU-UP, the gNB-CU-CP will apply the two PSI levels for the QoS flow and/or DRB.
  • the gNB-CU-CP will determine PDU set discard timers, e.g., PDCP PDU set discard timers based on the determined PSI levels.
  • the PDU set discard timers may be per PSI level.
  • Each PDU set discard timer is associated with a PSI level, and the PDU set discard timer may be referred to as a PSI based PDU set discard timer or PDU set discard timer per PSI level or the like.
  • the gNB-CU-CP will configure 4 PDU set discard timers per PSI level, e.g., 4 PDCP PDU set discard timers.
  • the same PSI level may be associated with one or more PDU set discard timers, e.g., in view of different PDU set discard modes.
  • the gNB-CU-CP may determine (or set or configure) different values of PDU set discard timers for different PSI levels. For example, for the PDU set with high PSI level (e.g., high importance) , the gNB-CU-CP will configure a large PDU set discard timer value; while for the PDU set with low PSI level (e.g., low importance) , the gNB-CU-CP will configure a smaller PDU set discard timer value. The larger PDU set discard timer value will ensure transmission of the PDU sets with high PSI level successfully as much as possible.
  • the gNB-CU-CP may set or indicate explicit PDU set discard timer value per PDU set discard timer per PSI level, e.g., ⁇ (PSI level 0, PDU set discard timer 1 ⁇ , ⁇ PSI level0, PDU set discard timer 2 ⁇ .
  • the gNB-CU-CP may set or indicate the PDU set discard timer value by using a legacy discard timer (e.g., as specified in TS 38.323) as the baseline for a certain PSI level by default.
  • the gNB-CU-CP may configure an offset to the legacy discard timer for PDU set discard timers associated with the PSI levels, e.g., ⁇ (PSI level 0, legacy discard timer ⁇ , ⁇ PSI level 0, legacy discard timer + offset ⁇ .
  • the gNB-CU-CP will indicate information associated with the determined or configured PDU set discard timers (or information associated with PDU set discard timers) to the UE for uplink data transmission, e.g., by RRC message; or indicate to the gNB-CU-UP for downlink data transmission, e.g., via E1AP Bearer Context Setup Request or Bearer Context Modification request messages.
  • the gNB-CU-CP will transmit the information associated with the PDU set discard timers as determined to the gNB-CU-UP in step 405.
  • the gNB-CU-UP will decide the discard of user data in step 407. In the case that the gNB-CU-UP makes a discard decision, e.g., in the case that a PDU set discard timer expires, the gNB-CU-UP will send a PDU set discard indication (or referred to as PSI based discard indication or the like) to the gNB-DU in step 409.
  • the PDU set discard indication will be carried in the F1-U frame in the GTP-U extension header, e.g., in the DL User Data frame as specified in TS 38.425.
  • the PDU set discard indication may indicate user data to be discarded in various manners, e.g., indicating user data for at least one PSI level to be discarded or user data for at least one PDU set to be discarded. In the case of indicating to discard user data for a PSI level, the PDU set discard indication will include the PSI level to be discarded. In the case of indicating to discard user data for a PDU set, the PDU set discard indication will include the sequence number of the PDU set to be discarded. In some embodiments of the present application, the PDU set discard indication may explicitly indicate user data to be discarded, e.g., including a sequence number of the user data to be discarded (e.g., PDCP sequence numbers of PDUs) .
  • a sequence number of the user data to be discarded e.g., PDCP sequence numbers of PDUs
  • the gNB-DU will perform discard operation (also referred to as PSI based discard operation or the like) in step 411.
  • the gNB-DU will discard the PDCP PDU if neither a RLC SDU nor a segment of the RLC SDU has been submitted to lower layers.
  • the gNB-DU will discard all PDCP PDUs as indicated with the PSI level, if neither the RLC SDU nor a segment thereof has been submitted to the lower layers.
  • the gNB-DU will discard the PDCP PDU if neither a RLC SDU nor a segment of the RLC SDU has been submitted to lower layers.
  • the gNB-DU will discard all PDCP PDUs as indicated with the PDU set sequence number, if neither the RLC SDU nor a segment thereof has been submitted to the lower layers.
  • the gNB-DU will discard the PDCP PDU in the case that neither a RLC SDU nor a segment of the RLC SDU has been submitted to lower layers.
  • the gNB-DU will discard all PDCP PDUs with the indicated sequence number, if neither the RLC SDU nor a segment thereof has been submitted to the lower layers.
  • the gNB-DU may provide the discard feedback for the gNB-CU, e.g., for the gNB-CU-UP in the case of a split CU in step 413.
  • the discard feedback will include the PDCP SN information for the discarded PDCP PDUs in the F1-U user plane protocol (e.g. in the DL Data Delivery Status frame) .
  • Exemplary discard feedback may include: PDCP SN of the discarded PDCP PDUs, or the lowest PDCP SNs of the discarded PDCP PDUs.
  • a PDU set includes PDUs with PDCP SNs#1, 2, 3 and 4.
  • the gNB-DU When the gNB-DU receives the discard indication indicating to discard PDUs with PDCP SNs#1, 2, 3 and 4, PDU with PDCP SN#1 has been transmitted to the UE or is transmitted to the lower layers. The gNB-DU will only discard PDUs with SNs#2, #3 and #4. Then, in the case of indicating PDCP SN of the discarded PDCP PDUs, the gNB-DU will provide PDCP SNs#2, #3, #4 in the discard feedback for the gNB-CU. In the case of indicating the lowest PDCP SNs of the discarded PDCP PDUs, the gNB-DU will only feed PDCP SN#2 back to the gNB-CU.
  • the gNB-CU will consider that other packets with PDCP SN higher than #2 have also been discarded by the gNB-DU.
  • the gNB-DU may also provide discard feedback to the gNB-CU in other cases, e.g. in non PSI-based discard cases or non PDU set based discard cases etc.
  • the gNB-CU will assign the PDCP SNs of the user data that has been discarded by the gNB-DU to PDCP SDUs (e.g., newly arrived) in step 415.
  • PDCP SDUs e.g., newly arrived
  • some measures are considered as illustrated in the following. Accordingly, the PDCP SN gap caused by discard operation (associated with PDU set discard timers or not) in the gNB-DU will be enhanced.
  • the gNB-CU will transmit an indication to the gNB-DU, indicating that PDCP SNs of the discarded PDCP PDUs are reused for new data.
  • the indication may be transmitted in the F1-U user plane protocol (e.g., the GTP-U header) , for example, in the DL User data frame.
  • the gNB-DU will treat the received PDCP PDUs with PDCP SNs of the discarded PDCP PDUs as new data after receiving such indication from the gNB-CU.
  • the gNB-DU will treat the received PDCP PDUs with PDCP SNs of the discarded PDCP PDUs as new data after sending the discard feedback.
  • the gNB-CU will forward PDCP PDUs using PDCP SNs of the discarded PDCP PDUs in the dedicated GTP-U tunnel, and the gNB-DU will treat the PDCP PDUs with PDCP SNs of the discarded PDCP PDUs received in the dedicated GTP-U tunnel as new data.
  • FIG. 5 is a flow chart illustrating a method of data transmission according to some other embodiments of the present application.
  • the method is illustrated in a system level within a split CU including CU-CP and CU-UP of the RAN node, e.g., between a gNB-CU-CP and gNB-CU-UP, persons skilled in the art should understand that the method implemented in the split CU can be separately implemented and/or incorporated by other apparatus with the like functions.
  • the method is illustrated in PSI based discard, it can also be used in other cases, e.g., in non-PSI based discard or non PDU set based discard etc.
  • the gNB-CU-CP will determine or configure a discard timer for each discard mode in step 501, that is, the discard timer is per mode.
  • the discard timer is per mode.
  • there are two PDU set discard modes (or more) e.g., PDU set non-congestion discard mode (or non-congestion discard mode) and PDU set congestion discard mode (or congestion discard mode) .
  • PDU set non-congestion discard mode or non-congestion discard mode
  • PDU set congestion discard mode or congestion discard mode
  • the discard timer used for the non-congestion discard mode may be a legacy discard timer (configured as legacy in view of the certain PSI level)
  • the discard timer used for the congestion discard mode may be non-legacy discard timer.
  • the gNB-CU-CP will transmit the information associated with the determined discard timer to the gNB-CU-UP in step 503, e.g., in an E1AP Bearer Context Setup Request or Bearer Context Modification Request message.
  • the gNB-CU-CP will decide an original discard mode from the multiple discard modes and indicate the original discard mode to the gNB-CU-UP, e.g., together with or separate from the information associated with the determined discard timer.
  • the gNB-CU-CP will be responsible for deciding the switch of the PDU set discard modes based on switching conditions in step 505a, and then indicate the gNB-CU-UP the decided PDU set discard mode to be switched to in step 505b.
  • the gNB-CU-CP will decide using which discard mode according to the congestion status. For example, the gNB-CU-CP may decide to use the non-congestion discard mode at first.
  • the gNB-CU-CP detects that the network is congested and discard mode switch is needed, the gNB-CU-CP will indicate the congestion discard mode to the gNB-CU-UP, e.g., by a PDCP discard mode switch command, which may an information element (IE) in the Bearer Context Modification Request message that indicates which discard mode will be used for sequent data transmission.
  • IE information element
  • the gNB-CU-UP will select (or activate or the like) the discard timers associated the congestion discard mode.
  • the gNB-CU-CP detects the network is not congested any more, the gNB-CU-CP will decide to switch to the non-congestion discard mode.
  • the gNB-CU-CP will indicate the non-congestion discard mode to the gNB-CU-UP, e.g., by a PDCP discard mode switch command. Accordingly, the gNB-CU-UP will select the discard timers associated the non-congestion discard mode.
  • the gNB-CU-CP will transmit the switching conditions to the gNB-CU-UP in step 507a, and the gNB-CU-UP will be responsible for deciding the switch of the discard modes based on the switching conditions in step 507b.
  • the gNB-CU-CP will configure the switching conditions, e.g., PDU set congestion conditions to the gNB-CU-UP, so that the gNB-CU-UP can switch the PDU set discard mode for a certain PSI level based on the PDU set congestion conditions.
  • the gNB-CU-UP may operate in the non-congestion discard mode at first.
  • the gNB-CU-UP detects that the network is congested and discard mode switch is needed based on the congestion conditions, the gNB-CU-UP will decide to switch to the congestion discard mode and select (or activate) the PDU set discard timer associated with the congestion discard mode.
  • the gNB-CU-UP In the case that the gNB-CU-UP detects that the network is not congested anymore and discard mode switch is needed based on the congestion conditions, the gNB-CU-UP will decide to switch to the non-congestion discard mode and select (or activate) the PDU set discard timer associated with the non-congestion discard mode.
  • FIG. 6 is a block diagram of an apparatus of data transmission according to some embodiments of the present application.
  • the apparatus 600 may include at least one non-transitory computer-readable medium 601, at least one receiving circuitry 602, at least one transmitting circuitry 604, and at least one processor 606 coupled to the non-transitory computer-readable medium 601, the receiving circuitry 602 and the transmitting circuitry 604.
  • the apparatus 600 may be a CU, or a split CU, or a DU configured to perform a method illustrated in the above or the like.
  • the at least one processor 606, transmitting circuitry 604, and receiving circuitry 602 are described in the singular, the plural is contemplated unless a limitation to the singular is explicitly stated.
  • the receiving circuitry 602 and the transmitting circuitry 604 can be combined into a single device, such as a transceiver.
  • the processor 606 may be a central processing unit (CPU) , a digital signaling processing (DSP) , a microprocessor etc.
  • the apparatus 600 may further include an input device, a memory, and/or other components.
  • the non-transitory computer-readable medium 601 may have stored thereon computer-executable instructions to cause the processor 606 to implement the method with respect to the CU, split CU or DU as described above.
  • the computer-executable instructions when executed, cause the processor 606 interacting with receiving circuitry 602 and transmitting circuitry 604, so as to perform the steps with respect to a CU, split CU or DU as depicted above.
  • FIG. 7 illustrates a block diagram of an apparatus 700 of data transmission according to some other embodiments of the present application.
  • the apparatus 700 may include at least one processor 702 and at least one transceiver 704.
  • the transceiver 704 may include at least one separate receiving circuitry 706 and transmitting circuitry 708, or at least one integrated receiving circuitry 706 and transmitting circuitry 708.
  • the at least one processor 702 may be a CPU, a DSP, a microprocessor etc.
  • the processor may be configured to: determine PDU set discard timers based on different PSI levels associated with a DRB, wherein each PDU set discard timer is associated with a respective one of the PSI levels; and transmit, to a CU-UP of the RAN node, information associated with the PDU set discard timers as determined.
  • the processor may be configured to: receive, from a CU-CP of the RAN node, information associated with PDU set discard timers for a DRB, wherein each PDU set discard timer is associated with a PSI level associated with the DRB; and transmit a PDU set discard indication, to a DU of the RAN node, indicating user data associated with a PDU set associated with a corresponding PDU set discard timer to be discarded in the case that the corresponding PDU set discard timer expires.
  • the processor may be configured to: receive, from a CU of the RAN node, a PDU set discard indication, indicating user data associated with a PDU set is to be discarded in the DU; responsive to receiving the PDU set discard indication, discard the user data associated with the PDU set; and transmit discard feedback associated with the discarded user data to the CU.
  • the method according to embodiments of the present application can also be implemented on a programmed processor.
  • the controllers, flowcharts, and modules may also be implemented on a general purpose or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit such as a discrete element circuit, a programmable logic device, or the like.
  • any device capable of implementing the flowcharts shown in the figures may be used to implement the processor functions of this application.
  • an embodiment of the present application provides an apparatus, including a processor and a memory. Computer programmable instructions for implementing a method are stored in the memory, and the processor is configured to perform the computer programmable instructions to implement the method.
  • the method may be a method as stated above or other method according to an embodiment of the present application.
  • An alternative embodiment preferably implements the methods according to embodiments of the present application in a non-transitory, computer-readable storage medium storing computer programmable instructions.
  • the instructions are preferably executed by computer-executable components preferably integrated with a network security system.
  • the non-transitory, computer-readable storage medium may be stored on any suitable computer readable media such as random access memory (RAMs) , read only memory (ROMs) , flash memory, electrically erasable programmable read only memory (EEPROMs) , optical storage devices (compact disc (CD) or digital video disc (DVD) ) , hard drives, floppy drives, or any suitable device.
  • the computer-executable component is preferably a processor but the instructions may alternatively or additionally be executed by any suitable dedicated hardware device.
  • an embodiment of the present application provides a non-transitory, computer-readable storage medium having computer programmable instructions stored therein.
  • the computer programmable instructions are configured to implement a method as stated above or other method according to an embodiment
  • embodiments are provided under specific network architecture and new service scenarios, such as 3GPP 5G, 3GPP LTE, and so on. It is contemplated that along with the developments of network architectures and new service scenarios, all embodiments in the present application are also applicable to similar technical problems. Moreover, the terminologies recited in the present application may change, which should not affect the principle of the present application.
  • the terms “includes, “ “including, “ or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
  • An element proceeded by “a, “ “an, “ or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element.
  • the term “another” is defined as at least a second or more.
  • the terms “having, “ and the like, as used herein, are defined as “including. "

Landscapes

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

Abstract

Des modes de réalisation de la présente demande concernent un procédé et un appareil de transmission de données. Un procédé donné à titre d'exemple, par ex., réalisé par un plan de commande (CP) d'unité centrale (CU) (CU-CP) d'un nœud de réseau d'accès radio (RAN), consiste à : déterminer des temporisateurs de rejet d'ensemble d'unités de données de protocole (PDU) sur la base de différents niveaux d'importance d'ensemble de PDU (PSI) associés à un support radio de données (DRB), chaque temporisateur de rejet d'ensemble de PDU étant associé à un niveau respectif parmi les niveaux PSI ; et transmettre, à un plan utilisateur (UP) de CU (CU-UP) du nœud RAN, des informations associées aux temporisateurs de rejet d'ensemble PDU tels que déterminés.
PCT/CN2023/093930 2023-05-12 2023-05-12 Procédé et appareil de transmission de données utilisant des temporisateurs de rejet d'ensemble d'unités de données de protocole WO2024087585A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/093930 WO2024087585A1 (fr) 2023-05-12 2023-05-12 Procédé et appareil de transmission de données utilisant des temporisateurs de rejet d'ensemble d'unités de données de protocole

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/093930 WO2024087585A1 (fr) 2023-05-12 2023-05-12 Procédé et appareil de transmission de données utilisant des temporisateurs de rejet d'ensemble d'unités de données de protocole

Publications (2)

Publication Number Publication Date
WO2024087585A1 true WO2024087585A1 (fr) 2024-05-02
WO2024087585A9 WO2024087585A9 (fr) 2024-06-13

Family

ID=90829872

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/093930 WO2024087585A1 (fr) 2023-05-12 2023-05-12 Procédé et appareil de transmission de données utilisant des temporisateurs de rejet d'ensemble d'unités de données de protocole

Country Status (1)

Country Link
WO (1) WO2024087585A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200322094A1 (en) * 2018-01-11 2020-10-08 Telefonaktiebolaget Lm Ericsson (Publ) Submitting a PDCP PDU for Transmission
CN113766461A (zh) * 2020-06-01 2021-12-07 中国电信股份有限公司 用户面数据处理方法和基站
CN115696435A (zh) * 2021-07-30 2023-02-03 华为技术有限公司 网络编码场景下的超时丢包方法、装置及可读存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200322094A1 (en) * 2018-01-11 2020-10-08 Telefonaktiebolaget Lm Ericsson (Publ) Submitting a PDCP PDU for Transmission
CN113766461A (zh) * 2020-06-01 2021-12-07 中国电信股份有限公司 用户面数据处理方法和基站
CN115696435A (zh) * 2021-07-30 2023-02-03 华为技术有限公司 网络编码场景下的超时丢包方法、装置及可读存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SRIGANESH RAJENDRAN, SAMSUNG ELECTRONICS CZECH: "Discussion on handling of PDU set prioritization.", 3GPP TSG-RAN WG2 MEETING #121, R2-2301751, 17 February 2023 (2023-02-17), XP052246377 *

Also Published As

Publication number Publication date
WO2024087585A9 (fr) 2024-06-13

Similar Documents

Publication Publication Date Title
EP3469830B1 (fr) Procédé de réalisation d'un rétablissement d'une entité pdcp associée à une entité rlc um dans un système de communication sans fil, et dispositif associé
US10462700B2 (en) Method for performing reflective quality of service (QOS) in wireless communication system and a device therefor
US10680967B2 (en) Method for handling state variables of a PDCP entity in wireless communication system and a device therefor
EP3603168B1 (fr) Procédé de transmission de paquets de données sans perte sur la base d'une structure de qualité de service (qos) dans un système de communication sans fil et dispositif associé
CN108366369B (zh) 一种数据安全传输的方法及接入网、终端、核心网设备
CN110352610B (zh) 在无线通信系统中发送tcp ack分组的方法及其装置
US10396931B2 (en) First network node, second network node and methods for transmitting and receiving a protocol data unit
US20220078247A1 (en) Data Transmission Method and Communications Device
CN108282833B (zh) 处理系统间移动中的分组数据流的装置及方法
US10638353B2 (en) Evolved data compression scheme for unreliable transmission modes
WO2017216510A1 (fr) Fourniture d'une description de flux de données de service
US11647419B2 (en) Adjusting window size based on quality of experience
WO2023184479A1 (fr) Procédé et appareil de prise en charge de mobilité
WO2023087145A1 (fr) Procédés et appareils de gestion de réordonnancement de pdcp
CN112690037A (zh) 终端装置、基站装置以及方法
WO2024087585A1 (fr) Procédé et appareil de transmission de données utilisant des temporisateurs de rejet d'ensemble d'unités de données de protocole
WO2024082361A1 (fr) Procédé et appareil de transmission de données
WO2024082572A1 (fr) Procédés et appareils pour un temporisateur de rejet
US20240107573A1 (en) Data control method and apparatus, communication device, and readable storage medium
WO2022151177A1 (fr) Procédés et appareils de services de diffusion non sélective et de diffusion sélective
WO2020196008A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
CN118160381A (zh) 用于支持pdcp层中归因于分组丢失的分组丢弃操作的方法及设备
CN116017332A (zh) 一种被用于无线通信的通信节点中的方法和装置

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

Country of ref document: EP

Kind code of ref document: A1