Authentication methods, devices, media and chips
By introducing an untrusted first agent entity outside the 3GPP operator domain, the load problem caused by the interaction between user equipment and application function entities is solved, achieving the effects of reducing the load of the target entity and improving the efficiency of user equipment.
Patent Information
- Application Number
- CN202280001673.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-05-09
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2042-05-09
AI Technical Summary
In wireless communication systems, the interaction between user equipment and application function entities increases the load on application function entities and reduces their efficiency, especially among untrusted entities providing application functions outside the 3GPP operator domain. Existing technologies have failed to effectively address this issue.
By introducing a unified, untrusted first agent entity outside the 3GPP operator domain to provide authentication functionality, it is possible to determine whether the user equipment and the target entity have communication permissions, and to perform identity authentication if the permissions are granted. This reduces the load on the target entity and improves the efficiency of the user equipment.
By using a unified first agent entity to implement permission and identity authentication between user devices and multiple target entities, the load on target entities is reduced, their efficiency is improved, and the authentication process for user devices is simplified.
Smart Images

Figure CN117378231B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of communication technology, and more specifically, to an authentication method, apparatus, medium, and chip. Background Technology
[0002] In wireless communication systems, 3GPP (3rd Generation Partnership Project) defines session security protection functions between User Equipment (UE) and application functions, and proposes an application-based key management method, abbreviated as AKMA (Authentication and Key Management for Applications based on 3GPP credentials).
[0003] In related technologies, user equipment can interact with application function (AF) entities based on AKMA to determine the user equipment's access permissions to the application function (AF) entity in order to establish a secure session with the application function (AF) entity. This increases the load on the application function (AF) entity and reduces the efficiency of the AF entity. Summary of the Invention
[0004] To overcome the aforementioned problems in related technologies, this disclosure provides an authentication method, apparatus, medium, and chip.
[0005] According to a first aspect of the present disclosure, an authentication method is provided, applied to a user equipment, the method comprising:
[0006] From one or more first entities, determine the target entity for which communication is requested;
[0007] Determine the first permission request parameters based on the target entity;
[0008] The application session establishment request message is sent to the first proxy entity according to the first permission request parameters; the application session establishment request message is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions according to the first permission request parameters; the first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions, the first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions, and the first proxy entity provides authentication proxy functions for the first entity.
[0009] In response to receiving an application session establishment response message sent by the first proxy entity, determine whether the user equipment and the target entity have first communication permissions;
[0010] When the user equipment has first communication permissions with the target entity, identity authentication is performed through the first proxy entity.
[0011] According to a second aspect of the present disclosure, an authentication method is provided, applied to a first proxy entity, the method comprising:
[0012] The system receives an application session establishment request message sent by a user equipment. The application session establishment request message includes a first permission request parameter. The application session establishment request message is used to instruct the first proxy entity to determine whether the user equipment and the target entity have a first communication permission based on the first permission request parameter. The target entity is the entity that the user equipment determines from one or more first entities to request communication. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity.
[0013] Determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameters;
[0014] If the user equipment has first communication permission with the target entity, an application session establishment response message is sent to the user equipment, and the user equipment is authenticated.
[0015] According to a third aspect of the present disclosure, an authentication method is provided, applied to a second entity, the method comprising:
[0016] The system receives a first key request message sent by a first proxy entity. The first key request message includes a second permission request parameter, which is a parameter determined by the first proxy entity based on the first permission request parameter sent by the user equipment. The first permission request parameter is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameter. The target entity is an entity that the user equipment determines from one or more first entities to request communication. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity.
[0017] Obtain the first pending key information based on the second permission request parameters;
[0018] A first key response message is sent to the first agent entity based on the first pending key information.
[0019] According to a fourth aspect of the present disclosure, an authentication method is provided, applied to a third entity, the method comprising:
[0020] The system receives a third key request message sent by a second entity. The third key request message includes a third permission request parameter, which is a parameter determined by the second entity based on the second permission request parameter. The second permission request parameter is a parameter determined by a first proxy entity based on the first permission request parameter sent by the user equipment. The first permission request parameter is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions. The target entity is an entity that the user equipment determines from one or more first entities to request communication. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity.
[0021] Based on the third permission request parameters, determine whether the user equipment and the target entity have first communication permissions;
[0022] If the user equipment has first communication permission with the target entity, obtain third pending key information;
[0023] Based on the third pending key information, a third key response message is sent to the second entity, the third key response message including the third pending key information.
[0024] According to a fifth aspect of the present disclosure, an authentication method is provided, applied to a first entity, wherein the first entity is one or more entities; the method includes:
[0025] In response to receiving an authentication result notification message from a first proxy entity, the system communicates with the user equipment. The authentication result notification message indicates that the target entity has communication permissions with the user equipment. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity.
[0026] According to a sixth aspect of the present disclosure, an authentication apparatus is provided, applied to a user equipment, the apparatus comprising:
[0027] The target entity determination module is configured to determine the target entity for the requested communication from one or more first entities;
[0028] The parameter determination module is configured to determine the first permission request parameters based on the target entity;
[0029] The first message sending module is configured to send an application session establishment request message to the first proxy entity according to the first permission request parameters; the application session establishment request message is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions according to the first permission request parameters; the first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions, the first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions, and the first proxy entity provides authentication proxy functions for the first entity;
[0030] The first message receiving module is configured to determine whether the user equipment and the target entity have first communication permissions in response to receiving an application session establishment response message sent by the first agent entity.
[0031] The authentication module is configured to perform identity authentication through the first proxy entity when the user equipment has first communication permissions with the target entity.
[0032] According to a seventh aspect of the present disclosure, an authentication apparatus is provided, applied to a first proxy entity, the apparatus comprising:
[0033] The first proxy receiving module is configured to receive an application session establishment request message sent by a user equipment. The application session establishment request message includes a first permission request parameter. The application session establishment request message is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameter. The target entity is the entity that the user equipment determines from one or more first entities to request communication. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity.
[0034] The first agent determination module is configured to determine whether the user device and the target entity have first communication permissions based on the first permission request parameters.
[0035] The first proxy sending module is configured to send an application session establishment response message to the user equipment and to authenticate the user equipment when the user equipment and the target entity have first communication permissions.
[0036] According to an eighth aspect of the present disclosure, an authentication device is provided for use with a second entity, the device comprising:
[0037] The second receiving module is configured to receive a first key request message sent by a first proxy entity. The first key request message includes a second permission request parameter, which is a parameter determined by the first proxy entity based on the first permission request parameter sent by the user equipment. The first permission request parameter is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameter. The target entity is an entity that the user equipment determines from one or more first entities to request communication. The first entities include untrusted entities outside the 3GPP operator domain that provide application functions. The first proxy entity includes untrusted entities outside the 3GPP operator domain that provide authentication functions. The first proxy entity provides authentication proxy functions for the first entity.
[0038] The second key acquisition module is configured to acquire the first pending key information based on the second permission request parameters;
[0039] The second sending module is configured to send a first key response message to the first agent entity based on the first pending key information.
[0040] According to a ninth aspect of the present disclosure, an authentication device is provided for use with a third entity, the device comprising:
[0041] The third receiving module is configured to receive a third key request message sent by the second entity. The third key request message includes a third permission request parameter, which is a parameter determined by the second entity based on the second permission request parameter. The second permission request parameter is a parameter determined by the first proxy entity based on the first permission request parameter sent by the user equipment. The first permission request parameter is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameter. The target entity is an entity that the user equipment determines from one or more first entities to request communication. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity.
[0042] The third determining module is configured to determine whether the user equipment and the target entity have first communication permissions based on the third permission request parameters.
[0043] The third key module is configured to obtain third pending key information when the user equipment has first communication permission with the target entity;
[0044] The third sending module is configured to send a third key response message to the second entity based on the third pending key information, wherein the third key response message includes the third pending key information.
[0045] According to a tenth aspect of the present disclosure, an authentication apparatus is provided, applied to a first entity, wherein the first entity is one or more; the apparatus includes:
[0046] The first communication module is configured to communicate with the user equipment in response to receiving an authentication result notification message sent by a first proxy entity; the authentication result notification message is used to indicate that the target entity has communication permissions with the user equipment, the first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions, the first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions, and the first proxy entity provides authentication proxy functions for the first entity.
[0047] According to an eleventh aspect of the present disclosure, an authentication apparatus is provided, comprising:
[0048] processor;
[0049] Memory used to store processor-executable instructions;
[0050] The processor is configured to perform the steps of the authentication method provided in the first aspect of this disclosure.
[0051] According to a twelfth aspect of the present disclosure, an authentication apparatus is provided, comprising:
[0052] processor;
[0053] Memory used to store processor-executable instructions;
[0054] The processor is configured to perform the steps of the authentication method provided in the second aspect of this disclosure.
[0055] According to a thirteenth aspect of the present disclosure, an authentication apparatus is provided, comprising:
[0056] processor;
[0057] Memory used to store processor-executable instructions;
[0058] The processor is configured to perform the steps of the authentication method provided in the third aspect of this disclosure.
[0059] According to a fourteenth aspect of the present disclosure, an authentication apparatus is provided, comprising:
[0060] processor;
[0061] Memory used to store processor-executable instructions;
[0062] The processor is configured to perform the steps of the authentication method provided in the fourth aspect of this disclosure.
[0063] According to a fifteenth aspect of the present disclosure, an authentication apparatus is provided, comprising:
[0064] processor;
[0065] Memory used to store processor-executable instructions;
[0066] The processor is configured to perform the steps of the authentication method provided in the fifth aspect of this disclosure.
[0067] According to a sixteenth aspect of the present disclosure, a computer-readable storage medium is provided that stores computer program instructions thereon, which, when executed by a processor, implement the steps of the authentication method provided in the first aspect of the present disclosure.
[0068] According to a seventeenth aspect of the present disclosure, a computer-readable storage medium is provided that stores computer program instructions thereon, which, when executed by a processor, implement the steps of the authentication method provided in the second aspect of the present disclosure.
[0069] According to an eighteenth aspect of the present disclosure, a computer-readable storage medium is provided that stores computer program instructions thereon, which, when executed by a processor, implement the steps of the authentication method provided in the third aspect of the present disclosure.
[0070] According to a nineteenth aspect of the present disclosure, a computer-readable storage medium is provided that stores computer program instructions thereon, which, when executed by a processor, implement the steps of the authentication method provided in the fourth aspect of the present disclosure.
[0071] According to a twentieth aspect of the present disclosure, a computer-readable storage medium is provided that stores computer program instructions thereon, which, when executed by a processor, implement the steps of the authentication method provided in the fifth aspect of the present disclosure.
[0072] According to a twenty-first aspect of the present disclosure, a chip is provided, comprising: a processor and an interface; the processor is configured to read instructions to execute the steps of the authentication method provided in the first aspect of the present disclosure.
[0073] According to a twenty-second aspect of the present disclosure, a chip is provided, comprising: a processor and an interface; the processor is configured to read instructions to execute the steps of the authentication method provided in the second aspect of the present disclosure.
[0074] According to a twenty-third aspect of the present disclosure, a chip is provided, comprising: a processor and an interface; the processor is configured to read instructions to execute the steps of the authentication method provided in a third aspect of the present disclosure.
[0075] According to a twenty-fourth aspect of the present disclosure, a chip is provided, comprising: a processor and an interface; the processor is configured to read instructions to execute the steps of the authentication method provided in the fourth aspect of the present disclosure.
[0076] According to a twenty-fifth aspect of the present disclosure, a chip is provided, comprising: a processor and an interface; the processor is configured to read instructions to perform the steps of the authentication method provided in the fifth aspect of the present disclosure.
[0077] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects: determining a target entity requesting communication from one or more first entities; determining a first permission request parameter based on the target entity; sending an application session establishment request message to a first proxy entity based on the first permission request parameter; determining whether the user equipment and the target entity have first communication permissions in response to receiving an application session establishment response message sent by the first proxy entity; and performing identity authentication through the first proxy entity when the user equipment and the target entity have first communication permissions. The application session establishment request message is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameter; the first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions; the first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions; and the first proxy entity provides authentication proxy functions for the first entity. In this way, for untrusted first entities outside the 3GPP operator domain, the first proxy entity determines whether the user equipment has the first communication permission with the first entity, and performs user equipment authentication if the user equipment has the first communication permission. This allows some functions of the first entity to be implemented through the first proxy entity, thereby reducing the load on the first entity and improving its efficiency. Furthermore, the user equipment performs permission authentication and identity authentication with one or more first entities through a unified first proxy entity, which also reduces the complexity of authentication for the user equipment and improves its efficiency.
[0078] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description
[0079] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.
[0080] Figure 1 This is a schematic diagram illustrating a communication system to which an embodiment of the present disclosure is applicable, according to an exemplary embodiment.
[0081] Figure 2 This is a schematic diagram illustrating a 5G communication system according to an exemplary embodiment.
[0082] Figure 3 This is a flowchart illustrating an authentication method according to an exemplary embodiment.
[0083] Figure 4 This is a flowchart illustrating an authentication method according to an exemplary embodiment.
[0084] Figure 5 This is a flowchart illustrating an authentication method according to an exemplary embodiment.
[0085] Figure 6 This is a flowchart illustrating an authentication method according to an exemplary embodiment.
[0086] Figure 7 This is a flowchart illustrating an authentication method according to an exemplary embodiment.
[0087] Figure 8 This is a flowchart illustrating an authentication method according to an exemplary embodiment.
[0088] Figure 9 This is a flowchart illustrating an authentication method according to an exemplary embodiment.
[0089] Figure 10 This is a flowchart illustrating an authentication method according to an exemplary embodiment.
[0090] Figure 11 This is a flowchart illustrating an authentication method according to an exemplary embodiment.
[0091] Figure 12 This is a flowchart illustrating an authentication method according to an exemplary embodiment.
[0092] Figure 13 This is a block diagram illustrating an authentication device according to an exemplary embodiment.
[0093] Figure 14 This is a block diagram illustrating an authentication device according to an exemplary embodiment.
[0094] Figure 15This is a block diagram illustrating an authentication device according to an exemplary embodiment.
[0095] Figure 16 This is a block diagram illustrating an authentication device according to an exemplary embodiment.
[0096] Figure 17 This is a block diagram illustrating an authentication device according to an exemplary embodiment.
[0097] Figure 18 This is a block diagram illustrating an authentication device according to an exemplary embodiment.
[0098] Figure 19 This is a block diagram illustrating an authentication device according to an exemplary embodiment.
[0099] Figure 20 This is a block diagram illustrating an authentication device according to an exemplary embodiment. Detailed Implementation
[0100] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.
[0101] It should be noted that all actions involving the acquisition of signals, information, or data in this disclosure are carried out in compliance with the relevant data protection laws and policies of the country where the location is situated, and with authorization from the owner of the relevant device.
[0102] In this disclosure, terms such as "first" and "second" are used to distinguish similar objects and should not be construed as referring to a specific order or sequence. Furthermore, unless otherwise stated, in the description with reference to the accompanying drawings, the same reference numerals in different drawings denote the same elements.
[0103] In the description of this disclosure, unless otherwise stated, "multiple" means two or more, and other quantifiers are similar; "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple; "and / or" is a description of the relationship between related objects, indicating that there can be three relationships, for example, A and / or B can mean: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural.
[0104] Although operations are described in a specific order in the accompanying drawings in this disclosure, it should not be construed as requiring these operations to be performed in the specific order or serial order shown, or requiring all of the shown operations to obtain the desired result. In certain environments, multitasking and parallel processing may be advantageous.
[0105] In related technologies, user equipment (UE) can interact with application function (AF) entities based on AKMA to determine its access permissions to the AF entity, thereby establishing a secure session with the AF entity. However, message interactions caused by multiple UEs increase the load on the AF entity, reducing its efficiency. Furthermore, when multiple AF entities exist in the network, direct message interaction between the UE and the AF to determine access permissions also reduces efficiency for the UE.
[0106] To address the aforementioned issues, this disclosure provides an authentication method, apparatus, medium, and chip.
[0107] The implementation environment of the embodiments of this disclosure is described below.
[0108] The embodiments disclosed herein can be applied to 4G (4th Generation) network systems, such as Long Term Evolution (LTE) systems, or to 5G (5th Generation) network systems, such as access networks employing New Radio Access Technology (New RAT), Cloud Radio Access Network (CRAN), and other communication systems.
[0109] Figure 1This is a schematic diagram illustrating a communication system applicable to an embodiment of the present disclosure according to an exemplary embodiment. It should be noted that the embodiments of the present disclosure are not limited to... Figure 1 In the system shown, in addition, Figure 1 The entities in the text can be hardware, software based on function, or a combination of both. Figure 1 The entities shown can be entities in any communication network architecture, such as 4G, 5G, or 6G networks.
[0110] like Figure 1 As shown, the communication system may include: a first entity 101, a second entity 102, a third entity 103, a first proxy entity 110, and a user equipment 160. The first entity 101 may be one or more entities, for example, it may include: first entity 1011, first entity 1012, ..., first entity 101n, etc. The first proxy entity 110 may be connected to the one or more first entities 101 (e.g., via a wired network, a wireless network, or a combination of both). The first proxy entity may be connected to the second entity, the second entity may be connected to the third entity, and the user equipment may be connected to both the first proxy entity and the third entity.
[0111] In some embodiments, the first entity 101 may include an entity that provides application functions, the first agent entity 110 may include an entity that provides authentication agent functions, the second entity 102 may include an entity that provides network access functions, and the third entity 103 may include an entity that provides AKMA authorization and application key deduction functions. For example, the third entity 103 may be a functional entity that provides AKMA anchoring functions and authenticates the communication permissions between the user equipment and the first entity.
[0112] In some embodiments, the first entity may include an untrusted entity outside the 3GPP operator domain that provides application functionality, and the first proxy entity may include an untrusted entity outside the 3GPP operator domain that provides authentication functionality. The first proxy entity provides authentication proxy functionality for the first entity, and the first entity may include one or more entities.
[0113] For example, the first entity may include: an Application Function (AF) entity or an Application Server (SCS / AS); the first proxy entity may include an AKMA Authentication Proxy (AP) entity; the second entity may include: a Network Exposure Function (NEF) entity or a Service Capability Exposure Function (SCEF) entity; and the third entity may include: an AKMA Anchor Function (AAnF) entity.
[0114] Figure 2 This is a schematic diagram illustrating a 5G communication system according to an exemplary embodiment, such as... Figure 2 As shown, the communication system is Figure 1 The communication system shown is specifically applied in a 5G network. This communication system may include AF entity 1010, AP entity 1100, NEF entity 1020, and UE (User Equipment) 1600.
[0115] Figure 3 This is an authentication method illustrated according to an exemplary embodiment, which can be applied to user equipment in the aforementioned communication system. For example... Figure 3 As shown, the method may include:
[0116] S301. The user equipment determines the target entity for which communication is requested from one or more first entities.
[0117] For example, the first entity may include an entity that provides application functionality, such as an application functionality (AF) entity. The user equipment can determine the AF entity requesting communication based on user functional requirements.
[0118] S302. The user equipment determines the first permission request parameters based on the target entity.
[0119] In some embodiments, a first target entity identifier of the target entity may be obtained first, and a first permission parameter may be determined based on the first target entity identifier.
[0120] For example, the first target entity identifier may include one or more of the target entity's FQDN (Fully Qualified Domain Name), IP (Internet Protocol) address, and port number.
[0121] In some embodiments, the first permission request parameters can be obtained based on the first target entity identifier and the user equipment identifier that represents the user equipment identity.
[0122] The user equipment identifier may include the key identifier A-KID corresponding to the user equipment. The key identifier A-KID may be generated by the user equipment when registering to access the communication system, based on the user equipment's hardware information and the registration information sent by the communication system. The key identifier A-KID can uniquely identify a user equipment in the communication system.
[0123] For example, the first target entity identifier and the key identifier A-KID corresponding to the user equipment can be used as the first permission request parameters.
[0124] S303. The user equipment sends an application session establishment request message to the first agent entity based on the first permission request parameter.
[0125] The application session establishment request message can be used to instruct the first agent entity to determine whether the user device and the target entity have first communication permissions based on the first permission request parameter.
[0126] In some embodiments, the first proxy entity is connected to one or more first entities. For example, a unified first proxy entity can be set up in a trust domain or an edge node, and this first proxy entity can be connected to each first entity in that trust domain or edge node. When a user device requests to communicate with a target entity in that trust domain or edge node, an Application Session Establishment Request message can be sent to the first proxy entity.
[0127] In some embodiments, the first entity may include an untrusted entity outside the 3GPP operator domain that provides application functionality, and the first proxy entity may include an untrusted entity outside the 3GPP operator domain that provides authentication functionality. The first proxy entity provides authentication proxy functionality for the first entity, and the first entity may include one or more entities.
[0128] In some embodiments, the user equipment may pre-configure the proxy domain name (e.g., FQDN) of the first proxy entity, through which the user equipment may interact with the first proxy entity for message exchange or data transmission.
[0129] S304. Upon receiving an application session establishment response message from the first agent entity, the user equipment determines whether the user equipment and the target entity have first communication permissions.
[0130] In some embodiments, upon receiving the application session establishment response message, the user equipment may determine that it has first communication permission with the target entity.
[0131] Conversely, if the user device does not receive the application session establishment response message within a preset time, it can be determined that the user device does not have the first communication permission with the target entity.
[0132] In other embodiments, the user equipment may determine that it has first communication permission with the target entity if it receives an application session establishment response message that includes success indication information.
[0133] Conversely, if the application session establishment response message received by the user equipment does not contain a success indication or contains a failure indication, it can be determined that the user equipment and the target entity do not have first communication permissions. The success indication can be any pre-set indication.
[0134] In other embodiments, the user equipment may determine that it has first communication permission with the target entity if it receives an application session establishment response message and the application session establishment response message does not contain failure indication information.
[0135] Conversely, if the application session establishment response message received by the user equipment contains failure indication information, it can be determined that the user equipment does not have first communication authority with the target entity. This failure indication information can be any pre-set error code.
[0136] S305. When the user equipment has first communication authority with the target entity, the user equipment performs identity authentication through the first proxy entity.
[0137] For example, a user equipment can generate an entity key K corresponding to a target entity based on the target entity's FQDN. AF And based on the entity key K AF Authenticate your identity with the first agent entity.
[0138] It should be noted that the user equipment can perform identity authentication by referring to the implementation in related technologies. For example, identity authentication can be performed based on the entity key information corresponding to the target entity, or it can be performed based on the user key information corresponding to the user equipment and the entity key information corresponding to the target entity. This disclosure does not limit this.
[0139] Using the above method, a target entity requesting communication is determined from one or more first entities; a first permission request parameter is determined based on the target entity; an application session establishment request message is sent to a first proxy entity based on the first permission request parameter; in response to receiving an application session establishment response message sent by the first proxy entity, it is determined whether the user equipment and the target entity have first communication permissions; if the user equipment and the target entity have first communication permissions, authentication is performed through the first proxy entity. The application session establishment request message instructs the first proxy entity to determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameter; the first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions; the first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions; and the first proxy entity provides authentication proxy functions for the first entity. In this way, for untrusted first entities outside the 3GPP operator domain, the first proxy entity determines whether the user equipment has the first communication permission with the first entity, and performs user equipment authentication if the user equipment has the first communication permission. This allows some functions of the first entity to be implemented through the first proxy entity, thereby reducing the load on the first entity and improving its efficiency. Furthermore, the user equipment performs permission authentication and identity authentication with one or more first entities through a unified first proxy entity, which also reduces the complexity of authentication for the user equipment and improves its efficiency.
[0140] In some embodiments, the first communication permission described above may include one or more of the following:
[0141] Permission 1: The user device has access rights to the target entity.
[0142] Permission 2: The user device has access rights to the first agent entity.
[0143] Permission 3: The first proxy entity has proxy permissions for the target entity.
[0144] Permission 4: The target entity has permission to obtain the user identifier of the user device.
[0145] For example, if it is determined that the user equipment has access rights to the target entity, then the user equipment and the target entity may have first communication rights; or if it is determined that the user equipment has access rights to the first proxy entity and the first proxy entity has proxy rights to the target entity, then the user equipment and the target entity may have first communication rights; or if it is determined that the user equipment has access rights to the target entity, the user equipment has access rights to the first proxy entity, and the first proxy entity has proxy rights to the target entity, then the user equipment and the target entity may have first communication rights.
[0146] In some embodiments, having a first communication permission between a user equipment and a target entity may include: the user equipment having access to a first proxy entity, and the first proxy entity having proxy permission to the target entity; for example, the first communication permission may be used if the first proxy entity and the target entity have the same FQDN.
[0147] In other embodiments, having a first communication permission between the user equipment and the target entity may include: the user equipment having access permission to the target entity, and the user equipment having access permission to a first proxy entity, and the first proxy entity having proxy permission to the target entity; for example, this first communication permission may be used when the FQDN of the first proxy entity and the target entity are different.
[0148] In some embodiments, the first entity may include: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain; the first proxy entity may include an untrusted authentication proxy (AP) entity outside the 3GPP operator domain.
[0149] In this way, user equipment can communicate with AF entities outside the operator's domain through the AP.
[0150] In some embodiments, after successful authentication through the first proxy entity, the user equipment can communicate with the target entity.
[0151] For example, the user equipment can communicate directly with the target entity, or it can communicate with the target entity through a first proxy entity, such as by forwarding communication messages between the user equipment and the target entity through the first proxy entity.
[0152] In other embodiments, after successful authentication through the first proxy entity, the user equipment can also determine whether the proxy domain name of the first proxy entity is the same as the first domain name of the target entity. If the proxy domain name is different from the first domain name, communication with the target entity can be carried out.
[0153] Conversely, if the proxy domain name is the same as the first domain name, the user device and the target entity can be further determined through a secure session between the user device and the proxy entity to determine whether the user device and the target entity have second communication permissions; if they have second communication permissions, they can communicate with the target entity.
[0154] It should be noted that the aforementioned proxy domain name can be the fully qualified domain name (FQDN) corresponding to the first proxy entity, and the first domain name can be the fully qualified domain name (FQDN) corresponding to the target entity. In some scenarios, the first proxy entity and the target entity may use the same FQDN but different IP addresses or port numbers. In this scenario, the aforementioned first communication permission can indicate that the user device has access to the FQDN, but it does not necessarily indicate that the user device has access to the target entity corresponding to the IP address or port number. In this case, the second communication permission can be further determined through the secure session between the user device and the proxy entity.
[0155] Figure 4 This is an authentication method illustrated according to an exemplary embodiment, which can be applied to user equipment. For example... Figure 4 As shown, the method may include:
[0156] S401. When the user equipment has first communication authority with the target entity, the user equipment performs identity authentication through the first proxy entity.
[0157] S402. After successful authentication through the first agent entity, the user equipment establishes a secure session with the first agent entity.
[0158] For example, the secure session could be a TLS (Transport Layer Security) session, which can ensure confidentiality and data integrity of communications between the user equipment and the first proxy entity.
[0159] S403. The user equipment obtains the proxy domain name of the first proxy entity and the first domain name of the target entity.
[0160] In some embodiments, the proxy domain name can be the fully qualified domain name (FQDN) corresponding to the first proxy entity, and the first domain name can be the fully qualified domain name (FQDN) corresponding to the target entity.
[0161] S404. When the proxy domain name is the same as the first domain name, the user equipment determines whether the user equipment and the target entity have second communication permissions through a secure session.
[0162] S405. If it is determined that the user equipment and the target entity have second communication permissions, the user equipment shall communicate with the target entity.
[0163] Similarly, the user equipment can communicate directly with the target entity, or it can communicate with the target entity through the first proxy entity, for example, by forwarding communication messages between the user equipment and the target entity through the first proxy entity.
[0164] In this way, by authenticating the first and second communication permissions, even if the FQDN of the first proxy entity and the target entity are the same, it can be determined that the user equipment has access to the target entity, thereby further enhancing security.
[0165] In some embodiments, determining whether the user equipment and the target entity have second communication permissions through a secure session in step S404 above may include the following steps:
[0166] First, the user equipment sends a target entity service request message to the first agent entity through the aforementioned secure session.
[0167] For example, the target entity service request message may include a second target entity identifier, which is a protected entity identifier obtained by the user equipment based on the first target entity identifier; the target entity service request message is used to instruct the first agent entity to determine whether the user equipment and the target entity have second communication permissions based on the second target entity identifier.
[0168] In some embodiments, the second target entity identifier is an identifier determined after protecting the first target entity identifier corresponding to the target entity according to the requirements of a security session (e.g., a TLS session).
[0169] In other embodiments, the first target entity identifier can be directly used as the second target entity identifier, and the second target entity identifier can be transmitted through a secure session to protect the first target entity identifier and prevent the entity identifier from being tampered with during transmission.
[0170] Then, in response to receiving the target entity service response message sent by the first agent entity, the user equipment determines whether the user equipment and the target entity have the second communication permission.
[0171] In some embodiments, upon receiving a service response message from the target entity, the user equipment may determine that it has second communication permissions with the target entity.
[0172] Conversely, if the user equipment does not receive a service response message from the target entity within a preset time, it can be determined that the user equipment does not have the second communication permission with the target entity.
[0173] In other embodiments, the user equipment may determine that it has second communication permission with the target entity if it receives a service response message from the target entity and the target entity service response message contains success indication information.
[0174] Conversely, if the service response message received by the user equipment from the target entity does not contain success indication information, or contains failure indication information, it can be determined that the user equipment and the target entity do not have second communication permissions. The success indication information can be any pre-set indication information.
[0175] In other embodiments, the user equipment may determine that it has second communication permission with the target entity if it receives a service response message from the target entity and the target entity service response message does not contain failure indication information.
[0176] Conversely, if the service response message received by the user equipment from the target entity contains failure indication information, it can be determined that the user equipment and the target entity do not have second communication permissions. This failure indication information can be any pre-set error code.
[0177] In this way, the user equipment can determine whether the user equipment and the target entity have second communication permissions through a secure session.
[0178] In some embodiments, the second communication permission described above may include one or more of the following permissions:
[0179] Permission 6: The user device has access rights to the target entity.
[0180] Permission 7: The first proxy entity has proxy permissions for the target entity.
[0181] Permission 8: The target entity has permission to obtain the user identifier of the user device.
[0182] In this way, the reliability of authentication can be further improved by determining whether the user equipment and the target entity have second communication permissions through the secure session between the user equipment and the first agent entity.
[0183] Figure 5 This is an authentication method illustrated according to an exemplary embodiment, which can be applied to the first proxy entity in the aforementioned communication system. For example... Figure 5 As shown, the method may include:
[0184] S501, The first agent entity receives the application session establishment request message sent by the user equipment.
[0185] The application session establishment request message includes a first permission request parameter. The application session establishment request message is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameter. The target entity is the entity that the user equipment determines from one or more first entities to request communication. The first entity may include an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity may include an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity. The first entity may include one or more.
[0186] S502, the first agent entity determines whether the user equipment and the target entity have the first communication permission based on the first permission request parameters.
[0187] In this way, for untrusted first entities outside the 3GPP operator domain, the first proxy entity determines whether the user equipment has the first communication permission with the first entity, and performs user equipment authentication if the user equipment has the first communication permission. This allows some functions of the first entity to be implemented through the first proxy entity, thereby reducing the load on the first entity and improving its efficiency. Furthermore, the user equipment performs permission authentication and identity authentication with one or more first entities through a unified first proxy entity, which also reduces the complexity of authentication for the user equipment and improves its efficiency.
[0188] In some embodiments, the first agent entity may determine whether the user equipment and the target entity have first communication permissions by interacting with a key request message with the second entity. For example, this may include the following steps:
[0189] First, the first proxy entity determines the second permission request parameters based on the first permission request parameters.
[0190] In some embodiments, the first permission request parameter and the proxy entity identifier corresponding to the first proxy entity can be used as the second permission request parameter. For example, if the first permission request parameter includes the first target entity identifier of the target entity and the key identifier A-KID corresponding to the user equipment, then the second permission request parameter may include the first target entity identifier, the key identifier A-KID, and the proxy entity identifier corresponding to the first proxy entity.
[0191] In other embodiments, the first permission request parameter can be used as the second permission request parameter.
[0192] Next, the first agent entity sends a first key request message to the second entity.
[0193] For example, the second entity may include an entity that provides network access functionality. The first key request message may include the aforementioned second permission request parameters.
[0194] Next, the first agent entity receives the first key response message sent by the second entity.
[0195] The first key response message may include first pending key information, which is key information obtained by the second entity according to the second permission request parameters.
[0196] In some embodiments, the first pending key information may include the application key K corresponding to the target entity. AF .
[0197] In other embodiments, the first pending key information may include the application key K corresponding to the target entity. AF and key validity period K AF Expiration time.
[0198] In some embodiments, the first key response message may further include a first user identifier of the user equipment. The first user identifier may be any identifier used to represent the user equipment, such as a Generic Public Subscription Identifier (GPSI) corresponding to the user equipment.
[0199] Finally, the first agent entity determines whether the user equipment and the target entity have the first communication permission based on the first pending key information.
[0200] For example, the first pending key information includes the application key K corresponding to the target entity. AF In this case, it can be determined that the user equipment and the target entity have first communication permissions. Conversely, if the first pending key information does not include the application key K corresponding to the target entity... AF Alternatively, the first pending key information does not include a valid application key K. AF Alternatively, if the first pending key information is not received within a preset time, it can be determined that the user equipment and the target entity do not have the first communication permission.
[0201] In this way, the first agent entity can determine whether the user device and the target entity have the first communication permission by interacting with the second entity.
[0202] In other embodiments, if the first proxy entity stores the user equipment communication permission policy, it can be directly determined whether the user equipment and the target entity have the first communication permission based on the first permission request parameter.
[0203] S503. When the user equipment and the target entity have first communication permissions, the first agent entity sends an application session establishment response message to the user equipment and performs identity authentication on the user equipment.
[0204] In some embodiments, the first agent entity can indicate that the user device and the target entity have first communication permissions by sending the application session establishment response message; conversely, it can indicate that the user device and the target entity do not have first communication permissions by not sending the application session establishment response message.
[0205] In other embodiments, the first proxy entity may include success indication information in the application session establishment response message, thereby indicating that the user device and the target entity have first communication permissions; conversely, by not including success indication information in the application session establishment response message, it indicates that the user device and the target entity do not have first communication permissions. The success indication information can be any pre-set indication information.
[0206] In other embodiments, if the user device and the target entity do not have the first communication permission, the first proxy entity may include failure indication information in the application session establishment response message to indicate that the user device and the target entity do not have the first communication permission; conversely, if the user device and the target entity have the first communication permission, the first proxy entity may indicate that the user device and the target entity have the first communication permission by not including failure indication information in the application session establishment response message.
[0207] Using the above method, the communication permissions between the user equipment and the first entity can be authenticated based on the first agent entity, thereby reducing the problem of excessive load caused by the first entity performing permission authentication.
[0208] In some embodiments, the first communication permission described above may include one or more of the following:
[0209] Permission 1: The user device has access rights to the target entity;
[0210] Permission 2: The user device has access rights to the first agent entity;
[0211] Permission 3: The first proxy entity has proxy permissions for the target entity.
[0212] Permission 4: The target entity has permission to obtain the user identifier of the user device.
[0213] In some embodiments, the first entity may include: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain; the first proxy entity may include an untrusted authentication proxy (AP) entity outside the 3GPP operator domain; the second entity may include: a network open function (NEF) entity or a service capability open function (SCEF) entity.
[0214] In some embodiments, if the first agent entity successfully authenticates the user equipment, the first agent entity may send an authentication result notification message to the target entity.
[0215] The authentication result notification message is used to indicate that the target entity has communication permissions with the user device.
[0216] Furthermore, the authentication result notification message may also include a first user identifier corresponding to the user equipment. For example, if the first key response message includes the first user identifier corresponding to the user equipment, the first agent entity can send the first user identifier to the target entity through the authentication result notification message.
[0217] It should be noted that the first user identifier can be any identifier used to represent the user equipment, for example, it can be the general public user identifier (GPSI) corresponding to the user equipment.
[0218] In this way, the first agent entity can verify the communication permissions between the user equipment and the first entity, and if the user equipment has the communication permissions, instruct the user equipment to communicate with the first entity.
[0219] In other embodiments, if the first proxy entity successfully authenticates the user device, the first proxy entity can obtain the proxy domain name of the first proxy entity and the first domain name of the target entity; if the proxy domain name is different from the first domain name, an authentication result notification message is sent to the target entity to indicate that the target entity has communication permissions or can communicate with the user device.
[0220] Conversely, if the proxy domain name is the same as the first domain name, the first proxy entity will not send the authentication result notification message to the target entity for the time being; it will wait to see if the user device and the target entity have the second communication permission, and only after confirming that the user device and the target entity have the second communication permission will it send the authentication result notification message to the target entity.
[0221] For example, the first agent entity can further determine whether the user equipment and the target entity have second communication permissions based on the target entity service request message sent by the user equipment.
[0222] It should also be noted that the aforementioned proxy domain name can be the fully qualified domain name (FQDN) corresponding to the first proxy entity, and the first domain name can be the fully qualified domain name (FQDN) corresponding to the target entity. In some scenarios, the first proxy entity and the target entity may use the same FQDN but different IP addresses or port numbers. In this scenario, the aforementioned first communication permission can indicate that the user device has access to the FQDN, but it does not necessarily indicate that the user device has access to the target entity corresponding to the IP address or port number. In this case, the second communication permission can be further determined through the secure session between the user device and the proxy entity.
[0223] Figure 6 This is an authentication method illustrated according to an exemplary embodiment, which can be applied to a first proxy entity. For example... Figure 6 As shown, the method may include:
[0224] S601. After successful authentication of the user equipment, the first agent entity establishes a secure session with the user equipment.
[0225] For example, the secure session could be a TLS (Transport Layer Security) session, which can ensure confidentiality and data integrity of communications between the first proxy entity and the user equipment.
[0226] S602. The first agent entity receives the target entity service request message sent by the user equipment through a secure session.
[0227] The target entity service request message includes a second target entity identifier, which is a protected entity identifier obtained by the user equipment based on the first target entity identifier of the target entity. The target entity service request message is a message sent by the user equipment when it is determined that the proxy domain name of the first proxy entity is the same as the first domain name of the target entity.
[0228] S603. The first agent entity determines whether the user equipment and the target entity have the second communication permission based on the identifier of the second target entity.
[0229] In some embodiments, if the second target entity identifier is the same as the first target entity identifier, it can be determined that the user equipment and the target entity have second communication permissions.
[0230] In other embodiments, when the second target entity identifier differs from the first target entity identifier, the first proxy entity can determine whether the user equipment and the target entity have second communication permissions by interacting with the key request message of the second entity. For example, this may include the following steps:
[0231] First, the first agent entity sends a second key request message to the second entity.
[0232] Secondly, the first agent entity receives the second key response message sent by the second entity.
[0233] Finally, the first agent entity determines whether the user equipment and the target entity have the second communication permission based on the second key response message.
[0234] For example, the second key request message may include a key identifier A-KID, a second target entity identifier, and a proxy entity identifier corresponding to the first proxy entity; the second key request message may be used to instruct the second entity to determine whether the user equipment and the target entity have second communication permissions based on the second key request message.
[0235] In some embodiments, the second key request message may include an authorization indication parameter. This authorization indication parameter can be used to instruct a second entity to determine, based on the second key request message, whether the user equipment and the target entity have second communication permissions. Similarly, the second key response message may also include an authorization indication parameter to characterize that the second key response message is a response to the second key request message.
[0236] In some embodiments, the second key response message may further include an authorization result parameter. This authorization result parameter can be used to indicate whether authorization was successful or failed. The first agent entity determines whether the user equipment and the target entity have second communication permissions based on the authorization result parameter. For example, if the authorization result parameter indicates successful authorization, it can be determined that the user equipment and the target entity have second communication permissions; conversely, if the authorization result parameter indicates authorization failure, or if the second key response message does not include the authorization result parameter, it can be determined that the user equipment and the target entity do not have second communication permissions.
[0237] S604. The first agent entity sends the target entity service response message to the user equipment.
[0238] The target entity service response message is used to indicate whether the user equipment has second communication permissions with the target entity.
[0239] In some embodiments, the first agent entity can indicate that the user equipment has second communication permissions with the target entity by sending the target entity service response message; conversely, it can indicate that the user equipment does not have second communication permissions with the target entity by not sending the target entity service response message.
[0240] In other embodiments, the first proxy entity may include success indication information in the target entity's service response message, indicating that the user equipment and the target entity have second communication permissions; conversely, by not including success indication information in the target entity's service response message, it indicates that the user equipment and the target entity do not have second communication permissions. The success indication information can be any pre-set indication information.
[0241] In other embodiments, when the user equipment and the target entity do not have the second communication permission, the first proxy entity may include a failure indication message in the target entity's service response message to indicate that the user equipment and the target entity do not have the second communication permission; conversely, when the user equipment and the target entity have the second communication permission, the first proxy entity may indicate that the user equipment and the target entity have the second communication permission by not including a failure indication message in the target entity's service response message. The failure indication message can be any pre-set error code.
[0242] In this way, the first agent entity can determine whether the user device and the target entity have the second communication permission through a secure session, and send the permission authentication result to the target device.
[0243] In some embodiments, the second communication permission described above may include one or more of the following permissions:
[0244] Permission 6: The user device has access rights to the target entity.
[0245] Permission 7: The first proxy entity has proxy permissions for the target entity.
[0246] Permission 8: The target entity has permission to obtain the user identifier of the user device.
[0247] In this way, the reliability of authentication can be further improved by determining whether the user equipment and the target entity have second communication permissions through the secure session between the user equipment and the first agent entity.
[0248] In some embodiments, if it is determined from the second key response message that the user equipment and the target entity have second communication permissions, the first agent entity may send an authentication result notification message to the target entity.
[0249] The authentication result notification message is used to indicate that the target entity has communication permissions with the user device.
[0250] Furthermore, the authentication result notification message may also include a first user identifier corresponding to the user equipment. For example, if the second key response message includes the first user identifier corresponding to the user equipment, the first agent entity can send the first user identifier to the target entity through the authentication result notification message.
[0251] It should be noted that the first user identifier can be any identifier used to represent the user equipment, for example, it can be the general public user identifier (GPSI) corresponding to the user equipment.
[0252] In this way, the first agent entity can verify the second communication permission between the user equipment and the first entity through a secure session, thereby further improving the reliability of authentication, and instructing the user equipment to communicate with the first entity when the user equipment and the first entity have the second communication permission.
[0253] Figure 7 This is an authentication method illustrated according to an exemplary embodiment, which can be applied to a second entity. For example... Figure 7 As shown, the method may include:
[0254] S701, The second entity receives the first key request message sent by the first agent entity.
[0255] The first key request message includes a second permission request parameter, which is a parameter determined by the first proxy entity based on the first permission request parameter sent by the user equipment. The first permission request parameter is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions. The target entity is the entity that the user equipment determines from one or more first entities to request communication. The first entity may include an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity may include an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity. The first entity may include one or more.
[0256] S702, The second entity obtains the first pending key information according to the second permission request parameters.
[0257] In some embodiments, the second entity may determine whether the user equipment and the target entity have first communication permissions by interacting with a key request message with the third entity, and obtain the first pending key information. For example, this may include the following steps:
[0258] First, the second entity determines the third permission request parameters based on the second permission request parameters.
[0259] Next, the second entity sends a third key request message to the third entity based on the third permission request parameters. For example, the third key request message may include the third permission request parameters.
[0260] Next, the second entity receives a third key response message sent by the third entity. For example, the third key response message includes third pending key information, which is key information obtained by the third entity after determining, based on the third permission request parameters, that the user equipment and the target entity have first communication permissions.
[0261] Finally, the second entity obtains the first pending key information based on the third pending key information.
[0262] In this way, the second entity can obtain the first pending key information by interacting with the third entity.
[0263] In some embodiments, the second entity may include an entity that provides network openness functionality, and the third entity may include an entity that provides AKMA authorization and application key derivation functionality.
[0264] In some embodiments, the second permission request parameter may include the proxy entity identifier corresponding to the first proxy entity, and the second entity may determine a third entity with permission to serve the first proxy entity based on a pre-set policy (e.g., configuration parameters).
[0265] In some embodiments, the second permission request parameters may include the key identifier A-KID corresponding to the user equipment, the first target entity identifier corresponding to the target entity, and the proxy entity identifier corresponding to the first proxy entity; the second entity may use the second permission request parameters as the third permission request parameters.
[0266] In some embodiments, the third pending key information includes the entity key information corresponding to the target entity; the second entity may use the entity key information corresponding to the target entity as the first pending key information.
[0267] In some embodiments, the entity key information corresponding to the target entity may include the application key K corresponding to the target entity. AF .
[0268] In other embodiments, the entity key information corresponding to the target entity may include the application key K corresponding to the target entity. AF and key validity period K AF Expiration time.
[0269] In some embodiments, the third key response message may further include a second user identifier of the user equipment, and the second entity may determine the first user identifier based on the second user identifier; and send the first key response message to the first agent entity based on the first pending key information and the first user identifier. For example, the first pending key information and the first user identifier may be included in the first key response message.
[0270] In some embodiments, the second user identifier may be an identifier representing the user equipment within the 3GPP operator domain; the first user identifier may be an identifier representing the user equipment outside the 3GPP operator domain. For example, the second user identifier may be a Subscription Permanent Identifier (SUPI) corresponding to the user equipment; the first user identifier may be a Generic Public Subscription Identifier (GPSI) corresponding to the user equipment.
[0271] The second entity can determine the first user identifier corresponding to the second user identifier based on a preset identifier correspondence relationship; the preset identifier correspondence relationship includes the correspondence relationship between the second user identifier and the first user identifier.
[0272] In this way, the second entity can obtain the first user identifier corresponding to the user device by interacting with the third entity.
[0273] In other embodiments, if the second entity stores the user equipment communication permission policy, it is possible to directly determine whether the user equipment and the target entity have the first communication permission based on the second permission request parameters, and obtain the first pending key information.
[0274] S703, the second entity sends a first key response message to the first agent entity based on the first pending key information.
[0275] For example, the first key response message may include first pending key information so that the first agent entity can determine whether the user equipment and the target entity have first communication permissions based on the first pending key information.
[0276] In this way, the second entity can determine whether the user equipment and the target entity have the first communication permission, and notify the first agent entity through the first pending key information.
[0277] In some embodiments, the first communication permission includes one or more of the following:
[0278] The user equipment has access rights to the target entity;
[0279] The user equipment has access to the first agent entity;
[0280] The first proxy entity has proxy authority over the target entity.
[0281] The target entity has permission to obtain the user identifier of the user device.
[0282] In some embodiments, the first entity may include: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain; the first proxy entity may include an untrusted authentication proxy (AP) entity outside the 3GPP operator domain; the second entity may include: a network open function (NEF) entity or a service capability open function (SCEF) entity.
[0283] Figure 8 This is an authentication method illustrated according to an exemplary embodiment, which can be applied to a second entity. For example... Figure 8 As shown, after sending the first key response message to the first agent entity, the method may further include:
[0284] S801, The second entity receives the second key request message sent by the first agent entity.
[0285] The second key request message is a message sent by the first agent entity to the second entity when it determines that the second target entity identifier is different from the first target entity identifier corresponding to the target entity; the second target entity identifier is a protected entity identifier obtained by the user equipment based on the first target entity identifier of the target entity.
[0286] S802, the second entity determines whether the user equipment and the target entity have the second communication permission based on the second key request message.
[0287] In some embodiments, the second entity may determine whether the user equipment and the target entity have second communication permissions by interacting with a key request message from a third entity. For example, this may include the following steps:
[0288] First, the second entity sends a fourth key request message to the third entity.
[0289] Secondly, the second entity receives the fourth key response message sent by the third entity.
[0290] Finally, the second entity determines whether the user equipment and the target entity have the second communication permission based on the fourth key response message.
[0291] For example, the second key request message may include a key identifier A-KID, a second target entity identifier, and a proxy entity identifier corresponding to the first proxy entity; the fourth key request message may also include a key identifier A-KID, a second target entity identifier, and a proxy entity identifier. This fourth key request message can be used to instruct a third entity to determine whether the user equipment and the target entity have second communication permissions based on the key identifier A-KID, the second target entity identifier, and the proxy entity identifier.
[0292] In some embodiments, both the second key request message and the fourth key request message may include an authorization indication parameter, which can be used to instruct a third entity to determine whether the user equipment and the target entity have second communication permissions based on the fourth key request message. Similarly, the second key response message may also include an authorization indication parameter to indicate that the second key response message is a response to the second key request message; the fourth key response message may also include an authorization indication parameter to indicate that the fourth key response message is a response to the fourth key request message.
[0293] In some embodiments, the fourth key response message may further include an authorization result parameter. This authorization result parameter can be used to indicate whether authorization was successful or failed.
[0294] S803, the second entity sends a second key response message to the first agent entity.
[0295] The second key response message is used to notify the first agent entity whether the user device and the target entity have the second communication permission.
[0296] In some embodiments, the second entity may also generate a second key response message based on the authorization result parameter in the fourth key response message. For example, the authorization result parameter may be included in the second key response message. In this way, the authorization result parameter may be forwarded to the first agent entity so that the first agent entity can determine whether the user equipment and the target entity have the second communication permission based on the authorization result parameter.
[0297] In some embodiments, the fourth key response message may further include a second user identifier corresponding to the user equipment, and the second entity may determine the first user identifier based on the second user identifier; and send the second key response message to the first agent entity based on the first user identifier. For example, the first user identifier may be included in the second key response message.
[0298] In some embodiments, the second user identifier may be an identifier representing the user equipment within the 3GPP operator domain; the first user identifier may be an identifier representing the user equipment outside the 3GPP operator domain. For example, the second user identifier may be a Subscription Permanent Identifier (SUPI) corresponding to the user equipment; the first user identifier may be a Generic Public Subscription Identifier (GPSI) corresponding to the user equipment.
[0299] The second entity can determine the first user identifier corresponding to the second user identifier based on a preset identifier correspondence relationship; the preset identifier correspondence relationship includes the correspondence relationship between the second user identifier and the first user identifier.
[0300] In some embodiments, the second communication permission includes one or more of the following:
[0301] The user equipment has access rights to the target entity;
[0302] The first proxy entity has proxy authority over the target entity;
[0303] The target entity has permission to obtain the user identifier of the user device.
[0304] In some embodiments, the aforementioned third entity may include: the AKMA anchor function AAnF entity.
[0305] Figure 9 This is an authentication method illustrated according to an exemplary embodiment, which can be applied to a third entity. For example... Figure 9 As shown, the method may include:
[0306] S901, The third entity receives the third key request message sent by the second entity.
[0307] The third key request message includes a third permission request parameter, which is a parameter determined by the second entity based on the second permission request parameter. The second permission request parameter is a parameter determined by the first proxy entity based on the first permission request parameter sent by the user equipment. The first permission request parameter is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameter. The target entity is the entity that the user equipment determines from one or more first entities to request communication. The first entity may include an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity may include an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity. The first entity may include one or more.
[0308] S902. The third entity determines whether the user equipment and the target entity have the first communication permission based on the third permission request parameters.
[0309] In some embodiments, the third permission request parameter may include the proxy entity identifier corresponding to the first proxy entity. After receiving the third permission request parameter, the third entity can determine whether it has the permission to serve the first proxy entity according to a preset policy. The preset policy may include pre-configured parameters.
[0310] If it is determined that the third entity has the authority to serve the first agent entity, the user equipment and the target entity shall be determined according to the third authority request parameters to determine whether they have the first communication authority.
[0311] Conversely, if it is determined that the third entity does not have the authority to serve the first proxy entity, the process can be terminated, and the checks on whether the user device and the target entity have the first communication authority can be stopped. In this case, the third entity can send a failure indication to the second entity so that the second entity can perform the appropriate failure handling; or, the third entity can also directly stop processing without sending any messages.
[0312] In some embodiments, the third permission request parameters include the key identifier A-KID corresponding to the user equipment, the first target entity identifier of the target entity, and the proxy entity identifier corresponding to the first proxy entity. In this step, determining whether the user equipment and the target entity have first communication permissions includes one or more of the following methods:
[0313] Method 1: Determine whether the user equipment has access rights to the target entity based on the key identifier A-KID and the first target entity identifier.
[0314] Method 2: Determine whether the user equipment has access rights to the first agent entity based on the key identifier A-KID and the agent entity identifier.
[0315] Method 3: Determine whether the first proxy entity has proxy authority over the target entity based on the proxy entity identifier and the first target entity identifier.
[0316] Method 4: Based on the key identifier A-KID and the second target entity identifier, determine whether the target entity has the right to obtain the user identifier of the user equipment.
[0317] Method 5: Determine whether the user equipment has permission to use AKMA based on the key identifier A-KID.
[0318] In some embodiments, a third entity may determine that the user equipment has first communication rights with the target entity if it is determined that the user equipment has access rights to both the first agent entity and the target entity, and that the first agent entity has proxy rights to the target entity.
[0319] In other embodiments, the third entity may determine that the user equipment and the target entity have first communication permissions if it is determined that the user equipment has access permissions to the target entity and the first proxy entity has proxy permissions to the target entity.
[0320] S903. The third entity obtains the third pending key information when the user equipment and the target entity have the first communication authority.
[0321] For example, third pending key information can be obtained based on the entity key information corresponding to the target entity.
[0322] In some embodiments, the entity key information corresponding to the target entity may include the application key K corresponding to the target entity. AF .
[0323] In other embodiments, the entity key information corresponding to the target entity may include the application key K corresponding to the target entity. AF and key validity period K AF Expiration time.
[0324] S904. The third entity sends a third key response message to the second entity based on the third pending key information.
[0325] For example, the third key response message may include third pending key information, so that the second entity can obtain the first pending key information based on the third pending key information and send the first pending key information to the first proxy entity. The first proxy entity can determine whether the user equipment and the target entity have first communication permissions based on the first pending key information. The third key response message may include the third pending key information.
[0326] In this way, the third entity can determine whether the user equipment and the target entity have the first communication permission, and notify the second entity through the third pending key information.
[0327] In some embodiments, the third key response message may further include a second user identifier of the user equipment. For example, the third entity may obtain the second user identifier corresponding to the user equipment and send a third key response message to the second entity based on the third pending key information and the second user identifier.
[0328] If the third entity determines that the target entity has the authority to obtain the user identifier, it may send the third pending key information and the second user identifier corresponding to the user equipment to the second entity through a third key response message.
[0329] In some embodiments, the second user identifier may be an identifier that represents the user equipment within the 3GPP operator domain; for example, the second user identifier may be the user permanent identifier (SUPI) corresponding to the user equipment.
[0330] In some embodiments, the first entity may include: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain; the first proxy entity may include an untrusted authentication proxy (AP) entity outside the 3GPP operator domain; the second entity may include: a network open function (NEF) entity or a service capability open function (SCEF) entity; and the third entity may include: an AKMA anchor function (AAnF) entity.
[0331] Figure 10 This is an authentication method illustrated according to an exemplary embodiment, which can be applied to a third entity. For example... Figure 10 As shown, after sending the third key response message to the second entity, the method may further include:
[0332] S1001, The third entity receives the fourth key request message sent by the second entity.
[0333] S1002, the third entity determines whether the user equipment and the target entity have the second communication permission based on the fourth key request message.
[0334] S1003, The third entity sends a fourth key response message to the second entity.
[0335] The fourth key response message is used to notify the second entity user equipment whether it has the second communication permission with the target entity.
[0336] In some embodiments, the fourth key request message may include the identifier of the proxy entity corresponding to the first proxy entity. After receiving the fourth key request message, the third entity can determine whether it has the authority to serve the first proxy entity according to a preset policy. The preset policy may include pre-configured parameters.
[0337] If it is determined that the third entity has the authority to serve the first agent entity, the user equipment and the target entity shall determine whether they have the second communication authority based on the fourth key request message.
[0338] Conversely, if it is determined that the third entity does not have the authority to serve the first proxy entity, the process can be terminated, and the checks on whether the user device and the target entity have the first communication authority can be stopped. In this case, the third entity can send a failure indication to the second entity so that the second entity can perform the appropriate failure handling; or, the third entity can also directly stop processing without sending any messages.
[0339] In some embodiments, the fourth key request message may include a key identifier A-KID, a second target entity identifier, and a proxy entity identifier corresponding to the first proxy entity. The second target entity identifier is a protected entity identifier obtained by the user equipment based on the first target entity identifier of the target entity. The method for determining whether the user equipment and the target entity have the second communication permission in step S1002 above may include one or more of the following:
[0340] Method 6: Determine whether the user equipment has access rights to the target entity based on the key identifier A-KID and the second target entity identifier;
[0341] Method 7: Determine whether the first proxy entity has proxy authority over the target entity based on the proxy entity identifier and the second target entity identifier.
[0342] Method 8: Based on the key identifier A-KID and the second target entity identifier, determine whether the target entity has the right to obtain the user identifier of the user equipment.
[0343] In some embodiments, a third entity may determine that the user equipment and the target entity have second communication permissions if it is determined that the user equipment has access to the target entity and the first proxy entity has proxy permissions to the target entity.
[0344] In some embodiments, the fourth key request message includes an authorization indication parameter, which instructs a third entity to determine whether the user equipment and the target entity have second communication permissions based on the fourth key request message. Similarly, the fourth key response message may also include an authorization indication parameter to characterize that the fourth key response message is a response to the fourth key request message.
[0345] In some embodiments, the fourth key response message may further include an authorization result parameter. This authorization result parameter can be used to indicate whether authorization was successful or failed. For example, the third entity can determine the value of the authorization result parameter based on whether the user equipment and the target entity have second communication permissions. For instance, if the third entity determines that the user equipment and the target entity have second communication permissions, it can set the authorization result parameter to authorization successful (e.g., 1); if it determines that the user equipment and the target entity do not have second communication permissions, it can set the value of the authorization result parameter to authorization failed (e.g., 0).
[0346] In other embodiments, the third entity may indicate that the user equipment and the target entity do not have the second communication permission by omitting the authorization result information from the fourth key response message. For example, if the third entity determines that the user equipment and the target entity do not have the second communication permission, it may omit the authorization result information from the fourth key response message; conversely, if it determines that the user equipment and the target entity have the second communication permission, it may include the authorization result information in the fourth key response message.
[0347] In some embodiments, the fourth key response message may further include a second user identifier corresponding to the user equipment. For example, if a third entity determines that the target entity has permission to obtain the user identifier, it may send a fourth key response message to the second entity based on the second user identifier corresponding to the user equipment. The second user identifier may be a user permanent identifier (SUPI) corresponding to the user equipment.
[0348] Figure 11This is an authentication method illustrated according to an exemplary embodiment, which can be applied to a first entity. For example... Figure 11 As shown, the method may further include:
[0349] S1101, The first entity receives the authentication result notification message sent by the first proxy entity.
[0350] S1102. Upon receiving the authentication result notification message sent by the first agent entity, the first entity communicates with the user equipment.
[0351] The authentication result notification message is used to indicate that the target entity and the user equipment have communication permissions. The first agent entity is connected to the first entity. Both the first entity and the first agent entity are untrusted functional entities outside the 3GPP operator domain.
[0352] It should be noted that the first entity may wait for the user equipment to initiate communication; the first entity may also actively initiate communication with the user equipment, and this disclosure does not limit this.
[0353] In some embodiments, the authentication result notification message includes a first user identifier for the user equipment. This first user identifier may be an identifier representing the user equipment outside the 3GPP operator domain. For example, the first user identifier is the General Public Subscriber Identifier (GPSI) corresponding to the user equipment.
[0354] In some embodiments, the first entity includes: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain; the first proxy entity includes an untrusted authentication proxy (AP) entity outside the 3GPP operator domain.
[0355] In this way, the first entity can determine whether the user equipment and the first entity have the first communication permission based on the authentication result notification message of the first agent entity, thereby reducing the load on the first entity and improving the efficiency of the first entity.
[0356] Figure 12 This is an authentication method illustrated according to an exemplary embodiment, such as Figure 12 As shown, the method may include:
[0357] S1201, The user equipment sends an application session establishment request message to the first agent entity.
[0358] For example, the application session establishment request message may include a first permission request parameter, which may include the user device's key identifier A-KID and the target entity's first target entity identifier Target AF ID. The target entity may be the entity that the user device determines from one or more first entities to request communication.
[0359] In some embodiments, the user equipment can obtain the key identifier A-KID through a preset functional entity in the communication system. This preset functional entity may include an Authentication Server Function (AUSF) entity.
[0360] S1202, In response to receiving the application session establishment request message, the first agent entity sends a first key request message to the second entity.
[0361] The first key request message may include a second permission request parameter.
[0362] In some embodiments, the first agent entity may receive an application session establishment request message sent by the user equipment and determine the second permission request parameter based on the first permission request parameter in the application session establishment request message.
[0363] For example, if the first permission request parameters include the user equipment's key identifier A-KID and the target entity's first target entity identifier Target AF ID, it can be determined that the second permission request parameters include the key identifier A-KID, the first target entity identifier Target AF ID, and the proxy entity identifier of the first proxy entity.
[0364] S1203. In response to receiving the first key request message, the second entity sends a third key request message to the third entity.
[0365] The third key request message may include third permission request parameters.
[0366] In some embodiments, the second entity may receive a first key request message sent by the first agent entity and determine a third permission request parameter based on the second permission request parameter in the first key request message.
[0367] For example, the second permission request parameter can be directly used as the third permission request parameter. For instance, if the second permission request parameter includes the key identifier A-KID, the first target entity identifier Target AF ID, and the proxy entity identifier of the first proxy entity, then the key identifier A-KID, the first target entity identifier Target AF ID, and the proxy entity identifier of the first proxy entity can be used as the third permission request parameter.
[0368] S1204. If the third entity determines that the user equipment and the target entity have first communication permissions based on the third key request message, the third entity obtains the third pending key information.
[0369] The third entity can authenticate the communication permissions of the user device and the target entity based on a preset permission policy to determine whether the user device and the target entity have the first communication permission. For example:
[0370] In some embodiments, the third entity may determine whether the user equipment and the target entity have first communication permissions in one or more of the following ways:
[0371] Method 1: Determine whether the user equipment has access rights to the target entity based on the key identifier A-KID and the first target entity identifier.
[0372] Method 2: Determine whether the user equipment has access rights to the first agent entity based on the key identifier A-KID and the agent entity identifier.
[0373] Method 3: Determine whether the first proxy entity has proxy authority over the target entity based on the proxy entity identifier and the first target entity identifier.
[0374] Method 4: Based on the key identifier A-KID and the second target entity identifier, determine whether the target entity has the right to obtain the user identifier of the user equipment.
[0375] Method 5: Determine whether the user equipment has permission to use AKMA based on the key identifier A-KID.
[0376] In other embodiments, the third entity can determine that the user equipment and the target entity have first communication permissions if it is determined that the user equipment has access to all target entities and the first proxy entity has proxy permissions to the target entities. For example, the third entity can determine whether the user equipment and the target entity have first communication permissions through the following steps:
[0377] S11. Based on the agent entity identifier and the first target entity identifier, determine whether the first agent entity has agency authority over the target entity.
[0378] If it is determined that the first proxy entity does not have proxy permissions for the target entity, then it is directly determined that the user equipment and the target entity do not have first communication permissions, and step S12 is not executed. Conversely, if it is determined that the first proxy entity has proxy permissions for the target entity, then step S12 is executed.
[0379] S12. Determine whether the user equipment has access rights to the target entity based on the key identifier A-KID and the first target entity identifier.
[0380] If it is determined that the user equipment does not have access rights to the target entity, then it is directly determined that the user equipment and the target entity do not have the first communication permission, and step S13 is not executed. Conversely, if it is determined that the user equipment has access rights to the target entity, then step S13 is executed.
[0381] S13. Determine whether the user equipment has permission to use AKMA based on the key identifier A-KID.
[0382] If it is determined that the user equipment has permission to use AKMA, it can be determined that the user equipment and the target entity have first-level communication permissions. Conversely, if it is determined that the user equipment does not have permission to use AKMA, it can be determined that the user equipment and the target entity do not have first-level communication permissions.
[0383] It should be noted that the third pending key information may include the entity key information corresponding to the target entity.
[0384] In some embodiments, the entity key information corresponding to the target entity may include the application key K corresponding to the target entity. AF .
[0385] In other embodiments, the entity key information corresponding to the target entity may include the application key K corresponding to the target entity. AF and key validity period K AF Expiration time.
[0386] S1205, The third entity sends a third key response message to the second entity based on the third pending key information.
[0387] For example, the third key response message may include the application key K corresponding to the target entity. AF and key validity period K AF Expiration time.
[0388] In some embodiments, the third key response message may further include a second user identifier of the user equipment, which may be an identifier representing the user equipment within the 3GPP operator domain; for example, the second user identifier may be a user permanent identifier (SUPI) corresponding to the user equipment.
[0389] S1206. The second entity sends a first key response message to the first agent entity based on the third key response message.
[0390] For example, the first key response message may include the application key K corresponding to the target entity. AF and key validity period K AF Expiration time.
[0391] If the third key response message includes a second user identifier (e.g., SUPI) of the user equipment, the second entity can obtain a first user identifier (e.g., GPSI) based on the second user identifier (e.g., SUPI) and include the first user identifier in the first key response message.
[0392] S1207. The first agent entity sends an application session establishment response message to the user equipment.
[0393] The first agent entity obtains the application key K from the first key response message. AF In this case, it can be determined that the user equipment and the target entity have first communication permissions. At this time, the first agent entity can send an application session establishment response message to the user equipment.
[0394] S1208. User equipment authenticates its identity through the first agent entity.
[0395] If the user equipment (UE) determines that it has first-level communication permissions with the target entity, it can perform authentication through a first proxy entity. For example, the UE can generate an entity key K corresponding to the target entity based on the target entity's FQDN. AF And based on the entity key K AF Authenticate your identity with the first agent entity.
[0396] S1209a, The first proxy entity sends an authentication result notification message to the target entity.
[0397] If the first key response message includes the user equipment's first user identifier (e.g., SUPI), the first agent entity may include that first user identifier in the authentication result notification message so that the target application can obtain the user equipment's identification information.
[0398] In some embodiments, if the first agent entity successfully authenticates the user equipment, the first agent entity may send an authentication result notification message to the target entity (execute step S1209a, and do not continue to execute steps S1209b and thereafter).
[0399] In other embodiments, if the first proxy entity successfully authenticates the user equipment, the first proxy entity can obtain the proxy domain name of the first proxy entity and the first domain name of the target entity; if the proxy domain name is different from the first domain name, an authentication result notification message is sent to the target entity (this step S1209a is executed, and S1209b and subsequent steps are not executed), so as to instruct the target entity to have communication permissions or to communicate with the user equipment.
[0400] In other embodiments, if the proxy domain name is the same as the first domain name, the first proxy entity may temporarily not send the authentication result notification message to the target entity; it may first wait to see if the user equipment and the target entity have the second communication permission, and only after determining that the user equipment and the target entity have the second communication permission will it send the authentication result notification message to the target entity. That is, step S1209a is not executed, and steps S1209b and thereafter are executed.
[0401] S1209b: The user equipment establishes a secure session with the first agent entity.
[0402] This secure session may include a TLS session.
[0403] S1210, The user equipment sends a target entity service request message to the first agent entity.
[0404] The target entity service request message includes a second target entity identifier, which is a protected entity identifier obtained by the user equipment based on the first target entity identifier of the target entity.
[0405] In some embodiments, the target entity service request message may include a key identifier A-KID and a second target entity identifier.
[0406] In some embodiments, if the second target entity identifier is the same as the first target entity identifier, it can be determined that the user equipment and the target entity have second communication permissions. Then, an authentication result notification message can be sent to the target entity, and a target entity service response message can be sent to the user equipment. That is, steps S1211a and S1218 are executed, without needing to execute steps S1211b to S1217.
[0407] In other embodiments, if the second target entity identifier is different from the first target entity identifier, the first proxy entity can determine whether the user equipment and the target entity have second communication permissions by interacting with the key request message of the second entity. That is, step S1211a is not executed, and steps S1211b and thereafter are executed.
[0408] S1211a, The first proxy entity sends an authentication result notification message to the target entity.
[0409] S1211b, The first agent entity sends a second key request message to the second entity.
[0410] In some embodiments, the second key request message may include a key identifier A-KID, a second target entity identifier, and a proxy entity identifier corresponding to the first proxy entity; the second key request message may be used to instruct the second entity to determine whether the user equipment and the target entity have second communication permissions based on the second key request message.
[0411] In some embodiments, the second key request message may further include an authorization indication parameter, which may be used to instruct the second entity to determine whether the user equipment and the target entity have second communication permissions based on the second key request message.
[0412] S1213. The second entity sends a fourth key request message to the third entity based on the second key request message.
[0413] In some embodiments, the fourth key request message may include a key identifier A-KID, a second target entity identifier, and a proxy entity identifier corresponding to the first proxy entity.
[0414] In some embodiments, the fourth key request message may also include an authorization indication parameter, which can be used to instruct a third entity to determine whether the user equipment and the target entity have second communication permissions based on the fourth key request message.
[0415] S1214. The third entity determines whether the user equipment and the target entity have the second communication permission based on the fourth key request message.
[0416] For example, the way a third entity determines whether a user device and a target entity have second communication permissions may include one or more of the following:
[0417] Method 6: Determine whether the user equipment has access rights to the target entity based on the key identifier A-KID and the second target entity identifier;
[0418] Method 7: Determine whether the first proxy entity has proxy authority over the target entity based on the proxy entity identifier and the second target entity identifier.
[0419] Method 8: Based on the key identifier A-KID and the second target entity identifier, determine whether the target entity has the right to obtain the user identifier of the user equipment.
[0420] In some embodiments, a third entity may determine that the user equipment and the target entity have second communication permissions if it is determined that the user equipment has access to the target entity and the first proxy entity has proxy permissions to the target entity.
[0421] S1215, The third entity sends a fourth key response message to the fourth entity.
[0422] The fourth key response message is used to notify the second entity user equipment whether it has the second communication permission with the target entity.
[0423] In some embodiments, the fourth key response message may further include a second user identifier of the user equipment, which may be an identifier that represents the user equipment within the 3GPP operator domain; for example, the second user identifier may be a user permanent identifier (SUPI) corresponding to the user equipment.
[0424] In some embodiments, the fourth key response message may further include an authorization result parameter. For example, the third entity may include this authorization result parameter in the fourth key response message after determining whether the user equipment and the target entity have second communication permissions.
[0425] S1216. The second entity sends a second key response message to the first agent entity based on the fourth key response message.
[0426] If the fourth key response message includes a second user identifier (e.g., SUPI) of the user equipment, the second entity can obtain a first user identifier (e.g., GPSI) based on the second user identifier (e.g., SUPI) and include the first user identifier in the second key response message.
[0427] If the fourth key response message includes the authorization result parameter, the second entity may also include the authorization result parameter in the second key response message.
[0428] S1217. The first proxy entity sends an authentication result notification message to the target entity.
[0429] For example, the first agent entity can send an authentication result notification message to the target entity based on the second key response message. For instance, if the first agent entity determines that the user equipment and the target entity have second communication permissions based on the second key response message, it can send an authentication result notification message to the target entity.
[0430] In some embodiments, the second key response message may include an authorization result parameter, which the first agent entity can use to determine that the user equipment and the target entity have second communication permissions.
[0431] If the second key response message includes the user equipment's first user identifier (e.g., SUPI), the first agent entity may include the first user identifier in the authentication result notification message so that the target application can obtain the user equipment's identification information.
[0432] S1218. The first agent entity sends the target entity service response message to the user equipment.
[0433] The target entity service response message is used to indicate whether the user device has second communication permissions with the target entity.
[0434] For example, the first agent entity can send a target entity service response message to the user equipment based on the second key response message. For instance, the first agent entity can send a target entity service response message to the user equipment if it determines that the user equipment and the target entity have second communication permissions based on the authorization result parameters in the second key response message.
[0435] In some embodiments, the first entity may include: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain; the first proxy entity may include an untrusted authentication proxy (AP) entity outside the 3GPP operator domain; the second entity may include: a network open function (NEF) entity or a service capability open function (SCEF) entity; and the third entity may include: an AKMA anchor function (AAnF) entity.
[0436] In this way, for untrusted first entities outside the 3GPP operator domain, the first proxy entity determines whether the user equipment has communication rights with the first entity, and performs user equipment authentication if the user equipment has first communication rights. Some functions of the first entity can be implemented through the first proxy entity, thereby reducing the load on the first entity and improving its efficiency. Furthermore, the user equipment performs permission authentication and identity authentication with one or more first entities through a unified first proxy entity, which also reduces the complexity of authentication for the user equipment and improves its efficiency.
[0437] Figure 13 This is a block diagram illustrating an authentication device 1300 according to an exemplary embodiment, which can be applied to user equipment. Figure 13 As shown, the device 1300 may include:
[0438] The target entity determination module 1301 is configured to determine the target entity for the request to communicate from one or more first entities;
[0439] The parameter determination module 1302 is configured to determine the first permission request parameters based on the target entity;
[0440] The first message sending module 1303 is configured to send an application session establishment request message to the first proxy entity according to the first permission request parameter; the application session establishment request message is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions according to the first permission request parameter; the first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions, the first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions, and the first proxy entity provides authentication proxy functions for the first entity;
[0441] The first message receiving module 1304 is configured to determine whether the user equipment and the target entity have first communication permissions in response to receiving an application session establishment response message sent by the first agent entity.
[0442] The authentication module is configured to perform identity authentication through the first proxy entity when the user device has first communication permissions with the target entity.
[0443] Optionally, the parameter determination module 1302 is configured to use the first target entity identifier of the target entity and the key identifier A-KID corresponding to the user equipment as the first permission request parameter.
[0444] Optionally, the first communication permission includes one or more of the following:
[0445] The user equipment has access rights to the target entity;
[0446] The user equipment has access to the first agent entity;
[0447] The first proxy entity has proxy authority over the target entity;
[0448] The target entity has permission to obtain the user identifier of the user device.
[0449] Figure 14 This is a block diagram illustrating an authentication device 1300 according to an exemplary embodiment, such as... Figure 14 As shown, the device may further include:
[0450] The user communication module 1305 is configured to establish a secure session with the first proxy entity after successful authentication through the first proxy entity; obtain the proxy domain name of the first proxy entity and the first domain name of the target entity; if the proxy domain name is the same as the first domain name, determine through the secure session whether the user device and the target entity have second communication permissions; and if it is determined that the user device and the target entity have second communication permissions, communicate with the target entity.
[0451] Optionally, the user communication module 1305 is configured to send a target entity service request message to the first proxy entity through the secure session; the target entity service request message includes a second target entity identifier, which is a protected entity identifier obtained by the user equipment based on the first target entity identifier; the target entity service request message is used to instruct the first proxy entity to determine whether the user equipment and the target entity have second communication permissions based on the second target entity identifier; in response to receiving a target entity service response message sent by the first proxy entity, it determines whether the user equipment and the target entity have second communication permissions.
[0452] Optionally, the second communication permission includes one or more of the following:
[0453] The user equipment has access rights to the target entity;
[0454] The first proxy entity has proxy authority over the target entity;
[0455] The target entity has permission to obtain the user's identifier on the user device.
[0456] Optionally, the first message receiving module 1304 is configured to determine that the user equipment and the target entity have first communication permissions upon receiving the application session establishment response message; or, upon receiving the application session establishment response message and the session establishment response message containing success indication information, determine that the user equipment and the target entity have first communication permissions.
[0457] Optionally, the first entity includes: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain; the first agent entity includes an untrusted authentication agent (AP) entity outside the 3GPP operator domain.
[0458] Figure 15 This is a block diagram illustrating an authentication device 1500 according to an exemplary embodiment, which can be applied to a first proxy entity. Figure 15 As shown, the device 1500 may include:
[0459] The first proxy receiving module 1501 is configured to receive an application session establishment request message sent by a user equipment. The application session establishment request message includes a first permission request parameter. The application session establishment request message is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameter. The target entity is the entity that the user equipment determines from one or more first entities to request communication. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity.
[0460] The first agent determination module 1502 is configured to determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameters.
[0461] The first proxy sending module 1503 is configured to send an application session establishment response message to the user equipment and to authenticate the user equipment when the user equipment has first communication permission with the target entity.
[0462] Optionally, the first permission request parameter includes the first target entity identifier of the target entity and the key identifier A-KID corresponding to the user equipment.
[0463] Optionally, the first communication permission includes one or more of the following:
[0464] The user equipment has access rights to the target entity;
[0465] The user equipment has access to the first agent entity;
[0466] The first proxy entity has proxy authority over the target entity;
[0467] The target entity has permission to obtain the user's identifier on the user device.
[0468] Optionally, the first agent determination module 1502 is configured to: determine a second permission request parameter based on the first permission request parameter; send a first key request message to the second entity; the first key request message includes the second permission request parameter; receive a first key response message sent by the second entity; the first key response message includes first pending key information, the first pending key information being key information obtained by the second entity based on the second permission request parameter; and determine whether the user equipment and the target entity have first communication permission based on the first pending key information.
[0469] Optionally, the first agent determination module 1502 is configured to use the first permission request parameter and the agent entity identifier corresponding to the first agent entity as the second permission request parameter.
[0470] Optionally, the first agent determination module 1502 is configured to determine that the user equipment has a first communication permission with the target entity when the first pending key information includes the entity key information corresponding to the target entity.
[0471] Optionally, the first proxy sending module 1503 is configured to send an authentication result notification message to the target entity when the user equipment is successfully authenticated; the authentication result notification message is used to indicate that the target entity has communication rights with the user equipment.
[0472] Optionally, the first proxy sending module 1503 is configured to obtain the proxy domain name of the first proxy entity and the first domain name of the target entity; and if the proxy domain name is different from the first domain name, send an authentication result notification message to the target entity.
[0473] Optionally, the first agent sending module 1503 is configured to send the first user identifier to the target entity through the authentication result notification message when the first key response message includes the first user identifier corresponding to the user equipment.
[0474] Optionally, the first user identifier is the General Public User Identifier (GPSI) corresponding to the user equipment.
[0475] Figure 16 This is a block diagram illustrating an authentication device 1500 according to an exemplary embodiment, such as... Figure 16 As shown, the device may further include:
[0476] The first proxy communication module 1504 is configured to establish a secure session with the user equipment after successful authentication; receive a target entity service request message from the user equipment through the secure session; the target entity service request message includes a second target entity identifier, which is a protected entity identifier obtained by the user equipment based on the first target entity identifier of the target entity; the target entity service request message is sent by the user equipment when it is determined that the proxy domain name of the first proxy entity is the same as the first domain name of the target entity; determine whether the user equipment and the target entity have second communication permissions based on the second target entity identifier; and send a target entity service response message to the user equipment; the target entity service response message is used to indicate whether the user equipment and the target entity have second communication permissions.
[0477] Optionally, the second communication permission includes one or more of the following:
[0478] The user equipment has access rights to the target entity;
[0479] The first proxy entity has proxy authority over the target entity;
[0480] The target entity has permission to obtain the user's identifier on the user device.
[0481] Optionally, the first proxy communication module 1504 is configured to determine that the user equipment has second communication permissions with the target entity if the second target entity identifier is the same as the first target entity identifier.
[0482] Optionally, the first proxy communication module 1504 is configured to send a second key request message to the second entity when the second target entity identifier is different from the first target entity identifier; the second key request message includes the key identifier A-KID, the second target entity identifier, and the proxy entity identifier corresponding to the first proxy entity; the second key request message is used to instruct the second entity to determine whether the user equipment and the target entity have second communication permissions; receive a second key response message sent by the second entity; and determine whether the user equipment and the target entity have second communication permissions based on the second key response message.
[0483] Optionally, the second key request message may further include an authorization indication parameter, which is used to instruct the second entity to determine whether the user equipment and the target entity have second communication permissions based on the second key request message.
[0484] Optionally, the first agent determination module 1502 is configured to send an authentication result notification message to the target entity when it is determined from the second key response message that the user equipment and the target entity have second communication permissions; the authentication result notification message is used to indicate that the target entity and the user equipment have communication permissions.
[0485] Optionally, the first agent determination module 1502 is configured to send the first user identifier to the target entity through the authentication result notification message if the second key response message includes the first user identifier corresponding to the user equipment.
[0486] Optionally, the first user identifier is the General Public User Identifier (GPSI) corresponding to the user equipment.
[0487] Optionally, the first pending key information includes the application key K. AF and key validity period.
[0488] Optionally, the second entity includes either a Network Open Function (NEF) entity or a Service Capability Open Function (SCEF) entity.
[0489] Optionally, the first entity includes: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain; the first agent entity includes an untrusted authentication agent (AP) entity outside the 3GPP operator domain.
[0490] Figure 17 This is a block diagram illustrating an authentication device 1700 according to an exemplary embodiment, which can be applied to a second entity. (As follows) Figure 17 As shown, the device 1700 may include:
[0491] The second receiving module 1701 is configured to receive a first key request message sent by a first proxy entity. The first key request message includes a second permission request parameter, which is a parameter determined by the first proxy entity based on the first permission request parameter sent by the user equipment. The first permission request parameter is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameter. The target entity is the entity that the user equipment determines from one or more first entities to request communication. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity.
[0492] The second key acquisition module 1702 is configured to acquire the first pending key information based on the second permission request parameter.
[0493] The second sending module 1703 is configured to send a first key response message to the first agent entity based on the first pending key information.
[0494] Optionally, the second key acquisition module 1702 is configured to: determine a third permission request parameter based on the second permission request parameter; send a third key request message to a third entity based on the third permission request parameter; receive a third key response message sent by the third entity; the third key response message includes third pending key information, which is key information obtained by the third entity when it determines that the user equipment has first communication permission with the target entity based on the third permission request parameter; and acquire the first pending key information based on the third pending key information.
[0495] Optionally, the first communication permission includes one or more of the following:
[0496] The user equipment has access rights to the target entity;
[0497] The user equipment has access to the first agent entity;
[0498] The first proxy entity has proxy authority over the target entity;
[0499] The target entity has permission to obtain the user's identifier on the user device.
[0500] Optionally, the second permission request parameter includes the key identifier A-KID corresponding to the user equipment, the first target entity identifier corresponding to the target entity, and the agent entity identifier corresponding to the first agent entity; the second key acquisition module 1702 is configured to use the second permission request parameter as the third permission request parameter.
[0501] Optionally, the third pending key information includes the entity key information corresponding to the target entity; the second key acquisition module 1702 is configured to use the entity key information corresponding to the target entity as the first pending key information.
[0502] Optionally, the entity key information includes the application key K. AF and key validity period.
[0503] Optionally, the third key response message may also include a second user identifier corresponding to the user equipment; the second sending module 1703 is configured to determine a first user identifier based on the second user identifier; and send a first key response message to the first agent entity based on the first pending key information and the first user identifier.
[0504] Optionally, the first user identifier is the General Public User Identifier (GPSI) corresponding to the user equipment; the second user identifier is the User Permanent Identifier (SUPI) corresponding to the user equipment.
[0505] Optionally, the second key acquisition module 1702 is configured to, after sending a first key response message to the first proxy entity based on the first pending key information, receive a second key request message sent by the first proxy entity; the second key request message is a message sent by the first proxy entity to the second entity when it determines that the second target entity identifier is different from the first target entity identifier corresponding to the target entity; the second target entity identifier is a protected entity identifier obtained by the user equipment based on the first target entity identifier of the target entity; determine whether the user equipment and the target entity have second communication permissions based on the second key request message; send a second key response message to the first proxy entity; the second key response message is used to notify the first proxy entity whether the user equipment and the target entity have second communication permissions.
[0506] Optionally, the second communication permission includes one or more of the following:
[0507] The user equipment has access rights to the target entity;
[0508] The first proxy entity has proxy authority over the target entity;
[0509] The target entity has permission to obtain the user's identifier on the user device.
[0510] Optionally, the second key request message includes the key identifier A-KID, the second target entity identifier, and the agent entity identifier corresponding to the first agent entity; the second key acquisition module 1702 is configured to send a fourth key request message to the third entity; the fourth key request message includes the key identifier A-KID, the second target entity identifier, and the agent entity identifier; receive a fourth key response message sent by the third entity; and determine whether the user equipment and the target entity have second communication permissions based on the fourth key response message.
[0511] Optionally, both the second key request message and the fourth key request message include an authorization indication parameter, which is used to instruct the third entity to determine whether the user equipment and the target entity have second communication permissions based on the fourth key request message.
[0512] Optionally, the third entity includes: the AKMA anchor function AAnF entity.
[0513] Optionally, the first entity includes: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain; the first agent entity includes an untrusted authentication agent (AP) entity outside the 3GPP operator domain; the second entity includes: a network open function (NEF) entity or a service capability open function (SCEF) entity.
[0514] Figure 18 This is a block diagram illustrating an authentication device 1800 according to an exemplary embodiment, which can be applied to a third entity. For example... Figure 18 As shown, the device 1800 may include:
[0515] The third receiving module 1801 is configured to receive a third key request message sent by a second entity. The third key request message includes a third permission request parameter, which is a parameter determined by the second entity based on the second permission request parameter. The second permission request parameter is a parameter determined by the first proxy entity based on the first permission request parameter sent by the user equipment. The first permission request parameter is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameter. The target entity is the entity that the user equipment determines from one or more first entities to request communication. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity.
[0516] The third determining module 1802 is configured to determine, based on the third permission request parameters, whether the user equipment and the target entity have first communication permissions.
[0517] The third key module 1803 is configured to obtain third pending key information when the user equipment has first communication permission with the target entity;
[0518] The third sending module 1804 is configured to send a third key response message to the second entity based on the third pending key information.
[0519] Optionally, the third permission request parameters include the key identifier A-KID corresponding to the user equipment, the first target entity identifier of the target entity, and the proxy entity identifier corresponding to the first proxy entity; the third determination module 1802 is configured to determine whether the user equipment and the target entity have first communication permissions by one or more of the following:
[0520] Based on the key identifier A-KID and the first target entity identifier, determine whether the user equipment has access rights to the target entity;
[0521] Based on the key identifier A-KID and the agent entity identifier, determine whether the user equipment has access rights to the first agent entity;
[0522] Based on the proxy entity identifier and the first target entity identifier, determine whether the first proxy entity has proxy authority over the target entity;
[0523] Based on the key identifier A-KID and the second target entity identifier, determine whether the target entity has the authority to obtain the user identifier of the user equipment.
[0524] Optionally, the third key module 1803 is configured to obtain the third pending key information based on the entity key information corresponding to the target entity.
[0525] Optionally, the third sending module 1804 is configured to, upon determining that the target entity has the authority to obtain the user identifier, send a third pending key information and a second user identifier corresponding to the user equipment to the second entity via a third key response message.
[0526] Optionally, the second user identifier is the user permanent identifier (SUPI) corresponding to the user equipment.
[0527] Optionally, the third determining module 1802 is further configured to, after sending a third key response message to the second entity, receive a fourth key request message sent by the second entity; determine whether the user equipment and the target entity have second communication permissions based on the fourth key request message; send a fourth key response message to the second entity; the fourth key response message is used to notify the second entity whether the user equipment and the target entity have second communication permissions.
[0528] Optionally, the fourth key request message includes the key identifier A-KID, the second target entity identifier, and the proxy entity identifier corresponding to the first proxy entity. The second target entity identifier is a protected entity identifier obtained by the user equipment based on the first target entity identifier of the target entity.
[0529] The third determining module 1802 is configured to determine whether the user equipment and the target entity have second communication permissions by one or more of the following:
[0530] Based on the key identifier A-KID and the second target entity identifier, determine whether the user equipment has access rights to the target entity;
[0531] Based on the proxy entity identifier and the second target entity identifier, determine whether the first proxy entity has proxy authority over the target entity;
[0532] Based on the key identifier A-KID and the second target entity identifier, determine whether the target entity has the authority to obtain the user identifier of the user equipment.
[0533] Optionally, the fourth key request message includes an authorization indication parameter, which is used to instruct the third entity to determine whether the user equipment and the target entity have second communication permissions based on the fourth key request message.
[0534] Optionally, the third determining module 1802 is configured to send a fourth key response message to the second entity based on the second user identifier corresponding to the user equipment when it is determined that the target entity has the authority to obtain the user identifier.
[0535] Optionally, the second user identifier is the user permanent identifier (SUPI) corresponding to the user equipment.
[0536] Optionally, the first entity includes: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain; the first agent entity includes an untrusted authentication agent (AP) entity outside the 3GPP operator domain; the second entity includes: a network open function (NEF) entity or a service capability open function (SCEF) entity; and the third entity includes: an AKMA anchor function (AAnF) entity.
[0537] Figure 19 This is a block diagram illustrating an authentication device 1900 according to an exemplary embodiment, which can be applied to a first entity. (As follows) Figure 19 As shown, the device 1900 may include:
[0538] The first communication module 1901 is configured to communicate with the user equipment in response to receiving an authentication result notification message sent by the first proxy entity; the authentication result notification message is used to indicate that the target entity has communication rights with the user equipment, the first proxy entity is connected to the first entity, and both the first entity and the first proxy entity are untrusted functional entities outside the 3GPP operator domain.
[0539] Optionally, the authentication result notification message includes the first user identifier of the user equipment.
[0540] Optionally, the first user identifier is the General Public User Identifier (GPSI) corresponding to the user equipment.
[0541] Optionally, the first entity includes: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain; the first agent entity includes an untrusted authentication agent (AP) entity outside the 3GPP operator domain.
[0542] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.
[0543] Figure 20This is a block diagram illustrating an authentication device according to an exemplary embodiment. For example, the authentication device 2000 may be a terminal device, such as a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.; the authentication device 2000 may also be a server, such as a local server or cloud server; the authentication device 2000 may also be... Figure 1 The user equipment shown, the authentication device 2000, can also be Figure 1 Any network entity in the communication system shown, such as the first entity, the first agent entity, the second entity, or the third entity.
[0544] Reference Figure 20 The device 2000 may include one or more of the following components: a processing component 2002, a memory 2004, and a communication component 2006.
[0545] Processing component 2002 typically controls the overall operation of device 2000, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 2002 may include one or more processors 2020 to execute instructions to complete all or part of the steps of the authentication method described above. Furthermore, processing component 2002 may include one or more modules to facilitate interaction between processing component 2002 and other components. For example, processing component 2002 may include a multimedia module to facilitate interaction between multimedia components and processing component 2002.
[0546] Memory 2004 is configured to store various types of data to support the operation of device 2000. Examples of this data include instructions for any application or method operating on device 2000, contact data, phonebook data, messages, pictures, videos, etc. Memory 2004 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.
[0547] Communication component 2006 is configured to facilitate wired or wireless communication between device 2000 and other devices. Device 2000 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 2006 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 2006 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
[0548] In an exemplary embodiment, the apparatus 2000 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the authentication method described above.
[0549] The aforementioned device 2000 can be a standalone electronic device or a part of a standalone electronic device. For example, in one embodiment, the electronic device can be an integrated circuit (IC) or a chip, wherein the integrated circuit can be a single IC or a collection of multiple ICs; the chip can include, but is not limited to, the following types: GPU (Graphics Processing Unit), CPU (Central Processing Unit), FPGA (Field Programmable Gate Array), DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), SOC (System on Chip), etc. The aforementioned integrated circuit or chip can be used to execute executable instructions (or code) to implement the aforementioned authentication method. The executable instructions can be stored in the integrated circuit or chip or obtained from other devices or equipment. For example, the integrated circuit or chip includes a processor, memory, and an interface for communicating with other devices. The executable instruction can be stored in the processor, and when the executable instruction is executed by the processor, the above authentication method is implemented; or, the integrated circuit or chip can receive the executable instruction through the interface and transmit it to the processor for execution to implement the above authentication method.
[0550] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 2004 including instructions, which can be executed by a processor 2020 of the device 2000 to complete the authentication method described above. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.
[0551] In another exemplary embodiment, a computer program product is also provided, the computer program product comprising a computer program executable by a programmable device, the computer program having a code portion for performing the above-described authentication method when executed by the programmable device.
[0552] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of this disclosure. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.
[0553] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.
Claims
1. An authentication method, characterized in that, Applied to user equipment, the method includes: From one or more first entities, determine the target entity for which communication is requested; The first target entity identifier of the target entity and the key identifier A-KID corresponding to the user equipment are used as the first permission request parameters; An application session establishment request message is sent to the first proxy entity according to the first permission request parameters; the application session establishment request message is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions according to the first permission request parameters; the first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions, the first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions, the first proxy entity provides authentication proxy functions for the first entity, and the first proxy entity includes an untrusted authentication proxy AP entity outside the 3GPP operator domain; In response to receiving an application session establishment response message sent by the first proxy entity, determine whether the user equipment and the target entity have first communication permissions; When the user equipment has first communication permissions with the target entity, identity authentication is performed through the first proxy entity.
2. The method according to claim 1, characterized in that, The first communication permission includes one or more of the following: The user equipment has access rights to the target entity; The user equipment has access rights to the first agent entity; The first proxy entity has proxy authority over the target entity; The target entity has permission to obtain the user identifier of the user equipment.
3. The method according to claim 1, characterized in that, After successful identity authentication through the first proxy entity, the method further includes: Establish a secure session with the first proxy entity; Obtain the proxy domain name of the first proxy entity and the first domain name of the target entity; If the proxy domain name is the same as the first domain name, the security session is used to determine whether the user equipment and the target entity have second communication permissions. If it is determined that the user equipment has second communication permissions with the target entity, then communication is conducted with the target entity.
4. The method according to claim 3, characterized in that, The step of determining whether the user equipment and the target entity have second communication permissions through the secure session includes: Through the secure session, a target entity service request message is sent to the first agent entity; the target entity service request message includes a second target entity identifier, which is a protected entity identifier obtained by the user equipment based on the first target entity identifier; the target entity service request message is used to instruct the first agent entity to determine whether the user equipment and the target entity have second communication permissions based on the second target entity identifier. In response to receiving a target entity service response message sent by the first agent entity, determine whether the user equipment and the target entity have second communication permissions.
5. The method according to claim 3, characterized in that, The second communication permission includes one or more of the following: The user equipment has access rights to the target entity; The first proxy entity has proxy authority over the target entity; The target entity has permission to obtain the user identifier of the user equipment.
6. The method according to claim 1, characterized in that, The step of determining whether the user equipment and the target entity have first communication permissions in response to receiving the application session establishment response message sent by the first proxy entity includes: Upon receiving the application session establishment response message, it is determined that the user equipment and the target entity have first communication permissions; or, Upon receiving the application session establishment response message, and if the session establishment response message contains success indication information, it is determined that the user equipment and the target entity have first communication permissions.
7. The method according to any one of claims 1 to 6, characterized in that, The first entity includes: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain.
8. An authentication method, characterized in that, Applied to a first proxy entity, the method includes: The system receives an application session establishment request message sent by a user equipment (UE). The application session establishment request message includes a first permission request parameter. The message instructs the first proxy entity to determine, based on the first permission request parameter, whether the UE and the target entity have first communication permissions. The first permission request parameter includes a first target entity identifier of the target entity and a key identifier (A-KID) corresponding to the UE. The target entity is the entity that the UE determines from one or more first entities to request communication. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functionality. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functionality. The first proxy entity provides authentication proxy functionality to the first entity. The first proxy entity includes an untrusted authentication proxy (AP) entity outside the 3GPP operator domain. Determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameters; If the user equipment has first communication permission with the target entity, an application session establishment response message is sent to the user equipment, and the user equipment is authenticated.
9. The method according to claim 8, characterized in that, The first communication permission includes one or more of the following: The user equipment has access rights to the target entity; The user equipment has access rights to the first agent entity; The first proxy entity has proxy authority over the target entity; The target entity has permission to obtain the user identifier of the user equipment.
10. The method according to claim 8, characterized in that, The step of determining whether the user equipment and the target entity have the first communication permission based on the first permission request parameter includes: The second permission request parameters are determined based on the first permission request parameters; A first key request message is sent to a second entity; the first key request message includes the second permission request parameter; the second entity includes an entity that provides network access functionality. Receive a first key response message sent by the second entity; the first key response message includes first pending key information, which is key information obtained by the second entity according to the second permission request parameters; Based on the first pending key information, determine whether the user equipment and the target entity have the first communication permission.
11. The method according to claim 10, characterized in that, Determining the second permission request parameter based on the first permission request parameter includes: The first permission request parameter and the proxy entity identifier corresponding to the first proxy entity are used as the second permission request parameter.
12. The method according to claim 10, characterized in that, The step of determining whether the user equipment and the target entity have the first communication permission based on the first pending key information includes: If the first pending key information includes the entity key information corresponding to the target entity, it is determined that the user equipment and the target entity have first communication permissions.
13. The method according to claim 10, characterized in that, If the user equipment is successfully authenticated, the method further includes: Send an authentication result notification message to the target entity; the authentication result notification message is used to indicate that the target entity has communication permissions with the user equipment.
14. The method according to claim 13, characterized in that, The step of sending the authentication result notification message to the target entity includes: Obtain the proxy domain name of the first proxy entity and the first domain name of the target entity; If the proxy domain name is different from the first domain name, an authentication result notification message is sent to the target entity.
15. The method according to claim 13, characterized in that, The step of sending the authentication result notification message to the target entity includes: If the first key response message includes a first user identifier corresponding to the user equipment, the first user identifier is sent to the target entity through the authentication result notification message.
16. The method according to claim 15, characterized in that, The first user identifier is the General Public User Identifier (GPSI) corresponding to the user equipment.
17. The method according to claim 8, characterized in that, After successfully authenticating the user equipment, the method further includes: Establish a secure session with the user equipment; Through the secure session, the user equipment receives a target entity service request message sent by the user equipment. The target entity service request message includes a second target entity identifier, which is a protected entity identifier obtained by the user equipment based on the first target entity identifier of the target entity. The target entity service request message is a message sent by the user equipment when it is determined that the proxy domain name of the first proxy entity is the same as the first domain name of the target entity. Determine whether the user equipment and the target entity have second communication permissions based on the second target entity identifier; Send a target entity service response message to the user equipment; the target entity service response message is used to indicate whether the user equipment and the target entity have second communication permissions.
18. The method according to claim 17, characterized in that, The second communication permission includes one or more of the following: The user equipment has access rights to the target entity; The first proxy entity has proxy authority over the target entity; The target entity has permission to obtain the user identifier of the user equipment.
19. The method according to claim 17, characterized in that, The step of determining whether the user equipment and the target entity have second communication permissions based on the second target entity identifier includes: If the second target entity identifier is the same as the first target entity identifier, it is determined that the user equipment has second communication permissions with the target entity.
20. The method according to claim 17, characterized in that, The step of determining whether the user equipment and the target entity have second communication permissions based on the second target entity identifier includes: If the second target entity identifier is different from the first target entity identifier, a second key request message is sent to the second entity; the second key request message includes the key identifier A-KID, the second target entity identifier, and the proxy entity identifier corresponding to the first proxy entity; the second key request message is used to instruct the second entity to determine whether the user equipment and the target entity have second communication permissions. Receive the second key response message sent by the second entity; The second key response message determines whether the user equipment and the target entity have the second communication permission.
21. The method according to claim 20, characterized in that, The second key request message also includes an authorization indication parameter, which is used to instruct the second entity to determine whether the user equipment and the target entity have second communication permissions based on the second key request message.
22. The method according to claim 20, characterized in that, If, based on the second key response message, it is determined that the user equipment and the target entity have second communication permissions, the method further includes: Send an authentication result notification message to the target entity; the authentication result notification message is used to indicate that the target entity has communication permissions with the user equipment.
23. The method according to claim 22, characterized in that, The step of sending the authentication result notification message to the target entity includes: If the second key response message includes the first user identifier corresponding to the user equipment, the first user identifier is sent to the target entity through the authentication result notification message.
24. The method according to claim 23, characterized in that, The first user identifier is the General Public User Identifier (GPSI) corresponding to the user equipment.
25. The method according to claim 10, characterized in that, The first pending key information includes the application key KAF and the key validity period.
26. The method according to claim 10, characterized in that, The second entity includes: the Network Open Function (NEF) entity or the Service Capability Open Function (SCEF) entity.
27. The method according to any one of claims 8 to 26, characterized in that, The first entity includes: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain.
28. An authentication method, characterized in that, Applied to a second entity, the method includes: The system receives a first key request message sent by a first proxy entity. The first key request message includes a second permission request parameter, which is a parameter determined by the first proxy entity based on the first permission request parameter sent by the user equipment. The first permission request parameter is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions. The second permission request parameter includes a key identifier A-KID corresponding to the user equipment, a first target entity identifier corresponding to the target entity, and a proxy entity identifier corresponding to the first proxy entity. The target entity is the entity that the user equipment determines from one or more first entities to request communication. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity. The first entity includes an untrusted authentication proxy AP entity outside the 3GPP operator domain. The second entity includes a Network Open Function (NEF) entity or a Service Capability Open Function (SCEF) entity. Obtain the first pending key information based on the second permission request parameters; A first key response message is sent to the first agent entity based on the first pending key information.
29. The method according to claim 28, characterized in that, The step of obtaining the first pending key information based on the second permission request parameter includes: The third permission request parameters are determined based on the second permission request parameters; A third key request message is sent to a third entity according to the third permission request parameters; the third entity includes an entity that provides AKMA authorization and application key deduction functions. Receive a third key response message sent by the third entity; the third key response message includes third pending key information, which is key information obtained by the third entity when it determines that the user equipment and the target entity have first communication permissions based on the third permission request parameters; Based on the third pending key information, the first pending key information is obtained.
30. The method according to claim 29, characterized in that, The first communication permission includes one or more of the following: The user equipment has access rights to the target entity; The user equipment has access rights to the first agent entity; The first proxy entity has proxy authority over the target entity; The target entity has permission to obtain the user identifier of the user equipment.
31. The method according to claim 29, characterized in that, Determining the third permission request parameter based on the second permission request parameter includes: Use the second permission request parameter as the third permission request parameter.
32. The method according to claim 29, characterized in that, The third pending key information includes the entity key information corresponding to the target entity; obtaining the first pending key information based on the third pending key information includes: The entity key information corresponding to the target entity is used as the first undetermined key information.
33. The method according to claim 32, characterized in that, The entity key information includes the application key KAF and the key validity period.
34. The method according to claim 29, characterized in that, The third key response message further includes a second user identifier corresponding to the user equipment; the first key response message sent to the first agent entity based on the first pending key information includes: The first user identifier is determined based on the second user identifier; A first key response message is sent to the first agent entity based on the first pending key information and the first user identifier.
35. The method according to claim 34, characterized in that, The first user identifier is the General Public User Identifier (GPSI) corresponding to the user equipment; the second user identifier is the User Permanent Identifier (SUPI) corresponding to the user equipment.
36. The method according to claim 28, characterized in that, After sending a first key response message to the first agent entity based on the first pending key information, the method further includes: The system receives a second key request message sent by a first agent entity; the second key request message is a message sent by the first agent entity to the second entity when it determines that the second target entity identifier is different from the first target entity identifier corresponding to the target entity; the second target entity identifier is a protected entity identifier obtained by the user equipment based on the first target entity identifier of the target entity. Determine whether the user equipment and the target entity have second communication permissions based on the second key request message; A second key response message is sent to the first agent entity; the second key response message is used to notify the first agent entity whether the user equipment and the target entity have second communication permissions.
37. The method according to claim 36, characterized in that, The second communication permission includes one or more of the following: The user equipment has access rights to the target entity; The first proxy entity has proxy authority over the target entity; The target entity has permission to obtain the user identifier of the user equipment.
38. The method according to claim 36, characterized in that, The second key request message includes the key identifier A-KID, the second target entity identifier, and the proxy entity identifier corresponding to the first proxy entity; The step of determining whether the user equipment and the target entity have second communication permissions based on the second key request message includes: Send a fourth key request message to a third entity; the fourth key request message includes the key identifier A-KID, the second target entity identifier, and the proxy entity identifier; Receive the fourth key response message sent by the third entity; The user equipment and the target entity are determined based on the fourth key response message to determine whether they have second communication permissions.
39. The method according to claim 38, characterized in that, Both the second key request message and the fourth key request message include an authorization indication parameter, which is used to instruct the third entity to determine whether the user equipment and the target entity have second communication permissions based on the fourth key request message.
40. The method according to claim 29, characterized in that, The third entity includes: the AKMA anchor function AAnF entity.
41. The method according to any one of claims 28 to 40, characterized in that, The first entity includes: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain.
42. An authentication method, characterized in that, Applied to a third entity, the method includes: The system receives a third key request message sent by a second entity. The third key request message includes a third permission request parameter, which is a parameter determined by the second entity based on the second permission request parameter. The second permission request parameter is a parameter determined by a first proxy entity based on a first permission request parameter sent by the user equipment. The first permission request parameter is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions. The third permission request parameter includes a key identifier (A-KID) corresponding to the user equipment, a first target entity identifier of the target entity, and a proxy entity identifier corresponding to the first proxy entity. The target entity is the entity that the user equipment determines from one or more first entities to request communication. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity. The first entity includes an untrusted authentication proxy (AP) entity outside the 3GPP operator domain. The second entity includes a Network Open Function (NEF) entity or a Service Capability Open Function (SCEF) entity. The third entity includes an AKMA anchor function (AAnF) entity. Based on the third permission request parameters, determine whether the user equipment and the target entity have first communication permissions; If the user equipment has first communication permission with the target entity, obtain third pending key information; Based on the third pending key information, a third key response message is sent to the second entity, the third key response message including the third pending key information.
43. The method according to claim 42, characterized in that, The step of determining whether the user equipment and the target entity have first communication permissions based on the third permission request parameters includes one or more of the following: Based on the key identifier A-KID and the first target entity identifier, it is determined whether the user equipment has access rights to the target entity; Based on the key identifier A-KID and the proxy entity identifier, it is determined whether the user equipment has access rights to the first proxy entity; Based on the proxy entity identifier and the first target entity identifier, determine whether the first proxy entity has proxy authority over the target entity; Based on the key identifier A-KID and the second target entity identifier, determine whether the target entity has permission to obtain the user identifier of the user equipment.
44. The method according to claim 42, characterized in that, The process of obtaining the third pending key information includes: Based on the entity key information corresponding to the target entity, the third pending key information is obtained.
45. The method according to claim 42, characterized in that, Sending a third key response message to the second entity based on the third pending key information includes: If it is determined that the target entity has the authority to obtain the user identifier, a third pending key information and a second user identifier corresponding to the user equipment are sent to the second entity through a third key response message.
46. The method according to claim 45, characterized in that, The second user identifier is the user permanent identifier SUPI corresponding to the user equipment.
47. The method according to claim 42, characterized in that, After sending a third key response message to the second entity, the method further includes: Receive the fourth key request message sent by the second entity; Determine whether the user equipment and the target entity have second communication permissions based on the fourth key request message; Send a fourth key response message to the second entity; the fourth key response message is used to notify the second entity whether the user equipment and the target entity have second communication permissions.
48. The method according to claim 47, characterized in that, The fourth key request message includes the key identifier A-KID, the second target entity identifier, and the proxy entity identifier corresponding to the first proxy entity. The second target entity identifier is a protected entity identifier obtained by the user equipment based on the first target entity identifier of the target entity. Determining whether the user equipment and the target entity have second communication permissions based on the fourth key request message includes one or more of the following: Based on the key identifier A-KID and the second target entity identifier, it is determined whether the user equipment has access rights to the target entity; Based on the proxy entity identifier and the second target entity identifier, determine whether the first proxy entity has proxy authority over the target entity; Based on the key identifier A-KID and the second target entity identifier, determine whether the target entity has permission to obtain the user identifier of the user equipment.
49. The method according to claim 47, characterized in that, The fourth key request message includes an authorization indication parameter, which is used to instruct the third entity to determine whether the user equipment and the target entity have second communication permissions based on the fourth key request message.
50. The method according to claim 47, characterized in that, Sending the fourth key response message to the second entity includes: If it is determined that the target entity has the authority to obtain the user identifier, a fourth key response message is sent to the second entity based on the second user identifier corresponding to the user equipment.
51. The method according to claim 50, characterized in that, The second user identifier is the user permanent identifier (SUPI) corresponding to the user equipment.
52. The method according to claim 47, characterized in that, Before determining whether the user equipment and the target entity have second communication permissions based on the fourth key request message, the method further includes: Determine whether the third entity has the authority to serve the first proxy entity according to a preset strategy; The step of determining whether the user equipment and the target entity have second communication permissions based on the fourth key request message includes: In determining whether the third entity has the authority to serve the first agent entity, the user equipment and the target entity have the second communication authority based on the fourth key request message.
53. The method according to claim 42, characterized in that, Before determining whether the user equipment and the target entity have first communication permissions based on the third permission request parameters, the method further includes: Determine whether the third entity has the authority to serve the first proxy entity according to a preset strategy; The step of determining whether the user equipment and the target entity have the first communication permission based on the third permission request parameter includes: In determining whether the third entity has the authority to serve the first proxy entity, the user equipment and the target entity have the first communication authority based on the third authority request parameters.
54. The method according to any one of claims 42 to 53, characterized in that, The first entity includes: an untrusted application function (AF) entity outside the 3GPP operator domain, or an untrusted application server (SCS / AS) entity outside the 3GPP operator domain.
55. An authentication device, characterized in that, Applied to user equipment, the device includes: The target entity determination module is configured to determine the target entity for the requested communication from one or more first entities; The parameter determination module is configured to use the first target entity identifier of the target entity and the key identifier A-KID corresponding to the user equipment as the first permission request parameters; The first message sending module is configured to send an application session establishment request message to the first proxy entity according to the first permission request parameters; the application session establishment request message is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions according to the first permission request parameters; the first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions, the first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions, the first proxy entity provides authentication proxy functions for the first entity, and the first proxy entity includes an untrusted authentication proxy AP entity outside the 3GPP operator domain; The first message receiving module is configured to determine whether the user equipment and the target entity have first communication permissions in response to receiving an application session establishment response message sent by the first agent entity. The authentication module is configured to perform identity authentication through the first proxy entity when the user equipment has first communication permissions with the target entity.
56. An authentication device, characterized in that, Applied to a first agent entity, the device includes: The first proxy receiving module is configured to receive an application session establishment request message sent by a user equipment. The application session establishment request message includes a first permission request parameter. The application session establishment request message is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameter. The first permission request parameter includes a first target entity identifier of the target entity and a key identifier A-KID corresponding to the user equipment. The target entity is the entity that the user equipment determines from one or more first entities to request communication. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity. The first proxy entity includes an untrusted authentication proxy AP entity outside the 3GPP operator domain. The first agent determination module is configured to determine whether the user device and the target entity have first communication permissions based on the first permission request parameters. The first proxy sending module is configured to send an application session establishment response message to the user equipment and to authenticate the user equipment when the user equipment and the target entity have first communication permissions.
57. An authentication device, characterized in that, Applied to a second entity, the device includes: The second receiving module is configured to receive a first key request message sent by a first proxy entity. The first key request message includes a second permission request parameter, which is a parameter determined by the first proxy entity based on the first permission request parameter sent by the user equipment. The first permission request parameter is used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions based on the first permission request parameter. The second permission request parameter includes a key identifier A-KID corresponding to the user equipment, a first target entity identifier corresponding to the target entity, and a proxy entity identifier corresponding to the first proxy entity. The target entity is the entity that the user equipment determines from one or more first entities to request communication. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity. The first entity includes an untrusted authentication proxy AP entity outside the 3GPP operator domain. The second entity includes a Network Open Function (NEF) entity or a Service Capability Open Function (SCEF) entity. The second key acquisition module is configured to acquire the first pending key information based on the second permission request parameters; The second sending module is configured to send a first key response message to the first agent entity based on the first pending key information.
58. An authentication device, characterized in that, Applied to a third entity, the device includes: The third receiving module is configured to receive a third key request message sent by the second entity. The third key request message includes third permission request parameters, which are parameters determined by the second entity based on the second permission request parameters. The second permission request parameters are parameters determined by the first proxy entity based on the first permission request parameters sent by the user equipment. The first permission request parameters are used to instruct the first proxy entity to determine whether the user equipment and the target entity have first communication permissions. The third permission request parameters include the key identifier A-KID corresponding to the user equipment, the first target entity identifier of the target entity, and the proxy entity identifier corresponding to the first proxy entity. The target entity is the entity that the user equipment determines from one or more first entities to request communication. The first entity includes an untrusted entity outside the 3GPP operator domain that provides application functions. The first proxy entity includes an untrusted entity outside the 3GPP operator domain that provides authentication functions. The first proxy entity provides authentication proxy functions for the first entity. The first proxy entity includes an untrusted authentication proxy AP entity outside the 3GPP operator domain. The second entity includes a Network Open Function (NEF) entity or a Service Capability Open Function (SCEF) entity. The third entity includes an AKMA anchor function (AAnF) entity. The third determining module is configured to determine whether the user equipment and the target entity have first communication permissions based on the third permission request parameters. The third key module is configured to obtain third pending key information when the user equipment has first communication permission with the target entity; The third sending module is configured to send a third key response message to the second entity based on the third pending key information, wherein the third key response message includes the third pending key information.
59. An authentication device, characterized in that, The device includes: processor; Memory used to store processor-executable instructions; The processor is configured to perform the steps of the method according to any one of claims 1 to 7, or the processor is configured to perform the steps of the method according to any one of claims 8 to 27, or the processor is configured to perform the steps of the method according to any one of claims 28 to 41, or the processor is configured to perform the steps of the method according to any one of claims 42 to 54.
60. A computer-readable storage medium having computer program instructions stored thereon, characterized in that, When the computer program instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7; or, when the computer program instructions are executed by a processor, they implement the steps of the method according to any one of claims 8 to 27; or, when the computer program instructions are executed by a processor, they implement the steps of the method according to any one of claims 28 to 41; or, when the computer program instructions are executed by a processor, they implement the steps of the method according to any one of claims 42 to 54.
61. A chip, characterized in that, The method includes a processor and an interface; the processor is configured to read instructions to perform the steps of the method according to any one of claims 1 to 7, or the processor is configured to read instructions to perform the steps of the method according to any one of claims 8 to 27, or the processor is configured to read instructions to perform the steps of the method according to any one of claims 28 to 41, or the processor is configured to read instructions to perform the steps of the method according to any one of claims 42 to 54.
Citation Information
Patent Citations
Authentication proxy for AKMA authentication service
EP4271014A1
