WO2024087986A1 - Network accessing method and related device thereof - Google Patents

Abstract

A network accessing method and a related device thereof, applied to Internet industry network communications. The method comprises: a first base station receives a first message sent by a communication device, the first message being used for instructing the communication device to access a second base station and a management device, wherein the second base station is a base station supporting access of the communication device; then, the first base station sends a handover request message to the management device on the basis of the first message, the handover request message being used for instructing the first base station to initiate S1 handover; next, the first base station receives a second message carrying a target NCC value sent by the management device, the target NCC value being obtained after the management device failing to prepare for S1 handover seven times in a row; and the first base station sends the target NCC value to the communication device on the basis of the second message, so that the communication device obtains the same key as the management device on the basis of the target NCC value. Therefore, it is ensured that a UE side can sense turnover of the NCC value, thereby ensuring that a key derived from a core network side is the same as a key derived from the UE side, and guaranteeing that a handover process is successfully executed.

Description

A method for accessing a network and a related device thereof

This application claims the priority of the Chinese patent application filed with the China Patent Office on October 28, 2022, with application number CN202211337501.X and application name “A method for accessing a network and related devices thereof”, the entire contents of which are incorporated by reference in this application.

Technical Field

The embodiments of the present application relate to the field of communications, and in particular to a method for accessing a network and related devices thereof.

Background technique

In the current security encryption process of Internet communications, the next hop chaining count (NCC) field is required for key derivation, and the key derivation includes two modes: horizontal derivation and vertical derivation.

Currently, after the user equipment (UE) completes access to the source base station, the S1 switching process is triggered. Due to some reasons, the S1 switching preparation fails, and the NCC value maintained by the core network (such as the mobility management entity (MME)) is accumulated during the S1 switching preparation failure process. However, the UE side does not perceive the S1 switching failure, so the NCC value maintained by the UE side remains unchanged. However, when there are too many consecutive S1 switching failures, the NCC value maintained by the MME flips, that is, the NCC value has completed a cycle of update. In the subsequent switching process for successful switching, the base station side and the UE side derive keys according to the latest NCC for information exchange. However, since the NCC value maintained by the MME flips, and the UE side does not perceive the flip of the NCC value, the number of keys derived by the UE side is different from the number of keys derived by the MME, resulting in the UE's key being different from the MME's key, which in turn causes the packet data convergence protocol (PDCD) integrity check to fail when subsequent uplink packets are sent, so that the base station side discards the reconfiguration completion message sent by the UE, resulting in the switching execution failure triggering a call drop.

Summary of the invention

The present application provides a method for accessing a network and a related device thereof, which are applied to network communications in the Internet industry. The present application solves the problem that when the UE side accesses the network, after the continuous S1 switching preparation fails for many times, the NCC value maintained by the core network side flips, that is, the NCC value completes a cycle of update, but the UE side cannot perceive the flipping of the NCC value, and ensures that the key derived by the core network side is the same as the key derived by the UE side, so as to ensure that when the UE side sends an uplink packet, the PDCD integrity check is successful, and the switching process is successfully executed and the communication is normal.

In a first aspect, a method for accessing a network is provided, comprising:

The first base station receives a first message sent by the communication device, wherein the first message is used to instruct the communication device to access the second base station and the management device, wherein the second base station is a base station supporting access by the communication device.

Then, the first base station sends a handover request message to the management device based on the first message, where the handover request message is used to instruct the first base station to initiate S1 handover.

Next, the first base station receives a second message sent by the management device and carrying a target NCC value, wherein the target NCC value is obtained by the management device failing to perform S1 handover preparation for seven consecutive times.

And the first base station sends the target NCC value to the communication device based on the second message, so that the communication device obtains the same key as the management device based on the target NCC value.

In the implementation manner of the present application, the first base station obtains a target NCC value, which is obtained by the management device based on seven consecutive failures of executing S1 handover preparation, and the first base station also sends the target NCC value to the communication device. As a result, the number of times the communication device derives a key based on the target NCC value is the same as the number of times the management device derives a key based on the target NCC value, that is, the communication device and the management device have the same key, thereby ensuring that the communication device, i.e., the UE side, perceives the flipping of the NCC value, and ensures that the key derived on the core network side is the same as the key derived on the UE side, thereby ensuring that when the UE side sends an uplink packet, the PDCD integrity check is successful, ensuring that the handover process is successfully executed, and the communication is normal.

In a possible implementation of the first aspect, the second message is used to indicate a current S1 switching preparation failure, the first base station determines that the S1 switching preparation failure indicated by the second message is the seventh consecutive S1 switching preparation failure, and the first base station sends a wireless resource control connection reconfiguration message to the communication device based on the target information, and the wireless resource control connection reconfiguration message carries a target NCC value.

In an implementation manner of the present application, the first base station determines that S1 handover preparation fails seven times in a row, and then sends a target NCC value to the communication device through a radio resource control connection reconfiguration message, providing a variety of application scenarios and reflecting the selectivity of the solution.

In a possible implementation manner of the first aspect, the target information belongs to a protocol field in protocol 33.401 or protocol 36.413.

In the implementation of the present application, the target information belongs to the protocol field in protocol 33.401 or protocol 36.413, which increases the complexity of the solution.

Diversity and flexibility.

In a possible implementation of the first aspect, before the first base station receives a second message carrying a target NCC value sent by the management device, the first base station receives a third message carrying a second NCC value sent by the management device, and the number of consecutive S1 switching preparation failures corresponding to the second NCC value is less than seven times.

In an implementation manner of the present application, the first base station receives the third message carrying the second NCC value sent by the management device, which enables the first base station to obtain the corresponding NCC value in real time, ensure real-time synchronization of the NCC value, and improve work accuracy.

In a possible implementation manner of the first aspect, the second message is sent by the management device after determining that the S1 switching preparation fails seven times consecutively.

In the implementation manner of the present application, the management device sends the target NCC value to the first base station only after determining that the S1 handover preparation fails seven times in a row, which can reduce information interaction and thus reduce resource occupation and improve work efficiency.

In a possible implementation of the first aspect, after the first base station sends the target NCC value to the communication device, the first base station receives a first NCC value sent by the management device, and its first NCC value corresponds to successful S1 switching preparation, and the first base station sends the first NCC value to the communication device, so that the communication device obtains the same key as the management device based on the first NCC value.

In the implementation manner of the present application, the communication device obtains the same key as the management device based on the first NCC value, which can ensure that the S1 handover or X2 handover is successfully executed, prevent call drops, and ensure normal communication.

In a second aspect, a method for accessing a network is provided, including:

The management device receives a switching request message sent by the first base station based on the first message, and the switching request message is used to instruct the first base station to initiate S1 switching, wherein the first message is used to instruct the communication device to access the second base station and the management device, wherein the first base station is the base station for accessing the communication device, and the second base station is the base station supporting access by the communication device.

Then, the management device performs S1 handover preparation based on the handover request message.

And in case the S1 switching preparation fails seven times in a row, the management device determines the target NCC value;

Furthermore, the management device sends a second message carrying the target NCC value to the first base station, so that the first base station sends the target NCC value to the communication device based on the second message.

In the implementation mode of the present application, the management device receives a switching request message sent by the first base station, and the management device performs S1 switching preparation based on the switching request message. When the S1 switching preparation fails for seven consecutive times, the management device determines the target NCC value and sends a second message carrying the target NCC value to the first base station, and the first base station sends the target NCC value to the communication device based on the second message. In this way, the number of times the communication device derives a key based on the target NCC value is the same as the number of times the management device derives a key based on the target NCC value, that is, the communication device and the management device have the same key, thereby ensuring that the communication device, i.e., the UE side, perceives the flipping of the NCC value, and ensures that the key derived on the core network side is the same as the key derived on the UE side, thereby ensuring that when the UE side sends an uplink packet, the PDCD integrity check is successful, ensuring that the switching process is successfully executed, and the communication is normal.

In a possible implementation of the second aspect, the second message is used to indicate that the current S1 switching preparation has failed. Before the management device determines the target NCC value, the management device sends a third message carrying the second NCC value to the first base station, and the number of consecutive S1 switching preparation failures corresponding to the second NCC value is less than seven times.

In an implementation manner of the present application, the management device sends a third message carrying the second NCC value to the first base station, which enables the first base station to obtain the corresponding NCC value in real time, ensures real-time synchronization of the NCC value, and improves the accuracy of the work.

In a possible implementation of the second aspect, after the management device sends a second message carrying the target NCC value to the first base station, the management device sends a first NCC value to the first base station, so that the first base station sends the first NCC value to the communication device, and the first NCC value corresponds to successful S1 switching preparation.

In an implementation manner of the present application, the management device sends a first NCC value to the first base station, and the first base station forwards the first NCC value to the communication device. The communication device then obtains the same key as the management device based on the first NCC value, thereby ensuring that the S1 switching or X2 switching is successful, preventing dropped calls, and ensuring normal communication.

In a third aspect, the present application provides a method for accessing a network, including:

The communication device sends a first message to the first base station, where the first message is used to instruct the communication device to access the second base station and the management device, wherein the first base station is a base station for accessing the communication device, and the second base station is a base station supporting access by the communication device.

Then, the communication device receives the target NCC value sent by the first base station, wherein the target NCC value is obtained by the management device failing to perform S1 handover preparation seven times in a row, wherein the S1 handover preparation is performed by the management device based on the handover request message sent by the first base station, and the handover request The message is sent by the first base station to the management device based on the first message.

The communication device acquires the same key as the management device based on the target NCC value.

In an embodiment of the present application, the communication device sends a first message to the first base station for accessing the second base station and the management device, and then the first base station sends a switching request message to the management device based on the first message, and the management device performs S1 switching preparation based on the switching request. When the S1 switching preparation fails for seven consecutive times, the management device determines the target NCC value and sends a second message carrying the target NCC value to the first base station, and the first base station sends the target NCC value to the communication device based on the second message. In this way, the number of times the communication device derives a key based on the target NCC value is the same as the number of times the management device derives a key based on the target NCC value, that is, the communication device and the management device have the same key, thereby ensuring that the communication device, i.e., the UE side, perceives the flipping of the NCC value, and ensures that the key derived on the core network side is the same as the key derived on the UE side, thereby ensuring that when the UE side sends an uplink packet, the PDCD integrity check is successful, ensuring that the switching process is successfully executed, and the communication is normal.

In a possible implementation manner of the third aspect, the communication device receives a radio resource control connection reconfiguration message sent by the first base station, where the radio resource control connection reconfiguration message carries a target NCC.

In an implementation manner of the present application, the communication device receives a radio resource control connection reconfiguration message carrying a target NCC value sent by the first base station, which is implemented by performing intra-cell switching through the first base station, thereby improving the implementation method of the present solution.

In a possible implementation of the third aspect, after the communication device receives the target NCC value sent by the first base station, the communication device receives a first NCC value sent by the first base station, the first NCC value corresponds to successful S1 switching preparation, and the communication device obtains the same key as the management device based on the first NCC value.

In an implementation manner of the present application, the communication device receives a first NCC value sent by the first base station, and the first NCC value corresponds to successful S1 switching preparation. The communication device then obtains the same key as the management device based on the first NCC value, thereby ensuring that the S1 switching or X2 switching is successfully executed, preventing dropped calls, and ensuring normal communication.

In a fourth aspect, a base station is provided, which has the function of implementing the method of the first aspect or any possible implementation of the first aspect. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

In the implementation manner of the present application, the base station of the fourth aspect executes the method described in the first aspect of the present application or any possible implementation manner of the first aspect.

In a fifth aspect, a management device is provided, which has the function of implementing the method of the second aspect or any possible implementation of the second aspect. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

In the implementation manner of the present application, the management device of the fifth aspect executes the method described in the second aspect of the present application or any possible implementation manner of the second aspect.

In a sixth aspect, a communication device is provided, which has the function of implementing the method of the third aspect or any possible implementation of the third aspect. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

In the implementation manner of the present application, the communication device of the sixth aspect executes the method described in the third aspect of the present application or any possible implementation manner of the third aspect.

In the seventh aspect, another communication device is provided, which may include a processor, which is coupled to a memory, wherein the memory is used to store instructions, and the processor is used to execute the instructions in the memory so that the communication device performs the method described in the first aspect of the present application or any possible implementation of the first aspect, or performs the method described in the second aspect of the present application or any possible implementation of the second aspect, or performs the method described in the third aspect of the present application or any possible implementation of the third aspect.

In an eighth aspect, another communication device is provided, comprising a processor for executing a computer program (or computer executable instructions) stored in a memory. When the computer program (or computer executable instructions) is executed, the method described in the first aspect and each possible implementation of the first aspect is executed, or the method described in the second aspect of the present application or any possible implementation of the second aspect is executed, or the method described in the third aspect of the present application or any possible implementation of the third aspect is executed.

In one possible implementation, the processor and the memory are integrated together;

In another possible implementation, the memory is located outside the communication device.

The communication device also includes a communication interface, which is used for the communication device to communicate with other devices, such as data and/or information. For example, the communication interface may be a transceiver, a circuit, a bus, a module or other types of communication interfaces.

The ninth aspect provides a computer-readable storage medium, including computer-readable instructions. When the computer-readable instructions are run on a computer, the method described in the first aspect, any possible implementation of the first aspect, the second aspect, any possible implementation of the second aspect, the third aspect, or any possible implementation of the third aspect of this application is executed.

In the tenth aspect, a computer program product is provided, comprising computer-readable instructions, which, when executed on a computer, enable the method described in the first aspect, any possible implementation of the first aspect, the second aspect, any possible implementation of the second aspect, the third aspect, or any possible implementation of the third aspect of the present application to be executed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of an application scenario in which S1 switching preparation fails;

FIG2 is another schematic diagram of an application scenario in which S1 switching preparation fails;

FIG3 is a schematic diagram of a method for accessing a network provided in an embodiment of the present application;

FIG4 is a schematic diagram of an application scenario provided by an embodiment of the present application;

FIG5 is another schematic diagram of an application scenario provided by an embodiment of the present application;

FIG6 is a schematic diagram of a structure of a communication device provided in an embodiment of the present application;

FIG7 is a schematic diagram of a structure of a base station provided in an embodiment of the present application;

FIG8 is a schematic diagram of a structure of a management device provided in an embodiment of the present application;

FIG. 9 is another schematic diagram of the structure of the communication device provided in an embodiment of the present application.

Detailed ways

The embodiment of the present application provides a method for accessing a network and a related device thereof, which are applied to network communications in the Internet industry. The method solves the problem that when the UE side accesses the network, after the continuous S1 switching preparation fails for many times, the NCC value maintained by the core network side flips, that is, the NCC value completes a cycle of update, but the UE side cannot perceive the flipping of the NCC value, and ensures that the key derived by the core network side is the same as the key derived by the UE side, so as to ensure that when the UE side sends an uplink packet, the PDCD integrity check is successful, and the switching process is successfully executed and the communication is normal.

The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and need not be used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, which is only to describe the distinction mode adopted by the objects of the same attributes when describing in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

To facilitate understanding of the embodiments of the present application, the following first briefly describes the relevant knowledge points of S1 switching and X2 switching and key derivation.

S1 handover is specifically S1 interface handover. S1 interface is the interface between evolved node B (eNB) and MME. S1 handover is mainly used for handover-related commands between base stations across MME.

X2 handover is specifically X2 interface handover. X2 interface is the interface between two eNBs. X2 handover is mainly used for interactive handover related commands between base stations, and can directly transmit service data between base stations.

Key derivation: Currently, in the security encryption process, the NCC field is required for key derivation. The range of the NCC field defined in the protocol is 0 to 7. Among them, the key is divided into horizontal derivation and vertical derivation.

Among them, S1 switching adopts vertical derivation, and a new key is derived from the initial key and the NCC value. Specifically, the final target key is derived from the initial key from the initial NCC value to the current NCC value in a loop. For example, the initial NCC=2, the current NCC=4, the initial key and NCC=3 are used to derive a new key, and then the target key is derived based on the new key and NCC=4. It can be understood that this example is only used to illustrate the understanding of the embodiment of the present application, and is not specifically limited here.

Among them, X2 switching adopts horizontal derivation, and a new key is derived from the initial key plus the current cell frequency and the physical cell identifier (PCI). It should be noted that the combination of each cell frequency and PCI is different.

Before introducing the embodiments of the present application, the following briefly introduces the relevant application scenarios of S1 switching preparation failure to facilitate subsequent understanding of the embodiments of the present application.

First, the application scenario where the continuous S1 switching preparation failures leading to the S1 switching failure is described as an example. For details, please refer to FIG. 1. FIG. 1 is a schematic diagram of an application scenario in which S1 handover preparation fails. This application scenario takes UE accessing a network access base station as an example. First, in step 101, the UE sends an access message to the source base station, i.e., source eNB, to access the base station and MME. Then, in step 102, the source eNB initiates S1 handover by sending an S1 handover request message (e.g., the handover require message in FIG. 1 ) to the MME. At this time, the NCC values maintained by the UE and the MME are both 2, i.e., NNC=2. Then, after receiving the handover require message, the MME executes step 103 to accumulate the maintained NCC value, i.e., NCC+. The current NCC value changes from 2 to 3, i.e., the NCC currently maintained by the MME is 3. The MME executes step 104 to send a handover request message carrying NCC=3 to the target base station 1, i.e., target eNB1, so that the target eNB1 obtains the current NCC value. At this time, the S1 handover preparation performed by the target eNB1 fails, and the target eNB1 executes step 105 to reply the handover preparation failure message, i.e., the handover preparation fail message, to the MME, and the MME executes step 106 to forward the handover preparation fail message to the source eNB, so that the source eNB determines that the current S1 handover preparation fails. As shown in FIG1 , from step 102 to step 111, there are 10 consecutive S1 handover preparation failures, and the current MME maintains NCC=4. At this time, the MME derives keys 10 times (specifically, the corresponding NCC in the derivation process is 3, 4, 5, 6, 7, 0, 1, 2, 3, 4). It can be understood that steps 107 to 111 are similar to those described in the aforementioned steps 102 to 106, and the details are not repeated here.

It can be seen that the NCC value has been updated for more than one cycle according to the definition range 0-7 of the NCC field, and the NCC value has flipped. Therefore, when the MME continues to execute steps 112 and 113 to obtain the current NCC＝5, the MME executes step 114 to send a handover request message carrying NCC＝5 to the target base station 2, namely target eNB2. At this time, the target eNB2 executes step 115 to send a handover preparation success message, namely a handover request acknowledgment message, to the MME. Then the MME executes step 116 to send a handover command message carrying NCC＝5 to the source eNB, namely a handover command message, triggering the source eNB to execute step 117 to send a radio resource control (RRC) connection reconfiguration message, namely an RRC connection reconfiguration message, to the UE, and the message carries the NCC＝5 corresponding to the successful S1 handover preparation. Therefore, the UE executes step 118 to send an RRC connection reconfiguration completion message, namely an RRC connection reconfiguration complete message based on the key derived from NCC＝5.

However, since the initial NCC of the UE is 2, and the corresponding NCC value for successful S1 handover preparation is 5, the UE derives keys 3 times (with NCC=3, 4, 5 respectively), while the MME derives keys 11 times. As a result, the keys of the UE and MME are inconsistent, resulting in the failure of the PCDC integrity check and being discarded by the PCDC layer of the target eNB2, which in turn causes the handover failure to trigger a call drop.

The following also provides an application scenario in which X2 handover failure due to continuous S1 handover preparation failure is explained as an example. For details, please refer to Figure 2, which is another schematic diagram of an application scenario in which S1 handover preparation fails. This application scenario takes UE accessing a network access base station as an example. Among them, the initial NCC values maintained by the UE and the MME are both 2. The UE executes step 201 to send an access message to the source eNB to access the base station and the MME, and then the source eNB executes step 202 to send a handover require message to the MME to initiate S1 handover. The MME executes step 203 to accumulate the NCC value to obtain NCC=3, and executes step 204 to send a handover request message carrying NCC=3 to the target eNB1. However, the target eNB1 fails to perform S1 handover preparation, so the target eNB1 executes step 205 to send a handover request message to the MME. The ME sends a handover preparation fail message to inform the MME that the current S1 handover preparation has failed, and the MME executes step 206 to forward the message to the source eNB until step 11. During this period, there are a total of 10 consecutive S1 handover preparation failures, and steps 207 to 211 correspond to the NCC=4 maintained by the MME. At this time, the MME derives the key 10 times (specifically, the corresponding NCCs in the derivation process are 3, 4, 5, 6, 7, 0, 1, 2, 3, 4). It can be understood that steps 207 to 211 are similar to those described in the aforementioned steps 202 to 206, and the details are not repeated here. During this period, the NCC value and the update of the NCC field definition range 0-7 exceed one cycle, that is, the NCC value has flipped.

After step 211, the source eNB executes step 212 to directly send a handover request message to the target eNB2 to initiate S1 handover. The handover request message is a key derived horizontally based on the initial key corresponding to NCC=2 of the source eNB. After the target eNB2 successfully executes S1 handover preparation, it executes step 213 to reply a handover request acknowledge message to the source eNB to inform that the S1 handover preparation is successful. Then, the source eNB executes step 214 to send an RRC connection reconfiguration message carrying NCC=2 to the UE, so that the UE obtains the NCC value corresponding to the successful S1 handover preparation. Then the UE derives a key horizontally based on the current NCC value to obtain the same key as the target eNB2, and executes step 215 based on the key to send an RRC connection reconfiguration complete message to the target eNB2, and then the target eNB2 executes step 216 to send a path switch request, i.e., a path switch request message, to the MME to notify the MME that the UE has changed the cell. After receiving the message, the MME executes step 217 to accumulate the NCC, i.e., the current NCC=5, and the MME continues to execute step 218 to send a path switch request confirmation message, i.e., a path switch request acknowledge message, to the target eNB2, and the path switch request acknowledge message also carries NCC=5 and the key A derived 11 times by the MME from NCC=2, and the target eNB2 sends a handover request message to the target eNB3 based on the received NCC=5 and the corresponding key A. Then, target eNB3 also executes step 219 based on NCC=5 and the corresponding key A to send a handover request acknowledge message to target eNB2. Then, target eNB2 executes step 220 to send an RRC connection reconfiguration message carrying NCC=5 to UE. Then, UE executes step 221 to derive the corresponding key B from NCC=2 three times based on NCC=5. Then, UE executes step 222 to send an RRC connection reconfiguration complete message to target eNB3. However, since the UE's key B is derived from NCC=2 three times, and the target eNB3's key A is derived from NCC=2 11 times, the key A is different from the key B, which results in the failure of the PCDC integrity check of the reconfiguration complete message. The reconfiguration complete message is discarded by target eNB3, and the X2 handover failure triggers a call drop.

From the above two examples, it can be seen that when the number of consecutive S1 switching preparation failures is at least 7 times, the NCC value is updated for at least one cycle and flipped. Therefore, when the subsequent S1 switching preparation is successful, the UE cannot perceive the NCC value flipping according to the NCC value corresponding to the successful S1 switching preparation. Therefore, based on the same NCC value, the number of times the UE derives the key is different from the number of times the MME derives the key, and the keys obtained by both parties are also different, resulting in the reconfiguration completion message sent by the UE to the target base station being discarded by the target base station due to the failure of the PCDC verification, which in turn causes the S1 switching or X2 switching execution failure to trigger a call drop.

To solve the above-mentioned problems, the embodiment of the present application first provides a method for accessing a network and a related device thereof, which are applied in the Internet industry. Among them, a first base station receives a first message sent by a communication device, and the first message is used to instruct the communication device to access a second base station and a management device, wherein the first base station is a base station for accessing the communication device, i.e., a source base station, and the second base station is a base station supporting access by the communication device, i.e., a target base station. Then, the first base station sends a switching request message to the management device based on the first message, and the switching request message is used to instruct the first base station to initiate an S1 switching. After that, the first base station receives a second message carrying a target NCC value sent by the management device, and then, the first base station sends the target NCC value to the communication device based on the second message, so that the communication device obtains the same key as the management device based on the target NCC value. The problem that the UE side cannot perceive the NCC value maintained by the core network side after flipping after the continuous S1 switching preparation fails multiple times during the process of accessing the network on the UE side is solved, and the key derived from the core network side is ensured to be the same as the key derived from the UE side, so as to ensure that when the UE side sends an uplink packet, its PCDC integrity check is successful, and the switching process is successfully executed and the communication is normal.

In order to better understand the embodiments of the present application, a method for accessing a network provided by the embodiments of the present application is first described in detail below in conjunction with the accompanying drawings. It is known to those skilled in the art that with the development of technology and the emergence of new scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

For ease of understanding, the following still introduces a method for accessing a network provided by an embodiment of the present application based on the application scenario example of S1 switching. For details, please refer to FIG. 3, which is a schematic diagram of a method for accessing a network provided by an embodiment of the present application. Specifically, it includes:

A1. The communication device sends a first message to the first base station.

The communication device sends a first message to the first base station, and the first message at least indicates that the communication device accesses the second base station and the management device, wherein the first base station is the base station for accessing the communication device, and the second base station is the base station supporting access by the communication device, which mainly allocates access resources.

For example, in order to facilitate understanding of the specific implementation of the embodiment of the present application, the following is explained based on the provided application scenario example. Please refer to Figure 4 for details, which is a schematic diagram of the application scenario provided by the embodiment of the present application. For example, the first base station is the source base station, i.e., source eNB, the second base station is the target base station, i.e., target eNB, the communication device is UE, and the management device is MME.

The first base station receives the first message sent by the communication device, that is, step 401 in FIG. 4:

401. The source eNB receives the first message sent by the UE.

The UE sends a first message to the source eNB, and accesses the target eNB and the MME through the source eNB, where the MME belongs to the core network. The details are similar to those in step 201 of FIG. 2 , and will not be described in detail here.

A2. The first base station sends a switching request message to the management device.

The first base station sends a handover request message to the management device based on the first message, where the handover request message is used to instruct the first base station to initiate S1 handover.

Then, the management device executes the S1 handover preparation process based on the first message. For example, the execution of the S1 handover preparation process is described by taking FIG. 4 as an example, wherein the management device takes MME as an example, and the first message takes a handover require message as an example, specifically including:

402. The source eNB sends a handover require message to the MME.

The Source eNB initiates S1 handover and sends a handover require message to the MME to execute the S1 handover preparation process. The details are similar to those in step 202 in FIG. 2 above and will not be described in detail here.

403. The MME accumulates the NCC value.

After receiving the handover require message, the MME accumulates the NCC value, that is, executes NCC+. The initial NCC value maintained by the MME is 2, and the accumulated NCC=3. It should be noted that step 403 is similar to step 203 in FIG. 2 , and will not be described in detail here.

404. MME sends a handover request message to the target eNB.

After obtaining NCC=3, the MME sends a handover request message to the target eNB, and the message carries NCC=3. However, the target eNB fails to perform handover preparation and executes step 405, which is as follows:

405. The target eNB sends a handover preparation fail message to the MME.

The target eNB sends a handover preparation fail message to the MME to inform that the current S1 handover preparation has failed. The details are similar to those in step 205 in FIG. 2 , and will not be described in detail here.

Based on the above-mentioned current S1 handover preparation failure, in a possible implementation, the management device sends a third message carrying a second NCC value to the first base station, and the number of consecutive current S1 handover preparation failures corresponding to the second NCC value is less than seven times, and as described in step A3 of FIG. 3:

A3. The management device sends a third message to the first base station.

The management device sends a third message to the first base station, the third message carrying the second NCC value. Specifically, whenever the S1 handover preparation fails, the management device sends a message to the first base station carrying the NCC value corresponding to the current S1 handover preparation failure.

Exemplarily, the following still corresponds to the example of FIG. 4 , and the third message may be a handover preparation fail message, which is as follows:

Step 406: MME sends a handover preparation fail message carrying NCC=3 to the source eNB.

After receiving the handover preparation fail message, the MME determines that the current S1 handover preparation has failed, and sends the NCC=3 currently maintained by the MME to the source eNB. For example, the handover preparation fail message forwarded to the source eNB may carry NCC=3 and be sent.

It should be noted that step 406 in the aforementioned FIG. 4 is merely used as an example for understanding the embodiment of the present application. It is understandable that the third message may also be other notification messages or reports, which are not specifically limited here.

Based on the above-mentioned current S1 handover preparation failure, in a possible implementation method, the management device sends a handover preparation fail message to the first base station. The message does not carry an NCC value and is only used to inform the first base station that the current S1 handover preparation has failed. For ease of understanding, please refer to the application scenario of Figure 5 as an example for explanation. Figure 5 is another schematic diagram of the application scenario provided by the embodiment of the present application. Among them, steps 501 to 505 are similar to those described in steps 401 to 404 in Figure 4 above, and the details are not repeated here. Please refer to the following step 506 for details:

Step 506: MME sends a handover preparation fail message to the source eNB.

After receiving the handover preparation fail message sent by the target eNB, the MME forwards the message to the source eNB to inform the source eNB that the current S1 handover preparation has failed so that the source eNB can continue to initiate the S1 handover.

In an implementation manner of the present application, the management device sends a third message carrying the second NCC value to the first base station, which enables the first base station to obtain the corresponding NCC value in real time, ensures real-time synchronization of the NCC value, and improves the accuracy of the work.

In the examples of Figures 4 and 5 above, when S1 handover preparation fails, the source eNB will receive a handover failure message to determine that the current S1 handover preparation has failed. The source eNB will continue to initiate S1 handover until S1 handover preparation succeeds.

Among them, until the S1 handover preparation fails seven times in a row, in a possible implementation, the first base station receives a second message carrying a target NCC value sent by the management device, and the target NCC value is obtained by the management device performing the S1 handover preparation failure seven times in a row. Specifically, please refer to step A4 in Figure 3, which is as follows:

A4. The management device sends a second message to the first base station.

The management device sends a second message carrying a target NCC to the first base station. The target NCC is obtained by the management device failing to perform S1 handover preparation for seven consecutive times.

In a possible implementation manner, the second message is used to indicate that the current S1 switching preparation fails.

Exemplarily, the following is still described using FIG. 4 as an example, wherein before the management device, i.e., the MME, sends the second message to the first base station, i.e., the source eNB, the MME executes the S1 handover preparation process multiple times, and the S1 handover preparation fails 7 times. Specifically, it includes:

407. The source eNB sends a handover require message to the MME.

Before step 407, the S1 handover preparation has failed six times in a row (excluding the S1 handover success and the X2 handover success). The NCC values are 3, 4, 5, 6, 7 and 0 respectively, and then the source eNB continues to initiate S1 handover, that is, sending a handover require message to the MME.

408. The MME performs accumulation of NCC values.

The MME accumulates the NCC value and obtains NCC=1.

409. MME sends a handover request message to the target eNB.

MME sends a handover request message to the target eNB, and the message carries NCC=1.

410. The target eNB sends a handover preparation fail message to the MME.

After the target eNB fails to execute S1 handover preparation, it sends a handover preparation fail message to the MME.

Steps 407 to 410 are similar to the aforementioned steps 402 to 405 and will not be described in detail here.

After receiving the handover preparation fail message, the MME executes step 411, which is as follows:

411. MME sends a handover preparation fail message with NCC=1 to the source eNB.

MME sends a handover preparation fail message carrying NCC = 1 to the source eNB. In step 402 to step 410, there have been seven consecutive S1 handover preparation failures, that is, the target NCC is 1, and the second message is the handover preparation fail message.

It should be noted that FIG4 only uses the handover preparation fail message as an example of the second message to illustrate the embodiment of the present application. It is understandable that the second message may also be other notification messages or reports, which are not specifically limited here.

In an implementation manner of the present application, the second message indicates that the current S1 switching preparation has failed. The management device sends the second message to the first base station in real time according to the S1 switching preparation failure, so that the first base station obtains the corresponding NCC value in real time, ensures real-time synchronization of the NCC value, and improves the accuracy of the work.

In a possible implementation, the second message is sent by the management device after determining that the S1 handover preparation fails seven times in succession. Exemplarily, FIG. 5 is used as an example for illustration, wherein steps 507 to 510 are similar to steps 407 to 410 in FIG. 4 above, and are not described in detail here.

After step 510, i.e., the MME receives the handover preparation fail message, the MME executes the following step 511:

511. MME sends a handover preparation fail message to source eNB.

MME forwards the received handover preparation fail message to source eNB, so that source eNB perceives that the current S1 handover preparation has failed.

After the MME executes step 511, when the MME determines that the number of consecutive S1 handover failures reaches seven, the MME sends a second message to the source eNB, and the second message includes the target NCC value. The specific steps are as follows:

Step 512: The MME determines that the number of consecutive S1 handover preparation failures reaches seven.

Exemplarily, in a possible implementation, the MME accumulates the number of consecutive S1 handover preparation failures and determines in real time whether the number of consecutive S1 handover preparation failures reaches seven. Optionally, when NCC=1, the corresponding S1 handover preparation fails, and the initial NCC value of the MME is 2, and there is no S1 handover or X2 handover success in the middle, then the MME determines that the number of consecutive handover preparation failures reaches seven.

When the MME determines that the number of consecutive S1 handover preparation failures reaches seven, the MME performs the following step 513:

513. MME sends an NCC update indication message to the source eNB.

The MME sends an NCC update indication message carrying NCC=1 to the source eNB, that is, in the example of FIG5 , the second message is the NCC update indication message. The NCC update indication is mainly used to send the target NCC value to the source eNB, so that the source eNB obtains the NCC value to be flipped, so that the subsequent communication device can obtain the same key as the MME.

Optionally, the second message, i.e., the NCC update indication message, may be a message or a field, which carries the target NCC value. It is understandable that the second message may also be in other forms, which are not specifically limited here.

In the implementation manner of the present application, the management device sends the target NCC value to the first base station only after determining that the S1 handover preparation fails seven times in a row, which can reduce information interaction and thus reduce resource occupation and improve work efficiency.

As described above, the first base station receives the second message carrying the target NCC, and then the first base station sends the target NCC value to the communication device based on the second message, as shown in step A5 in FIG3 :

A5. The first base station sends a target NCC value to the communication device.

The first base station triggers the intra-cell handover process based on the second message, thereby sending the target NCC value obtained by the first base station to the communication device.

In one possible implementation, the second message is used to indicate a current S1 switching preparation failure, and the first base station determines that the S1 switching preparation failure indicated by the second message is the seventh consecutive S1 switching preparation failure. The first base station sends a radio resource control connection reconfiguration (RRC connection reconfiguration) message to the communication device based on the target information, and the RRC connection reconfiguration message carries a target NCC value.

For example, the following is still described using FIG. 4 as an example, specifically including:

Step 412: The source eNB determines that the number of consecutive S1 handover preparation failures reaches seven.

Among them, the first base station, namely the source eNB, accumulates consecutive S1 handover preparation failures, and when an S1 handover success or an X2 handover success occurs during the accumulation process, it accumulates again. When the source eNB receives the message sent in step 411, the total number of consecutive S1 handover failures is seven, that is, the S1 handover preparation failure indicated by the second message is the seventh consecutive S1 handover preparation failure.

Optionally, the source eNB may record at least the NCC value corresponding to the first S1 handover preparation failure (it should be noted that the NCC value is recorded again when the S1 handover is successful or the X2 handover is successful), and determine that the S1 handover preparation failure indicated by the second message is the seventh consecutive S1 handover preparation failure based on the first S1 and target NCC values.

Afterwards, the first base station, i.e., source eNB, triggers intra-cell handover based on the target information to refresh the NCC value of the communication device, i.e., UE. Specifically, as shown in step 413 in FIG. 4:

413. The source eNB sends an RRC connection reconfiguration message to the UE.

Based on the target information, when the source eNB determines that the S1 handover preparation has failed seven times in a row, the source eNB is triggered to perform an intra-cell handover. The source eNB sends an RRC connection reconfiguration message to the UE, which carries a handover indication. The target cell for handover is the cell where the UE accesses the source eNB. It also carries a target NCC value, i.e., NCC=1, which is used for key update. That is, the UE obtains the target NCC value and updates the key to ensure that after the NCC value is flipped, the number of times the communication device derives the key is the same as the number of times the management device derives the key, and the same key is obtained. The subsequent S1 handover or X2 handover can be executed normally, thereby preventing call drops and ensuring normal communication.

It should be noted that the target information belongs to the protocol field in protocol 33.401 or protocol 36.413. Exemplarily, the target information may be "Re-freshing the KeNB is done using intra cell handover as described in clause "KeNB refresh" of the present specification when S1-based handover preparation fails reach seven consecutive times". It can be understood that the target information may also belong to other protocols, and the specific content of the target information may be determined according to the actual application scenario, which is not limited here.

In the implementation manner of the present application, the target information belongs to the protocol field in protocol 33.401 or protocol 36.413, which increases the diversity and flexibility of the solution.

Afterwards, the UE executes step 414 to determine that the keys of both parties are the same, as follows:

Step 414: UE sends an RRC connection reconfiguration complete message to source eNB.

UE sends an RRC connection reconfiguration complete message to source eNB. At this time, the key derived by UE based on the target NCC value is the same as the key derived by source eNB based on the target NCC value. The message passes the PCDC integrity check successfully. Source eNB receives the reconfiguration completion message normally, ensuring the success of subsequent switching.

In an implementation manner of the present application, the first base station determines that S1 handover preparation fails seven times in a row, and then sends a target NCC value to the communication device through a radio resource control connection reconfiguration message, providing a variety of application scenarios and reflecting the selectivity of the solution.

In addition, in the example of FIG. 5 , the second message in step 513, namely the NCC update indication message, can be used to indicate that the S1 handover preparation fails seven times in a row, so the source eNB can trigger the intra-cell handover based on the second message to update the NCC value of the UE. That is, as shown in the following step 514:

514. The source eNB sends an RRC connection reconfiguration message to the UE.

The source eNB triggers intra-cell switching based on the second message and sends an RRC connection reconfiguration message to the UE. The message carries the target NCC value, which is similar to that described in step 413 in FIG. 4 above and will not be described in detail here.

Then, the UE updates the key based on the target NCC value and executes step 515 as follows:

515. UE sends an RRC connection reconfiguration complete message to source eNB.

It should be noted that step 515 is similar to step 414 in FIG. 4 , and will not be described in detail here.

It should be noted that the aforementioned target NCC value is the NCC value corresponding to seven consecutive S1 switching preparation failures. The judgment of the seven consecutive times is based on the NCC value maintained by the UE. It can be understood that when the UE's initial NCC value is updated to the target NCC value, exemplarily, as in the aforementioned Example 4 or Example 5, the UE's NCC=2 is updated to NCC=1, that is, the target NCC value corresponding to the next seven consecutive S1 switching preparation failures starts to accumulate from NCC=1.

In an implementation manner of the present application, the communication device obtains the target NCC value, which can ensure that the communication device perceives the flipping of the NCC value, ensures that the number of times the communication device derives keys is the same as the number of times the management device derives keys, and further ensures that the keys derived by the communication device are the same as the keys derived by the management device.

In one possible implementation, after the first base station sends the target NCC value to the communication device, the first base station receives a first NCC value sent by the management device, which corresponds to successful S1 switching preparation. Then the first base station sends the first NCC value to the communication device, so that the communication device obtains the same key as the management device based on the first NCC value.

For example, please refer to step A6, step A7 and step A8 in FIG. 3 , which are specifically as follows:

A6. The management device sends the first NCC value to the first base station.

After the first base station sends the target NCC value to the communication device, the management device sends a first NCC value to the first base station, where the first NCC value corresponds to successful S1 handover preparation.

Exemplarily, after the management device receives the message indicating that the S1 switching is ready successfully, the management device sends a handover command message carrying the first NCC value to the first base station, which is similar to that described in FIG. 1 or FIG. 2 above and will not be described in detail here.

Afterwards, the first base station performs step A7:

A7. The first base station sends a first NCC value to the communication device.

Exemplarily, the first base station sends an RRC connection reconfiguration message carrying a first NCC value to the communication device, which is similar to that described in the aforementioned Figures 4 and 5 and will not be described in detail here.

Then, the communication device executes step A8:

A8. The communication device determines a key based on the first NCC value.

The number of times the communication device derives the key based on the first NCC value is the same as the number of times the management device derives the key based on the first NCC value, that is, the keys derived by the communication device and the management device based on the first NCC value are the same.

In the implementation manner of the present application, the communication device obtains the same key as the management device based on the first NCC value, which can ensure that the S1 handover or X2 handover is successfully executed, prevent call drops, and ensure normal communication.

In an embodiment of the present application, the communication device sends a first message to the first base station for accessing the second base station and the management device, and then the first base station sends a switching request message to the management device based on the first message, and the management device performs S1 switching preparation based on the switching request. When the S1 switching preparation fails for seven consecutive times, the management device determines the target NCC value and sends a second message carrying the target NCC value to the first base station, and the first base station sends the target NCC value to the communication device based on the second message. In this way, the number of times the communication device derives a key based on the target NCC value is the same as the number of times the management device derives a key based on the target NCC value, that is, the communication device and the management device have the same key, thereby ensuring that the communication device, i.e., the UE side, perceives the flipping of the NCC value, and ensures that the key derived on the core network side is the same as the key derived on the UE side, thereby ensuring that when the UE side sends an uplink packet, the PDCD integrity check is successful, ensuring that the switching process is successfully executed, and the communication is normal.

It should be noted that the aforementioned Figures 4 and 5 are merely used as examples for understanding the embodiments of the present application and do not impose substantial limitations on the present application. It is understandable that the actual application scenarios may also be in other forms, which are not specifically limited here.

The above is a detailed introduction to a method for accessing a network provided by an embodiment of the present application. The principles and implementation methods of the present application are described in detail using specific examples herein. The description of the above embodiments is only used to help understand the method and core idea of the present application. At the same time, for a person skilled in the art, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as limiting the present application.

It should be noted that the aforementioned communication device may be a vehicle-mounted computer device, industrial equipment, a personal computer, a terminal, a tablet computer, a watch or other network device or computer device that accesses a base station, and is not specifically limited here.

In order to implement the functions of the method provided in the above embodiment of the present application, the communication device, the first base station and/or the management device may include a hardware structure and/or a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether one of the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

As shown in Figure 6, an embodiment of the present application also provides a communication device, which is applied to the Internet industry. Please refer to Figure 6 for details. Figure 6 is a structural schematic diagram of a communication device provided in an embodiment of the present application. In one possible implementation, the communication device may include a module or unit that corresponds to the method/operation/step/action of Figure 3 in the above method embodiment. The unit may be a hardware circuit, or software, or a hardware circuit combined with software. In one possible implementation, the communication device 600 may include: a receiving unit 601, a processing unit 602, and a sending unit 603. The sending unit 603 can be used to execute the step of sending a first message to the first base station in the above method embodiment, the receiving unit 601 can be used to execute the step of receiving the target NCC value in the above method embodiment, and the processing unit 602 can be used to execute the step of obtaining the same key as the management device based on the target NCC in the above method embodiment.

In an embodiment of the present application, a sending unit 603 sends a first message to a first base station for accessing a second base station and a management device, and a receiving unit 601 receives a target NCC value sent by the first base station, the target NCC value being obtained by the management device after seven failed attempts to perform S1 handover preparation, the S1 handover preparation being performed by the management device based on a handover request message sent by the first base station, the handover request message being sent by the first base station based on the first message. The processing unit 602 obtains the same key as the management device based on the target NCC value. This can solve the problem that the UE side cannot perceive the flipping of the NCC value, and ensure in real time that the keys on the UE side and the core network side are the same, thereby ensuring that when the UE side sends an uplink packet, the PDCD integrity check is successful, ensuring that the handover process is successfully executed, and that communication is normal.

In other possible designs, the above-mentioned receiving unit 601, processing unit 602 and sending unit 603 can execute the methods/operations/steps/actions in various possible implementation methods of the communication device in the above-mentioned method embodiment one by one.

In a possible design, the above-mentioned receiving unit 601 is specifically used to receive a wireless resource control connection reconfiguration message sent by the first base station, and the wireless resource control connection reconfiguration message carries a target NCC.

In a possible design, the receiving unit 601 is further used to receive a first NCC value sent by the first base station, wherein the first NCC value corresponds to successful S1 switching preparation, and the processing unit 602 is further used to obtain the same key as the management device based on the first NCC value.

For the beneficial effects of the various designed communication devices mentioned above in the present application, please refer to the beneficial effects of the various corresponding implementation methods in the method embodiments in the above Figures 3, 4 and 5, and the details will not be repeated here.

It should be noted that the information interaction, execution process, etc. between the modules/units in the communication device of the embodiment corresponding to Figure 6 are based on the same concept as the method embodiment corresponding to Figure 3 in the present application. For specific contents, please refer to the description in the method embodiment shown in the previous part of the present application, and will not be repeated here.

As shown in Figure 7, an embodiment of the present application also provides a base station, which is applied to the Internet industry. Please refer to Figure 7 for details. Figure 7 is a structural diagram of a base station provided in an embodiment of the present application. In one possible implementation, the base station may include a module or unit that corresponds to the method/operation/step/action of Figure 3 in the above method embodiment. The unit may be a hardware circuit, or software, or a hardware circuit combined with software. In one possible implementation, the base station 700 may include: a receiving unit 701, a processing unit 702, and a sending unit 703. The receiving unit 701 can be used to perform the steps of receiving a first message and receiving a second message in the above method embodiment, and the sending unit 703 can be used to perform the steps of sending a switching request message to a management device and sending a target NCC in the above method embodiment.

In another possible design, the base station 700 further includes a processing unit, wherein the second message is used to indicate a current S1 switching preparation failure, the processing unit 702 is used to determine that the S1 switching preparation failure indicated by the second message is the seventh consecutive S1 switching preparation failure, and the sending unit 703 is specifically used to send a wireless resource control connection reconfiguration message to the communication device based on the target information, and the wireless resource control connection reconfiguration message carries a target NCC value.

In an embodiment of the present application, a receiving unit 701 receives a first message sent by a communication device, and the first message is used to instruct the communication device to access a second base station and a management device, and the second device is a base station that supports access by the communication device. Then, a sending unit 703 sends a switching request message to the management device based on the first message, and the switching request message is used to instruct the base station to initiate an S1 switch. Next, the receiving unit 701 receives a second message carrying a target NCC value sent by the management device, and the target NCC value is obtained by the management device failing to perform S1 switching preparation seven times in a row. Its sending unit 703 sends the target NCC value to the communication device, so that the communication device obtains the same key as the management device based on the target NCC value. This can solve the problem that the UE side cannot perceive the NCC value flip, and ensure that the keys on the UE side and the core network side are the same in real time, thereby ensuring that when the UE side sends an uplink packet, the PDCD integrity check is successful, ensuring that the switching process is successfully executed, and communication is normal.

In other possible designs, the above-mentioned receiving unit 701, processing unit 702 and sending unit 703 can execute the methods/operations/steps/actions in various possible implementation methods of the first base station in the above-mentioned method embodiment one by one.

In one possible design, the above target information belongs to the protocol field in protocol 33.401 or protocol 36.413.

In one possible design, the above-mentioned receiving unit 701, before receiving the second message carrying the target NCC value sent by the management device, is also used to receive a third message carrying a second NCC value sent by the management device, and the number of consecutive S1 switching preparation failures corresponding to the second NCC value is less than seven times.

In a possible design, the second message is sent by the management device after determining that S1 switching preparation has failed seven times in a row.

In a possible design, the receiving unit 701 receives a first NCC value sent by a management device, and the first NCC value corresponds to successful S1 switching preparation.

The sending unit 703 is further configured to send the first NCC value to the communication device, so that the communication device obtains the same key as the management device based on the first NCC value.

For the beneficial effects of the various designs of base stations mentioned above in the present application, please refer to the beneficial effects of the various corresponding implementation methods in the method embodiments in Figures 3, 4 and 5 above, and the details will not be repeated here.

It should be noted that the information interaction, execution process, etc. between the modules/units in the base station of the embodiment corresponding to Figure 7 are based on the same concept as the method embodiment corresponding to Figure 3 in the present application. For specific contents, please refer to the description in the method embodiment shown in the previous part of the present application, and will not be repeated here.

As shown in Figure 8, an embodiment of the present application also provides a management device, which is applied to the Internet industry. Please refer to Figure 8 for details. Figure 8 is a structural diagram of the management device provided by the embodiment of the present application. In one possible implementation, the management device may include a module or unit that corresponds to the method/operation/step/action of Figure 3 in the above method embodiment. The unit may be a hardware circuit, or software, or a hardware circuit combined with software. In one possible implementation, the management device 800 may include: a receiving unit 801, a processing unit 802, and a sending unit 803. The receiving unit 801 can be used to perform the step of receiving a switching request message in the above method embodiment, the processing unit 802 can be used to perform the step of executing the S1 switching preparation process based on the switching request message and the step of determining the target NCC value, and the sending unit 803 can be used to perform the step of sending a second message carrying the target NCC value to the first base station in the above method embodiment.

In an embodiment of the present application, a receiving unit 801 receives a handover request message sent by a first base station based on a first message, wherein the handover request message is used to instruct the first base station to initiate an S1 handover, and the first message is used to instruct the communication device to access the second base station and the management device, wherein the first base station is a base station for accessing the communication device, and the second base station is a base station that supports access by the communication device. Then, the processing unit 802 performs S1 handover preparation based on the handover request message, and determines the target NCC value when the S1 handover preparation fails seven times in a row. Next, the sending unit 803 sends a second message carrying the target NCC value to the first base station, so that the first base station sends the target NCC value to the communication device based on the second message. In this way, the first base station can obtain the target NCC value that is about to flip, and the first base station sends the target NCC value to the communication device, which can solve the problem that the UE side cannot perceive the flip of the NCC value, and ensures that the keys on the UE side and the core network side are the same in real time, thereby ensuring that when the UE side sends an uplink packet, the PDCD integrity check is successful, and the handover process is successfully executed and the communication is normal.

In other possible designs, the above-mentioned receiving unit 801, processing unit 802 and sending unit 803 can execute the methods/operations/steps/actions in various possible implementation methods of the management device in the above-mentioned method embodiment one by one.

In one possible design, the above-mentioned sending unit 803, when the second message is used to indicate the current S1 switching preparation failure and before the management device determines the target NCC value, is also used to send a third message carrying a second NCC value to the first base station, and the number of consecutive S1 switching preparation failures corresponding to the second NCC value is less than seven times.

In a possible design, the sending unit 803 is further used to send a first NCC value to the first base station, so that the first base station sends a first NCC value to the communication device, and the first NCC value corresponds to successful S1 switching preparation.

For the beneficial effects of the various designs of the management devices described above in the present application, please refer to the beneficial effects of the various corresponding implementation methods in the method embodiments in Figures 3, 4 and 5 above, and the details will not be repeated here.

It should be noted that the information interaction, execution process, etc. between the modules/units in the management device of the embodiment corresponding to Figure 8 are based on the same concept as the method embodiment corresponding to Figure 3 in the present application. For specific contents, please refer to the description in the method embodiment shown in the previous part of the present application, and will not be repeated here.

In addition, each functional module or unit in each embodiment of the present application may be integrated into one processor, or may exist physically separately, or two or more modules or units may be integrated into one module or unit. The above-mentioned integrated modules or units may be implemented in the form of hardware or in the form of software functional modules.

Next, another communication device provided in an embodiment of the present application is introduced. Please refer to FIG. 9. FIG. 9 is a communication device provided in an embodiment of the present application. Another structural schematic diagram of the device is shown in FIG. 6 , FIG. 7 , or FIG. 8 , where the communication device 900 may be a communication device, a base station, or a management device of the corresponding embodiment in FIG. 6 , FIG. 7 , or FIG. 8 , and is used to implement the functions of the communication device, base station, or management device in FIG. 6 , FIG. 7 , or FIG. 8 . Specifically, the communication device 900 is implemented by one or more servers, and the communication device 900 may have relatively large differences due to different configurations or performances, and may include one or more central processing units (CPU) 922 (for example, one or more central processing units) and a memory 932, and one or more storage media 930 (for example, one or more storage devices). Among them, the memory 932 and the storage medium 930 may be temporary storage or permanent storage. The program stored in the storage medium 930 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations in the communication device 900. Furthermore, the central processing unit 922 may be configured to communicate with the storage medium 930, and execute a series of instruction operations in the storage medium 930 on the communication device 900.

The communication device 900 may also include one or more power supplies 926 , one or more wired or wireless network interfaces 950 , and/or one or more input/output interfaces 958 .

In the embodiment of the present application, the central processor 922 is used to execute the method executed by the communication device in the embodiment corresponding to Figure 3. For example, the central processor 922 can be used to: send a first message to the first base station, wherein the first message is used to instruct the communication device to access the second base station and the management device, wherein the first base station is a base station accessing the communication device, and the second base station is a base station supporting the communication device to access, and receive the target NCC value sent by the first base station, the target NCC value is obtained by the management device after seven consecutive failures in performing S1 switching preparation, and the S1 switching preparation is performed by the management device based on the switching request message sent by the first base station, the switching request message is sent by the first base station based on the first message, and then the same key as the management device is obtained based on the target NCC value. In this way, the problem that the UE side cannot perceive the NCC value flip can be solved, and the keys on the UE side and the core network side are the same in real time, so as to ensure that when the UE side sends an uplink packet, the PDCD integrity check is successful, and the switching process is successfully executed and the communication is normal.

Alternatively, in an embodiment of the present application, the central processor 922 is used to execute the method executed by the first base station in the embodiment corresponding to Figure 3. For example, the central processor 922 can be used to: receive a first message sent by a communication device, wherein the first message is used to instruct the communication device to access the second base station and the management device, and then send a switching request message to the management device based on the first message, wherein the switching request message is used to instruct the first base station to initiate S1 switching, and receive a second message sent by the management device carrying a target NCC value, wherein the target NCC value is obtained by the management device failing to perform S1 switching preparation seven times in a row, and send the target NCC value to the communication device based on the second message, so that the communication device obtains the same key as the management device based on the target NCC value. In this way, the problem that the UE side cannot perceive the NCC value flip can be solved, and the keys on the UE side and the core network side can be ensured to be the same in real time, thereby ensuring that when the UE side sends an uplink packet, the PDCD integrity check is successful, ensuring that the switching process is successfully executed, and the communication is normal.

Alternatively, in an embodiment of the present application, the central processor 922 is used to execute the method executed by the management device in the embodiment corresponding to Figure 3. For example, the central processor 922 can be used to: receive a switching request message sent by the first base station based on the first message, and perform S1 switching preparation based on the switching request message, and determine the target NCC value when the S1 switching preparation fails seven times in a row, and send a second message carrying the target NCC value to the first base station, so that the first base station sends the target NCC value to the communication device based on the second message. In this way, the problem that the UE side cannot perceive the flipping of the NCC value can be solved, and the keys of the UE side and the core network side are the same in real time, so as to ensure that when the UE side sends an uplink packet, the PDCD integrity check is successful, and the switching process is successfully executed and the communication is normal.

Another communication device provided in an embodiment of the present application includes a processor, which is coupled to a memory, the memory stores instructions, and the processor is used to execute the instructions so that the communication device executes any one of the implementation methods shown in the aforementioned method embodiments.

An embodiment of the present application also provides a computer-readable storage medium, including computer-readable instructions. When the computer-readable instructions are executed on a computer, the computer executes any one of the implementation methods shown in the aforementioned method embodiments.

The embodiments of the present application also provide a computer program product, which includes a computer program or instructions. When the computer program or instructions are executed on a computer, the computer executes any one of the implementation methods shown in the aforementioned method embodiments.

The present application also provides a chip or chip system, which may include a processor. The chip may also include a memory (or storage module) and/or a transceiver (or communication module), or the chip is coupled to a memory (or storage module) and/or a transceiver (or communication module), wherein the transceiver (or communication module) can be used to support the chip for wired and/or wireless communication, and the memory (or storage module) can be used to store a program or a set of instructions, and the processor calls the program or the set of instructions to implement the above method embodiment, the operation performed by the terminal or the communication device in any possible implementation of the method embodiment. The chip system may include the above chip, and may also include the above chip and other separate devices, such as a memory (or storage module) and/or a transceiver (or communication module).

It should be noted that the above-described device embodiments are merely illustrative, and the units described as separate components may be Or they may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, in the drawings of the device embodiments provided by the present application, the connection relationship between the modules indicates that there is a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines.

Through the description of the above implementation methods, the technicians in the relevant field can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course, it can also be implemented by special hardware including special integrated circuits, special CPUs, special memories, special components, etc. In general, all functions completed by computer programs can be easily implemented by corresponding hardware, and the specific hardware structures used to implement the same function can also be various, such as analog circuits, digital circuits or special circuits. However, for the present application, software program implementation is a better implementation method in more cases. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer floppy disk, a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a training device, or a communication device, etc.) to execute the methods of each embodiment of the present application.

In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented 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 process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, a computer, a training device or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, training device or data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a training device, a data center, etc. that includes one or more available media integration. The available medium can be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a solid state drive (solid state drive, SSD)), etc.

Claims (27)

1. A method for accessing a network, characterized in that it is performed by a base station, and the method comprises:

   The first base station receives a first message sent by a communication device, where the first message is used to instruct the communication device to access a second base station and a management device, where the second base station is a base station that supports access by the communication device;

   The first base station sends a handover request message to the management device based on the first message, where the handover request message is used to instruct the first base station to initiate an S1 handover;

   The first base station receives a second message sent by the management device and carrying a target next hop chain calculation NCC value, where the target NCC value is obtained by the management device executing the S1 handover preparation failure seven times in a row;

   The first base station sends the target NCC value to the communication device based on the second message, so that the communication device obtains the same key as the management device based on the target NCC value.
2. The method according to claim 1, wherein the second message is used to indicate that the current S1 handover preparation fails, and the first base station sends the target NCC value to the communication device, comprising:

   The first base station determines that the S1 handover preparation failure indicated by the second message is the seventh consecutive S1 handover preparation failure;

   The first base station sends a radio resource control connection reconfiguration message to the communication device based on the target information, and the radio resource control connection reconfiguration message carries the target NCC value.
3. The method according to claim 2 is characterized in that the target information belongs to a protocol field in protocol 33.401 or protocol 36.413.
4. The method according to claim 2 or 3 is characterized in that before the first base station receives the second message carrying the target NCC value sent by the management device, the method further comprises:

   The first base station receives a third message carrying a second NCC value sent by the management device, and the second NCC value corresponds to a number of consecutive failures of the S1 handover preparation that is less than seven times.
5. The method according to claim 1 is characterized in that the second message is sent by the management device after determining that the S1 switching preparation has failed seven times in a row.
6. The method according to any one of claims 1 to 5, characterized in that after the first base station sends the target NCC value to the communication device, the method further comprises:

   The first base station receives a first NCC value sent by the management device, the first NCC value corresponding to the successful S1 handover preparation;

   The first base station sends the first NCC value to the communication device, so that the communication device acquires the same key as the management device based on the first NCC value.
7. A method for accessing a network, characterized in that it is performed by a management device, and the method comprises:

   The management device receives a handover request message sent by the first base station based on a first message, wherein the handover request message is used to instruct the first base station to initiate an S1 handover, the first message is used to instruct the communication device to access the second base station and the management device, the first base station is a base station to access the communication device, and the second base station is a base station supporting access by the communication device;

   The management device performs S1 handover preparation based on the handover request message;

   In the case where the S1 handover preparation fails seven times in succession, the management device determines a target NCC value;

   The management device sends a second message carrying the target NCC value to the first base station, so that the first base station sends the target NCC value to the communication device based on the second message.
8. The method according to claim 7, wherein the second message is used to indicate that the current S1 handover preparation fails, and before the management device determines the target NCC value, the method further comprises:

   The management device sends a third message carrying a second NCC value to the first base station, and the second NCC value corresponds to a number of consecutive failures of the S1 handover preparation that is less than seven times.
9. The method according to claim 7 or 8, characterized in that after the management device sends a second message carrying the target NCC value to the first base station, the method further comprises:

   The management device sends the first NCC value to the first base station, so that the first base station sends the first NCC value to the communication device, and the first NCC value corresponds to the success of the S1 handover preparation.
10. A method for accessing a network, characterized in that it is performed by a communication device, and the method comprises:

    The communication device sends a first message to the first base station, where the first message is used to instruct the communication device to access the second base station and the management device, where the first base station is a base station accessed by the communication device, and the second base station is a base station supporting access by the communication device;

    The communication device receives a target NCC value sent by the first base station, the target NCC value being obtained by the management device failing to perform the S1 handover preparation seven times in a row, the S1 handover preparation being performed by the management device based on a handover request message sent by the first base station, the handover request message being sent by the first base station based on the first message;

    The communication device acquires the same key as that of the management device based on the target NCC value.
11. The method according to claim 10, wherein the communication device receives the target NCC value sent by the first base station comprises:

    The communication device receives a radio resource control connection reconfiguration message sent by the first base station, where the radio resource control connection reconfiguration message carries the target NCC.
12. The method according to claim 10 or 11, characterized in that after the communication device receives the target NCC value sent by the first base station, the method further comprises:

    The communication device receives a first NCC value sent by the first base station, the first NCC value corresponding to the successful S1 handover preparation;

    The communication device acquires the same key as that of the management device based on the first NCC value.
13. A base station, characterized by comprising:

    A receiving unit, configured to receive a first message sent by a communication device, wherein the first message is used to instruct the communication device to access a second base station and a management device, wherein the second base station is a base station that supports access by the communication device;

    a sending unit, configured to send a handover request message to the management device based on the first message, wherein the handover request message is used to instruct the base station to initiate an S1 handover;

    The receiving unit is further configured to receive a second message carrying a target NCC value sent by the management device, where the target NCC value is obtained by the management device failing to execute the S1 handover preparation for seven consecutive times;

    The sending unit is further configured to send the target NCC value to the communication device, so that the communication device obtains the same key as the management device based on the target NCC value.
14. The base station according to claim 13, characterized in that the second message is used to indicate that the current S1 handover preparation fails, and the base station further comprises a processing unit:

    The processing unit is configured to determine that the S1 handover preparation failure indicated by the second message is the seventh consecutive S1 handover preparation failure;

    The sending unit is specifically configured to send a radio resource control connection reconfiguration message to the communication device based on the target information, wherein the radio resource control connection reconfiguration message carries the target NCC value.
15. The base station according to claim 14 is characterized in that the target information belongs to a protocol field in protocol 33.401 or protocol 36.413.
16. The base station according to claim 14 or 15, characterized in that before receiving the second message carrying the target NCC value sent by the management device,

    The receiving unit is further configured to receive a third message carrying a second NCC value sent by the management device, wherein the number of consecutive S1 switching preparation failures corresponding to the second NCC value is less than seven.
17. The base station according to claim 13 is characterized in that the second message is sent by the management device after determining that the S1 switching preparation has failed seven times in a row.
18. The base station according to any one of claims 13 to 17, characterized in that the receiving unit is further used to receive a first NCC value sent by the management device, the first NCC value corresponding to the S1 handover preparation being successful;

    The sending unit is further configured to send the first NCC value to the communication device, so that the communication device obtains the same key as the management device based on the first NCC value.
19. A management device, characterized in that the management device comprises:

    a receiving unit, configured to receive a handover request message sent by a first base station based on a first message, wherein the handover request message is used to instruct the first base station to initiate an S1 handover, wherein the first message is used to instruct a communication device to access a second base station and the management device, wherein the first base station is a base station for accessing the communication device, and the second base station is a base station supporting access by the communication device;

    a processing unit, configured to perform S1 handover preparation based on the handover request message;

    The processing unit is further used to determine a target NCC value when the S1 handover preparation fails seven times in a row;

    A sending unit is used to send a second message carrying the target NCC value to the first base station, so that the first base station sends the target NCC value to the communication device based on the second message.
20. The management device according to claim 19, wherein the second message is used to indicate that the current S1 handover preparation fails, before the management device determines the target NCC value.

    The sending unit is further configured to send a third message carrying a second NCC value to the first base station, wherein the number of consecutive S1 handover preparation failures corresponding to the second NCC value is less than seven.
21. The management device according to claim 19 or 20 is characterized in that the sending unit is further used to send the first NCC value to the first base station, so that the first base station sends the first NCC value to the communication device, and the first NCC value corresponds to the successful S1 switching preparation.
22. A communication device, characterized in that the communication device comprises:

    A sending unit, configured to send a first message to a first base station, wherein the first message is used to instruct the communication device to access a second base station and a management device, the first base station is a base station accessed by the communication device, and the second base station is a base station supporting access by the communication device;

    a receiving unit, configured to receive a target NCC value sent by the first base station, the target NCC value being obtained by the management device failing to execute the S1 handover preparation seven times in a row, the S1 handover preparation being executed by the management device based on a handover request message sent by the first base station, the handover request message being sent by the first base station based on the first message;

    A processing unit is used to obtain the same key as the management device based on the target NCC value.
23. The communication device according to claim 22 is characterized in that the receiving unit is specifically used to receive a wireless resource control connection reconfiguration message sent by the first base station, and the wireless resource control connection reconfiguration message carries the target NCC.
24. The communication device according to claim 22 or 23, characterized in that the receiving unit is further used to receive a first NCC value sent by the first base station, the first NCC value corresponding to the success of the S1 handover preparation;

    The processing unit is further configured to obtain a key identical to that of the management device based on the first NCC value.
25. A communication device, characterized by a processor, wherein the processor is coupled to a memory, the memory stores instructions, and the processor is used to execute the instructions, so that the communication device executes the method described in any one of claims 1 to 12.
26. A computer-readable storage medium comprises computer-readable instructions, wherein when the computer-readable instructions are executed on a computer, the method according to any one of claims 1 to 12 is executed.
27. A computer program product comprises computer-readable instructions, wherein when the computer-readable instructions are run on a computer, the method according to any one of claims 1 to 12 is executed.