WO2019096171A1 - Method and apparatus for requesting recovery of connection - Google Patents

Abstract

The present application provides a method and apparatus for requesting recovery of a connection. The method comprises: a terminal sends a connection recovery request message to a target base station; the terminal receives a connection recovery reject message and a message authentication code from the target base station, the connection recovery reject message comprising information of a timer, and the message authentication code being generated on the basis of an integrity protection key of a source base station and the information of the timer; and if the terminal verifies that the message authentication code is correct according to the information of the timer and an integrity protection key of the terminal, the terminal initiates a connection recovery requesting process according to the information of the timer. Before the terminal uses the information of the timer, the message authentication code is first verified, and if the verification is successful, the information of the timer is considered as not being modified by an attacker, so that the terminal initiates the connection recovery requesting process according to the information of the time, and thus the terminal can normally re-initiate a connection recovery request according to the information of the timer, and use of information of the timer that is tampered with by an attacker is effectively avoided.

Description

Method and device for requesting restoration of connection

This application claims the priority of the Chinese Patent Application filed on November 16, 2017, the disclosure of which is hereby incorporated by reference. Combined in this application.

Technical field

The present application relates to the field of mobile communications technologies, and in particular, to a method and apparatus for requesting to restore a connection.

Background technique

In long term evolution (LTE), the suspend and resume process can be used for narrowband internet of things (NB-IoT) terminals, ie, IoT devices with low mobility or low power consumption. Such as smart water meters.

When the base station informs the terminal to release the current connection in a suspended manner, the terminal and the base station delete the context of the part of the access layer, and also retain the context of the part of the access layer, such as the access layer key, the security capability of the terminal, and the current Selected security algorithms, etc. The terminal then enters an inactive state from the connected state. When the terminal wishes to resume the connection with the base station, it can quickly recover from the inactive state to the connected state.

In the fifth generation (5th generation, 5G) system and future communication systems, the above service flow can be extended to apply the suspend and resume process to an enhanced mobile broadband (eMBB) terminal such as a smart phone.

Due to the high mobility of the terminal, the base station to which the terminal is connected may change. Further, when the base station serves the terminal, a scenario of load balancing is considered. For example, when the terminal requests to recover from the inactive state to the connected state, if the load of the base station that the terminal currently wants to access is heavy, the base station will reject the access of the terminal, that is, reject the connection recovery request of the terminal. And sending the timer information to the terminal, the information of the timer is used to notify the terminal of the time of denying the access, and can also be understood as the minimum duration for waiting for the terminal to re-initiate the connection recovery request.

In the above scenario, there is a problem that if the attacker obtains the information of the timer sent by the base station to the terminal, the information of the timer may be tampered with. For example, if the attacker modifies the waiting time indicated by the timer information to a larger duration, the length of time for the terminal to re-initiate the connection recovery request is extended.

Summary of the invention

The present application provides a method and apparatus for requesting a recovery connection to solve the problem that the information of the timer is tampered with.

In a first aspect, the present application provides a method for requesting to restore a connection, including: a terminal sending a connection recovery request message to a target base station, where the connection recovery request message is used to request to restore a radio resource control (RRC) connection;

The terminal receives a connection recovery reject message and a message authentication code from the target base station, where the connection recovery reject message is used to indicate that the terminal is denied to restore the RRC connection, and the connection recovery reject message includes information of a timer. The message authentication code is generated according to an integrity protection key of the source base station and information of the timer;

If the terminal verifies that the message authentication code is correct according to the information of the timer and the integrity protection key of the terminal, the terminal initiates a connection recovery request procedure according to the information of the timer.

In the above method, the target base station generates the message authentication code according to the information of the timer, and the terminal checks the message authentication code before using the information of the timer. If the verification is correct, the information of the timer is not modified by the attacker. Therefore, the terminal initiates a connection recovery request process according to the information of the timer, so that the terminal can re-initiate the connection recovery request according to the information of the timer, thereby effectively avoiding the use of the timer of the timer falsified by the attacker.

In a possible implementation, the message authentication code is generated according to the integrity protection key of the source base station, the information of the timer, and the freshness parameter, and the message used by the message authentication code is generated twice. Sexual parameters are different.

The above method, by introducing the freshness parameter, makes the message authentication code generated each time different, which can effectively solve the problem that the attacker continuously sends the same connection recovery rejection message to the terminal and causes the terminal to sleep all the time.

In a possible implementation manner, the freshness parameter includes a number of rejections, and the number of rejections is used to indicate the number of times the terminal is rejected when attempting to resume the RRC connection.

In a possible implementation manner, the connection recovery request message includes an indication parameter, where the indication parameter is used to indicate the freshness parameter. Optionally, the freshness parameter comprises a packet data convergence protocol count PDCP COUNT, the indication parameter comprising part or all of the bits of the PDCP COUNT.

In a second aspect, the present application provides a method for requesting a connection to restore, comprising: receiving, by a source base station, information of a timer from a target base station; and the source base station protecting the density according to the information of the timer and the integrity of the source base station And generating a message authentication code, where the message authentication code is used for authenticity of the information that the terminal authenticates the timer; and the source base station sends the message authentication code to the target base station.

In a possible implementation, the source base station generates a message authentication code according to the information of the timer and the integrity protection key of the source base station, including: the source base station according to the information of the timer The integrity protection key and the freshness parameter of the source base station generate the message authentication code; wherein the freshness parameters used to generate the message authentication code twice are different.

In a possible implementation manner, the freshness parameter includes a number of rejections, and the number of rejections is used to indicate the number of times the terminal is rejected when attempting to resume the RRC connection.

In a possible implementation manner, the source base station may further receive an indication parameter from the target base station, where the indication parameter is used to indicate the freshness parameter.

In such an implementation, the freshness parameter may include a packet data convergence protocol count PDCP COUNT, the indication parameter including some or all of the bits of the PDCP COUNT. In a third aspect, the present application provides a method for requesting a connection to restore, comprising: receiving, by a source base station, a connection reject request message from a target base station, where the connection reject request message includes information of a timer, and the connection reject request message is used to indicate Rejecting the terminal to restore the radio resource control RRC connection; the source base station generates a message authentication code according to the connection reject request message and the integrity protection key of the source base station, where the message authentication code is used for the terminal authentication The validity of the information of the timer; the source base station sends the message authentication code to the target base station.

In a possible implementation, the source base station generates a message authentication code according to the connection reject request message and the integrity protection key of the source base station, including: the source base station according to the connection reject request message And the integrity protection key and the freshness parameter of the source base station generate a message authentication code; wherein the freshness parameters used to generate the message authentication code twice are different.

In a possible implementation manner, the freshness parameter includes a number of rejections, and the number of rejections is used to indicate the number of times the terminal is rejected when attempting to resume the RRC connection.

In a possible implementation manner, the source base station receives an indication parameter from the target base station, where the indication parameter is used to indicate the freshness parameter.

In such an implementation, the freshness parameter may include a packet data convergence protocol count PDCP COUNT, the indication parameter including some or all of the bits of the PDCP COUNT. In a fourth aspect, the application provides a method for requesting a connection to restore, comprising: receiving, by a target base station, a connection recovery request message from a terminal, where the connection recovery request message is used to request to restore a radio resource control RRC connection; if the target base station rejects Recovering the RRC connection, sending a connection recovery reject message and a message authentication code to the terminal, the connection recovery reject message includes information of a timer, and the connection reject request message is used to indicate that the terminal is refused to resume the RRC The message authentication code is used by the terminal to authenticate the validity of the timer.

In a possible implementation, the method may further include: the target base station transmitting information of the timer to a source base station; the target base station receiving the message authentication code from the source base station, the message The authentication code is generated by the source base station according to the integrity protection key of the source base station and the information of the timer.

In a possible implementation, the connection recovery request message includes an indication parameter, where the indication parameter is used to indicate a freshness parameter, and the target base station sends the indication parameter to the source base station; wherein the message The authentication code is generated by the source base station according to the integrity protection key of the source base station, the freshness parameter, and the information of the timer, and the freshness parameters used to generate the message authentication code twice are different.

In a possible implementation manner, the target base station sends the connection reject request message to a source base station; the target base station receives the message authentication code from the source base station, where the message authentication code is used by the source The base station generates according to the integrity protection key of the source base station and the connection reject request message.

In this implementation, the connection recovery request message may include an indication parameter, where the indication parameter is used to indicate a freshness parameter, and the method may further include: the target base station sending the indication parameter to the source base station; The message authentication code is generated by the source base station according to the integrity protection key of the source base station, the freshness parameter, and the connection rejection request message, and the freshness parameter used by the message authentication code is generated twice. different.

In a possible implementation manner, the method may further include: the target base station receiving a key from the source base station; and the target base station generating the message according to the information of the key and the timer Authentication Code.

In a possible implementation manner, the target base station generates the message authentication code according to the information of the key and the timer, including: the target base station according to the key, the timer The information and freshness parameters are generated, and the message authentication code is generated; wherein the freshness parameters used to generate the message authentication code two times are different.

In a possible implementation manner, the freshness parameter includes a number of rejections, and the number of rejections is used to indicate the number of times the terminal is rejected when attempting to resume the RRC connection.

In a possible implementation, the connection recovery request message includes an indication parameter, where the indication parameter is used to indicate the freshness parameter, and the freshness parameter includes a packet data convergence protocol count PDCP COUNT, the indication parameter Some or all of the bits of the PDCP COUNT are included.

In a possible implementation manner, the method may further include: the target base station receiving a key from the source base station; and the target base station generating the message according to the key and the connection request rejection message Authentication Code.

In a possible implementation manner, the target base station generates the message authentication code according to the key and the connection request rejection message, including: the target base station rejects according to the key, the connection request The message and the freshness parameter are generated, and the message authentication code is generated; wherein the freshness parameters used to generate the message authentication code two times are different.

In a possible implementation manner, the freshness parameter includes a number of rejections, and the number of rejections is used to indicate the number of times the terminal is rejected when attempting to resume the RRC connection.

In a possible implementation, the connection recovery request message includes an indication parameter, where the indication parameter is used to indicate the freshness parameter, and the freshness parameter includes a packet data convergence protocol count PDCP COUNT, the indication parameter Some or all of the bits of the PDCP COUNT are included.

In a fifth aspect, the present application provides a device, which may be a terminal or a chip in a terminal. The device has the functionality to implement the various embodiments of the first aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible design, when the device is a terminal, the terminal includes: a transmitting unit, a processing unit, and a receiving unit. The processing unit may for example be a processor, which may for example be a receiver, a transmitting unit, for example a transmitter. The receiver and transmitter include radio frequency circuits. Optionally, the terminal further comprises a storage unit, which may be, for example, a memory. When the terminal includes a storage unit, the storage unit stores a computer execution instruction, the processing unit is connected to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit, so that the terminal performs the request to restore the connection according to any one of the foregoing first aspects. Methods.

In another possible design, when the device is a chip in the terminal, the chip includes: a transmitting unit, a processing unit, and a receiving unit. The processing unit can be, for example, a processing circuit, which can be, for example, an input interface, a pin or a circuit, etc., and the transmitting unit can be, for example, an output interface, a pin or a circuit. The processing unit may execute a computer-executed instruction stored by the storage unit to cause the method of restoring the connection of any of the above-described first aspects to be performed. Optionally, the storage unit may be a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the terminal, such as a read-only memory (ROM), and may be stored. Other types of static storage devices, random access memory (RAM), etc. for static information and instructions.

The processor mentioned in any of the above may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more A program-implemented integrated circuit for controlling a method of requesting a resume connection of any of the above first aspects.

In a sixth aspect, the application provides a device, which may be a source base station or a chip in a source base station. The device has the functionality to implement the various embodiments of the second aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible design, when the device is a source base station, the base station includes: a receiving unit, a transmitting unit, and a processing unit. The processing unit may for example be a processor, which may for example be a receiver, a transmitting unit, for example a transmitter. The receiver and transmitter include radio frequency circuits. Optionally, the base station further comprises a storage unit, which may be, for example, a memory. When the base station includes a storage unit, the storage unit stores a computer execution instruction, the processing unit is coupled to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit to cause the base station to perform the request to restore the connection according to any one of the foregoing second aspects. Methods.

In another possible design, when the device is a chip in a source base station, the chip includes: a receiving unit, a transmitting unit, and a processing unit. The processing unit can be, for example, a processing circuit, which can be, for example, an input interface, a pin or a circuit, etc., and the transmitting unit can be, for example, an output interface, a pin or a circuit. The processing unit may execute a computer-executed instruction stored by the storage unit to cause the method of restoring the connection of any of the above-described second aspects to be performed. Optionally, the storage unit may be a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the terminal, such as a ROM only, other types of statics that can store static information and instructions. Storage device, RAM, etc.

Wherein, the processor mentioned in any of the above may be a general-purpose CPU, a microprocessor, an ASIC, or a program executed by one or more methods for controlling the connection recovery request of any of the above second aspects. integrated circuit.

In a seventh aspect, the application provides a device, which may be a source base station or a chip in a source base station. The device has the functionality to implement the various embodiments of the third aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible design, when the device is a source base station, the base station includes: a receiving unit, a transmitting unit, and a processing unit. The processing unit may for example be a processor, which may for example be a receiver, a transmitting unit, for example a transmitter. The receiver and transmitter include radio frequency circuits. Optionally, the base station further comprises a storage unit, which may be, for example, a memory. When the base station includes a storage unit, the storage unit stores a computer execution instruction, the processing unit is connected to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit, so that the base station performs the request to restore the connection according to any one of the foregoing third aspects. Methods.

In another possible design, when the device is a chip in a source base station, the chip includes: a receiving unit, a transmitting unit, and a processing unit. The processing unit can be, for example, a processing circuit, which can be, for example, an input interface, a pin or a circuit, etc., and the transmitting unit can be, for example, an output interface, a pin or a circuit. The processing unit may execute a computer-executed instruction stored by the storage unit to cause the method of restoring the connection of any of the above-described third aspects to be performed. Optionally, the storage unit may be a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the terminal, such as a ROM only, other types of statics that can store static information and instructions. Storage device, RAM, etc.

Wherein, the processor mentioned in any of the above may be a general-purpose CPU, a microprocessor, an ASIC, or a program executed by one or more methods for controlling the connection recovery request of any of the above third aspects. integrated circuit.

In an eighth aspect, the present application provides an apparatus, which may be a target base station or a chip in a target base station. The device has the functionality to implement the various embodiments of the fourth aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible design, when the device is a target base station, the base station includes: a receiving unit and a sending unit, and optionally, a processing unit. The processing unit may for example be a processor, which may for example be a receiver, a transmitting unit, for example a transmitter. The receiver and transmitter include radio frequency circuits. Optionally, the base station further comprises a storage unit, which may be, for example, a memory. When the base station includes a storage unit, the storage unit stores a computer execution instruction, the processing unit is coupled to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit to cause the base station to perform the request to restore the connection according to any one of the foregoing fourth aspects. Methods.

In another possible design, when the device is a chip in a target base station, the chip includes: a receiving unit and a transmitting unit, and optionally, a processing unit. The processing unit can be, for example, a processing circuit, which can be, for example, an input interface, a pin or a circuit, etc., and the transmitting unit can be, for example, an output interface, a pin or a circuit. The processing unit may execute a computer-executed instruction stored by the storage unit to cause the method of requesting to restore the connection of any of the above fourth aspects to be performed. Optionally, the storage unit may be a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the terminal, such as a ROM only, other types of statics that can store static information and instructions. Storage device, RAM, etc.

Wherein, the processor mentioned in any of the above may be a general-purpose CPU, a microprocessor, an ASIC, or a program executed by one or more methods for controlling a connection recovery connection according to any of the above fourth aspects. integrated circuit.

In a ninth aspect, the present application further provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the methods described in the above aspects.

In a tenth aspect, the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the various aspects above.

In an eleventh aspect, the present application provides a communication system, the system comprising the device of the fifth aspect, the device of the sixth aspect, and the device of the eighth aspect, or the system includes the fifth aspect The device, the device of the seventh aspect, and the device of the eighth aspect.

In addition, the technical effects brought by the implementation modes of the first aspect to the eleventh aspect can be referred to the technical effects brought by different implementation manners in the first aspect, and details are not described herein again.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

DRAWINGS

FIG. 1 is a schematic diagram of a possible network architecture provided by the present application;

2 is a schematic diagram of a method for requesting a connection to be restored according to the present application;

FIG. 3 is a flowchart of another method for requesting a recovery connection according to the present application; FIG.

4 is a flowchart of another method for requesting a recovery connection according to the present application;

FIG. 5 is a flowchart of another method for requesting a recovery connection according to the present application; FIG.

FIG. 6 is a flowchart of another method for requesting a recovery connection according to the present application; FIG.

Figure 7 is a schematic diagram of a device provided by the present application;

Figure 8 is a schematic diagram of another apparatus provided by the present application;

Figure 9 is a schematic view of another apparatus provided by the present application;

FIG. 10 is a schematic diagram of another apparatus provided by the present application.

Detailed ways

The present application will be further described in detail below with reference to the accompanying drawings. The specific method of operation in the method embodiments can also be applied to device embodiments or system embodiments. In the description of the present application, the meaning of "a plurality" is two or more unless otherwise stated.

It should be noted that the method of requesting to restore the connection of the present application may be performed by a device. Wherein, the device may include a device on the network side and/or a device on the terminal side. On the network side, the device may be a chip in the base station or the base station, that is, the method of requesting to restore the connection may be performed by the chip in the base station or the base station; on the terminal side, the device may be a chip in the terminal or the terminal, that is, The method of requesting to restore a connection of the present application can be performed by a chip in a terminal or a terminal. The base station may be a target base station or a source base station.

For convenience of description, the present application uses a device as a base station or a terminal as an example to describe a method for requesting to restore a connection. For a method in which a device is a chip in a base station or a chip in a terminal, the connection may be restored by referring to the request of the base station or the terminal. The specific description of the method is not repeated.

FIG. 1 is a schematic diagram of a possible network architecture of the present application. It includes a terminal, a source base station, and a target base station. The terminal communicates with the source base station and the target base station through a wireless interface. The source base station and the target base station can communicate through a wired connection, such as through an X2 interface, an Xn interface, or can communicate through an air interface.

In the present application, the terminal may move from the source base station to the target base station due to the movement of the terminal or the like. The source base station is a base station that the terminal accesses first, and the target base station is a base station that is accessed after the terminal moves.

Among them, the terminal is a device with wireless transceiver function, which can be deployed on land, indoors or outdoors, handheld or on-board; it can also be deployed on the water surface (such as ships); it can also be deployed in the air (such as airplanes, balloons). And satellites, etc.). The terminal may be a mobile phone, a tablet, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, industrial control (industrial control) Wireless terminal, wireless terminal in self driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety, A wireless terminal in a smart city, a wireless terminal in a smart home, and the like.

A base station is a device that provides wireless communication functions for a terminal, including but not limited to: a next-generation base station (g nodeB, gNB), an evolved node B (eNB), and a radio network controller (radio) in 5G. Network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved node B, or home node B) , HNB), BaseBand Unit (BBU), transmission and receiving point (TRP), transmitting point (TP), mobile switching center, etc.

In the present application, the terminal generally has three states, that is, a connected state, an idle state, and an inactive state.

Wherein, when the terminal is in the connected state, the terminal is in a normal working state. User data can be sent and received between the network side and the terminal.

When the terminal enters the idle state from the connected state, the terminal and the base station generally delete all the access stratum (AS) contexts of the terminal. In a special case, in 4G, when the network side releases the connection of the terminal by the suspend reason, the terminal also enters the idle state from the connected state, but at this time, the terminal and the base station delete part of the AS context, and retain A partial AS context, for example, may retain an access layer key (which may be referred to as KeNB in 4G), a security capability of the terminal, and a security algorithm (including an integrity protection algorithm and an encryption algorithm) for communication between the terminal and the source base station to which the terminal accesses. . The security capability of the terminal refers to the security algorithm supported by the terminal, including the supported encryption algorithm and the supported integrity protection algorithm. At this time, the special idle state in which the terminal is located may be referred to as a suspended state.

In 5G, an inactive state is introduced. When the terminal enters the inactive state from the connected state, the base station suspends the terminal. At this time, the terminal and the base station delete part of the AS context, and reserve part of the AS context, for example, the access layer may be reserved. The key (which can be called KgNB in 5G), the security capability of the terminal, and the security algorithm (including integrity protection algorithm and encryption algorithm) for communication between the terminal and the source base station accessed by the terminal. The security capability of the terminal refers to the security algorithm supported by the terminal, including the supported encryption algorithm and the supported integrity protection algorithm.

For convenience of explanation, the subsequent unification of the suspended state defined in 4G and the inactive state defined in 5G is called inactive state. When the terminal is in an inactive state, the base station connected to the terminal and the terminal before the terminal enters the inactive state will save part of the AS context. For details, refer to the foregoing description.

When the terminal is in an inactive state, since part of the AS context is reserved on the terminal, the terminal enters the connected state from the inactive state more quickly than when the terminal enters the connected state from the idle state.

In addition, considering the mobility of the terminal, when the terminal returns from the inactive state to the connected state, the terminal may need to replace the base station. That is, the terminal first establishes a connection with the source base station, and then the terminal enters an inactive state at the source base station for some reason, such as network side notification. When the terminal wishes to return to the connected state, if the terminal has moved to the coverage of the target base station, the terminal will resume from the inactive state to the connected state at the target base station.

Of course, the present application is also applicable to the scenario in which the target base station and the source base station are the same when the terminal is restored from the inactive state to the connected state, that is, the base station accessed by the terminal may not change, and is still the same base station.

The method for requesting a recovery connection provided by the present application is described below with reference to the accompanying drawings.

As shown in FIG. 2, a schematic diagram of a method for requesting a connection recovery provided by the present application includes the following steps:

Step 201: The terminal sends a connection recovery request message to the target base station, and the target base station receives a connection recovery request message from the terminal.

A connection recovery request message sent by the terminal, used to request to resume the RRC connection. That is, the terminal requests to return from the inactive state to the connected state.

Step 202: The target base station determines to reject the connection recovery request of the terminal.

For example, if the load of the target base station is relatively heavy and cannot access the terminal, the target base station may reject the connection recovery request of the terminal, that is, reject the terminal from accessing the target base station.

Step 203: The target base station sends a connection recovery reject message and a message authentication code to the terminal, where the terminal receives the connection recovery reject message and the message authentication code from the target base station.

The connection recovery reject message is used to indicate that the terminal is denied the RRC connection. The connection recovery refusal message carries the information of the timer, and the information of the timer is used to indicate the time for denying the terminal access, and can also be understood as the minimum duration for the terminal to wait for the terminal to re-request to resume the RRC connection. For example, if the timer indicates that the duration is 30 minutes, the terminal needs to wait at least 30 minutes to re-initiate the connection recovery request.

The message authentication code (MAC) is used for the validity of the information of the terminal authentication timer.

The message authentication code is generated based on the integrity protection key of the source base station and the information of the timer.

Alternatively, the message authentication code is generated according to the integrity protection key and the connection recovery rejection message of the source base station, wherein the connection recovery rejection message includes information of a timer, and optionally, the connection recovery rejection message further includes other information.

Step 204: If the terminal verifies that the message authentication code is correct according to the information of the timer and the integrity protection key of the terminal, the terminal initiates a connection recovery request process according to the information of the timer.

For example, the message authentication code sent by the target base station to the terminal is generated according to the integrity protection key of the source base station and the information of the timer, and the manner in which the terminal checks the message authentication code is: the terminal according to the information of the timer and The integrity protection key of the terminal generates a message authentication code. If the message authentication code is the same as the message authentication code sent by the target base station to the terminal, the verification is correct. If not, the verification fails.

If the verification message authentication code is correct, the terminal considers that the information of the timer is not modified by the attacker. Therefore, the terminal initiates a connection recovery request process according to the information of the timer, that is, re-initiates the connection recovery request according to the duration indicated by the information of the timer. .

If the verification message authentication code fails, the terminal ignores the information of the timer, that is, does not re-initiate the connection recovery request according to the duration indicated by the information of the timer.

Through the above steps 201-204, since the target base station generates the message authentication code according to the information of the timer, the terminal checks the message authentication code before using the information of the timer. If the verification is correct, the information of the timer is not found. The attacker modifies, so the terminal initiates a connection recovery request process according to the information of the timer, so that the terminal can re-initiate the connection recovery request according to the information of the timer, effectively avoiding the use of the timer of the tampering by the attacker.

The following example shows why an attacker cannot attack successfully. For example, the information of the timer included in the connection recovery rejection message sent by the target base station to the terminal is 30 minutes, and the message authentication code is generated according to the integrity protection key of the source base station and the information of the timer. The message authentication code sent by the base station to the terminal is generated according to the integrity protection key of the source base station for 30 minutes. The generated message authentication code is represented by MAC (30 minutes, Krrc-int1), where Krrc-int1 represents the integrity protection key of the source base station.

The target base station sends a MAC (30 minutes, Krrc-int1) and a connection recovery reject message to the terminal. The connection recovery reject message includes information of a timer, and the information of the timer indicates a duration of 30 minutes.

Assuming that the attacker modifies the duration indicated by the information of the timer included in the connection recovery rejection message to 100 minutes, the terminal will acquire the MAC (30 minutes, Krrc-int1), and acquire 100 minutes from the connection recovery rejection message.

Next, the terminal generates a message authentication code MAC (100 minutes, Krrc-int2) according to the acquired 100 minutes and the integrity protection key of the terminal (represented by Krrc-int2). Among them, Krrc-int1 and Krrc-int2 are the same under normal conditions.

It can be seen that the MAC generated by the terminal (100 minutes, Krrc-int2) and the MAC sent by the target base station to the terminal (30 minutes, Krrc-int1) are different because the durations in the input parameters are different, so the verification fails. . Thus, the terminal will ignore this information for 100 minutes. Therefore, the solution of the present application can protect the attacker from attack.

The following describes several methods for generating the message authentication code sent by the target base station.

Method 1: The source base station generates a message authentication code according to the information of the timer and the integrity protection key of the source base station.

As shown in FIG. 3, a flow chart of a method for requesting a connection recovery provided by the present application includes the following steps:

Steps 301 to 302 are the same as steps 201 to 202 shown in FIG. 2, and the foregoing description may be referred to.

Step 303: The target base station sends the information of the timer to the source base station, and the source base station receives the information of the timer from the target base station.

Step 304: The source base station generates a message authentication code according to the information of the timer and the integrity protection key of the source base station.

The integrity protection key of the source base station refers to the integrity protection key corresponding to the context of the terminal stored by the source base station, and the integrity protection key is generated according to the following manner: the source base station acquires the integrity in the context of the terminal. The protection algorithm (also referred to as the integrity protection algorithm of the source base station) and the access layer key, and then derive the integrity protection key according to the access layer key (which may be referred to as the integrity protection key of the source base station) ). Or, the source base station directly acquires an integrity protection algorithm in the context of the terminal (which may also be referred to as an integrity protection algorithm of the source base station) and an integrity protection key in the context of the terminal (which may be referred to as an integrity protection key of the source base station). key). The access layer key may also be an updated access layer key.

Step 305: The source base station sends a message authentication code to the target base station, and the target base station receives the message authentication code from the source base station.

Step 306-Step 307 is the same as Step 203-Step 204 shown in FIG. 2, and can refer to the foregoing description.

In the first method, the source base station generates a message authentication code according to the information of the timer and the integrity protection key of the source base station, and sends the message authentication code to the target base station.

Method 2: The source base station generates a message authentication code according to the connection reject request message and the integrity protection key of the source base station, where the connection reject request message includes information of a timer.

As shown in FIG. 4, a flow chart of a method for requesting a connection recovery provided by the present application includes the following steps:

Steps 401 to 402 are the same as steps 201 to 202 shown in FIG. 2, and may be referred to the foregoing description.

Step 403: The target base station sends a connection reject request message to the source base station, where the source base station receives a connection reject request message from the target base station, where the connection reject request message includes information of a timer.

The connection reject request message is that the target base station is configured to be sent to the terminal. Since the target base station does not have the context of the terminal, the message needs to be sent to the source base station, and the source base station performs protection.

Step 404: The source base station generates a message authentication code according to the connection reject request message and the integrity protection key of the source base station.

The source base station obtains the integrity protection key, which is the same as step 304 shown in FIG. 3, and can refer to the foregoing description.

Step 405: The source base station sends a message authentication code to the target base station, and the target base station receives the message authentication code from the source base station.

Step 406-Step 407 is the same as Step 203-Step 204 shown in FIG. 2, and may refer to the foregoing description.

In the second method, the source base station generates a message authentication code according to the connection reject request message and the integrity protection key of the source base station, and sends the message authentication code to the target base station. Since the connection rejection request message includes the information of the timer, the generated message authentication code can also secure the information of the timer. Correspondingly, when the terminal checks, the message authentication code is verified according to the received connection rejection request message and the integrity protection key of the terminal.

Method 3: The target base station generates a message authentication code according to the information of the timer and the integrity protection key of the source base station.

As shown in FIG. 5, a flow chart of a method for requesting a connection recovery provided by the present application includes the following steps:

Steps 501 to 502 are the same as steps 201 to 202 shown in FIG. 2, and the foregoing description may be referred to.

Step 503: The target base station sends a request message to the source base station.

The request message requests the source base station to acquire a key.

Step 504: The source base station sends a key to the target base station.

The key may be an integrity protection key of the source base station or an access layer key.

Step 505: The target base station generates a message authentication code according to the information and the key of the timer.

Specifically, if the key sent by the source base station is the integrity protection key of the source base station, the target base station generates a message authentication code according to the information of the timer and the integrity protection key of the source base station.

If the key sent by the source base station is an access layer key, the target base station generates an integrity protection key according to the access layer key, and then generates a message authentication code according to the timer information and the integrity protection key.

Steps 506 to 507 are the same as steps 203 to 204 shown in FIG. 2, and the foregoing description may be referred to.

In the third method, the target base station acquires a key from the source base station, and then generates a message authentication code according to the information and the key of the timer.

Method 4: The target base station generates a message authentication code according to the connection rejection request message and the integrity protection key of the source base station, where the connection rejection request message includes the timer information.

As shown in FIG. 6, a flowchart of a method for requesting a connection recovery provided by the present application includes the following steps:

Steps 601 to 602 are the same as steps 201 to 202 shown in FIG. 2, and the foregoing description may be referred to.

Step 603: The target base station sends a request message to the source base station.

The request message requests the source base station to acquire a key.

Step 604: The source base station sends a key to the target base station.

The key may be an integrity protection key of the source base station or an access layer key.

Step 605: The target base station generates a message authentication code according to the connection rejection request message and the key. The connection rejection request message includes information of a timer.

Specifically, if the key sent by the source base station is the integrity protection key of the source base station, the target base station generates a message authentication code according to the connection reject request message and the integrity protection key of the source base station.

If the key sent by the source base station is an access layer key, the target base station generates an integrity protection key according to the access layer key, and then generates a message authentication code according to the connection rejection request message and the integrity protection key.

Step 606-Step 607 is the same as Step 203-Step 204 shown in FIG. 2, and can refer to the foregoing description.

In the fourth method, the target base station acquires a key from the source base station, and then generates a message authentication code according to the connection rejection request message and the key.

For the method of requesting to restore the connection shown in FIG. 2, another attack scenario is considered: after acquiring the message authentication code and the timer information sent by the target base station to the terminal, the attacker does not modify the timer information, but continuously Replaying, that is, repeating the above step 203, causing the terminal to continuously sleep, causing an attack on the terminal.

As an example, assume that the information of the timer that the target base station sends to the terminal for the first time indicates a duration of 30 minutes, and the message authentication code is MAC (30 minutes, Krrc-int1), where Krrc-int1 is the integrity of the source base station. Protect the key, then:

The target base station transmits a connection recovery reject message and a MAC (30 minutes, Krrc-int1) to the terminal through the above-mentioned step 203, and the information indicated by the timer included in the connection recovery rejection message is 30 minutes. After verifying the MAC (30 minutes, Krrc-int1), the terminal enters 30 minutes of sleep.

Before the arrival of 30 minutes, the attacker sends a connection recovery rejection message and MAC to the terminal (30 minutes, Krrc-int1), the terminal will still verify the MAC (30 minutes, Krrc-int1) successfully, and then enter 30 minutes of sleep. .

Then, before the arrival of 30 minutes, the attacker sends a connection recovery rejection message and MAC to the terminal (30 minutes, Krrc-int1), the terminal will still verify the MAC (30 minutes, Krrc-int1) successfully, and then enter 30 again. Minutes of sleep. In this way, the terminal will sleep all the time, and the connection recovery request cannot be successful.

In order to solve the above problems, the present application provides a corresponding solution.

The solution provided by the present application is improved on the basis of the above-mentioned FIG. 2 to FIG. 6, and the object of solving the above problems has been achieved. Specifically, freshness parameters are introduced to solve the above problems, which are specifically described below.

For the foregoing process shown in FIG. 2, the connection recovery request message in step 201 carries an indication parameter, and the indication parameter is used to indicate a freshness parameter.

The freshness parameter may be used by the target base station to generate a message authentication code, that is, in the above step 203, the message authentication code sent by the target base station to the terminal is generated according to the freshness parameter.

Specifically, the target base station generates a message authentication code according to the integrity protection key of the source base station, the information of the timer, and the freshness parameter. Alternatively, the target base station generates a message authentication code according to the integrity protection key of the source base station, the connection recovery rejection message, and the freshness parameter, where the connection recovery rejection message includes information of the timer.

Moreover, the freshness parameters used to generate the message authentication code two times are different. That is, the specific value of the freshness parameter changes every time the message authentication code is generated, so that the freshness parameter used when generating the message authentication code is different from the freshness parameter used when the message authentication code is generated last time. .

As an implementation manner, the freshness parameter includes a Packet Data Convergence Protocol (PDCP) count (COUNT), and the PDCP COUNT may include an uplink PDCP COUNT and a downlink PDCP COUNT, and the terminal uplinks every time an uplink PDCP packet is sent. The PDCP COUNT is incremented by 1, and the downlink PDCP COUNT is incremented by one for each downlink PDCP packet sent by the base station. For example, the PDCP COUNT may be the uplink PDCP COUNT of the signaling radio bearer (SRB). Optionally, whenever the wireless is re-established At the time of bearer, the PDCP COUNT can be reset to zero. Since the PDCP COUNT is constantly changing, the message authentication code generated by the terminal each time is different from the last generated message authentication code.

The connection recovery request message sent by the terminal to the target base station carries an indication parameter, where the indication parameter is used to indicate a freshness parameter.

Specifically, the indication parameter may be the freshness parameter itself, or may be a parameter indicating the freshness parameter.

For example, if the freshness parameter is PDCP COUNT and the PDCP COUNT is represented by a binary bit, the indication parameter may be the PDCP COUNT itself, that is, all bits of the PDCP COUNT. The indication parameter can also be a partial bit of the PDCP COUNT.

For example, suppose the PDCP COUNT is represented by 32 bits. Since the change between the PDCP COUNTs used when generating the message authentication code two times is not particularly large, between two adjacent PDCP COUNTs Only the lower bits change, and the higher bits do not change. Therefore, the indication parameter can be represented using a portion of the low bit of the PDCP COUNT. For example, the PDCP COUNT used by the terminal to generate the message authentication code is “00000000000011111111111100011111”, and the PDCP COUNT used by the terminal to generate the message authentication code is “00000000000011111111111100100011”. It can be found that only the lower 5 bits of the PDCP COUNT have changed. The high 27 did not change. Therefore, the lower N bits of the PDCP COUNT can be selected as the indication parameter, N being greater than 1, and less than 32. Of course, the indication parameter can also be all bits of the PDCP COUNT.

As another implementation manner, the freshness parameter may include the number of rejections, and the number of rejections may be used to indicate the number of times the terminal attempts to restore the RRC connection rejected by the network side. Each time the terminal attempts to resume being rejected by the network side, the number of rejections is increased by one. Alternatively, the number of rejections may be reset to zero each time the RRC connection is successfully restored. Since the number of rejections is always changing, the message authentication code generated by the terminal each time is different from the message authentication code generated last time.

It should be noted that, when the freshness parameter includes the number of rejections, the terminal may not carry the indication parameter in the connection recovery request message. In a specific implementation, the terminal may determine the current number of rejections by itself, and the base station (such as the target base station or the source base station) may also determine the current number of rejections by itself. That is, the terminal and the target base station each maintain the number of times the terminal is refused to resume the connection. Alternatively, the terminal and the source base station each maintain the number of times the terminal is refused to resume the connection.

For example, after receiving the connection rejection request message, the terminal verifies that the message authentication code passes, and the terminal updates the number of rejections, including the number of rejections plus one. After receiving the timer or connection rejection request message sent by the target base station, the source base station updates the number of rejections, including the number of rejections plus one. After the target base station decides to reject the terminal to resume the connection, the target base station updates the number of rejections, including the number of rejections plus one.

Of course, as another implementation, when the freshness parameter includes the number of rejections, the terminal may also carry an indication parameter in the connection recovery request message, where the indication parameter is used to indicate the number of rejections.

Through the above method, the message authentication code generated by the target base station is different from the message authentication code generated last time. Therefore, even if the attacker steals the message authentication code used by the target last time, the message is "expired". Code, therefore, the attacker will not be able to attack successfully.

The improved method can effectively solve the problem of the vulnerability of the method shown in FIG. 2 after introducing the freshness parameter. The following is explained in conjunction with specific examples.

For example, the target base station generates a message authentication code according to the freshness parameter, the information of the timer, and the integrity protection key of the source base station, and the freshness parameter is PDCP COUNT as an example. The terminal is currently in an inactive state.

Assuming that the value of the PDCP COUNT indicated by the indication parameter of the connection recovery request message is 5, the target base station generates a message authentication code according to the value of the PDCP COUNT, the information of the timer, and the integrity protection key of the source base station.

If the target base station rejects the connection recovery request of the terminal, the message authentication code is generated. Specifically, the message authentication code is generated according to the value of the PDCP COUNT, the information of the timer, and the integrity protection key of the source base station, where the value of the PDCP COUNT is 5. For ease of understanding, the generated message authentication code is represented as MAC (5, 30 minutes, Krrc-int1), where 5 is the value of PDCP COUNT, 30 minutes is the waiting time indicated by the timer information, and Krrc-int1 is The integrity protection key of the source base station.

Then, the target base station sends a connection recovery reject message and a MAC (5, 30 minutes, Krrc-int1) to the terminal, and the information including the timer is included in the connection recovery reject message, and the indicated duration is 30 minutes, that is, the terminal is instructed to try after 30 minutes. Re-initiate the connection recovery request.

The terminal receives the connection recovery rejection message and the MAC (5, 30 minutes, Krrc-int1), and obtains the information of the timer from the connection recovery rejection message, and then according to the acquired timer information, the integrity protection key of the terminal. The value of the PDCP COUNT is used to generate a message authentication code. Here, the message authentication code generated by the terminal is MAC (5, 30 minutes, Krrc-int2), where 5 is the value of the PDCP COUNT sent by the terminal to the target base station, and 30 minutes is the terminal. The length of time indicated by the information of the timer obtained from the connection recovery rejection message, Krrc-int2 is the integrity protection key of the terminal. In general, Krrc-int1 is the same as Krrc-int2. Therefore, if the MAC (5, 30 minutes, Krrc-int1) generated by the terminal is the same as the MAC (5, 30 minutes, Krrc-int1) transmitted by the target base station, the terminal check message authentication code is correct. Then the terminal sleeps for 30 minutes.

Assume that before the arrival of 30 minutes, the attacker target base station steals the connection recovery reject message and MAC (5, 30 minutes, Krrc-int2), masquerades as the target base station, and sends a connection recovery reject message and MAC to the terminal (5, 30 minutes, Krrc-int2). After receiving the connection recovery reject message and the MAC (5, 30 minutes, Krrc-int2), the terminal first obtains the duration indicated by the information of the timer from the connection recovery rejection message, which is 30 minutes, and then the terminal acquires the current PDCP of the terminal. The value of COUNT, here, since the value of PDCP COUNT has generally changed, for example, has been updated to 12, the message authentication code generated by the terminal is MAC (12, 30 minutes, Krrc-int2). Since the value of PDCP COUNT has changed, the MAC generated by the terminal (12, 30 minutes, Krrc-int2) is different from the MAC (5, 30 minutes, Krrc-int1) sent by the attacker, and the verification fails. Ignore the information for the timer in the connection recovery reject message.

For example, taking the freshness parameter as the rejection number as an example, assume that the value of the number of rejections currently stored by the terminal and the source base station is 2, and the terminal is currently in an inactive state.

The terminal sends a connection recovery request message to the target base station for the first time. The connection recovery request message carries a message authentication code and a recovery identifier. The message authentication code is generated according to the number of rejections and the integrity protection key of the terminal. 2.

If the target base station rejects the connection recovery request of the terminal, the connection recovery rejection message sent to the terminal carries the information of the waiting timer, indicating that the terminal may try to re-initiate the connection recovery request after 30 minutes, and the terminal update rejection number is 3. At the same time, the target base station notifies the source base station to update the number of rejections in the context of the terminal of the source base station to 3.

It is assumed that before the terminal sends the connection recovery request message to the target base station for the second time, the attacker steals the message authentication code and the recovery identifier from the connection recovery request message sent by the terminal to the target base station for the first time, where the message authentication code is generated. The number of rejections used is 2.

Then, the attacker sends a connection recovery request message to the target base station, where the connection recovery request message carries the stolen message authentication code and the recovery identifier, and after receiving the connection recovery request message, the target base station, if it agrees to the attacker's recovery request, then The source base station sends a context request message. Then, the source base station checks the message authentication code sent by the attacker, because the number of rejections used by the attacker to send the message authentication code is 2, and the number of rejections in the context of the terminal of the source base station is 3, so the school The test failed. Thus, the attacker fails to attack.

Therefore, the above solution provided by the present application can effectively solve the problem that the method shown in FIG. 2 is vulnerable.

If the flow shown in Figure 2 is modified in accordance with this method, then the methods shown in Figures 3-6 need to be adjusted accordingly. The following is explained one by one.

For the foregoing process shown in FIG. 3, the connection recovery request message of step 301 may carry an indication parameter for indicating a freshness parameter, and the message authentication code generated in step 306 is generated by combining the freshness parameter. The specific improved method is the same as the foregoing improved method for step 202 and step 204 of FIG. 2, and the foregoing description may be referred to.

Further, the target base station may further send an indication parameter to the source base station, for example, the information of the timer and the indication parameter may be sent in step 303, or the indication parameter may be sent in a separate step. The source base station can then determine the freshness parameter based on the indication parameters. For example, if the freshness parameter is PDCP COUNT, and the indication parameter indicates a part of the low bit of the PDCP COUNT, the source base station may indicate according to a part of the high bit of the last used PDCP COUNT and an indication parameter received from the target base station. Part of the low bit of PDCP COUNT, get PDCP COUNT.

Further, for step 304, the specific method for generating the message authentication code needs to be modified as follows: the source base station generates a message authentication code according to the integrity protection key of the source base station, the freshness parameter, and the information of the timer.

Further, if the freshness parameter is the number of rejections, the source base station may obtain the number of rejections from the context of the terminal. At this time, the connection recovery request message of step 301 and step 303 may not carry the indication parameter for indicating the freshness parameter. Since the target base station rejects the connection recovery request of the terminal, the source base station also needs to update the context of the terminal in the source base station, specifically: the source base station increases the number of rejections by one. For step 307, after verifying that the message authentication code is passed, the terminal needs to update the context of the terminal, specifically: the terminal adds 1 to the number of rejections.

For the process shown in FIG. 4 above, the connection recovery request message of step 401 may carry an indication parameter for indicating a freshness parameter, and the message authentication code generated in step 406 is generated by combining the freshness parameter. The method is specifically improved, which is the same as the foregoing improved method for step 202 and step 204 of FIG. 2, and can be referred to the foregoing description.

Further, the target base station may further send the indication parameter to the source base station, for example, the connection rejection request message and the indication parameter may be sent in step 403, or the indication parameter may be sent in a separate step. The source base station can then determine the freshness parameter based on the indication parameters. The method is the same as above.

Further, for step 404, the specific method for generating the message authentication code needs to be modified as follows: the source base station generates a message authentication code according to the integrity protection key, the freshness parameter, and the connection rejection request message of the source base station.

Further, if the freshness parameter is the number of rejections, the source base station may obtain the number of rejections from the context of the terminal. At this time, the connection recovery request message of step 401 and step 403 may not carry the indication parameter for indicating the freshness parameter. Since the target base station rejects the connection recovery request of the terminal, the source base station also needs to update the context of the terminal in the source base station, specifically: the source base station increases the number of rejections by one. For step 407, after verifying that the message authentication code is passed, the terminal needs to update the context of the terminal, specifically: the terminal adds 1 to the number of rejections.

For the foregoing process shown in FIG. 5, the connection recovery request message of step 501 needs to carry an indication parameter for indicating a freshness parameter, and the message authentication code generated in step 506 is generated by combining the freshness parameter. The method is specifically improved, which is the same as the foregoing improved method for step 202 and step 204 of FIG. 2, and can be referred to the foregoing description.

Further, the target base station further needs to send the indication parameter to the source base station, for example, the request message and the indication parameter may be sent in step 503, or the indication parameter may be sent in a separate step. The source base station can then determine the freshness parameter based on the indication parameters. The method is the same as above.

Further, the source base station also needs to send the determined freshness parameter to the target base station, for example, the key and the freshness parameter may be sent in step 504, or the freshness parameter may be sent in a separate step.

Further, for step 505, the specific method for generating the message authentication code needs to be modified as follows: the target base station generates a message authentication code according to the key, the freshness parameter, and the information of the timer.

Further, if the freshness parameter is the number of rejections, the target base station may obtain the number of rejections from the source base station. At this time, the connection recovery request message of step 501 and step 503 may not carry the indication parameter for indicating the freshness parameter. Since the target base station rejects the connection recovery request of the terminal, the source base station also needs to update the context of the terminal in the source base station, specifically: the source base station increases the number of rejections by one. For step 507, after verifying that the message authentication code is passed, the terminal needs to update the context of the terminal, specifically: the terminal adds 1 to the number of rejections.

For the foregoing process shown in FIG. 6, the connection recovery request message of step 601 needs to carry an indication parameter for indicating a freshness parameter, and the message authentication code generated in step 606 is generated by combining the freshness parameter. The method is specifically improved, which is the same as the foregoing improved method for step 202 and step 204 of FIG. 2, and can be referred to the foregoing description.

Further, the target base station further needs to send the indication parameter to the source base station, for example, the request message and the indication parameter may be sent in step 603, or the indication parameter may be sent in a separate step. The source base station can then determine the freshness parameter based on the indication parameters. The method is the same as above.

Further, the source base station also needs to send the determined freshness parameter to the target base station, for example, the key and the freshness parameter may be sent in step 604, or the freshness parameter may be sent in a separate step.

Further, for step 605, the specific method for generating the message authentication code needs to be modified as follows: the target base station generates a message authentication code according to the key, the freshness parameter, and the connection recovery reject message.

Further, if the freshness parameter is the number of rejections, the target base station may obtain the number of rejections from the local. In this case, the connection recovery request message of step 601 and step 603 may not carry the indication parameter for indicating the freshness parameter. Since the target base station rejects the connection recovery request of the terminal, the source base station needs to update the context of the terminal in the source base station according to the freshness parameter, specifically: the source base station adds 1 to the number of rejections. For the step 607, after verifying that the message authentication code is passed, the terminal also needs to update the context of the terminal, specifically: the terminal adds 1 to the number of rejections.

It should be noted that the connection recovery request message, the connection recovery rejection message, and the like in the foregoing embodiment are only one name, and the name does not limit the message itself. In the 5G network and other networks in the future, the connection recovery request message and the connection recovery rejection message may be other names, which are not specifically limited in the embodiment of the present application. For example, the connection recovery request message may also be replaced with a request message, a recovery request message, a connection request message, etc., and the connection recovery rejection message may be replaced with a rejection message, a recovery rejection message, a connection rejection message, and the like.

The foregoing provides a description of the solution provided by the present application from the perspective of interaction between the various network elements. It can be understood that, in order to implement the above functions, each of the foregoing network elements includes a hardware structure and/or a software module corresponding to each function. Those skilled in the art will readily appreciate that the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

Based on the same inventive concept, as shown in FIG. 7, a schematic diagram of a device, which may be a terminal, a target base station, or a source base station, may be implemented by a terminal, a target base station, or a source base station in any of the above embodiments. The method of execution.

The apparatus 700 includes at least one processor 701, a transmitter 702, a receiver 703, and optionally a memory 704. The processor 701, the transmitter 702, the receiver 703, and the memory 704 are connected by a communication line.

The processor 701 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.

The communication line can include a path for communicating information between the units.

The transmitter 702 and the receiver 703 are configured to communicate with other devices or communication networks. The transmitter and receiver include radio frequency circuits.

The memory 704 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions. The dynamic storage device may also be an electrically erasable programmabler-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, or a disc storage ( Including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be stored by a computer Any other media taken, but not limited to this. The memory 704 may be independent and connected to the processor 701 via a communication line. Memory 704 can also be integrated with the processor. The memory 704 is used to store application code for executing the solution of the present invention, and is controlled by the processor 701 for execution. The processor 701 is configured to execute application code stored in the memory 704.

In a specific implementation, as an embodiment, the processor 701 may include one or more CPUs, such as CPU0 and CPU1 in FIG.

In a particular implementation, as an embodiment, apparatus 700 can include multiple processors, such as processor 701 and processor 708 in FIG. Each of these processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.

It should be understood that, when the device 700 is a terminal, the device 700 may be used to implement the steps performed by the terminal in the method of the embodiment of the present invention. For example, the device 700 may perform step 301, step 307 in FIG. 3, and may also perform Step 401 and step 407 in FIG. 4, step 501 and step 507 in FIG. 5 may also be performed, and step 601 and step 607 in FIG. 6 may also be performed. For related features, reference may be made to the above, and details are not described herein again.

When the device 700 is a target base station, the device 700 can be used to implement the steps performed by the target base station in the method of the embodiment of the present invention. For example, the device 700 can perform step 302, step 303, and step 306 in FIG. Step 502, step 403, step 406 in FIG. 5 may be performed, and step 502, step 503, step 505, and step 506 in FIG. 5 may be performed, and step 602, step 603, step 605 in FIG. 6 may also be performed. Step 606, related features may refer to the above, and details are not described herein again.

When the device 700 is a source base station, the device 700 can be used to implement the steps performed by the source base station in the method of the embodiment of the present invention. For example, the device 700 can perform step 304 and step 305 in FIG. In step 404 and step 405 of FIG. 4, step 504 in FIG. 5 may also be performed, and step 604 in FIG. 6 may also be performed. For related features, reference may be made to the above, and details are not described herein again.

In a specific implementation, the actions of the terminal in FIG. 3-6 may be performed by the processor 701 (and/or the processor 708) in the device 700 calling the application code stored in the memory 704. Any restrictions.

The application may divide the function module into the terminal according to the above method example. For example, each function module may be divided according to each function, or two or more functions may be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the present application is schematic, and is only a logical function division, and may be further divided in actual implementation. For example, in the case of dividing each functional module by using corresponding functions, FIG. 8 shows a schematic diagram of a device, which may be the terminal involved in the above embodiment, and the device 800 includes a processing unit 801 and a receiving unit 802. And transmitting unit 803.

In an implementation of a method of requesting a restore connection:

The sending unit 803 is configured to send a connection recovery request message to the target base station, where the connection recovery request message is used to request to resume the radio resource control RRC connection;

The receiving unit 802 is configured to receive a connection recovery reject message and a message authentication code from the target base station, where the connection recovery reject message is used to indicate that the device is denied to restore the RRC connection, and the connection recovery reject message includes Information of the timer, the message authentication code is generated according to the integrity protection key of the source base station and the information of the timer;

The processing unit 801 is configured to: if the message authentication code is verified to be correct according to the information of the timer and the integrity protection key of the device, initiate a connection recovery request process according to the information of the timer.

In a possible implementation, the message authentication code is generated according to the integrity protection key of the source base station, the information of the timer, and the freshness parameter, and the message used by the message authentication code is generated twice. Sexual parameters are different.

In a possible implementation manner, the connection recovery request message includes an indication parameter, where the indication parameter is used to indicate the freshness parameter.

In a possible implementation manner, the freshness parameter includes a packet data convergence protocol count PDCP COUNT, and the indication parameter includes part or all of the bits of the PDCP COUNT.

In a possible implementation manner, the freshness parameter includes a number of rejections, the number of rejections being used to indicate the number of times the device is rejected when attempting to resume the RRC connection.

It should be understood that the terminal may be used to implement the steps performed by the terminal in the method of the embodiment of the present invention. For related features, reference may be made to the above, and details are not described herein again.

The application may perform the division of the function modules on the target base station according to the foregoing method example. For example, each function module may be divided according to each function, or two or more functions may be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the present application is schematic, and is only a logical function division, and may be further divided in actual implementation. For example, in the case of dividing each functional module by corresponding functions, FIG. 9 shows a schematic diagram of a device, which may be the target base station involved in the above embodiment, and the device 900 includes a receiving unit 902 and a transmitting unit. 903. Optionally, a processing unit 901 is also included.

In an implementation of a method of requesting a restore connection:

The receiving unit 902 is configured to receive a connection recovery request message from the terminal, where the connection recovery request message is used to request to resume the radio resource control RRC connection;

The sending unit 903 is configured to: if the RRC connection is refused to be restored, send a connection recovery reject message and a message authentication code to the terminal, where the connection recovery reject message includes information of a timer, and the connection reject request message is used by And instructing to reject the terminal to resume the RRC connection.

In a possible implementation manner, the sending unit 903 is further configured to send information about the timer to a source base station;

The receiving unit 902 is further configured to receive the message authentication code from the source base station, where the message authentication code is used by the source base station according to the integrity protection key of the source base station and the information of the timer generate.

In a possible implementation manner, the connection recovery request message includes an indication parameter, where the indication parameter is used to indicate a freshness parameter, and the sending unit 903 is further configured to send the indication parameter to the source base station;

The message authentication code is generated by the source base station according to the integrity protection key of the source base station, the freshness parameter, and the information of the timer, and the message used by the message authentication code is generated twice. Sexual parameters are different.

In a possible implementation, the sending unit 903 is further configured to send the connection reject request message to the source base station;

The receiving unit 902 is further configured to receive the message authentication code from the source base station, where the message authentication code is used by the source base station according to the integrity protection key of the source base station and the connection reject request message. generate.

In a possible implementation manner, the connection recovery request message includes an indication parameter, where the indication parameter is used to indicate a freshness parameter, and the sending unit 903 is further configured to send the indication parameter to the source base station;

The message authentication code is generated by the source base station according to the integrity protection key of the source base station, the freshness parameter, and the connection rejection request message, and the message used by the message authentication code is generated twice. Sexual parameters are different.

In a possible implementation manner, the receiving unit 902 is further configured to receive a key from the source base station;

The processing unit 901 is configured to generate the message authentication code according to the key and the information of the timer.

In a possible implementation, the processing unit 901 is specifically configured to generate the message authentication code according to the key, the information of the timer, and the freshness parameter.

The freshness parameters used to generate the message authentication code twice are different.

In a possible implementation, the connection recovery request message includes an indication parameter, where the indication parameter is used to indicate the freshness parameter, and the freshness parameter includes a packet data convergence protocol count PDCP COUNT, the indication parameter Some or all of the bits of the PDCP COUNT are included.

In a possible implementation manner, the freshness parameter includes a number of rejections, and the number of rejections is used to indicate the number of times the terminal is rejected when attempting to resume the RRC connection.

In a possible implementation manner, the receiving unit 902 is further configured to receive a key from the source base station;

The processing unit 901 is configured to generate the message authentication code according to the key and the connection request rejection message.

In a possible implementation, the processing unit 901 is specifically configured to generate the message authentication code according to the key, the connection request rejection message, and the freshness parameter.

The freshness parameters used to generate the message authentication code twice are different.

In a possible implementation, the connection recovery request message includes an indication parameter, where the indication parameter is used to indicate the freshness parameter, and the freshness parameter includes a packet data convergence protocol count PDCP COUNT, the indication parameter Some or all of the bits of the PDCP COUNT are included.

In a possible implementation manner, the freshness parameter includes a number of rejections, and the number of rejections is used to indicate the number of times the terminal is rejected when attempting to resume the RRC connection. It should be understood that the target base station may be used to implement the steps performed by the target base station in the method of the embodiment of the present invention. For related features, reference may be made to the above, and details are not described herein again.

The application may divide the function modules of the source base station according to the foregoing method example. For example, each function module may be divided according to each function, or two or more functions may be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the present application is schematic, and is only a logical function division, and may be further divided in actual implementation. For example, in the case of dividing each functional module by corresponding functions, FIG. 10 shows a schematic diagram of a device, which may be the source base station involved in the above embodiment, and the device 1000 includes a processing unit 1001 and a receiving unit. 1002 and transmitting unit 1003.

In an implementation of a method of requesting a restore connection:

The receiving unit 1002 is configured to receive information about a timer from a target base station;

The processing unit 1001 is configured to generate a message authentication code according to the information of the timer and the integrity protection key of the device;

The sending unit 1003 is configured to send the message authentication code to the target base station.

In a possible implementation, the processing unit 1001 is specifically configured to generate the message authentication code according to the information of the timer, the integrity protection key of the device, and the freshness parameter.

The freshness parameters used to generate the message authentication code twice are different.

In a possible implementation manner, the receiving unit 1002 is further configured to receive an indication parameter from the target base station, where the indication parameter is used to indicate the freshness parameter.

In a possible implementation manner, the freshness parameter includes a packet data convergence protocol count PDCP COUNT, and the indication parameter includes part or all of the bits of the PDCP COUNT.

In a possible implementation manner, the freshness parameter includes a number of rejections, and the number of rejections is used to indicate the number of times the terminal is rejected when attempting to resume the RRC connection.

In another implementation of a method that requests a restore connection:

The receiving unit 1002 is configured to receive a connection reject request message from the target base station, where the connection reject request message includes information of a timer, where the connection reject request message is used to indicate that the terminal is refused to resume the radio resource control RRC connection;

The processing unit 1001 is configured to generate a message authentication code according to the connection reject request message and the integrity protection key of the device;

The sending unit 1003 is configured to send the message authentication code to the target base station.

In a possible implementation, the processing unit 1001 is specifically configured to:

Generating a message authentication code according to the connection rejection request message, the integrity protection key of the device, and the freshness parameter;

The freshness parameters used to generate the message authentication code twice are different.

In a possible implementation manner, the receiving unit 1002 is further configured to receive an indication parameter from the target base station, where the indication parameter is used to indicate the freshness parameter.

In a possible implementation manner, the freshness parameter includes a packet data convergence protocol count PDCP COUNT, and the indication parameter includes part or all of the bits of the PDCP COUNT.

In a possible implementation manner, the freshness parameter includes a number of rejections, and the number of rejections is used to indicate the number of times the terminal is rejected when attempting to resume the RRC connection.

It should be understood that the source base station may be used to implement the steps performed by the source base station in the method of the embodiment of the present invention. For related features, reference may be made to the above, and details are not described herein again.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a Solid State Disk (SSD)) or the like.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a Solid State Disk (SSD)) or the like.

Although the present invention has been described herein in connection with the embodiments of the present invention, it will be understood by those skilled in the <RTIgt; Other variations of the disclosed embodiments are achieved. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill several of the functions recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not mean that the measures are not combined to produce a good effect.

Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, apparatus (device), computer readable storage medium, or computer program product. Thus, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware aspects, which are collectively referred to herein as "module" or "system."

Those skilled in the art can also understand that the various illustrative logical blocks and steps listed in the embodiments of the present application can be implemented by electronic hardware, computer software, or a combination of the two. Whether such functionality is implemented by hardware or software depends on the design requirements of the particular application and the overall system. Those skilled in the art can implement the described functions using various methods for each specific application, but such implementation should not be construed as being beyond the scope of the embodiments of the present application.

While the invention has been described with respect to the specific embodiments and embodiments thereof, various modifications and combinations may be made without departing from the spirit and scope of the invention. Accordingly, the specification and drawings are to be construed as the It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

Claims (38)

1. A method for requesting a connection to restore, characterized in that it comprises:

   The terminal sends a connection recovery request message to the target base station, where the connection recovery request message is used to request to resume the radio resource control RRC connection;

   The terminal receives a connection recovery reject message and a message authentication code from the target base station, where the connection recovery reject message is used to indicate that the terminal is denied to restore the RRC connection, and the connection recovery reject message includes information of a timer. The message authentication code is generated according to an integrity protection key of the source base station and information of the timer;

   If the terminal verifies that the message authentication code is correct according to the information of the timer and the integrity protection key of the terminal, the terminal initiates a connection recovery request procedure according to the information of the timer.
2. The method according to claim 1, wherein the message authentication code is generated according to an integrity protection key of the source base station, the information of the timer, and a freshness parameter, and the message authentication code is generated twice. The freshness parameters used are different.
3. The method of claim 2, wherein the connection recovery request message includes an indication parameter, the indication parameter being used to indicate the freshness parameter.
4. The method of claim 2, wherein the freshness parameter comprises a number of rejections, the number of rejections being used to indicate a number of times the terminal is rejected when attempting to resume the RRC connection.
5. A method for requesting a connection to restore, characterized in that it comprises:

   The source base station receives information of a timer from the target base station;

   The source base station generates a message authentication code according to the information of the timer and the integrity protection key of the source base station;

   The source base station sends the message authentication code to the target base station.
6. The method according to claim 5, wherein the source base station generates a message authentication code according to the information of the timer and the integrity protection key of the source base station, including:

   The source base station generates the message authentication code according to the information of the timer, the integrity protection key of the source base station, and a freshness parameter;

   The freshness parameters used to generate the message authentication code twice are different.
7. The method of claim 6 wherein the method further comprises:

   The source base station receives an indication parameter from the target base station, and the indication parameter is used to indicate the freshness parameter.
8. The method of claim 6, wherein the freshness parameter comprises a number of rejections, the number of rejections being used to indicate the number of times the terminal is rejected when attempting to resume the RRC connection.
9. A method for requesting a connection to restore, characterized in that it comprises:

   The source base station receives a connection reject request message from the target base station, where the connection reject request message includes information of a timer, and the connection reject request message is used to indicate that the terminal is allowed to resume the radio resource control RRC connection;

   The source base station generates a message authentication code according to the connection reject request message and the integrity protection key of the source base station;

   The source base station sends the message authentication code to the target base station.
10. The method according to claim 9, wherein the source base station generates a message authentication code according to the connection reject request message and the integrity protection key of the source base station, including:

    The source base station generates a message authentication code according to the connection reject request message, the integrity protection key of the source base station, and the freshness parameter;

    The freshness parameters used to generate the message authentication code twice are different.
11. A method for requesting a connection to restore, characterized in that it comprises:

    The target base station receives a connection recovery request message from the terminal, where the connection recovery request message is used to request to resume the radio resource control RRC connection;

    If the target base station refuses to restore the RRC connection, sending a connection recovery reject message and a message authentication code to the terminal, the connection recovery reject message includes information of a timer, and the connection reject request message is used to indicate the reject The terminal resumes the RRC connection.
12. The method of claim 11 wherein the method further comprises:

    Sending, by the target base station, information of the timer to a source base station;

    The target base station receives the message authentication code from the source base station, and the message authentication code is generated by the source base station according to the integrity protection key of the source base station and the information of the timer.
13. The method according to claim 12, wherein the connection recovery request message includes an indication parameter, the indication parameter is used to indicate a freshness parameter, and the method further comprises:

    Sending, by the target base station, the indication parameter to the source base station;

    The message authentication code is generated by the source base station according to the integrity protection key of the source base station, the freshness parameter, and the information of the timer, and the message used by the message authentication code is generated twice. Sexual parameters are different.
14. The method of claim 11 wherein the method further comprises:

    Sending, by the target base station, the connection reject request message to the source base station;

    The target base station receives the message authentication code from the source base station, and the message authentication code is generated by the source base station according to the integrity protection key of the source base station and the connection reject request message.
15. The method according to claim 14, wherein the connection recovery request message includes an indication parameter, the indication parameter is used to indicate a freshness parameter, and the method further comprises:

    Sending, by the target base station, the indication parameter to the source base station;

    The message authentication code is generated by the source base station according to the integrity protection key of the source base station, the freshness parameter, and the connection rejection request message, and the message used by the message authentication code is generated twice. Sexual parameters are different.
16. An apparatus, comprising: a transmitting unit, a receiving unit, and a processing unit;

    The sending unit is configured to send a connection recovery request message to the target base station, where the connection recovery request message is used to request to resume the radio resource control RRC connection;

    The receiving unit is configured to receive a connection recovery reject message and a message authentication code from the target base station, where the connection recovery reject message is used to indicate that the device is denied to restore the RRC connection, and the connection recovery reject message includes timing Information of the device, the message authentication code is generated according to the integrity protection key of the source base station and the information of the timer;

    The processing unit is configured to: if the message authentication code is verified to be correct according to the information of the timer and the integrity protection key of the device, initiate a connection recovery request process according to the information of the timer.
17. The apparatus according to claim 16, wherein the message authentication code is generated according to an integrity protection key of the source base station, the information of the timer, and a freshness parameter, and the message authentication code is generated twice. The freshness parameters used are different.
18. The apparatus of claim 17, wherein the connection recovery request message includes an indication parameter, the indication parameter being used to indicate the freshness parameter.
19. The apparatus of claim 17, wherein the freshness parameter comprises a number of rejections, the number of rejections being used to indicate the number of times the device was rejected when attempting to resume the RRC connection.
20. An apparatus, comprising: a receiving unit, a transmitting unit, and a processing unit;

    The receiving unit is configured to receive information about a timer from a target base station;

    The processing unit is configured to generate a message authentication code according to the information of the timer and the integrity protection key of the device;

    The sending unit is configured to send the message authentication code to the target base station.
21. The device according to claim 20, wherein the processing unit is configured to generate the message authentication code according to the information of the timer, the integrity protection key of the device, and a freshness parameter;

    The freshness parameters used to generate the message authentication code twice are different.
22. The apparatus according to claim 21, wherein the receiving unit is further configured to receive an indication parameter from the target base station, where the indication parameter is used to indicate the freshness parameter.
23. The apparatus of claim 21, wherein the freshness parameter comprises a number of rejections, the number of rejections being used to indicate a number of times the terminal is rejected when attempting to resume the RRC connection.
24. An apparatus, comprising: a receiving unit, a transmitting unit, and a processing unit;

    The receiving unit is configured to receive a connection reject request message from a target base station, where the connection reject request message includes information of a timer, where the connection reject request message is used to indicate that the terminal is denied to restore the radio resource control RRC connection;

    The processing unit is configured to generate a message authentication code according to the connection rejection request message and the integrity protection key of the device;

    The sending unit is configured to send the message authentication code to the target base station.
25. The device according to claim 24, wherein the processing unit is configured to generate a message authentication code according to the connection rejection request message, the integrity protection key of the device, and a freshness parameter;

    The freshness parameters used to generate the message authentication code twice are different.
26. A device, comprising: a receiving unit and a transmitting unit;

    The receiving unit is configured to receive a connection recovery request message from the terminal, where the connection recovery request message is used to request to resume the radio resource control RRC connection;

    The sending unit is configured to: if the RRC connection is refused to be restored, send a connection recovery reject message and a message authentication code to the terminal, where the connection recovery reject message includes information of a timer, and the connection reject request message is used for Instructing to reject the terminal to resume the RRC connection.
27. The apparatus according to claim 26, wherein the sending unit is further configured to send information of the timer to a source base station;

    The receiving unit is further configured to receive the message authentication code from the source base station, where the message authentication code is generated by the source base station according to the integrity protection key of the source base station and the information of the timer .
28. The device according to claim 27, wherein the connection recovery request message includes an indication parameter, the indication parameter is used to indicate a freshness parameter, and the sending unit is further configured to send the Indication parameter

    The message authentication code is generated by the source base station according to the integrity protection key of the source base station, the freshness parameter, and the information of the timer, and the message used by the message authentication code is generated twice. Sexual parameters are different.
29. The apparatus according to claim 26, wherein the sending unit is further configured to send the connection reject request message to a source base station;

    The receiving unit is further configured to receive the message authentication code from the source base station, where the message authentication code is generated by the source base station according to the integrity protection key of the source base station and the connection reject request message. .
30. The device according to claim 29, wherein the connection recovery request message includes an indication parameter, the indication parameter is used to indicate a freshness parameter, and the sending unit is further configured to send the Indication parameter

    The message authentication code is generated by the source base station according to the integrity protection key of the source base station, the freshness parameter, and the connection rejection request message, and the message used by the message authentication code is generated twice. Sexual parameters are different.
31. A computer storage medium, characterized in that the computer readable storage medium stores instructions that, when run on a computer, cause the computer to perform the method of any of claims 1-4.
32. A computer storage medium, characterized in that the computer readable storage medium stores instructions that, when run on a computer, cause the computer to perform the method of any one of claims 5-8.
33. A computer storage medium, characterized in that the computer readable storage medium stores instructions that, when run on a computer, cause the computer to perform the method of claim 9 or 10.
34. A computer storage medium, characterized in that the computer readable storage medium stores instructions that, when run on a computer, cause the computer to perform the method of any one of claims 11-15.
35. An apparatus, comprising: a memory and a processor coupled to the memory;

    Program instructions are stored in the memory, and when the processor executes the program instructions, cause the apparatus to perform the method of any of claims 1-4.
36. An apparatus, comprising: a memory and a processor coupled to the memory;

    Program instructions are stored in the memory, and when the processor executes the program instructions, cause the apparatus to perform the method of any of the preceding claims 5-8.
37. An apparatus, comprising: a memory and a processor coupled to the memory;

    Program instructions are stored in the memory, and when the processor executes the program instructions, cause the apparatus to perform the method of claim 9 or 10.
38. An apparatus, comprising: a memory and a processor coupled to the memory;

    Program instructions are stored in the memory, and when the processor executes the program instructions, cause the apparatus to perform the method of any of the preceding claims 11-15.

Images