WO2021233445A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2021233445A1
WO2021233445A1 PCT/CN2021/095326 CN2021095326W WO2021233445A1 WO 2021233445 A1 WO2021233445 A1 WO 2021233445A1 CN 2021095326 W CN2021095326 W CN 2021095326W WO 2021233445 A1 WO2021233445 A1 WO 2021233445A1
Authority
WO
WIPO (PCT)
Prior art keywords
indication information
rlc entity
network device
primary
communication device
Prior art date
Application number
PCT/CN2021/095326
Other languages
English (en)
French (fr)
Inventor
屈凯旸
徐小英
范强
韩锋
娄崇
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21809596.6A priority Critical patent/EP4145900A4/en
Priority to AU2021273886A priority patent/AU2021273886A1/en
Publication of WO2021233445A1 publication Critical patent/WO2021233445A1/zh
Priority to US18/056,938 priority patent/US20230077500A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the embodiments of the present application relate to the field of wireless communication, and in particular to methods and devices for data transmission.
  • the fifth generation (5G) mobile communication system has a significant feature that is the increase in ultra-reliable and low-latency communication.
  • communications, URLLC URLLC
  • URLLC's business types include many types, and typical use cases include industrial control, unmanned driving, remote surgery, and smart grids.
  • a typical requirement is that the reliability of sending 32 bytes of data within 1 millisecond (millisecond, ms) must reach 99.999%. It should be pointed out that the above performance indicators are just examples. Different URLLC services may have different requirements for reliability. For example, in some extremely demanding industrial control application scenarios, the transmission success probability of URLLC service data needs to be within 0.25 ms. Reached 99.9999999%.
  • This application provides a method and device for data transmission, which are used to improve the reliability of data transmission.
  • the present application provides a data transmission method, and the execution subject of the method is the auxiliary network device or a module in the auxiliary network device.
  • the description is made by taking the auxiliary network device as the execution subject as an example.
  • the secondary network device receives first indication information from the primary network device, the first indication information indicates the primary radio link control RLC entity of the first radio bearer RB, and the first RB is associated with one primary RLC entity and at most 3 secondary RLC entities
  • the secondary network device sends a 3-bit length of second indication information to the terminal device, the second indication information indicates the status of each secondary RLC entity associated with the first RB, and the different secondary RLC entities associated with the first RB correspond to the Different bits in 3 bits.
  • the secondary network device receives the indication information from the primary network device, and the secondary network device can determine the The main RLC entity associated with the radio bearer can thus accurately indicate which RLC entities need to be activated and deactivated by the terminal device, which improves the reliability of data transmission.
  • the secondary network device receives configuration information from the primary network device, the configuration information indicates M RLC entities associated with the first RB in the secondary network device, and M is 1, 2. Or 3.
  • the foregoing first indication information indicates the primary radio link control RLC entity of the first radio bearer RB, which specifically includes: the first indication information indicates whether there is a second RLC entity among the M RLC entities.
  • the primary RLC entity of an RB; or, the first indication information indicates the number of secondary RLC entities of the first RB among the M RLC entities; or, the first indication information indicates the RLC associated with the first RB in the primary network device Whether the primary RLC entity of the first RB exists in the entity; or the first indication information indicates the initial state of the X secondary RLC entities among the M RLC entities, and X is 0, 1, 2, or 3.
  • the secondary network device receives third indication information from the primary network device, where the third indication information indicates the number of RLC entities associated with the first RB in the primary network device. Or, the third indication information indicates the identities of all RLC entities associated with the first RB in the primary network device; or, the third indication information indicates the identity of the secondary RLC entities associated with the first RB in the primary network device Number; or, the third indication information indicates the identities of all secondary RLC entities associated with the first RB in the primary network device.
  • the foregoing first indication information indicates the primary radio link control RLC entity of the first radio bearer RB, which specifically includes: the first indication information indicates that the first RB in the foregoing primary network device Whether each associated RLC entity is the primary RLC entity of the first RB.
  • the foregoing first indication information indicates the primary radio link control RLC entity of the first radio bearer RB, which specifically includes: the first indication information indicates that the first RB in the foregoing primary network device The number of associated RLC entities, and the number of secondary RLC entities associated with the first RB in the primary network device.
  • the foregoing first indication information further indicates the primary RLC entity of the first RB, which specifically includes: the first indication information indicates that each of the first RBs associated with the first RB in the foregoing primary network device The initial state of the secondary RLC entity, and the number of RLC entities associated with the first RB in the primary network device.
  • the secondary network device when the primary RLC entity associated with the first RB is located in the above-mentioned secondary network device, the secondary network device sends fourth indication information to the primary network device, and the fourth indication information indicates the first The identity of the primary RLC entity associated with the RB.
  • the present application provides a data transmission method, where the execution subject of the method is a main network device or a module in the main network device.
  • the main network device is taken as the execution subject as an example for description.
  • the primary network device sends first indication information to the secondary network device, where the first indication information indicates the primary radio link control RLC entity of the first radio bearer RB, and the first RB is associated with one primary RLC entity and at most 3 secondary RLC entities;
  • the main network device sends fifth indication information to the terminal device, where the fifth indication information indicates the main RLC entity of the first RB.
  • the primary network device sends configuration information to the secondary network device, the configuration information indicates the M RLC entities associated with the first RB in the secondary network device, and M is 1, 2, or 3.
  • the foregoing first indication information indicates the primary radio link control RLC entity of the first radio bearer RB, which specifically includes: the first indication information indicates whether there is a second RLC entity among the M RLC entities.
  • the primary RLC entity of an RB; or, the first indication information indicates the number of secondary RLC entities of the first RB among the M RLC entities; or, the first indication information indicates the RLC associated with the first RB in the primary network device Whether the primary RLC entity of the first RB exists in the entity; or the first indication information indicates the initial state of the X secondary RLC entities among the M RLC entities, and X is 0, 1, 2, or 3.
  • the primary network device sends third indication information to the secondary network device, where the third indication information indicates the number of RLC entities associated with the first RB in the primary network device; or , The third indication information indicates the identities of all RLC entities associated with the first RB in the primary network device; or, the third indication information indicates the number of secondary RLC entities associated with the first RB in the primary network device; Or, the third indication information indicates the identities of all secondary RLC entities associated with the first RB in the primary network device.
  • the above-mentioned first indication information indicates the primary radio link control RLC entity of the first radio bearer RB, which specifically includes: the first indication information indicates that the first RB in the above-mentioned primary network device Whether each associated RLC entity is the primary RLC entity of the first RB.
  • the above-mentioned first indication information indicates the primary radio link control RLC entity of the first radio bearer RB, which specifically includes: the first indication information indicates that the first RB in the above-mentioned primary network device The number of associated RLC entities, and the number of secondary RLC entities associated with the first RB in the primary network device.
  • the above-mentioned first indication information further indicates the primary RLC entity of the first RB, which specifically includes: the first indication information indicates each associated with the first RB in the above-mentioned primary network device The initial state of the secondary RLC entity, and the number of RLC entities associated with the first RB in the primary network device.
  • the primary network device when the primary RLC entity associated with the first RB is located in the above-mentioned secondary network device, the primary network device receives fourth indication information from the secondary network device, and the fourth indication information indicates the first The identity of the primary RLC entity associated with an RB.
  • a communication device which includes functional modules for implementing the foregoing first aspect and any possible implementation of the first aspect.
  • a communication device which includes functional modules for implementing the foregoing second aspect and any possible implementation of the second aspect.
  • a communication device including a processor and an interface circuit, the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or send signals from the processor
  • the processor is used to implement the foregoing first aspect and the method in any possible implementation manner of the first aspect through a logic circuit or executing code instructions.
  • a communication device including a processor and an interface circuit
  • the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or to transfer signals from the processor Sent to other communication devices other than the communication device
  • the processor is used to implement the foregoing second aspect and the method in any possible implementation manner of the second aspect through a logic circuit or executing code instructions.
  • a computer-readable storage medium stores a computer program or instruction.
  • the computer program or instruction When executed, it realizes any of the foregoing first aspect and any of the first aspects.
  • a computer-readable storage medium stores a computer program or instruction.
  • the computer program or instruction is executed, any possibility of the aforementioned second aspect and the second aspect is realized.
  • the method in the implementation is provided.
  • a computer program product containing instructions is provided, and when the instructions are executed, the foregoing first aspect and the method in any possible implementation manner of the first aspect are implemented.
  • a computer program product containing instructions is provided, when the instructions are executed, the foregoing second aspect and the method in any possible implementation manner of the second aspect are implemented.
  • a computer program includes code or instructions, and when the code or instruction is executed, the foregoing first aspect and the method in any possible implementation manner of the first aspect are implemented.
  • a computer program includes code or instructions, and when the code or instructions are executed, the foregoing second aspect and the method in any possible implementation manner of the second aspect are implemented.
  • a chip system in a thirteenth aspect, includes a processor and may also include a memory for implementing at least one of the methods described in the first and second aspects.
  • the chip system can be composed of chips, or it can include chips and other discrete devices.
  • a communication system in a fourteenth aspect, includes the device described in the third aspect or the fifth aspect (such as a secondary network device) and the device described in the fourth aspect or the sixth aspect (such as a main network device). ).
  • FIG. 1a is a schematic diagram of the architecture of a communication system applied in an embodiment of this application.
  • FIG. 1b is a schematic diagram of the separation of CU and DU applied in the embodiment of this application;
  • Figure 2a shows the network architecture involved in implementing PDCP duplication in a DC scenario
  • Figure 2b shows the network architecture involved in implementing PDCP duplication in the CA scenario
  • Figure 3 is a schematic diagram of activating and deactivating PDCP duplication in a CA scenario
  • Figure 4a and Figure 4b show the network architecture involved in implementing PDCP duplication in the DC+CA scenario
  • 4c and 4d are exemplary diagrams of the second indication information
  • Figure 4e and Figure 4f show the network architecture involved in implementing PDCP duplication in the DC+CA scenario
  • 5 to 8 are schematic diagrams of the corresponding processes of the data transmission method provided by the embodiments of this application.
  • Figures 9 and 10 are schematic structural diagrams of possible communication devices provided by embodiments of this application.
  • 5G long term evolution
  • 5G 5th generation
  • WiFi Wireless Fidelity
  • future communication systems e.g., GSM
  • NR new radio
  • eMBB enhanced mobile broadband
  • ultra-reliable low-latency communication ultra -reliable low-latency communication
  • URLLC ultra-reliable low-latency communication
  • MTC machine type communication
  • mMTC massive machine type communications
  • D2D device-to-device
  • V2X vehicle to everything
  • V2V vehicle to vehicle
  • IoT internet of things
  • Communication between communication devices may include: communication between a network device and a terminal device, communication between a network device and a network device, and/or communication between a terminal device and a terminal device.
  • the term “communication” can also be described as "transmission", “information transmission”, or “signal transmission” and so on. Transmission can include sending and/or receiving.
  • the technical solution is described by taking the communication between the network device and the terminal device as an example. Those skilled in the art can also use the technical solution for communication between other scheduling entities and subordinate entities, such as macro base stations and micro base stations.
  • Air interface resources include one or more of the following resources: time domain resources, frequency domain resources, code resources, and space resources.
  • the multiple types may be two, three, four, or more types, which are not limited in the embodiments of the present application.
  • the communication between the network device and the terminal device includes: the network device sends a downlink signal/information to the terminal device, and/or the terminal device sends an uplink signal/information to the network device.
  • "/" can indicate that the associated objects are in an "or” relationship.
  • A/B can indicate A or B; and "and/or” can be used to describe that there are three types of associated objects.
  • the relationship, for example, A and/or B can mean that: A alone exists, A and B exist at the same time, and B exists alone. Among them, A and B can be singular or plural.
  • words such as “first” and “second” may be used to distinguish technical features with the same or similar functions. The words “first” and “second” do not limit the quantity and order of execution, and the words “first” and “second” do not limit the difference.
  • words such as “exemplary” or “for example” are used to indicate examples, illustrations, or illustrations, and embodiments or design solutions described as “exemplary” or “for example” should not be interpreted as It is more preferable or advantageous than other embodiments or design solutions.
  • the use of words such as “exemplary” or “for example” is intended to present related concepts in a specific manner to facilitate understanding.
  • FIG. 1a is a schematic diagram of the architecture of a communication system to which an embodiment of the present application can be applied.
  • the communication system includes a terminal device 110 and two network devices (a secondary network device 120 and a main network device 130 in FIG. 1a).
  • Fig. 1a is only a schematic diagram, and the embodiment of the present application does not limit the number of network devices and terminal devices included in the communication system.
  • the terminal equipment involved in the embodiments of the present application may also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, and so on.
  • Terminal equipment can be mobile phones, tablet computers, computers with wireless transceiver functions, virtual reality terminal equipment, augmented reality terminal equipment, wireless terminals in industrial control, wireless terminals in unmanned driving, wireless terminals in remote surgery, and smart grids Wireless terminals in the Internet, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and so on.
  • the embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal device.
  • the device used to implement the function of the terminal device may be a terminal device; it may also be a device capable of supporting the terminal device to implement the function, such as a chip system.
  • the device may be installed in the terminal device or connected to the terminal device. The equipment is matched and used.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the device used to implement the functions of the terminal device is a terminal device as an example to describe the technical solutions provided by the embodiments of the present application.
  • the network equipment involved in the embodiments of this application is an access device that a terminal device wirelessly accesses to the mobile communication system. It can be a base station, an evolved NodeB (eNodeB), or a transmission reception point. TRP), the next generation NodeB (gNB) in the 5G mobile communication system, the base station in the future mobile communication system or the access node in the WiFi system, etc.; it can also be a module or unit that completes part of the functions of the base station.
  • eNodeB evolved NodeB
  • TRP transmission reception point
  • gNB next generation NodeB
  • control plane protocol layer structure can include RRC layer, packet data convergence protocol (packet data convergence protocol, PDCP) layer, radio link control (radio link control) , RLC layer, media access control (MAC) layer and physical layer and other protocol layer functions;
  • user plane protocol layer structure can include PDCP layer, RLC layer, MAC layer and physical layer and other protocol layer functions,
  • the PDCP layer may also include a service data adaptation protocol (service data adaptation protocol, SDAP) layer.
  • SDAP service data adaptation protocol
  • the network equipment may include a centralized unit (CU) and a distributed unit (DU).
  • the interface between CU and DU can be called F1 interface, as shown in Figure 1b.
  • the control panel (CP) interface may be F1-C
  • the user panel (UP) interface may be F1-U.
  • the CU and the DU can be divided according to the protocol layers of the wireless network. For example, the functions of the PDCP layer and above are set in the CU, and the functions of the protocol layers below the PDCP layer (such as the RLC layer and the MAC layer, etc.) are set in the DU.
  • the signaling generated by the CU can be sent to the terminal device through the DU, or the signaling generated by the terminal device can be sent to the CU through the DU.
  • the DU may directly pass the protocol layer encapsulation without analyzing the signaling and transparently transmit it to the terminal device or CU.
  • the embodiment of the present application does not limit the specific technology and specific device form adopted by the network device.
  • the device used to implement the function of the network device may be a network device; it may also be a device capable of supporting the network device to implement the function, such as a chip system.
  • the device may be installed in the network device or connected to the network.
  • the equipment is matched and used.
  • the device used to implement the functions of the network equipment is the network equipment as an example to describe the technical solutions provided by the embodiments of the present application.
  • Network equipment and terminal equipment can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; they can be deployed on water; or, they can be deployed on airplanes, balloons, or satellites in the air.
  • the embodiments of the present application do not limit the application scenarios of network equipment and terminal equipment.
  • Network equipment and terminal equipment can communicate through licensed spectrum, communicate through unlicensed spectrum, or communicate through licensed spectrum and unlicensed spectrum.
  • Network equipment and terminal equipment can communicate through a frequency spectrum below 6 gigahertz (gigahertz, GHz), communicate through a frequency spectrum above 6 GHz, or communicate using a frequency spectrum below 6 GHz and a frequency spectrum above 6 GHz.
  • the embodiment of the present application does not limit the spectrum resource used between the network device and the terminal device.
  • dual connectivity refers to: a terminal device is connected to two network devices at the same time.
  • the two network devices connected by the terminal device can be base stations under the same wireless access technology.
  • both are the base stations in the LTE communication system or both are the base stations in the 5G mobile communication system, or the two base stations connected by the terminal device can also be Base stations under different wireless access technologies, for example, one is a base station in an LTE communication system, and the other is a base station in a 5G mobile communication system.
  • carrier aggregation refers to: aggregating multiple component carriers (CC) together to provide services for one terminal device to achieve larger transmission bandwidth, thereby improving uplink and downlink Transmission rate.
  • the terminal device and the network device may establish at least one radio bearer (RB) to transmit data.
  • Radio bearers can be divided into a signaling radio bearer (SRB) used to transmit signaling data and a data radio bearer (DRB) used to transmit service data.
  • a set of functional entities corresponding to the same radio bearer includes a packet data convergence protocol (PDCP) entity, at least one radio link control (RLC) entity corresponding to the PDCP entity, and at least one RLC entity Corresponding at least one medium access control (MAC) entity.
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • the PDCP entity is located at the PDCP layer
  • the RLC entity is located at the RLC layer
  • the MAC entity is located at the MAC layer.
  • the copy transmission of the PDCP layer refers to: copy the data packet carried by the radio into multiple identical packets (that is, copy the packet) at the PDCP layer, and then submit the multiple data packets to the multiple Two different RLC entities perform transmission. Specifically, each RLC entity transmits data packets to the MAC layer through a logical channel (logical channel, LCH) corresponding to the RLC entity.
  • LCH logical channel
  • the copy transmission of the PDCP layer is different from the usual retransmission (retransmission). Retransmission refers to the transmission of the same data packet after the transmission fails, while the copy transmission of the PDCP layer copies a data packet into Multiple data packets are transmitted through multiple logical channels.
  • the replication transmission of the PDCP layer may also be referred to as "PDCP duplication", "PDCP duplication", and "PDCP layer duplication".
  • PDCP duplication includes PDCP duplication in a DC scenario (also referred to as: DC duplication) and PDCP duplication in a CA scenario (also referred to as: CA duplication).
  • DC duplication also referred to as: DC duplication
  • CA duplication also referred to as: CA duplication
  • Figure 2a shows a network architecture that implements PDCP duplication in a DC scenario.
  • the DC scenario involves the main network equipment and the auxiliary network equipment.
  • For one RB there is one PDCP entity, one RLC entity and one MAC entity in the primary network device, and one RLC entity and one MAC entity in the secondary network device.
  • For this RB there is one PDCP entity, two RLC entities, and two MAC entities in the terminal device.
  • the main network device may also have an SDAP entity above the PDCP entity
  • the terminal device may also have an SDAP entity above the PDCP entity.
  • a terminal device is connected to two network devices at the same time, that is, the primary network device and the secondary network device.
  • the PDCP duplication function is configured for a certain RB, then two identical data packets that have been replicated at the PDCP layer will be It is transmitted to two different RLC entities, and transmitted to two different MAC entities through different logical channels, and finally two MAC protocol data units (protocol data unit, PDU) are respectively scheduled in two different MAC entities Transmission on cell resources.
  • the PDCP layer in the primary network device will transmit the duplicated two data packets to two different RLC entities. These two RLC entities are located in the primary network device and the secondary network device.
  • the RLC entity in the network device transmits the received data packet to the MAC entity in the primary network device, and the RLC entity in the secondary network device transmits the received data packet to the MAC entity in the secondary network device.
  • the respective cell resources transmit data packets, and for a terminal device, two RLC entities and two MAC entities are located in the terminal device.
  • a terminal device there may be two cell groups that provide services for terminal devices, namely, a master cell group (MCG) and a secondary cell group (SCG).
  • MCG master cell group
  • SCG secondary cell group
  • the primary cell group It is managed and configured by the main network equipment
  • the secondary cell group is managed and configured by the auxiliary network equipment.
  • Figure 2b shows a network architecture that implements PDCP duplication in a CA scenario.
  • a terminal device is connected to a network device, and at least two carriers (or cells) under the same network device serve the terminal device.
  • For one RB there is one PDCP entity, two RLC entities, and one MAC entity in the network device.
  • two RLC entities and one MAC entity in the terminal equipment corresponding to one PDCP entity, two RLC entities and one MAC entity in the terminal equipment.
  • a network device configures the PDCP duplication function for a radio bearer, two identical data packets that have been replicated at the PDCP layer will be transmitted to two different RLC entities, and the two RLC entities will be transmitted to them through different logical channels.
  • the same MAC entity When a network device configures the PDCP duplication function for a radio bearer, two identical data packets that have been replicated at the PDCP layer will be transmitted to two different RLC entities, and the two RLC entities will be transmitted to them through different
  • parameter A a parameter for the logical channel, for example, called parameter A.
  • the value of parameter A is used to indicate different cells, so as to ensure that the two same data packets can eventually form two MAC PDUs for transmission on different cells. Thereby improving reliability.
  • the network device When the network device configures the PDCP duplication function for a radio bearer through radio resource control (radio resource control, RRC) signaling, it can indicate whether the initial state of the PDCP duplication function of the radio bearer is activated or deactivated. Further, the network device may also configure the activation/deactivation of the PDCP duplication function of the radio bearer through a MAC control element (MAC control element, MAC CE).
  • RRC radio resource control
  • the PDCP layer replicates data packets and transmits them through two logical channels;
  • the DC duplication configured for a radio bearer is After the duplication function is deactivated, it falls back to the DC split bearer, that is, the terminal device can send different data packets to the primary network device and the secondary network device through the two logical channels on the terminal device side, or, The terminal device can receive different data packets from the main network device and the auxiliary network device through the two logical channels on the terminal device side.
  • CA duplication is limited to one radio bearer to transmit data packets that are copied at the PDCP layer through two logical channels (also commonly known as two-leg duplication transmission).
  • one of the legs can also be configured as a primary leg, for example, the leg where the logical channel 1 is located is the primary leg.
  • the primary leg can refer to the primary RLC entity, or the logical channel associated with the primary RLC entity, also referred to as the primary logical channel;
  • the secondary leg can refer to the secondary RLC entity or the logic associated with the secondary RLC entity Channel, also called secondary logical channel.
  • the CA duplication function When the CA duplication function is activated, as shown in Figure 3, data from logical channel 1 can only be transmitted on cell 1 or cell 2 (logical channel 1 is associated with cell 1 and cell 2), and data from logical channel 2 can only be transmitted on cell 1 or cell 2. Transmit on cell 3 (logical channel 2 is associated with cell 3); when the CA duplication function is deactivated, the terminal device can only transmit data to the network device through the main logical channel 1. At this time, in order to increase the transmission capacity, the cell binding relationship configured for logical channel 1 is no longer applicable, that is, the data in logical channel 1 can be transmitted on all the cells that have established wireless connections with the terminal equipment.
  • the DC scenario shown in Figure 2a and the CA scenario shown in Figure 2b are both PDCP duplication of two logical channels.
  • PDCP duplication with more than two logical channels is introduced.
  • three or four logical channels may be used to transmit data packets that are duplicated at the PDCP layer.
  • Figure 4a shows a network architecture that implements PDCP duplication in a DC+CA scenario.
  • a terminal device is connected to the main network device and the auxiliary network device.
  • Two carriers (or cells) under the main network device serve the terminal device
  • two carriers (or cells) under the secondary network device serve the terminal device.
  • One RB corresponds to one PDCP entity, two RLC entities and one MAC entity in the primary network device, and corresponds to two RLC entities and one MAC entity in the secondary network device.
  • RLC1 and RLC2 are transmitted to the same MAC entity through logical channel 1 and logical channel 2, respectively, which is MAC1;
  • RLC3 and RLC4 are transmitted to the same MAC entity through logical channel 3 and logical channel 4, respectively, which is MAC2.
  • the network device configures a primary logical channel and a shunt auxiliary logical channel for the radio bearer, where the main logical channel is located in the main network device, the shunt auxiliary logical channel is located in the auxiliary network device, or the main logical channel is located in the auxiliary network device, The offload secondary logical channel is located in the main network device.
  • the primary network device or the secondary network device configures the PDCP duplication function for a radio bearer through RRC signaling, it can indicate whether the initial state of the PDCP duplication function of the radio bearer is activated or deactivated. Further, the primary network device or the secondary network device may also indicate the activation/deactivation status of the RLC entity associated with the radio bearer to the terminal device through the MAC CE. The terminal device can perform the PDCP layer copy transmission with the network device through the activated RLC entity.
  • the terminal device stops the PDCP layer replication transmission, and the terminal device can use the terminal device's primary logical channel and offload auxiliary logical channel to respectively distribute to the network device and offload where the primary logical channel is located.
  • the network device where the auxiliary logical channel is located sends different data packets, or the terminal device can receive data from the network device where the main logical channel is located and the network device where the branch auxiliary logical channel is located through the main logical channel and the shunt auxiliary logical channel of the terminal device. Different packets.
  • the embodiments of the present application provide a data transmission method.
  • the secondary network device instructs the terminal device to use the data based on the indication information of the primary network device.
  • At least one RLC entity associated with the radio bearer performs data transmission, or the primary network device instructs the terminal device to use the at least one RLC entity associated with the radio bearer to perform data transmission based on the indication information of the secondary network device.
  • MAC CE configures the activation/deactivation of the RLC entity associated with the radio bearer, which can also be understood as: MAC CE configures the radio It bears the activation/deactivation of the associated logical channel.
  • FIG. 5 is a schematic flowchart of a data transmission method provided by an embodiment of this application.
  • This embodiment relates to a specific process of data transmission between a secondary network device, a main network device, and a terminal device.
  • This embodiment relates to a scenario where the PDCP entity associated with the radio bearer is located in the main network device.
  • Figures 4a and 4b are two examples of this scenario.
  • the method may include: S501, S502, and S503.
  • the execution sequence of S501, S502, and S503 is not limited in the embodiment of the present application.
  • the primary network device sends first instruction information to the secondary network device, and correspondingly, the secondary network device receives the first instruction information from the primary network device.
  • the first indication information indicates the primary RLC entity of the first RB, and the first RB is associated with one primary RLC entity and at most 3 secondary RLC entities.
  • the first indication information may be carried on a secondary station addition request (s-node addition request) message or carried on a secondary station modification request (s-node modification request) message.
  • the secondary network device determines the RLC entity associated with the first RB in the secondary network device. Specifically, the secondary network device receives configuration information from the primary network device, the configuration information indicates the M RLC entities associated with the first RB in the secondary network device, and M is 1 or 2, 3. Optionally, the configuration information is carried on a request message for adding a secondary station or a request message for modifying a secondary station.
  • the secondary network device After determining the RLC entity associated with the first RB in the secondary network device, the secondary network device determines the primary RLC entity associated with the first RB.
  • the primary RLC entity of the first RB there is one and only one primary RLC entity of the first RB, that is, the primary RLC entity of the first RB is located in the primary network device, or located in the secondary network device.
  • the manner in which the first indication information indicates the primary RLC entity of the first RB includes any one of the following four manners.
  • the first indication information indicates whether there is a primary RLC entity of the first RB among the foregoing M RLC entities.
  • the first indication information includes one bit.
  • the value of the bit is "0" it indicates that the primary RLC entity of the first RB exists among the M RLC entities (that is, the primary RLC entity of the first RB is located in the secondary RLC entity).
  • the first indication information indicating the number of the first RB secondary RLC entity the RLC entity of the M.
  • the first indication information includes two bits.
  • the value of this bit is "00", it means that the number of secondary RLC entities of the first RB among the M RLC entities is 0.
  • the value of this bit is 0, When it is "01”, it means that the number of secondary RLC entities of the first RB among the above M RLC entities is 1, and when the value of this bit is "10", it means that the number of secondary RLC entities of the first RB among the above M RLC entities is 1.
  • the number of RLC entities is 2, and when the value of this bit is "11", it means that the number of secondary RLC entities of the first RB among the M RLC entities is 3.
  • the number of secondary RLC entities of the first RB indicated by the first indication information is less than M, it means that the primary RLC entity of the first RB is located in the secondary network device; if the secondary RLC entity of the first RB indicated by the first indication information is The number of RLC entities is equal to M, which means that the primary RLC entity of the first RB is located in the primary network device.
  • the secondary network device determines, according to the first indication information, that the number of secondary RLC entities of the first RB among the M RLC entities is 1, if the value of M is 1, it represents the primary RLC of the first RB The entity is located in the primary network device. If the value of M is 2, it means that the two RLC entities associated with the first RB in the secondary network device are one secondary RLC entity and one primary RLC entity, that is, the primary RLC entity of the above-mentioned first RB The entity is located in the auxiliary network device.
  • the first indication information indicates whether the first RB exists in the RLC entity associated with the first RB in the primary network device The main RLC entity.
  • the first indication information includes a bit, and when the value of the bit is "0", it indicates that the main RLC entity of the first RB exists in the RLC entity associated with the first RB in the main network device (ie , The primary RLC entity of the first RB is located in the primary network device).
  • this bit When the value of this bit is "1", it means that the primary RLC entity of the first RB does not exist among the RLC entities associated with the first RB in the primary network device (ie , The primary RLC entity of the first RB is located in the secondary network device); when the value of this bit is "1", it means that the primary RLC entity of the first RB exists in the RLC entity associated with the first RB in the primary network device (ie, The primary RLC entity of the first RB is located in the primary network device. When the value of this bit is "0”, it means that the primary RLC entity of the first RB does not exist among the RLC entities associated with the first RB in the primary network device (ie, The primary RLC entity of the first RB is located in the secondary network device).
  • the first indication information indicates the index of the primary RLC entity of the first RB or the identifier of the logical channel corresponding to the primary RLC entity.
  • the first indication information further indicates the initial state of each secondary RLC entity associated with the first RB.
  • the first indication information includes j bits, and the different secondary RLC entities associated with the first RB correspond to different bits of the j bits, where j is a positive integer, and the above corresponding The relationship can be preset.
  • Each of the above j bits is used to indicate whether the state of the secondary RLC entity corresponding to the bit is active (active) or inactive (inactive).
  • each bit when the value of each bit is "0", it means that the initial state of the secondary RLC entity corresponding to the bit is deactivated, and when the value of each bit is "1", it means that the bit corresponds to The initial state of the secondary RLC entity is activated; or, when the value of each bit is "1", it means that the initial state of the secondary RLC entity corresponding to the bit is deactivated, and when the value of each bit is "0" When, it means that the initial state of the secondary RLC entity corresponding to this bit is active.
  • the first indication information indicates the initial state of the X secondary RLC entities among the above M RLC entities, and X is 0, 1, 2, or 3. In the embodiment of the present application, the initial state of the primary RLC entity of the first RB does not need to be indicated.
  • the initial state of the primary RLC entity of the first RB does not need to be indicated, when the first indication information indicates the initial states of the two RLC entities, it means that the primary RLC entity of the first RB is located in the primary network device. .
  • the first indication information indicates the initial state of one RLC entity
  • the value of M can only be 1, indicating that the only RLC entity associated with the first RB in the secondary network device is the primary RLC entity, that is, the above The primary RLC entity of the first RB is located in the secondary network device.
  • the secondary network device may determine the secondary network device associated with the first RB in the secondary network device according to the first indication information and the value of M. The number of RLC entities and the number of master RLC entities.
  • the primary network device further sends third instruction information to the secondary network device, and correspondingly, the secondary network device receives the third instruction information from the primary network device.
  • the third indication information may be carried on the auxiliary station addition request message or the auxiliary station modification request message.
  • the third indication information and the first indication information may be carried on the same message or carried on different messages.
  • the secondary network device determines the number of secondary RLCs and the number of primary RLCs associated with the first RB in the primary network device according to the first indication information and the third indication information.
  • the third indication information indicates any one or more of the following:
  • the secondary network device can calculate that the first RB in the primary network device is associated with m secondary RLC entities and 0 primary RLC entities. If the first indication information indicates that the primary RLC entity of the first RB is located in the primary network device, the secondary network device can infer that the first RB in the primary network device is associated with m-1 secondary RLC entities and 1 primary RLC entity.
  • the secondary network device can calculate that the first RB in the primary network device is associated with m secondary RLC entities and 0 primary RLC entities. If the first indication information indicates that the primary RLC entity of the first RB is located in the primary network device, the secondary network device can infer that the first RB in the primary network device is associated with m-1 secondary RLC entities and 1 primary RLC entity.
  • the first indication The information indicates that the primary RLC entity of the first RB is located in the secondary network device, and the secondary network device can calculate that the first RB in the primary network device is associated with n secondary RLC entities and 0 primary RLC entities. If the first indication information indicates that the primary RLC entity is located in the primary network device, the secondary network device can calculate that the first RB in the primary network device is associated with n secondary RLC entities and 1 primary RLC entity.
  • the secondary network device can calculate that the first RB in the primary network device is associated with n secondary RLC entities and 0 primary RLC entities. If the first indication information indicates that the primary RLC entity of the first RB is located in the primary network device, the secondary network device can calculate that the first RB in the primary network device is associated with n secondary RLC entities and 1 primary RLC entity.
  • the secondary network device can calculate that the first RB in the primary network device is associated with p-M+1 secondary RLC entities and 0 primary RLC entities. If the first indication information indicates that the primary RLC entity of the first RB is located in the primary network device, the secondary network device can infer that the first RB in the primary network device is associated with p-M secondary RLC entities and 1 primary RLC entity.
  • the first indication indicates that the primary RLC entity of the first RB is located in the secondary network device
  • the secondary network device can calculate that the first RB in the primary network device is associated with p-M+1 secondary RLC entities and 0 primary RLC entities. If the first indication information indicates that the primary RLC entity of the first RB is located in the primary network device, the secondary network device can calculate that the first RB in the primary network device is associated with p-M secondary RLC entities and 1 primary RLC entity.
  • the secondary network device can calculate that the first RB in the primary network device is associated with qM secondary RLC entities and 0 primary RLC entities. If the first indication information indicates that the primary RLC entity of the first RB is located in the primary network device, the secondary network device can calculate that the first RB in the primary network device is associated with q-M-1 secondary RLC entities and 1 primary RLC entity.
  • the secondary network device can calculate that the first RB in the primary network device is associated with qM secondary RLC entities and 0 primary RLC entities. If the first indication information indicates that the primary RLC entity of the first RB is located in the primary network device, the secondary network device can calculate that the first RB in the primary network device is associated with q-M-1 secondary RLC entities and 1 primary RLC entity.
  • the first indication information may also use any one of the following five manners to indicate the primary RLC entity of the first RB.
  • the first indication information indicates the number and/or of all RLC entities associated with the first RB in the primary network device Identification, and, the number and/or identification of all secondary RLC entities associated with the first RB in the primary network device.
  • the primary RLC entity associated with an RB is located in the secondary network device, that is, the first RB in the primary network device is associated with w secondary RLC entities and 0 primary RLC entities.
  • the first indication information indicates the number and/or of all RLC entities associated with the first RB in the primary network device Identification, and, the number and/or identification of the primary RLC entity associated with the first RB in the primary network device.
  • the first indication information indicates the initial status of each secondary RLC entity associated with the first RB in the primary network device. State, and, the number and/or identity of all RLC entities associated with the first RB in the primary network device.
  • the primary RLC entity associated with an RB is located in the secondary network device, that is, the first RB in the primary network device is associated with r secondary RLC entities and 0 primary RLC entities.
  • the first indication information indicates the initial status of each secondary RLC entity associated with the first RB in the secondary network device. State, and, the number and/or identity of all RLC entities associated with the first RB in the primary network device.
  • the first indication information indicates whether each RLC entity associated with the first RB in the primary network device is the first The main RLC entity of the RB.
  • the first indication information includes h bits, and h is a positive integer.
  • Different RLC entities associated with the first RB in the primary network device correspond to different bits in the h bits, and the above-mentioned corresponding relationship may be preset.
  • Each of the above h bits is used to indicate whether the RLC entity corresponding to the bit is the master RLC entity.
  • each bit when the value of each bit is "0", it means that the RLC entity corresponding to the bit is the master RLC entity, and when the value of each bit is "1", it means that the RLC entity corresponding to the bit is not The main RLC entity; or, when the value of each bit is "1”, it means that the RLC entity corresponding to the bit is the main RLC entity, and when the value of each bit is "0", it means that the bit corresponds to The RLC entity is not the main RLC entity.
  • the auxiliary network device after receiving the above-mentioned first indication information, sends fourth indication information to the main network device.
  • the main network device receives the fourth indication information from the auxiliary network device.
  • the fourth indication information may be carried on a secondary station addition request acknowledgement (s-node addition request acknowledgement) message or carried on a secondary station modification request acknowledgement (s-node modification request acknowledgement) message.
  • the fourth indication information indicates that one of the RLC entities associated with the first RB in the secondary network device is the primary RLC entity associated with the first RB.
  • the fourth indication information indicates the index of the primary RLC entity associated with the first RB, or the fourth indication information indicates the logical channel associated with the primary RLC entity associated with the first RB (also referred to as the primary logical channel of the first RB) Of the logo.
  • the primary RLC entity associated with the first RB is determined by the secondary network device.
  • the fourth indication information indicates the offloaded secondary RLC entity associated with the first RB in the secondary network device.
  • the fourth indication information indicates the index of the offload secondary RLC entity associated with the first RB, or the identifier of the logical channel associated with the offload secondary RLC entity associated with the first RB.
  • the logical channel associated with the offload secondary RLC entity associated with the first RB is called the offload secondary logical channel (also called: split secondary path).
  • the terminal device can transmit data to the primary network device through the primary logical channel located in the primary network device, or the terminal device can communicate with the secondary logical channel through the offloading secondary logical channel located in the secondary network device.
  • Network equipment for data transmission When the PDCP duplication function of the first RB is deactivated, the terminal device can transmit data to the primary network device through the primary logical channel located in the primary network device, or the terminal device can communicate with the secondary logical channel through the offloading secondary logical channel located in the secondary network device.
  • step S501 can be replaced by step S501a.
  • the primary network device sends first instruction information to the secondary network device, and correspondingly, the secondary network device receives the first instruction information from the primary network device.
  • the first indication information is used to request the secondary network device to establish the primary RLC entity of the first RB, or the first indication information is used to request the secondary network device to establish the offloaded secondary RLC entity of the first RB.
  • the first indication information may be carried on a secondary station addition request (s-node addition request) message or carried on a secondary station modification request (s-node modification request) message.
  • the secondary network device determines the RLC entity associated with the first RB in the secondary network device. Specifically, the secondary network device receives configuration information from the primary network device, the configuration information indicates the M RLC entities associated with the first RB in the secondary network device, and M is 1 or 2, 3. Optionally, the configuration information is carried on a request message for adding a secondary station or a request message for modifying a secondary station.
  • the secondary network device After determining the RLC entity associated with the first RB in the secondary network device, the secondary network device determines the primary RLC entity associated with the first RB. Specifically, when the first indication information is used to request the establishment of the primary RLC entity of the first RB, it indicates that the primary RLC entity of the first RB is located in the secondary network device, and when the first indication information is used to request the establishment of the offloaded secondary RLC entity of the first RB When it is an entity, it means that the primary RLC entity of the first RB is located in the primary network device. In an optional manner, the first indication information includes a bit. When the value of this bit is "0", it means that the first indication information is used to request the establishment of the primary RLC entity of the first RB.
  • the main network device further sends third indication information to the auxiliary network device, and correspondingly, the auxiliary network device receives the third indication information from the main network device.
  • the third indication information refer to step S501, which will not be repeated here.
  • the secondary network device After receiving the above-mentioned first instruction information, the secondary network device sends fourth instruction information to the primary network device.
  • the primary network device receives the fourth instruction information from the secondary network device.
  • the fourth indication information For a description of the fourth indication information, refer to step S501, which will not be repeated here.
  • the main network device sends fifth indication information to the terminal device.
  • the terminal device receives fifth indication information from the main network device.
  • the fifth indication information may be carried on the RRC reconfiguration message, and the fifth indication information indicates The primary RLC entity associated with the first RB.
  • the fifth indication information indicates the index of the primary RLC entity associated with the first RB, or the fifth indication information indicates the identifier of the logical channel associated with the primary RLC entity associated with the first RB.
  • the terminal device determines the primary RLC entity associated with the first RB according to the fifth indication information.
  • the fifth indication information further indicates the initial states of all secondary RLC entities associated with the first RB.
  • the fifth indication information further indicates the identifier of the offload secondary RLC entity associated with the first RB or the identifier of the logical channel associated with the offload secondary RLC entity.
  • step S502 can also be replaced with S502a.
  • the auxiliary network device sends the foregoing fifth indication information to the terminal device.
  • the terminal device receives the fifth indication information from the auxiliary network device.
  • the fifth indication information may be carried on the RRC reconfiguration message, and the fifth indication information indicates the index of the primary RLC entity associated with the first RB/the identifier of the logical channel associated with the primary RLC entity associated with the first RB, and the first RB Any one or more of the index of the associated offload secondary RLC entity/the identification of the logical channel associated with the offload secondary RLC entity associated with the first RB, and the initial states of all the secondary RLC entities associated with the first RB.
  • the auxiliary network device sends the second indication information of 3 bits in length to the terminal device, and correspondingly, the terminal device receives the second indication information of 3 bits in length from the auxiliary network device.
  • the second indication information indicates the status of each secondary RLC entity of all secondary RLC entities associated with the first RB, where different RLC entities associated with the first RB correspond to different bits of the 3 bits.
  • the second indication information is carried in a MAC CE.
  • the use status of the secondary RLC entity of the first RB in the primary network device and the use status of the secondary RLC entity of the first RB in the secondary network device are sequentially arranged . That is, in the above 3 bits, the low bit is used to indicate the use status of the secondary RLC entity in the primary network device of the first RB, and the high bit is used to indicate the use status of the secondary RLC entity in the secondary network device of the first RB. state.
  • the RLC entities corresponding to the logical channel with the low logical channel identifier and the logical channel with the high logical channel identifier are arranged in sequence The RLC entity. That is, in the above 3 bits, the low bit is used to indicate the use status of the RLC entity corresponding to the logical channel with the low logical channel identifier associated with the first RB, and the high bit is used to indicate the high logical channel identifier associated with the first RB. The usage status of the RLC entity corresponding to the logical channel.
  • the third bit of the above three bits indicates the state of RLC2, the second bit indicates the state of RLC3, and the first bit indicates the state of RLC4; when RLC2 is the master In the case of RLC entity, the third bit of the above 3 bits indicates the status of RLC1, the second bit indicates the status of RLC3, and the first bit indicates the status of RLC4; when RLC3 is the main RLC entity, the third bit of the above 3 bits indicates the status of RLC1.
  • the three bits represent the status of RLC1, the second bit represents the status of RLC2, the first bit represents the status of RLC4; when RLC4 is the main RLC entity, the third bit of the above three bits represents the status of RLC1, and the second bit represents the status of RLC1.
  • the bits represent the status of RLC2, and the first bit represents the status of RLC3.
  • the first RB is associated with a total of 2 secondary RLC entities and 1 primary RLC entity, as shown in FIG. 4b, it is assumed that the identity of LCH1 ⁇ the identity of LCH3 ⁇ the identity of LCH4.
  • RLC1 is the master RLC entity, as shown in Figure 4d
  • the third bit of the above three bits indicates the status of RLC3, the second bit indicates the status of RLC4, and the first bit is empty;
  • RLC3 is the master RLC entity ,
  • the third bit of the above 3 bits represents the status of RLC1, the second bit represents the status of RLC4, and the first bit is empty;
  • RLC4 is the main RLC entity, the third bit of the above 3 bits represents the status of RLC1 Status, the second bit indicates the status of RLC3, and the first bit is empty.
  • the terminal device determines the state of the secondary RLC entity corresponding to the bit according to the value of each of the above 3 bits.
  • any bit of the above 3 bits when the value of any bit of the above 3 bits is "0", it indicates that the status of the secondary RLC entity corresponding to the bit is deactivated, or it can also be understood as: indicates that the bit corresponds to The state of the logical channel associated with the secondary RLC entity is deactivated; when the value of any bit of the above 3 bits is "1", it means that the state of the secondary RLC entity corresponding to the bit is activated, or it can also be understood as: It indicates that the status of the logical channel associated with the secondary RLC entity corresponding to this bit is active.
  • any bit of the above 3 bits when the value of any bit of the above 3 bits is "1", it indicates that the status of the secondary RLC entity corresponding to the bit is deactivated, or it can also be understood as: indicates that the bit corresponds to The state of the logical channel associated with the secondary RLC entity is deactivated; when the value of any bit of the above 3 bits is "0”, it means that the state of the secondary RLC entity corresponding to the bit is activated, or it can also be understood as : Indicates that the status of the logical channel associated with the secondary RLC entity corresponding to this bit is active.
  • the secondary RLC entity When the status of any secondary RLC entity associated with the first RB is active, the secondary RLC entity is allowed to be used for PDCP duplication, that is, the terminal device can perform PDCP layer replication transmission with the network device through the logical channel associated with the secondary RLC entity; When the status of any secondary RLC entity associated with the first RB is deactivated, the secondary RLC entity is not allowed to be used for PDCP duplication, that is, the terminal device cannot perform PDCP layer replication transmission with the network device through the logical channel associated with the secondary RLC entity .
  • the terminal device stops the PDCP duplication function of the first RB, and performs offload transmission operations. Specifically, the terminal device determines, according to the threshold of offload transmission, whether to transmit different data to the network device where the primary logical channel is located and the network device where the offload secondary logical channel is located through the primary logical channel of the first RB and the secondary logical channel of the first RB. data pack.
  • the terminal device transmits to the network device where the primary logical channel is located through the primary logical channel of the first RB; when the amount of data to be sent is greater than or equal to the threshold for offloaded transmission
  • the terminal device sends different data packets to the network device where the main logical channel is located and the network device where the shunt auxiliary logical channel is located through the primary logical channel of the first RB and the offload secondary logical channel of the first RB, respectively.
  • the terminal device After the terminal device determines the status of all the secondary RLC entities associated with the first RB according to the second indication information, it activates or deactivates the corresponding secondary RLC entity, and the logical channel corresponding to the secondary RLC entity, so as to communicate with the primary network device and the secondary network device Perform data transfer.
  • the foregoing embodiment provides a data transmission method.
  • the secondary network device receives the indication information from the primary network device, and the secondary network device can follow the indication information
  • the primary RLC entity associated with the radio bearer is determined, so that the terminal device can be accurately indicated which RLC entities need to be activated and deactivated, which improves the reliability of data transmission.
  • FIG. 6 is a schematic flowchart of a data transmission method provided by an embodiment of this application.
  • This embodiment relates to a specific process of data transmission between a secondary network device, a main network device, and a terminal device.
  • This embodiment relates to a scenario where the PDCP entity associated with the radio bearer is located in the secondary network device.
  • Figures 4e and 4f are two examples of this scenario.
  • the method may include: S601, S602, and S603.
  • the execution sequence of S601, S602, and S603 is not limited in the embodiment of the present application.
  • the secondary network device sends first instruction information to the primary network device, and correspondingly, the primary network device receives the first instruction information from the secondary network device.
  • the first indication information indicates the primary RLC entity of the first RB, and the first RB is associated with one primary RLC entity and at most 3 secondary RLC entities.
  • the first indication information is carried in the auxiliary station addition request acknowledgement (s-node addition request acknowledgement) message, the auxiliary station modification request acknowledgement (s-node modification request acknowledgement) message, or the auxiliary station modification request message (s-node modification required).
  • the primary network device determines the RLC entity associated with the first RB in the primary network device.
  • the primary network device receives configuration information from the secondary network device, and the configuration information indicates K RLC entities associated with the first RB in the primary network device, where K is 1, 2, or 3.
  • the configuration information is carried on a secondary station addition request confirmation message, secondary station modification request confirmation message, or secondary station modification request message.
  • the primary network device After determining the RLC entity associated with the first RB in the primary network device, the primary network device determines the primary RLC entity associated with the first RB.
  • the manner in which the first indication information indicates the primary RLC entity of the first RB includes any one of the following four manners.
  • the first indication information indicates whether there is a primary RLC entity of the first RB among the above K RLC entities.
  • the first indication information includes 1 bit.
  • the value of this bit is "0" it means that the primary RLC entity of the first RB exists among the K RLC entities (that is, the primary RLC entity of the first RB is located at Primary network device), when the value of this bit is "1", it means that the primary RLC entity of the first RB does not exist among the above K RLC entities (that is, the primary RLC entity of the first RB is located in the secondary network device); or When the value of this bit is "1", it means that the primary RLC entity of the first RB exists among the above K RLC entities (that is, the primary RLC entity of the first RB is located in the primary network device), when the value of this bit When it is "0", it means that the primary RLC entity of the first RB does not exist among the above K RLC entities (that is, the primary RLC entity of the first RB is located in the secondary network device).
  • the first indication information indicates the number of secondary RLC entities of the first RB among the above K RLC entities.
  • the first indication information includes two bits.
  • the value of this bit is "00", it means that the number of secondary RLC entities of the first RB among the above K RLC entities is 0.
  • the value of this bit is 0
  • it means that the number of secondary RLC entities of the first RB in the above K RLC entities is 1
  • the value of this bit is "10”
  • the number of RLC entities is 2, and when the value of this bit is “11”, it means that the number of secondary RLC entities of the first RB among the K RLC entities is 3.
  • mode 2 if the number of secondary RLC entities of the first RB indicated by the first indication information is less than K, it means that the primary RLC entity of the first RB is located in the primary network device; if the secondary RLC entity of the first RB indicated by the first indication information is The number of RLC entities is equal to K, which means that the primary RLC entity of the first RB is located in the secondary network device.
  • the primary network device determines, according to the first indication information, that the number of secondary RLC entities of the first RB among the K RLC entities is 1, if the value of K is 1, it represents the primary RLC entity of the first RB Located in the secondary network device, if the value of K is 2, it means that the two RLC entities associated with the first RB in the primary network device are one secondary RLC entity and one primary RLC entity, that is, the primary RLC entity of the above-mentioned first RB Located on the main network device.
  • the first indication information indicates whether the first RB exists in the RLC entity associated with the first RB in the secondary network device The main RLC entity.
  • the first indication information includes 1 bit.
  • the value of this bit is "0" it indicates that the primary RLC entity of the first RB exists among the RLC entities associated with the first RB in the secondary network device ( That is, the primary RLC entity of the first RB is located in the secondary network device)
  • the value of this bit is "1” it means that the primary RLC entity of the first RB does not exist among the RLC entities associated with the first RB in the secondary network device ( That is, the primary RLC entity of the first RB is located in the primary network device; when the value of this bit is "1", it means that the primary RLC entity of the first RB exists in the RLC entity associated with the first RB in the secondary network device (ie , The primary RLC entity of the first RB is located in the secondary network device).
  • this bit When the value of this bit is "0", it means that there is no primary RLC entity of the first RB among the RLC entities associated with the first RB in the secondary network device (ie , The main RLC entity of the first RB is located in the main network device).
  • the first indication information indicates the index of the primary RLC entity of the first RB or the identifier of the logical channel associated with the primary RLC entity of the first RB .
  • the first indication information further indicates the initial state of each secondary RLC entity associated with the first RB. Participating in step S501 is described in detail, which will not be repeated here.
  • the first indication information indicates the initial state of the Y RLC entities among the above K RLC entities, and Y is 0, 1, 2 or 3.
  • the primary RLC entity of the first RB since the initial state of the primary RLC entity of the first RB does not need to be indicated, when the first indication information indicates the initial states of the two RLC entities, it means that the primary RLC entity of the first RB is located Auxiliary network equipment.
  • the first indication information indicates the initial state of an RLC entity
  • the value of K is 1, it means that the primary RLC entity of the first RB is located in the secondary network device, and if the value of K is 2, it means The first indication information only indicates the initial state of one of the two RLC entities, that is, the other RLC entity with no initial state indicated is the primary RLC entity, that is, the primary RLC entity of the first RB is located in the primary network equipment.
  • the value of K can only be 1, indicating that the only RLC entity associated with the first RB in the primary network device is the primary RLC entity, that is, the above
  • the main RLC entity of the first RB is located in the main network device.
  • the primary network device may determine the secondary RLC entity associated with the first RB in the primary network device according to the first indication information and the value of K. The number of RLC entities and the number of master RLC entities.
  • the primary network device further sends third instruction information to the secondary network device, and correspondingly, the secondary network device receives the third instruction information from the primary network device.
  • the third indication information is carried on a secondary station addition request confirmation message, secondary station modification request confirmation, or secondary station modification request message.
  • the third indication information and the first indication information may be carried on the same message or carried on a different message.
  • the third indication information can also indicate any one or more of the following:
  • the first indication information may also use any one of the following five manners to indicate the primary RLC entity of the first RB.
  • the first indication information indicates the number and/or of all RLC entities associated with the first RB in the secondary network device Identification, and, the number and/or identification of all secondary RLC entities associated with the first RB in the secondary network device.
  • the first indication information indicates the number and/or of all RLC entities associated with the first RB in the secondary network device Identification, and, the number and/or identification of all primary RLC entities associated with the first RB in the secondary network device.
  • the first indication information indicates the initial status of each secondary RLC entity associated with the first RB in the secondary network device. State, and, the number and/or identity of all RLC entities associated with the first RB in the secondary network device.
  • the first indication information indicates the initial status of each secondary RLC entity associated with the first RB in the primary network device. State, and, the number and/or identity of all RLC entities associated with the first RB in the secondary network device.
  • the first indication information indicates whether each RLC entity associated with the first RB in the secondary network device is the first The main RLC entity of the RB.
  • Mode 5 to Mode 9 are similar to Modes 5 to 9 in S501, and only the "primary network device” and the “secondary network device” need to be exchanged, which will not be repeated here.
  • the main network device after receiving the above-mentioned first indication information, the main network device sends fourth indication information to the auxiliary network device, and correspondingly, the auxiliary network device receives the fourth indication information from the main network device.
  • the fourth indication information may be carried on the secondary station addition request confirmation message or carried on the secondary station modification request confirmation message.
  • the fourth indication information indicates that one of the RLC entities associated with the first RB in the primary network device is the primary RLC entity associated with the first RB.
  • the fourth indication information indicates the index of the primary RLC entity associated with the first RB, or the fourth indication information indicates the logical channel associated with the primary RLC entity associated with the first RB (also referred to as the primary logical channel of the first RB) Of the logo.
  • the master RLC entity associated with the first RB is determined by the master network device.
  • the fourth indication information indicates the offload secondary RLC entity associated with the first RB in the primary network device.
  • the fourth indication information indicates the index of the offload secondary RLC entity associated with the first RB, or the identifier of the logical channel associated with the offload secondary RLC entity associated with the first RB.
  • the logical channel associated with the offload secondary RLC entity associated with the first RB is called the offload secondary logical channel (also called: split secondary path).
  • the terminal device can transmit data to the secondary network device through the primary logical channel located in the secondary network device, or the terminal device can communicate with the primary logical channel through the offload secondary logical channel located in the primary network device.
  • Network equipment for data transmission When the PDCP duplication function of the first RB is deactivated, the terminal device can transmit data to the secondary network device through the primary logical channel located in the secondary network device, or the terminal device can communicate with the primary logical channel through the offload secondary logical channel located in the primary network device.
  • step S601 can be replaced by step S601a.
  • the secondary network device sends first instruction information to the primary network device, and correspondingly, the primary network device receives the first instruction information from the secondary network device.
  • the first indication information is used to request the primary network device to establish the primary RLC entity of the first RB, or the first indication information is used to request the primary network device to establish the offloaded secondary RLC entity of the first RB.
  • the first indication information is carried on a secondary station addition request acknowledgement (s-node addition request acknowledgement) message or a secondary station modification request acknowledgement (s-node modification request acknowledgement) message.
  • the primary network device determines the RLC entity associated with the first RB in the primary network device.
  • the primary network device receives configuration information from the secondary network device, and the configuration information indicates K RLC entities associated with the first RB in the primary network device, where K is 1, 2, or 3.
  • the configuration information is carried on the auxiliary station addition request confirmation message or the auxiliary station modification request confirmation message.
  • the primary network device After determining the RLC entity associated with the first RB in the primary network device, the primary network device determines the primary RLC entity associated with the first RB. Specifically, when the first indication information is used to request the establishment of the primary RLC entity of the first RB, it indicates that the primary RLC entity of the first RB is located in the primary network device, and when the first indication information is used to request the establishment of the offloaded secondary RLC entity of the first RB When it is an entity, it means that the primary RLC entity of the first RB is located in the secondary network device. In an optional manner, the first indication information includes a bit. When the value of this bit is "0", it means that the first indication information is used to request the establishment of the primary RLC entity of the first RB.
  • the auxiliary network device further sends third indication information to the main network device, and correspondingly, the main network device receives the third indication information from the auxiliary network device.
  • the third indication information refer to step S601, which will not be repeated here.
  • the primary network device After receiving the first instruction information, the primary network device sends fourth instruction information to the secondary network device, and correspondingly, the secondary network device receives the fourth instruction information from the primary network device.
  • the fourth indication information For the description of the fourth indication information, refer to step S601, which will not be repeated here.
  • the auxiliary network device sends fifth indication information to the terminal device.
  • the terminal device receives fifth indication information from the auxiliary network device.
  • the fifth indication information may be an RRC reconfiguration message, and the fifth indication information indicates the first The primary RLC entity associated with the RB.
  • the fifth indication information indicates the identity of the primary RLC entity associated with the first RB, or the fifth indication information indicates the identity of the logical channel associated with the primary RLC entity associated with the first RB.
  • the terminal device determines the primary RLC entity associated with the first RB according to the fifth indication information.
  • the fifth indication information further indicates the initial states of all secondary RLC entities associated with the first RB.
  • the fifth indication information further indicates the identifier of the offload secondary RLC entity associated with the first RB or the identifier of the logical channel associated with the offload secondary RLC entity.
  • step S602 can also be replaced with S602a.
  • the main network device sends the above-mentioned fifth indication information to the terminal device.
  • the terminal device receives the fifth indication information from the auxiliary network device.
  • the fifth indication information may be carried on the RRC reconfiguration message, and the fifth indication information indicates the index of the primary RLC entity associated with the first RB/the identifier of the logical channel associated with the primary RLC entity associated with the first RB, and the first RB Any one or more of the index of the associated offload secondary RLC entity/the identification of the logical channel associated with the offload secondary RLC entity associated with the first RB, and the initial states of all the secondary RLC entities associated with the first RB.
  • the main network device sends second indication information with a length of 3 bits to the terminal device, and correspondingly, the terminal device receives the second indication information with a length of 3 bits from the main network device.
  • the second indication information indicates the status of each secondary RLC entity of all the secondary RLC entities associated with the first RB. Wherein, different RLC entities associated with the first RB correspond to different bits in the 3 bits.
  • the second indication information is carried in a MAC CE.
  • the terminal device determines the state of the secondary RLC entity corresponding to the bit according to the value of each of the above 3 bits. Participating in step S503 is described in detail, which will not be repeated here.
  • the above embodiment provides a data transmission method.
  • the primary network device receives the indication information from the secondary network device, and the primary network device can follow the indication information
  • the primary RLC entity associated with the radio bearer is determined, so that the terminal device can be accurately indicated which RLC entities need to be activated and deactivated, which improves the reliability of data transmission.
  • FIG. 7 is a schematic flowchart of a data transmission method provided by an embodiment of the application.
  • the embodiment shown in FIG. 7 is applicable to a network architecture that implements the PDCP duplication function in a DC+CA scenario, where the CU and DU of the network device are separated.
  • This embodiment relates to the specific process of data transmission between the first DU, the CU and the terminal device.
  • the PDCP entity associated with the radio bearer is located in the second DU, that is, the second DU includes a PDCP entity, an RLC entity, and a MAC entity.
  • the first DU includes an RLC entity and a MAC entity.
  • the CU in this embodiment is implemented by the CU-CP. Operation.
  • the method may include: S701, S702, and S703.
  • the execution order of S701, S702, and S703 is not limited in the embodiment of the present application.
  • the CU sends first indication information to the first DU, and correspondingly, the first DU receives the first indication information from the CU.
  • the first indication information indicates the primary RLC entity of the first RB.
  • the first RB is associated with one primary RLC entity and at most 3 secondary RLC entities.
  • the first indication information is carried in a context setup request (context setup request) message or a context modification request (context modification request) message.
  • the first DU determines the RLC entity associated with the first RB in the first DU. Specifically, the first DU receives configuration information from the CU, and the configuration information indicates M RLC entities associated with the first RB in the first DU, where M is 1, 2, or 3.
  • the configuration information can be carried on the context establishment request message or on the context modification request message.
  • the primary RLC entity associated with the first RB is determined. There is one and only one primary RLC entity of the first RB, that is, the primary RLC entity of the first RB is located in the first DU, or located in the second DU.
  • the first indication information indicates the primary RLC entity of the first RB
  • the second DU is replaced by the second DU, which will not be repeated here.
  • the CU further sends third indication information to the first DU, and correspondingly, the first DU receives the third indication information from the CU.
  • the third indication information may be carried on the context establishment request message or the context modification request message. Specifically, for the description of the third indication information, refer to S501, only the "secondary network device" is replaced by the first DU, and the "primary network device” is replaced by the second DU, which will not be repeated here.
  • any one of manners 5 to 9 in S501 may also be used to indicate the primary RLC entity of the first RB, and only Replace the "secondary network device" in Mode 5 to Mode 9 with the first DU, and replace the "primary network device" with the second DU, which will not be repeated here.
  • the first DU after receiving the foregoing first indication information, the first DU sends fourth indication information to the CU, and correspondingly, the CU receives the fourth indication information from the first DU.
  • the fourth indication information may be carried on a context setup response (context setup response) message or on a context modification response (context modification response) message.
  • the fourth indication information indicates that one of the RLC entities associated with the first RB in the first DU is the primary RLC entity associated with the first RB.
  • the fourth indication information indicates the identity of the primary RLC entity associated with the first RB, or the fourth indication information indicates the logical channel associated with the primary RLC entity associated with the first RB (also referred to as the primary logical channel of the first RB) Of the logo.
  • the primary RLC entity associated with the first RB is determined by the first DU.
  • the fourth indication information indicates the offload secondary RLC entity associated with the first RB in the first DU.
  • the fourth indication information indicates the index of the offload secondary RLC entity associated with the first RB, or the identifier of the logical channel associated with the offload secondary RLC entity associated with the first RB.
  • the logical channel associated with the offload secondary RLC entity associated with the first RB is called the offload secondary logical channel (also called: split secondary path).
  • the terminal device can transmit data to the second DU via the primary logical channel located in the second DU, or the terminal device can transmit data to the second DU via the offload secondary logical channel located in the first DU.
  • One DU performs data transmission.
  • step S701 can be replaced by step S701a.
  • the CU sends first indication information to the first DU.
  • the first DU receives the first indication information from the CU.
  • the first indication information is used to request the first DU to establish the primary RLC entity of the first RB, or the first indication information is used to request the first DU to establish the offload secondary RLC entity of the first RB.
  • the first indication information is carried in a context setup request (context setup request) message or a context modification request (context modification request) message.
  • the first DU determines the RLC entity associated with the first RB in the first DU. Specifically, the first DU receives configuration information from the CU, and the configuration information indicates M RLC entities associated with the first RB in the first DU, where M is 1, 2, or 3.
  • the configuration information can be carried on the context establishment request message or on the context modification request message.
  • the primary RLC entity associated with the first RB is determined. Specifically, when the first indication information is used to request the establishment of the primary RLC entity of the first RB, it means that the primary RLC entity of the first RB is located in the first DU, and when the first indication information is used to request the establishment of the offloaded secondary RLC entity of the first RB When it is an entity, it means that the primary RLC entity of the first RB is located in the second DU.
  • the first indication information includes a bit. When the value of the bit is "0", it means that the first indication information is used to request the establishment of the primary RLC entity of the first RB.
  • the CU further sends third indication information to the first DU, and correspondingly, the first DU receives the third indication information from the CU.
  • the third indication information refer to step S701, which will not be repeated here.
  • the first DU After receiving the first indication information, the first DU sends fourth indication information to the CU. Correspondingly, the CU receives the fourth indication information from the first DU. For the description of the fourth indication information, refer to step S701, which will not be repeated here.
  • the CU sends fifth instruction information to the terminal device, and correspondingly, the terminal device receives the fifth instruction information from the CU.
  • the fifth indication information refer to step S502 in the embodiment shown in FIG. 5.
  • the terminal device determines the primary RLC entity associated with the first RB according to the fifth indication information, and then determines, according to the above second indication information, that the status of all secondary RLC entities associated with the first RB is activated or deactivated. For specific description, refer to step S502 in the embodiment shown in FIG. 5.
  • the first DU sends second indication information to the terminal device, and correspondingly, the terminal device receives the second indication information from the first DU.
  • the second indication information indicates the status of each secondary RLC entity of all the secondary RLC entities associated with the first RB.
  • the foregoing embodiment provides a data transmission method.
  • the first DU receives the indication information from the CU, and the first DU can determine the The main RLC entity associated with the radio bearer can thus accurately indicate which RLC entities need to be activated and deactivated by the terminal device, which improves the reliability of data transmission.
  • FIG. 8 is a schematic flowchart of a data transmission method provided by an embodiment of this application.
  • the embodiment shown in FIG. 8 is applicable to a network architecture that implements the PDCP duplication function in a DC+CA scenario, where the CU and DU of the network device are separated.
  • This embodiment relates to the specific process of data transmission between the second DU, the CU and the terminal device.
  • the PDCP entity associated with the radio bearer is located in the first DU, that is, the first DU includes a PDCP entity, an RLC entity, and a MAC entity.
  • the second DU includes an RLC entity and a MAC entity.
  • the CU-CP implements the CU in this embodiment. Operation.
  • the method may include: S801, S802, and S803.
  • the execution order of S801, S802, and S803 is not limited in the embodiment of the present application.
  • the CU sends first indication information to the second DU, and correspondingly, the second DU receives the first indication information from the CU.
  • the first indication information indicates the primary RLC entity of the first RB, and the first RB is associated with one primary RLC entity and at most 3 secondary RLC entities.
  • the first indication information may be carried on a context setup request (context setup request) message or on a context modification request (context modification request) message.
  • the second DU determines the RLC entity associated with the first RB in the second DU. Specifically, the second DU receives configuration information from the CU, and the configuration information indicates K RLC entities associated with the first RB in the second DU, where K is 1, 2, or 3.
  • the configuration information can be carried on the context establishment request message or on the context modification request message.
  • the second DU After determining the RLC entity associated with the first RB in the second DU, the second DU determines the primary RLC entity associated with the first RB.
  • the first indication information indicates the primary RLC entity of the first RB
  • the second DU determines the primary RLC entity associated with the first RB.
  • the second DU after receiving the above-mentioned first indication information, the second DU sends fourth indication information to the CU, and correspondingly, the CU receives the fourth indication information from the second DU.
  • the fourth indication information may be a context setup response message (context setup response) or a context modification response message (context modification response).
  • the fourth indication information indicates that one of the RLC entities associated with the first RB in the second DU is the primary RLC entity associated with the first RB.
  • the fourth indication information indicates the index of the primary RLC entity associated with the first RB, or the fourth indication information indicates the identifier of the logical channel associated with the primary RLC entity associated with the first RB.
  • the primary RLC entity associated with the first RB is determined by the second DU.
  • the fourth indication information indicates that the logical channel corresponding to one of the RLC entities associated with the first RB in the second DU is the offload secondary logical channel (also referred to as: split secondary path). Specifically, the fourth indication information may indicate the identity of the offload secondary logical channel.
  • the terminal device can transmit data to the first DU through the primary RLC entity located in the first DU, or the terminal device can communicate with the first DU through the offload secondary logical channel located in the second DU.
  • the second DU performs data transmission.
  • step S801 can be replaced by step S801a.
  • the CU sends first indication information to the second DU, and correspondingly, the second DU receives the first indication information from the CU.
  • the first indication information is used to request the second DU to establish the primary RLC entity of the first RB, or the first indication information is used to request the second DU to establish the offload secondary RLC entity of the first RB.
  • the first indication information is carried on a context setup request (context setup request) message or a context modification request (context modification request) message.
  • the second DU determines the RLC entity associated with the first RB in the second DU. Specifically, the second DU receives configuration information from the CU, and the configuration information indicates K RLC entities associated with the first RB in the second DU, where K is 1, 2, or 3.
  • the configuration information can be carried on the context establishment request message or on the context modification request message.
  • the second DU determines the primary RLC entity associated with the first RB. Specifically, when the first indication information is used to request the establishment of the primary RLC entity of the first RB, it indicates that the primary RLC entity of the first RB is located in the second DU, and when the first indication information is used to request the establishment of the offloaded secondary RLC entity of the first RB When it is an entity, it means that the primary RLC entity of the first RB is located in the first DU.
  • the first indication information includes a bit. When the value of the bit is "0", it means that the first indication information is used to request the establishment of the primary RLC entity of the first RB.
  • the CU further sends third indication information to the second DU, and correspondingly, the second DU receives the third indication information from the CU.
  • the third indication information refer to step S801, which will not be repeated here.
  • the second DU After receiving the above-mentioned first indication information, the second DU sends fourth indication information to the CU. Correspondingly, the CU receives the fourth indication information from the second DU. For the description of the fourth indication information, refer to step S801, which will not be repeated here.
  • the CU sends fifth instruction information to the terminal device, and correspondingly, the terminal device receives the fifth instruction information from the CU.
  • the fifth indication information refer to the description of the fifth indication information in step S602.
  • the second DU sends second indication information to the terminal device, and correspondingly, the terminal device receives the second indication information from the second DU.
  • the second indication information indicates the status of each secondary RLC entity of all the secondary RLC entities associated with the first RB.
  • the foregoing embodiment provides a data transmission method.
  • the second DU receives the indication information from the CU, and the second DU can determine the The main RLC entity associated with the radio bearer can thus accurately indicate which RLC entities need to be activated and deactivated by the terminal device, which improves the reliability of data transmission.
  • the network device and the terminal device include hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware, software, or a combination of hardware and software. Whether a certain function is executed by hardware, software, or computer software-driven hardware depends on the specific application scenarios and design constraints of the technical solution.
  • Figures 9 and 10 are schematic structural diagrams of possible communication devices provided by embodiments of this application. These communication devices can be used to implement the functions of the terminal device or the network device in the foregoing method embodiment, and therefore can also achieve the beneficial effects of the foregoing method embodiment.
  • the communication device may be the auxiliary network device 120 shown in FIG. 1, or the main network device 130 shown in FIG. 1, or may be applied to the auxiliary network device or the main network device. Modules (such as chips).
  • the communication device 900 includes a processing unit 910 and a transceiving unit 920.
  • the communication device 900 is used to implement the functions of the auxiliary network device or the main network device in the method embodiments shown in FIGS. 5 to 6 above, or the communication device 900 is used to implement the method implementation shown in FIGS. 7 to 8 above.
  • the transceiving unit 920 is used to receive first indication information from the main network device, the first indication information indicating the first radio bearer RB
  • the primary radio link control RLC entity of the first RB is associated with a primary RLC entity and at most 3 secondary RLC entities; the transceiver unit 920 is also configured to send second indication information with a length of 3 bits to the terminal device, the second indication information Indicate the status of each secondary RLC entity associated with the first RB, and different secondary RLC entities associated with the first RB correspond to different bits in the 3 bits.
  • the transceiving unit 920 is used to send first indication information to the secondary network device, where the first indication information indicates the status of the first radio bearer RB
  • the primary radio link controls the RLC entity, and the first RB is associated with one primary RLC entity and at most 3 secondary RLC entities.
  • the transceiver unit 920 is further configured to send fifth indication information to the terminal device, where the fifth indication information indicates the primary RLC entity of the first RB.
  • the transceiving unit 920 is used to send first indication information to the main network device, where the first indication information indicates the first radio bearer RB
  • the primary radio link controls the RLC entity, and the first RB is associated with one primary RLC entity and at most 3 secondary RLC entities.
  • the transceiver unit 920 is further configured to send fifth indication information to the terminal device, where the fifth indication information indicates the primary RLC entity of the first RB.
  • the transceiver unit 920 is used to receive first indication information from the secondary network device, the first indication information indicating the first radio bearer RB
  • the primary radio link control RLC entity of the first RB is associated with one primary RLC entity and at most 3 secondary RLC entities; the transceiver unit 920 is also configured to send second indication information with a length of 3 bits to the terminal device, the second indication information Indicate the status of each secondary RLC entity associated with the first RB, and different secondary RLC entities associated with the first RB correspond to different bits in the 3 bits.
  • the transceiving unit 920 is used to receive first indication information from the CU.
  • the first indication information indicates the master of the first radio bearer RB.
  • the radio link control RLC entity, the first RB is associated with a primary RLC entity and at most 3 secondary RLC entities; the transceiver unit 920 is further configured to send second indication information with a length of 3 bits to the terminal device, where the second indication information indicates the foregoing
  • the state of each secondary RLC entity associated with the first RB, and the different secondary RLC entities associated with the first RB correspond to different bits in the 3 bits.
  • the transceiver unit 920 is used to send first indication information to the first DU.
  • the first indication information indicates the primary radio of the first radio bearer RB.
  • Link control RLC entity, the first RB is associated with one primary RLC entity and at most 3 secondary RLC entities.
  • the transceiver unit 920 is further configured to send fifth indication information to the terminal device, where the fifth indication information indicates the primary RLC entity of the first RB.
  • the transceiver unit 920 is used to receive the first indication information from the CU, and the first indication information indicates the master of the first radio bearer RB.
  • the radio link control RLC entity, the first RB is associated with a primary RLC entity and at most 3 secondary RLC entities; the transceiver unit 920 is further configured to send second indication information with a length of 3 bits to the terminal device, where the second indication information indicates the foregoing
  • the state of each secondary RLC entity associated with the first RB, and the different secondary RLC entities associated with the first RB correspond to different bits in the 3 bits.
  • the transceiver unit 920 is used to send first indication information to the second DU.
  • the first indication information indicates the primary radio of the first radio bearer RB.
  • Link control RLC entity, the first RB is associated with one primary RLC entity and at most 3 secondary RLC entities.
  • the transceiver unit 920 is further configured to send fifth indication information to the terminal device, where the fifth indication information indicates the primary RLC entity of the first RB.
  • processing unit 910 and the transceiver unit 920 can be obtained directly with reference to the relevant descriptions in the method embodiments shown in FIG. 5 to FIG. 8, and will not be repeated here.
  • the communication device 1000 includes a processor 1010 and an interface circuit 1020.
  • the processor 1010 and the interface circuit 1020 are coupled with each other.
  • the interface circuit 1020 may be a transceiver or an input/output interface.
  • the communication device 1000 may further include a memory 1030 for storing instructions executed by the processor 1010 or storing input data required by the processor 1010 to run the instructions or storing data generated after the processor 1010 runs the instructions.
  • the processor 1010 is used to implement the functions of the above-mentioned processing unit 1010
  • the interface circuit 1020 is used to implement the functions of the above-mentioned transceiving unit 1020.
  • the terminal device chip When the foregoing communication device is a chip applied to a terminal device, the terminal device chip implements the function of the terminal device in the foregoing method embodiment.
  • the terminal device chip receives information from other modules in the terminal device (such as a radio frequency module or antenna), and the information is sent by the network device to the terminal device; or, the terminal device chip sends information to other modules in the terminal device (such as a radio frequency module or antenna).
  • the antenna sends information, which is sent by the terminal device to the network device.
  • the network device chip implements the function of the network device in the foregoing method embodiment.
  • the network device chip receives information from other modules in the network device (such as radio frequency modules or antennas), and the information is sent by the terminal device to the network device; or, the network device chip sends information to other modules in the network device (such as radio frequency modules or antennas).
  • the antenna sends information, which is sent by the network device to the terminal device.
  • the processor in the embodiments of the present application may be a central processing unit (Central Processing Unit, CPU), or other general-purpose processors, digital signal processors (Digital Signal Processors, DSPs), and application specific integrated circuits. (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the processor may be random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable Except programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art middle.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the ASIC can be located in a network device or a terminal device.
  • the processor and the storage medium may also exist as discrete components in the network device or the terminal device.
  • the computer program product includes one or more computer programs or instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal device, or other programmable devices.
  • the computer program or instruction may be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server integrating one or more available media.
  • the usable medium may be a magnetic medium, such as a floppy disk, a hard disk, and a magnetic tape; it may also be an optical medium, such as a DVD; and it may also be a semiconductor medium, such as a solid state disk (SSD).

Landscapes

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

Abstract

本申请实施例提供了数据传输的方法和装置，当为一个无线承载RB配置多于两个无线链路控制RLC实体时，辅网络设备接收来自主网络设备的指示信息，辅网络设备可以根据该指示信息确定该无线承载关联的主RLC实体，从而可以准确地指示终端设备哪些RLC实体需要被激活和去激活，提升了数据传输的可靠性。

Description

一种通信方法及装置
本申请要求在2020年05月21日提交中国专利局、申请号为202010437695.5、申请名称为“数据传输的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及无线通信领域，尤其涉及数据传输的方法和装置。
背景技术
第五代(5th generation，5G)移动通信系统与第四代(4th generation，4G)移动通信系统相比的一大显著特征就是增加了对超可靠低时延通信(ultra-reliable and low-latency communications,URLLC)业务的支持。URLLC的业务种类包括很多种，典型的用例包括工业控制、无人驾驶、远程手术和智能电网等。对于URLLC业务，一个典型需求是在1毫秒(millisecond，ms)内发送32字节的数据的可靠性要达到99.999％。需要指出的是，上述性能指标仅是个示例，不同的URLLC业务可能对可靠性有不同的需求，比如在某些极端苛刻的工业控制应用场景中，URLLC业务数据的传输成功概率需要在0.25ms内达到99.9999999％。
发明内容
本申请提供了一种数据传输的方法和装置，用于提升数据传输的可靠性。
第一方面，本申请提供了一种数据传输的方法，该方法的执行主体为辅网络设备或辅网络设备中的一个模块。这里以辅网络设备为执行主体为例进行描述。辅网络设备接收来自主网络设备的第一指示信息，该第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，该第一RB关联一个主RLC实体和至多3个辅RLC实体；辅网络设备向终端设备发送3比特长度的第二指示信息，该第二指示信息指示上述第一RB关联的每一个辅RLC实体的状态，上述第一RB关联的不同辅RLC实体对应所述3比特中的不同比特。
通过实施第一方面所描述的方法，当为一个RB配置多于两个RLC实体(或逻辑信道)时，辅网络设备接收来自主网络设备的指示信息，辅网络设备可以根据该指示信息确定该无线承载关联的主RLC实体，从而可以准确地指示终端设备哪些RLC实体需要被激活和去激活，提升了数据传输的可靠性。
在第一方面的一种可能的实现方式中，辅网络设备接收来自主网络设备的配置信息，该配置信息指示在上述辅网络设备中第一RB关联的M个RLC实体，M为1、2或3。
在第一方面的一种可能的实现方式中，上述第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，具体包括：第一指示信息指示上述M个RLC实体中是否存在第一RB的主RLC实体；或，第一指示信息指示上述M个RLC实体中第一RB的辅RLC实体的个数；或，第一指示信息指示在上述主网络设备中第一RB关联的RLC实体中是否存在第一RB的主RLC实体；或第一指示信息指示上述M个RLC实体中的X个辅RLC实体的初始状态，X为 0、1、2或3。
在第一方面的一种可能的实现方式中，辅网络设备接收来自所述主网络设备的第三指示信息，该第三指示信息指示在上述主网络设备中第一RB关联的RLC实体的个数；或，该第三指示信息指示在上述主网络设备中第一RB关联的所有RLC实体的标识；或，该第三指示信息指示在上述主网络设备中第一RB关联的辅RLC实体的个数；或，该第三指示信息指示在上述主网络设备中第一RB关联的所有辅RLC实体的标识。
在第一方面的一种可能的实现方式中，上述第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，具体包括：第一指示信息指示在上述主网络设备中第一RB关联的每一个RLC实体是否为第一RB的主RLC实体。
在第一方面的一种可能的实现方式中，上述第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，具体包括：第一指示信息指示在上述主网络设备中第一RB关联的RLC实体的个数，和，在上述主网络设备中第一RB关联的辅RLC实体的个数。
在第一方面的一种可能的实现方式中，上述第一指示信息还指示第一RB的主RLC实体，具体包括：该第一指示信息指示在上述主网络设备中第一RB关联的每一个辅RLC实体的初始状态，和，在上述主网络设备中第一RB关联的RLC实体的个数。
在第一方面的一种可能的实现方式中，当第一RB关联的主RLC实体位于上述辅网络设备时，辅网络设备向主网络设备发送第四指示信息，该第四指示信息指示第一RB关联的主RLC实体的标识。
第二方面，本申请提供了一种数据传输的方法，该方法的执行主体为主网络设备或主网络设备中的一个模块。这里以主网络设备为执行主体为例进行描述。主网络设备向辅网络设备发送第一指示信息，该第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，该第一RB关联一个主RLC实体和至多3个辅RLC实体；主网络设备向终端设备发送第五指示信息，该第五指示信息指示第一RB的主RLC实体。
在第二方面的一种可能的实现方式中，主网络设备向辅网络设备发送配置信息，该配置信息指示在上述辅网络设备中第一RB关联的M个RLC实体，M为1、2或3。
在第二方面的一种可能的实现方式中，上述第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，具体包括：第一指示信息指示上述M个RLC实体中是否存在第一RB的主RLC实体；或，第一指示信息指示上述M个RLC实体中第一RB的辅RLC实体的个数；或，第一指示信息指示在上述主网络设备中第一RB关联的RLC实体中是否存在第一RB的主RLC实体；或第一指示信息指示上述M个RLC实体中的X个辅RLC实体的初始状态，X为0、1、2或3。
在第二方面的一种可能的实现方式中，主网络设备向辅网络设备发送第三指示信息，该第三指示信息指示在上述主网络设备中第一RB关联的RLC实体的个数；或，该第三指示信息指示在上述主网络设备中第一RB关联的所有RLC实体的标识；或，该第三指示信息指示在上述主网络设备中第一RB关联的辅RLC实体的个数；或，该第三指示信息指示在上述主网络设备中第一RB关联的所有辅RLC实体的标识。
在第二方面的一种可能的实现方式中，上述第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，具体包括：第一指示信息指示在上述主网络设备中第一RB关联的每一个RLC实体是否为第一RB的主RLC实体。
在第二方面的一种可能的实现方式中，上述第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，具体包括：第一指示信息指示在上述主网络设备中第一RB关联的RLC实体的个数，和，在上述主网络设备中第一RB关联的辅RLC实体的个数。
在第二方面的一种可能的实现方式中，上述第一指示信息还指示第一RB的主RLC实体，具体包括：该第一指示信息指示在上述主网络设备中第一RB关联的每一个辅RLC实体的初始状态，和，在上述主网络设备中第一RB关联的RLC实体的个数。
在第二方面的一种可能的实现方式中，当第一RB关联的主RLC实体位于上述辅网络设备时，主网络设备接收来自辅网络设备的第四指示信息，该第四指示信息指示第一RB关联的主RLC实体的标识。
第三方面，提供了一种通信装置，包括用于实现前述第一方面、第一方面的任意可能的实现方式中的方法的功能模块。
第四方面，提供了一种通信装置，包括用于实现前述第二方面、第二方面的任意可能的实现方式中的方法的功能模块。
第五方面，提供了一种通信装置，包括处理器和接口电路，接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发送给该通信装置之外的其它通信装置，该处理器通过逻辑电路或执行代码指令用于实现前述第一方面、第一方面的任意可能的实现方式中的方法。
第六方面，提供了一种通信装置，包括处理器和接口电路，该接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发送给该通信装置之外的其它通信装置，该处理器通过逻辑电路或执行代码指令用于实现前述第二方面、第二方面的任意可能的实现方式中的方法。
第七方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序或指令，当该计算机程序或指令被执行时，实现前述第一方面、第一方面的任意可能的实现方式中的方法。
第八方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序或指令，当该计算机程序或指令被执行时，实现前述第二方面、第二方面的任意可能的实现方式中的方法。
第九方面，提供了一种包含指令的计算机程序产品，当该指令被运行时，实现前述第一方面、第一方面的任意可能的实现方式中的方法。
第十方面，提供了一种包含指令的计算机程序产品，当该指令被运行时，实现前述第二方面、第二方面的任意可能的实现方式中的方法。
第十一方面，提供了一种计算机程序，该计算机程序包括代码或指令，当该代码或指令被运行时，实现前述第一方面、第一方面的任意可能的实现方式中的方法。
第十二方面，提供了一种计算机程序，该计算机程序包括代码或指令，当该代码或指令被运行时，实现前述第二方面、第二方面的任意可能的实现方式中的方法。
第十三方面，提供一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现前述第一方面和第二方面描述的至少一种方法。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第十四方面，提供一种通信系统，所述系统包括第三方面或者第五方面所述的装置(如 辅网络设备)、和第四方面或者第六方面所述的装置(如主网络设备)。
附图说明
图1a为本申请的实施例应用的通信系统的架构示意图；
图1b为本申请的实施例应用的CU和DU分离的示意图；
图2a为DC场景下实现PDCP duplication所涉及的网络架构；
图2b为CA场景下实现PDCP duplication所涉及的网络架构；
图3为CA场景下激活和去激活PDCP duplication的示意图；
图4a和图4b为DC+CA场景下实现PDCP duplication所涉及的网络架构；
图4c和图4d为第二指示信息的示例图；
图4e和图4f为DC+CA场景下实现PDCP duplication所涉及的网络架构；
图5至图8为本申请实施例提供的数据传输方法对应的流程示意图；
图9和图10为本申请的实施例提供的可能的通信装置的结构示意图。
具体实施方式
本申请实施例提供的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution,LTE)系统、第五代(5th generation,5G)移动通信系统、WiFi系统、未来的通信系统、或者多种通信系统融合的系统等，本申请实施例不做限定。其中，5G还可以称为新无线(new radio,NR)。
本申请实施例提供的技术方案可以应用于各种通信场景，例如可以应用于以下通信场景中的一种或多种：增强移动宽带(enhanced mobile broadband，eMBB)、超可靠低时延通信(ultra-reliable low-latency communication，URLLC)、机器类型通信(machine type communication，MTC)、大规模机器类型通信(massive machine type communications，mMTC)、设备到设备(device-to-device，D2D)、车辆外联(vehicle to everything，V2X)、车辆到车辆(vehicle to vehicle，V2V)、和物联网(internet of things，IoT)等。
本申请实施例提供的技术方案可以应用于通信设备间的通信。通信设备间的通信可以包括：网络设备和终端设备间的通信、网络设备和网络设备间的通信、和/或终端设备和终端设备间的通信。在本申请实施例中，术语“通信”还可以描述为“传输”、“信息传输”、或“信号传输”等。传输可以包括发送和/或接收。本申请实施例中，以网络设备和终端设备间的通信为例描述技术方案，本领域技术人员也可以将该技术方案用于进行其它调度实体和从属实体间的通信，例如宏基站和微基站之间的通信，例如第一终端设备和第二终端设备间的通信。其中，调度实体可以为从属实体分配空口资源。空口资源包括以下资源中的一种或多种：时域资源、频域资源、码资源和空间资源。在本申请实施例中，多种可以是两种、三种、四种或者更多种，本申请实施例不做限制。
在本申请实施例中，网络设备和终端设备间的通信包括：网络设备向终端设备发送下行信号/信息，和/或终端设备向网络设备发送上行信号/信息。
在本申请实施例中，“/”可以表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；“和/或”可以用于描述关联对象存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。其中A，B可以是单数或者复数。在 本申请实施例中，可以采用“第一”、“第二”等字样对功能相同或相似的技术特征进行区分。该“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。在本申请实施例中，“示例性的”或者“例如”等词用于表示例子、例证或说明，被描述为“示例性的”或者“例如”的实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
图1a是本申请的实施例可以应用的通信系统的架构示意图。如图1a所示，该通信系统中包括一个终端设备110和两个网络设备(如图1a中的辅网络设备120和主网络设备130)。图1a只是示意图，本申请的实施例对该通信系统中包括的网络设备和终端设备的数量不做限定。
本申请实施例涉及到的终端设备也可以称为终端、用户设备(user equipment，UE)、移动台、移动终端等。终端设备可以是手机、平板电脑、带无线收发功能的电脑、虚拟现实终端设备、增强现实终端设备、工业控制中的无线终端、无人驾驶中的无线终端、远程手术中的无线终端、智能电网中的无线终端、运输安全中的无线终端、智慧城市中的无线终端、智慧家庭中的无线终端等等。本申请的实施例对终端设备所采用的具体技术和具体设备形态不做限定。在本申请实施例中，用于实现终端设备的功能的装置可以是终端设备；也可以是能够支持终端设备实现该功能的装置，例如芯片系统，该装置可以被安装在终端设备中或者和终端设备匹配使用。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。本申请实施例提供的技术方案中，以用于实现终端设备的功能的装置是终端设备为例，描述本申请实施例提供的技术方案。
本申请实施例涉及到的网络设备是终端设备通过无线方式接入到该移动通信系统中的接入设备，可以是基站、演进型基站(evolved NodeB，eNodeB)、发送接收点(transmission reception point，TRP)、5G移动通信系统中的下一代基站(next generation NodeB，gNB)、未来移动通信系统中的基站或WiFi系统中的接入节点等；也可以是完成基站部分功能的模块或单元。
网络设备和终端设备之间的通信遵循一定的协议层结构，例如控制面协议层结构可以包括RRC层、分组数据汇聚层协议(packet data convergence protocol，PDCP)层、无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理层等协议层的功能；用户面协议层结构可以包括PDCP层、RLC层、MAC层和物理层等协议层的功能，在一种可能的实现中，PDCP层之上还可以包括业务数据适配协议(service data adaptation protocol，SDAP)层。
网络设备可以包括集中式单元(central unit，CU)和分布式单元(distributed unit，DU)。CU和DU之间的接口可以称为F1接口，如图1b所示。其中，控制面(control panel，CP)接口可以为F1-C，用户面(user panel，UP)接口可以为F1-U。CU和DU可以根据无线网络的协议层划分，比如PDCP层及以上协议层的功能设置在CU，PDCP层以下协议层(例如RLC层和MAC层等)的功能设置在DU。CU产生的信令可以通过DU发送给终端设备，或者终端设备产生的信令可以通过DU发送给CU。DU可以不对该信令进行解析而直接通过协议层封装后透传给终端设备或CU。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。在本申请实施例中，用于实现网络设备的功能的装置可以是网络设备；也 可以是能够支持网络设备实现该功能的装置，例如芯片系统，该装置可以被安装在网络设备中或者和网络设备匹配使用。在本申请实施例中，以用于实现网络设备的功能的装置是网络设备为例，描述本申请实施例提供的技术方案。
网络设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；可以部署在水面上；或者，可以部署在空中的飞机、气球或人造卫星上。本申请的实施例对网络设备和终端设备的应用场景不做限定。网络设备和终端设备之间可以通过授权频谱进行通信，可以通过非授权频谱进行通信，或者可以通过授权频谱和非授权频谱进行通信。网络设备和终端设备之间可以通过6千兆赫兹(gigahertz，GHz)以下的频谱进行通信，可以通过6GHz以上的频谱进行通信，或者可以使用6GHz以下的频谱和6GHz以上的频谱进行通信。本申请的实施例对网络设备和终端设备之间所使用的频谱资源不做限定。
在本申请实施例中，双连接(dual connectivity，DC)是指：终端设备同时连接两个网络设备。终端设备连接的两个网络设备可以是同一无线接入技术下的基站，例如都是LTE通信系统中的基站或都是5G移动通信系统中的基站，或者终端设备连接的两个基站也可以是不同的无线接入技术下的基站，例如一个是LTE通信系统中的基站，另一个是5G移动通信系统中的基站。
在本申请实施例中，载波聚合(carrier aggregation，CA)是指：将多个成员载波(component carrier，CC)聚合在一起为一个终端设备提供服务，实现更大的传输带宽，从而提高上下行传输速率。
终端设备和网络设备之间可以通过建立至少一个无线承载(radio bearer，RB)来传输数据。无线承载可以分为用于传输信令数据的信令无线承载(signalling radio bearer，SRB)和用于传输业务数据的数据无线承载(data radio bearer，DRB)。同一无线承载对应的一组功能实体集合包括一个分组数据汇聚协议(packet data convergence protocol,PDCP)实体、该PDCP实体对应的至少一个无线链路控制(radio link control，RLC)实体、至少一个RLC实体对应的至少一个媒体访问控制(medium access control,MAC)实体。其中，PDCP实体位于PDCP层，RLC实体位于RLC层，MAC实体位于MAC层。
在本申请实施例中，PDCP层的复制传输是指：将无线承载的数据包在PDCP层复制成多个相同的包(也就是复制包)，然后这复制的多个数据包分别递交给多个不同的RLC实体进行传输，具体的，每个RLC实体通过该RLC实体对应的逻辑信道(logical channel，LCH)将数据包传输到MAC层。需要注意的是，PDCP层的复制传输与通常所说的重传(retransmission)不同，重传是指同一个数据包传输失败后再一次传输，而PDCP层的复制传输是将一个数据包复制成多个数据包，分别通过多个逻辑信道进行传输。在本申请实施例中，PDCP层的复制传输也可以称为“PDCP duplication”、“PDCP复制”、“PDCP层复制”。
在本申请实施例中，PDCP duplication包括DC场景的PDCP duplication(也可以称为：DC duplication)和CA场景的PDCP duplication(也可以称为：CA duplication)。下面针对DC场景和CA场景，分别介绍的PDCP duplication的功能如何实现。
图2a示出了一种DC场景下实现PDCP duplication功能的网络架构。对于网络设备来说，DC场景涉及到主网络设备和辅网络设备。对于一个RB，在主网络设备中对应一个PDCP实体、一个RLC实体和一个MAC实体，在辅网络设备中对应一个RLC实体和一个MAC实体。对于该RB，在终端设备中对应一个PDCP实体、两个RLC实体和两个MAC实体。对于一个 RB，主网络设备在PDCP实体之上还可以有SDAP实体，终端设备在PDCP实体之上也还可以有SDAP实体。在DC场景下，一个终端设备同时连接两个网络设备，即主网络设备和辅网络设备，如果为某个RB配置了PDCP duplication功能，那么在PDCP层经过复制的两个相同的数据包将被传输给不同的两个RLC实体，并通过不同的逻辑信道分别传输给不同的两个MAC实体，最终形成两个MAC协议数据单元(protocol data unit，PDU)分别在两个不同的MAC实体各自调度的小区资源上进行传输。对于网络设备来说，主网络设备中的PDCP层会将经过复制的两个数据包传输给不同的两个RLC实体，这两个RLC实体分别位于主网络设备和辅网络设备中，之后，主网络设备中的RLC实体将接收的数据包传输给主网络设备中的MAC实体，辅网络设备中的RLC实体将接收的数据包传输给辅网络设备中的MAC实体，这两个MAC实体会通过各自的小区资源传输数据包，而对于终端设备来说，两个RLC实体和两个MAC实体都位于该终端设备中。示例性地，在DC场景下，可以有两个小区组为终端设备提供服务，分别为主小区组(master cell group，MCG)和辅小区组(secondary cell group，SCG)，其中，主小区组由主网络设备管理和配置，辅小区组由辅网络设备管理和配置。
图2b示出了一种CA场景下实现PDCP duplication功能的网络架构。在CA场景下，一个终端设备连接到一个网络设备，在同一个网络设备下至少有两个载波(或小区)为该终端设备服务。对于一个RB，在网络设备中对应一个PDCP实体、两个RLC实体和一个MAC实体。在终端设备中对应一个PDCP实体、两个RLC实体和一个MAC实体。当网络设备为一个无线承载配置了PDCP duplication功能时，在PDCP层经过复制的两个相同数据包将被传输给不同的两个RLC实体，并由这两个RLC实体通过不同的逻辑信道传输给同一个MAC实体。此时，由于两个相同的数据包传输到了同一个MAC实体中，MAC实体会将这两个数据包放到一个MAC PDU中传输，因此，为了使得这两个数据包通过两个小区分别传输，可以为逻辑信道配置一个参数，例如称为参数A，通过参数A的取值来指示不同的小区，从而保证这两个相同的数据包最终能形成两个MAC PDU在不同的小区上传输，从而提高可靠性。
当网络设备通过无线资源控制(radio resource control，RRC)信令为一个无线承载配置PDCP duplication功能时，可以指示该无线承载的PDCP duplication功能的初始状态是激活还是去激活。进一步地，网络设备还可以通过MAC控制元素(MAC control element，MAC CE)配置该无线承载的PDCP duplication功能的激活/去激活。
具体的，在图2a所示的DC场景下，当为一个无线承载配置的DC duplication功能被激活以后，PDCP层对数据包进行复制并通过两个逻辑信道传输；当为一个无线承载配置的DC duplication功能被去激活以后，则回退到DC分离承载(split bearer)，即，终端设备可以通过终端设备侧的两个逻辑信道分别向主网络设备和辅网络设备发送不同的数据包，或者，终端设备可以通过终端设备侧的两个逻辑信道接收分别来自主网络设备和辅网络设备的不同的数据包。
在图2b所示CA场景下，当为一个无线承载配置的CA duplication功能被去激活后，该无线承载中的逻辑信道和小区之间的关联关系也将不再适用。目前，CA duplication只限于一个无线承载通过两个逻辑信道来传输在PDCP层被复制的数据包(也俗称，两条腿(leg)的复制传输)。进一步地，还可以配置其中一条腿为主腿(primary leg)，比如逻辑信道1所在的腿为主腿。在本申请实施例中，主腿可以指主RLC实体，也可以指主RLC实 体关联的逻辑信道，也称作主逻辑信道；辅腿可以指辅RLC实体，也可以指辅RLC实体关联的逻辑信道，也称作辅逻辑信道。当CA duplication功能被激活时，如图3所示，来自逻辑信道1的数据只能在小区1或者小区2上传输(逻辑信道1关联小区1和小区2)，来自逻辑信道2的数据只能在小区3上传输(逻辑信道2关联小区3)；当CA duplication功能被去激活时，终端设备只能通过主逻辑信道1与网络设备传输数据。此时为了提高传输容量，逻辑信道1所配置的小区绑定关系不再适用，即逻辑信道1中的数据可以在与终端设备建立了无线连接的所有小区上传输。
图2a所示的DC场景和图2b所示的CA场景都是两个逻辑信道的PDCP duplication。为了进一步提高可靠性，引入了多于两个逻辑信道的PDCP duplication，例如可能通过三个或四个逻辑信道来传输在PDCP层被复制的数据包。
图4a示出了一种DC+CA场景下实现PDCP duplication功能的网络架构。如图4a所示，一个终端设备连接到主网络设备和辅网络设备。主网络设备下有两个载波(或小区)为该终端设备服务，辅网络设备下有两个载波(或小区)为该终端设备服务。对于一个RB，在主网络设备中对应一个PDCP实体、两个RLC实体和一个MAC实体，在辅网络设备中对应两个RLC实体和一个MAC实体。对应的，对应该RB，在终端设备中对应一个PDCP实体、四个RLC实体和两个MAC实体。在这种场景下，当主网络设备为一个无线承载配置了PDCP duplication功能时，在PDCP层经过复制的四个相同的数据包将被传输给不同的四个RLC实体，分别为RLC1、RLC2、RLC3和RLC4。其中，RLC1和RLC2分别通过逻辑信道1和逻辑信道2传输给同一个MAC实体，为MAC1；RLC3和RLC4分别通过逻辑信道3和逻辑信道4传输给同一个MAC实体，为MAC2。此时，四个相同的数据包中的两个数据包传输到了同一个MAC1中，MAC1会将这两个数据包在不同的小区上传输，另外两个相同的数据包传输到了同一个MAC2中，MAC2会将这两个数据包在不同的小区上传输，即，这四个相同的数据包分别在四个不同的小区上传输，从而可以进一步提升数据传输的可靠性。进一步的，网络设备为该无线承载配置一条主逻辑信道和一条分流辅逻辑信道，其中，主逻辑信道位于主网络设备，分流辅逻辑信道位于辅网络设备，或者，主逻辑信道位于辅网络设备，分流辅逻辑信道位于主网络设备。
当主网络设备或辅网络设备通过RRC信令为一个无线承载配置PDCP duplication功能时，可以指示该无线承载的PDCP duplication功能的初始状态是激活还是去激活。进一步地，主网络设备或辅网络设备还可以通过MAC CE指示终端设备该无线承载关联的RLC实体的激活/去激活状态。终端设备可以通过被激活的RLC实体与网络设备进行PDCP层的复制传输。当DC+CA场景下的PDCP duplication功能被去激活后，终端设备停止PDCP层的复制传输，终端设备可以通过终端设备的主逻辑信道和分流辅逻辑信道分别向主逻辑信道所在的网络设备和分流辅逻辑信道所在的网络设备发送不同的数据包，或者，终端设备可以通过终端设备的主逻辑信道和分流辅逻辑信道接收分别来自主逻辑信道所在的网络设备和分流辅逻辑信道所在的网络设备的不同的数据包。
在DC+CA场景下，主网络设备和辅网络设备如何指示终端设备使用该无线承载关联的至少一个RLC实体进行数据传输，是一个亟待解决的问题。
基于上述问题，本申请实施例提供一种数据传输的方法，当为无线承载配置多于两个RLC实体(或逻辑信道)时，辅网络设备基于主网络设备的指示信息来指示终端设备使用该 无线承载关联的至少一个RLC实体进行数据传输，或者，主网络设备基于辅网络设备的指示信息来指示终端设备使用该无线承载关联的至少一个RLC实体进行数据传输。
在本申请实施例中，由于一个RLC实体关联一个逻辑信道，一个逻辑信道关联一个RLC实体，MAC CE配置该无线承载关联的RLC实体的激活/去激活，也可以理解为：MAC CE配置该无线承载关联的逻辑信道的激活/去激活。
图5为本申请实施例提供的一种数据传输的方法的流程示意图，本实施例涉及的是辅网络设备、主网络设备和终端设备之间进行数据传输的具体过程。本实施例涉及的是无线承载关联的PDCP实体位于主网络设备的场景，图4a和图4b为该场景的两个示例。如图5所示，该方法可以包括：S501、S502和S503。其中，S501、S502和S503的执行顺序，本申请实施例不作限制。
S501、主网络设备向辅网络设备发送第一指示信息，对应的，辅网络设备接收来自主网络设备的第一指示信息。该第一指示信息指示第一RB的主RLC实体，该第一RB关联一个主RLC实体和至多3个辅RLC实体。可选的，第一指示信息可以承载在辅站添加请求(s-node addition request)消息上或承载在辅站修改请求(s-node modification request)消息上。
辅网络设备确定辅网络设备中第一RB关联的RLC实体。具体的，辅网络设备接收来自主网络设备的配置信息，该配置信息指示辅网络设备中第一RB关联的M个RLC实体，M为1或2，3。可选的，该配置信息承载在辅站添加请求消息或辅站修改请求消息上。
辅网络设备确定辅网络设备中第一RB关联的RLC实体后，确定第一RB关联的主RLC实体。在本申请实施例中，第一RB的主RLC实体有且仅有一个，即，第一RB的主RLC实体位于主网络设备，或，位于辅网络设备。第一指示信息指示第一RB的主RLC实体的方式包括以下4种方式中的任意一种。
方式1、第一指示信息指示上述M个RLC实体中是否存在第一RB的主RLC实体。
具体的，第一指示信息包括一个比特，当该比特的取值为“0”时，表示上述M个RLC实体中存在第一RB的主RLC实体(即，第一RB的主RLC实体位于辅网络设备)，当该比特的取值为“1”时，表示上述M个RLC实体中不存在第一RB的主RLC实体(即，第一RB的主RLC实体位于主网络设备)；或者，当该比特的取值为“1”时，表示上述M个RLC实体中存在第一RB的主RLC实体(即，第一RB的主RLC实体位于辅网络设备)，当该比特的取值为“0”时，表示上述M个RLC实体中不存在第一RB的主RLC实体(即，第一RB的主RLC实体位于主网络设备)。 方式2、第一指示信息指示上述M个RLC实体中第一RB的辅RLC实 体的个数。
具体的，第一指示信息包括两个比特，当该比特的取值为“00”时，表示上述M个RLC实体中第一RB的辅RLC实体的个数为0，当该比特的取值为“01”时，表示上述M个RLC实体中第一RB的辅RLC实体的个数为1，当该比特的取值为“10”时，表示上述M个RLC实体中第一RB的辅RLC实体的个数为2，当该比特的取值为“11”时，表示上述M个RLC实体中第一RB的辅RLC实体的个数为3。
在方式2中，若第一指示信息指示的第一RB的辅RLC实体的个数小于M，表示第一RB的主RLC实体位于辅网络设备；若第一指示信息指示的第一RB的辅RLC实体的个数等于M，表示第一RB的主RLC实体位于主网络设备。
示例性地，当辅网络设备根据第一指示信息确定上述M个RLC实体中第一RB的辅RLC实体的个数为1时，若M的取值为1，表示上述第一RB的主RLC实体位于主网络设备，若M的取值为2，表示辅网络设备中第一RB关联的2个RLC实体为1个辅RLC实体和1个主RLC实体，即，上述第一RB的主RLC实体位于辅网络设备。
方式3、第一指示信息指示在主网络设备中第一RB关联的RLC实体中是否存在第一RB 的主RLC实体。
一种可选的方式，第一指示信息包括一个比特，当该比特的取值为“0”时，表示主网络设备中第一RB关联的RLC实体中存在第一RB的主RLC实体(即，第一RB的主RLC实体位于主网络设备)，当该比特的取值为“1”时，表示主网络设备中第一RB关联的RLC实体中不存在第一RB的主RLC实体(即，第一RB的主RLC实体位于辅网络设备)；当该比特的取值为“1”时，表示主网络设备中第一RB关联的RLC实体中存在第一RB的主RLC实体(即，第一RB的主RLC实体位于主网络设备)，当该比特的取值为“0”时，表示主网络设备中第一RB关联的RLC实体中不存在第一RB的主RLC实体(即，第一RB的主RLC实体位于辅网络设备)。
另一种可选的方式，当第一RB的主RLC实体位于主网络设备时，第一指示信息指示第一RB的主RLC实体的索引或主RLC实体对应的逻辑信道的标识。
可选的，在方式1至方式3中，第一指示信息还指示第一RB关联的每一个辅RLC实体的初始状态。具体的，当第一RB关联j个辅RLC实体时，第一指示信息包括j比特，第一RB关联的不同辅RLC实体对应这j比特中的不同比特,其中，j为正整数，上述对应关系可以是预设的。上述j比特中的每个比特用于指示该比特对应的辅RLC实体的状态是激活(active)或去激活(inactive)。示例性地，当每个比特的取值为“0”时，表示该比特对应的辅RLC实体的初始状态为去激活,当每个比特的取值为“1”时，表示该比特对应的辅RLC实体的初始状态为激活；或者，当每个比特的取值为“1”时，表示该比特对应的辅RLC实体的初始状态为去激活,当每个比特的取值为“0”时，表示该比特对应的辅RLC实体的初始状态为激活。
方式4、第一指示信息指示上述M个RLC实体中的X个辅RLC实体的初始状态，X为 0、1、2、或3。在本申请实施例中，第一RB的主RLC实体的初始状态不需要指示。
具体的，由于第一RB的主RLC实体的初始状态是不需要指示的，所以，当第一指示信息指示2个RLC实体的初始状态时，表示上述第一RB的主RLC实体位于主网络设备。
示例性地，当第一指示信息指示1个RLC实体的初始状态时，若M的取值为1，表示上述第一RB的主RLC实体位于主网络设备；若M的取值为2，表示第一指示信息只指示了2个RLC实体中的一个RLC实体的初始状态，即，另一个没有被指示初始状态的RLC实体为主RLC实体，即，上述第一RB的主RLC实体位于辅网络设备；当第一指示信息没有指示任何一个RLC实体的初始状态，即X＝0时，表示上述第一RB的主RLC实体位于辅网络设备。
示例性地，当第一指示信息指示0个RLC实体的初始状态时，M的取值只能为1，表示辅网络设备中第一RB关联的唯一一个RLC实体为主RLC实体，即，上述第一RB的主RLC实体位于辅网络设备。
当第一指示信息使用上述4种方式的任意一种方式指示第一RB的主RLC实体时，辅网络设备可以根据第一指示信息和M的值，确定辅网络设备中第一RB关联的辅RLC实体个数 以及主RLC实体的个数。
可选的，在上述方式1至方式4中，主网络设备还向辅网络设备发送第三指示信息，对应的，辅网络设备接收来自主网络设备的第三指示信息。该第三指示信息可以承载在辅站添加请求消息或辅站修改请求消息上。第三指示信息与第一指示信息可以承载在相同的消息上或承载在不同的消息上。
辅网络设备根据第一指示信息和第三指示信息确定主网络设备中第一RB关联的辅RLC个数和主RLC个数。具体的，第三指示信息指示以下任意一项或多项：
a.在主网络设备中第一RB关联的RLC实体的个数；
b.在主网络设备中第一RB关联的所有RLC实体的标识；
c.在主网络设备中第一RB关联的辅RLC实体的个数；
d.在主网络设备中第一RB关联的所有辅RLC实体的标识；
e.第一RB关联的辅RLC实体的个数；
f.第一RB关联的所有辅RLC实体的标识；
g.第一RB关联的RLC实体的个数；
h.第一RB关联的所有RLC实体的标识。
当第三指示信息上述a项时，即，第三指示信息指示主网络设备中第一RB关联的所有RLC实体的个数为m(m＝1,2,3)时，若第一指示信息指示第一RB的主RLC实体位于辅网络设备，则辅网络设备可以推算出主网络设备中第一RB关联m个辅RLC实体，0个主RLC实体。若第一指示信息指示第一RB的主RLC实体位于主网络设备，则辅网络设备可以推算出主网络设备中第一RB关联m-1个辅RLC实体，1个主RLC实体。
当第三指示信息上述b项时，即，第三指示信息指示m(m＝1,2,3)个RLC实体的标识时，若第一指示信息指示第一RB的主RLC实体位于辅网络设备，则辅网络设备可以推算出主网络设备中第一RB关联m个辅RLC实体，0个主RLC实体。若第一指示信息指示第一RB的主RLC实体位于主网络设备，则辅网络设备可以推算出主网络设备中第一RB关联m-1个辅RLC实体，1个主RLC实体。
当第三指示信息上述c项时，即，第三指示信息指示主网络设备中第一RB关联的所有辅RLC实体的个数为n(n＝1,2,3)时，若第一指示信息指示第一RB的主RLC实体位于辅网络设备，则辅网络设备可以推算出主网络设备中第一RB关联n个辅RLC实体，0个主RLC实体。若第一指示信息指示主RLC实体位于主网络设备，则辅网络设备可以推算出主网络设备中第一RB关联n个辅RLC实体，1个主RLC实体。
当第三指示信息上述d项时，即，第三指示信息指示n个辅RLC实体的标识时，若第一指示信息指示第一RB的主RLC实体位于辅网络设备(此时，n＝1,2,3)，则辅网络设备可以推算出主网络设备中第一RB关联n个辅RLC实体，0个主RLC实体。若第一指示信息指示第一RB的主RLC实体位于主网络设备，则辅网络设备可以推算出主网络设备中第一RB关联n个辅RLC实体，1个主RLC实体。
当第三指示信息上述e项时，即，第三指示信息指示主网络设和辅网络设备中第一RB关联的所有辅RLC实体的个数为p(p＝2,3)时，若第一指示信息指示第一RB的主RLC实体位于辅网络设备，则辅网络设备可以推算出主网络设备中第一RB关联p-M+1个辅RLC实体，0个主RLC实体。若第一指示信息指示第一RB的主RLC实体位于主网络设备，则辅网络设 备可以推算出主网络设备中第一RB关联p-M个辅RLC实体，1个主RLC实体。
当第三指示信息上述f项时，即，第三指示信息指示主网络设和辅网络设备中第一RB关联的p(p＝2,3)个辅RLC实体的标识时，若第一指示信息指示第一RB的主RLC实体位于辅网络设备，则辅网络设备可以推算出主网络设备中第一RB关联p-M+1个辅RLC实体，0个主RLC实体。若第一指示信息指示第一RB的主RLC实体位于主网络设备，则辅网络设备可以推算出主网络设备中第一RB关联p-M个辅RLC实体，1个主RLC实体。
当第三指示信息上述g项时，即，第三指示信息指示主网络设和辅网络设备中第一RB关联的所有RLC实体的个数为q(p＝3,4)时，若第一指示信息指示第一RB的主RLC实体位于辅网络设备，则辅网络设备可以推算出主网络设备中第一RB关联q-M个辅RLC实体，0个主RLC实体。若第一指示信息指示第一RB的主RLC实体位于主网络设备，则辅网络设备可以推算出主网络设备中第一RB关联q-M-1个辅RLC实体，1个主RLC实体。
当第三指示信息上述h项时，即，第三指示信息指示主网络设和辅网络设备中第一RB关联的q(p＝3,4)个RLC实体的标识时，若第一指示信息指示第一RB的主RLC实体位于辅网络设备，则辅网络设备可以推算出主网络设备中第一RB关联q-M个辅RLC实体，0个主RLC实体。若第一指示信息指示第一RB的主RLC实体位于主网络设备，则辅网络设备可以推算出主网络设备中第一RB关联q-M-1个辅RLC实体，1个主RLC实体。
第一指示信息除了使用上述方式1至方式4指示第一RB的主RLC实体外，还可以采用以下5种方式中的任意一种方式指示第一RB的主RLC实体。
方式5、第一指示信息指示在主网络设备中第一RB关联的所有RLC实体的个数和/或 标识，和，在主网络设备中第一RB关联的所有辅RLC实体的个数和/或标识。
示例性地，第一指示信息指示在主网络设备中第一RB关联的所有RLC实体的个数为w(w＝1,2,3),第一指示信息还指示在主网络设备中第一RB关联的所有辅RLC实体的个数为v(v＝0,1,2)。当w>v时，表示第一RB关联的主RLC实体位于主网络设备，即，主网络设备中第一RB关联v个辅RLC实体，1个主RLC实体；当w＝v时，表示第一RB关联的主RLC实体位于辅网络设备，即，主网络设备中第一RB关联w个辅RLC实体，0个主RLC实体。
方式6、第一指示信息指示在主网络设备中第一RB关联的所有RLC实体的个数和/或 标识，和，在主网络设备中第一RB关联的主RLC实体的个数和/或标识。
示例性地，第一指示信息指示在主网络设备中第一RB关联的所有RLC实体的个数为w(w＝1,2,3),第一指示信息还指示在主网络设备中第一RB关联的主RLC实体的个数为v’(v’＝0,1)。当v’＝1时，表示第一RB关联的主RLC实体位于主网络设备，即，主网络设备中第一RB关联w-1个辅RLC实体，1个主RLC实体；当v’＝0时，表示第一RB关联的主RLC实体位于辅网络设备，即，主网络设备中第一RB关联w个辅RLC实体，0个主RLC实体。
方式7、第一指示信息指示在主网络设备中第一RB关联的每一个辅RLC实体的初始状 态，和，在主网络设备中第一RB关联的所有RLC实体的个数和/或标识。
具体的，第一指示信息指示r(r＝0,1,2，3)个RLC实体的初始状态,第一指示信息还指示在主网络设备中第一RB关联的所有RLC实体的个数为s(s＝1,2,3)。当r<s时，表示第一RB关联的主RLC实体位于主网络设备，即，主网络设备中第一RB关联r个辅RLC实体，1个主RLC实体；当r＝s时，表示第一RB关联的主RLC实体位于辅网络设备，即，主网络 设备中第一RB关联r个辅RLC实体，0个主RLC实体。
方式8、第一指示信息指示在辅网络设备中第一RB关联的每一个辅RLC实体的初始状 态，和，在主网络设备中第一RB关联的所有RLC实体的个数和/或标识。
具体的，第一指示信息指示r’(r＝0,1,2，3)个RLC实体的初始状态,第一指示信息还指示在主网络设备中第一RB关联的所有RLC实体的个数为s(s＝1,2,3)。当r’＝M时，表示第一RB关联的主RLC实体位于主网络设备，即，主网络设备中第一RB关联s-1个辅RLC实体，1个主RLC实体；当r’<M时，表示第一RB关联的主RLC实体位于辅网络设备，即，主网络设备中第一RB关联s个辅RLC实体，0个主RLC实体。
方式9、第一指示信息指示在主网络设备中第一RB关联的每一个RLC实体是否为第一 RB的主RLC实体。
具体的，第一指示信息包括h比特，h为正整数。主网络设备中第一RB关联的不同RLC实体对应这h比特中的不同比特，上述对应关系可以是预设的。上述h比特中的每个比特用于指示该比特对应的RLC实体是否为主RLC实体。示例性地，当每个比特的取值为“0”时，表示该比特对应的RLC实体为主RLC实体,当每个比特的取值为“1”时，表示该比特对应的RLC实体不为主RLC实体；或者，当每个比特的取值为“1”时，表示该比特对应的RLC实体为主RLC实体,当每个比特的取值为“0”时，表示该比特对应的RLC实体不为主RLC实体。
可选的，辅网络设备接收到上述第一指示信息后，向主网络设备发送第四指示信息，对应的，主网络设备接收来自辅网络设备的第四指示信息。可选的，该第四指示信息可以承载在辅站添加请求确认(s-node addition request acknowledge)消息上或承载在辅站修改请求确认(s-node modification request acknowledge)消息上。
当第一RB关联的主RLC实体位于辅网络设备时，该第四指示信息指示辅网络设备中第一RB关联的RLC实体中的一个RLC实体为第一RB关联的主RLC实体。例如，该第四指示信息指示第一RB关联的主RLC实体的索引，或，第四指示信息指示第一RB关联的主RLC实体所关联的逻辑信道(也称第一RB的主逻辑信道)的标识。其中，第一RB关联的主RLC实体为辅网络设备确定的。
当第一RB关联的主RLC实体位于主网络设备时，第四指示信息指示在辅网络设备中第一RB关联的分流辅RLC实体。例如，该第四指示信息指示第一RB关联的分流辅RLC实体的索引，或，第一RB关联的分流辅RLC实体关联的逻辑信道的标识。其中，第一RB关联的分流辅RLC实体关联的逻辑信道称作分流辅逻辑信道(也称：split secondary path)。当第一RB的PDCP duplication功能被去激活时，终端设备可以通过位于主网络设备的主逻辑信道与主网络设备进行数据传输，或者，终端设备可以通过位于辅网络设备的分流辅逻辑信道与辅网络设备进行数据传输。
可选的，步骤S501可以被步骤S501a替换。
S501a、主网络设备向辅网络设备发送第一指示信息，对应的，辅网络设备接收来自主网络设备的第一指示信息。该第一指示信息用于请求辅网络设备建立第一RB的主RLC实体，或，该第一指示信息用于请求辅网络设备建立第一RB的分流辅RLC实体。可选的，第一指示信息可以承载在辅站添加请求(s-node addition request)消息上或承载在辅站修改请求(s-node modification request)消息上。
辅网络设备确定辅网络设备中第一RB关联的RLC实体。具体的，辅网络设备接收来自主网络设备的配置信息，该配置信息指示辅网络设备中第一RB关联的M个RLC实体，M为1或2，3。可选的，该配置信息承载在辅站添加请求消息或辅站修改请求消息上。
辅网络设备确定辅网络设备中第一RB关联的RLC实体后，确定第一RB关联的主RLC实体。具体的，当第一指示信息用于请求建立第一RB的主RLC实体时，表示第一RB的主RLC实体位于辅网络设备，当第一指示信息用于请求建立第一RB的分流辅RLC实体时，表示第一RB的主RLC实体位于主网络设备。一种可选的方式，第一指示信息包括一个比特，当该比特的取值为“0”时，表示第一指示信息用于请求建立第一RB的主RLC实体，当该比特的取值为“1”时，表示第一指示信息用于请求建立第一RB的分流辅RLC实体；或者，当该比特的取值为“1”时，表示第一指示信息用于请求建立第一RB的主RLC实体，当该比特的取值为“0”时，表示第一指示信息用于请求建立第一RB的分流辅RLC实体。
可选的，主网络设备还向辅网络设备发送第三指示信息，对应的，辅网络设备接收来自主网络设备的第三指示信息。关于第三指示信息的描述参见步骤S501，这里不再赘述。
辅网络设备接收到上述第一指示信息后，向主网络设备发送第四指示信息，对应的，主网络设备接收来自辅网络设备的第四指示信息。关于第四指示信息的描述参见步骤S501，这里不再赘述。
S502、主网络设备向终端设备发送第五指示信息，对应的，终端设备接收来自主网络设备的第五指示信息，该第五指示信息可以承载在RRC重配置消息上，该第五指示信息指示第一RB关联的主RLC实体。例如，第五指示信息指示第一RB关联的主RLC实体的索引，或，第五指示信息指示第一RB关联的主RLC实体所关联的逻辑信道的标识。终端设备根据该第五指示信息确定第一RB关联的主RLC实体。
可选的，第五指示信息还指示第一RB关联的所有辅RLC实体的初始状态。可选的，第五指示信息还指示第一RB关联的分流辅RLC实体的标识或分流辅RLC实体所关联的逻辑信道的标识。
可选的，步骤S502也可以被替换为S502a。
S502a、辅网络设备向终端设备发送上述第五指示信息。对应的，终端设备接收来自辅网络设备的第五指示信息。该第五指示信息可以承载在RRC重配置消息上，该第五指示信息指示第一RB关联的主RLC实体的索引/第一RB关联的主RLC实体所关联的逻辑信道的标识、第一RB关联的分流辅RLC实体的索引/第一RB关联的分流辅RLC实体关联的逻辑信道的标识、和第一RB关联的所有辅RLC实体的初始状态中的任意一项或多项。
S503、辅网络设备向终端设备发送3比特长度的第二指示信息，对应的，终端设备接收来自辅网络设备的3比特长度的第二指示信息。该第二指示信息指示上述第一RB关联的所有辅RLC实体的每一个辅RLC实体的状态，其中，该第一RB关联的不同RLC实体对应所述3比特中的不同比特。可选的，该第二指示信息承载在一个MAC CE中。
下面介绍上述3比特中的每一个比特与第一RB关联的所有辅RLC实体的每一个辅RLC实体的对应关系。具体的，该对应关系可以是协议预设的。示例性地的，上述对应关系满足以下两个原则：
原则一、上述3比特中，从低比特位到高比特位，依次排列第一RB在主网络设备中的辅RLC实体的使用状态和第一RB在辅网络设备中的辅RLC实体的使用状态。即，在上述3 比特中，低比特位用于指示第一RB在主网络设备中的辅RLC实体的使用状态，高比特位用于指示第一RB在辅网络设备中的辅RLC实体的使用状态。
原则二、对于同一个网络设备的辅RLC实体，在上述3比特中，从低比特位到高比特位，依次排列逻辑信道标识低的逻辑信道对应的RLC实体和逻辑信道标识高的逻辑信道对应的RLC实体。即，在上述3比特中，低比特位用于指示第一RB关联的逻辑信道标识低的逻辑信道所对应的RLC实体的使用状态，高比特位用于指示第一RB关联的逻辑信道标识高的逻辑信道所对应的RLC实体的使用状态。
示例性地，当第一RB一共关联3个辅RLC实体和1个主RLC实体时，如图4a所示，假设LCH1的标识<LCH2的标识<LCH3的标识<LCH4的标识。当RLC1为主RLC实体时，如图4c所示，上述3个比特的第三个比特表示RLC2的状态，第二个比特表示RLC3的状态，第一个比特表示RLC4的状态；当RLC2为主RLC实体时，上述3个比特的第三个比特表示RLC1的状态，第二个比特表示RLC3的状态，第一个比特表示RLC4的状态；当RLC3为主RLC实体时，上述3个比特的第三个比特表示RLC1的状态，第二个比特表示RLC2的状态，第一个比特表示RLC4的状态；当RLC4为主RLC实体时，上述3个比特的第三个比特表示RLC1的状态，第二个比特表示RLC2的状态，第一个比特表示RLC3的状态。
示例性地，当第一RB一共关联2个辅RLC实体和1个主RLC实体时，如图4b所示，假设LCH1的标识<LCH3的标识<LCH4的标识。当RLC1为主RLC实体时，如图4d所示，上述3个比特的第三个比特表示RLC3的状态，第二个比特表示RLC4的状态，第一个比特空置；当RLC3为主RLC实体时，上述3个比特的第三个比特表示RLC1的状态，第二个比特表示RLC4的状态，第一个比特空置；当RLC4为主RLC实体时，上述3个比特的第三个比特表示RLC1的状态，第二个比特表示RLC3的状态，第一个比特空置。
终端设备根据上述3个比特中的每一个比特的值确定该比特对应的辅RLC实体的状态。
一种可选的方式，当上述3比特的其中任意比特的取值为“0”时，表示该比特对应的辅RLC实体的状态为去激活，或者，也可以理解为：表示该比特对应的辅RLC实体关联的逻辑信道的状态为去激活；当上述3比特的其中任意比特的取值为“1”时，表示该比特对应的辅RLC实体的状态为激活，或者，也可以理解为：表示该比特对应的辅RLC实体关联的逻辑信道的状态为激活。
另一种可选的方式，当上述3比特的其中任意比特的取值为“1”时，表示该比特对应的辅RLC实体的状态为去激活，或者，也可以理解为：表示该比特对应的辅RLC实体关联的逻辑信道的状态为去激活；当上述3比特的其中任意比特的取值为“0”时，表示该比特对应的辅RLC实体的状态为激活，或者，也可以理解为：表示该比特对应的辅RLC实体关联的逻辑信道的状态为激活。
当第一RB关联的任意一个辅RLC实体状态为激活时，辅RLC实体被允许用于PDCP duplication，即终端设备可以通过该辅RLC实体关联的逻辑信道与网络设备进行PDCP层的复制传输；当第一RB关联的任意一个辅RLC实体状态为去激活时，辅RLC实体不被允许用于PDCP duplication，即终端设备不可以通过该辅RLC实体关联的逻辑信道与网络设备进行PDCP层的复制传输。
当第一RB关联的所有辅RLC实体状态为去激活时，终端设备停止第一RB的PDCP duplication功能，进行分流传输操作。具体的，终端设备根据分流传输的门限确定是否通 过第一RB的主逻辑信道和第一RB的分流辅逻辑信道分别向主逻辑信道所在的网络设备和分流辅逻辑信道所在的网络设备传输不同的数据包。具体的，当待发送数据量小于分流传输的门限时，终端设备通过第一RB的主逻辑信道向该主逻辑信道所在的网络设备进行传输；当待发送数据量大于或等于分流传输的门限时，终端设备通过第一RB的主逻辑信道和第一RB的分流辅逻辑信道分别向该主逻辑信道所在的网络设备和该分流辅逻辑信道所在的网络设备发送不同的数据包。
终端设备根据第二指示信息确定第一RB关联的所有辅RLC实体的状态后，激活或去激活对应的辅RLC实体，以及，辅RLC实体对应的逻辑信道，从而和主网络设备和辅网络设备进行数据传输。
上述实施例提供了一种数据传输的方法，当为无线承载配置多于两个RLC实体(或逻辑信道)时，辅网络设备接收来自主网络设备的指示信息，辅网络设备可以根据该指示信息确定该无线承载关联的主RLC实体，从而可以准确地指示终端设备哪些RLC实体需要被激活和去激活，提升了数据传输的可靠性。
图6为本申请实施例提供的一种数据传输的方法的流程示意图，本实施例涉及的是辅网络设备、主网络设备和终端设备之间进行数据传输的具体过程。本实施例涉及的是无线承载关联的PDCP实体位于辅网络设备的场景，图4e和4f为该场景的两个示例。如图6所示，该方法可以包括：S601、S602和S603。其中，S601、S602和S603的执行顺序，本申请实施例不作限制。
S601、辅网络设备向主网络设备发送第一指示信息，对应的，主网络设备接收来自辅网络设备的第一指示信息。该第一指示信息指示第一RB的主RLC实体，该第一RB关联一个主RLC实体和至多3个辅RLC实体。可选的，第一指示信息承载在辅站添加请求确认(s-node addition request acknowledge)消息、辅站修改请求确认(s-node modification request acknowledge)消息、或辅站修改请求消息(s-node modification required)上。
主网络设备确定主网络设备中第一RB关联的RLC实体。主网络设备接收来自辅网络设备的配置信息，该配置信息指示主网络设备中第一RB关联的K个RLC实体，K为1、2或3。可选的，该配置信息承载在辅站添加请求确认消息、辅站修改请求确认消息、或辅站修改请求消息上。
主网络设备确定主网络设备中第一RB关联的RLC实体后，确定第一RB关联的主RLC实体。其中，第一指示信息指示第一RB的主RLC实体的方式包括以下4种方式中的任意一种。
方式1、第一指示信息指示上述K个RLC实体中是否存在第一RB的主RLC实体。
具体的，第一指示信息包括1个比特，当该比特的取值为“0”时，表示上述K个RLC实体中存在第一RB的主RLC实体(即，第一RB的主RLC实体位于主网络设备)，当该比特的取值为“1”时，表示上述K个RLC实体中不存在第一RB的主RLC实体(即，第一RB的主RLC实体位于辅网络设备)；或者，当该比特的取值为“1”时，表示上述K个RLC实体中存在第一RB的主RLC实体(即，第一RB的主RLC实体位于主网络设备)，当该比特的取值为“0”时，表示上述K个RLC实体中不存在第一RB的主RLC实体(即，第一RB的主RLC实体位于辅网络设备)。
方式2、第一指示信息指示上述K个RLC实体中第一RB的辅RLC实体的个数。
具体的，第一指示信息包括两个比特，当该比特的取值为“00”时，表示上述K个RLC实体中第一RB的辅RLC实体的个数为0，当该比特的取值为“01”时，表示上述K个RLC实体中第一RB的辅RLC实体的个数为1，当该比特的取值为“10”时，表示上述K个RLC实体中第一RB的辅RLC实体的个数为2，当该比特的取值为“11”时，表示上述K个RLC实体中第一RB的辅RLC实体的个数为3。
在方式2中，若第一指示信息指示的第一RB的辅RLC实体的个数小于K，表示第一RB的主RLC实体位于主网络设备；若第一指示信息指示的第一RB的辅RLC实体的个数等于K，表示第一RB的主RLC实体位于辅网络设备。
示例性地，当主网络设备根据第一指示信息确定上述K个RLC实体中第一RB的辅RLC实体的个数为1时，若K的取值为1，表示上述第一RB的主RLC实体位于辅网络设备，若K的取值为2，表示主网络设备中第一RB关联的2个RLC实体为1个辅RLC实体和1个主RLC实体，即，上述第一RB的主RLC实体位于主网络设备。
方式3、第一指示信息指示在辅网络设备中第一RB关联的RLC实体中是否存在第一RB 的主RLC实体。
一种可选的方式，第一指示信息包括1个比特，当该比特的取值为“0”时，表示辅网络设备中第一RB关联的RLC实体中存在第一RB的主RLC实体(即，第一RB的主RLC实体位于辅网络设备)，当该比特的取值为“1”时，表示辅网络设备中第一RB关联的RLC实体中不存在第一RB的主RLC实体(即，第一RB的主RLC实体位于主网络设备)；当该比特的取值为“1”时，表示辅网络设备中第一RB关联的RLC实体中存在第一RB的主RLC实体(即，第一RB的主RLC实体位于辅网络设备)，当该比特的取值为“0”时，表示辅网络设备中第一RB关联的RLC实体中不存在第一RB的主RLC实体(即，第一RB的主RLC实体位于主网络设备)。
另一种可选的方式，当第一RB的主RLC实体位于辅网络设备时，第一指示信息指示第一RB的主RLC实体的索引或第一RB的主RLC实体关联的逻辑信道的标识。
可选的，在方式1至方式3中，第一指示信息还指示第一RB关联的每一个辅RLC实体的初始状态。具体描述参加步骤S501，这里不再赘述。
方式4、第一指示信息指示上述K个RLC实体中的Y个RLC实体的初始状态，Y为0、 1、2或3。
具体的，由于第一RB的主RLC实体主RLC实体的初始状态是不需要指示的，所以，当第一指示信息指示2个RLC实体的初始状态时，表示上述第一RB的主RLC实体位于辅网络设备。
示例性地，当第一指示信息指示1个RLC实体的初始状态时，若K的取值为1，表示上述第一RB的主RLC实体位于辅网络设备，若K的取值为2，表示第一指示信息只指示了2个RLC实体中的一个RLC实体的初始状态，即，另一个没有被指示初始状态的RLC实体为主RLC实体，即，上述第一RB的主RLC实体位于主网络设备。
示例性地，当第一指示信息指示0个RLC实体的初始状态时，K的取值只能为1，表示主网络设备中第一RB关联的唯一一个RLC实体为主RLC实体，即，上述第一RB的主RLC实体位于主网络设备。
当第一指示信息使用上述4种方式的任意一种方式指示第一RB的主RLC实体时，主网络设备可以根据第一指示信息和K的值，确定主网络设备中第一RB关联的辅RLC实体个数以及主RLC实体的个数。
可选的，在上述方式1至方式4中，主网络设备还向辅网络设备发送第三指示信息，对应的，辅网络设备接收来自主网络设备的第三指示信息。可选的，第三指示信息承载在辅站添加请求确认消息、辅站修改请求确认、或辅站修改请求消息上。第三指示信息可以与第一指示信息承载在相同的消息上或承载在不同的消息上。
第三指示信息还可以指示以下任意一项或多项：
a.在辅网络设备中第一RB关联的RLC实体的个数；
b.在辅网络设备中第一RB关联的所有RLC实体的标识；
c.在辅网络设备中第一RB关联的辅RLC实体的个数；
d.在辅网络设备中第一RB关联的所有辅RLC实体的标识；
e.第一RB关联的辅RLC实体的个数；
f.第一RB关联的所有辅RLC实体的标识；
g.第一RB关联的RLC实体的个数；
h.第一RB关联的所有RLC实体的标识。
第一指示信息除了使用上述方式1至方式4指示第一RB的主RLC实体外，还可以采用以下5种方式中的任意一种方式指示第一RB的主RLC实体。
方式5、第一指示信息指示在辅网络设备中第一RB关联的所有RLC实体的个数和/或 标识，和，在辅网络设备中第一RB关联的所有辅RLC实体的个数和/或标识。
方式6、第一指示信息指示在辅网络设备中第一RB关联的所有RLC实体的个数和/或 标识，和，在辅网络设备中第一RB关联的所有主RLC实体的个数和/或标识。
方式7、第一指示信息指示在辅网络设备中第一RB关联的每一个辅RLC实体的初始状 态，和，在辅网络设备中第一RB关联的所有RLC实体的个数和/或标识。
方式8、第一指示信息指示在主网络设备中第一RB关联的每一个辅RLC实体的初始状 态，和，在辅网络设备中第一RB关联的所有RLC实体的个数和/或标识。
方式9、第一指示信息指示在辅网络设备中第一RB关联的每一个RLC实体是否为第一 RB的主RLC实体。
其中，方式5至方式9的具体指示方式与S501中的方式5至方式9类似，只需要将“主网络设备”与“辅网络设备”互换，这里不再赘述。
可选的，主网络设备接收到上述第一指示信息后，向辅网络设备发送第四指示信息，对应的，辅网络设备接收来自主网络设备的第四指示信息。可选的，该第四指示信息可以承载在辅站添加请求确认消息上或承载在辅站修改请求确认消息上。
当第一RB关联的主RLC实体位于主网络设备时，该第四指示信息指示主网络设备中第一RB关联的RLC实体中的一个RLC实体为第一RB关联的主RLC实体。例如，该第四指示信息指示第一RB关联的主RLC实体的索引，或，第四指示信息指示第一RB关联的主RLC实体所关联的逻辑信道(也称第一RB的主逻辑信道)的标识。其中，第一RB关联的主RLC实体为主网络设备确定的。
当第一RB关联的主RLC实体位于辅网络设备时，第四指示信息指示在主网络设备中第 一RB关联的分流辅RLC实体。例如，该第四指示信息指示第一RB关联的分流辅RLC实体的索引，或，第一RB关联的分流辅RLC实体关联的逻辑信道的标识。其中，第一RB关联的分流辅RLC实体关联的逻辑信道称作分流辅逻辑信道(也称：split secondary path)。当第一RB的PDCP duplication功能被去激活时，终端设备可以通过位于辅网络设备的主逻辑信道与辅网络设备进行数据传输，或者，终端设备可以通过位于主网络设备的分流辅逻辑信道与主网络设备进行数据传输。
可选的，步骤S601可以被步骤S601a替换。
S601a、辅网络设备向主网络设备发送第一指示信息，对应的，主网络设备接收来自辅网络设备的第一指示信息。该第一指示信息用于请求主网络设备建立第一RB的主RLC实体，或，该第一指示信息用于请求主网络设备建立第一RB的分流辅RLC实体。可选的，第一指示信息承载在辅站添加请求确认(s-node addition request acknowledge)消息或辅站修改请求确认(s-node modification request acknowledge)消息上。
主网络设备确定主网络设备中第一RB关联的RLC实体。主网络设备接收来自辅网络设备的配置信息，该配置信息指示主网络设备中第一RB关联的K个RLC实体，K为1、2或3。可选的，该配置信息承载在辅站添加请求确认消息或辅站修改请求确认消息上。
主网络设备确定主网络设备中第一RB关联的RLC实体后，确定第一RB关联的主RLC实体。具体的，当第一指示信息用于请求建立第一RB的主RLC实体时，表示第一RB的主RLC实体位于主网络设备，当第一指示信息用于请求建立第一RB的分流辅RLC实体时，表示第一RB的主RLC实体位于辅网络设备。一种可选的方式，第一指示信息包括一个比特，当该比特的取值为“0”时，表示第一指示信息用于请求建立第一RB的主RLC实体，当该比特的取值为“1”时，表示第一指示信息用于请求建立第一RB的分流辅RLC实体；或者，，当该比特的取值为“1”时，表示第一指示信息用于请求建立第一RB的主RLC实体，当该比特的取值为“0”时，表示第一指示信息用于请求建立第一RB的分流辅RLC实体。
可选的，辅网络设备还向主网络设备发送第三指示信息，对应的，主网络设备接收来自辅网络设备的第三指示信息。关于第三指示信息的描述参见步骤S601，这里不再赘述。
主网络设备接收到上述第一指示信息后，向辅网络设备发送第四指示信息，对应的，辅网络设备接收来自主网络设备的第四指示信息。关于第四指示信息的描述参见步骤S601，这里不再赘述。
S602、辅网络设备向终端设备发送第五指示信息，对应的，终端设备接收来自辅网络设备的第五指示信息，该第五指示信息可以是RRC重配置消息，该第五指示信息指示第一RB关联的主RLC实体。例如，第五指示信息指示第一RB关联的主RLC实体的标识，或，第五指示信息指示第一RB关联的主RLC实体所关联的逻辑信道的标识。终端设备根据该第五指示信息确定第一RB关联的主RLC实体。
可选的，第五指示信息还指示第一RB关联的所有辅RLC实体的初始状态。可选的，第五指示信息还指示第一RB关联的分流辅RLC实体的标识或分流辅RLC实体所关联的逻辑信道的标识。
可选的，步骤S602也可以被替换为S602a。
S602a、主网络设备向终端设备发送上述第五指示信息。对应的，终端设备接收来自辅网络设备的第五指示信息。该第五指示信息可以承载在RRC重配置消息上，该第五指示信 息指示第一RB关联的主RLC实体的索引/第一RB关联的主RLC实体所关联的逻辑信道的标识、第一RB关联的分流辅RLC实体的索引/第一RB关联的分流辅RLC实体关联的逻辑信道的标识、和第一RB关联的所有辅RLC实体的初始状态中的任意一项或多项。
S603、主网络设备向终端设备发送3比特长度的第二指示信息，对应的，终端设备接收来自主网络设备的3比特长度的第二指示信息。该第二指示信息指示上述第一RB关联的所有辅RLC实体的每一个辅RLC实体的状态。其中，该第一RB关联的不同RLC实体对应所述3比特中的不同比特。可选的，该第二指示信息承载在一个MAC CE中。
上述3比特中的每一个比特与第一RB关联的所有辅RLC实体的每一个辅RLC实体的对应关系。具体对应规则参见步骤S503，这里不再赘述。
终端设备根据上述3个比特中的每一个比特的值确定该比特对应的辅RLC实体的状态。具体描述参加步骤S503，这里不再赘述。
上述实施例提供了一种数据传输的方法，当为无线承载配置多于两个RLC实体(或逻辑信道)时，主网络设备接收来自辅网络设备的指示信息，主网络设备可以根据该指示信息确定该无线承载关联的主RLC实体，从而可以准确地指示终端设备哪些RLC实体需要被激活和去激活，提升了数据传输的可靠性。
图7为本申请实施例提供的一种数据传输的方法的流程示意图。图7所示的实施例适用于DC+CA场景下实现PDCP duplication功能的网络架构，其中，网络设备的CU和DU是分离的。本实施例涉及的是第一DU、CU和终端设备之间进行数据传输的具体过程，其中，无线承载关联的PDCP实体位于第二DU，即，第二DU包括PDCP实体、RLC实体和MAC实体，第一DU包括RLC实体和MAC实体。在图7所示的实施例中，当CU分离为控制面CU实体(即CU-CP实体)和用户面CU实体(即CU-UP实体)时，由CU-CP来实现本实施例中CU的操作。
如图7所示，该方法可以包括：S701、S702和S703。其中，S701、S702和S703的执行顺序，本申请实施例不作限制。
S701、CU向第一DU发送第一指示信息，对应的，第一DU接收来自CU的第一指示信息。该第一指示信息指示第一RB的主RLC实体。该第一RB关联一个主RLC实体和至多3个辅RLC实体。可选的，第一指示信息承载在上下文建立请求(context setup request)消息，或上下文修改请求(context modification request)消息。
第一DU确定第一DU中第一RB关联的RLC实体。具体的，第一DU接收来自CU的配置信息，该配置信息指示第一DU中第一RB关联的M个RLC实体，其中，M为1、2或3。该配置信息可以承载在上下文建立请求消息上，或承载在上下文修改请求消息上。
第一DU确定第一DU中第一RB关联的RLC实体后，确定第一RB关联的主RLC实体。第一RB的主RLC实体有且仅有一个，即，第一RB的主RLC实体位于第一DU，或，位于第二DU。第一指示信息指示第一RB的主RLC实体的方式参见图5所示实施例中的步骤S501中的描述，只需把S501的方式1至方式4中的“辅网络设备”替换为第一DU，“主网络设备”替换为第二DU，这里不再赘述。
可选的，在上述方式1至方式4中，CU还向第一DU发送第三指示信息，对应的，第一DU接收来自CU的第三指示信息。该第三指示信息可以承载在上下文建立请求消息或上下文 修改请求消息上。具体的，关于第三指示信息的描述参见S501，只需把“辅网络设备”替换为第一DU，把“主网络设备”替换为第二DU，这里不再赘述。
第一指示信息除了使用上述方式1至方式4指示第一RB的主RLC实体外，还可以采用S501中的方式5至方式9中的任意一种方式指示第一RB的主RLC实体，只需要把方式5至方式9中的“辅网络设备”替换为第一DU，把“主网络设备”替换为第二DU，这里不再赘述。
可选的，第一DU接收到上述第一指示信息后，向CU发送第四指示信息，对应的，CU接收来自第一DU的第四指示信息。可选的，第四指示信息可以承载在上下文建立回复(context setup response)消息上，或上下文修改回复(context modification response)消息上。
当第一RB关联的主RLC实体位于第一DU时，该第四指示信息指示第一DU中第一RB关联的RLC实体中的一个RLC实体为第一RB关联的主RLC实体。例如，该第四指示信息指示第一RB关联的主RLC实体的标识，或，第四指示信息指示第一RB关联的主RLC实体所关联的逻辑信道(也称第一RB的主逻辑信道)的标识。其中，第一RB关联的主RLC实体为第一DU确定的。
当第一RB关联的主RLC实体位于第二DU时，第四指示信息指示在第一DU中第一RB关联的分流辅RLC实体。例如，该第四指示信息指示第一RB关联的分流辅RLC实体的索引，或，第一RB关联的分流辅RLC实体关联的逻辑信道的标识。其中，，第一RB关联的分流辅RLC实体关联的逻辑信道称作分流辅逻辑信道(也称：split secondary path)。当第一RB的PDCP duplication功能被去激活时，终端设备可以通过位于第二DU的主逻辑信道与第二DU进行数据传输，或者，终端设备可以通过位于第一DU的分流辅逻辑信道与第一DU进行数据传输。
可选的，步骤S701可以被步骤S701a替换。
S701a、CU向第一DU发送第一指示信息，对应的，第一DU接收来自CU的第一指示信息。该第一指示信息用于请求第一DU建立第一RB的主RLC实体，或，该第一指示信息用于请求第一DU建立第一RB的分流辅RLC实体。可选的，第一指示信息承载在上下文建立请求(context setup request)消息，或上下文修改请求(context modification request)消息。
第一DU确定第一DU中第一RB关联的RLC实体。具体的，第一DU接收来自CU的配置信息，该配置信息指示第一DU中第一RB关联的M个RLC实体，其中，M为1、2或3。该配置信息可以承载在上下文建立请求消息上，或承载在上下文修改请求消息上。
第一DU确定第一DU中第一RB关联的RLC实体后，确定第一RB关联的主RLC实体。具体的，当第一指示信息用于请求建立第一RB的主RLC实体时，表示第一RB的主RLC实体位于第一DU，当第一指示信息用于请求建立第一RB的分流辅RLC实体时，表示第一RB的主RLC实体位于第二DU。一种可选的方式，第一指示信息包括一个比特，当该比特的取值为“0”时，表示第一指示信息用于请求建立第一RB的主RLC实体，当该比特的取值为“1”时，表示第一指示信息用于请求建立第一RB的分流辅RLC实体；或者，，当该比特的取值为“1”时，表示第一指示信息用于请求建立第一RB的主RLC实体，当该比特的取值为“0”时，表示第一指示信息用于请求建立第一RB的分流辅RLC实体。
可选的，CU还向第一DU发送第三指示信息，对应的，第一DU接收来自CU的第三指示信息。关于第三指示信息的描述参见步骤S701，这里不再赘述。
第一DU接收到上述第一指示信息后，向CU发送第四指示信息，对应的，CU接收来自第一DU的第四指示信息。关于第四指示信息的描述参见步骤S701，这里不再赘述。
S702、CU向终端设备发送第五指示信息，对应的，终端设备接收来自CU的第五指示信息。关于第五指示信息的描述参见图5所示实施例中的步骤S502。
终端设备根据该第五指示信息确定第一RB关联的主RLC实体，进而根据上述第二指示信息确定第一RB关联的所有辅RLC实体的状态为激活或去激活。具体描述参见图5所示实施例中的步骤S502。
S703、第一DU向终端设备发送第二指示信息，对应的，终端设备接收来自第一DU的第二指示信息。该第二指示信息指示上述第一RB关联的所有辅RLC实体的每一个辅RLC实体的状态。第二指示信息的具体描述参见图5所示实施例中的步骤S503，只需把步骤S503中的“辅网络设备”替换为第一DU，把“主网络设备”替换为第二DU，这里不再赘述。
上述实施例提供了一种数据传输的方法，当为无线承载配置多于两个RLC实体(或逻辑信道)时，第一DU接收来自CU的指示信息，第一DU可以根据该指示信息确定该无线承载关联的主RLC实体，从而可以准确地指示终端设备哪些RLC实体需要被激活和去激活，提升了数据传输的可靠性。
图8为本申请实施例提供的一种数据传输的方法的流程示意图。图8所示的实施例适用于DC+CA场景下实现PDCP duplication功能的网络架构，其中，网络设备的CU和DU是分离的。本实施例涉及的是第二DU、CU和终端设备之间进行数据传输的具体过程，其中，无线承载关联的PDCP实体位于第一DU，即，第一DU包括PDCP实体、RLC实体和MAC实体，第二DU包括RLC实体和MAC实体。在图8所示的实施例中，当CU分离为控制面CU实体(即CU-CP实体)和用户面CU实体(即CU-UP实体)时，由CU-CP来实现本实施例中CU的操作。
如图8所示，该方法可以包括：S801、S802和S803。其中，S801、S802和S803的执行顺序，本申请实施例不作限制。
S801、CU向第二DU发送第一指示信息，对应的，第二DU接收来自CU的第一指示信息。该第一指示信息指示第一RB的主RLC实体，该第一RB关联一个主RLC实体和至多3个辅RLC实体。可选的，第一指示信息可以承载在上下文建立请求(context setup request)消息上，或承载在上下文修改请求(context modification request)消息上。
第二DU确定第二DU中第一RB关联的RLC实体。具体的，第二DU接收来自CU的配置信息，该配置信息指示第二DU中第一RB关联的K个RLC实体，其中，K为1、2或3。该配置信息可以承载在上下文建立请求消息上，或承载在上下文修改请求消息上。
第二DU确定第二DU中第一RB关联的RLC实体后，确定第一RB关联的主RLC实体。其中，第一指示信息指示第一RB的主RLC实体的方式参见图6所示实施例中的步骤S601中的描述，只需把步骤S601中的“主网络设备”替换为第二DU，把“辅网络设备”替换为第一DU，这里不再赘述。
可选的，第二DU接收到上述第一指示信息后，向CU发送第四指示信息，对应的，CU 接收来自第二DU的第四指示信息。可选的，该第四指示信息可以是上下文建立回复消息(context setup response)，或上下文修改回复消息(context modification response)。
当第一RB关联的主RLC实体位于第二DU时，该第四指示信息指示第二DU中第一RB关联的RLC实体中的一个RLC实体为第一RB关联的主RLC实体。例如，该第四指示信息指示第一RB关联的主RLC实体的索引，或，第四指示信息指示第一RB关联的主RLC实体所关联的逻辑信道的标识。其中，第一RB关联的主RLC实体为第二DU确定的。
当第一RB关联的主RLC实体位于第一DU时，第四指示信息指示在第二DU中第一RB关联的RLC实体中的一个RLC实体对应的逻辑信道为分流辅逻辑信道(也称：split secondary path)。具体的，该第四指示信息可以指示该分流辅逻辑信道的标识。当第一RB的PDCP duplication功能被去激活时，终端设备可以通过位于第一DU的主RLC实体与第一DU进行数据传输，或者，终端设备可以通过位于第二DU的分流辅逻辑信道与第二DU进行数据传输。
可选的，步骤S801可以被步骤S801a替换。
S801a、CU向第二DU发送第一指示信息，对应的，第二DU接收来自CU的第一指示信息。该第一指示信息用于请求第二DU建立第一RB的主RLC实体，或，该第一指示信息用于请求第二DU建立第一RB的分流辅RLC实体。可选的，第一指示信息承载在上下文建立请求(context setup request)消息，或上下文修改请求(context modification request)消息上。
第二DU确定第二DU中第一RB关联的RLC实体。具体的，第二DU接收来自CU的配置信息，该配置信息指示第二DU中第一RB关联的K个RLC实体，其中，K为1、2或3。该配置信息可以承载在上下文建立请求消息上，或承载在上下文修改请求消息上。
第二DU确定第二DU中第一RB关联的RLC实体后，确定第一RB关联的主RLC实体。具体的，当第一指示信息用于请求建立第一RB的主RLC实体时，表示第一RB的主RLC实体位于第二DU，当第一指示信息用于请求建立第一RB的分流辅RLC实体时，表示第一RB的主RLC实体位于第一DU。一种可选的方式，第一指示信息包括一个比特，当该比特的取值为“0”时，表示第一指示信息用于请求建立第一RB的主RLC实体，当该比特的取值为“1”时，表示第一指示信息用于请求建立第一RB的分流辅RLC实体；或者，，当该比特的取值为“1”时，表示第一指示信息用于请求建立第一RB的主RLC实体，当该比特的取值为“0”时，表示第一指示信息用于请求建立第一RB的分流辅RLC实体。
可选的，CU还向第二DU发送第三指示信息，对应的，第二DU接收来自CU的第三指示信息。关于第三指示信息的描述参见步骤S801，这里不再赘述。
第二DU接收到上述第一指示信息后，向CU发送第四指示信息，对应的，CU接收来自第二DU的第四指示信息。关于第四指示信息的描述参见步骤S801，这里不再赘述。
S802、CU向终端设备发送第五指示信息，对应的，终端设备接收来自CU的第五指示信息。其中，第五指示信息的具体描述参见步骤S602中关于第五指示信息的描述。
S803、第二DU向终端设备发送第二指示信息，对应的，终端设备接收来自第二DU的第二指示信息。该第二指示信息指示上述第一RB关联的所有辅RLC实体的每一个辅RLC实体的状态。第二指示信息的具体描述参见图5所示实施例中的步骤S503，只需把步骤S501中的“辅网络设备”替换为第一DU，把“主网络设备”替换为CU，这里不再赘述。
上述实施例提供了一种数据传输的方法，当为无线承载配置多于两个RLC实体(或逻辑信道)时，第二DU接收来自CU的指示信息，第二DU可以根据该指示信息确定该无线承载关联的主RLC实体，从而可以准确地指示终端设备哪些RLC实体需要被激活和去激活，提升了数据传输的可靠性。
可以理解的是，为了实现上述实施例中功能，网络设备和终端设备包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件、软件、或硬件和软件相结合的形式来实现。某个功能究竟以硬件、软件、或是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用场景和设计约束条件。
图9和图10为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中终端设备或网络设备的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请的实施例中，该通信装置可以是如图1所示的辅网络设备120，也可以是如图1所示的主网络设备130，还可以是应用于辅网络设备或主网络设备的模块(如芯片)。
如图9所示，通信装置900包括处理单元910和收发单元920。通信装置900用于实现上述图5至图6中所示的方法实施例中辅网络设备或主网络设备的功能，或者，通信装置900用于实现上述图7至图8中所示的方法实施例中第一CU或第二CU的功能。
当通信装置900用于实现图5所示的方法实施例中辅网络设备的功能时，收发单元920用于接收来自主网络设备的第一指示信息，该第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，该第一RB关联一个主RLC实体和至多3个辅RLC实体；收发单元920还用于向终端设备发送3比特长度的第二指示信息，该第二指示信息指示上述第一RB关联的每一个辅RLC实体的状态，上述第一RB关联的不同辅RLC实体对应所述3比特中的不同比特。
当通信装置900用于实现图5所示的方法实施例中主网络设备的功能时，收发单元920用于向辅网络设备发送第一指示信息，该第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，该第一RB关联一个主RLC实体和至多3个辅RLC实体。收发单元920还用于向终端设备发送第五指示信息，该第五指示信息指示第一RB的主RLC实体。
当通信装置900用于实现图6所示的方法实施例中辅网络设备的功能时，收发单元920用于向主网络设备发送第一指示信息，该第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，该第一RB关联一个主RLC实体和至多3个辅RLC实体。收发单元920还用于向终端设备发送第五指示信息，该第五指示信息指示第一RB的主RLC实体。
当通信装置900用于实现图6所示的方法实施例中主网络设备的功能时，收发单元920用于接收来自辅网络设备的第一指示信息，该第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，该第一RB关联一个主RLC实体和至多3个辅RLC实体；收发单元920还用于向终端设备发送3比特长度的第二指示信息，该第二指示信息指示上述第一RB关联的每一个辅RLC实体的状态，上述第一RB关联的不同辅RLC实体对应所述3比特中的不同比特。
当通信装置900用于实现图7所示的方法实施例中第一DU的功能时，收发单元920用于接收来自CU的第一指示信息，该第一指示信息指示第一无线承载RB的主无线链路控制 RLC实体，该第一RB关联一个主RLC实体和至多3个辅RLC实体；收发单元920还用于向终端设备发送3比特长度的第二指示信息，该第二指示信息指示上述第一RB关联的每一个辅RLC实体的状态，上述第一RB关联的不同辅RLC实体对应所述3比特中的不同比特。
当通信装置900用于实现图7所示的方法实施例中CU的功能时，收发单元920用于向第一DU发送第一指示信息，该第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，该第一RB关联一个主RLC实体和至多3个辅RLC实体。收发单元920还用于向终端设备发送第五指示信息，该第五指示信息指示第一RB的主RLC实体。
当通信装置900用于实现图8所示的方法实施例中第二DU的功能时，收发单元920用于接收来自CU的第一指示信息，该第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，该第一RB关联一个主RLC实体和至多3个辅RLC实体；收发单元920还用于向终端设备发送3比特长度的第二指示信息，该第二指示信息指示上述第一RB关联的每一个辅RLC实体的状态，上述第一RB关联的不同辅RLC实体对应所述3比特中的不同比特。
当通信装置900用于实现图8所示的方法实施例中CU的功能时，收发单元920用于向第二DU发送第一指示信息，该第一指示信息指示第一无线承载RB的主无线链路控制RLC实体，该第一RB关联一个主RLC实体和至多3个辅RLC实体。收发单元920还用于向终端设备发送第五指示信息，该第五指示信息指示第一RB的主RLC实体。
有关上述处理单元910和收发单元920更详细的描述可以直接参考图5至图8所示的方法实施例中相关描述直接得到，这里不加赘述。
如图10所示，通信装置1000包括处理器1010和接口电路1020。处理器1010和接口电路1020之间相互耦合。可以理解的是，接口电路1020可以为收发器或输入输出接口。可选的，通信装置1000还可以包括存储器1030，用于存储处理器1010执行的指令或存储处理器1010运行指令所需要的输入数据或存储处理器1010运行指令后产生的数据。
当通信装置1000用于实现图5至图8所示的方法时，处理器1010用于实现上述处理单元1010的功能，接口电路1020用于实现上述收发单元1020的功能。
当上述通信装置为应用于终端设备的芯片时，该终端设备芯片实现上述方法实施例中终端设备的功能。该终端设备芯片从终端设备中的其它模块(如射频模块或天线)接收信息，该信息是网络设备发送给终端设备的；或者，该终端设备芯片向终端设备中的其它模块(如射频模块或天线)发送信息，该信息是终端设备发送给网络设备的。
当上述通信装置为应用于网络设备的芯片时，该网络设备芯片实现上述方法实施例中网络设备的功能。该网络设备芯片从网络设备中的其它模块(如射频模块或天线)接收信息，该信息是终端设备发送给网络设备的；或者，该网络设备芯片向网络设备中的其它模块(如射频模块或天线)发送信息，该信息是网络设备发送给终端设备的。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其它通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中处理器可以是随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、 可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于网络设备或终端设备中。当然，处理器和存储介质也可以作为分立组件存在于网络设备或终端设备中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、终端设备、或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，DVD；还可以是半导体介质，例如，固态硬盘(solid state disk，SSD)。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。

Claims (42)

  1. 一种通信方法，其特征在于，所述方法适用于第一通信装置，所述第一通信装置为辅网络设备或辅网络设备中的芯片，所述方法包括：
    接收来自主网络设备的辅站添加请求消息或辅站修改请求消息，所述消息包括配置信息和第一指示信息，其中，所述配置信息指示在所述辅网络设备中第一无线承载RB关联M个无线链路控制RLC实体，M为1、2或3，所述第一指示信息指示所述M个RLC实体中是否存在主RLC实体，所述第一RB关联一个主RLC实体和至多3个辅RLC实体；
    向终端设备发送3比特长度的第二指示信息，所述第二指示信息指示所述第一RB关联的每一个辅RLC实体的状态，所述第一RB关联的不同辅RLC实体对应所述3比特中的不同比特。
  2. 根据权利要求1所述的方法，其特征在于，所述第二指示信息承载在媒体接入控制MAC控制元素中。
  3. 根据权利要求1或2所述的方法，其特征在于，所述3比特中的每一个比特与所述第一RB关联的每一个辅RLC实体的对应关系是预设的。
  4. 根据权利要求3所述的方法，其特征在于，当所述3比特中的任意一个比特的取值为“1”时，所述任意一个比特对应的辅RLC实体的状态为激活状态，或，所述任意一个比特对应的辅RLC实体关联的逻辑信道的状态为激活状态。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，当所述第一RB关联的主RLC实体位于所述辅网络设备时，所述方法还包括：
    向所述主网络设备发送第四指示信息，所述第四指示信息指示所述第一RB关联的主RLC实体所关联的逻辑信道的标识。
  6. 根据权利要求5所述的方法，其特征在于，所述第四指示信息承载在辅站添加请求确认消息上或承载在辅站修改请求确认消息上。
  7. 一种通信方法，其特征在于，所述方法适用于第二通信装置，所述第二通信装置为主网络设备或主网络设备中的芯片，所述方法包括：
    向辅网络设备发送辅站添加请求消息或辅站修改请求消息，所述辅站添加请求消息或辅站修改请求消息包括配置信息和第一指示信息，其中，所述配置信息指示在所述辅网络设备中第一无线承载RB关联M个无线链路控制RLC实体，M为1、2或3，所述第一指示信息指示所述M个RLC实体中是否存在主RLC实体，所述第一RB关联一个主RLC实体和至多3个辅RLC实体；
    向终端设备发送第五指示信息，所述第五指示信息指示所述第一RB的主RLC实体。
  8. 根据权利要求7所述的方法，其特征在于，所述第五指示信息承载在无线资源控制RRC重配置消息上。
  9. 根据权利要求7或8所述的方法，其特征在于，所述第五指示信息指示所述第一RB的主RLC实体，具体包括：
    所述第五指示信息指示所述第一RB关联的主RLC实体的索引，或，所述第五指示信息指示所述第一RB关联的主RLC实体所关联的逻辑信道的标识。
  10. 根据权利要求7至9中任一项所述的方法，其特征在于，所述第五指示信息还指示所述第一RB关联的所有辅RLC实体的初始状态。
  11. 根据权利要求7或10所述的方法，其特征在于，所述第五指示信息还指示所述第 一RB关联的分流辅RLC实体的标识或分流辅RLC实体所关联的逻辑信道的标识。
  12. 根据权利要求7至11中一项所述的方法，其特征在于，当所述第一RB关联的主RLC实体位于所述辅网络设备时，所述方法还包括：
    接收来自所述辅网络设备的第四指示信息，所述第四指示信息指示所述第一RB关联的主RLC实体的标识。
  13. 根据权利要求12所述的方法，其特征在于，所述第四指示信息承载在辅站添加请求确认消息上或承载在辅站修改请求确认消息上。
  14. 一种通信方法，其特征在于，所述方法适用于第三通信装置，所述第三通信装置为第一分布式单元DU或第一DU中的芯片，所述方法包括：
    接收来自CU的上下文建立请求消息或上下文修改请求消息，所述上下文建立请求消息或上下文修改请求消息包括配置信息和第一指示信息，所述配置信息指示在所述DU中第一无线承载RB关联M个无线链路控制RLC实体，M为1、2或3，所述第一指示信息指示所述M个RLC实体中是否存在主RLC实体，所述第一RB关联一个主RLC实体和至多3个辅RLC实体；
    向终端设备发送3比特长度的第二指示信息，所述第二指示信息指示所述第一RB关联的每一个辅RLC实体的状态，所述第一RB关联的不同辅RLC实体对应所述3比特中的不同比特。
  15. 根据权利要求14所述的方法，其特征在于，所述第二指示信息承载在媒体接入控制MAC控制元素中。
  16. 根据权利要求14或15所述的方法，其特征在于，所述3比特中的每一个比特与所述第一RB关联的每一个辅RLC实体的对应关系是预设的。
  17. 根据权利要求16所述的方法，其特征在于，当所述3比特中的任意一个比特的取值为“1”时，所述任意一个比特对应的辅RLC实体的状态为激活状态，或，所述任意一个比特对应的辅RLC实体关联的逻辑信道的状态为激活状态。
  18. 根据权利要求14至17中任一项所述的方法，其特征在于，当所述第一RB关联的主RLC实体位于所述第一DU时，所述方法还包括：
    向所述CU发送第四指示信息，所述第四指示信息指示所述第一RB关联的主RLC实体所关联的逻辑信道的标识。
  19. 根据权利要求18所述的方法，其特征在于，所述第四指示信息承载在上下文建立回复消息上，或承载在上下文修改回复消息上。
  20. 一种通信方法，其特征在于，所述方法适用于第四通信装置，所述第四通信装置为集中式单元CU或CU中的芯片，所述方法包括：
    向第一DU发送上下文建立请求消息或上下文修改请求消息，所述上下文建立请求消息或上下文修改请求消息包括配置信息和第一指示信息，所述配置信息指示在所述第一DU中第一无线承载RB关联M个无线链路控制RLC实体，M为1、2或3，所述第一指示信息指示所述M个RLC实体中是否存在主RLC实体，所述第一RB关联一个主RLC实体和至多3个辅RLC实体；
    向终端设备发送第五指示信息，所述第五指示信息指示所述第一RB的主RLC实体。
  21. 根据权利要求20所述的方法，其特征在于，所述第五指示信息承载在无线资源控制RRC重配置消息上。
  22. 根据权利要求20或21所述的方法，其特征在于，所述第五指示信息指示所述第一RB的主RLC实体，具体包括：
    所述第五指示信息指示所述第一RB关联的主RLC实体的索引，或，所述第五指示信息指示所述第一RB关联的主RLC实体所关联的逻辑信道的标识。
  23. 根据权利要求20至22中任一项所述的方法，其特征在于，所述第五指示信息还指示所述第一RB关联的所有辅RLC实体的初始状态。
  24. 根据权利要求20或23所述的方法，其特征在于，所述第五指示信息还指示所述第一RB关联的分流辅RLC实体的标识或分流辅RLC实体所关联的逻辑信道的标识。
  25. 根据权利要求20至24中一项所述的方法，其特征在于，当所述第一RB关联的主RLC实体位于所述第一DU时，所述方法还包括：
    接收来自所述第一DU的第四指示信息，所述第四指示信息指示所述第一RB关联的主RLC实体的标识。
  26. 根据权利要求25所述的方法，其特征在于，所述第四指示信息承载在上下文建立回复消息上，或承载在上下文修改回复消息上。
  27. 一种通信装置，包括用于执行如权利要求1至6中任一项所述方法的模块。
  28. 一种通信装置，包括用于执行如权利要求7至13中任一项所述方法的模块。
  29. 一种通信装置，包括用于执行如权利要求14至19中任一项所述方法的模块。
  30. 一种通信装置，包括用于执行如权利要求20至26中任一项所述方法的模块。
  31. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器和所述存储器耦合，所述处理器用于实现如权利要求1至6中任一项所述的方法。
  32. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器和所述存储器耦合，所述处理器用于实现如权利要求7至13中任一项所述的方法。
  33. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器和所述存储器耦合，所述处理器用于实现如权利要求14至19中任一项所述的方法。
  34. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器和所述存储器耦合，所述处理器用于实现如权利要求20至26中任一项所述的方法。
  35. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1至6中任一项所述的方法。
  36. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求7至13中任一项所述的方法。
  37. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求14至19中任一项所述的方法。
  38. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信 号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求20至26中任一项所述的方法。
  39. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至6，或，7至13，或14至19，或，20至26中任一项所述的方法。
  40. 一种通信系统，包括如权利要求27、31、35中任一项所述的通信装置，和如权利要求28、32、36中任一项所述的通信装置。
  41. 一种通信系统，包括如权利要求29、33、37中任一项所述的通信装置，和如权利要求30、34、38中任一项所述的通信装置。
  42. 一种计算机程序产品，其特征在于，所述计算机程序产品包括指令，当所述指令被计算机运行时，实现如权利要求1至6，或，7至13，或14至19，或，20至26中任一项所述的方法。
PCT/CN2021/095326 2020-05-21 2021-05-21 一种通信方法及装置 WO2021233445A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP21809596.6A EP4145900A4 (en) 2020-05-21 2021-05-21 COMMUNICATION METHOD AND DEVICE
AU2021273886A AU2021273886A1 (en) 2020-05-21 2021-05-21 Communication method and apparatus
US18/056,938 US20230077500A1 (en) 2020-05-21 2022-11-18 Communication Method and Apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010437695.5 2020-05-21
CN202010437695.5A CN113709908A (zh) 2020-05-21 2020-05-21 数据传输的方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/056,938 Continuation US20230077500A1 (en) 2020-05-21 2022-11-18 Communication Method and Apparatus

Publications (1)

Publication Number Publication Date
WO2021233445A1 true WO2021233445A1 (zh) 2021-11-25

Family

ID=78646107

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/095326 WO2021233445A1 (zh) 2020-05-21 2021-05-21 一种通信方法及装置

Country Status (5)

Country Link
US (1) US20230077500A1 (zh)
EP (1) EP4145900A4 (zh)
CN (1) CN113709908A (zh)
AU (1) AU2021273886A1 (zh)
WO (1) WO2021233445A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114158071A (zh) * 2021-11-26 2022-03-08 中国联合网络通信集团有限公司 专网中数据传输的方法和装置

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4042622A1 (en) * 2019-10-11 2022-08-17 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for multi-connection flow control in a wireless communication network
CN116506893A (zh) * 2022-01-18 2023-07-28 中国移动通信有限公司研究院 一种数据传输方法及网络设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015008966A1 (en) * 2013-07-16 2015-01-22 Lg Electronics Inc. Method for segmenting and reordering a radio link control status protocol data unit and a device therefor
CN110167067A (zh) * 2018-02-13 2019-08-23 展讯通信（上海）有限公司 数据传输方法及装置、存储介质、终端、基站
CN110972205A (zh) * 2018-09-28 2020-04-07 华为技术有限公司 一种通信方法及设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015008966A1 (en) * 2013-07-16 2015-01-22 Lg Electronics Inc. Method for segmenting and reordering a radio link control status protocol data unit and a device therefor
CN110167067A (zh) * 2018-02-13 2019-08-23 展讯通信（上海）有限公司 数据传输方法及装置、存储介质、终端、基站
CN110972205A (zh) * 2018-09-28 2020-04-07 华为技术有限公司 一种通信方法及设备

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114158071A (zh) * 2021-11-26 2022-03-08 中国联合网络通信集团有限公司 专网中数据传输的方法和装置
CN114158071B (zh) * 2021-11-26 2023-05-30 中国联合网络通信集团有限公司 专网中数据传输的方法和装置

Also Published As

Publication number Publication date
US20230077500A1 (en) 2023-03-16
AU2021273886A1 (en) 2023-01-05
CN113709908A (zh) 2021-11-26
EP4145900A1 (en) 2023-03-08
EP4145900A4 (en) 2023-10-25

Similar Documents

Publication Publication Date Title
US11882480B2 (en) Method and device for controlling duplicate packet transmission in wireless communication system
WO2021233445A1 (zh) 一种通信方法及装置
CN115460571A (zh) 由无线通信系统中的第一终端或第二终端执行的方法
WO2021233217A1 (zh) 能力信息上报方法及其装置
WO2022027359A1 (en) New radio (nr) channel state information (csi) capability related signaling enhancement
EP3750358B1 (en) Method and apparatus for transmitting and receiving duplicated data in wireless communication system
WO2021026902A1 (zh) 一种配置方法、通信装置和通信系统
CN109644101B (zh) 承载配置方法及终端和网络设备
US20220217549A1 (en) Communication Method, Apparatus, and System
WO2022027523A1 (zh) 一种辅助信息的配置方法及通信装置
CN113784385A (zh) 一种通信方法及相关装置
WO2022001641A1 (zh) 用于切换的数据传输的方法和装置
WO2023103958A1 (zh) 一种通信方法及装置
WO2022141332A1 (zh) 一种通信方法及装置
WO2020200055A1 (zh) 一种数据传输方法及装置
WO2021244078A1 (zh) 一种切换方法及装置
WO2022120541A1 (zh) 数据传输的方法和装置
WO2022068336A1 (zh) 路由信息更新方法、通信装置及存储介质
WO2022067512A1 (zh) 通信方法及通信设备
WO2023246746A1 (zh) 一种通信方法及相关设备
WO2024027636A1 (zh) 一种通信方法、通信装置及通信系统
EP4351192A1 (en) Relay communication method, apparatus and system
WO2024093933A1 (zh) 数据传输方法和通信装置
WO2024016173A1 (zh) 中继承载配置的确定方法、装置、设备及存储介质
US20240057219A1 (en) Communication method and apparatus

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021809596

Country of ref document: EP

Effective date: 20221129

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021273886

Country of ref document: AU

Date of ref document: 20210521

Kind code of ref document: A