[go: up one dir, main page]

WO2024065471A1 - Procédé et dispositif de communication sans fil - Google Patents

Procédé et dispositif de communication sans fil Download PDF

Info

Publication number
WO2024065471A1
WO2024065471A1 PCT/CN2022/122829 CN2022122829W WO2024065471A1 WO 2024065471 A1 WO2024065471 A1 WO 2024065471A1 CN 2022122829 W CN2022122829 W CN 2022122829W WO 2024065471 A1 WO2024065471 A1 WO 2024065471A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
pdu set
drb
protocol layer
layer entity
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/CN2022/122829
Other languages
English (en)
Inventor
Yincheng Zhang
Xiaoyong TANG
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.)
Shenzhen TCL New Technology Co Ltd
Original Assignee
Shenzhen TCL New Technology Co 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 Shenzhen TCL New Technology Co Ltd filed Critical Shenzhen TCL New Technology Co Ltd
Priority to CN202280100504.3A priority Critical patent/CN119948835B/xx
Priority to PCT/CN2022/122829 priority patent/WO2024065471A1/fr
Publication of WO2024065471A1 publication Critical patent/WO2024065471A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/187—Details of sliding window management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1825—Adaptation of specific ARQ protocol parameters according to transmission conditions
    • 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
    • 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/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/28—Timers or timing mechanisms used in protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/321—Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present disclosure relates to the field of telecommunication, and in particular to a wireless communication method and device.
  • Wireless communication systems such as the third-generation (3G) of mobile telephone standards and technology are well known.
  • 3G standards and technology have been developed by the third Generation Partnership Project (3GPP) .
  • the 3rd generation of wireless communications has generally been developed to support macro-cell mobile phone communications.
  • Communication systems and networks have developed towards being a broadband and mobile system.
  • UE user equipment
  • RAN radio access network
  • the RAN comprises a set of base stations (BSs) that provide wireless links to the UEs located in cells covered by the base station, and an interface to a core network (CN) which provides overall network control.
  • BSs base stations
  • CN core network
  • the RAN and CN each conduct respective functions in relation to the overall network.
  • LTE Long Term Evolution
  • E-UTRAN Evolved Universal Mobile Telecommunication System Territorial Radio Access Network
  • 5G or NR new radio
  • the 5G wireless communication system has been designed to deliver enhanced mobile broadband (eMBB) , ultra-reliable low-latency communication (URLLC) , and massive machine type communication (mMTC) services.
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low-latency communication
  • mMTC massive machine type communication
  • Extended reality is an umbrella term covering Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) .
  • AR Augmented Reality
  • MR Mixed Reality
  • VR Virtual Reality
  • XR applications typically require high throughput and low latency and Cloud Gaming is another application with the same requirement.
  • XR and Cloud Gaming are important applications that will be enabled by 5G.
  • XR service is featured by its special traffic streams which is real-time, high data rate, and low latency.
  • XR video streams have are different frames/video slices.
  • a group of pictures (GOP) has I/P/B frames.
  • the date size of different frames varies, and a frame can be segmented into a group of packets.
  • an application can decode frames/video slices if all packets of the frames/video slices are successfully received.
  • a group of packets (referred to as packet group hereafter) belonging to a frame/video slice should be handled as a unit.
  • packets of P frame and B frame depend on the packets of I frame
  • packets of B frame depends on the packets of P frame. That is, a dependency does exist between different groups of packets.
  • the obsolete packet Since the XR service is a real-time service, usually the obsolete packet is useless and should be discarded as earlier as possible. Moreover, due to the dependency of a group of packets for XR service, the obsolete packet is usually a group of packets. In another case, if packet transmission failed in a predefined duration, the lost packets would also incur the discarding of a group of packets according to the dependency.
  • the problem includes:
  • An object of the present disclosure is to propose a wireless communication method and device.
  • an embodiment of the invention provides a wireless communication method, executable in a wireless communication device operates as a transmitter device, and the method comprises:
  • PDUs protocol data units
  • SDU service data unit
  • SDU service data unit
  • SN PDU set sequence number
  • an embodiment of the invention provides a wireless communication device comprising a processor configured to call and run a computer program stored in a memory, to cause a device in which the processor is installed to execute the disclosed method.
  • an embodiment of the invention provides a wireless communication device comprising a processor configured to call and run a computer program stored in a memory, to cause a device in which the processor is installed to execute the disclosed method.
  • the disclosed method may be implemented in a chip.
  • the chip may include a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the disclosed method.
  • the disclosed method may be programmed as computer executable instructions stored in non-transitory computer readable medium.
  • the non-transitory computer readable medium when loaded to a computer, directs a processor of the computer to execute the disclosed method.
  • the non-transitory computer readable medium may comprise at least one from a group consisting of: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a Read-Only Memory, a Programmable Read-Only Memory, an Erasable Programmable Read-Only Memory, EPROM, an Electrically Erasable Programmable Read-Only Memory and a Flash memory.
  • the disclosed method may be programmed as a computer program product, which causes a computer to execute the disclosed method.
  • the disclosed method may be programmed as a computer program, which causes a computer to execute the disclosed method.
  • An embodiment of the disclosure provides a method in which a transmitter device transfers an discarding indication so as to enable a receiver device to properly deal with a sequence number (SN gap) due to group PDU discarding.
  • An embodiment of the disclosure provides a method in which a receiver device receives protocol data units (PDUs) according to a discard control PDU so that PDU reception can works smoothly and properly.
  • PDUs protocol data units
  • FIG. 1 illustrates a schematic view of a telecommunication system.
  • FIG. 2 illustrates a schematic view showing an embodiment of a network for the disclosed wireless communication method.
  • FIG. 3 illustrates a schematic view showing protocol layers of a transmitter device and a receiver device.
  • FIG. 4 illustrates a schematic view showing a wireless communication method according to an embodiment of the present disclosure.
  • FIG. 5 illustrates a schematic view showing a wireless communication method according to an embodiment of the present disclosure.
  • FIG. 6 illustrates a schematic view showing a general model for the layer 2.
  • FIG. 7 illustrates a schematic view showing a delivery window with a fixed window size for each dynamic radio bearer (DRB) and a discard timer for each protocol data unit (PDU) set.
  • DRB dynamic radio bearer
  • PDU protocol data unit
  • FIG. 8 illustrates a schematic view showing update of a delivery window and packet discarding based on the discard timer expiration.
  • FIG. 9 illustrates a schematic view showing an example packet discarding based on failed PDU transmission.
  • FIG. 10 illustrates a schematic view showing optional solutions for determining all PDUs of a PDU set have been transferred.
  • FIG. 11 is a block diagram of a system for wireless communication according to an embodiment of the present disclosure.
  • This invention disclosed a wireless communication method for processing extended reality (XR) traffic in extended reality (XR) service (s) .
  • XR service may include augmented reality (AR) , virtual reality (VR) , or mixed reality (MR) .
  • a packet may be a PDU or a SDU of a protocol layer.
  • packet may refer to a PDU or SDU
  • PDU may refer to a PDU or SDU.
  • a data unit being depended is referred to as a depended data unit, and a data unit depending on the depended data unit is referred to as a dependent data unit.
  • a DRB being depended is referred to as a depended DRB
  • a DRB depending on the depended DRB is referred to as a dependent DRB.
  • a PDU set being depended is referred to as a depended PDU set
  • a PDU set depending on the depended PDU set is referred to as a dependent PDU set.
  • a packet being depended is referred to as a depended packet, and a packet depending on the depended packet is referred to as a dependent packet.
  • a QoS flow being depended is referred to as a depended QoS flow, and a QoS flow depending on the depended QoS flow is referred to as a dependent QoS flow.
  • a sub-QoS flow being depended is referred to as a depended sub-QoS flow, and a sub-QoS flow depending on the depended sub-QoS flow is referred to as a dependent sub-QoS flow.
  • a PDU Set is composed of one or more PDUs carrying a payload of one information unit generated at the application level (e.g. a frame or video slice for XR Services, as used in TR 26.926) .
  • the application level e.g. a frame or video slice for XR Services, as used in TR 26.926, .
  • all PDUs in a PDU Set are needed by the application layer to use the information unit.
  • the application layer can recover parts or all of the information unit, when some PDUs are missing.
  • a PDU set may be a group of packets or PDUs which can be decoded or processed as a whole unit at the Application layer.
  • XR traffic has some potential dependencies between packets of a PDU set and/or dependencies between PDU sets.
  • An service traffic stream of an XR service can comprise different types of PDU sets with different importance levels and QoS requirements.
  • a telecommunication system including a UE 10a, a UE 10b, a base station (BS) 20a, and a network entity device 30 executes the disclosed method according to an embodiment of the present disclosure.
  • FIG. 1 is shown for illustrative, not limiting, and the system may comprise more UEs, BSs, and CN entities. Connections between devices and device components are shown as lines and arrows in the FIGs.
  • the UE 10a may include a processor 11a, a memory 12a, and a transceiver 13a.
  • the UE 10b may include a processor 11b, a memory 12b, and a transceiver 13b.
  • the base station 20a may include a processor 21a, a memory 22a, and a transceiver 23a.
  • the network entity device 30 may include a processor 31, a memory 32, and a transceiver 33.
  • Each of the processors 11a, 11b, 21a, and 31 may be configured to implement proposed functions, procedures and/or methods described in the description. Layers of radio interface protocol may be implemented in the processors 11a, 11b, 21a, and 31.
  • Each of the memory 12a, 12b, 22a, and 32 operatively stores a variety of programs and information to operate a connected processor.
  • Each of the transceivers 13a, 13b, 23a, and 33 is operatively coupled with a connected processor, transmits and/or receives radio signals or wireline signals.
  • the UE 10a may be in communication with the UE 10b through a sidelink.
  • the base station 20a may be an eNB, a gNB, or one of other types of radio nodes, and may configure radio resources for the UE 10a and UE 10b.
  • the network entity device 30 may be a node in a CN.
  • CN may include LTE CN or 5G core (5GC) which includes user plane function (UPF) , session management function (SMF) , 5G core access and mobility management function (AMF) , unified data management (UDM) , policy control function (PCF) , control plane (CP) /user plane (UP) separation (CUPS) , authentication server (AUSF) , network slice selection function (NSSF) , and the network exposure function (NEF) .
  • UPF user plane function
  • SMF session management function
  • AMF 5G core access and mobility management function
  • UDM unified data management
  • PCF policy control function
  • PCF control plane
  • CP control plane
  • UP user plane
  • CUPS authentication server
  • NSSF network slice selection function
  • NEF network exposure function
  • An example of the UE in the description may include one of the UE 10a or UE 10b.
  • An example of the base station in the description may include the base station 20a.
  • Uplink (UL) transmission of a control signal or data may be a transmission operation from a UE to a base station.
  • Downlink (DL) transmission of a control signal or data may be a transmission operation from a base station to a UE.
  • a DL control signal may comprise downlink control information (DCI) or a radio resource control (RRC) signal, from a base station to a UE.
  • DCI downlink control information
  • RRC radio resource control
  • FIG. 2 is a model of a transport network for XR service supported by 5G system.
  • a UE 10 is a 5G terminal which can support XR service and XR application and can be referred to as a client, a client terminal, or an XR client.
  • a gNB 20 is 5G radio node. The gNB 20 communicates with the UE 10 and provides NR user plane and control plane protocol terminations towards the UE via NR Uu interface. The gNB 20 connects via NG interface to a 5GC 300.
  • An UPF 30b is an UPF in the 5GC 300 which is a 5G Core Network.
  • DN 40 is a data network (DN) 40 where an XR server 41 providing XR service is located.
  • DN data network
  • the DN 40 can provide network operator services, Internet access, or 3rd party services.
  • the XR server 41 may include a processor 411, a memory 412, and a transceiver 413.
  • the processor 411 may be configured to implement XR service related functions, procedures and/or methods described in the description. Layers of radio interface protocol may be implemented in the processor 411.
  • the memory 412 operatively stores a variety of programs and information to operate a connected processor.
  • the transceiver 413 is operatively coupled with a connected processor, transmits and/or receives radio signals or wireline signals.
  • Each of the processors 411, 11a, 11b, 21a, and 31 may include an application-specific integrated circuit (ASICs) , other chipsets, logic circuits and/or data processing devices.
  • ASICs application-specific integrated circuit
  • Each of the memory 412, 12a, 12b, 22a, and 32 may include read-only memory (ROM) , a random access memory (RAM) , a flash memory, a memory card, a storage medium and/or other storage devices.
  • Each of the transceivers 413, 13a, 13b, 23a, and 33 may include baseband circuitry and radio frequency (RF) circuitry to process radio frequency signals.
  • RF radio frequency
  • the modules may be stored in a memory and executed by the processors.
  • the memory may be implemented within a processor or external to the processor, in which those may be communicatively coupled to the processor via various means are known in the art.
  • a device executing the wireless communication method may be a transmitter device that transmits an XR traffic flow of an XR service to a receiver device or a receiver device that receives the XR traffic flow.
  • the XR traffic flow may comprise one or more service traffic streams of the XR service.
  • the device executing the wireless communication method may comprise the gNB 20, an XR server 41 in data network 40, or a UE.
  • the XR server 41 in data network 40 may operate as a transmitter device that executes a wireless communication method in some XR traffic delivery occasions, while one or more XR clients (e.g., one or more of the UE 10, UE 10a, and UE 10b) operates as the receiver device receiver the XR traffic flow sent from the transmitter device.
  • an XR client e.g., one or more of the UE 10, UE 10a, and UE 10b
  • the transmitter device may comprise an intermediate device between the UE 10 and the XR server 41.
  • the UE 10 may comprise an embodiment of the UE 10a or UE 10b.
  • the gNB 20 may comprise an embodiment of the base station 20a.
  • the wireless communication method may be executed by a base station, such as another gNB, an eNB, a base station integrating an eNB and a gNB, or a base station for beyond 5G technologies.
  • the UPF/5GC 30b may comprise another network entity of 5GC.
  • a service traffic stream 5 such as an XR stream of an XR service, is established between the UE 10 and the XR server 41.
  • the stream 5 comprise a traffic flow 51 from the XR server 41 to the UE 10 and a traffic flow 52 from the UE 10 to the XR server 41.
  • a layer such as an application layer, a PDCP layer, an RLC layer, an MAC layer, or physical layer (PHY layer or L1 layer)
  • a protocol layer entity may be implemented by a program or a software module executed by a processor or implemented by a hardware module in a integrated circuit (IC) .
  • transmitter device 10c an example of the transmitter device is shown as transmitter device 10c
  • receiver device 10d an example of the receiver device is shown as receiver device 10d.
  • the transmitter device 10c comprise a physical layer (PHY layer or L1 layer) 14c, MAC layer 15c, RLC layer 16c, PDCP layer 17c, RRC layer 18c, and application layer 19c.
  • the receiver device 10d comprise a physical layer (PHY layer or L1 layer) 14d, MAC layer 15d, RLC layer 16d, PDCP layer 17d, RRC layer 18d, and application layer 19d.
  • the layers in transmitter device 10c serves as transmitting protocol layer entities at the transmitting side
  • the layers in receiver device 10d serves as receiving protocol layer entities at the receiving side.
  • Embodiments of the disclosed may be implemented in the PDCP layer or RLC layer.
  • One or more steps (or blocks) in of embodiments of the disclosure may be implemented as computer programs, instructions, software module (s) stored in a memory of the transmitter device, or circuits or hardware module (s) in a processor of the transmitter device, or IC chip (s) , circuits, or plug-in (s) of the transmitter device.
  • a video stream of an XR service will be encoded and compressed in form of frames quasi-periodically with the respective frame periodicity of 1/60, 1/90, or 1/120 the second. Since the transmitter device may divide a video stream of an XR service into a number of transport units, encapsulate and transmit each of the transport units into a transport packet transmitted across the network, the transmission mechanism of the XR service is actually based on packet instead of frame.
  • the size of each of the packets may be variable, the number of the packets may be variable and configurable based on one or more parameters of the QoS requirements and characteristics of the XR service, such as packet delay budget (PDB) , packet error rate (PER) , packet loss rate (PLR) , frame error rate, frame delay budget, resolution, frame rate, and/or data rate.
  • PDB packet delay budget
  • PER packet error rate
  • PLR packet loss rate
  • a transmitter device executes an embodiment of the disclosed method and initiate an XR service.
  • a protocol layer data transmits protocol data units (PDUs) of a PDU set of a service from a protocol layer entity to a lower layer according to a discard timer of the PDU set and a delivery window spaning a plurality of PDU sets (B101) .
  • B101 further comprises the steps in FIG. 5.
  • the protocol layer entity starts the discard timer of the PDU set when the protocol layer entity receives a first service data unit (SDU) associated with the PDU set from a higher layer (C101) .
  • the protocol layer entity receives the subsequent SDU from the higher layer (C102) and determines whether the subsequent SDU is associated with a PDU set sequence number (SN) of the PDU set less than a minimum PDU set SN of the delivery window (C103) .
  • the protocol layer entity discards a subsequent service data unit (SDU) associated with the PDU set when the protocol layer entity receives the subsequent SDU from the higher layer and the subsequent SDU is associated with a PDU set sequence number (SN) of the PDU set less than a minimum PDU set SN of the delivery window (C104) .
  • SDU service data unit
  • SN PDU set sequence number
  • the protocol layer entity generates a PDU from the subsequent SDU for transfer to the lower layer when the PDU set SN associated with the subsequent SDU is not a less than the minimum PDU set SN of the delivery window and the subsequent SDU is not discarded (C105) .
  • the protocol layer entity stops the discard timer when receiving and transferring all the PDUs of the PDU Set to the lower layer (C106) .
  • the protocol layer entity discards all PDUs of the PDU Set and stops the discard timer when the discard timer for the PDU set expires (C107) .
  • one or more of the following parameters are configured for the PDU Set:
  • the delivery window comprises parameters of the minimum PDU set SN and a maximum PDU set SN.
  • the protocol layer entity sets a value of the maximum PDU set SN to a PDU set SN associated with a new arriving SDU of the PDU set received by the protocol layer entity from the higher layer and starts a new discard timer for the PDU set when the PDU set SN associated with the new arriving SDU is greater than the maximum PDU set SN of the delivery window.
  • the protocol layer entity generates a PDU from the new arriving SDU for transfer to the lower layer.
  • the protocol layer entity sets a value of the minimum PDU set SN to a PDU set SN of a next PDU set for which a least one PDU has not been transferred to the lower layer when all the PDUs of the PDU set have been transferred to the lower layer and the PDU set SN of the PDU Set is equal to the minimum PDU set SN of the delivery window.
  • the delivery window comprises parameters of the minimum PDU set SN and a window size.
  • the protocol layer entity discards the subsequent SDU when the PDU set SN associated with the subsequent SDU is greater than the maximum PDU set SN of the delivery window.
  • the protocol layer entity sets a value of the minimum PDU set SN to a PDU set SN of a next PDU set for which a least one PDU has not been transferred to the lower layer and sets a value of the maximum PDU set SN to the minimum PDU set SN plus the window size when all the PDUs of the PDU set have been transferred to the lower layer and the PDU set SN of the PDU Set is equal to the minimum PDU set SN of the delivery window.
  • the delivery window comprises parameters of a maximum PDU set SN and a window size.
  • the protocol layer entity sets a value of the maximum PDU set SN to a PDU set SN associated with a new arriving SDU of the PDU set received by the protocol layer entity from the higher layer and starts a new discard timer for the PDU set when the PDU set SN associated with the new arriving SDU is greater than the maximum PDU set SN of the delivery window.
  • the protocol layer entity sets a value of the minimum PDU set SN to the maximum PDU set SN minus the window size.
  • the protocol layer entity generates a PDU from the new arriving SDU for transfer to the lower layer.
  • the protocol layer entity discards all the SDU for which the associated PDU Set SN is less than the minimum PDU set SN.
  • the delivery window is configured for a first dynamic radio bearer (DRB) .
  • DRB dynamic radio bearer
  • the protocol layer entity discards all the PDUs of the PDU set upon expiration of the discard timer of the PDU set showing that at least one depended PDU in the PDU set is discarded.
  • the protocol layer entity updates the delivery window for the first DRB.
  • the protocol layer entity discards all PDUs of a first dependent PDU set in the first DRB which is intra-DRB dependent on the PDU set in the same DRB upon expiration of the discard timer of the PDU set.
  • the protocol layer entity stops a discard timer of the first dependent PDU set.
  • the protocol layer entity updates the delivery window for the first DRB.
  • the protocol layer entity discards all PDUs of a second dependent PDU set in a second DRB which is inter-DRB dependent on the PDU set in the first DRB upon expiration of the discard timer of the PDU set.
  • the protocol layer entity stops a discard timer of the second dependent PDU set.
  • the protocol layer entity updates the delivery window for the first DRB and a delivery window for the second DRB.
  • the protocol layer entity determines all SDUs of the PDU set has been received by the protocol layer entity and all PDUs of the PDU set have been transferred to the lower layer by the protocol layer entity based on a number of PDUs for the PDU set or an indicator that indicates the last PDU of the PDU set.
  • the transmitter device is a base station.
  • the number of PDUs for the PDU Set is provided by a 5G core (5GC) via an NG Application Protocol (NGAP) message or a General Packet Radio Service Tunnelling Protocol-user plane (GTP-U) PDU.
  • An indicator that indicates the last PDU of the PDU set is received from the 5GC via an NGAP message or a GTP-U PDU.
  • the transmitter device is a user equipment (UE) .
  • the number of PDUs for the PDU Set is provided by an application layer of the UE.
  • An indicator that indicates the last PDU of the PDU set is provided by the application layer of the UE.
  • the transmitter device is a base station.
  • a period timed by the discard timer is configured by a 5G core (5GC) via an NG Application Protocol (NGAP) message or a General Packet Radio Service Tunnelling Protocol-user plane (GTP-U) PDU.
  • 5GC 5G core
  • NGAP NG Application Protocol
  • GTP-U General Packet Radio Service Tunnelling Protocol-user plane
  • the transmitter device is a user equipment (UE) .
  • a period timed by the discard timer is configured by a base station via a radio resource control (RRC) message or is configured by an application of the UE.
  • RRC radio resource control
  • the transmitting PDUs of the PDU set from the protocol layer entity to the lower layer is performed in the order of PDU Set SN.
  • the transmitting PDUs of the PDU set from the protocol layer entity to the lower layer are performed in the order of the arrival time for the PDUs.
  • FIG. 6 is a general model for the layer 2 which is responsible for the data transmission.
  • 3GPP TS 38.321 v17.1.0 for media access control (MAC)
  • 3GPP TS 38.321 v17.1.0 for radio link layer (RLC)
  • 3GPP TS 38.321 v17.1.0 for packet data convergence protocol (PDCP)
  • XR is a kind of real-time and interactive service
  • UM unacknowledge mode
  • RLC radio link layer
  • PDCP packet data convergence protocol
  • each HARQ process supports one transport block (TB ) and each HARQ process is associated with a HARQ process identifier.
  • a TB can be transmitted or re-transmitted multiple times if the transmission fails.
  • the transmission or retransmission for a TB can be terminated when the TB was transmitted successfully or the maximum retransmission times were met or a timer for the TB transmission expires.
  • the maximum retransmission times and the duration of the timer can be configurable or predefined.
  • the transmission for the TB can be regarded as failed transmission.
  • the MAC should report the status information of the data transfer service to an upper layer, such as the RLC layer.
  • the status information can include an indication of successful delivery or unsuccessful delivery of RLC PDUs.
  • RLC can interpret the status information from MAC into the status information of the data transfer service provided by RLC to the upper layer, such as the PDCP layer, especially for the UM data transfer service.
  • RLC can include an indication of successful delivery or unsuccessful delivery of PDCP PDUs to PDCP.
  • a method for PDU delivery to lower layer for a dynamic radio bearer (DRB) based on PDU Set and the dependency configuration is disclosed in the followings.
  • a delivery window or buffering queue is defined based on PDU Set and the sequence number (SN) of PDU Set, and/or packets associated with PDU Set, and/or PDUs for a protocol layer associated with PDU Set for the DRB.
  • the window or queue can be defined with one or more parameters in the set ⁇ minimum PDU Set, minimum PDU Set SN, window size based on PDU Set, maximum PDU Set, maximum PDU Set SN ⁇
  • the delivery window or buffering queue is defined based on PDCP PDU, each PDCP PDU belongs to a PDU Set, and each PDU Set can comprise a plurality of PDCP PDUs.
  • Each PDCP PDU is associated with the SN of the PDU Set to which the PDCP PDU belongs. Especially, if segmentation is supported in PDCP, each PDCP PDU should only include a segment from SDUs which belong to the same PDU Sets.
  • the delivery window or buffering queue is defined based on RLC PDU, each RLC PDU belongs to a PDU Set, and each PDU Set can comprise a plurality of RLC PDUs.
  • Each RLC PDU is associated with the SN of the PDU Set to which the RLC PDU belongs.
  • each RLC PDU should only include a segment from SDUs which belong to the same PDU Sets.
  • the size for the window or queue is configured and fixed: the window is define based on minimum PDU Set SN and window size.
  • the window size can be configurable and configured when the PDCP or RLC entity is established or re-established for a DRB.
  • the window size can be configured based on one or more characteristic parameters of the PDU Set for the DRB.
  • the characteristic parameters can comprise periodicity, packet jitter information, a delay budget, a packet size, a number of packets, which can be configured by the 5GC via NG Application Protocol (NGAP) message.
  • NGAP NG Application Protocol
  • the window size can be configured by gNB via an radio resource control (RRC) message.
  • RRC radio resource control
  • the size for the window or queue is variable.
  • the window is defined based on minimum PDU Set SN.
  • the size can be variable as the SN of a new arrived PDU changes.
  • a discard timer is associated with each PDU Set for a DRB.
  • a layer e.g., MAC, RLC, or PDCP
  • a new discard timer is started and associated with the SN of the PDU Set.
  • an expiring period for the discard timer for all PDU Sets for a DRB can be configured with the same value by the 5GC (e.g., 5GC 30) via an NGAP message.
  • the expiring period for the discard timer for all PDU Sets for a DRB can be configured with the same value by the gNB (e.g., gNB 20) via an RRC message.
  • the expiring period for the discard timer for a PDU Set for a DRB can be configured by the 5GC via GTP-U PDU which is used to transfer the packet for the PDU Set from the 5GC to gNB.
  • the expiring period for the discard timer for a PDU Set for a DRB can be configured by the application (i.e., the application layer or an application layer entity) in the UE.
  • a discard timer is associated with a PDU Set and configured with an expiring period.
  • the discard timer of the PDU Set is started and when the first SDU related to the PDU Set is received.
  • a protocol layer entity e.g., the PDCP, RLC, or MAC layer of the transmitter device performs packet discarding for the PDU Set in response to expiration of the discard timer of the PDU Set.
  • the protocol layer entity When receiving and transferring all the PDUs of the PDU Set to the lower layer, the protocol layer entity stops the discard timer for the PDU Set.
  • One or more following parameters are configured for the DRB to which the PDU Sets belong:
  • the inter-DRB dependency configuration Information (or a configuration) of inter-DRB dependency includes a DRB identifier (ID) of a DRB on which a DRB depends, and/or the treatment for dependency.
  • the DRB being depended is referred to as a depended DRB, and the DRB depending on the depended DRB is referred to as a dependent DRB.
  • treatment of inter-DRB dependency indicates whether to discard unsent PDUs of one or more other PDU Sets in an Inter-DRB dependent DRB which are Inter-DRB dependent on the lost or discarded PDU Set in an Inter-DRB depended DRB.
  • the intra-DRB dependency configuration indicates whether a PDU Set in a DRB is dependent on another PDU Set in the same DRB, and/or the treatment for dependency.
  • Information (or a configuration) of intra-DRB dependency may include a PDU Set identifier (ID) of a PDU Set on which a PDU Set depends, and/or the treatment for dependency.
  • the PDU set being depended is referred to as a depended PDU set, and the PDU set depending on the depended PDU set is referred to as a dependent PDU set.
  • the depended PDU set and the dependent PDU set are in the same DRB.
  • the treatment (or a configuration) of intra-DRB dependency indicates whether to discard the unsent PDUs of the dependent PDU Set which is Intra-DRB dependent on the lost or discarded PDU Set for the same DRB.
  • the intra-PDU-Set dependency configuration indicates whether one or more packets (e.g., PDU) belonging to one or more PDU Sets is dependent on a packet in the same PDU Set, and the treatment for dependency.
  • Information (or a configuration) of intra-PDU-Set dependency may include a PDU identifier (ID) on which another PDU depends, and/or the treatment for dependency.
  • the PDU being depended is referred to as a depended PDU, and the PDU depending on the depended PDU is referred to as a dependent PDU.
  • the depended PDU and the dependent PDU are in the same PDU set.
  • treatment of the intra-PDU-Set dependency indicates, if one depended PDU is lost or discarded, whether to discard the unsent dependent PDUs in the same PDU Set.
  • three DRBs are configured for a XR service, t represents an axis in a time domain, and variables n and x are positive integers. Those three DRBs can be further configured as a DRB group.
  • the DRB 1 is independent
  • the DRB 2 is Inter-DRB dependent on the DRB 1
  • the DRB 3 is Inter-DRB dependent on DRB 1 and DRB 2.
  • the DRB 2 is configured with Intra-DRB dependency.
  • the DRB 2 and DRB 3 are all configured with Intra-PDU-Set dependency.
  • the dependency treatment can be configured with the value of “discard” .
  • a window or queue is defined for each DRB, and the minimum PDU Set SN of the window or queue is named as Minimum_PDU_Set_SN and should be set to 0 for the DRB establishment or re-establishment.
  • a discarding timer is named discard_timer (n) for PDU Set SN n and should be started and configured with an expiring period for a PDU Set.
  • a window is used as an example.
  • a window is defined for each DRB, and the window size is variable.
  • the Minimum_PDU_Set_SN is used as a baseline, an additional parameter Maximum_PDU_Set_SN is used to record the SN which is equal to the biggest SN of a new arrived SDU plus 1.
  • an SN of the SDU is associated with an SN of the PDU Set and is represented as PDU_Set_SN (SDU) . (Note that the following SN comparison should consider the PDU Set SN wraparound)
  • a window is defined for each DRB, and the window size are configured with a static value.
  • the Minimum_PDU_Set_SN is used as a baseline, the Maximum_PDU_Set_SN used for the window is equal to Minimum_PDU_Set_SN plus window size.
  • SN related to the SDU in the following operations represented by pseudo codes is the SN PDU_Set_SN (SDU) of the PDU Set which is equal to the SN of the related PDU Set. (Note that the following SN comparison should consider the PDU Set SN wraparound)
  • a window is defined for each DRB, and the window size are configured with a static value.
  • Variables n and x are intergers.
  • the Maximum_PDU_Set_SN is used as a baseline,
  • the Minimum_PDU_Set_SN used for the window is equal to Maximum_PDU_Set_SN minus window size.
  • a discard timer is started and configured with an expiring period and associated with a PDU Set when the first SDU related to the PDU Set is received.
  • Solution 1 For the gNB side, the number of PDUs for a PDU Set is provided by the 5GC via an NGAP message or a GTP-U PDU. For the UE side, the number of PDUs for a PDU Set is provided by the application layer. When the number of the received and delivered PDU is equal to the provided number of PDUs for a PDU Set, a protocol layer entity of the transmitter device (e.g., the gNB or the UE) can determine that all the PDUs of a PDU Set is received and delivered to lower layer. In this case, the PDU reception and delivery for a PDU Set can be out of sequence or in sequence.
  • Solution 2 For the gNB side, an indicator indicating the last PDU of a PDU Set is received from the 5GC via an NGAP message or a GTP-U PDU; For the UE side, an indicator indicating the last PDU for a PDU Set is provide by the application layer. In this case, the PDU reception and delivery for a PDU Set can be in sequence.
  • the corresponding protocol layer should support the functionality of buffering the arriving PDU (s) in advance.
  • the PDUs of different PDU Sets for a DRB can be delivered to the low layer in order of arrival time regardless of the order of SN for different PDU Sets.
  • variables n, k, x, y, and z are positive integers.
  • a protocol layer entity of the transmitter device e.g., the gNB or the UE
  • a protocol layer entity of the transmitter device e.g., the gNB or the UE
  • FIG. 11 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present disclosure. Embodiments described herein may be implemented into the system using any suitably configured hardware and/or software.
  • FIG. 11 illustrates the system 700 including a radio frequency (RF) circuitry 710, a baseband circuitry 720, a processing unit 730, a memory/storage 740, a display 750, a camera 760, a sensor 770, and an input/output (I/O) interface 780, coupled with each other as illustrated.
  • RF radio frequency
  • the processing unit 730 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors.
  • the processors may include any combinations of general-purpose processors and dedicated processors, such as graphics processors and application processors.
  • the processors may be coupled with the memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems running on the system.
  • the radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc.
  • the baseband circuitry may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry may support communication with 5G NR, LTE, an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) .
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • the baseband circuitry 720 may include circuitry to operate with signals that are not strictly considered as being in a baseband frequency.
  • baseband circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.
  • the system 700 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, etc.
  • the system may have more or less components, and/or different architectures.
  • the methods described herein may be implemented as a computer program.
  • the computer program may be stored on a storage medium, such as a non-transitory storage medium.
  • the embodiment of the present disclosure is a combination of techniques/processes that can be adopted in 3GPP specification to create an end product.
  • the software function unit is realized and used and sold as a product, it can be stored in a readable storage medium in a computer.
  • the technical plan proposed by the present disclosure can be essentially or partially realized as the form of a software product.
  • one part of the technical plan beneficial to the conventional technology can be realized as the form of a software product.
  • the software product in the computer is stored in a storage medium, including a plurality of commands for a computational device (such as a personal computer, a server, or a network device) to run all or some of the steps disclosed by the embodiments of the present disclosure.
  • the storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM) , a random access memory (RAM) , a floppy disk, or other kinds of media capable of storing program codes.

Landscapes

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

Abstract

L'invention concerne un procédé de communication sans fil, exécutable dans un dispositif de communication sans fil. Le dispositif transmet des unités de données de protocole (PDU) d'un ensemble de PDU d'un service d'une entité de couche de protocole à une couche inférieure selon un temporisateur de rejet de l'ensemble de PDU et une fenêtre de distribution couvrant une pluralité d'ensembles de PDU.
PCT/CN2022/122829 2022-09-29 2022-09-29 Procédé et dispositif de communication sans fil Ceased WO2024065471A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280100504.3A CN119948835B (en) 2022-09-29 Wireless communication method and device
PCT/CN2022/122829 WO2024065471A1 (fr) 2022-09-29 2022-09-29 Procédé et dispositif de communication sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/122829 WO2024065471A1 (fr) 2022-09-29 2022-09-29 Procédé et dispositif de communication sans fil

Publications (1)

Publication Number Publication Date
WO2024065471A1 true WO2024065471A1 (fr) 2024-04-04

Family

ID=90475396

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/122829 Ceased WO2024065471A1 (fr) 2022-09-29 2022-09-29 Procédé et dispositif de communication sans fil

Country Status (1)

Country Link
WO (1) WO2024065471A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180146504A1 (en) * 2015-05-15 2018-05-24 Sharp Kabushiki Kaisha Method for reconfiguring data radio bearer and user equipment
CN110383880A (zh) * 2017-08-11 2019-10-25 Lg电子株式会社 用于发送数据单元的方法和设备
US20200196374A1 (en) * 2017-06-16 2020-06-18 Intel Corporation L2 handling for bearer type change

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180146504A1 (en) * 2015-05-15 2018-05-24 Sharp Kabushiki Kaisha Method for reconfiguring data radio bearer and user equipment
US20200196374A1 (en) * 2017-06-16 2020-06-18 Intel Corporation L2 handling for bearer type change
CN110383880A (zh) * 2017-08-11 2019-10-25 Lg电子株式会社 用于发送数据单元的方法和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "PDCP PDU Discarding by Secondary RLC entities", 3GPP DRAFT; R2-2000818, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Elbonia; 20200224 - 20200306, 13 February 2020 (2020-02-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051848612 *

Also Published As

Publication number Publication date
CN119948835A (zh) 2025-05-06

Similar Documents

Publication Publication Date Title
US20250056319A1 (en) Communication method and apparatus
US20250365615A1 (en) Data processing method and apparatus
US20250351125A1 (en) Methods and apparatuses for enhancements of a data discarding operation
WO2023133900A1 (fr) Procédé de traitement de trafic à réalité étendue et dispositif émetteur
US20250158934A1 (en) Methods and apparatuses for supporting a packet discarding operation in a pdcp layer due to a packet loss
CN112399477B (zh) 一种通信方法及设备
WO2024065471A1 (fr) Procédé et dispositif de communication sans fil
CN119948835B (en) Wireless communication method and device
WO2023168573A1 (fr) Procédé et dispositif de communication sans fil pour trafic de réalité étendue
WO2024065477A1 (fr) Procédé et dispositif de communication sans fil
GB2629871A (en) Methods for controlling a packet data convergence protocol communication network
WO2024065470A1 (fr) Procédé de communication sans fil et station de base
WO2024073877A1 (fr) Procédé et dispositif de communication sans fil
CN116261848A (zh) 用于新无线电的无线电链路控制累积模式
EP4576926A1 (fr) Procédé et appareil de transmission de données
WO2025030466A1 (fr) Procédé et dispositif de communication sans fil
US12375211B2 (en) Radio link control cumulative mode for new radio
EP4668845A1 (fr) Procédé et appareil de traitement de données
WO2025030296A1 (fr) Procédé de communication sans fil, équipement utilisateur et station de base
WO2023197143A1 (fr) Station de base, équipement utilisateur et procédé de traitement de réalité étendue
CN120711447A (zh) 一种通信方法及相关设备
GB2640203A (en) Method for managing data transmission in a communication network
WO2025247157A1 (fr) Procédé de transmission de données, appareil de communication et dispositif de communication
WO2024208024A1 (fr) Procédé de communication et appareil de communication
WO2024231496A1 (fr) Procédés de commande d'un réseau de communication de protocole de convergence de données par paquets

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202280100504.3

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 202280100504.3

Country of ref document: CN

122 Ep: pct application non-entry in european phase

Ref document number: 22960108

Country of ref document: EP

Kind code of ref document: A1