Intra-cell switching method and device and storage medium

Abstract

The invention relates to an intra-cell switching method and device and a storage medium, and the method comprises the steps: transmitting a reconfiguration message to terminal equipment under the condition that the current condition of the terminal equipment meets the triggering condition of intra-cell switching; the uplink scheduling, the downlink DRB scheduling, the uplink HARQ transmission and the downlink DRB HARQ transmission of the terminal equipment are stopped; receiving uplink data from the terminal equipment and an identifier of the terminal equipment; under the condition that the uplink data is first data and the identifier of the terminal equipment is the identifier before switching, an RLC state report corresponding to the first data is sent to the terminal equipment through the SRB, and the first data is data of which the feedback RLC state report is not received in the data sent to the access network equipment through the SRB before the terminal equipment receives the reconfiguration message; the RLC state report corresponding to the first data is used for triggering the terminal equipment to process the reconfiguration message so as to complete intra-cell switching. According to the invention, the success rate of intra-cell switching can be improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus and storage medium for intra-cell handover. Background Technology

[0002] Intra-cell handover refers to the handover performed by a terminal device within the same cell. During intra-cell handover, after the access network device sends a reconfiguration message to the terminal device, it suspends all uplink and downlink scheduling and Hybrid Automatic Repeat Request (HARQ) transmissions for the terminal device between sending the reconfiguration message to the terminal device and receiving the reconfiguration completion message from the terminal device.

[0003] If the terminal device does not correctly receive the Radio Link Control (RLC) status report corresponding to the data transmitted via the Signalling Radio Bearer (SRB) before receiving the reconfiguration message, the access network device will be unable to send these RLC status reports to the terminal device because the access network device has suspended all uplink and downlink scheduling and HARQ transmissions to the terminal device.

[0004] In cases where the terminal device needs to confirm receipt of these RLC status reports before it can process the reconfiguration message, the access network device is unable to send these RLC status reports to the terminal device, causing the terminal device to be unable to process the reconfiguration message, thus resulting in a handover failure within the cell. Summary of the Invention

[0005] This application provides an intra-cell handover method, apparatus, and storage medium to improve the success rate of intra-cell handover.

[0006] In a first aspect, this application provides an intra-cell handover method, applied to access network equipment, the method comprising:

[0007] If the current conditions of the first terminal device meet the triggering conditions for intra-cell handover, a reconfiguration message is sent to the first terminal device, where the first terminal device is any terminal device within the coverage area of ​​the access network device.

[0008] The uplink scheduling, downlink data radio bearer (DRB) scheduling, uplink hybrid automatic repeat request (HARQ) transmission, and downlink DRB HARQ transmission of the first terminal device are suspended.

[0009] Receive a random access message from the first terminal device, the random access message carrying uplink data and the identifier of the first terminal device;

[0010] When the uplink data is the first data and the identifier of the first terminal device is the first identifier, the radio link control (RLC) status report corresponding to the first data is sent to the first terminal device via the signaling radio bearer (SRB). The first data is the data in the second data for which the first terminal device has not received the corresponding RLC status report. The second data is the data sent by the first terminal device to the access network device via the SRB before receiving the reconfiguration message. The first identifier is the identifier of the first terminal device before the intra-cell handover. The RLC status report corresponding to the first data is used to trigger the first terminal device to process the reconfiguration message to complete the intra-cell handover.

[0011] As one possible implementation, the method further includes:

[0012] If the RLC sequence number SN carried in the random access message is a first preset value, the uplink data is determined to be reconfiguration completion information;

[0013] Rebuild the RLC connection and the PDCP connection with the first terminal device.

[0014] As one possible implementation, the method further includes:

[0015] If the identifier of the first terminal device carried in the random access message is the first identifier, the first identifier is determined to be the identifier of the first terminal device after the intra-cell handover.

[0016] As one possible implementation, the method further includes:

[0017] If the identifier of the first terminal device carried in the random access message is a second identifier, the second identifier is determined to be the identifier of the first terminal device after intra-cell handover, and the second identifier is the reconfiguration identifier of the first terminal device.

[0018] As one possible implementation, the current conditions of the first terminal device satisfy the triggering conditions for intra-cell handover, including:

[0019] The PDCP count value of the first terminal device is a second preset value; or

[0020] The DRB identifier of the first terminal device is a third preset value.

[0021] As one possible implementation, the method further includes:

[0022] Restore uplink scheduling, downlink DRB scheduling, uplink HARQ transmission, and downlink DRBHARQ transmission of the first terminal device.

[0023] Secondly, this application provides an intra-cell handover device, applied to access network equipment, including a memory, a transceiver, and a processor:

[0024] The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:

[0025] If the current conditions of the first terminal device meet the triggering conditions for intra-cell handover, a reconfiguration message is sent to the first terminal device, where the first terminal device is any terminal device within the coverage area of ​​the access network device.

[0026] The uplink scheduling, downlink data radio bearer (DRB) scheduling, uplink hybrid automatic repeat request (HARQ) transmission, and downlink DRB HARQ transmission of the first terminal device are suspended.

[0027] Receive a random access message from the first terminal device, the random access message carrying uplink data and the identifier of the first terminal device;

[0028] When the uplink data is the first data and the identifier of the first terminal device is the first identifier, the radio link control (RLC) status report corresponding to the first data is sent to the first terminal device via the signaling radio bearer (SRB). The first data is the data in the second data for which the first terminal device has not received the corresponding RLC status report. The second data is the data sent by the first terminal device to the access network device via the SRB before receiving the reconfiguration message. The first identifier is the identifier of the first terminal device before the intra-cell handover. The RLC status report corresponding to the first data is used to trigger the first terminal device to process the reconfiguration message to complete the intra-cell handover.

[0029] In one possible implementation, the processor is also configured to read a computer program from the memory and perform the following operations:

[0030] If the RLC sequence number SN carried in the random access message is a first preset value, the uplink data is determined to be reconfiguration completion information;

[0031] Rebuild the RLC connection and the PDCP connection with the first terminal device.

[0032] In one possible implementation, the processor is also configured to read a computer program from the memory and perform the following operations:

[0033] If the identifier of the first terminal device carried in the random access message is the first identifier, the first identifier is determined to be the identifier of the first terminal device after the intra-cell handover.

[0034] In one possible implementation, the processor is also configured to read a computer program from the memory and perform the following operations:

[0035] If the identifier of the first terminal device carried in the random access message is a second identifier, the second identifier is determined to be the identifier of the first terminal device after intra-cell handover, and the second identifier is the reconfiguration identifier of the first terminal device.

[0036] As one possible implementation, the current conditions of the first terminal device satisfy the triggering conditions for intra-cell handover, including:

[0037] The PDCP count value of the first terminal device is a second preset value; or

[0038] The DRB identifier of the first terminal device is a third preset value.

[0039] In one possible implementation, the processor is also configured to read a computer program from the memory and perform the following operations:

[0040] Restore uplink scheduling, downlink DRB scheduling, uplink HARQ transmission, and downlink DRBHARQ transmission of the first terminal device.

[0041] Thirdly, this application provides an intra-cell handover device applied to access network equipment, the device comprising:

[0042] The communication unit is used to send a reconfiguration message to a first terminal device when the current conditions meet the triggering conditions for intra-cell handover. The first terminal device is any terminal device within the coverage area of ​​the access network device.

[0043] The abort unit is used to abort the uplink scheduling, downlink data radio bearer (DRB) scheduling, uplink hybrid automatic repeat request (HARQ) transmission, and downlink DRB HARQ transmission of the first terminal device.

[0044] The communication unit is further configured to receive a random access message from the first terminal device, the random access message carrying uplink data and the identifier of the first terminal device;

[0045] The communication unit is further configured to, when the uplink data is first data and the identifier of the first terminal device is a first identifier, send a Radio Link Control (RLC) status report corresponding to the first data to the first terminal device via a Signaling Radio Bearer (SRB). The first data is the data in the second data for which the first terminal device has not received the corresponding RLC status report. The second data is the data sent by the first terminal device to the access network device via the SRB before receiving the reconfiguration message. The first identifier is the identifier of the first terminal device before intra-cell handover. The RLC status report corresponding to the first data is used to trigger the first terminal device to process the reconfiguration message to complete the intra-cell handover.

[0046] Fourthly, this application also provides a processor-readable storage medium storing a computer program that, when executed by a processor, implements the intra-cell handover method described in the first aspect or any possible implementation thereof.

[0047] Fifthly, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the intra-cell handover method described in the first aspect or any possible implementation thereof.

[0048] In this embodiment, when the current conditions of the first terminal device meet the triggering conditions for intra-cell handover, the access network device sends a reconfiguration message to the first terminal device, suspending the uplink scheduling, downlink DRB scheduling, uplink HARQ transmission, and downlink DRB HARQ transmission of the first terminal device. Then, it receives a random access message from the first terminal device carrying uplink data and the identifier of the first terminal device. If the uplink data is the first data and the identifier of the first terminal device is the first identifier, the access network device sends an RLC status report corresponding to the first data to the first terminal device via SRB. This allows the first terminal device to successfully receive the RLC status report corresponding to the first data and process the reconfiguration message to complete the intra-cell handover. The first data is the data in the second data for which the first terminal device has not received the corresponding RLC status report. The second data is the data sent to the access network device via SRB by the first terminal device before receiving the reconfiguration message. The first identifier is the identifier of the first terminal device before the intra-cell handover. As can be seen, during intra-cell handover, the access network equipment only suspends uplink scheduling, downlink DRB scheduling, uplink HARQ transmission, and downlink DRB HARQ transmission of the terminal equipment, but does not suspend downlink SRB scheduling and downlink SRB HARQ transmission. Therefore, if the access network equipment does not send the RLC status reports corresponding to the data sent by the terminal equipment via SRB before the intra-cell handover to the terminal equipment, the access network equipment can send these RLC status reports to the terminal equipment through downlink SRB scheduling. After successfully receiving these RLC status reports, the terminal equipment can process the reconfiguration message so that it can continue other processes of intra-cell handover. This avoids the situation where the terminal equipment cannot process the reconfiguration message because it has not received all the RLC status reports corresponding to the data sent via SRB before the intra-cell handover, thus improving the success rate of intra-cell handover. Attached Figure Description

[0049] Figure 1 This application provides a schematic diagram of a network architecture.

[0050] Figure 2 A flowchart illustrating an intra-cell handover method provided in an embodiment of this application;

[0051] Figure 3 A flowchart illustrating another intra-cell handover method provided in an embodiment of this application;

[0052] Figure 4 This is a schematic diagram of the structure of an intra-cell handover device provided in an embodiment of this application;

[0053] Figure 5 This is a schematic diagram of another intra-cell handover device provided in an embodiment of this application. Detailed Implementation

[0054] In this embodiment of the invention, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0055] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0056] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0057] This application provides an intra-cell handover method, apparatus, and storage medium to improve the success rate of intra-cell handover.

[0058] The method and apparatus are based on the same concept of the application. Since the methods and apparatus solve problems in similar ways, the implementation of the apparatus and methods can refer to each other, and the repeated parts will not be described again.

[0059] To better understand the embodiments of this application, the relevant technologies will be described below.

[0060] In communication systems such as 4G and 5G, intra-cell handover is required when cell signal quality is poor or key updates are needed.

[0061] For example, in 4G and 5G communication systems, when the Data Radio Bearer (DRB) identifier (ID) needs to be flipped, the key needs to be updated to ensure security. This key update can be achieved through intra-cell handover.

[0062] For example, in 4G and 5G communication systems, when the Packet Data Convergence Protocol (DRB) count needs to be flipped, the established DRB needs to be deleted first, and then the DRB needs to be re-established. To ensure security, the reuse of the DRB ID requires updating the key, which can be achieved through intra-cell handover.

[0063] During intra-cell handover, after the access network device sends a reconfiguration message to the terminal device, it cannot determine the status of the terminal device between the time it receives the reconfiguration completion message from the terminal device. As a result, the transmitted data may not be received correctly due to the inconsistency between the status of the access network device and the terminal device, which reduces the success rate of intra-cell handover.

[0064] To address the aforementioned issues, after the access network device sends a reconfiguration message to the terminal device, and between receiving the reconfiguration completion message from the terminal device, the access network device suspends all uplink and downlink scheduling and all uplink and downlink HARQ transmissions of the terminal device. During this period, if the terminal device needs to send data to the access network device, it can do so through a random access procedure.

[0065] In cases where the terminal device needs to confirm successful reception of all RLC status reports corresponding to data transmitted via SRB before the intra-cell handover before processing the reconfiguration message, if the terminal device, after receiving the reconfiguration message, has not successfully received any RLC status reports corresponding to data transmitted via SRB before the handover, the access network device cannot transmit and / or retransmit these RLC status reports to the terminal device because it has already suspended all uplink / downlink scheduling and all uplink / downlink HARQ transmissions. To obtain these RLC status reports, the terminal device can send information to the access network device through a random access procedure to retrieve them. Upon receiving this information, the access network device, having already suspended all uplink / downlink scheduling and all uplink / downlink HARQ transmissions, cannot send these RLC status reports back to the terminal device, causing the terminal device to be unable to process the reconfiguration message, resulting in a failed intra-cell handover.

[0066] To address the aforementioned issues, during intra-cell handover, the access network equipment only suspends uplink scheduling, downlink DRB scheduling, uplink HARQ transmission, and downlink DRB HARQ transmission for the terminal device, without suspending downlink SRB scheduling and downlink SRB HARQ transmission. Therefore, even if the access network equipment does not send the RLC status reports corresponding to the data sent by the terminal device via SRB before the intra-cell handover, the access network equipment can send these RLC status reports to the terminal device via downlink SRB scheduling. After successfully receiving these RLC status reports, the terminal device can process the reconfiguration message to continue other processes of the intra-cell handover. This avoids the situation where the terminal device cannot process the reconfiguration message because it has not received all the RLC status reports corresponding to the data sent via SRB before the intra-cell handover, thus improving the success rate of intra-cell handover.

[0067] To better understand the embodiments of this application, the network architecture of this application will be described below.

[0068] Figure 1 This is a schematic diagram of a network architecture provided in an embodiment of this application. Figure 1 As shown, the network architecture may include access network device 101 and terminal device 102. Access network device 101 and terminal device 102 are connected via a network.

[0069] In the event of an intra-cell handover, access network device 101 can send a reconfiguration message for intra-cell handover to terminal device 102. After receiving the reconfiguration message from access network device 101, if terminal device 102 needs to confirm successful reception of the RLC status reports corresponding to all data transmitted via SRB before the handover before processing the reconfiguration message, terminal device 102 determines whether it has successfully received the RLC status reports corresponding to all data transmitted via SRB before the handover. If it determines that the RLC status reports corresponding to all data transmitted via SRB before the handover have been successfully received, it can process the reconfiguration message. If it determines that the RLC status reports corresponding to all data transmitted via SRB before the handover have not been successfully received, terminal device 102 can first confirm that the data transmitted via SRB before the handover has not been successfully received, and then send this data to access network device 101 through a random access procedure. After receiving this data, access network device 101 can send the corresponding RLC status reports to terminal device 102. After terminal device 102 successfully receives the corresponding RLC status reports, it can process the reconfiguration message.

[0070] If terminal device 102 does not need to confirm the successful reception of RLC status reports corresponding to all data transmitted via SRB before the handover, terminal device 102 can directly process the reconfiguration message.

[0071] After the terminal device 102 completes the reconfiguration based on the reconfiguration message, it can send the reconfiguration completion information to the access network device 101 through the random access procedure, so that the access network device 101 can continue to complete the remaining procedures of intra-cell handover.

[0072] The terminal devices involved in the embodiments of this application can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems. For example, in 5G and / or 6G systems, the terminal device can be called User Equipment (UE). Wireless terminal devices can be USB storage devices, other personal computer memory devices, and dongles. They can also communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices. For example, they can be portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the radio access network. Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), personal computers, tablets, and Machine-type Communication (MTC) terminal devices. Wireless terminal devices can also be referred to as systems, subscriber units, subscriber stations, mobile stations, mobile terminals, remote stations, access points, remote terminals, access terminals, user terminals, user agents, user devices, and wireless access devices and routers / modems that meet the limitations of this definition; however, this application does not limit the scope of the embodiments described.

[0073] The access network equipment involved in this application embodiment is a device that provides wireless access for terminal devices, mainly responsible for functions such as air interface-side radio resource management, Quality of Service (QoS) flow management, data compression, and encryption. The access network equipment can be a base station, which may include multiple cells providing services to terminal devices. Depending on the specific application, the base station may also be called an access point or other names. For example, the access network equipment involved in this application embodiment can be an evolved network device (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a 5G network architecture, a 6G base station in a 6G network architecture, etc., or it can be a Home evolved Node B (HeNB), a relay node, a femto, a pico, network testing equipment, etc., and is not limited in this application embodiment.

[0074] The technical solutions provided in this application can be applied to a variety of systems. For example, applicable systems may include Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Long Term Evolution Advanced (LTE-A) systems, Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5G New Radio (NR) systems and their evolved communication systems, 6G systems and their evolved communication systems, etc. These various systems may include terminal equipment and access network equipment. The system may also include a core network component, such as the Evolved Packet Core (EPC) and the 5G Core Network (5GC).

[0075] It should be noted that, Figure 1 The network architecture shown is not limited to the terminal devices and access network devices shown in the figure. It may also include other terminal devices and / or access network devices not shown in the figure, and core network devices, which will not be listed here in this application.

[0076] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0077] Based on the above network architecture Figure 2 This is a flowchart illustrating an intra-cell handover method provided in an embodiment of this application. Figure 2 As shown, the intra-cell handover method may include the following steps.

[0078] 201. When the current conditions of the first terminal device meet the triggering conditions for intra-cell handover, the access network device sends a reconfiguration message to the first terminal device.

[0079] Accordingly, the first terminal device receives a reconfiguration message from the access network device.

[0080] The first terminal device is any terminal device within the coverage area of ​​the access network device.

[0081] The triggering conditions for intra-cell handover can be understood as the conditions that can trigger intra-cell handover.

[0082] A reconfiguration message may include a message identifier and configuration information. The message identifier identifies that the reconfiguration message is for intra-cell handover. The configuration information is for intra-cell handover configuration.

[0083] The reconfiguration message can be a Radio Resource Control (RRC) reconfiguration message or other reconfiguration messages.

[0084] Access network equipment can determine, in real-time, periodically, or at regular intervals, whether the current conditions of the first terminal device meet the triggering conditions for intra-cell handover. If it is determined that the current conditions of the first terminal device do not meet the triggering conditions for intra-cell handover, it indicates that the first terminal device does not need to perform intra-cell handover and does not execute subsequent steps. This reduces unnecessary processing and interaction processes, thereby reducing the power consumption of the access network equipment and saving communication resources. If it is determined that the current conditions of the first terminal device meet the triggering conditions for intra-cell handover, it indicates that the first terminal device needs to perform intra-cell handover, and the access network equipment can send a reconfiguration message to the first terminal device.

[0085] 202. The access network equipment suspends uplink scheduling, downlink DRB scheduling, uplink HARQ transmission and downlink DRB HARQ transmission of the first terminal equipment.

[0086] If the current conditions of the first terminal device meet the triggering conditions for intra-cell handover, the access network device may also suspend the uplink scheduling, downlink DRB scheduling, uplink HARQ transmission and downlink DRB HARQ transmission of the first terminal device, that is, stop the uplink scheduling, downlink DRB scheduling, uplink HARQ transmission and downlink DRB HARQ transmission of the first terminal device.

[0087] The uplink scheduling of the first terminal device can be understood as all uplink scheduling of the first terminal device, or as the scheduling of all uplinks of the first terminal device.

[0088] Because the access network device suspended uplink scheduling for the first terminal device, it cannot schedule uplink resources for the first terminal device until the access network device resumes uplink scheduling. Consequently, the first terminal device cannot send information to the access network device using the scheduled uplink resources and can only send information to the access network device through a random access procedure.

[0089] The downlink DRB scheduling of the first terminal device can be understood as the scheduling of all downlink DRBs of the first terminal device, or it can be understood as the scheduling of all downlink DRBs of the first terminal device.

[0090] Because the access network device suspended downlink DRB scheduling for the first terminal device, it was unable to schedule downlink DRB resources for the first terminal device until the access network device resumed downlink DRB scheduling for the first terminal device, thus preventing the access network device from sending information to the first terminal device via DRB.

[0091] The uplink HARQ transmission of the first terminal device can be understood as all uplink HARQ transmissions of the first terminal device, or as the transmission of all uplink HARQs of the first terminal device.

[0092] Because the access network device suspended the uplink HARQ transmission of the first terminal device, the first terminal device was unable to send a HARQ to the access network device. Consequently, the access network device was unable to receive the HARQ from the first terminal device.

[0093] The downlink DRB HARQ transmission of the first terminal device can be understood as all downlink DRB HARQ transmissions of the first terminal device, or as the transmission of all downlink DRB HARQs of the first terminal device.

[0094] Because the access network device suspended the downlink DRB HARQ transmission of the first terminal device, the access network device was unable to send HARQ to the first terminal device via DRB. Consequently, the first terminal device was unable to receive HARQ from the access network device via DRB.

[0095] 203. The first terminal device sends a random access message carrying uplink data and the identifier of the first terminal device to the access network device.

[0096] Accordingly, the access network device receives a random access message from the first terminal device, carrying uplink data and the identifier of the first terminal device.

[0097] Random access messages can carry uplink data and the identifier of the first terminal device. The uplink data is the data that the first terminal device needs to send to the access network device. The identifier of the first terminal device can be a Cell Radio Network Temporary Identifier (CRNTI) or other information that uniquely identifies the first terminal device.

[0098] After receiving the reconfiguration message from the access network device, if the first terminal device needs to transmit uplink data to the access network device, it can generate a random access message carrying the uplink data and the identifier of the first terminal device, and then send the random access message to the access network device.

[0099] The first terminal device can send data to the access network device via SRB. After the access network device successfully receives the data from the first terminal device via SRB, it can send or send back an RLC status report indicating successful data reception. Therefore, when the first terminal device needs to confirm receipt of the RLC status report corresponding to the second data before processing the reconfiguration message, the first terminal device can first determine whether it has successfully received the RLC status report corresponding to the second data. If it determines that it has not successfully received the RLC status report corresponding to the second data, it can first determine the first data, then generate a random access message carrying the first data and the identifier of the first terminal device, and then send the random access message to the access network device. The second data is the data sent by the first terminal device to the access network device via SRB before receiving the reconfiguration message. The first data is the data in the second data for which the first terminal device has not received the corresponding RLC status report, that is, the data in the second data for which the first terminal device has not received the corresponding RLC status report from the access network device, and also the data in the second data for which the first terminal device has not received the RLC status report fed back by the access network device.

[0100] The random access message can be a message (Message, msg) 3 during the random access process, or it can be other uplink messages during the random access process.

[0101] 204. When the uplink data is the first data and the identifier of the first terminal device is the first identifier, the access network device sends the RLC status report corresponding to the first data to the first terminal device through SRB.

[0102] Accordingly, the first terminal device receives the RLC status report corresponding to the first data from the access network device via the SRB.

[0103] The first identifier is the identifier of the first terminal device before the intra-cell handover, that is, the identifier of the first terminal device when the current conditions of the first terminal device meet the triggering conditions for intra-cell handover.

[0104] After receiving a random access message from the first terminal device, the access network device can first parse the random access message to obtain the uplink data and the identifier of the first terminal device. Then, it can identify the uplink data and the identifier of the first terminal device. If the uplink data is identified as the first data and the identifier of the first terminal device is identified as the first identifier, it indicates that the first terminal device needs to confirm that it has successfully received the RLC status report corresponding to the second data before it can process the reconfiguration message. If the first terminal device has not successfully received the RLC status report corresponding to the first data, it can generate the RLC status report corresponding to the first data.

[0105] As can be seen from step 202, the access network device only suspended the downlink DRB scheduling of the first terminal device, and did not suspend the downlink SRB scheduling of the first terminal device. Therefore, the access network device can send the RLC status report corresponding to the first data to the first terminal device through SRB.

[0106] After the first terminal device receives the RLC status report corresponding to the first data from the access network device via SRB, it can first determine whether the RLC status report corresponding to the first data has been successfully received. If it has been successfully received, it indicates that the RLC status report corresponding to the first data has been successfully received, and the reconfiguration message can be processed so that the remaining procedures of intra-cell handover can be completed.

[0107] exist Figure 2In the intra-cell handover method shown, during the intra-cell handover process, the access network device only suspends the uplink scheduling, downlink DRB scheduling, uplink HARQ transmission, and downlink DRB HARQ transmission of the terminal device, but does not suspend the downlink SRB scheduling and downlink SRB HARQ transmission. Therefore, if the access network device does not send the RLC status reports corresponding to the data sent by the terminal device via SRB before the intra-cell handover to the terminal device, the access network device can send these RLC status reports to the terminal device through downlink SRB scheduling. After successfully receiving these RLC status reports, the terminal device can process the reconfiguration message. This avoids the situation where the terminal device cannot process the reconfiguration message because it has not received all the RLC status reports corresponding to the data sent via SRB before the intra-cell handover, thus improving the success rate of intra-cell handover.

[0108] Based on the above network architecture Figure 3 This is a flowchart illustrating another intra-cell handover method provided in an embodiment of this application. Figure 3 As shown, the intra-cell handover method may include the following steps.

[0109] 301. If the current conditions of the first terminal device meet the triggering conditions for intra-cell handover, the access network device sends a reconfiguration message to the first terminal device.

[0110] Accordingly, the first terminal device receives a reconfiguration message from the access network device.

[0111] The first terminal device is any terminal device within the coverage area of ​​the access network device.

[0112] The triggering conditions for intra-cell handover can be understood as the conditions that can trigger intra-cell handover.

[0113] A reconfiguration message may include a message identifier and configuration information. The message identifier identifies that the reconfiguration message is for intra-cell handover. The configuration information is for intra-cell handover configuration.

[0114] Reconfiguration messages can be RRC reconfiguration messages or other types of reconfiguration messages.

[0115] The reconfiguration message may include a second identifier. The second identifier is the reconfiguration identifier of the first terminal device, that is, the identifier used by the access network device to reconfigure the first terminal device when the current conditions of the first terminal device meet the triggering conditions for intra-cell handover.

[0116] Access network equipment can determine in real-time, periodically, or at regular intervals whether the current conditions of the first terminal device meet the triggering conditions for intra-cell handover. If it is determined that the current conditions of the first terminal device do not meet the triggering conditions for intra-cell handover, it indicates that the first terminal device does not need to perform intra-cell handover and does not execute subsequent steps. This reduces unnecessary processing and interaction processes, thereby reducing the power consumption of the access network equipment and saving communication resources. If it is determined that the current conditions of the first terminal device meet the triggering conditions for intra-cell handover, it indicates that the first terminal device needs to perform intra-cell handover. The access network equipment can first reconfigure the identifier of the first terminal device to obtain a second identifier, then generate a reconfiguration message including the second identifier, and then send the reconfiguration message to the first terminal device.

[0117] The access network equipment can determine whether the current conditions of the first terminal device meet the triggering conditions for intra-cell handover based on the current scenario of the first terminal device.

[0118] In some embodiments, when the current scenario of the first terminal device is that the Packet Data Convergence Protocol (PDCP) count has reached its maximum value, it can be determined that the current conditions of the first terminal device meet the triggering conditions for intra-cell handover. Specifically, the access network device can determine in real time, periodically, or at regular intervals whether the PDCP count value of the first terminal device is a second preset value. If the PDCP count value of the first terminal device is not the second preset value, it indicates that the PDCP count value of the first terminal device has not reached its maximum value, and it can be determined that the current conditions of the first terminal device do not meet the triggering conditions for intra-cell handover. If the PDCP count value of the first terminal device is the second preset value, it indicates that the PDCP count value of the first terminal device has reached its maximum value, and the access network device can determine that the current conditions of the first terminal device meet the triggering conditions for intra-cell handover.

[0119] In some embodiments, when the current scenario of the first terminal device is a DRB reconstruction and key update triggered by DRB ID flipping, it can be determined that the current conditions of the first terminal device meet the triggering conditions for intra-cell handover. Specifically, the access network device can determine in real time, periodically, or at regular intervals whether the DRB ID of the first terminal device is a third preset value. If the value of the DRB ID of the first terminal device is not the third preset value, it indicates that the DRB ID of the first terminal device does not need to be flipped, and it can be determined that the current conditions of the first terminal device do not meet the triggering conditions for intra-cell handover. If the DRB ID of the first terminal device is the third preset value, it indicates that the DRB ID of the first terminal device needs to be flipped, and the access network device can determine that the current conditions of the first terminal device meet the triggering conditions for intra-cell handover. The third preset value can be 31 or other values, and is not limited thereto. For example, the third preset value can also be 28.

[0120] It should be understood that the above is an exemplary description of determining whether the current conditions of the first terminal device meet the triggering conditions for intra-cell handover based on the current scenario of the first terminal device, and does not limit the determination of whether the current conditions of the first terminal device meet the triggering conditions for intra-cell handover based on the current scenario of the first terminal device. For example, if the current scenario of the first terminal device is a scenario with poor signal quality, it can be determined that the current conditions of the first terminal device meet the triggering conditions for intra-cell handover.

[0121] Because the higher layers of the access network equipment may not be able to determine which reconfiguration process the received reconfiguration completion information corresponds to, in order to avoid confusion between reconfiguration completion information corresponding to different reconfiguration processes, if the current conditions of the first terminal device meet the triggering conditions for intra-cell handover, the access network equipment can first determine whether the first terminal device is currently in another reconfiguration process. If it is determined that the first terminal device is in another reconfiguration process, the access network equipment can only send the reconfiguration message to the first terminal device after receiving the reconfiguration completion information corresponding to that other reconfiguration process.

[0122] Other reconfiguration procedures can be the reconfiguration procedure for establishing a DRB, or other reconfiguration procedures other than those for intra-cell handover.

[0123] 302. The access network equipment suspends uplink scheduling, downlink DRB scheduling, uplink HARQ transmission and downlink DRB HARQ transmission of the first terminal equipment.

[0124] The access network equipment can also suspend uplink scheduling, downlink DRB scheduling, uplink HARQ transmission, and downlink DRB HARQ transmission of the first terminal device. For a detailed description of the uplink scheduling, downlink DRB scheduling, uplink HARQ transmission, and downlink DRB HARQ transmission of the first terminal device, please refer to the relevant description below step 202, which will not be repeated here.

[0125] In some embodiments, while the access network device sends a reconfiguration message to the first terminal device, the higher layers of the access network device may also send a first message to the medium access control (MAC) layer of the access network device. The first message is a message used to indicate intra-cell handover. The first message may include a second identifier.

[0126] After receiving the first message from the higher layers of the access network device, the MAC layer of the access network device can determine the terminal device undergoing intra-cell handover as the first terminal device based on the first message and the second identifier.

[0127] Access network equipment can also clear the uplink HARQ process and downlink DRB HARQ process of the first terminal device, which can avoid unnecessary process execution and reduce the power consumption of the access network equipment.

[0128] 303. The first terminal device sends a random access message carrying uplink data and the identifier of the first terminal device to the access network device.

[0129] Accordingly, the access network device receives a random access message from the first terminal device, which includes uplink data and the identifier of the first terminal device.

[0130] The random access message may include uplink data and the identifier of the first terminal device. A detailed description of the uplink data and the identifier of the first terminal device can be found in the relevant description of step 203, and will not be repeated here.

[0131] After receiving a reconfiguration message from the access network device, if there is uplink data that needs to be transmitted to the access network device, the first terminal device can generate a random access message carrying the uplink data and the identifier of the first terminal device, and then send the random access message to the access network device.

[0132] After receiving the reconfiguration message from the access network device, the first terminal device can first determine whether it has successfully received the reconfiguration message. If the first terminal device has not successfully received the reconfiguration message, it can generate a random access message including third data and a first identifier, and then send the random access message to the access network device. The third data is used to indicate that the reconfiguration message reception failed. A detailed description of the first identifier can be found in the relevant description below step 204, and will not be repeated here.

[0133] If the first terminal device successfully receives the reconfiguration message, and the first terminal device needs to confirm that it has successfully received the RLC status report corresponding to the second data before processing the reconfiguration message, the first terminal device can first determine whether it has successfully received the RLC status report corresponding to the second data. If it is determined that the RLC status report corresponding to the second data has not been successfully received, the first data can be determined first, and then a random access message carrying the first data and the first identifier can be generated, and then the random access message can be sent to the access network device. A detailed description of the first data and the second data can be found in the relevant description below step 203, and will not be repeated here.

[0134] If the first terminal device can process the reconfiguration message only after successfully receiving it and without needing to confirm the successful receipt of the RLC status report corresponding to the second data, or if the first terminal device can process the reconfiguration message after successfully receiving the RLC status report corresponding to the second data, then the first terminal device can process the reconfiguration message, i.e., perform reconfiguration based on the reconfiguration message. After processing the reconfiguration message, i.e. after the reconfiguration is completed according to the reconfiguration message, a random access message carrying reconfiguration completion information and the identifier of the first terminal device can be generated, and then the random access message can be sent to the access network device.

[0135] The reconfiguration completion information is used to instruct the first terminal device to complete the reconfiguration based on the reconfiguration message, that is, the first terminal device has finished processing the reconfiguration message. The reconfiguration completion information is the response information to the aforementioned reconfiguration message.

[0136] The identifier of the first terminal device in a random access message can be either a first identifier or a second identifier. Whether the identifier of the first terminal device in a random access message is the first identifier or the second identifier is determined by the first terminal device. The identifier of the first terminal device may differ depending on the type of the first terminal device.

[0137] For example, when the first terminal device is a Test Mobile (TM) terminal device, the identifier of the first terminal device for the random access message can be a first identifier. For example, when the first terminal device is not a TM terminal device, the identifier of the first terminal device for the random access message can be a second identifier. For example, the TM terminal device can be a TM500.

[0138] The random access message can be a message (Message, msg) 3 during the random access process, or it can be other uplink messages during the random access process.

[0139] 304. If the RLC sequence number (SN) carried in the random access message is a first preset value, the access network device determines that the uplink data is reconfiguration completion information and rebuilds the RLC connection and PDCP connection with the first terminal device.

[0140] In related technologies, after receiving a random access message, the access network device can determine whether the terminal device has completed processing the reconfiguration message based on the identifier of the first terminal device carried in the random access message. If the identifier of the first terminal device carried in the random access message is a reconfiguration identifier, it is determined that the terminal device has completed processing the reconfiguration message; if the identifier of the first terminal device carried in the random access message is the identifier before handover, it is determined that the terminal device has not completed processing the reconfiguration message. However, when the terminal device is a TM terminal device and the TM terminal device has completed processing the reconfiguration message, since the random access message carries the identifier before handover, the access network device determines that the TM terminal device has not completed processing the reconfiguration message based on the identifier before handover. Therefore, because the actual state of the TM terminal device is inconsistent with the state determined by the access network device, the access network device cannot continue to complete the remaining procedures of intra-cell handover, resulting in intra-cell handover failure.

[0141] After receiving a random access message, the access network device can identify whether the RLC SN carried in the random access message is a first preset value. If the RLC SN of the random access message is identified as the first preset value, it can determine that the uplink data is reconfiguration completion information, indicating that the first terminal device has completed reconfiguration according to the reconfiguration message. Afterwards, the RLC connection and PDCP connection with the first terminal device can be rebuilt. Specifically, the access network device can notify the RLC layer to rebuild the RLC connection with the first terminal device, and it can notify the PDCP layer to rebuild the PDCP connection with the first terminal device. The first preset value can be 0 or other values, which are not limited here.

[0142] As can be seen, the access network device determines whether the RLC SN carried in the random access message is the first preset value to ascertain whether the terminal device has finished processing the reconfiguration message. Therefore, regardless of whether the terminal device identifier carried in the random access message is the identifier before handover or the reconfiguration identifier, it will not affect the access network device's judgment, ensuring that the terminal device's determined state by the access network is consistent with the actual state of the terminal device. Thus, after the TM terminal device finishes processing the reconfiguration message, the access network device can continue to complete the remaining procedures of intra-cell handover, thereby improving the success rate of intra-cell handover.

[0143] If the RLC SN carried in the random access message is identified as the first preset value, the access network device can also determine the identifier of the first terminal device after cell handover, and then rebuild the RLC connection and PDCP connection with the first terminal device.

[0144] In some embodiments, when the identifier of the first terminal device carried in the random access message is a first identifier, the first identifier can be determined as the identifier of the first terminal device after the intra-cell handover, that is, the identifier of the first terminal device after the intra-cell handover is the identifier before reconfiguration, i.e., the identifier before the intra-cell handover.

[0145] In some embodiments, when the identifier of the first terminal device carried in the random access message is a second identifier, the second identifier can be determined as the identifier of the first terminal device after intra-cell handover, that is, the identifier of the first terminal device after intra-cell handover is the reconfigured identifier, that is, the reconfigured identifier during intra-cell handover.

[0146] 305. When the uplink data is the first data and the identifier of the first terminal device is the first identifier, the access network device sends the RLC status report corresponding to the first data to the first terminal device through the SRB.

[0147] Accordingly, the first terminal device receives the RLC status report corresponding to the first data from the access network device via the SRB.

[0148] After receiving a random access message from the first terminal device, the access network device can first parse the random access message to obtain the uplink data and the identifier of the first terminal device. Then, it can identify the uplink data and the identifier of the first terminal device. If the uplink data is identified as the first data and the identifier of the first terminal device is identified as the first identifier, it indicates that the first terminal device needs to confirm that it has successfully received the RLC status report corresponding to the second data before it can process the reconfiguration message. If the first terminal device has not successfully received the RLC status report corresponding to the first data, it can generate the RLC status report corresponding to the first data.

[0149] If it is determined that the RLC SN carried in the random access message is not the first preset value, it can be determined that the uplink data is not reconfiguration completion information, and the uplink data and the identifier of the first terminal device can continue to be identified.

[0150] As can be seen from step 302, the access network device only suspended the downlink DRB scheduling of the first terminal device, and did not suspend the downlink SRB scheduling of the first terminal device. Therefore, the access network device can send the RLC status report corresponding to the first data to the first terminal device through SRB.

[0151] After the first terminal device receives the RLC status report corresponding to the first data from the access network device via SRB, it can first determine whether the RLC status report corresponding to the first data has been successfully received. If it has been successfully received, it indicates that the RLC status report corresponding to the second data has been successfully received, and the reconfiguration message can be processed. For a detailed description, please refer to the relevant description below step 303.

[0152] 306. The access network equipment restores the uplink scheduling, downlink DRB scheduling, uplink HARQ transmission and downlink DRB HARQ transmission of the first terminal equipment.

[0153] After the access network equipment rebuilds the RLC and PDCP connections with the first terminal equipment, it can restore the uplink scheduling and downlink DRB scheduling of the first terminal equipment so that the intra-cell handover of the first terminal equipment can be completed.

[0154] In some embodiments, when the uplink data is third data, the access network device can retransmit a reconfiguration message to the first terminal device via SRB so that the first terminal device can complete the intra-cell handover.

[0155] exist Figure 3In the intra-cell handover method shown, during the intra-cell handover process, the access network device only suspends the uplink scheduling, downlink DRB scheduling, uplink HARQ transmission, and downlink DRB HARQ transmission of the terminal device, but does not suspend the downlink SRB scheduling and downlink SRB HARQ transmission. Therefore, if the access network device does not send the RLC status reports corresponding to the data sent by the terminal device via SRB before the intra-cell handover to the terminal device, the access network device can send these RLC status reports to the terminal device through downlink SRB scheduling. After successfully receiving these RLC status reports, the terminal device can process the reconfiguration message. This avoids the situation where the terminal device cannot process the reconfiguration message because it has not received all the RLC status reports corresponding to the data transmitted via SRB before the intra-cell handover, thus improving the success rate of intra-cell handover. Furthermore, since the completion of reconfiguration message processing is determined by the RLC SN carried in the random access message, the identification of the first terminal device carried in the random access message will not affect the result judgment. This ensures that the state determined by the access network device is consistent with the state of the terminal device. After the terminal device completes the reconfiguration message processing, the access network device can continue to complete the remaining procedures of intra-cell handover, thereby improving the success rate of intra-cell handover.

[0156] It should be understood that the same or corresponding information in different embodiments can be referenced to each other.

[0157] It should be understood that in the above embodiments, some steps may be omitted, and some steps may be combined.

[0158] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0159] Based on the same inventive concept, this application also provides an intra-cell handover apparatus for implementing the intra-cell handover method described above. The solution provided by this intra-cell handover apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more intra-cell handover apparatus embodiments provided below can be found in the limitations of the intra-cell handover method described above, and will not be repeated here.

[0160] Based on the above network architecture Figure 4 This is a schematic diagram of an intra-cell handover device provided in an embodiment of this application. The intra-cell handover device can be applied to access network equipment. The intra-cell handover device may include:

[0161] The communication unit 401 is used to send a reconfiguration message to a first terminal device when the current conditions meet the triggering conditions for intra-cell handover. The first terminal device is any terminal device within the coverage area of ​​the access network device.

[0162] The termination unit 402 is used to terminate the uplink scheduling, downlink DRB scheduling, uplink HARQ transmission and downlink DRB HARQ transmission of the first terminal device.

[0163] Communication unit 401 is also used to receive a random access message from the first terminal device, the random access message carrying uplink data and the identifier of the first terminal device;

[0164] The communication unit 401 is further configured to send an RLC status report corresponding to the first data to the first terminal device via SRB when the uplink data is the first data and the identifier of the first terminal device is the first identifier. The first data is the data in the second data for which the first terminal device has not received the corresponding RLC status report. The second data is the data sent by the first terminal device to the access network device via SRB before receiving the reconfiguration message. The first identifier is the identifier of the first terminal device before the intra-cell handover. The RLC status report corresponding to the first data is used to trigger the first terminal device to process the reconfiguration message in order to complete the intra-cell handover.

[0165] In some embodiments, the intra-cell handover device may further include:

[0166] The determining unit is used to determine that the uplink data is reconfiguration completion information when the RLC SN carried in the random access message is a first preset value;

[0167] The reconstruction unit is used to rebuild the RLC connection and PDCP connection with the first terminal device.

[0168] In some embodiments, the determining unit is further configured to determine the first identifier as the identifier of the first terminal device after intra-cell handover if the identifier of the first terminal device carried in the random access message is a first identifier.

[0169] In some embodiments, the determining unit is further configured to determine the second identifier as the identifier of the first terminal device after intra-cell handover when the identifier of the first terminal device carried in the random access message is the second identifier, and the second identifier is the reconfiguration identifier of the first terminal device.

[0170] In some embodiments, the current conditions of the first terminal device satisfying the triggering conditions for intra-cell handover include:

[0171] The PDCP count value of the first terminal device is a second preset value; or

[0172] The DRB identifier of the first terminal device is the third preset value.

[0173] In some embodiments, the intra-cell handover device may further include:

[0174] The recovery unit is used to restore the uplink scheduling, downlink DRB scheduling, uplink HARQ transmission and downlink DRB HARQ transmission of the first terminal device.

[0175] It should be noted that the intra-cell handover device provided in this application embodiment can implement all the method steps of the access network device in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0176] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0177] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application.

[0178] It should be noted that the apparatus provided in this embodiment of the invention can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0179] Based on the above network architecture Figure 5This is a schematic diagram of another intra-cell handover device provided in an embodiment of this application. This intra-cell handover device implements the above-described intra-cell handover method. This intra-cell handover device can be an access network device, such as… Figure 5 As shown, the intra-cell handover device may include a processor 501, a memory 502, and a transceiver 503. The memory 502 stores computer programs. The transceiver 503 receives and transmits data under the control of the processor 501; a detailed description can be found in the transmission and reception steps of the access network device in the intra-cell handover method described above. The processor 501 reads the computer program from the memory 502 and executes the operations performed by the access network device in the intra-cell handover method described above; a detailed description can be found in the relevant description of the access network device in the intra-cell handover method described above.

[0180] Among them, Figure 5 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (represented by a processor) and memory (represented by a memory). The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface. The transceiver can be multiple components, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor is responsible for managing the bus architecture and general processing, and the memory can store data used by the processor 501 during operation.

[0181] The processor can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0182] This application also provides a processor-readable storage medium, which can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0183] In one embodiment, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described intra-cell handover method.

[0184] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0185] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0186] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0187] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0188] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0189] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for intra-cell handover, characterized in that, Applied to access network equipment, the method includes: If the current conditions of the first terminal device meet the triggering conditions for intra-cell handover, a reconfiguration message is sent to the first terminal device, where the first terminal device is any terminal device within the coverage area of ​​the access network device. The uplink scheduling, downlink data radio bearer (DRB) scheduling, uplink hybrid automatic repeat request (HARQ) transmission, and downlink DRB HARQ transmission of the first terminal device are suspended. Receive a random access message from the first terminal device, the random access message carrying uplink data and the identifier of the first terminal device; When the uplink data is the first data and the identifier of the first terminal device is the first identifier, the radio link control (RLC) status report corresponding to the first data is sent to the first terminal device via the signaling radio bearer (SRB). The first data is the data in the second data for which the first terminal device has not received the corresponding RLC status report. The second data is the data sent by the first terminal device to the access network device via the SRB before receiving the reconfiguration message. The first identifier is the identifier of the first terminal device before the intra-cell handover. The RLC status report corresponding to the first data is used to trigger the first terminal device to process the reconfiguration message to complete the intra-cell handover.

2. The method according to claim 1, characterized in that, The method further includes: If the RLC sequence number SN carried in the random access message is a first preset value, the uplink data is determined to be reconfiguration completion information; Rebuild the RLC connection and the PDCP connection with the first terminal device.

3. The method according to claim 2, characterized in that, The method further includes: If the identifier of the first terminal device carried in the random access message is the first identifier, the first identifier is determined to be the identifier of the first terminal device after the intra-cell handover.

4. The method according to claim 2, characterized in that, The method further includes: If the identifier of the first terminal device carried in the random access message is a second identifier, the second identifier is determined to be the identifier of the first terminal device after intra-cell handover, and the second identifier is the reconfiguration identifier of the first terminal device.

5. The method according to any one of claims 1-4, characterized in that, The current conditions of the first terminal device satisfy the triggering conditions for intra-cell handover, including: The PDCP count value of the first terminal device is a second preset value; or The DRB identifier of the first terminal device is a third preset value.

6. The method according to any one of claims 2-4, characterized in that, The method further includes: Restore uplink scheduling, downlink DRB scheduling, uplink HARQ transmission, and downlink DRB HARQ transmission of the first terminal device.

7. A cell handover device, characterized in that, Applied to access network equipment, including memory, transceivers, and processors: The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations: If the current conditions of the first terminal device meet the triggering conditions for intra-cell handover, a reconfiguration message is sent to the first terminal device, where the first terminal device is any terminal device within the coverage area of ​​the access network device. The uplink scheduling, downlink data radio bearer (DRB) scheduling, uplink hybrid automatic repeat request (HARQ) transmission, and downlink DRB HARQ transmission of the first terminal device are suspended. Receive a random access message from the first terminal device, the random access message carrying uplink data and the identifier of the first terminal device; When the uplink data is the first data and the identifier of the first terminal device is the first identifier, the radio link control (RLC) status report corresponding to the first data is sent to the first terminal device via the signaling radio bearer (SRB). The first data is the data in the second data for which the first terminal device has not received the corresponding RLC status report. The second data is the data sent by the first terminal device to the access network device via the SRB before receiving the reconfiguration message. The first identifier is the identifier of the first terminal device before the intra-cell handover. The RLC status report corresponding to the first data is used to trigger the first terminal device to process the reconfiguration message to complete the intra-cell handover.

8. The apparatus according to claim 7, characterized in that, The processor is also configured to read the computer program in the memory and perform the following operations: If the RLC sequence number SN carried in the random access message is a first preset value, the uplink data is determined to be reconfiguration completion information; Rebuild the RLC connection and the PDCP connection with the first terminal device.

9. The apparatus according to claim 8, characterized in that, The processor is also configured to read the computer program in the memory and perform the following operations: If the identifier of the first terminal device carried in the random access message is the first identifier, the first identifier is determined to be the identifier of the first terminal device after the intra-cell handover.

10. The apparatus according to claim 8, characterized in that, The processor is also configured to read the computer program in the memory and perform the following operations: If the identifier of the first terminal device carried in the random access message is a second identifier, the second identifier is determined to be the identifier of the first terminal device after intra-cell handover, and the second identifier is the reconfiguration identifier of the first terminal device.

11. The apparatus according to any one of claims 7-10, characterized in that, The current conditions of the first terminal device satisfy the triggering conditions for intra-cell handover, including: The PDCP count value of the first terminal device is a second preset value; or The DRB identifier of the first terminal device is a third preset value.

12. The apparatus according to any one of claims 7-10, characterized in that, The processor is also configured to read the computer program in the memory and perform the following operations: Restore uplink scheduling, downlink DRB scheduling, uplink HARQ transmission, and downlink DRB HARQ transmission of the first terminal device.

13. A cell handover device, characterized in that, Applied to access network equipment, the device includes: The communication unit is used to send a reconfiguration message to a first terminal device when the current conditions meet the triggering conditions for intra-cell handover. The first terminal device is any terminal device within the coverage area of ​​the access network device. The abort unit is used to abort the uplink scheduling, downlink data radio bearer (DRB) scheduling, uplink hybrid automatic repeat request (HARQ) transmission, and downlink DRB HARQ transmission of the first terminal device. The communication unit is further configured to receive a random access message from the first terminal device, the random access message carrying uplink data and the identifier of the first terminal device; The communication unit is further configured to, when the uplink data is first data and the identifier of the first terminal device is a first identifier, send a Radio Link Control (RLC) status report corresponding to the first data to the first terminal device via a Signaling Radio Bearer (SRB). The first data is the data in the second data for which the first terminal device has not received the corresponding RLC status report. The second data is the data sent by the first terminal device to the access network device via the SRB before receiving the reconfiguration message. The first identifier is the identifier of the first terminal device before intra-cell handover. The RLC status report corresponding to the first data is used to trigger the first terminal device to process the reconfiguration message to complete the intra-cell handover.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1 to 6.

Images