Communication method and communication device

Abstract

According to a communication method and a communication device, a first device can perform frequency domain copying on a data packet on a packet data convergence protocol layer, a radio link control layer or a medium access control layer, and distributes an original data packet and the copied data packet to different links or carriers for transmission. In this way, the first data can be transmitted by using the air interface vacancy corresponding to multiple links or multiple carriers at the same time, and by taking the multiple links as a new wireless transmission link and a long term evolution transmission link as an example, the first device can use new wireless and long term evolution air interface vacancy resources at the same time. Therefore, according to the scheme of the invention, air interface spare resources can be utilized as much as possible through a data redundancy transmission mode, so that packet loss is reduced, transmission delay is reduced, the reliability of downlink data transmission of the service is guaranteed, and the user experience of the service is improved.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly, to a communication method and a communication device. Background Art

[0002] Packet loss rate and transmission delay are important factors affecting the user experience of services. Fluctuations in the channel environment can lead to an increase in the packet loss rate, an increase in the transmission delay, and even a situation where the service is interrupted, which will result in a decline in the user experience of the service. Summary of the Invention

[0003] This application provides a communication method and a communication device, aiming to reduce packet loss and lower the transmission delay, thereby enhancing the user experience of services.

[0004] In a first aspect, a communication method is provided. The method includes: an entity of a first layer of a first device receives first data, and the entity of the first layer is associated with a first entity and a second entity of a second layer; the entity of the first layer sends the first data through the first entity of the second layer and sends the first data through the second entity of the second layer.

[0005] Exemplarily, the first device may be a first access network device. Without special instructions, the "first access network device" may refer to the first access network device itself or a device capable of supporting the first access network device to implement its functions. When the first device is the first access network device, the entity of the first layer of the first access network device may send the first data to a terminal device through the first entity of the second layer and send the first data to the terminal device through the second entity of the second layer.

[0006] Based on the above method, the first device can send the first data through the first entity and the second entity of the second layer, that is, the first device can send the same data through multiple links or multiple carriers. In this way, the available radio resources corresponding to multiple links or multiple carriers can be used simultaneously to transmit the first data. Taking the transmission links of New Radio and Long-Term Evolution as examples of multiple links, the available radio resources of New Radio and Long-Term Evolution can be used simultaneously to transmit the first data. Therefore, the above method can use the available radio resources as much as possible through redundant data transmission to reduce packet loss, lower the transmission delay, ensure the reliability of downlink data transmission of services, and help improve the user experience of services.

[0007] In combination with the first aspect, in some possible implementation manners, the first layer is a packet data convergence protocol (PDCP) layer, and the second layer is a radio link control (RLC) layer; or, the first layer is an RLC layer, and the second layer is a media access control (MAC) layer; or, the first layer is a MAC layer, and the second layer is a physical (PHY) layer.

[0008] In combination with the first aspect or any of its implementation manners, in some other possible implementation manners, the first entity of the second layer and the second entity of the second layer belong to the first device; or, the first entity of the second layer belongs to the first device, and the second entity of the second layer belongs to a second device.

[0009] In the above implementation manners, the first entity of the second layer and the second entity of the second layer belong to the same first device, that is, the above implementation manners are applicable to the carrier aggregation scenario. The first entity of the second layer belongs to the first device, and the second entity of the second layer belongs to the second device, that is, the above implementation manners are applicable to the dual connection scenario.

[0010] In combination with the first aspect or any of its implementation manners, in some other possible implementation manners, the first device and the second device have the same radio access technology (RAT).

[0011] In combination with the first aspect or any of its implementation manners, in some other possible implementation manners, the first device and the second device are access network devices of the 5th generation (5G) RAT.

[0012] In combination with the first aspect or any of its implementation manners, in some other possible implementation manners, the first device and the second device have different RATs.

[0013] In combination with the first aspect or any of its implementation manners, in some other possible implementation manners, the first device is an access network device of the 5G RAT, and the second device is an access network device of the 4th generation (4G) RAT; or, the first device is an access network device of the 4G RAT, and the second device is an access network device of the 5G RAT.

[0014] In combination with the first aspect or any of its implementation manners, in some other possible implementation manners, the first device and the second device are two access network devices connected to the same terminal device in a dual connection scenario.

[0015] Combined with the first aspect or any implementation thereof, in some other possible implementations, the method further includes: an entity in the first layer of the first device determines that the frequency-domain replication function is enabled. That is, when the frequency-domain replication function in the first layer of the first device is enabled, the entity in the first layer of the first device sends the first data through the first entity in the second layer and sends the first data through the second entity in the second layer.

[0016] Based on the above implementation, the entity in the first layer of the first device can send the same data through multiple links or multiple carriers when the frequency-domain replication function is enabled, and send one data through a single link or a single carrier when the frequency-domain replication function is not enabled, which helps to balance between the reliability of downlink data transmission and resource waste.

[0017] Combined with the first aspect or any implementation thereof, in some other possible implementations, the entity in the first layer of the first device sending the first data through the first entity in the second layer includes: the entity in the first layer of the first device sends the first data to the first entity in the second layer; the first entity in the second layer sends the first data through the first entity in the third layer and the first entity in the second layer sends the first data through the second entity in the third layer.

[0018] Based on the above implementation, the first data can be replicated at multiple protocol layers, so that the first device can send the same data through more links or more carriers, thereby simultaneously utilizing more available radio interfaces to transmit the same data, further reducing packet loss and reducing transmission delay, further ensuring the reliability of data transmission for services, and thus enhancing the user experience of services.

[0019] Combined with the first aspect or any implementation thereof, in some other possible implementations, the first data is user-plane data.

[0020] Combined with the first aspect or any implementation thereof, in some other possible implementations, the method further includes: the entity in the first layer receives second data, and the second data is control-plane data; the entity in the first layer sends the second data through the first entity in the second layer, and the first entity in the second layer is the main entity corresponding to the main link or the primary component carrier.

[0021] In a second aspect, a communication method is provided, and the method includes: the first entity in the second layer of the third device receives the first data and sends the first data to the entity in the first layer of the third device; the second entity in the second layer receives the first data and sends the first data to the entity in the first layer; the entity in the first layer processes the first data from the first entity in the second layer and the first data from the second entity in the second layer.

[0022] Exemplarily, the third device may be a terminal device. Without special instructions, the "terminal device" may refer to the terminal device itself or a module or unit that can support the terminal device to implement its functions.

[0023] Based on the above method, both the first entity and the second entity in the second layer of the third device can receive the first data. That is, the third device can receive the same data through multiple links or multiple carriers. In this way, the available radio resources corresponding to multiple links or multiple carriers can be utilized simultaneously to transmit the first data. Taking the transmission links of the new radio and the long-term evolution as an example of multiple links, the available radio resources of the new radio and the long-term evolution can be utilized simultaneously to transmit the first data. Therefore, the above method can utilize the available radio resources as much as possible through the redundant transmission of data to reduce packet loss, reduce transmission delay, ensure the reliability of data transmission for services, and help improve the user experience of services.

[0024] Combined with the second aspect, in some possible implementation manners, the processing includes reordering processing and / or duplicate packet processing.

[0025] Combined with the second aspect or any of its implementation manners, in some other possible implementation manners, the first layer is the PDCP layer and the second layer is the RLC layer; or, the first layer is the RLC layer and the second layer is the MAC layer; or, the first layer is the MAC layer and the second layer is the PHY layer.

[0026] Combined with the second aspect or any of its implementation manners, in some other possible implementation manners, the first entity in the second layer of the third device receiving the first data includes: the first entity in the second layer receiving the first data from the first device; the second entity in the second layer of the third device receiving the first data includes: the first entity in the second layer receiving the first data from the first device; or, the first entity in the second layer of the third device receiving the first data includes: the first entity in the second layer receiving the first data from the first device; the second entity in the second layer of the third device receiving the first data includes: the second entity in the second layer receiving the first data from the second device.

[0027] In the above implementation manners, both the first entity and the second entity in the second layer of the third device receive the first data from the first device. That is, the above implementation manners are applicable to the carrier aggregation scenario. The first entity in the second layer of the third device receives the first data from the first device, and the second entity in the second layer of the third device receives the first data from the second device. That is, the above implementation manners are applicable to the dual connectivity scenario.

[0028] Combined with the second aspect or any implementation thereof, in some other possible implementations, the first device and the second device have the same standard.

[0029] Combined with the second aspect or any implementation thereof, in some other possible implementations, the first device and the second device are two access network devices of 5G standard connected to the same third device in a dual-connection scenario.

[0030] Combined with the second aspect or any implementation thereof, in some other possible implementations, the first device and the second device have different standards.

[0031] Combined with the second aspect or any implementation thereof, in some other possible implementations, the first device and the second device are two access network devices connected to the same terminal device in a dual-connection scenario. Among them, the first device is an access network device of 5G standard, and the second device is an access network device of 4G standard; or, the first device is an access network device of 4G standard, and the second device is an access network device of 5G standard.

[0032] Combined with the second aspect or any implementation thereof, in some other possible implementations, the first data is user data.

[0033] Combined with the second aspect or any implementation thereof, in some other possible implementations, before the first entity of the second layer sends the first data to the entity of the first layer of the third device, the method further includes: the first entity of the second layer performs reordering processing and / or duplicate packet processing on the first data; and / or, before the second entity of the second layer sends the first data to the entity of the first layer of the third device, the method further includes: the second entity of the second layer performs reordering processing and / or duplicate packet processing on the first data.

[0034] Based on the above implementation, the processing time of the first data by the entity of the first layer of the third device can be reduced. And since the first entity of the second layer of the third device and the second entity of the second layer of the third device can perform reordering processing and / or duplicate packet processing on the first data simultaneously, the overall data processing time can be reduced.

[0035] In a third aspect, a communication device is provided, which is used to execute the methods provided in any of the above aspects or their implementation manners. Specifically, the device may include units and / or modules for executing the methods provided in any of the above aspects or their implementation manners, such as a processing unit and / or a transceiver unit. Among them, the processing unit is used to execute the processing steps in the methods provided in any of the above aspects or their implementation manners, such as managing network management intents. The transceiver unit is used to execute the transceiver steps in the methods provided in any of the above aspects or their implementation manners, such as receiving or sending intent reports, first information, subscription messages, etc.

[0036] In one implementation manner, the device is the first device or the third device. When the device is the first device or the third device, the transceiver unit may be a transceiver, or an input / output interface, or a communication interface; the processing unit may be at least one processor. Exemplarily, the transceiver is a transceiver circuit. Exemplarily, the input / output interface is an input / output circuit.

[0037] In another implementation manner, the device is a chip, a chip system, or a circuit used in the first device or the third device. When the device is a chip, a chip system, or a circuit used in the first device or the third device, the transceiver unit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit, etc. on the chip, the chip system, or the circuit; the processing unit may be at least one processor, a processing circuit, or a logic circuit, etc.

[0038] In a fourth aspect, a communication device is provided, which includes: a memory for storing programs; at least one processor for executing the computer programs or instructions stored in the memory to execute the methods provided in any of the above aspects or their implementation manners.

[0039] In one implementation manner, the device is the first device or the third device.

[0040] In another implementation manner, the device is a chip, a chip system, or a circuit used in the first device or the third device.

[0041] In a fifth aspect, a communication device is provided, which includes: at least one processor and a communication interface, and the at least one processor is used to obtain the computer programs or instructions stored in the memory through the communication interface to execute the methods provided in any of the above aspects or their implementation manners. The communication interface may be implemented by hardware or software.

[0042] In one implementation manner, the device further includes the memory.

[0043] In a sixth aspect, a processor is provided, which is used to execute the methods provided in the above aspects.

[0044] For operations such as sending and obtaining / receiving involved by the processor, if there is no special description, or if it does not conflict with its actual function or internal logic in the relevant description, then it can be understood as the operations of the processor for output, reception, input, etc., or it can also be understood as the sending and receiving operations performed by the radio frequency circuit and the antenna. This application does not make any limitations in this regard.

[0045] In a seventh aspect, a computer-readable storage medium is provided. The computer-readable medium stores program code for a device to execute. The program code includes methods for executing any of the above aspects or their implementation manners.

[0046] In an eighth aspect, a computer program product including instructions is provided. When the instructions run on a computer, the computer is caused to execute the methods provided by any of the above aspects or their implementation manners.

[0047] In a ninth aspect, a chip is provided. The chip includes a processor and a communication interface. The processor reads instructions stored on a memory through the communication interface and executes the methods provided by any of the above aspects or their implementation manners. The communication interface can be implemented by hardware or software.

[0048] Exemplarily, as an implementation manner, the chip further includes a memory. A computer program or instructions are stored in the memory. The processor is configured to execute the computer program or instructions stored on the memory. When the computer program or instructions are executed, the processor is configured to execute the methods provided by any of the above aspects or their implementation manners.

[0049] Wherein, when the method provided by this application is executed by a chip, this application does not limit the number of chips for specifically implementing the method of this application. For example, it can be executed by one chip, or can be executed by two or more chips. And when the number of chips for implementing the method of this application is two or more, the chip manufacturers are not limited, and they can be the same manufacturer or different manufacturers.

[0050] In a tenth aspect, a communication system is provided, including at least one of the first device, the second device, or the third device described above.

[0051] Exemplarily, the first device can be a first access network device. Exemplarily, the second device can be a second access network device. Exemplarily, the third device can be a terminal device.

[0052] In an eleventh aspect, a computer program is provided. When it runs on a computer, the methods provided by any of the above aspects or their implementation manners are caused to be executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 is a schematic diagram of the architecture of a communication system 1000 to which the embodiments of this application can be applied;

[0054] Figure 2 It is a schematic diagram of a data splitting mode in dual connectivity (DC).

[0055] Figure 3 It is a schematic diagram of a data splitting mode in carrier aggregation (CA).

[0056] Figure 4 It is a schematic flowchart of the communication method 500 provided by the embodiments of the present application.

[0057] Figure 5 It is a schematic diagram of PDCP processing on the access network device side in the DC scenario.

[0058] Figure 6 It is a schematic flowchart of the PDCP entity on the access network device side sending services in the DC scenario.

[0059] Figure 7 It is a schematic diagram of RLC processing on the access network device side in the CA scenario.

[0060] Figure 8 It is a schematic diagram of MAC processing on the access network device side in the CA scenario.

[0061] Figure 9 It is a schematic process of the RLC entity on the access network device side sending services in the CA scenario Figure 1 ;

[0062] Figure 10 It is a schematic process of the RLC entity on the access network device side sending services in the CA scenario Figure 2 ;

[0063] Figure 11 It is a schematic flowchart of the communication method 1200 provided by the embodiments of the present application.

[0064] Figure 12 It is a schematic diagram of the overall process of RLC processing on the terminal device side in unacknowledged mode (UM).

[0065] Figure 13 It is a schematic diagram of the specific process of RLC processing on the terminal device side in UM.

[0066] Figure 14 It is a schematic diagram of the overall process of RLC processing on the terminal device side in acknowledged mode (AM).

[0067] Figure 15It is a schematic diagram of the specific process of RLC processing on the terminal device side under AM;

[0068] Figure 16 It is a schematic structural diagram of a device provided by an embodiment of the present application;

[0069] Figure 17 It is another schematic structural diagram of a device provided by an embodiment of the present application;

[0070] Figure 18 It is a schematic diagram of a chip system provided by an embodiment of the present application. Detailed implementation manners

[0071] To facilitate the understanding of the embodiments of the present application, the following points are explained before introducing the embodiments of the present application.

[0072] "Indication" includes direct indication (also known as explicit indication) and implicit indication. Among them, directly indicating information A means including this information A; implicitly indicating information A means indicating information A through the correspondence between information A and information B and directly indicating information B. Among them, the correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured. Information C is used for the determination of information D, which includes both the case where information D is determined only based on information C and the case where it is determined based on information C and other information. In addition, when information C is used for the determination of information D, there can also be an indirect determination case. For example, information D is determined based on information E, and information E is determined based on information C. "Network element A sends information A to network element B" can be understood as the destination of this information A or an intermediate network element in the transmission path between the destination and the source is network element B, which can include directly or indirectly sending information to network element B. "Network element B receives information A from network element A" can be understood as the source of this information A or an intermediate network element in the transmission path between the source and the destination is network element A, which can include directly or indirectly receiving information from network element A. Necessary processing may be performed on the information between the source and the destination of the information transmission, such as format change, etc., but the destination can understand the valid information from the source. The various digital numbers such as the first, the second, etc. are only for the convenience of description and are not used to limit the scope of the embodiments of this application. For example, they are used to distinguish different messages, different information, etc. The "protocol" involved can refer to the standard protocols in the communication field. For example, it can include the long term evolution (LTE) protocol, the new radio (NR) protocol, and the related protocols applied to future communication systems. This application does not make any limitations in this regard. Words such as "exemplary", "for example", "exemplarily", "as (another) example", etc. are used to represent examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary" in this application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. The terms "include", "comprise", "have" and their variants all mean "including but not limited to", unless otherwise specifically emphasized in other ways. "A plurality of" means two or more. "And / or" describes the association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects before and after. "At least one (item)" or its similar expression refers to any combination of these items, including any combination of a single item or multiple items. For example, at least one (item) of a, b, and c can represent: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Where a, b, and c can be single or multiple respectively.Descriptions such as "when", "in the case of", "if", and "provided that" all refer to the fact that the device will perform corresponding processing under certain objective circumstances, rather than limiting the time. It does not require the device to have a judgment action during implementation, nor does it imply other limitations.

[0073] In addition, the network architecture and service scenarios described in the embodiments of this application are for more clearly explaining the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those of ordinary skill in the art can understand that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of this application are equally applicable to similar technical problems.

[0074] Next, a communication system to which the embodiments of this application can be applied will be described.

[0075] The embodiments of this application can be applied to various communication systems, such as: LTE system, frequency division duplex (FDD) system, time division duplex (TDD) system, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, 5G system or NR system, 6th generation (6G) system or future communication system, etc. The 5G mobile communication system described in this application includes a non-standalone (NSA) 5G mobile communication system or a standalone (SA) 5G mobile communication system. The communication system can also be a public land mobile network (PLMN) network, a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an Internet of Things (IoT) communication system, a vehicle-to-everything (V2X) communication system, an uncrewed aerial vehicle (UAV) communication system, or other communication systems.

[0076] A device in a communication system can send signals to another device or receive signals from another device. The signals can include information, signaling, data, etc. Herein, the device can also be replaced with an entity, a network entity, a communication device, a communication module, a node, a communication node, etc. In this application, the description is given by taking the device as an example. For example, a communication system can include at least one terminal device and at least one network device. The network device can send downlink signals to the terminal device, and / or the terminal device can send uplink signals to the network device.

[0077] Exemplarily, Figure 1 FIG. 1000 shows a schematic architecture diagram of a communication system 1000 to which an embodiment of the present application is applied. As Figure 1 shown, the communication system includes a radio access network 100 and a core network 200. In a possible implementation, the communication system 1000 may further include the Internet 300. Among them, the RAN 100 may include at least one radio access network device (such as Figure 1 110a and 110b in FIG. 1000), and may further include at least one terminal device (such as Figure 1 120a - 120j in FIG. 1000). The terminal device is connected to the radio access network device in a wireless manner, and the radio access network device is connected to the core network in a wireless or wired manner. The core network device and the radio access network device may be independent different physical devices, or the functions of the core network device and the logical functions of the radio access network device may be integrated on the same physical device, or the functions of part of the core network device and part of the radio access network device may be integrated on a physical device. The terminal devices can be connected to each other in a wired or wireless manner, and the radio access network devices can be connected to each other in a wired or wireless manner. Figure 1 This is just a schematic diagram, and other network devices may also be included in the communication system, such as wireless relay devices and wireless backhaul devices, which are not drawn in Figure 1 FIG. 1000.

[0078] The terminal device in the communication system 1000 can also be referred to as a terminal, a user equipment (UE), a mobile station, a mobile terminal, etc. The terminal device can be widely applied to various scenarios, such as D2D, V2X, MTC, IoT, virtual reality, augmented reality, industrial control, autonomous driving, remote medical treatment, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, etc. The terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a robotic arm, a smart home device, etc. The embodiments of the present application do not limit the device form of the terminal device.

[0079] The radio access network 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as a 4G mobile communication system, a 5G mobile communication system, or an evolved system for the future (such as a 6G mobile communication system). The radio access network 100 can also be an Open Radio Access Network (O-RAN), or a Cloud Radio Access Network (CRAN). The radio access network 100 can also be a communication system that integrates two or more of the above systems.

[0080] The radio access network device, sometimes also referred to as a radio access network node, a radio access network entity, or an access node, etc., is a part of the communication system used to help terminal devices achieve wireless access. Multiple radio access network devices in the communication system 1000 can be of the same type of node or different types of nodes.

[0081] In a possible scenario, the radio access network device can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a next generation base station in a 6G mobile communication system, or a base station in a future mobile communication system, etc. The RAN node can be a macro base station (such as Figure 1 110a in Figure 1 ), a micro base station or an indoor station (such as 110b in ), a relay node or a donor node, or a radio controller in a CRAN scenario. Exemplarily, the radio access network node can also be a server, a wearable device, a vehicle or an in-vehicle device, etc. For example, the access network device in V2X technology can be a Road Side Unit (RSU).

[0082] In another possible scenario, multiple radio access network devices cooperate to assist a terminal device in achieving wireless access, and different radio access network devices respectively implement some functions of a base station. For example, the radio access network device may be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and the DU may be separately provided, or may also be included in the same network element, such as a baseband unit (BBU). The RU may be included in a radio device or a radio unit, such as included in a remote radio unit (RRU), a radio frequency unit (RFU), an active antenna unit (AAU), or a remote radio head (RRH).

[0083] In different systems, the CU, DU, or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, the CU may also be referred to as an open-CU (O-CU), the DU may also be referred to as an open-DU (O-DU), and the RU may also be referred to as an open-RU (O-RU). Any one of the CU, DU, and RU may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0084] The embodiments of the present application do not limit the specific technologies and specific device forms adopted by the radio access network device. For the convenience of description, the access network device is used as an abbreviation for the radio access network device.

[0085] The base station and the terminal device may be in fixed positions or movable. The base station and the terminal device may be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; may also be deployed on water; may also be deployed on airplanes, balloons, and artificial satellites. The embodiments of the present application do not limit the application scenarios of the base station and the terminal device.

[0086] The roles of the base station and the terminal device may be relative. For example, Figure 1The helicopter or drone 120i therein can be configured as a mobile base station. For the terminal devices 120j accessing the radio access network 100 through 120i, 120i is the base station; but for the base station 110a, 120i is the terminal device, that is, the communication between 110a and 120i is through the radio air interface protocol. Of course, the communication between 110a and 120i can also be through the interface protocol between base stations. At this time, relative to 110a, 120i is also the base station. Therefore, both the base station and the terminal device can be uniformly referred to as communication devices. Figure 1 110a and 110b therein can be referred to as communication devices with base station functions. Figure 1 120a - 120j therein can be referred to as communication devices with terminal device functions.

[0087] The communication between the base station and the terminal device, between the base station and the base station, and between the terminal device and the terminal device can be carried out through the authorized spectrum, can also be carried out through the unlicensed spectrum, or can also be carried out through the authorized spectrum and the unlicensed spectrum simultaneously; it can communicate through the spectrum below 6 gigahertz (GHz), can also communicate through the spectrum above 6 GHz, and can also use the spectrum below 6 GHz and the spectrum above 6 GHz simultaneously. The embodiments of the present application do not limit the spectrum resources used for wireless communication.

[0088] In the embodiments of the present application, the functions of the base station can also be executed by modules (such as chips) in the base station, or can also be executed by a control subsystem including base station functions. The control subsystem including base station functions here can be the control center in the above application scenarios such as smart grid, industrial control, intelligent transportation, and smart city. The functions of the terminal device can also be executed by modules (such as chips or modems) in the terminal device, or can also be executed by a device including terminal device functions.

[0089] It should be understood that the network architecture shown above is only an exemplary illustration, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture capable of realizing the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0090] It should also be understood that the above naming is only defined for the convenience of distinguishing different functions and should not constitute any limitation to the present application. The present application does not exclude the possibility of using other naming in the 6G network and future other networks.

[0091] To facilitate the understanding of the embodiments of the present application, several concepts or terms involved in the embodiments of the present application are briefly described below.

[0092] The concepts or terms introduced below are described based on the concepts or terms defined in the reference protocol. However, this does not mean that the embodiments of this application can only be applied to existing systems. The concepts or terms involved in the embodiments of this application can be applied to future systems. Moreover, the specific names of the concepts or terms (such as those related to functional descriptions) may be adjusted with the development of future systems.

[0093] 1. Dual Connectivity

[0094] In dual connectivity (DC), a terminal device may communicate with multiple base stations, and the network side can utilize the resources of multiple base stations to provide communication services for the terminal device.

[0095] The multiple base stations in DC may be base stations of the same radio access technology (RAT), such as all 4G base stations or all 5G base stations. The multiple base stations in DC may also be base stations of different RATs. This type of DC is called multi-RAT dual connectivity (MR-DC). For example, one is a 4G base station and the other is a 5G base station. The RAT of 4G is also called evolved universal terrestrial radio access (E-UTRA), and the RAT of 5G is also called NR. MR-DC includes: DC between E-UTRA and NR (E-UTRA-NR DC, EN-DC); DC between E-UTRA of NG-RAN and NR (NG-RAN E-UTRA-NR DC, NGEN-DC); DC between NR and E-UTRA (NR-E-UTRA DC, NE-DC); DC between NR and NR (NR-NR DC, NR-DC). In EN-DC, the primary base station connected to the 4G core network is the LTE base station eNB, and the secondary base station is the NR base station gNB; in NGEN-DC, the primary base station connected to the 5G core network (5G core, 5GC) is the LTE base station ng-eNB, and the secondary base station is the NR base station gNB; in NE-DC, the primary base station connected to the 5GC is the NR base station gNB, and the secondary base station is the LTE base station ng-eNB; in NR-DC, the primary base station connected to the 5GC is the NR base station gNB; the secondary base station is the NR base station gNB.

[0096] In DC, one PDCP entity can be associated with multiple RLC entities. The multiple RLC entities can be arranged on multiple base stations. Each RLC entity can be associated with one or more MAC entities. The data from the upper layer can be split at the PDCP entity and sent through one of the associated multiple RLC entities.

[0097] Taking EN-DC as an example, Figure 2 a data splitting mode in DC is shown. Figure 2 Taking the Option3X architecture as an example, a PDCP entity is associated with two RLC entities of different radio access technologies. For example, Figure 2 as shown, the NR PDCP entity is associated with the LTE RLC entity and the NR RLC entity. Each of the two RLC entities is associated with a MAC entity. For example, Figure 2 as shown, the LTE RLC entity is associated with an LTE MAC entity, and the NR RLC entity is associated with an NR MAC entity. Data from the upper server arrives at the NR PDCP entity through the NR S1-U interface and is split at the PDCP layer. The data sent by the NR PDCP entity will be sent to either the LTE RLC entity or the NR RLC entity, and further transmitted through the associated MAC entity. The data arrives at a MAC entity of the terminal device through the air interface and is further aggregated to the PDCP entity through the associated RLC entity.

[0098] As can be seen from the above, in DC, data from the upper layer is split at the PDCP layer and sent to one of the multiple associated RLC entities. When the channel quality of the communication link corresponding to the RLC entity is poor, it will lead to an increase in the packet loss rate and transmission delay of the entire service, because the packet loss and delay conditions of the single link correspond to those of the entire service.

[0099] 2. Carrier Aggregation

[0100] Carrier Aggregation (CA) can aggregate multiple component carriers (CCs) together to increase the transmission bandwidth. In CA, a PDCP entity can be associated with an RLC entity. An RLC entity can be associated with multiple MAC entities. Data from the upper layer can be split at the RLC entity and sent through one of the associated multiple MAC entities.

[0101] Figure 3 A data splitting mode in CA is shown. For example, Figure 3 as shown, a PDCP entity is associated with an RLC entity. The RLC entity is associated with w MAC entities, where w is a positive integer. Data from the upper layer can be split at the RLC layer, and the data sent by the RLC entity will be transmitted through one of the w MAC entities.

[0102] As can be seen from the above, in CA, data from the upper layer is split at the RLC entity and sent through one of multiple associated MAC entities. When the channel quality of the carrier corresponding to this MAC entity is poor, it will lead to an increase in the packet loss rate and transmission delay of the entire service, because the packet loss and delay conditions of this single carrier correspond to those of the entire service.

[0103] The concepts or terms introduced above are described based on the concepts or terms defined in the reference protocol, but this does not mean that the embodiments of the present application can only be applied to existing systems. The concepts or terms involved in the embodiments of the present application can be applied to future systems. And the specific names of the concepts or terms (such as those involving functional descriptions) can be adjusted with the development of future systems.

[0104] As can be seen from the above, in DC or CA, the packet loss rate and transmission delay of a service depend on the channel quality of a single link or a single carrier. When the channel quality of this single link or single carrier is poor, it will lead to an increase in the packet loss rate and transmission delay of the entire service. Especially in weak coverage scenarios, poor channel quality of a single link or a single carrier will directly cause data packet loss and large air interface delay. And the packet loss rate and transmission delay are important factors affecting the user experience of a service. An increase in the packet loss rate and transmission delay will lead to a decline in the user experience of the service.

[0105] Table 1 shows a set of data on the impact of packet loss rate and delay jitter on the user experience. Among them, the mean opinion score (MOS) can be used as an indicator to measure the service quality or user experience. The higher the MOS, the better the service quality or user experience.

[0106] Table 1

[0107]

[0108] As can be seen from Table 1, the real-time transport protocol (RTP) packet loss rate of 0.09 in Group M is lower than the RTP packet loss rate of 0.15 in Group N, the RTP delay jitter of 121.09 ms in Group M is lower than the RTP delay jitter of 121.17 ms in Group N, and the average MOS of 4.43 in Group M is higher than the average MOS of 4.35 in Group N. That is, in the case of low packet loss rate and low delay jitter, the service quality or user experience is better.

[0109] In view of the above problems, the present application provides a communication method and a communication device, which can maximize the utilization of the available radio resources through redundant data transmission, reduce packet loss, reduce transmission delay, ensure the reliability of downlink data transmission of services, and help improve the user experience of services.

[0110] Embodiments of the present application are applicable to the transmission of downlink data of various services, such as the transmission of downlink data of small packet services.

[0111] The method embodiments of the present application will be described below.

[0112] It should be noted that the "entity of the first layer", "entity of the second layer" or "entity of the third layer" in the embodiments of the present application may also be respectively described as "the first layer", "the second layer" or "the third layer", or "the first protocol layer", "the second protocol layer" or "the third protocol layer", or "entity of the first layer", "entity of the second layer" or "entity of the third layer", etc., without limitation. The following will uniformly use "entity of the first layer", "entity of the second layer" or "entity of the third layer" for description. The "first layer", "second layer" or "third layer" may be logical layers.

[0113] It should also be noted that the "entity of the first layer", "entity of the second layer" or "entity of the third layer" may belong to the same device. For example, the "entity of the first layer", "entity of the second layer" or "entity of the third layer" are different modules of the same device. For example, entities of different protocol layers of an access network device or a terminal device may be different modules in the access network device or the terminal device. The "entity of the first layer", "entity of the second layer" or "entity of the third layer" may also belong to different devices. For example, entities of different protocol layers of an access network device or a terminal device may be independently set.

[0114] Figure 4 It is a schematic flowchart of a communication method 500 provided by an embodiment of the present application.

[0115] The method 500 may be executed by a first device. Without special instructions, the "first device" may refer to the first device itself, or may refer to a module or unit capable of supporting the first device to implement its functions. The method 500 includes at least part of the following content.

[0116] Step 501, an entity of the first layer of the first device receives first data.

[0117] Exemplarily, the entity of the first layer of the first device receives the first data from an entity of the upper layer of the first layer.

[0118] Among them, the entity of the first layer of the first device is associated with entities of multiple second layers. Hereinafter, only the example where the entity of the first layer of the first device is associated with the first entity of the second layer and the second entity of the second layer is described. The embodiments of the present application can be applied to scenarios where the entity of the first layer of the first device is associated with more entities of the second layer, such as a scenario where the entity of the first layer of the first device is associated with 3 entities of the second layer, a scenario where the entity of the first layer of the first device is associated with 4 entities of the second layer, etc.

[0119] The entity of the first layer of the first device is associated with the first entity of the second layer and the second entity of the second layer, which can be understood as: the entity of the first layer of the first device can send and receive data through the first entity of the second layer and the second entity of the second layer.

[0120] In the embodiments of the present application, the first entity of the second layer and the second entity of the second layer associated with the entity of the first layer of the first device can belong to the same device or different devices, without limitation. Exemplarily, in DC, the first entity of the second layer can belong to the first device, and the second entity of the second layer can belong to the second device. Exemplarily, in CA, the first entity of the second layer and the second entity of the second layer can both belong to the first device.

[0121] The embodiments of the present application do not limit the system type of the first device and / or the second device, or rather the RAT adopted by the first device and / or the second device. Exemplarily, the first device and / or the second device can be a 4G access network device or a 5G access network device, etc.

[0122] In addition, the system types of the first device and the second device can be the same. For example, in DC, both the first device and the second device can be 5G access network devices, such as NR-DC, etc. The system types of the first device and the second device can also be different. For example, in DC, the first device is a 5G access network device and the second device is a 4G access network device, such as NE-DC, etc. Another example is that in DC, the first device is a 4G access network device and the second device is a 5G access network device, such as EN-DC, etc.

[0123] The first device and / or the second device is a device of a certain system type, which can be understood as: the first device and / or the second device adopts or supports the RAT corresponding to this system type, or the first device and / or the second device supports the services of this system type, etc.

[0124] The embodiments of the present application do not limit the specific protocol layers of the first layer and the second layer.

[0125] Exemplarily, the first layer is the PDCP layer and the second layer is the RLC layer. That is, the PDCP entity of the first device receives PDCP service data units (SDUs) from the upper layer, and the PDCP entity of the first device is associated with the first RLC entity and the second RLC entity. Among them, the PDCP SDU includes first data.

[0126] Exemplarily, the first layer is the RLC layer and the second layer is the MAC layer. That is, the RLC entity of the first device receives RLC SDUs from the upper layer (such as the PDCP layer), and the RLC entity of the first device is associated with the first MAC entity and the second MAC entity. Among them, the RLC SDU includes first data.

[0127] Exemplarily, the first layer is the MAC layer and the second layer is the PHY layer. That is, the MAC entity of the first device receives MAC SDUs from the upper layer (such as the RLC layer), and the MAC entity of the first device is associated with the first PHY entity and the second PHY entity. Among them, the MAC SDU includes first data.

[0128] The embodiments of the present application do not limit the type of the first data. Exemplarily, the first data is user plane data, such as the data carried by a data protocol data unit (data PDU). Exemplarily, the first data is control plane data, such as the data carried by a control protocol data unit (control PDU).

[0129] Step 502, the entity of the first layer of the first device sends the first data through the first entity of the second layer and sends the first data through the second entity of the second layer.

[0130] Exemplarily, after receiving the first data, the entity of the first layer of the first device may copy the first data and send the original first data through the first entity of the second layer and send the copied first data through the second entity of the second layer.

[0131] Exemplarily, when the first data is downlink data, the entity of the first layer of the first device may send the first data to the terminal device through the first entity of the second layer and send the first data to the terminal device through the second entity of the second layer.

[0132] It should be noted that the first data in method 500 may refer to net data or payload. In this case, the entity of the first layer of the first device copying the first data may refer to the entity of the first layer of the first device copying the data after adding the header of the first layer. The data after adding the header of the first layer includes the first data, so that the original data and the copied data include the same header of the first layer and the first data. In addition, during the process of the entity of the first layer of the first device sending the first data through the first entity of the second layer, the entity of the second layer may also add a corresponding header to the first data.

[0133] Thus, based on method 500, the first device can send the same data through multiple links or multiple carriers, that is, it can simultaneously utilize the idle radio resources corresponding to multiple links or multiple carriers to transmit the same data. Taking multiple links as NR transmission links and LTE transmission links as an example, the first device can simultaneously utilize the idle radio resources of NR and LET to transmit the same data. In this way, method 500 can utilize the idle radio resources as much as possible through the redundant transmission of data. In addition, the first device sending the same data through multiple links or multiple carriers helps to reduce packet loss. For example, assume that the data to be sent includes data 1 to data 4, and the multiple links are NR transmission links and LTE transmission links. The data transmitted through the NR transmission link is lost, and data 3 is lost. The data 1 to data 4 are successfully transmitted through the LTE transmission link. In this way, the receiving device of the data can obtain all the data 1 to data 4 by combining and restoring the data received on the two transmission links. Compared with transmitting data 1 to data 4 only through the NR transmission link, packet loss can be reduced. In addition, the first device sending the same data through multiple links or multiple carriers helps to reduce the transmission delay. For example, assume that the data to be sent includes data 1 to data 4, and the multiple links are NR transmission links and LTE transmission links. Based on the current idle radio resources of NR, the NR transmission link can only transmit data 1 and data 2 and needs a period of time to continue transmitting data 3 and data 4. Based on the current idle radio resources of LTE, the LTE transmission link can transmit data 1 to data 4. The two links transmit data 1 to data 4 simultaneously. The receiving device of the data receives data 1 and data 2 through the NR transmission link and data 1 to data 4 through the LTE transmission link. The receiving device of the data can obtain all the data 1 to data 4 by combining and restoring the data received on the two transmission links. Compared with transmitting data 1 to data 4 only through the NR transmission link, the transmission delay of data 1 to data 4 can be reduced. Therefore, method 500 can utilize the idle radio resources as much as possible through the redundant transmission of data, helps to reduce packet loss and reduce the transmission delay, thereby ensuring the reliability of the data transmission of the service and helping to improve the user experience of the service.

[0134] In some other implementations, the entity of the first layer of the first device sends the first data through the first entity of the second layer, which may include: the entity of the first layer of the first device sends the first data to the first entity of the second layer; the first entity of the second layer sends the first data through the first entity of the third layer, and the first entity of the second layer sends the first data through the second entity of the third layer. Exemplarily, the first layer is the PDCP layer, the second layer is the RLC layer, and the third layer is the MAC layer. Exemplarily, the first layer is the RLC layer, the second layer is the MAC layer, and the third layer is the PHY layer. Exemplarily, the first layer is the PDCP layer, the second layer is the RLC layer, and the third layer is the PHY layer. Based on this implementation, the first data can be replicated in multiple protocol layers, so that the first device can send the same data through more links or more carriers, thereby utilizing more air interfaces to transmit the same data at the same time, which further reduces packet loss. Moreover, since different links are used to transmit the same data, the overall delay caused by the transmission delay of one of the links is avoided when different links transmit different data. When different links are used to transmit the same data, the state of one of the links will not affect the integrity of the data packet finally transmitted to the terminal device, thereby achieving the effect of reducing the transmission delay, thereby further ensuring the reliability of the data transmission of the service, and thus improving the user experience of the service. The description of this beneficial effect can be applied to the description of other similar implementations in this application, and will not be repeated here.

[0135] In some other implementations, method 500 may further include: an entity of the first layer of the first device determines that the frequency domain replication function is turned on. That is, when the frequency domain replication function of the first layer of the first device is turned on, the entity of the first layer of the first device sends the first data through the first entity of the second layer, and sends the first data through the second entity of the second layer. If the frequency domain replication function of the first layer of the first device is not turned on, the entity of the first layer of the first device may send the first data through the first entity of the second layer or send the first data to the second entity of the second layer. In this way, the entity of the first layer of the first device can send the same data through multiple links or multiple carriers when the frequency domain replication function is turned on, and send one data through a single link or a single carrier when the frequency domain replication function is not turned on, which helps to strike a balance between the reliability of data transmission and resource waste.

[0136] For control plane data, it can be sent by the method described in steps 501 and 502. In some other implementation manners, it can also be sent only through the entity corresponding to the second layer of the primary link or the primary component carrier. In this case, method 500 may further include: an entity of the first layer of the first device receives second data, where the second data is control plane data; the entity of the first layer of the first device sends the second data through a first entity of the second layer, and the first entity of the second layer is the entity corresponding to the primary link or the primary component carrier. For example, in EN-DC, the PDCP entity of the first device receives the second data and sends the second data through the RLC entity corresponding to the primary link or the primary component carrier.

[0137] Next, in combination with a specific scenario, taking the first device as an access network device and the first data as downlink data as an example, the process on the first device side in the embodiments of the present application will be described in detail.

[0138] Scenario 1: DC scenario

[0139] Figure 5 It is a schematic diagram of PDCP processing on the access network device side in the DC scenario.

[0140] Figure 5 Taking EN-DC and NR-DC as examples, the PDCP processing on the access network device side will be described. Figure 5 The PDCP entity in can correspond to the entity of the first layer above, and the payload carried in the PDU can correspond to the first data above. Figure 5 The LTE RLC entity in the (a) diagram of can correspond to the first entity of the second layer above, and the NR RLC entity can correspond to the second entity of the second layer above. Figure 5 The NR RLC entity #2 in the (b) diagram of can correspond to the first entity of the second layer above, and the NR RLC entity #1 can correspond to the second entity of the second layer above.

[0141] As Figure 5 shown in the (a) diagram of, in the EN-DC scenario, the PDCP entity of the access network device can perform PDCP duplication on PDCP PDUs (such as PDU#1 and PDU#2 in Figure 5 ), and send the original PDCP PDUs (such as PDU#1 and PDU#2 in Figure 5 ) to the NR RLC entity, and send the replicated PDCP PDUs (such as Figure 5The PDU#1' and PDU#2' in are sent to the LTE RLC entity, so that the original PDCP PDU and the replicated PDCP PDU are transmitted on the secondary cell group (SCG) and the master cell group (MCG) respectively. The PDCP processing on the access network device side in the EN-DC scenario is as Figure 5 shown in Figure (b) of. The PDCP processing on the access network device side in the NR-DC scenario is similar to that in the EN-DC, except that both RLC entities associated with the PDCP entity are NR RLC entities.

[0142] Figure 6 It is a schematic flowchart of the PDCP entity on the access network device side sending services in the DC scenario.

[0143] Figure 6 Taking EN-DC as an example, the process of the PDCP entity on the access network device side sending services is described. Figure 6 The PDCP entity in can correspond to the entity of the first layer above, the payload carried in the PDU or SDU can correspond to the first data above, the RLC entity corresponding to the primary link can correspond to the first entity of the second layer above, and the RLC entity corresponding to the secondary link can correspond to the second entity of the second layer above.

[0144] In Figure 6 , the access network device can implement packet replication at the PDCP layer. When the PDCP entity sends services, it can be configured as a sending PDCP entity, hereinafter simply referred to as the PDCP entity.

[0145] Step 701, the PDCP entity receives a PDCP SDU from the upper layer. The descriptions in Step 701 and Step 501 can be cross-referenced or referred to each other.

[0146] Step 702, the PDCP entity starts a discard timer associated with the PDCP SDU.

[0147] Step 703, the PDCP entity associates the COUNT value corresponding to TX_NEXT with the PDCP SDU.

[0148] Among them, TX_NEXT represents the COUNT value of the next PDCP SDU to be transmitted.

[0149] Step 704, the PDCP entity performs PDCP SDU header compression.

[0150] Step 705, the PDCP entity performs integrity protection for the PDCP SDU and encrypts TX_NEXT.

[0151] Step 706, the PDCP entity sets the sequence number (SN) of the PDCP PDU.

[0152] Wherein, the PDCP PDU is the PDCP PDU corresponding to the PDCP SDU.

[0153] Step 707, the PDCP entity increments TX_NEXT by 1.

[0154] Step 708, the PDCP entity determines whether PDCP duplication is configured. Or rather, the PDCP entity determines whether PDCP duplication is activated. Or rather, the PDCP entity determines whether the PDCP duplication function is enabled.

[0155] When PDCP duplication is configured, branch to step 709. When PDCP duplication is not configured, branch to step 713.

[0156] Step 709, when PDCP duplication is configured, the PDCP entity further determines whether the PDCP PDU in step 706 is a PDCP data PDU.

[0157] When the PDCP PDU is a PDCP data PDU, branch to step 710. When the PDCP PDU is a PDCP control PDU, branch to step 712.

[0158] Step 710, when the PDCP PDU is a PDCP data PDU, the PDCP entity performs PDCP duplication and duplicates the PDCP PDU at the packet transmission moment.

[0159] Wherein, the replicated PDCP PDU has the same information as the original PDCP PDU.

[0160] Step 711, the PDCP entity submits the original PDCP PDU to the associated NR RLC entity and submits the replicated PDCP PDU to the associated LTE RLC entity.

[0161] The descriptions in steps 711, 712 and step 502 can be cross-referenced or referred to each other.

[0162] Step 712, when the PDCP PDU is a PDCP control PDU, the PDCP entity sends the PDCP PDU to the RLC entity corresponding to the primary link.

[0163] Step 713, when PDCP replication is not configured, the PDCP entity determines whether the total amount of PDCP data and RLC data to be processed in the initial transmission of two associated RLC entities is greater than the splitting threshold.

[0164] When the total amount of data is greater than the splitting threshold, branch to step 714 is executed. When the total amount of data is less than or equal to the splitting threshold, branch to step 715 is executed.

[0165] Step 714, when the total amount of data is greater than the splitting threshold, the PDCP entity sends the PDCP PDU to the RLC entity corresponding to the primary link and the RLC entity corresponding to the secondary link.

[0166] Step 715, when the total amount of data is less than or equal to the splitting threshold, the PDCP entity sends the PDCP PDU to the RLC entity corresponding to the primary link.

[0167] In Figure 5 and Figure 6 , the access network device can replicate data packets at the PDCP layer and distribute the original data packets and the replicated data packets to different RLC entities for transmission. Figure 5 and Figure 6 For the beneficial effects of the solutions shown in

[0168] Scenario 2: CA scenario

[0169] Figure 7 is a schematic diagram of RLC processing on the access network device side in the CA scenario.

[0170] Figure 7 The RLC entities in Figure 7 can correspond to the entities in the first layer above, the payload carried in the SDU can correspond to the first data above, and any two of MAC entity #1, MAC entity #2,..., MAC entity #w can correspond to the first entity in the second layer and the second entity in the second layer above. As Figure 7 shown, the RLC entity of the access network device can perform RLC replication on the SDU (such as Figure 7 the SDU#1 and SDU#2 in Figure 7 ), and send the original SDU (such as Figure 7 the SDU#1 and SDU#2 in Figure 7 ) and the replicated SDU (such as Figure 7 the PDU#1”, PDU#2”, PDU#1”’, and PDU#2”’ in Figure 7 ) to different MAC entities, so that the original SDU and the replicated SDU are transmitted on the primary component carrier (PCC) and the secondary component carrier (SCC), respectively.

[0171] Figure 8 It is a schematic diagram of MAC processing on the access network device side in the CA scenario.

[0172] Figure 8 The MAC entity in it can correspond to the entity of the first layer above, the payload carried in the SDU can correspond to the first data above, and any two of the PHY entity #1, PHY entity #2, …, PHY entity #v can correspond to the first entity of the second layer and the second entity of the second layer above. And Figure 7 Different from Figure 8 in it, the MAC entity of the access network device performs MAC duplication on the SDU, and sends the original SDU and the duplicated SDU to different PHY entities, so that the original SDU and the duplicated SDU are transmitted on the PCC and SCC respectively.

[0173] Next, taking the RLC entity of the access network device performing RLC duplication on the SDU as an example, the process of the PDCP entity on the access network device side sending services in the CA scenario will be described.

[0174] In the CA scenario, the RLC entity can be configured to execute data transmission in any one of the following modes: transparent mode (TM), UM, or AM. The embodiments of the present application are applicable to UM and AM. Next, the process of the PDCP entity on the access network device side sending services under UM and the process of the PDCP entity on the access network device side sending services under AM will be described respectively.

[0175] 1) UM

[0176] Figure 9 It is a schematic process of the RLC entity on the access network device side sending services in the CA scenario Figure 1 .

[0177] Figure 9 What is shown is the process of the RLC entity on the access network device side sending services under UM. Figure 9 The RLC entity in it can correspond to the entity of the first layer above, the payload carried in the PDU or SDU can correspond to the first data above, the MAC entity corresponding to the primary component carrier can correspond to the first entity of the second layer above, and the MAC entity corresponding to the secondary component carrier can correspond to the second entity of the second layer above.

[0178] In Figure 9 it, the access network device can implement packet duplication at the RLC layer. When the RLC entity sends services, it can be configured as a sending RLC entity, hereinafter simply referred to as the RLC entity.

[0179] Step 1001, the RLC entity receives an RLC SDU from the upper layer.

[0180] Among them, the upper layer may refer to the PDCP layer. The descriptions in Step 1001 and Step 501 may refer to or reference each other.

[0181] Step 1002, the RLC entity determines whether to fragment the RLC SDU.

[0182] Among them, fragmentation may also be referred to as segmentation.

[0183] When it is determined to fragment the RLC SDU, the branch of Step 1003 is executed. When it is determined not to fragment the RLC SDU, the branch of Step 1006 is executed.

[0184] Step 1003, the RLC entity sets the SN of the UM data (UMD) PDU to TX_NEXT.

[0185] Among them, the UMD PDU is an RLC PDU generated based on a segment of the RLCSDU, that is, whether the UMD PDU contains a segment of the RLCSDU.

[0186] Step 1004, the RLC entity determines whether the UMD PDU is the last fragment corresponding to the RLC SDU.

[0187] That is, the RLC entity determines whether the UMD PDU is the last UMD PDU generated based on the RLC SDU.

[0188] When the UMD PDU is the last fragment corresponding to the RLC SDU, the branch of Step 1005 is executed. When the UMD PDU is not the last fragment corresponding to the RLC SDU, the branch of Step 1006 is executed.

[0189] Step 1005, the RLC entity increments TX_NEXT by 1.

[0190] Step 1006, the RLC determines whether RLC duplication is configured. Or rather, the RLC entity determines whether RLC duplication is activated. Or rather, the RLC entity determines whether the RLC duplication function is enabled.

[0191] When RLC duplication is configured, the branch of Step 1007 is executed. When RLC duplication is not configured, the branch of Step 1009 is executed.

[0192] Step 1007, when RLC duplication is configured, the RLC entity performs RLC duplication and copies the UMD PDU at the packet sending moment.

[0193] Among them, the copied UMD PDU has the same information as the original UMD PDU.

[0194] Step 1008: The RLC entity submits the original PDCP PDU to the MAC entity corresponding to the associated primary component carrier, and submits the copied PDCP PDU to the MAC entity corresponding to the associated secondary component carrier.

[0195] The descriptions in Steps 1007 and 1008 and those in Step 502 can be referred to or referenced mutually.

[0196] Step 1009: When RLC duplication is not configured, the RLC entity determines whether the total amount of pending RLC data and MAC data in the initial transmission of the associated MAC entity is greater than the splitting threshold.

[0197] When the total amount of data is less than or equal to the splitting threshold, the branch of Step 1011 is executed. When the total amount of data is greater than the splitting threshold, the branch of Step 1010 is executed.

[0198] Step 1010: When the total amount of data is greater than the splitting threshold, the RLC entity distributes the UDM PDU to the MAC entity corresponding to the primary component carrier and the MAC entity corresponding to the secondary component carrier.

[0199] Step 1011: When the total amount of data is less than or equal to the splitting threshold, the RLC entity distributes the UMD PDU to the MAC entity corresponding to the primary component carrier.

[0200] In Figure 9 , the access network device can duplicate data packets at the RLC layer and distribute the original data packets and the copied data packets to different MAC entities for transmission. Figure 9 The beneficial effects of the solution shown can refer to the beneficial effects of Method 500 and will not be elaborated here.

[0201] 2) AM

[0202] Figure 10 is a schematic process of the RLC entity on the access network device side sending services in the CA scenario Figure 2 .

[0203] Figure 10 Shows the process of the RLC entity on the access network device side sending services under AM. Figure 10 The RLC entity in

[0204] In Figure 10 , the access network device can replicate data packets at the RLC layer. When the RLC entity sends services, it can be configured as a sending RLC entity, hereinafter simply referred to as the RLC entity.

[0205] Step 1101, the RLC entity receives an RLC SDU from the upper layer.

[0206] Among them, the upper layer can refer to the PDCP layer. The descriptions in Step 1101 and Step 501 can be referenced or referred to each other.

[0207] Step 1102, the RLC entity maintains a transmission window according to the status variable.

[0208] The RLC entity does not submit any AM data (AM data, AMD) PDU whose SN falls outside the transmission window to its lower layer.

[0209] Step 1103, the RLC entity associates the SN with the RLC SDU equal to TX_NEXT, and constructs an AMD PDU by setting the SN of the AMD PDU to TX_NEXT.

[0210] Step 1104, the RLC entity increments TX_NEXT by 1.

[0211] Step 1105, the RLC determines whether RLC replication is configured. Or rather, the RLC entity determines whether RLC replication is activated. Or rather, the RLC entity determines whether the RLC replication function is enabled.

[0212] When RLC replication is configured, branch to Step 1106 is executed. When RLC replication is not configured, branch to Step 1108 is executed.

[0213] Step 1106, when RLC replication is configured, the RLC entity performs RLC replication and replicates the AMD PDU at the packet sending moment.

[0214] Among them, the replicated AMD PDU has the same information as the original AMD PDU.

[0215] Step 1107, the RLC entity submits the original PDCP PDU to the MAC entity corresponding to the associated primary component carrier, and submits the replicated PDCP PDU to the MAC entity corresponding to the associated secondary component carrier.

[0216] The descriptions in Steps 1106 and 1107 and Step 502 can be referenced or referred to each other.

[0217] Step 1108: When RLC duplication is not configured, the RLC entity determines whether the total amount of pending RLC data and MAC data in the associated MAC entity for the initial transmission is greater than the splitting threshold.

[0218] When the total amount of data is less than or equal to the splitting threshold, branch to Step 1110. When the total amount of data is greater than the splitting threshold, branch to Step 1109.

[0219] Step 1109: When the total amount of data is greater than the splitting threshold, the RLC entity sends the ADMPDU to the MAC entity corresponding to the primary component carrier and the MAC entity corresponding to the secondary component carrier.

[0220] Step 1110: When the total amount of data is less than or equal to the splitting threshold, the RLC entity sends the AMDPDU to the MAC entity corresponding to the primary component carrier.

[0221] Step 1111: The RLC entity determines whether it has received a positive acknowledgement (ACK) for the RLC SDU with SN = x.

[0222] Step 1112: When the RLC entity receives an ACK for the RLC SDU with SN = x, it sends an indication message to the upper layer that has successfully delivered the RLC SDU.

[0223] Among them, the indication message is used to indicate that the RLC SDU has been successfully transmitted.

[0224] Step 1113: The RLC entity refreshes the transmission window.

[0225] In Figure 10 , the access network device can duplicate the data packet at the RLC layer and distribute the original data packet and the duplicated data packet to different MAC entities for transmission. Figure 10 The beneficial effects of the solution shown can refer to the beneficial effects of Method 500 and will not be elaborated here.

[0226] The above describes the process on the first device side in combination with Figures 4 to 10 Next, the process on the third device side will be described.

[0227] Figure 11 is a schematic flowchart of the communication method 1200 provided by the embodiment of the present application.

[0228] Method 1200 can be executed by the third device. Without special instructions, the "third device" can refer to the third device itself or a module or unit that can support the third device to implement its functions. Method 1200 includes at least some of the following content.

[0229] In step 1201, the first entity in the second layer of the third device receives the first data and sends the first data to the entity in the first layer of the third device. Correspondingly, the entity in the first layer of the third device receives the first data from the first entity in the second layer of the third device.

[0230] In step 1202, the second entity in the second layer of the third device receives the first data and sends the first data to the entity in the first layer of the third device. Correspondingly, the entity in the first layer of the third device receives the first data from the second entity in the second layer of the third device.

[0231] The embodiments of the present application do not limit the specific protocol layers of the first layer and the second layer. Exemplarily, the first layer is the PDCP layer and the second layer is the RLC layer. Exemplarily, the first layer is the RLC layer and the second layer is the MAC layer. Exemplarily, the first layer is the RLC layer and the second layer is the PHY layer.

[0232] Exemplarily, the third device in the embodiments of the present application may be a terminal device.

[0233] When the first data is downlink data, the first entity and the second entity in the second layer of the third device may receive the first data from the first device, or receive the first data from the first device and the second device.

[0234] The embodiments of the present application do not limit the system types of the first entity in the second layer of the third device and / or the second entity in the second layer of the third device. The system types of the first entity in the second layer of the third device and / or the second entity in the second layer of the third device correspond to the system types of the corresponding first device or second device. Exemplarily, when both the first entity in the second layer of the third device and the second entity in the second layer of the third device correspond to the first device, if the first device is of the 4G system type, then both the first entity in the second layer of the third device and the second entity in the second layer of the third device may be of the 4G system type; if the first device is of the 5G system type, then both the first entity in the second layer of the third device and the second entity in the second layer of the third device may be of the 5G system type. Exemplarily, when the first entity in the second layer of the third device corresponds to the first device and the second entity in the second layer of the third device corresponds to the second device, if the first device is an access network device of the 4G system type and the second device is an access network device of the 5G system type, then the first entity in the second layer of the third device is of the 4G system type and the second entity in the second layer of the third device is of the 5G system type; if the first device is an access network device of the 5G system type and the second device is an access network device of the 4G system type, then the first entity in the second layer of the third device is of the 5G system type and the second entity in the second layer of the third device is of the 4G system type.

[0235] The entity in the second layer of the third device is of a certain standard. It can be understood that: the entity in the second layer of the third device adopts or supports the RAT corresponding to this standard, or the entity in the second layer of the third device supports the services of this standard, etc.

[0236] When both the first entity in the second layer of the third device and the second entity in the second layer of the third device correspond to the first device, the first entity in the second layer of the third device and the second entity in the second layer of the third device receive the first data from the first device. When the first entity in the second layer of the third device corresponds to the first device and the second entity in the second layer of the third device corresponds to the second device, the first entity in the second layer of the third device receives the first data from the first device, and the second entity in the second layer of the third device receives the first data from the second device.

[0237] The embodiments of the present application do not limit the type of the first data. Exemplarily, the first data is user plane data, such as the data carried by a data PDU (data PDU). Exemplarily, the first data is control plane data, such as the data carried by a control PDU (control PDU).

[0238] It should be noted that the first data in method 1200 may refer to the net data or payload. In this case, after receiving the data including the first data, the header of the second layer, and the header of the first layer, the entity in the second layer of the third device may remove the header of the second layer and deliver the data after removing the header of the second layer upward to the entity in the first layer of the third device. The data packet after removing the header of the second layer includes the first data and the header of the first layer. The first data and the header of the first layer included in the data delivered upward by the first entity in the second layer of the third device and the data delivered upward by the second entity in the second layer of the third device are the same.

[0239] Step 1203, the entity in the first layer of the third device processes the first data from the first entity in the second layer of the third device and the first data from the second entity in the second layer of the third device.

[0240] A possible implementation manner is that the entity in the first layer of the third device processes the first data from the first entity in the second layer of the third device and the first data from the second entity in the second layer of the third device, including: reordering processing and / or duplicate packet processing.

[0241] It should be noted that the entities in the first layer of the third device can be associated with multiple entities in the second layer. The above description is only an example in which the entity in the first layer of the third device is associated with the first entity in the second layer and the second entity in the second layer. The embodiments of the present application can be applied to scenarios where the entity in the first layer of the third device is associated with more entities in the second layer, such as a scenario where the entity in the first layer of the third device is associated with 3 entities in the second layer, a scenario where the entity in the first layer of the third device is associated with 4 entities in the second layer, and so on. The entity in the first layer of the third device is associated with the first entity in the second layer and the second entity in the second layer, which can be understood as: the entity in the first layer of the third device can send and receive data through the first entity in the second layer and the second entity in the second layer.

[0242] In this way, based on method 1200, the third device can receive the same data through multiple links or multiple carriers, that is, it can simultaneously utilize the available radio resources corresponding to multiple links or multiple carriers to transmit the same data. Taking the transmission links of the new radio and the long-term evolution as the multiple links, it can simultaneously utilize the available radio resources of the new radio and the long-term evolution to transmit the same data. Therefore, method 1200 can utilize the available radio resources as much as possible through the redundant transmission of data, so as to reduce packet loss, reduce transmission delay, ensure the reliability of the downlink data transmission of the service, and help improve the user experience of the service. For a more detailed description of the beneficial effects of method 1200, reference can be made to method 500, which will not be elaborated here.

[0243] In some other implementation manners, before the first entity in the second layer of the third device sends the first data to the entity in the first layer of the third device, the first entity in the second layer of the third device performs reordering processing and / or duplicate packet processing on the first data, and / or, before the second entity in the second layer of the third device sends the first data to the entity in the first layer of the third device, the second entity in the second layer of the third device performs reordering processing and / or duplicate packet processing on the first data. Based on this implementation manner, the time for the entity in the first layer of the third device to process the first data can be reduced. And since the first entity in the second layer of the third device and the second entity in the second layer of the third device can simultaneously perform reordering processing and / or duplicate packet processing on the first data, the overall data processing time can be reduced.

[0244] Next, in combination with a specific scenario, taking the third device as a terminal device and the first layer as the PDCP layer or the RLC layer as an example, the process on the third device side in the embodiments of the present application will be described in detail.

[0245] Scenario A: The PDCP entity of the terminal device performs reordering processing and / or duplicate packet processing

[0246] If the access network device side performs PDCP duplication at the PDCP entity and sends the original PDCP PDU and the replicated PDCP PDU to multiple associated RLC entities respectively, the PDCP entity of the terminal device can receive multiple PDCP PDUs from multiple RLC entities. The multiple PDCP PDUs are the same, and the processing of each PDCP PDU by the PDCP entity of the terminal device can refer to Section 5.2.2 of the standard protocol TS38.323.

[0247] Scenario B: The reordering process and / or duplicate packet process are performed by the RLC entity of the terminal device

[0248] If the access network device side performs RLC duplication at the RLC entity and sends the original RLC PDU and the replicated RLC PDU to multiple associated MAC entities respectively, the RLC entity of the terminal device can receive multiple RLC PDUs from multiple MAC entities. The multiple RLC PDUs are the same, and the processing of each RLC PDU by the RLC entity of the terminal device can be as follows Figures 12 to 15 shown.

[0249] The following combines Figure 12 and Figure 13 , and describes the process of the RLC entity of the terminal device receiving services under UM.

[0250] Figure 12 is a schematic diagram of the overall process of RLC processing on the terminal device side under UM.

[0251] When receiving a UMD PDU, the receiving UM RLC entity can perform the following operations:

[0252] 1) Detect whether a duplicate UMD PDU is received, discard the duplicate UMD PDU, and if out-of-order delivery is not configured and the UMD PDU is out-of-order, reorder the UMD PDU;

[0253] 2) Remove the RLC header;

[0254] 3) Based on the reordered UMD PDU, reconstruct the RLC SDU and deliver the RLC SDU to the upper layer in ascending order of RLC SN.

[0255] It can be seen that in the embodiments of the present application, duplicate packet discarding and reordering of UMD PDUs can be performed at the RLC entity (such as Figure 12 the receiving UM RLC entity in

[0256] Figure 12 For the description of other operations in, reference can be made to Section 5.2.2 of the relevant standard TS38.322, which will not be elaborated here.

[0257] Figure 13 It is a schematic diagram of the specific process of RLC processing on the terminal device side under UM.

[0258] Figure 13 The RLC entity in it can correspond to the entity of the first layer above, and the payload carried in the PDU or SDU can correspond to the first data above. In Figure 13 the terminal device can implement duplicate packet discard and reordering of data packets at the RLC layer. When receiving services, the RLC entity can be configured as a receiving RLC entity, hereinafter simply referred to as the RLC entity.

[0259] Step 1401, the RLC entity receives a UMD PDU from the lower layer.

[0260] Among them, the lower layer can refer to the MAC layer. The UDM PDU can be one of multiple identical UMDPDUs that the RLC entity can receive. The description in Step 1401 can be cross-referenced or referred to the description in Step 1201 or Step 1202.

[0261] Step 1402, the RLC entity maintains a reordering window and a reassembly window according to the status variable.

[0262] Step 1403, the RLC entity determines whether the header of the UMD PDU contains an SN.

[0263] When the header of the UMD PDU does not contain an SN, the branch of Step 1404 can be executed; when the header of the UMD PDU contains an SN, the branch of Step 1405 can be executed.

[0264] Step 1404, the RLC entity removes the RLC header in the UMD PDU and delivers the obtained RLC SDU to the upper layer.

[0265] Step 1405, the RLC entity determines whether the SN of the UDM PDU is within the receive window.

[0266] When the SN of the UDM PDU is within the receive window, the branch of Step 1406 can be executed; when the SN of the UDM PDU is not within the receive window, the branch of Step 1408 can be executed.

[0267] Step 1406, the RLC entity puts the UDM PDU into the receive buffer.

[0268] Step 1407, the RLC entity determines whether a duplicate UDM PDU is received.

[0269] When the UDM PDU is a duplicate UDM PDU, the branch of step 1408 can be executed; when the UDM PDU is not a duplicate UDM PDU, the branches of step 1409, step 1412, and step 1418 can be executed.

[0270] Step 1408, the RLC entity discards the received UMD PDU.

[0271] Step 1409, the RLC entity determines whether all segments of the RLC SDU with SN = x have been received.

[0272] When all segments of the RLC SDU with SN = x have been received, the branch of step 1410 can be executed.

[0273] Step 1410, the RLC entity reassembles the RLC SDU based on all segments with SN = x.

[0274] Step 1411, the RLC entity removes the RLC header and delivers the reassembled RLC SDU to the upper layer.

[0275] Step 1412, the RLC entity determines whether x is equal to RX_Next_Reassembly.

[0276] Where RX_Next_Reassembly represents the SN of the next reassembly SDU expected to be received.

[0277] When x is equal to RX_Next_Reassembly, the branch of step 1413 can be executed.

[0278] Step 1413, the RLC entity updates the reassembly window.

[0279] Step 1414, the RLC entity determines whether the reordering timer is running and whether the SN falls outside the reordering window.

[0280] When the reordering timer is running and the SN falls outside the reordering window, the branch of step 1415 is executed; otherwise, the branch of step 1416 is executed.

[0281] Step 1415, the RLC entity stops and resets the reordering timer.

[0282] Step 1414, the RLC entity updates the reordering window.

[0283] Step 1417, the RLC entity reorders the RLC SDU, deletes the RLC header, and delivers it to the upper layer.

[0284] Step 1418, the RLC entity determines whether SN = x is outside the reassembly window.

[0285] Execute the branch of step 1419 when SN = x is outside the reordering window.

[0286] Step 1419, the RLC entity updates the receive window.

[0287] Step 1420, the RLC entity discards the UMD PDUs whose SNs are no longer outside the reordering window.

[0288] The descriptions in steps 1402 - 1420 and step 1203 can be cross - referenced or referred to each other.

[0289] In Figure 12 and Figure 13 , the terminal device can perform duplicate packet discarding and reordering on data packets at the RLC layer (as shown in steps 1402, 1407, 1414 - 1417). Figure 12 and Figure 13 For the beneficial effects of the solutions shown, reference can be made to the beneficial effects of method 1200, which will not be elaborated here.

[0290] Next, in combination with Figure 14 and Figure 15 , the process of the RLC entity on the terminal device side receiving services under AM is described.

[0291] Figure 14 is a schematic diagram of the overall process of RLC processing on the terminal device side under AM.

[0292] When an AMD PDU is received, the receiving AM RLC entity can perform the following operations:

[0293] 1) Detect whether a duplicate AMD PDU is received, discard the duplicate AMD PDU, and if out - of - order delivery is not configured and the AMD PDU is out - of - order, reorder the AMD PDU;

[0294] 2) Detect the loss of RLC data PDUs and request the transmitting AM RLC entity to re - transmit the lost RLC data PDUs;

[0295] 3) Remove the RLC header;

[0296] 4) If out - of - order delivery is not configured, based on the reordered AMD PDU, reassemble the RLC SDU and deliver the RLC SDU to the upper layer in order; if out - of - order delivery is configured, based on the reordered AMD PDU, reassemble the RLC SDU and directly deliver the RLC SDU to the upper layer.

[0297] It can be seen that in the embodiments of the present application, duplicate packet discarding and reordering of AMD PDUs can be performed at the RLC entity (such as the receiving AM RLC entity in Figure 14 ).

[0298] Figure 14 For the description of other operations, reference can be made to Section 5.2.3 of the relevant standard TS38.322, which will not be elaborated here.

[0299] Figure 15 It is a schematic diagram of the specific process of RLC processing on the terminal device side under AM.

[0300] Figure 15 The RLC entity in it can correspond to the entity of the first layer above, and the payload carried in the PDU or SDU can correspond to the first data above. In Figure 15 In, the terminal device can implement duplicate packet discard and reordering of data packets at the RLC layer. When receiving services, the RLC entity can be configured as a receiving RLC entity, hereinafter simply referred to as the RLC entity.

[0301] Step 1601, the RLC entity receives an AMD PDU from the lower layer.

[0302] Among them, the lower layer can refer to the MAC layer. The ADM PDU can be one of multiple identical AMDPDUs that the RLC entity can receive. The description in Step 1601 can be cross-referred to or referenced with the description in Step 1201 or Step 1202.

[0303] Step 1602, the RLC entity determines whether the SN of the ADM PDU is within the receiving window.

[0304] When the SN of the ADM PDU is within the receiving window, the branch of Step 1603 can be executed; when the SN of the ADM PDU is not within the receiving window, the branch of Step 1605 can be executed.

[0305] Step 1603, when the SN of the ADM PDU is within the receiving window, the RLC entity determines whether it has received a duplicate ADMPDU.

[0306] When the ADM PDU is a duplicate ADM PDU, the branch of Step 1605 can be executed; when the ADM PDU is not a duplicate ADM PDU, the branch of Step 1604 can be executed.

[0307] Step 1604, when the ADM PDU is not a duplicate, the RLC entity puts the ADM PDU into the receive buffer.

[0308] Step 1605, the RLC entity discards the received AMD PDU.

[0309] Step 1606, the RLC entity determines whether it has not received some segments of the RLC SDU contained in the AMD PDU.

[0310] When some segments of the RLC SDU contained in the AMD PDU have not been received, the branch of step 1608 can be executed; when some segments of the RLC SDU contained in the AMD PDU have been received, the branch of step 1607 can be executed.

[0311] Step 1607, when some segments of the RLC SDU contained in the AMD PDU have been received, the RLC entity discards the duplicate segments.

[0312] Step 1608, when some segments of the RLC SDU contained in the AMD PDU have not been received, the RLC entity determines whether SN = x is greater than or equal to RX_NEXT_highest.

[0313] Wherein, RX_NEXT_highest represents the SN upper limit of the reordering window.

[0314] When SN = x is greater than or equal to RX_NEXT_highest, the branch of step 1609 can be executed; when SN = x is less than RX_NEXT_highest, the branch of step 1610 can be executed.

[0315] Step 1609, when SN = x is greater than or equal to RX_NEXT_highest, the RLC entity updates the receive window.

[0316] Step 1610, the RLC entity determines whether all segments of the RLC SDU with SN = x have been received.

[0317] When all segments of the RLC SDU with SN = x have been received, the branch of step 1611 can be executed. When all segments of the RLC SDU with SN = x have not been received, the branch of step 1612 can be executed.

[0318] Step 1611, when all segments of the RLC SDU with SN = x have been received, the RLC entity reassembles the RLC SDU based on all segments of the RLC SDU with SN = x, removes the RLC header and delivers the reassembled RLC SDU to the upper layer.

[0319] Step 1612, when all segments of the RLC SDU with SN = x have not been received, the RLC entity determines whether the reordering timer has timed out.

[0320] When the reordering timer has timed out, the branch of step 1613 can be executed.

[0321] Step 1613, when the reordering timer has timed out, the RLC entity updates the receive window.

[0322] Step 1614, the RLC entity reassembles the packet.

[0323] Step 1615, the RLC entity resets the reordering timer.

[0324] Step 1616, the RLC entity determines whether the reordering timer is running and whether the SN falls outside the reordering window.

[0325] When the reordering timer is running and the SN falls outside the reordering window, execute the branch of Step 1617; otherwise, execute the branch of Step 1618.

[0326] Step 1617, the RLC entity stops and resets the reordering timer.

[0327] Step 1618, the RLC entity updates the reordering window.

[0328] Step 1619, the RLC entity reorders the RLC SDU.

[0329] Step 1620, the RLC entity deletes the RLC header and delivers it to the upper layer.

[0330] The descriptions in Steps 1602 - 1620 and Step 1203 can be cross - referenced or referred to each other.

[0331] In Figure 14 and Figure 15 , the terminal device can perform duplicate packet discard and reordering on data packets at the RLC layer (as shown in Steps 1603, 1616 - 1620). Figure 14 and Figure 15 For the beneficial effects of the solutions shown, reference can be made to the beneficial effects of Method 1200, and details will not be repeated.

[0332] Above, in combination with Figures 4 to 15 , the method embodiments provided by the present application have been described in detail. Next, in combination with Figures 16 to 18 , the apparatus embodiments of the present application will be described.

[0333] It can be understood that, in order to implement the functions in the above - mentioned embodiments, Figures 16 to 18 the apparatus in

[0334] Figure 16 and Figure 17 are schematic structural diagrams of possible apparatuses provided by the embodiments of the present application. These apparatuses can be used to implement the functions of the first apparatus, the second apparatus, or the third apparatus in the above - mentioned method embodiments, and thus can also achieve the beneficial effects of the above - mentioned method embodiments.

[0335] As Figure 16 shown, the device 10 includes a transceiver unit 11 and a processing unit 12.

[0336] When the device 10 is used to implement the functions of the first device in the above method embodiments, the transceiver unit 11 is used to perform the transceiver steps of the first device, and the processing unit 12 is used to perform the processing steps of the first device. When the device 10 is used to implement the functions of the second device in the above method embodiments, the transceiver unit 11 is used to perform the transceiver steps of the second device, and the processing unit 12 is used to perform the processing steps of the second device. When the device 10 is used to implement the functions of the third device in the above method embodiments, the transceiver unit 11 is used to perform the transceiver steps of the third device, and the processing unit 12 is used to perform the processing steps of the third device.

[0337] For a more detailed description of the above transceiver unit 11 and processing unit 12, reference can be made to the relevant descriptions in the above method embodiments, which will not be elaborated here.

[0338] As Figure 17 shown, the device 20 includes a processor 21. The processor 21 is coupled to a memory 23, and the memory 23 is used to store instructions. When the device 20 is used to implement the method described above, the processor 21 is used to execute the instructions in the memory 23 to implement the functions of the above processing unit 12.

[0339] In a possible implementation, the device 20 further includes a memory 23.

[0340] In a possible implementation, the device 20 further includes an interface circuit 22. The processor 21 and the interface circuit 22 are coupled to each other. It can be understood that the interface circuit 22 can be a transceiver or an input / output interface. When the device 20 is used to implement the method described above, the processor 21 is used to execute instructions to implement the functions of the above processing unit 12, and the interface circuit 22 is used to implement the functions of the above transceiver unit 11.

[0341] Exemplarily, when the device 20 is a chip applied to the first device, the second device or the third device, the chip implements the functions of the first device, the second device or the third device in the above method embodiments. The chip receives information from other modules (such as a radio frequency module or an antenna) in the first device, the second device or the third device, and the information is sent by other devices to the first device, the second device or the third device; or, the chip sends information to other modules (such as a radio frequency module or an antenna) in the first device, the second device or the third device, and the information is sent by the first device, the second device or the third device to other devices.

[0342] Figure 18It is a schematic diagram of a chip system 30 provided by an embodiment of the present application. The chip system 30 (or can also be referred to as a processing system) includes a logic circuit 31 and an input / output interface 32.

[0343] Among them, the logic circuit 31 can be the processing circuit in the chip system 30. The logic circuit 31 can be coupled to a storage unit and call instructions in the storage unit, so that the chip system 30 can implement the methods and functions of the embodiments of the present application. The input / output interface 32 can be the input / output circuit in the chip system 30, output the information processed by the chip system 30, or input the data or signaling information to be processed into the chip system 30 for processing.

[0344] As a solution, the chip system 30 is used to implement the operations performed by the first device, the second device, or the third device in the above method embodiments.

[0345] For example, the logic circuit 31 is used to implement the processing-related operations performed by the first device, the second device, or the third device in the above method embodiments; the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the first device, the second device, or the third device in the above method embodiments.

[0346] The present application also provides a communication device, including a processor, the processor is coupled to a memory, the memory is used to store computer programs or instructions and / or data, the processor is used to execute the computer programs or instructions stored in the memory, or read the data stored in the memory to execute the methods in the above method embodiments. A possible implementation manner is that the processor is one or more. A possible implementation manner is that the communication device includes a memory. A possible implementation manner is that the memory is one or more. A possible implementation manner is that the memory is integrated with the processor or is separately provided.

[0347] The present application also provides a chip, including a processor, the processor is coupled to a memory, the memory is used to store computer programs or instructions, and the processor is used to execute the computer programs or instructions stored in the memory to implement the methods performed by the first device, the second device, or the third device in the above method embodiments.

[0348] The present application also provides a computer-readable storage medium, on which computer instructions for implementing the methods performed by the first device, the second device, or the third device in the above method embodiments are stored.

[0349] The present application also provides a computer program product, including instructions, which when executed by a computer, implement the methods performed by the first device, the second device, or the third device in the above method embodiments.

[0350] The present application further provides a communication system, which includes at least one of the first device, the second device or the third device in the above embodiments.

[0351] For the explanations and beneficial effects of the relevant content in any of the above provided devices, reference may be made to the corresponding method embodiments provided above, and details are not described herein again.

[0352] It can be understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) 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.

[0353] The method steps in the embodiments of the present application may be implemented in a hardware manner or by a processor executing software instructions. The software instructions may be composed of corresponding software modules, and the software modules may be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a removable hard disk, a compact disc read-only memory (CD-ROM) or any other form of storage medium well known in the art. 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. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may be located in an ASIC. Additionally, the ASIC may be located in the first device, the second device or the third device. Of course, the processor and the storage medium may also exist as discrete components in the first device, the second device or the third device.

[0354] In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable devices. The computer program or instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer program or instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired or wireless manner. 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 or a data center integrating one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disc; or it may be a semiconductor medium, such as a solid-state drive.

[0355] In various embodiments of the present application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be cross-referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0356] Unless otherwise specified, all technical and scientific terms used in the embodiments of the present application have the same meaning as commonly understood by those skilled in the technical field of the present application. The terms used in the present application are only for the purpose of describing specific embodiments and are not intended to limit the scope of the present application. It should be understood that the above is for illustrative purposes only, and the above examples are only to help those skilled in the art understand the embodiments of the present application, rather than to limit the embodiments of the application to the specific numerical values or specific scenarios shown. Obviously, those skilled in the art can make various equivalent modifications or changes based on the examples given above, and such modifications and changes also fall within the scope of the embodiments of the present application.

Claims

1. A communication method, characterized in that, The method includes: An entity in the first layer of the first device receives first data, and the entity in the first layer is associated with a first entity and a second entity in the second layer; The entity in the first layer sends the first data through the first entity in the second layer and sends the first data through the second entity in the second layer.

2. The method according to claim 1, wherein The first layer is a Packet Data Convergence Protocol (PDCP) layer, and the second layer is a Radio Link Control (RLC) layer; or The first layer is a Radio Link Control (RLC) layer, and the second layer is a Medium Access Control (MAC) layer; or The first layer is a Medium Access Control (MAC) layer, and the second layer is a Physical (PHY) layer.

3. The method according to claim 1 or 2, wherein The first entity and the second entity in the second layer belong to the first device; or The first entity in the second layer belongs to the first device, and the second entity in the second layer belongs to a second device.

4. The method according to claim 3, wherein The first device and the second device have the same radio access technology (RAT).

5. The method according to claim 4, wherein The first device and the second device are access network devices of the fifth-generation RAT.

6. The method according to claim 3, wherein The first device and the second device have different RATs.

7. The method according to claim 6, wherein The first device is an access network device of the fifth-generation RAT, and the second device is an access network device of the fourth-generation RAT; or The first device is an access network device of the fourth-generation RAT, and the second device is an access network device of the fifth-generation RAT.

8. The method according to any one of claims 3 to 7, wherein The first device and the second device are two access network devices connected to the same terminal device in a dual connectivity scenario.

9. The method according to any one of claims 1 to 8, characterized in that, The entity in the first layer sends the first data through the first entity in the second layer, including: The entity in the first layer sends the first data to the first entity in the second layer; The first entity in the second layer sends the first data through a first entity in the third layer and sends the first data through a second entity in the third layer.

10. The method according to any one of claims 1 to 9, characterized in that, The first data is user plane data.

11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: The entity in the first layer receives second data, and the second data is control plane data; The entity in the first layer sends the second data through the first entity in the second layer, and the first entity in the second layer is the entity corresponding to the primary link or the primary component carrier.

12. A communication method, characterized in that, The method includes: The first entity in the second layer of the third device receives first data and sends the first data to the entity in the first layer of the third device; The second entity in the second layer receives the first data and sends the first data to the entity in the first layer; The entity in the first layer processes the first data from the first entity in the second layer and the first data from the second entity in the second layer.

13. A communication device, characterized in that, It includes a module or unit for executing the method according to any one of claims 1 to 12.

14. A communication device, characterized in that, It includes a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or send signals from the processor to other communication devices outside the communication device. The processor uses logic circuits or executes code instructions to implement the method according to any one of claims 1 to 12.

15. The communication device according to claim 14, characterized in that, The communication device is a chip or a chip system.

16. A computer-readable storage medium, characterized in that, A computer program or instruction is stored in the storage medium. When the computer program or instruction is executed by the communication device, the method according to any one of claims 1 to 12 is implemented.

17. A computer program product comprising instructions, characterized in that, When the instruction runs on a computer, the computer implements the method according to any one of claims 1 to 12.

18. A communication system, characterized in that, Comprising: A first device and a second device. The entity on the first layer of the first device is associated with the first entity on the second layer of the first device and the entity on the second layer of the second device. The first device is used to execute the method according to any one of claims 1 to 11, and the second device is used to receive and send data from the entity on the first layer of the first device.

19. A communication system, characterized in that, Comprising: An access network device for executing the method according to any one of claims 1 to 11, and a terminal device for executing the method according to claim 12.

Images