WO2020155124A1 - Procédé de transmission de données dupliquées, dispositif terminal, et dispositif de réseau d'accès - Google Patents

Procédé de transmission de données dupliquées, dispositif terminal, et dispositif de réseau d'accès Download PDF

Info

Publication number
WO2020155124A1
WO2020155124A1 PCT/CN2019/074504 CN2019074504W WO2020155124A1 WO 2020155124 A1 WO2020155124 A1 WO 2020155124A1 CN 2019074504 W CN2019074504 W CN 2019074504W WO 2020155124 A1 WO2020155124 A1 WO 2020155124A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc
information
entity
data
transmission
Prior art date
Application number
PCT/CN2019/074504
Other languages
English (en)
Chinese (zh)
Inventor
石聪
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN201980062120.5A priority Critical patent/CN112740825B/zh
Priority to PCT/CN2019/074504 priority patent/WO2020155124A1/fr
Publication of WO2020155124A1 publication Critical patent/WO2020155124A1/fr

Links

Images

Classifications

    • 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 embodiments of the present application relate to communication technologies, and in particular, to a transmission method, terminal equipment, and access network equipment for copying data.
  • the radio access network protocol of the Long Term Evolution (LTE) system is divided into three levels: physical layer (L1), data link layer (L2) and radio resource control layer (L3).
  • the data link layer (L2) may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (Packet Data Convergence Protocol, PDCP) layer .
  • MAC medium access control
  • RLC radio link control
  • PDCP Packet Data Convergence Protocol
  • the mode type of the RLC entity in the RLC layer can be configured as Transparent Mode (TM), Unacknowledged Mode (UM) or Acknowledged Mode (AM).
  • TM Transparent Mode
  • UM Unacknowledged Mode
  • AM Acknowledged Mode
  • the fifth-generation communication technology puts forward higher requirements on delay and reliability to meet the requirements of enhanced mobile bandwidth (eMBB), massive machine communication (mMTC), and ultra-reliable , Low Latency (uRLLC) and other application scenarios, and the configuration of each RLC entity in the RLC layer cannot meet the 5G requirements for latency and reliability.
  • eMBB enhanced mobile bandwidth
  • mMTC massive machine communication
  • uRLLC Ultra-reliable , Low Latency
  • the embodiments of the present application provide a transmission method, terminal equipment, and access network equipment for copying data to meet the 5G requirements for delay and reliability.
  • an embodiment of the present application provides a method for transmitting copied data, including:
  • the terminal device receives first information, where the first information is used to indicate: at least two radio link control RLC transmission modes of the same radio bearer or the same PDCP entity of the same packet data convergence protocol.
  • an embodiment of the present application provides a method for transmitting copied data, including:
  • the access network device determines first information, where the first information is used to indicate: at least two radio link control RLC transmission modes of duplicate data of the same radio bearer or the same packet data convergence protocol PDCP entity;
  • the access network device sends the first information.
  • an embodiment of the present application provides a terminal device, including:
  • the receiving module is configured to receive first information, where the first information is used to indicate: at least two radio link control RLC transmission modes of the same radio bearer or the same PDCP entity of the same packet data convergence protocol.
  • an embodiment of the present application provides an access network device, including:
  • a processing module configured to determine first information, where the first information is used to indicate: at least two radio link control RLC transmission modes of duplicate data of the same radio bearer or the same packet data convergence protocol PDCP entity;
  • the sending module is used to send the first information.
  • an embodiment of the present application provides a terminal device, including: a processor and a memory;
  • the memory stores computer execution instructions
  • the processor executes the computer-executable instructions stored in the memory, so that the processor executes the copy data transmission method as described in the first aspect.
  • an embodiment of the present application provides an access network device, including: a processor and a memory;
  • the memory stores computer execution instructions
  • the processor executes the computer-executable instructions stored in the memory, so that the processor executes the copy data transmission method described in the second aspect.
  • an embodiment of the present application provides a computer-readable storage medium having computer-executable instructions stored in the computer-readable storage medium.
  • the computer-executable instructions are executed by a processor, the The method for transmitting the copied data as described above, or the method for implementing the method for transmitting the copied data as described in the second aspect.
  • the first information is sent to the terminal device through the access network device, and the first information is used to indicate the copy data of the same radio bearer or the same PDCP entity
  • At least two RLC transmission modes so as to realize the flexible configuration of RLC transmission modes, to take into account the needs of transmission delay and transmission reliability, so as to realize a more flexible and effective copy data transmission method, which can meet various business scenarios Demand.
  • FIG. 1 is a schematic diagram of an application scenario of an embodiment of the application
  • FIG. 2 is a flowchart of a method for transmitting copied data provided by an embodiment of the application
  • FIG. 3A is a schematic diagram of a radio bearer corresponding to multiple RLC entities according to an embodiment of this application;
  • 3B is a schematic diagram of a radio bearer corresponding to multiple RLC entities according to an embodiment of the application
  • FIG. 5 is a flowchart of a method for transmitting copied data according to an embodiment of the application
  • FIG. 6 is a flowchart of a method for transmitting copied data according to an embodiment of the application.
  • FIG. 7 is a flowchart of a method for transmitting copied data according to an embodiment of the application.
  • FIG. 8A is a schematic diagram of the configuration of a radio bearer corresponding to multiple RLC entities according to an embodiment of this application;
  • FIG. 8B is a flowchart of the process of copying data in the scenario shown in FIG. 8A according to an embodiment of the application;
  • FIG. 9A is a schematic diagram of an application scenario of the process of copying data provided by an embodiment of this application.
  • FIG. 9B is a flowchart of the process of copying data in the scenario shown in FIG. 9A according to an embodiment of the application;
  • FIG. 10 is a flowchart of the process of copying data in the scenario shown in FIG. 9A according to an embodiment of the application;
  • FIG. 11 is a schematic structural diagram of a terminal device provided by an embodiment of this application.
  • FIG. 12 is a schematic structural diagram of a terminal device provided by an embodiment of this application.
  • FIG. 13 is a schematic structural diagram of an access network device provided by an embodiment of this application.
  • FIG. 14 is a schematic structural diagram of an access network device provided by an embodiment of this application.
  • Fig. 1 is a schematic diagram of an application scenario of an embodiment of the application.
  • the application scenario includes: a terminal device 11 and an access network device 12.
  • the terminal device 11 establishes a communication connection with the access network device 12.
  • the terminal device 11 and the access network device 12 can both be used as the transmitting end or the receiving end.
  • the terminal device 11 acts as the transmitting end and the access network device 12 acts as the receiving end.
  • the terminal device 12 is the receiving end
  • the access network device 12 is the sending end.
  • the transmission method of copying data in the embodiment of this application can be used to meet the service's requirements for delay and reliability.
  • the transmission method of copying data in the embodiment of this application can be used to meet the service's requirements for delay and reliability.
  • Terminal device which can also be called user equipment (User Equipment, UE), mobile terminal (Mobile Terminal, MT), mobile user equipment, etc., can pass through a radio access network (for example, Radio Access Network, RAN) Communicate with one or more core networks.
  • the user equipment may be a mobile terminal, such as a mobile phone (or called a "cellular" phone) and a computer with mobile capabilities. For example, it may be a portable, pocket-sized, handheld, built-in computer or vehicle-mounted mobile device. It can also be a communication device in Machine Type Communication (MTC).
  • MTC Machine Type Communication
  • An access network device may be a device deployed in a wireless access network to provide wireless communication functions for terminal devices.
  • the access network equipment may include various forms of macro base stations, micro base stations (also called small stations), relay stations, access points, etc., and may also include various forms of control nodes, such as network controllers.
  • the control node may be connected to multiple base stations and configure resources for multiple terminal devices covered by the multiple base stations.
  • the names of devices with base station functions may be different, such as eNB or e-NodeB in LTE, or base stations or transmitting and receiving endpoints in 5G or NR, such as gNB, this embodiment of the application does not limit this.
  • the processing method for data copy transmission in the embodiments of this application can be applied to various data processing communication systems, for example: code division multiple access (code division multiple access, CDMA), time division multiple access (time division multiple access, TDMA), Frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single carrier frequency division multiple access (single carrier FDMA, SC-FDMA) and other systems.
  • code division multiple access code division multiple access
  • TDMA time division multiple access
  • FDMA Frequency division multiple access
  • OFDMA orthogonal frequency-division multiple access
  • single carrier frequency division multiple access single carrier frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • the term “system” can be used interchangeably with "network”.
  • the CDMA system can implement wireless technologies such as universal terrestrial radio access (UTRA) and CDMA2000.
  • UTRA can include wideband CDMA (WCDMA) technology and other CDMA variants.
  • CDMA2000 can cover the interim standard (IS) 2000 (
  • the TDMA system can implement wireless technologies such as the global system for mobile communication (GSM).
  • GSM global system for mobile communication
  • OFDMA system can realize such as evolved universal wireless terrestrial access (evolved UTRA, E-UTRA), ultra mobile broadband (ultra mobile broadband, UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.10, Flash OFDMA And other wireless technologies.
  • UTRA and E-UTRA are UMTS and UMTS evolved versions.
  • 3GPP is a new version of UMTS using E-UTRA in long term evolution (LTE) and various versions based on LTE evolution.
  • 5G fifth generation
  • 5G New Radio
  • the communication system can also be applied to future-oriented communication technologies , All apply to the technical solutions provided in the embodiments of this application.
  • the system architecture and business scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions in the embodiments of this application, and do not constitute a comparison of the technical solutions provided in the embodiments of this application.
  • those of ordinary skill in the art know that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.
  • the "plurality” referred to in the embodiments of the present application refers to two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone.
  • the character “/” generally indicates that the associated objects are in an "or” relationship.
  • the "identification of the RLC entity" involved in the embodiments of the present application can be replaced with the identification of the logical channel.
  • the "radio bearer" involved in the embodiments of the present application may correspond to at least one PDCP entity, one PDCP entity may correspond to one or more RLC entities, and one RLC entity may correspond to one MAC entity.
  • the "replicated data" involved in the embodiment of the present application includes the original PDCP data PDU and a copy of the original PDCP data PDU.
  • the PDCP entity in the PDCP layer can correspond to one or two RLC entities, and different RLC entities can correspond to the same or different MAC entities.
  • each RLC entity in the RLC layer is usually configured in the same RLC mode. Configuring each RLC entity in the RLC layer to the same RLC mode cannot meet the 5G requirements for delay and reliability. Specifically, for example, if each RLC entity in the RLC layer is configured as AM, the transmission delay is relatively large, and if each RLC entity in the RLC layer is configured as UM, the transmission reliability is not high.
  • the copy data transmission method of the embodiment of the present application involves a configuration process.
  • the configuration process of the embodiment of the present application can configure at least two RLC transmission modes to the terminal device, and explain the transmission characteristics of different RLC transmission modes.
  • TM data The characteristics of transmission are simple processing and small delay.
  • the characteristic of UM data transmission is that compared with TM, it provides a certain degree of reliability guarantee and small delay.
  • AM data transmission is characterized by high reliability, but it has a longer delay than the previous two transmission modes.
  • the embodiment of the application configures multiple RLC transmission modes for replicated data of the same radio bearer or the same PDCP entity, which can realize the flexible configuration of the RLC transmission mode to meet the requirements of transmission delay and transmission reliability, thereby meeting the requirements of some business scenarios .
  • This business scenario may include enhanced mobile bandwidth (eMBB), massive machine communication (mMTC), ultra-reliable, low-latency (uRLLC), industrial Internet (Industrial Interest of Things, IIoT), etc.
  • FIG. 2 is a flowchart of a method for transmitting copied data provided by an embodiment of this application. As shown in FIG. 2, the method of this embodiment may include:
  • Step 101 The access network device determines the first information.
  • the first information is used to indicate: at least two RLC transmission modes of duplicate data of the same radio bearer or the same PDCP entity.
  • the RLC transmission modes involved may be, for example, TM, UM, AM, but are not limited to the above three RLC transmission modes, and the at least two RLC transmission modes may include at least two of TM, UM, and AM.
  • the access network device configures at least two RLC transmission modes to the same radio bearer of the terminal device or replicated data of the same PDCP entity through the first information, and the terminal device can select one or more of the at least two RLC transmission modes according to requirements Or all copy data transmission.
  • the first information is used to indicate that the replicated data of the same PDCP entity supports UM and AM transmission, and the terminal device uses UM, or AM, or UM and AM to transmit the replicated data of the same PDCP entity.
  • the access network device may determine the first one or more of information such as service transmission characteristics, channel transmission quality, cell load, data volume to be transmitted, and data characteristics/priority. information.
  • Step 102 The access network device sends the first information to the terminal device.
  • the terminal device receives the first information sent by the access network device.
  • the first information in the embodiment of the present application is information used to indicate at least two RLC transmission modes of the same radio bearer or copy data of the same PDCP entity, and its name is not limited by this.
  • the access network device may send the first information to the terminal device through high-layer signaling.
  • the high-layer signaling may be radio resource control (Radio Resource Control, RRC) signaling, and the RRC signaling may be RRC reconfiguration signaling.
  • RRC Radio Resource Control
  • the PDCP entity in the embodiment of the present application corresponds to a radio bearer
  • the radio bearer may include a data radio bearer (DRB) and/or a signaling radio bearer (Signal Radio Bearer, SRB).
  • DRB data radio bearer
  • SRB Signaling Radio Bearer
  • one radio bearer may correspond to at least one PDCP entity.
  • the replicated data of the DRB or SRB can support at least two RLC transmission modes for transmission, or the replicated data of the PDCP entity can support at least two RLC transmission modes for transmission.
  • the replicated data of the PDCP entity is also It can be understood as the replicated data of the radio bearer, that is, the replicated data of the DRB or SRB.
  • the replicated data of the DRB or SRB may include two replicated data, or two or more replicated data of any number.
  • the copied data may be obtained after copying the data to be transmitted (for example, the original PDCP data PDU), and the data to be transmitted may be the packet data convergence protocol (Packet Data Convergence Protocol, PDCP) data unit to be transmitted (Protocol Data Unit, PDU).
  • PDCP Packet Data Convergence Protocol
  • PDU Protocol Data Unit
  • the first information is determined by the access network device, and the access network device sends the first information to the terminal device.
  • the first information is used to indicate at least two RLC transmission modes of the same radio bearer or copy data of the same PDCP entity , So as to realize the flexible configuration of the RLC transmission mode to take into account the needs of transmission delay and transmission reliability, so as to realize a more flexible and effective method of copying data transmission, which can meet the needs of some business scenarios (for example, IIoT) .
  • the first information is specifically used to indicate that each radio bearer or each PDCP entity corresponds to multiple RLC entities, and the multiple RLC entities correspond to at least two RLC transmission modes.
  • the first information may be used to indicate that the PDCP entity of the DRB 1 corresponds to multiple RLC entities, and the multiple RLC entities correspond to two RLC transmission modes.
  • the terminal device may configure the transmission modes of multiple RLC entities corresponding to the PDCP entity of the DRB 1 to UM and AM, or UM and TM, or TM and AM according to the first indication information.
  • the specific configuration of the transmission mode of each RLC entity may be implemented in the first mode or the second mode.
  • the first information can be applied to the scenario of multiple cell groups (CG).
  • radio bearer DRB1 corresponds to one PDCP entity
  • the PDCP entity corresponds to four RLC entities, of which two RLC entities
  • MCG master cell group
  • SCG secondary cell group
  • the first information can be used to indicate that the four RLC entities correspond to at least two RLC transmission modes .
  • the first information can also be applied to a scenario where a cell group corresponds to more than two RLC entities.
  • radio bearer DRB1 corresponds to one PDCP entity
  • the PDCP entity corresponds to two RLC entities
  • the two RLC entities correspond to MCG
  • the first information may be used to indicate that the above two RLC entities correspond to at least two RLC transmission modes.
  • the first information can also be applied to a combination of the first two scenarios.
  • the terminal device configures one or more RLC entities of the same cell group to the same transmission mode according to the first information, for example, when accessing the network
  • the device configures the transmission mode of the RLC entity of the PDCP entity to be UM and AM through the first information, then the terminal device can configure the transmission mode of one or more RLC entities of the master cell group (master cell group, MCG) to be AM, and auxiliary
  • the transmission mode of one or more RLC entities of a cell group (sencondary cell group, SCG) is UM.
  • the terminal device determines the transmission mode of each RLC entity according to the first information. It should be noted that in this manner, the transmission mode of the RLC entity may be related to CG or not. For example, the terminal device may configure one RLC entity as UM and other RLC entities as AM according to the first information.
  • the terminal device may select one or more of the at least two RLC transmission modes indicated by the first information to configure each The transmission mode of the RLC entity.
  • the terminal device may also determine the specific configuration of the transmission mode of each RLC entity in combination with one or more of information such as channel transmission quality, data volume to be transmitted, and data characteristics/priority.
  • the first information is specifically used to indicate that one or more RLC entities correspond to one RLC transmission mode, that is, the first information may indicate that the PDCP entities correspond to multiple RLC entity, the multiple RLC entities correspond to at least two RLC transmission modes, and may indicate the RLC transmission mode corresponding to one or more RLC entities.
  • the first information may indicate that the transmission mode of one or more RLC entities of the MCG is AM, and the transmission mode of one or more RLC entities of the SCG is UM.
  • the transmission mode of the RLC entity may be related to CG or not.
  • the first information may indicate that one RLC entity is UM, and other RLC entities are AM.
  • the first information may indicate that one or more RLC entities are AM, and other RLC entities are UM.
  • the terminal device can configure the corresponding RLC entity according to the first information.
  • one or more RLC entities in the same cell group adopt an RLC transmission mode, that is, one or more RLC entities in the same cell group adopt the same RLC transmission mode.
  • the RLC transmission modes of the RLC entities mapped to one CG are the same, and the RLC transmission modes of the RLC entities mapped to different CGs are different.
  • RLC entities or logical channels with the same transmission mode of the RLC entities can be activated at the same time, which has the advantage of having less impact on the existing protocol; or, the transmission modes of the RLC entities are different
  • the RLC entity or logical channel can also be activated at the same time, which has the advantage of increasing the flexibility of replication data transmission.
  • Figure 3A is a schematic diagram of a radio bearer corresponding to multiple RLC entities provided by an embodiment of this application.
  • This embodiment takes DRB1 and DRB2 as examples for illustration.
  • the terminal device completes the following configuration:
  • the PDCP entity of the DRB 1 of the terminal device corresponds to four RLC entities, among which, from left to right, the first two RLC entities correspond to the MCG MAC entity, and the last two RLC entities
  • the entity corresponds to the SCG MAC entity, the transmission mode of the first two RLC entities is AM, and the transmission mode of the last two RLC entities is UM.
  • the PDCP entity of the DRB 2 of the terminal device corresponds to two RLC entities, where the two RLC entities correspond to the SCG MAC entity, and the transmission mode of the two RLC entities is UM.
  • one or more RLC entities in the same cell group adopt different RLC transmission modes.
  • the RLC transmission modes of related RLC entities may be the same or different.
  • the RLC transmission modes of the RLC entities mapped to a CG may be the same or different. The advantage is that it is more flexible to configure and use the transmission mode of the RLC entity.
  • RLC entities or logical channels with the same transmission mode of the RLC entity can be configured to be activated at the same time, which has the advantage of having less impact on the existing protocol; or, configure the transmission mode of the RLC entity
  • Different RLC entities or logical channels can also be activated at the same time, which has the advantage of increasing the flexibility of replication data transmission.
  • Figure 3B is a schematic diagram of a radio bearer corresponding to multiple RLC entities provided by an embodiment of this application.
  • This embodiment takes DRB1 and DRB2 as examples for illustration.
  • the terminal device completes the following configuration:
  • the PDCP entity of the DRB 1 of the terminal device corresponds to four RLC entities, among which, from left to right, the first two RLC entities correspond to the MCG MAC entity, and the last two RLC entities
  • the entity corresponds to the SCG MAC entity, the transmission mode of the first and fourth RLC entities is UM, and the transmission mode of the second and third RLC entities is AM.
  • the PDCP entity of the DRB 2 of the terminal device corresponds to two RLC entities, where the two RLC entities correspond to SCG MAC entities, the transmission mode of the first RLC entity is AM, and the transmission mode of the second RLC entity is UM.
  • the transmission mode of the RLC entity of a CG is AM
  • the transmission mode of the RLC entity of other CGs is a transmission mode other than AM.
  • the transmission mode of the RLC entity of a CG is AM
  • the transmission mode of the RLC entity of other CGs may be AM or other transmission modes.
  • the first information may include at least one of the following information: RLC mode information and RLC activation indication information, where the RLC mode information is used to indicate the transmission mode type of the RLC entity, and the RLC The activation indication information is used to instruct multiple RLC entities to activate data replication transmission.
  • the RLC activation indication information is used to indicate the data replication transmission status of the RLC entity, and the data replication transmission status includes at least one of the following: activation and deactivation.
  • the RLC mode information is used to indicate that the transmission modes of the four RLC entities corresponding to DRB 1 are AM and UM, and the terminal device determines that the RLC entity of AM is activated according to the RLC activation indication information, or the terminal device activates according to the RLC
  • the indication information determines that the RLC entities of AM and UM are activated, or the terminal device determines the activated RLC entity in the corresponding RLC entity according to the RLC activation indication information.
  • activation and deactivation are used to indicate whether to use the RLC entity for copy data transmission, and can also be replaced with: use or not to indicate the same function, and the name is not limited by this.
  • the RLC activation indication information may include at least one of the identity of the RLC entity, the identity of the logical channel, and the identity of the CG.
  • the identity of the RLC entity and the identity of the CG can also be replaced with other information to achieve the same function as the identity of the RLC entity and the identity of the CG of the RLC activation indication information.
  • the embodiments of this application vary. for example.
  • the method of the embodiment of the present application may further include: when the access network device determines that the transmission mode of the copied data needs to be changed, it may send the updated updated data to the terminal device through a dedicated message.
  • RLC activation indication information the updated RLC activation indication information is used to instruct one or more RLC entities to activate/deactivate data replication transmission.
  • the access network device configures the transmission of the copy data to the configuration shown in FIG. 3A through the first information, and instructs the first RLC entity and the second RLC entity to activate the data copy transmission, that is, the active transmission mode is
  • the AM RLC entity that is, the AM RLC entity transmits the copied data.
  • the access network device sends the updated RLC activation indication information to the terminal device to achieve The RLC entity of the UM is activated, and the RLC entity of the UM is switched to transmit the replicated data.
  • the transmission mode of the replicated data can be configured or updated according to the channel quality, so as to improve the utilization of wireless resources while ensuring transmission delay and transmission reliability.
  • the method for transmitting copied data in the embodiment of the present application also involves a data transmission process.
  • a data transmission process please refer to the specific description of the embodiment shown in FIG. 4.
  • FIG. 4 is a flowchart of a method for transmitting copied data provided by an embodiment of the application. As shown in FIG. 4, this embodiment implements the transmission of copied data on the basis of the configuration process of the embodiment shown in FIG. Examples of methods can include:
  • Step 201 The access network device determines the first information.
  • Step 202 The access network device sends the first information to the terminal device.
  • steps 201 to 202 can refer to steps 101 to 102 of the embodiment shown in FIG. 2, and details are not repeated here.
  • Step 203 The terminal device transmits the copied data according to the first information.
  • the terminal device uses one or more RLC transmission modes to transmit the copied data of the same radio bearer or the same PDCP entity according to the first information.
  • the transmission can be uplink data transmission or downlink data transmission.
  • the PDCP entity of the terminal device can Four copies of data (the original PDCP data PDU and three copies of the original PDCP data PDU) are respectively sent to the corresponding RLC entity, and each RLC entity transmits the copied data according to its own transmission mode configuration.
  • the embodiment of the present application configures multiple RLC transmission modes for the same radio bearer or replicated data of the same PDCP entity, so that flexible configuration of the RLC transmission mode can be realized to meet the requirements of transmission delay and transmission reliability.
  • the terminal device may use one or more RLC transmission modes to transmit the copied data based on the first information, thereby realizing a more flexible and effective way of transmitting the copied data, which can meet the requirements of some business scenarios (for example, IIoT).
  • the method for transmitting copied data in the embodiment of the present application also relates to the process of copying data.
  • the following embodiments are used to specifically explain the process of copying data involved in the method for transmitting copied data in the embodiment of the present application.
  • the sending end may be a terminal device or an access network device.
  • the sending end It is a terminal device, that is, the terminal device executes the method steps of the following embodiments.
  • the sending end is an access network device, that is, the access network device executes the method steps of the following embodiments.
  • the process of copying data in the following embodiments of the present application is applicable to any copying data transmission mode.
  • the multiple RLC transmission modes described in the foregoing embodiment are mixed for transmission, and the transmission may also be performed in one RLC transmission mode.
  • the following embodiments may be executed after the method steps shown in FIG. 2 or FIG. 4, or may be method steps executed after the RLC entity is configured using the configuration mode of other RLC entities.
  • Fig. 5 is a flowchart of a method for transmitting copied data provided by an embodiment of the application.
  • the execution subject of this embodiment is the sending end, and this embodiment can perform packet loss processing to reduce the redundancy of copied data.
  • the method of this embodiment may include:
  • Step 301 Determine whether the set condition is met, and if so, perform step 302.
  • the set condition is used to indicate that the transmission of the copied data of the PDCP entity is completed, or the transmission is successful, or can be discarded.
  • the four RLC entities of the PDCP entity of the DRB 1 are all activated/used to transmit replicated data. Assume that the PDCP entity of the DRB 1 at the transmitting end replicates the data to be transmitted into four replicated data, respectively Sent to the four RLC entities, and the four RLC entities transmit the received copy data and transmit it to the receiving end through the air interface.
  • step 301 can determine the PDCP entity of the DRB 1 Whether the transmission of the copied data is completed, or the transmission is successful, or can be discarded.
  • step 302 is executed. For example, when the transmission of the copied data transmitted by the third RLC entity as shown in FIG. 3A is completed, the transmission is successful, or the preset time period is exceeded, it can be determined that the set condition is satisfied.
  • Step 302 Discard the copied data of the PDCP entity.
  • the copied data of the PDCP entity can be discarded, so as to reduce waste of air interface resources.
  • the sender can transmit data transmitted by the first RLC entity, the second RLC entity, and the fourth RLC entity of DRB 1.
  • the replicated data is discarded, that is, the replicated data that is the same as the replicated data transmitted by the third RLC entity in the sender is discarded.
  • the third RLC entity transmits the copied data earlier than the first RLC entity and The second RLC entity, the reason may be that the RLC entity of the AM RLC entity copied the data due to the link or ARQ.
  • the RLC PDU is still in the buffer, that is, it has not been transmitted due to resource constraints, or the channel quality problem has failed to transmit or failed to transmit Success, and the RLC entity of UM has been transmitted.
  • the discarded copy data can be at least one of the following: copy data that has been formed into RLC PDUs, copied data that has not been issued by RLC PDUs, PDCP PDUs that have not yet formed RLC PDU, corresponding to the copied data RLC SDU.
  • any copy data transmitted by any PDCP entity if a set condition is met, the copy data of the PDCP entity is discarded, and the set condition is used to indicate that the copy data of the PDCP entity is transmitted or is transmitted. Success, or it can be discarded to reduce redundant transmission of replicated data and reduce waste of air interface resources.
  • the setting condition includes the timeout of the copy data transmission.
  • the setting condition is to determine the second information, and the second information is used to indicate that the copy data transmission is successful.
  • the second information may be based on any of the following granularities: one radio bearer, one or more radio bearers that transmit replicated data, multiple radio bearers, and one or more PDCP entities.
  • the second information may be determined by at least one of the following: HARQ feedback information, ARQ feedback information, PDCP status PDU.
  • the sending end determines whether the replication data is successfully transmitted according to at least one of HARQ feedback information, ARQ feedback information, and PDCP status PDU.
  • the sender determines whether the replication data is successfully transmitted according to at least one of HARQ-ACK, ARQ-ACK, PDCP status PDU, SN, and HARQ process ID (process ID). If the transmission is successful, the second information is determined.
  • the setting condition including the copy data transmission timeout is explained: the above step 301 is to determine whether the copy data transmission is timed out, and if so, the above step 302 is executed to reduce the redundant transmission of the copy data and reduce the waste of air interface resources.
  • a possible implementation of the copy data transmission timeout is that the copy data transmission time exceeds the first set time, and the first set time may be preset or instructed by the access network device.
  • the length of the first set time and the starting point of the first set time can be flexibly set according to requirements.
  • the PDCP entity of the radio bearer is used as the starting point to transmit the copied data downward to determine whether the PDCP entity is copy data The transmission is longer than one time.
  • the PDCP entity of the radio bearer at the transmitting end sends a first instruction to the RLC entity that transmits the same copy data.
  • the first instruction is used to instruct to discard the copied data.
  • the first set time can be implemented by a timer. That is, the first timer set by the PDCP entity of the radio bearer expires, and the copied data of the PDCP entity is discarded.
  • the first timer may be predefined, or may be instructed by the network (for example, an access network device).
  • the trigger condition of the first timer may be that the PDCP entity of the radio bearer transmits the replicated data downward.
  • the implementation of the first timer will be explained in a specific embodiment below.
  • FIG. 6 is a flowchart of a method for transmitting copied data provided by an embodiment of the application. As shown in FIG. 6, this embodiment is a specific implementation manner for packet loss processing in the embodiment shown in FIG. For example, each functional entity of a radio bearer at the transmitting end adopts the DRB 1 configuration as shown in FIG. 3A for illustration.
  • the method in this embodiment may include:
  • Step 401 When the PDCP entity of the radio bearer submits the copied data down, start the first timer.
  • the PDCP entity copies the data to be transmitted into four copies of copy data, and transmits them down to the four RLC entities
  • the first timer is started, that is, the trigger condition of the first timer is that the PDCP entity submits the copy data downward.
  • Step 402 When the first timer expires, the PDCP entity sends a first instruction to the corresponding RLC entity, where the first instruction is used to instruct to discard the copied data.
  • the corresponding RLC entity refers to the RLC entity that transmits the same copy data.
  • the PDCP entity sends the first instruction to the four RLC entities, and the first instruction is used to instruct to discard the copied data.
  • Step 403 The RLC entity discards the copied data according to the first instruction.
  • the four RLC entities discard the copied data transmitted by the PDCP according to the first instruction.
  • the copied data to be discarded may be determined according to the PDCP sequence number, and discarded, that is, the copied data will not be transmitted through the air interface. .
  • the first timer when the PDCP entity of the radio bearer submits the copy data downward, the first timer is started. When the first timer expires, the PDCP entity sends a first instruction to the corresponding RLC entity, and the RLC entity responds to the first instruction , Discard the copied data, thereby reducing the redundant transmission of the copied data and reducing the waste of air interface resources.
  • the "corresponding RLC entity” involved in the foregoing embodiment specifically refers to the RLC entity corresponding to the PDCP entity and used to transmit the same replicated data.
  • any first RLC entity exceeds the second set time
  • any first RLC entity is any RLC entity corresponding to the PDCP entity.
  • the second preset duration of any first RLC entity may be related or unrelated.
  • the second set time may be preset, or may be instructed by the access network device.
  • the duration of the second set time and the starting point of the first set time can be flexibly set according to requirements. For example, the RLC entity of the PDCP entity transmits the copy data downward as the starting point to determine whether the copy data transmission exceeds one duration.
  • the first RLC entity at the transmitting end sends a second indication to the PDCP entity of the radio bearer.
  • the second indication is used to instruct to discard the copied data, and the PDCP entity Send a second indication to other RLC entities in the radio bearer that transmit the same copy data.
  • the first RLC entity refers to the RLC entity used to trigger packet loss processing among multiple RLC entities that transmit the same duplicate data.
  • the first RLC entity is only used to distinguish the RLC entity that triggers packet loss processing among multiple RLC entities and perform packet loss processing.
  • the transmission mode of the first RLC entity includes but is not limited to at least one of the following: AM, UM, TM.
  • the first RLC entity may be a specific RLC entity, such as an RLC entity in a specific transmission mode, an RLC entity designated by the network, or a master RLC entity, or a predetermined RLC entity.
  • another achievable way of discarding the copied data may be that the first RLC entity sends to the PDCP entity a piece of information for indicating the transmission status of the copied data, and the PDCP entity uses the information for indicating the transmission status of the copied data according to the information. Send a second indication to other RLC entities corresponding to the same PDCP entity that transmit the same copy data. Further, the information used to indicate the transmission status of the copied data may also include PDCP SN.
  • the second set time can be implemented by a timer. That is, when the second timer expires, the copied data is discarded.
  • the second timer may be predefined, or may be instructed by the network (for example, an access network device).
  • the trigger condition of the second timer may be that the first RLC entity transmits the copied data downward or the first RLC entity receives the copied data from the PDCP entity.
  • the following uses a specific embodiment to explain the implementation of the second timer .
  • FIG. 7 is a flowchart of a method for transmitting copied data according to an embodiment of the application.
  • this embodiment is a specific implementation manner for packet loss processing in the embodiment shown in FIG.
  • each functional entity of a radio bearer at the transmitting end adopts the configuration of DRB 1 as shown in FIG. 3A, and the third RLC entity of DRB 1 is taken as an example for illustration.
  • the transmission mode of the third RLC entity is UM.
  • the method of this embodiment may include:
  • Step 501 When the first RLC entity delivers to the MAC entity or the first RLC entity receives copy data from the PDCP entity, start the second timer of the first RLC entity.
  • the PDCP entity copies the data to be transmitted into four copies of data (including the data to be transmitted), and sends It is transmitted to four RLC entities, each RLC entity is set with a second timer, and the trigger condition of the second timer is that the RLC entity receives the copied data or the RLC entity sends the copied data to the MAC entity.
  • Step 502 When the second timer of any first RLC entity expires, the PDCP entity sends a second instruction to other RLC entities, where the second instruction is used to instruct to discard the copied data.
  • the other RLC entity is an RLC entity other than the first RLC entity that transmits the same duplicate data.
  • the first RLC entity may notify the PDCP entity, so that the PDCP entity sends the second indication to other RLC entities.
  • the second timer of the third RLC entity is timed out as an example.
  • the third RLC entity triggers the PDCP entity to transmit the same copy data to other RLC entities in the same radio bearer (such as the first RLC entity in FIG. 3A).
  • the second RLC entity and the fourth RLC entity send a second instruction, which is used to instruct to discard the copied data.
  • the third RLC entity sends a second indication to the first RLC entity, the second RLC entity, and the fourth RLC entity through the PDCP entity to instruct to discard the copied data.
  • the third RLC entity sends a message to the PDCP entity to indicate the successful transmission of the copied data
  • the PDCP entity sends a message to the first RLC entity and the first RLC entity according to the information used to indicate the successful transmission of the copied data.
  • the two RLC entities and the fourth RLC entity send a second instruction to instruct to discard the copied data.
  • Step 503 Other RLC entities that transmit the same copied data discard the copied data according to the second instruction.
  • the first RLC entity, the second RLC entity, and the fourth RLC entity discard the copied data transmitted by the PDCP according to the second instruction.
  • the copied data that needs to be discarded may be determined according to the PDCP sequence number, and the data to be discarded Discard, that is, the copied data will not be transmitted through the air interface.
  • the second timer when the first RLC entity delivers to the MAC entity or the first RLC entity receives copy data from the PDCP entity, the second timer is started. When the second timer expires, the first RLC entity transmits the same copy to other entities.
  • the RLC entity of the data sends a second instruction, the second instruction is used to instruct to discard the duplicate data, and other RLC entities transmitting the same duplicate data discard the duplicate data according to the second instruction, thereby reducing redundant transmission of the duplicate data and reducing the air interface Waste of resources.
  • the setting condition includes determining the second information, and the second information is used to indicate that the copy data transmission is successful, and an explanation is made: the above step 301 is to determine whether the second information is determined for the copied data transmitted by any PDCP entity, if yes , The foregoing step 302 is executed, thereby reducing redundant transmission of duplicate data and reducing waste of air interface resources.
  • the second information may be determined by the first RLC entity, or the first MAC entity, or the PDCP entity.
  • the PDCP entity indicates the corresponding The RLC entity discards the copied data.
  • an achievable manner of the second information is: the second information is determined by the first RLC entity.
  • the second RLC entity determines the second information according to the ARQ feedback information
  • the ARQ feedback information may include confirmation information for the copied data.
  • a specific implementation manner of step 302 is: (For example, the PDCP entity) sends a third indication, the third indication is used to indicate the copy data discard or the transmission success confirmation, the third indication includes at least one of the following information: the second information, the copy data of the second RLC entity The PDCP sequence number of the copied data, the PDCP entity instructs the corresponding RLC entity to discard the copied data. The RLC entity discards the copied data according to the instruction of the PDCP entity.
  • the second information is determined by the first MAC entity, and the first MAC entity is a MAC entity corresponding to the PDCP entity.
  • the first MAC entity determines the second information according to the hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) feedback information, and the MAC PDU corresponding to the HARQ feedback information contains the replicated data of at least one third RLC entity carried by the radio.
  • the HARQ feedback information may include an acknowledgment (ACK) message for the copied data.
  • a specific implementation manner of step 302 is: the first MAC entity sends the second information or sends to a higher layer (for example, the third RLC entity) Information used to indicate the discard of the copied data or the confirmation of the transmission success; the third RLC entity sends a fourth instruction to the higher layer (for example, the PDCP entity), the fourth instruction is used to indicate the discard of the copied data or the confirmation of the transmission success, and the fourth instruction includes At least one of the following information: the second information, the RLC sequence number of the replicated data of the third RLC entity, the PDCP sequence number of the replicated data, and the PDCP entity instructs the corresponding RLC entity to send and discard the replicated data.
  • the RLC sequence number and the PDCP sequence number may be determined by at least one of the following: MAC entity determination, RLC entity determination, PDCP entity determination, or may be carried in feedback information.
  • Another achievable manner of the second information is that the second information is determined by the PDCP entity.
  • the PDCP entity determines the second information according to the received PDCP status PDU.
  • the PDCP status PDU may contain confirmation information for the copied data.
  • a specific implementation manner of step 302 is: the PDCP entity sends the corresponding RLC The entity sends a fifth instruction, which is used to instruct to discard the copied data.
  • FIG 8A is a schematic diagram of the configuration of a radio bearer corresponding to multiple RLC entities provided by an embodiment of this application.
  • the terminal device completes the following configuration: DRB1 of the terminal device
  • the PDCP entity corresponds to two RLC entities. From left to right, the first RLC entity corresponds to the MCG MAC entity, the second RLC entity corresponds to the SCG MAC entity, the transmission mode of the first RLC entity is UM, and the second RLC entity The transmission mode is AM.
  • Another DRB The PDCP entity of DRB 2 corresponds to two RLC entities, and the two RLC entities correspond to SCG MAC entities. From left to right, the transmission mode of the first RLC entity is AM, and the transmission of the second RLC entity The mode is UM. Among them, it is assumed that the replication data transmission of the two RLC entities of DRB 1 is activated.
  • FIG. 8B is a flowchart of the process of copying data in the scenario shown in FIG. 8A provided by an embodiment of the application. As shown in FIG. 8B, the method of this embodiment may include:
  • Step 601 When the first MAC entity determines the second information according to the HARQ feedback information, the first MAC entity sends the second information to the third RLC entity, the third RLC entity sends a fourth indication to the PDCP entity, and the PDCP entity indicates that the transmission is the same The RLC entity that replicates the data discards the replicated data.
  • the second information may be determined according to the HARQ feedback information.
  • the MAC entity of the sender (MCG MAC entity as shown in Figure 8A) packages the copied data of the RLC entity to generate MAC PDU, transmits the MAC PDU through the physical layer, and stores the copied data information.
  • the data information may include at least one of the existence identifier of the copied data and the corresponding RLC SN, PDCP SN, RLC entity or logical channel identifier.
  • the copied data information may be stored in the MAC PDU, or may be stored in the HARQ process/entity corresponding to the MAC PDU.
  • the receiving end receives the replicated data (assuming that the successfully received replicated data is the replicated data transmitted by the first RLC entity as shown in FIG. 8A), and carries feedback information of the replicated data in HARQ.
  • the first MAC entity at the sending end receives the HARQ feedback information from the receiving end, and the first MAC entity determines according to the copy data information that the HARQ feedback information displays or implicitly contains the feedback information of the copied data
  • the first MAC entity determines the second information according to the HARQ-ACK, and sends the second information to the first RLC entity, that is, the first RLC entity is the aforementioned third RLC entity .
  • the first RLC entity instructs other RLC entities that transmit the same duplicate data to lose packets.
  • the first RLC entity sends the fourth indication to the PDCP entity, and the PDCP entity instructs the RLC entity that transmits the same duplicate data to discard the duplicate data.
  • the first RLC entity sends the fourth instruction to the PDCP entity, and the PDCP entity sends the fourth instruction to the RLC entity that transmits the same copy data.
  • the foregoing fourth indication includes but is not limited to at least one of the following: RLC SN, PDCP SN, packet loss indication/successful transmission indication.
  • Step 602 The RLC entity that transmits the same replicated data discards the replicated data.
  • the second RLC entity discards the copied data.
  • the second RLC entity may determine the copied data to be discarded according to PDCP SN, and discard it.
  • the RLC entity may also store it and determine the corresponding PDCP SN according to the RLC SN.
  • the second RLC entity of the AM is triggered to perform packet loss through the fourth instruction, thereby avoiding redundant transmission of duplicate data and reducing waste of air interface resources.
  • the first MAC entity when the first MAC entity receives the HARQ feedback information, the first MAC entity determines the second information according to the HARQ feedback information, the first MAC entity sends the second information to the third RLC entity, and the third RLC entity sends the PDCP The entity sends a fourth instruction.
  • the PDCP entity instructs the RLC entity that transmits the same duplicate data to discard the duplicate data, and the RLC entity that transmits the same duplicate data discards the duplicate data, which can avoid redundant transmission of duplicate data and reduce air interface resource waste.
  • FIG. 9A is a schematic diagram of an application scenario of the process of copying data provided by an embodiment of this application.
  • the UE is the sender and the gNB is the receiver for example.
  • the gNB can be implemented through the above configuration process. For example, configure the transmission mode of the replicated data of the UE and configure it as a hybrid of UM and AM as shown in FIG. 9A, that is, configure the transmission modes of the two RLC entities corresponding to the PDCP of DRB 1 to UM and AM respectively. It is understandable that the transmission modes of the two RLC entities corresponding to the PDCP of the DRB 1 of the gNB are the same as those of the UE.
  • Fig. 9B is a flowchart of the process of copying data in the scenario shown in Fig. 9A provided by an embodiment of the application. As shown in Fig. 9B, the method of this embodiment may include:
  • Step 701 When the PDCP entity determines the second information according to the PDCP status PDU, the PDCP entity sends a fifth instruction to the RLC entity that transmits the same copy data, and the fifth instruction is used to instruct to discard the copy data.
  • the PDCP entity at the transmitting end receives the PDCP status PDU, and can determine the second information according to the PDCP status PDU.
  • the MAC entity of the sender packs the copied data from the RLC entity to generate a MAC PDU, and transmits the MAC PDU to the MAC entity of the receiver through the physical layer (such as The MAC entity of gNB shown in Figure 9A).
  • the MAC entity at the receiving end transmits the MAC PDU to the higher layer, and the PDCP entity at the receiving end receives the copied data and sends a PDCP status PDU to the transmitting end to indicate that the copied data is successfully received.
  • the PDCP status PDU is sent to the transmitting end to indicate the copied data successfully received in the period.
  • the MAC entity of the sender receives the PDCP status PDU and transmits it to the higher layer.
  • the PDCP entity of the sender When the PDCP entity of the sender receives the PDCP status PDU, it instructs other RLC entities that transmit the same duplicate data to lose packets.
  • the indication method may be specifically through the fifth indication, or through other information for packet loss indication, which will not be illustrated here.
  • Step 702 The RLC entity that transmits the same replicated data discards the replicated data.
  • the PDCP entity instructs the second RLC entity to discard the same duplicate data to avoid redundant transmission.
  • the second RLC entity may determine the copied data to be discarded according to PDCP SN, and discard it.
  • the second RLC entity of the AM is triggered to perform packet loss through the fourth instruction, thereby avoiding redundant transmission of duplicate data and reducing waste of air interface resources.
  • the PDCP entity at the transmitting end receives the PDCP status PDU
  • the PDCP entity determines the second information according to the PDCP status PDU
  • the PDCP entity sends a fifth instruction to the RLC entity that transmits the same copy data.
  • the fifth instruction is used for Instructs to discard the replicated data, and the RLC entity that transmits the same replicated data discards the replicated data, which can avoid redundant transmission of replicated data and reduce waste of air interface resources.
  • FIG. 10 is a flowchart of the process of copying data in the scenario shown in FIG. 9A provided by an embodiment of the application.
  • This embodiment adopts an application scenario with the same configuration as that of FIG. 9A.
  • the second information is determined according to the ARQ feedback information.
  • the process of copying data is explained.
  • the method of this embodiment may include:
  • Step 801 When the second RLC entity determines the second information according to the ARQ feedback information, the second RLC entity sends a third indication to the PDCP entity.
  • the third indication is used to indicate that the copied data is discarded or the transmission is successful, and the PDCP entity indicates the corresponding The RLC entity discards the copied data.
  • the second RLC entity at the transmitting end receives the ARQ feedback information, and the second RLC entity may determine the second information according to the ARQ feedback information.
  • the PDCP entity receives at least one of the following information from the bottom layer: SN, second information.
  • the PDCP entity considers that it has received the PDCP data packet/duplicated transmission data packet successfully transmission indication
  • the bottom layer such as the RLC entity, when receiving the ARQ-ACK, it submits at least one of the following information to the high layer: SN, second information.
  • the PDCP entity instructs the RLC entity of the UM of FIG. 9A to discard the copied data.
  • Step 802 The RLC entity that transmits the same replicated data discards the replicated data.
  • the RLC entity of the UM can determine the copied data that needs to be discarded according to the PDCP SN, and discard it.
  • the copy data transmission of the AM RLC entity as shown in FIG. 9A is successful.
  • the fifth instruction is used to trigger the UM RLC entity to perform Packet loss can avoid redundant transmission of duplicate data and reduce waste of air interface resources.
  • the ARQ feedback information may also be a confirmation of the copied data transmitted by the RLC entity of the UM or TM, and this embodiment of the present application is not limited by the above examples.
  • the second RLC entity at the transmitting end receives the ARQ feedback information
  • the second RLC entity determines the second information according to the ARQ feedback information
  • the second RLC entity sends a third indication to the PDCP entity, and the third indication is used for Indicate that the copied data is discarded or the transmission is successful
  • the PDCP entity instructs the corresponding RLC entity to discard the copied data
  • the RLC entity that transmits the same copied data discards the copied data, which can avoid redundant transmission of the copied data and reduce waste of air interface resources.
  • FIG. 11 is a schematic structural diagram of a terminal device provided by an embodiment of this application.
  • This embodiment provides a terminal device.
  • the terminal equipment may also be referred to as a UE, an access terminal, a user unit, a user station, a mobile station, a mobile station, a user terminal, a terminal, a wireless communication device, a user agent, or a user device.
  • the terminal device can be a smart phone, a cellular phone, a cordless phone, a tablet computer, a PDA device, a handheld device with wireless communication function or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device, etc.
  • the terminal equipment includes:
  • the receiving module 101 is configured to receive first information, where the first information is used to indicate: at least two radio link control RLC transmission modes of the same radio bearer or the same PDCP entity of the same packet data convergence protocol.
  • the processing module 102 is configured to transmit the copied data according to the first information, and control the sending module 103 to send the copied data to the access network device.
  • the first information is specifically used to indicate: each of the radio bearers or each of the PDCP entities corresponds to at least two RLC entities, and the at least two RLC entities correspond to at least two of the RLC transmission modes .
  • the first information is specifically used to indicate that one or more of the RLC entities adopt a corresponding RLC transmission mode.
  • the RLC transmission mode is related or not related to the cell group.
  • the first information is further used to indicate: one or more RLC entities in the same cell group correspond to one of the RLC transmission modes; or, one or more RLC entities in the same cell group correspond to different The RLC transmission mode.
  • the first information includes at least one of the following information: RLC mode information and RLC activation indication information, the RLC mode information is used to indicate the transmission mode type of the RLC entity, and the RLC activation indication information is used to indicate all The data replication transmission status of the RLC entity.
  • the data replication transmission state includes at least one of the following: activated and deactivated.
  • the processing module 102 is further configured to: if a set condition is met, discard the copied data, and the set condition is used to indicate that the copied data is transmitted, or the transmission is successful, or throw away.
  • the processing module 102 is configured to: instruct the corresponding RLC entity to discard the copied data through the PDCP entity.
  • the setting condition includes: the transmission of the copy data is timed out; or, determining second information, where the second information is used to indicate that the transmission of the copy data is successful.
  • the copy data transmission timeout includes: the copy data transmission time exceeds a first set time.
  • the processing module 102 is configured to: send a first instruction to a corresponding RLC entity through the PDCP entity, and the first instruction is used to instruct to discard the copied data.
  • the copy data transmission timeout includes: the copy data transmission time of any first RLC entity exceeds a second set time, and the any first RLC entity is any RLC entity corresponding to the PDCP entity .
  • the processing module 102 is configured to: send a second indication to another RLC entity through the PDCP entity, where the second indication is used for the other RLC entity to discard replicated data; the other RLC entity is the An RLC entity other than the first RLC entity that transmits the same duplicate data.
  • the second information is determined by a second RLC entity.
  • the processing module 102 is further configured to: send a third indication to a higher layer through the second RLC entity, the third indication is used to indicate that the copied data is discarded or the transmission is successful; the third indication includes the following At least one of the information: the second information, the RLC sequence number of the second RLC entity, and the PDCP sequence number.
  • the processing module 102 is further configured to determine the second information according to the automatic repeat request ARQ information through the second RLC entity.
  • the second information is determined by a first MAC entity, and the first MAC entity is a MAC entity corresponding to the PDCP entity.
  • the processing module 102 is further configured to: send the second information to the higher layer through the first MAC entity; send the fourth instruction to the higher layer by the third RLC entity, and the fourth instruction is used to indicate Copy data discarding or transmission success confirmation; the fourth indication includes at least one of the following information: the second information, the RLC sequence number of the third RLC entity, and the PDCP sequence number.
  • the processing module 102 is further configured to determine the second information according to the hybrid automatic retransmission HARQ feedback information through the first MAC entity.
  • the second information is determined by the PDCP entity.
  • the processing module 102 is configured to: send the fifth instruction to a corresponding RLC entity through the PDCP entity, and the fifth instruction is used to instruct to discard the copied data.
  • the processing module 102 is further configured to determine the second information according to the PDCP status PDU through the PDCP entity.
  • the copy data transmission time exceeding a first set time includes: the first timer of the PDCP entity expires.
  • the start time of the first timer is when the PDCP entity sends copy data to multiple corresponding RLC entities.
  • the copy data transmission time of any first RLC entity exceeds a second set time, including: the second timer of the first RLC entity expires.
  • the start time of the second timer is when the first RLC entity sends copy data to the medium access MAC entity, or the first RLC entity receives copy data from the PDCP entity.
  • the terminal device of the embodiment of the present application may be used to implement the technical solutions executed by the terminal device in the foregoing method embodiments of the present application.
  • the implementation principles and technical effects are similar, and details are not described herein again.
  • FIG. 12 is a schematic structural diagram of a terminal device provided by an embodiment of this application.
  • the terminal equipment may also be referred to as a UE, an access terminal, a user unit, a user station, a mobile station, a mobile station, a user terminal, a terminal, a wireless communication device, a user agent, or a user device.
  • the terminal device may be a smart phone, a cellular phone, a cordless phone, a tablet computer, a PDA device, a handheld device with wireless communication function or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device, etc.
  • the terminal device includes: a processor 111 and a memory 112.
  • the memory 112 stores computer execution instructions
  • the processor 111 executes the computer-executable instructions stored in the memory 112, so that the processor 112 executes the above-mentioned copy data transmission method.
  • the terminal device further includes a transceiver 113, which is used to implement communication with other network devices (such as access network devices) or terminal devices.
  • a transceiver 113 which is used to implement communication with other network devices (such as access network devices) or terminal devices.
  • the terminal device of the embodiment of the present application may be used to implement the technical solutions executed by the terminal device in the foregoing method embodiments of the present application.
  • the implementation principles and technical effects are similar, and details are not described herein again.
  • FIG. 13 is a schematic structural diagram of an access network device provided by an embodiment of this application. This embodiment provides an access network device. As shown in Figure 13, the access network equipment includes:
  • the processing module 121 is configured to determine first information, and the first information is used to indicate that the copied data of the same packet data convergence protocol PDCP entity is transmitted in at least two radio link control RLC transmission modes; the sending module 122 is configured to send The first information.
  • the access network device may further include a receiving module 123 for receiving copied data sent by the terminal device.
  • the processing module 121 is further configured to: transmit the copied data according to the first information, and control the sending module 122 to send the copied data to the terminal device.
  • the processing module 121 is further configured to: if a set condition is met, discard the copied data, and the set condition is used to indicate that the transfer of the copied data is completed, or the transfer is successful, or throw away.
  • the setting condition includes: the transmission of the copied data is timed out; or, determining second information, the second information being used to indicate that the transmission of the copied data is successful.
  • the sending module 122 is further configured to send configuration information, where the configuration information is used to indicate the first set time or the second set time.
  • the access network device of the embodiment of the present application can be used to implement the technical solutions executed by the access network device in the foregoing method embodiments of the present application.
  • the implementation principles and technical effects are similar, and details are not described herein again.
  • FIG. 14 is a schematic structural diagram of an access network device provided by an embodiment of this application. As shown in FIG. 14, the access network device includes: a processor 131 and a memory 132.
  • the memory 132 stores computer execution instructions
  • the processor 131 executes the computer-executable instructions stored in the memory 132, so that the processor 132 executes the aforementioned random access method.
  • the access network device further includes a transceiver 133, which is used to implement communication with other network devices (such as other access network devices) or terminal devices.
  • a transceiver 133 which is used to implement communication with other network devices (such as other access network devices) or terminal devices.
  • the access network device of the embodiment of the present application can be used to implement the technical solutions executed by the access network device in the foregoing method embodiments of the present application.
  • the implementation principles and technical effects are similar, and details are not described herein again.
  • An embodiment of the present application also provides a computer-readable storage medium, which stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement any one of the above-mentioned copy data transmission methods Steps performed by terminal equipment or access network equipment.
  • the embodiment of the present application also provides a computer program product, the program product includes a computer-executable instruction, when the computer-executable instruction is executed by a processor, it is used to implement any one of the above-mentioned copy data transmission methods in the terminal device or the access network device The steps performed.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the aforementioned computer program can be stored in a computer readable storage medium.
  • the computer program When the computer program is executed by the processor, it realizes the steps including the foregoing method embodiments; and the foregoing storage medium includes: ROM, RAM, magnetic disk, or optical disk and other media that can store program codes.

Landscapes

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

Abstract

Les modes de réalisation de la présente invention concernent un procédé de transmission de données dupliquées, un dispositif terminal, et un dispositif de réseau d'accès. Le procédé de transmission de données dupliquées selon l'invention comprend l'étape suivante : un dispositif terminal reçoit des premières informations, les premières informations étant utilisées pour indiquer au moins deux types de modes de transmission RLC (gestion de la liaison radio) de données dupliquées du même support radio ou de la même entité de protocole de convergence de données par paquets (PDCP). Les modes de réalisation de la présente invention sont aptes à réaliser la configuration flexible de modes de transmission RLC, répondant ainsi aux exigences de divers scénarios de service.
PCT/CN2019/074504 2019-02-01 2019-02-01 Procédé de transmission de données dupliquées, dispositif terminal, et dispositif de réseau d'accès WO2020155124A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201980062120.5A CN112740825B (zh) 2019-02-01 2019-02-01 复制数据的传输方法、终端设备及接入网设备
PCT/CN2019/074504 WO2020155124A1 (fr) 2019-02-01 2019-02-01 Procédé de transmission de données dupliquées, dispositif terminal, et dispositif de réseau d'accès

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/074504 WO2020155124A1 (fr) 2019-02-01 2019-02-01 Procédé de transmission de données dupliquées, dispositif terminal, et dispositif de réseau d'accès

Publications (1)

Publication Number Publication Date
WO2020155124A1 true WO2020155124A1 (fr) 2020-08-06

Family

ID=71840677

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/074504 WO2020155124A1 (fr) 2019-02-01 2019-02-01 Procédé de transmission de données dupliquées, dispositif terminal, et dispositif de réseau d'accès

Country Status (2)

Country Link
CN (1) CN112740825B (fr)
WO (1) WO2020155124A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024011463A1 (fr) * 2022-07-13 2024-01-18 Oppo广东移动通信有限公司 Procédé et appareil de traitement de données, et dispositif de communication
WO2024022343A1 (fr) * 2022-07-28 2024-02-01 上海朗帛通信技术有限公司 Procédé et appareil utilisés dans la communication sans fil

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109075919A (zh) * 2016-04-19 2018-12-21 诺基亚技术有限公司 拆分承载双/多连接重传分集
CN109151903A (zh) * 2017-06-16 2019-01-04 三星电子株式会社 用于在下一代移动通信系统中处理分组的方法和装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009086679A1 (fr) * 2007-12-29 2009-07-16 Zte Corporation Procédé de commande de réinitialisation d'entité de commande de liaison hertzienne
EP3585087B1 (fr) * 2017-03-13 2021-05-05 Huawei Technologies Co., Ltd. Procédé de traitement des données et station de base pour gérer le changement de type de support radio
CN108924871B (zh) * 2017-03-23 2022-09-20 夏普株式会社 无线配置方法、用户设备和基站
WO2018200565A1 (fr) * 2017-04-24 2018-11-01 Motorola Mobility Llc Duplication de pdu pdcp pour un support radioélectrique
SG11201911247VA (en) * 2017-07-21 2020-02-27 Guangdong Oppo Mobile Telecommunications Corp Ltd Method and device for processing data

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109075919A (zh) * 2016-04-19 2018-12-21 诺基亚技术有限公司 拆分承载双/多连接重传分集
CN109151903A (zh) * 2017-06-16 2019-01-04 三星电子株式会社 用于在下一代移动通信系统中处理分组的方法和装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CATT: "Packet Duplication Configuration and Control", 3GPP TSG-RAN WG2 MEETING #NR AH2 R2-1706361, 29 June 2017 (2017-06-29), XP051300874 *
HUAWEI ET AL.: "TP for TS 36.300 on the Usage of PDCP Duplication (De)activation MAC CE", 3GPP TSG-RAN WG2 #103 MEETING R2-1812078, 24 August 2018 (2018-08-24), XP051521701 *
LG ELECTRONICS INC.: "Discussion on the RLC Modes for PDCP Duplication", 3GPP TSG-RAN2 MEETING RAN2#103BIS R2-1818339, 12 October 2018 (2018-10-12), XP051557834 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024011463A1 (fr) * 2022-07-13 2024-01-18 Oppo广东移动通信有限公司 Procédé et appareil de traitement de données, et dispositif de communication
WO2024022343A1 (fr) * 2022-07-28 2024-02-01 上海朗帛通信技术有限公司 Procédé et appareil utilisés dans la communication sans fil

Also Published As

Publication number Publication date
CN112740825A (zh) 2021-04-30
CN112740825B (zh) 2023-06-06

Similar Documents

Publication Publication Date Title
CN110574426B (zh) 分组复制操作模式之间的切换
CN108617029B (zh) 无线承载配置方法、及相应的ue和基站
CN109982360B (zh) 通信方法和装置
TWI454096B (zh) Ｍａｃ層重置後ｂ節點緩衝資料之高效回復系統
EP3499949B1 (fr) Procédé, dispositif et système de traitement de signalisation de commande
US20220070748A1 (en) Data transmission method and related device
WO2018202037A1 (fr) Procédé de transmission de données, dispositif terminal et dispositif de réseau
EP3661316B1 (fr) Procédé de traitement d'échec de liaison radio et dispositif terminal
EP3634076B1 (fr) Procédé et dispositif de traitement de données
TW201906443A (zh) 用於傳輸數據的方法、終端設備和網絡設備
WO2021000783A1 (fr) Procédé et appareil pour indiquer des situations de transmission de données
WO2020155124A1 (fr) Procédé de transmission de données dupliquées, dispositif terminal, et dispositif de réseau d'accès
WO2015113259A1 (fr) Procede de traitement de donnees, dispositif de communication et systeme
WO2019153209A1 (fr) Procédé de traitement d'échec de liaison radio (rlf) et dispositif terminal
WO2022120744A1 (fr) Procédé de traitement de transmission de données et appareil associé
WO2021129701A1 (fr) Procédé de commande d'entité pdcp et entité pdcp
WO2019153208A1 (fr) Procédé de traitement d'un défaut de liaison radio (rlf) et dispositif terminal
WO2022120541A1 (fr) Procédé et appareil de transmission de données
WO2017117800A1 (fr) Procédé et appareil de réception et d'envoi de données, et système de communication
WO2024000110A1 (fr) Procédé et appareil de transfert cellulaire, dispositif terminal et dispositif de réseau
WO2021098638A1 (fr) Procédé de radiocommunication et dispositif de radiocommunication
WO2019193734A1 (fr) Dispositif de communication
WO2019052174A1 (fr) Procédé et dispositif permettant de changer un type de support et support de stockage informatique
CN118235353A (zh) 无线通信方法和通信设备

Legal Events

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

Ref document number: 19913201

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19913201

Country of ref document: EP

Kind code of ref document: A1