CN113316151B

CN113316151B - Communication method, device and equipment

Info

Publication number: CN113316151B
Application number: CN202110627445.2A
Authority: CN
Inventors: 陈伟; 金逸
Original assignee: Spreadtrum Communications Shanghai Co Ltd
Current assignee: Spreadtrum Communications Shanghai Co Ltd
Priority date: 2021-06-04
Filing date: 2021-06-04
Publication date: 2023-10-20
Anticipated expiration: 2041-06-04
Also published as: CN113316151A

Abstract

The application provides a communication method, a device and equipment, wherein the method comprises the following steps: when the terminal equipment performs network registration in the first access mode, a first message is sent to the first network equipment, the first message comprises a first SUCI, the terminal equipment receives a first GUTI corresponding to the first SUCI sent by the first network equipment, and when the terminal equipment performs network registration in the second access mode, the terminal equipment can perform network registration through the first GUTI or perform network registration through the first SUCI, so that the SUCI does not need to be generated by adopting an encryption algorithm again, the frequency of SUCI generation is reduced, and the consumption of computing resources of the terminal equipment is reduced.

Description

Communication method, device and equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a communications method, apparatus, and device.

Background

The terminal device may be registered in the network through a plurality of access modes. For example, registration into the network may be through third generation partnership project (3rd generation partnership project,3GPP) access technologies, and may also be through non-3 GPP access technologies.

The fifth generation mobile communication technology (5th generation mobile communication technology,5G) further improves the security of the international mobile subscriber identity (international mobile subscriber identity, IMSI) and does not allow the plaintext of the IMSI to be transferred over the air. Therefore, in the network registration process of the terminal device, when the IMSI needs to be sent, the terminal device may encrypt the IMSI by using a preset encryption algorithm to generate a user hidden identifier (subscription concealed identifier, sui), so that the terminal device may perform network registration through sui.

In the scene that the terminal equipment performs network registration through multiple access modes, when the terminal equipment performs network registration through each access mode, SUCI is required to be generated through an encryption algorithm, and the encryption algorithm is complex in operation, so that more computing resources of the terminal equipment are required to be consumed.

Disclosure of Invention

The application provides a communication method, a device and equipment, which are used for reducing the consumption of computing resources of terminal equipment.

In a first aspect, the present application provides a communication method comprising:

when network registration is carried out in a first access mode, a first message is sent to first network equipment, wherein the first message comprises a first user hidden identifier SUCI;

receiving a first global unique temporary terminal identifier GUTI corresponding to the first SUCI and sent by the first network equipment;

and when network registration is performed through a second access mode, performing network registration through the first GUTI or the first SUCI.

In a possible implementation manner, when performing network registration through the second access manner, performing network registration through the first GUTI or the first sui includes:

when network registration is carried out in the second access mode, a first network identifier of a network registered in the first access mode and a second network identifier of a network to be registered in the second access mode are obtained;

And carrying out network registration through the first GUTI or the first SUCI according to the first network identifier and the second network identifier.

In a possible implementation manner, according to the first network identifier and the second network identifier, performing network registration through the first GUTI or the first sui, including:

if the first network identifier is the same as the second network identifier, network registration is performed through the first GUTI;

and if the first network identifier is different from the second network identifier, performing network registration through the first SUCI.

In a possible implementation manner, the network registration through the first GUTI includes:

sending a first registration request message to second network equipment, wherein the first registration request message comprises the first GUTI;

and receiving a registration acceptance message sent by the second network equipment.

In a possible implementation manner, the network registration through the first sui includes:

sending a second registration request message to a second network device, wherein the second registration request message comprises the first SUCI;

receiving a second GUTI corresponding to the first sui sent by the second network device;

And sending a registration completion message to the second network equipment according to the second GUTI.

receiving a first identity request message sent by a second network device, where the first identity request message is used to request to obtain a SUCI corresponding to the second access mode;

and sending a first identity response message to the second network device, wherein the first identity response message comprises the first SUCI.

In a possible implementation manner, after the first message is sent to the first network device, the method further includes:

and starting a timer corresponding to the first SUCI.

In a possible implementation manner, the first network identifier and the second network identifier are the same; after receiving the first GUTI corresponding to the first suli sent by the first network device, the method further includes:

and stopping the timer corresponding to the first SUCI.

In a possible implementation manner, the first network identifier and the second network identifier are different; after network registration through the first sui, the method further includes:

and stopping the timer corresponding to the first SUCI.

In one possible implementation, sending a first message to a first network device includes:

Sending a third registration request message to the first network device; or alternatively, the process may be performed,

and sending a second identity response message to the first network device, wherein the second identity response message is a response message corresponding to a second identity request message, and the second identity request message is used for requesting to acquire the SUCI corresponding to the first access mode.

In a possible implementation manner, the first access manner is a 3GPP access manner, and the second access manner is a non-3 GPP access manner; or alternatively, the process may be performed,

the first access mode is a non-3 GPP access mode, and the second access mode is a 3GPP access mode.

In a second aspect, the present application provides a communication apparatus comprising:

the network registration module is used for receiving a first message from the first network equipment when the network registration is performed in a first access mode, wherein the first message comprises a first user hidden identifier SUCI;

the receiving module is used for receiving a first global unique temporary terminal identifier GUTI corresponding to the first SUCI sent by the first network equipment;

and the processing module is used for carrying out network registration through the first GUTI or the first SUCI when carrying out network registration through the second access mode.

In a possible implementation manner, the processing module is specifically configured to:

controlling the sending module to send a first registration request message to second network equipment, wherein the first registration request message comprises the first GUTI;

and controlling the receiving module to receive the registration acceptance message sent by the second network equipment.

Controlling the sending module to send a second registration request message to second network equipment, wherein the second registration request message comprises the first SUCI;

controlling the receiving module to receive a second GUTI corresponding to the first sui sent by the second network device;

and controlling the sending module to send a registration completion message to the second network equipment according to the second GUTI.

controlling the receiving module to receive a first identity request message sent by a second network device, where the first identity request message is used to request to obtain a SUCI corresponding to the second access mode;

and controlling the sending module to send a first identity response message to the second network equipment, wherein the first identity response message comprises the first SUCI.

In a possible implementation manner, the processing module is further configured to:

and after the first message is sent to the first network equipment, starting a timer corresponding to the first SUCI.

In a possible implementation manner, the first network identifier and the second network identifier are the same; the processing module is further configured to:

and stopping the timer corresponding to the first SUCI after receiving the first GUTI corresponding to the first SUCI sent by the first network equipment.

and stopping the timer corresponding to the first SUCI after the network registration is carried out through the first SUCI.

In a possible implementation manner, the sending module is specifically configured to:

In a third aspect, the present application provides a terminal device, including: a transceiver, a processor, a memory;

the memory stores computer-executable instructions that when executed by the processor implement the method of any of the first aspects.

In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, implement the method of any of the first aspects.

In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the method according to any of the first aspects.

Drawings

In order to more clearly illustrate the embodiments of the application or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, it being obvious that the drawings in the description below are only some embodiments of the application, and that other drawings can be obtained according to these drawings without inventive faculty for a person skilled in the art.

Fig. 1 is a schematic diagram of a communication system to which an embodiment of the present application is applicable;

fig. 2 is a schematic flow chart of a communication method according to an embodiment of the present application;

fig. 3 is a flow chart of another communication method according to an embodiment of the present application;

fig. 4 is a flow chart of another communication method according to an embodiment of the present application;

fig. 5 is a flow chart of another communication method according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Fig. 1 is a schematic diagram of a communication system to which an embodiment of the present application is applied, and in the communication system shown in fig. 1, an example of the communication system 100 includes a network device 110 and two terminal devices 120 is described. It will be appreciated that the communication system 100 may include a plurality of network devices and that each network device may include other numbers of terminal devices within its coverage area, as embodiments of the present application are not limited in this respect.

The network device 110 may be a device that communicates with the terminal device 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area.

The communication system 100 may be a global system for mobile communications (global system of mobile communication, GSM) system, a code division multiple access (code division multiple access, CDMA) system, a wideband code division multiple access (wideband code division multiple access, WCDMA) system, a general packet Radio service (general packet Radio service, GPRS), a long term evolution (long term evolution, LTE) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, TDD) system, a long term evolution advanced (advanced long term evolution, LTE-a) system, a New Radio (NR) system, an evolution system of the NR system, an LTE-based access to unlicensed spectrum on an unlicensed frequency band, an LTE-based access to unlicensed spectrum on an LTE-U system, an NR-based access to unlicensed spectrum on an unlicensed frequency band, a universal mobile telecommunication system (universal mobile telecommunication system, UMTS), a worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX) communication system, a wireless local area network (wireless local area networks, WLAN), a wireless fidelity (wireless fidelity, wiFi), a next-generation communication system, or other communication system, etc.

Alternatively, the NR system may also be referred to as a 5G system or 5G network.

Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, as the communication technology advances, the mobile communication system will support not only conventional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (machine to machine, M2M) communication, machine type communication (machine type communication, MTC), inter-vehicle (vehicle to vehicle, V2V) communication, and the like, to which the embodiments of the present application can also be applied.

Alternatively, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

When the communication system is AN NR system, the network device 110 may be a (radio) access network (radio access network, (R) AN) device in the NR system, and the (R) AN device in the NR system may be: an access network of non-3 GPP such as an Access Point (AP) of a WiFi network, a next generation base station (which may be collectively referred to as a new generation radio access network node (NG-RAN node), wherein the next generation base station includes a new air interface base station (NR node b, gNB), a new generation evolved base station (NG-eNB), a Central Unit (CU), and a Distributed Unit (DU) in a separated form gNB, etc.), a new radio controller (new radio controller, NR controller), a remote radio module, a micro base station, a relay (relay), a transceiver point (transmission receive point, TRP), a transmission point (transmission point, TP), or other nodes.

The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the network equipment. For convenience of description, in all embodiments of the present application, the above-mentioned apparatus for providing a wireless communication function for a terminal device is referred to as a network device.

In the embodiment of the present application, the terminal device 120 may be any terminal, for example, the terminal device 120 may be a user device for machine type communication. The terminal device 120 may also be referred to as a User Equipment (UE), a Mobile Station (MS), a mobile terminal (mobile terminal), a terminal (terminal), etc.

The terminal device 120 may communicate with one or more core networks via the RAN, and thus the terminal device 120 may also be referred to as a wireless terminal, which may be a device that provides voice and/or data connectivity to a user, a handheld device with wireless connectivity, or other processing device connected to a wireless modem.

For example, the terminal device 120 may be a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device or a wearable device, a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in telemedicine (remote media), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), or the like. The embodiment of the application is not particularly limited.

As another example, terminal device 120 includes, but is not limited to, a connection via a wireline, such as via a public-switched telephone network (public switched telephone networks, PSTN), a digital subscriber line (digital subscriber line, DSL), a digital cable, a direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., for a cellular network, a wireless local area network (wireless local area network, WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and/or means of the other terminal device arranged to receive/transmit communication signals; and/or internet of things (internet of things, ioT) devices. Terminal devices arranged to communicate over a wireless interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals". Examples of mobile terminals include, but are not limited to, satellites or cellular telephones; a personal communications system (personal communications system, PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, internet/intranet access, web browser, organizer, calendar, and/or a global positioning system (global positioning system, GPS) receiver; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver.

Alternatively, the network device 110 and the terminal device 120 may be deployed on land, including indoors or outdoors, hand-held or vehicle-mounted; the device can be deployed on the water surface; but also on aerial planes, balloons and satellites. The embodiment of the present application does not limit the application scenarios of the network device 110 and the terminal device 120.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited by the embodiment of the present application.

It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions, where the network device 110 and the terminal device 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

When the terminal device performs network registration through the sui, the terminal device needs to transmit the sui to the network device in the following several scenarios.

Scene 1: when the terminal device needs to send a registration request message (REGISTRATION REQUEST message) to the network device, the terminal device has no valid globally unique temporary terminal identity (globally unique temporary UE identity, GUTI).

Scene 2: when the terminal device needs to send a logoff request message (DEREGISTRATION REQUEST message) to the network device, the terminal device has no valid GUTI.

Scene 3: when the terminal device receives the identity request message (IDENTITY REQUEST message) sent by the network device, it needs to send an identity response message (IDENTITY RESPONSE message) to the network device, and the identity response message carries the sui.

The terminal device needs to generate the SUCI through an encryption algorithm every time the terminal device needs to send the SUCI to the network device. For example, an elliptic algorithm may be used to encrypt the IMSI to generate the sui. And the encryption algorithm is complex in operation, and frequent generation of the SUCI consumes more computing resources of the terminal equipment.

In some related art, in order to reduce consumption of computing resources of the terminal device, a timer may be used to manage the sui.

Specifically, when the terminal device generates a new sui and sends the sui to the network device, a timer is started. For example, a timer may be started in several scenarios:

(1) The terminal device generates a new SUCI and starts a timer when sending an identity response message (IDENTITY RESPONSE message) carrying the SUCI to the network device.

(2) The terminal device generates a new SUCI and starts a timer when sending a registration request message (REGISTRATION REQUEST message) carrying the SUCI to the network device.

(3) The terminal device generates a new SUCI and starts a timer when sending a cancellation request message (DEREGISTRATION REQUEST message) carrying the SUCI to the network device.

And stopping the timer when the terminal equipment receives the new GUTI allocated by the network equipment. For example, the timer may be stopped in several scenarios:

(1) The terminal device receives a registration accept message (REGISTRATION ACCEPT message) sent by the network device, where the message carries a new GUTI allocated by the network device to the terminal device, and stops the timer.

(2) The terminal device receives a configuration update command message (CONFIGURATION UPDATE COMMAND message) sent by the network device, where the message carries a new GUTI allocated by the network device to the terminal device, and stops the timer.

(3) The terminal device receives a logout accept message (DEREGISTRATION ACCEPT message) sent by the network device and stops the timer.

And deleting the SUCI generated last time after the timer is overtime. The next time the terminal device needs to send a SUCI to the network device, the SUCI is regenerated again and the timer is restarted.

Alternatively, the timer may be a T3519 timer. Illustratively, the duration of the T3519 timer may be 60 seconds.

By employing a timer to manage the SUCI, when a new SUCI is generated and sent to the network device, the timer is started, and during the timer running, if the terminal device needs to send the SUCI to the network device again, the latest generated SUCI is used. In this way, the number of times the terminal device generates the SUCI can be reduced, thereby reducing the consumption of computing resources of the terminal device to a certain extent.

In some application scenarios, the terminal device may register to the network through multiple access modes. For example, registration into the network may be through third generation partnership project (3rd generation partnership project,3GPP) access technologies, and may also be through non-3 GPP access technologies. Non-3 GPP access technologies include, but are not limited to: wireless local area network (wireless local area network, WLAN), wireless fidelity network (Wireless Fidelity, wi-Fi), etc.

In a scenario in which the terminal device supports multiple access modes to perform network registration, the terminal device manages the generation of the sui for each access mode respectively. That is, a set of flows for generating and managing the sui is maintained for each access mode.

For example, when network registration is performed in the first access manner, the terminal device generates a first sui, and sends a registration request message to the first network device, where the registration request message carries the first sui. The terminal equipment starts a first timer, and manages the first SUCI by using the first timer. Specifically, after receiving a registration acceptance message carrying a first GUTI sent by a first network device, the terminal device sends a registration completion message to the first network device, and stops the first timer. After the first timer expires, the terminal device deletes the first GUTI.

When network registration is performed in the second access mode, the terminal equipment generates a second SUCI, and sends a registration request message to the second network equipment, wherein the registration request message carries the second SUCI. The terminal device starts a second timer, and manages a second SUCI by using the second timer. Specifically, after the terminal device receives the registration acceptance message carrying the second GUTI sent by the second network device, the terminal device sends a registration completion message to the second network device, and stops the second timer. After the second timer expires, the terminal device deletes the second GUTI.

In the network registration scenario of the terminal device through multiple access modes, the terminal device needs to generate the sui through the encryption algorithm when registering the network through each access mode, and still consumes more computing resources of the terminal device.

In order to solve the technical problems, the embodiment of the application provides a communication method, a device and equipment. In the technical scheme of the application, in the scene that the terminal equipment performs network registration through multiple access modes, SUCI generation and management can be uniformly performed aiming at the terminal equipment with multiple access modes, that is, multiple access modes can share one set of SUCI generation and management flow, thereby further reducing the frequency of SUCI generation and reducing the consumption of computing resources of the terminal equipment. In addition, the code can be simplified, and the maintainability of the code is improved.

The technical scheme of the application is described in detail below by specific examples. The following embodiments may be combined with each other, and some embodiments may not be repeated for the same or similar concepts or processes.

Fig. 2 is a flow chart of a communication method according to an embodiment of the present application. The method of the present embodiment may be performed by a terminal device. As shown in fig. 2, the method of the present embodiment includes:

S201: and when the network registration is performed in the first access mode, a first message is sent to the first network equipment, wherein the first message comprises a first SUCI.

Specifically, when the terminal device performs network registration in a first access manner, and when the SUCI needs to be sent to the first network device, the terminal device generates a first SUCI by adopting a preset encryption algorithm, and sends a first message to the first network device, wherein the first message comprises the first SUCI. The first network device is a network device accessed by the terminal device through a first access mode.

Wherein the first message is a message for carrying a first sui. Alternatively, the first message may be any one of the following messages: a registration request message (REGISTRATION REQUEST message), an identity response message (IDENTITY RESPONSE message), a deregistration request message (DEREGISTRATION REQUEST message).

S202: and receiving a first GUTI corresponding to the first SUCI and sent by the first network equipment.

Specifically, after receiving the first SUCI, the first network device allocates a first GUTI to the terminal device according to the first SUCI, and sends the first GUTI carried in the air interface message to the terminal device. Thus, the terminal device receives the first GUTI.

Optionally, the terminal device receives a registration accept message (REGISTRATION ACCEPT message) sent by the first network device, where the message includes a first GUTI corresponding to the first sui.

Optionally, the terminal device receives a configuration update command message (CONFIGURATION UPDATE COMMAND message) sent by the first network device, where the message includes a first GUTI corresponding to the first sui.

Optionally, the terminal device receives a logout accept message (DEREGISTRATION ACCEPT message) sent by the first network device, where the message includes a first GUTI corresponding to the first sui.

S203: and when network registration is performed through a second access mode, performing network registration through the first GUTI or the first SUCI.

In this embodiment, when network registration is performed by the second access method, network registration is performed by the first GUTI or the first sui, which may include any one of the following scenarios:

scene 1: when a registration request message (REGISTRATION REQUEST message) needs to be sent to the second network device during network registration in the second access mode, the registration request message carries the first GUTI or the first sui.

Scene 2: when a logout request message (DEREGISTRATION REQUEST message) needs to be sent to the second network device during network registration in the second access mode, the logout request message carries the first GUTI or the first sui.

Scene 3: when the identity response message (IDENTITY RESPONSE message) needs to be sent to the second network device during network registration in the second access mode, the identity response message carries the first SUCI.

In the above scenarios, the second network device is a network device to which the terminal device is connected through a second access mode.

In this embodiment, when the terminal device performs network registration in the second access manner, the terminal device may perform network registration through the first GUTI, or perform network registration through the first sui, so that it is not necessary to generate the sui by adopting the encryption algorithm again, the number of times of generating the sui is reduced, and the consumption of computing resources of the terminal device is reduced.

In a possible implementation manner, when network registration is performed in the second access manner, the terminal device may acquire a first network identifier registered in the first access manner and a second network identifier of a network to be registered in the second access manner, and further perform network registration through the first GUTI or the first sui according to the first network device and the second network identifier.

In this embodiment, the network identifier is used to indicate the network accessed by the terminal device. The network identity may be, for example, an identity of a PLMN to which the terminal device has access.

Optionally, if the first network label and the second network identifier are the same, that is, the terminal device registers to the same PLMN through the first access mode and the second access mode, the terminal device may perform network registration through the first GUTI when performing network registration through the second access mode.

For example, the terminal device performs network registration through the first GUTI, which may include case 1 or case 2 described below.

Case 1: the terminal device sends a first registration request message to the second network device, wherein the first registration request message comprises a first GUTI.

Case 2: the terminal device sends a first logout request message to the second network device, wherein the first logout request message comprises a first GUTI.

Optionally, if the first network identifier and the second network identifier are different, that is, the terminal device registers to different PLMNs through the first access manner and the second access manner, the terminal device may perform network registration through the first sui when performing network registration through the second access manner.

The network registration of the terminal device by the first sui may include any one of the following cases 1 to 3:

case 1: the terminal equipment sends a second registration request message to the second network equipment, wherein the second registration request message comprises a first SUCI, receives a second GUTI corresponding to the first SUCI and sent by the second network equipment, and sends a registration completion message to the second network equipment according to the second GUTI.

Case 2: the terminal device sends a second logout request message to the second network device, where the second logout request message includes the first SUCI.

Case 3: the terminal equipment receives a first identity request message sent by the second network equipment, wherein the first identity request message is used for requesting to acquire SUCI corresponding to the second access mode. The terminal device sends a first identity response message to the second network device, wherein the first identity response message comprises a first SUCI.

It should be noted that, in this embodiment, a scenario in which the terminal device performs network registration through two access modes is taken as an example to describe the embodiment, and when the terminal device performs network registration through more access modes, the implementation principle is similar, and this embodiment is not illustrated.

Optionally, the first access mode is a 3GPP access mode, and the second access mode is a non-3 GPP access mode.

Optionally, the first access mode is a non-3 GPP access mode, and the second access mode is a 3GPP access mode.

The communication method provided in this embodiment includes: when the terminal equipment performs network registration in the first access mode, a first message is sent to the first network equipment, the first message comprises a first SUCI, the terminal equipment receives a first GUTI corresponding to the first SUCI sent by the first network equipment, and when the terminal equipment performs network registration in the second access mode, the terminal equipment can perform network registration through the first GUTI or perform network registration through the first SUCI, so that the SUCI does not need to be generated by adopting an encryption algorithm again, the frequency of SUCI generation is reduced, and the consumption of computing resources of the terminal equipment is reduced.

On the basis of the embodiment, when the terminal equipment performs network registration through multiple access modes, the same timer can be adopted to manage the SUCI aiming at the multiple access modes, so that the frequency of generating the SUCI is further reduced, and the consumption of computing resources of the terminal equipment is reduced. The following detailed description is provided in connection with several specific embodiments. In the following several embodiments, two access manners of 3GPP and non-3 GPP are exemplified.

In a possible application scenario, the terminal device registers to the same PLMN through both 3GPP and non-3 GPP access modes. In this scenario, the terminal device may only maintain one GUTI for both access modes. That is, as long as a valid GUTI is acquired in one access mode, the GUTI is also used in another access mode.

For the initial registration flow, after successful registration by the SUCI in one access mode and effective GUTI is allocated, when the registration flow is reinitiated by another access mode, the registration by the SUCI is not needed, but the registration by the GUTI is performed. Therefore, when the single timer is used for managing the SUCI, the timer is started only when any access mode is registered through the SUCI. And stopping the timer when receiving the effective GUTI in any access mode registration process.

For the identity inquiry flow, after any access mode is successfully registered, the two access modes are distributed to the effective GUTI, the network equipment can inquire the IMSI through the GUTI, and the SUCI of the terminal equipment is generally not required to be inquired through the identity inquiry flow.

It can be seen that, after network registration is performed in one access mode through the sui, the other access mode also obtains an effective GUTI at the same time, and network registration is not performed in the other access mode through the sui. Thus, in a scenario where two access methods are registered to the same PLMN, both access methods may share one timer to manage the generation of the sui.

Specifically, the management flow of the timer is as follows:

and the terminal equipment generates a new SUCI in any access mode, and starts a timer when the SUCI is sent to the network equipment. For example, the timer may be started in any one of several scenarios:

(1) The terminal equipment generates a new SUCI under the 3GPP or non-3 GPP access mode, and starts a timer when an identity response message (IDENTITY RESPONSE message) carrying the SUCI is sent to the network equipment.

(2) The terminal equipment generates a new SUCI under the 3GPP or non-3 GPP access mode, and starts a timer when a registration request message (REGISTRATION REQUEST message) carrying the SUCI is sent to the network equipment.

(3) The terminal equipment generates a new SUCI under the 3GPP or non-3 GPP access mode, and starts a timer when sending a cancellation request message (DEREGISTRATION REQUEST message) carrying the SUCI to the network equipment.

And stopping the timer when the terminal equipment receives the new GUTI allocated to the terminal equipment by the network equipment in any access mode. For example, the timer may be stopped in several scenarios:

(1) The terminal equipment receives a registration acceptance message (REGISTRATION ACCEPT message) sent by the network equipment in a 3GPP or non-3 GPP access mode, wherein the message carries a new GUTI distributed by the network equipment for the terminal equipment, and stops the timer.

(2) The terminal equipment receives a configuration update command message (CONFIGURATION UPDATE COMMAND message) sent by the network equipment in a 3GPP or non-3 GPP access mode, wherein the message carries a new GUTI distributed by the network equipment for the terminal equipment, and stops the timer.

(3) The terminal device receives a cancellation acceptance message (DEREGISTRATION ACCEPT message) sent by the network device in the 3GPP or non-3 GPP access mode, and stops the timer.

And deleting the SUCI generated last time after the timer is overtime.

In the following, with reference to fig. 3, an example is described for a scenario in which a terminal device registers to the same PLMN through two access methods, i.e. 3GPP and non-3 GPP.

Fig. 3 is a flow chart of another communication method according to an embodiment of the present application. As shown in fig. 3, the method of the present embodiment includes:

s301: when network registration is performed through a 3GPP access mode, the terminal equipment generates a first SUCI.

S302: the terminal equipment sends a registration request message to the 3GPP access network equipment, and the 3GPP access network equipment forwards the registration request message to the core network equipment, wherein the registration request message comprises a first SUCI.

S303: the terminal equipment starts a timer corresponding to the first SUCI.

S304: the core network device sends a registration acceptance message to the 3GPP access network device, and the 3GPP access network device forwards the registration acceptance message to the terminal device, wherein the registration acceptance message comprises a first GUTI corresponding to the first SUCI.

For example, the core network device corresponding to the first PLMN allocates a first GUTI to the terminal device, sends a registration accept message carrying the first GUTI to the 3GPP access network device, and the 3GPP access network device forwards the registration accept message to the terminal device.

S305: the terminal equipment sends a registration completion message to the 3GPP access network equipment, and the 3GPP access network equipment forwards the registration completion message to the core network equipment.

S306: and the terminal equipment stops the timer corresponding to the first SUCI.

S307: when network registration is performed in a non-3 GPP access mode, the terminal equipment performs network registration through a first GUTI.

The terminal device sends a registration request message carrying the first GUTI to the non-3 GPP access network device, and the non-3 GPP access network device forwards the registration request message to the core network device.

Or the terminal equipment sends a cancellation request message carrying the first GUTI to the non-3 GPP access network equipment, and the non-3 GPP access network equipment forwards the cancellation request message to the core network equipment.

In this embodiment, when the terminal device registers to the same PLMN through two access modes of 3GPP and non-3 GPP, the same timer may be used to manage the generation of the sui, so that the two access modes may share a set of process for generating and managing the sui, so that the code is simplified, the maintainability of the code is improved, the number of times of generating the sui is reduced, and the consumption of computing resources of the terminal device is reduced.

In another possible application scenario, the terminal device registers to different PLMNs through two access modes, namely 3GPP and non-3 GPP. In the scene, the terminal equipment maintains the mutually independent GUTI under each access mode.

For the initial registration procedure, even if the terminal device has successfully registered through the sui in one access mode and obtained an effective GUTI, network registration through the sui is still required in another access mode. The duration of the normal network registration procedure in the access mode is generally not longer than 20-30 seconds, and since the duration of the timer for managing the sui is generally 60 seconds, if the initial registration procedures in the two access modes occur serially (i.e., the interval between the initial registration procedures in the two access modes is short), the two access modes can share one timer.

Under the condition that two access modes share one timer, the timer can be started when any one access mode carries out network registration through SUCI, and the timer is stopped when both access modes are successfully registered and the effective GUTI is acquired. Thus, when the initial registration process is initiated successively under the two access modes, the initial registration process initiated later can carry the SUCI generated in the initial registration process before, and the SUCI does not need to be generated again. Therefore, the frequency of SUCI generation is further reduced, and the consumption of computing resources of the terminal equipment is reduced.

If the initial registration processes in the two access modes do not occur in series (i.e., the interval between the initial registration processes in the two access modes is longer), a first SUCI can be generated and a timer can be started when network registration is performed through the SUCI in the first access mode; and stopping the timer when the first access mode registration successfully acquires the GUTI corresponding to the first SUCI. When network registration is carried out through SUCI in the second access mode, the second SUCI is generated again, and the timer is restarted; and stopping the timer when the second access mode is successfully registered and the GUTI corresponding to the second SUCI is acquired.

Specifically, the management flow of the timer is as follows:

Under the condition that initial registration flows under two access modes occur in series, the timer is not stopped when the first access mode is successful in registering through SUCI and acquiring effective GUTI, but is stopped when the second access mode is also successful in registering through SUCI and acquiring effective GUTI. For example, the timer may be stopped in several scenarios:

(1) The terminal equipment has effective GUTI in the 3GPP access mode, has no effective GUTI in the non-3 GPP access mode, and receives a registration acceptance message (REGISTRATION ACCEPT message) sent by the network equipment in the non-3 GPP access mode, wherein the message carries GUTI distributed by the network equipment for the terminal equipment, and stops the timer. Or alternatively, the process may be performed,

the terminal equipment has effective GUTI in a non-3 GPP access mode, has no effective GUTI in a 3GPP access mode, and receives a registration acceptance message (REGISTRATION ACCEPT message) sent by the network equipment in the 3GPP access mode, wherein the message carries the GUTI distributed by the network equipment for the terminal equipment, and stops the timer.

(2) The terminal equipment has effective GUTI in the 3GPP access mode, has no effective GUTI in the non-3 GPP access mode, receives a configuration update command message (CONFIGURATION UPDATE COMMAND message) sent by the network equipment in the non-3 GPP access mode, carries the GUTI distributed by the network equipment for the terminal equipment, and stops the timer. Or alternatively, the process may be performed,

the terminal equipment has effective GUTI in a non-3 GPP access mode, has no effective GUTI in a 3GPP access mode, receives a configuration update command message (CONFIGURATION UPDATE COMMAND message) sent by the network equipment in the 3GPP access mode, carries the GUTI distributed by the network equipment for the terminal equipment, and stops a timer.

Under the condition that the initial registration flow under the two access modes does not occur in series, the timer is stopped when the first access mode is successful in registering through SUCI and acquiring effective GUTI, and the timer is stopped when the second access mode is successful in registering through SUCI and acquiring effective GUTI. For example, the timer may be stopped in several scenarios:

And deleting the SUCI generated last time after the timer is overtime.

In the following, with reference to fig. 4 and fig. 5, an example is described for a scenario in which a terminal device registers to different PLMNs through two access methods of 3GPP and non-3 GPP. Fig. 4 illustrates a case where initial registration flows of two access modes of 3GPP and non-3 GPP occur in series. Fig. 5 illustrates a case where the initial registration procedure of both the 3GPP and the non-3 GPP access methods does not occur serially.

Fig. 4 is a flow chart of another communication method according to an embodiment of the present application. As shown in fig. 4, the method of the present embodiment includes:

s401: when network registration is performed through a 3GPP access mode, the terminal equipment generates a first SUCI.

S402: the terminal equipment sends a registration request message to the 3GPP access network equipment, and the 3GPP access network equipment forwards the registration request message to the first core network equipment, wherein the registration request message comprises a first SUCI.

In this embodiment, a network accessed by the terminal device through a 3GPP access manner is a first PLMN, and a core network device corresponding to the first PLMN is a first core network device.

S403: the terminal equipment starts a timer corresponding to the first SUCI.

S404: the first core network device sends a registration acceptance message to the 3GPP access network device, and the 3GPP access network device forwards the registration acceptance message to the terminal device, wherein the registration acceptance message comprises a first GUTI corresponding to the first SUCI.

S405: the terminal equipment sends a registration completion message to the 3GPP access network equipment, and the 3GPP access network equipment forwards the registration completion message to the first core network equipment.

S406: when network registration is performed in a non-3 GPP access mode, the terminal equipment sends a registration request message to the non-3 GPP access network equipment, and the non-3 GPP access network equipment forwards the registration request message to the second core network equipment, wherein the registration request message comprises a first SUCI.

In this embodiment, the network to which the terminal device accesses through the non-3 GPP access mode is a second PLMN, and the core network device corresponding to the second PLMN is a second core network device.

In this embodiment, the time interval between the initial registration procedure of the non-3 GPP access mode and the initial registration procedure of the 3GPP access mode is shorter, for example, smaller than a certain preset threshold.

S407: the second core network device sends a registration acceptance message to the non-3 GPP access network device, and the non-3 GPP access network device forwards the registration acceptance message to the terminal device, wherein the registration acceptance message comprises a second GUTI corresponding to the first SUCI.

S408: the terminal equipment sends a registration completion message to the non-3 GPP access network equipment, and the non-3 GPP access network equipment forwards the registration completion message to the second core network equipment.

S409: and the terminal equipment stops the timer corresponding to the first SUCI.

In this embodiment, when the terminal device registers to different PLMNs through two access modes of 3GPP and non-3 GPP, the same timer may be used to manage the generation of the suis, so that the two access modes may share a set of process for generating and managing the suis, which makes the code concise and improves the maintainability of the code. And under the condition that the initial registration processes corresponding to the two access modes occur in series, the number of times of SUCI generation can be reduced, and the consumption of computing resources of the terminal equipment is reduced.

Fig. 5 is a flow chart of another communication method according to an embodiment of the present application. As shown in fig. 5, the method of the present embodiment includes:

s501: when network registration is performed through a 3GPP access mode, the terminal equipment generates a first SUCI.

S502: the terminal equipment sends a registration request message to the 3GPP access network equipment, and the 3GPP access network equipment forwards the registration request message to the first core network equipment, wherein the registration request message comprises a first SUCI.

S503: the terminal equipment starts a timer corresponding to the first SUCI.

S504: the first core network device sends a registration acceptance message to the 3GPP access network device, and the 3GPP access network device forwards the registration acceptance message to the terminal device, wherein the registration acceptance message comprises a first GUTI corresponding to the first SUCI.

S505: the terminal equipment sends a registration completion message to the 3GPP access network equipment, and the 3GPP access network equipment forwards the registration completion message to the first core network equipment.

S506: and the terminal equipment stops the timer corresponding to the first SUCI.

S507: and when the network registration is performed through a non-3 GPP access mode, the terminal equipment generates a second SUCI.

S508: the terminal equipment sends a registration request message to the non-3 GPP access network equipment, and the non-3 GPP access network equipment forwards the registration request message to the second core network equipment, wherein the registration request message comprises a second SUCI.

In this embodiment, the time interval between the initial registration procedure of the non-3 GPP access mode and the initial registration procedure of the 3GPP access mode is longer, for example, greater than 60 seconds.

S509: and the terminal equipment starts a timer corresponding to the second SUCI.

S510: the second core network device sends a registration acceptance message to the non-3 GPP access network device, and the non-3 GPP access network device forwards the registration acceptance message to the terminal device, wherein the registration acceptance message comprises a second GUTI corresponding to a second SUCI.

S511: the terminal equipment sends a registration completion message to the non-3 GPP access network equipment, and the non-3 GPP access network equipment forwards the registration completion message to the second core network equipment.

S512: and the terminal equipment stops the timer corresponding to the second SUCI.

In this embodiment, when the terminal device registers to different PLMNs through two access modes of 3GPP and non-3 GPP, the same timer may be used to manage the generation of the suis, so that the two access modes may share a set of process for generating and managing the suis, which makes the code concise and improves the maintainability of the code.

Fig. 6 is a schematic structural diagram of a communication device according to an embodiment of the present application. The apparatus may be in the form of software and/or hardware. The device may be a terminal device, or may be a chip or a chip module integrated in the terminal device. As shown in fig. 6, the communication apparatus 600 provided in this embodiment includes: a transmitting module 601, a receiving module 602 and a processing module 603.

The sending module 601 is configured to send a first message to a first network device when performing network registration in a first access manner, where the first message includes a first user hidden identifier sui;

a receiving module 602, configured to receive a first globally unique temporary terminal identifier GUTI corresponding to the first sui sent by the first network device;

and the processing module 603 is configured to perform network registration through the first GUTI or the first sui when performing network registration through the second access method.

In a possible implementation manner, the processing module 603 is specifically configured to:

controlling the sending module 601 to send a first registration request message to a second network device, where the first registration request message includes the first GUTI;

the receiving module 602 is controlled to receive a registration accept message sent by the second network device.

controlling the sending module 601 to send a second registration request message to a second network device, where the second registration request message includes the first sui;

the receiving module 602 is controlled to receive a second GUTI corresponding to the first suli sent by the second network device;

and controlling the sending module 601 to send a registration completion message to the second network device according to the second GUTI.

the receiving module 602 is controlled to receive a first identity request message sent by a second network device, where the first identity request message is used to request to obtain a sui corresponding to the second access mode;

And controlling the sending module 601 to send a first identity response message to the second network device, where the first identity response message includes the first sui.

In a possible implementation manner, the processing module 603 is further configured to:

In a possible implementation manner, the first network identifier and the second network identifier are the same; the processing module 603 is further configured to:

In a possible implementation manner, the sending module 601 is specifically configured to:

The communication device provided in this embodiment may be used to execute the communication method executed by the terminal device in any of the above method embodiments, and its implementation principle and technical effects are similar, and are not described herein.

Fig. 7 is a schematic structural diagram of a terminal device according to an embodiment of the present application. As shown in fig. 7, the terminal device 700 provided in this embodiment may include: a transceiver 701, a memory 702, a processor 703. The transceiver 701 may include: a transmitter and/or a receiver. The transmitter may also be referred to as a transmitter, transmit port, transmit interface, or the like, and the receiver may also be referred to as a receiver, receive port, receive interface, or the like. Illustratively, the transceiver 701, the memory 702, and the processor 703 are interconnected by a bus 704.

Memory 702 is used to store computer-executable instructions;

the processor 703 is configured to execute computer-executable instructions stored in the memory, to cause the terminal device 700 to perform any of the methods described above.

The transmitter in the transceiver 701 may be configured to perform the transmitting function of the terminal device in the foregoing method embodiment. The receiver in transceiver 701 may be configured to perform the receiving functions of the terminal device in the above-described method embodiments. The processor 703 is operable to perform the communication methods performed by the terminal device in the method embodiments described above.

The terminal device provided in this embodiment may be used to execute the communication method executed by the terminal device in any of the above method embodiments, and its implementation principle and technical effects are similar, and are not described herein.

The embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium includes a computer program, where the computer program is configured to implement a method according to any one of the above method embodiments, and the implementation principle and technical effects are similar, and are not described herein.

The embodiment of the application also provides a chip, which comprises: the computer program is executed by the processor to execute the method of any of the above method embodiments, and the implementation principle and technical effects are similar, and are not repeated here.

The embodiment of the present application further provides a computer program product, which includes a computer program, where the computer program when executed by a processor implements a method of any of the foregoing method embodiments, and the implementation principle and technical effects are similar, and are not described herein in detail.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple modules may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.

The modules described as separate components may or may not be physically separate, and components shown as modules may or may not be physical units, may be located in one place, or may be distributed over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional module in the embodiments of the present application may be integrated in one processing unit, or each module may exist alone physically, or two or more modules may be integrated in one unit. The units formed by the modules can be realized in a form of hardware or a form of hardware and software functional units.

The integrated modules, which are implemented in the form of software functional modules, may be stored in a computer readable storage medium. The software functional module is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (english: processor) to perform some of the steps of the methods according to the embodiments of the application.

It should be understood that the above processor may be a central processing unit (english: central Processing Unit, abbreviated as CPU), or may be other general purpose processors, digital signal processors (english: digital Signal Processor, abbreviated as DSP), application specific integrated circuits (english: application Specific Integrated Circuit, abbreviated as ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution.

The memory may comprise a high-speed RAM memory, and may further comprise a non-volatile memory NVM, such as at least one magnetic disk memory, and may also be a U-disk, a removable hard disk, a read-only memory, a magnetic disk or optical disk, etc.

The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (Peripheral Component, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, the buses in the drawings of the present application are not limited to only one bus or to one type of bus.

The storage medium may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuits, ASIC for short). It is also possible that the processor and the storage medium reside as discrete components in an electronic device or a master device.

Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.

Claims

1. A method of communication, comprising:

when network registration is carried out in a second access mode, a first network identifier of a network registered in the first access mode and a second network identifier of a network to be registered in the second access mode are obtained;

if the first network identifier is different from the second network identifier, network registration is performed through the first SUCI;

after sending the first message to the first network device, further comprising:

starting a timer corresponding to the first SUCI;

the first network identifier is the same as the second network identifier; after receiving the first GUTI corresponding to the first suli sent by the first network device, the method further includes:

and stopping the timer corresponding to the first SUCI.

2. The method according to claim 1, wherein the method further comprises:

and if the first network identifier is the same as the second network identifier, performing network registration through the first GUTI.

3. The method of claim 2, wherein network registration through the first GUTI comprises:

4. The method of claim 1, wherein performing network registration through the first sui comprises:

5. The method of claim 1, wherein performing network registration through the first sui comprises:

6. The method of claim 1, wherein the first network identification and the second network identification are not the same; after network registration through the first sui, the method further includes:

And stopping the timer corresponding to the first SUCI.

7. The method of any of claims 1 to 6, wherein sending the first message to the first network device comprises:

8. The method according to any one of claim 1 to 6, wherein,

the first access mode is a 3GPP access mode, and the second access mode is a non-3 GPP access mode; or alternatively, the process may be performed,

9. A communication device, comprising:

The processing module is used for acquiring a first network identifier of a network registered in the first access mode and a second network identifier of a network to be registered in the second access mode when network registration is performed in the second access mode; if the first network identifier is different from the second network identifier, network registration is performed through the first SUCI;

the processing module is further configured to:

after a first message is sent to a first network device, starting a timer corresponding to the first SUCI;

the first network identifier is the same as the second network identifier; the processing module is further configured to:

10. The apparatus of claim 9, wherein the processing module is specifically configured to:

11. The apparatus of claim 10, wherein the processing module is specifically configured to:

12. The apparatus of claim 9, wherein the processing module is specifically configured to:

13. The apparatus of claim 9, wherein the processing module is specifically configured to:

14. The apparatus of claim 9, wherein the first network identification and the second network identification are the same; the processing module is further configured to:

15. The apparatus according to any one of claims 9 to 14, wherein the sending module is specifically configured to:

16. The device according to any one of claims 9 to 14, wherein,

17. A terminal device, comprising: a transceiver, a processor, a memory;

the memory stores computer-executable instructions that when executed by the processor implement the method of any one of claims 1 to 8.

18. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor implement the method of any one of claims 1 to 8.