A communication method and related products

Abstract

The embodiment of the application discloses a communication method and related products, which can be applied to the communication field in the electronic technology field. The communication method is applied to a network device, and includes transmitting first type data through a primary carrier cell (PCC) and transmitting second type data through a secondary carrier cell (SCC). The first type data includes control plane data, and the second type data includes user plane data. Alternatively, the first type data includes uplink data, and the second type data includes downlink data. Alternatively, the first type data includes downlink data, and the second type data includes uplink data. The application can reduce the waste of communication resources and improve the utilization rate of communication resources.

Description

Technical Field

[0001] This invention relates to the field of electronic technology, and more specifically to a communication method and related products. Background Technology

[0002] With the development of technology and the progress of society, in order to provide higher service speeds, the 3rd Generation Partnership Project (3GPP) has been developing its own technology. rd The Generation Partnership Project introduces Carrier Aggregation (CA) to aggregate multiple continuous or non-contiguous component carriers (CC) into a larger bandwidth, as well as Dual Connectivity to fully utilize the resources and advantages of different carriers and standards, thereby improving the user's uplink and downlink peak rate experience.

[0003] In the existing network architecture, under CA (Carrier Access) scenarios, both the control plane and user plane are carried on the primary carrier cell (PCC). Then, the user plane data is offloaded to the secondary carrier cell (SCC) via the PCC's RLC layer. Similarly, in CA scenarios, uplink and downlink are carried on the same carrier cell (PCC or SCC). Furthermore, in dual connectivity (DC) scenarios, uplink and downlink are carried on the same carrier group (primary carrier group MCG or secondary carrier group SCG).

[0004] In such multi-carrier scenarios (CA or DC), the strong coupling between the control plane and user plane, and uplink and downlink (carried on the same carrier) can lead to situations where there are large differences in carrier capabilities, such as the SCC's carrier capability being much greater than the PCC's carrier capability. In this case, the SCC can carry most of the traffic, so the user plane traffic carried on the PCC needs to be diverted to the SCC through the PCC's RLC layer. The diversion process not only adds an extra path, causing path delay, but the path also limits the diverted traffic, thus making it impossible to maximize resource utilization according to service requirements. Summary of the Invention

[0005] This application provides a communication method and related products to reduce the waste of communication resources and improve the utilization rate of communication resources.

[0006] In a first aspect, embodiments of the present invention provide a communication method, characterized in that it is applied to a network device, the method comprising: transmitting a first type of data through a primary carrier cell (PCC) and transmitting a second type of data through a secondary carrier cell (SCC); wherein the first type of data includes control plane data and the second type of data includes user plane data, or the first type of data includes uplink data and the second type of data includes downlink data, or the first type of data includes downlink data and the second type of data includes uplink data.

[0007] This invention, applied to carrier aggregation (CA) scenarios, employs a user plane and control plane, uplink and downlink separation architecture. It transforms the original architecture where the control plane and user plane, uplink and downlink, could only be carried on the same carrier into one where the control plane is on the PCC and the user plane on the SCC, or uplink on the PCC and downlink on the SCC, or downlink on the PCC and uplink on the SCC. Unlike existing architectures where the control plane and user plane, or uplink and downlink, can only be carried on the same carrier, this invention not only allows the user plane and control plane to be carried on different carriers (e.g., control plane on PCC, user plane on SCC), but also addresses the issue of data exceeding PCC capacity requiring transmission via the PCC's RLC layer, through the transmission channel, and then via the SCC's MAC layer to the terminal when the SCC's carrier capacity exceeds that of the PCC, introducing additional path delay. Furthermore, if the transmission channel is limited, the SCC's capacity cannot be fully utilized, wasting resources. Moreover, it allows for separate uplink and downlink deployment, enabling each to select the optimal carrier for deployment. For example, high-volume downlink traffic requires deployment on a high-bandwidth SCC (Short-Range Carrier). However, the SCC has weak uplink capabilities, while the PCC (Programmable Controller) has strong uplink capabilities but weak downlink capabilities. In this case, if a tightly coupled uplink / downlink deployment is still used, the performance of one side will inevitably suffer. Therefore, using the separation architecture provided in this invention, uplink and downlink can be deployed on carriers with superior performance, respectively. In summary, the communication method provided in this invention allows the user plane and control plane, or uplink and downlink, to be deployed on different carriers, thereby fully utilizing the resources and advantages of different carriers, maximizing resource utilization, and improving service rates.

[0008] In one possible implementation, the first type of data includes control plane data, and the second type of data includes user plane data; the transmission of the first type of data through the primary carrier cell (PCC) includes: generating a first message through the Packet Data Convergence Protocol (PDCP) layer of the PCC and sending it to the Radio Link Control (RLC) layer of the PCC; receiving the first message through the RLC layer of the PCC, generating a second message using the first message, and sending it to the Media Access Control (MAC) layer of the PCC.

[0009] This invention improves resource utilization by using a separate architecture where control plane data is deployed on the PCC and user plane data is deployed on the SCC. A first message is generated through the PDCP layer of the PCC and sent to the RLC layer of the PCC. The RLC layer of the PCC receives the first message, generates a second message using the first message, and sends it to the MAC layer of the PCC. A third message is generated through the PDCP layer of the SCC and sent to the RLC layer of the SCC. The RLC layer of the SCC receives the third message, generates a fourth message using the third message, and sends it to the MAC layer of the SCC. Alternatively, the RLC layer of the SCC receives the third message, generates a fourth message using the third message, sends a portion of the fourth message to the MAC layer of the SCC, and sends another portion of the fourth message to the MAC layer of the PCC. This separate architecture allows user plane data to go directly from the core network to the SCC and be sent directly from the SCC air interface, avoiding path detours and reducing data transmission latency. At the same time, even if data exceeding the SCC's capacity needs to be sent to the PCC, the PCC's capacity is smaller and the required transmission bandwidth is also smaller, thus reducing transmission-restricted scenarios.

[0010] In one possible implementation, the transmission of the second type of data via the secondary carrier cell (SCC) includes: generating a third message through the PDCP layer of the SCC and sending it to the RLC layer of the SCC; receiving the third message through the RLC layer of the SCC, generating a fourth message using the third message, and sending it to the MAC layer of the SCC. Alternatively, receiving the third message through the RLC layer of the SCC, generating a fourth message using the third message, sending a portion of the fourth message to the MAC layer of the SCC, and sending another portion of the fourth message to the MAC layer of the PCC. In this embodiment of the invention, when user plane data exceeds the carrier capacity of the SCC, it is necessary to offload the excess data from the SCC to the PCC. First, the generated third message is sent to the RLC layer of the SCC through the PDCP layer; then, the fourth message is received through the RLC layer of the SCC, and a fourth message is generated using the third message. The portion of the fourth message that the SCC can carry is sent to the MAC layer of the SCC, and the excess portion of the fourth message is sent to the MAC layer of the PCC. Because the PCC has a smaller carrier capability and requires less transmission bandwidth, even if the split channel can transmit less data, it will not limit the transmission of the split channel, since the PCC itself requires less data.

[0011] In one possible implementation, the first type of data includes uplink data, and the second type of data includes downlink data. The transmission of the first type of data through the primary carrier cell (PCC) includes: generating a first message through the MAC layer of the PCC, or generating a portion of the first message through the MAC layer of the PCC, then generating another portion of the first message through the MAC layer of the SCC, and sending it to the RLC layer of the PCC; receiving the first message through the RLC layer of the PCC, generating a second message using the first message, and sending it to the PDCP layer of the PCC. This embodiment of the invention improves the peak uplink and downlink rates by using a separate architecture where uplink data is deployed on the PCC and downlink data is deployed on the SCC. The first message is generated through the MAC layer of the PCC, or a portion of the first message is generated through the MAC layer of the PCC, then generating another portion of the first message through the MAC layer of the SCC, and sending it to the RLC layer of the PCC; the first message is received through the RLC layer of the PCC, generating a second message using the first message, and sending it to the PDCP layer of the PCC. This separate architecture allows downlink data to go directly from the core network to the SCC and be sent directly from the SCC air interface, avoiding path detours and reducing data transmission latency. At the same time, even if data exceeding the SCC's capacity needs to be sent to the PCC, the PCC has a smaller capacity and requires less transmission bandwidth, thus reducing transmission-restricted scenarios.

[0012] In one possible implementation, the transmission of the second type of data via the secondary carrier cell (SCC) includes: generating a third message through the PDCP layer of the SCC and sending it to the RLC layer of the SCC; receiving the third message through the RLC layer of the SCC, generating a fourth message using the third message, and sending it to the MAC layer of the SCC; or receiving the third message through the RLC layer of the SCC, generating a fourth message using the third message, sending a portion of the fourth message to the MAC layer of the SCC, and sending another portion of the fourth message to the MAC layer of the PCC. In this embodiment of the invention, when downlink data exceeds the carrier capacity of the SCC, the excess data on the SCC needs to be diverted to the PCC. First, the generated third message is sent to the RLC layer of the SCC through the PDCP layer; then, the fourth message is received through the RLC layer of the SCC, and a fourth message is generated using the third message. The portion of the fourth message that the SCC can carry is sent to the MAC layer of the SCC, and the excess portion of the fourth message is sent to the MAC layer of the PCC. Because the PCC has a smaller carrier capability and requires less transmission bandwidth, even if the split channel can transmit less data, it will not limit the transmission of the split channel, since the PCC itself requires less data.

[0013] In one possible implementation, the first type of data includes downlink data, and the second type of data includes uplink data. The transmission of the first type of data through the primary carrier cell (PCC) includes: generating a first message through the PDCP layer of the PCC and sending it to the RLC layer of the PCC; receiving the first message through the RLC layer of the PCC, generating a second message using the first message, and sending it to the MAC layer of the PCC. Alternatively, receiving the first message through the RLC layer of the PCC, generating a second message using the first message, sending a portion of the second message to the MAC layer of the PCC, and sending another portion of the second message to the MAC layer of the SCC.

[0014] This invention improves peak uplink and downlink rates through a separate architecture where downlink data is deployed on the PCC and uplink data on the SCC. A first message is generated at the PCC's PDCP layer and sent to the PCC's RLC layer. The PCC's RLC layer receives the first message, generates a second message using the first message, and sends it to the PCC's MAC layer. Alternatively, the PCC's RLC layer receives the first message, generates a second message using the first message, sends a portion of the second message to the PCC's MAC layer, and sends the other portion of the second message to the SCC's MAC layer. This separate architecture allows uplink data to directly reach the SCC from the terminal device, avoiding path detours and reducing data transmission latency. Furthermore, even if data exceeding the SCC's capacity needs to be sent to the PCC, the PCC's smaller capacity requires less bandwidth, thus reducing transmission-constrained scenarios.

[0015] In one possible implementation, the transmission of the second type of data via the secondary carrier cell (SCC) includes: generating a third message through the MAC layer of the SCC, or generating a portion of the third message through the MAC layer of the SCC, and then generating another portion of the third message through the MAC layer of the PCC, and sending it to the RLC layer of the SCC; receiving the third message through the RLC layer of the SCC, using the third message to generate a fourth message, and sending it to the PDCP layer of the SCC. In this embodiment of the invention, when uplink data exceeds the carrier capacity of the SCC, it is necessary to offload the excess data from the SCC to the PCC. This involves generating a third message through the MAC layer of the SCC, or generating a portion of the third message through the MAC layer of the SCC, and then generating another portion of the third message through the MAC layer of the PCC, and sending it to the RLC layer of the SCC; receiving the third message through the RLC layer of the SCC, using the third message to generate a fourth message, and sending it to the PDCP layer of the SCC. Because the PCC has a smaller carrier capability and requires less transmission bandwidth, even if the split channel can transmit less data, it will not limit the transmission of the split channel, since the PCC itself requires less data.

[0016] Secondly, embodiments of the present invention provide a communication method, characterized in that it is applied to a network device, the method comprising: transmitting a third type of data through a primary carrier group (MCG) and transmitting a fourth type of data through a secondary carrier group (SCG); wherein the third type of data includes uplink data and the fourth type of data includes downlink data, or the third type of data includes downlink data and the fourth type of data includes uplink data.

[0017] This invention, applied to dual-connectivity DC scenarios, employs a separate uplink and downlink architecture. Instead of the original configuration where uplink and downlink could only be carried on the same carrier, it transforms the configuration into one where uplink is on the MCG and downlink on the SCG, or vice versa. Unlike existing architectures where uplink and downlink can only be carried on the same carrier, this invention allows for separate deployment of uplink and downlink, enabling each to select the carrier with optimal performance. For example, high-volume downlink traffic might require deployment on a high-bandwidth SCG, but the SCG has weak uplink capabilities while the MCG has strong uplink capabilities but weak downlink capabilities. In such a case, strong coupling of uplink and downlink deployment would inevitably result in performance degradation on one side. Therefore, the separation architecture provided by this invention allows uplink and downlink to select the carrier with optimal performance for each. In summary, to improve service rates, the communication method provided by this invention allows uplink and downlink to be deployed on different carriers, thereby fully utilizing the resources and advantages of different carriers and maximizing resource utilization.

[0018] In one possible implementation, the third type of data includes uplink data, and the fourth type of data includes downlink data; the transmission of the third type of data through the primary carrier group (MCG) includes: generating a fifth message at the MAC layer of the MCG and sending it to the RLC layer of the MCG; the RLC layer of the MCG receiving the fifth message, generating a sixth message using the fifth message, and sending it to the PDCP layer of the MCG; or generating a portion of the fifth message at the MAC layer of the MCG and another portion of the fifth message at the MAC layer of the SCG, sending the portion of the fifth message to the RLC layer of the MCG, and sending the other portion of the fifth message to the RLC layer of the SCG; the RLC layer of the MCG receiving the portion of the fifth message, generating a sixth message using the portion of the fifth message, and sending it to the PDCP layer of the MCG; the RLC layer of the SCG receiving the other portion of the fifth message, generating a sixth message using the other portion of the fifth message, and sending it to the PDCP layer of the MCG.

[0019] This invention deploys uplink data on the MCG (Multi-Channel Group). A fifth message is generated at the MCG's MAC layer and sent to the MCG's RLC (Remote Control Center) layer. The MCG's RLC layer receives the fifth message, uses it to generate a sixth message, and sends it to the MCG's PDCP (Plan-Do-Check-Act) layer. Alternatively, a portion of the fifth message is generated at the MCG's MAC layer, and another portion is generated at the SCG's MAC layer. The portion of the fifth message is sent to the MCG's RLC layer, and the other portion is sent to the SCG's RLC layer. The MCG's RLC layer receives the portion of the fifth message, uses it to generate a sixth message, and sends it to the MCG's PDCP layer. The SCG's RLC layer receives the other portion of the fifth message, uses it to generate a sixth message, and sends it to the MCG's PDCP layer. This separated architecture allows uplink data to directly reach the MCG from the terminal device, avoiding path detours and reducing data transmission latency.

[0020] In one possible implementation, the transmission of the fourth type of data via a secondary carrier group (SCG) includes: generating a seventh message at the PDCP layer of the SCG and sending it to the RLC layer of the SCG; the RLC layer of the SCG receiving the seventh message, generating an eighth message using the seventh message, and sending it to the MAC layer of the SCG. Alternatively, a seventh message can be generated at the PDCP layer of the SCG, a portion of the seventh message sent to the RLC layer of the SCG, and another portion sent to the RLC layer of the MCG; the RLC layer of the SCG receiving a portion of the seventh message, generating an eighth message using the portion of the seventh message, and sending it to the MAC layer of the SCG; the RLC layer of the MCG receiving the other portion of the seventh message, generating a ninth message using the other portion of the seventh message, and sending it to the MAC layer of the MCG. In this embodiment of the invention, when downlink data exceeds the carrier capacity of the SCG, it is necessary to offload the excess data from the SCG to the MCG. First, a seventh message is generated at the PDCP layer of the SCG. A portion of this seventh message is sent to the RLC layer of the SCG, and another portion is sent to the RLC layer of the MCG. The RLC layer of the SCG receives a portion of the seventh message, uses it to generate an eighth message, and sends it to the MAC layer of the SCG. The RLC layer of the MCG receives the other portion of the seventh message, uses it to generate a ninth message, and sends it to the MAC layer of the MCG. Because the MCG has a relatively small carrier capability and requires less transmission bandwidth, even if the offloaded channel can transmit a smaller amount of data, it will not limit the offloaded transmission, as the MCG itself requires relatively little data.

[0021] In one possible implementation, the third type of data includes downlink data, and the fourth type of data includes uplink data. The transmission of the third type of data via the primary carrier group (MCG) includes: generating a fifth message at the PDCP layer of the MCG and sending it to the RLC layer of the MCG; the RLC layer of the MCG receiving the fifth message, generating a sixth message using the fifth message, and sending it to the MAC layer of the MCG; or generating a fifth message at the PDCP layer of the MCG, sending a portion of the fifth message to the RLC layer of the MCG, and sending another portion of the fifth message to the RLC layer of the SCG; the RLC layer of the MCG receiving a portion of the fifth message, generating a sixth message using the portion of the fifth message, and sending it to the MAC layer of the MCG; the RLC layer of the SCG receiving the other portion of the fifth message, generating a sixth message using the other portion of the fifth message, and sending it to the MAC layer of the SCG.

[0022] This invention employs an uplink and downlink separation architecture, transforming the original approach where uplink and downlink could only be carried on the same carrier into one where uplink is on the MCG and downlink on the SCG, or vice versa. Unlike existing architectures where uplink and downlink can only be carried on the same carrier, this invention allows for separate deployment of uplink and downlink, enabling each to select the carrier with optimal performance. For example, high-volume downlink traffic might require deployment on a high-bandwidth SCG, but the SCG has weak uplink capabilities while the MCG has strong uplink capabilities but weak downlink capabilities. In such a case, strong coupling of uplink and downlink deployment would inevitably result in performance degradation on one side. Therefore, the separation architecture provided by this invention allows uplink and downlink to select the carrier with optimal performance for each. In summary, to improve service rates, the communication method provided by this invention allows uplink and downlink to be deployed on different carriers, thereby fully utilizing the resources and advantages of different carriers and maximizing resource utilization.

[0023] In one possible implementation, the third type of data includes uplink data, and the fourth type of data includes downlink data; the transmission of the third type of data through the primary carrier group (MCG) includes: generating a fifth message at the MAC layer of the MCG and sending it to the RLC layer of the MCG; the RLC layer of the MCG receiving the fifth message, generating a sixth message using the fifth message, and sending it to the PDCP layer of the MCG; or generating a portion of the fifth message at the MAC layer of the MCG and another portion of the fifth message at the MAC layer of the SCG, sending the portion of the fifth message to the RLC layer of the MCG, and sending the other portion of the fifth message to the RLC layer of the SCG; the RLC layer of the MCG receiving the portion of the fifth message, generating a sixth message using the portion of the fifth message, and sending it to the PDCP layer of the MCG; the RLC layer of the SCG receiving the other portion of the fifth message, generating a sixth message using the other portion of the fifth message, and sending it to the PDCP layer of the MCG.

[0024] This invention deploys uplink data on the MCG (Multi-Channel Group). A fifth message is generated at the MCG's MAC layer and sent to the MCG's RLC (Remote Control Center) layer. The MCG's RLC layer receives the fifth message, uses it to generate a sixth message, and sends it to the MCG's PDCP (Plan-Do-Check-Act) layer. Alternatively, a portion of the fifth message is generated at the MCG's MAC layer, and another portion is generated at the SCG's MAC layer. The portion of the fifth message is sent to the MCG's RLC layer, and the other portion is sent to the SCG's RLC layer. The MCG's RLC layer receives the portion of the fifth message, uses it to generate a sixth message, and sends it to the MCG's PDCP layer. The SCG's RLC layer receives the other portion of the fifth message, uses it to generate a sixth message, and sends it to the MCG's PDCP layer. This separated architecture allows uplink data to directly reach the MCG from the terminal device, avoiding path detours and reducing data transmission latency.

[0025] In one possible implementation, the transmission of fourth-type data via a secondary carrier group (SCG) includes: generating a seventh message at the SCG's MAC layer and sending it to the SCG's RLC layer; the SCG's RLC layer receiving the seventh message, generating an eighth message using the seventh message, and sending it to the SCG's PDCP layer. Alternatively, a portion of the seventh message can be generated at the SCG's MAC layer, and another portion can be generated at the MCG's MAC layer. The portion of the seventh message is sent to the SCG's RLC layer, and the other portion is sent to the MCG's RLC layer. The SCG's RLC layer receives the portion of the seventh message, generates an eighth message using the portion of the seventh message, and sends it to the SCG's PDCP layer. The MCG's RLC layer receives the other portion of the seventh message, generates an eighth message using the other portion of the seventh message, and sends it to the SCG's PDCP layer. In this embodiment of the invention, when uplink data exceeds the SCG's carrier capacity, the excess data on the SCG needs to be diverted to the MCG. First, a portion of the seventh message is generated by the SCG's MAC layer, and another portion is generated by the MCG's MAC layer. The first portion of the seventh message is sent to the SCG's RLC layer, and the second portion is sent to the MCG's RLC layer. The SCG's RLC layer receives the first portion of the seventh message, uses it to generate an eighth message, and sends it to the SCG's PDCP layer. Similarly, the MCG's RLC layer receives the second portion of the seventh message, uses it to generate an eighth message, and sends it to the SCG's PDCP layer. Because the MCG has a smaller carrier capability and requires less transmission bandwidth, even if the split channel can transmit less data, it will not limit the split transmission, as the MCG itself requires relatively little data.

[0026] Thirdly, embodiments of the present invention provide a communication device, characterized in that it includes: a first transmission unit, configured to transmit a first type of data via a primary carrier cell (PCC) and transmit a second type of data via a secondary carrier cell (SCC); wherein the first type of data includes control plane data and the second type of data includes user plane data, or the first type of data includes uplink data and the second type of data includes downlink data, or the first type of data includes downlink data and the second type of data includes uplink data.

[0027] In one possible implementation, the first transmission unit is specifically used for:

[0028] The first message is generated by the Packet Data Convergence Protocol (PDCP) layer of the PCC and sent to the Radio Link Control (RLC) layer of the PCC.

[0029] The PCC receives the first message through its RLC layer, generates a second message using the first message, and sends it to the PCC's Media Access Control (MAC) layer.

[0030] In one possible implementation, the first transmission unit is specifically used for:

[0031] A third message is generated through the PDCP layer of the SCC and sent to the RLC layer of the SCC.

[0032] The third message is received through the RLC layer of the SCC, a fourth message is generated using the third message, and then sent to the MAC layer of the SCC. Alternatively, the third message is received through the RLC layer of the SCC, a fourth message is generated using the third message, a portion of the fourth message is sent to the MAC layer of the SCC, and another portion of the fourth message is sent to the MAC layer of the PCC.

[0033] In one possible implementation, the first transmission unit is specifically used for:

[0034] The first message is generated through the MAC layer of the PCC, or a part of the first message is generated through the MAC layer of the PCC, and another part of the first message is generated through the MAC layer of the SCC, and then sent to the RLC layer of the PCC.

[0035] The first message is received by the RLC layer of the PCC, a second message is generated using the first message, and then sent to the PDCP layer of the PCC.

[0036] In one possible implementation, the first transmission unit is specifically used for:

[0037] A third message is generated through the PDCP layer of the SCC and sent to the RLC layer of the SCC.

[0038] The third message is received through the RLC layer of the SCC, a fourth message is generated using the third message, and then sent to the MAC layer of the SCC; or the third message is received through the RLC layer of the SCC, a fourth message is generated using the third message, a part of the fourth message is sent to the MAC layer of the SCC, and another part of the fourth message is sent to the MAC layer of the PCC.

[0039] In one possible implementation, the first transmission unit is specifically used for:

[0040] The first message is generated through the PDCP layer of the PCC and sent to the RLC layer of the PCC;

[0041] The first message is received by the RLC layer of the PCC, a second message is generated using the first message, and then sent to the MAC layer of the PCC.

[0042] Alternatively, the first message can be received through the RLC layer of the PCC, and a second message can be generated using the first message. A portion of the second message can be sent to the MAC layer of the PCC, and the other portion of the second message can be sent to the MAC layer of the SCC.

[0043] In one possible implementation, the first transmission unit is specifically used for:

[0044] The third message is generated through the MAC layer of the SCC, or a portion of the third message is generated through the MAC layer of the SCC, and another portion of the third message is generated through the MAC layer of the PCC, and then sent to the RLC layer of the SCC.

[0045] The third message is received by the RLC layer of the SCC, a fourth message is generated using the third message, and then sent to the PDCP layer of the SCC.

[0046] Fourthly, embodiments of the present invention provide a communication device, characterized in that it includes:

[0047] The second transmission unit is used to transmit the third type of data through the main carrier group (MCG) and the fourth type of data through the auxiliary carrier group (SCG).

[0048] Wherein, the third type of data includes uplink data and the fourth type of data includes downlink data, or the third type of data includes downlink data and the fourth type of data includes uplink data;

[0049] In one possible implementation, the second transmission unit is specifically used for:

[0050] The fifth message is generated at the MAC layer of the MCG and sent to the RLC layer of the MCG.

[0051] The RLC layer of the MCG receives the fifth message, uses the fifth message to generate a sixth message, and sends it to the PDCP layer of the MCG.

[0052] Alternatively, a portion of the fifth message can be generated through the MAC layer of the MCG and another portion of the fifth message can be generated through the MAC layer of the SCG. The portion of the fifth message can be sent to the RLC layer of the MCG and the other portion of the fifth message can be sent to the RLC layer of the SCG.

[0053] The RLC layer of the MCG receives the portion of the fifth message, uses the portion of the fifth message to generate the sixth message, and sends it to the PDCP layer of the MCG.

[0054] The RLC layer of the SCG receives another part of the fifth message, uses the other part of the fifth message to generate a sixth message, and sends it to the PDCP layer of the MCG.

[0055] In one possible implementation, the second transmission unit is specifically used for:

[0056] The seventh message is generated at the PDCP layer of the SCG and sent to the RLC layer of the SCG.

[0057] The RLC layer of the SCG receives the seventh message, uses the seventh message to generate the eighth message, and sends it to the MAC layer of the SCG.

[0058] In one possible implementation, the second transmission unit is specifically used for:

[0059] A seventh message is generated at the PDCP layer of the SCG, a portion of the seventh message is sent to the RLC layer of the SCG, and another portion of the seventh message is sent to the RLC layer of the MCG.

[0060] The RLC layer of the SCG receives a portion of the seventh message, uses the portion of the seventh message to generate an eighth message, and sends it to the MAC layer of the SCG.

[0061] The RLC layer of the MCG receives another part of the seventh message, uses the other part of the seventh message to generate the ninth message, and sends it to the MAC layer of the MCG.

[0062] In one possible implementation, the second transmission unit is specifically used for:

[0063] The fifth message is generated at the PDCP layer of the MCG and sent to the RLC layer of the MCG.

[0064] The RLC layer of the MCG receives the fifth message, uses the fifth message to generate a sixth message, and sends it to the MAC layer of the MCG.

[0065] Alternatively, a fifth message can be generated at the PDCP layer of the MCG, a portion of which is sent to the RLC layer of the MCG, and the other portion of which is sent to the RLC layer of the SCG.

[0066] The RLC layer of the MCG receives a portion of the fifth message, uses the portion of the fifth message to generate a sixth message, and sends it to the MAC layer of the MCG.

[0067] The RLC layer of the SCG receives another part of the fifth message, uses the other part of the fifth message to generate a sixth message, and sends it to the MAC layer of the SCG.

[0068] In one possible implementation, the second transmission unit is specifically used for:

[0069] The seventh message is generated at the MAC layer of the SCG and sent to the RLC layer of the SCG.

[0070] The RLC layer of the SCG receives the seventh message, uses the seventh message to generate the eighth message, and sends it to the PDCP layer of the SCG.

[0071] In one possible implementation, the second transmission unit is specifically used for:

[0072] A portion of the seventh message is generated by the MAC layer of the SCG and another portion of the seventh message is generated by the MAC layer of the MCG. The portion of the seventh message is sent to the RLC layer of the SCG and the other portion of the seventh message is sent to the RLC layer of the MCG.

[0073] The RLC layer of the SCG receives the portion of the seventh message, uses the portion of the seventh message to generate the eighth message, and sends it to the PDCP layer of the SCG.

[0074] The RLC layer of the MCG receives another part of the seventh message, uses the other part of the seventh message to generate an eighth message, and sends it to the PDCP layer of the SCG.

[0075] Fifthly, embodiments of this application also provide a computer program, characterized in that the computer program includes instructions that, when executed by a processor, enable the method described in any one of the first or second aspects to be implemented.

[0076] In a sixth aspect, embodiments of this application also provide a computer-readable storage medium, characterized in that the computer-readable storage medium stores program code for execution by a device, which, when executed by the device, is used to implement the method described in any one of the first or second aspects. Attached Figure Description

[0077] To more clearly illustrate the technical model in the embodiments or background art of this application, the accompanying drawings used in the embodiments or background art of this application will be described below.

[0078] Figure 1 This is a schematic diagram of a carrier aggregation system architecture provided by an embodiment of the present invention.

[0079] Figure 2This is a schematic diagram of a dual-connectivity system architecture provided by an embodiment of the present invention.

[0080] Figure 3 This is an architecture diagram of a communication method provided in an embodiment of the present invention.

[0081] Figure 3a This is a flowchart illustrating a communication method provided in an embodiment of the present invention.

[0082] Figure 4 This is a schematic diagram of a process for separating the user plane and the control plane according to an embodiment of the present invention.

[0083] Figure 5a This is an architecture diagram provided by an embodiment of the present invention, in which both the user plane and the control plane are deployed on the PCC.

[0084] Figure 5b This is an architecture diagram provided by an embodiment of the present invention, in which the control plane is deployed on the PCC and the user plane is deployed on the SCC.

[0085] Figure 6 This is an architecture diagram provided by an embodiment of the present invention, in which uplink is deployed on PCC and downlink is deployed on SCC.

[0086] Figure 7 This is an architecture diagram provided by an embodiment of the present invention, in which downlink is deployed on PCC and uplink is deployed on SCC.

[0087] Figure 8a This is an architecture diagram provided by an embodiment of the present invention, in which both downlink and uplink are carried on PCC / MCG.

[0088] Figure 8b This is an architecture diagram provided by an embodiment of the present invention, in which both downlink and uplink are carried on SCC / SCG.

[0089] Figure 8c This is an architecture diagram provided by an embodiment of the present invention, in which uplink is carried on PCC / MCG and downlink is carried on SCC / SCG.

[0090] Figure 8d This is an architecture diagram provided by an embodiment of the present invention, in which downlink is carried on PCC / MCG and uplink is carried on SCC / SCG.

[0091] Figure 9 This is an architecture diagram of another communication method provided in an embodiment of the present invention.

[0092] Figure 9a This is an architecture diagram provided by an embodiment of the present invention, in which uplink is deployed on MCG and downlink is deployed on SCG.

[0093] Figure 9bThis is an architecture diagram provided by an embodiment of the present invention, in which downlink is deployed on MCG and uplink is deployed on SCG.

[0094] Figure 9c This is a flowchart illustrating another communication method provided in an embodiment of the present invention.

[0095] Figure 10 This is a schematic diagram of a communication device structure provided in an embodiment of the present invention.

[0096] Figure 11 This is a schematic diagram of another communication device structure provided in an embodiment of the present invention. Detailed Implementation

[0097] The embodiments of the present invention will now be described with reference to the accompanying drawings.

[0098] The terms "first," "second," "third," and "fourth," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0099] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0100] As used in this specification, the terms "component," "module," "system," etc., are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process and / or an execution thread, and components may be located on a single computer and / or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0101] First, this paper analyzes and proposes the specific technical problem to be solved in this application. With the development of technology and the progress of society, in order to provide higher service rates, 3GPP introduced the CA (Carrier Aggregator) function, which aggregates multiple continuous or non-contiguous component carriers into a larger bandwidth, and the DC (Distribution Capacity) function, to fully utilize the resources and advantages of different carriers and different standards, thereby improving the user's uplink and downlink peak rate experience. In the existing network architecture, in the CA scenario, both the control plane and user plane are carried on the primary carrier cell (PCC), and then the user plane data is offloaded to the secondary carrier cell (SCC) through the RLC layer of the PCC. Similarly, in the CA scenario, uplink and downlink are also carried on the same carrier cell (PCC or SCC). Meanwhile, in the DC scenario, uplink and downlink are also carried on the same carrier group (primary carrier group MCG or secondary carrier group SCG).

[0102] In such multi-carrier scenarios (CA or DC), the strong coupling between the control plane and user plane, and uplink and downlink (carried on the same carrier) can lead to situations where there are large differences in carrier capabilities, such as the SCC's carrier capability being much greater than the PCC's carrier capability. In this case, the SCC can carry most of the traffic, so the user plane traffic carried on the PCC needs to be diverted to the SCC through the PCC's RLC layer. The diversion process not only adds an extra path, causing path delay, but the path also limits the diverted traffic, thus making it impossible to maximize resource utilization according to service requirements.

[0103] In summary, existing communication methods cannot meet users' demands for peak uplink and downlink rates and result in a significant waste of resources. Therefore, the communication method provided in this application is intended to solve the aforementioned technical problems.

[0104] To facilitate understanding of the embodiments of the present invention, the following exemplary examples illustrate the scenarios in which the communication method in this application is applied, which may include the following two scenarios:

[0105] Scenario 1, applied to carrier aggregation (CA) scenarios:

[0106] Carrier aggregation (CA) was introduced by 3GPP in Release 10. It aggregates multiple consecutive or non-consecutive carriers (Component Carriers, or CCs) into a larger bandwidth to meet 3GPP requirements. For details, please refer to [link to relevant documentation]. Figure 1 , Figure 1 This is a schematic diagram of a carrier aggregation system architecture provided by an embodiment of the present invention, such as... Figure 1 As shown, the system architecture may include terminal device 100, network device 110, multiple different carriers F1, F2, F3, etc., and NR. New Radio (NR) represents the channel through which the terminal device and network device establish a wireless connection. F1, F2, F3, etc., represent different carriers. The process of terminal device 100 and network device 110 transmitting data by aggregating multiple continuous or non-contiguous carriers (F1, F2, F3, etc.) in NR to create a larger bandwidth is called carrier aggregation.

[0107] Scenario 2, applied to dual-connection DC scenarios:

[0108] A dual-connectivity scenario means that one terminal device maintains connections with two network devices. See details. Figure 2 , Figure 2 This is a schematic diagram of a dual-connectivity system architecture provided in an embodiment of the present invention, such as... Figure 2 As shown, the system architecture may include terminal device 200, network device 210, and network device 220. Terminal device 200 establishes connections with network device 210 and network device 220 respectively.

[0109] It is understood that the above two application scenarios are only a few exemplary implementations in the embodiments of the present invention, and the application scenarios in the embodiments of the present invention include, but are not limited to, the above application scenarios.

[0110] Based on the technical problems mentioned above and the corresponding application scenarios in this application, and also to facilitate understanding of the embodiments of the present invention, one network architecture on which the embodiments of the present invention are based is described below. Please refer to... Figure 3 , Figure 3 This invention provides an architecture diagram of a communication method according to an embodiment of the invention. The technical method of this invention can be used in... Figure 3 Specific implementation in the system architecture shown in the example or a similar system architecture. For example... Figure 3 As shown, the system architecture may include core network equipment and network equipment, such as... Figure 3As shown, this method can be applied to the above. Figure 1 In the system architecture described herein, the one in which Figure 1 The architecture in the document can be used to support and execute... Figure 3 The method flow shown is step S301. The following will refer to the appendix... Figure 3 Described from the network device side. The method may include the following steps S301.

[0111] Step S301: Transmit the first type of data through the primary carrier cell PCC and transmit the second type of data through the secondary carrier cell SCC.

[0112] Specifically, the first type of data includes control plane data and the second type of data includes user plane data, or the first type of data includes uplink data and the second type of data includes downlink data, or the first type of data includes downlink data and the second type of data includes uplink data.

[0113] For example, the specific process of the first type of data including control plane data and the second type of data including user plane data may include the following steps:

[0114] Please see Figure 4 , Figure 4 This invention provides a schematic diagram of a user plane and control plane separation process. First, data from the core network's control plane is received by the PCC's PDCP layer 401. Then, a first message is generated by the PCC's PDCP layer and sent to the PCC's RLC layer 402. Upon receiving the first message, the PCC's RLC layer generates a second message and sends it to the PCC's MAC layer 403. Finally, the MAC layer sends the third message to the terminal device. Simultaneously, a third message is generated by the SCC's PDCP layer 404 and sent to the SCC's RLC layer 405. Then, the SCC's RLC layer receives the third message, generates a fourth message, and sends it to the SCC's MAC layer 406. Alternatively, the SCC's RLC layer receives the third message, generates a fourth message, sends a portion of the fourth message to the SCC's MAC layer 406, and sends the other portion to the PCC's MAC layer 403. Optionally, the above steps can also be applied to... Figure 3a , Figure 3a This is a flowchart illustrating a communication method provided in an embodiment of the present invention. The above flowchart is also applicable to this system architecture.

[0115] The technical advantages of using the above transmission path can be seen in [reference needed]. Figure 5a and Figure 5b , Figure 5a This is an architecture diagram provided by an embodiment of the present invention, in which both the user plane and the control plane are deployed on the PCC. Figure 5a In the existing architecture, both the control plane (CP) and user plane (UP) from the core network 503 are deployed on PCC501. This means the user plane can only route data to SCC502 via the RLC layer of PCC before sending it to the terminal device 500. This results in path latency when data still needs to be routed through PCC, even when SCC can handle most of the traffic, and it is also susceptible to transmission channel limitations, leading to a loss of CA gain. However, the architecture provided in this embodiment of the invention can achieve the following... Figure 5b The deployment. Figure 5b This is an architecture diagram provided by an embodiment of the present invention, in which the control plane is deployed on the PCC and the user plane is deployed on the SCC. Figure 5b The control plane CP from core network 503 is deployed on PCC501, and the user plane UP is deployed on SCC502.

[0116] And adopting a traditional CA architecture, such as Figure 5a The control plane and user plane bearers can only be deployed on the PCC, with data offloaded from the PCC's RLC to the SCCMAC. If the SCC carrier capacity exceeds the PCC carrier capacity, data exceeding the PCC's capacity needs to be sent via the PCC RLC, through the transmission channel, and then via the SCCMAC to the terminal, introducing additional path delay. Furthermore, if the transmission channel is limited, the SCC's capacity cannot be fully utilized, impacting user experience. The separation architecture described in this invention... Figure 5b Afterwards, the user plane can be carried on the SCC, and data can be directly transmitted from the core network to the SCC and sent directly through the SCC air interface, avoiding path detours and reducing data transmission latency. At the same time, even if data exceeding the capacity of the SCC needs to be sent to the PCC, the PCC has a smaller capacity and requires less transmission bandwidth, reducing transmission-restricted scenarios.

[0117] The specific process of uplinking data in the first type of data packet and downlinking data in the second type of data packet may include the following steps:

[0118] Please see Figure 6 , Figure 6This is an architecture diagram provided by an embodiment of the present invention, in which uplink is deployed on PCC and downlink on SCC. First, a first message is generated through the MAC layer 601 of the PCC, or a portion of the first message is generated through the MAC layer 601 of the PCC, and another portion of the first message is generated through the MAC layer 606 of the SCC, and sent to the RLC layer 602 of the PCC. The RLC layer of the PCC receives the first message, uses the first message to generate a second message, and sends it to the PDCP layer 603 of the PCC. Optionally, then, a third message is first generated through the PDCP layer 604 of the SCC and sent to the RLC layer 605 of the SCC; the RLC layer of the SCC receives the third message, uses the third message to generate a fourth message, and sends it to the MAC layer 606 of the SCC; or the RLC layer 605 of the SCC receives the third message, uses the third message to generate a fourth message, sends a portion of the fourth message to the MAC layer 601 of the SCC, and sends another portion of the fourth message to the MAC layer 606 of the PCC.

[0119] The specific process of handling downlink data of the first type of data packet and uplink data of the second type of data packet may include the following steps:

[0120] Please see Figure 7 , Figure 7 This is an architecture diagram provided by an embodiment of the present invention, in which downlink is deployed on PCC and uplink on SCC. First, a first message is generated through the PDCP layer 701 of the PCC and sent to the RLC layer 702 of the PCC. The RLC layer of the PCC receives the first message, uses it to generate a second message, and sends it to the MAC layer 703 of the PCC. Alternatively, the RLC layer 702 of the PCC receives the first message, uses it to generate a second message, sends a portion of the second message to the MAC layer 703 of the PCC, and sends another portion of the second message to the MAC layer 704 of the SCC. Optionally, a third message is then generated through the MAC layer 704 of the SCC, or a portion of the third message is generated through the MAC layer of the SCC, and another portion of the third message is generated through the MAC layer 703 of the PCC and sent to the RLC layer 705 of the SCC. The RLC layer of the SCC receives the third message, uses it to generate a fourth message, and sends it to the PDCP layer 706 of the SCC.

[0121] The technical advantages of using the above transmission path can be seen in [reference needed]. Figures 8a-8d , Figure 8aThis is an architecture diagram provided by an embodiment of the present invention, in which both downlink and uplink are carried on PCC / MCG. Figure 8a The existing architecture has the uplink and downlink tasks of the terminal device 800 deployed on the PCC / MCG801. Figure 8b This is an architecture diagram provided by an embodiment of the present invention, in which both downlink and uplink are carried on SCC / SCG. Figure 8b The existing architecture deploys both uplink and downlink tasks of the terminal device 800 on the SCC / SCG802. Figure 8c This is an architecture diagram provided by an embodiment of the present invention, in which uplink is carried on PCC / MCG and downlink is carried on SCC / SCG. Figure 8c The architecture provided in this embodiment of the invention is such that the uplink of the terminal device 800 is deployed on PCC / MCG801, and the downlink is deployed on SCC / SCG802. Figure 8d This is an architecture diagram provided by an embodiment of the present invention, in which downlink is carried on PCC / MCG and uplink is carried on SCC / SCG. Figure 8d The architecture provided in this embodiment of the invention is such that the downlink of the terminal device 800 is deployed on PCC / MCG801, and the uplink is deployed on SCC / SCG802.

[0122] As shown in the diagram above, in a traditional CA / DC architecture, uplink and downlink traffic can only be deployed on a single carrier. When the uplink and downlink capabilities of the carriers are not comparable, and the uplink and downlink service requirements are inconsistent, it can lead to deployment conflicts, preventing both from achieving optimal performance simultaneously. For example, in a combined FDD and TDD scenario, high-volume downlink traffic needs to be deployed on a high-bandwidth TDD carrier, but TDD uplink capabilities are weaker, requiring uplink traffic to be deployed on FDD. This strong coupling between uplink and downlink deployments means that one side will always suffer performance degradation. This invention adopts a separate uplink and downlink deployment, allowing each to select the carrier with the optimal performance for deployment.

[0123] In summary, applying the above steps to a carrier aggregation (CA) scenario, and adopting a user plane and control plane, uplink and downlink separation architecture, transforms the original architecture where the control plane and user plane, uplink and downlink could only be carried on the same carrier into one where the control plane is on the PCC and the user plane is on the SCC, or uplink on the PCC and downlink on the SCC, or downlink on the PCC and uplink on the SCC. This differs from existing architectures where the control plane and user plane, or uplink and downlink, can only be carried on the same carrier. This invention not only allows the user plane and control plane to be carried on different carriers (e.g., control plane on PCC and user plane on SCC), but also addresses the issue that when the SCC's carrier capacity exceeds the PCC's, data exceeding the PCC's capacity needs to be sent through the PCC's RLC layer, via the transmission channel, and then through the SCC's MAC layer to the terminal, introducing additional path delay. Furthermore, if the transmission channel is limited, the SCC's capacity cannot be fully utilized, wasting resources. Moreover, it allows for separate deployment of uplink and downlink, enabling each to select the carrier with the optimal performance. For example, high-volume downlink traffic requires deployment on a high-bandwidth SCC (Short-Range Carrier). However, the SCC has weak uplink capabilities, while the PCC (Programmable Controller) has strong uplink capabilities but weak downlink capabilities. In this case, if a tightly coupled uplink / downlink deployment is still used, the performance of one side will inevitably suffer. Therefore, using the separation architecture provided in this invention, uplink and downlink can be deployed on carriers with superior performance, respectively. In summary, the communication method provided in this invention allows the user plane and control plane, or uplink and downlink, to be deployed on different carriers, thereby fully utilizing the resources and advantages of different carriers, maximizing resource utilization, and improving service rates.

[0124] Please see Figure 9 , Figure 9 This is an architecture diagram of another communication method provided by an embodiment of the present invention. The technical method of the present invention can be used in... Figure 9 Specific implementation in the system architecture shown in the example or a similar system architecture. For example... Figure 9 As shown, the system architecture may include core network equipment and network equipment, such as... Figure 9 As shown, this method can be applied to the above. Figure 2 In the system architecture described herein, the one in which Figure 2 The architecture in the document can be used to support and execute... Figure 9 The method flow step S901 is shown below. The following will refer to the appendix... Figure 9 Described from the network device side. The method may include the following steps S901.

[0125] Step S901: Transmit the third type of data through the main carrier group (MCG) and transmit the fourth type of data through the secondary carrier group (SCG).

[0126] Specifically, the third type of data includes uplink data and the fourth type of data includes downlink data, or the third type of data includes downlink data and the fourth type of data includes uplink data;

[0127] For example, the specific process of the third type of data including uplink data and the fourth type of data including downlink data may include the following steps:

[0128] See Figure 9a , Figure 9a This is an architecture diagram provided by an embodiment of the present invention, in which uplink is deployed on the MCG and downlink on the SCG. First, the network device generates a fifth message at the MAC layer 901 of the MCG and sends it to the RLC layer 902 of the MCG; the RLC layer of the MCG receives the fifth message, uses it to generate a sixth message, and sends it to the PDCP layer 903 of the MCG; or, the network device generates a portion of the fifth message through the MAC layer 901 of the MCG and another portion of the fifth message through the MAC layer 906 of the SCG, sends the portion of the fifth message to the RLC layer 902 of the MCG, and the other portion of the fifth message to the RLC layer 905 of the SCG; the RLC layer of the MCG receives the portion of the fifth message, uses it to generate a sixth message, and sends it to the PDCP layer 903 of the MCG; the RLC layer of the SCG receives the other portion of the fifth message, uses it to generate a sixth message, and sends it to the PDCP layer 903 of the MCG.

[0129] Optionally, while sending the aforementioned message, the network device also generates a seventh message at the PDCP layer 904 of the SCG and sends it to the RLC layer 905 of the SCG; the RLC layer of the SCG receives the seventh message, uses the seventh message to generate an eighth message, and sends it to the MAC layer 906 of the SCG; or the network device generates a seventh message at the PDCP layer 904 of the SCG, sends a part of the seventh message to the RLC layer 905 of the SCG, and sends another part of the seventh message to the RLC layer 902 of the MCG; the RLC layer of the SCG receives a part of the seventh message, uses the part of the seventh message to generate an eighth message, and sends it to the MAC layer 906 of the SCG; the RLC layer of the MCG receives the other part of the seventh message, uses the other part of the seventh message to generate a ninth message, and sends it to the MAC layer 901 of the MCG.

[0130] For example, the specific process of the third type of data including downlink data and the fourth type of data including uplink data may include the following steps:

[0131] See Figure 9b , Figure 9bThis is an architecture diagram provided by an embodiment of the present invention, in which downlink is deployed on the MCG and uplink on the SCG. First, a fifth message is generated at the PDCP layer 903 of the MCG and sent to the RLC layer 902 of the MCG. The RLC layer of the MCG receives the fifth message, uses it to generate a sixth message, and sends it to the MAC layer 901 of the MCG. Alternatively, a fifth message is generated at the PDCP layer 903 of the MCG, a portion of the fifth message is sent to the RLC layer 902 of the MCG, and another portion of the fifth message is sent to the RLC layer 905 of the SCG. The RLC layer of the MCG receives a portion of the fifth message, uses it to generate a sixth message, and sends it to the MAC layer 901 of the MCG. The RLC layer of the SCG receives the other portion of the fifth message, uses it to generate a sixth message, and sends it to the MAC layer 906 of the SCG.

[0132] Optionally, a seventh message is then generated at the SCG's MAC layer 906 and sent to the SCG's RLC layer 905. The SCG's RLC layer receives the seventh message, uses it to generate an eighth message, and sends it to the SCG's PDCP layer 904. Alternatively, a portion of the seventh message is generated at the SCG's MAC layer 906, and another portion is generated at the MCG's MAC layer 901. The portion of the seventh message is sent to the SCG's RLC layer 905, and the other portion is sent to the MCG's RLC layer 902. The SCG's RLC layer receives the portion of the seventh message, uses it to generate an eighth message, and sends it to the SCG's PDCP layer 904. The MCG's RLC layer receives the other portion of the seventh message, uses it to generate an eighth message, and sends it to the SCG's PDCP layer 904. Optionally, the above process steps can also be used... Figure 9c The system architecture, Figure 9c This is a flowchart illustrating another communication method provided in an embodiment of the present invention.

[0133] As shown in the diagram above, in a traditional CA / DC architecture, uplink and downlink traffic can only be deployed on a single carrier. When the uplink and downlink capabilities of the carriers are not comparable, and the uplink and downlink service requirements are inconsistent, it can lead to deployment conflicts, preventing both from achieving optimal performance simultaneously. For example, in a combined FDD and TDD scenario, high-volume downlink traffic needs to be deployed on a high-bandwidth TDD carrier, but TDD uplink capabilities are weaker, requiring uplink traffic to be deployed on FDD. This strong coupling between uplink and downlink deployments means that one side will always suffer performance degradation. This invention adopts a separate uplink and downlink deployment, allowing each to select the carrier with the optimal performance for deployment.

[0134] In summary, applying this invention to a dual-connectivity DC scenario, a separate uplink and downlink architecture is adopted. This transforms the original scenario where uplink and downlink could only be carried on the same carrier into one where uplink is on the MCG and downlink is on the SCG, or vice versa. Unlike existing architectures where uplink and downlink can only be carried on the same carrier, this invention allows for separate deployment of uplink and downlink, enabling each to select the carrier with the best performance. For example, high-volume downlink traffic requires deployment on the high-bandwidth SCG, but the SCG has weak uplink capabilities while the MCG has strong uplink capabilities but weak downlink capabilities. In this case, a tightly coupled uplink / downlink deployment would inevitably result in performance degradation on one side. Therefore, the separate architecture provided by this invention is necessary, allowing uplink and downlink to select the carrier with the best performance for each. In conclusion, to improve service rates, the communication method provided by this invention allows uplink and downlink to be deployed on different carriers, thereby fully utilizing the resources and advantages of different carriers and maximizing resource utilization.

[0135] Please see Figure 10 , Figure 10 This is a schematic diagram of a communication device structure provided in an embodiment of the present invention. The communication device 100 may include a first transmission unit 1001, wherein...

[0136] The first transmission unit 1001 is used to transmit first type of data through the primary carrier cell PCC and to transmit second type of data through the secondary carrier cell SCC.

[0137] The first type of data includes control plane data and the second type of data includes user plane data; or the first type of data includes uplink data and the second type of data includes downlink data; or the first type of data includes downlink data and the second type of data includes uplink data.

[0138] In one possible implementation, the first transmission unit is specifically used for:

[0139] The first message is generated by the Packet Data Convergence Protocol (PDCP) layer of the PCC and sent to the Radio Link Control (RLC) layer of the PCC.

[0140] The PCC receives the first message through its RLC layer, generates a second message using the first message, and sends it to the PCC's Media Access Control (MAC) layer.

[0141] In one possible implementation, the first transmission unit is specifically used for:

[0142] A third message is generated through the PDCP layer of the SCC and sent to the RLC layer of the SCC.

[0143] The third message is received through the RLC layer of the SCC, a fourth message is generated using the third message, and then sent to the MAC layer of the SCC. Alternatively, the third message is received through the RLC layer of the SCC, a fourth message is generated using the third message, a portion of the fourth message is sent to the MAC layer of the SCC, and another portion of the fourth message is sent to the MAC layer of the PCC.

[0144] In one possible implementation, the first transmission unit is specifically used for:

[0145] The first message is generated through the MAC layer of the PCC, or a part of the first message is generated through the MAC layer of the PCC, and another part of the first message is generated through the MAC layer of the SCC, and then sent to the RLC layer of the PCC.

[0146] The first message is received by the RLC layer of the PCC, a second message is generated using the first message, and then sent to the PDCP layer of the PCC.

[0147] In one possible implementation, the first transmission unit is specifically used for:

[0148] A third message is generated through the PDCP layer of the SCC and sent to the RLC layer of the SCC.

[0149] The third message is received through the RLC layer of the SCC, a fourth message is generated using the third message, and then sent to the MAC layer of the SCC; or the third message is received through the RLC layer of the SCC, a fourth message is generated using the third message, a part of the fourth message is sent to the MAC layer of the SCC, and another part of the fourth message is sent to the MAC layer of the PCC.

[0150] In one possible implementation, the first transmission unit is specifically used for:

[0151] The first message is generated through the PDCP layer of the PCC and sent to the RLC layer of the PCC;

[0152] The first message is received by the RLC layer of the PCC, a second message is generated using the first message, and then sent to the MAC layer of the PCC.

[0153] Alternatively, the first message can be received through the RLC layer of the PCC, and a second message can be generated using the first message. A portion of the second message can be sent to the MAC layer of the PCC, and the other portion of the second message can be sent to the MAC layer of the SCC.

[0154] In one possible implementation, the first transmission unit is specifically used for:

[0155] The third message is generated through the MAC layer of the SCC, or a portion of the third message is generated through the MAC layer of the SCC, and another portion of the third message is generated through the MAC layer of the PCC, and then sent to the RLC layer of the SCC.

[0156] The third message is received by the RLC layer of the SCC, a fourth message is generated using the third message, and then sent to the PDCP layer of the SCC.

[0157] Figure 10 Each unit can be implemented in software, hardware, or a combination thereof. Hardware-implemented units may include circuits, electric furnaces, algorithm circuits, or analog circuits, etc. Software-implemented units may include program instructions, which are considered a software product, stored in memory, and can be executed by a processor to perform related functions; see the previous introduction for details.

[0158] It should be noted that the functions of the communication device 100 described in the above embodiments of this application can be found in the above description. Figures 3-8d The relevant descriptions in the method embodiments are not repeated here.

[0159] Please see Figure 11 , Figure 11 This is a schematic diagram of another communication device structure provided in an embodiment of the present invention. The communication device 110 may include a second transmission unit 1101; wherein,

[0160] The second transmission unit 1101 is used to transmit third type data through the main carrier group (MCG) and fourth type data through the auxiliary carrier group (SCG).

[0161] Wherein, the third type of data includes uplink data and the fourth type of data includes downlink data, or the third type of data includes downlink data and the fourth type of data includes uplink data;

[0162] In one possible implementation, the second transmission unit is specifically used for:

[0163] The fifth message is generated at the MAC layer of the MCG and sent to the RLC layer of the MCG.

[0164] The RLC layer of the MCG receives the fifth message, uses the fifth message to generate a sixth message, and sends it to the PDCP layer of the MCG.

[0165] Alternatively, a portion of the fifth message can be generated through the MAC layer of the MCG and another portion of the fifth message can be generated through the MAC layer of the SCG. The portion of the fifth message can be sent to the RLC layer of the MCG and the other portion of the fifth message can be sent to the RLC layer of the SCG.

[0166] The RLC layer of the MCG receives the portion of the fifth message, uses the portion of the fifth message to generate the sixth message, and sends it to the PDCP layer of the MCG.

[0167] The RLC layer of the SCG receives another part of the fifth message, uses the other part of the fifth message to generate a sixth message, and sends it to the PDCP layer of the MCG.

[0168] In one possible implementation, the second transmission unit is specifically used for:

[0169] The seventh message is generated at the PDCP layer of the SCG and sent to the RLC layer of the SCG.

[0170] The RLC layer of the SCG receives the seventh message, uses the seventh message to generate the eighth message, and sends it to the MAC layer of the SCG.

[0171] In one possible implementation, the second transmission unit is specifically used for:

[0172] A seventh message is generated at the PDCP layer of the SCG, a portion of the seventh message is sent to the RLC layer of the SCG, and another portion of the seventh message is sent to the RLC layer of the MCG.

[0173] The RLC layer of the SCG receives a portion of the seventh message, uses the portion of the seventh message to generate an eighth message, and sends it to the MAC layer of the SCG.

[0174] The RLC layer of the MCG receives another part of the seventh message, uses the other part of the seventh message to generate the ninth message, and sends it to the MAC layer of the MCG.

[0175] In one possible implementation, the second transmission unit is specifically used for:

[0176] The fifth message is generated at the PDCP layer of the MCG and sent to the RLC layer of the MCG.

[0177] The RLC layer of the MCG receives the fifth message, uses the fifth message to generate a sixth message, and sends it to the MAC layer of the MCG.

[0178] Alternatively, a fifth message can be generated at the PDCP layer of the MCG, a portion of which is sent to the RLC layer of the MCG, and the other portion of which is sent to the RLC layer of the SCG.

[0179] The RLC layer of the MCG receives a portion of the fifth message, uses the portion of the fifth message to generate a sixth message, and sends it to the MAC layer of the MCG.

[0180] The RLC layer of the SCG receives another part of the fifth message, uses the other part of the fifth message to generate a sixth message, and sends it to the MAC layer of the SCG.

[0181] In one possible implementation, the second transmission unit is specifically used for:

[0182] The seventh message is generated at the MAC layer of the SCG and sent to the RLC layer of the SCG.

[0183] The RLC layer of the SCG receives the seventh message, uses the seventh message to generate the eighth message, and sends it to the PDCP layer of the SCG.

[0184] In one possible implementation, the second transmission unit is specifically used for:

[0185] A portion of the seventh message is generated by the MAC layer of the SCG and another portion of the seventh message is generated by the MAC layer of the MCG. The portion of the seventh message is sent to the RLC layer of the SCG and the other portion of the seventh message is sent to the RLC layer of the MCG.

[0186] The RLC layer of the SCG receives the portion of the seventh message, uses the portion of the seventh message to generate the eighth message, and sends it to the PDCP layer of the SCG.

[0187] The RLC layer of the MCG receives another part of the seventh message, uses the other part of the seventh message to generate an eighth message, and sends it to the PDCP layer of the SCG.

[0188] Figure 11 Each unit can be implemented in software, hardware, or a combination thereof. Hardware-implemented units may include circuits, electric furnaces, algorithm circuits, or analog circuits, etc. Software-implemented units may include program instructions, which are considered a software product, stored in memory, and can be executed by a processor to perform related functions; see the previous introduction for details.

[0189] It should be noted that the functions of the communication device 110 described in the above embodiments of this application can be found in the above description. Figures 9-9bThe relevant descriptions in the method embodiments are not repeated here.

[0190] This invention also provides a computer storage medium, wherein the computer storage medium may store a program, which, when executed, includes some or all of the steps described in any of the above method embodiments.

[0191] This invention also provides a computer program that includes instructions that, when executed by a computer, enable the computer to perform some or all of the steps described in any of the above method embodiments.

[0192] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0193] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0194] In the several embodiments provided in this application, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical or other forms.

[0195] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0196] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0197] If the integrated units described above are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which can be a personal computer, server, or network device, specifically a processor in the computer device) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium may include various media capable of storing program code, such as a USB flash drive, portable hard drive, magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM).

[0198] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A communication method, characterized in that, Applied to network devices, the method includes: The first type of data is transmitted through the primary carrier cell (PCC), and the second type of data is transmitted through the secondary carrier cell (SCC). The first type of data includes control plane data, and the second type of data includes user plane data. The transmission of the first type of data through the primary carrier cell (PCC) includes: receiving the first type of data from the core network through the packet data convergence protocol (PDCP) layer of the PCC, generating a first message based on the first type of data, and sending it to the radio link control (RLC) layer of the PCC; receiving the first message through the RLC layer of the PCC, generating a second message using the first message, and sending it to the media access control (MAC) layer of the PCC. The transmission of the second type of data through the secondary carrier cell (SCC) includes: receiving the second type of data from the core network through the PDCP layer of the SCC, generating a third message based on the second type of data, and sending it to the RLC layer of the SCC; receiving the third message through the RLC layer of the SCC, generating a fourth message using the third message, and sending it to the MAC layer of the SCC; or receiving the third message through the RLC layer of the SCC, generating a fourth message using the third message, sending a part of the fourth message to the MAC layer of the SCC, and sending another part of the fourth message to the MAC layer of the PCC.

2. The method according to claim 1, characterized in that, The first type of data includes uplink data, and the second type of data includes downlink data; the transmission of the first type of data through the primary carrier cell (PCC) includes: The first message is generated through the MAC layer of the PCC, or a part of the first message is generated through the MAC layer of the PCC, and another part of the first message is generated through the MAC layer of the SCC, and then sent to the RLC layer of the PCC. The first message is received by the RLC layer of the PCC, a second message is generated using the first message, and then sent to the PDCP layer of the PCC.

3. The method according to claim 2, characterized in that, The transmission of the second type of data via the secondary carrier cell (SCC) includes: A third message is generated through the PDCP layer of the SCC and sent to the RLC layer of the SCC. The third message is received through the RLC layer of the SCC, a fourth message is generated using the third message, and then sent to the MAC layer of the SCC; or the third message is received through the RLC layer of the SCC, a fourth message is generated using the third message, a part of the fourth message is sent to the MAC layer of the SCC, and another part of the fourth message is sent to the MAC layer of the PCC.

4. The method according to claim 1, characterized in that, The first type of data includes downlink data, and the second type of data includes uplink data; the transmission of the first type of data through the primary carrier cell (PCC) includes: The first message is generated through the PDCP layer of the PCC and sent to the RLC layer of the PCC; The first message is received by the RLC layer of the PCC, a second message is generated using the first message, and then sent to the MAC layer of the PCC. Alternatively, the first message can be received through the RLC layer of the PCC, and a second message can be generated using the first message. A portion of the second message can be sent to the MAC layer of the PCC, and the other portion of the second message can be sent to the MAC layer of the SCC.

5. The method according to claim 4, characterized in that, The transmission of the second type of data via the secondary carrier cell (SCC) includes: The third message is generated through the MAC layer of the SCC, or a portion of the third message is generated through the MAC layer of the SCC, and another portion of the third message is generated through the MAC layer of the PCC, and then sent to the RLC layer of the SCC. The third message is received by the RLC layer of the SCC, a fourth message is generated using the third message, and then sent to the PDCP layer of the SCC.

6. A communication method, characterized in that, Applied to network devices, the method includes: The third type of data is transmitted through the primary carrier group (MCG), and the fourth type of data is transmitted through the secondary carrier group (SCG). The third type of data originates from the core network and is transmitted through the PDCP layer, RLC layer, and MAC layer of the MCG in the following order. The fourth type of data originates from the core network and is transmitted through the PDCP layer, RLC layer, and MAC layer of the SCG in the following order. The third type of data includes uplink data and the fourth type of data includes downlink data, or the third type of data includes downlink data and the fourth type of data includes uplink data.

7. The method according to claim 6, characterized in that, The third type of data includes uplink data, and the fourth type of data includes downlink data; the transmission of the third type of data through the main carrier group (MCG) includes: The fifth message is generated at the MAC layer of the MCG and sent to the RLC layer of the MCG. The RLC layer of the MCG receives the fifth message, uses the fifth message to generate a sixth message, and sends it to the PDCP layer of the MCG. Alternatively, a portion of the fifth message can be generated through the MAC layer of the MCG and another portion of the fifth message can be generated through the MAC layer of the SCG. The portion of the fifth message can be sent to the RLC layer of the MCG and the other portion of the fifth message can be sent to the RLC layer of the SCG. The RLC layer of the MCG receives the portion of the fifth message, uses the portion of the fifth message to generate the sixth message, and sends it to the PDCP layer of the MCG. The RLC layer of the SCG receives another part of the fifth message, uses the other part of the fifth message to generate a sixth message, and sends it to the PDCP layer of the MCG.

8. The method according to claim 7, characterized in that, The transmission of the fourth type of data via the secondary carrier group (SCG) includes: The seventh message is generated at the PDCP layer of the SCG and sent to the RLC layer of the SCG. The RLC layer of the SCG receives the seventh message, uses the seventh message to generate the eighth message, and sends it to the MAC layer of the SCG.

9. The method according to claim 7, characterized in that, The transmission of the fourth type of data via the secondary carrier group (SCG) includes: A seventh message is generated at the PDCP layer of the SCG, a portion of the seventh message is sent to the RLC layer of the SCG, and another portion of the seventh message is sent to the RLC layer of the MCG. The RLC layer of the SCG receives a portion of the seventh message, uses the portion of the seventh message to generate an eighth message, and sends it to the MAC layer of the SCG. The RLC layer of the MCG receives another part of the seventh message, uses the other part of the seventh message to generate the ninth message, and sends it to the MAC layer of the MCG.

10. The method according to claim 6, characterized in that, The third type of data includes downlink data, and the fourth type of data includes uplink data; the transmission of the third type of data through the primary carrier group (MCG) includes: The fifth message is generated at the PDCP layer of the MCG and sent to the RLC layer of the MCG. The RLC layer of the MCG receives the fifth message, uses the fifth message to generate a sixth message, and sends it to the MAC layer of the MCG. Alternatively, a fifth message can be generated at the PDCP layer of the MCG, a portion of which is sent to the RLC layer of the MCG, and the other portion of which is sent to the RLC layer of the SCG. The RLC layer of the MCG receives a portion of the fifth message, uses the portion of the fifth message to generate a sixth message, and sends it to the MAC layer of the MCG. The RLC layer of the SCG receives another part of the fifth message, uses the other part of the fifth message to generate a sixth message, and sends it to the MAC layer of the SCG.

11. The method according to claim 10, characterized in that, The transmission of the fourth type of data is performed via the secondary carrier group (SCG). The seventh message is generated at the MAC layer of the SCG and sent to the RLC layer of the SCG. The RLC layer of the SCG receives the seventh message, uses the seventh message to generate the eighth message, and sends it to the PDCP layer of the SCG.

12. The method according to claim 10, characterized in that, The transmission of the fourth type of data via the secondary carrier group (SCG) includes: A portion of the seventh message is generated by the MAC layer of the SCG and another portion of the seventh message is generated by the MAC layer of the MCG. The portion of the seventh message is sent to the RLC layer of the SCG and the other portion of the seventh message is sent to the RLC layer of the MCG. The RLC layer of the SCG receives the portion of the seventh message, uses the portion of the seventh message to generate the eighth message, and sends it to the PDCP layer of the SCG. The RLC layer of the MCG receives another part of the seventh message, uses the other part of the seventh message to generate an eighth message, and sends it to the PDCP layer of the SCG.

13. A communication device, characterized in that, include: The first transmission unit is used to transmit first type of data through the primary carrier cell PCC and to transmit second type of data through the secondary carrier cell SCC. The first type of data includes control plane data, and the second type of data includes user plane data. The transmission unit is specifically used for: The first type of data is received from the core network through the Packet Data Convergence Protocol (PDCP) layer of the PCC, a first message is generated based on the first type of data, and then sent to the Radio Link Control (RLC) layer of the PCC. The PCC receives the first message through its RLC layer, generates a second message using the first message, and sends it to the PCC's Media Access Control (MAC) layer. The transmission unit is specifically used for: The second type of data is received from the core network through the PDCP layer of the SCC, and a third message is generated based on the second type of data and sent to the RLC layer of the SCC. The third message is received through the RLC layer of the SCC, a fourth message is generated using the third message, and then sent to the MAC layer of the SCC; or the third message is received through the RLC layer of the SCC, a fourth message is generated using the third message, a part of the fourth message is sent to the MAC layer of the SCC, and another part of the fourth message is sent to the MAC layer of the PCC.

14. The apparatus according to claim 13, characterized in that, The first type of data includes uplink data, and the second type of data includes downlink data; the transmission unit is specifically used for: The first message is generated through the MAC layer of the PCC, or a part of the first message is generated through the MAC layer of the PCC, and another part of the first message is generated through the MAC layer of the SCC, and then sent to the RLC layer of the PCC. The first message is received by the RLC layer of the PCC, a second message is generated using the first message, and then sent to the PDCP layer of the PCC.

15. The apparatus according to claim 14, characterized in that, The transmission unit is specifically used for: A third message is generated through the PDCP layer of the SCC and sent to the RLC layer of the SCC. The third message is received through the RLC layer of the SCC, a fourth message is generated using the third message, and then sent to the MAC layer of the SCC; or the third message is received through the RLC layer of the SCC, a fourth message is generated using the third message, a part of the fourth message is sent to the MAC layer of the SCC, and another part of the fourth message is sent to the MAC layer of the PCC.

16. The apparatus according to claim 13, characterized in that, The first type of data includes downlink data, and the second type of data includes uplink data; the transmission unit is specifically used for: The first message is generated through the PDCP layer of the PCC and sent to the RLC layer of the PCC; The first message is received by the RLC layer of the PCC, a second message is generated using the first message, and then sent to the MAC layer of the PCC. Alternatively, the first message can be received through the RLC layer of the PCC, and a second message can be generated using the first message. A portion of the second message can be sent to the MAC layer of the PCC, and the other portion of the second message can be sent to the MAC layer of the SCC.

17. The apparatus according to claim 16, characterized in that, The transmission unit is specifically used for: The third message is generated through the MAC layer of the SCC, or a portion of the third message is generated through the MAC layer of the SCC, and another portion of the third message is generated through the MAC layer of the PCC, and then sent to the RLC layer of the SCC. The third message is received by the RLC layer of the SCC, a fourth message is generated using the third message, and then sent to the PDCP layer of the SCC.

18. A communication device, characterized in that, include: The transmission unit is used for transmitting third-type data via the primary carrier group (MCG) and fourth-type data via the secondary carrier group (SCG); the third-type data originates from the core network and is transmitted via the PDCP layer, RLC layer, and MAC layer of the MCG in the following order; the fourth-type data originates from the core network and is transmitted via the PDCP layer, RLC layer, and MAC layer of the SCG in the following order. The third type of data includes uplink data and the fourth type of data includes downlink data, or the third type of data includes downlink data and the fourth type of data includes uplink data.

19. The apparatus according to claim 18, characterized in that, The third type of data includes uplink data, and the fourth type of data includes downlink data; the transmission unit is specifically used for: The fifth message is generated at the MAC layer of the MCG and sent to the RLC layer of the MCG. The RLC layer of the MCG receives the fifth message, uses the fifth message to generate a sixth message, and sends it to the PDCP layer of the MCG. Alternatively, a portion of the fifth message can be generated through the MAC layer of the MCG and another portion of the fifth message can be generated through the MAC layer of the SCG. The portion of the fifth message can be sent to the RLC layer of the MCG and the other portion of the fifth message can be sent to the RLC layer of the SCG. The RLC layer of the MCG receives the portion of the fifth message, uses the portion of the fifth message to generate the sixth message, and sends it to the PDCP layer of the MCG. The RLC layer of the SCG receives another part of the fifth message, uses the other part of the fifth message to generate a sixth message, and sends it to the PDCP layer of the MCG.

20. The apparatus according to claim 19, characterized in that, The transmission unit is specifically used for: The seventh message is generated at the PDCP layer of the SCG and sent to the RLC layer of the SCG. The RLC layer of the SCG receives the seventh message, uses the seventh message to generate the eighth message, and sends it to the MAC layer of the SCG.

21. The apparatus according to claim 19, characterized in that, The transmission unit is specifically used for: A seventh message is generated at the PDCP layer of the SCG, a portion of the seventh message is sent to the RLC layer of the SCG, and another portion of the seventh message is sent to the RLC layer of the MCG. The RLC layer of the SCG receives a portion of the seventh message, uses the portion of the seventh message to generate an eighth message, and sends it to the MAC layer of the SCG. The RLC layer of the MCG receives another part of the seventh message, uses the other part of the seventh message to generate the ninth message, and sends it to the MAC layer of the MCG.

22. The apparatus according to claim 18, characterized in that, The third type of data includes downlink data, and the fourth type of data includes uplink data; the transmission unit is specifically used for: The fifth message is generated at the PDCP layer of the MCG and sent to the RLC layer of the MCG. The RLC layer of the MCG receives the fifth message, uses the fifth message to generate a sixth message, and sends it to the MAC layer of the MCG. Alternatively, a fifth message can be generated at the PDCP layer of the MCG, a portion of which is sent to the RLC layer of the MCG, and the other portion of which is sent to the RLC layer of the SCG. The RLC layer of the MCG receives a portion of the fifth message, uses the portion of the fifth message to generate a sixth message, and sends it to the MAC layer of the MCG. The RLC layer of the SCG receives another part of the fifth message, uses the other part of the fifth message to generate a sixth message, and sends it to the MAC layer of the SCG.

23. The apparatus according to claim 22, characterized in that, The transmission unit is specifically used for: The seventh message is generated at the MAC layer of the SCG and sent to the RLC layer of the SCG. The RLC layer of the SCG receives the seventh message, uses the seventh message to generate the eighth message, and sends it to the PDCP layer of the SCG.

24. The apparatus according to claim 22, characterized in that, The transmission unit is specifically used for: A portion of the seventh message is generated by the MAC layer of the SCG and another portion of the seventh message is generated by the MAC layer of the MCG. The portion of the seventh message is sent to the RLC layer of the SCG and the other portion of the seventh message is sent to the RLC layer of the MCG. The RLC layer of the SCG receives the portion of the seventh message, uses the portion of the seventh message to generate the eighth message, and sends it to the PDCP layer of the SCG. The RLC layer of the MCG receives another part of the seventh message, uses the other part of the seventh message to generate an eighth message, and sends it to the PDCP layer of the SCG.

25. A computer program, characterized in that, The computer program includes instructions that, when executed by a processor, enable the implementation of the method according to any one of claims 1-5 or 6-12.

26. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores program code for execution by the device, which, when executed by the device, is used to implement the method of any one of claims 1-5 or 6-12.

Images