Communication method and communication device applied to dual-connection DC scene

Abstract

The invention provides a communication method applied to a dual connectivity DC scene, the method is applied to a first communication device, and the method comprises the following steps: receiving first indication information, the first indication information being used for activating a function of a first entity in the first communication device or used for deactivating the function of the first entity in the first communication device; according to the first indication information, when the function of the first entity is activated, discarding data of the first entity according to a first timer; or discarding the data of the first entity according to a second timer under the condition that the function of the first entity is deactivated according to the first indication information. According to the method, in a DC scene, excessive data packets can be prevented from being discarded, and the service experience feeling is improved.

Description

Technical Field

[0001] This application relates to the field of wireless communication, and more specifically, to a communication method and a communication device applied to a dual-connectivity (DC) scenario. Background Art

[0002] Future extended reality (XR) will become the main business carried by communication networks. Not only will the clarity of XR be upgraded from 8K to 16K / 32K or even higher, but the augmented reality (AR) business scenarios for industry applications will also evolve from single-terminal communication to multi-XR collaborative interaction and develop rapidly around 2025. At that time, due to the influence of service traffic and service characteristics, XR services will put forward higher requirements for SLA guarantees such as network capacity, latency, and bandwidth. At the same time, there is still great room for development in basic communication services. Multi-party video calls, virtual meetings, etc., represented by remote work, will become the norm. In terms of service forms, the current meeting method of fixed access + video + call will be transformed into multi-party remote collaboration of mobile access + rich media + real-time interaction. For example, enterprise employees can access the enterprise office environment at any time with virtual avatars and communicate efficiently with colleagues. Therefore, the current capabilities of 5G networks are still insufficient, and new voice network architectures and enhanced interactive communication capabilities need to be provided to meet the service development needs of the evolution from the existing communication method mainly based on clear voice to a full-sensing, interactive, and immersive communication method, and enable the upgrade of personal consumption experience.

[0003] In related technical solutions, a terminal device is connected to a network device, and the network device controls the terminal device to discard data according to its own congestion situation. In the scenario of dual-connectivity (DC), this technical solution will cause the terminal device to discard too many data packets, thus affecting the service experience.

[0004] Therefore, how to avoid the terminal device from discarding too many data packets in the DC scenario has become a technical problem that urgently needs to be solved. Summary of the Invention

[0005] This application provides a communication method applied to a dual-connectivity (DC) scenario. In this scenario, this method can avoid discarding too many data packets and improve the service experience.

[0006] In a first aspect, a communication method applied to a dual-connectivity (DC) scenario is provided. This method can be executed by a first communication device, or alternatively, can be executed by a component (such as a chip or a circuit) of the first communication device. This application does not make any limitations in this regard. Specifically, the first communication device is a terminal device in a dual-connectivity (DC) scenario.

[0007] The method includes: receiving first indication information, where the first indication information is used to activate the function of a first entity in the first communication device or to deactivate the function of the first entity in the first communication device; according to the first indication information, when the function of the first entity is activated, discarding the data of the first entity according to a first timer; or according to the first indication information, when the function of the first entity is deactivated, discarding the data of the first entity according to a second timer.

[0008] The above-mentioned first entity is different from a second entity, where the second entity is used to manage or maintain the first timer and the second timer, and the first timer is different from the second timer.

[0009] The function of the above-mentioned first entity may refer to the data discarding function of the first entity. As an example, the function may refer to data discarding based on the importance of a protocol data unit set (PSI). PSI based discard means that the terminal device discards data according to the importance of the data. For video services, the importance of an I-frame is greater than that of a P-frame.

[0010] In the above technical solution, in the DC scenario, when only one network device is congested, the first communication device only needs to control the data discarding towards that network device, and other network devices are not affected. In this way, it is possible to avoid the first communication device discarding too much data and improve the service experience.

[0011] Combined with the first aspect, in some implementation manners of the first aspect, the first indication information further includes identification information of a first radio bearer (RB), the first RB corresponds to the first entity, the first RB corresponds to the second entity, and the first RB is any one of the following: a split RB, a duplicated RB, or a dual active protocol stack (DAPS) RB.

[0012] The above-mentioned first RB is a logical channel for transmitting service data. For a split RB, different data is transmitted between the first communication device and different network devices, and these data are protected by the same key for security. For a duplicated RB, the same data is transmitted between the first communication device and different network devices, and these data are protected by the same key for security. For a DAPS RB, different data is transmitted between the first communication device and different network devices, and these data are protected by different keys for security.

[0013] In combination with the first aspect, in certain implementations of the first aspect, when the function of the first entity is activated, the function of the third entity is in a deactivated state. The third entity is used to discard the data in the third entity according to the second timer. The third entity and the first entity correspond to different network devices in the DC scenario.

[0014] The above-mentioned first RB corresponds to the third entity and the second entity, that is, the first RB corresponds to the third entity, and the first RB corresponds to the second entity.

[0015] In combination with the first aspect, in certain implementations of the first aspect, the first entity is an RLC entity corresponding to the master node MN, and the third entity is an RLC entity corresponding to the secondary node SN; or the first entity is an RLC entity corresponding to the SN, and the third entity is an RLC entity corresponding to the MN.

[0016] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: receiving configuration information, where the configuration information is used to configure the function in the DC scenario, and the configuration information includes the duration of the first timer and the duration of the second timer.

[0017] In combination with the first aspect, in certain implementations of the first aspect, the configuration information further includes second indication information, and the second indication information is used to indicate the function in the DC scenario.

[0018] In combination with the first aspect, in certain implementations of the first aspect, receiving first indication information from the MN, where the first indication information is used to activate the above-mentioned function of the first entity in the first communication device; further including receiving third indication information from the SN, where the third indication information is used to activate the function of the third entity in the first communication device; discarding the data of the first entity, and / or the data of the second entity, and / or the data in the third entity according to the first timer.

[0019] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: sending a first report, where the first report is used to indicate the sequence number SN of the data discarded by the first communication device, and the discarded data includes at least one of the following data: the data discarded by the first entity, the data discarded by the second entity, or the data discarded by the third entity.

[0020] In combination with the first aspect, in certain implementations of the first aspect, the first indication information is further used to indicate the first entity.

[0021] In combination with the first aspect, in certain implementations of the first aspect, when the first timer expires, discard the data of the first entity.

[0022] In combination with the first aspect, in some implementations of the first aspect, when the second timer expires, discard the data of the first entity.

[0023] In combination with the first aspect, in some implementations of the first aspect, the first timer and the second timer correspond to a first RB.

[0024] In combination with the first aspect, in some implementations of the first aspect, the duration of the first timer is less than the duration of the second timer.

[0025] In a second aspect, a communication method applied to a dual-connectivity (DC) scenario is provided. This method can be executed by a second communication device, or alternatively, can be executed by components (such as chips or circuits) of the second communication device. This application does not make any limitations in this regard.

[0026] By way of example, the second communication device is a network device in a dual-connectivity (DC) scenario. In one example, the second communication device is a MN in a DC scenario. In another example, the second communication device is a SN in a DC scenario.

[0027] The method includes: determining first indication information; sending the first indication information, where the first indication information is used to activate the function of a first entity in a first communication device or to deactivate the function of the first entity. The first communication device is a terminal device in the DC scenario. When the function of the first entity is activated, the first entity is used to discard the data of the first entity according to a first timer. When the function of the first entity is deactivated, the first entity is used to discard the data of the first entity according to a second timer. The first entity is different from a second entity in the first communication device, and the second entity is used to manage the first timer and the second timer.

[0028] In combination with the second aspect, in some implementations of the second aspect, the first indication information further includes identification information of a first radio bearer (RB). The first RB corresponds to the first entity, the first RB corresponds to the second entity, and the first RB is any one of the following: a split RB, a duplicate RB, or a dual active protocol stack (DAPS) RB.

[0029] In combination with the second aspect, in some implementations of the second aspect, the method further includes: sending configuration information, where the configuration information is used to configure the function of the first communication device in the DC scenario. The configuration information includes the duration of the first timer and the duration of the second timer. The first timer and the second timer correspond to a first RB.

[0030] In combination with the second aspect, in some implementations of the second aspect, the configuration information further includes second indication information, which is used to indicate the function of the first communication device in the DC scenario.

[0031] In combination with the second aspect, in some implementations of the second aspect, the method further includes: receiving a first report, where the first report is used to indicate the sequence number SN of the data discarded by the first communication device, and the discarded data includes at least one of the following data: data discarded by the first entity, data discarded by the second entity, or data discarded by the third entity.

[0032] The above-mentioned third entity and the first entity correspond to different network devices in the DC scenario.

[0033] In combination with the second aspect, in some implementations of the second aspect, the method further includes: sending a second report, where the second report is used to indicate that the discarded data has been successfully received.

[0034] It should be understood that the second report includes a false ACK indication. At this time, according to the second report, the bottom of the receiving SN window of the third communication device skips the SN of the data that has been discarded by the first communication device. Otherwise, without the second report, the bottom of the receiving SN window in the third communication device will stay at the SN of the data that has been discarded by the first communication device, resulting in the inability to receive subsequent data in the third communication device and thus affecting the service experience.

[0035] In combination with the second aspect, in some implementations of the second aspect, the network state is a congestion state, and the first indication information is used to activate the function of the first entity in the first communication device.

[0036] In combination with the second aspect, in some implementations of the second aspect, the network state is a non-congestion state, and the first indication information is used to deactivate the function of the first entity in the first communication device.

[0037] In combination with the second aspect, in some implementations of the second aspect, the duration of the first timer is less than the duration of the second timer.

[0038] In combination with the second aspect, in some implementations of the second aspect, the first indication information is further used to indicate the first entity.

[0039] The technical effects of the method shown in the above second aspect and its possible designs can refer to the technical effects in the first aspect and its possible designs.

[0040] In a third aspect, a communication method applicable to a dual-connectivity (DC) scenario is provided. This method can be executed by a first communication device, or alternatively, by a component (such as a chip or a circuit) of the first communication device. This application does not make any limitations in this regard.

[0041] For example, the first communication device is a network device in a DC scenario. As an example, the first communication device is the central unit (CU) of the MN in a DC scenario. As another example, the first communication device is the CU of the SN in a DC scenario.

[0042] The method includes: determining first indication information; and sending the first indication information to a second communication device according to the network state information. The first indication information is used to activate the function of a first entity in a third communication device or to deactivate the function of the first entity in the third communication device. The second communication device is a network device in the DC scenario, and the third communication device is a terminal device in the DC scenario.

[0043] In the above technical solution, by interacting the network state information between different network devices in a DC scenario, the entities in the third communication device are centrally controlled to perform data discarding, avoiding excessive data discarding by the third communication device in the DC scenario and improving the service experience.

[0044] In combination with the third aspect, in some implementation manners of the third aspect, network state information from the second communication device and / or a fourth communication device is received, and the first indication information is determined according to the network state information of the second communication device and / or the fourth communication device.

[0045] The above fourth communication device is a network device in the DC scenario. For example, the DU of the network device.

[0046] In combination with the third aspect, in some implementation manners of the third aspect, the method further includes: sending first control information to the second communication device, where the first control information is used to control the second communication device to report the network state information of the second communication device; and / or sending second control information to the fourth communication device, where the second control information is used to control the fourth communication device to report the network state information of the fourth communication device.

[0047] In combination with the third aspect, in some implementation manners of the third aspect, the network state information is congestion state information, and the first indication information is used to activate the function of the first entity.

[0048] In combination with the third aspect, in some implementation manners of the third aspect, the network state information is non-congestion state information, and the first indication information is used to deactivate the function of the first entity.

[0049] In combination with the third aspect, in some implementation manners of the third aspect, the first indication information further includes identification information of a first radio bearer (RB), the first RB corresponds to the first entity, and the first RB is any one of the following: a split RB, a duplicate RB, or a dual active protocol stack (DAPS) RB.

[0050] In combination with the third aspect, in some implementation manners of the third aspect, the method further includes: receiving a first report, where the first report is used to indicate a sequence number (SN) of data discarded by the third communication device.

[0051] In combination with the third aspect, in some implementation manners of the third aspect, sending a second report, where the second report is used to indicate that the discarded data is successfully received.

[0052] Fourth aspect, a communication device is provided, and the device is used to execute the method provided in the first aspect above. Specifically, the communication device may include units and / or modules for executing the method provided in any one of the implementation manners of the first aspect above, such as a processing unit and an obtaining unit.

[0053] In one implementation manner, the transceiver unit may be a transceiver, or an input / output interface; the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0054] In another implementation manner, the transceiver unit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit, etc. on the chip, chip system, or circuit; the processing unit may be at least one processor, a processing circuit, or a logic circuit, etc.

[0055] Fifth aspect, a communication device is provided, and the device is used to execute the method provided in the second aspect above. Specifically, the communication device may include units and / or modules for executing the method provided in the second aspect above, such as a processing unit and an obtaining unit.

[0056] In one implementation manner, the transceiver unit may be a transceiver, or an input / output interface; the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0057] In another implementation manner, the transceiver unit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit, etc. on the chip, chip system, or circuit; the processing unit may be at least one processor, a processing circuit, or a logic circuit, etc.

[0058] Sixth aspect, a communication device is provided, and the device is used to execute the method provided in the above third aspect. Specifically, the communication device may include units and / or modules for executing the method provided in the third aspect, such as a processing unit and an acquisition unit.

[0059] In one implementation, the transceiver unit may be a transceiver, or an input / output interface; the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0060] In another implementation, the transceiver unit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc. on the chip, chip system or circuit; the processing unit may be at least one processor, a processing circuit or a logic circuit, etc.

[0061] Seventh aspect, the present application provides a processor for executing the method provided in any one of the implementations of the above first aspect, second aspect and third aspect.

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

[0063] Eighth aspect, a computer-readable storage medium is provided, and the computer-readable storage medium stores program codes for a device to execute, and the program codes include the method provided in any one of the implementations of the above first aspect, second aspect and third aspect.

[0064] Ninth aspect, a computer program product containing instructions is provided. When the computer program product runs on a computer, it causes the computer to execute the method provided in any one of the implementations of the above first aspect, second aspect and third aspect.

[0065] Tenth aspect, a chip is provided. The chip includes a processor and a communication interface. The processor reads instructions stored on a memory through the communication interface and executes the method provided in any one of the implementations of the above first aspect, second aspect and third aspect.

[0066] Optionally, as an implementation, the chip further includes a memory. A computer program or instructions are stored in the memory, and the processor is used to execute the computer program or instructions stored on the memory. When the computer program or instructions are executed, the processor is used to execute the method provided in any one of the implementations of the above first aspect, second aspect and third aspect.

[0067] In the eleventh aspect, a communication system is provided, including the communication device described in the fourth aspect and / or the communication device described in the fifth aspect, or including the communication device described in the fourth aspect and / or the communication device described in the sixth aspect. Description of the Drawings

[0068] Figure 1 FIG. is a schematic diagram of a system architecture provided by an embodiment of the present application.

[0069] Figure 2 FIG. is a schematic block diagram of a terminal device (e.g., UE) supporting EN-DC.

[0070] Figure 3 FIG. is a schematic block diagram of a terminal device (e.g., UE) supporting MR-DC.

[0071] Figure 4 FIG. is a schematic block diagram of an MN and an SN in an MR-DC scenario.

[0072] Figure 5 FIG. is a schematic flowchart of a communication method applied to a dual-connection DC scenario provided by an embodiment of the present application.

[0073] Figure 6 FIG. is a schematic flowchart of another communication method applied to a dual-connection DC scenario provided by an embodiment of the present application.

[0074] Figure 7 FIG. is a schematic flowchart of another communication method applied to a dual-connection DC scenario provided by an embodiment of the present application.

[0075] Figure 8 FIG. is a schematic diagram of an enhanced format of PSI-based activation or deactivation provided by an embodiment of the present application.

[0076] Figure 9 FIG. is a schematic flowchart of another communication method applied to a dual-connection DC scenario provided by an embodiment of the present application.

[0077] Figure 10 FIG. is a schematic diagram of a format of PSI-based activation or deactivation provided by an embodiment of the present application.

[0078] Figure 11 FIG. is a schematic block diagram of a communication device provided by an embodiment of the present application.

[0079] Figure 12 FIG. is a schematic diagram of another communication device provided by an embodiment of the present application.

[0080] Figure 13 FIG. is a schematic diagram of a chip system provided by an embodiment of the present application. Specific Embodiments

[0081] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0082] First, in the present application, "for indicating" may include directly indicating and indirectly indicating. When describing that a certain indication information is for indicating A, it may include that the indication information directly indicates A or indirectly indicates A, and it does not necessarily mean that A is carried in the indication information.

[0083] The information indicated by the indication information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated. For example, but not limited to, it can directly indicate the information to be indicated, such as the information to be indicated itself or the index of the information to be indicated, etc. It can also indirectly indicate the information to be indicated by indicating other information, where there is an association relationship between the other information and the information to be indicated. It can also only indicate a part of the information to be indicated, while the other parts of the information to be indicated are known or pre-agreed. For example, it can also achieve the indication of specific information by relying on the arrangement order of each piece of information pre-agreed (such as protocol regulations), so as to reduce the indication overhead to a certain extent. At the same time, it can also identify the common parts of each piece of information and uniformly indicate them to reduce the indication overhead caused by separately indicating the same information.

[0084] Second, in the present application, "at least one" shown means one or more, and "a plurality" means two or more. In addition, in the embodiments of the present application, "first", "second" and various numerical numbers (such as "#1", "#2", etc.) are only for the convenience of description and do not limit the scope of the embodiments of the present application. The size of the serial numbers of the following processes does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. It should be understood that the objects described in this way can be interchanged under appropriate circumstances so as to be able to describe the solutions other than the embodiments of the present application. In addition, in the embodiments of the present application, words such as "S210" are only marks made for the convenience of description and do not limit the order of execution steps.

[0085] Third, in the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly speaking, using words such as "exemplary" or "for example" aims to present relevant concepts in a specific way.

[0086] Fourth, the "storage" involved in the embodiments of the present application may refer to storage in one or more memories. The one or more memories may be separately provided or integrated in an encoder, a decoder, a processor, or a communication device. The one or more memories may also have a part separately provided and a part integrated in a decoder, a processor, or a communication device. The type of the memory may be any form of storage medium, and the present application does not limit this.

[0087] Fifth, in the implementation of the present application, the "protocol" may refer to a standard protocol in the communication field. For example, it may include the NR protocol and related protocols applied to future communication systems. The present application does not limit this.

[0088] Sixth, in the embodiments of the present application, the terms "of", "corresponding", "corresponding", and "associated" may sometimes be used interchangeably. It should be noted that when their differences are not emphasized, the meanings they express are the same.

[0089] Seventh, in the embodiments of the present application, the phrases "in the case of", "when", and "if" may sometimes be used interchangeably. It should be noted that when their differences are not emphasized, the meanings they express are the same.

[0090] Eighth, the term "and / or" in this document is merely a description of the association relationship between associated objects, indicating that there can be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally represents an "or" relationship between the preceding and following associated objects.

[0091] For ease of description, the system architecture of the embodiments of the present application will be introduced in detail below.

[0092] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5th Generation (5G) mobile communication system or New Radio (NR). Among them, the 5G mobile communication system can be Non-Standalone (NSA) or Standalone (SA).

[0093] The technical solution provided by this application can also be applied to machine type communication (MTC), long term evolution - machine (LTE - M), device - to - device (D2D) network, machine - to - machine (M2M) network, internet of things (IoT) network or other networks. Among them, the IoT network can include, for example, the vehicle - to - everything (V2X) network. Among them, the communication methods in the V2X network system are collectively referred to as vehicle - to - X (V2X, where X can represent anything). For example, the V2X can include: vehicle - to - vehicle (V2V) communication, vehicle - to - infrastructure (V2I) communication, vehicle - to - pedestrian (V2P) communication, or vehicle - to - network (V2N) communication, etc.

[0094] The technical solution provided by this application can also be applied to future communication systems, such as the 6th Generation (6G) mobile communication system, etc. This application does not limit this.

[0095] In the embodiments of this application, the terminal device can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile platform, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.

[0096] The terminal devices in the embodiments of the present application include various devices with wireless communication functions, which can be used to connect people, objects, machines, etc. The terminal devices can be widely applied to various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer (P2P), M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and other scenarios. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. The terminal device can be a user equipment (UE), terminal, fixed device, mobile station device or mobile device, subscriber unit, handheld device, vehicle-mounted device, wearable device, cellular phone, smart phone, session initialization protocol (SIP) phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver function, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (such as drones, helicopters, multi-rotor helicopters, quadcopters, or airplanes, etc.), ship, remote control device, smart home device, industrial device, or a device built into the above devices (such as a communication module, modem or chip in the above devices), or other processing devices connected to a wireless modem. For the convenience of description, the terminal device will be described below by taking the terminal or UE as an example.

[0097] Among them, a wearable device, also known as a wearable intelligent device, is a general term for devices developed by applying wearable technology to the intelligent design of daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is directly worn on the body or integrated into the user's clothing or accessories. A wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with complete functions and large sizes that can realize complete or partial functions without relying on a smartphone, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones, such as various smart bracelets and smart jewelry for physical sign monitoring.

[0098] In addition, the terminal device can also be a terminal device in an Internet of Things (IoT) system. The IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-object interconnection. IoT technology can achieve massive connections, deep coverage, and low power consumption of terminals through, for example, narrowband (NB) technology.

[0099] In the embodiments of the present application, the terminal device can also be a vehicle or a whole vehicle, and communication can be realized through a vehicle network, or it can be a component located inside the vehicle (for example, placed inside the vehicle or installed inside the vehicle), that is, an in-vehicle terminal device, an in-vehicle module, or an on-board unit (OBU).

[0100] In addition, the terminal device can also include sensors such as intelligent printers, train detectors, and gas stations. Its main functions include collecting data (for some terminal devices), receiving control information and downlink data from network devices, and transmitting electromagnetic waves to transmit uplink data to network devices.

[0101] In the present application, the device for realizing the functions of the terminal device can be the terminal device; it can also be a device capable of supporting the terminal device to realize such functions, such as a chip system, a hardware circuit, a software module, or a combination of a hardware circuit and a software module. This device can be installed in the terminal device or can be used in matching with the terminal device. In the technical solutions provided in the present disclosure, taking the device for realizing the functions of the terminal device as the terminal device and the terminal device as the UE as an example, the technical solutions provided in the present disclosure are described.

[0102] The network device in the embodiments of the present application is an entity on the network side for transmitting or receiving signals, which can be used to mutually convert received airframes and Internet Protocol (IP) packets, and act as a router between a terminal device and the rest of the access network, where the rest of the access network may include an IP network, etc.

[0103] The network device in the embodiments of the present application can be a device for communicating with a terminal device. This network device can also be referred to as an access network device or a radio access network device. For example, the network device can be a base station. The network device in the embodiments of the present application can refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station can generally cover various names below, or be replaced with the following names, such as: Node B, evolved Node B (eNB), next generation Node B (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station, secondary station, multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. A base station can also refer to a communication module, a modem, or a chip disposed in the aforementioned device or apparatus. A base station can also be a mobile switching center and a device that undertakes the function of a base station in D2D, V2X, M2M communications, a network-side device in a 6G network, a device that undertakes the function of a base station in a future communication system, etc. A base station can support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technologies and specific device forms adopted by the network device.

[0104] A base station can be fixed or mobile. For example, a helicopter or a drone can be configured to act as a mobile base station, and one or more cells can move according to the position of the mobile base station. In other examples, a helicopter or a drone can be configured to be used as a device for communicating with another base station.

[0105] In some deployments, the gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC), medium access control (MAC), and physical (PHY) layers. The AAU implements some physical layer processing functions, radio frequency processing, and related functions of active antennas. Since the information in the RRC layer will ultimately become the information in the PHY layer, or is transformed from the information in the PHY layer, therefore, in this architecture, high-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or sent by the DU and the CU. It can be understood that the network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU can be classified as a network device in the radio access network (RAN), or the CU can be classified as a network device in the core network (CN), and this application does not make any limitations on this.

[0106] The above-mentioned network device provides services for a cell, and the terminal device communicates with the cell through the transmission resources allocated by the network device (for example, frequency domain resources, or in other words, spectrum resources). This cell may belong to a macro base station (such as a macro eNB or a macro gNB, etc.), or may belong to a base station corresponding to a small cell. Here, the small cell may include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage range and low transmission power, and are suitable for providing high-rate data transmission services.

[0107] In this application, the device for implementing the functions of an access network device may be the access network device; it may also be a device capable of supporting the access network device to implement such functions, such as a chip system, a hardware circuit, a software module, or a combination of a hardware circuit and a software module. This device may be installed in the access network device or may be used in combination with the access network device. In the technical solution provided in this application, taking the device for implementing the functions of an access network device as the access network device and the access network device as a base station as an example, the technical solution provided in this application is described.

[0108] In an embodiment of this application, a network device may include one or more cells, and each cell may include one or more transmission reception points (TRPs) or transmission points (TPs).

[0109] The function mentioned in the embodiment of this application may refer to a data discarding function. For example, the above function may refer to data discarding based on the importance of a protocol data unit set (PSI). PSI-based discard means that the terminal device discards data according to the importance of the data. For video services, the importance of I-frames is greater than that of P-frames.

[0110] In an embodiment of this application, the management timer includes starting or restarting the timer and determining whether the timer times out.

[0111] In an embodiment of this application, data is discarded according to the timer. It should be understood that data is discarded when the timer times out.

[0112] The network device and the terminal device may be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they may also be deployed on water; they may also be deployed on airplanes, balloons, and satellites in the air. In the embodiment of this application, the scenarios where the network device and the terminal device are located are not limited. In addition, the terminal device and the network device may be hardware devices, or software functions running on dedicated hardware or software functions running on general hardware. For example, they are virtualized functions instantiated on a platform (such as a cloud platform), or entities including dedicated or general hardware devices and software functions. The specific forms of the terminal device and the network device in this application are not limited.

[0113] Figure 1 It is a schematic diagram of a communication system 100 applicable to the embodiment of this application. As Figure 1 shown, the communication system 100 may include at least one terminal device, such as Figure 1 the terminal device 110 shown; the communication system 100 may also include at least two network devices, such asFigure 1 The network devices 120 and 130 shown. Among them, the terminal device 110 can communicate with the network device 120 and the network device 130 simultaneously. As an example, the terminal device 110 and the network device 120, and the terminal device 110 and the network device 130 can communicate through a wireless link. Each communication device, such as the terminal device 110, the network device 120, or the network device 130, can be configured with multiple antennas. For each communication device in this communication system, the multiple antennas configured can include at least one transmitting antenna for transmitting signals and at least one receiving antenna for receiving signals. Therefore, between each communication device in this communication system, between the terminal device 110 and the network device 120, and between the terminal device 110 and the network device 130, communication can be carried out through multi-antenna technology.

[0114] It should be understood that Figure 1 This is only a simplified schematic diagram shown for ease of understanding. Other network devices or other terminal devices may also be included in this communication system, Figure 1 which are not drawn in the figure.

[0115] It should also be understood that the terminal device 110 communicating with the network device 120 and the network device 130 simultaneously can also be referred to as dual-connectivity (DC) of the terminal device. Among them, one network device communicating with the terminal device 110 can be called the master node (MN), and the other network device communicating with the terminal device 110 can be called the secondary node (SN). As an example, assume that the network device 120 is the MN and the network device 130 is the SN.

[0116] As an example, according to the different types of MN and SN, the DC scenario can be further divided into: EN-DC, MR-DC. The following will describe EN-DC and MR-DC in detail respectively.

[0117] 1. EN-DC

[0118] EN-DC refers to LTE and 5G dual connectivity. The letter E represents evolved universal terrestrial radio access new radio (E-UTRA), which is the air interface in the LTE cellular network. The letter N represents new radio (NR), which is the global standard for the unified and more powerful 5G radio air interface. That is, a terminal device supporting EN-DC can be simultaneously connected to the LTE master node eNB (MN-eNB) and the 5G-NR secondary node gNB (SN-gNB). EN-DC is a technology that can introduce 5G services and data rates in a 4G-dominated network.

[0119] For example, Figure 2 is a schematic block diagram of a terminal device (e.g., UE) supporting EN-DC. As Figure 2 shown, the bearers in the network can be divided into three categories: master cell group (MCG) bearers, secondary cell group (SCG) bearers, and Split bearers. In EN-DC, MCG bearers use the PDCP, RLC, and MAC corresponding to the master node. For EN-DC, 4G (E-UTRA) is the master node. Therefore, MCG bearers use E-UTRA PDCP, E-UTRA RLC, and E-UTRA MAC. SCG bearers use the PDCP, RLC, and MAC corresponding to the secondary node. For EN-DC, 5G-NR (gNB) is the secondary node. Therefore, SCG bearers use NR PDCP, NR RLC, and NR MAC. Split bearers split the air interface data into two bearers. In PDCP, NR PDCP is used. In RLC, E-UTRA RLC is used to carry the air interface data of the MN, and NR RLC is used to carry the air interface data of the SN. In MAC, E-UTRA MAC is used to carry the air interface data of the MN, and NR MAC is used to carry the air interface data of the SN.

[0120] It should be understood that the LTE master node eNB (MN-eNB) uses multiple different frequency points to form a network of multi-layer cells, and all these cells can serve as control plane anchor points. Therefore, these 4G cells are collectively called MCG, and the radio data bearers established thereon are called MCG bearers. Correspondingly, multiple 5G cells form SCG, and the radio data bearers established thereon are called SCG bearers. And Split bearers refer to splitting the air interface data into two bearers.

[0121] 2. MR-DC

[0122] MR-DC refers to 5G and 5G dual connectivity. A terminal device supporting MR-DC can be simultaneously connected to a 5G-NR master node gNB (MN-gNB) and a 5G-NR secondary node gNB (SN-gNB).

[0123] For example, Figure 3 is a schematic block diagram of a terminal device (e.g., UE) supporting MR-DC. As Figure 3 shown, the bearers in the network can be divided into three categories: master cell group (MCG) bearers, secondary cell group (SCG) bearers, and Split bearers. In EN-DC, MCG bearers use the PDCP, RLC, and MAC corresponding to the master node. For MR-DC, 5G-NR (gNB) is the master node. Therefore, MCG bearers use NR PDCP, MN RLC, and MN MAC. SCG bearers use the PDCP, RLC, and MAC corresponding to the secondary node. For EN-DC, 5G-NR (gNB) is the secondary node. Therefore, SCG bearers use NR PDCP, SN RLC, and SN MAC. Split bearers split the air interface data into two bearers. NR PDCP is used at the PDCP layer. At the RLC layer, MN RLC is used to carry the air interface data of MN, and SN RLC is used to carry the air interface data of SN. At the MAC layer, MN MAC is used to carry the air interface data of MN, and SN MAC is used to carry the air interface data of SN.

[0124] For example, Figure 4 is a schematic block diagram of the MN and SN in the MR-DC scenario. As Figure 4 shown, taking the downlink data as an example, assuming that the MN is the anchor point, after receiving the data from the core network, for Split bearers, the downlink data diverges from the PDCP layer and is respectively sent to the RLC / MAC of the MN and SN for processing. For example, on the one hand, the MN can send the downlink data to the terminal device through the MN RLC and MN MAC layers in the MN, and on the other hand, the MN can also send the downlink data to the SN RLC in the SN, and the SN RLC and MN MAC layers in the SN send the downlink data to the terminal device.

[0125] In the future, extended reality (XR) will become the main service carried by communication networks. Not only will the clarity of XR be upgraded from 8K to 16K / 32K or even higher, but the augmented reality (AR) service scenarios for industrial applications will also evolve from single-terminal communication to multi-XR collaborative interaction and develop rapidly around 2025. By then, due to the influence of service traffic and service characteristics, XR services will pose higher requirements for SLA guarantees such as network capacity, latency, and bandwidth. At the same time, there is still significant room for development in basic communication services. Multi-party video calls, virtual meetings, etc., represented by remote work, will become the norm. In terms of service forms, the current meeting mode of fixed access + video + call will be transformed into multi-party remote collaboration of mobile access + rich media + real-time interaction. For example, enterprise employees can access the enterprise office environment at any time with virtual avatars and communicate efficiently with colleagues. Therefore, the current capabilities of 5G networks are still insufficient, and new voice network architectures and enhanced interactive communication capabilities need to be provided to meet the service development needs of the evolution from the existing communication mode mainly based on clear voice to a full-sensing, interactive, and immersive communication mode, enabling the upgrade of personal consumption experiences.

[0126] PSI based discard (protocol data unit set importance based discard) refers to the terminal device discarding data according to the importance of the data. In related technical solutions, the terminal device is connected to a network device, and the network device sends configuration information to the terminal device. This configuration information is used to configure a discard timer with a short value and a discard timer with a long value. The terminal device receives the activation command or deactivation command of PSI based discard from the network device. According to the activation command, it determines to start the corresponding discard timer with a short value, or according to the deactivation command, starts the corresponding discard timer with a long value. After the timer times out, the terminal device discards the corresponding received data in the PDCP entity.

[0127] In the above technical solution, a terminal device is connected to a network device, and the network device sends an activation or deactivation command for PSI based discard to the terminal device according to its own congestion situation. However, in the DC scenario, the network device cannot know the congestion situations of other network devices. If it sends an activation command for PSI based discard to the terminal device only based on its own congestion situation, it will cause the terminal device to discard too many data packets.

[0128] In view of this, an embodiment of the present application provides a communication method, which can avoid the terminal device from discarding too many data packets in the DC scenario.

[0129] The following combines Figure 5 , and details a communication method provided by an embodiment of the present application. It should be understood that the specific structure of the execution subject of the method provided by the embodiment of the present application is not particularly limited by the embodiments shown below. As long as it can communicate according to the method provided by the embodiment of the present application by running a program recorded with the code of the method provided by the embodiment of the present application, for example, the execution subject of the method provided by the embodiment of the present application can be a receiving device or a sending device, or a functional module in the receiving device or the sending device that can call and execute the program.

[0130] It should be understood that Figure 5 uses the interaction between the first communication device, the second communication device, and the third communication device as an example to detail the communication method provided by the embodiment of the present application. The first communication device can be a terminal device in the DC scenario, and the second communication device and the third communication device can be different network devices in the DC scenario. For example, the second communication device is an MN in the DC scenario, and the third communication device is an SN in the DC scenario. Another example is that the second communication device is an SN in the DC scenario, and the third communication device is an MN in the DC scenario.

[0131] Figure 5 is a schematic flowchart of a communication method applied to the dual-connection DC scenario provided by the embodiment of the present application. As Figure 5 shown, the method may include steps 510-530, and the following details steps 510-530 respectively.

[0132] Step 510: The second communication device sends first indication information to the first communication device, and the first indication information is used to activate the function of the first entity in the first communication device or to deactivate the function of the first entity in the first communication device.

[0133] In an embodiment of the present application, the second communication device may send first indication information to the first communication device, where the first indication information is used to activate the function of the first entity in the first communication device or to deactivate the function of the first entity in the first communication device.

[0134] It should be understood that the entity in the first communication device may be a protocol layer of the first communication device, and different entities are used to manage different data processing functions.

[0135] It should be understood that the above function may refer to a data discarding function. For example, the above function may refer to PSI based discard. The data discarding function of the first entity will be described in detail below in combination with step 520, and will not be elaborated here for the time being.

[0136] As an example, the second communication device may send the above first indication information to the first communication device based on the network state of the second communication device. For example, if the network state of the second communication device is a congested state, the second communication device may send first indication information to the first communication device, where the first indication information is used to activate the function of the first entity in the first communication device. Another example is that if the network state of the second communication device is a non-congested state (i.e., a normal state), the second communication device may send first indication information to the first communication device, where the first indication information is used to deactivate the function of the first entity in the first communication device.

[0137] Step 520: When the function of the first entity in the first communication device is activated according to the first indication information, the first communication device discards the data in the first entity according to the first timer.

[0138] It should be understood that the first timer is used to control the discarding of data with a low level of importance when the above function is activated.

[0139] In an embodiment of the present application, after the first communication device receives the first indication information sent by the second communication device, if the first indication information indicates to activate the function of the first entity in the first communication device, the first communication device activates the above function of the first entity.

[0140] As an example, the first entity is an RLC entity (for example, the first RLC entity) in the first communication device, and the first RLC entity corresponds to the second communication device.

[0141] It should be understood that the first RLC entity in the above first communication device refers to the RLC entity in the RLC layer that receives the data sent by the second communication device or sends data to the second communication device. For example, assuming that the second communication device is an MN and the first communication device is a terminal device, taking the above EN-DC scenario as an example, the first RLC entity is Figure 2E-UTRA RLC in; taking the above MR-DC scenario as an example, the first RLC entity is Figure 3 the MN RLC in.

[0142] For example, when the above functions of the first entity are activated, the data in the first entity is discarded according to the first timer. Specifically, when the first timer expires, the first communication device discards the data in the first entity, for example, data of low importance. By way of example, the importance of a video P-frame is lower than that of a video I-frame. When both the video P-frame and the video I-frame exist, the video P-frame is preferentially discarded.

[0143] The expiration of the above first timer can be understood as that the running time of the first timer has reached the first duration.

[0144] Step 530: The first communication device discards the data in the first entity according to the second timer when the function of the first entity in the first communication device is deactivated according to the first indication information.

[0145] In the embodiments of the present application, after the first communication device receives the first indication information sent by the second communication device, if the first indication information indicates deactivating the function of the first entity in the first communication device, the first communication device deactivates the above function of the first entity. For example, in one implementation, when the above function of the first entity is deactivated, the first communication device discards the data in the first entity according to the second timer.

[0146] It should be understood that the second timer is different from the first timer. The second timer is used to control the discarding of the data in the first entity when the above function of the first entity is deactivated, including data of low importance and data of high importance. For example, when the second timer expires, the first communication device discards the data in the first entity, including data of low importance and data of high importance. By way of example, when both the video P-frame and the video I-frame exist, the video P-frame and the video I-frame are discarded.

[0147] The expiration of the above second timer can be understood as that the running time of the second timer has reached the second duration. Wherein, the second duration is greater than the above first duration, that is, the duration of the first timer is less than the duration of the second timer.

[0148] The first entity in the above first communication device is different from the second entity. The second entity is an entity in the first communication device, and the second entity is used to manage or maintain the first timer and the second timer. Specifically, the data processing of the first entity is after the data processing of the second entity. By way of example, the second entity is the PDCP entity in the first communication device, and the first entity is the RLC entity in the first communication device.

[0149] It should be understood that the management timer includes starting or restarting the timer and determining whether the timer times out.

[0150] It should be understood that when the second entity in the first communication device receives data from an upper layer (e.g., IP layer or transport layer) in the first communication device, it starts or restarts the first timer or the second timer.

[0151] In the embodiments of the present application, the above first indication information further includes the identification information of the first RB, and the first RB corresponds to the above first entity and the second.

[0152] It should be understood that the data in the above first entity and second entity is transmitted in the manner of the first RB.

[0153] The above first RB is any one of the following RBs: split RB, duplicated RB, or dual active protocol stack (DAPS) RB. Among them, the first RB is a logical channel for transmitting service data. For the split RB, different data is transmitted between a terminal device (e.g., UE) and different network devices, and these data are protected by the same key. For the duplicated RB, the same data is transmitted between a terminal device (e.g., UE) and different network devices, and these data are protected by the same key. For the DAPS RB, different data is transmitted between a terminal device (e.g., UE) and different network devices, and these data are protected by different keys.

[0154] In a possible implementation, the format of the first indication information may refer to Figure 8 the MAC CE format shown below, and the MAC CE format in Figure 8 will be described in detail below and will not be elaborated here for the time being.

[0155] Optionally, in some embodiments, the third communication device further sends third indication information to the first communication device, and the third indication information is used to indicate activating the above function of the third entity in the first communication device or deactivating the above function of the third entity in the first communication device.

[0156] It should be understood that the third entity is another entity in the first communication device, and the third entity is different from the first entity. As an example, the third entity is the RLC entity (e.g., the second RLC entity) in the first communication device, and the second RLC entity corresponds to the third communication device.

[0157] It should be understood that the second RLC entity in the above-mentioned first communication device refers to the RLC entity in the RLC layer that receives data sent by the third communication device or sends data to the third communication device. For example, assuming that the third communication device is the SN and the first communication device is the terminal device, taking the above-mentioned EN-DC scenario as an example, the second RLC entity is Figure 2 the NR RLC in; taking the above-mentioned MR-DC scenario as an example, the second RLC entity is Figure 3 the SN RLC in.

[0158] The third entity in the above-mentioned first communication device is different from the first entity, and they respectively correspond to different network devices in the DC scenario. In one implementation, the first entity is the entity corresponding to the MN in the DC scenario, and the third entity is the entity corresponding to the SN in the DC scenario. For example, the first entity is the RLC entity corresponding to the MN, and the third entity is the RLC entity corresponding to the SN. In another possible implementation, the first entity is the RLC entity corresponding to the SN, and the third entity is the RLC entity corresponding to the MN.

[0159] It should be understood that taking the EN-DC scenario as an example, the RLC entity corresponding to the MN is the E-UTRA RLC, and the RLC entity corresponding to the SN is the NR RLC. Taking the MR-DC scenario as an example, both the RLC entity corresponding to the MN and the RLC entity corresponding to the SN are the NR RLC.

[0160] As an example, the third communication device may send the above-mentioned third indication information to the first communication device based on the network state of the third communication device. For example, if the network state of the third communication device is a congestion state, the third communication device may send the third indication information to the first communication device, and the third indication information is used to activate the function of the third entity in the first communication device. Another example is that if the network state of the third communication device is a non-congestion state (i.e., the normal state), the third communication device may send the third indication information to the first communication device, and the third indication information is used to deactivate the function of the third entity in the first communication device.

[0161] Illustrated by way of example, the function of the above-mentioned third entity may refer to the data discarding function of the third entity. Specifically, when the above-mentioned function of the third entity is activated, data in the third entity (such as low-importance data) is discarded according to the first timer. When the above-mentioned function of the third entity is deactivated, data in the third entity (such as low-importance data) is discarded according to the second timer.

[0162] An example is that when the first communication device receives the above-mentioned first indication information (the first indication information indicates activating the function of the first entity in the first communication device) and the third indication information (the third indication information indicates activating the function of the third entity in the first communication device), the first communication device discards the data of the second entity (such as low-importance data) according to the first timer.

[0163] Another example is that when the first communication device receives the above-mentioned first indication information (the first indication information indicates activating the function of the first entity in the first communication device) and the third indication information (the third indication information indicates deactivating the function of the third entity in the first communication device), the first communication device discards the data of the first entity (such as low-importance data) according to the first timer, discards the data of the third entity (such as high-importance data and low-importance data) according to the second timer, and discards the data of the second entity (including low-importance data and high-importance data) according to the second timer.

[0164] Another example is that when the first communication device receives the above-mentioned first indication information (the first indication information indicates deactivating the function of the first entity in the first communication device) and the third indication information (the third indication information indicates activating the function of the third entity in the first communication device), the first communication device discards the data of the first entity (such as high-importance data and low-importance data) according to the second timer, discards the data of the third entity (such as low-importance data) according to the first timer, and discards the data of the second entity (including low-importance data and high-importance data) according to the second timer.

[0165] Another example is that when the first communication device only receives the above-mentioned third indication information (the third indication information indicates activating the function of the third entity in the first communication device) or the above-mentioned first indication information (the first indication information indicates activating the function of the first entity in the first communication device), the first communication device discards the data of the second entity (including low-importance data and high-importance data) according to the second timer.

[0166] Another example is that when the first communication device receives the above-mentioned first indication information (the first indication information indicates deactivating the function of the first entity in the first communication device) and the third indication information (the third indication information indicates deactivating the function of the third entity in the first communication device), the first communication device discards the data of the second entity (including low-importance data and high-importance data) according to the second timer.

[0167] Another example is that when the first communication device only receives the above-mentioned first indication information (the first indication information indicates deactivating the function of the first entity in the first communication device), the first communication device discards the data of the first entity according to the second timer.

[0168] In another example, when the first communication device only receives the above-mentioned third indication information (the third indication information indicates deactivating the function of the third entity in the first communication device), the first communication device discards the data of the third entity according to the second timer.

[0169] It should be understood that the data discarded in the first entity, the data discarded in the second entity, and the data discarded in the third entity may be the same or different, and the embodiments of the present application do not make specific limitations on this.

[0170] Optionally, before step 510, the second communication device sends configuration information to the first communication device, and the configuration information is used to configure the above functions of the first communication device in the DC scenario. Specifically, the indication information may include the duration of the above-mentioned first timer (for example, the first duration) and the duration of the second timer (for example, the second duration).

[0171] Optionally, the above configuration information may further include second indication information, and the second indication information is used to indicate the above functions of the first communication device in the DC scenario.

[0172] Optionally, in some embodiments, the first communication device may further send a first report (for example, the first PDCP report) to the second communication device, and the first report is used to indicate the sequence number SN of the data discarded by the first communication device. The discarded data includes the data discarded by the entity in the first communication device, and the entity may be at least one of the following entities: the first entity, the second entity, and the third entity.

[0173] For example, in the case where the control anchor point (which may also be referred to as the RB termination point) is switched from the second communication device to the third communication device, the second communication device may further send a second report (for example, the second PDCP report) to the third communication device, and the second report is used to indicate that the data discarded by the first communication device is successfully received. Among them, the data discarded by the first communication device in the second report is determined by the first report. At this time, according to the second report, the third communication device skips the SN of the data that has been discarded by the first communication device at the bottom of the received SN window. Otherwise, without the second report, the bottom of the received SN window in the third communication device will stay at the SN of the data that has been discarded by the first communication device, resulting in the inability to receive subsequent data in the third communication device and further affecting the service experience.

[0174] The above-mentioned control anchor point refers to which station the PDCP entity is in, and that station is the control anchor point.

[0175] It should be understood that the second report includes a false ACK indication, that is, the data indicated as discarded by the first communication device in the first report is indicated as successfully received in the second report (for example, successfully received by the second communication device).

[0176] In the above technical solution, in the DC scenario, when only one network device is congested, the first communication device only needs to control the data discarding to that network device, and other network devices are not affected. In this way, the first communication device can avoid discarding too much data and improve the service experience.

[0177] Figure 6 It is a schematic flowchart of a communication method applied to a dual-connection DC scenario provided by an embodiment of the present application. As Figure 6 shown, the method may include steps 610-650, and the steps 610-650 will be described in detail below.

[0178] It should be understood that Figure 6 the interaction between the first communication device, the second communication device, the third communication device, the fourth communication device, and the fifth communication device is taken as an example to detail the communication method provided by the embodiment of the present application. The first communication device and the fifth communication device may be logical units of different network devices in the DC scenario (for example, CUs of different network devices), and the second communication device and the fourth communication device may be logical units of different network devices in the DC scenario (for example, DUs of different network devices). The third communication device is a terminal device in the DC scenario.

[0179] Step 610: The first communication device determines first indication information, where the first indication information is used to activate the function of the first entity in the third communication device or to deactivate the function of the first entity in the third communication device.

[0180] In the embodiment of the present application, the first communication device may determine the first indication information. In one implementation, the first communication device may determine the above first indication information according to the network status information of the second communication device and / or the fourth communication device, where the first indication information is used to activate the function of the first entity in the first communication device or to deactivate the function of the first entity in the first communication device.

[0181] In one implementation, the first communication device may send first control information to the second communication device, where the first control information is used to control the second communication device to report the network status information of the second communication device. After receiving the first control information, the second communication device reports the network status information of the second communication device to the first communication device. Among them, the network status of the second communication device includes a congestion status or a non-congestion status (that is, a normal status).

[0182] In another implementation, the first communication device may also send second control information to the fourth communication device through the fifth communication device. The second control information is used to control the fourth communication device to report the network status information of the fourth communication device. After receiving the second control information, the fourth communication device reports the network status information of the fourth communication device to the first communication device through the fifth communication device. The network status of the fourth communication device includes a congestion status or a non-congestion status (i.e., a normal status).

[0183] In a possible implementation, if the first communication device obtains network status information as congestion status information, the first indication information is used to activate the function of the first entity in the third communication device.

[0184] In another possible implementation, if the first communication device obtains network status information as non-congestion status information, the first indication information is used to deactivate the function of the first entity in the third communication device.

[0185] The function of the first entity described above may refer to the data discarding function of the first entity. For specific descriptions of the function of the first entity, please refer to Figure 5 the description in, which will not be elaborated here.

[0186] In the embodiments of the present application, the first indication information further includes the identification information of the first RB, and the first RB corresponds to the first entity. The first RB is any one of the following RBs: split RB, duplicated RB, or dual active protocol stack (DAPS) RB.

[0187] Step 620: The first communication device sends the first indication information to the second communication device.

[0188] As an example, the first indication information may be sent to the second communication device through a PDCP message or an F1AP message. The second communication device then sends the first indication information to the third communication device. At this time, the first indication information may be transmitted through a PDCP message or a MAC CE.

[0189] In a possible implementation, the format of the first indication information may refer to Figure 10 the MAC CE format shown below. The MAC CE format in Figure 10 will be described in detail below and will not be elaborated here for the time being.

[0190] Step 630: The second communication device sends the first indication information to the third communication device.

[0191] In an embodiment of the present application, after receiving the first indication information sent by the first communication device, the second communication device may send the first indication information to the third communication device.

[0192] Step 640: According to the first indication information, when the function of the first entity in the third communication device is activated, the third communication device discards the data in the first entity according to the first timer.

[0193] In an embodiment of the present application, after receiving the first indication information sent by the second communication device, if the first indication information indicates to activate the function of the first entity in the third communication device, the third communication device activates the above-mentioned function of the first entity. Specifically, when the first timer times out, the data in the first entity is discarded.

[0194] Step 650: According to the first indication information, when the function of the first entity in the third communication device is deactivated, the third communication device discards the data in the first entity according to the second timer.

[0195] In an embodiment of the present application, after receiving the first indication information sent by the second communication device, if the first indication information indicates to deactivate the function of the first entity in the third communication device, the third communication device deactivates the above-mentioned function of the first entity. Specifically, when the second timer times out, the data in the first entity is discarded.

[0196] Optionally, in some embodiments, the second communication device further sends third indication information to the third communication device, where the third indication information is used to indicate to activate the above-mentioned function of the third entity in the third communication device, or to deactivate the above-mentioned function of the third entity in the third communication device. Specifically, if the above-mentioned function of the third entity in the third communication device is in an activated state, when the first timer times out, the data in the third entity is discarded. If the above-mentioned function of the third entity in the third communication device is in a deactivated state, when the second timer times out, the data in the third entity is discarded.

[0197] As an example, when the third communication device receives the above first indication information (the first indication information indicates to activate the function of the first entity in the third communication device) and the third indication information (the third indication information indicates to activate the function of the third entity in the third communication device), the third communication device discards the data of the second entity (for example, low-importance data) according to the first timer.

[0198] Another example is that when the third communication device receives the above-mentioned first indication information (the first indication information indicates activating the function of the first entity in the third communication device) and the third indication information (the third indication information indicates deactivating the function of the third entity in the third communication device), the third communication device discards the data of the first entity (such as low-importance data) according to the first timer, discards the data of the third entity (such as high-importance data and low-importance data) according to the second timer, and discards the data of the second entity (including low-importance data and high-importance data) according to the second timer.

[0199] Another example is that when the third communication device receives the above-mentioned first indication information (the first indication information indicates deactivating the function of the first entity in the third communication device) and the third indication information (the third indication information indicates activating the function of the third entity in the third communication device), the third communication device discards the data of the first entity (such as high-importance data and low-importance data) according to the second timer, discards the data of the third entity (such as low-importance data) according to the first timer, and discards the data of the second entity (including low-importance data and high-importance data) according to the second timer.

[0200] Another example is that when the third communication device only receives the above-mentioned third indication information (the third indication information indicates activating the function of the third entity in the third communication device) or the above-mentioned first indication information (the first indication information indicates activating the function of the first entity in the third communication device), the third communication device discards the data of the second entity (including low-importance data and high-importance data) according to the second timer.

[0201] Another example is that when the third communication device receives the above-mentioned first indication information (the first indication information indicates deactivating the function of the first entity in the third communication device) and the third indication information (the third indication information indicates deactivating the function of the third entity in the third communication device), the third communication device discards the data of the second entity (including low-importance data and high-importance data) according to the second timer.

[0202] Another example is that when the third communication device only receives the above-mentioned first indication information (the first indication information indicates deactivating the function of the first entity in the third communication device), the third communication device discards the data of the first entity according to the second timer.

[0203] Another example is that when the third communication device only receives the above-mentioned third indication information (the third indication information indicates deactivating the function of the third entity in the third communication device), the third communication device discards the data of the third entity according to the second timer.

[0204] Optionally, in some embodiments, the third communication device may further send a first report (e.g., a first PDCP report) to the first communication device, where the first report is used to indicate the sequence number SN of the data discarded by the third communication device. The discarded data includes the data discarded by an entity in the third communication device, and the entity may be at least one of the following entities: a first entity, a second entity, and a third entity.

[0205] For example, in the case where the control anchor point (which may also be referred to as the RB termination point) is switched from the first communication device to the fifth communication device, the first communication device may further send a second report (e.g., a second PDCP report) to the fifth communication device, where the second report is used to indicate that the data discarded by the third communication device has been successfully received. Among them, the data discarded by the third communication device in the second report is determined by the first report. At this time, according to the second report, the bottom of the receiving SN window of the fifth communication device skips the SN of the data that has been discarded by the third communication device. Otherwise, without the second report, the bottom of the receiving SN window in the fifth communication device will stay at the SN of the data that has been discarded by the third communication device, resulting in the inability to receive subsequent data in the fifth communication device, thereby affecting the service experience.

[0206] In the above technical solution, by interacting with the network status information between different network devices in the DC scenario, the entity in the third communication device is centrally controlled to discard data, avoiding excessive data discarded by the third communication device in the DC scenario and improving the service experience.

[0207] The following combines Figure 7 , and a specific implementation manner of the communication method provided by the embodiments of the present application will be described in detail. It should be understood that Figure 7 the examples are only to help those skilled in the art understand the embodiments of the present application, rather than limiting the embodiments of the application to Figure 7 the specific numerical values or specific scenarios shown. Those skilled in the art can clearly make various equivalent modifications or changes according to Figure 7 the following examples given, and such modifications and changes also fall within the scope of the embodiments of the present application.

[0208] Figure 7 FIG. Figure 7 shows a schematic flowchart of another communication method applied to the dual-connection DC scenario provided by the embodiments of the present application. As

[0209] should be understood, Figure 7 corresponds to Figure 5 , that is Figure 7 is Figure 5A specific implementation of the communication method shown. In Figure 7 the terminal device may correspond to the first communication device in Figure 5 MN-DU corresponds to the second communication device in Figure 5 SN-DU corresponds to the third communication device in Figure 5 the first RLC entity corresponds to the first entity in Figure 5 the second RLC entity corresponds to the third entity in Figure 5 PDCP corresponds to the second entity in Figure 5 the second entity.

[0210] For ease of description, Figure 7 in

[0211] MN is used as the control anchor for illustration.

[0212] Step 710: MN-CU sends a first RRC reconfiguration message for the first RB to the terminal device through MN-DU.

[0213] As an example, MN-CU may send an RRC reconfiguration message to the terminal device through MN-DU. The RRC reconfiguration message may include, but is not limited to: the duration of the first timer, the duration of the second timer, and the configuration information of the enhanced format of PSI-based activation or deactivation.

[0214] Optionally, before step 710, the terminal device may also send capability information to MN-CU through MN-DU, and the capability information is used to indicate that the terminal device can support the enhanced format of PSI-based activation or deactivation.

[0215] Both the first timer and the second timer correspond to the first RB, and the first RB may be any one of the following: split RB, duplicated RB, or dual active protocol stack (DAPS) RB.

[0216] In the embodiments of the present application, before step 710, after the MN receives downlink data from the core network as a control anchor point (which can also be referred to as the RB termination point), on the one hand, the MN-CU sends the downlink data to the terminal device through the MN-DU. On the other hand, the MN-CU also sends the downlink data to the SN-CU, and the SN-CU sends the downlink data to the terminal device through the SN-DU. Specifically, the MN-DU sends the downlink data to the first MAC entity (or simply referred to as the first MAC) corresponding to the MN in the terminal device, and passes through the first RLC entity (or simply referred to as the first RLC) corresponding to the MN. The SN-DU sends the downlink data to the second MAC entity (or simply referred to as the second MAC) corresponding to the MN in the terminal device, and passes through the second RLC entity (or simply referred to as the second RLC) corresponding to the MN. Finally, the downlink data sent by the MN to the terminal device and the downlink data sent by the SN to the terminal device will be aggregated at the NR PDCP of the terminal device.

[0217] The above-mentioned SN-CU refers to the CU in the SN, and the SN-DU refers to the DU in the SN. As an example, in the scenario of EN-DC or MR-DC, the SN is the 5G-NR secondary node gNB (SN-gNB).

[0218] In a possible implementation manner, in the EN-DC scenario, the first RLC entity is Figure 2 the E-UTRA RLC in Figure 2 the E-UTRA MAC in Figure 2 the NR RLC in Figure 2 the NR MAC in

[0219] In another possible implementation manner, in the MR-DC scenario, the first RLC entity is Figure 3 the MN RLC in Figure 3 the MN MAC in Figure 3 the SN RLC in Figure 3 the SN MAC in

[0220] For example, Figure 8 is a schematic diagram of an enhanced format of PSI-based activation or deactivation provided by the embodiments of the present application. It should be understood that the indication information of PSI-based activation or deactivation can be carried in the MAC CE, and the format of this MAC CE is an enhanced format. See Figure 8, the MAC CE may include: a DRB ID field and an RLCi field. Among them, the DRB ID field indicates the identifier of the DRB corresponding to the current MAC CE (for example, the identifier of the first RB), and the field length is, for example, 5 bits. RLCi represents the ID of the logical channel of the RLC entity, and these logical channel IDs all correspond to the first RB, and are numbered in ascending order of MCG and SCG. For example, when i = 0, RLCi represents RLC entity 0, and when i = 1, RLCi represents RLC entity 1. Taking the MR-DC scenario as an example, RLC entity 0 may correspond to the MN RLC entity, and RLC entity 1 may correspond to the SN RLC entity. The value of the RLCi field is used to indicate the activation / deactivation state of the PSI-based discard of the RLC entity i. Setting the value of the RLCi field to 1 may indicate that the PSI-based discard of the RLC entity i is activated, and setting the value of the RLCi field to 0 may indicate that the PSI-based discard of the RLC entity i is deactivated.

[0221] Combined with steps 715 - 735 below, the specific implementation manner of sending a PSI based discard activation indication for the RLC entity corresponding to the first RB to the terminal device in the case of congestion of the DU (MN-DU and / or SN-DU) is described in detail.

[0222] Step 715: In the case of congestion of the MN-DU, the MN-DU sends a first activation indication for the first RLC entity corresponding to the first RB to the terminal device.

[0223] In the embodiment of the present application, in the case of congestion of the MN-DU, the MN-DU determines to activate the PSI based discard of the first RLC entity corresponding to the first RB, and sends a PSI based discard activation indication for the first RLC entity corresponding to the first RB to the terminal device, and this PSI based discard activation indication may also be referred to as the first activation indication.

[0224] As an example, this first activation indication may be carried in Figure 8 the MAC CE, and for the specific format of the MAC CE, please refer to the description of Figure 8 above, and will not be elaborated here.

[0225] Step 720: After receiving the first activation indication sent by the MN-DU, the terminal device activates the function of the PSI based discard of the first RLC entity corresponding to the first RB.

[0226] In an embodiment of the present application, after the terminal device receives the first activation indication sent by the MN-DU, it can activate the PSI based discard function of the first RLC entity corresponding to the first RB. After the terminal device activates the PSI based discard function of the first RLC entity corresponding to the first RB, if the PDCP entity of the terminal device receives data (e.g., the first data) from the upper layer of the terminal device, it starts a first timer, and the duration of the first timer is the first duration. The terminal device determines whether to discard the first data received from the PDCP entity in the first RLC entity according to the running state of the first timer.

[0227] It should be understood that the above first data is transmitted through the first RB.

[0228] As an example, if the first timer expires, the terminal device discards the first data received from the PDCP entity in the first RLC entity.

[0229] As another example, if the first timer does not expire, the terminal device does not discard the first data received from the PDCP entity in the first RLC entity, that is, it caches the first data received from the PDCP entity in the first RLC entity.

[0230] It should be noted that at this time, the terminal device does not determine whether to discard data according to the running state of the second timer. Optionally, when the PDCP entity of the terminal device receives data (e.g., the first data) from the upper layer of the terminal device, the terminal device can also start a second timer, but does not discard data based on the running state of the second timer. For example, it does not discard the first data received from the PDCP entity.

[0231] Step 725: In the case of SN-DU congestion, the SN-DU sends a second activation indication of the second RLC entity corresponding to the first RB to the terminal device.

[0232] In an embodiment of the present application, in the case of SN-DU congestion, the SN-DU determines to activate the PSI based discard of the second RLC entity corresponding to the first RB, and sends a PSI based discard activation indication of the second RLC entity corresponding to the first RB to the terminal device. The PSI based discard activation indication can also be referred to as the second activation indication.

[0233] As an example, the second activation indication can be carried in Figure 8 the MAC CE. For the specific format of the MAC CE, please refer to the description of Figure 8 above, which will not be elaborated here.

[0234] Step 730: After the terminal device receives the second activation indication sent by the SN-DU, it activates the PSI based discard function of the second RLC entity corresponding to the first RB.

[0235] In the embodiments of the present application, after the terminal device receives the second activation indication sent by the SN-DU, it can activate the PSI based discard function of the second RLC entity corresponding to the first RB. After the terminal device activates the PSI based discard function of the second RLC entity corresponding to the first RB, if the PDCP entity of the terminal device receives data from the upper layer of the terminal device (for example, the second data), it starts the above-mentioned first timer, and the terminal device determines whether to discard the first data received from the PDCP entity in the second RLC entity according to the running state of the first timer.

[0236] It should be understood that the above-mentioned second data is transmitted through the first RB.

[0237] For example, if the first timer expires, the terminal device discards the second data received from the PDCP entity in the second RLC entity.

[0238] Another example, if the first timer does not expire, the terminal device does not discard the second data received from the PDCP entity in the second RLC entity, that is, it caches the second data received from the PDCP entity in the second RLC entity.

[0239] Similarly, at this time, the terminal device does not determine whether to discard data according to the running state of the second timer. Optionally, when the PDCP entity of the terminal device receives data from the upper layer of the terminal device (for example, the second data), the terminal device can also start the second timer, but does not discard data based on the running state of the second timer. For example, it does not discard the second data received from the PDCP entity.

[0240] Step 735: When the terminal device receives both the first activation indication sent by the MN-DU and the second activation indication sent by the SN-DU, the terminal device activates the PSI based discard function of the PDCP entity corresponding to the first RB.

[0241] In some embodiments, if the terminal device receives both the first activation indication sent by the MN-DU and the second activation indication sent by the SN-DU, the terminal device may activate the PSI based discard function of the PDCP entity corresponding to the first RB. After the terminal device activates the PSI based discard function of the PDCP entity corresponding to the first RB, if the PDCP entity of the terminal device receives data from the upper layer of the terminal device (e.g., the third data), the above-mentioned first timer is started, and whether to discard the received third data in the PDCP entity is determined according to the running state of the first timer.

[0242] It should be understood that the above-mentioned third data is transmitted through the first RB.

[0243] As an example, if the first timer expires, the terminal device discards the received third data in the PDCP entity. That is, after the third data is discarded in the PDCP entity, the third data will not be sent to the first RLC entity and the second RLC entity anymore.

[0244] Another example, if the first timer does not expire, the terminal device does not discard the received third data in the PDCP entity. That is, the third data will be sent to the first RLC entity and / or the second RLC entity through the PDCP entity.

[0245] Similarly, at this time, the terminal device does not determine whether to discard data according to the running state of the second timer. Optionally, when the PDCP entity of the terminal device receives data from the upper layer of the terminal device (e.g., the third data), the terminal device may also start the second timer, but does not discard data based on the running state of the second timer. For example, it does not determine whether to discard the received third data in the PDCP entity.

[0246] It should be noted that the above-mentioned first data, second data, and third data may be the same data, or may be different data, and the embodiments of the present application do not make specific limitations on this.

[0247] Next, in combination with step 740-step 760, the specific implementation manner of sending a PSI based discard deactivation indication to the RLC entity corresponding to the first RB to the terminal device in the case where the DU (MN-DU and / or SN-DU) is not congested is described in detail.

[0248] For example, it may be when the DU (MN-DU and / or SN-DU) changes from the above-mentioned congested situation to a non-congested situation that the following steps 740-760 are executed.

[0249] Step 740: When MN-DU is not congested, MN-DU sends a first deactivation indication of the first RLC entity corresponding to the first RB to the terminal device.

[0250] In the embodiments of the present application, when MN-DU is not congested, MN-DU determines to deactivate PSI based discard of the first RLC entity corresponding to the first RB, and sends a PSI based discard deactivation indication of the first RLC entity corresponding to the first RB to the terminal device. This PSI based discard deactivation indication can also be referred to as the first deactivation indication.

[0251] As an example, this first deactivation indication can be carried in Figure 8 the MAC CE of, and for the specific format of the MAC CE, please refer to the description of Figure 8 above, which will not be elaborated here.

[0252] Step 745: After receiving the first deactivation indication sent by MN-DU, the terminal device deactivates the function of PSI based discard of the first RLC entity corresponding to the first RB.

[0253] In the embodiments of the present application, after receiving the first deactivation indication sent by MN-DU, the terminal device can deactivate the function of PSI based discard of the first RLC entity corresponding to the first RB. After the terminal device deactivates the function of PSI based discard of the first RLC entity corresponding to the first RB, if the PDCP entity of the terminal device receives data from the upper layer of the terminal device (for example, the fourth data), a second timer is started. The duration of the second timer is the second duration, and the terminal device determines whether to discard the fourth data received from the PDCP entity in the first RLC entity according to the running state of the second timer.

[0254] It should be understood that the above-mentioned fourth data is transmitted through the first RB.

[0255] One example is that if the second timer expires, the terminal device discards the fourth data received from the PDCP entity in the first RLC entity.

[0256] Another example is that if the second timer does not expire, the terminal device does not discard the fourth data received from the PDCP entity in the first RLC entity, that is, the fourth data received from the PDCP entity is cached in the first RLC entity.

[0257] It should be noted that at this time, the terminal device does not determine whether to discard data based on the running state of the first timer. Optionally, the PDCP entity of the terminal device receives data from the upper layer of the terminal device (for example, the fourth data), and the terminal device can also start the first timer, but does not discard data based on the running state of the first timer. For example, it does not discard the fourth data received from the PDCP entity.

[0258] Step 750: In the case of non-congestion of the SN-DU, the SN-DU sends a second deactivation indication of the second RLC entity corresponding to the first RB to the terminal device.

[0259] In the embodiments of the present application, in the case of non-congestion of the SN-DU, the SN-DU determines to deactivate the PSI based discard of the second RLC entity corresponding to the first RB, and sends a PSI based discard deactivation indication of the second RLC entity corresponding to the first RB to the terminal device. The PSI based discard deactivation indication can also be referred to as the second deactivation indication.

[0260] As an example, the second deactivation indication can be carried in Figure 8 the MAC CE. For the specific format of the MAC CE, please refer to the description of Figure 8 above, which will not be elaborated here.

[0261] Step 755: After receiving the second deactivation indication sent by the SN-DU, the terminal device deactivates the PSI based discard function of the second RLC entity corresponding to the first RB.

[0262] In the embodiments of the present application, after receiving the second deactivation indication sent by the SN-DU, the terminal device can deactivate the PSI based discard function of the second RLC entity corresponding to the first RB. After the terminal device deactivates the PSI based discard function of the second RLC entity corresponding to the first RB, if the PDCP entity of the terminal device receives data from the upper layer of the terminal device (for example, the fifth data), the above-mentioned second timer is started, and the terminal device determines whether to discard the fifth data received from the PDCP entity in the second RLC entity according to the running state of the second timer.

[0263] It should be understood that the above-mentioned fifth data is transmitted through the first RB.

[0264] As an example, if the second timer times out, the terminal device will discard the fifth data received from the PDCP entity in the second RLC entity.

[0265] Another example, if the second timer does not time out, the terminal device will not discard the fifth data received from the PDCP entity in the second RLC entity, that is, it will cache the fifth data received from the PDCP entity in the second RLC entity.

[0266] Similarly, at this time, the terminal device does not determine whether to discard data according to the running state of the first timer. Optionally, the PDCP entity of the terminal device receives data from the upper layer of the terminal device (for example, the fifth data), and the terminal device can also start the first timer, but does not discard data based on the running state of the first timer. For example, it does not discard the fifth data received from the PDCP entity.

[0267] Step 760: The terminal device receives both the first deactivation indication sent by the MN-DU and the second deactivation indication sent by the SN-DU, and the terminal device deactivates the PSI based discard function of the PDCP entity corresponding to the first RB.

[0268] In some embodiments, if the terminal device receives both the first deactivation indication sent by the MN-DU and the second deactivation indication sent by the SN-DU, the terminal device can deactivate the PSI based discard function of the PDCP entity corresponding to the first RB. After the terminal device deactivates the PSI based discard function of the PDCP entity corresponding to the first RB, if the PDCP entity of the terminal device receives data from the upper layer of the terminal device (for example, the sixth data), it starts the above-mentioned second timer and determines whether to discard the received sixth data in the PDCP entity according to the running state of the second timer.

[0269] It should be understood that the above-mentioned sixth data is transmitted through the first RB.

[0270] An example, if the second timer times out, the terminal device will discard the received sixth data in the PDCP entity. That is, after the second data is discarded in the PDCP entity, the second data will not be sent to the first RLC entity and the second RLC entity anymore.

[0271] Another example, if the second timer does not time out, the terminal device will not discard the received sixth data in the PDCP entity. That is, the sixth data will be sent to the first RLC entity and / or the second RLC entity through the PDCP entity.

[0272] Similarly, at this time, the terminal device does not determine whether to discard data based on the running state of the first timer. Optionally, the PDCP entity of the terminal device receives data from the upper layer of the terminal device (for example, the first stream data), and the terminal device can also start the first timer, but does not discard data based on the running state of the first timer. For example, it does not determine whether to discard the received sixth data in the PDCP entity.

[0273] It should be noted that the above fourth data, fifth data, and sixth data can be the same data, or they can be different data. The embodiments of the present application do not make specific limitations on this.

[0274] Step 765: The terminal device sends a first PDCP report to the MN-CU, and the first PDCP report indicates the sequence number (SN) of the data that has been discarded by the terminal device.

[0275] In this embodiment, step 765 is optional.

[0276] In the embodiments of the present application, the terminal device also sends a first PDCP report to the MN-CU, and the first PDCP report indicates the SN (which can also be referred to as the PDCP SN) of the data that has been discarded by the terminal device.

[0277] For example, the SN of the data discarded by the terminal device may include at least one of the following SNs: the SN of the first data, the SN of the second data, and the SN of the third data.

[0278] As an example, the above first PDCP report may be in a control protocol data unit (PDU), or it may also be in a user PDU. The embodiments of the present application do not make specific limitations on this.

[0279] Step 770: The MN-CU sends a second PDCP report to the SN-CU.

[0280] In the embodiments of the present application, after receiving the first PDCP report sent by the terminal device, when the RB termination point switches from the MN to the SN, the MN-CU sends a second PDCP report to the SN-CU, and the second PDCP report indicates that the data discarded by the terminal device has been successfully received. After receiving the second PDCP report, the SN-CU skips the SN of the data discarded by the terminal device at the bottom of the received SN window according to the second PDCP report.

[0281] It should be understood that Figure 7The above example uses MN as the control anchor point (which can also be called the RB termination point). Therefore, the terminal device sends the first PDCP report to the MN-CU. In the case where the RB termination point switches from MN to SN, the MN-CU sends the second PDCP report to the SN-CU. If the control anchor point is SN, then the terminal device will send the first PDCP report to the SN-CU. After receiving the first PDCP report, in the case where the RB termination point switches from SN to MN, the SN-CU sends the second PDCP report to the MN-CU.

[0282] It should be noted that the second PDCP report contains a false ACK indication. That is, if there is no second report, the bottom of the receive SN window in the SN-CU will stay at the SN of the data that has been discarded by the terminal device, resulting in the inability to receive subsequent data in the SN-CU and thus affecting the service experience.

[0283] In the embodiments of the present application, after the RB termination point switches from MN to SN and the SN receives downlink data from the core network as the control anchor point, on the one hand, the SN-CU sends the downlink data to the terminal device through the SN-DU. On the other hand, the SN-CU also sends the downlink data to the MN-CU, and the MN-CU sends the downlink data to the terminal device through the MN-DU.

[0284] In the above technical solution, MN and SN respectively control the activation and deactivation of the PSI-based discard of their respective corresponding RLC entities in the terminal device. When only one of MN and SN is congested, only the data discard function of the corresponding RLC entity is activated, and the data transmission between the other network device and the terminal device remains unaffected. That is, the data transmission between the other network device and the terminal device is not affected, thus avoiding the terminal device from discarding too much data and improving the service experience.

[0285] The following combines Figure 9 to describe in detail another specific implementation manner of the communication method provided by the embodiments of the present application. It should be understood that Figure 9 the examples are only for helping those skilled in the art to understand the embodiments of the present application, rather than limiting the embodiments of the application to Figure 9 the specific numerical values or specific scenarios shown. Those skilled in the art can obviously make various equivalent modifications or changes according to Figure 9 the following examples given, and such modifications and changes also fall within the scope of the embodiments of the present application.

[0286] It should be understood that Figure 9 and Figure 6Corresponding, that is Figure 9 is Figure 6 a specific implementation manner of the communication method shown. In Figure 9 the first node's CU corresponds to Figure 6 the first communication device in Figure 6 the second communication device in Figure 6 the third communication device in Figure 6 the fourth communication device in Figure 6 the fifth communication device in

[0287] Figure 9 is a schematic flowchart of another communication method provided by an embodiment of the present application applied to a dual-connectivity DC scenario. As Figure 9 shown, the method may include steps 910-980, which will be described in detail below for steps 910-980.

[0288] Step 910: The CU of the first node sends an RRC reconfiguration message for the first RB to the terminal device.

[0289] It should be understood that in an embodiment of the present application, the first node represents the node where the control anchor point (which can also be referred to as the RB termination point) of the first RB is located. Taking the MN as the RB termination point, the first node is the MN, and the CU of the first node is the CU of the MN (abbreviated as MN-CU). Taking the SN as the RB termination point, the first node is the SN, and the CU of the first node is the CU of the SN (abbreviated as SN-CU).

[0290] Step 910 is similar to step 710. For specific details, please refer to the description in step 710 and will not be elaborated here.

[0291] Step 915: The CU of the first node sends congestion reporting control information to the DU of the first node.

[0292] In an embodiment of the present application, the CU of the first node may send congestion reporting control information to the DU of the first node, and the congestion reporting control information is used to control the DU of the first node to report congestion information of the DU of the first node for the first RB (for example, the congestion information may be at the RB granularity) to the CU of the first node.

[0293] It should be understood that, taking MN as the RB termination point, the DU of the first node is the DU of MN (abbreviated as MN-DU). Taking SN as the RB termination point, the DU of the first node is the DU of SN (abbreviated as SN-DU).

[0294] Step 920: The CU of the first node sends congestion reporting control information to the DU of the second node through the CU of the second node.

[0295] In the embodiments of the present application, the CU of the first node may also send congestion reporting control information to the DU of the second node through the CU of the second node, and the congestion reporting control information is used to control the DU of the second node to report congestion information of the DU of the second node for the first RB to the CU of the first node (for example, the congestion information may be at the RB granularity).

[0296] The following combines steps 925-step 945 to describe in detail the specific implementation manner of sending a PSI based discard activation indication for the RLC entity corresponding to the first RB to the terminal device in the case of congestion of the DU (the DU of the first node, the DU of the second node).

[0297] Step 925: The DU of the first node reports congestion information of the DU of the first node for the first RB to the CU of the first node.

[0298] In the embodiments of the present application, after receiving the congestion reporting control information sent by the CU of the first node, when the DU of the first node is congested, the DU of the first node reports congestion information of the DU of the first node for the first RB to the CU of the first node.

[0299] Step 930: The DU of the second node reports congestion information of the DU of the second node for the first RB to the CU of the first node.

[0300] In the embodiments of the present application, after receiving the congestion reporting control information sent by the CU of the first node, when the DU of the second node is congested, the DU of the second node reports congestion information of the DU of the second node for the first RB to the CU of the first node through the CU of the second node.

[0301] Step 935: The CU of the first node sends a PSI based discard activation indication for the first RB to the DU of the first node or the DU of the second node according to the congestion information of the DU of the first node and / or the DU of the second node.

[0302] In an embodiment of the present application, after the CU of the first node receives the congestion information of the DU of the first node for the first RB and / or the congestion information of the DU of the second node for the first RB, it may determine to activate the PSI based discard of the first RLC entity corresponding to the first RB according to the congestion information of the DU of the first node and / or the DU of the second node, and send a PSI based discard activation indication for the first RB to the DU of the first node or the DU of the second node. This PSI based discard activation indication may also be referred to as a third activation indication.

[0303] For ease of description, Figure 9 it is described by taking the CU of the first node sending a PSI based discard activation indication for the first RB to the DU of the first node as an example.

[0304] Step 940: The DU of the first node or the DU of the second node sends a third activation indication of the first RLC entity corresponding to the first RB to the terminal device.

[0305] In one example, the CU of the first node sends a PSI based discard activation indication for the first RB to the DU of the first node according to the congestion information of the DU of the first node and / or the DU of the second node. The DU of the first node sends a MAC CE to the terminal device, and the MAC CE includes a third activation indication of the first RLC entity corresponding to the first RB.

[0306] In another example, the CU of the first node sends a PSI based discard activation indication for the first RB to the DU of the second node through the CU of the second node according to the congestion information of the DU of the first node and / or the DU of the second node. The DU of the second node sends a MAC CE to the terminal device, and the MAC CE includes a third activation indication of the first RLC entity corresponding to the first RB.

[0307] For ease of description, Figure 9 it is described by taking the DU of the first node sending a third activation indication of the first RLC entity corresponding to the first RB to the terminal device as an example.

[0308] In an embodiment of the present application, the format of the MAC CE in step 940 is as Figure 10As shown, the MAC CE may include: a Di field. Here, i represents the order of DRB IDs in the DRB for PSI-discarded SDUs from smallest to largest. Di = 1 indicates that DRB i needs to activate the PSI-based SDU discard function. Di = 0 indicates that DRB i deactivates the PSI-based SDU discard function.

[0309] Step 945: After receiving the third activation indication, the terminal device activates the PSI-based discard function of the first RLC entity corresponding to the first RB.

[0310] In the embodiments of the present application, after receiving the third activation indication sent by the DU of the first node or the DU of the second node, the terminal device can activate the PSI-based discard function of the first RLC entity corresponding to the first RB. After the terminal device activates the PSI-based discard function of the first RLC entity corresponding to the first RB, if the PDCP entity of the terminal device receives data from the upper layer of the terminal device (for example, the seventh data), a first timer is started. The duration of the first timer is the first duration. The terminal device determines whether to discard the seventh data received from the PDCP entity in the PDCP entity and / or the RLC entity (including the first RLC entity and the second RLC entity) according to the running state of the first timer.

[0311] It should be understood that the above seventh data is transmitted through the first RB.

[0312] As an example, if the first timer expires, the terminal device discards the received seventh data in the PDCP entity and / or the RLC entity (including the first RLC entity and the second RLC entity).

[0313] It should be noted that at this time, the terminal device does not determine whether to discard data according to the running state of the second timer. Optionally, when the PDCP entity of the terminal device receives data from the upper layer of the terminal device (for example, the seventh data), the terminal device can also start a second timer, but does not discard data based on the running state of the second timer. For example, it does not discard the seventh data received from the PDCP entity.

[0314] Next, in combination with steps 950 - 970, the specific implementation method of sending a PSI-based discard deactivation indication for the RLC entity corresponding to the first RB to the terminal device in the case where the DU (the DU of the first node, the DU of the second node) is not congested is described in detail.

[0315] Step 950: The DU of the first node reports the non-congestion information of the first node's DU for the first RB to the CU of the first node.

[0316] In the embodiment of the present application, after the DU of the first node receives the congestion reporting control information sent by the CU of the first node, in the case that the DU of the first node is not congested, the DU of the first node reports to the CU of the first node the non-congestion information of the DU of the first node for the first RB.

[0317] Step 955: The DU of the second node reports to the CU of the first node the non-congestion information of the DU of the second node for the first RB.

[0318] In the embodiment of the present application, after the DU of the second node receives the congestion reporting control information sent by the CU of the first node, in the case that the DU of the second node is not congested, the DU of the second node reports to the CU of the first node through the CU of the second node the non-congestion information of the DU of the second node for the first RB.

[0319] Step 960: The CU of the first node sends a deactivation indication of PSI based discard for the first RB to the DU of the first node or the DU of the second node according to the non-congestion information of the DU of the first node and / or the DU of the second node.

[0320] In the embodiment of the present application, after the CU of the first node receives the non-congestion information of the DU of the first node for the first RB and / or the non-congestion information of the DU of the second node for the first RB, it can determine to deactivate the PSI based discard of the first RLC entity corresponding to the first RB according to the non-congestion information of the DU of the first node and / or the DU of the second node, and send a deactivation indication of PSI based discard for the first RB to the DU of the first node or the DU of the second node. This deactivation indication of PSI based discard can also be referred to as the third deactivation indication.

[0321] Step 965: The DU of the first node or the DU of the second node sends the third deactivation indication of the first RLC entity corresponding to the first RB to the terminal device.

[0322] As an example, the CU of the first node sends a deactivation indication of PSI based discard for the first RB to the DU of the first node according to the non-congestion information of the DU of the first node and / or the DU of the second node. The DU of the first node sends a MAC CE to the terminal device, and the MAC CE includes the third deactivation indication of the first RLC entity corresponding to the first RB.

[0323] In another example, the CU of the first node sends a PSI based discard deactivation indication for the first RB to the DU of the second node through the CU of the second node according to the non-congestion information of the DU of the first node and / or the DU of the second node. The DU of the second node sends a MAC CE to the terminal device, and the MAC CE includes a third deactivation indication for the first RLC entity corresponding to the first RB.

[0324] In the embodiments of the present application, the third deactivation indication may be carried in Figure 10 the MAC CE shown. For the specific format of the MAC CE, please refer to the description of Figure 10 above, which will not be elaborated here.

[0325] Step 970: After receiving the third deactivation indication, the terminal device deactivates the PSI based discard function of the first RLC entity corresponding to the first RB.

[0326] In the embodiments of the present application, after receiving the third deactivation indication sent by the DU of the first node or the DU of the second node, the terminal device may deactivate the PSI based discard function of the first RLC entity corresponding to the first RB. After the terminal device deactivates the PSI based discard function of the first RLC entity corresponding to the first RB, if the PDCP entity of the terminal device receives data from the upper layer of the terminal device (for example, the eighth data), the second timer is started. The duration of the second timer is the second duration. The terminal device determines whether to discard the received eighth data in the PDCP entity and / or the RLC entity (including the first RLC entity and the second RLC entity) according to the running state of the second timer.

[0327] It should be understood that the above-mentioned eighth data is transmitted through the first RB.

[0328] In one example, if the second timer expires, the terminal device discards the received eighth data in the PDCP entity and / or the RLC entity (including the first RLC entity and the second RLC entity).

[0329] It should be noted that at this time, the terminal device does not determine whether to discard data according to the running state of the first timer. Optionally, when the PDCP entity of the terminal device receives data from the upper layer of the terminal device (for example, the eighth data), the terminal device may also start the first timer, but does not discard data based on the running state of the first timer. For example, it does not discard the received eighth data.

[0330] Step 975: The terminal device sends a first PDCP report to the CU of the first node, and the first PDCP report indicates the sequence number (SN) of the data discarded by the terminal device.

[0331] In this embodiment, step 975 is optional.

[0332] In the embodiment of the present application, the terminal device also sends a first PDCP report to the CU of the first node, and the first PDCP report indicates the SN of the data discarded by the terminal device.

[0333] For example, the SN of the data discarded by the terminal device may include at least one of the following SNs: the SN of the seventh data, the SN of the eighth data.

[0334] Step 980: The CU of the first node sends a second PDCP report to the CU of the second node.

[0335] In the embodiment of the present application, after receiving the first PDCP report sent by the terminal device, when the RB termination point switches from the first node to the second node, the CU of the first node sends a second PDCP report to the CU of the second node, and the second PDCP report indicates that the data discarded by the terminal device has been successfully received. After receiving the second PDCP report, the CU of the second node skips the SN of the data discarded by the terminal device at the bottom of the received SN window according to the second PDCP report.

[0336] In the above technical solution, by inter-station interaction of congestion information and centralized control of the activation and deactivation of PSI-based, it is avoided that the terminal device discards too many data packets in the DC scenario, thereby improving the service experience.

[0337] It should be understood that the magnitudes of the sequence numbers of the above processes do not mean the order of execution. The execution order of each process should be determined according to its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0338] It should also be understood that in various embodiments of the present application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0339] It should also be understood that in some of the above embodiments, the devices in the existing network architecture are mainly used as examples for illustrative purposes. It should be understood that the specific form of the device is not limited in the embodiments of the present application. For example, devices that can achieve the same functions in the future are applicable to the embodiments of the present application.

[0340] It can be understood that, in the above method embodiments, the methods and operations implemented by devices (such as the first communication device and the second communication device) can also be implemented by components (such as chips or circuits) available for the devices.

[0341] It can also be understood that some optional features in the embodiments of the present application can, in some scenarios, be independent of other features, and in some scenarios, can be combined with other features, without limitation.

[0342] As above, in combination with Figures 5 - 7 , Figure 9 the communication method provided in the embodiments of the present application has been described in detail. The above communication method has been introduced mainly from the perspectives of the first communication device and the second communication device. It can be understood that, in order to implement the above functions, the first communication device and the second communication device include corresponding hardware structures and / or software modules for executing each function.

[0343] Those skilled in the art should be able to realize that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraint conditions of the technical solution. Professional technicians can use different methods to implement the described function for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0344] As follows, in combination with Figures 11 to 13 the communication device provided in the embodiments of the present application will be described in detail. It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, for the content not described in detail, reference can be made to the above method embodiments. For the sake of brevity, some content will not be repeated.

[0345] The embodiments of the present application can divide the functional modules of the sending-end device or the receiving-end device according to the above method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiments of the present application is illustrative, only a logical functional division, and there can be other division methods in actual implementation. Hereinafter, taking the division of each functional module corresponding to each function as an example for description.

[0346] Figure 11It is a schematic block diagram of a communication device 10 provided by an embodiment of the present application. The device 10 includes a transceiver module 11 and a processing module 12. The transceiver module 11 can implement corresponding communication functions, and the processing module 12 is used for data processing. Or rather, the transceiver module 11 is used to perform operations related to reception and transmission, and the processing module 12 is used to perform other operations except reception and transmission. The transceiver module 11 can also be referred to as a communication interface or a communication unit.

[0347] Optionally, the device 10 may further include a storage module 13. The storage module 13 can be used to store instructions and / or data. The processing module 12 can read the instructions and / or data in the storage module so that the device can implement the actions of the device in the foregoing method embodiments.

[0348] In one design, the device 10 can correspond to the first communication device in the foregoing method embodiment, or be a component (such as a chip) of the first communication device.

[0349] The device 10 can implement the steps or processes corresponding to those performed by the first communication device in the foregoing Figure 5 Among them, the transceiver module 11 can be used to perform operations related to reception and transmission of the first communication device in the foregoing Figure 5 And the processing module 12 can be used to perform operations related to processing of the first communication device in the foregoing Figure 5 Among them.

[0350] In a possible implementation, the transceiver module 11 is used to receive first indication information, which is used to activate the function of the first entity in the first communication device or to deactivate the function of the first entity in the first communication device; the processing module 12 is used to, according to the first indication information, when the function of the first entity is activated, discard the data of the first entity according to a first timer; or the processing module 12 is used to, according to the first indication information, when the function of the first entity is deactivated, discard the data of the first entity according to a second timer.

[0351] In another possible implementation, the first indication information further includes identification information of a first radio bearer RB. The first RB corresponds to the first entity, the first RB corresponds to the second entity, and the first RB is any one of the following: a split RB, a duplicate RB, or a dual active protocol stack DAPS RB.

[0352] In another possible implementation, when the function of the first entity is activated, the function of the third entity is in a deactivated state. The third entity is used to discard the data in the third entity according to the second timer. The third entity and the first entity correspond to different network devices in the DC scenario.

[0353] In another possible implementation, the first entity is an RLC entity corresponding to the master node MN, and the third entity is an RLC entity corresponding to the secondary node SN; or the first entity is an RLC entity corresponding to the SN, and the third entity is an RLC entity corresponding to the MN.

[0354] In another possible implementation, the transceiver module 11 is configured to receive configuration information for configuring the function in the DC scenario. The configuration information includes the duration of the first timer and the duration of the second timer.

[0355] In another possible implementation, the configuration information further includes second indication information for indicating the function in the DC scenario.

[0356] In another possible implementation, the transceiver module 11 is configured to receive first indication information from the MN for activating the above function of the first entity in the first communication device; the transceiver module 11 is further configured to receive third indication information from the SN for activating the function of the third entity in the first communication device; the processing module 12 is configured to discard the data of the first entity, and / or the data of the second entity, and / or the data in the third entity according to the first timer.

[0357] In another possible implementation, the transceiver module 11 is configured to send a first report for indicating the sequence number SN of the data discarded by the first communication device. The discarded data includes at least one of the following data: the data discarded by the first entity, the data discarded by the second entity, or the data discarded by the third entity.

[0358] In another possible implementation, the first indication information is further used to indicate the first entity.

[0359] In another possible implementation, the processing module 12 is configured to discard the data of the first entity when the first timer expires.

[0360] In another possible implementation, the processing module 12 is configured to discard the data of the first entity when the second timer expires.

[0361] In another possible implementation, the first timer and the second timer correspond to the first RB.

[0362] In another possible implementation, the duration of the first timer is less than the duration of the second timer.

[0363] In another design, the device 10 may correspond to the second communication device in the above method embodiment, or may be a component (such as a chip) of the second communication device.

[0364] The device 10 can realize the above Figure 5 The steps or processes performed by the second communication device in the embodiment, wherein the transceiver module 11 can be used to perform the above Figure 5 The processing module 12 can be used to perform the above-mentioned operations related to the transmission and reception of the second communication device. Figure 5 Operations related to processing by the second communication device.

[0365] In one possible implementation, the processing module 12 is used to determine first indication information; the transceiver module 11 is used to send the first indication information, the first indication information is used to activate the function of a first entity in a first communication device, or to deactivate the function of the first entity, the first communication device is a terminal device in the DC scenario, when the function of the first entity is activated, the first entity is used to discard the data of the first entity according to a first timer, when the function of the first entity is deactivated, the first entity is used to discard the data of the first entity according to a second timer, the first entity is different from the second entity in the first communication device, and the second entity is used to manage the first timer and the second timer.

[0366] In another possible implementation, the first indication information also includes identification information of a first wireless bearer RB, the first RB corresponds to the first entity, the first RB corresponds to the second entity, and the first RB is any one of the following: a separated RB, a repeated RB, or a dual activation protocol stack DAPS RB.

[0367] In another possible implementation, the transceiver module 11 is used to send configuration information, which is used to configure the function of the first communication device in the DC scenario. The configuration information includes the duration of the first timer and the duration of the second timer. The first timer and the second timer correspond to the first RB.

[0368] In another possible implementation, the configuration information also includes second indication information, and the second indication information is used to indicate the function of the first communication device in the DC scenario.

[0369] In another possible implementation, the transceiver module 11 is used to receive a first report, which is used to indicate the sequence number SN of data discarded by the first communication device, and the discarded data includes at least one of the following data: data discarded by the first entity, data discarded by the second entity, or data discarded by a third entity.

[0370] In another possible implementation, the transceiver module 11 is used to send a second report, and the second report is used to indicate that the discarded data has been successfully received.

[0371] In another possible implementation, the network state is a congestion state, and the first indication information is used to activate the function of the first entity in the first communication device.

[0372] In another possible implementation, the network state is a non-congestion state, and the first indication information is used to deactivate the function of the first entity in the first communication device.

[0373] In another possible implementation, the duration of the first timer is less than the duration of the second timer.

[0374] In another possible implementation, the first indication information is further used to indicate the first entity.

[0375] In another design, the device 10 may correspond to the first communication device in the above method embodiment, or be a component (such as a chip) of the first communication device.

[0376] The device 10 can implement the steps or processes corresponding to those performed by the first communication device above Figure 6 wherein, the transceiver module 11 can be used to perform the operations related to the transceiver of the first communication device above Figure 6 and the processing module 12 can be used to perform the operations related to the processing of the first communication device above Figure 6 in the first communication device.

[0377] In a possible implementation, the processing module 12 is used to determine the first indication information; the transceiver module 11 is used to send the first indication information to the second communication device according to the network state information, and the first indication information is used to activate the function of the first entity in the third communication device or to deactivate the function of the first entity in the third communication device, the second communication device is a network device in the DC scenario, and the third communication device is a terminal device in the DC scenario.

[0378] In another possible implementation, the transceiver module 11 is used to receive the network state information from the second communication device and / or the fourth communication device, and determine the first indication information according to the network state information of the second communication device and / or the fourth communication device.

[0379] In another possible implementation, the transceiver module 11 is configured to send first control information to the second communication device, where the first control information is used to control the second communication device to report the network status information of the second communication device; and / or the transceiver module 11 is configured to send second control information to the fourth communication device, where the second control information is used to control the fourth communication device to report the network status information of the fourth communication device.

[0380] In another possible implementation, the network status information is congestion status information, and the first indication information is used to activate the function of the first entity.

[0381] In another possible implementation, the network status information is non-congestion status information, and the first indication information is used to deactivate the function of the first entity.

[0382] In another possible implementation, the first indication information further includes identification information of a first radio bearer (RB), where the first RB corresponds to the first entity, and the first RB is any one of the following: a split RB, a duplicate RB, or a dual active protocol stack (DAPS) RB.

[0383] In another possible implementation, the transceiver module 11 is configured to receive a first report, where the first report is used to indicate the sequence number (SN) of the data discarded by the third communication device.

[0384] In another possible implementation, the transceiver module 11 is configured to send a second report, where the second report is used to indicate that the discarded data has been successfully received.

[0385] It should also be understood that the device 10 here is embodied in the form of functional modules. The term "module" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor, or a group of processors, etc.) for executing one or more software or firmware programs, a memory, a combined logic circuit, and / or other suitable components that support the described functions. In an alternative example, those skilled in the art can understand that the device 10 may specifically be the first communication device in the above embodiments, and may be used to execute the respective processes and / or steps corresponding to the first communication device in the above method embodiments; or, the device 10 may specifically be the second communication device in the above embodiments, and may be used to execute the respective processes and / or steps corresponding to the second communication device in the above method embodiments. To avoid repetition, details are not described herein again.

[0386] The device 10 in each of the above solutions has the function of implementing the corresponding steps performed by the devices (such as the first communication device) in the above method. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver module can be replaced by a transceiver (for example, the sending unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as the processing module, can be replaced by a processor to perform the transceiver operations and related processing operations in each method embodiment respectively.

[0387] In addition, the above transceiver module 11 can also be a transceiver circuit (for example, it can include a receiving circuit and a sending circuit), and the processing module can be a processing circuit.

[0388] Figure 12 It is a schematic diagram of another communication device 20 provided by an embodiment of the present application. The device 20 includes a processor 21, and the processor 21 is used to execute the computer program or instruction stored in the memory 22, or read the data / signaling stored in the memory 22 to execute the methods in the above method embodiments. Optionally, the processor 21 is one or more.

[0389] Optionally, as Figure 12 shown, the device 20 further includes a memory 22, and the memory 22 is used to store computer programs or instructions and / or data. The memory 22 can be integrated with the processor 21 or can be separately provided. Optionally, the memory 22 is one or more.

[0390] Optionally, as Figure 12 shown, the device 20 further includes a transceiver 23, and the transceiver 23 is used for receiving and / or sending signals. For example, the processor 21 is used to control the transceiver 23 to receive and / or send signals.

[0391] As a solution, the device 20 is used to implement the operations performed by the first communication device or the second communication device in the above method embodiments.

[0392] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0393] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, the RAM may be used as an external cache. By way of example and not limitation, the RAM includes the following various forms: static random access memory (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0394] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) may be integrated in the processor.

[0395] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

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

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

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

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

[0400] The embodiment of the present application also provides a computer-readable storage medium, on which computer instructions for implementing the methods executed by the devices in the above method embodiments are stored.

[0401] For example, when the computer program is executed by a computer, the computer can implement the methods executed by the first communication device or the second communication device in the above method embodiments.

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

[0403] The embodiment of the present application also provides a communication system, including the aforementioned first communication device and second communication device.

[0404] The explanations and beneficial effects of the relevant content in any of the above-mentioned devices can refer to the corresponding method embodiments provided above, and will not be elaborated here.

[0405] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled professionals may use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0406] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated herein.

[0407] In several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

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

[0409] In addition, the functional units in each embodiment of this application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0410] When the above-described function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art or a part of this 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 for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0411] As described above, the above are only specific implementation manners of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed by this application can easily think of changes or substitutions, which should all be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A communication method applied to the dual-connection DC scenario, characterized in that, The method is applied to a first communication device, and the method includes: Receiving first indication information, where the first indication information is used to activate the function of a first entity in the first communication device or to deactivate the function of the first entity in the first communication device; According to the first indication information, when the function of the first entity is activated, discarding the data of the first entity according to a first timer; or According to the first indication information, when the function of the first entity is deactivated, discarding the data of the first entity according to a second timer; Wherein, the first entity is different from a second entity, the second entity is used to manage the first timer and the second timer, and the first timer is different from the second timer.

2. The method according to claim 1, wherein The first indication information further includes identification information of a first radio bearer (RB), the first RB corresponds to the first entity, the first RB corresponds to the second entity, and the first RB is any one of the following: a split RB, a duplicate RB, or a dual active protocol stack (DAPS) RB.

3. The method according to claim 1 or 2, characterized in that, When the function of the first entity is activated, the function of a third entity is in a deactivated state, the third entity is used to discard the data in the third entity according to the second timer, and the third entity and the first entity correspond to different network devices in the DC scenario.

4. The method according to claim 3, wherein: The first entity is an RLC entity corresponding to a master node (MN), and the third entity is an RLC entity corresponding to a secondary node (SN); or The first entity is an RLC entity corresponding to the SN, and the third entity is an RLC entity corresponding to the MN.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Receiving configuration information, where the configuration information is used to configure the function in the DC scenario, and the configuration information includes the duration of the first timer and the duration of the second timer.

6. The method according to claim 5, wherein The configuration information further includes second indication information, and the second indication information is used to indicate the function in the DC scenario.

7. The method according to any one of claims 1 to 6, wherein: The receiving the first indication information includes: Receiving first indication information from the MN, where the first indication information is used to activate the function of the first entity in the first communication device; The method further includes: Receiving third indication information from the SN, where the third indication information is used to activate the function of a third entity in the first communication device; The discarding the data of the first entity according to the first timer includes: Discarding the data of the first entity, and / or the data of the second entity, and / or the data in the third entity according to the first timer.

8. The method according to any one of claims 1 to 7, characterized in that The method further includes: Sending a first report, where the first report is used to indicate the sequence number (SN) of the data discarded by the first communication device, and the discarded data includes at least one of the following data: the data discarded by the first entity, the data discarded by the second entity, or the data discarded by the third entity.

9. The method according to any one of claims 1 to 8, characterized in that, The first indication information is further used to indicate the first entity.

10. The method according to any one of claims 1 to 9, characterized in that, Discarding the data of the first entity according to the first timer includes: Discarding the data of the first entity when the first timer expires.

11. The method according to any one of claims 1 to 10, characterized in that, Discarding the data of the first entity according to the second timer includes: Discarding the data of the first entity when the second timer expires.

12. The method according to any one of claims 1 to 11, characterized in that, The first timer and the second timer correspond to a first radio bearer (RB).

13. The method according to any one of claims 1 to 12, characterized in that, The duration of the first timer is less than the duration of the second timer.

14. A communication method applied to the dual-connectivity DC scenario, characterized in that, The method is applied to a second communication device, and the method includes: Determining first indication information; Sending the first indication information, where the first indication information is used to activate the function of a first entity in a first communication device or to deactivate the function of the first entity. The first communication device is a terminal device in the DC scenario. When the function of the first entity is activated, the first entity is used to discard the data of the first entity according to a first timer. When the function of the first entity is deactivated, the first entity is used to discard the data of the first entity according to a second timer. The first entity is different from a second entity in the first communication device, and the second entity is used to manage the first timer and the second timer.

15. The method according to claim 14, wherein The first indication information further includes identification information of a first radio bearer (RB). The first RB corresponds to the first entity, the first RB corresponds to the second entity, and the first RB is any one of the following: a split RB, a duplicate RB, or a dual active protocol stack (DAPS) RB.

16. The method according to claim 14 or 15, characterized in that The method further includes: Sending configuration information, where the configuration information is used to configure the function of the first communication device in the DC scenario. The configuration information includes the duration of the first timer and the duration of the second timer. The first timer and the second timer correspond to a first RB.

17. The method according to claim 16, characterized in that The configuration information further includes second indication information, where the second indication information is used to indicate the function of the first communication device in the DC scenario.

18. The method according to any one of claims 14 to 17, characterized in that The method further includes: Receiving a first report, where the first report is used to indicate the sequence number (SN) of the data discarded by the first communication device. The discarded data includes at least one of the following data: the data discarded by the first entity, the data discarded by the second entity, or the data discarded by a third entity, where the third entity and the first entity correspond to different network devices in the DC scenario.

19. The method according to claim 18, characterized in that, The method further includes: Sending a second report, where the second report is used to indicate that the discarded data has been successfully received.

20. The method according to any one of claims 14 to 19, characterized in that, When the network state is a congestion state, the first indication information is used to activate the function of the first entity in the first communication device.

21. The method according to any one of claims 14 to 19, characterized in that, When the network state is a non-congestion state, the first indication information is used to deactivate the function of the first entity in the first communication device.

22. The method according to any one of claims 14 to 21, characterized in that, The duration of the first timer is less than the duration of the second timer.

23. The method according to any one of claims 14 to 22, characterized in that, The first indication information is further used to indicate the first entity.

24. A communication method applied to the dual-connectivity DC scenario, characterized in that, The method is applied to a first communication device, and the method includes: Determining first indication information; Send the first indication information to a second communication device according to network status information, where the first indication information is used to activate the function of a first entity in a third communication device or to deactivate the function of the first entity in the third communication device. The second communication device is a network device in the DC scenario, and the third communication device is a terminal device in the DC scenario.

25. The method according to claim 24, wherein The determining the first indication information includes: Receiving network status information from the second communication device and / or a fourth communication device, where the fourth communication device is a network device in the DC scenario; Determining the first indication information according to the network status information of the second communication device and / or the fourth communication device.

26. The method according to claim 24 or 25, characterized in that, The method further includes: Sending first control information to the second communication device, where the first control information is used to control the second communication device to report the network status information of the second communication device; and / or Sending second control information to a fourth communication device, where the second control information is used to control the fourth communication device to report the network status information of the fourth communication device.

27. The method according to any one of claims 24 to 26, characterized in that, The network status information is congestion status information, and the first indication information is used to activate the function of the first entity.

28. The method according to any one of claims 24 to 26, characterized in that, The network status information is non-congestion status information, and the first indication information is used to deactivate the function of the first entity.

29. The method according to any one of claims 24 to 28, characterized in that, The first indication information further includes identification information of a first radio bearer (RB), where the first RB corresponds to the first entity, and the first RB is any one of the following: a split RB, a duplicate RB, or a dual active protocol stack (DAPS) RB.

30. The method according to any one of claims 24 to 29, characterized in that, The method further includes: Receiving a first report, where the first report is used to indicate the sequence number (SN) of data discarded by the third communication device.

31. The method according to claim 30, wherein The method further includes: Sending a second report, where the second report is used to indicate that the discarded data has been successfully received.

32. A communication device, characterized in that, Including a processor, where the processor is coupled to a memory, the memory is used to store a computer program or instruction, and the processor is used to execute the computer program or instruction in the memory, so that the device executes the method according to any one of claims 1 to 31.

33. A computer-readable storage medium, characterized in that, A computer program or instruction is stored on the computer-readable storage medium, and when the computer program or instruction runs on a computer, the computer executes the method according to any one of claims 1 to 31.

34. A chip system, characterized in that, Including: a processor, configured to call and run a computer program from a memory, so that a communication device equipped with the chip system executes the method according to any one of claims 1 to 31.

35. A computer program product, characterized in that, When the computer program product runs on a computer, the computer executes the method according to any one of claims 1 to 31.

Images