WO2020147056A1 - 用于复制数据传输的方法和设备 - Google Patents

用于复制数据传输的方法和设备 Download PDF

Info

Publication number
WO2020147056A1
WO2020147056A1 PCT/CN2019/072059 CN2019072059W WO2020147056A1 WO 2020147056 A1 WO2020147056 A1 WO 2020147056A1 CN 2019072059 W CN2019072059 W CN 2019072059W WO 2020147056 A1 WO2020147056 A1 WO 2020147056A1
Authority
WO
WIPO (PCT)
Prior art keywords
field
entity
pdcp entity
pdcp
indication information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2019/072059
Other languages
English (en)
French (fr)
Inventor
石聪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp 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 Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to PCT/CN2019/072059 priority Critical patent/WO2020147056A1/zh
Priority to CN202110968809.3A priority patent/CN113691359B/zh
Priority to EP19910091.8A priority patent/EP3911006B1/en
Priority to CN201980087029.9A priority patent/CN113261337A/zh
Publication of WO2020147056A1 publication Critical patent/WO2020147056A1/zh
Priority to US17/377,980 priority patent/US12004012B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/26—Special purpose or proprietary protocols or architectures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/12—Flow control between communication endpoints using signalling between network elements

Definitions

  • the embodiments of the present application relate to the field, and more specifically, to a method and device for copy data transmission.
  • multiple network nodes such as a master base station (Master eNB, MN) and a secondary base station (Secondary eNB, SN), can serve terminal equipment, and multiple base stations and terminal equipment can perform Transmission of copy data.
  • Master eNB, MN master base station
  • Secondary eNB, SN secondary base station
  • the Packet Data Convergence Protocol can copy a PDCP protocol data unit (Protocol Data Unit, PDU) into two copies and map them to different
  • PDU Packet Data Unit
  • the RLC entity is mapped to two different physical carriers through the MAC entity to achieve frequency diversity gain to improve the reliability of data transmission.
  • Radio Link Control (RLC) entities associated with the PDCP entity Data Radio Bearer, DRB
  • DRB Data Radio Bearer
  • the embodiments of the present application provide a method and device for copy data transmission, which can realize effective copy data transmission.
  • a method for copying data transmission including: a terminal device receives first indication information; and the terminal device processes a PDCP PDU according to the first indication information.
  • the first indication information is used to indicate the activation or deactivation of the replication data transmission function of at least one PDCP entity, and/or indicate the RLC used to transmit replicated data among multiple RLC entities respectively associated with the at least one PDCP entity entity.
  • a method for copying data transmission including: a network device sends first indication information, where the first indication information is used by a terminal device to process a PDCP PDU, wherein the first indication information It is used to indicate activation or deactivation of the replication data transmission function of at least one PDCP entity, and/or to indicate the RLC entity used to transmit replicated data among multiple RLC entities respectively associated with the at least one PDCP entity.
  • a terminal device which can execute the method in the first aspect or any optional implementation manner of the first aspect.
  • the terminal device may include a functional module for performing the method in the first aspect or any possible implementation manner of the first aspect.
  • a network device in a fourth aspect, can execute the foregoing second aspect or any optional implementation of the second aspect.
  • the network device may include a functional module for performing the method in the second aspect or any possible implementation manner of the second aspect.
  • a terminal device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect or any possible implementation manner of the first aspect.
  • a network device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or any possible implementation manner of the second aspect.
  • a chip for implementing the above-mentioned first aspect or the method in any possible implementation manner of the first aspect.
  • the chip includes a processor for calling and running a computer program from the memory, so that the device installed with the chip executes the method in the first aspect or any possible implementation manner of the first aspect.
  • a chip for implementing the method in the second aspect or any possible implementation manner of the second aspect.
  • the chip includes a processor for calling and running a computer program from the memory, so that the device installed with the chip executes the method in the second aspect or any possible implementation manner of the second aspect.
  • a computer-readable storage medium for storing a computer program, which causes the computer to execute the method in the first aspect or any possible implementation manner of the first aspect.
  • a computer-readable storage medium for storing a computer program that causes a computer to execute the method in the second aspect or any possible implementation manner of the second aspect.
  • a computer program product including computer program instructions, which cause the computer to execute the method in the first aspect or any possible implementation manner of the first aspect.
  • a computer program product including computer program instructions that cause a computer to execute the foregoing second aspect or any possible implementation method of the second aspect.
  • a computer program which when run on a computer, causes the computer to execute the method in the first aspect or any possible implementation manner of the first aspect.
  • a computer program which when run on a computer, causes the computer to execute the method in the second aspect or any possible implementation manner of the second aspect.
  • a communication system including terminal equipment and network equipment. among them:
  • the network device is used to send the first indication information to the terminal device.
  • the terminal device is configured to receive the first indication information sent by the network device.
  • the first indication information is used to indicate the activation or deactivation of the replication data transmission function of at least one PDCP entity, and/or indicate the RLC used to transmit replicated data among multiple RLC entities respectively associated with the at least one PDCP entity entity.
  • the first indication information is used to indicate the activation/deactivation of the replication data transmission function of at least one PDCP entity, and to indicate the RLC entity used to transmit replicated data among the multiple RLC entities respectively associated with the at least one PDCP entity , So that in a copy data transmission mechanism with more than two copies, effective copy data transmission can still be realized.
  • Figure 1 is a schematic diagram of a multi-connection scenario.
  • Figure 2 is a schematic architecture diagram of replicated data transmission in a DC scenario and a CA scenario.
  • Figures 3(a) and 3(b) are schematic diagrams of a replication data transmission mechanism for more than two copies of an embodiment of the present application.
  • Fig. 4 is a flow interaction diagram of a method for copying data transmission according to an embodiment of the present application.
  • Fig. 5 is a flow interaction diagram of a method for copying data transmission according to an embodiment of the present application.
  • Figures 6(a) and 6(b) are schematic diagrams of implementation of the first indication information in an embodiment of the present application.
  • FIG. 7 is a schematic diagram of an implementation manner of first indication information in an embodiment of the present application.
  • FIG. 8 is a schematic diagram of an implementation manner of first indication information in a CA scenario in an embodiment of the present application.
  • Figures 9(a) and 9(b) are schematic diagrams of the implementation of the first indication information in the DA scenario of an embodiment of the present application.
  • FIG. 10 is a schematic diagram of an implementation manner of first indication information in an embodiment of the present application.
  • FIG. 11(a) and FIG. 11(b) are schematic diagrams of implementation of the first indication information in an embodiment of the present application.
  • FIG. 12(a) and FIG. 12(b) are schematic diagrams of the implementation of the first indication information in an embodiment of the present application.
  • Figures 13(a) and 13(b) are schematic diagrams of implementations of the first indication information in an embodiment of the present application.
  • Fig. 14(a), Fig. 14(b) and Fig. 14(c) are schematic diagrams of implementation of the first indication information in an embodiment of the present application.
  • FIG. 15(a) and FIG. 15(b) are schematic diagrams of implementation of the first indication information in an embodiment of the present application.
  • FIG. 16 is a schematic diagram of an implementation manner of first indication information in an embodiment of the present application.
  • FIG. 17 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 18 is a schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 19 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 20 is a schematic structural diagram of a chip of an embodiment of the present application.
  • FIG. 21 is a schematic block diagram of a communication system according to an embodiment of the present application.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • LTE-A Advanced long term evolution
  • NR New Radio
  • NR NR system evolution system
  • LTE on unlicensed frequency bands LTE-based access to unlicensed spectrum, LTE-U
  • NR NR-based access to unlicensed spectrum, NR-U
  • UMTS Universal Mobile Telecommunication System
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • WLAN Wireless Local Area Networks
  • WiFi Wireless Fidelity
  • future 5G systems also called New Wireless (New Wireless) Radio, NR
  • the network device or network node mentioned in the embodiment of the present application may provide communication coverage for a specific geographic area, and may communicate with terminal devices located in the coverage area.
  • the network equipment may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station ( Evolutional Node B, eNB or eNodeB), or the wireless controller in Cloud Radio Access Network (CRAN), or the network device can be a relay station, access point, vehicle-mounted device, wearable device, future Network-side equipment in the 5G network or network equipment in the public land mobile network (Public Land Mobile Network, PLMN) that will evolve in the future.
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • eNB evolved base station
  • CRAN Cloud Radio Access Network
  • the network device can be a relay station, access point, vehicle-mounted device, wearable device, future Network-side equipment in
  • terminal device mentioned in the embodiment of the present application may be mobile or fixed.
  • terminal equipment may refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal, terminal, wireless communication equipment , User agent or user device.
  • Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital processing (Personal Digital Assistant (PDA), wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks or terminal devices in future evolved PLMNs, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • wireless communication Functional handheld devices computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks or terminal devices in future evolved PLMNs, etc
  • NR supports two modes of replication data transmission: DC Duplication in the DC scenario and CA Duplication in the CA scenario.
  • multiple cell groups can serve terminal devices, and the multiple CGs can include, for example, a primary CG (Master CG, MCG) or a secondary CG (Secondary CG, SCG), which can also be called Primary base station or secondary base station.
  • the network equipment around the terminal device 130 in FIG. 1 includes a primary base station 110 and at least one secondary base station 120.
  • the at least one secondary base station 120 is respectively connected to the main base station 110 to form multiple connections, and is connected to the terminal device 130 to provide services for it.
  • the primary base station 110 may be an LTE network, and the secondary base station 120 may be an NR network; or, the primary base station 110 may be an NR network, and the secondary base station 120 may be an LTE network; or, both the primary base station 110 and the secondary base station 120 may be For the NR network.
  • the primary base station may also be a GSM base station, a CDMA base station, etc.
  • the secondary base station may also be a GSM base station, a CDMA base station, etc., which are not limited here.
  • the terminal device 130 can simultaneously establish a connection through the primary base station 110 and the secondary base station 120.
  • the connection established between the terminal device 130 and the primary base station 110 is the primary connection
  • the connection established between the terminal device 130 and the secondary base station 120 is the secondary connection.
  • the control signaling of the terminal device 130 may be transmitted through the main connection
  • the data of the terminal device may be transmitted through the main connection and the auxiliary connection at the same time, or may be transmitted only through the auxiliary connection.
  • the transmission of replicated data can be performed between the primary base station and the secondary base station and the terminal equipment, and the method of the replicated data transmission adopts a split bearer protocol architecture.
  • FIG. 2 shows three PDCP entities: PDCP entity 1, PDCP entity 2, and PDCP entity 3.
  • Each PDCP entity uniquely corresponds to a data radio bearer (Data Radio Bearer, DRB) or signaling radio bearer (Signaling Radio Bearer, SRB).
  • DRB Data Radio Bearer
  • SRB Signaling radio bearer
  • the following describes the DRB as an example, PDCP entity 1, PDCP entity 2, and PDCP entity 3
  • the corresponding DRB identifiers are DRB ID1, DRB ID2, and DBRID3 in order.
  • PDCP entity 2 For copy data transmission under DC, reference may be made to PDCP entity 2 shown in FIG. 2 for example.
  • PDCP entity 2 is associated with two different RLC entities: RLC entity 3 and RLC entity 4.
  • the RLC entity 3 and the RLC entity 4 are respectively associated with two different media access control (Media Access Control, MAC) entities: the MAC entity of the MCG and the MAC entity of the SCG.
  • Media Access Control Media Access Control
  • the PDCP entity copies the PDCP PDU into the same two copies.
  • the two PDCPs pass through the RLC entities and MAC entities of different CGs, and then reach the corresponding MAC of the terminal equipment (downlink) or base station (uplink) through the air interface. Entity and RLC entity, and finally converge to PDCP entity.
  • the PDCP layer detects that the two PDCP PDUs are the same copy version. For example, it can be judged by whether the two PDCP PDUs have the same serial number (Serial Number, SN). When the SN of the two PDCP PDUs is the same, they are discarded One PDCP PDU, then another PDCP PDU is delivered to the higher layer. It should be noted that the two copied PDCP PDUs may not reach the PDCP layer at the same time.
  • the PDCP entity can copy a PDCP PDU into two copies, respectively map to different RLC entities, and map to two different physical carriers through the MAC entity, thereby achieving frequency diversity gain and improving the reliability of data transmission Sex.
  • the replication data transmission under CA is, for example, PDCP entity 1 and PDCP entity 3 in FIG. 2.
  • the copy data transmission under CA uses the CA's protocol architecture.
  • PDCP entity 1 and PDCP entity 3 are respectively associated with two different RLC entities, PDCP entity 1 is associated with RLC entity 1 and RLC entity 2, and PDCP entity 3 is associated with RLC entity 5 and RLC entity 6.
  • RLC entity 1 and RLC entity 2 are associated with the same MAC entity, that is, the MAC entity of MCG;
  • RLC entity 5 and RLC entity 6 are associated with the same MAC entity, that is, the MAC entity of SCG.
  • each PDCP entity copies the PDCP PDU into the same two copies, each PDCP entity passes through a different RLC entity and the same MAC entity, and then reaches the terminal device (downlink) or base station (uplink) via the air interface. The corresponding MAC entity and RLC entity are finally converged to the PDCP entity.
  • the PDCP layer detects that the two PDCP PDUs are the same copy version. For example, it can be judged by whether the two PDCP PDUs have the same SN. When the SN of the two PDCP PDUs are the same, one PDCP PDU is discarded, and the other A PDCP PDU is delivered to the upper layer. It should be noted that the two copied PDCP PDUs may not reach the PDCP layer at the same time.
  • the copied data will be restricted to be transmitted on different carriers.
  • the protocol currently configures a logical channel priority (Logical Channel Prioritization, LCP) mapping parameter for the logical channel corresponding to each RLC entity.
  • LCP Logical Channel Prioritization
  • each PDCP entity can Associated with more than two RLC entities, each PDCP entity can also generate more than two copies of data.
  • the PDCP entity is associated with four RLC entities.
  • Each RLC entity corresponds to a logical channel.
  • LCID Logical Channel Identity
  • the PDCP PDU can be transmitted through the logical channels corresponding to these 4 RLC entities.
  • RLC entity 2 and RLC entity 3 are used to transmit replicated data, it is the transmission of replicated PDCP PDU in the DC scenario.
  • RLC entity 1 and RLC entity 2 or RLC entity 3 and RLC entity 4 are used to transmit replicated data , It corresponds to the transmission of the duplicate PDCP PDU in the CA scenario.
  • RLC entity 1 and RLC entity 2 are RLC entities of MCG
  • RLC entity 3 and RLC entity 4 are RLC entities of SCG.
  • the PDCP PDUs transmitted by the RLC entity 1 and the RLC entity 2 are respectively mapped to the carriers in the carrier set 1 and the carrier set 2 through the MAC entity of the MCG.
  • the copied PDCP PDUs transmitted by the RLC entity 3 and the RLC entity 4 are mapped to the carriers in the carrier set 3 and the carrier set 4 through the MAC entity 2 of the SCG, respectively.
  • the copied PDCP PDU can be transmitted on up to 4 physical carriers, achieving higher resource usage and data transmission reliability.
  • RLC entities associated with PDCP may be associated with the same MAC entity, such as the MAC entity of MCG or the MAC entity of SCG.
  • a terminal device When transmitting replicated data, a terminal device needs to know which PDCP entities are activated or deactivated, and which RLC entities of the multiple RLC entities associated with each PDCP entity can currently be used to transmit replicated data. For example, as shown in Figure 3, the terminal device not only needs to know whether the PDCP entity is activated or deactivated, and when the PDCP entity is activated, the terminal device also needs to know which RLC entities of the four RLC entities associated with the PDCP entity are used for transmission Copy the data.
  • the embodiment of the present application proposes a method based on copy data transmission, which can also realize effective copy data transmission in a copy data transmission mechanism with more than two copies.
  • the replication data transmission mechanism with more than two copies described in the embodiment of this application refers to the number of RLC entities associated with a PDCP entity may be greater than two, but this does not mean that the PDCP PDU The number of copies is greater than 2.
  • the PDCP entity is associated with four RLC entities, but two PDCP PDUs are copied, and the two PDCP PDUs are respectively transmitted on two of the four RLC entities.
  • these two RLC entities are called The RLC entity used to transmit replicated data.
  • the RLC entity used to transmit the replicated data may be different each time. When the channel condition of the used RLC entity changes, other RLC entities among the four RLC entities may be used to transmit the replicated data.
  • Fig. 4 is a flow interaction diagram of a method for copying data transmission according to an embodiment of the present application.
  • the method 400 may be executed by a terminal device and a network device.
  • the terminal device may be, for example, the terminal device 130 shown in FIG. 1.
  • the network device may be, for example, the primary base station 110 or the secondary base station 120 shown in FIG. 1, or may also be a core network device.
  • the method 400 for copying data transmission includes some or all of the following steps.
  • the network device sends the first indication information to the terminal device.
  • the terminal device receives the first indication information sent by the network device.
  • the first indication information is used to indicate the activation or deactivation of the replication data transmission function of at least one PDCP entity, and/or indicate the RLC entity used to transmit replicated data among multiple RLC entities respectively associated with the at least one PDCP entity .
  • the at least one PDCP entity may include, for example, a PDCP entity that replicates data transmission based on CA, and/or a PDCP entity that replicates data transmission based on DC.
  • one PDCP entity in the embodiment of the present application can be associated with any number of RLC entities.
  • the terminal device may, for example, perform data copy processing on the PDCP PDU according to the first indication information, and send the processed PDCP PDU to the network device.
  • the first indication information is carried in a media access control control element (MAC Control Element, MAC CE).
  • MAC Control Element MAC Control Element
  • the first indication information is carried in the MAC CE, and the method 500 for copying data transmission includes 510 to 540. among them:
  • the network device sends the MAC CE to the terminal device.
  • the MAC entity of the terminal device receives and parses the MAC CE to obtain the first indication information.
  • the MAC entity of the terminal device sends the first indication information to the PDCP entity of the terminal device.
  • the PDCP entity of the terminal device receives the first indication information.
  • the network device When the network device needs to activate/deactivate the copy data transmission function of one or more PDCP entities, it will send a MAC CE to the terminal device, and the MAC CE carries the first indication information.
  • the MAC entity of the terminal device interprets the MAC CE after receiving it, and obtains the first indication information, that is, the information of the PDCP entity that is activated/deactivated and/or the RLC entity used to transmit replicated data.
  • the MAC entity will parse these The information is indicated to the PDCP entity, so that the PDCP entity processes the PDCP PDU based on the information.
  • the terminal device may determine the activated/deactivated PDCP entity according to the received first indication information, and further, may determine according to the first indication information which RLC entities associated with the activated PDCP entity are currently available
  • the transmitted copied data and PDCP PDU are copied into several copies.
  • each PDCP entity is only associated with two RLC entities
  • one byte or one octet can be used to indicate the activated/deactivated PDCP entity.
  • Each bit in the byte or octet corresponds to a PDCP entity, and each bit is used to indicate whether the corresponding PDCP entity activates or deactivates the copy data transmission function.
  • there is no need to indicate which RLC entity is used to transmit the replicated data because both RLC entities will be used to transmit the replicated data.
  • the PDCP entity when the PDCP entity is associated with more RLC entities and can copy more PDCP PDUs, it not only needs to indicate the activation/deactivation of the PDCP entity, but also indicate which RLC entities among the RLC entities associated with the activated PDCP entity Used to transfer copied data.
  • the first indication information is used to indicate the activation/deactivation of the replication data transmission function of at least one PDCP entity, and to indicate the RLC used to transmit replicated data among multiple RLC entities associated with the at least one PDCP entity.
  • the entity can still achieve effective replication data transmission in a replication data transmission mechanism with more than two copies.
  • the embodiments of the present application provide different implementations of the first indication information, which are described below with reference to FIGS. 6 to 16 respectively.
  • the PDCP entity is also referred to as a radio bearer, and the DRB ID can be used for identification; and the RLC entity is referred to as a logical channel, and the LCID can be used for identification.
  • the at least one PDCP entity includes N PDCP entities, and N is a positive integer.
  • the first indication information includes M fields, wherein each field includes N bits, the N PDCP entities respectively correspond to the N bits, and multiple RLC entities associated with the same PDCP entity respectively correspond to all The multiple bits at the same position in the M fields, where each bit is used to indicate whether the RLC entity corresponding to each bit is used to transmit replicated data, and M is the maximum number of RLC entities associated with a PDCP entity.
  • the M fields may be located in M bytes or M octets, for example.
  • the first indication information includes M bytes, each byte includes 8 bits, and the first N bits from the right among the 8 bits of each byte respectively correspond to N PDCP entities, and 1 ⁇ N ⁇ 8.
  • the number of N is less than or equal to the total number of PDCP entities configured with the replication data transmission function.
  • the first indication information received from the MAC entity of the MCG may include the activation/deactivation information of the PDCP entity 1 and the PDCP entity 2 and the copy data transmission information of the RLC entity.
  • the first indication information received from the MAC entity of the SCG may include PDCP entity 2 and PDCP entity 3 activation/deactivation information and RLC entity copy data transmission information.
  • the first indication information received from the MAC entity of the MCG or the MAC entity of the SCG does not necessarily indicate all the PDCP entities 1, the PDCP entity 2 and the PDCP entity 3. It only indicates the information of the PDCP entity associated with itself, namely can.
  • the first to fourth columns from the right correspond to DRB ID0, DRB ID3, DRB ID5, and DRB ID7, respectively.
  • the bits in rows 1-4 in the first column correspond to the 4 RLC entities associated with DRB ID0; the bits in rows 1-4 in the second column correspond to the 4 RLC entities associated with DRB ID3; the first in the third column -The 4 rows of bits respectively correspond to the 4 RLC entities associated with DRB ID5; the first row and the second row of bits in the 4th column respectively correspond to the 2 RLC entities associated with DRB ID7.
  • the number of RLC entities associated with each PDCP entity may be the same or different.
  • the number of RLC entities associated with the PDCP entities corresponding to DRB ID0, DRB ID 3, and DRBID 5 are all 4, and the PDCP entity corresponding to DRB ID7
  • the number of associated RLC entities is 2.
  • Each small square represents a bit, and the value of each bit is used to indicate whether the RLC entity corresponding to the bit is currently used to transmit replicated data. Below, it is assumed that the bit value is 0 to indicate that it is not used to transmit replicated data. A value of 1 indicates that it is used to transfer copied data.
  • the information about whether the copy data transmission function of the PDCP entity is activated For example, it can be indicated by a byte shown in Figure 6(a), where the first 4 bits from the right of the byte correspond to DRB respectively. ID0, DRB ID3, DRB ID5, and DRB ID7, the value of each bit is used to indicate whether the copy data transmission function of the PDCP entity corresponding to the bit is activated. As shown in Figure 6(a), the first 4 bits are all 1, indicating that the copy data transmission functions of the PDCP entities corresponding to DRB ID0, DRB ID3, DRB ID5, and DRB ID7 are all activated.
  • Figure 6(b) you can use Figure 6(b) to obtain the activated/deactivated DRB.
  • the value of the bit column corresponding to the DRB is all 0 or there is a bit value 1, it means that the copy data transmission function of the DRB is deactivated; when at least two bits in the value of the bit column corresponding to the DRB have a value of 1, it means that the copy data transmission function of the DRB is activated, and both The RLC corresponding to each bit is used to transmit copied data.
  • each PDCP entity After determining the activation/deactivation of the replication data transmission function of each PDCP entity, determine which RLC entities of the RLC entities associated with the activated PDCP entity are used to transmit the replicated data. As shown in Figure 6(b), the first three RLC entities associated with the PDCP entity associated with DRB ID0 are used to transmit replicated data, and the first two RLC entities associated with the PDCP entity associated with DRB ID3 are used to transmit replicated data. DRB The four RLC entities associated with the PDCP entity associated with ID5 are all used to transmit replicated data, and the two RLC entities associated with the PDCP entity associated with DRB and ID7 are all used to transmit replicated data.
  • DRB ID0, DRB ID3, DRB ID5, and DRB ID7 shown in FIG. 6(b) are in the order of the size of the DRB ID, for example, in ascending order, corresponding to 4 columns of bits from right to left.
  • this application is not limited to this, and DRB ID0, DRB ID3, DRB ID5, and DRB ID7 may also correspond to other bit arrays, respectively.
  • the PDCP indicated by the first indication information may include PDCP using the data copy function in the DC scenario and/or PDCP using the data copy function in the CA scenario.
  • the associated MAC entity is the same as the MAC entity that transmits the first indication information.
  • the at least one PDCP entity includes N PDCP entities, and N is a positive integer.
  • the first indication information includes N fields, and the N PDCP entities respectively correspond to the N fields, wherein each field includes multiple bits, and the multiple bits respectively correspond to each field.
  • the N fields may be located in N bytes or N octets, for example.
  • rows 1 to 4 correspond to DRB ID0, DRB ID3, DRB ID5, and DRB ID7 in sequence.
  • the first 4 bits in row 1 correspond to the 4 RLC entities associated with DRB ID0;
  • the first 4 bits in row 2 correspond to the 4 RLC entities associated with DRB ID3 in sequence;
  • the first 4 bits in row 3 They correspond to the 4 RLC entities associated with DRB ID5 in sequence;
  • the first 2 bits in the fourth row correspond to the 2 RLC entities associated with DRB ID7 in sequence.
  • the first three RLC entities associated with DRB ID0 are used to transmit replicated data
  • the first three RLC entities associated with DRB ID3 are used to transmit replicated data
  • the four RLC entities associated with DRB ID5 are all used to transmit replicated data.
  • DRB The two RLC entities associated with ID7 are both used to transmit replicated data.
  • the at least one PDCP entity indicated by the first indication information may include a PDCP entity based on CA-based replication data transmission, and may also include a PDCP entity based on DC-based replication data transmission.
  • the RLC entities associated with the PDCP entity are all associated with the same MAC entity, so the LCIDs of these RLC entities are different.
  • LCID 1, LCID 4, LCID 5, and LCID 8 may correspond to the 4 bits in the first column in order from top to bottom.
  • the network device wants to activate the copy data transmission function of DRB ID0, and wants DRB ID0 to transmit the copied data through RLC entity 1, RLC entity 2 and RLC entity 3, then the first 3 rows of the first column are set to 1. , The last line is set to 0.
  • the RLC entities associated with the PDCP entity may be associated with the MAC entities of different CGs, so the LCIDs of the RLC entities of different MAC entities may be the same.
  • the different CGs described here may include MCG and SCG, or may include more than two CGs.
  • the replication data transmission in the DC scenario may include the case where one CG has one RLC entity, and may also include the case where one CG has multiple RLC entities.
  • the RLC entity of the MCG and the RLC entity of the SCG may be respectively corresponded.
  • the embodiment of the present application provides two ways to map RLC entities of different CGs to bit rows or bit columns corresponding to PDCP entities associated with these RLC entities.
  • a possible implementation manner is that, among the N PDCP entities, multiple RLC entities associated with the PDCP entity based on DC-based replication data transmission correspond to the multiple bits in sequence according to the order of the cell group to which they belong.
  • the four RLC entities associated with DRB ID5 correspond to LCID 1, LCID 4, LCID 1, and LCID 8, respectively.
  • the 4 bits in the bit string corresponding to DRB ID5 correspond to LCID 1, LCID 4, LCID 1, and LCID 8, from top to bottom.
  • the bit array corresponding to DRB ID5 first corresponds to LCID 1 and LCID 4 of MCG from top to bottom, and after corresponding to the RLC entity of MCG, it immediately corresponds to LCID 1 and LCID 8 of SCG.
  • the LCIDs of RLC entity 1 and RLC entity 3 belonging to different CGs are LCID 1, because they correspond to MCG first and then SCG, the first row of the bit column corresponding to DRB ID5 corresponds to the MCG.
  • the RLC entity 1 is used to indicate whether the RLC entity 1 is used to transmit replicated data; the third row corresponds to the RLC entity 3 of the SCG and is used to indicate whether the RLC entity 3 is used to transmit replicated data.
  • Another possible implementation manner is that, among the N PDCP entities, multiple RLC entities associated with the PDCP entity based on DC-based replication data transmission are based on the cell group to which they belong, and respectively correspond to the data in the multiple bits. Bits divided by each cell group.
  • the 4 RLC entities associated with DRB ID5 correspond to LCID 1, LCID 4, LCID 1, and LCID 8, respectively.
  • the 4 bits in the bit string corresponding to DRB ID5 are divided into two groups.
  • the first group is used for the RLC entity corresponding to MCG, including the first 2 bits;
  • the second group is used for the RLC entity corresponding to SCG, including the last two Bits.
  • the LCID 1 and LCID 4 of the MCG correspond to the first two bits in the first group
  • the LCID 1 and LCID 8 of the SCG correspond to the first two bits in the second group.
  • the LCIDs corresponding to RLC entity 1 and RLC entity 3 belonging to different CGs are LCID 1
  • the bits corresponding to RLC entity 1 of MCG are in the first group of bits
  • the bits corresponding to RLC entity 3 of SCG are in the second group of bits. Therefore, it is possible to indicate the RLC entities of different CGs respectively.
  • each RLC entity should be based on the cell group to which it belongs, and respectively correspond to the bits divided for the cell group. Even if the number of bits in the first group is more than the number of RLC entities of MCG, the more bits in the first group are not used to indicate the RLC entity of SCG, but the bits in the second group should be used to indicate the RLC entity of SCG .
  • multiple RLC entities belonging to the same cell group sequentially correspond to multiple bits in the order of the corresponding logical channel identifiers.
  • LCID 1, LCID 4, LCID 5, and LCID 8 from small to large correspond to the first, second, third, and fourth bits in the first column from front to back.
  • the LCID 1 and LCID 4 of the MCG are from small to large, corresponding to the first and second bits from front to back in the first group; the LCID 1 and LCID 8 of the SCG are from small to large. Large, corresponding to the first and second bits from front to back in the second group.
  • the network device uses method 1 to send the first instruction information to the terminal device to control the transmission of the copied data
  • multiple DRBs can be activated/deactivated through a MAC CE, and the network device can use the first instruction information to indicate that it is used to transmit the copied data
  • the RLC entity thus controls the replication data transmission function of the activated/deactivated DRB. Under the replication data transmission mechanism with more than two copies, effective replication data transmission is realized.
  • the at least one PDCP entity includes one PDCP entity.
  • the first indication information includes a first field, and the first field is used to indicate the PDCP entity, and the first indication information further includes a second field and/or a third field, and the second field is used for To indicate the activation or deactivation of the copy data transmission function of the PDCP entity, the third field is used to indicate the RLC entity used to transmit the copy data among the multiple RLC entities associated with the PDCP entity.
  • the first indication information may be carried in the MAC CE, for example.
  • the network device separately instructs each PDCP entity, and the first indication information includes the activation/deactivation information of a PDCP entity, and/or the RLC associated with the PDCP entity for transmitting replicated data.
  • Information about the entity Compared with method 1, in method 2, there is no need to additionally define the correspondence between PDCP entities and bits. Instead, the PDCP entity information is directly obtained according to the content indicated by each field, and the DC scene and the CA scene The PDCP replication data transmission does not need to be defined separately, which reduces the implementation complexity.
  • the embodiment of the present application provides the following two modes:
  • One implementation manner is to respectively indicate multiple PDCP entities through multiple first indication information.
  • the multiple first indication information may be carried on the same MAC CE, or may be carried on different MAC CEs. For example, by sending multiple MAC CEs to respectively instruct multiple PDCP entities to activate the RLC entity used to transmit replicated data among the RLC entities associated with the PDCP entity.
  • Another implementation manner is to associate the PDCP entity with another PDCP entity, and the other PDCP entity and the associated PDCP entity are simultaneously activated/deactivated.
  • multiple groups of PDCP entities can be set, and the PDCP entities in each group of PDCP entities are activated/deactivated at the same time.
  • the copy data transmission function of a PDCP entity in the group of PDCP entities is activated, the copy data transmission function of the group of PDCP entities is activated; when the copy data transmission function of a PDCP entity in the group of PDCP entities is deactivated , Then the copy data transmission function of the group of PDCP entities are all deactivated.
  • the network device can control the activation/deactivation of multiple PDCP entities by instructing the activation/deactivation of one PDCP entity.
  • the first indication information includes a first field, and the first field is used to indicate a PDCP entity, and the first field may be, for example, a DRB ID corresponding to the PDCP entity.
  • the first indication information may include a second field, and the second field is used to indicate the activation/deactivation of the copy data transmission function of the PDCP entity.
  • the first indication information includes one byte or one octet.
  • the first indication information includes a first field and a second field.
  • the following assumes that the total number of DRBs is 32, and the first field may include 5 bits to indicate different DRB IDs.
  • the second field is the Deactivation/Activation (D/A) field shown in Figure 10, including 1 bit, which is used to indicate the activation/deactivation of the copy data transmission function of the DRB ID indicated by the first field For example, when it is 1, it means activation, and 0 means deactivation.
  • D/A Deactivation/Activation
  • the terminal device can determine the activated/deactivated DRB according to the first field and the second field.
  • the first indication information may further include a third field, where the third field is used to indicate an RLC entity used to transmit replicated data among multiple RLC entities associated with the PDCP entity.
  • the third field can indicate the RLC entity used to transmit the copied data in the following two ways.
  • the third field includes multiple bits, and the multiple bits respectively correspond to multiple RLC entities associated with the PDCP entity, and each bit is used to indicate whether the RLC entity corresponding to each bit is used for Transfer copied data.
  • multiple RLC entities associated with a PDCP entity for CA-based replication data transmission may sequentially correspond to multiple bits in the third field in the order of their corresponding logical channel identifiers. Similar to the mapping method shown in Figure 8.
  • multiple RLC entities associated with a PDCP entity for DC-based replication data transmission may correspond to multiple bits in the third field in sequence according to the order of the cell group to which they belong. Similar to the mapping method shown in Figure 9(a).
  • multiple RLC entities associated with a PDCP entity for DC-based replication data transmission may be based on the cell group to which they belong, and respectively correspond to the bits divided for each cell group in the third field. Similar to the mapping method shown in Figure 9(b).
  • the RLC entities belonging to the same cell group correspond to the multiple in the third field in the order of the corresponding logical channel identifiers. Bits.
  • the third field is used to indicate the RLC entity group used to transmit replicated data among multiple RLC entities associated with the PDCP entity, wherein the RLC entities in the same RLC entity group are used to transmit replicated data at the same time .
  • the network device may send the second indication information to the terminal device.
  • the terminal device receives the second indication information sent by the network device.
  • the second indication information is used to indicate multiple RLC entity groups, and the RLC entities in different RLC entity groups are partially or completely different.
  • the second indication information may be carried in radio resource control (Radio Resource Control, RRC) signaling, for example.
  • RRC Radio Resource Control
  • the RRC signaling may include the ID of the RLC entity group, and the RLC entity group is indicated by the RLC entity group identifier carried in the RRC signaling.
  • the information of multiple RLC entity groups and the ID of the RLC entity group used to transmit replicated data in the multiple RLC entity groups are carried in the RLC-BearerConfig information element (Information Element) of RRC signaling .
  • the IE includes two domains. One domain may include the information of multiple divided RLC entity groups, and the other domain may include the identification information of the RLC entity group to be used.
  • the multiple RLC entity groups may also be pre-configured in the terminal device, for example, agreed in advance by a protocol.
  • the PDCP entity is associated with 4 RLC entities, and the LCIDs corresponding to the 4 RLC entities are LCID 1, LCID 4, LCID 5, and LCID 8, respectively.
  • the 4 RLC entities are divided into 4 RLC entity groups. Among them, the LCIDs corresponding to the RLC entities included in the RLC entity group 1 are LCID 1, LCID 4; the LCIDs corresponding to the RLC entities included in the RLC entity group 2 are LCID 1, LCID 5; the RLC entities included in the RLC entity group 3 correspond to The LCID is LCID 4 and LCID 5; the LCIDs corresponding to the RLC entities included in the RLC entity group 4 are LCID 5 and LCID 8.
  • the third field includes 2 bits, as shown in Table 1, according to the content of the third field, it is possible to know which RLC entity group is used to transmit the replicated data, and the RLC entities in the same RLC entity group jointly transmit the replicated data.
  • RLC entity group ID 00 RLC entity group 1 (LCID 1, LCID 4) 01 RLC entity group 2 (LCID 1, LCID 5) 10 RLC entity group 3 (LCID 4, LCID 5) 11 RLC entity group 4 (LCID 5, LCID 8)
  • the first indication information includes one byte or one octet.
  • the first indication information includes a first field, a second field, and a third field. Assuming that the total number of current DRBs is 32, the first field may include 5 bits to indicate different DRB IDs.
  • the second field may be a D/A field, including 1 bit, which is used to indicate whether the copy data transmission function of the DRB ID indicated by the first field is activated. For example, if it is 1, it means activation, and 0 means deactivation.
  • the third field indicates the LCID or the identifier of the RLC entity group (referred to as the group identifier for short) corresponding to the RLC entity used to transmit the copied data.
  • the terminal device can determine whether the copy data transmission function of the DRB ID is activated according to the first field and the second field. If the copy data transmission function of the DRB ID is activated, it can be judged according to the third field The RLC entity used to transmit replicated data.
  • the third field includes 1 bit, which can be used to indicate two RLC entity groups or two RLC entities associated with the DRB ID.
  • the third field includes 2 bits, which can be used to indicate four RLC entity groups or four RLC entities associated with the DRB ID.
  • the third field is used to indicate which RLC entities of the RLC entities associated with the PDCP entity are used to transmit the copied data;
  • the second field indicates that the replication data transmission function of the DRB ID is deactivated.
  • the third field may indicate the RLC entity used to transmit non-replicated data, and other The RLC entity does not perform data transmission, or the third field may be vacant or indicate other information, which is not limited here.
  • the RLC entity used to transmit non-replicated data can also be pre-configured. For example, a certain RLC entity of MCG can be pre-configured.
  • the RLC entity can be used to transmit non-replicated data when the copy data transmission function of its associated PDCP entity is deactivated. Copy the data.
  • the first field, the second field, and the third field are described above, but the first indication information does not necessarily include the second field and the third field at the same time. There are the following four situations in the embodiments of this application, which are described separately below.
  • the first indication information includes a first field, a second field, and a third field.
  • the first field may be used to indicate the PDCP entity
  • the second field may be used to indicate the activation/deactivation of the PDCP copy data transmission function
  • the third field may be used to indicate the RLC entity that transmits the copy data.
  • the first field includes the DRB ID; the second field is the D/A field, which is used to indicate whether the DRB ID’s copy data transmission function Activate; the third field is used to indicate the LCID or the ID of the RLC entity group corresponding to the RLC entity that transmits the copied data.
  • the first indication information includes a first field and a third field.
  • the third field may also be used to indicate the activation/deactivation of the copy data transmission function of the PDCP entity.
  • the third field is a specific value, such as 0, the third field is used to indicate that the PDCP entity's copy data transmission is deactivated; and/or, the third field is a value other than the specific value At this time, the third field is used to indicate that the copy data transmission function of the PDCP entity is activated.
  • the first indication information includes a first field and a third field.
  • the first field may include 5 bits to indicate different DRB IDs.
  • the third field may include 3 bits, used to indicate the activation/deactivation of the copy data transmission function of the DRB ID, and used to indicate the RLC entity that transmits the copied data.
  • the third field when the third field is 000, it can be used to indicate that the DRB ID's copy data transmission function is deactivated; when the third field has other values, it can be used to indicate the copy of the DRB ID
  • the data transmission function is activated, and the value of the third field can indicate the LCID or RLC entity group corresponding to the RLC entity used to transmit the copied data.
  • the value of the third field when the value of the third field is 011, it can be determined
  • the copy data transmission function of the DRB ID is activated, and the third field indicates that the RLC entity in the RLC entity group corresponding to 011 is used to transmit the copy data.
  • the third field in FIG. 12(a) and FIG. 12(b) includes 3 bits, but is not limited to this, and the third field may also include 1 bit, 2 bits, and so on.
  • the first indication information may include one byte or two bytes.
  • the third field and the first field are located in different bytes of the two bytes.
  • the foregoing Fig. 10, Fig. 11(a), Fig. 11(b), Fig. 12(a) and Fig. 12(b) are all cases where the first indication information includes one byte.
  • the third field is usually used to indicate the RLC entity group that transmits the replicated data, but cannot separately indicate whether each RLC is used for Transfer copied data.
  • the third field may not belong to the same byte as the first field.
  • Figures 13(a) and 13(b) show the case where the first indication information includes two bytes. Among them, in Figure 13(a), the first field and the second field are located in the first byte, and the third field is located in the second byte. In Figure 13(b), the first indication information does not include the second field, the first field is located in the first byte, and the third field is located in the second byte. In this way, the third field can include up to 8 bits, and can indicate up to 8 RLC entities. When the copy data transmission function of the DRB ID indicated by the first field is activated, the third field may indicate whether a specific RLC entity is used to transmit the copy data.
  • Each bit of the third field can correspond to an LCID, and the LCIDs corresponding to multiple RLC entities associated with the PDCP entity indicated in the first field can be in descending order, starting from the first bit of the third field.
  • the LCID corresponding to its associated RLC entity can correspond to the bits in the third field in the order from MCG to SCG, from right to left.
  • the associated RLC entity corresponds to the bit divided for the CG according to the CG to which the RLC entity belongs.
  • the LCID corresponding to its associated RLC entity can be in the order of LCID size, for example, in ascending order, corresponding to the items in the third field from right to left. Bits.
  • the first indication information includes a first field and a second field.
  • the first indication information includes the third field
  • the first indication information does not include the third field.
  • the first field and the third field in the first indication information may be located in different bytes, which introduces new bit overhead.
  • the third field can be omitted to save bit overhead.
  • the third field is used to indicate the RLC entity used to transmit the copy data.
  • two types of MAC CE can be set.
  • the formats of the two MAC CEs are different, and they can be distinguished by the MAC subheader (MAC subheader).
  • the first indication information can be carried in these two types of MAC CE.
  • the LCID in the MAC sub-packet header can be used to distinguish two different types of MAC CE.
  • one type of MAC CE is used to indicate the activation of the copy data transmission function of the PDCP entity.
  • This type of MAC CE includes 2 bytes, and the first byte includes the first field.
  • the second byte includes a third field, which is used to indicate the RLC entity that transmits the copied data.
  • another type of MAC CE is used to indicate the deactivation of the copy data transmission function of the PDCP entity.
  • This type of MAC CE may only include 1 byte.
  • the format of the MAC CE used to instruct the deactivation of the copy data transmission function of the PDCP entity may reuse the existing MAC CE format in the current protocol, such as the MAC CE format described in Figure 6(a).
  • the second field indicates that the copy data transmission function of the PDCP entity is activated
  • the first indication information includes the third field
  • the second field indicates that the copy data transmission function of the PDCP entity is deactivated.
  • the indication information does not include the third field.
  • the terminal device can determine the format of the MAC CE according to the received sub-packet header of the MAC CE, and can determine whether the copy data transmission function of the PDCP entity is activated according to the format of the MAC CE, and determine which RLC entity is used for the third field when activated. Transfer copied data.
  • the RLC entity or the RLC entity used to transmit replicated data among the multiple RLC entities associated with the PDCP entity may also be dynamically indicated through, for example, RRC signaling.
  • RLC entity group when the first indication information only includes the first field and the second field, the RLC entity or the RLC entity used to transmit replicated data among the multiple RLC entities associated with the PDCP entity may also be dynamically indicated through, for example, RRC signaling. RLC entity group.
  • the first indication information includes the first field, the second field, and the third field.
  • Case 4 is a special case of Case 1.
  • the method further includes:
  • the terminal device reads the third field; and/or,
  • the terminal device does not read the third field.
  • the content included in the first indication information is different when the PDCP entity is activated and deactivated, that is, the format of the MAC CE is different when activated and deactivated.
  • the first indication information includes the third field, and the format of the MAC CE is always the same. After receiving the first indication information, the terminal device determines whether or not it is based on reading the first field and the second field. Read the third field.
  • the third field is always carried in the first indication information, and the terminal device may determine whether to read the third field based on the implementation of the terminal device.
  • the activation/deactivation of the copy data transmission function of the PDCP entity and the RLC entity used to transmit the copied data are indicated by bitmap, which can realize multiple PDCP entities and multiple RLCs. At the same time the entity indicates.
  • the activation/deactivation of the copy data transmission function of the PDCP entity is separately instructed. Further, the RLC entity associated with the PDCP entity for transmitting the copy data can also be instructed, which is less than the mode 1.
  • the MAC CE overhead is further reduced. In addition, the manner in which the terminal device reads the first indication information can be more flexible, which improves data processing efficiency.
  • FIG. 17 is a schematic block diagram of a terminal device 1700 according to an embodiment of the present application. As shown in FIG. 17, the terminal device 1700 includes a receiving unit 1710 and a processing unit 1720. among them:
  • the receiving unit 1710 is configured to receive first indication information
  • the processing unit 1720 is configured to process the PDCP PDU according to the first indication information received by the receiving unit 1710.
  • the first indication information is used to indicate the activation or deactivation of the replication data transmission function of at least one PDCP entity, and/or indicate that the at least one PDCP entity is used for transmission in multiple RLC entities associated with each of the at least one PDCP entity.
  • the RLC entity that replicates the data is used to indicate the activation or deactivation of the replication data transmission function of at least one PDCP entity, and/or indicate that the at least one PDCP entity is used for transmission in multiple RLC entities associated with each of the at least one PDCP entity.
  • the RLC entity that replicates the data is used to indicate the activation or deactivation of the replication data transmission function of at least one PDCP entity, and/or indicate that the at least one PDCP entity is used for transmission in multiple RLC entities associated with each of the at least one PDCP entity.
  • the RLC entity that replicates the data is used to indicate the activation or deactivation of the replication data transmission function of at least one PDCP entity, and/or indicate that the at least
  • the at least one PDCP entity includes: a PDCP entity based on carrier aggregation CA for replication data transmission; and/or a PDCP entity based on dual connectivity DC for replication data transmission.
  • the at least one PDCP entity includes N PDCP entities.
  • the first indication information includes M fields, wherein each field includes N bits, the N PDCP entities respectively correspond to the N bits, and multiple RLC entities associated with the same PDCP entity correspond to the M Multiple bits in the same position in each field, where each bit is used to indicate whether the RLC entity corresponding to each bit is used to transmit replicated data, M and N are positive integers, and M is the RLC entity associated with a PDCP entity the most amount.
  • the M fields are located in M bytes respectively.
  • the at least one PDCP entity includes N PDCP entities.
  • the first indication information includes N fields, and the N PDCP entities respectively correspond to the N fields, wherein each field includes a plurality of bits, and the plurality of bits respectively correspond to each field.
  • the N fields are located in N bytes respectively.
  • multiple RLC entities associated with the PDCP entity based on dual-connection duplication data transmission among the N PDCP entities correspond to the multiple bits in sequence according to the order of the cell group to which they belong.
  • multiple RLC entities associated with the PDCP entity based on dual-connectivity duplication data transmission are based on the cell group to which they belong, and correspond to the division of the multiple bits for each cell group respectively. Of bits.
  • multiple RLC entities belonging to the same cell group correspond to multiple bits in sequence according to the sequence of the corresponding logical channel identifiers.
  • the at least one PDCP entity includes one PDCP entity.
  • the first indication information includes a first field, the first field is used to indicate the PDCP entity, the first indication information further includes a second field and/or a third field, and the second field is used to indicate The copy data transmission function of the PDCP entity is activated or deactivated, and the third field is used to indicate the RLC entity used to transmit the copied data among the multiple RLC entities associated with the PDCP entity.
  • the PDCP entity is associated with another PDCP entity, and the other PDCP entity is activated or deactivated simultaneously with the PDCP entity.
  • the first indication information does not include the second field
  • the third field is also used to indicate the activation or deactivation of the copy data transmission function of the PDCP entity.
  • the third field is also used to indicate the activation or deactivation of the copy data transmission function of the PDCP entity, including: when the third field is a specific value, the third field is used to indicate the PDCP The copy data transmission function of the entity is deactivated; when the third field is a value other than the specific value, the third field is used to indicate that the copy data transmission function of the PDCP entity is activated.
  • the first indication information includes the second field. If the second field indicates that the copy data transmission function of the PDCP entity is activated, the first indication information includes the third field, and if the second field indicates that the copy data transmission function of the PDCP entity is deactivated, The first indication information does not include the third field.
  • the first indication information includes the second field and the third field
  • the processing unit is further configured to: if the second field indicates that the copy data transmission function of the PDCP entity is activated, The terminal device reads the third field; and/or, if the second field indicates that the copy data transmission function of the PDCP entity is deactivated, the terminal device does not read the third field.
  • the first indication information includes one byte.
  • the first indication information includes two bytes, and the third field and the first field are located in different bytes of the two bytes.
  • the first indication information is carried in the MAC CE.
  • multiple bits in the third field correspond to the multiple RLC entities associated with the PDCP entity, and each bit is used to indicate whether the RLC entity corresponding to each bit is used for Transfer copied data.
  • multiple RLC entities associated with the PDCP entity based on dual-connection duplication data transmission correspond to multiple bits in the third field in sequence according to the order of the cell group to which they belong.
  • the multiple RLC entities associated with the PDCP entity based on dual-connection duplication data transmission respectively correspond to the bits divided for each cell group in the third field based on the cell group to which they belong.
  • the RLC entities belonging to the same cell group sequentially correspond to multiple bits in the third field in the order of the corresponding logical channel identifiers.
  • the third field is used to indicate the RLC entity used to transmit replicated data among the multiple RLC entities associated with the PDCP entity, including: the third field is used to indicate the multiple RLC entities used in the multiple RLC entities RLC entity group for transmitting replicated data, wherein RLC entities in the same RLC entity group are used to transmit replicated data at the same time.
  • the receiving unit 1710 is further configured to: receive second indication information sent by the network device, where the second indication information is used to indicate multiple RLC entity groups, and some or all of the RLC entities in different RLC entity groups are different .
  • the second indication information is carried in RRC signaling.
  • terminal device 1700 can perform the corresponding operations performed by the terminal device in the foregoing method 400, and for brevity, details are not described herein again.
  • FIG. 18 is a schematic block diagram of a terminal device 1800 according to an embodiment of the present application. As shown in FIG. 18, the terminal device 1800 includes a processing unit 1810 and a sending unit 1820. among them:
  • the processing unit 1810 is configured to generate first indication information
  • the processing unit 1820 is configured to send the first indication information generated by the processing unit 1810.
  • the first indication information is used to indicate the activation or deactivation of the replication data transmission function of at least one PDCP entity, and/or indicate that the at least one PDCP entity is used for transmission in multiple RLC entities associated with each of the at least one PDCP entity.
  • the RLC entity that replicates the data is used to indicate the activation or deactivation of the replication data transmission function of at least one PDCP entity, and/or indicate that the at least one PDCP entity is used for transmission in multiple RLC entities associated with each of the at least one PDCP entity.
  • the RLC entity that replicates the data is used to indicate the activation or deactivation of the replication data transmission function of at least one PDCP entity, and/or indicate that the at least one PDCP entity is used for transmission in multiple RLC entities associated with each of the at least one PDCP entity.
  • the RLC entity that replicates the data is used to indicate the activation or deactivation of the replication data transmission function of at least one PDCP entity, and/or indicate that the at least
  • the at least one PDCP entity includes: a PDCP entity based on carrier aggregation CA for replication data transmission; and/or a PDCP entity based on dual connectivity DC for replication data transmission.
  • the at least one PDCP entity includes N PDCP entities.
  • the first indication information includes M fields, wherein each field includes N bits, the N PDCP entities respectively correspond to the N bits, and multiple RLC entities associated with the same PDCP entity correspond to the M Multiple bits in the same position in each field, where each bit is used to indicate whether the RLC entity corresponding to each bit is used to transmit replicated data, M and N are positive integers, and M is the RLC entity associated with a PDCP entity the most amount.
  • the M fields are located in M bytes respectively.
  • the at least one PDCP entity includes N PDCP entities.
  • the first indication information includes N fields, and the N PDCP entities respectively correspond to the N fields, wherein each field includes a plurality of bits, and the plurality of bits respectively correspond to each field.
  • the N fields are located in N bytes respectively.
  • multiple RLC entities associated with the PDCP entity based on dual-connection duplication data transmission among the N PDCP entities correspond to the multiple bits in sequence according to the order of the cell group to which they belong.
  • multiple RLC entities associated with the PDCP entity based on dual-connectivity duplication data transmission are based on the cell group to which they belong, and correspond to the division of the multiple bits for each cell group respectively. Of bits.
  • multiple RLC entities belonging to the same cell group correspond to multiple bits in sequence according to the sequence of the corresponding logical channel identifiers.
  • the at least one PDCP entity includes one PDCP entity.
  • the first indication information includes a first field, the first field is used to indicate the PDCP entity, the first indication information further includes a second field and/or a third field, and the second field is used to indicate The copy data transmission function of the PDCP entity is activated or deactivated, and the third field is used to indicate the RLC entity used to transmit the copied data among the multiple RLC entities associated with the PDCP entity.
  • the PDCP entity is associated with another PDCP entity, and the other PDCP entity is activated or deactivated simultaneously with the PDCP entity.
  • the first indication information does not include the second field
  • the third field is also used to indicate the activation or deactivation of the copy data transmission function of the PDCP entity.
  • the third field is also used to indicate the activation or deactivation of the copy data transmission function of the PDCP entity, including: when the third field is a specific value, the third field is used to indicate the PDCP The copy data transmission function of the entity is deactivated; when the third field is a value other than the specific value, the third field is used to indicate that the copy data transmission function of the PDCP entity is activated.
  • the first indication information includes the second field. If the second field indicates that the copy data transmission function of the PDCP entity is activated, the first indication information includes the third field, and if the second field indicates that the copy data transmission function of the PDCP entity is deactivated, The first indication information does not include the third field.
  • the first indication information includes the second field and the third field
  • the processing unit is further configured to: if the second field indicates that the copy data transmission function of the PDCP entity is activated, The terminal device reads the third field; and/or, if the second field indicates that the copy data transmission function of the PDCP entity is deactivated, the terminal device does not read the third field.
  • the first indication information includes one byte.
  • the first indication information includes two bytes, and the third field and the first field are located in different bytes of the two bytes.
  • the first indication information is carried in the MAC CE.
  • multiple bits in the third field correspond to the multiple RLC entities associated with the PDCP entity, and each bit is used to indicate whether the RLC entity corresponding to each bit is used for Transfer copied data.
  • multiple RLC entities associated with the PDCP entity based on dual-connection duplication data transmission correspond to multiple bits in the third field in sequence according to the order of the cell group to which they belong.
  • the multiple RLC entities associated with the PDCP entity based on dual-connection duplication data transmission respectively correspond to the bits divided for each cell group in the third field based on the cell group to which they belong.
  • the RLC entities belonging to the same cell group sequentially correspond to multiple bits in the third field in the order of the corresponding logical channel identifiers.
  • the third field is used to indicate the RLC entity used to transmit replicated data among the multiple RLC entities associated with the PDCP entity, including: the third field is used to indicate the multiple RLC entities used in the multiple RLC entities RLC entity group for transmitting replicated data, wherein RLC entities in the same RLC entity group are used to transmit replicated data at the same time.
  • the sending unit 1820 is further configured to send second indication information to the terminal device, where the second indication information is used to indicate multiple RLC entity groups, and the RLC entities in different RLC entity groups are partially or completely different.
  • the second indication information is carried in RRC signaling.
  • the network device 1800 can perform the corresponding operations performed by the network device in the foregoing method 400, which is not repeated here for brevity.
  • FIG. 19 is a schematic structural diagram of a communication device 1900 according to an embodiment of the present application.
  • the communication device 1900 shown in FIG. 19 includes a processor 1910, and the processor 1910 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the communication device 1900 may further include a memory 1920.
  • the processor 1910 can call and run a computer program from the memory 1920 to implement the method in the embodiment of the present application.
  • the memory 1920 may be a separate device independent of the processor 1910, or it may be integrated in the processor 1910.
  • the communication device 1900 may further include a transceiver 1930, and the processor 1910 may control the transceiver 1930 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 1930 may include a transmitter and a receiver.
  • the transceiver 1930 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 1900 may specifically be a terminal device in an embodiment of the application, and the communication device 1900 may implement the corresponding process implemented by the terminal device in each method of the embodiment of the application. For brevity, details are not repeated here. .
  • the communication device 1900 may specifically be a network device of an embodiment of the application, and the communication device 1900 may implement the corresponding process implemented by the network device in each method of the embodiment of the application. For brevity, details are not repeated here. .
  • FIG. 20 is a schematic structural diagram of a chip of an embodiment of the present application.
  • the chip 2000 shown in FIG. 20 includes a processor 2010, and the processor 2010 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the chip 2000 may further include a memory 2020.
  • the processor 2010 can call and run a computer program from the memory 2020 to implement the method in the embodiment of the present application.
  • the memory 2020 may be a separate device independent of the processor 2010, or may be integrated in the processor 2010.
  • the chip 2000 may further include an input interface 2030.
  • the processor 2010 can control the input interface 2030 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the chip 2000 may further include an output interface 2040.
  • the processor 2010 can control the output interface 2040 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • chips mentioned in the embodiments of the present application may also be referred to as system-level chips, system-on-chips, system-on-chips, or system-on-chips.
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments may be completed by instructions in the form of hardware integrated logic circuits or software in the processor.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA ready-made programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, and a register.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be Read-Only Memory (ROM), Programmable Read-Only Memory (Programmable ROM, PROM), Erasable Programmable Read-Only Memory (Erasable PROM, EPROM), and Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • Synchlink DRAM SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data) SDRAM (DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memories in the embodiments of the present application are intended to include but are not limited to these and any other suitable types of memories.
  • FIG. 21 is a schematic block diagram of a communication system 2100 according to an embodiment of the present application. As shown in FIG. 21, the communication system 2100 includes a network device 2110 and a terminal device 2120.
  • the network device 2110 is configured to send first indication information to the terminal device 2120.
  • the terminal device 2120 is configured to receive the first indication information sent by the network device 2110.
  • the first indication information is used to indicate the activation or deactivation of the replication data transmission function of at least one PDCP entity, and/or indicate the RLC used to transmit replicated data among multiple RLC entities respectively associated with the at least one PDCP entity entity.
  • the network device 2110 can be used to implement the corresponding functions implemented by the network device in the above method 500, and the composition of the network device 2110 can be as shown in the network device 1800 in FIG. 18, for the sake of brevity, it will not be repeated here.
  • the terminal device 2120 may be used to implement the corresponding functions implemented by the terminal device in the above method 500, and the composition of the terminal device 2120 may be as shown in the terminal device 1700 in FIG. 17, which is not repeated here for brevity.
  • Embodiments of the present application also provide a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium may be applied to the terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For brevity, here No longer.
  • An embodiment of the present application also provides a computer program product, including computer program instructions.
  • the computer program product can be applied to the terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the embodiment of the application also provides a computer program.
  • the computer program may be applied to the terminal device in the embodiment of the present application.
  • the computer program runs on the computer, it causes the computer to execute the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program is run on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity , I won’t repeat it here.
  • B corresponding (corresponding) to A means that B is associated with A, and B can be determined according to A.
  • determining B based on A does not mean determining B based on A alone, and B may also be determined based on A and/or other information.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a division of logical functions.
  • there may be another division manner for example, multiple units or components may be combined or may Integration 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 purpose of the solution of this embodiment.
  • each functional unit in each embodiment 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 function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product
  • the computer software product is stored in a storage medium, including Several instructions are used to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application.
  • the foregoing storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

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

Abstract

本申请公开了一种用于复制数据传输的方法，能够在多于两个副本的复制数据传输机制中实现有效的复制数据传输。该方法包括：终端设备接收所述第一指示信息；所述终端设备根据所述第一指示信息对PDCP PDU进行处理，其中，所述第一指示信息用于指示至少一个PDCP实体的复制数据传输功能激活或者去激活，和/或指示所述至少一个PDCP实体各自关联的多个RLC实体中用于传输复制数据的RLC实体。

Description

用于复制数据传输的方法和设备 技术领域
本申请实施例涉及领域，并且更具体地，涉及一种用于复制数据传输的方法和设备。
背景技术
在双连接(Dual Connectivity，DC)场景下，多个网络节点例如主基站(Master eNB，MN)和辅基站(Secondary eNB，SN)可以为终端设备服务，多个基站和终端设备之间可以进行复制数据的传输。
在载波聚合场(Carrier Aggregation，CA)场景下，分组数据汇聚层协议(Packet Data Convergence Protocol，PDCP)可以将一个PDCP协议数据单元(Protocol Data Unit，PDU)复制成两份，分别映射到不同的RLC实体，并通过MAC实体映射到两个不同的物理载波上，从而达到频率分集增益以提高数据传输的可靠性。
在新无线(New Radio，NR)系统中，PDCP实体(Data RadioBearer，DRB)所关联的无线链路控制(Radio Link Control，RLC)实体的数量会更多，PDCP实体可以复制的PDCP PDU的数量也会更多。因此，如何有效地进行复制数据传输，成为亟待解决的问题。
发明内容
本申请实施例提供一种用于复制数据传输的方法和设备，能够实现有效的复制数据传输。
第一方面，提供了一种用于复制数据传输的方法，包括：终端设备接收第一指示信息；所述终端设备根据所述第一指示信息对PDCP PDU进行处理。其中，所述第一指示信息用于指示至少一个PDCP实体的复制数据传输功能激活或者去激活，和/或指示所述至少一个PDCP实体各自关联的多个RLC实体中用于传输复制数据的RLC实体。
第二方面，提供了一种用于复制数据传输的方法，包括：网络设备发送第一指示信息，所述第一指示信息用于终端设备对PDCP PDU进行处理，其中，所述第一指示信息用于指示至少一个PDCP实体的复制数据传输功能激活或者去激活，和/或指示所述至少一个PDCP实体各自关联的多个RLC实体中用于传输复制数据的RLC实体。
第三方面，提供了一种终端设备，该终端设备可以执行上述第一方面或第一方面的任意可选的实现方式中的方法。具体地，该终端设备可以包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的功能模块。
第四方面，提供了一种网络设备，该网络设备可以执行上述第二方面或第二方面的任意可选的实现方式中的方法。具体地，该网络设备可以包括用于执行上述第二方面或第二方面的任意可能的实现方式中的方法的功能模块。
第五方面，提供了一种终端设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第六方面，提供了一种网络设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第七方面，提供了一种芯片，用于实现上述第一方面或第一方面的任意可能的实现方式中的方法。具体地，该芯片包括处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行如上述第一方面或第一方面的任意可能的实现方式中的方法。
第八方面，提供了一种芯片，用于实现上述第二方面或第二方面的任意可能的实现方式中的方法。具体地，该芯片包括处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行如上述第二方面或第二方面的任意可能的实现方式中的方法。
第九方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第十方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第十一方面，提供了一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第十二方面，提供了一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第十三方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第十四方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第十五方面，提供了一种通信系统，包括终端设备和网络设备。其中：
所述网络设备用于：向终端设备发送第一指示信息。
所述终端设备用于：接收网络设备发送的所述第一指示信息。
其中，所述第一指示信息用于指示至少一个PDCP实体的复制数据传输功能激活或者去激活，和/或指示所述至少一个PDCP实体各自关联的多个RLC实体中用于传输复制数据的RLC实体。
基于上述技术方案，通过第一指示信息来指示至少一个PDCP实体的复制数据传输功能的激活/去激活，以及指示该至少一个PDCP实体各自关联的多个RLC实体中用于传输复制数据的RLC实体，从而在多于两个副本的复制数据传输机制中，仍能够实现有效的复制数据传输。
附图说明
图1是一种多连接场景的示意图。
图2是DC场景和CA场景下的复制数据传输的示意性架构图。
图3(a)和图3(b)是本申请实施例的多于两个副本的复制数据传输机制的示意图。
图4是本申请实施例的用于复制数据传输的方法的流程交互图。
图5是本申请实施例的用于复制数据传输的方法的流程交互图。
图6(a)和图6(b)是本申请实施例的第一指示信息的实现方式的示意图。
图7是本申请实施例的第一指示信息的实现方式的示意图。
图8是本申请实施例的CA场景下的第一指示信息的实现方式的示意图。
图9(a)和图9(b)是本申请实施例的DA场景下的第一指示信息的实现方式的示意图。
图10是本申请实施例的第一指示信息的实现方式的示意图。
图11(a)和图11(b)是本申请实施例的第一指示信息的实现方式的示意图。
图12(a)和图12(b)是本申请实施例的第一指示信息的实现方式的示意图。
图13(a)和图13(b)是本申请实施例的第一指示信息的实现方式的示意图。
图14(a)、图14(b)和图14(c)是本申请实施例的第一指示信息的实现方式的示意图。
图15(a)和图15(b)是本申请实施例的第一指示信息的实现方式的示意图。
图16是本申请实施例的第一指示信息的实现方式的示意图。
图17是本申请实施例的终端设备的示意性框图。
图18是本申请实施例的网络设备的示意性框图。
图19本申请实施例的通信设备的示意性结构图。
图20是本申请实施例的芯片的示意性结构图。
图21是本申请实施例的通信系统的示意性框图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、非授权频段上的LTE(LTE-based access to unlicensed spectrum，LTE-U)系统、非授权频段上的NR(NR-based access to unlicensed spectrum，NR-U)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、未来的5G系统(也可以称为新无线(New Radio，NR)系统或其他通信系统等。
可选地，本申请实施例提到的网络设备或网络节点可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。可选地，该网络设备可以是GSM系统或CDMA系统中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是 LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备、未来5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
可选地，本申请实施例题到的终端设备可以是移动的或固定的。可选地，终端设备可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、未来5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
NR中支持两种模式下的复制数据传输：DC场景下的复制数据传输(DC Duplication)和CA场景下的复制数据传输(CA Duplication)。
在DC场景下，多个小区组(Cell Group，CG)可以为终端设备服务，该多个CG例如可以包括主CG(Master CG，MCG)或者辅CG(Secondary CG，SCG)，也可以称为主基站或者辅基站。如图1所示，图1中的终端设备130周围的网络设备包括主基站110和至少一个辅基站120。该至少一个辅基站120分别与主基站110相连，构成多连接，并分别与终端设备130连接为其提供服务。
该主基站110可以为LTE网络，该辅基站120可以为NR网络；或者，该主基站110可以为NR网络，该辅基站120可以为LTE网络；或者，该主基站110和该辅基站120都为NR网络。此外，该主基站还可以为GSM基站、CDMA基站等，该辅基站也可以为GSM基站、CDMA基站等，这里均不做限定。
终端设备130可以通过主基站110和辅基站120同时建立连接。终端设备130和主基站110建立的连接为主连接，终端设备130与辅基站120建立的连接为辅连接。终端设备130的控制信令可以通过主连接进行传输，而终端设备的数据可以通过主连接和辅连接同时传输，也可以只通过辅连接进行传输。
主基站和辅基站与终端设备之间可以进行复制数据的传输，复制数据传输的方式采用的是分叉承载(split bearer)的协议架构。例如图2所述的复制数据传输的架构示意图，图2示出了三个PDCP实体：PDCP实体1、PDCP实体2和PDCP实体3。其中每个PDCP实体唯一对应于一个数据无线承载(Data RadioBearer，DRB)或信令无线承载(Signaling Radio Bearer,SRB)，以下均以DRB为例进行描述，PDCP实体1、PDCP实体2和PDCP实体3分别对应的DRB的标识依次为DRB ID1、DRB ID2和DBRID3。
DC下的复制数据传输例如可以参考图2中所示的PDCP实体2。PDCP实体2关联于两个不同的RLC实体：RLC实体3和RLC实体4。RLC实体3和RLC实体4分别关联于两个不同的媒介访问控制(Media Access Control，MAC)实体：MCG的MAC实体和SCG的MAC实体。对于上下行传输来说，PDCP实体将PDCP PDU复制为相同的两份，两个PDCP经过不同CG的RLC实体和MAC实体，再经过空口到达终端设备(下行)或者基站(上行)的相应的MAC实体和RLC实体，最后再汇聚到PDCP实体。PDCP层检测到两个PDCP PDU为相同的复制版本，例如可以通过这两个PDCP PDU是否有相同的序列号(Serial Number，SN)来判断，当两个PDCP PDU的SN相同时，则丢弃其中一个PDCP PDU，再将另外一个PDCP PDU递交到高层。应注意，复制的两个PDCP PDU不一定同时到达PDCP层。
在CA场景下，PDCP实体可以将一个PDCP PDU复制成两份，分别映射到不同的RLC实体，并通过MAC实体映射到两个不同的物理载波上，从而达到频率分集增益以提高数据传输的可靠性。
CA下的复制数据传输例如图2中的PDCP实体1和PDCP实体3。CA下的复制数据传输采用的是CA的协议架构。PDCP实体1和PDCP实体3各自关联于两个不同的RLC实体，PDCP实体1关联于RLC实体1和RLC实体2，PDCP实体3关联于RLC实体5和RLC实体6。其中，RLC实体1和RLC实体2关联于同一个MAC实体，即MCG的MAC实体；RLC实体5和RLC实体6关联于同一个MAC实体，即SCG的MAC实体。对于上下行传输来说，每个PDCP实体将PDCP PDU复制为相同的两份，每个PDCP实体经过不同的RLC实体和同一个MAC实体，再经过空口到达终端设备(下行)或者基站(上行)的相应的MAC实体和RLC实体，最后再汇聚到PDCP实体。PDCP层检测到两个PDCP PDU为相同的复制版本，例如可以通过这两个PDCP PDU是否具有相同的SN来判断，当两个PDCP PDU的SN相同时，则丢弃其中一个PDCP PDU，再将另外一个PDCP PDU递交到高层。应注意，复制的两个PDCP PDU不一定同时到达PDCP层。
如图2所示，复制的数据会被限制在不同的载波上进行传输。对于DC下的复制数据传输，由于不同的RLC实体分别关联于不同的MAC实体，这样，经过复制的PDCP PDU自然会在不同的载波上进 行传输。对于CA下的复制数据传输，由于不同的RLC实体关联于同一个MAC实体，协议目前给每个RLC实体对应的逻辑信道配置了一个逻辑信道优先级(Logical Channel Prioritization，LCP)映射参数例如该逻辑信道可用的载波集合(allowed serving cells)，用于限制该逻辑信道的数据只能在对应的载波中传输。通过配置LCP映射参数，能够保证经过不同RLC实体的复制数据即使经过同一个MAC实体也可以在不同的载波上传输。
为了充分利用DC场景和CA场景下的复制数据功能以获得更高的资源使用率和数据传输的可靠性，本申请实施例引入多于两个副本的复制数据传输机制，即每个PDCP实体可以关联于两个以上的RLC实体，每个PDCP实体也可以生成多于两份的复制数据。例如图3(a)所示，PDCP实体关联于四个RLC实体，每个RLC实体对应一个逻辑信道，对于关联到一个MAC实体的每个逻辑信道，其具有唯一的逻辑信道标识(Logical Channel Identity，LCID)。PDCP PDU可以通过这4个RLC实体对应的逻辑信道传输。其中，如果用RLC实体2和RLC实体3来传输复制数据，则为DC场景下的复制PDCP PDU的传输，如果用RLC实体1和RLC实体2或用RLC实体3和RLC实体4来传输复制数据，则对应于CA场景下的复制PDCP PDU的传输。RLC实体1和RLC实体2为MCG的RLC实体，RLC实体3和RLC实体4为SCG的RLC实体。RLC实体1和RLC实体2传输的PDCP PDU通过MCG的MAC实体分别映射至载波集合1和载波集合2中的载波上。RLC实体3和RLC实体4传输的复制的PDCP PDU通过SCG的MAC实体2分别映射至载波集合3和载波集合4中的载波上。理论上，复制的PDCP PDU最多能够在4个物理载波上进行传输，实现了更高的资源使用率和数据传输的可靠性。
又例如图3(b)所示的仅CA场景下的复制数据传输，PDCP下面关联多个RLC实体可以关联于同一个MAC实体，例如MCG的MAC实体或者SCG的MAC实体。
终端设备在进行复制数据传输时，需要知道哪些PDCP实体被激活或者去激活，以及每个PDCP实体关联的多个RLC实体中哪些RLC实体当前可以用来传输复制数据。例如图3所示，终端设备不仅需要知道该PDCP实体被激活还是去激活，并且该PDCP实体被激活时终端设备也需要知道该PDCP实体关联的4个RLC实体中哪几个RLC实体用来传输复制数据。
本申请实施例提出了一种基于复制数据传输的方法，在多于两个副本的复制数据传输机制中，也能够实现有效的复制数据传输。
应理解，本申请实施例中所述的多于两个副本的复制数据传输机制，指的一个PDCP实体关联的RLC实体的数量可以大于2两个，但是，这并不意味着该PDCP PDU的复制的份数大于2。例如，该PDCP实体关联于4个RLC实体，但是复制两份PDCP PDU，两份PDCP PDU分别在这4个RLC实体中的其中两个RLC实体上进行传输，以下，称这两个RLC实体为用于传输复制数据的RLC实体。每次用于传输复制数据的RLC实体可以不同，当使用的RLC实体的信道状况发生变化，则可以使用这4个RLC实体中的其他的RLC实体传输复制数据。
图4是本申请实施例的用于复制数据传输的方法的流程交互图。该方法400可以由终端设备和网络设备执行。该终端设备例如可以为图1所示的终端设备130。该网络设备例如可以为图1所示的主基站110或辅基站120，或者也可以是核心网设备。如图4所示，所述用于复制数据传输的方法400包括以下步骤中的部分或全部。
在410中，网络设备向终端设备发送第一指示信息。
在420中，终端设备接收网络设备发送的该第一指示信息。
其中，该第一指示信息用于指示至少一个PDCP实体的复制数据传输功能激活或者去激活，和/或指示所述至少一个PDCP实体各自关联的多个RLC实体中用于传输复制数据的RLC实体。
所述至少一个PDCP实体中例如可以包括基于CA的复制数据传输的PDCP实体，和/或，基于DC的复制数据传输的PDCP实体。并且本申请实施例中的一个PDCP实体可以关联任意数量的RLC实体。
终端设备接收到该第一指示信息后，例如可以根据该第一指示信息对PDCP PDU进行复制数据的处理，并将处理后的PDCPPDU发送给网络设备。
可选地，该第一指示信息承载于媒质访问控制控制元素(MAC Control Element，MAC CE)。
例如图5所示，第一指示信息承载于MAC CE，所述用于复制数据传输的方法500包括510至540。其中：
在510中，网络设备向终端设备发送MAC CE。
在520中，终端设备的MAC实体接收并解析该MAC CE，得到第一指示信息。
在530中，终端设备的MAC实体向该终端设备的PDCP实体发送第一指示信息。
在540中，终端设备的PDCP实体接收第一指示信息。
网络设备需要激活/去激活一个或多个PDCP实体的复制数据传输功能时，会发送MAC CE给终端设备，该MAC CE中携带第一指示信息。终端设备的MAC实体接收到MAC CE后进行解读，得到第 一指示信息，即，得到激活/去激活的PDCP实体和/或用于传输复制数据的RLC实体的信息，MAC实体将解析后的这些信息指示给PDCP实体，从而PDCP实体基于这些信息对PDCP PDU进行处理。
当第一指示信息指示某个PDCP实体的复制数据传输功能激活时，该PDCP实体关联的多个RLC实体中的至少部分RLC实体可以用于传输复制数据。终端设备可以根据接收到的该第一指示信息，确定被激活/去激活的PDCP实体，并且进一步地，可以根据该第一指示信息确定被激活的PDCP实体所关联的哪些RLC实体当前可以用来传输的复制数据，以及PDCP PDU被复制成几份。
当每个PDCP实体仅关联两个RLC实体时，可以通过一个字节(byte)或一个八元组(octet)(以下均以字节为例)，来指示被激活/去激活的PDCP实体，其中该字节或八元组中的每个比特位对应于一个PDCP实体，每个比特位用来指示其对应的PDCP实体激活还是去激活复制数据传输功能。并且，无需指示哪个RLC实体用来传输复制数据，因为两个RLC实体均会用来传输复制数据。
但是，当PDCP实体关联更多的RLC实体，以及能够复制更多份的PDCP PDU时，不仅需要指示PDCP实体的激活/去激活，还要指示激活的PDCP实体所关联的RLC实体中哪些RLC实体用于传输复制数据。
本申请实施例中，通过第一指示信息来指示至少一个PDCP实体的复制数据传输功能的激活/去激活，以及指示该至少一个PDCP实体各自关联的多个RLC实体中用于传输复制数据的RLC实体，从而在多于两个副本的复制数据传输机制中，仍能够实现有效的复制数据传输。
为了使该第一指示信息能够指示上述内容，本申请实施例提供了第一指示信息的不同实现方式，下面结合图6至图16分别进行描述。
以下，也将PDCP实体称为无线承载，可以使用DRB ID来进行标识；以及将RLC实体称为逻辑信道，可以使用LCID来进行标识。
方式1
可选地，所述至少一个PDCP实体包括N个PDCP实体，N为正整数。
其中，所述第一指示信息包括M个字段，其中每个字段包括N个比特，所述N个PDCP实体分别对应于所述N个比特，同一PDCP实体关联的多个RLC实体分别对应于所述M个字段中位置相同的多个比特，其中每个比特用于指示所述每个比特对应的RLC实体是否用于传输复制数据，M为一个PDCP实体关联的RLC实体的最大数量。
该M个字段例如可以分别位于M个字节或分别位于M个八元组。
即，该第一指示信息包括M个字节，每个字节包括8比特，每个字节的8比特中的右起前N个比特分别对应于N个PDCP实体，1≤N≤8。
应理解，N的数量小于或等于配置了复制数据传输功能的PDCP实体总数。例如图2所示，假设有3个PDCP实体配置了复制数据传输功能，分别为PDCP实体1、PDCP实体2和PDCP实体3。从MCG的MAC实体接收的第一指示信息中可以包括PDCP实体1和PDCP实体2的激活/去激活信息和RLC实体的复制数据传输信息，从SCG的MAC实体接收的第一指示信息中可以包括PDCP实体2和PDCP实体3的激活/去激活信息和RLC实体的复制数据传输信息。也就是说，从MCG的MAC实体或SCG的MAC实体接收的第一指示信息不一定要指示全部的PDCP实体1、PDCP实体2和PDCP实体3，仅指示与自己相关联的PDCP实体的信息即可。
以图6(b)为例进行描述。该第一指示信息承载于MAC CE，该MAC CE的格式至少包括M个字节，假设M＝4，即PDCP关联的RLC实体的最大数量为4。假设N＝4，且各自对应的逻辑信道的标识分别为DRB ID0、DRB ID3、DRB ID5和DRB ID7。
其中，从右起第1列至第4列分别对应于DRB ID0、DRB ID3、DRB ID5和DRB ID7。第1列的第1-4行比特分别对应于DRB ID0关联的4个RLC实体；第2列的第1-4行比特分别对应于DRB ID3关联的4个RLC实体；第3列的第1-4行比特分别对应于DRB ID5关联的4个RLC实体；第4列的第1行和第2行比特分别对应于DRB ID7关联的2个RLC实体。这里，每个PDCP实体所关联的RLC实体的数量可以相同也可以不同，例如DRB ID0、DRB ID 3和DRBID 5对应的PDCP实体所关联RLC实体的数量均为4，而DRB ID7对应的PDCP实体所关联RLC实体的数量为2。每个小方格代表一个比特(bit)，每个比特的值用于表示该比特对应的RLC实体当前是否用于传输复制数据，以下，均假设比特值为0表示不用于传输复制数据，比特值为1表示用于传输复制数据。
首先需要获取PDCP实体的复制数据传输功能是否激活的信息，这里例如可以通过图6(a)所示的一个字节来指示，其中，该字节从右起的前4个比特分别对应于DRB ID0、DRB ID3、DRB ID5和DRB ID7，每个比特的值用于表示该比特对应的PDCP实体的复制数据传输功能是否激活。如图6(a)所示，该前4个比特均为1，表示DRB ID0、DRB ID3、DRB ID5和DRB ID7对应的PDCP实体的复制数据传输功能均被激活。
或者，也可以不使用图6(a)，而是通过图6(b)来获取被激活/去激活的DRB，当该DRB对应的比特列上的值均为0或者有一个比特的值为1，则表示该DRB的复制数据传输功能去激活；当该DRB对应的比特列上的值中，有至少两个比特的值为1，则表示该DRB的复制数据传输功能激活，并且这两个比特对应的RLC用于传输复制数据。
确定每个PDCP实体的复制数据传输功能激活/去激活后，确定激活的PDCP实体所关联的RLC实体中哪些RLC实体用于传输复制数据。如图6(b)所示，DRB ID0关联的PDCP实体所关联的前3个RLC实体用于传输复制数据，DRB ID3关联的PDCP实体所关联的前2个RLC实体用于传输复制数据，DRB ID5关联的PDCP实体所关联的4个RLC实体均用于传输复制数据，DRB ID7关联的PDCP实体所关联的2个RLC实体均用于传输复制数据。
通过图6(b)所示的方式，可以同时指示多个PDCP实体各自关联的多个RLC实体中用于传输复制数据的RLC实体。
应理解，图6(b)所示DRB ID0、DRB ID3、DRB ID5和DRB ID7是按照DRB ID的大小顺序例如升序，从右至左依次对应于4列比特。但本申请不限于此，DRB ID0、DRB ID3、DRB ID5和DRB ID7也可以分别对应于其他比特列。
另外，该第一指示信息指示的PDCP可以包括使用DC场景下的复制数据功能的PDCP和/或使用CA场景下的复制数据功能的PDCP。但对于使用CA场景下的复制数据功能的PDCP，其关联的MAC实体与传输该第一指示信息的MAC实体相同。
图6(b)中的比特行和比特列所表示的含义可以调换。可选地，所述至少一个PDCP实体包括N个PDCP实体，N为正整数。
其中，所述第一指示信息包括N个字段，所述N个PDCP实体分别对应于所述N个字段，其中每个字段包括多个比特，所述多个比特分别对应于所述每个字段对应的PDCP实体所关联的多个RLC实体，其中每个比特用于指示所述每个比特对应的RLC实体是否用于传输复制数据。
该N个字段例如可以分别位于N个字节或分别位于N个八元组。
以图7为例，第1行至第4行依次对应于DRB ID0、DRB ID3、DRB ID5和DRB ID7。从右至左，第1行前4个比特依次对应于DRB ID0关联的4个RLC实体；第2行前4个比特依次对应于DRB ID3关联的4个RLC实体；第3行前4个比特依次对应于DRB ID5关联的4个RLC实体；第4行前2个比特依次对应于DRB ID7关联的2个RLC实体。可以看出，DRB ID0关联的前3个RLC实体用于传输复制数据，DRB ID3关联的前3个RLC实体用于传输复制数据，DRB ID5关联的4个RLC实体均用于传输复制数据，DRB ID7关联的2个RLC实体均用于传输复制数据。
该第一指示信息指示的至少一个PDCP实体中可以包括基于CA的复制数据传输的PDCP实体，也可以包括基于DC的复制数据传输的PDCP实体。对于CA的复制数据传输，PDCP实体所关联的RLC实体均关联于同一个MAC实体，因此这些RLC实体的LCID是不同的。
以图8为例，假设DRB ID0关联的4个RLC实体对应的逻辑信道分别为LCID 1、LCID 4、LCID 5和LCID 8。LCID 1、LCID 4、LCID 5和LCID 8可以从上至下依次对应于第1列的4个比特。如图8所示，如果网络设备想激活DRB ID0的复制数据传输功能，且希望DRB ID0通过RLC实体1、RLC实体2和RLC实体3来传输复制数据，那么第一列的前3行置1，最后1行置0。
但是，对于DC的复制数据传输，PDCP实体所关联的RLC实体可能关联于不同CG的MAC实体，因此不同MAC实体RLC实体的LCID可能相同。这里所述的不同CG可以包括MCG和SCG，也可以包括多于两个CG。DC场景下的复制数据传输可以包括一个CG具有一个RLC实体的情况，也可以包括一个CG具有多个RLC实体的情况。
考虑到不同MAC实体对应的RLC实体的LCID可能相同，因此可以将MCG的RLC实体和SCG的RLC实体分别进行对应。本申请实施例提供两种方式将不同CG的RLC实体映射至这些RLC实体关联的PDCP实体所对应的比特行或比特列。
一种可能的实现方式为，所述N个PDCP实体中基于DC的复制数据传输的PDCP实体所关联的多个RLC实体，按照所属的小区组的顺序，依次对应于所述多个比特。
例如图9(a)所示，以图6(b)中的DRB ID5为例，DRB ID5关联的4个RLC实体分别对应LCID 1、LCID 4、LCID 1和LCID 8。DRB ID5对应的比特列中的4个比特，从上至下依次对应于LCID 1、LCID 4、LCID 1和LCID 8。其中，DRB ID5对应的比特列从上至下先对应MCG的LCID 1和LCID 4，对应完MCG的RLC实体后，紧接着对应SCG的LCID 1和LCID 8。尽管属于不同CG的RLC实体1和RLC实体3对应的LCID均为LCID 1，但是由于时按照先MCG后SCG的方式对应的，因此，DRB ID5对应的比特列中的第1行对应于MCG的RLC实体1，用于指示RLC实体1是否用于传输复制数据；第3行对应于SCG的RLC实体3，用于指示RLC实体3是否用于传输复制数据。
另一种可能的实现方式为，所述N个PDCP实体中基于DC的复制数据传输的PDCP实体所关联的多个RLC实体，基于各自所属的小区组，分别对应于所述多个比特中针对各个小区组划分的比特。
例如图9(b)所示，以图6(b)中的DRB ID5为例，DRB ID5关联的4个RLC实体分别对应LCID 1、LCID 4、LCID 1和LCID 8。其中，DRB ID5对应的比特列中的4个比特分为两组，第一组用于对应MCG的RLC实体，包括前2个比特；第二组用于对应SCG的RLC实体，包括后2个比特。MCG的LCID 1和LCID 4对应于该第一组内的前两个比特，SCG的LCID 1和LCID 8对应于该第二组内的前两个比特。尽管属于不同CG的RLC实体1和RLC实体3对应的LCID均为LCID 1，但是MCG的RLC实体1对应的比特位于第一组比特中，SCG的RLC实体3对应的比特位于第二组比特中，因此可以实现对不同CG的RLC实体分别进行指示。
使用该方式时，每个RLC实体应当基于各自所属的小区组，分别对应于针对该小区组划分的比特。即使第一组内的比特数量多于MCG的RLC实体的数量，第一组内多于的比特也不用于指示SCG的RLC实体，而是应当使用第二组内的比特来指示SCG的RLC实体。
进一步地，可选地，属于相同小区组的多个RLC实体按照所对应的逻辑信道标识的顺序，依次对应于多个比特。
例如图8所示，LCID 1、LCID 4、LCID 5和LCID 8从小至大，依次对应于第一列从前至后的第1个、第2个、第3个和第4个比特。
又例如图9(b)所示，MCG的LCID 1和LCID 4从小至大，依次对应于第一组中从前至后的第1个和第2个比特；SCG的LCID 1和LCID 8从小至大，依次对应于第二组中从前至后的第1个和第2个比特。
网络设备使用方式1向终端设备发送第一指示信息以控制复制数据传输时，可以通过一个MAC CE来激活/去激活多个DRB，并且网络设备可以通过该第一指示信息指示用于传输复制数据的RLC实体，从而控制激活/去激活的DRB的复制数据传输功能。在多于两个副本的复制数据传输机制下，实现了有效的复制数据传输。
方式2
可选地，所述至少一个PDCP实体包括一个PDCP实体。
其中，所述第一指示信息包括第一字段，所述第一字段用于指示所述PDCP实体，所述第一指示信息还包括第二字段和/或第三字段，所述第二字段用于指示所述PDCP实体的复制数据传输功能激活或者去激活，所述第三字段用于指示所述PDCP实体关联的多个RLC实体中用于传输复制数据的RLC实体。
该第一指示信息例如可以承载于MAC CE中。
该实施例中，网络设备是针对每个PDCP实体分别进行指示，该第一指示信息中包括一个PDCP实体的激活/去激活的信息，和/或该PDCP实体关联的用于传输复制数据的RLC实体的信息。相比于方式1，在方式2中，不需要额外定义PDCP实体与比特位之间的对应关系，而是根据每个字段所指示的内容直接获取PDCP实体的信息，并且，DC场景和CA场景下的PDCP复制数据传输也不需要分别定义，降低了实现复杂度。
但是，由于方式2中的第一指示信息每次仅指示一个PDCP实体的信息，因此，当需要指示多个PDCP实体时，本申请实施例提供以下两种方式：
一种实现方式是，通过多个第一指示信息分别对多个PDCP实体进行指示。其中，这多个第一指示信息可以承载于同一个MAC CE，也可以承载于不同的MAC CE。例如，通过发送多个MAC CE以分别指示多个PDCP实体激活和该PDCP实体关联的RLC实体中用于传输复制数据的RLC实体。
另一种实现方式是，将该PDCP实体关联于其他PDCP实体，所述其他PDCP实体与关联的该PDCP实体同时激活/去激活。
换句话说，可以设置多组PDCP实体，每组PDCP实体中的PDCP实体同时激活/去激活。当该组PDCP实体中有一个PDCP实体的复制数据传输功能被激活，则该组PDCP实体的复制数据传输功能均被激活；当该组PDCP实体中有一个PDCP实体的复制数据传输功能被去激活，则该组PDCP实体的复制数据传输功能均被去激活。网络设备可以通过指示一个PDCP实体的激活/去激活，来实现对多个PDCP实体的激活/去激活进行控制。
下面分别对该第一指示信息中的各个字段进行描述。
该第一指示信息包括第一字段，该第一字段用于指示PDCP实体，该第一字段例如可以为该PDCP实体对应的DRB ID。
该第一指示信息可能包括第二字段，所述第二字段用于指示所述PDCP实体的复制数据传输功能激活/去激活。
例如图10所示，该第一指示信息包括一个字节或一个八元组。该第一指示信息包括第一字段和第二字段。以下均假设DRB的总数为32，那么第一字段可以包括5比特，用于表示不同的DRB ID。该第二字段如图10所示的去激活/激活(Deactivation/Activation，D/A)字段，包括1比特，该比特用于表示第一字段指示的DRB ID的复制数据传输功能激活/去激活，比如为1时表示激活，为0表示去激活。终端设备接收该第一指示信息后，根据第一字段和第二字段就可以判断出激活/去激活的DRB。
该第一指示信息还可能包括第三字段，所述第三字段用于指示该PDCP实体关联的多个RLC实体中用于传输复制数据的RLC实体。
其中，该第三字段可以通过以下两种方式指示用于传输复制数据的RLC实体。
一种实现方式是，该第三字段包括多个比特，该多个比特分别与该PDCP实体关联的多个RLC实体对应，其中每个比特用于指示与每个比特对应的RLC实体是否用于传输复制数据。
例如，基于CA的复制数据传输的PDCP实体所关联的多个RLC实体，可以按照其对应的逻辑信道标识的顺序，依次对应于所述第三字段中的多个比特。类似于图8所示的映射方法。
又例如，基于DC的复制数据传输的PDCP实体所关联的多个RLC实体，可以按照所属的小区组的顺序，依次对应于所述第三字段中的多个比特。类似于图9(a)所示的映射方法。
又例如，基于DC的复制数据传输的PDCP实体所关联的多个RLC实体，可以基于各自所属的小区组，分别对应于所述第三字段中针对各个小区组划分的比特。类似于图9(b)所示的映射方法。
又例如，基于DC的复制数据传输的PDCP实体所关联的多个RLC实体中，属于相同小区组的RLC实体按照所对应的逻辑信道标识的顺序，依次对应于所述第三字段中的多个比特。
另一种实现方式是，该第三字段用于指示该PDCP实体关联的多个RLC实体中用于传输复制数据的RLC实体组，其中，同一RLC实体组中的RLC实体同时用于传输复制数据。
可选地，网络设备可以向终端设备发送第二指示信息。
相应地，所述终端设备接收网络设备发送的第二指示信息。
其中，所述第二指示信息用于指示多个RLC实体组，不同RLC实体组中的RLC实体部分或全部不同。所述第二指示信息例如可以承载于无线资源控制(Radio Resourse Control，RRC)信令。
该RRC信令中可以包括RLC实体组的ID，通过RRC信令中携带的RLC实体组标识来指示该RLC实体组。例如，将多个RLC实体组的信息以及该多个RLC实体组中用于传输复制数据的RLC实体组的ID携带于RRC信令的RLC承载配置(RLC-BearerConfig)信息单元(Information Element)中。该IE中包括两个域，其中一个域可以包括所划分的多个RLC实体组的信息，另一个域可以包括待使用的RLC实体组的标识信息。
或者，所述多个RLC实体组也可以是预配置在终端设备中的，例如协议事先约定的。
举例来说，PDCP实体关联于4个RLC实体，这4个RLC实体对应的LCID分别为LCID 1、LCID 4、LCID 5和LCID 8。这4个RLC实体被划分为4个RLC实体组。其中，RLC实体组1中包括的RLC实体对应的LCID为LCID 1、LCID 4；RLC实体组2中包括的RLC实体对应的LCID为LCID 1、LCID 5；RLC实体组3中包括的RLC实体对应的LCID为LCID 4、LCID 5；RLC实体组4中包括的RLC实体对应的LCID为LCID 5、LCID 8。假设第三字段包括2比特，如表一所示，根据第三字段的内容，就可以知道该哪个RLC实体组用于传输复制数据，同一个RLC实体组中的RLC实体共同传输复制数据。
表一
第三字段(2比特) RLC实体组ID
00 RLC实体组1(LCID 1、LCID 4)
01 RLC实体组2(LCID 1、LCID 5)
10 RLC实体组3(LCID 4、LCID 5)
11 RLC实体组4(LCID 5、LCID 8)
例如图11(a)和图11(b)所示，第一指示信息包括一个字节或一个八元组。该第一指示信息包括第一字段、第二字段和第三字段。假设当前的DRB的总数为32，那么第一字段可以包括5比特，用于指示不同的DRB ID。该第二字段可以为D/A字段，包括1比特，该比特用于表示第一字段指示的DRB ID的复制数据传输功能是否被激活，比如为1时表示激活，为0表示去激活。该第三字段指示用于传输复制数据的RLC实体对应的LCID或者RLC实体组的标识(简称为组标识)。终端设备接收该第一指示信息后，根据第一字段和第二字段可以确定该DRB ID的复制数据传输功能是否激活，若该DRB ID的复制数据传输功能激活，则根据第三字段就可以判断用于传输复制数据的RLC实体。其中，图11(a)中，第三字段包括1比特，可以用于指示两个RLC实体组，或者用于指示该DRB ID关联的 2个RLC实体。图11(b)中，第三字段包括2比特，可以用于指示四个RLC实体组，或者用于指示该DRB ID关联的4个RLC实体。
应理解，本申请实施例中，当第二字段指示PDCP实体的复制数据传输功能激活时，第三字段用于指示该PDCP实体关联的RLC实体中哪些RLC实体用于传输复制数据；而当第二字段指示该DRB ID的复制数据传输功能去激活，由于无需再指示用于传输复制数据的RLC实体，因此，可选地，第三字段可以指示用于传输非复制数据的RLC实体，而其他RLC实体不进行数据传输，或者第三字段也可以空余或者指示其他信息，这里不做限定。当然，用于传输非复制数据的RLC实体也可以是预配置的，例如可以预配置MCG的某个RLC实体，该RLC实体在其关联的PDCP实体的复制数据传输功能去激活时用来传输非复制数据。
上面分别对第一字段、第二字段和第三字段进行了描述，但是，第一指示信息并不一定同时包括第二字段和第三字段。本申请实施例中存在以下四种情况，下面分别描述。
情况1
所述第一指示信息包括第一字段、第二字段和第三字段。
其中，第一字段可以用于指示PDCP实体，第二字段用于指示该PDCP的复制数据传输功能的激活/去激活，该第三字段用于指示传输复制数据的RLC实体。
例如图11(a)和图11(b)所示的第一指示信息的结构，第一字段包括DRB ID；第二字段为D/A字段，用于指示该DRB ID的复制数据传输功能是否激活；第三字段用于指示传输复制数据的RLC实体对应的LCID或者RLC实体组的ID。
情况2
所述第一指示信息包括第一字段和第三字段。
这时，由于该第一指示信息不包括第二字段，那么，可选地，该第三字段还可以用于指示所述PDCP实体的复制数据传输功能激活/去激活。
可选地，该第三字段为特定数值例如0时，该第三字段用于指示该PDCP实体的复制数据传输去激活；和/或，该第三字段为除该特定数值之外的其他数值时，该第三字段用于指示该PDCP实体的复制数据传输功能激活。
例如图12(a)和图12(b)所示，第一指示信息包括第一字段和第三字段。假设当前的DRB的总数为32，那么第一字段可以包括5比特，用于指示不同的DRB ID。第三字段可以包括3比特，用于指示该DRB ID的复制数据传输功能激活/去激活，以及用于指示传输复制数据的RLC实体。如图12(a)所示，该第三字段为000时，可以用来表示该DRB ID的复制数据传输功能去激活；该第三字段为其他值时，可以用于指示该DRB ID的复制数据传输功能激活，并且第三字段的值可以指示用于传输复制数据的RLC实体对应的LCID或者RLC实体组，例如图12(b)所示，该第三字段的值为011时，可以确定该DRB ID的复制数据传输功能激活，并且该第三字段表示011对应的RLC实体组中的RLC实体用于传输复制数据。图12(a)和图12(b)中的第三字段包括3比特，但并不限于此，第三字段也可以包括1比特、2比特等。
应理解，该第一指示信息可以包括一个字节，也可以包括两个字节。例如，当所述第一指示信息包括两个字节时，所述第三字段与所述第一字段位于所述两个字节中的不同字节。上述图10、图11(a)、图11(b)、图12(a)和图12(b)均为第一指示信息包括一个字节的情况。这时，由于第三字段的比特数量有限，当PDCP实体关联的RLC实体的数量较多时，该第三字段通常用来指示传输复制数据的RLC实体组，而无法单独指示每个RLC是否用于传输复制数据。
为了更灵活地对RLC实体进行指示，并简化配置RLC实体组的过程，本申请实施例中，第三字段可以与第一字段不属于同一字节。图13(a)和图13(b)中所示为第一指示信息包括两个字节的情况。其中，在图13(a)中，第一字段和第二字段位于第一个字节，第三字段位于第二个字节。在图13(b)中，第一指示信息不包括第二字段，第一字段位于第一个字节，第三字段位于第二个字节。这样，第三字段最多可以包括8个比特，可以指示最多8个RLC实体。当第一字段指示的DRB ID的复制数据传输功能激活时，该第三字段可以指示某个具体的RLC实体是否用于传输复制数据。
该第三字段的每个比特可以对应于一个LCID，第一字段指示的PDCP实体所关联的多个RLC实体对应的LCID可以按照从小到大的顺序，从第三字段的第1个比特开始对应。当该PDCP实体为DC场景下的PDCP实体，例如图14(a)所示，其关联的RLC实体对应的LCID可以按照MCG至SCG的顺序，从右至左依次对应于第三字段中的比特；或者，例如图14(b)所示，其关联的RLC实体根据该RLC实体所属的CG，对应于针对该CG划分的比特。例如图14(c)所示，当该PDCP实体为CA场景下的PDCP实体，其关联的RLC实体对应的LCID可以按照LCID的大小顺序例如升序，从右至左依次对应于第三字段中的比特。
情况3
所述第一指示信息包括第一字段和第二字段。
可选地，若所述第二字段指示所述PDCP实体的复制数据传输功能激活，所述第一指示信息包括所述第三字段；和/或，
若所述第二字段指示所述PDCP实体的复制数据传输功能去激活，所述第一指示信息不包括所述第三字段。
根据前面的描述，该第一指示信息中的第一字段和第三字段可以位于不同的字节，这样就引入了新的比特开销。但是，当PDCP实体的复制数据传输功能去激活时，可以不需要指示用于传输复制数据的RLC实体，因此第三字段可以省略，以节省比特开销。而当PDCP实体的复制数据传输功能激活时，才通过第三字段来指示用于传输复制数据的RLC实体。
这时，可以设置两种类型的MAC CE，两种MAC CE的格式不同，可以通过MAC CE的子包头(MAC subheader)来区分。第一指示信息可以承载于这两种类型的MAC CE中。这里例如可以通过MAC子包头中的LCID来区分两种不同类型的MAC CE。例如图15(a)所示，其中一种类型的MAC CE用于指示PDCP实体的复制数据传输功能激活，该类型的MAC CE包括2字节，第1个字节中包括第一字段，用于指示PDCP；第2个字节中包括第三字段，用于指示传输复制数据的RLC实体。例如图15(b)所示，另一种类型的MAC CE用于指示PDCP实体的复制数据传输功能去激活，该类型的MAC CE可以仅包括1字节。
可选地，用于指示PDCP实体的复制数据传输功能去激活的MAC CE的格式可以复用目前协议中已有的MAC CE格式例如图6(a)所述的MAC CE格式。
由于可以通过MAC CE的格式来区分该BRB ID的复制数据传输功能是否激活，因此图15(a)和图15(b)中的第二字段也可以省略。
换句话说，该第二字段指示PDCP实体的复制数据传输功能激活，所述第一指示信息包括所述第三字段，该第二字段指示PDCP实体的复制数据传输功能去激活，所述第一指示信息不包括所述第三字段。终端设备根据接收到的MAC CE的子包头可以判断MAC CE的格式，根据MAC CE的格式可以确定该PDCP实体的复制数据传输功能是否激活，并在激活时根据第三字段确定哪些RLC实体用于传输复制数据。
可选地，当第一指示信息仅包括第一字段和第二字段时，也可以通过例如RRC信令等动态地指示该PDCP实体关联的多个RLC实体中用于传输复制数据的RLC实体或者RLC实体组。
情况4
所述第一指示信息包括所述第一字段、所述第二字段和所述第三字段。情况4作为情况1的一种特殊情况，可选地，对于终端设备，所述方法还包括：
若所述第二字段指示所述PDCP实体的复制数据传输功能激活，所述终端设备读取所述第三字段；和/或，
若所述第二字段指示所述PDCP实体的复制数据传输功能去激活，所述终端设备不读取所述第三字段。
在情况3中，PDCP实体激活和去激活时第一指示信息所包括的内容不同，即MAC CE的格式在激活和去激活的时候是不同的。而在情况4中，第一指示信息包括第三字段，MAC CE的格式始终是相同的，终端设备接收到第一指示信息后，基于对第一字段和第二字段的读取，来判断是否读取第三字段。
例如图16所示，如果第二字段指示PDCP实体的复制数据传输功能去激活，即D/A＝0，则终端设备不用读取第三字段；第二字段指示PDCP实体的复制数据传输功能激活，即D/A＝1，终端设备才读取第三字段，以获知哪些RLC实体用于传输复制数据。在方式4中，该第三字段始终携带于第一指示信息中，终端设备可以基于终端设备的实现，确定是否读取该第三字段。
综上，在方式1中，是通过比特图(bitmap)的方式指示PDCP实体的复制数据传输功能激活/去激活以及用于传输复制数据的RLC实体，可以实现对多个PDCP实体和多个RLC实体的同时指示。
在方式2中，是单独对PDCP实体的复制数据传输功能激活/去激活进行指示，进一步地，还可以对该PDCP实体关联的用于传输复制数据的RLC实体进行指示，相比于方式1减少了MAC CE的开销。并且，通过动态变化第一指示信息的格式以及配置RLC实体组等方式，进一步减小MAC CE的开销。并且，终端设备读取第一指示信息的方式可以更灵活，提高了数据处理效率。
本申请实施例对第一字段、第二字段和第三字段在字节中的位置以及各字段包括的比特数不做任何限定，上述附图仅为示例。
需要说明的是，在不冲突的前提下，本申请描述的各个实施例和/或各个实施例中的技术特征可以 任意的相互组合，组合之后得到的技术方案也应落入本申请的保护范围。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
上文中详细描述了根据本申请实施例的用于复制数据传输的方法，下面将结合图17至图21，描述根据本申请实施例的装置，方法实施例所描述的技术特征适用于以下装置实施例。
图17是根据本申请实施例的终端设备1700的示意性框图。如图17所示，该终端设备1700包括接收单元1710和处理单元1720。其中：
接收单元1710，用于接收第一指示信息；
处理单元1720，用于根据所述接收单元1710接收的所述第一指示信息，对PDCP PDU进行处理。
其中，所述第一指示信息用于指示至少一个分组数据汇聚协议PDCP实体的复制数据传输功能激活或者去激活，和/或指示所述至少一个PDCP实体各自关联的多个RLC实体中用于传输复制数据的RLC实体。
可选地，所述至少一个PDCP实体中包括：基于载波聚合CA的复制数据传输的PDCP实体；和/或，基于双连接DC的复制数据传输的PDCP实体。
可选地，所述至少一个PDCP实体包括N个PDCP实体。所述第一指示信息包括M个字段，其中每个字段包括N个比特，所述N个PDCP实体分别对应于所述N个比特，同一PDCP实体关联的多个RLC实体分别对应于所述M个字段中位置相同的多个比特，其中每个比特用于指示所述每个比特对应的RLC实体是否用于传输复制数据，M、N为正整数，M为一个PDCP实体关联的RLC实体的最大数量。
可选地，所述M个字段分别位于M个字节。
可选地，所述至少一个PDCP实体包括N个PDCP实体。所述第一指示信息包括N个字段，所述N个PDCP实体分别对应于所述N个字段，其中每个字段包括多个比特，所述多个比特分别对应于所述每个字段对应的PDCP实体所关联的多个RLC实体，其中每个比特用于指示所述每个比特对应的RLC实体是否用于传输复制数据，N为正整数。
可选地，所述N个字段分别位于N个字节。
可选地，所述N个PDCP实体中基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，按照所属的小区组的顺序，依次对应于所述多个比特。
可选地，所述N个PDCP实体中基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，基于各自所属的小区组，分别对应于所述多个比特中针对各个小区组划分的比特。
可选地，属于相同小区组的多个RLC实体按照所对应的逻辑信道标识的顺序，依次对应于多个比特。
可选地，所述至少一个PDCP实体包括一个PDCP实体。所述第一指示信息包括第一字段，所述第一字段用于指示所述PDCP实体，所述第一指示信息还包括第二字段和/或第三字段，所述第二字段用于指示所述PDCP实体的复制数据传输功能激活或者去激活，所述第三字段用于指示所述PDCP实体关联的多个RLC实体中用于传输复制数据的RLC实体。
可选地，所述PDCP实体关联于其他PDCP实体，所述其他PDCP实体与所述PDCP实体同时激活或者去激活。
可选地，所述第一指示信息不包括所述第二字段，所述第三字段还用于指示所述PDCP实体的复制数据传输功能激活或者去激活。
可选地，所述第三字段还用于指示所述PDCP实体的复制数据传输功能激活或者去激活，包括：所述第三字段为特定数值时，所述第三字段用于指示所述PDCP实体的复制数据传输功能去激活；所述第三字段为除所述特定数值之外的其他数值时，所述第三字段用于指示所述PDCP实体的复制数据传输功能激活。
可选地，所述第一指示信息包括所述第二字段。若所述第二字段指示所述PDCP实体的复制数据传输功能激活，所述第一指示信息包括所述第三字段，若所述第二字段指示所述PDCP实体的复制数据传输功能去激活，所述第一指示信息不包括所述第三字段。
可选地，所述第一指示信息包括所述第二字段和所述第三字段，所述处理单元还用于：若所述第二字段指示所述PDCP实体的复制数据传输功能激活，所述终端设备读取所述第三字段；和/或，若所述第二字段指示所述PDCP实体的复制数据传输功能去激活，所述终端设备不读取所述第三字段。
可选地，所述第一指示信息包括一个字节。
可选地，所述第一指示信息包括两个字节，所述第三字段与所述第一字段位于所述两个字节中的不同字节。
可选地，所述第一指示信息承载于MAC CE。
可选地，所述第三字段中的多个比特分别与所述PDCP实体关联的所述多个RLC实体对应，其中每个比特用于指示与所述每个比特对应的RLC实体是否用于传输复制数据。
可选地，基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，按照所属的小区组的顺序，依次对应于所述第三字段中的多个比特。
可选地，基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，基于各自所属的小区组，分别对应于所述第三字段中针对各个小区组划分的比特。
可选地，属于相同小区组的RLC实体按照所对应的逻辑信道标识的顺序，依次对应于所述第三字段中的多个比特。
可选地，所述第三字段用于指示所述PDCP实体关联的多个RLC实体中用于传输复制数据的RLC实体，包括：所述第三字段用于指示所述多个RLC实体中用于传输复制数据的RLC实体组，其中，同一RLC实体组中的RLC实体同时用于传输复制数据。
可选地，所述接收单元1710还用于：接收网络设备发送的第二指示信息，所述第二指示信息用于指示多个RLC实体组，不同RLC实体组中的RLC实体部分或全部不同。
可选地，所述第二指示信息承载于RRC信令。
应理解，该终端设备1700可以执行上述方法400中由终端设备执行的相应操作，为了简洁，在此不再赘述。
图18是根据本申请实施例的终端设备1800的示意性框图。如图18所示，该终端设备1800包括处理单元1810和发送单元1820。其中：
处理单元1810，用于生成第一指示信息；
处理单元1820，用于发送所述处理单元1810生成的所述第一指示信息。
其中，所述第一指示信息用于指示至少一个分组数据汇聚协议PDCP实体的复制数据传输功能激活或者去激活，和/或指示所述至少一个PDCP实体各自关联的多个RLC实体中用于传输复制数据的RLC实体。
可选地，所述至少一个PDCP实体中包括：基于载波聚合CA的复制数据传输的PDCP实体；和/或，基于双连接DC的复制数据传输的PDCP实体。
可选地，所述至少一个PDCP实体包括N个PDCP实体。所述第一指示信息包括M个字段，其中每个字段包括N个比特，所述N个PDCP实体分别对应于所述N个比特，同一PDCP实体关联的多个RLC实体分别对应于所述M个字段中位置相同的多个比特，其中每个比特用于指示所述每个比特对应的RLC实体是否用于传输复制数据，M、N为正整数，M为一个PDCP实体关联的RLC实体的最大数量。
可选地，所述M个字段分别位于M个字节。
可选地，所述至少一个PDCP实体包括N个PDCP实体。所述第一指示信息包括N个字段，所述N个PDCP实体分别对应于所述N个字段，其中每个字段包括多个比特，所述多个比特分别对应于所述每个字段对应的PDCP实体所关联的多个RLC实体，其中每个比特用于指示所述每个比特对应的RLC实体是否用于传输复制数据，N为正整数。
可选地，所述N个字段分别位于N个字节。
可选地，所述N个PDCP实体中基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，按照所属的小区组的顺序，依次对应于所述多个比特。
可选地，所述N个PDCP实体中基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，基于各自所属的小区组，分别对应于所述多个比特中针对各个小区组划分的比特。
可选地，属于相同小区组的多个RLC实体按照所对应的逻辑信道标识的顺序，依次对应于多个比特。
可选地，所述至少一个PDCP实体包括一个PDCP实体。所述第一指示信息包括第一字段，所述第一字段用于指示所述PDCP实体，所述第一指示信息还包括第二字段和/或第三字段，所述第二字段用于指示所述PDCP实体的复制数据传输功能激活或者去激活，所述第三字段用于指示所述PDCP实体关联的多个RLC实体中用于传输复制数据的RLC实体。
可选地，所述PDCP实体关联于其他PDCP实体，所述其他PDCP实体与所述PDCP实体同时激活或者去激活。
可选地，所述第一指示信息不包括所述第二字段，所述第三字段还用于指示所述PDCP实体的复制数据传输功能激活或者去激活。
可选地，所述第三字段还用于指示所述PDCP实体的复制数据传输功能激活或者去激活，包括：所 述第三字段为特定数值时，所述第三字段用于指示所述PDCP实体的复制数据传输功能去激活；所述第三字段为除所述特定数值之外的其他数值时，所述第三字段用于指示所述PDCP实体的复制数据传输功能激活。
可选地，所述第一指示信息包括所述第二字段。若所述第二字段指示所述PDCP实体的复制数据传输功能激活，所述第一指示信息包括所述第三字段，若所述第二字段指示所述PDCP实体的复制数据传输功能去激活，所述第一指示信息不包括所述第三字段。
可选地，所述第一指示信息包括所述第二字段和所述第三字段，所述处理单元还用于：若所述第二字段指示所述PDCP实体的复制数据传输功能激活，所述终端设备读取所述第三字段；和/或，若所述第二字段指示所述PDCP实体的复制数据传输功能去激活，所述终端设备不读取所述第三字段。
可选地，所述第一指示信息包括一个字节。
可选地，所述第一指示信息包括两个字节，所述第三字段与所述第一字段位于所述两个字节中的不同字节。
可选地，所述第一指示信息承载于MAC CE。
可选地，所述第三字段中的多个比特分别与所述PDCP实体关联的所述多个RLC实体对应，其中每个比特用于指示与所述每个比特对应的RLC实体是否用于传输复制数据。
可选地，基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，按照所属的小区组的顺序，依次对应于所述第三字段中的多个比特。
可选地，基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，基于各自所属的小区组，分别对应于所述第三字段中针对各个小区组划分的比特。
可选地，属于相同小区组的RLC实体按照所对应的逻辑信道标识的顺序，依次对应于所述第三字段中的多个比特。
可选地，所述第三字段用于指示所述PDCP实体关联的多个RLC实体中用于传输复制数据的RLC实体，包括：所述第三字段用于指示所述多个RLC实体中用于传输复制数据的RLC实体组，其中，同一RLC实体组中的RLC实体同时用于传输复制数据。
可选地，所述发送单元1820还用于：向终端设备发送第二指示信息，所述第二指示信息用于指示多个RLC实体组，不同RLC实体组中的RLC实体部分或全部不同。
可选地，所述第二指示信息承载于RRC信令。
应理解，该网络设备1800可以执行上述方法400中由网络设备执行的相应操作，为了简洁，在此不再赘述。
图19是本申请实施例提供的一种通信设备1900示意性结构图。图19所示的通信设备1900包括处理器1910，处理器1910可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图19所示，通信设备1900还可以包括存储器1920。其中，处理器1910可以从存储器1920中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1920可以是独立于处理器1910的一个单独的器件，也可以集成在处理器1910中。
可选地，如图19所示，通信设备1900还可以包括收发器1930，处理器1910可以控制该收发器1930与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器1930可以包括发射机和接收机。收发器1930还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备1900具体可为本申请实施例的终端设备，并且该通信设备1900可以实现本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备1900具体可为本申请实施例的网络设备，并且该通信设备1900可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
图20是本申请实施例的芯片的示意性结构图。图20所示的芯片2000包括处理器2010，处理器2010可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图20所示，芯片2000还可以包括存储器2020。其中，处理器2010可以从存储器2020中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器2020可以是独立于处理器2010的一个单独的器件，也可以集成在处理器2010中。
可选地，该芯片2000还可以包括输入接口2030。其中，处理器2010可以控制该输入接口2030与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片2000还可以包括输出接口2040。其中，处理器2010可以控制该输出接口2040与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的终端设备，并且该芯片可以实现本申请实施例的各个方 法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片、系统芯片、芯片系统或片上系统芯片等。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
图21是根据本申请实施例的通信系统2100的示意性框图。如图21所示，该通信系统2100包括网络设备2110和终端设备2120。
网络设备2110用于：向终端设备2120发送第一指示信息。
终端设备2120用于：接收网络设备2110发送的所述第一指示信息。
其中，所述第一指示信息用于指示至少一个PDCP实体的复制数据传输功能激活或者去激活，和/或指示所述至少一个PDCP实体各自关联的多个RLC实体中用于传输复制数据的RLC实体。
其中，网络设备2110可以用于实现上述方法500中由网络设备实现的相应的功能，以及该网络设备2110的组成可以如图18中的网络设备1800所示，为了简洁，在此不再赘述。
其中，终端设备2120可以用于实现上述方法500中由终端设备实现的相应的功能，以及该终端设备2120的组成可以如图17中的终端设备1700所示，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。可选的，该计算机可读存储介质可应用于本申请实施例中的终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。可选地，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。可选的，该计算机程序产品可应用于本申请实施例中的终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。可选地，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。可选的，该计算机程序可应用于本申请实施例中的终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。可选地，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
还应理解，在本发明实施例中，“与A相应(对应)的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，该单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (58)

  1. 一种用于复制数据传输的方法，其特征在于，所述方法包括：
    发送第一指示信息；或者，
    接收所述第一指示信息；
    其中，所述第一指示信息用于指示至少一个分组数据汇聚协议PDCP实体的复制数据传输功能激活或者去激活，和/或指示所述至少一个PDCP实体各自关联的多个RLC实体中用于传输复制数据的RLC实体。
  2. 根据权利要求1所述的方法，其特征在于，所述至少一个PDCP实体中包括：
    基于载波聚合CA的复制数据传输的PDCP实体；和/或，
    基于双连接DC的复制数据传输的PDCP实体。
  3. 根据权利要求1或2所述的方法，其特征在于，所述至少一个PDCP实体包括N个PDCP实体，
    所述第一指示信息包括M个字段，其中每个字段包括N个比特，所述N个PDCP实体分别对应于所述N个比特，同一PDCP实体关联的多个RLC实体分别对应于所述M个字段中位置相同的多个比特，其中每个比特用于指示所述每个比特对应的RLC实体是否用于传输复制数据，M、N为正整数，M为一个PDCP实体关联的RLC实体的最大数量。
  4. 根据权利要求3所述的方法，其特征在于，所述M个字段分别位于M个字节。
  5. 根据权利要求1或2所述的方法，其特征在于，所述至少一个PDCP实体包括N个PDCP实体，
    所述第一指示信息包括N个字段，所述N个PDCP实体分别对应于所述N个字段，其中每个字段包括多个比特，所述多个比特分别对应于所述每个字段对应的PDCP实体所关联的多个RLC实体，其中每个比特用于指示所述每个比特对应的RLC实体是否用于传输复制数据，N为正整数。
  6. 根据权利要求5所述的方法，其特征在于，所述N个字段分别位于N个字节。
  7. 根据权利要求3至6中任一项所述的方法，其特征在于，所述N个PDCP实体中基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，按照所属的小区组的顺序，依次对应于所述多个比特。
  8. 根据权利要求3至6中任一项所述的方法，其特征在于，所述N个PDCP实体中基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，基于各自所属的小区组，分别对应于所述多个比特中针对各个小区组划分的比特。
  9. 根据权利要求3至8中任一项所述的方法，其特征在于，属于相同小区组的多个RLC实体按照所对应的逻辑信道标识的顺序，依次对应于多个比特。
  10. 根据权利要求1或2所述的方法，其特征在于，所述至少一个PDCP实体包括一个PDCP实体，
    所述第一指示信息包括第一字段，所述第一字段用于指示所述PDCP实体，所述第一指示信息还包括第二字段和/或第三字段，所述第二字段用于指示所述PDCP实体的复制数据传输功能激活或者去激活，所述第三字段用于指示所述PDCP实体关联的多个RLC实体中用于传输复制数据的RLC实体。
  11. 根据权利要求10所述的方法，其特征在于，所述PDCP实体关联于其他PDCP实体，所述其他PDCP实体与所述PDCP实体同时激活或者去激活。
  12. 根据权利要求10或11所述的方法，其特征在于，所述第一指示信息不包括所述第二字段，所述第三字段还用于指示所述PDCP实体的复制数据传输功能激活或者去激活。
  13. 根据权利要求12所述的方法，其特征在于，所述第三字段还用于指示所述PDCP实体的复制数据传输功能激活或者去激活，包括：
    所述第三字段为特定数值时，所述第三字段用于指示所述PDCP实体的复制数据传输功能去激活；
    所述第三字段为除所述特定数值之外的其他数值时，所述第三字段用于指示所述PDCP实体的复制数据传输功能激活。
  14. 根据权利要求10或11所述的方法，其特征在于，所述第一指示信息包括所述第二字段，
    若所述第二字段指示所述PDCP实体的复制数据传输功能激活，所述第一指示信息包括所述第三字段，
    若所述第二字段指示所述PDCP实体的复制数据传输功能去激活，所述第一指示信息不包括所述第三字段。
  15. 根据权利要求10或11所述的方法，其特征在于，所述方法由终端设备执行，所述第一指示信息包括所述第二字段和所述第三字段，所述方法还包括：
    若所述第二字段指示所述PDCP实体的复制数据传输功能激活，所述终端设备读取所述第三字段；和/或，
    若所述第二字段指示所述PDCP实体的复制数据传输功能去激活，所述终端设备不读取所述第三字 段。
  16. 根据权利要求10至15中任一项所述的方法，其特征在于，所述第一指示信息包括一个字节。
  17. 根据权利要求10至15中任一项所述的方法，其特征在于，所述第一指示信息包括两个字节，所述第三字段与所述第一字段位于所述两个字节中的不同字节。
  18. 根据权利要求1至17中任一项所述的方法，其特征在于，所述第一指示信息承载于媒质访问控制控制元素MAC CE。
  19. 根据权利要求10至18中任一项所述的方法，其特征在于，所述第三字段中的多个比特分别与所述PDCP实体关联的所述多个RLC实体对应，其中每个比特用于指示与所述每个比特对应的RLC实体是否用于传输复制数据。
  20. 根据权利要求10至19中任一项所述的方法，其特征在于，基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，按照所属的小区组的顺序，依次对应于所述第三字段中的多个比特。
  21. 根据权利要求10至19中任一项所述的方法，其特征在于，基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，基于各自所属的小区组，分别对应于所述第三字段中针对各个小区组划分的比特。
  22. 根据权利要求20或21所述的方法，其特征在于，属于相同小区组的RLC实体按照所对应的逻辑信道标识的顺序，依次对应于所述第三字段中的多个比特。
  23. 根据权利要求10至18中任一项所述的方法，其特征在于，所述第三字段用于指示所述PDCP实体关联的多个RLC实体中用于传输复制数据的RLC实体，包括：
    所述第三字段用于指示所述多个RLC实体中用于传输复制数据的RLC实体组，其中，同一RLC实体组中的RLC实体同时用于传输复制数据。
  24. 根据权利要求23所述的方法，其特征在于，所述方法由网络设备执行，所述方法还包括：
    所述网络设备向终端设备发送第二指示信息，所述第二指示信息用于指示多个RLC实体组，不同RLC实体组中的RLC实体部分或全部不同。
  25. 根据权利要求23所述的方法，其特征在于，所述方法由终端设备执行，所述方法还包括：
    所述终端设备接收网络设备发送的第二指示信息，所述第二指示信息用于指示多个RLC实体组，不同RLC实体组中的RLC实体部分或全部不同。
  26. 根据权利要求24或25所述的方法，其特征在于，所述第二指示信息承载于无线资源控制RRC信令。
  27. 一种用于复制数据传输的通信设备，其特征在于，所述通信设备包括：
    发送单元，用于发送第一指示信息；
    或者，接收单元，用于接收所述第一指示信息；
    其中，所述第一指示信息用于指示至少一个分组数据汇聚协议PDCP实体的复制数据传输功能激活或者去激活，和/或指示所述至少一个PDCP实体各自关联的多个RLC实体中用于传输复制数据的RLC实体。
  28. 根据权利要求27所述的通信设备，其特征在于，所述至少一个PDCP实体中包括：
    基于载波聚合CA的复制数据传输的PDCP实体；和/或，
    基于双连接DC的复制数据传输的PDCP实体。
  29. 根据权利要求27或28所述的通信设备，其特征在于，所述至少一个PDCP实体包括N个PDCP实体，
    所述第一指示信息包括M个字段，其中每个字段包括N个比特，所述N个PDCP实体分别对应于所述N个比特，同一PDCP实体关联的多个RLC实体分别对应于所述M个字段中位置相同的多个比特，其中每个比特用于指示所述每个比特对应的RLC实体是否用于传输复制数据，M、N为正整数，M为一个PDCP实体关联的RLC实体的最大数量。
  30. 根据权利要求29所述的通信设备，其特征在于，所述M个字段分别位于M个字节。
  31. 根据权利要求27或28所述的通信设备，其特征在于，所述至少一个PDCP实体包括N个PDCP实体，
    所述第一指示信息包括N个字段，所述N个PDCP实体分别对应于所述N个字段，其中每个字段包括多个比特，所述多个比特分别对应于所述每个字段对应的PDCP实体所关联的多个RLC实体，其中每个比特用于指示所述每个比特对应的RLC实体是否用于传输复制数据，N为正整数。
  32. 根据权利要求31所述的通信设备，其特征在于，所述N个字段分别位于N个字节。
  33. 根据权利要求29至32中任一项所述的通信设备，其特征在于，所述N个PDCP实体中基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，按照所属的小区组的顺序，依次对应于 所述多个比特。
  34. 根据权利要求29至32中任一项所述的通信设备，其特征在于，所述N个PDCP实体中基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，基于各自所属的小区组，分别对应于所述多个比特中针对各个小区组划分的比特。
  35. 根据权利要求29至34中任一项所述的通信设备，其特征在于，属于相同小区组的多个RLC实体按照所对应的逻辑信道标识的顺序，依次对应于多个比特。
  36. 根据权利要求27或28所述的通信设备，其特征在于，所述至少一个PDCP实体包括一个PDCP实体，
    所述第一指示信息包括第一字段，所述第一字段用于指示所述PDCP实体，所述第一指示信息还包括第二字段和/或第三字段，所述第二字段用于指示所述PDCP实体的复制数据传输功能激活或者去激活，所述第三字段用于指示所述PDCP实体关联的多个RLC实体中用于传输复制数据的RLC实体。
  37. 根据权利要求36所述的通信设备，其特征在于，所述PDCP实体关联于其他PDCP实体，所述其他PDCP实体与所述PDCP实体同时激活或者去激活。
  38. 根据权利要求36或37所述的通信设备，其特征在于，所述第一指示信息不包括所述第二字段，所述第三字段还用于指示所述PDCP实体的复制数据传输激活或者去激活。
  39. 根据权利要求38所述的通信设备，其特征在于，所述第三字段还用于指示所述PDCP实体的复制数据传输功能激活或者去激活，包括：
    所述第三字段为特定数值时，所述第三字段用于指示所述PDCP实体的复制数据传输功能去激活；
    所述第三字段为除所述特定数值之外的其他数值时，所述第三字段用于指示所述PDCP实体的复制数据传输功能激活。
  40. 根据权利要求36或37所述的通信设备，其特征在于，所述第一指示信息包括所述第二字段，
    若所述第二字段指示所述PDCP实体的复制数据传输功能激活，所述第一指示信息包括所述第三字段，
    若所述第二字段指示所述PDCP实体的复制数据传输功能去激活，所述第一指示信息不包括所述第三字段。
  41. 根据权利要求36或37所述的通信设备，其特征在于，所述通信设备由终端设备执行，所述第一指示信息包括所述第二字段和所述第三字段，所述通信设备还包括：
    若所述第二字段指示所述PDCP实体的复制数据传输功能激活，所述终端设备读取所述第三字段；和/或，
    若所述第二字段指示所述PDCP实体的复制数据传输功能去激活，所述终端设备不读取所述第三字段。
  42. 根据权利要求36至41中任一项所述的通信设备，其特征在于，所述第一指示信息包括一个字节。
  43. 根据权利要求36至41中任一项所述的通信设备，其特征在于，所述第一指示信息包括两个字节，所述第三字段与所述第一字段位于所述两个字节中的不同字节。
  44. 根据权利要求27至43中任一项所述的通信设备，其特征在于，所述第一指示信息承载于媒质访问控制控制元素MAC CE。
  45. 根据权利要求36至44中任一项所述的通信设备，其特征在于，所述第三字段中的多个比特分别与所述PDCP实体关联的所述多个RLC实体对应，其中每个比特用于指示与所述每个比特对应的RLC实体是否用于传输复制数据。
  46. 根据权利要求36至45中任一项所述的通信设备，其特征在于，基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，按照所属的小区组的顺序，依次对应于所述第三字段中的多个比特。
  47. 根据权利要求36至45中任一项所述的通信设备，其特征在于，基于双连接的复制数据传输的PDCP实体所关联的多个RLC实体，基于各自所属的小区组，分别对应于所述第三字段中针对各个小区组划分的比特。
  48. 根据权利要求46或47所述的通信设备，其特征在于，属于相同小区组的RLC实体按照所对应的逻辑信道标识的顺序，依次对应于所述第三字段中的多个比特。
  49. 根据权利要求36至44中任一项所述的通信设备，其特征在于，所述第三字段用于指示所述PDCP实体关联的多个RLC实体中用于传输复制数据的RLC实体，包括：
    所述第三字段用于指示所述多个RLC实体中用于传输复制数据的RLC实体组，其中，同一RLC实体组中的RLC实体同时用于传输复制数据。
  50. 根据权利要求49所述的通信设备，其特征在于，所述通信设备为网络设备，所述网络设备包括所述发送单元，所述发送单元用于：
    向终端设备发送第二指示信息，所述第二指示信息用于指示多个RLC实体组，不同RLC实体组中的RLC实体部分或全部不同。
  51. 根据权利要求49所述的通信设备，其特征在于，所述通信设备为终端设备，所述终端设备包括所述接收单元，所述接收单元用于：
    接收网络设备发送的第二指示信息，所述第二指示信息用于指示多个RLC实体组，不同RLC实体组中的RLC实体部分或全部不同。
  52. 根据权利要求50或51所述的通信设备，其特征在于，所述第二指示信息承载于无线资源控制RRC信令。
  53. 一种通信设备，其特征在于，所述终端设备包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行权利要求1至26中任一项所述的方法。
  54. 一种芯片，其特征在于，所述芯片包括处理器，所述处理器用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行权利要求1至26中任一项所述的方法。
  55. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行权利要求1至26中任一项所述的方法。
  56. 一种计算机程序产品，其特征在于，包括计算机程序指令，所述计算机程序指令使得计算机执行权利要求1至26中任一项所述的方法。
  57. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行权利要求1至26中任一项所述的方法。
  58. 一种通信系统，其特征在于，包括如权利要求27至52中任意一项所述的通信设备。
PCT/CN2019/072059 2019-01-16 2019-01-16 用于复制数据传输的方法和设备 Ceased WO2020147056A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
PCT/CN2019/072059 WO2020147056A1 (zh) 2019-01-16 2019-01-16 用于复制数据传输的方法和设备
CN202110968809.3A CN113691359B (zh) 2019-01-16 2019-01-16 用于复制数据传输的方法和设备
EP19910091.8A EP3911006B1 (en) 2019-01-16 2019-01-16 Method and device used for duplicate data transmission
CN201980087029.9A CN113261337A (zh) 2019-01-16 2019-01-16 用于复制数据传输的方法和设备
US17/377,980 US12004012B2 (en) 2019-01-16 2021-07-16 Method and device used for duplicate data transmission

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/072059 WO2020147056A1 (zh) 2019-01-16 2019-01-16 用于复制数据传输的方法和设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/377,980 Continuation US12004012B2 (en) 2019-01-16 2021-07-16 Method and device used for duplicate data transmission

Publications (1)

Publication Number Publication Date
WO2020147056A1 true WO2020147056A1 (zh) 2020-07-23

Family

ID=71614207

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/072059 Ceased WO2020147056A1 (zh) 2019-01-16 2019-01-16 用于复制数据传输的方法和设备

Country Status (4)

Country Link
US (1) US12004012B2 (zh)
EP (1) EP3911006B1 (zh)
CN (2) CN113261337A (zh)
WO (1) WO2020147056A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023071599A1 (zh) * 2021-10-29 2023-05-04 大唐移动通信设备有限公司 数据传输方法、装置、设备及存储介质
WO2023186162A1 (zh) * 2022-04-01 2023-10-05 上海朗帛通信技术有限公司 一种被用于无线通信的方法和设备
WO2025051171A1 (zh) * 2023-09-08 2025-03-13 上海朗帛通信技术有限公司 一种被用于无线通信的通信节点中的方法和装置

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113366882B (zh) * 2019-01-28 2024-12-06 中兴通讯股份有限公司 动态数据包汇聚协议配置
WO2020159427A1 (en) * 2019-02-01 2020-08-06 Telefonaktiebolaget Lm Ericsson (Publ) First communication device, second communication device and methods performed therein for controlling transmission
CN111757548B (zh) * 2019-03-29 2022-05-24 华为技术有限公司 通信方法和通信装置
CN113079585B (zh) * 2020-01-03 2023-02-21 大唐移动通信设备有限公司 一种信息处理方法及终端
EP4252446A1 (en) 2020-11-25 2023-10-04 InterDigital Patent Holdings, Inc. Enhancement to redundant transmission in 5g network

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108282823A (zh) * 2017-01-06 2018-07-13 株式会社Kt 用于控制冗余数据发送的方法和设备
WO2018170891A1 (en) * 2017-03-24 2018-09-27 Nokia Technologies Oy Handling of pdcp duplication and data recovery in new radio access technology
CN109151903A (zh) * 2017-06-16 2019-01-04 三星电子株式会社 用于在下一代移动通信系统中处理分组的方法和装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3242514B1 (en) * 2014-12-30 2019-07-03 Huawei Technologies Co., Ltd. Transmission method and device for control information
WO2017132925A1 (zh) * 2016-02-04 2017-08-10 华为技术有限公司 物联网的传输优化方法、装置和设备
EP3446426B1 (en) * 2016-04-19 2024-05-29 Nokia Technologies Oy Split bearer dual/multiple connectivity retransmission diversity
KR102170530B1 (ko) * 2017-03-16 2020-10-28 주식회사 케이티 제어 메시지 중복수신 방법 및 장치
CN107342851B (zh) 2017-06-15 2020-05-26 电信科学技术研究院 一种重复传输的配置及重复传输方法及装置
EP3642993B1 (en) * 2017-06-22 2025-01-15 Sharp Kabushiki Kaisha Device and method for packet data convergence protocol packet data unit duplication

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108282823A (zh) * 2017-01-06 2018-07-13 株式会社Kt 用于控制冗余数据发送的方法和设备
WO2018170891A1 (en) * 2017-03-24 2018-09-27 Nokia Technologies Oy Handling of pdcp duplication and data recovery in new radio access technology
CN109151903A (zh) * 2017-06-16 2019-01-04 三星电子株式会社 用于在下一代移动通信系统中处理分组的方法和装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CATT: "3GPP TSG-RAN WG2 Meeting #102 R2-1809023", INTRODUCTION OF PDCP DUPLICATION, 21 May 2018 (2018-05-21), XP051452850 *
See also references of EP3911006A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023071599A1 (zh) * 2021-10-29 2023-05-04 大唐移动通信设备有限公司 数据传输方法、装置、设备及存储介质
WO2023186162A1 (zh) * 2022-04-01 2023-10-05 上海朗帛通信技术有限公司 一种被用于无线通信的方法和设备
WO2025051171A1 (zh) * 2023-09-08 2025-03-13 上海朗帛通信技术有限公司 一种被用于无线通信的通信节点中的方法和装置

Also Published As

Publication number Publication date
US12004012B2 (en) 2024-06-04
EP3911006A1 (en) 2021-11-17
CN113691359B (zh) 2023-04-18
EP3911006A4 (en) 2022-01-12
CN113691359A (zh) 2021-11-23
EP3911006B1 (en) 2023-05-10
CN113261337A (zh) 2021-08-13
US20210345178A1 (en) 2021-11-04

Similar Documents

Publication Publication Date Title
CN113691359B (zh) 用于复制数据传输的方法和设备
CN113518416B (zh) 上报功率回退信息的方法及装置、终端设备、网络设备
CN113766571B (zh) 数据传输的方法和通信设备
EP4102892B1 (en) Relay communication method and related device
CN113595704B (zh) 一种信息处理方法、网络设备、终端设备
CN113194551B (zh) 数据复制传输配置方法、装置、芯片及计算机程序
TW201906443A (zh) 用於傳輸數據的方法、終端設備和網絡設備
WO2021232297A1 (zh) 上报功率回退信息的方法及装置、网络设备、终端设备
CN115835198B (zh) 一种控制安全功能的方法及装置、网络设备、终端设备
US12193018B2 (en) Method and device based on duplicate data transmission
WO2021016778A1 (zh) 一种传输资源选择方法、网络设备、用户设备
CN113794544B (zh) 无线通信方法和终端设备
CN114793363A (zh) 资源指示方法、终端设备和网络设备
WO2020147054A1 (zh) 一种数据复制传输的指示方法、终端设备及网络设备
WO2021169732A1 (zh) 一种切换方法及通信装置
US20230217444A1 (en) Data forwarding for user equipment with data transmission
WO2020087294A1 (zh) 基于复制数据的传输方法和设备
CN112640509B (zh) 一种数据复制传输的处理方法、终端设备及网络设备
WO2023000176A1 (zh) 一种控制scg状态的方法及装置、终端设备、网络设备
US20240349389A1 (en) Rrc message configuration method, apparatus and system
CN114845345B (zh) 无线通信的方法、终端设备和网络设备
WO2025031148A1 (zh) 一种通信方法、通信装置及通信系统
WO2023044610A1 (zh) 一种识别mac ce类型的方法及装置、终端设备、网络设备
WO2023000146A1 (zh) 一种配置载波的方法及装置、终端设备、网络设备
CN117597882A (zh) 一种激活trs的方法及装置、终端设备、网络设备

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019910091

Country of ref document: EP

Effective date: 20210810