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

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

Info

Publication number
WO2024065477A1
WO2024065477A1 PCT/CN2022/122836 CN2022122836W WO2024065477A1 WO 2024065477 A1 WO2024065477 A1 WO 2024065477A1 CN 2022122836 W CN2022122836 W CN 2022122836W WO 2024065477 A1 WO2024065477 A1 WO 2024065477A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
window
pdcp
rlc
discard
Prior art date
Application number
PCT/CN2022/122836
Other languages
English (en)
Inventor
Yincheng Zhang
Xiaoyong TANG
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 PCT/CN2022/122836 priority Critical patent/WO2024065477A1/fr
Publication of WO2024065477A1 publication Critical patent/WO2024065477A1/fr

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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1832—Details of sliding window management
    • 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

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 discard 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, comprising:
  • control PDU comprises one or more SN windows in which SNs for the discarded PDUs are continuous.
  • an embodiment of the invention provides a wireless communication 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 method, executable in a wireless communication device, comprising:
  • control PDU that indicates sequence number (SN) information of discarded protocol data units (PDUs) discarded by the transmitter device
  • control PDU comprises one or more SN windows in which SNs for the discarded PDUs are continuous.
  • 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 disclosure.
  • FIG. 5 illustrates a schematic view showing an example of packet discarding.
  • FIG. 6 illustrates a schematic view showing an example of packet discarding.
  • FIG. 7 illustrates a schematic view of a packet data convergence protocol (PDCP) discard indication protocol data unit (PDU) .
  • PDCP packet data convergence protocol
  • PDU protocol data unit
  • FIG. 8 illustrates a schematic view of a radio link control (RLC) discard indication PDU with 12 bit SN.
  • RLC radio link control
  • FIG. 9 illustrates a schematic view showing a method of PDU discarding at a receiving PDCP layer entity.
  • FIG. 10 illustrates a schematic view showing modified PDU receiving at a receiving RLC layer entity.
  • FIG. 11 illustrates a schematic view showing a method of PDU discarding in a receiving PDCP layer entity.
  • FIG. 12 illustrates a schematic view showing modified PDU receiving at a receiving RLC layer entity.
  • FIG. 13 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 11 b, 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, 11 b, 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, 11 b, 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, 11 b, 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 the transmitter device is shown as transmitter device 10c
  • receiver device 10d an example of the 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
  • the transmitter device 10c and the receiver device 10d execute an embodiment of the disclosed method and initiate an XR service.
  • the transmitter device 10c transmits to the receiver device 10d a control PDU that indicates sequence number (SN) information of discarded protocol data units (PDUs) discarded by a protocol layer entity of the transmitter device (310) .
  • the control PDU comprises one or more SN windows in which SNs for the discarded PDUs are continuous.
  • the receiver device 10d receives from the transmitter device 10c a control PDU that indicates sequence number (SN) information of discarded protocol data units (PDUs) discarded by the transmitter device (303) .
  • SN sequence number
  • PDUs protocol data units
  • the control PDU comprises one or more SN windows in which SNs for the discarded PDUs are continuous.
  • the control PDU may be a control PDU of a protocol layer, such as PDCP, RLC, and/or others.
  • the control PDU comprises a field of E that indicates whether or not configuration of another SN window follows the field of E. Thus, multiple SN windows can be indicated in one control PDU.
  • the 301 and 303 may be performed at the protocol layer.
  • control PDU being a packet data convergence protocol (PDCP) discard indication PDU comprises a field of PDU type indicating a PDU type of PDCP discard indication PDU.
  • PDCP packet data convergence protocol
  • the PDCP discard indication PDU comprises configuration of an SN window among the one or more SN windows, and the configuration of the SN window comprises:
  • ⁇ a field of MinDC in the PDCP discard indication PDU means Minimum Discard COUNT corresponding to the minimum PDCP PDU SN in the SN window
  • ⁇ a field of MaxDC in the PDCP discard indication PDU means Maximum Discard COUNT corresponding to the maximum PDCP PDU SN in the SN window.
  • a protocol layer entity of the receives discards received PDUs in the SN window when a PDCP data PDU is received from a lower layer.
  • the protocol layer entity is PDCP layer and the lower layer is a radio link control (RLC) layer.
  • RLC radio link control
  • the protocol layer entity modifies a parameter that indicating an count value of a waiting PDU in a PDCP layer of the receiver device to MaxDC+1 when a PDCP data PDU is received from a lower layer, wherein the waiting PDU has not been transmitted to an upper layer.
  • the parameter is RX_DELIV or RX_NEXT.
  • the protocol layer entity modifies a parameter that indicating an count value of a waiting PDU in a PDCP layer of the receiver device to MaxDC+1 when a timer t-Reordering expires, wherein the waiting PDU has not been transmitted to an upper layer.
  • the parameter is RX_DELIV.
  • control PDU being a radio link control (RLC) discard indication PDU comprises a field of PDU type indicating a PDU type of RLC discard indication PDU.
  • RLC radio link control
  • the RLC discard indication PDU comprises configuration of an SN window among the one or more SN windows, and the configuration of the SN window comprises:
  • ⁇ a field of MinSN in the RLC discard indication PDU means the Minimum Discard SN corresponding to the minimum RLC PDU SN in the SN window
  • ⁇ a field of MaxSN in the RLC discard indication PDU means the Maximum Discard SN corresponding to the maximum RLC PDU SN in the SN window.
  • a protocol layer entity of the receives discards received PDUs in the SN window when an UMD PDU is received from a lower layer.
  • the protocol layer entity is RLC layer and the lower layer is a medium access control (MAC) layer.
  • MAC medium access control
  • the protocol layer entity modifies a parameter that indicating an earliest SN for reassembly in an RLC layer of the receiver device to MaxSN+1 when an UMD PDU is placed in a reception buffer of the RLC layer.
  • the parameter is RX_Next_Reassembly or RX_Next_Highest.
  • the protocol layer entity modifies a parameter that indicating an earliest SN for reassembly in an RLC layer of the receiver device to MaxSN+1 when a timer t-Reassembly expires.
  • the parameter is RX_Next_Reassembly.
  • a PDU Set can comprise a plurality of packets or PDUs, including dependent PDUs and depended PDUs
  • a method to deal with the SN gap due to the packet discarding is disclosed in the following, especially for the transmission based on PDCP and UM RLC protocol.
  • the transmitter device transmits a control PDU to a receiver device to indicate SN information of the discarded PDUs.
  • the indicated SN information includes one or more of the following:
  • each window comprises:
  • a PDCP control PDU can be defined as FIG. 7 and named as a PDCP discard indication PDU:
  • a new PDU Type is defined as the PDU discard indicator (i.e., a PDU type of the PDCP discard indication PDU) .
  • a field of MinDC in the PDCP discard indication PDU means Minimum Discard COUNT corresponding to the minimum PDCP PDU SN in the SN window.
  • a field of MaxDC in the PDCP discard indication PDU means Maximum Discard COUNT corresponding to the maximum PDCP PDU SN in the SN window.
  • MinDC and MaxDC are configuration of an SN window.
  • a field of E in the PDCP discard indication PDU is an optional extension bit to indicates whether or not another SN window follows.
  • a value 1 for the field of E means another SN window follows and a value 0 means no other SN window follows.
  • a value 1 for the field of E means configuration of a subsequent SN window follows the configuration of the SN window before the field E and a value 0 means no configuration of any other SN window follows the configuration of an SN window before the field E.
  • an RLC control PDU can be defined for RLC UM data transfer and named RLC discard indication PDU:
  • a new field of CPT (Control PDU Type) in the RLC discard indication PDU is defined as the PDU discard indicator (i.e., a PDU type of the RLC discard indication PDU) .
  • a field of MinSN in the RLC discard indication PDU means the Minimum Discard SN corresponding to the minimum RLC PDU SN in the SN window.
  • a field of MaxSN in the RLC discard indication PDU means the Maximum Discard SN corresponding to the maximum RLC PDU SN in the SN window.
  • MinDC and MaxDC are configuration of an SN window.
  • a field of E in the RLC discard indication PDU is an optional extension bit to indicates whether or not another SN window follows.
  • a value 1 for the field of E means another SN window follows and a value 0 means no other SN window follows.
  • a value 1 for the field of E means configuration of a subsequent SN window follows the configuration of the SN window before the field E and a value 0 means no configuration of any other SN window follows the configuration of an SN window before the field E.
  • the length of the SN can be different and the format of the RLC control PDU can be different accordingly.
  • RX_NEXT This state variable indicates the COUNT value of the next PDCP SDU expected to be received.
  • the initial value is 0, except for sidelink broadcast and groupcast, and for SRBs configured with state variables continuation.
  • the initial value of the SN part of RX_NEXT is (x +1) modulo (2 [sl-PDCP-SN-Size] ) , where x is the SN of the first received PDCP Data PDU.
  • the initial value is the value stored in PDCP entity for the corresponding source SRB.
  • source SRB configured with state variables continuation the initial value is the value stored in PDCP entity for the corresponding target SRB.
  • RX_NEXT For NR sidelink communication for broadcast and groupcast, it is up to UE implementation to select the HFN part for RX_NEXT such that initial value of RX_DELIV should be a positive value.
  • RX_DELIV This state variable indicates the COUNT value of the first PDCP SDU not delivered to the upper layers, but still waited for.
  • the initial value is 0, except for sidelink broadcast and groupcast, and for SRBs configured with state variables continuation.
  • the initial value of the SN part of RX_DELIV is (x –0.5 ⁇ 2 [sl-PDCP-SN-Size–1] ) modulo (2 [sl-PDCP-SN-Size] ) , where x is the SN of the first received PDCP Data PDU.
  • the initial value is the value stored in PDCP entity for the corresponding source SRB.
  • the initial value is the value stored in PDCP entity for the corresponding target SRB.
  • sl-PDCP-SN-Size is defined in 3GPP TS 38.331.
  • sl-PDCP-SN-Size is a PDCP sequence number size for unicast NR sidelink communication, 12 or 18 bits, as specified in TS 38.323.
  • RX_REORD This state variable indicates the COUNT value following the COUNT value associated with the PDCP Data PDU which triggered t-Reordering.
  • the initial value is the value stored in PDCP entity for the corresponding source SRB.
  • the initial value is the value stored in PDCP entity for the corresponding target SRB.
  • t-Reordering The duration of the timer t-Reordering is configured by upper layers as specified inTS 38.331, except for the case of NR sidelink communication.
  • the t-Reordering timer is determined by the UE implementation. This timer is used to detect loss of PDCP Data PDUs as specified in clause 5.2.2 of TS 38.323. If t-Reordering is running, t-Reordering shall not be started additionally, i.e. only one t-Reordering per receiving PDCP entity is running at a given time.
  • a receiver device receive the PDUs according to the discard control PDU as follows:
  • an PDCP control PDU is defined as PDCP discard indication PDU illustrated in FIG. 7.
  • the receive operation is illustrated in the following as an enhancement to TS 38.323 and the highlighted content is something new:
  • the receiver device executes the following operations:
  • a protocol layer entity e.g., PDCP layer in the receiver device receives and decodes a PDCP discard indication PDU from the transmitter device (C101) .
  • the protocol layer entity decodes the PDCP discard indication PDU to determine whether any SN window is indicated in the PDCP discard indication PDU.
  • the protocol layer entity When one or more SN windows is indicated in the PDCP discard indication PDU, the protocol layer entity obtains each of the one or more SN windows as a current SN window and performs the following operations for each SN window.
  • the protocol layer entity When receiving a PDCP data PDU (C102) , the protocol layer entity obtains the current SN window with [MinCD, MaxCD] (C103) and determines whether a parameter RCVD_COUNT associated with the PDCP data PDU is in the range [MinCD, MaxCD] (C104) , that is, whether RCVD_COUNT associated with the PDCP data PDU meets the condition MinCD ⁇ RCVD_COUNT ⁇ MaxCD.
  • the protocol layer entity discards the PDCP data PDU (C106) .
  • the protocol layer entity determines whether the SN window is the last SN window in the windows indicated by the PDCP discard indication PDU (C105) . If the SN window is not the last SN window, the protocol layer entity obtains a next one of the one or more SN windows indicated by the PDCP discard indication PDU as the current SN window (C107) and performs step C104. If the SN window is the last SN window, the execution terminates.
  • the receiver device executes the following operations:
  • a protocol layer entity e.g., PDCP layer in the receiver device receives and decodes a PDCP discard indication PDU from the transmitter device (C201) .
  • the protocol layer entity decodes the PDCP discard indication PDU to determine whether more than one SN window is indicated in the PDCP discard indication PDU and multiple SN windows indicated in the PDCP discard indication PDU are not sorted (C203) .
  • the protocol layer entity sorts all the SN windows according to the value of MinCD and MaxCD for each SN window in ascending order (C204) and obtains each of the one or more SN windows as a current SN window and performs the following operations for each SN window.
  • the protocol layer entity When receiving a PDCP data PDU (C205) , the protocol layer entity obtains the current SN window with [MinCD, MaxCD] (C206) and determines whether a parameter RX_DELIV associated with the PDCP data PDU is in the range [MinCD, MaxCD] (C207) , that is, whether RX_DELIV associated with the PDCP data PDU meets the condition MinCD ⁇ RX_DELIV ⁇ MaxCD.
  • the protocol layer entity updates the RX_DELIV to MaxDC+1 (C208) .
  • the protocol layer entity determines whether the SN window is the last SN window in the windows indicated by the PDCP discard indication PDU (C209) . If the SN window is not the last SN window, the protocol layer entity obtains a next one of the one or more SN windows indicated by the PDCP discard indication PDU as the current SN window (C210) and performs step C207. If the SN window is the last SN window, the execution terminates.
  • TX_NEXT TX_Next –UM send state variable This state variable holds the value of the SN to be assigned for the next newly generated UMD PDU with segment. It is initially set to 0, and is updated after the UM RLC entity submits a UMD PDU including the last segment of an RLC SDU to lower layers.
  • RX_Next_Reassembly is a UM receive state variable. This state variable holds the value of the earliest SN that is still considered for reassembly. It is initially set to 0. For groupcast and broadcast of NR sidelink communication, it is initially set to the SN of the first received UMD PDU containing an SN.
  • RX_Next_Highest is a Highest received state variable. This state variable holds the value of the SN following the SN of the RLC SDU with the highest SN among received RLC SDUs. It is initially set to 0.
  • t-Reassembly This t-Reassembly timer is used by the receiving side of an AM RLC entity and receiving UM RLC entity in order to detect loss of RLC PDUs at lower layer (see sub clauses 5.2.2.2 and 5.2.3.2 of TS 38.322) . If t-Reassembly is running, t-Reassembly shall not be started additionally, i.e. only one t-Reassembly per RLC entity is running at a given time.
  • an RLC control PDU is defined as RLC discard indication PDU illustrated in FIG. 8.
  • RLC discard indication PDU illustrated in FIG. 8.
  • the receiver device executes the following operations:
  • a protocol layer entity e.g., RLC layer in the receiver device receives and decodes a RLC discard indication PDU from the transmitter device (D101) .
  • the protocol layer entity decodes the RLC discard indication PDU to determine whether any SN window is indicated in the RLC discard indication PDU.
  • the protocol layer entity When one or more SN windows is indicated in the RLC discard indication PDU, the protocol layer entity obtains each of the one or more SN windows as a current SN window and performs the following operations for each SN window.
  • the protocol layer entity When receiving a RLC data PDU (D102) , the protocol layer entity obtains the current SN window with [MinSN, MaxSN] (D103) and determines whether an SN associated with the RLC data PDU is in the range [MinSN, MaxSN] (D104) , that is, whether SN associated with the RLC data PDU meets the condition MinSN ⁇ SN ⁇ MaxSN.
  • the protocol layer entity discards the RLC data PDU (D106) .
  • the protocol layer entity determines whether the SN window is the last SN window in the windows indicated by the RLC discard indication PDU (D105) . If the SN window is not the last SN window, the protocol layer entity obtains a next one of the one or more SN windows indicated by the RLC discard indication PDU as the current SN window (D107) and performs step D104. If the SN window is the last SN window, the execution terminates.
  • the receiver device executes the following operations:
  • a protocol layer entity e.g., RLC layer in the receiver device receives and decodes a RLC discard indication PDU from the transmitter device (D201) .
  • the protocol layer entity decodes the RLC discard indication PDU to determine whether more than one SN window is indicated in the RLC discard indication PDU and multiple SN windows indicated in the RLC discard indication PDU are not sorted (D203) .
  • the protocol layer entity sorts all the SN windows according to the value of MinSN and MaxSN for each SN window in ascending order (D204) and obtains each of the one or more SN windows as a current SN window and performs the following operations for each SN window.
  • the protocol layer entity When receiving a RLC data PDU (D205) , the protocol layer entity obtains the current SN window with [MinSN, MaxSN] (D206) and determines whether a parameter RX_NEXT associated with the RLC data PDU is in the range [MinSN, MaxSN] (D207) , that is, whether RX_NEXT associated with the RLC data PDU meets the condition MinSN ⁇ RX_NEXT ⁇ MaxSN.
  • the RX_NEXT may include RX_Next_Reassembly and/or RX_Next_Highest.
  • the protocol layer entity updates the RX_NEXT to MaxDC+1 (D208) .
  • the protocol layer entity determines whether the SN window is the last SN window in the windows indicated by the RLC discard indication PDU (D209) . If the SN window is not the last SN window, the protocol layer entity obtains a next one of the one or more SN windows indicated by the RLC discard indication PDU as the current SN window (D210) and performs step D206. If the SN window is the last SN window, the execution terminates.
  • FIG. 13 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. 13 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. Un dispositif émetteur transmet à un dispositif récepteur une PDU de commande qui indique des informations de numéro de séquence (SN) d'unités de données de protocole (PDU) rejetées par une entité de couche de protocole du dispositif émetteur. La PDU de commande comprend une ou plusieurs fenêtres SN dans lesquelles des SN pour le PDU rejetées sont continus.
PCT/CN2022/122836 2022-09-29 2022-09-29 Procédé et dispositif de communication sans fil WO2024065477A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/122836 WO2024065477A1 (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/122836 WO2024065477A1 (fr) 2022-09-29 2022-09-29 Procédé et dispositif de communication sans fil

Publications (1)

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

Family

ID=90475390

Family Applications (1)

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

Country Status (1)

Country Link
WO (1) WO2024065477A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020141894A1 (fr) * 2019-01-04 2020-07-09 Lg Electronics Inc. Procédé et appareil d'émission d'une unité de donnes basée sur un indicateur de temps d'exécution dans un système de communications sans fil
WO2022081073A1 (fr) * 2020-10-16 2022-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Émission et réception de paquets dans un réseau de communication sans fil
US20220150693A1 (en) * 2020-11-10 2022-05-12 Samsung Electronics Co., Ltd. Method and apparatus for accelerating data processing in next-generation wireless communication system
WO2022146039A1 (fr) * 2020-12-29 2022-07-07 삼성전자 주식회사 Procédé et appareil de traitement de paquet dans un système de communication sans fil

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020141894A1 (fr) * 2019-01-04 2020-07-09 Lg Electronics Inc. Procédé et appareil d'émission d'une unité de donnes basée sur un indicateur de temps d'exécution dans un système de communications sans fil
WO2022081073A1 (fr) * 2020-10-16 2022-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Émission et réception de paquets dans un réseau de communication sans fil
US20220150693A1 (en) * 2020-11-10 2022-05-12 Samsung Electronics Co., Ltd. Method and apparatus for accelerating data processing in next-generation wireless communication system
WO2022146039A1 (fr) * 2020-12-29 2022-07-07 삼성전자 주식회사 Procédé et appareil de traitement de paquet dans un système de communication sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NSN, NOKIA CORPORATION: "PDCP window handling for split bearers", 3GPP DRAFT; R2-142087 PDCP WINDOW HANDLING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Seoul, Korea; 20140519 - 20140523, 18 May 2014 (2014-05-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP050790058 *

Similar Documents

Publication Publication Date Title
US10986493B2 (en) Method and device for receiving data unit
CN109714134B (zh) 接收窗口滑动方法及装置
CN109474651B (zh) 处理数据的方法和设备
EP4009696A1 (fr) Procédé et dispositif de communication
US20160241680A1 (en) Apparatuses and methods for processing data communicated between different protocol layers
US11296831B2 (en) Method and apparatus for wireless communication
CN110035095A (zh) 语音通道建立方法、装置、终端及计算机可读存储介质
WO2024065477A1 (fr) Procédé et dispositif de communication sans fil
WO2024065471A1 (fr) Procédé et dispositif de communication sans fil
WO2024073877A1 (fr) Procédé et dispositif de communication sans fil
CN112399477B (zh) 一种通信方法及设备
WO2024065470A1 (fr) Procédé de communication sans fil et station de base
WO2021087729A1 (fr) Procédé et appareil pour indiquer un objet décompressé, et dispositif de communication
CN111357223B (zh) 一种通信的方法、装置和计算机可读存储介质
WO2023168573A1 (fr) Procédé et dispositif de communication sans fil pour trafic de réalité étendue
WO2023197143A1 (fr) Station de base, équipement utilisateur et procédé de traitement de réalité étendue
WO2023133900A1 (fr) Procédé de traitement de trafic à réalité étendue et dispositif émetteur
WO2023141816A1 (fr) Unité centrale, unité distribuée, équipement utilisateur et procédé pour la transmission de données basée sur une unité de données d'application
WO2024104101A1 (fr) Procédé et appareil de traitement de données, dispositif de communication et support de stockage lisible
WO2024067374A1 (fr) Procédé et appareil de communication
WO2023066106A1 (fr) Procédé et appareil de rejet de données, terminal et dispositif côté réseau
WO2024011380A1 (fr) Procédé de communication sans fil et station de base pour un trafic de réalité étendue
WO2023201607A1 (fr) Procédé et appareil de transmission de données, et dispositif de communication
US20230164085A1 (en) Modifying modem timers based on jitter timing associated with an application
WO2024082572A1 (fr) Procédés et appareils pour un temporisateur de rejet

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

Country of ref document: EP

Kind code of ref document: A1