Wireless communication method and related apparatus

Abstract

The embodiment of the application provides a kind of wireless communication method and related device, the wireless communication method includes: receiving first message, first message is used to indicate the PDCP sequence number gap after inquiring PDCP entity switching, first message is associated with network side PDCP sequence number gap;Send second message, second message is used to indicate the first data sent by terminal after PDCP entity switching, first data includes PDCP data PDU.In the above technical scheme, the PDCP sequence number gap after inquiring PDCP entity switching is inquired by first message, and the first data sent by terminal after PDCP entity switching is indicated by second message, so the synchronization of PDCP state variable is realized based on second message.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a wireless communication method and related apparatus. Background Technology

[0002] In various application scenarios, the Packet Data Convergence Protocol (PDCP) entity in the wireless communication system undergoes changes when the terminal and network sides perform services. Examples include: high-speed handover between two base stations; RRC connection reconstruction after a wireless link failure; and bearer changes in 5G dual connectivity. After the PDCP entity changes, it is necessary to ensure the synchronization of PDCP state variables between the terminal and the network side. Summary of the Invention

[0003] This application provides a wireless communication method and related apparatus, the purpose of which is to realize the synchronization of PDCP state variables.

[0004] To achieve the above objectives, this application provides the following technical solution:

[0005] In a first aspect, this application provides a wireless communication method, which may be executed by a terminal, or by a component (such as a circuit, chip, or chip system) configured in the terminal, or by a logic module or software capable of implementing all or part of the terminal's functions. This application does not limit the scope of this method.

[0006] A wireless communication method includes: receiving a first message, the first message indicating a query for a PDCP sequence number gap after a PDCP entity handover, the first message being associated with a PDCP sequence number gap existing on the network side; and sending a second message, the second message indicating the first data sent by the terminal after the PDCP entity handover, the first data including a PDCP data protocol data unit (PDU).

[0007] In the above technical solution, the PDCP sequence number gap after the PDCP entity switch is queried by the first message, and the first data sent by the terminal after the PDCP entity switch is indicated by the second message. Therefore, the synchronization of PDCP state variables is realized based on the second message.

[0008] In one possible implementation, the second message includes the sequence number of the first data.

[0009] In one possible implementation, the first message includes a first PDCP control PDU, the type of which is used to indicate a query of the PDCP sequence number gap after a PDCP entity switch.

[0010] In one possible implementation, the second message includes a second PDCP control PDU, the type of which is used to indicate a query response for the PDCP sequence number gap after the PDCP entity switch.

[0011] In one possible implementation, the wireless communication method further includes sending a third message indicating the capability of a synchronization transmission recovery point.

[0012] Secondly, this application provides a wireless communication method, which can be executed by a network device, or by a component (such as a circuit, chip, or chip system) configured in the network device, or by a logic module or software capable of implementing all or part of the functions of the network device. This application does not limit the scope of the method. The following description uses a network device as an example.

[0013] A wireless communication method includes: sending a first message, the first message indicating a query for a PDCP sequence number gap after a PDCP entity handover, the first message being associated with a PDCP sequence number gap existing on the network side; and receiving a second message, the second message indicating the first data sent by the terminal after the PDCP entity handover, the first data including a PDCP data protocol data unit (PDU).

[0014] In one possible implementation, the second message includes the sequence number of the first data.

[0015] In one possible implementation, the first message includes a first PDCP control PDU, the type of which is used to indicate a query of the PDCP sequence number gap after a PDCP entity switch.

[0016] In one possible implementation, the second message includes a second PDCP control PDU, the type of which is used to indicate a query response for the PDCP sequence number gap after the PDCP entity switch.

[0017] In one possible implementation, associating the first message with the existence of a PDCP sequence number gap on the network side includes: the first message is sent when a PDCP sequence number gap exists on the network side.

[0018] In one possible implementation, the wireless communication method further includes: marking the first data as discarded or not requiring processing based on a second message, wherein the first data is data sent prior to the first data.

[0019] In one possible implementation, the wireless communication method further includes stopping the reordering timer based on a second message.

[0020] In one possible implementation, the wireless communication method further includes: adjusting the processing order of the second data based on the sequence number of the second data, wherein the second data is data transmitted after the first data.

[0021] Thirdly, this application provides a communication device, which includes a transceiver module. The transceiver module is used to receive a first message, which indicates that a PDCP sequence number gap has been queried after a PDCP entity handover. The first message is associated with a PDCP sequence number gap existing on the network side. The transceiver module is used to send a second message, which indicates that the terminal sends the first data after the PDCP entity handover. The first data includes a PDCP data protocol data unit (PDU).

[0022] Fourthly, this application provides a communication device including a transceiver module. The transceiver module is used to send a first message indicating a query for a PDCP sequence number gap after a PDCP entity handover, and the first message is associated with a PDCP sequence number gap existing on the network side; and to receive a second message indicating the first data sent by the terminal after the PDCP entity handover, the first data including a PDCP data protocol data unit (PDU).

[0023] Fifthly, this application provides a communication device including a processor coupled to a memory, which can be used to execute instructions or data in the memory to implement the method in the first aspect above.

[0024] In one possible implementation, the communication device also includes a memory.

[0025] In one possible implementation, the communication device also includes a communication interface, to which the processor is coupled.

[0026] In one implementation, the communication interface can be a transceiver, or an input / output interface.

[0027] In another implementation, the communication device is a chip configured in the terminal. When the communication device is a chip configured in the terminal, the communication interface can be an input / output interface.

[0028] In another implementation, the communication device is a chip configured in a network device. When the communication device is a chip configured in an access network device, the communication interface can be an input / output interface.

[0029] In a sixth aspect, this application provides a communication device including a processor coupled to a memory, which can be used to execute instructions or data in the memory to implement the method in the second aspect above.

[0030] In one possible implementation, the communication device also includes a memory.

[0031] In one possible implementation, the communication device also includes a communication interface, to which the processor is coupled.

[0032] In one implementation, the communication interface can be a transceiver, or an input / output interface.

[0033] In another implementation, the communication device is a chip configured in a network device. When the communication device is a chip configured in a network device, the communication interface can be an input / output interface.

[0034] In a seventh aspect, this application provides a processor, including: an input circuit, an output circuit, and a processing circuit. The processing circuit is used to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method in any of the aspects.

[0035] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0036] Eighthly, this application provides a computer program product comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the methods described in any of the preceding aspects.

[0037] Ninthly, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods of any of the preceding aspects.

[0038] In a tenth aspect, this application provides a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or possible implementations to be executed. The chip system may be composed of a chip or may include chips and other discrete devices. The chip system may include input circuitry or interfaces for transmitting information or data, and output circuitry or interfaces for receiving information or data.

[0039] Eleventhly, a communication system is provided, including the aforementioned terminal and network equipment.

[0040] In one possible implementation, the communication system may also include other devices that communicate with one or more of the terminals and network devices.

[0041] The technical effects of the solutions provided in the second to eleventh aspects can be found in the content of the first aspect. Attached Figure Description

[0042] Figure 1 A schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0043] Figure 2 and Figure 3 This is a schematic diagram of the protocol stack architecture provided in an embodiment of this application;

[0044] Figure 4 A flowchart illustrating the wireless communication method provided in an embodiment of this application;

[0045] Figures 5 to 7 The flowcharts illustrate the execution of wireless communication methods in three application scenarios provided in the embodiments of this application.

[0046] Figure 8 This is a structural example diagram of another communication device disclosed in the embodiments of this application;

[0047] Figure 9 This is a structural example diagram of another communication device disclosed in an embodiment of this application. Detailed Implementation

[0048] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. The terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be a limitation of this application. As used in the specification and appended claims of this application, the singular expressions "a," "an," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, "one or more" refers to one, two, or more; "and / or" describes the relationship between related objects, indicating that three relationships may exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0049] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0050] The "multiple" mentioned in the embodiments of this application refers to two or more. It should be noted that in the description of the embodiments of this application, terms such as "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying order.

[0051] The technical solutions provided in this application can be applied to communication systems, which may include, but are not limited to, the following systems: second-generation (2G) communication systems, third-generation (3G) communication systems, long-term evolution (LTE) systems, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) systems or new radio (NR) systems, 5.5G systems or sixth-generation (6G) systems and future mobile communication systems, vehicle-to-X (V2X); V2X may include vehicle-to-network (V2N), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), etc., long-term evolution-vehicle (LTE-V) technology for vehicle-to-everything (V2V), vehicle-to-everything (V2X), machine-type communication (MTC), and the Internet of Things (IoT). Things (IoT), Ambient Internet of Things (AIOT), Long Term Evolution of Machines (LTE-M), Machine to Machine (M2M), etc.

[0052] The communication system can be applied to scenarios including: terrestrial cellular communication, non-terrestrial network (NTN), satellite communication, high altitude platform station (HAPS) communication, vehicle-to-everything (V2X) communication, integrated access and backhaul (IAB) communication, and reconfigurable intelligent surface (RIS) communication, etc.

[0053] For example, Figure 1 A schematic diagram of an architecture of a communication system provided in an embodiment of this application is shown.

[0054] like Figure 1 As shown, the communication system includes terminal device 100, access network device 200, and core network device 300. Terminal device 100 accesses the data network (DN) through access network device 200 and core network device 300. DN is a network located outside the operator's network. The operator's network can access multiple DNs, and various services can be deployed on DNs, providing data and / or voice services to terminal device 100.

[0055] Terminal device 100 is a device that accesses the network. In this embodiment, the terminal device can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, and smart home. Terminals can take various forms, such as mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality terminal devices, augmented reality terminal devices, wireless terminals in industrial control, vehicle-mounted terminal devices, wireless terminals in autonomous driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, wearable terminal devices, and so on. Terminal equipment may also be referred to as terminals, user equipment (UE), access terminal equipment, vehicle-mounted terminals, industrial control terminals, UE units, UE stations, mobile stations, mobile stations, remote stations, remote terminal equipment, mobile devices, UE terminal equipment, wireless communication equipment, UE agents, or UE devices, etc. Terminals can also be fixed terminals or mobile terminals.

[0056] Access network equipment 200 can be either a radio access network (RAN) device or a wired access network device. The RAN device can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system; it can also be a module or unit that performs some of the functions of a base station, for example, it can be a central unit (CU) or a distributed unit (DU). Here, the CU performs the functions of the base station's radio resource control protocol and packet data convergence protocol (PDCP), and can also perform the functions of the service data adaptation protocol (SDAP); the DU performs the functions of the base station's radio link control layer and medium access control (MAC) layer, and can also perform some or all of the physical layer functions. For specific descriptions of the above protocol layers, please refer to the relevant 3GPP technical specifications. Wireless access network equipment can be macro base stations, micro base stations, indoor stations, relay nodes, or donor nodes, etc. The embodiments of this application do not limit the specific technologies or equipment forms used in the wireless access network equipment.

[0057] The core network (CN) equipment 300 includes, but is not limited to, some or all of the following network elements: authentication server function (AUSF) network element, unified data management (UDM) network element, network repository function (NRF) network element, network exposure function (NEF) network element, application function (AF) network element, policy control function (PCF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, user plane function (UPF) network element, network data analytics function (NWDAF) network element, etc.

[0058] It is understood that the above network elements are examples of one implementation method, and this application does not exclude the possibility that network elements or devices with the above-mentioned network element functions may have other names or other forms in future wireless communication systems. Furthermore, the above-mentioned network elements or functions can be network components in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). As one possible implementation method, the above-mentioned network elements or functions can be implemented by one device, multiple devices working together, or a functional module within a single device; this application does not specifically limit this.

[0059] In some embodiments, the communication system may also include other devices that communicate with the terminal device 100, the access network device 200, and the core network device 300, which is not a limitation of this application.

[0060] To facilitate understanding, the concepts involved in this application will be explained below.

[0061] Protocol stack architecture in 5G.

[0062] An example of a control plane protocol stack is as follows: Figure 2 As shown, the control plane protocol stack is responsible for managing and controlling the connection, and mainly consists of two parts:

[0063] Wireless access network section.

[0064] Both the UE and gNB include radio resource control (RRC) to establish control signaling connections between them. Both the UE and gNB also include packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC), and physical layer (PHY) to provide transmission functions for control plane signaling (such as RRC messages and NAS messages).

[0065] Core network section.

[0066] The UE and the core network control plane network elements (such as AMF) include a non-access stratum (NAS), which is responsible for high-level signaling interaction between the terminal and the core network and realizes key control functions such as mobility management, session management and security authentication.

[0067] An example of a user plane protocol stack is as follows: Figure 3 As shown, the user plane protocol stack focuses on lossless and fast data transmission.

[0068] Both the UE and gNB include PDCP, RLC, MAC, and PHY, providing transmission functions for user plane data.

[0069] Both the UE and gNB also include a Service Data Adaptation Protocol (SDAP) to map QoS flows to the data radio bearer (DRB). Data transmitted via the DRB is also passed to the UPF via the NG-U (next generation – user plane) channel, and then decapsulated and routed to the external network by the UPF.

[0070] The descriptions of the protocol stack architecture, etc., are only for the purpose of facilitating understanding of the technical solutions in this application and do not constitute any limitation on this application.

[0071] In communication systems, the terminal and network sides need to ensure the synchronization of PDCP state variables.

[0072] In one application scenario, the terminal performs high-speed handover between two base stations.

[0073] For example, a user is riding in a high-speed mobile vehicle, such as an autonomous vehicle, traveling in an urban or highway environment and frequently switching between different base stations. In this scenario, the user is also using a terminal to perform services with stringent requirements for the continuity and latency of uplink data transmission. For instance, if the terminal is an AR glasses or XR headset, and the user is using it to run an immersive cloud-rendered AR meeting or cloud game, the terminal needs to continuously upload local high-precision sensor data (such as head posture information) to the cloud server in real time. The cloud server then renders a synchronized virtual scene in real time based on this data and sends back the video stream.

[0074] During communication, if the PDCP entity at the sending end (such as the terminal) actively discards some packet data convergence protocol service data units (PDCP SDUs) that have not yet been submitted to the lower-layer RLC due to reasons such as the timer expires, it will generate and send a PDCP-SN gap report to inform the receiving end (such as the base station) in advance which data packets have been discarded. This avoids the receiving end from starting a reordering timer and waiting unnecessarily when it detects that the sequence number (SN) is discontinuous, thereby effectively reducing data transmission latency.

[0075] When a terminal switches between different base stations, if it is in a handover edge area where the wireless environment is extremely unstable, the PDCP-SN gap report may be lost en route to the source base station (source gNB), and the source base station may fail to receive the report. As a result, when transmitting UE state information (UE context) to the target base station (target gNB), it cannot inform the target base station that "some data packets have been actively discarded by the terminal".

[0076] After the base station handover is complete, the terminal begins sending subsequent data to the target base station. Upon receiving the data, the target base station's PDCP entity discovers a gap in the sequence number (SN) (e.g., the expected SN=X, but the received SN=Y, where Y > X). Since the target base station is unaware of which data packets have been discarded by the terminal, it will, according to standard procedure, start a t-reordering timer to wait for a discarded data packet that will never arrive, resulting in the "t-reordering timer unnecessary waiting" problem.

[0077] During the t-Reordering timer's operation (which can last for hundreds of milliseconds), all subsequent, perfectly normal data packets (such as subsequent head pose data) are stuck in the target base station's buffer and cannot be delivered to the upper-layer application. This will immediately cause a service interruption that the user can perceive, such as the AR screen freezing instantly or being severely out of sync with the user's movements, causing dizziness and a very poor service experience.

[0078] In another application scenario, RRC connection re-establishment is performed after the terminal experiences a radio link failure (RLF) problem.

[0079] During communication, the terminal may encounter RLF issues due to reasons such as instantaneous deep signal fading or T304 timer timeout. In this case, the terminal will stop communicating with the original base station and attempt to initiate an RRC connection reconstruction process on the same or a new cell to restore service.

[0080] If, just moments before an RLF occurs, the terminal has just dropped some PDCP SDUs due to a timeout and generated a PDCP-SN gap report, this report is highly likely to be lost in the chaotic radio environment of an RLF and will never reach any base station. When the terminal rebuilds its RRC connection and resumes data transmission on a new cell (e.g., sending data with SN=Y), the new base station will find that its expected SN (e.g., X) does not match the SN sent by the terminal (Y > X). The new base station will also start a t-Reordering timer, which will lead to the "t-Reordering timer unnecessarily waiting" problem, causing a severe delay in service recovery.

[0081] Another application scenario involves bearer changes in 5G dual connectivity (DC).

[0082] In a 5G dual-connectivity architecture, a terminal can simultaneously connect to both the master node (MN) and the secondary node (SN). The PDCP protocol termination point of the data radio bearer (DRB) can be either the MN or the SN. During network operation, RRC signaling (such as RRC connection reconfiguration messages) can trigger bearer changes, for example, changing a "bearer terminated by the SN" to a "bearer terminated by the MN".

[0083] If the terminal discarded the PDCP SDU before the change (when data was being sent to the SN) and the PDCP-SN gap report was also lost; after the change, the terminal starts sending data to the new termination point (MN). At this time, the MN, as the new PDCP receiving entity, will also experience the "t-Reordering timer unnecessarily waiting" problem due to the PDCP state asynchrony, affecting service recovery.

[0084] Based on this, embodiments of this application provide a wireless communication method to achieve synchronization of PDCP state variables.

[0085] Figure 4 A flowchart illustrating the wireless communication method provided in an embodiment of this application is shown.

[0086] like Figure 4 As shown, the wireless communication method includes:

[0087] S401, The network device sends the first message to the terminal, and the terminal receives the first message accordingly.

[0088] The first message is used to indicate the PDCP sequence number gap after the PDCP entity handover. The first message is also associated with the existence of PDCP sequence number gaps on the network side.

[0089] For example, associating the first message with the existence of a PDCP sequence number gap on the network side includes: the first message is sent when a PDCP sequence number gap exists at the network layer. That is, the network device sends the first message when it determines that a PDCP sequence number gap exists at the network layer.

[0090] In this embodiment, the first message is associated with a PDCP sequence number gap on the network side, ensuring that the first message is only activated and sent when a data gap actually occurs and there is a potential delay risk, thus achieving "on-demand" triggering. Furthermore, the network device sending the first message constitutes an active query on the network side, replacing passive and lengthy waiting with proactive and rapid querying.

[0091] The following explains the existence of PDCP sequence number gaps in the network layer:

[0092] In some application scenarios, the terminal sends uplink data to the network device, which includes PDCP data PDU; the uplink data sent by the terminal is not a one-time event, but is sent continuously.

[0093] In some cases, a handover occurs between the network-side PDCP entities. Before the handover is complete, the terminal loses certain PDCP data PDUs, or the corresponding PDCP SDUs. The terminal generates a PDCP-SN gap report, but this report fails to be sent to the network device. The terminal subsequently continues to send uplink data to the network device, including PDCP data PDUs. The network device cannot identify the lost uplink data through the PDCP-SN gap report, and the first uplink data received subsequently has a PDCP sequence number gap with the expected uplink data.

[0094] For example, a network device can obtain PDCP receive status variables (such as RX_DELIV, the next expected sequential COUNT value) based on the terminal context, obtain the PDCP sequence number of the next expected consecutive data packet (including PDCP data PDU) based on the PDCP receive status variables, and compare the PDCP sequence number of the next expected consecutive data packet with the PDCP sequence number of the first received uplink data to determine whether there is a PDCP sequence number gap.

[0095] For example: if the PDCP sequence number of the first received uplink data is Y, and the PDCP sequence number of the next expected consecutive data packet is X, and Y > X, it is determined that there is a data gap between sequence numbers X and Y.

[0096] Optionally, RX_DELIV can represent the next expected sequential delivery value of the COUNT. That is, all PDCP SDUs with COUNT values ​​less than RX_DELIV have already been delivered to the upper layer in sequence. Therefore, both RX_DELIV and the next expected sequential delivery value of the COUNT can indicate the PDCP sequence number of the next consecutive data packet expected to be received.

[0097] In some embodiments, the first message indicating the query of the PDCP sequence number gap after the PDCP entity switch includes: the first message includes a first PDCP control PDU, the type of which is used to indicate the query of the PDCP sequence number gap after the PDCP entity switch.

[0098] For example, the first PDCP controls the PDU type as PDU Type “101”.

[0099] PDU Type “101” is a reserved type. This embodiment uses this type to indicate the query of the PDCP sequence number gap after the PDCP entity switch, which realizes the reuse of PDU data type, avoids resource waste, and also avoids scheme complexity.

[0100] S402, The terminal sends a second message to the network device, and the corresponding network device receives the second message.

[0101] The terminal's PDCP layer receives and parses the first message, identifies it as being used for post-handover gap query, and can then send the second message.

[0102] The second message indicates the first data sent by the terminal after the PDCP entity handover. This first data includes PDCP data PDUs. In other words, the first data sent by the terminal refers to the first data sent by the terminal after the network side completes the PDCP entity handover.

[0103] For example, the second message used to indicate the first data sent by the terminal includes: the second message includes the PDCP sequence number of the first data sent by the terminal.

[0104] As another example, the second message used to indicate the first data sent by the terminal includes: the second message includes the first data sent by the terminal, or indication information of the first data, which may directly or indirectly indicate the PDCP sequence number of the first data.

[0105] In some embodiments, the first data sent by the second message indicating the terminal includes: the second message includes a second PDCP control PDU, and the type of the first PDCP control PDU is used to indicate the query response of the PDCP sequence number gap after the PDCP entity switch.

[0106] For example, the type of the second PDCP control PDU is PDU Type "110".

[0107] PDU Type “110” is also a reserved type. This embodiment uses this type to indicate the query response of the PDCP sequence number gap after the PDCP entity switch, realizing the reuse of PDU data type, avoiding resource waste, and also avoiding scheme complexity.

[0108] As another example, the payload of the second PDCP control PDU includes a first field, which may include the COUNT value (i.e., a 32-bit complete sequence number) of the first data transmitted by the terminal. Optionally, the COUNT value is defined as a transmission recovery point (TRP).

[0109] Compared to retransmitting a complete PDCP SN gap report that may contain complex bitmaps, the terminal replies with a lightweight signaling message containing only a single TRP value, which greatly saves uplink radio resources and UE power consumption, achieving "minimized communication overhead".

[0110] In this embodiment, the PDCP sequence number gap after the PDCP entity switch is queried through the first message, and the first data sent by the terminal after the PDCP entity switch is indicated through the second message. Therefore, the synchronization of PDCP state variables is achieved based on the second message.

[0111] In other embodiments, before performing step S401, the terminal may also send a third message to the network device, and the network device receives the third message. The third message is used to indicate the capability of the synchronization transmission recovery point.

[0112] For example, when a terminal initially accesses the network, it reports its ability to support this "adaptive transmission recovery point synchronization mechanism," i.e., the ability to synchronize transmission recovery points, to the network device via a third message.

[0113] Optionally, the third message may be RRC signaling, but this does not constitute a limitation.

[0114] Optionally, if the network device receives a third message indicating that the terminal has the capability to synchronize transmission recovery points, it can configure and activate the function corresponding to the scheme provided in the embodiments of this application for the first radio bearer through RRC signaling.

[0115] A wireless bearer refers to the data transmission path between the terminal and the network side. For example, a first wireless bearer refers to a data channel that is sensitive to latency and uses acknowledged mode (AM) transmission, such as low-latency AM DRB (Acknowledged Mode Data Radio Bearer), the "attitude information" uplink bearer of XR / AR headsets, and the "control signaling and real-time stream" bearer of cloud gaming / cloud rendering conferencing.

[0116] In other embodiments, after receiving the second message, the network device may also perform at least one of the following steps:

[0117] S403, Stop the reordering timer based on the second message.

[0118] The network side detects a SN gap, sends the first message, and starts a reordering timer. During the timer's duration, the network side waits for missing earlier data packets. The purpose of this is to allow the network side to receive out-of-order data packets during the timer's operation. Once the timer expires, the network device delivers the currently ordered consecutive data packets to the upper layer for processing. As can be seen from the foregoing, the terminal lost some data packets, therefore the duration of the reordering timer is an unnecessary waiting period. After the network device receives the second message, it stops the reordering timer, thus eliminating this unnecessary waiting.

[0119] S404. The first data is marked as discarded or does not need to be processed based on the second message. The first data is the data sent before the first data.

[0120] The network device receives the second message, obtains the PDCP sequence number of the first data sent by the terminal after the PDCP entity handover based on the second message, determines that data packets with a PDCP sequence number smaller than the PDCP sequence number are the first data, and determines that the first data does not need to wait any longer, and marks them as "discarded" or "no need to process".

[0121] S405. Adjust the processing order of the second data based on the sequence number of the second data, where the second data is the data sent after the first data.

[0122] Based on the second message, the network device can also adjust the PDCP receive window and mark all data packets in the buffer with a COUNT value greater than or equal to TRP (i.e., the second data, such as SN=Y and its subsequent packets) as ordered. This ordered order is the ascending order of the PDCP sequence numbers of the second data, which is the processing order of the second data. The second data is then delivered to the upper layer for processing according to this order. TRP indicates the PDCP sequence number of the first data sent by the terminal after the PDCP entity handover. In this way, the congestion of the service data flow is immediately relieved. Furthermore, since the reordering timer is stopped immediately after receiving the second message, data delivery to the upper layer can resume within the time of a single signaling interaction, completely resolving the service delay problem caused by the loss of intermittent reports.

[0123] This application does not limit the execution order of steps S403, S404 and S405; the three steps can be executed in parallel or in a specific order.

[0124] Application scenarios for PDCP entity handover on the network side include: high-speed handover between two base stations by the terminal, RRC connection reconstruction after a terminal experiences a radio link failure, and bearer changes in 5G dual connectivity. The following sections will discuss these three application scenarios in conjunction with... Figures 5 to 7 The wireless communication method provided in this embodiment will be described in three application scenarios.

[0125] For example, Figure 5 A flowchart illustrating a wireless communication method in a mobile terminal scenario is shown.

[0126] like Figure 5 As shown, the wireless communication method includes:

[0127] S501, the terminal and the source base station communicate to perform services.

[0128] For example, this service is one that has stringent requirements for the continuity and latency of uplink data transmission, such as the uplink of "posture information" for XR / AR headsets, and cloud gaming / cloud rendering conferencing services.

[0129] S502. The source base station sends a handover command to the terminal. Correspondingly, the terminal receives the handover command, which indicates that the source base station is to be switched to the target base station.

[0130] During communication, the source base station selects the target base station based on measurement reports, load conditions, and policies. The source base station sends a handover command to the terminal, instructing it to switch from the source base station to the target base station. The terminal receives the handover command and executes the handover. For details on the source base station's selection of the target base station and the terminal's execution of the base station handover, please refer to the relevant 3GPP protocols; they will not be elaborated upon here.

[0131] The terminal discards data packets, and a PDCP-SN gap report loss occurs, thus the source base station fails to obtain the PDCP-SN gap report. For an explanation of the PDCP-SN gap report, please refer to the previous text; it will not be repeated here.

[0132] S503, The source base station synchronizes the terminal status with the target base station.

[0133] For example, the source base station can send the terminal's context to the target base station to synchronize the terminal's state with the target base station. If the source base station does not successfully receive the PDCP-SN gap report, it cannot inform the target base station that "some data packets have been dropped by the terminal".

[0134] S504: The target base station detected a gap in the uplink data packet sequence number.

[0135] After the source base station is switched to the target base station, the terminal continues to send uplink data packets for the service to the target base station. Because the terminal has lost some PDCP data PDUs, or the PDCP SDUs corresponding to the PDCP data PDUs, the target base station will detect gaps in the uplink data packet sequence numbers.

[0136] After the target base station detects a gap in the uplink data packet sequence number, steps S505 and S506 can be executed respectively.

[0137] S505, The target base station starts the reordering timer.

[0138] S506, The target base station sends the first message to the terminal, and the corresponding terminal receives the first message.

[0139] The first message is used to indicate the PDCP sequence number gap after the PDCP entity switch.

[0140] For an explanation of step S506, please refer to step S401 above; it will not be repeated here.

[0141] S507. The terminal sends a second message to the target base station, and the target base station receives the second message.

[0142] The second message is used to indicate the first data sent by the terminal after the PDCP entity handover. The first data includes PDCP data PDU.

[0143] For an explanation of step S507, please refer to step S402 above, which will not be repeated here.

[0144] After the target base station receives the second message, it can execute steps S508 to S510 respectively. The execution order of steps S508 to S510 is not limited.

[0145] S508, Target base station stop reordering timer.

[0146] For an explanation of step S506, please refer to step S403 above, which will not be repeated here.

[0147] S509. The target base station marks the first data as discarded or not requiring processing, and the first data is sent before the first data.

[0148] For an explanation of step S506, please refer to step S404 above, which will not be repeated here.

[0149] S510: The target base station adjusts the processing order of the second data based on the sequence number of the second data, and the second data is sent after the first data.

[0150] For an explanation of step S506, please refer to step S405 above, which will not be repeated here.

[0151] In this embodiment of the application, in a scenario where the terminal performs high-speed mobile handover between two base stations, after the target base station detects a gap in the uplink data packet sequence number, it queries the PDCP sequence number gap after the PDCP entity handover through the first message, and can obtain the first data sent by the terminal after the PDCP entity handover through the second message. Therefore, the synchronization of the PDCP state variables is achieved based on the second message.

[0152] For example, Figure 6 A flowchart illustrating the wireless communication method in the RRC connection reconstruction scenario is shown.

[0153] like Figure 6 As shown, the wireless communication method includes:

[0154] S601, the terminal and base station A communicate to perform services.

[0155] This service is not limited to services with stringent requirements for the continuity and latency of uplink data transmission.

[0156] S602, The terminal detected a wireless link failure.

[0157] During communication with base station A, the terminal may encounter a wireless link failure due to reasons such as transient deep signal fading or T304 timer timeout. In this case, the terminal will cease communication with base station A and attempt to initiate an "RRC connection reconstruction" procedure on the same or a new cell to restore service. For example, the same or new cell mentioned here may refer to the cell of base station B.

[0158] The terminal discarded data packets, and a PDCP-SN gap report loss occurred. As a result, base station A failed to successfully obtain the PDCP-SN gap report. The explanation of the PDCP-SN gap report is provided above and will not be repeated here.

[0159] S603, The terminal successfully re-established the connection on base station B.

[0160] For example, the RRC connection reconstruction process includes:

[0161] The terminal sends an RRC reestablishment request to base station B. After receiving the request, base station B requests the terminal's context from base station A. If base station B successfully obtains the terminal's context, it sends an RRC reestablishment message. The terminal replies with an RRC reestablishment complete message to restore the connection and services.

[0162] Since base station A did not successfully obtain the PDCP-SN gap report, the context of the terminal obtained by base station B from base station A cannot indicate that "some data packets have been dropped by the terminal".

[0163] S604, Base Station B detected a gap in the uplink data packet sequence number.

[0164] After base station A switches to base station B, the terminal continues to send uplink data packets for its services to base station B. Because the terminal loses some PDCP data PDUs, or the PDCP SDUs corresponding to those PDUs, base station B will detect gaps in the uplink data packet sequence numbers.

[0165] After base station B detects a gap in the uplink data packet sequence number, steps S605 and S606 can be executed respectively.

[0166] S605, Base Station B starts the reordering timer.

[0167] S606, Base station B sends the first message to the terminal, and the corresponding terminal receives the first message.

[0168] The first message is used to indicate the PDCP sequence number gap after the PDCP entity switch.

[0169] For an explanation of step S606, please refer to step S402 above, which will not be repeated here.

[0170] S607. The terminal sends a second message to base station B, and correspondingly, base station B receives the second message.

[0171] The second message is used to indicate the first data sent by the terminal after the PDCP entity handover. The first data includes PDCP data PDU.

[0172] For an explanation of step S607, please refer to step S402 above, which will not be repeated here.

[0173] After receiving the second message, base station B can execute steps S608 to S610 respectively. The execution order of steps S608 to S610 is not limited.

[0174] S608, Base Station B Stop Reordering Timer.

[0175] For an explanation of step S608, please refer to step S403 above, which will not be repeated here.

[0176] S609, Base Station B marks the first data as discarded or not requiring processing, and the first data is sent before the first data.

[0177] For an explanation of step S609, please refer to step S404 above, which will not be repeated here.

[0178] S610, Base Station B adjusts the processing order of the second data based on the sequence number of the second data, and the second data is sent after the first data.

[0179] For an explanation of step S610, please refer to step S405 above, which will not be repeated here.

[0180] In this embodiment of the application, in the RRC connection reconstruction scenario, after the base station B detects a gap in the uplink data packet sequence number, it queries the PDCP sequence number gap after the PDCP entity handover through the first message, and can obtain the first data sent by the terminal after the PDCP entity handover through the second message. Therefore, the synchronization of the PDCP state variables is realized based on the second message.

[0181] For example, Figure 7 A flowchart illustrating the wireless communication method under the bearer change scenario in 5G dual connectivity is presented.

[0182] like Figure 7 As shown, the wireless communication method includes:

[0183] S701, the decision of the main base station and the auxiliary base station is to change the data bearer of the auxiliary base station to the main base station.

[0184] For example, in scenarios where the network side senses changes in signal quality, needs to perform load balancing, or where business requirements (such as starting a high-reliability, low-latency service) change, there is a need to change the data bearer.

[0185] The network side can make change decisions based on factors such as measurement reports. In step S701, the terminal and the auxiliary base station execute services, and the primary base station and the auxiliary base station decide, based on the measurement report, that the data bearer of the auxiliary base station be changed to the primary base station.

[0186] It is understandable that the change of the data bearer of the secondary base station to the primary base station as indicated in step S701 is only an example and does not constitute a limitation. For example, the data bearer change provided in this embodiment can also be: a service that was originally carried independently by the secondary base station is changed to a "split bearer" that is jointly handled by the primary and secondary base stations; the service executed by the primary base station is changed to be executed by the secondary base station.

[0187] S702, The primary base station sends an RRC command to the terminal to instruct the secondary base station to change its data bearer to the primary base station.

[0188] For example, the RRC signaling can be an RRC connection reconfiguration message (RRCReconfiguration); after receiving the RRC signaling, the terminal will apply the new configuration, complete random access with the cell of the main base station, and establish a radio link.

[0189] The terminal discarded data packets, and a PDCP-SN gap report loss issue occurred. As a result, the secondary base station failed to successfully obtain the PDCP-SN gap report. For an explanation of the PDCP-SN gap report, please refer to the previous text; it will not be repeated here.

[0190] The primary base station and the secondary base station can also exchange terminal context. Since the secondary base station did not successfully obtain the PDCP-SN gap report, the terminal context obtained by the primary base station from the secondary base station cannot indicate that "some data packets have been dropped by the terminal".

[0191] S703: The main base station detected a gap in the uplink data packet sequence number.

[0192] The terminal continues to send uplink data packets for the service to the main base station. Because the terminal has lost some PDCP data PDUs, or PDCP SDUs corresponding to PDCP data PDUs, the main base station will detect gaps in the uplink data packet sequence numbers.

[0193] After the main base station detects a gap in the uplink data packet sequence number, it can execute steps S704 and S705 respectively.

[0194] S704, The main base station starts the reordering timer.

[0195] S705: The main base station sends the first message to the terminal, and the corresponding terminal receives the first message.

[0196] The first message is used to indicate the PDCP sequence number gap after the PDCP entity switch.

[0197] S706: The terminal sends a second message to the main base station, and the main base station receives the second message accordingly.

[0198] The second message is used to indicate the first data sent by the terminal after the PDCP entity handover. The first data includes PDCP data PDU.

[0199] After receiving the second message, the main base station can execute steps S707 to S709 respectively, and the execution order of steps S707 to S709 is not limited.

[0200] S707, Main base station stop reordering timer.

[0201] For an explanation of step S707, please refer to step S403 above, which will not be repeated here.

[0202] S708, the main base station marks the first data as discarded or not requiring processing, and the first data is sent before the first data.

[0203] For a description of step S708, please refer to step S404 above, which will not be repeated here.

[0204] S709: The main base station adjusts the processing order of the second data based on the sequence number of the second data, and the second data is sent after the first data.

[0205] For an explanation of step S709, please refer to step S405 above, which will not be repeated here.

[0206] In this embodiment of the application, in the bearer change scenario of 5G dual connectivity, after the main base station (the changed base station) detects a gap in the uplink data packet sequence number, it queries the PDCP sequence number gap after the PDCP entity switch through the first message, and can know the first data sent by the terminal after the PDCP entity switch through the second message. Therefore, the synchronization of PDCP state variables is realized based on the second message.

[0207] Figure 8 This is a schematic block diagram of a communication device provided in an embodiment of this application.

[0208] like Figure 8As shown, the communication device 800 may include a communication module 820. The communication module 820 can implement corresponding communication functions, which can be internal communication functions of the communication device 800 or communication functions between the communication device 800 and other devices. Optionally, the communication module 820 may also be referred to as a communication interface, transceiver module, or transceiver unit.

[0209] Optionally, the communication device 800 further includes a processing module 810. The processing module 810 can perform corresponding processing functions, and optionally, the processing module 810 can also be referred to as a processing unit.

[0210] Optionally, the communication device 800 further includes a storage module, which can be used to store instructions and / or data; the processing module 810 can read the instructions and / or data in the storage module so that the communication device 800 can implement the aforementioned method embodiments.

[0211] In one possible design, the communication device 800 may correspond to the terminal in the above method embodiments or a component (such as a circuit, chip, or chip system) configured in the terminal. The communication device 800 can be used to execute the steps or processes performed by the terminal in any of the above method embodiments.

[0212] For example, the communication module 820 is used to receive a first message, which indicates that a PDCP sequence number gap has been queried after the PDCP entity handover, and the first message is associated with the existence of a PDCP sequence number gap on the network side; and to send a second message, which indicates the first data sent by the terminal after the PDCP entity handover, the first data including PDCP data PDU.

[0213] For example, the second message includes the sequence number of the first data item.

[0214] For example, the first message includes a first PDCP control PDU, the type of which is used to indicate the query of the PDCP sequence number gap after the PDCP entity switch.

[0215] For example, the second message includes a second PDCP control PDU, the type of which is used to indicate a query response for the PDCP sequence number gap after the PDCP entity switch.

[0216] For example, the communication module 820 is also used to send a third message indicating the capability of a synchronization transmission recovery point.

[0217] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0218] In one possible design, the communication device 800 may correspond to a network device or a functional unit within a network device in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured within a network device. The communication device 800 can be used to execute the steps or processes performed by the network device in any of the above method embodiments.

[0219] For example, the communication module 820 is used to send a first message, which indicates the query of the PDCP sequence number gap after the PDCP entity handover, and the first message is associated with the existence of a PDCP sequence number gap on the network side; and to receive a second message, which indicates the first data sent by the terminal after the PDCP entity handover, the first data including PDCP data PDU.

[0220] For example, the second message includes the sequence number of the first data item.

[0221] For example, the first message includes a first PDCP control PDU, the type of which is used to indicate the query of the PDCP sequence number gap after the PDCP entity switch.

[0222] For example, the second message includes a second PDCP control PDU, the type of which is used to indicate a query response for the PDCP sequence number gap after the PDCP entity switch.

[0223] For example, the association of the first message with the existence of a PDCP sequence number gap on the network side includes: the first message is sent when a PDCP sequence number gap exists on the network side.

[0224] For example, the processing module 810 is also used to mark the first data as discarded or not requiring processing based on the second message, wherein the first data is data sent before the first data.

[0225] For example, the processing module 810 is also used to stop the reordering timer based on the second message.

[0226] For example, the processing module 810 is also used to adjust the processing order of the second data based on the sequence number of the second data, where the second data is data sent after the first data.

[0227] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0228] Figure 9 This is another schematic block diagram of the communication device 900 provided in the embodiments of this application.

[0229] The communication device 900 can be a terminal, network device, chip, chip system, or processor that implements the above methods. The communication device 900 can be used to implement the methods described in the above method embodiments; please refer to the descriptions in the above method embodiments for details.

[0230] like Figure 9 As shown, the communication device 900 may include one or more processors 910, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 910 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 900 (such as a base station, baseband chip, user, or user chip), execute software programs, and process data from the software programs.

[0231] In an alternative design, the processor 910 may also store instructions and / or data, which can be executed by the processor 910 to cause the communication device 900 to perform the methods described in the above method embodiments.

[0232] In another alternative design, the communication device 900 may include a communication interface 920 for implementing receiving and transmitting functions. For example, the communication interface 920 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0233] Optionally, the communication device 900 may include one or more memories 930, which may store instructions that can be executed on the processor 910, causing the communication device 900 to perform the methods described in the above method embodiments. Optionally, the memories 930 may also store data. Optionally, the processor 910 may also store instructions and / or data. The processor 910 and the memories 930 may be provided separately or integrated together.

[0234] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0235] In one implementation, the communication device 900 may correspond to the terminal in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal in the above method embodiments. The processor 910 may be used to execute instructions stored in the memory 930, and when the processor 910 executes the instructions stored in the memory, the processor 910 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal.

[0236] In another implementation, the communication device 900 may correspond to the network device in the above method embodiments and may be used to execute the various steps and / or processes executed by the network device in the above method embodiments. The processor 910 may be used to execute instructions stored in the memory 930, and when the processor 910 executes the instructions stored in the memory, the processor 910 is used to execute the various steps and / or processes of the above method embodiments corresponding to the access network device.

[0237] It is understood that the aforementioned processor can be one or more chips. For example, the processor can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0238] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0239] This application also provides a computer-readable storage medium storing instructions that, when executed on one or more computing devices, cause the one or more computing devices to perform the wireless communication method described in the above embodiments.

[0240] Computer-readable storage media can be non-transitory computer-readable storage media, such as read-only memory (ROM), random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage devices.

[0241] This application also provides a computer program product. When executed by one or more computing devices, the computer program product enables the computing devices to execute any of the aforementioned wireless communication methods. The computer program product can be a software installation package. When any of the aforementioned wireless communication methods needs to be used, the computer program product can be downloaded and executed on a computer.

[0242] This application also provides a processor, including: an input circuit, an output circuit, and a processing circuit. The processing circuit receives signals through the input circuit and transmits signals through the output circuit, causing the processor to execute the wireless communication method described in the above embodiments.

[0243] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be output to, for example, but not limited to, a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0244] This application also provides a chip system including one or more processors for calling and executing instructions stored in a memory, thereby causing the wireless communication method described in the above embodiments to be executed. The chip system may be composed of a chip or may include chips and other discrete devices. The chip system may include input circuitry or interfaces for transmitting information or data, and output circuitry or interfaces for receiving information or data.

[0245] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0246] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

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

[0248] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0249] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A wireless communication method, characterized in that, include: Receive a first message, which is used to indicate the PDCP sequence number gap after the PDCP entity handover, and the first message is associated with the existence of a PDCP sequence number gap on the network side. A second message is sent, which is used to indicate the first data sent by the terminal after the PDCP entity handover, the first data including PDCP data protocol data unit (PDU).

2. The method according to claim 1, characterized in that, The second message includes the sequence number of the first data.

3. The method according to claim 1 or 2, characterized in that, The first message includes a first PDCP control PDU, the type of which is used to indicate the query of the PDCP sequence number gap after the PDCP entity switch.

4. The method according to claim 1 or 2, characterized in that, The second message includes a second PDCP control PDU, the type of which is used to indicate the query response for the PDCP sequence number gap after the PDCP entity switch.

5. The method according to claim 1 or 2, characterized in that, Also includes: A third message is sent, which indicates the capability of the synchronization transmission recovery point.

6. A wireless communication method, characterized in that, include: Send a first message, which is used to indicate the PDCP sequence number gap after the PDCP entity handover. The first message is associated with the existence of a PDCP sequence number gap on the network side. A second message is received, which is used to indicate the first data sent by the terminal after the PDCP entity handover, the first data including PDCP data protocol data unit (PDU).

7. The method according to claim 6, characterized in that, The second message includes the sequence number of the first data.

8. The method according to claim 6 or 7, characterized in that, The first message includes a first PDCP control PDU, the type of which is used to indicate the query of the PDCP sequence number gap after the PDCP entity switch.

9. The method according to claim 6 or 7, characterized in that, The second message includes a second PDCP control PDU, the type of which is used to indicate the query response for the PDCP sequence number gap after the PDCP entity switch.

10. The method according to claim 6 or 7, characterized in that, The association of the first message with the existence of a PDCP sequence number gap on the network side includes: the first message is sent when the PDCP sequence number gap exists on the network side.

11. The method according to claim 6 or 7, characterized in that, Also includes: The first data is marked as discarded or does not need to be processed based on the second message, and the first data is the data sent before the first data.

12. The method according to claim 6 or 7, characterized in that, Also includes: The reordering timer is stopped based on the second message.

13. The method according to claim 6 or 7, characterized in that, Also includes: The processing order of the second data is adjusted based on the sequence number of the second data, where the second data is data sent after the first data.

14. A communication device, characterized in that, The communication device includes a processing module and a transceiver module, and is used to perform the method as described in any one of claims 1 to 13.

15. A communication device, characterized in that, include: Memory, used to store computer instructions; A processor for executing a computer program or computer instructions stored in the memory, causing the communication device to perform the method as described in any one of claims 1 to 13.

16. A communication system, characterized in that, Includes the communication device as described in claim 15.

17. A computer storage medium, characterized in that, Used to store a computer program, which, when executed, is used to implement the method as described in any one of claims 1 to 13.

18. A computer program product, characterized in that, Its computer program, when the computer program is run, causes the method as described in any one of claims 1 to 13.

Images