A communication method and apparatus

By sending an RRC reconfiguration completion message after the terminal device switches over and executing the RRC establishment or reconstruction process when no downlink data is received, the communication anomaly caused by inconsistent security parameters in the 5G communication system is resolved, normal communication between the terminal device and the target base station is realized, and the user experience is improved.

CN123075739APending Publication Date: 2026-11-10HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510591255.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-05-07
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In 5G communication systems, during cell handover, inconsistent security parameters can prevent the target base station from receiving the handover completion message, thus hindering normal communication between the terminal device and the target base station and reducing user experience.

Method used

After the terminal device switches from the cell of the source network device to the cell of the target network device, it sends an RRC reconfiguration complete message to the target network device. If no valid downlink data is received within the first time period, the terminal device sends an RRC establishment request or an RRC reconstruction request and executes the RRC establishment procedure or the RRC reconstruction procedure to ensure the alignment of security parameters.

Benefits of technology

By ensuring that the security parameters of the terminal device and the target network device are consistent, the normality of communication during the first time period is improved, thus enhancing the user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123075739A_ABST
    Figure CN123075739A_ABST
Patent Text Reader

Abstract

This application provides a communication method and apparatus to solve the communication problem when security parameters are inconsistent between a terminal device and a network device, thereby improving the user experience. The communication method includes: after the terminal device switches from the cell of the source network device to the cell of the target network device, sending a Radio Resource Control (RRC) reconfiguration completion message to the target network device; if no valid downlink data is received from the target network device within a first time duration, sending an RRC establishment request or executing an RRC reconstruction request to the target network device, wherein the first time duration is less than a preset time duration, the preset time duration being the time the target network device's RRC layer waits to receive the RRC reconfiguration completion message; the terminal device executes the RRC establishment procedure or the RRC reconstruction procedure, and the terminal device and the target network device re-activate security, causing the security parameters to realign, enabling the terminal device to communicate normally with the target network device, thus improving the user experience.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] In 5G communication systems, terminal devices exist in three radio resource control (RRC) states: RRC-connected, RRC-idle, and RRC-inactive. Terminal devices in the connected state can communicate with network devices (such as base stations). When a terminal device moves, cell handover ensures its connected state remains intact. Cell handover refers to the terminal device switching from the source base station's cell to the target base station's cell. During cell handover, the source base station sends multiple handover requests to the target base station through the core network. Each time the core network receives a handover request, it performs a network hopchaining count (NCC) calculation and key deduction. Once the NCC value reaches its maximum value, it flips back to its initial value of 0. Multiple handover requests result in multiple key deductions by the core network. The terminal device performs key deduction based on the difference between the NCC value on the core network side and the NCC value on the terminal device. This may result in the terminal device performing key deduction a different number of times than the core network performs key deduction. Consequently, the security parameters of the terminal device and the target base station are inconsistent. As a result, the RRC layer of the target base station cannot receive the handover completion message sent by the terminal device within a preset time period, which in turn prevents normal communication between the terminal device and the target base station. Summary of the Invention

[0003] This application provides a communication method and apparatus to solve the problem of incompatibility between terminal devices and network devices due to inconsistent security parameters, thereby improving user experience.

[0004] Firstly, a communication method is provided. This communication method includes: after a terminal device switches from a cell of a source network device to a cell of a target network device, sending a Radio Resource Control (RRC) reconfiguration completion message to the target network device; if no valid downlink data is received from the target network device within a first time duration, sending an RRC establishment request or an RRC reconstruction request to the target network device, wherein the first time duration is less than a preset time duration, the preset time duration being the duration for which the RRC layer of the target network device waits to receive the RRC reconfiguration completion message; and the terminal device executing an RRC establishment procedure or an RRC reconstruction procedure.

[0005] In the above technical solution, after the terminal device switches from the cell of the source network device to the cell of the target network device, it sends an RRC reconfiguration completion message to the target network device. If the terminal device does not receive valid downlink data from the target network device within the first time period, the terminal device sends an RRC establishment request or an RRC reconstruction request to the target network device. The terminal device executes the RRC establishment procedure or the RRC reconstruction procedure to align the security parameters of the terminal device with those of the target network device, thus ensuring that the security parameters of the terminal device and the target network device are consistent. This allows the terminal device to communicate normally with the target network device within the first time period, improving the user experience.

[0006] In one possible implementation of the first aspect, before sending an RRC establishment request to the target network device, the method further includes: releasing the RRC connection with the target network device; the RRC establishment process includes: receiving an RRC establishment message sent by the target network device; establishing an RRC connection with the target network device; and sending an RRC establishment completion message to the target network device. In the above possible implementation, the terminal device releases the RRC connection with the target network device, and the terminal device's state transitions from the RRC connected state to the RRC idle state. The terminal device in the RRC idle state does not have corresponding security parameters. After executing the RRC establishment process, the terminal device reactivates its security and obtains new security parameters, making the terminal device's security parameters consistent with the target network device's security parameters. This allows the terminal device to communicate normally with the target network device for the first time period, improving the user experience.

[0007] In one possible implementation of the first aspect, the RRC reconstruction process includes: receiving an RRC establishment message from the target network device; and sending an RRC establishment completion message to the target network device. In the above possible implementation, after receiving the RRC establishment message from the target network device and the terminal device securely reactivating, it obtains new security parameters, ensuring that the security parameters of the terminal device are consistent with those of the target network device. This allows the terminal device to communicate normally with the target network device for the first period of time, improving the user experience.

[0008] In one possible implementation of the first aspect, the RRC reconstruction process includes: receiving an RRC reconstruction message from the target network device; and sending an RRC reconstruction complete message to the target network device. In the above possible implementation, the terminal device performs security deduction based on the NCC value carried in the RRC reconstruction message to obtain new security parameters, ensuring that the security parameters of the terminal device are consistent with those of the target network device. This allows the terminal device to communicate normally with the target network device for a first time period, improving the user experience.

[0009] In one possible implementation of the first aspect, after sending a Radio Resource Control (RRC) reconfiguration completion message to the target network device, the method further includes: adjusting the operation of sending measurement reports to the source network device when the number of anomalies encountered by the terminal device within a preset time is greater than or equal to a preset threshold; wherein the adjustment operation includes: changing the time of sending the measurement report, changing the content of sending the measurement report, or stopping the sending of the measurement report; anomalies include: receiving a paging message sent by the target network device, failing to verify the integrity of a message sent by the target network device, or not receiving valid downlink data sent by the target network device. In the above possible implementations, adjusting the sending of measurement reports to the source network device can improve the handover success rate of the source network device during the next cell handover.

[0010] In a second aspect, a communication device is provided, comprising a transmitting module and a processing module: the transmitting module is configured to send a Radio Resource Control (RRC) reconfiguration completion message to the target network device after the terminal device switches from the cell of the source network device to the cell of the target network device; the transmitting module is further configured to send an RRC establishment request or an RRC reconstruction request to the target network device if no valid downlink data is received from the target network device within a first duration, the first duration being less than a preset duration, the preset duration being the duration for which the RRC layer of the target network device waits to receive the RRC reconfiguration completion message; the processing module is configured to execute the RRC establishment procedure or the RRC reconstruction procedure.

[0011] In one possible implementation of the second aspect, the communication device further includes: a receiving module; a processing module, further configured to release the RRC connection with the target network device before the sending module sends the RRC establishment request; a receiving module, configured to receive the RRC establishment message sent by the target network device; a processing module, configured to establish the RRC connection with the target network device; and a sending module, further configured to send an RRC establishment completion message to the target network device.

[0012] In one possible implementation of the second aspect, the communication device further includes: a receiving module. The receiving module is used to receive an RRC establishment message from the target network device; the sending module is also used to send an RRC establishment completion message to the target network device.

[0013] In one possible implementation of the second aspect, the communication device further includes a receiving module. The receiving module is used to receive an RRC reconstruction message from the target network device; the sending module is also used to send an RRC reconstruction completion message to the target network device.

[0014] In one possible implementation of the second aspect, the processing module is further configured to adjust the operation of sending measurement reports to the source network device when the number of times the terminal device experiences an anomaly within a preset time is greater than or equal to a preset threshold after the sending module sends the control RRC reconfiguration completion message; wherein the adjustment operation includes: changing the time of sending the measurement report, changing the content of sending the measurement report, or stopping the sending of the measurement report; the anomalies include: receiving a paging message sent by the target network device, failing to verify the integrity of a message sent by the target network device, or not receiving valid downlink data sent by the target network device.

[0015] Thirdly, a communication device is provided, comprising a processor and a memory; the memory stores instructions; the processor is used to execute the instructions, causing the communication device to perform the communication method provided by the first aspect or any possible implementation thereof.

[0016] Fourthly, a computer-readable storage medium is provided, which stores instructions that, when executed on a terminal device, cause the terminal device to perform the communication method provided by the first aspect or any possible implementation thereof.

[0017] Fifthly, a computer program product is provided, comprising a computer program that, when run on a terminal device, causes the terminal device to perform the communication method provided by the first aspect or any possible implementation thereof.

[0018] It is understood that the beneficial effects that the communication device provided above can be referred to in the first aspect above or any possible implementation of the first aspect in the communication method, and will not be repeated here. Attached Figure Description

[0019] Figure 1 A schematic diagram illustrating different states of a terminal device provided in an embodiment of this application;

[0020] Figure 2 A schematic diagram of key deduction provided for an embodiment of this application;

[0021] Figure 3 This application provides a schematic diagram of a control plane protocol stack in a mobile communication technology.

[0022] Figure 4 A flowchart illustrating a communication method provided in an embodiment of this application;

[0023] Figure 5 A flowchart illustrating another communication method provided in an embodiment of this application;

[0024] Figure 6 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0025] Figure 7 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0026] Figure 8 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0027] Figure 9 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0028] Figure 10 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0029] Figure 11 This is a schematic diagram of another communication device provided in an embodiment of this application;

[0030] Figure 12 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0031] The following sections will discuss the fabrication and use of various embodiments in detail. However, it should be understood that many applicable inventive concepts provided in this application can be implemented in a variety of specific environments. The specific embodiments discussed are merely illustrative of specific ways of implementing and using this application and technology, and do not limit the scope of this application.

[0032] Unless otherwise defined, all technical terms used herein have the same meaning as commonly known to one of ordinary skill in the art.

[0033] Each circuit or other component may be described or referred to as "for" performing one or more tasks. In this context, "for" is used to imply a structure by indicating that the circuit / component includes a structure (e.g., a circuit system) that performs one or more tasks during operation. Therefore, even when the specified circuit / component is currently inoperable (e.g., not turned on), it can still be referred to as "for performing that task." Circuits / components used with the term "for" include hardware, such as circuits that perform operations.

[0034] The technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings. In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, a, b, and c; where a, b, and c can be single or multiple.

[0035] The embodiments of this application use terms such as "first" and "second" to distinguish objects with similar names, functions, or effects. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or order of execution. The term "coupling" is used to indicate an electrical connection, including direct connection via wires or terminals or indirect connection via other devices. Therefore, "coupling" should be considered as a broad type of electronic communication connection.

[0036] It should be noted that, in this application, the terms "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0037] Before introducing the embodiments of this application, the technical terms involved in this application will be explained first.

[0038] Combination Figure 1 First, the three radio resource control (RRC) states of the terminal device will be explained. This terminal device can also be referred to as user equipment (UE).

[0039] 1. Idle state

[0040] The idle state can be the state in which the terminal device is not connected to the network device. In this application, the idle state generally refers to the RRC idle state unless otherwise specified.

[0041] For example, in the idle state, the terminal device can perform procedures such as public land mobile network (PLMN) selection, cell selection, cell reselection, and system message broadcasting. Furthermore, in the idle state, since the terminal device is not connected to the network device, does not access the network, does not occupy the network device's service resources, and does not obtain the terminal device's context and key, it cannot transmit service data.

[0042] 2. Connected state

[0043] The connection state can be the state that the terminal device is in after completing the connection with the network device. In this application, the connection state generally refers to the RRC connection state unless otherwise specified.

[0044] For example, in connected mode, the terminal device can obtain the context and key from the network device to transmit service data using the context and key.

[0045] Optionally, the terminal device can enter the connected state from the idle state. For example, in the idle state, the terminal device can establish an RRC connection with the network device by sending an RRC connection establishment request to the network device, thereby entering the connected state. Alternatively, the terminal device can also enter the connected state from the inactive state. For example, in the inactive state, the terminal device can restore the RRC connection with the network device by sending an RRC recovery request to the network device, thereby entering the connected state. Furthermore, in the connected state, the terminal device can also release to the idle or inactive state based on an RRC release message sent by the network device, thereby reducing resource overhead, lowering power consumption, and improving the terminal device's battery life. This RRC release message is defined in the 3rd Generation Partnership Project (3GPP)-38300 standard protocol; if it is a release with a pending state, it releases to the inactive state; if it is a release without a pending state, it releases to the idle state.

[0046] 3. Inactive state

[0047] The inactive state can be an intermediate state between the connected state and the idle state. In this application, the inactive state generally refers to the RRC inactive state, which can also be called the "third state".

[0048] For example, after a terminal device is released from the connected state to the inactive state, it can delete the key but retain the context so that it can quickly restore to the connected state later. In the inactive state, the terminal device can perform cell reselection and send RRC messages, such as RRC recovery request messages, to perform early data transmission, thereby reducing resource overhead and improving communication efficiency.

[0049] 4. Key deduction

[0050] In both inactive and connected states, to ensure secure data transmission between the terminal device and the network device, both devices need to perform key derivation to ensure that the key used for data encryption is continuously updated, thereby guaranteeing the security of data transmission.

[0051] Specifically, the following is combined with Figure 2 The key derivation process is explained in detail using a terminal device as an example.

[0052] according to Figure 2 As shown in the process, the terminal device can perform key deduction using the algorithm within its context. For example, the terminal device can obtain the key K from the core network in advance. AMF Using this key K AMF Derive the initial key K used for key derivation. gNB Using key K AMF and initial key K gNB The next hop parameter (NH) used for key derivation is derived, referred to here as NH1. Further, the terminal device can calculate the network hop chaining count (NCC) 0, which is a preset next hop chain with a value of 0, and then compare it with the initial key K. gNB It is associated with NH1. In this way, after receiving NCC1 from the network device, the terminal device can determine whether the value of NCC1 is the same as that of NCC0. If they are the same, the terminal device uses the initial key K associated with NCC0. gNB Perform horizontal deduction; otherwise, perform vertical deduction based on NH1 associated with NCC0 to determine the latest key. The procedures for horizontal and vertical deduction are described below.

[0053] Horizontal deduction:

[0054] If the terminal device receives the above NCC1=NCC0 from the network device, it can perform horizontal deduction, that is, based on the initial key K. gNB (the initial key K) gNB It can be considered as K gNB1 ), and deduce the key K from the physical cell identifier (PCI) and carrier frequency of the target cell of the terminal device. gNB2 Thus, the terminal device stores a pair of K... gNB And NH, can be obtained from the initial key K gNB Update NH1 to key K gNB2The association between NCC0 and NH1 can be updated as follows: NCC0 is associated with key K respectively. gNB2 Associated with NH1. Then, the terminal device can use the key K gNB2 The keys K_RRCint, K_RRCenc, K_UPenc, and K_UPint are derived. Keys K_UPint and K_RRCint can be used for data integrity protection, while keys K_RRCenc and K_UPenc can be used for data encryption.

[0055] Subsequently, if the terminal device receives the aforementioned NCC1 from the network device, it can continue to perform horizontal deduction, that is, based on the key K. gNB2 The PCI and carrier frequency of the target cell of the terminal device are used to deduce the key K. gNB3 Thus, the terminal device stores a pair of K... gNB And NH, can be obtained from key K gNB2 Update NH1 to key K gNB3 The association between NCC0 and NH1 can also be updated to: NCC0 is associated with key K respectively. gNB3 Associated with NH1. Then, the terminal device can use the key K. gNB3 The key K_RRCint, key K_RRCenc, key K_UPenc, and key K_UPint are derived, and the previously derived key K_RRCint, key K_RRCenc, key K_UPenc, and key K_UPint are deleted, and so on.

[0056] Vertical extrapolation:

[0057] If the terminal device receives NCC2 from the network device, and the value of NCC2 is 2, which is different from the value of NCC0 (0), meaning the difference between NCC2 and NCC0 is greater than 0, then vertical deduction can be performed, i.e., based on the key K. AMF From NH1, NH2 is derived. And from key NH1, the PCI and carrier frequency of the target cell of the terminal device, key K is derived. gNB4 Thus, the terminal device stores a pair of K... gNB And NH, can be obtained from the initial key K gNB Update NH1 to key K gNB4 And NH2, and the association can also be updated so that NCC2 is associated with key K respectively. gNB4 Associated with NH2. Then, the terminal device can use the key K gNB4 The keys K_RRCint, K_RRCenc, K_UPenc, and K_UPint are derived.

[0058] Among them, the terminal device is based on key KgNB4 Deducing the key K gNB5 and key K gNB6 The process and the deduction of the key K in the horizontal direction mentioned above gNB2 and key K gNB3 The process is similar and will not be repeated here.

[0059] Subsequently, if the terminal device receives NCC3 from the network device, and the value of NCC3 is 3, which is different from the value of NCC2 (2), then vertical deduction can continue, that is, it can proceed based on the key K. AMF From NH2, NH3 is derived; and based on NH2, the PCI and carrier frequency of the target cell of the terminal equipment, the key K is derived. gNB7 Thus, the terminal device stores a pair of K... gNB And NH, can be produced by K gNB4 And NH2 is updated to key K gNB7 And NH3, and the association can also be updated so that NCC3 is associated with key K respectively. gNB7 Associated with NH3. Then, the terminal device can use the key K gNB7 The process derives the keys K_RRCint, K_RRCenc, K_UPenc, and K_UPint, and deletes the previously derived keys K_RRCint, K_RRCenc, K_UPenc, and K_UPint, and so on.

[0060] Among them, the terminal device is based on key K gNB7 Deducing the key K gNB8 and key K gNB9 The process and the deduction of the key K in the horizontal direction mentioned above gNB2 and key K gNB3 The process is similar and will not be repeated here.

[0061] Similarly, if the terminal device receives NCC4 from the network device, and the value of NCC3 is 4, the terminal device can deduce the key K. gNB10 To key K gNB12 The process is similar to the one described above, and will not be repeated here.

[0062] In summary, since each NCC can be paired with a pair of NH and K gNB For example, NCC0 can be associated with the initial key K. gNB And NH1 or related K gNB2 K can be associated with NH1 and NCC2. gNB4 and NH2 or related K gNB5 K can be associated with NH2 and NCC3. gNB7 And NH3 or related K gNB8With NH3, the terminal device can quickly perform horizontal or vertical deduction based on the pair of NH and KgNB associated with the NCC, ensuring the efficiency of key deduction. The key and NCC can be collectively referred to as security parameters.

[0063] 5. Cell handover

[0064] As mentioned earlier, in connected mode, a terminal device can switch from its currently camped cell (the source cell) to another cell (the target cell). Cell handover can include intra-site handover and inter-site handover. Intra-site handover refers to a terminal device switching from one cell of the same base station to another, while inter-site handover refers to a terminal device switching from one cell of one base station to another.

[0065] 6. Control plane protocol stack in mobile communication technology.

[0066] In the 3rd Generation Partnership Project (3GPP)-38300 standard protocol, the terminal device is described as the UE, such as... Figure 3 As shown, the UE's non-access-stratum (NAS) can interact with the NAS of the access and mobility management function (AMF) in the core network, and the UE's RRC layer can interact with the RRC layer of the next-generation NodeB (gNB) in the access network. Similarly, the UE's packet data convergence protocol (PDCP) layer can interact with the gNB's PDCP layer. The UE's radio link control (RLC) layer can interact with the gNB's RLC layer. The UE's media access control (MAC) layer can interact with the gNB's MAC layer. The UE's physical (PHY) layer can interact with the gNB's PHY layer.

[0067] In this process, both the UE and gNB transmit and receive messages layer by layer according to their respective layers. For example, when the UE sends a message to the gNB, the UE's RRC layer forwards the message to the UE's PHY layer in the direction from the RRC layer to the PHY layer. The UE's PHY layer then sends the message to the gNB's PHY layer. When the gNB's PHY layer receives a message from the UE, it forwards the message to the gNB's RRC layer in the direction from the PHY layer to the RRC layer.

[0068] Before introducing the specific implementation examples, we will first introduce and explain the relevant knowledge about cell handover.

[0069] In fifth-generation (5G) communication systems, terminal devices exist in three states: connected (RRC-connected), idle (RRC-idle), and inactive. In the connected state, the terminal device can communicate with network devices (such as base stations). When the terminal device moves, cell handover ensures its continued connectivity; cell handover refers to the terminal device switching from the source base station's cell to the target base station's cell.

[0070] Specifically, during cell handover, the source base station sends multiple handover requests to the target base station through the core network. Each time the core network receives a handover request, it counts the corresponding NCC value and performs a key deduction to determine a new key. When the NCC value reaches its maximum value, it flips back to the initial value of 0. Multiple handover requests result in multiple key deductions by the core network. When the target base station agrees to the handover request, it sends a handover message to the terminal device. This message includes the current NCC value from the core network. The terminal device performs key deduction based on the difference between the NCC value in the handover message and its own NCC value. If the number of consecutive key deductions by the core network exceeds the maximum NCC value, the number of key deductions performed by the terminal device may differ from the number performed by the core network. This discrepancy between the security parameters of the terminal device and the target base station will prevent the target base station's RRC layer from receiving the handover completion message from the terminal device within a preset time period, ultimately preventing normal communication between the terminal device and the target base station.

[0071] In one possible embodiment, if the RRC layer of the target base station does not receive a handover completion message within a preset time period, the target base station sends a message to the terminal device to release the RRC connection with the target base station. After the terminal device fails to verify the integrity of the message, the terminal device sends an RRC reconstruction request to the target base station. The terminal device and the target base station then re-align their security parameters to ensure that the security parameters of the terminal device are consistent with those of the target base station.

[0072] In one possible embodiment, when the RRC layer of the target base station does not receive a handover completion message within a preset time period, the target base station sends a paging message to the terminal device. The terminal device releases the RRC connection with the target base station based on the paging message, that is, the terminal device migrates from the RRC connected state to the RRC idle state based on the paging message. The terminal device sends an RRC establishment request to the target base station, and the terminal device and the target base station re-align their security parameters so that the security parameters of the terminal device are consistent with those of the target base station.

[0073] However, both of the above schemes are triggered only after the target base station's RRC layer does not receive the handover completion message within a preset time period. During the preset time period, the terminal device and the target base station still cannot communicate normally, which reduces the user experience.

[0074] Based on this, embodiments of this application provide a communication method to solve the problem that inconsistent security parameters between terminal devices and network devices prevent them from communicating, thereby improving user experience.

[0075] The method provided in this application can be applied to various communication devices, which can be terminal devices. Optionally, the communication device can be a terminal device with wireless transceiver capabilities or a chip or chip system that can be configured in the terminal device.

[0076] The terminal device may include, but is not limited to: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), cameras, wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), audio equipment, audio and video players, set-top boxes, game consoles, printers, mice, keyboards, in-vehicle equipment (such as equipment on vehicles like cars, airplanes, ships, trains, and high-speed trains), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, intelligent robots, wireless terminals in self-driving, wireless terminals in transportation safety, and flying equipment (such as intelligent robots, hot air balloons, drones, and airplanes). This embodiment does not limit this.

[0077] Before introducing the embodiments of this application, firstly, in conjunction with Figure 4 The scenario described in this application is as follows. In the following embodiments, the terminal device is referred to as UE.

[0078] In this application, either the source network device or the target network device can include a 5th generation (5G) core network (5GC) and a new radio-radio access network (NR-RAN). The 5GC can include an AMF (Active Signalling Controller), which is used for UE access authentication, mobility management, signaling interaction between various functional network elements, and termination of non-access stratum (NAS) layer signaling security. This includes managing user registration status, reachability status, N1 / N2 interface signaling transmission, access authentication and authorization, user connection status, user registration and network access, cell handover user authentication, and key security.

[0079] Additionally, NR-RAN can include next-generation NodeBs (gNBs), which are devices deployed in NR-RAN that meet 5G standards to provide wireless communication functions for UEs. gNBs can be various forms of macro base stations and micro base stations. A gNB can include a central unit (CU) and a distributed unit (DU) integrated on it. In an architecture where CU and DU are separated, the gNB can be either a CU or a DU.

[0080] For ease of distinction, in the following embodiments, the AMF included in the source network device is referred to as the source AMF, and the gNB included in the source network device is referred to as the source gNB. Similarly, the AMF included in the target network device is referred to as the target AMF, and the gNB included in the target network device is referred to as the target gNB. Optionally, the source AMF and the target AMF can be AMFs corresponding to the same base station or AMFs corresponding to different base stations, and the source gNB and the target gNB can be the same base station or different base stations. This application does not specifically limit this aspect.

[0081] The following examples illustrate the situation by assuming that the source AMF and target AMF are AMFs of different base stations, and the source gNB and target gNB are different base stations.

[0082] For example, the source gNB communicates with the source AMF via the N2 interface, and the target gNB communicates with the target AMF via the N2 interface. The source gNB uses the source AMF to communicate with the target gNB through the target AMF.

[0083] Furthermore, cell A of the source network device refers to any cell within the coverage area of ​​the source gNB. Cell B of the target network device refers to any cell within the coverage area of ​​the target gNB. Cells covered by the source gNB include lightweight (Redcap) cells and non-Redcap cells. Non-Redcap cells refer to all cells covered by the source gNB except for Redcap cells. Cells covered by the target gNB also include Redcap and non-Redcap cells; similarly, non-Redcap cells refer to all cells covered by the target gNB except for Redcap cells.

[0084] Understandably, different types of cells support different types of UEs. For example, Redcap cells can support Redcap UEs, while non-Redcap cells can support ordinary UEs (non-lightweight UEs). This embodiment uses cells A and B as Redcap cells and Redcap UEs as examples. In practical applications, the UE can also be a non-Redcap UE.

[0085] like Figure 4 As shown, when the UE accesses cell A of the source gNB, that is, the UE camps or enters connected state in cell A of the source gNB, and completes security activation (assuming that the NCC values ​​of the UE, the source gNB, and the target gNB are all 0, and the keys of the UE, the source gNB, and the target gNB are all the initial key K). gNB After identity authentication, capability query, obtaining context, and host configuration, the following steps can be performed:

[0086] S401. The source gNB can send a measurement configuration message to the UE. Correspondingly, the UE can receive the measurement configuration message from the source gNB.

[0087] The measurement configuration message may include a measurement object, such as the synchronization signal and physical broadcast channel block (SSB) frequency, SSB subcarrier spacing, SSB measurement timing configuration (SMTC), channel status information-reference signal (CSI-RS) frequency, reference signal (RS) type, absolute threshold SSB or CSI-RS consolidation, the number of SSB or CSI-RS resources to be averaged (nrofSS-Blocks / CSI-RS-ResourcesToAverage), allowed cells, and excluded cells. The measurement configuration message may also include conditions related to parameter values. When the parameter values ​​measured by the UE meet the conditions in the measurement configuration message, a measurement report is sent to the source gNB, triggering step S403 below.

[0088] S402, the UE can send a configuration complete message to the source gNB. Correspondingly, the source gNB can receive the configuration complete message from the UE.

[0089] The UE performs measurements on the cell. In this embodiment, "performing measurements on the cell" means "measuring the cell's signal strength, signal quality, or energy." The cell's signal strength, signal quality, or energy can be characterized by at least one of the following parameters: reference signal received power (RSRP), received signal strength indication (RSSI), signal-to-interference plus noise ratio (SINR), or reference signal receiving quality (RSRQ). This is explained uniformly here and will not be repeated below.

[0090] S403. The UE can send a measurement report to the source gNB. Correspondingly, the source gNB can receive the measurement report from the UE.

[0091] The measurement report may include measurement results of the currently serving cell. It may also include measurement results of the best neighboring cell, or it may include measurement results of multiple neighboring cells. Measurement results may include the cell's signal strength, signal quality, or energy; that is, measurement results may include RSRP, RSSI, SINR, and RSRQ. The number of neighboring cells can be determined by the configured reporting quantity cell. The measurement results of all neighboring cells can be sorted in descending order of quality, and the aforementioned multiple neighboring cells can be the neighboring cells with the best measurement results among all neighboring cells.

[0092] For example, step S403 can be triggered when the parameter value measured by the UE meets the conditions in the measurement configuration message.

[0093] S404. The source gNB can send a first handover request to the source AMF. Specifically, the source gNB sends a first handover request to the source AMF if it determines that the handover conditions are met based on the measurement report. The first handover request instructs the UE to hand over from cell A of the source gNB to cell C of the target gNB, where cell C is a non-Redcap cell. Accordingly, the source AMF can receive the first handover request from the source gNB.

[0094] For example, after the source AMF receives the first handover request, the source AMF's NCC value (hereinafter referred to as the source NCC value) is automatically incremented by 1, and the source NCC value becomes 1. The source AMF then performs a horizontal key deduction to obtain the latest key K. gNB 1. This allows you to obtain the latest security parameters.

[0095] S405, the source AMF sends the first handover request to the target AMF. Accordingly, the target AMF can receive the first handover request from the source AMF.

[0096] For example, after the target AMF receives the first handover request, the target AMF's NCC value (hereinafter referred to as the target NCC value) is automatically incremented by 1, and the target NCC value becomes 1. The source AMF then performs a horizontal key deduction to obtain the key K with the source AMF. gNB 1. Same latest key K gNB 1. This allows you to obtain the latest security parameters.

[0097] S406, the target AMF sends the first handover request to the target gNB. Accordingly, the target gNB can receive the first handover request from the target AMF.

[0098] S407. The target gNB sends a handover failure message to the target AMF. Specifically, the target gNB determines that cell C is a non-Redcap cell and sends a handover failure message to the target AMF. Correspondingly, the target AMF can receive the handover failure message from the target gNB.

[0099] S408. The target AMF sends a handover failure message to the source AMF. Correspondingly, the source AMF can receive the handover failure message from the target AMF.

[0100] S409, the source AMF sends a handover failure message to the source gNB. Correspondingly, the source gNB can receive the handover failure message from the source AMF.

[0101] Furthermore, the source gNB reselects a cell that meets the handover conditions in the measurement report, similarly executing steps S404 to S409. Steps S404 to S409 are repeated N times. Here, N is greater than the NCC flip value; after the NCC value exceeds the flip value, the NCC value returns to its initial value of 0. The NCC flip value can be set according to actual needs or the experience of relevant personnel; for example, the NCC flip value can be 7. This application's embodiment does not impose specific limitations.

[0102] For example, assuming N=8, then both the source NCC value and the target NCC value are 1. Both the source AMF and the target AMF have undergone 8 horizontal key deductions to obtain the latest key K. gNB 8.

[0103] S410, the source gNB can send a second handover request to the source AMF. Specifically, if the source gNB determines that the handover conditions are met based on the measurement report, it can send a second handover request to the source AMF. The second handover request instructs the UE to hand over from cell A of the source gNB to cell B of the target gNB, where cell B is a Redcap cell. Correspondingly, the source AMF can receive the second handover request from the source gNB.

[0104] S411, the source AMF sends the second handover request to the target AMF. Accordingly, the target AMF can receive the second handover request from the source AMF.

[0105] S412, the target AMF sends the second handover request to the target gNB. Accordingly, the target gNB can receive the second handover request from the target AMF.

[0106] S413. The target gNB sends a handover request response to the target AMF. Specifically, the target gNB determines that cell B is a Redcap cell and sends a handover request response to the target AMF. Correspondingly, the target AMF can receive the handover request response from the target gNB.

[0107] S414. The target AMF sends a handover request response to the source AMF. Correspondingly, the source AMF can receive the handover request response from the target AMF.

[0108] S415. In response to the handover request, the source AMF sends a handover command to the source gNB. Accordingly, the source gNB receives the handover command from the source AMF.

[0109] S416. In response to sending a handover command, the source gNB sends an RRC reconfiguration message to the UE. Correspondingly, the UE can receive the RRC reconfiguration message from the source gNB. The RRC reconfiguration message instructs the UE to handover from cell A (within the source gNB) to cell B (within the target gNB).

[0110] S417. After receiving the RRC reconfiguration message, the UE performs a handover from cell A of the source gNB to cell B of the target gNB.

[0111] The RRC reconfiguration message includes a target NCC value of 1, while the UE's NCC value is 0. In practical applications, the UE performs one vertical key deduction and one horizontal key deduction based on the NCC difference of 1 to obtain the latest key K. gNB 1. Because the number of times the UE performs key deduction is different from the number of times the target gNB performs key deduction, the key K... gNB 1 and key K gNB 8. Different.

[0112] For example, after the UE hands over from cell A of the source gNB to cell B of the target gNB, the UE uses key K gNB 1. Send an RRC reconfiguration complete message to the target gNB, with key K. gNB 1. This is used for integrity protection and encryption of the RRC reconfiguration completion message. Specifically, the UE's PHY layer sends an RRC reconfiguration completion message to the target gNB's PHY layer. After receiving the RRC reconfiguration completion message, the target gNB forwards it layer by layer. When the target gNB's RLC layer receives the RRC reconfiguration completion message, the target gNB sends an RRC response to the UE. After receiving the RRC response from the target gNB, the UE determines that the handover is complete.

[0113] When the PDCP layer of the target gNB receives the RRC reconfiguration complete message, the PDCP layer uses key K... gNB 8. Perform integrity verification on the RRC reconfiguration completion message, due to key K. gNB 8 and key K gNB Unlike other methods, if PDCP integrity verification fails, PDCP stops delivering the RRC reconfiguration complete message to the target gNB's RRC layer. The target gNB's RRC layer then waits to receive the RRC reconfiguration complete message. For example, the target gNB's RRC layer can wait for 20 seconds.

[0114] Understandably, the above Figure 4 This explanation uses the example of multiple handover failures between the target gNB and the source gNB, resulting in a key inconsistency between the target gNB and the UE, as an example. In practical applications, the UE may also experience multiple handover failures; for example, the UE may fail to execute step S417 multiple times, leading to a key inconsistency between the target gNB and the UE. The communication method provided in this application is applicable to both of these scenarios.

[0115] The following is combined with Figures 5 to 8 The communication method provided in the embodiments of this application will be described and explained.

[0116] For example, Figure 5 This is a flowchart illustrating a communication method provided in an embodiment of this application. This communication method can be applied to a UE, a chip within the UE, or a chip system. For ease of description, "UE, chip within the UE, or chip system" will be collectively referred to as "UE" below. The communication method may include the following steps:

[0117] S501. After the UE switches from cell A of the source gNB to cell B of the target gNB, the UE sends an RRC reconfiguration complete message to the target gNB.

[0118] The RRC reconfiguration complete message indicates that the UE has switched from cell A of the source gNB to cell B of the target gNB.

[0119] S502a. If the UE does not receive valid downlink data from the target gNB within the first time period, the UE sends an RRC reconstruction request to the target gNB.

[0120] The first duration is less than a preset duration, which is the duration for the target gNB's RRC layer to wait for the RRC reconfiguration completion message. This preset duration can be set according to actual needs or the experience of relevant personnel; for example, it can be 20 seconds. In practical applications, the UE can determine this preset duration based on the interaction information with the target gNB, which may include tracking logs and monitoring information.

[0121] Among them, the situations in which the UE does not receive valid downlink data from the target gNB within the first time period include: the UE does not receive downlink data or downlink signaling within the first time period, or the downlink data received by the UE within the first time period is invalid data.

[0122] S503a, UE executes RRC reconstruction procedure.

[0123] In one possible embodiment, such as Figure 6 As shown, step S503 a may include:

[0124] S503a1: The UE receives an RRC establishment message from the target gNB.

[0125] Specifically, in response to the RRC establishment message, the UE switches from a secure active state to a non-secure active state. This is the UE procedure fallback.

[0126] S503a2: The UE sends an RRC establishment completion message to the target gNB.

[0127] For further information, please refer to [link / reference]. Figure 6 The method provided in this application embodiment further includes:

[0128] S504, the UE receives a security activation message from the target gNB.

[0129] In practical applications, after the target gNB sends a security activation message to the UE, the target gNB performs security activation, that is, the target gNB starts key deduction from target NCC=0 to determine the initial key K. gNB .

[0130] S505. In response to the security activation message, the UE performs security activation. Specifically, the UE starts key deduction from target NCC=0 to determine the initial key K. gNB .

[0131] S506, the UE sends a security activation complete message to the target gNB.

[0132] In this embodiment, when the UE does not receive valid downlink data from the target gNB within the first time period, the UE sends an RRC reconstruction request to the target gNB. The target gNB sends an RRC establishment message to the UE. When the UE receives the RRC establishment message from the target gNB, the UE switches from a secure active state to a non-secure active state, i.e., the UE performs secure fallback. After the UE sends an RRC establishment completion message to the target gNB, it performs secure activation based on the target gNB's secure activation message, ensuring that the target gNB's key and the UE's key are consistent and both are the initial key K. gNBThe NCC value of the target gNB and the NCC value of the UE are the same and both equal to 0, thereby realigning the security parameters of the target gNB and the security parameters of the UE, enabling the UE to communicate normally with the target gNB in ​​the first time period and improving the user experience.

[0133] In one possible embodiment, such as Figure 7 As shown, step S503a may include:

[0134] S503a3: The UE receives an RRC reconstruction message from the target gNB. This RRC reconstruction message includes the NCC value of the target gNB.

[0135] Specifically, in response to the RRC reconstruction message, the UE performs key deduction based on the NCC value in the RRC reconstruction message to obtain the latest security key.

[0136] S503a4: The UE sends an RRC reconstruction complete message to the target gNB.

[0137] In this embodiment, when the UE does not receive valid downlink data from the target gNB within the first time period, the UE sends an RRC reconstruction request to the target gNB. The target gNB sends an RRC reconstruction message to the UE. When the UE receives the RRC reconstruction message from the target gNB, the UE performs key deduction based on the NCC value carried in the RRC reconstruction message to obtain the latest key, that is, the UE refreshes the security parameters, thereby re-aligning the security parameters of the target gNB and the UE, enabling the UE to communicate normally with the target gNB within the first time period, thus improving the user experience.

[0138] In one possible embodiment, such as Figure 8 As shown, after step S501, the method provided in this application embodiment further includes:

[0139] S507, UE releases RRC connection with target gNB.

[0140] Among them, the release of the RRC connection between the UE and the target gNB means that the UE's state transitions from the connected state to the idle state, and the UE switches from the secure active state to the insecure active state.

[0141] S502b: If the UE does not receive valid downlink data from the target gNB within the first time period, the UE sends an RRC establishment request to the target gNB.

[0142] S503b, UE executes the RRC establishment process.

[0143] In one possible embodiment, such as Figure 9 As shown, step S503b may include:

[0144] S503b1, The UE receives the RRC establishment message sent by the target gNB.

[0145] S503b2, The UE establishes an RRC connection with the target gNB. After establishing the RRC connection with the target gNB, the UE's state transitions from idle state to connected state.

[0146] S503b3, the UE sends an RRC establishment completion message to the target gNB.

[0147] Furthermore, as the UE transitions from the idle state to the connected state, it needs to reactivate its security. Specifically, the UE executes steps S504 to S506 to ensure that the target gNB's key and the UE's key are identical and both are the initial key K. gNB This allows the UE to communicate normally with the target gNB within the first time period, improving the user experience.

[0148] In this embodiment, when the UE does not receive valid downlink data from the target gNB within a first time period, the UE releases the RRC connection with the target gNB and switches from a secure active state to a non-secure active state. The UE sends an RRC establishment request to the target gNB to establish an RRC connection. When the UE receives a secure activation message from the target gNB, it performs secure activation, ensuring that the key of the target gNB and the key of the UE are consistent and both are the initial key K. gNB The NCC value of the target gNB and the NCC value of the UE are the same and both equal to 0, thereby realigning the security parameters of the target gNB and the security parameters of the UE, enabling the UE to communicate normally with the target gNB in ​​the first time period and improving the user experience.

[0149] In one possible embodiment, after step S501, the method provided in this application further includes:

[0150] If the number of times the UE exhibits anomalies within a preset time period exceeds or equals a preset threshold, the operation of sending measurement reports to the source gNB will be adjusted. This adjustment includes: changing the time of measurement report transmission, changing the content of the measurement report, or stopping the transmission of measurement reports. Anomalies include: the UE receiving a paging message from the target gNB (which is typically received when the UE is in an idle or inactive state), the integrity verification of a message received from the target gNB failing, or not receiving valid downlink data from the target gNB.

[0151] The preset time and the preset threshold can be set according to actual needs or the experience of relevant personnel. For example, the preset time can be 15 seconds and the preset threshold can be greater than or equal to 1. This application does not make specific limitations on this.

[0152] Additionally, changing the timing of measurement report transmission means that the UE sends a measurement report before or after the first time when the next time to send a measurement report is set as the first time. Changing the content of the measurement report transmission means that the UE changes at least one parameter of the cell's RSRP, RSSI, SINR, or RSRQ in the measurement report at the first time. For example, it might lower at least one parameter of the RSRP, RSSI, SINR, or RSRQ of a cell that failed handover (e.g., cell C), raise at least one parameter of the RSRP, RSSI, SINR, or RSRQ of a cell that successfully handed over (e.g., cell B), delete a cell that failed handover, or add a new cell. Alternatively, the UE might stop sending measurement reports at the first time, meaning the UE does not report measurement reports at the first time.

[0153] In this embodiment, by adjusting the operation of sending measurement reports to the source gNB, the measurement reports received by the source gNB are different from those received in step S503, thereby improving the handover success rate of the source gNB during the next cell handover.

[0154] In this embodiment, after the terminal device switches from the cell of the source network device to the cell of the target network device, it sends a Radio Resource Control (RRC) reconfiguration completion message to the target network device. If the terminal device does not receive valid downlink data from the target network device within a first time period, the terminal device sends an RRC reconstruction request or an RRC establishment request to the target network device. The terminal device executes the RRC reconstruction procedure or the RRC establishment procedure. During this process, the terminal device and the target network device reactivate the security key, so that the security parameters of the terminal device and the security parameters of the target network device are aligned, that is, the security parameters of the terminal device and the security parameters of the target network device are consistent, thereby enabling the terminal device to communicate normally with the target network device within the first time period, improving the user experience.

[0155] The above primarily describes the solutions provided by the embodiments of this application from the perspective of the terminal device. It is understood that, in order to achieve the above functions, the terminal device includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0156] This application embodiment can divide the terminal device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the division of functional modules according to each function as an example.

[0157] When using integrated units, Figure 10 A schematic diagram of a communication device according to the above embodiments is shown. The communication device may include: a transmitting module 901, a processing module 902, and a receiving module 903. The transmitting module 901 can be used to support the communication device in performing steps S401, S402a, and S402b in the above method embodiments, and / or other transmitting steps in the embodiments of this application; the processing module 902 can be used to support the communication device in performing steps S403a and S403b in the above method embodiments, and / or other steps in the embodiments of this application; the receiving module 903 can be used to support the communication device in performing steps S403a1 and S403b1 in the above method embodiments, and / or other receiving steps in the embodiments of this application.

[0158] In one possible embodiment, such as Figure 11 As shown, the transmitting module 901 and the receiving module 903 can be integrated together and referred to as the transceiver module 904.

[0159] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here in the embodiments of this application.

[0160] Based on the hardware implementation, the processing module 902 can be a processor, the sending module 901 can be a transmitter, the receiving module 903 can be a receiver, and the transceiver module 904 can be a transceiver.

[0161] For example, such as Figure 12 As shown, the communication device may include a processor 110, a memory 111, a transceiver 112, and a bus 113. The processor 110, memory 111, and transceiver 112 are coupled via the bus 113.

[0162] The processor 110 is the control center of the communication device and can be a single processor or a collective term for multiple processing elements. For example, the processor 110 can be one or more central processing units (CPUs), application-specific integrated circuits (ASICs), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0163] Optionally, the processor 110 can perform various functions of the communication device by running or executing software programs stored in the memory 111 and calling data stored in the memory 111.

[0164] In a specific implementation, as one example, the processor 110 may include one or more CPUs, for example... Figure 12 CPU0 and CPU1 are shown in the diagram.

[0165] In a specific implementation, as one example, the communication device may also include multiple processors, for example... Figure 12 The processors 110 and 114 shown are illustrated. Each of these processors can be a single-core processor or a multi-core processor. Here, "processor" can refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0166] The memory 111 is used to store the software program that executes the solution of this application, and is controlled by the processor 110 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.

[0167] Optionally, the memory 111 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 111 may be integrated with the processor 110 or exist independently, and may be connected via an interface circuit of a communication device (…). Figure 12 (Not shown in the image) is coupled to the processor 110, but this embodiment does not specifically limit this.

[0168] Transceiver 112 is used for communication with other communication devices. For example, when the communication device is a terminal device, transceiver 112 can be used to communicate with network devices or with another terminal device.

[0169] Optionally, transceiver 112 may include a receiver and a transmitter. Figure 12 (Not shown separately). The receiver is used to implement the receiving function, and the transmitter is used to implement the transmitting function.

[0170] Alternatively, the transceiver 112 can be integrated with the processor 110, or it can exist independently and be connected via the interface circuit of the communication device. Figure 12 (Not shown in the image) is coupled to the processor 110, but this embodiment does not specifically limit this.

[0171] It should be noted that, Figure 12 The structure of the communication device shown does not constitute a limitation on the communication device. Actual communication devices may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0172] Furthermore, the technical effects of the communication device can be referred to the technical effects of the communication method described in the above method embodiments, and will not be repeated here.

[0173] This application also provides a chip system that may include: a processor coupled to a memory for storing programs or instructions, wherein when the program or instructions are executed by the processor, the chip system implements the methods in any of the above method embodiments.

[0174] Optionally, the chip system may contain one or more processors. These processors can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0175] Optionally, the chip system may contain one or more memories. The memory may be integrated with the processor or disposed separately from it; this application does not limit this. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed separately on different chips. This application does not specifically limit the type of memory or the arrangement of the memory and processor.

[0176] For example, the chip system may 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 micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

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

[0178] It should also be 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 random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0179] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product may include one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium may be a solid-state drive.

[0180] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or 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 device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

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

[0182] 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 readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause the device to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0183] In another aspect of this application, a computer-readable storage medium is provided, which includes computer instructions that, when executed on a terminal device, cause the terminal device to perform the relevant steps in the above method embodiments.

[0184] In another aspect of this application, a computer program product containing instructions is provided, which, when run on a terminal device, causes the terminal device to execute the relevant steps in the above method embodiments.

[0185] Finally, it should be noted that the above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method includes: After the terminal device switches from the cell of the source network device to the cell of the target network device, it sends a Radio Resource Control (RRC) reconfiguration complete message to the target network device. If no valid downlink data is received from the target network device within a first time period, an RRC establishment request or an RRC reconstruction request is sent to the target network device. The first time period is less than a preset time period, which is the time that the RRC layer of the target network device waits to receive the RRC reconfiguration completion message. Execute the RRC creation process or the RRC reconstruction process.

2. The method according to claim 1, characterized in that, Before sending an RRC establishment request to the target network device, the method further includes: Release the RRC connection with the target network device; The execution of the RRC establishment process includes: Receive the RRC establishment message sent by the target network device; Establish an RRC connection with the target network device; Send an RRC establishment complete message to the target network device.

3. The method according to claim 1, characterized in that, The RRC reconstruction process includes: Receive an RRC establishment message from the target network device; In response to the RRC reconstruction message, switch from the secure active state to the insecure active state; Send an RRC establishment complete message to the target network device.

4. The method according to claim 1, characterized in that, The RRC reconstruction process includes: Receive an RRC rebuild message from the target network device; Send an RRC reconstruction complete message to the target network device.

5. The method according to any one of claims 1-4, characterized in that, After sending a Radio Resource Control (RRC) reconfiguration complete message to the target network device, the method further includes: If the number of times the terminal device experiences an anomaly within a preset time period is greater than or equal to a preset threshold, the operation of sending a measurement report to the source network device is adjusted; wherein, the adjustment operation includes: changing the time of sending the measurement report, changing the content of sending the measurement report, or stopping the sending of the measurement report; The anomalies include: receiving a paging message from the target network device, failing to verify the integrity of a message sent by the target network device, or not receiving valid downlink data from the target network device.

6. A communication device, characterized in that, The communication device includes a transmitting module and a processing module: The sending module is used to send a Radio Resource Control (RRC) reconfiguration complete message to the target network device after the terminal device switches from the cell of the source network device to the cell of the target network device. The sending module is further configured to send an RRC establishment request or an RRC reconstruction request to the target network device if no valid downlink data is received from the target network device within a first time period. The first time period is less than a preset time period, which is the time that the RRC layer of the target network device waits to receive the RRC reconfiguration completion message. The processing module is used to execute the RRC establishment process or the RRC reconstruction process.

7. The communication device according to claim 6, characterized in that, The communication device further includes: a receiving module; The processing module is further configured to release the RRC connection with the target network device before the sending module sends the RRC establishment request; The receiving module is used to receive the RRC establishment message sent by the target network device; The processing module is used to establish an RRC connection with the target network device; The sending module is also used to send an RRC establishment completion message to the target network device.

8. The communication device according to claim 6, characterized in that, The communication device further includes: a receiving module; The receiving module is used to receive an RRC establishment message from the target network device; The sending module is also used to send an RRC establishment completion message to the target network device.

9. The communication device according to claim 6, characterized in that, The communication device further includes: a receiving module; The receiving module is used to receive RRC reconstruction messages from the target network device; The sending module is also used to send an RRC reconstruction complete message to the target network device.

10. The communication device according to any one of claims 6-9, characterized in that, The processing module is further configured to adjust the operation of sending a measurement report to the source network device when the number of times the terminal device experiences an anomaly within a preset time is greater than or equal to a preset threshold after the sending module sends the control RRC reconfiguration completion message; wherein the adjustment operation includes: changing the time of sending the measurement report, changing the content of sending the measurement report, or stopping the sending of the measurement report; The anomalies include: receiving a paging message from the target network device, failing to verify the integrity of a message sent by the target network device, or not receiving valid downlink data from the target network device.

11. A communication device, characterized in that, The communication device includes a processor and a memory; the memory stores instructions; the processor is used to execute the instructions, causing the communication device to perform the communication method as described in any one of claims 1-5.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a terminal device, cause the terminal device to perform the communication method as described in any one of claims 1-5.

13. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a terminal device, causes the terminal device to perform the communication method as described in any one of claims 1-5.