Communication method and communication apparatus

Abstract

A communication method and a communication apparatus. A first apparatus can perform frequency domain replication on a data packet in a packet data convergence protocol layer, a radio link control layer, or a medium access control layer, and distribute the original data packet and the replicated data packet to different links or carriers for transmission. In this way, idle air interfaces corresponding to multiple links or multiple carriers can be simultaneously utilized to transmit first data. Taking the multiple links being new radio transmission links and long-term evolution transmission links as an example, the first apparatus can simultaneously utilize idle new radio air interface resources and idle long-term evolution air interface resources. Therefore, the solution of the present application can utilize idle air interface resources as much as possible by means of redundant transmission of data, thereby reducing packet loss, reducing transmission delay, ensuring the reliability of downlink data transmission of services, and improving user experience of the services.

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 28, 2023, with application number 202311846267.8 and invention name “A Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0003] Packet loss rate and transmission latency are important factors that affect the user experience of services. Fluctuations in the channel environment can lead to increased packet loss rate, increased transmission latency, and even service interruptions, which can degrade the user experience. Summary of the Invention

[0004] The present application provides a communication method and a communication device to reduce packet loss and lower transmission delay, thereby improving the user experience of the service.

[0005] In a first aspect, a communication method is provided, comprising: an entity of a first layer of a first device receives first data, the entity of the first layer is associated with a first entity of a second layer and a second entity of the 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.

[0006] Exemplarily, the first device may be a first access network device. Unless otherwise specified, the "first access network device" may refer to the first access network device itself, or may refer to a device capable of supporting the first access network device in implementing its functions. When the first device is the first access network device, a first-layer entity of the first access network device may send first data to a terminal device via a first-layer entity of the second layer, and may send the first data to the terminal device via a second-layer entity of the second layer.

[0007] Based on the above method, the first device can send the first data through the first entity of the second layer 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 air interface spare resources corresponding to multiple links or multiple carriers can be used to transmit the first data at the same time. Taking the multiple links as the new wireless transmission link and the long-term evolution transmission link as an example, the air interface spare resources of the new wireless and long-term evolution can be used to transmit the first data at the same time. Therefore, the above method can make full use of the air interface spare resources by redundantly transmitting data to reduce packet loss, reduce transmission delay, ensure the reliability of downlink data transmission of the service, and help improve the user experience of the service.

[0008] In combination with the first aspect, in some possible implementations, 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 media access control (MAC); or, the first layer is a MAC layer, and the second layer is a physical (PHY) layer.

[0009] In combination with the first aspect or any implementation thereof, in some other possible implementations, 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 the second device.

[0010] In the above implementation, 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 is applicable to carrier aggregation scenarios. 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 is applicable to dual connectivity scenarios.

[0011] In combination with the first aspect or any implementation manner thereof, in some other possible implementation manners, the first device and the second device are of the same standard.

[0012] In combination with the first aspect or any implementation thereof, in some other possible implementations, the first device and the second device are access network devices of the fifth generation (5G) standard.

[0013] In combination with the first aspect or any implementation manner thereof, in some other possible implementation manners, the first device and the second device are of different systems.

[0014] In combination with the first aspect or any implementation thereof, in some other possible implementations, the first device is an access network device of the 5G standard, and the second device is an access network device of the fourth generation (4G) standard; or, the first device is an access network device of the 4G standard, and the second device is an access network device of the 5G standard.

[0015] In combination with the first 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.

[0016] In combination with the first aspect or any implementation manner thereof, in some other possible implementation manners, the method further includes: an entity in the first layer of the first device determining that a frequency domain replication function is enabled. That is, when the frequency domain replication function of 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.

[0017] Based on the above implementation method, 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 achieve a balance between the reliability of downlink data transmission and resource waste.

[0018] In combination with the first aspect or any implementation manner thereof, in some other possible implementation manners, the entity of the first layer of the first device sends the first data through the first entity of the second layer, including: 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.

[0019] Based on the above implementation method, the first data can be copied at 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, thereby further reducing packet loss and transmission delay, further ensuring the reliability of data transmission of the service, and thus improving the user experience of the service.

[0020] In combination with the first aspect or any implementation manner thereof, in some other possible implementation manners, the first data is user plane data.

[0021] In combination with the first aspect or any implementation thereof, in some other possible implementations, the method further includes: the entity of the first layer receives second data, where the second data is control plane data; the entity of the first layer sends the second data through the first entity of the second layer, where the first entity of the second layer is the main entity corresponding to the main link or main component carrier.

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

[0023] Exemplarily, the third device may be a terminal device. Unless otherwise specified, "terminal device" may refer to the terminal device itself, or may refer to a module or unit that can support the terminal device to implement its functions.

[0024] Based on the above method, the first entity of the second layer and the second entity of the second layer of the third device can both receive the first data, that is, the third device can receive the same data through multiple links or multiple carriers. In this way, the air interface vacancies corresponding to multiple links or multiple carriers can be used to transmit the first data at the same time. Taking the multiple links as the new wireless transmission link and the long-term evolution transmission link as an example, the air interface vacancies of the new wireless and long-term evolution can be used to transmit the first data at the same time. Therefore, the above method can make full use of the air interface vacancies by redundantly transmitting data, so as to reduce packet loss, reduce transmission delay, ensure the reliability of data transmission of the service, and help improve the user experience of the service.

[0025] In combination with the second aspect, in some possible implementations, the processing includes reordering processing and / or duplicate packet processing.

[0026] In combination with the second aspect or any implementation thereof, in some other possible implementations, the first layer is a PDCP layer, and the second layer is an RLC layer; or, the first layer is an RLC layer, and the second layer is a MAC layer; or, the first layer is a MAC layer, and the second layer is a PHY layer.

[0027] In combination with the second aspect or any implementation thereof, in some other possible implementations, the first entity of the second layer of the third device receives the first data, including: the first entity of the second layer receives the first data from the first device; the second entity of the second layer of the third device receives the first data, including: the first entity of the second layer receives the first data from the first device; or, the first entity of the second layer of the third device receives the first data, including: the first entity of the second layer receives the first data from the first device; the second entity of the second layer of the third device receives the first data, including: the second entity of the second layer receives the first data from the second device.

[0028] In the above implementation, the first entity of the second layer and the second entity of the second layer of the third device both receive the first data from the first device, meaning that the above implementation is applicable to carrier aggregation scenarios. The first entity of the second layer of the third device receives the first data from the first device, and the second entity of the second layer of the third device receives the first data from the second device, meaning that the above implementation is applicable to dual connectivity scenarios.

[0029] In combination with the second aspect or any implementation manner thereof, in some other possible implementation manners, the first device and the second device are of the same standard.

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

[0031] In combination with the second aspect or any implementation manner thereof, in some other possible implementation manners, the first device and the second device are of different systems.

[0032] In conjunction 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. The first device is a 5G access network device, and the second device is a 4G access network device; or the first device is a 4G access network device, and the second device is a 5G access network device.

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

[0034] In combination 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.

[0035] Based on the above implementation, the time required for the first layer entity of the third device to process the first data can be reduced. Furthermore, because the first layer entity of the third device and the second layer entity of the third device can simultaneously perform reordering and / or duplicate packet processing on the first data, the overall data processing time can be reduced.

[0036] In a third aspect, a communication device is provided, configured to execute the method provided by any of the aforementioned aspects or implementations thereof. Specifically, the device may include units and / or modules, such as a processing unit and / or a transceiver unit, configured to execute the method provided by any of the aforementioned aspects or implementations thereof. The processing unit is configured to execute the processing steps of the method provided by any of the aforementioned aspects or implementations thereof. The transceiver unit is configured to execute the transceiver steps of the method provided by any of the aforementioned aspects or implementations thereof.

[0037] In one implementation, the device is a first device or a third device. When the device is the first device or the third device, the transceiver unit may be a transceiver, an input / output interface, or a communication interface; and 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.

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

[0039] In a fourth aspect, a communication device is provided, comprising: a memory for storing programs; and at least one processor for executing computer programs or instructions stored in the memory to perform the method provided by any one of the above aspects or its implementation.

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

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

[0042] In a fifth aspect, a communication device is provided, comprising: at least one processor and a communication interface, wherein the at least one processor is configured to retrieve a computer program or instruction stored in a memory through the communication interface to execute the method provided by any of the above aspects or implementations thereof. The communication interface may be implemented in hardware or software.

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

[0044] In a sixth aspect, a processor is provided for executing the methods provided in the above aspects.

[0045] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as operations such as processor output, reception, and input, or as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

[0046] In a seventh aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes a method for executing any one of the above aspects or its implementation.

[0047] In an eighth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the method provided by any one of the above aspects or its implementation.

[0048] In a ninth aspect, a chip is provided, comprising a processor and a communication interface, wherein the processor reads instructions stored in a memory through the communication interface and executes the method provided by any one of the above aspects or implementations thereof. The communication interface may be implemented in hardware or software.

[0049] Exemplarily, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored on the memory. When the computer program or instruction is executed, the processor is used to execute the method provided by any of the above aspects or its implementation methods.

[0050] When the method provided in this application is executed by a chip, this application does not limit the number of chips that implement the method. For example, the method can be executed by one chip or by two or more chips. Furthermore, when the number of chips implementing the method of this application is two or more, the chip manufacturers are not limited and can be the same manufacturer or different manufacturers.

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

[0052] Exemplarily, the first device may be a first access network device. Exemplarily, the second device may be a second access network device. Exemplarily, the third device may be a terminal device.

[0053] In an eleventh aspect, a computer program is provided, which, when executed on a computer, enables the method provided by any one of the above aspects or its implementation to be executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] FIG1 is a schematic diagram of the architecture of a communication system 1000 to which embodiments of the present application may be applied;

[0055] FIG2 is a schematic diagram of a data offloading mode in dual connectivity (DC);

[0056] FIG3 is a schematic diagram of a data offload mode in carrier aggregation (CA);

[0057] FIG4 is a schematic flow chart of a communication method 500 provided in an embodiment of the present application;

[0058] FIG5 is a schematic diagram of PDCP processing on the access network device side in a DC scenario;

[0059] FIG6 is a schematic flow chart of a PDCP entity sending a service on the access network device side in a DC scenario;

[0060] FIG7 is a schematic diagram of RLC processing on the access network device side in a CA scenario;

[0061] FIG8 is a schematic diagram of MAC processing on the access network device side in a CA scenario;

[0062] FIG9 is a schematic flow chart of a service sent by an RLC entity on the access network device side in a CA scenario;

[0063] FIG10 is a second schematic flow chart of a service sent by an RLC entity on the access network device side in a CA scenario;

[0064] FIG11 is a schematic flow chart of a communication method 1200 provided in an embodiment of the present application;

[0065] FIG12 is a schematic diagram of the overall process of RLC processing on the terminal device side in unacknowledged mode (UM);

[0066] FIG13 is a schematic diagram of a specific process of RLC processing on the terminal device side under UM;

[0067] FIG14 is a schematic diagram of the overall process of RLC processing on the terminal device side under acknowledged mode (AM);

[0068] FIG15 is a schematic diagram of a specific process of RLC processing on the terminal device side under AM;

[0069] FIG16 is a schematic structural diagram of a device provided in an embodiment of the present application;

[0070] FIG17 is another schematic structural diagram of the device provided in an embodiment of the present application;

[0071] FIG18 is a schematic diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0072] To facilitate understanding of the embodiments of the present application, the following explanations are made before introducing the embodiments of the present application.

[0073] "Indication" includes direct indication (also known as explicit indication) and implicit indication. Direct indication of information A refers to the inclusion of information A; implicit indication of information A refers to the indication of information A through the correspondence between information A and information B, as well as the direct indication of information B. The correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured. Information C is used to determine information D, including situations where information D is determined solely based on information C or based on information C and other information. Furthermore, information C can also be used to determine information D indirectly, for example, when 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 network element B being the destination of information A or an intermediate network element in the transmission path between the destination and the network element, and can include direct or indirect transmission of information to network element B. "Network element B receives information A from network element A" can be understood as network element A being the source of information A or an intermediate network element in the transmission path between the source and the network element, and can include direct or indirect receipt of information from network element A. The information may be processed as necessary between the source and destination of the information transmission, such as format changes, but the destination can understand the valid information from the source. The first, second, and other various digital numbers are only used for the convenience of description and are not used to limit the scope of the embodiments of the present application, such as distinguishing different messages, different information, etc. The "protocol" involved may refer to a standard protocol in the field of communications, for example, it may include the long term evolution (LTE) protocol, the new radio (NR) protocol and related protocols used in future communication systems, and this application does not limit this. Words such as "exemplary", "for example", "exemplarily", "as (another) example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as an "example" in this application should not be interpreted as being more preferred or more advantageous than other embodiments or design schemes. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized. "Multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can mean: 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 plural, respectively.Descriptions such as "when...", "in the case of...", "if...", and "if" all mean that the device will take corresponding actions under certain objective circumstances. They do not limit the time, nor do they require the device to make judgments when implementing them, nor do they imply the existence of other limitations.

[0074] In addition, the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0075] A communication system to which the embodiments of the present application can be applied is described below.

[0076] The embodiments of the present 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), world-wide interoperability for microwave access (WiMAX) communication system, 5G system or NR system or future communication system. The 5G mobile communication system described in the present 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 system.

[0077] A device in a communication system can send signals to or receive signals from another device. These signals may include information, signaling, or data. The term "device" can also be replaced by an entity, network entity, communication device, communication module, node, communication node, etc. This application uses devices as an example for description. For example, a communication system may include at least one terminal device and at least one network device. A network device can send downlink signals to a terminal device, and / or a terminal device can send uplink signals to a network device.

[0078] For example, FIG1 shows a schematic diagram of the architecture of a communication system 1000 used in an embodiment of the present application. As shown in FIG1 , the communication system includes a radio access network 100 and a core network 200. In one possible implementation, the communication system 1000 may also include the Internet 300. The RAN 100 may include at least one radio access network device (such as 110a and 110b in FIG1 ) and at least one terminal device (such as 120a-120j in FIG1 ). The terminal device is wirelessly connected to the radio access network device, and the radio access network device is wirelessly or wiredly connected to the core network. The core network device and the radio access network device may be independent and distinct physical devices, or the functions of the core network device and the logical functions of the radio access network device may be integrated into the same physical device, or a single physical device may integrate some of the functions of the core network device and some of the functions of the radio access network device. Terminal devices and radio access network devices may be connected to each other via wired or wireless means. FIG1 is only a schematic diagram. The communication system may further include other network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in FIG1 .

[0079] The terminal devices in the communication system 1000 may also be referred to as terminals, user equipment (UE), mobile stations, mobile terminals, etc. The terminal devices can be widely used in various scenarios, such as D2D, V2X, MTC, IoT, virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. The terminal devices can be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of the present application do not limit the device form of the terminal devices.

[0080] The radio access network 100 may be a cellular system related to the Third Generation Partnership Project (3GPP), such as a 4G mobile communication system, a 5G mobile communication system, or a future-oriented evolutionary system. The radio access network 100 may also be an open access network (O-RAN or ORAN) or a cloud radio access network (CRAN). The radio access network 100 may also be a communication system that integrates two or more of the above systems.

[0081] A radio access network device, sometimes also referred to as a radio access network node, radio access network entity, or access node, is part of a communication system and helps terminal devices achieve wireless access. The multiple radio access network devices in communication system 1000 can be nodes of the same type or different types.

[0082] In one possible scenario, a wireless access network device may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), or a base station in a future mobile communication system. A RAN node may be a macro base station (such as 110a in Figure 1 ), a micro base station or an indoor station (such as 110b in Figure 1 ), a relay node or a donor node, or a wireless controller in a CRAN scenario. Exemplarily, a wireless access network node may also be a server, a wearable device, a vehicle, or an onboard device. For example, the access network device in V2X technology may be a road side unit (RSU).

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

[0084] In different systems, CU, DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in the ORAN system, CU may also be called open-CU (open-CU, O-CU), DU may also be called open-DU (open-DU, O-DU), and RU may also be called open-RU (open-RU, O-RU). Any of the CU, DU, and RU units can be implemented as software modules, hardware modules, or a combination of software and hardware modules.

[0085] The embodiments of the present application do not limit the specific technology and specific device form used by the wireless access network device. For the convenience of description, the access network device is referred to as the wireless access network device.

[0086] Base stations and terminal devices can be fixed or mobile. They can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; on water; or on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of base stations and terminal devices.

[0087] The roles of base stations and terminal devices can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. For terminal devices 120j accessing the wireless access network 100 via 120i, terminal device 120i is a base station. However, for base station 110a, 120i is a terminal device, meaning that communication between 110a and 120i occurs via a wireless air interface protocol. Of course, communication between 110a and 120i can also occur via a base station-to-base station interface protocol. In this case, 120i is also a base station relative to 110a. Therefore, base stations and terminal devices can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be referred to as communication devices with base station functionality, and 120a-120j in Figure 1 can be referred to as communication devices with terminal functionality.

[0088] Communication between base stations and terminal devices, between base stations, and between terminal devices can be carried out through authorized spectrum, unauthorized spectrum, or both; communication can be carried out through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz. The embodiments of the present application do not limit the spectrum resources used for wireless communication.

[0089] In the embodiments of the present application, the functions of the base station may also be performed by a module (such as a chip) in the base station, or by a control subsystem that includes the base station functions. The control subsystem that includes the base station functions here may be a control center in the above-mentioned application scenarios such as smart grid, industrial control, smart transportation, and smart city. The functions of the terminal device may also be performed by a module (such as a chip or a modem) in the terminal device, or by a device that includes the terminal device functions.

[0090] 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 to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0091] It should also be understood that the above naming is only defined to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in other networks in the future.

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

[0093] The concepts and terms introduced below are explained with reference to those specified in the protocol. However, this does not mean that the embodiments of this application are applicable only to existing systems. The concepts and terms involved in the embodiments of this application can be applied to future systems. Furthermore, the specific names of the concepts and terms (for example, concepts and terms describing functionality) may be adjusted as future systems develop.

[0094] 1. Dual connection

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

[0096] 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), such as one is a 4G base station and the other is a 5G base station. The 4G RAT is also called evolved universal terrestrial radio access (E-UTRA), and the 5G RAT is also called NR. MR-DC includes: DC between E-UTRA and NR (E-UTRA-NR DC, EN-DC); DC between NG-RAN's E-UTRA 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 main 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 main 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 main base station connected to 5GC is the NR base station gNB, and the secondary base station is the LTE base station ng-eNB; in NR-DC, the main base station connected to 5GC is the NR base station gNB, and the secondary base station is the NR base station gNB.

[0097] In DC, a PDCP entity can be associated with multiple RLC entities. Multiple RLC entities can be deployed on multiple base stations. Each RLC entity can be associated with one or more MAC entities. Data from upper layers can be offloaded at the PDCP entity and sent through one of the multiple associated RLC entities.

[0098] Taking EN-DC as an example, Figure 2 shows a data diversion mode in DC. Figure 2 takes the Option3X architecture as an example. A PDCP entity is associated with two RLC entities of different standards. As shown in Figure 2, the NR PDCP entity is associated with the LTE RLC entity and the NR RLC entity. The two RLC entities are respectively associated with a MAC entity. As shown in Figure 2, the LTE RLC entity is associated with an LTE MAC entity, and the NR RLC entity is associated with an NR MAC entity. The data from the upper server reaches the NR PDCP entity through the NR S1-U interface and is diverted at the PDCP layer. The data sent by the NR PDCP entity will be sent to one of the LTE RLC entity and the NR RLC entity, and further sent through the associated MAC entity. The data reaches a MAC entity of the terminal device through the air interface and is further converged to the PDCP entity through the associated RLC entity.

[0099] As can be seen from the above, in DC, data from upper layers is split at the PDCP layer and sent to one of the associated RLC entities. When the channel quality of the communication link corresponding to this 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 of this single link are reflected in the packet loss and delay of the entire service.

[0100] 2. Carrier Aggregation

[0101] Carrier aggregation (CA) aggregates multiple component carriers (CCs) to increase transmission bandwidth. In CA, a PDCP entity can be associated with one RLC entity. An RLC entity can be associated with multiple MAC entities. Data from higher layers can be offloaded to the RLC entity and sent through one of the associated MAC entities.

[0102] Figure 3 illustrates a data offload model in CA. As shown in Figure 3, one PDCP entity is associated with one RLC entity. This RLC entity is associated with w MAC entities, where w is a positive integer. Data from upper layers can be offloaded at the RLC layer, with data sent by the RLC entity being transmitted through one of the w MAC entities.

[0103] As can be seen from the above, in CA, data from upper layers is offloaded at the RLC entity and sent through one of the multiple associated MAC entities. When the channel quality of the carrier corresponding to the MAC entity is poor, the packet loss rate and transmission delay of the entire service will increase, because the packet loss and delay of a single carrier are reflected in the packet loss and delay of the entire service.

[0104] The concepts and terms introduced above are described with reference to those specified in the protocol. However, this does not mean that the embodiments of this application are applicable only to existing systems. The concepts and terms involved in the embodiments of this application can be applied to future systems. Furthermore, the specific names of the concepts and terms (for example, concepts and terms describing functionality) may be adjusted as future systems develop.

[0105] 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 carrier. When the channel quality of a single link or carrier is poor, the packet loss rate and transmission delay of the entire service will increase. Especially in weak coverage scenarios, poor channel quality of a single link or carrier will directly cause data packet loss and large air interface delay. Packet loss rate and transmission delay are important factors affecting the user experience of services. Increased packet loss rate and transmission delay will lead to a decline in user experience of services.

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

[0107] Table 1

[0108] Table 1 shows that 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. The average MOS of 4.43 in group M is higher than the average MOS of 4.35 in group N. This means that with low packet loss rate and low delay jitter, service quality or user experience is better.

[0109] In response to the above problems, the present application provides a communication method and a communication device that can maximize the use of free air interface resources through redundant data transmission to reduce packet loss, reduce transmission delay, ensure the reliability of downlink data transmission of the service, and help improve the user experience of the service.

[0110] The 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 following describes the method embodiments of the present application.

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

[0113] It should also be noted that a "first layer entity," a "second layer entity," or a "third layer entity" may belong to the same device, such as a "first layer entity," a "second layer entity," or a "third layer entity" may be 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. A "first layer entity," a "second layer entity," or a "third layer entity" 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 configured.

[0114] FIG4 is a schematic flow chart of a communication method 500 provided in an embodiment of the present application.

[0115] Method 500 may be performed by a first device. Unless otherwise specified, "first device" may refer to the first device itself or a module or unit that supports the first device in performing its functions. Method 500 includes at least part of the following contents.

[0116] Step 501: An entity of a first layer of a first device receives first data.

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

[0118] The first-layer entity of the first device is associated with multiple second-layer entities. The following description only uses the association of the first-layer entity of the first device with the first entity of the second layer and the second entity of the second layer as an example. The embodiments of the present application can be applied to scenarios where the first-layer entity of the first device is associated with more second-layer entities, such as scenarios where the first-layer entity of the first device is associated with three second-layer entities, scenarios where the first-layer entity of the first device is associated with four second-layer entities, etc.

[0119] The first-layer entity of the first device is associated with the first-layer entity of the second layer and the second-layer entity of the second layer. It can be understood that the first-layer entity of the first device can send and receive data through the first-layer entity of the second layer and the second-layer entity.

[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 first entity of the first device may belong to the same device or different devices, without limitation. For example, in DC, the first entity of the second layer may belong to the first device, and the second entity of the second layer may belong to the second device. For example, in CA, the first entity of the second layer and the second entity of the second layer may both belong to the first device.

[0121] The embodiments of the present application do not limit the standard of the first device and / or the second device, or the RAT used by the first device and / or the second device. For example, the first device and / or the second device can be a 4G access network device or a 5G access network device.

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

[0123] The first device and / or the second device are devices of a certain standard, which can be understood as: the first device and / or the second device adopts or supports the RAT corresponding to the standard, or the first device and / or the second device supports services of the standard, 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 a PDCP layer, and the second layer is an RLC layer. That is, a PDCP entity of the first device receives a PDCP service data unit (SDU) from an upper layer, and the PDCP entity of the first device is associated with a first RLC entity and a second RLC entity, wherein 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 an RLC SDU from an upper layer (such as a PDCP layer), and the RLC entity of the first device is associated with a first MAC entity and a second MAC entity, wherein the RLC SDU includes the first data.

[0127] Exemplarily, the first layer is a MAC layer and the second layer is a PHY layer. That is, the MAC entity of the first device receives a MAC SDU from an upper layer (such as an RLC layer), and the MAC entity of the first device is associated with a first PHY entity and a second PHY entity, wherein the MAC SDU includes the 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 data carried by a data protocol data unit (data PDU). Exemplarily, the first data is control plane data, such as data carried by a control protocol data unit (control PDU).

[0129] In step 502 , a first layer entity of a first device sends first data through a first layer entity, and sends first data through a second layer entity.

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

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

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

[0133] In this way, based on method 500, the first device can send the same data through multiple links or multiple carriers, that is, it can simultaneously use the air interface spare resources corresponding to multiple links or multiple carriers to transmit the same data. Taking the multiple links as NR transmission links and LTE transmission links as an example, the first device can simultaneously use the air interface spare resources of NR and LTE to transmit the same data. In this way, method 500 can make use of the air interface spare resources as much as possible through redundant transmission of data. In addition, the first device can send the same data through multiple links or multiple carriers to help reduce packet loss. For example, assuming that the data to be sent includes data 1 to data 4, 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. Data 1 to data 4 are successfully transmitted through the LTE transmission link. In this way, the receiving end device of the data can obtain all data 1 to data 4 by merging and restoring the data received on the two transmission links. Compared with transmitting data 1 to data 4 through the NR transmission link alone, packet loss can be reduced. In addition, the first device can transmit the same data through multiple links or multiple carriers, which helps reduce transmission delay. For example, assuming that the data to be transmitted includes data 1 to data 4, and the multiple links are NR transmission links and LTE transmission links, based on the current available air interface resources of NR, the NR transmission link can only transmit data 1 and data 2 and requires a delay before continuing to transmit data 3 and data 4. Based on the current available air interface resources of LTE, the LTE transmission link can transmit data 1 to data 4. The two links simultaneously transmit data 1 to data 4. The data receiving device receives data 1 and data 2 through the NR transmission link and receives data 1 to data 4 through the LTE transmission link. The data receiving device can obtain all data 1 to data 4 by merging and restoring the data received on the two transmission links. Compared with transmitting data 1 to data 4 separately through the NR transmission link, the transmission delay of data 1 to data 4 can be reduced. Therefore, method 500 can maximize the use of available air interface resources through redundant data transmission, which helps reduce packet loss and transmission delay, thereby ensuring the reliability of data transmission of the service and improving the user experience of the service.

[0134] In other implementations, the first layer entity of the first device sending the first data via the first layer entity of the second device may include: the first layer entity of the first device sending the first data to the first layer entity of the second device; the first layer entity of the second device sending the first data via the first layer entity of the third device; and the first layer entity of the second device sending the first data via the second layer entity of the third device. 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, thereby further reducing 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 status of one of the links will not affect the integrity of the data packet ultimately 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 other implementations, method 500 may further include: the 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 through the methods described in steps 501 and 502. In other implementations, it can also be sent only through the second-layer entity corresponding to the primary link or primary component carrier. In this case, method 500 may also include: the first-layer entity of the first device receives the second data, and the second data is control plane data; the first-layer entity of the first device sends the second data through the first-layer first entity, and the first-layer first entity is the entity corresponding to the primary link or 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 primary component carrier.

[0137] In the following, 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 embodiment of the present application is described in detail.

[0138] Scene 1: DC scene

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

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

[0141] As shown in Figure 5 (a), in the EN-DC scenario, the PDCP entity of the access network device can perform PDCP replication on the PDCP PDU (such as PDU#1 and PDU#2 in Figure 5), and send the original PDCP PDU (such as PDU#1 and PDU#2 in Figure 5) to the NR RLC entity, and send the replicated PDCP PDU (such as PDU#1' and PDU#2' in Figure 5) 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 shown in Figure 5 (b). The PDCP processing on the access network device side in the NR-DC scenario is similar to the PDCP processing on the access network device side in EN-DC, except that the two RLC entities associated with the PDCP entity are both NR RLC entities.

[0142] FIG6 is a schematic flowchart of a PDCP entity on the access network device side sending a service in a DC scenario.

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

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

[0145] In step 701, the PDCP entity receives a PDCP SDU from an upper layer. The descriptions of step 701 and step 501 may be referenced to each other.

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

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

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

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

[0150] In step 705, the PDCP entity performs integrity protection on the PDCP SDU and ciphers TX_NEXT.

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

[0152] The PDCP PDU is the PDCP PDU corresponding to the PDCP SDU.

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

[0154] In step 708, the PDCP entity determines whether PDCP duplication is configured. In other words, the PDCP entity determines whether PDCP duplication is activated. In other words, the PDCP entity determines whether the PDCP duplication function is turned on.

[0155] When PDCP duplication is configured, the process proceeds to step 709. When PDCP duplication is not configured, the process proceeds 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, the process proceeds to step 710. When the PDCP PDU is a PDCP control PDU, the process proceeds to step 712.

[0158] In step 710, when the PDCP PDU is a PDCP data PDU, the PDCP entity performs PDCP replication to copy the PDCP PDU at the time of packet transmission.

[0159] The copied PDCP PDU has the same information as the original PDCP PDU.

[0160] In step 711, the PDCP entity submits the original PDCP PDU to the associated NR RLC entity and submits the copied PDCP PDU to the associated LTE RLC entity.

[0161] The descriptions in steps 711 and 712 and step 502 may be referenced or compared 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 the to-be-processed PDCP data and the RLC data initially transmitted in the two associated RLC entities is greater than the offload threshold.

[0164] When the total amount of data is greater than the diversion threshold, the process proceeds to step 714. When the total amount of data is less than or equal to the diversion threshold, the process proceeds to step 715.

[0165] Step 714: When the total amount of data is greater than the offload threshold, the PDCP entity sends the PDCP PDU to the RLC entity corresponding to the primary link and the RLC entity corresponding to the auxiliary link.

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

[0167] In Figures 5 and 6, the access network device can replicate the data packet at the PDCP layer and distribute the original data packet and the replicated data packet to different RLC entities for transmission. The beneficial effects of the solutions shown in Figures 5 and 6 can be referred to the beneficial effects of method 500 and will not be repeated here.

[0168] Scenario 2: CA Scenario

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

[0170] The RLC entity in Figure 7 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 MAC entity #1, MAC entity #2, ..., MAC entity #w can correspond to the first entity of the second layer and the second entity of the second layer above. As shown in Figure 7, the RLC entity of the access network device can perform RLC replication on the SDU (such as SDU#1 and SDU#2 in Figure 7), and send the original SDU (such as SDU#1 and SDU#2 in Figure 7) and the replicated SDU (such as 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] FIG8 is a schematic diagram of MAC processing on the access network device side in a CA scenario.

[0172] The MAC entity in Figure 8 may correspond to the first-layer entity described above, the payload carried in the SDU may correspond to the first data described above, and any two of PHY entity #1, PHY entity #2, ..., and PHY entity #v may correspond to the first entity and the second entity of the second layer described above. Unlike Figure 7 , in Figure 8 , the MAC entity of the access network device performs MAC replication on the SDU and sends the original and replicated SDUs to different PHY entities, allowing the original and replicated SDUs to be transmitted on the PCC and SCC, respectively.

[0173] The following describes the process of the PDCP entity on the access network device side sending services in the CA scenario, taking the RLC entity of the access network device performing RLC replication on the SDU as an example.

[0174] In a CA scenario, the RLC entity can be configured to perform data transmission in any of the following modes: transparent mode (TM), UM, or AM. The embodiments of the present application are applicable to both UM and AM. The following describes the process for the PDCP entity on the access network device side to send services in UM and AM, respectively.

[0175] 1)UM

[0176] FIG9 is a schematic flowchart 1 of the RLC entity on the access network device side sending a service in a CA scenario.

[0177] Figure 9 illustrates the process of transmitting services by an RLC entity on the access network device side under UM. The RLC entity in Figure 9 may correspond to the entity of the first layer described above, the payload carried in the PDU or SDU may correspond to the first data described above, the MAC entity corresponding to the primary component carrier may correspond to the first entity of the second layer described above, and the MAC entity corresponding to the secondary component carrier may correspond to the second entity of the second layer described above.

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

[0179] Step 1001: An RLC entity receives an RLC SDU from an upper layer.

[0180] The upper layer may refer to the PDCP layer. The descriptions in step 1001 and step 501 may be referenced or referred to each other.

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

[0182] Among them, shards can also be called segments.

[0183] When it is determined that the RLC SDU is to be fragmented, the process proceeds to step 1003. When it is determined that the RLC SDU is not to be fragmented, the process proceeds to step 1006.

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

[0185] The UMD PDU is an RLC PDU generated based on a segment of the RLC SDU, that is, whether the UMD PDU includes a segment of the RLC SDU.

[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 process goes to step 1005. When the UMD PDU is not the last fragment corresponding to the RLC SDU, the process goes to step 1006.

[0189] Step 1005: The RLC entity increments TX_NEXT by 1.

[0190] In step 1006, the RLC determines whether RLC duplication is configured. In other words, the RLC entity determines whether RLC duplication is activated. In other words, the RLC entity determines whether the RLC duplication function is turned on.

[0191] When RLC replication is configured, the process branches to step 1007. When RLC replication is not configured, the process branches to step 1009.

[0192] Step 1007: When RLC replication is configured, the RLC entity performs RLC replication and copies the UMD PDU at the time of packet transmission.

[0193] The copied UMD PDU has the same information as the original UMD PDU.

[0194] In 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 step 502 may be referenced or referred to each other.

[0196] Step 1009: When RLC replication is not configured, the RLC entity determines whether the total amount of RLC data to be processed and MAC data initially transmitted in the associated MAC entity is greater than the offload threshold.

[0197] When the total amount of data is less than or equal to the diversion threshold, the process proceeds to step 1011. When the total amount of data is greater than the diversion threshold, the process proceeds to step 1010.

[0198] Step 1010: When the total amount of data is greater than the offload threshold, the RLC entity sends 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 offload threshold, the RLC entity sends the UMD PDU to the MAC entity corresponding to the primary component carrier.

[0200] In Figure 9, the access network device can replicate the data packet at the RLC layer and distribute the original data packet and the replicated data packet to different MAC entities for transmission. The beneficial effects of the solution shown in Figure 9 can refer to the beneficial effects of method 500 and will not be repeated here.

[0201] 2) AM

[0202] FIG10 is a second schematic flow chart of the RLC entity on the access network device side sending services in a CA scenario.

[0203] Figure 10 shows the process of sending services by the RLC entity on the access network device side under AM. The RLC entity in Figure 10 may correspond to the entity of the first layer mentioned above, the payload carried in the PDU or SDU may correspond to the first data mentioned above, the MAC entity corresponding to the primary component carrier may correspond to the first entity of the second layer mentioned above, and the MAC entity corresponding to the secondary component carrier may correspond to the second entity of the second layer mentioned above.

[0204] In Figure 10, the access network device can implement data packet replication at the RLC layer. When an RLC entity sends a service, it can be configured as a sending RLC entity, hereinafter referred to as an RLC entity.

[0205] Step 1101: The RLC entity receives an RLC SDU from an upper layer.

[0206] The upper layer may refer to the PDCP layer. The descriptions in step 1101 and step 501 may be referenced or referred to each other.

[0207] Step 1102: The RLC entity maintains a sending window according to the state variables.

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

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

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

[0211] In step 1105, the RLC determines whether RLC replication is configured. In other words, the RLC entity determines whether RLC replication is activated. In other words, the RLC entity determines whether the RLC replication function is turned on.

[0212] When RLC replication is configured, the process branches to step 1106. When RLC replication is not configured, the process branches to step 1108.

[0213] Step 1106: When RLC replication is configured, the RLC entity performs RLC replication and copies the AMD PDU at the time of packet transmission.

[0214] The copied AMD PDU has the same information as the original AMD PDU.

[0215] In step 1107, 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.

[0216] The descriptions in steps 1106 and 1107 and step 502 may be referenced or referred to each other.

[0217] Step 1108: When RLC replication is not configured, the RLC entity determines whether the total amount of RLC data to be processed and MAC data initially transmitted in the associated MAC entity is greater than the offload threshold.

[0218] When the total amount of data is less than or equal to the diversion threshold, the process proceeds to step 1110. When the total amount of data is greater than the diversion threshold, the process proceeds to step 1109.

[0219] Step 1109: When the total amount of data is greater than the offload threshold, the RLC entity sends the ADM PDU 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 offload threshold, the RLC entity sends the AMD PDU to the MAC entity corresponding to the primary component carrier.

[0221] In step 1111 , the RLC entity determines whether a positive acknowledgement (ACK) for the RLC SDU with SN=x is received.

[0222] Step 1112: When receiving the ACK for the RLC SDU with SN=x, the RLC entity sends an indication to the upper layer of the successful delivery of the RLC SDU.

[0223] The indication information is used to indicate that the RLC SDU has been successfully transmitted.

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

[0225] In Figure 10, the access network device can replicate the data packet at the RLC layer and distribute the original data packet and the replicated data packet to different MAC entities for transmission. The beneficial effects of the solution shown in Figure 10 can be referred to the beneficial effects of method 500 and will not be repeated here.

[0226] The process on the first device side is described above with reference to Figures 4 to 10. The process on the third device side is described below.

[0227] FIG11 is a schematic flowchart of a communication method 1200 provided in an embodiment of the present application.

[0228] Method 1200 may be performed by a third device. Unless otherwise specified, "third device" may refer to the third device itself or a module or unit that supports the third device in performing its functions. Method 1200 includes at least part of the following contents.

[0229] Step 1201: A first entity of a second layer of a third device receives first data and sends the first data to an entity of a first layer of the third device. Accordingly, the entity of the first layer of the third device receives the first data from the first entity of the second layer of the third device.

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

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

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

[0233] When the first data is downlink data, the first entity and the second entity of 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 format of the first entity of the second layer of the third device and / or the second entity of the second layer of the third device. The format of the first entity of the second layer of the third device and / or the second entity of the second layer of the third device corresponds to the format of the first device or the second device to which it corresponds. For example, when the first entity of the second layer of the third device and the second entity of the second layer of the third device both correspond to the first device, if the first device is of 4G format, the first entity of the second layer of the third device and the second entity of the second layer of the third device may both be of 4G format, and if the first device is of 5G format, the first entity of the second layer of the third device and the second entity of the second layer of the third device may both be of 5G format. Exemplarily, when the first entity of the second layer of the third device corresponds to the first device and the second entity of the second layer of the third device corresponds to the second device, if the first device is a 4G access network device and the second device is a 5G access network device, then the first entity of the second layer of the third device is a 4G standard and the second entity of the second layer of the third device is a 5G standard; if the first device is a 5G access network device and the second device is a 4G access network device, then the first entity of the second layer of the third device is a 5G standard and the second entity of the second layer of the third device is a 4G standard.

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

[0236] When the first entity of the second layer of the third device and the second entity of the second layer of the third device both correspond to the first device, the first entity of the second layer of the third device and the second entity of the second layer of the third device receive the first data from the first device. When the first entity of the second layer of the third device corresponds to the first device and the second entity of the second layer of the third device corresponds to the second device, the first entity of the second layer of the third device receives the first data from the first device, and the second entity of 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 data carried by a data PDU. Exemplarily, the first data is control plane data, such as data carried by a control PDU.

[0238] It should be noted that the first data in method 1200 may refer to net data or payload. In this case, after receiving data including the first data, a second-layer header, and a first-layer header, the second-layer entity of the third device may remove the second-layer header and submit the data after the second-layer header is removed to the first-layer entity of the third device. The data packet after the second-layer header is removed includes the first data and the first-layer header. The data submitted upward by the first entity of the second layer of the third device and the data submitted upward by the second entity of the second layer of the third device include the same first data and first-layer header.

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

[0240] In one possible implementation, the entity of the first layer of the third device processes the first data from the first entity of the second layer of the third device and the first data from the second entity of the second layer of the third device, including: reordering processing and / or duplicate packet processing.

[0241] It should be noted that the entity of the first layer of the third device can be associated with multiple entities of the second layer. The above description only takes the association of the entity of the first layer of the third device with the first entity of the second layer and the second entity of the second layer as an example. The embodiments of the present application can be applied to scenarios where the entity of the first layer of the third device is associated with more entities of the second layer, such as scenarios where the entity of the first layer of the third device is associated with 3 entities of the second layer, scenarios where the entity of the first layer of the third device is associated with 4 entities of the second layer, etc. The entity of the first layer of the third 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 third device can send and receive data through the first entity of the second layer and the second entity of 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 use the air interface spare resources corresponding to multiple links or multiple carriers to transmit the same data. Taking the multiple links as the new wireless transmission link and the long-term evolution transmission link as an example, the new wireless and long-term evolution air interface spare resources can be used to transmit the same data at the same time. Therefore, method 1200 can make full use of the air interface spare resources by redundantly transmitting data to reduce packet loss, reduce transmission delay, ensure the reliability of downlink data transmission of the service, and help improve the user experience of the service. A more detailed description of the beneficial effects of method 1200 can be referred to method 500 and will not be repeated here.

[0243] In other implementations, before the first entity of the second layer of the third device sends the first data to the entity of the first layer of the third device, the first entity of the second layer of the third device performs reordering and / or packet duplication on the first data, and / or before the second entity of the second layer of the third device sends the first data to the entity of the first layer of the third device, the second entity of the second layer of the third device performs reordering and / or packet duplication on the first data. Based on this implementation, the time required for the entity of the first layer of the third device to process the first data can be reduced. Furthermore, because the first entity of the second layer of the third device and the second entity of the second layer of the third device can simultaneously perform reordering and / or packet duplication on the first data, the overall data processing time can be reduced.

[0244] Below, in combination with specific scenarios, 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 embodiment of the present application is described in detail.

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

[0246] If the access network device side performs PDCP replication on 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. 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 RLC entity of the terminal device performs reordering and / or duplicate packet processing

[0248] If the access network device side performs RLC replication in 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 RLC entity of the terminal device can process each RLC PDU as shown in Figures 12 to 15 below.

[0249] 12 and 13 , the process of receiving services by the RLC entity on the terminal device side under UM will be described below.

[0250] FIG12 is a schematic diagram of the overall flow of RLC processing on the terminal device side under UM.

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

[0252] 1) Detect whether duplicate UMD PDUs are received and discard the duplicate UMD PDUs. If out-of-order delivery is not configured and the UMD PDUs are out of order, reorder the UMD PDUs.

[0253] 2) Remove the RLC header;

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

[0255] It can be seen that in the embodiment of the present application, duplicate packet discarding and reordering of UMD PDUs can be performed in an RLC entity (such as the receiving UM RLC entity in FIG12 ).

[0256] For descriptions of other operations in FIG12 , reference may be made to section 5.2.2 of the relevant standard TS38.322 and will not be described in detail.

[0257] FIG13 is a schematic diagram of a specific flow of RLC processing on the terminal device side under UM.

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

[0259] Step 1401: The RLC entity receives a UMD PDU from a lower layer.

[0260] The lower layer may refer to the MAC layer. The UDM PDU may be one of a plurality of identical UDM PDUs that may be received by the RLC entity. Step 1401 may be referenced to or referred to in step 1201 or step 1202.

[0261] Step 1402: The RLC entity maintains a reordering window and a reassembly window according to state variables.

[0262] Step 1403: The RLC entity determines whether the header of the UMD PDU contains a SN.

[0263] When the header of the UMD PDU does not include an SN, the process may proceed to step 1404 ; when the header of the UMD PDU includes an SN, the process may proceed to step 1405 .

[0264] In step 1404, the RLC entity removes the RLC header from 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 receiving window.

[0266] When the SN of the UDM PDU is within the receiving window, the process may proceed to step 1406 ; when the SN of the UDM PDU is not within the receiving window, the process may proceed to step 1408 .

[0267] Step 1406: The RLC entity places the UDM PDU into a receiving 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, step 1408 may be executed; when the UDM PDU is not a duplicate UDM PDU, step 1409, step 1412 and step 1418 may 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 are received.

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

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

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

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

[0276] RX_Next_Reassembly indicates the SN of the next reassembled SDU expected to be received.

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

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

[0279] In 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, execute step 1415 branch; otherwise, execute step 1416 branch.

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

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

[0283] In step 1417, the RLC entity reorders the RLC SDU, deletes the RLC header, and submits it to the upper layer.

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

[0285] When SN=x is outside the reassembly window, the process branches to step 1419.

[0286] Step 1419: The RLC entity updates the receiving window.

[0287] Step 1420: The RLC entity discards the UMD PDU outside the SN no longer reassembly window.

[0288] The description in steps 1402 to 1420 and step 1203 may be referenced or referred to each other.

[0289] In Figures 12 and 13, the terminal device can discard duplicate packets and reorder data packets at the RLC layer (as shown in steps 1402, 1407, and 1414-1417). The beneficial effects of the solutions shown in Figures 12 and 13 can refer to the beneficial effects of method 1200 and will not be repeated here.

[0290] 14 and 15 , the process of receiving services by the RLC entity on the terminal device side under AM will be described below.

[0291] FIG14 is a schematic diagram of the overall flow of RLC processing on the terminal device side under AM.

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

[0293] 1) Detect whether duplicate AMD PDUs are received and discard the duplicate AMD PDUs. If out-of-order delivery is not configured and the AMD PDUs are out of order, reorder the AMD PDUs.

[0294] 2) Detect the loss of RLC data PDUs and request the sending AM RLC entity to retransmit the lost RLC data PDUs;

[0295] 3) Remove the RLC header;

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

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

[0298] For descriptions of other operations in FIG14 , please refer to section 5.2.3 of the relevant standard TS38.322 and will not be described in detail.

[0299] FIG15 is a schematic diagram of a specific flow of RLC processing on the terminal device side under AM.

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

[0301] Step 1601: The RLC entity receives an AMD PDU from a lower layer.

[0302] The lower layer may refer to the MAC layer. The ADM PDU may be one of a plurality of identical AMD PDUs that may be received by the RLC entity. Step 1601 may be referenced to or referred to 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 step 1603 branch can be executed; when the SN of the ADM PDU is not within the receiving window, the step 1605 branch can be executed.

[0305] Step 1603: When the SN of the ADM PDU is within the receiving window, the RLC entity determines whether a duplicate ADM PDU is received.

[0306] When the ADM PDU is a repeated ADM PDU, the step 1605 branch may be executed; when the ADM PDU is not a repeated ADM PDU, the step 1604 branch may be executed.

[0307] Step 1604: If the ADM PDU is not a duplicate, the RLC entity places the ADM PDU into a receiving buffer.

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

[0309] Step 1606: The RLC entity determines whether some segments of the RLC SDU included in the AMD PDU have not been received.

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

[0311] Step 1607: When receiving some segments of the RLC SDU included in the AMD PDU, the RLC entity discards duplicate segments.

[0312] Step 1608: When some segments of the RLC SDU included 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] RX_NEXT_highest indicates the upper limit of the SN of the reassembly window.

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

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

[0316] Step 1610: The RLC entity determines whether all segments of the RLC SDU with SN=x are received.

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

[0318] Step 1611: Upon receiving all segments of the RLC SDU with SN=x, 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 an upper layer.

[0319] Step 1612: When all segments of the RLC SDU with SN=x are not received, the RLC entity determines whether the reassembly timer has expired.

[0320] When the reassembly timer times out, step 1613 may be executed.

[0321] Step 1613: When the reassembly timer times out, the RLC entity updates the receiving window.

[0322] Step 1614: The RLC entity reassembles the message.

[0323] Step 1615: The RLC entity resets the reassembly timer.

[0324] In 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 step 1617 branch; otherwise, execute step 1618 branch.

[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 SDUs.

[0329] In step 1620, the RLC entity deletes the RLC header and submits it to the upper layer.

[0330] The description in steps 1602 to 1620 and step 1203 may be referenced or referred to each other.

[0331] In Figures 14 and 15, the terminal device can discard duplicate packets and reorder data packets at the RLC layer (as shown in steps 1603, 1616-1620). The beneficial effects of the solutions shown in Figures 14 and 15 can refer to the beneficial effects of method 1200 and will not be repeated here.

[0332] The above describes in detail the method embodiment provided by the present application in conjunction with Figures 4 to 15 , and the following will describe the device embodiment of the present application in conjunction with Figures 16 to 18 .

[0333] It is understood that, in order to implement the functions in the above embodiments, the apparatuses in Figures 16 to 18 include hardware structures and / or software modules corresponding to the functions. Those skilled in the art should readily appreciate that, in conjunction with the various exemplary units and method steps described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software.

[0334] Figures 16 and 17 are schematic diagrams of possible devices provided in embodiments of the present application. These devices can be used to implement the functions of the first device, the second device, or the third device in the above method embodiments, thereby also achieving the beneficial effects of the above method embodiments.

[0335] As shown in FIG. 16 , 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 each of the above method embodiments, the transceiver unit 11 is used to execute the transceiver steps of the first device, and the processing unit 12 is used to execute the processing steps of the first device. When the device 10 is used to implement the functions of the second device in each of the above method embodiments, the transceiver unit 11 is used to execute the transceiver steps of the second device, and the processing unit 12 is used to execute the processing steps of the second device. When the device 10 is used to implement the functions of the third device in each of the above method embodiments, the transceiver unit 11 is used to execute the transceiver steps of the third device, and the processing unit 12 is used to execute the processing steps of the third device.

[0337] For a more detailed description of the transceiver unit 11 and the processing unit 12 , please refer to the relevant description in the above method embodiment, which will not be described again here.

[0338] As shown in FIG17 , the apparatus 20 includes a processor 21. The processor 21 is coupled to a memory 23, which is used to store instructions. When the apparatus 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 processing unit 12 described above.

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

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

[0341] Exemplarily, when 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-mentioned method embodiment. The chip receives information from other modules (such as a radio frequency module or antenna) in the first device, the second device, or the third device, where the information is sent to the first device, the second device, or the third device by the other device; or the chip sends information to other modules (such as a radio frequency module or antenna) in the first device, the second device, or the third device, where the information is sent to the other device by the first device, the second device, or the third device.

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

[0343] The logic circuit 31 may be a processing circuit in the chip system 30. The logic circuit 31 may 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 various embodiments of the present application. The input / output interface 32 may be an input / output circuit in the chip system 30, outputting information processed by the chip system 30 or inputting 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 each of 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 embodiment; 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 embodiment.

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

[0347] The present application also provides a chip, including a processor, which 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-mentioned method embodiments.

[0348] The present application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the first device, the second device, or the third device in the above-mentioned method embodiments.

[0349] The present application also provides a computer program product comprising 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-mentioned method embodiments.

[0350] The present application also 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] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[0352] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0353] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can 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 mobile 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 can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in the first device, the second device or the third device. Of course, the processor and the storage medium can also be present in the first device, the second device or the third device as discrete components.

[0354] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented 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 performed 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 device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. 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 data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive.

[0355] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0356] Unless otherwise indicated, all technical and scientific terms used in the embodiments of the present application have the same meaning as those generally understood by those skilled in the art of the technical field of the application. The terms used in this application are only for the purpose of describing specific embodiments and are not intended to limit the scope of the application. It should be understood that the above are for illustration, and the examples above are only for helping those skilled in the art to understand the embodiments of the present application, rather than limiting the application embodiments to the specific numerical values ​​or specific scenarios illustrated. Those skilled in the art can obviously carry out 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. The method according to any one of claims 1 to 11, characterized in that, The method further includes: The entity in the first layer of the first device determines that the frequency domain replication function is enabled.

13. 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.

14. The method according to claim 13, characterized in that, The processing includes reordering processing and / or duplicate packet processing.

15. The method according to claim 13 or 14, 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.

16. The method according to any one of claims 13 to 15, wherein the first entity of the second layer of the third device receiving the first data includes: the first entity of the second layer receiving the first data from the first device; the second entity of the second layer of the third device receiving the first data includes: the first entity of the second layer receiving the first data from the first device; or the first entity of the second layer of the third device receiving the first data includes: the first entity of the second layer receiving the first data from the first device; the second entity of the second layer of the third device receiving the first data includes: the second entity of the second layer receiving the first data from the second device.

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

18. The method according to claim 17, wherein the first device and the second device are two 5G RAT access network devices connected to the same third device in a dual connectivity scenario.

19. The method according to claim 16, wherein the first device and the second device have different radio access technologies (RATs).

20. The method according to claim 19, wherein the first device and the second device are two access network devices connected to the same terminal device in a dual connectivity scenario; wherein, the first device is a 5G RAT access network device, and the second device is a 4G RAT access network device; or the first device is a 4G RAT access network device, and the second device is a 5G RAT access network device.

21. The method according to any one of claims 13 to 20, wherein the first data is user data.

22. The method according to any one of claims 13 to 21, wherein 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 performing 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 performing reordering processing and / or duplicate packet processing on the first data.

23. A communication device, characterized in that, including a module or unit for executing the method according to any one of claims 1 to 22.

24. 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 22.

25. The communication device according to claim 24, wherein The communication device is a chip or a chip system.

26. 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 22 is implemented.

27. A computer program product containing instructions, characterized in that, When the instruction runs on a computer, the computer is caused to implement the method according to any one of claims 1 to 22.

28. 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 12, and the second device is used to receive and send data from the entity on the first layer of the first device.

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

Images