WO2022252133A1

WO2022252133A1 - Method and apparatus for recovery after security activation failure

Info

Publication number: WO2022252133A1
Application number: PCT/CN2021/097792
Authority: WO
Inventors: 白帆; 刘文卓; 王琪; 林天柱; 杨峰; 王经谊
Original assignee: 华为技术有限公司
Priority date: 2021-06-02
Filing date: 2021-06-02
Publication date: 2022-12-08
Also published as: CN115707358A

Abstract

The present application relates to the technical field of wireless communications, and discloses a method and apparatus for recovery after a security mode activation failure. The method comprises: a terminal device receiving a security mode command from a network, and starting an access stratum security activation process; after a security activation failure, sending a security mode failure message to the network; and under the condition that the security mode failure message is sent to the network and no radio resource control (RRC) connection release message is received, initiating a random access process to the network to establish a new RRC connection. By using the solution, the problem that the terminal device needs to rely on a network notification to release the RRC connection after sending the security mode failure message can be solved, and the random access process can be initiated independently to speed up service recovery.

Description

Recovery method and device after security activation failure

technical field

The present application relates to a wireless communication system, and in particular to a recovery method and device after security activation fails.

Background technique

In today's mobile wireless communication network, the control of radio resources involves the processing of various radio resources, for example, the processing of system messages, connection control, mobility management, measurement and other processing. In addition, the connection control part of the access stratum (AS for short) also includes many sub-processes, among which there is the initial access stratum security activation (Initial AS security activation) process.

For the initial security activation process of the AS, that is, the activation of the security mode includes the following steps: the network sends a security mode command (security mode command, referred to as SMC), and the terminal obtains the relevant security parameters of the AS after receiving the SMC message from the network, and Received messages are verified for integrity protection. Wherein, if the terminal passes the integrity protection verification of the AS, it sends a security mode complete message to the network; if it fails the integrity protection verification of the AS, it sends a security mode failure message to the network. After the configuration of the security mode is completed, the terminal can normally carry out data service information and voice information services. Therefore, the failure of the initial security activation process will directly affect the user's service experience.

In the prior art, failure to activate the security of the terminal AS will cause it to fail to perform data and voice services normally. With the diversified development of wireless communication services and application environments, the network environment will become more challenging. Therefore, it is necessary to study how to accelerate the normal services of terminals for data and voice services and improve The user's communication experience.

Contents of the invention

The embodiments of the present application provide a recovery method and device after security activation failure, which is used to accelerate the recovery and normal progress of data services and voice calls for users in the case of security mode activation failures, thereby ensuring user service quality and communication experience.

In a first aspect, the embodiment of the present application provides a wireless communication method, and the method may be executed by a wireless communication device. The method includes: receiving a security mode command from the network, where the security mode command is used to provide access layer security activation information; sending a security mode failure message to the network, where the security mode failure message is used to indicate that the security mode is activated Failure; after sending a security mode failure message to the network and not receiving a radio resource control (Radio Resource Control, RRC) connection release message from the network, initiate a random access procedure to the network to Establish a new RRC connection.

Based on the above method, the terminal reduces the waiting time for the RRC connection release message. In the prior art, the release of the RRC connection by the terminal depends on the RRC connection release message from the network. In an unstable network scenario, the terminal waiting for the RRC connection release message will cause user services to fail normally. In contrast, adopting the above-mentioned solution is beneficial to reduce the terminal's dependence on the network, accelerate service recovery and normal operation, and is conducive to responding to service needs in a timely manner and improving user service experience.

As a possible implementation, after the terminal sends the security mode failure message to the network within a period of time (for example, the first duration), if the terminal does not receive the RRC connection release message from the network, send the The network initiates a random access procedure.

In a specific implementation, the terminal may start a timer after sending the security mode failure message, and the duration of the timer is the first duration. Furthermore, the value of the first duration is one of multiple configurable values, that is, the first duration can be adjusted. The adjustment method can be based on big data statistics or network conditions, and the range can be controlled between 100 and 3000 milliseconds.

In this technical solution, the terminal avoids unlimited waiting for the RRC connection release message by limiting the time when it does not receive the RRC connection release message, and reduces the dependence on the network, so that the RRC connection with the network can be reestablished as soon as possible.

As another possible implementation, after sending a security mode failure message to the network, the terminal initiates a random Access process. The other downlink messages may refer to RRC messages, and the RRC messages include RRC connection reconfiguration messages.

In this technical solution, by receiving an RRC message from the network that is not considered an RRC connection release message, the terminal regards it as an RRC connection release message with a decoding error, so as to perform RRC connection re-establishment in a timely manner, avoiding problems caused by decoding errors and other reasons. infinite waiting time.

As another possible implementation manner, after sending a security mode failure message to the network, the terminal actively initiates a random access procedure to the network when no RRC connection release message is received from the network.

In this technical solution, the terminal does not need to try to receive the RRC connection release message from the network, and actively initiates a random access process after sending the security mode failure message, which can further reduce the time delay.

As another possible implementation, the terminal first enters the RRC idle state after sending the security mode failure message to the network and does not receive the RRC connection release message from the network, and sends The network sends a random access preamble.

In this technical solution, the terminal enters the RRC idle state in time, and sends a random access preamble to the network when there is a service demand, reducing the power consumption of the terminal maintaining the RRC connection state, and balancing delay and power consumption.

In a second aspect, the embodiment of the present application provides a wireless communication method, and the method may be executed by a wireless communication device. The method includes: receiving a security mode command from the network, where the security mode command is used to provide access layer security activation information; sending a security mode failure message to the network, where the security mode failure message is used to indicate that the security mode is activated failure; and after sending a security mode failure message to the network, directly initiate a random access procedure to the network to establish a new RRC connection.

Based on the above method, after sending a security mode failure message to the network, the terminal can directly initiate a random access procedure without trying to receive an RRC connection release message. Compared with the aforementioned existing technology, since there is no need to wait for the time of the RRC connection release message, the recovery of the business depends on the time when the security mode failure message is sent by itself, so the recovery of the business can be maximized compared with the existing technology. accelerate.

As a possible implementation manner, after sending a security mode failure message to the network, the terminal first enters the RRC idle state, and sends a random access preamble to the network according to service requirements.

In this technical solution, the terminal releases resources in time, enters the RRC idle state, and sends a random access preamble to the network when there is a service demand, that is, starts random access to the network. Power consumption can be reduced by reducing the time that the terminal stays in the RRC connection state in the case of no service.

In a third aspect, an embodiment of the present application provides a wireless communication device, including a processing unit and a transceiver unit, wherein the processing unit is used to control the transceiver unit; the transceiver unit is used to send and receive related functions, including : receiving a security mode command from the network, where the security mode command is used to provide access layer security activation information; sending a security mode failure message to the network, where the security mode failure message is used to indicate security activation failure; and After sending a security mode failure message to the network and when no RRC connection release message is received from the network, initiate a random access procedure to the network to establish a new RRC connection.

Optionally, the transceiving unit includes a receiving unit and a sending unit. In one design, the wireless communication device is a communication chip, the processing unit may be one or more processors or processor cores, and the transceiver unit may be an input-output circuit or interface of the communication chip.

In another design, the transceiving unit may be a transmitter and a receiver, or the transceiving unit may be a transmitter and a receiver.

Optionally, the wireless communication device further includes various modules that can be used to implement any implementation manner of any wireless communication method from the first aspect to the second aspect.

In a fourth aspect, the embodiment of the present application provides a wireless communication device, and the device may be a terminal, and may also be a chip for the terminal. The device has the function of realizing the method of the above first aspect or any possible realization method thereof. This function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a fifth aspect, the embodiment of the present application provides a wireless communication device, including a processor and a memory. Optionally, a transceiver is also included. The memory is used to store computer programs or instructions, and the processor is used to call and run the computer programs or instructions from the memory. When the processor executes the computer programs or instructions in the memory, the wireless communication device executes the above-mentioned first aspect to Any implementation of any wireless communication method in the second aspect.

Optionally, there are one or more processors, and one or more memories.

Optionally, the memory may be integrated with the processor, or the memory may be separated from the processor.

Alternatively, memory can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.

In a sixth aspect, a system is provided, and the system includes the wireless communication apparatus and network equipment described above.

In a seventh aspect, a computer program product is provided, and the computer program product includes: a computer program (also referred to as code, or an instruction), which, when the computer program is executed, causes the computer to execute any of the above first to second aspects. A method in a possible implementation manner, or causing a computer to execute the method in any one of the foregoing first aspect to the second aspect.

In an eighth aspect, a computer-readable storage medium is provided, and the computer-readable medium stores a computer program (also referred to as code, or an instruction) which, when run on a computer, causes the computer to perform the above-mentioned first to second aspects. The method in any possible implementation manner in the aspect, or causing the computer to execute the method in any implementation manner in the first aspect to the second aspect above.

In a ninth aspect, a chip system is provided, and the chip system may include a processor. The processor is coupled with the memory, and may be used to execute any one of the first aspect to the second aspect, and the method in any possible implementation manner of any one of the first aspect to the second aspect. Optionally, the chip system further includes a memory. Memory, used to store computer programs (also called code, or instructions). A processor for calling and running a computer program from a memory, so that the device installed with the system-on-a-chip executes any one of the first to second aspects, and any possible one of any of the first to second aspects method in the implementation.

In a tenth aspect, a wireless communication device is provided, including: an interface circuit and a processing circuit. Interface circuitry may include input circuitry and output circuitry. The processing circuit is used to receive signals through the input circuit and transmit signals through the output circuit, so that any one of the first aspect to the third aspect, and the method in any possible implementation manner of the first aspect to the second aspect are realized.

In a specific implementation process, the wireless communication device may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits. The input signal received by the input circuit may be received and input by, for example but not limited to, the receiver, the output signal of the output circuit may be, for example but not limited to, output to the transmitter and transmitted by the transmitter, and the input circuit and the output The circuit may be the same circuit, which is used as an input circuit and an output circuit respectively at different times. The embodiment of the present application does not limit the specific implementation manners of the processor and various circuits.

In an implementation manner, the wireless communication device may be a wireless communication device, that is, a computer device supporting a wireless communication function. Specifically, the wireless communication device may be a terminal such as a smart phone, or a wireless access network device such as a base station. A system chip can also be called a system on chip (system on chip, SoC), or simply a SoC chip. Communication chips may include baseband processing chips and radio frequency processing chips. Baseband processing chips are also sometimes referred to as modems or baseband chips. RF processing chips are sometimes also referred to as RF transceivers or RF chips. In physical implementation, part or all of the chips in the communication chip can be integrated inside the SoC chip. For example, the baseband processing chip is integrated in the SoC chip, and the radio frequency processing chip is not integrated with the SoC chip. The interface circuit may be a radio frequency processing chip in the wireless communication device, and the processing circuit may be a baseband processing chip in the wireless communication device.

In yet another implementation manner, the wireless communication device may be a part of a wireless communication device, such as an integrated circuit product such as a system chip or a communication chip. The interface circuit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system. A processor may also be embodied as processing circuitry or logic circuitry.

Description of drawings

FIG. 1 is a schematic structural diagram of a wireless communication system provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a control plane wireless protocol architecture provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of an RRC connection state transition process provided by an embodiment of the present application;

FIG. 4 is a schematic flow diagram of establishing an RRC connection provided by an embodiment of the present application;

Figure 5 is an initial security activation process of the access layer provided by the embodiment of the present application. Figure 5(a) shows the process of initial security activation success, and Figure 5(b) shows the process of initial security activation failure;

FIG. 6 is a block diagram of an abnormal active recovery after a security mode activation failure provided by an embodiment of the present application;

FIG. 7 is a schematic flowchart of an abnormal active recovery after a security mode activation failure provided by an embodiment of the present application;

FIG. 8 is a schematic flow diagram of an abnormal active recovery after another security mode activation failure provided by the embodiment of the present application;

FIG. 9 is a schematic flow diagram of an abnormal active recovery after another security mode activation failure provided by the embodiment of the present application;

FIG. 10 is a schematic flow diagram of another abnormal active recovery after the failure to activate the security mode provided by the embodiment of the present application;

FIG. 11 is a schematic flow diagram of an abnormal active recovery after another security mode activation failure provided by the embodiment of the present application;

FIG. 12 is a schematic block diagram of a wireless communication device provided by an embodiment of the present application;

FIG. 13 is a schematic structural diagram of a wireless communication device provided by an embodiment of the present application.

It should be understood that in the above structural diagrams, the size and shape of each block diagram are for reference only, and should not constitute an exclusive interpretation of the embodiment of the present application. The relative positions and containment relationships among the block diagrams shown in the structural schematic diagram are only schematic representations of the structural relationships among the block diagrams, rather than limiting the physical connection methods of the embodiments of the present application.

Detailed ways

The technical solutions provided by the present application will be further described below in conjunction with the accompanying drawings and examples. It should be understood that the system structure and business scenarios provided in the embodiments of the present application are mainly for explaining some possible implementations of the technical solution of the present application, and should not be interpreted as a unique limitation on the technical solution of the present application. Those skilled in the art may know that with the evolution of the system and the emergence of newer business scenarios, the technical solutions provided in this application are still applicable to the same or similar technical problems.

It should be understood that the technical solutions provided by the embodiments of the present application include a method for proactively recovering abnormality after the activation of the security mode fails and related devices. The principles of these technical solutions to solve problems are the same or similar. In the introduction of the following specific embodiments, some repetitions may not be repeated, but it should be considered that these specific embodiments have mutual references and can be combined with each other.

In a wireless communication system, devices can be divided into devices that provide wireless network services and devices that use wireless network services. Devices that provide wireless network services refer to those devices that make up a wireless communication network, which can be referred to as network equipment or network elements for short. Network equipment is usually owned by operators (such as China Mobile and Vodafone) or infrastructure providers (such as tower companies), and these manufacturers are responsible for operation or maintenance. Network equipment can be further divided into radio access network (radio access network, RAN) equipment and core network (core network, CN) equipment. Typical RAN equipment includes a base station (base station, BS).

It should be understood that sometimes the base station may also be called a wireless access point (access point, AP), or a transmission reception point (transmission reception point, TRP). Specifically, the base station can be a general node B (generation Node B, gNB) in a 5G new radio (new radio, NR) system, or an evolved node B (evolutional Node B, eNB) in a 4G long term evolution (long term evolution, LTE) system. ).

Devices using wireless network services are usually located at the edge of the network, and may be referred to as terminals for short. The terminal can establish a connection with the network equipment, and provide users with specific wireless communication services based on the services of the network equipment. It should be understood that, because the relationship between the terminal and the user is closer, it is sometimes called user equipment (user equipment, UE), or a subscriber unit (subscriber unit, SU). In addition, compared with the base station usually placed in a fixed location, the terminal often moves with the user, and is sometimes called a mobile station (mobile station, MS). In addition, some network devices, such as a relay node (relay node, RN) or a wireless router, etc., can sometimes be considered as terminals because they have a UE identity or belong to a user.

Specifically, the terminal can be a mobile phone (mobile phone), a tablet computer (tablet computer), a laptop computer (laptop computer), a wearable device (such as a smart watch, a smart bracelet, a smart helmet, smart glasses), and other Devices with wireless access capabilities, such as smart cars, various Internet of things (IOT) devices, including various smart home devices (such as smart meters and smart home appliances) and smart city devices (such as security or monitoring equipment, Intelligent road traffic facilities), etc.

For the convenience of expression, in this application, a base station and a terminal will be taken as examples to describe the technical solutions of the embodiments of this application in detail.

FIG. 1 is a schematic structural diagram of a wireless communication system provided by an embodiment of the present application. As shown in Fig. 1, a wireless communication system includes a terminal and a base station. According to different transmission directions, the transmission link from the terminal to the base station is marked as uplink (uplink, UL), and the transmission link from the base station to the terminal is marked as downlink (downlink, DL). Similarly, data transmission in the uplink may be abbreviated as uplink data transmission or uplink transmission, and data transmission in the downlink may be abbreviated as downlink data transmission or downlink transmission.

In the wireless communication system, the base station can provide communication coverage for a specific geographical area through an integrated or external antenna device. One or more terminals within the communication coverage of the base station can access the base station. One base station can manage one or more cells. Each cell has an identification (identification), which is also called a cell identity (cell ID). From the perspective of radio resources, a cell is a combination of downlink radio resources and its paired uplink radio resources (not necessary).

It should be understood that the wireless communication system can comply with the wireless communication standard of 3GPP, and can also comply with other wireless communication standards, such as the 802 series (such as 802.11, 802.15, or 802.20) of the Institute of Electrical and Electronics Engineers (Institute of Electrical and Electronics Engineers, IEEE). wireless communication standards. Although only one base station and one terminal are shown in FIG. 1 , the wireless communication system may also include other numbers of terminals and base stations. In addition, the wireless communication system may also include other network equipment, such as core network equipment.

The terminal and the base station should know the predefined configuration of the wireless communication system, including the radio access technology (radio access technology, RAT) supported by the system, and the wireless resources specified by the system, such as radio frequency bands and carriers. The carrier is a frequency range that complies with system regulations. This frequency range can be jointly determined by the center frequency of the carrier (referred to as the carrier frequency) and the bandwidth of the carrier. The predefined configurations of these systems can be used as part of the standard protocol of the wireless communication system, or determined through the interaction between the terminal and the base station. The content of the standard protocol of the wireless communication system may be pre-stored in the memory of the terminal and the base station, and/or embodied as a hardware circuit or software code of the terminal and the base station.

In this wireless communication system, the terminal and the base station support one or more of the same RAT, such as 5G NR, 4G LTE, or the RAT of the future evolution system. Specifically, the terminal and the base station use the same air interface parameters, coding scheme, modulation scheme, etc., and communicate with each other based on radio resources specified by the system. Wherein, the air interface parameter is a parameter used to describe air interface characteristics. In English, air interface parameters are sometimes called numerology. The air interface parameters may include subcarrier spacing (subcarrier spacing, SC), and may also include a cyclic prefix (cyclic prefix, CP). The wireless communication system can support various air interface parameters, and these air interface parameters can be used as a part of the standard protocol.

The transmission between the terminal and the network (including the base station and the core network equipment) can follow the technical specifications defined by relevant standard organizations. FIG. 2 is a schematic diagram of a control plane wireless protocol architecture provided by an embodiment of the present application. The wireless protocol architecture can correspond to the wireless protocol architecture of 3GPP. The wireless protocol stack is divided into two planes: the user plane and the control plane. The user plane (User Plane, UP) protocol stack is the protocol cluster used for user data transmission, and the control plane (Control Plane, CP) protocol stack is the protocol cluster used for system control signaling transmission. Among them, the user plane protocol is mainly responsible for functions related to user data transmission, and the control plane protocol is mainly responsible for functions such as connection establishment, mobility management, and security management.

As shown in Figure 2, the wireless protocol architecture corresponds to the control plane protocol. From the bottom protocol to the high layer protocol, a protocol stack is formed, including: physical (PHY) layer protocol, media access control (media access control, MAC) layer protocol, radio link control (radio link control, RLC) layer protocol, packet data convergence (packet data convergence protocol, PDCP) layer protocol, radio resource control (radio resource control, RRC) layer protocol and non-access layer (non- access stratum, NAS) layer protocol. Taking the terminal as an example, the message on the control plane is first transmitted from the high layer to the bottom layer, and then transmitted to the base station or core network side through the physical channel, and then submitted by the bottom layer to the corresponding high layer, thus completing a communication transmission.

From the perspective of the protocol stack, the communication process between the terminal and the network can be divided into an access stratum (Access Stratum, AS) process and a non-access stratum (Non-access Stratum, NAS) process. Among them, the process of the access layer can be understood as the process that requires the participation of terminal equipment and base stations in the wireless access layer, and the process of the non-access layer refers to the signaling process that only the terminal and the core network participate in the processing. Let the process function as a transport. The latter corresponds to the NAS layer protocol, and the former includes the RRC protocol and other layer protocols below for link establishment. Through the flow of the access layer, a communication path is established between the terminal and the core network, thereby realizing the signaling flow of the non-access layer.

In the signaling process throughout the access layer and the non-access layer, radio resource management is a very important part of the mobile communication network. It is to maximize the utilization of the wireless spectrum under the condition of limited bandwidth and prevent the network Congestion and keep the signaling load as small as possible to provide service quality guarantee for wireless user terminals in the network. The control of radio resources involves the processing of various radio resources, for example, processing of system messages, connection control, mobility management, and measurement.

Among them, in the above-mentioned wireless resource processing process, the signaling process at the access layer includes: paging (Paging) process, radio resource connection establishment (RRC connection establishment), initial security activation (Initial AS security activation) process, radio resource reconfiguration (RRC Reconfiguration) radio resource connection release (RRC Connection Release) process, etc. Its processes at the non-access layer mainly include mobility management in the CS domain, call control in the CS domain, mobility management in the PS domain, and session management in the PS domain.

Taking the next generation (NR) mobile communication network as an example, in the process of wireless resource processing, the network needs to establish an RRC connection with the terminal before communicating control signaling and service data.

FIG. 3 is a schematic diagram of an RRC connection state transition process provided by an embodiment of the present application. As shown in Figure 3, the terminal and the network can enter different RRC connection states, including: idle state (RRC_IDLE) and connected state (RRC_CONNECTED), and the reasons may include mobility changes or service triggers.

Taking the terminal and the base station as an example, the terminal is initially in the RRC_IDLE state. When the scene changes, such as registration or service triggering, etc., the terminal establishes a link with the base station, and changes from the RRC_IDLE state to the RRC_CONNECTED state. FIG. 4 is a schematic flowchart of an RRC connection establishment provided by an embodiment of the present application, wherein UE refers to a terminal device, and NW refers to a network, which are commonly used in subsequent schematic flowcharts. Figure 4 indicates the flow of the terminal from the RRC_IDLE state to the RRC_CONNECTED state:

Step 401, the terminal sends an RRC connection setup request (RRC Connection Setup Request) to the base station, and the RRC connection setup request is used to request to establish an RRC connection with the base station.

Step 402, the terminal receives an RRC connection setup (RRC Connection Setup) message from the base station, and the RRC connection setup message is used to respond to the RRC connection setup request.

Step 403, the terminal sends an RRC Connection Setup Complete (RRC Connection Setup Complete) message to the base station, and the RRC Connection Setup Complete message is used to indicate that the RRC connection setup between the terminal and the base station is completed.

Wherein, when the terminal receives the RRC connection establishment message, its connection state changes from the RRC_IDLE state to the RRC_CONNECTED state. The sending of the RRC connection establishment completion message by the terminal means that the establishment of the RRC connection is completed. Only when the connection is released, the terminal can return to the RRC_IDLE state. The implementation method is that the terminal receives the RRC connection release message from the base station. In the prior art, the base station side starts a timer, and when the communication interaction with the terminal stops exceeding a certain threshold, the base station sends an RRC connection release message.

There are two conditions for the terminal to release the RRC connection and enter the RRC_IDLE state, one of which can be satisfied: 1. The wireless link connection is not normal; 2. The terminal receives the RRC Connection Release (RRC Connection Release) message.

The above-mentioned RRC connection establishment request, RRC connection establishment message, RRC connection establishment completion message and RRC connection release message all belong to the control signaling of the RRC layer, which are transmitted using a signaling radio bearer (SRB). Various SRBs are defined in wireless communication, mainly including SRB0, SRB1 and SRB2.

SRB0 is a radio bearer established by default, without integrity protection and encryption processing, such as the above-mentioned RRC connection establishment request and RRC connection establishment message.

SRB1 is used to send RRC signaling messages, which are used to indicate the status and changes of the RRC connection, such as air interface node configuration, link switching, and so on. The signaling carried by it includes the above RRC connection establishment complete message and RRC connection release message.

SRB2 is used to send RRC messages including recorded measurement information and NAS layer messages, which can offload the signaling load of SRB1. In addition, the RRC layer also transmits user plane data downwards, which is in charge of the data radio bearer (DRB). Among them, generally speaking, SRB1, SRB2 and DRB need integrity protection and encryption protection.

In order to achieve integrity protection and encryption protection, the terminal needs to perform security mode activation with the base station, that is, activate AS initial security. The security function of the AS layer refers to the integrity protection and encryption protection of the RRC signaling of the control plane and the encryption protection of the data of the user plane.

For a terminal in the RRC_CONNECTED state, the initial security activation process of the AS includes: initial security activation success process and initial security activation failure process. FIG. 5 shows an AS initial security activation process provided by the embodiment of the present application. FIG. 5(a) shows a successful initial security activation process, and FIG. 5(b) shows a failed initial security activation process.

It can be seen from the figure that the terminal first receives a Security Mode Command (SMC) message from the network. The SMC message is carried by SRB1 and carries relevant security parameters of the AS for activation of the security mode.

The relevant security parameters of the AS include a key group, an integrity protection algorithm, and an encryption protection algorithm. Among them, the key group includes the root key, integrity protection and encryption protection algorithm key, the latter is derived from the root key K _asme . The root key _Kasme is managed and generated by the mobility management entity. When the root key changes, the AS layer security algorithm key derived from it will also change accordingly. It should be noted that this change is made synchronously between the terminal and the network, so as to ensure the normal operation of the integrity protection mechanism and the confidentiality protection mechanism.

The algorithm keys for AS layer integrity protection and encryption protection are obtained based on K _asme and the uplink NAS count value (that is, the non-access layer uplink message count sequence value) (NAS UPLINK COUNT), the two calculate the access layer root key key, and then calculate the security algorithm key of the AS layer from the root key of the access layer.

When the terminal accesses the network, the network is configured by the MME to select the corresponding integrity algorithm, encryption and decryption algorithm, and _Kasme , and then the SMC informs the terminal of the security algorithm, which includes the integrity algorithm and the encryption algorithm. At the same time, the terminal generates AS layer security keys based on K _asme , the above security algorithm and NAS UPLINK COUNT, including control plane integrity protection keys and encryption keys, and user plane encryption and decryption keys. Afterwards, the terminal will verify the integrity of the SMC message based on the integrity protection key and algorithm, and update the security parameters if the verification passes. It can be seen that if the security parameters of the terminal are updated, it is considered that the activation of the security mode is successful, otherwise, the activation of the security mode fails.

If the security mode of the terminal is successfully activated, it will send a Security Mode Complete (Security Mode Complete) message to the network to confirm the successful activation of AS security, see Figure 5(a). The terminal configures the updated key group, integrity protection algorithm and encryption algorithm.

If the activation of the security mode of the terminal fails, a Security Mode Failure (Security Mode Failure) message will be sent to the network to indicate that the activation of the AS security fails, as shown in Figure 5(b). The failure scenarios of the terminal security mode activation mainly include: the uplink NAS count value used by the network and the terminal to deduce the key group is inconsistent, etc.

The failure to activate the AS security will cause the terminal and the network to fail to establish SRB2 and DRB, which is an exception after the activation of the security mode fails. Wherein, since the DRB is used to carry data service information and voice information, a failure to configure the DRB makes the user's data service and voice call unable to proceed normally. It can be seen from this that after the terminal fails to activate the security mode, it will enter an abnormal state where user services cannot be normally performed, further affecting the user's service experience.

In the prior art, the DRB configuration process is fixed on the premise that the RRC connection is completed and the security mode is successfully activated. According to the 3GPP 38.331 technical specification, the terminal needs to end the SMC process after the security mode activation fails. After the SMC process ends, the terminal remains in the RRC_CONNECTED state, and does not have the conditions to initiate an RRC connection establishment request to the base station; and only when certain conditions are met, such as an abnormal wireless link, can the terminal initiate an RRC connection establishment request to the base station. Therefore, the terminal cannot automatically restart the activation of the security mode by re-establishing the RRC connection, resulting in the failure of DRB configuration and the failure of user services.

In the prior art, the terminal can change its RRC connection state to the RRC_IDLE state by receiving the RRC connection release message sent by the base station. When the terminal is in the RRC_IDLE state, it can actively send an RRC connection establishment request to the network through random access again through subsequent service requirements, such as data services or voice calls. After the terminal completes the establishment of the RRC connection with the network, it can receive the SMC message from the network again, thereby re-starting the initial security activation of the AS. When uncontrollable situations such as network congestion or data packet loss occur, the RRC connection release message cannot reach the terminal in time, which will cause service interruption and uncontrollability. It can be known from the above that in the prior art, reactivating the security mode requires the terminal to wait passively for the RRC connection release message sent by the network, so as to further establish the DRB and restore the normal operation of user services.

In order to solve the above problems, the general idea of the embodiment of the present application is as follows: enable the terminal to initiate a random access process to the network without receiving the RRC connection release message, and respond to existing or new service requirements in a timely manner. Therefore, the normal progress of user services is accelerated, and the services include but are not limited to data communication, voice calls, registration, etc. actively initiated by the terminal.

As shown in FIG. 6 , it is a flow chart of an abnormal active recovery after a security mode activation failure provided by the embodiment of the present application. In this process, after the first AS security activation fails, the terminal re-connects to the network and establishes a communication link to start the second AS security activation. This flowchart includes the following steps:

Step 601, the terminal receives a security mode command from the network, and the security mode command is used to provide access layer security activation information.

Step 602, the terminal sends a security mode failure message to the network, where the security mode failure message is used to indicate that the activation of the security mode fails.

Step 603, when the terminal does not receive the RRC connection release message from the network, it initiates a random access procedure to the network to establish a new RRC connection.

Wherein, after the terminal completes the establishment of the RRC connection with the network, as shown in step 601, it receives a security mode command, and the AS security parameter carried by the security mode command is used to indicate security activation; when the security mode activation fails, as in step 602 As shown in , the terminal sends a security mode failure message to the network, which is used to indicate that the activation of the security mode failed this time. In this case, the network should normally issue an RRC connection release message to instruct the terminal to release the current RRC connection resources and enter the RRC_IDLE state. However, due to various reasons such as network failure, the terminal delays or fails to receive the RRC connection release message.

In order to reduce the terminal's dependence on the RRC connection release message issued by the network and improve the robustness of communication, the embodiment of the present application provides that the terminal can initiate a random access procedure even if it does not receive the RRC connection release message. The technical solution is as described in step 603. Wherein, the situation that the terminal does not receive the RRC connection release message from the network after sending the security mode failure message to the network may include the following situations:

1. After sending a security mode failure message to the network, the terminal actively initiates a random access procedure to the network. That is, after the terminal sends the security mode failure message, it can independently initiate a random access procedure to establish a new RRC connection without trying to receive the RRC connection release message delivered by the network. In this case, since the terminal does not need to wait for the receiving network to deliver the RRC connection release message, it does not depend on the network, and this solution can enable it to re-establish the RRC connection and perform security activation more quickly.

2. After the terminal sends the security mode failure message to the network, the terminal waits for a period of time, such as the first period of time, and tries to receive the RRC connection release message within this period of time. If the terminal receives the expected RRC connection release message within the first period of time, the terminal can normally enter the RRC idle state according to the existing standard protocol, and then re-establish the RRC connection. If the terminal does not receive the expected RRC connection release message within the first period of time, the terminal can independently initiate a random access procedure to establish a new RRC connection. In this case, by introducing a period of time (the first duration) of waiting and the terminal independently initiates a random access process, it can be compatible with existing standard protocols, and can also be used as a product implementation solution. When the existing standard protocol cannot solve the problem, By independently initiating the random access process by the terminal, the delay in re-establishing network connection and performing security activation is reduced.

3. After the terminal sends the security mode failure message to the network, the terminal tries to receive the RRC connection release message. If the downlink message received subsequently by the terminal is an RRC connection release message, the terminal can normally enter the RRC idle state according to the existing standard protocol, and then re-establish the RRC connection. If the downlink message (for example, the first RRC message) received by the terminal subsequently is not an RRC connection release message, then the terminal can autonomously initiate a random access procedure to establish a new RRC connection. In this case, by identifying other downlink messages other than the RRC connection release message as a trigger condition, it can be compatible with the existing standard protocol, and can also be used as another product implementation solution. When the existing standard protocol cannot solve the problem, through The terminal independently initiates a random access process to reduce the delay in re-establishing network connection and security activation.

It should be understood that the above three situations are only examples of some possible situations of the embodiment of the present application, and do not limit the applicable situations of the embodiment of the present application. In addition, the three situations mentioned above may also be combined with each other. For example, the latter two cases can be considered to be combined, that is, if other RRC messages other than the RRC connection release message are received within the first period of time, the terminal can initiate a random access procedure autonomously.

On the basis of the embodiment shown in FIG. 6 , the following will introduce the embodiment of the present application in combination with a specific message interaction process. As shown in FIG. 7 , it is a schematic flowchart of an abnormal active recovery after a security mode activation failure provided by the embodiment of the present application. Wherein, the message interaction surrounded by the dotted line box belongs to the random access process in step 703 . May include the following steps:

Step 701, the terminal receives a security mode command from the network.

Step 702, the terminal sends a security mode failure message to the network.

Step 703: Initiate a random access procedure to the network after the security mode failure message is sent to the network and the RRC connection release message from the network is not received.

Step 704, the terminal receives an RRC connection establishment message from the network.

Step 705, the terminal sends an RRC connection establishment complete message to the network.

Step 706, the terminal receives a new security mode command from the network.

For the above steps 701, 702 and 703, reference may be made to steps 601, 602 and 603, which will not be repeated here.

In addition, in step 703, if the above-mentioned RRC connection release message is not received, the terminal will initiate a random access procedure to re-connect to the network. The initiation of the random access process is as shown in the figure, which mainly includes four message interactions: the terminal sends a random access preamble message, receives a random access preamble response message, sends an uplink message (here the uplink message is an RRC connection establishment request), receives Contention resolution message. Through the random access procedure, the terminal can synchronize with the network and obtain uplink resources. Here, the terminal starts the random access procedure to send an RRC connection establishment request to the network, thereby establishing a new RRC connection.

As described in the previous embodiment, when the RRC connection release message is not received, according to the timing when the terminal sends the random access preamble message, the start of the random access process by the terminal can also be divided into two categories:

1. The terminal immediately sends a random access preamble message. After the aforementioned situations where the RRC connection release message is not received, the terminal immediately starts the random access process, and immediately sends a random access preamble message to the network to obtain uplink resources and request the network to establish an RRC connection. In this case, the recovery speed of the RRC connection between the terminal and the network can be maximized, thereby optimizing user service experience.

2. The terminal sends a random access preamble message non-immediately. One of its implementation methods can refer to Figure 8, and the specific steps are as follows:

Step 802, the terminal sends a security mode failure message to the network.

Step 803 includes the following steps:

Step 8031, the terminal enters the RRC_IDLE state.

Step 8032, the terminal initiates a random access procedure to the network according to service requirements, the random access procedure includes sending a random access preamble message, and the random access procedure is used to establish a new RRC connection.

Wherein, in step 8031, the terminal actively releases the current RRC connection and first enters the RRC_IDLE state after the above-mentioned multiple situations of not receiving the RRC connection release message. If the terminal receives the RRC connection release message in the RRC_IDLE state, the message cannot be delivered to the RRC layer in the idle state, the terminal discards the message and does not perform its corresponding operation. After the terminal is in the RRC_IDLE state, it can respond to new service requirements. When there is a service requirement, such as a voice call or data service, the terminal starts a random access process to establish a new RRC connection. If during this process, that is, during the random access process initiated by the terminal and before a new RRC connection is established, it receives an RRC connection release message, discards the message, and does not perform the corresponding operation.

In this case, by first entering the RRC idle state and sending the random access preamble message non-immediately, the terminal can slow down the speed of re-connecting to the network when there is no business demand, and can effectively reduce the power consumption in the scene, and Respond in a timely manner to the generated business needs and reduce the delay in restoring network connections.

After the terminal establishes uplink synchronization, the network receives the RRC connection establishment request from it, reconfigures the relevant parameters of the RRC connection, and sends it to the terminal through the RRC connection establishment message, as shown in step 704 .

In step 705, after receiving the RRC connection establishment message, the terminal applies the configuration carried in it, and sends an RRC connection establishment complete message to the network to indicate that the RRC connection establishment is successful. So far, the new RRC connection between the terminal and the network, and the SRB1 carrying the signaling communication are all established.

According to the protocol, the network sends the SMC message again, as in step 706, to instruct the terminal to perform a new security mode activation to activate AS security and establish communication bearers between SRB2 and DRB.

So far, when the previous security activation failed and the RRC connection release message was not received, the terminal proactively sends a random access preamble and establishes an RRC connection with the network again to promote a new security activation and accelerate the normal operation of services.

Considering that steps 701, 704, 705 and 706 are repetitive for subsequent embodiments, they will not be repeated in other embodiments.

In addition, it should be understood that the above two situations are only examples of some possible situations of the embodiments of the present application, and do not limit the applicable situations of the embodiments of the present application. In addition, the above two cases can be combined with the aforementioned "the case that the terminal does not receive the RRC connection release message from the network after sending the security mode failure message to the network" to expand the implementation.

As shown in FIG. 9 , it is a schematic flowchart of an abnormal active recovery after a security mode activation failure provided by the embodiment of the present application. This flow diagram corresponds to the situation that the terminal does not receive the RRC connection release message from the network within the first period of time after sending the security mode failure message. The specific realization of the first period of time can be achieved through the timing module, such as setting a timer. The process therefore consists of the following steps:

Step 902, the terminal sends a security mode failure message to the network.

Step 903 includes the following steps:

Step 9031, the terminal starts a timer, and the duration of the timer is the first duration.

Step 9032, when the timer expires, the terminal initiates random access to the network, and the random access is used to request uplink resources, thereby sending an RRC connection establishment request.

Wherein, after the terminal finishes sending the security mode failure message, it starts a timer as shown in step 9031, and the duration of the timer is the first duration. The timer can be counted forward or counted down. The terminal detects whether an RRC connection release message from the network is received within the first duration.

If received, it will be executed according to the subsequent procedure of the RRC connection release message in the prior art.

If the terminal does not receive it, it stops waiting for the RRC connection release message. The terminal terminates the timer, and initiates random access to the network.

The value of the first duration can be set as a fixed value, and the value can also be adjusted. The adjustment method includes dynamic adjustment or selecting one of multiple configurable values. The minimum unit of adjustment can be the International System of Units, For example, 1ms, etc., or TTI (transmission time interval, sending time interval) in the communication protocol, is used to describe that the RRC connection release message has not been received within several TTIs. For example, the value range of the first duration can be controlled between 100ms and 3000ms. If you pay attention to the power consumption of the mobile terminal, you can reduce the value of the first duration, such as 100ms; when faced with extremely bad network conditions 1. That is, the receiving of the RRC connection release message is slow, and the signaling interaction with the network should be considered to be reduced, and the value of the first duration can be increased, for example, 3000ms. In addition, the basis for adjusting its value may also include: according to the number of RRC connection establishment failures perceived by the terminal, service demand statistics or big data statistics.

If the terminal receives the RRC connection release message after the first duration, and no new RRC connection is currently established, the RRC connection release message is discarded, and the random access procedure is continued, and the random access procedure is used to establish the New RRC connection.

According to the above solution, when the security activation fails, the terminal can recover from the failure according to the duration of not receiving the RRC connection release message, that is, its own timer, start the random access process, and promote a new The RRC connection is established and the security mode is activated, so that the business can be carried out normally.

As shown in FIG. 10 , it is a schematic flowchart of an abnormal active recovery after another security mode activation failure provided by the embodiment of the present application. This flowchart corresponds to the situation that the terminal receives a downlink message other than an RRC connection release message after sending the security mode failure message. The terminal may receive other messages from the network without receiving the RRC connection release message. Wherein, because the terminal fails to configure AS security, the terminal cannot decode signaling messages carried by SRBs other than SRB0 and data messages carried by DRBs. Taking the RRC message as an example, the RRC message received by the terminal mainly includes signaling messages carried by the SRB (such as RRC connection reconfiguration messages), and signaling messages that are not protected in transparent mode (such as system information blocks). The process includes the following steps:

Step 1002, the terminal sends a security mode failure message to the network.

Step 1003 includes the following steps:

Step 10031: After sending the security mode failure message to the network, receive other RRC messages from the network except the RRC connection release message.

Step 10032: Initiate a random access procedure to the network, and the random access procedure is used to request re-establishment of the RRC connection.

Wherein, in step 10031, after the network receives the safety mode failure message, it should issue an RRC connection release message. The aforementioned situation of "the received downlink message is not an RRC connection release message" means that the RRC message received by the terminal is not considered as an RRC connection release message, which can be regarded as including two situations:

1. The received RRC message is an RRC connection release message, but it may happen that the above message fails to be decoded due to reasons such as network transmission and internal processing. That is, the terminal cannot recognize it as an RRC connection release message.

2. The received RRC message is other RRC messages other than the RRC connection release message. The RRC messages delivered by the network are messages carried by the SRB and not related to service content, including, for example, RRC connection reconfiguration messages, NAS direct transfer messages, and the like.

From the above two situations, it can be seen that for the terminal, after sending the safety mode failure message, it can mark it as an RRC connection with decoding error if it receives any other RRC message from the network that is not an RRC connection release message. Release the message and delete the original RRC connection configuration. During this process, the terminal does not perform any operation indicated by the received RRC message. Then initiate a random access process to the network and apply for the establishment of a new RRC connection, so as to perform a new security activation after the RRC connection is established. After the security mode is successfully activated, a DRB can be established to restore the normal operation of user services.

In the above embodiment, when the security activation fails, the terminal regards all RRC messages from the network that are not RRC connection release messages as RRC connection release messages with decoding errors for subsequent processing, not limited to RRC connection release messages. Delete the RRC connection configuration, thereby reducing the dependence on the network, and speeding up the establishment of the RRC connection and the normal recovery of services.

As shown in FIG. 11 , it is a schematic flowchart of an abnormal active recovery after another security mode activation failure provided by the embodiment of the present application. This flow diagram is for the case where the terminal does not need to try to receive the RRC connection release message sent by the network after sending the security mode failure message. It mainly includes the following steps:

Step 1102, the terminal sends a security mode failure message to the network.

Step 1103: After sending the security mode failure message to the network, the terminal directly initiates a random access procedure to the network, and the random access procedure is used to request re-establishment of the RRC connection.

After sending the security mode failure message to the network, the terminal may directly initiate a random access procedure to the network without waiting for a response from the network, that is, without trying to receive an RRC connection release message from the network. It is worth noting that the need not to try to receive here does not refer to physically closing the ability of the terminal to receive downlink messages, or ignoring all the messages received by the terminal, but to make the subsequent execution of "initiating a random access procedure to the network" rely on The completion of the aforementioned "sending the security mode failure message to the network" is not the reception of the RRC connection release message. That is, the terminal relies on itself, not the release of the network. Wherein, the terminal directly initiates the random access procedure to the network can be divided into the following two situations:

1. After sending the security mode failure message to the network, the terminal immediately initiates a random access procedure to the network. Since the security mode failure message sent in step 1102 indicates that the previous communication connection between the terminal and the network failed to be established, this also means that the previous service that requires the establishment of an RRC connection has not been satisfied. In order to meet the previous service requirement, the terminal can start the random access process immediately after sending the security mode failure message, so as to shorten the time of abnormal service. Common application scenarios such as: during a call or data service, when the terminal fails to activate the security mode, after sending the security mode failure message, it immediately sends a random access preamble message directly to the network and deletes the original RRC connection configuration, so that The RRC connection with the network and the recovery speed of services are maximized to optimize user experience.

2. After sending the security mode failure message to the network, the terminal does not immediately initiate a random access process to the network. The terminal ignores the previous service requirements. If the terminal fails to activate the security mode during the handover process, and it has no ongoing voice or data services, the terminal can release the RRC connection first after sending the security mode failure message, and switch its own RRC The connected state is changed to the RRC idle state, and when there is a business demand later, such as calling or data exchange, apply for access to the network and restore the RRC connection. In this case, the terminal performs a random access process by actively entering the RRC_IDLE state and responding to service requirements. On the premise of not relying on the RRC release message of the network, the terminal performs network access according to the service requirements to speed up the normal operation of services. In addition, by actively entering the RRC_IDLE state in time, the terminal can also effectively reduce power consumption in scenarios.

After receiving the security mode failure message, the network will send the RRC connection release message without waiting for the terminal to reply and confirm, and directly delete the existing RRC connection configuration on the network, that is, the retransmission of the RRC connection release message will not be arranged. Therefore, after receiving the security mode failure message, the network will execute the corresponding random access procedure after receiving the random access preamble message in a normal sequence, so as to establish an RRC connection with the terminal.

If the terminal receives the RRC connection release message before establishing a new RRC connection, since the RRC connection configuration has been deleted, the RRC connection release message cannot be delivered to the RRC layer, so the message is discarded and the random access process is continued. The random access procedure is used to establish the new RRC connection.

It can be seen from the above that the terminal directly initiates the random access process to the network after sending the security mode failure message, and does not try to receive the message sent by the network, and the operation of starting random access depends on the operation of sending the security mode failure message or Based on the triggering of business needs, the dependence on the network is reduced, so as to realize the active recovery from the failure of security activation, accelerate the RRC connection reconstruction, and reduce the time for abnormal business.

A wireless communication device provided by an embodiment of the present application is introduced below.

Referring to FIG. 12 , it is a schematic block diagram of a wireless communication device provided by an embodiment of the present application. The communication device 1200 includes a processing unit 1210 and a transceiver unit 1220 , both of which are connected by wires. The wireless communication device is used to implement each step corresponding to the terminal in each of the above embodiments:

The processing unit 1210 is configured to control the transceiver unit 1220 to communicate with the network; and is configured to control the transceiver unit to start a random access procedure when sensing service requirements, so as to establish an RRC connection with the network.

The transceiver unit 1220 is configured to receive a security mode command from the network, the security mode command is used to provide access layer security activation information; send a security mode failure message; start a random access process.

In a possible implementation method, the transceiver unit 1220 is further configured to send a random message to the network if no RRC connection release message is received from the network within the first period of time after sending the security mode failure message. Access process.

In a possible implementation method, the processing unit 1210 further includes a timer, and is configured to start the timer after sending the security mode failure message, and the duration of the timer is the first duration.

In a possible implementation method, the transceiver unit 1220 is further configured to, after sending the security mode failure message, receive an RRC message from the network other than the RRC connection release message from the network, send the message to the network Initiate a random access procedure.

In a possible implementation method, the other RRC messages include RRC connection reconfiguration messages.

In a possible implementation method, the transceiver unit 1220 is further configured to actively initiate a random access procedure to the network after sending the security mode failure message.

In a possible implementation method, the processing unit 1210 is also used to actively release the occupied RRC resources, and control the communication device 1200 to enter the RRC idle state; In the case of releasing the message, after the communication device 1200 enters the RRC idle state, it sends a random access preamble message when there is a service demand.

In the above implementation manners, the transceiver unit 1220 may also be divided into a receiving unit and a sending unit, each of which has the function of receiving and sending, which is not limited here.

Optionally, the above-mentioned communication device may also include a storage unit, which is used to store data or instructions (also referred to as codes or programs), and each of the above-mentioned units may interact or be coupled with the storage unit to implement corresponding methods or functions . The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.

In the embodiment of the present application, the division of units in the communication device is only a division of logical functions, which may be fully or partially integrated into one physical entity or physically separated during actual implementation. In addition, the units in the communication device can be implemented in the form of software calling through the processing elements; they can also be implemented in the form of hardware; some units can also be implemented in the form of software calling through the processing elements, and some units can be implemented in the form of hardware. For example, each unit can be an independently established processing element, or can be integrated into a certain chip of the communication device. In addition, it can also be stored in the memory in the form of a program, which is called and executed by a certain processing element of the communication device. function of the unit. In addition, all or part of these units can be integrated together, or implemented independently. The processing element described here may also be referred to as a processor, and may be an integrated circuit with a signal processing capability. In the process of implementation, each step of the above method or each unit above may be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software called by the processing element.

In one example, the units in any of the above communication devices may be one or more integrated circuits configured to implement the above method, for example: one or more specific integrated circuits (application specific integrated circuit, ASIC), or, one or multiple microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (field programmable gate array, FPGA), or a combination of at least two of these integrated circuit forms. For another example, when the units in the communication device can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (central processing unit, CPU) or other processors that can call programs. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

Referring to FIG. 13 , it is a schematic structural diagram of a wireless communication device provided in an embodiment of the present application. The wireless communication device may be a wireless communication device or a network device, or may be a chip or a circuit, such as a chip or a A circuit, such as a chip or a circuit that may be set in a network device, is used to implement the methods in the above method embodiments. As shown in FIG. 13 , the communication device 1300 includes: a processor 1310 and a transceiver 1330 . Optionally, the communication device 1300 also includes a memory 1320 , which is indicated by a dotted line box in the figure and is optional. The transceiver 1330 is used to communicate with other devices. Wherein, the processor 1310, the memory 1320, and the transceiver 1330 implement connection and data communication through a bus.

It should be understood that the above processor 1310 may be a chip. For example, the processor 1310 may be a field programmable gate array (field programmable gate array, FPGA), may be an application specific integrated circuit (ASIC), may also be a system chip (system on chip, SoC), or It can be a central processing unit (central processor unit, CPU), or a network processor (network processor, NP), or a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (micro controller) unit, MCU), it can also be a programmable controller (programmable logic device, PLD) or other integrated chips.

In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1310 or instructions in the form of software. The steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor 1310 . The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register. The storage medium is located in the memory 1320, and the processor 1310 reads the information in the memory 1320, and completes the steps of the above method in combination with its hardware.

Specifically, the function of the processing unit 1210 in FIG. 12 and its implementation process may be implemented by the processor 1310 in the communication device 1300 shown in FIG. 13 calling computer-executable instructions stored in the memory 1320 . Alternatively, the function/implementation process of the transceiver unit 1220 in FIG. 12 may be implemented by the transceiver 1330 in the communication device 1300 shown in FIG. 13 .

It should be noted that the processor 1310 in the embodiment of the present application may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above-mentioned method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components . Various methods, steps, and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.

In the embodiment of the present application, the memory 1320 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, many forms of RAM are available such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

In the case where the communication device 1300 corresponds to the wireless communication device in the above method, the communication device may include a processor 1310 , a transceiver 1330 and a memory 1320 . The memory 1320 is used to store instructions, and the processor 1310 is used to execute the instructions stored in the memory 1320, which can be implemented by the wireless communication device in any one or more of the corresponding methods shown in FIGS. 6 to 10 above. A step of.

Those of ordinary skill in the art can understand that the first, second, and other numbers involved in the embodiments of the present application are only for convenience of description, and are not used to limit the scope of the embodiments of the present application, and also indicate the sequence. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B may indicate: A exists alone, A and B exist simultaneously, and B exists independently. The character "/" generally indicates that the contextual objects are an "or" relationship. "At least one" means one or more. At least two means two or more. "At least one", "any one" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural item(s). For example, at least one item (one, species) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or Multiple. "Multiple" means two or more than two, and other quantifiers are similar.

It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

The technical solutions provided by the embodiments of the present application may be fully or partially implemented by software, hardware, firmware or any combination thereof. When implemented using 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 the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a terminal device, a network device, an artificial intelligence device or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device including a server, a data center, and the like integrated with one or more available media. The available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (solid state disk, SSD)), etc.

In the embodiments of the present application, the various embodiments may refer to each other, for example, the methods and/or terms between the method embodiments may refer to each other, for example, the functions and/or terms between the device embodiments may refer to each other, such as the device Functions and/or terms between the embodiments and the method embodiments may refer to each other.

The above is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Anyone skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention. All should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims

A wireless communication method, characterized in that, comprising:

receiving a security mode command from the network, where the security mode command is used to provide access layer security activation information;

sending a security mode failure message to the network, the security mode failure message being used to indicate security activation failure; and

Initiating a random access procedure to the network to establish a new RRC connection after sending a security mode failure message to the network and not receiving a radio resource control RRC connection release message from the network.
The method according to claim 1, characterized in that:

Initiating a random access procedure to the network after sending a security mode failure message to the network and not receiving an RRC connection release message from the network, including:

Initiate a random access procedure to the network if no RRC connection release message is received from the network within the first period of time after the security mode failure message is sent to the network.
The method according to claim 2, further comprising:

A timer is started after the security mode failure message is sent, and the duration of the timer is the first duration.
The method according to claim 3, characterized in that:

The value of the first duration is one of multiple configurable values.
The method according to claim 1, characterized in that:

Initiating a random access procedure to the network after sending a security mode failure message to the network and not receiving an RRC connection release message from the network, including:

After sending the security mode failure message to the network, in the case of receiving other RRC messages from the network than the RRC connection release message, initiate a random access procedure to the network.
The method according to claim 5, characterized in that:

The other RRC messages include RRC connection reconfiguration messages.
The method according to claim 1, characterized in that:

Initiating a random access procedure to the network after sending a security mode failure message to the network and not receiving an RRC connection release message from the network, including:

After sending the security mode failure message to the network, actively initiate a random access procedure to the network.
The method according to any one of claims 1 to 7, characterized in that:

Initiating a random access procedure to the network after sending a security mode failure message to the network and not receiving an RRC connection release message from the network, including:

After sending the security mode failure message to the network and not receiving the RRC connection release message from the network, first enter the RRC idle state, and send a random access preamble to the network according to service requirements.
A wireless communication device, characterized in that it includes:

processing unit and transceiver unit;

Wherein, the processing unit is used to control the transceiver unit, and the transceiver unit is used to:

receiving a security mode command from the network, where the security mode command is used to provide access layer security activation information;

sending a security mode failure message to the network, the security mode failure message being used to indicate security activation failure; and

Initiating a random access procedure to the network to establish a new RRC connection after sending a security mode failure message to the network and not receiving a radio resource control RRC connection release message from the network.
The device according to claim 9, characterized in that:

The transceiver unit is configured to initiate a random access procedure to the network after sending a security mode failure message to the network and not receiving an RRC connection release message from the network, including:

The transceiver unit is configured to initiate a random access procedure to the network if no RRC connection release message is received from the network within a first period of time after the security mode failure message is sent to the network.
The device according to claim 10, characterized in that:

The processing unit is further configured to start a timer after the sending and receiving unit sends the security mode failure message, and the duration of the timer is the first duration.
The device according to claim 11, characterized in that:

The processing unit is further configured to set a value of the first duration, and the value of the first duration is one of a plurality of settable values.
The device according to claim 9, characterized in that:

The transceiver unit is configured to initiate a random access procedure to the network after sending a security mode failure message to the network and not receiving an RRC connection release message from the network, including:

The transceiver unit is configured to initiate a random access procedure to the network when receiving other RRC messages from the network than the RRC connection release message after sending the security mode failure message to the network.
The device according to claim 13, characterized in that:

The other RRC messages include RRC connection reconfiguration messages.
The device according to claim 9, characterized in that:

The transceiver unit is configured to initiate a random access procedure to the network after sending a security mode failure message to the network and not receiving an RRC connection release message from the network, including:

The transceiver unit is configured to actively initiate a random access procedure to the network after sending a security mode failure message to the network.
The device according to any one of claims 9 to 15, characterized in that:

The transceiver unit is configured to initiate a random access procedure to the network after sending a security mode failure message to the network and not receiving an RRC connection release message from the network, including:

The transceiver unit is configured to first enter the RRC idle state after sending a safety mode failure message to the network and not receive an RRC connection release message from the network, and send a random message to the network according to business requirements. Access the lead.
A wireless communication device, characterized in that it includes:

A processor and a memory, wherein the memory is used to store program instructions, and the processor is used to execute the program instructions in the memory, so as to implement the method according to any one of claims 1 to 8.
A wireless communication device, characterized in that it includes:

processing circuits and interface circuits; where,

The interface circuit is used to couple with a memory external to the wireless communication device, and provide a communication interface for the processing circuit to access the memory;

The processing circuit is configured to execute program instructions in the memory, so as to implement the method as described in any one of claims 1-8.
A computer-readable storage medium, characterized in that:

A program code is stored in the computer-readable storage medium, and when the program code is executed by a processor, the method according to any one of claims 1 to 8 is implemented.
A computer program product, characterized in that:

When the program code included in the computer program product is executed by the processor, the method according to any one of claims 1 to 8 is implemented.