Communication methods, devices, and storage media

Abstract

This disclosure discloses a communication method, apparatus, and storage medium. The method includes a first device transmitting an instruction message to a terminal, the instruction message being used to instruct the terminal to perform a rebootstrap operation.

Description

Technical Field

[0001] (Cross-reference to Related Applications) This disclosure is filed based on a Chinese patent application with application number 202310273426.3 and filing date of March 20, 2023, claims priority based on the Chinese patent application, and all its contents are incorporated into this disclosure by reference.

[0002] This disclosure relates to the field of wireless communication, and particularly to communication methods, devices, and storage media.

Background Art

[0003] In the prior art, in an Extended Generic Bootstrapping Architecture (GBA) system, after the execution of the extended GBA security processing flow is completed, the network service side and the terminal (UE, User Equipment) can communicate via a shared session key K*. The session key K* must be generated after the terminal actively requests authentication. The network service side cannot request re-authentication of the terminal identity and cannot regenerate a new GBA application layer session key K*.

[0004] Similar to the extended GBA system, for the session key KA* adopted in the Extended Authentication and Key Management for Applications (AKMA) system, it must also be generated after the terminal actively requests authentication. The network service side cannot request re-authentication of the terminal identity and cannot regenerate a new session key KA*.

Summary of the Invention

Problems to be Solved by the Invention

[0005] In view of this, the main object of this disclosure is to provide communication methods, devices, and storage media. [Means for solving the problem]

[0006] To achieve the above objectives, the technical solution of this disclosure is implemented as follows.

[0007] In a first embodiment, an embodiment of the present disclosure provides a communication method performed by a first device, the method being This includes sending an instruction message to the terminal, which is used to instruct the terminal to perform a rebootstrap operation.

[0008] In one embodiment, the method further includes receiving uplink data from the terminal, wherein the uplink data includes at least data encrypted with a first key, the first key being a GBA application session key or an AKMA application session key. Sending the instruction message to the aforementioned terminal means The method includes sending the instruction message to the terminal if the first key does not meet the key validity conditions set by the first device based on the security policy, or if it is necessary to trigger an update of the first key.

[0009] In one embodiment, if the first key does not satisfy the key validity conditions set by the first device based on the security policy, The first key has reached its maximum number of reuses, The first key has reached the usage time permitted by the application, This includes at least one of the following: the first key is exposed to the outside.

[0010] In one embodiment, sending the instruction message to the terminal is: Sending the instruction message directly to the aforementioned terminal, This includes transmitting the instruction message to a second device, wherein the instruction message is transmitted from the second device to the terminal.

[0011] In one embodiment, receiving the uplink data from the terminal is: Receiving the uplink data transmitted directly by the aforementioned terminal, Receiving the uplink data transmitted by the second device, which includes the uplink data being transmitted from the terminal to the second device.

[0012] In one embodiment, when the first device communicates directly with the terminal, the uplink data and / or the instruction message are: Transmission is based on at least one of the following protocols: Hypertext Transfer Protocol (HTTP), The Constrained Application Protocol (CoAP), Message Queuing Telemetry Transport (MQTT), or a preset private protocol.

[0013] In one embodiment, when the first device communicates with the terminal via the second device, the uplink data and / or the instruction message are transmitted based on the HTTP protocol.

[0014] In one embodiment, the method further includes: This includes receiving a new first key and / or key lifetime transmitted by a second device and updating the local first key and / or key lifetime.

[0015] In one embodiment, when the method is applied to a general-purpose bootstrap architecture GBA system, the first device is a server, and the second device includes a Network Application Function (NAF) and / or an Authentication Proxy (AP).

[0016] In one embodiment, when the method is applied to an AKMA system, the first device includes an application function (AF) and / or a server. The second device includes at least one of the following: AKMA anchor function (AAnF), AKMA authentication proxy (AAP), AP, and application function network element (NEF).

[0017] In a second embodiment, an embodiment of the present disclosure provides a communication method performed by a terminal, the method being: Receiving an instruction message from the first device, the instruction message being used to instruct the terminal to perform a rebootstrap operation, This includes sending a rebootstrap request message to a third device.

[0018] In one embodiment, receiving the instruction message from the first device means that Receiving the instruction message transmitted directly by the first device, Receiving the instruction message transmitted by the second device, wherein the instruction message is transmitted from the first device to the second device.

[0019] In one embodiment, the method further includes: including transmitting upstream data to the first device, the upstream data including at least data encrypted with a first key, the first key being a GBA application session key or an AKMA application session key.

[0020] In one embodiment, transmitting upstream data to the first device comprises either directly transmitting the upstream data to the first device or transmitting the upstream data to a second device, the upstream data being transmitted from the second device to the first device.

[0021] In one embodiment, when the first device communicates directly with the terminal, the upstream data and / or the instruction message are transmitted based on at least one communication protocol among HTTP, CoAP, MQTT, and a preset private protocol.

[0022] In one embodiment, when the first device communicates with the terminal via a second device, the upstream data and / or the instruction message are transmitted based on the HTTP communication protocol.

[0023] In one embodiment, the method further comprises transmitting a first message to a second device, the first message carrying at least one identifier information of the first device, the at least one first device having established an association with the terminal regarding application security and being at least one first device provided with services by the second device.

[0024] In one embodiment, the method further comprises receiving a second message transmitted by the second device, the second message carrying an update result for all or part of the first devices to update the first key and / or the key lifetime.

[0025] In one embodiment, the method further comprises This includes generating and storing a new first key corresponding to each of the at least one first device based on the second key, Here, the second key is a shared key negotiated by the terminal and the second device by re-executing the GBA bootstrap procedure and the GBA bootstrap security association usage procedure.

[0026] In one embodiment, when the method is applied to a GBA system, the first device is a server, the second device includes a NAF and / or AP, and the third device is a Bootstrap Server Function (BSF).

[0027] In one embodiment, when the method is applied to an AKMA system, the first device includes an AF and / or a server, the second device includes at least one of AAnF, AAP, AP, and NEF, and the third device includes an AAnF and / or AAP.

[0028] In a third embodiment, an embodiment of the present disclosure provides a communication method performed by a second device, the method being The process includes receiving a first message transmitted by a terminal, the first message including identifier information for at least one first device, the at least one first device having already established an application security association with the terminal and being serviced by the second device.

[0029] In one embodiment, the method further includes: Based on the identifier information of at least one first device in the first message, a new first key and / or key lifetime corresponding to each first device is generated, This includes transmitting a new first key and / or key lifetime to the corresponding first device.

[0030] In one embodiment, the method further includes: Sending a third message to each first device based on the identifier information of at least one first device in the first message, wherein the third message includes the identifier information of the corresponding first device. Receiving the fourth message transmitted by each first device, To generate a corresponding new first key and / or key lifetime for each first device, This includes transmitting the corresponding new first key and / or key lifetime to each first device.

[0031] In one embodiment, the method further includes: Determining the key transmission mode adopted by at least one of the first devices, If the first device adopts push mode, a new first key and / or key lifetime corresponding to the first device is generated based on the identifier information of the first device, the new first key and / or key lifetime is transmitted to the corresponding first device, and / or if the first device adopts request mode, a third message containing the identifier information of the first device is transmitted to the first device based on the identifier information of the first device. Receiving the fourth message transmitted by the first device, To generate a new first key and / or key lifetime corresponding to the first device, This includes transmitting a new first key and / or key lifetime to the first device.

[0032] In one embodiment, the method further includes: This includes generating and storing a new corresponding first key for each first device based on the second key, Here, the second key is a shared key negotiated by the terminal and the second device by re-executing the GBA bootstrap procedure and the GBA bootstrap security association usage procedure.

[0033] In one embodiment, the method further includes: To receive the result of successful reception of a new first key and / or key lifetime by each first device, Receiving the result of failure to receive a new first key and / or key lifetime for each first device, This includes at least one of the following: not receiving a result indicating successful reception of a new first key and / or key lifetime by the first device.

[0034] In one embodiment, the method further includes: This includes sending a second message to the terminal, the second message including an update result in which all or some of the first devices update the first key and / or key lifetime.

[0035] In one embodiment, the method further includes: Receiving an instruction message from the first device, the instruction message being used to instruct the terminal to perform a rebootstrap operation, This includes sending the aforementioned instruction message to the terminal.

[0036] In one embodiment, the method further includes: The process involves receiving uplink data from a terminal, wherein the uplink data includes at least business data encrypted with a first key. This includes transmitting the aforementioned uplink data to the first device.

[0037] In one embodiment, when the method is applied to a GBA system, the first device is a server, and the second device includes a NAF and / or AP.

[0038] In one embodiment, when the method is applied to an AKMA system, the first device includes an AF and / or a server, and the second device includes at least one of AAnF, AAP, AP, and NEF.

[0039] In a fourth embodiment, an embodiment of the present disclosure provides a communication device applicable to a first device, the device is The system includes a first transmitting module configured to send instruction messages to a terminal, which are used to instruct the terminal to perform a rebootstrap operation.

[0040] In one embodiment, the device further includes a first receiving module configured to receive uplink data from the terminal, wherein the uplink data includes at least data encrypted with a first key, the first key being a GBA application session key or an AKMA application session key. The first transmission module is configured to send an instruction message to the terminal if the first key does not meet the key validity conditions set by the first device based on the security policy, or if it is necessary to trigger an update of the first key.

[0041] In one embodiment, if the first key does not satisfy the key validity conditions set by the first device based on the security policy, The first key has reached its maximum number of reuses, The first key has reached the usage time permitted by the application, This includes at least one of the following: the first key is exposed to the outside.

[0042] In one embodiment, the first transmission module is Sending the instruction message directly to the aforementioned terminal, The system is configured to perform one of the following: sending the instruction message to a second device, wherein the instruction message is sent from the second device to the terminal.

[0043] In one embodiment, the first receiving module is Receiving the uplink data transmitted directly by the aforementioned terminal, The device is configured to perform one of the following: receiving the uplink data transmitted by the second device, wherein the uplink data is transmitted from the terminal to the second device.

[0044] In one embodiment, when the first device communicates directly with the terminal, the uplink data and / or the instruction message are: Transmission is based on at least one of the following protocols: HTTP, CoAP, MQTT, or a preset private protocol.

[0045] In one embodiment, when the first device communicates with the terminal via the second device, the uplink data and / or the instruction message are transmitted based on the HTTP protocol.

[0046] In one embodiment, the first receiving module is further configured to receive a new first key and / or key lifetime transmitted by the second device and to update the local first key and / or key lifetime.

[0047] In one embodiment, when the device is applied to a general-purpose bootstrap architecture GBA system, the first device is a server, and the second device includes a NAF and / or AP.

[0048] In one embodiment, when the device is applied to an AKMA system, the first device includes an AF and / or a server, and the second device includes at least one of AAnF, AAP, AP, and NEF.

[0049] In a fifth embodiment, an embodiment of the present disclosure provides a communication device to be applied to a terminal, the device being A second receiving module configured to receive instruction messages from a first device, wherein the instruction messages are used to instruct a terminal to perform a rebootstrap operation, It includes a second transmitting module configured to send a rebootstrap request message to a third device.

[0050] In one embodiment, the second receiving module is Receiving the instruction message transmitted directly by the first device, The system is configured to perform one of the following: receiving the instruction message transmitted by the second device, wherein the instruction message is transmitted from the first device to the second device.

[0051] In one embodiment, the second transmission module is further configured to transmit uplink data to the first device, the uplink data including at least data encrypted with a first key, the first key being a GBA application session key or an AKMA application session key.

[0052] In one embodiment, the second transmission module is Transmitting the uplink data directly to the first device, The system is configured to perform one of the following: transmit the uplink data to a second device, and transmit the uplink data from the second device to the first device.

[0053] In one embodiment, when the first device communicates directly with the terminal, the uplink data and / or the instruction message are: It is transmitted based on at least one of the following communication protocols: HTTP, CoAP, MQTT, or a preset private protocol.

[0054] In one embodiment, when the first device communicates with the terminal via the second device, the uplink data and / or the instruction message are transmitted based on the HTTP communication protocol.

[0055] In one embodiment, the second transmission module is further configured to transmit a first message to a second device, the first message including identifier information of at least one first device, the at least one first device having already established an application security association with the terminal and being serviced by the second device.

[0056] In one embodiment, the second receiving module is further configured to receive a second message transmitted by the second device, the second message including an update result in which all or part of the first device updates the first key and / or key lifetime.

[0057] In one embodiment, the apparatus further includes a second processing module configured to generate and store a new first key corresponding to each of the at least one first device based on the second key. Here, the second key is a shared key negotiated by the terminal and the second device by re-executing the GBA bootstrap procedure and the GBA bootstrap security association usage procedure.

[0058] In one embodiment, when the device is applied to a GBA system, the first device is a server, the second device includes a NAF and / or AP, and the third device is a BSF.

[0059] In one embodiment, when the device is applied to an AKMA system, the first device includes an AF and / or a server, the second device includes at least one of AAnF, AAP, AP, and NEF, and the third device includes an AAnF and / or AAP.

[0060] In a sixth embodiment, an embodiment of the present disclosure provides a communication device applicable to a second device, the device being The system includes a third receiving module configured to receive a first message transmitted by a terminal, the first message including identifier information for at least one first device, the at least one first device having already established an application security association with the terminal and being serviced by the second device.

[0061] In one embodiment, the device further includes a third processing module configured to generate a new first key and / or key lifetime corresponding to each first device based on identifier information of several first devices in the first message, The device further includes a third transmitting module configured to transmit a new first key and / or key lifetime to the corresponding first device.

[0062] In one embodiment, the third transmission module is further configured to transmit a third message to each first device based on identifier information of at least one first device in the first message, the third message being accompanied by the corresponding identifier information of the first device. The third receiving module is further configured to receive the fourth message transmitted by each first device. The third processing module is further configured to generate a corresponding new first key and / or key lifetime for each first device, The third transmission module is further configured to transmit a corresponding new first key and / or key lifetime to each first device.

[0063] In one embodiment, the third processing module is further configured to determine the key transmission mode employed by the at least one first device. If the first device adopts push mode, the third transmission module is configured to generate a new first key and / or key lifetime corresponding to the first device based on the identifier information of the first device, and to further transmit the new first key and / or key lifetime to the corresponding first device, and / or if the first device adopts request mode, the third transmission module is configured to further transmit a third message to the first device accompanied by the identifier information of the first device based on the identifier information of the first device. The third receiving module is further configured to receive a fourth message transmitted by the first device. The third processing module is further configured to generate a new first key and / or key lifetime corresponding to the first device. The third transmission module is further configured to transmit a new first key and / or key lifetime to the first device.

[0064] In one embodiment, the third processing module is further configured to generate and store a new corresponding first key for each first device based on the second key. Here, the second key is a shared key negotiated by the terminal and the second device by re-executing the GBA bootstrap procedure and the GBA bootstrap security association usage procedure.

[0065] In one embodiment, the third receiving module further, To receive the result of successful reception of a new first key and / or key lifetime by each first device, Receiving the result of failure to receive a new first key and / or key lifetime for each first device, It is configured to perform at least one of the following: not receiving a result indicating successful reception of a new first key and / or key lifetime by the first device.

[0066] In one embodiment, the third transmission module is further configured to transmit a second message to a terminal, the second message including an update result in which all or some of the first devices update the first key and / or key lifetime.

[0067] In one embodiment, the third receiving module is further configured to receive instruction messages from the first device, which are used to instruct the terminal to perform a rebootstrap operation. The third transmission module is further configured to transmit the instruction message to the terminal.

[0068] In one embodiment, the third receiving module is further configured to receive uplink data from a terminal, and the uplink data includes at least business data encrypted with a first key. The third transmission module is further configured to transmit the uplink data to the first device.

[0069] In one embodiment, when the device is applied to a GBA system, the first device is a server, and the second device includes a NAF and / or AP.

[0070] In one embodiment, when the device is applied to an AKMA system, the first device includes an AF and / or a server, and the second device includes at least one of AAnF, AAP, AP, and NEF.

[0071] In a seventh embodiment, an embodiment of the present disclosure provides a communication device including memory, a processor, and a computer program stored in the memory and executable on the processor, which implements any one of the steps of the method that the first device side performs when the processor executes the program, or any one of the steps of the method that the terminal side performs when the processor executes the program, or any one of the steps of the method that the second device side performs when the processor executes the program.

[0072] In the eighth embodiment, an embodiment of the present disclosure provides a computer-readable storage medium in which a computer program is stored, and implements any one step of the method that is performed by the first device when the computer program is executed on a processor, or implements any one step of the method that is performed by the terminal when the computer program is executed on a processor, or implements any one step of the method that is performed by the second device when the computer program is executed on a processor. [Effects of the Invention]

[0073] According to one communication method, apparatus, and storage medium relating to an embodiment of the present disclosure, in the method, a first device transmits an instruction message to a terminal, which is used to instruct the terminal to perform a rebootstrap operation, and accordingly, the terminal receives the instruction message from the first device and transmits a rebootstrap request message to a third device, and the second device receives the first message transmitted by the terminal, wherein the first message includes identifier information of at least one first device, and the at least one first device is at least one first device that has already established an application security association with the terminal and is serviced by the second device. In this way, the first device can proactively transmit a rebootstrap instruction message to the terminal, and the terminal can re-execute the security mechanism and rebuild the application layer security association. [Brief explanation of the drawing]

[0074] [Figure 1] This is a network architecture diagram of a GBA system in a 4G network environment. [Figure 2] This is a diagram of the extended GBA system architecture. [Figure 3] AKMA basic architecture diagram. [Figure 4] This is an extended AKMA system architecture. [Figure 5] This is a flowchart of the 3GPP standard bootstrap renegotiation method. [Figure 6] This is a schematic flowchart of one communication method according to an embodiment of the present disclosure. [Figure 7] This is a schematic flowchart of another communication method according to the embodiment of this disclosure. [Figure 8] This is a schematic flowchart of yet another communication method according to the embodiments of this disclosure. [Figure 9] This is a schematic flowchart of a rebootstrap method for a GBA system according to an embodiment of the present disclosure. [Figure 10] This is a schematic flowchart of a rebootstrap method for another GBA system according to an embodiment of the present disclosure. [Figure 11] This is a schematic flowchart of a rebootstrap method for an extended AKMA system according to one embodiment of the present disclosure. [Figure 12] This is a schematic flowchart of a rebootstrap method for another extended AKMA system according to an embodiment of the present disclosure. [Figure 13] This is a schematic flowchart of a rebootstrap method for a GBA system of one or more Servers according to an embodiment of this disclosure. [Figure 14] This is a schematic flowchart of a rebootstrap method for a GBA system of another set of Servers according to an embodiment of this disclosure. [Figure 15] This is a schematic flowchart of a method for determining a second key according to an embodiment of this disclosure. [Figure 16] This is a schematic diagram of the structure of one communication device according to the present disclosure. [Figure 17] This is a schematic diagram of the structure of another communication device according to the present disclosure. [Figure 18] This is a schematic diagram of the structure of yet another communication device according to the present disclosure. [Figure 19] This is a schematic diagram of the structure of one communication device according to the embodiment of this disclosure. [Modes for carrying out the invention]

[0075] Before providing a detailed explanation of this disclosure, we will describe the relevant technical methods. The Generic Bootstrapping Architecture (GBA) is a general-purpose authentication and session key negotiation method based on mobile communication networks and Universal Subscriber Identity Modules (USIMs), as defined in the 3rd Generation Partnership Project (3GPP®). It can provide full security authentication and application-layer session channel encryption services to application layer operations. The GBA system can be built on top of 4th generation mobile communication technology (4G) or 5th generation mobile communication technology (5G) networks. The network architecture of the GBA system in a 4G network environment is shown in Figure 1. The system architecture in a 5G network is similar, and the Home Subscriber Server (HSS) can be replaced with Unified Data Management (UDM).

[0076] In the standard GBA architecture, the Network Application Function (NAF) network element is integrated with the server and deployed externally on the service provider side. The NAF network element performs authentication and key negotiation (AKA) identity authentication for terminal devices accessing the server using the 4G / 5G cellular network GBA security mechanism. After successful authentication, it obtains the GBA session key Ks_NAF shared with the terminal from the Bootstrap Server Function (BSF) network element, establishes a security association, and enables secure communication between the terminal and the server based on Ks_NAF.

[0077] However, in the 3GPP standard GBA architecture, NAF network elements are deployed externally and integrated with external servers on the service provider side. A single NAF network element can only provide GBA security services to its associated application service, and cannot provide services to multiple applications. Therefore, this deployment method results in high GBA application costs and is disadvantageous for the large-scale deployment and widespread adoption of GBA technology.

[0078] To increase the utilization rate of NAF network elements and reduce the operating costs of mobile operator networks, an extended GBA system architecture has been proposed, as shown in Figure 2. In this system, NAF network elements are located on the operator network side and not on the service provider side, thereby enabling operators to construct a GBA business platform based on NAF network elements and provide security services to multiple different servers. Servers interact with NAF network elements through an integrated and simplified NAF' business function processing module, realizing an enhanced GBA security authentication and key negotiation mechanism. After performing GBA AKA identity authentication on the terminal UE, they obtain a GBA application layer session key K* derived from Ks_NAF from the NAF network element, establish an application layer security association, and perform secure communication with the terminal based on K*. In Figure 2, Zh, Ub, Zn, Ua, and Zn' are all interfaces involved in the communication process.

[0079] To enable better integration with 5G networks based on a Service-based Architecture (SBA), 3GPP defined an Authentication and Key Management for Applications (AKMA) processing flow referencing the GBA processing mechanism. AKMA is an upgrade of GBA in 5G systems, and like GBA, it authenticates the identity of the UE based on 3GPP security certificates and can negotiate an AKMA session key KAF for shared use by the server and UE. KAF corresponds to Ks_NAF in GBA. Figure 3 is a diagram of one AKMA basic architecture. As shown in Figure 3, the main network elements of AKMA have almost the same functions as the main network elements of GBA, the AKMA Anchor Function (AAnF) is similar to BSF, and the Application Function Network Element (AF) is similar to NAF, so their explanation is omitted here. In Figure 3, N13, N12, N2, N61, N62, N1, and Ua* are all interfaces involved in the communication process.

[0080] To reduce the operating costs for service providers and realize one-to-many security services, we are currently proposing an extended AKMA mechanism that references the extended GBA mechanism, and its architecture is shown in Figure 4. This mechanism adds an AKMA Authentication Proxy (AAP) network element between AAnF and AF, which is one K AF Different AKMA application layer session keys (K) for different servers based on this. A *By generating this, it is possible to provide services to multiple servers. In this case, the AAP network element corresponds to the NAF in the extended GBA, AF corresponds to the NAF', K A * corresponds to K*.

[0081] In an extended GBA system, after the execution of the extended GBA security processing flow is complete, if the server and terminal UE already possess the shared GBA application layer session key K*, the server may proactively request re-authentication of the terminal UE identity for security reasons and completely reset the GBA operating mechanism by regenerating a new GBA application layer session key K*.

[0082] To address the business application need to re-establish security associations, the 3GPP standard proposes a "Bootstrapping renegotiation request" flow, which requires the terminal UE to re-execute the GBA security mechanism and re-complete GBA AKA authentication, after which it obtains and uses a new GBA session key Ks_NAF to achieve secure communication. Specifically, as shown in Figure 5, the 3GPP standard bootstrap renegotiation request process includes the following steps.

[0083] In 501, the terminal (UE) sends a request to the NAF network element (i.e., the server), and this request may be a Hypertext Transfer Protocol (HTTP) message.

[0084] In 502, when the NAF network element receives a business request from the UE, it sends a bootstrap renegotiation request to the UE, requesting that the UE re-execute the GBA security mechanism to obtain a new key.

[0085] However, the above measures apply only to standard 3GPP GBA systems and not to extended GBA systems. Therefore, when aiming for an extended GBA system architecture, it is necessary to propose technical solutions that support the re-establishment of GBA application layer security associations by the server.

[0086] In addition, the expandable AKMA system has a similar problem.

[0087] Based on this, in a method according to an embodiment of the present disclosure, a first device sends an instruction message to a terminal, which is used to instruct the terminal to perform a rebootstrap operation, and in response, the terminal receives the instruction message from the first device and sends a rebootstrap request message to a third device, and the terminal sends a first message to a second device, which includes identifier information of several first devices, the several first devices being several first devices that have already established an application security association with the terminal and are serviced by the second device.

[0088] Figure 6 is a schematic flowchart of one communication method according to an embodiment of the present disclosure. As shown in Figure 6, the method may be applied to a first device. The method includes the following steps.

[0089] In step 601, an instruction message is sent to the terminal. The instruction message is used to instruct the terminal to perform a rebootstrap operation.

[0090] In actual application, when the method is applied to a GBA system or an extended GBA system, the first device may be a server, and the second device may include a Network Application Function (NAF) and / or an Authentication Proxy (AP).

[0091] The aforementioned rebootstrap operation is called the bootstrap renegotiation process. Its purpose is for the terminal device to re-execute the GBA bootstrap flow, re-execute identity authentication, and negotiate a new GBA session key (Ks_NAF). Embodiments of this disclosure do not limit the name of the rebootstrap operation, but only if the corresponding function can be implemented.

[0092] In actual application, when the method is applied to an AKMA system or an extended AKMA system, the first device may include an Application function (AF) and / or a server. The second device may include at least one of the following: an AKMA anchor function (AAnF), an AKMA authentication proxy (AAP), an AP, or an Application Function Network Element (NEF). In one example, the second device may include an AAnF, an AAP, and / or a NEF. In another example, the second device may include an AAnF, an AP, and / or a NEF. In yet another example, the second device may include at least one of the AAnF, an AAP, an AP, or a NEF. This is not an limitation.

[0093] The aforementioned rebootstrap operation can also be described to restart the AKMA process. Embodiments of this disclosure do not limit the name of the rebootstrap operation, as long as the corresponding function can be implemented.

[0094] In the embodiments of this disclosure, the names of the first and second devices are not limited, and it is sufficient that they can perform the functions of the first and second devices.

[0095] In some embodiments, the instruction message is used to instruct the terminal to perform a rebootstrap operation.

[0096] In one example, the instruction message may be an HTTP 401 Unauthorized message, and in another example, the instruction message may be a message of another format or a message accompanied by a corresponding rebootstrap instruction.

[0097] In some embodiments, the method further This includes receiving uplink data from the terminal, and the uplink data includes at least data encrypted with a first key. Here, the first key is either a GBA application session key or an AKMA application session key. Sending an instruction message to the aforementioned terminal means If the first key does not meet the key validity conditions set by the server based on the security policy, or if it is necessary to trigger an update of the first key, an instruction message is sent to the terminal.

[0098] In some embodiments, the first key does not satisfy the key validity conditions set by the server based on the security policy. The first key has reached its maximum number of reuses, The first key has reached the usage time permitted by the application, This includes at least one of the following: the first key is exposed to the outside.

[0099] Illustratively, the method described above is applied to a server in an extended GBA system, and the execution of the extended GBA security processing flow is complete, and the server and terminal possess a shared GBA application layer session key K* (i.e., the first key). In such a situation, the server proactively requests re-authentication of the terminal identity for security reasons and resets the GBA mechanism operational state by regenerating a new GBA application layer session key K*, thereby allowing the server to re-establish the GBA application layer security association with the terminal. For example, the following situation can be considered:

[0100] (1) The first key has reached its maximum number of reuses. For example, this could be due to K* reaching its maximum number of reuses. (2) The first key has reached the usage time permitted by the application. For example, K* may become invalid or no longer be new, or K* may have already exceeded its key lifetime or will exceed its key lifetime. (3) The server failed to obtain K*. For example, the Bootstrap Transaction IDentifier (B-TID) used to obtain K* may have expired, causing the server to fail to obtain K* from the second device (e.g., NAF). (4) When recovering from an abnormal state, the server needs to proactively re-establish the application layer security association with the terminal, and other situations may arise such as the K* shared between the server and the terminal not matching.

[0101] In situations where the aforementioned server needs to proactively re-establish security associations, this disclosure submits a GBA rebootstrap flow to enable the server to proactively restart the extended GBA security mechanism.

[0102] In some embodiments, sending an instruction message to the terminal is: Sending the instruction message directly to the aforementioned terminal, This includes one of the following: transmitting the instruction message to a second device, wherein the instruction message is transmitted from the second device to the terminal.

[0103] Here, the first device sending an instruction message to the terminal may either send it directly to the terminal or forward it to the terminal via the second device.

[0104] Here, the second device may either pass the instruction message to the terminal directly, or it may modify the instruction message accordingly before sending it to the terminal.

[0105] The transmission of other messages via the second device is similar; the second device may directly pass through the other messages to the terminal, or it may modify the other messages accordingly before sending them to the terminal, a process that will not be described in detail here.

[0106] In some embodiments, receiving uplink data from the terminal is The terminal directly transmits uplink data, Receiving uplink data transmitted by a second device, the uplink data being transmitted from the terminal to the second device, is one of the following:

[0107] Here, when a terminal transmits data up to the first device, it may either transmit directly to the first device or transfer the data to the first device via the second device.

[0108] Here, the transmission of uplink data from the terminal to the first device by the second device may be done either by the second device directly passing the uplink data to the first device, or by the first device performing the corresponding modifications before transmitting the data to the first device, which will not be described in detail here.

[0109] The same applies to transmitting other data or messages via the second device, where the second device may directly pass through the other data or messages to the first device, or it may modify the other data or messages accordingly before transmitting them to the first device.

[0110] In some embodiments, when the first device communicates directly with the terminal, the uplink data and / or the instruction message are Transmission is based on at least one of the following protocols: Hypertext Transfer Protocol (HTTP), The Constrained Application Protocol (CoAP), Message Queuing Telemetry Transport (MQTT), or a preset private protocol.

[0111] In some embodiments, when the first device communicates with the terminal via the second device, the uplink data and / or instruction messages are transmitted based on the HTTP protocol.

[0112] In some embodiments, the method further This includes receiving a new first key and / or key lifetime transmitted by a second device and updating the local first key and / or key lifetime.

[0113] Here, the first device can perform a corresponding update operation when it receives a new first key and / or key lifetime, in order to ensure that the key being used is the latest key.

[0114] In some embodiments, the method further The system transmits the result of successful reception for a new first key and / or key lifetime to the second device, This may include at least one of the following: transmitting the result of a failure to receive a new first key and / or key lifetime to a second device.

[0115] Here, when the first device receives a new first key and / or key lifetime, it can notify the second device of the result. If a new first key and / or key lifetime has not been received for a certain period of time, the first device can notify the second device of the result of the reception failure or the result of not receiving the key.

[0116] Figure 7 is a schematic flowchart of another communication method according to an embodiment of the present disclosure. As shown in Figure 7, the method may be applied to a terminal. The method includes the following steps.

[0117] In step 701, an instruction message is received from the first device. This instruction message is used to instruct the terminal to perform a rebootstrap operation.

[0118] In step 702, a rebootstrap request message is sent to the third device.

[0119] In actual application, when the method is applied to a GBA system or an extended GBA system, the first device may be a server, the second device may include a NAF and / or AP, and the third device may be a Bootstrap Server Function (BSF).

[0120] The aforementioned rebootstrap operation is also called the bootstrap renegotiation process. Its purpose is for the terminal device to re-execute the GBA bootstrap flow, re-execute identity authentication, and negotiate a new GBA session key (Ks_NAF). Embodiments of this disclosure do not limit the name of the rebootstrap operation, but only if the corresponding function can be implemented.

[0121] In actual application, when the method is applied to an AKMA system or an extended AKMA system, the first device may include an AF and / or a server. The second device may include at least one of AAnF, AAP, AP, or NEF. The third device may include AAnF and / or AAP, or the third device may include AAnF and / or AP, or the third device may include AAnF, AAP, and / or AP, without limitation.

[0122] The aforementioned rebootstrap operation can also be described to restart the AKMA process. Embodiments of this disclosure do not limit the name of the rebootstrap operation, as long as the corresponding function can be implemented.

[0123] In the embodiments of this disclosure, the names of the first, second, and third devices are not limited, and it is sufficient that the functions of the first, second, and third devices can be realized.

[0124] In some embodiments, receiving instruction messages from the first device means that Receiving the instruction message transmitted directly by the first device, Receiving the instruction message transmitted by the second device, wherein the instruction message is transmitted from the first device to the second device.

[0125] Here, the second device may either pass the instruction message to the terminal directly, or it may modify the instruction message accordingly before sending it to the terminal.

[0126] In some embodiments, the method further The process includes transmitting uplink data to a first device, wherein the uplink data includes at least data encrypted with a first key, and the first key is a GBA application session key or an AKMA application session key.

[0127] Here, when the method is applied to a GBA system, the first key is a GBA application session key, When the above method is applied to an AKMA system, the first key is the AKMA application session key.

[0128] In some embodiments, transmitting data uplink to the first device is: Transmitting data directly to the first device, This includes transmitting uplink data to a second device, wherein the uplink data is transmitted from the second device to the first device.

[0129] Here, the transmission of uplink data from the second device to the first device may be either a pass-through to the first device or the uplink data may be transmitted to the first device after the corresponding modifications have been made.

[0130] In some embodiments, when the first device communicates directly with the terminal, the uplink data and / or the instruction message are It is transmitted based on at least one of the following communication protocols: HTTP, CoAP, MQTT, or a preset private protocol.

[0131] In some embodiments, when the first device communicates with the terminal via the second device, the uplink data and / or instruction messages are transmitted based on the HTTP communication protocol.

[0132] In some embodiments, the method further The process includes sending a first message to a second device, the first message including identifier information for several first devices, the several first devices being those that have already established an application security association with the terminal and are provided services by the second device.

[0133] Here, the aforementioned several first devices are several first devices that have already established an application security association with the terminal and are provided with services by the second device. Alternatively, the aforementioned several first devices can be described as including several first devices that have already established an application security association with the terminal and are provided with services by the second device.

[0134] Some of the aforementioned can also be described as at least one, representing one or more. Here, "plural" represents two or more.

[0135] The aforementioned services refer to the provision by the second device of security services such as identity authentication and application session keys.

[0136] When the above method is applied to a GBA system or an extended GBA system, establishing an application security association means that, before initiating the rebootstrap execution process, the terminal has already completed identity authentication by the extended GBA mechanism and established a security channel with a first device (e.g., a server) based on a shared first key obtained from a second device (e.g., a NAF and / or AP), thereby enabling secure communication with the first device.

[0137] In some embodiments, the method further This includes receiving a second message transmitted by a second device, the second message including an update result in which all or part of the first device updates the first key and / or key lifetime.

[0138] In some embodiments, the method further This includes generating and storing a new corresponding first key for each first device based on the second key, Here, the second key is a shared key negotiated by the terminal and the second device by re-executing the GBA bootstrap procedure and the GBA bootstrap security association usage procedure.

[0139] Here, considering the case where there are multiple first devices, and assuming that the first device is a server, when one of the servers triggers the execution of the terminal's rebootstrap flow, that server must update its first key, and then update the first keys of the remaining servers. The updated first key is a shared key between the terminal and each server.

[0140] Here, the terminal can calculate a new first key corresponding to the server based on the second key. For example, a method can be employed to generate a GBA application session key based on a shared key (e.g., a GBA session key). The calculation method is not limited here.

[0141] Figure 8 is a schematic flowchart of yet another communication method according to an embodiment of the present disclosure. As shown in Figure 8, the method may be applied to a second device. The method includes the following steps.

[0142] In step 801, the first message transmitted by the terminal is received, and the first message includes several identifiers of the first device. Here, the aforementioned first devices are several first devices that have already established an application security association with the terminal and are provided with services by the second device.

[0143] In actual application, when the method is applied to a GBA system or an extended GBA system, the first device may be a server, and the second device may include a NAF and / or AP.

[0144] In actual application, when the method is applied to an AKMA system or an extended AKMA system, the first device may include an AF and / or a server, and the second device may include at least one of AAnF, AAP, AP, and NEF.

[0145] In the embodiments of this disclosure, the names of the first and second devices are not limited, and it is sufficient that they implement the functions of the first and second devices.

[0146] A key push method is provided to achieve key updates and pushes in actual application. In some embodiments, the method further... Based on the identifier information of several first devices in the first message, a new first key and / or key lifetime corresponding to each first device is generated, This includes transmitting a new first key and / or key lifetime to the corresponding first device.

[0147] Here, we provide a first type of key push method, assuming that the second device includes a NAF and / or an AP, and the first device is a server. When the second device (e.g., the NAF and / or AP) receives a first message from a terminal that includes identifier information for each first device (e.g., a server), it generates an updated first key and / or key lifetime for each server based on the identifier information for each server, and actively pushes the updated first key and / or key lifetime to each server.

[0148] In actual application, an alternative key push method is provided to achieve key updates and pushes. In some embodiments, the method further, The method involves sending a third message to each first device based on the identifier information of several first devices in the first message, wherein the third message includes the identifier information of the corresponding first device. Receiving the fourth message transmitted by each first device, To generate a corresponding new first key and / or key lifetime for each first device, This includes transmitting the corresponding new first key and / or key lifetime to each first device.

[0149] Here, we provide a second type of key push method, assuming that the second device includes a NAF and / or an AP, and the first device is a server. When the second device (e.g., the NAF and / or AP) receives a first message from a terminal accompanied by identifier information for each server, it sends an Application Request to each server based on the identifier information, and each server subsequently replies with a fourth message (e.g., a User Info Request). When the NAF and / or AP receives the User Info Requests replied by each server, it generates a corresponding new first key and / or key lifetime for each server and actively pushes the new first key and / or key lifetime to each server.

[0150] Here, the key generation and key push flows for each server can occur together. That is, when the NAF and / or AP receive all User Info Requests, they uniformly generate a new first key and / or key lifetime for each server and then uniformly push it. Alternatively, the key generation and key push flows for each server can occur separately. That is, when a User Info Request is received from any server, a new first key and / or key lifetime for that server is generated and immediately pushed.

[0151] In some embodiments, the method further Determining the key transmission mode adopted by the aforementioned first devices, If the first device adopts push mode, a new first key and / or key lifetime corresponding to the first device is generated based on the identifier information of the first device, the new first key and / or key lifetime is transmitted to the corresponding first device, and / or, if the first device adopts request mode, a third message accompanied by the identifier information of the first device is transmitted to the first device based on the identifier information of the first device. Receiving the fourth message transmitted by the first device, To generate a new first key and / or key lifetime corresponding to the first device, This includes transmitting a new first key and / or key lifetime to the first device.

[0152] Here, the second device can first determine whether the first device (server) adopts push mode or request mode. If push mode is adopted, the second device adopts a type 1 key push method, and if request mode is adopted, the second device adopts a type 2 key push method.

[0153] In some embodiments, the method further This includes generating and storing a new corresponding first key for each first device based on the second key, Here, the second key is a shared key negotiated by the terminal and the second device by re-executing the GBA bootstrap procedure and the GBA bootstrap security association usage procedure.

[0154] Here, the second device can calculate a new first key corresponding to the server based on the second key. For example, it can employ a method of generating a GBA application session key based on a shared key (e.g., a GBA session key). The calculation method is not limited here.

[0155] In some embodiments, the method further To receive the result of successful reception of a new first key and / or key lifetime by each first device, Receiving the result of failure to receive a new first key and / or key lifetime for each first device, This includes at least one of the following: not receiving a result indicating successful reception of a new first key and / or key lifetime by the first device.

[0156] In some embodiments, the method further This includes sending a second message to the terminal, the second message including an update result in which all or some of the first devices update the first key and / or key lifetime.

[0157] Here, considering the case where there are multiple first devices (e.g., servers), if one of the servers triggers the terminal to execute the rebootstrap flow, that server must update its first key, and then update the first keys of the remaining servers. Accordingly, the terminal can obtain the update result where all or some of the first devices update their first keys and / or key lifetimes.

[0158] In some embodiments, the method further Receiving an instruction message from the first device, the instruction message being used to instruct the terminal to perform a rebootstrap operation, This includes sending the aforementioned instruction message to the terminal.

[0159] In some embodiments, the method further The process involves receiving uplink data from a terminal, wherein the uplink data includes at least business data encrypted with a first key. This includes transmitting the aforementioned uplink data to the first device.

[0160] Figure 9 is a schematic flowchart of a rebootstrap method for an extended GBA system according to an embodiment of the present disclosure, and as shown in Figure 9, the method includes the following steps.

[0161] In step 901, the UE sends data up to the Server, which may include business data information encrypted and protected with the GBA application session key K*.

[0162] Here, data transmission can be implemented using any application layer communication protocol such as HTTP, CoAP, MQTT, or a private protocol.

[0163] In step 902, for some reason, the Server triggers the UE to re-execute the GBA authentication mechanism, re-negotiating to obtain the GBA application session key K*.

[0164] Here, we provide some examples of the following reasons, which can be set in practice to include, but not be limited to, the following reasons.

[0165] (1) The Server does not have a locally valid GBA application session key K*. For example, K* may have become invalid or no longer be new, or K* may have already exceeded its key lifetime or will soon exceed its key lifetime. (2) K* fails to meet the key validity conditions set by the Server based on the security policy. For example, K* may have reached its maximum number of reuses. (3) Failure to obtain K*. For example, the B-TID required to obtain K* has expired, so the Server failed to obtain K* from the NAF and / or AP. (4) Other situations include, for example, when recovering from an abnormal state, the Server needs to actively re-establish the application layer security association with the UE, and the K* shared between the Server and the UE may not match.

[0166] In step 903, the Server sends a GBA reboot bootstrapping instruction message back to the UE.

[0167] Here, the specific format of the GBA rebootstrap instruction message depends on the application layer communication protocol used and is not limited thereto.

[0168] In step 904, upon receiving the GBA rebootstrap instruction message, the UE restarts the GBA bootstrap flow to the BSF.

[0169] In this case, the UE can directly access the Server via IP network routing. The UE and Server can interact using any application layer communication protocol, such as HTTP, CoAP, MQTT, or private protocols, but are not limited to those mentioned here.

[0170] Figure 10 is a schematic flowchart of a rebootstrap method for another extended GBA system according to an embodiment of the present disclosure. As shown in Figure 10, the method includes the following steps:

[0171] In step 1001, the UE sends an HTTP message to the Server via the NAF and / or AP, which may include business data information encrypted and protected with the GBA application layer session key K*.

[0172] In step 1002, the NAF and / or AP forward the HTTP messages sent by the UE to the Server.

[0173] In step 1003, for some reason, the Server triggers the UE to re-execute the GBA authentication mechanism, re-negotiate, and obtain the GBA application layer session key K*.

[0174] Here, the aforementioned reasons could be one or more of the methods shown in Figure 9, and their explanation is omitted here.

[0175] In step 1004, the Server returns an HTTP 401 Unauthorized message (equivalent to an instruction message).

[0176] In step 1005, the NAF and / or AP forward the HTTP 401 Unauthorized message to the UE.

[0177] In step 1006, upon receiving an HTTP 401 Unauthorized message, the UE restarts the GBA bootstrap flow to the BSF.

[0178] In this case, the UE can access the Server via NAF and / or AP network elements through IP network routing. Interaction between each network element is performed using the HTTP protocol, in which case the uplink encrypted data transmission message carrying user business data is an HTTP message, and the GBA rebootstrap instruction message is an HTTP 401 Unauthorized message.

[0179] According to the method of the embodiment of this disclosure, if a situation arises in which it is necessary to restart the GBA mechanism during the process in which the UE and Server complete GBA security authentication and securely perform data interaction based on the GBA application layer session key K* obtained by negotiation, the Server executes a GBA rebootstrap flow, and the security association between the UE and the Server is re-established. Depending on the message transmission method, there are specifically two implementation methods. One implementation method is direct transmission, which is specifically the GBA rebootstrap flow when application layer data is directly transmitted, as shown in Figure 9. The other implementation method is relay transmission via NAF and / or AP, which is specifically the GBA rebootstrap flow when application layer data is relayed via NAF and / or AP network elements, as shown in Figure 10.

[0180] Figure 11 is a schematic flowchart of a rebootstrap method for an extended AKMA system according to an embodiment of the present disclosure. As shown in Figure 11, the method includes the following steps.

[0181] In step 1101, the UE sends upstream data to the AF and / or Server, which may include business data information encrypted and protected with the AKMA application layer session key KA*.

[0182] Data transmission can be implemented using any application layer communication protocol, such as HTTP, CoAP, MQTT, or a private protocol.

[0183] In step 1102, for some reason, the AF and / or Server trigger the UE to re-execute the AKMA security access and authentication mechanism, re-negotiate to obtain the AKMA application layer session key KA*.

[0184] Here, we provide some examples of the following reasons, which can be set in practice to include, but not be limited to, the following reasons.

[0185] (1) The Server does not have a locally valid AKMA application tier session key KA*. For example, KA* may have become invalid or no longer be new, or KA* may have already exceeded its key lifetime or will soon exceed its key lifetime. (2) KA* fails to meet the key validity conditions set by AF and / or Server based on the security policy. For example, KA* may have reached its maximum number of reuses. (3) Failed to obtain KA*. For example, the B-TID required to obtain KA* has expired, so AF and / or Server failed to obtain KA* from AAnF and / or AAP. (4) Other situations include, for example, when recovering from an abnormal state, the AF and / or Server need to actively re-establish the application layer security association with the UE, and the KA* shared between the AF and / or Server and the UE do not match.

[0186] In step 1103, the AF and / or Server send an AKMA rebootstrap instruction message back to the UE.

[0187] Here, the specific format of the AKMA rebootstrap instruction message depends on the application layer communication protocol used and is not limited thereto.

[0188] In step 1104, upon receiving a rebootstrap instruction message, the UE restarts the AKMA processing flow for AAnF and / or AAP, thereby achieving AKMA rebootstrap.

[0189] For extended AKMA systems, if the AF and / or Server need to reset the AKMA operating state, a rebootstrap flow can be used to cause the terminal to re-execute the AKMA security access and authentication flow, thereby achieving an AKMA reset for the UE.

[0190] Figure 12 is a schematic flowchart of a rebootstrap method for another extended AKMA system according to an embodiment of the present disclosure. As shown in Figure 12, the method includes the following steps.

[0191] In step 1201, the UE transmits uplink data to the AAnF and / or AAP, which may include business data information encrypted and protected with the AKMA application layer session key KA*.

[0192] In step 1202, AAnF and / or AAP forward the HTTP messages sent by the UE to AF and / or Server.

[0193] In step 1203, for some reason, the AF and / or Server trigger the UE to re-execute the AKMA security access and authentication mechanism, re-negotiate to obtain the AKMA application layer session key KA*.

[0194] Here, the aforementioned reasons could be one or more of the methods shown in Figure 11, and their explanation is omitted here.

[0195] In step 1204, the AF and / or Server send an AKMA rebootstrap instruction message back to the AAnF and / or AAP.

[0196] In step 1205, AAnF and / or AAP forward the AKMA rebootstrap instruction message to the UE.

[0197] In step 1206, when the UE receives the AKMA rebootstrap instruction message, the UE restarts the AKMA processing flow for AAnF and / or AAP to perform the AKMA rebootstrap.

[0198] In addition to employing the direct transmission method shown in Figure 11, in the case of extended AKMA systems, there are situations in which messages interacting between the UE and AF and / or Server are transferred via network elements such as AAP and NEF. That is, the method shown in Figure 12 may be adopted, and the AKMA system may implement the rebootstrap processing flow by transferring messages via network elements such as AAP and NEF.

[0199] The following provides a flow of a specific method for rebootbootstrapping a GBA system with multiple servers. As shown in Figure 13, the third device is the BSF, the second device includes the NAF and / or AP, and the first device includes Server1, Server2, and Server3. The method includes the following steps.

[0200] In step 1301, the UE sends an HTTP message to Server1 via NAF and / or AP, which may include business data information encrypted and protected with K*.

[0201] In step 1302, for some reason, Server1 triggers the UE to re-execute the GBA authentication mechanism, re-negotiate, and obtain the GBA application layer session key K*1.

[0202] Here, the aforementioned reason could be one or more of the methods shown in Figure 9, and the explanation is omitted here. For example, the Server may not have a locally valid GBA application layer session key K*1.

[0203] In step 1303, Server1 sends an HTTP / 1.1 401 Unauthorized message to the UE via NAF and / or AP.

[0204] Here, the Unauthorized message corresponds to an instruction message, which may include a reason for triggering a re-execution of the GBA authentication mechanism determined by Server1.

[0205] In step 1304, the UE restarts the GBA bootstrap flow to the BSF.

[0206] In step 1305, the UE restarts the NAF and / or AP and GBA bootstrap security association use flow.

[0207] The restart of the GBA bootstrap flow may be triggered by a Server (for example, Server1 in Figure 13), i.e., by executing step 1304 after steps 1301 to 1303, or it may be actively triggered by a UE, i.e., by the UE actively executing step 1304.

[0208] It is understood that the method may include steps 1301 to 1303, i.e., a Server may trigger the UE to start the GBA bootstrap flow, or the method may not include steps 1301 to 1303 and directly execute step 1304, i.e., the UE may actively restart the GBA bootstrap flow.

[0209] After performing steps 1304 and 1305, the UE and NAF and / or AP obtain a new GBA session key (corresponding to the second key), i.e., the UE and the NAF and / or AP re-execute the GBA bootstrap procedure and the GBA bootstrap security association usage procedure to obtain the negotiated shared key.

[0210] In step 1306, the UE calculates a new GBA application session key K* based on the new GBA session key for each Server where a GBA application security association has already been established before the rebootstrap. For example, A new K*1 is calculated for Server1, A new K*2 is calculated for Server2, Perform a new K*3 calculation for Server3.

[0211] In step 1307, the UE sends an Application Request to the NAF and / or AP.

[0212] Here, the Application Request corresponds to the first message, which may include identifier information for several first devices. These several first devices are servers that have already established an application security association with the terminal and are provided services by the second device.

[0213] For example, an Application Request can include the B-TID, Server1 FQDN, Server2 FQDN, and Server3 FQDN.

[0214] Here, FQDN represents the fully qualified domain name of a server, and each server's FQDN is globally unique.

[0215] In step 1308, the NAF and / or AP calculate a new GBA application session key K* for each Server based on the new GBA session key. For example, A new K*1 is calculated for Server1, Calculate a new K*2 for Server2, Calculate a new K*3 for Server3.

[0216] Here, the method for calculating K*1, K*2, and K*3 can be determined by prior negotiation between the UE and the NAF and / or AP, and both may employ the same mechanism. The method is not limited here.

[0217] In step 1309a, the NAF and / or AP send a Key Update to Server1.

[0218] Here, Key Update can include the updated GBA application session key K*1 and / or key lifetime.

[0219] For example, Key Update can include B-TID, Server1 FQDN, a new K*1, and key lifetime.

[0220] Here, Key Update represents a key update message, and key lifetime represents the key's lifespan.

[0221] In step 1310a, Server1 provides HTTP 200 OK feedback to the NAF and / or AP.

[0222] In step 1309b, the NAF and / or AP send a Key Update to Server2.

[0223] Here, Key Update can include the B-TID, Server2 FQDN, a new K*2, and key lifetime.

[0224] In step 1310b, Server2 provides HTTP 200 OK feedback to the NAF and / or AP.

[0225] In step 1309c, the NAF and / or AP send a Key Update to Server3.

[0226] Here, Key Update can include the B-TID, Server3 FQDN, a new K*3, and key lifetime.

[0227] In step 1310c, Server3 provides HTTP 200 OK feedback to the NAF and / or AP.

[0228] In step 1310, the NAF and / or AP send an HTTP 200 OK to the UE (Server1 FQDN, Server2 FQDN, Server3 FQDN).

[0229] Here, the NAF and / or AP can send the key update result (corresponding to the second message) to the UE, which is used to notify the UE whether some or all of the Servers have successfully updated the key and / or key lifetime.

[0230] In step 1311a, UE and Server1 communicate securely based on the new K*1.

[0231] In step 1311b, the UE and Server2 communicate securely based on the new K*2.

[0232] In step 1311c, the UE and Server3 communicate securely based on the new K*3.

[0233] The following provides a flow of a re - bootstrap method for a GBA system of another specific plurality of Servers. As shown in FIG. 14, the third device is the BSF, the second device includes the NAF and / or AP, and the first device includes Server1, Server2, and Server3. The method includes the following steps.

[0234] In step 1401, the UE sends an HTTP message to Server1 via the NAF and / or AP, and can carry business data information encrypted and protected by K* therein.

[0235] In step 1402, for some reason, Server1 triggers the UE to re - execute the GBA authentication mechanism and re - negotiate to obtain the GBA application layer session key K*1.

[0236] Here, the reason may be any one or more of the reasons in the method shown in FIG. 9, and the description is omitted here. For example, the Server may not have a locally valid GBA application layer session key K*1.

[0237] In step 1403, Server1 sends an HTTP / 1.1 401 Unauthorized message to the UE via the NAF and / or AP.

[0238] Here, the Unauthorized message is equivalent to an indication message, and can carry the reason for triggering the re - execution of the GBA authentication mechanism determined by Server1 therein.

[0239] In step 1404, the UE restarts the GBA bootstrap flow to the BSF.

[0240] In step 1405, the UE restarts the NAF and / or AP and GBA bootstrap security association use flow.

[0241] The restart of the GBA bootstrap flow may be triggered by a Server (for example, Server1 in Figure 13), i.e., by executing step 1404 after steps 1401 to 1403, or it may be actively triggered by a UE, i.e., by the UE actively executing step 1404.

[0242] It is understood that the method may include steps 1401 to 1403, i.e., a Server may trigger the UE to start the GBA bootstrap flow, or the method may not include steps 1401 to 1403 and directly execute step 1404, i.e., the UE may actively restart the GBA bootstrap flow.

[0243] After steps 1404 and 1405 are performed, the UE and NAF and / or AP obtain a new GBA session key (corresponding to the second key), i.e., the UE and the NAF and / or AP re-execute the GBA bootstrap procedure and the GBA bootstrap security association usage procedure to obtain the negotiated shared key.

[0244] In step 1406, a new GBA application session key K* is calculated for each Server where a GBA application security association has already been established before the rebootstrap, based on the new GBA session key. For example, A new K*1 is calculated for Server1, A new K*2 is calculated for Server2, A new K*3 will be calculated for Server3.

[0245] In step 1407, the UE sends an Application Request to the NAF and / or AP, which includes the B-TID, Server1 FQDN, Server2 FQDN, and Server3 FQDN.

[0246] In step 1408a, the NAF and / or AP send an Application Request to Server1, which includes the B-TID and Server1 FQDN.

[0247] In step 1409a, Server1 sends a User Info Request to the NAF and / or AP, and the User Info Request includes the B-TID and Server1 FQDN.

[0248] In step 1410a, the NAF and / or AP calculate a new GBA application session key K*1 for Server1 based on the new GBA session key.

[0249] In step 1411a, the NAF and / or AP send an HTTP 200 OK to Server1, with a new K*1 and key lifetime attached.

[0250] In step 1412a, Server1 sends HTTP 200 OK to NAF and / or AP.

[0251] In step 1408b, the NAF and / or AP send an Application Request to Server2, which includes the B-TID and Server2 FQDN.

[0252] In step 1409b, Server2 sends a User Info Request to the NAF and / or AP, and the User Info Request carries the B-TID and Server2 FQDN.

[0253] In step 1410b, the NAF and / or AP calculates a new GBA application session key K*2 for Server2 based on the new GBA session key.

[0254] In step 1411b, the NAF and / or AP sends an HTTP 200 OK to Server2, carrying the new K*2 and key lifetime.

[0255] In step 1412b, Server2 sends an HTTP 200 OK to the NAF and / or AP.

[0256] In step 1408c, the NAF and / or AP sends an Application Request to Server3, and the Application Request carries the B-TID and Server3 FQDN.

[0257] In step 1409c, Server3 sends a User Info Request to the NAF and / or AP, and the User Info Request carries the B-TID and Server3 FQDN.

[0258] In step 1410c, the NAF and / or AP calculates a new GBA application session key K*3 for Server3 based on the new GBA session key.

[0259] In step 1411c, the NAF and / or AP sends an HTTP 200 OK to Server2, carrying the new K*3 and key lifetime.

[0260] In step 1412c, Server3 sends HTTP 200 OK to the NAF and / or AP.

[0261] Here, for example, as shown in steps 1408 to 1412 above (e.g., steps 1408a to 1412a, steps 1408b to 1412b, steps 1408c to 1412c), when the NAF and / or AP receive the identifier information attached to each Server sent by the UE (i.e., the UE performs step 1407), it first sends an Application Request to each Server based on the identifier information of each Server (e.g., steps 1408a, 1408b, 1408c), and then each Server replies with a User Info Request (e.g., steps 1409a, 1409b, 1409c). When the NAF and / or AP receive a User Info Request returned by each Server, they generate a new corresponding first key for each Server (e.g., steps 1410a, 1410b, and 1410c) and proactively push the new first key to each Server (e.g., steps 1411a, 1411b, and 1411c).

[0262] Here, the key generation and key push flows for each server can occur together. That is, when NAF and / or AP receive all User Info Requests, they uniformly generate new keys for each server and then uniformly push them. Alternatively, the key generation and key push flows for each server can occur separately. That is, when a User Info Request is received for any server, a new key is generated for that server and immediately pushed.

[0263] In step 1413, the NAF and / or AP send an HTTP 200 OK to the UE, with the Server1 FQDN, Server2 FQDN, and Server3 FQDN attached.

[0264] In step 1414a, communication is made to security based on the new K*1.

[0265] In step 1414b, communication is made to security based on the new K*2.

[0266] In step 1414c, security is communicated based on a new K*3.

[0267] Figure 15 is a schematic flowchart of a method for determining a second key according to an embodiment of the present disclosure. As shown in Figure 15, the terminal and a second device (e.g., NAF and / or AP) re-execute the GBA bootstrap procedure and the GBA bootstrap security association usage procedure, and finally the terminal and the second device negotiate to determine a shared key (i.e., a second key, also called a GBA session key). The method includes the following steps.

[0268] Step 151 is the GBA bootstrap procedure. Specifically, Step 151 includes the following steps 1511-1517.

[0269] In step 1511, the UE sends an authentication request to the BSF, which is accompanied by a user identifier (UE ID).

[0270] In step 1512, the BSF obtains an authentication vector (AV) from the HSS or UDM based on the user identifier.

[0271] The authentication vector is used by the BSF to estimate the GBA session intermediate key Ks.

[0272] In step 1513, the BSF responds to the UE by sending an HTTP 401 message (with RAND and AUTN attached) instructing the UE to use GBA authentication.

[0273] Here, RAND is a random number and AUTN is an authentication token.

[0274] In step 1514, the UE executes AKA to verify AUTH, generates RES, and requests permission for RES from the BSF.

[0275] In step 1515, BSF verifies RES and calculates Ks = CK || IK.

[0276] Here, RES is the user response, CK is the cipher key, and IK is the integrity key.

[0277] In step 1516, an HTTP 200 OK is sent to the UE, and the B-TID and the corresponding key lifetime (Key lifetime) are attached.

[0278] In step 1517, UE calculates Ks = CK || IK, and then derives Ks_NAF.

[0279] Step 152 is the procedure for using GBA bootstrap security association. Specifically, Step 152 includes the following steps 1521-1524.

[0280] In step 1521, the UE sends an application request to the NAF, to which the B-TID is attached.

[0281] In step 1522, the NAF sends a request to the BSF to generate a Ks_NAF, to which the B-TID is attached.

[0282] In step 1523, the BSF generates a Ks_NAF (i.e., the GBA session key) based on the Ks corresponding to the B-TID and sends the Ks_NAF to the NAF.

[0283] In step 1524, the NAF saves Ks_NAF and sends an HTTP 200 OK to the UE.

[0284] Regarding the method for determining the second key, the method shown in Figure 15 above may be adopted, or other methods may be used. For example, the UE and the second device (NAF and / or AP) may negotiate and determine it according to certain rules, or according to a predefined protocol. The method for determining the second key is not limited.

[0285] Figure 16 is a schematic diagram of the structure of one communication device according to an embodiment of the present disclosure. As shown in Figure 16, the device is applied to a first device, and the device, The system includes a first transmitting module configured to send instruction messages to a terminal, which are used to instruct the terminal to perform a rebootstrap operation.

[0286] In addition, while the above-described explanation focused solely on the division of each program module when the communication device according to the above embodiment implements the corresponding communication method, in actual application, the above processes can be assigned to different program modules as needed to complete the process. In other words, the internal structure of the first device is divided into different program modules to complete all or part of the above-described processes. Furthermore, the device according to the above embodiment belongs to the same concept as the method embodiment shown in Figure 6, and details of its specific implementation process can be found in the method embodiment, so the explanation is omitted here.

[0287] Figure 17 is a schematic diagram of the structure of another communication device according to the present disclosure. As shown in Figure 17, the device is applied to a terminal, and the device, A second receiving module configured to receive instruction messages from a first device, wherein the instruction messages are used to instruct a terminal to perform a rebootstrap operation, It includes a second transmitting module configured to send a rebootstrap request message to a third device.

[0288] In addition, while the above-described explanation focused solely on the division of each program module when the communication device according to the above embodiment implements the corresponding communication method, in actual application, the above processes can be assigned to different program modules as needed to complete the process. In other words, the internal structure of the terminal can be divided into different program modules to complete all or part of the above-described processes. Furthermore, the device according to the above embodiment belongs to the same concept as the method embodiment shown in Figure 7, and details of its specific implementation process can be found in the method embodiment, so the explanation is omitted here.

[0289] Figure 18 is a schematic diagram of yet another communication device according to an embodiment of the present disclosure. As shown in Figure 18, the device is applied to a second device, and the device is The system includes a third receiving module configured to receive a first message transmitted by a terminal, the first message containing identifier information for several first devices, the several first devices being several first devices that have already established an application security association with the terminal and are serviced by the second device.

[0290] Although the above-described explanation focused solely on the division of each program module when the communication device according to the above embodiment implements the corresponding communication method, in actual application, the above processing can be assigned to different program modules as needed to complete the process. In other words, the internal structure of the second device is divided into different program modules to complete all or part of the above-described processing. Furthermore, the device according to the above embodiment belongs to the same concept as the method embodiment shown in Figure 8, and details of its specific implementation process can be found in the method embodiment, so the explanation is omitted here.

[0291] Figure 19 is a schematic diagram of the structure of one communication device according to an embodiment of the present disclosure. As shown in Figure 19, the communication device 190 includes a processor 1901 and a memory 1902 for storing computer programs that can be executed by the processor.

[0292] When the communication device is applied to the first device, the processor 1901 is configured to send an instruction message to the terminal when executing the computer program, and the instruction message is used to instruct the terminal to perform a rebootstrap operation. Specifically, the communication device can further perform the method shown in Figure 6, which is based on the same concept as the method embodiment shown in Figure 6, and details of its specific implementation process should be referred to the method embodiment, and will not be explained here.

[0293] When the communication device is applied to a terminal, the processor 1901 is configured to receive an instruction message from the first device when executing the computer program, the instruction message being used to instruct the terminal to perform a rebootstrap operation, and to send a rebootstrap request message to the third device. Specifically, the communication device can further perform the method shown in Figure 7, which is based on the same concept as the method embodiment shown in Figure 7, and details of its specific implementation process should be referred to the method embodiment, and will not be explained here.

[0294] When the communication device is applied to the second device, the processor 1901 is configured to receive a first message transmitted by the terminal when executing the computer program, the first message containing identifier information of several first devices, the several first devices being several first devices that have already established an application security association with the terminal and are provided services by the second device. Specifically, the communication device can further perform the method shown in Figure 8, which belongs to the same concept as the method embodiment shown in Figure 8, and the details of its specific implementation process should be referred to the method embodiment, and will not be explained here.

[0295] In actual application, the communication device 190 may further include at least one network interface 1903. Each component within the communication device 190 is coupled via a bus system 1904. It is understood that the bus system 1904 is used to enable connection communication between these components. The bus system 1904 includes a data bus, as well as a power bus, a control bus, and a status signal bus. However, for clarity, in Figure 19, the various buses are denoted as the bus system 1904. Here, the number of processors 1901 may be at least one. The network interface 1903 is used for wired or wireless communication between the communication device 190 and other devices.

[0296] In the embodiments of this disclosure, the memory 1902 is used to store various types of data in order to support the operation of the communication device 190.

[0297] The methods according to the embodiments of the present disclosure are applied to or implemented by the processor 1901. The processor 1901 may be an integrated circuit chip having signal processing capabilities. In implementation, each step of the method can be executed by integrated logic circuits of hardware within the processor 1901 or by instructions in software form. The processor 1901 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 1901 can implement or execute each method, step and logic block diagram according to the embodiments of the present disclosure. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods according to the embodiments of the present disclosure can be combined and directly implemented as completion by a hardware decoding processor or by a combination of hardware and software modules within the decoding processor. The software modules may be located in a storage medium, which is located in memory 1902, and the processor 1901 reads information in memory 1902 and combines its hardware to complete the steps of the method.

[0298] In exemplary embodiments, the communication device 190 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontroller units (MCUs), microprocessors, or other electronic components used to perform the above method.

[0299] Embodiments of this disclosure further provide computer-readable storage media on which computer programs are stored.

[0300] When the computer-readable storage medium is applied to the first device, the computer program, when executed by the processor, performs the action of sending an instruction message to the terminal, and the instruction message is used to instruct the terminal to perform a rebootstrap operation. Specifically, the computer program can further perform the method shown in Figure 6, which belongs to the same concept as the method embodiment shown in Figure 6, and the details of its specific implementation process should be referred to the method embodiment, and will not be explained here.

[0301] When the computer-readable storage medium is applied to a terminal, the computer program, when executed by the processor, receives an instruction message from a first device, which is used to instruct the terminal to perform a rebootstrap operation, and sends a rebootstrap request message to a third device. Specifically, the computer program can further perform the method shown in Figure 7, which is based on the same concept as the method embodiment shown in Figure 7, and details of its specific implementation process should be referred to the method embodiment, and will not be explained here.

[0302] When the computer-readable storage medium is applied to a second device, the computer program, when executed by the processor, performs the task of receiving a first message transmitted by a terminal, the first message includes identifier information of several first devices, the several first devices being several first devices that have already established an application security association with the terminal and are provided services by the second device. Specifically, the computer program can further perform the method shown in Figure 8, which belongs to the same concept as the method embodiment shown in Figure 8, and the details of its specific implementation process should be referred to the method embodiment, and will not be explained here.

[0303] In some embodiments relating to this disclosure, it should be understood that the disclosed apparatus and methods may be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the division of the units is only one logical functional division, and in actual implementation, there may be other division methods, such as multiple units or components being combined, integrated into another system, or some features being ignored or not performed. Furthermore, the combination, direct combination, or communication connection between each component shown or discussed may be an indirect combination or communication connection via some interface, apparatus, or unit, and may be in electrical, mechanical, or other forms.

[0304] The units described above as separation means may or may not be physically separated, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. To achieve the objectives of this embodiment, some or all of these units can be selected as needed.

[0305] Furthermore, each functional unit in each embodiment of this disclosure may be integrated into a single processing unit, each unit may stand alone as a single unit, or two or more units may be integrated into a single unit. The integrated unit may be implemented in hardware form, or in the form of a hardware plus software functional unit.

[0306] Those skilled in the art will understand that the implementation of all or some of the steps of the above-described method embodiment can be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium, and the steps of the above-described method embodiment are performed when the program is executed. The storage medium includes various media capable of storing program code, such as mobile storage devices, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0307] Alternatively, if the integrated units of the present disclosure are implemented in the form of software function modules and sold or used as independent products, they may be stored in a computer-readable storage medium. Based on this understanding, the essential or prior art-contributing portions of the technical solutions of the embodiments of the present disclosure can be embodied in the form of a software product, which is stored in a storage medium containing several instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods of each embodiment of the present disclosure. The storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, RAMs, magnetic disks, and optical disks.

[0308] Note that terms like "1st," "2nd," etc., do not indicate a specific order or priority, but rather are used to distinguish similar objects.

[0309] Furthermore, the technical solutions described in the embodiments of this disclosure may be combined in any way that does not conflict with each other.

[0310] The above are merely specific embodiments of the Disclosure, but the scope of protection of the Disclosure is not limited thereto. Within the scope of the art disclosed, a person skilled in the art can easily conceive of modifications and substitutions, all of which should fall within the scope of protection of the Disclosure. Therefore, the scope of protection of the Disclosure must be in accordance with the claims. [Explanation of Symbols]

[0311] 190 Communication equipment 1901 Processor 1902 memory 1903 Network Interface 1904 Bus System

Claims

1. A communication method performed by a first device, A method comprising sending an instruction message to a terminal, the instruction message being used to instruct the terminal to perform a rebootstrap operation.

2. The above method further, The process includes receiving uplink data from the aforementioned terminal, wherein the uplink data includes at least data encrypted with a first key, and the first key is a GBA application session key or an AKMA application session key. Sending the instruction message to the aforementioned terminal means The method according to claim 1, further comprising sending the instruction message to the terminal if the first key does not satisfy the key validity conditions set by the first device based on the security policy, or if it is necessary to trigger an update of the first key.

3. The first key does not satisfy the key validity conditions set by the first device based on the security policy. The first key has reached its maximum number of reuses, The first key has reached the usage time permitted by the application, The method according to claim 2, comprising at least one of the following: the first key is exposed to the outside.

4. Sending the instruction message to the aforementioned terminal means Sending the instruction message directly to the aforementioned terminal, The method according to claim 1, comprising transmitting the instruction message to a second device, wherein the instruction message is transmitted from the second device to the terminal.

5. Receiving the aforementioned uplink data from the aforementioned terminal means Receiving the uplink data transmitted directly by the aforementioned terminal, The method according to claim 2, comprising receiving the uplink data transmitted by the second device, wherein the uplink data is transmitted from the terminal to the second device.

6. When the first device communicates directly with the terminal, the uplink data and / or the instruction message are: The method according to any one of claims 1 to 5, wherein transmission is based on at least one protocol from among the Hypertext Transfer Protocol HTTP, the Restricted Application Protocol CoAP, the Message Queue Telemetry Transmission MQTT protocol, and a preset private protocol.

7. The method according to any one of claims 1 to 5, wherein when the first device communicates with the terminal via the second device, the uplink data and / or the instruction message are transmitted based on the HTTP protocol.

8. The above method further, The method according to claim 1, comprising receiving a new first key and / or key lifetime transmitted by a second device and updating the local first key and / or key lifetime.

9. The method according to any one of claims 1 to 8, wherein the method is applied to a general-purpose bootstrap architecture GBA system, the first device is a server, and the second device includes a network application function NAF and / or an authentication proxy AP.

10. The method according to any one of claims 1 to 8, wherein when the method is applied to an application layer authentication and key management AKMA system, the first device includes an AF and / or a server, and the second device includes at least one of an AKMA anchor function AAnF, an AKMA authentication proxy AAP, an AP, and an application function network element NEF.

11. A communication method performed by a terminal, Receiving an instruction message from a first device, the instruction message being used to instruct the terminal to perform a rebootstrap operation, A method including sending a rebootstrap request message to a third device.

12. Receiving the instruction message from the first device means Receiving the instruction message transmitted directly by the first device, The method according to claim 11, comprising receiving the instruction message transmitted by the second device, wherein the instruction message is transmitted from the first device to the second device.

13. The above method further, The method according to claim 11, comprising transmitting uplink data to the first device, wherein the uplink data includes at least data encrypted with a first key, the first key being a GBA application session key or an AKMA application session key.

14. Transmitting the uplink data to the first device is: Transmitting the uplink data directly to the first device, The method according to claim 13, comprising transmitting the uplink data to a second device, wherein the uplink data is transmitted from the second device to the first device.

15. The method according to any one of claims 11 to 14, wherein when the first device communicates directly with the terminal, the uplink data and / or the instruction message are transmitted based on at least one communication protocol from HTTP, CoAP, MQTT, and a preset private protocol.

16. The method according to any one of claims 11 to 14, wherein when the first device communicates with the terminal via the second device, the uplink data and / or the instruction message are transmitted based on the HTTP communication protocol.

17. The above method further, The method according to claim 11, comprising sending a first message to a second device, the first message including identifier information of at least one first device, the at least one first device having already established an application security association with the terminal and being serviced by the second device.

18. The above method further, The method according to claim 17, comprising receiving a second message transmitted by a second device, wherein the second message includes an update result in which all or part of the first device updates the first key and / or key lifetime.

19. The above method further, This includes generating and storing a new first key corresponding to each of the at least one first device based on the second key, The method according to claim 17, wherein the second key is a shared key negotiated by the terminal and the second device by re-executing the GBA bootstrap procedure and the GBA bootstrap security association usage procedure.

20. The method according to any one of claims 11 to 18, wherein, when the method is applied to a GBA system, the first device is a server, the second device includes a NAF and / or AP, and the third device is a bootstrap server function BSF.

21. The method according to any one of claims 11 to 18, wherein, when the method is applied to an AKMA system, the first device includes an AF and / or a server, the second device includes at least one of AAnF, AAP, AP, and NEF, and the third device includes an AAnF and / or AAP.

22. A communication method performed by a second device, A method comprising receiving a first message transmitted by a terminal, wherein the first message includes identifier information for at least one first device, and the at least one first device is one that has already established an application security association with the terminal and is serviced by the second device.

23. The above method further, Based on the identifier information of at least one first device in the first message, a new first key and / or key lifetime corresponding to each first device is generated, The method according to claim 22, comprising transmitting a new first key and / or key lifetime to a corresponding first device.

24. The above method further, The method involves transmitting a third message to each first device based on the identifier information of at least one first device in the first message, wherein the third message includes the identifier information of the corresponding first device. Receiving the fourth message transmitted by each first device, To generate a new first key and / or key lifetime corresponding to each first device, The method according to claim 22, comprising transmitting a corresponding new first key and / or key lifetime to each first device.

25. The above method further, Determining the key transmission mode adopted by at least one of the first devices, If the first device adopts push mode, a new first key and / or key lifetime corresponding to the first device is generated based on the identifier information of the first device, the new first key and / or key lifetime is transmitted to the corresponding first device, and / or, if the first device adopts request mode, a third message containing the identifier information of the first device is transmitted to the first device based on the identifier information of the first device. Receiving the fourth message transmitted by the first device, To generate a new first key and / or key lifetime corresponding to the first device, The method according to claim 22, further comprising transmitting a new first key and / or key lifetime to the first device.

26. The above method further, This includes generating and storing a new, corresponding first key for each first device based on the second key, The method according to any one of claims 22 to 25, wherein the second key is a shared key negotiated by the terminal and the second device by re-executing the GBA bootstrap procedure and the GBA bootstrap security association usage procedure.

27. The above method further, To receive the result of successful reception of a new first key and / or key lifetime by each first device, Receiving the result of failure to receive a new first key and / or key lifetime for each first device, The method according to any one of claims 23 to 25, comprising at least one of not receiving a result of successful reception of a new first key and / or key lifetime by the first device.

28. The above method further, The method according to claim 27, comprising sending a second message to the terminal, wherein the second message includes an update result in which all or some of the first devices update the first key and / or key lifetime.

29. The above method further, Receiving an instruction message from a first device, the instruction message being used to instruct the terminal to perform a rebootstrap operation, The method according to claim 22, further comprising sending the instruction message to a terminal.

30. The above method further, The process involves receiving uplink data from a terminal, wherein the uplink data includes at least business data encrypted with a first key. The method according to claim 22, further comprising transmitting the uplink data to the first device.

31. The method according to claim 22, wherein when the method is applied to a GBA system, the first device is a server and the second device includes a NAF and / or AP.

32. The method according to claim 22, wherein, when the method is applied to an AKMA system, the first device includes an AF and / or a server, and the second device includes at least one of AAnF, AAP, AP, and NEF.

33. A communication device applicable to the first device, A communication device comprising a first transmitting module configured to send instruction messages to a terminal, the instruction messages being used to instruct the terminal to perform a rebootstrap operation.

34. A communication device applied to a terminal, A second receiving module configured to receive instruction messages from a first device, wherein the instruction messages are used to instruct a terminal to perform a rebootstrap operation, A communication device including a second transmitting module configured to send a rebootstrap request message to a third device.

35. A communication device applicable to the second device, Includes a third receiving module configured to receive a first message transmitted by a terminal, A communication device wherein the first message includes identifier information for at least one first device, and the at least one first device is one first device that has already established an application security association with the terminal and is provided with services by the second device.

36. A communication device comprising memory, a processor, and a computer program stored in memory and executable on the processor, wherein when the processor executes the computer program, the steps of the method according to any one of claims 1 to 10 are realized, or when the processor executes the computer program, the steps of the method according to any one of claims 11 to 21 are realized, or when the processor executes the computer program, the steps of the method according to any one of claims 22 to 32 are realized.

37. A computer-readable storage medium storing a computer program, wherein when the computer program is executed on a processor, it realizes a step according to any one of claims 1 to 10, or when the computer program is executed on a processor, it realizes a step according to any one of claims 11 to 21, or when the computer program is executed on a processor, it realizes a step according to any one of claims 22 to 32.

Images