Authorization revocation method and apparatus
By sending authorization revocation requests in the CAPIF framework to delete the refresh token, the problem of high CCF memory footprint is solved, and the performance and efficiency of the API framework is improved.
Patent Information
- Application Number
- PCT/CN2023/094069
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-12
- Publication Date
- 2024-11-21
AI Technical Summary
In the API call scenario that subscribers are aware of, CCF cannot effectively clear a large amount of security and authorization information, resulting in high memory usage and reduced performance.
By sending an authorization revocation request to the first entity in the CAPIF framework, it instructs a refresh token to delete the security and authorization information stored in the CCF, reducing the burden on the CCF, and improving the performance of the API framework.
It has achieved the reduction of CCF memory footprint, improved the processing speed and efficiency of the API framework, and improved the performance of data processing.
Smart Images

Figure CN2023094069_21112024_PF_FP_ABST
Abstract
Description
Authorization revocation method and device Technical Field
[0001] The present application relates to the field of communication technology, and in particular to an authorization revocation method and apparatus thereof. Background Art
[0002] In subscriber-aware northbound API access (SNA) scenarios, the Common API Framework (CAPIF) core function (CCF) obtains authorization from the resource owner and accesses the target resource based on the authorization information. During this process, CCF needs to store all security and authorization information related to the API caller and the resource owner. Since CCF cannot clear this large amount of security and authorization information, it consumes a large amount of memory, burdening CCF and affecting the performance of the Common API Framework.
[0003] Summary of the Invention
[0004] The embodiments of the present application provide an authorization revocation method and apparatus thereof, which can be applied in the communication field to solve the problem that CCF cannot clear a large amount of security and authorization information, reduce the burden on CCF, and improve the performance of the general API framework.
[0005] In a first aspect, an embodiment of the present application provides a method for revoking authorization, the method comprising:
[0006] A first authorization revocation request is sent to a first entity in a common application programming interface (CAPIF) framework, wherein the first authorization revocation request is used to indicate a refresh token associated with a resource owner.
[0007] In this technical solution, the second entity sends an indicated refresh token authorization revocation request to the first entity to achieve the purpose of revoking authorization, thereby deleting a large amount of security and authorization information stored in the CCF, reducing the burden on the CCF, improving the performance of the CAPIF framework, and thus improving the speed and efficiency of data processing.
[0008] In a second aspect, an embodiment of the present application provides another authorization revocation method, the method comprising:
[0009] A first authorization revocation request or a third authorization revocation request is received, wherein the first authorization revocation request or the second authorization revocation request is used to indicate a refresh token related to a resource owner; and a revocation operation is performed on the refresh token based on the first authorization revocation request or the third authorization revocation request.
[0010] In a third aspect, an embodiment of the present application provides another authorization revocation method, the method comprising:
[0011] Send a second authorization revocation request to a second entity, wherein the second authorization revocation request is used to determine the first authorization revocation request sent to the first entity; or, send a third authorization revocation request to the first entity in the CAPIF framework; wherein the first authorization revocation request or the second authorization revocation request or the third authorization revocation request is used to indicate a refresh token associated with the resource owner.
[0012] In a fourth aspect, an embodiment of the present application provides a communication device that has the function of implementing some or all of the functions of the second entity in the method described in the first aspect above. For example, the functions of the communication device may have the functions of some or all of the embodiments in this application, or may have the function of implementing any one of the embodiments in this application separately. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.
[0013] In one implementation, the communication device may include a transceiver module and a processing module, wherein the processing module is configured to support the communication device in performing the corresponding functions of the above-mentioned method. The transceiver module is used to support communication between the communication device and other devices. The communication device may also include a storage module, which is coupled to the transceiver module and the processing module and stores computer programs and data necessary for the communication device.
[0014] As an example, the processing module may be a processor, the transceiver module may be a transceiver or a communication interface, and the storage module may be a memory.
[0015] In a fifth aspect, an embodiment of the present application provides another communication device, which has some or all of the functions of the first entity in the CAPIF framework in the method example described in the second aspect above. For example, the functions of the communication device may have the functions of some or all of the embodiments in this application, or may have the functions of implementing any one of the embodiments in this application separately. The functions can be implemented by hardware, or by executing corresponding software implementations through hardware. The hardware or software includes one or more units or modules corresponding to the above functions.
[0016] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions of the above-described method. The transceiver module is configured to support communication between the communication device and other devices. The communication device may also include a storage module, coupled to the transceiver module and the processing module, which stores computer programs and data necessary for the communication device.
[0017] As an example, the processing module may be a processor, the transceiver module may be a transceiver or a communication interface, and the storage module may be a memory.
[0018] In a sixth aspect, an embodiment of the present application provides another communication device, which has the function of implementing some or all of the functions of the resource owner client or terminal device in the method example described in the third aspect above. For example, the functions of the communication device may have the functions of some or all of the embodiments in this application, or may have the function of implementing any one of the embodiments in this application alone. The functions may be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more units or modules corresponding to the above functions.
[0019] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions of the above-described method. The transceiver module is configured to support communication between the communication device and other devices. The communication device may also include a storage module, coupled to the transceiver module and the processing module, which stores computer programs and data necessary for the communication device.
[0020] As an example, the processing module may be a processor, the transceiver module may be a transceiver or a communication interface, and the storage module may be a memory.
[0021] In a seventh aspect, an embodiment of the present application provides a communication device, which includes a processor. When the processor calls a computer program in a memory, it executes the method described in the first aspect above.
[0022] In an eighth aspect, an embodiment of the present application provides a communication device, which includes a processor. When the processor calls a computer program in a memory, it executes the method described in the second aspect above.
[0023] In a ninth aspect, an embodiment of the present application provides a communication device, which includes a processor. When the processor calls a computer program in a memory, it executes the method described in the third aspect above.
[0024] In the tenth aspect, an embodiment of the present application provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the first aspect above.
[0025] In the eleventh aspect, an embodiment of the present application provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the second aspect above.
[0026] In the twelfth aspect, an embodiment of the present application provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the third aspect above.
[0027] In the thirteenth aspect, an embodiment of the present application provides a communication device, which includes a processor and an interface circuit, the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the first aspect above.
[0028] In the fourteenth aspect, an embodiment of the present application provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the second aspect above.
[0029] In the fifteenth aspect, an embodiment of the present application provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the third aspect above.
[0030] In the sixteenth aspect, an embodiment of the present application provides an authorization revocation system, which includes the communication device described in the fourth aspect, the communication device described in the fifth aspect, and the communication device described in the sixth aspect, or the system includes the communication device described in the seventh aspect, the communication device described in the eighth aspect, and the communication device described in the ninth aspect, or the system includes the communication device described in the tenth aspect, the communication device described in the eleventh aspect, and the communication device described in the twelfth aspect, or the system includes the communication device described in the thirteenth aspect, the communication device described in the fourteenth aspect, and the communication device described in the fifteenth aspect.
[0031] In a seventeenth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions for the second entity, and when the instructions are executed, the second entity executes the method described in the first aspect.
[0032] In the eighteenth aspect, an embodiment of the present invention provides a readable storage medium for storing instructions used by the first entity in the above-mentioned CAPIF framework. When the instructions are executed, the first entity in the CAPIF framework executes the method described in the above-mentioned second aspect.
[0033] In the nineteenth aspect, an embodiment of the present invention provides a readable storage medium for storing instructions used by the above-mentioned resource owner client or terminal device. When the instructions are executed, the resource owner client or terminal device executes the method described in the above-mentioned third aspect.
[0034] In the twentieth aspect, the present application further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.
[0035] In the twenty-first aspect, the present application also provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the second aspect above.
[0036] In the twenty-second aspect, the present application also provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the third aspect above.
[0037] In a twenty-third aspect, the present application provides a chip system comprising at least one processor and an interface for supporting a second entity in implementing the functions described in the first aspect, such as determining or processing at least one of the data and information described in the above method. In one possible design, the chip system further comprises a memory for storing computer programs and data necessary for the second entity. The chip system may be composed of a chip or may include a chip and other discrete components.
[0038] In a twenty-fourth aspect, the present application provides a chip system comprising at least one processor and an interface for supporting the first entity in the CAPIF framework to implement the functions involved in the second aspect, for example, determining or processing at least one of the data and information involved in the above method. In one possible design, the chip system further comprises a memory for storing the necessary computer programs and data for the first entity in the CAPIF framework. The chip system may be composed of a chip or may include a chip and other discrete devices.
[0039] In aspect 25, the present application provides a chip system comprising at least one processor and an interface for supporting a resource owner client or terminal device in implementing the functions described in aspect 3, such as determining or processing at least one of the data and information described in the aforementioned method. In one possible design, the chip system further comprises a memory for storing computer programs and data necessary for the resource owner client or terminal device. The chip system may consist of a chip alone or may include a chip and other discrete components.
[0040] In the twenty-sixth aspect, the present application provides a computer program which, when executed on a computer, enables the computer to execute the method described in the first aspect above.
[0041] In aspect 27, the present application provides a computer program which, when executed on a computer, enables the computer to execute the method described in aspect 2 above.
[0042] In aspect 28, the present application provides a computer program which, when executed on a computer, enables the computer to execute the method described in aspect 3 above. BRIEF DESCRIPTION OF THE DRAWINGS
[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background technology, the drawings required for use in the embodiments of the present application or the background technology will be described below.
[0044] FIG1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;
[0045] FIG2 is a flow chart of an authorization revocation method provided in an embodiment of the present application;
[0046] FIG3 is a flow chart of another authorization revocation method provided in an embodiment of the present application;
[0047] FIG4 is a flow chart of another authorization revocation method provided in an embodiment of the present application;
[0048] FIG5 is a flow chart of another authorization revocation method provided in an embodiment of the present application;
[0049] FIG6 is a flow chart of another authorization revocation method provided in an embodiment of the present application;
[0050] FIG7 is a flow chart of another authorization revocation method provided in an embodiment of the present application;
[0051] FIG8 is a flow chart of another authorization revocation method provided in an embodiment of the present application;
[0052] FIG9 is a flow chart of another authorization revocation method provided in an embodiment of the present application;
[0053] FIG10 is a flow chart of another authorization revocation method provided in an embodiment of the present application;
[0054] FIG11 is a flow chart of another authorization revocation method provided in an embodiment of the present application;
[0055] FIG12 is an interactive diagram of an authorization revocation method provided in an embodiment of the present application;
[0056] FIG13 is an interactive diagram of another authorization revocation method provided in an embodiment of the present application;
[0057] FIG14 is a schematic structural diagram of a communication device provided in an embodiment of the present application;
[0058] FIG15 is a schematic structural diagram of another communication device provided in an embodiment of the present application;
[0059] FIG16 is a schematic structural diagram of a chip provided in an embodiment of the present application;
[0060] FIG17 is a communication system for authorization revocation provided in an embodiment of the present application;
[0061] FIG18 is another communication system for authorization revocation provided in an embodiment of the present application. DETAILED DESCRIPTION
[0062] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
[0063] The terms used in the embodiments of the present disclosure are for the purpose of describing specific embodiments only and are not intended to limit the embodiments of the present disclosure. The singular forms "a," "an," and "the" used in the embodiments of the present disclosure and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and includes any or all possible combinations of one or more associated listed items.
[0064] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining" For the purpose of brevity and ease of understanding, the terms used herein when characterizing size relationships are "greater than" or "less than", "higher than" or "lower than". However, for those skilled in the art, it can be understood that the term "greater than" also covers the meaning of "greater than or equal to", and "less than" also covers the meaning of "less than or equal to"; the term "higher than" covers the meaning of "higher than or equal to", and "lower than" also covers the meaning of "lower than or equal to".
[0065] In order to better understand the authorization revocation method disclosed in the embodiment of the present application, the communication system to which the embodiment of the present application is applicable is first described below.
[0066] Please refer to Figure 1, which is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. The communication system may include, but is not limited to, a network device and a terminal device. The number and form of devices shown in Figure 1 are for example purposes only and do not constitute a limitation on the embodiments of the present application. In actual applications, two or more network devices and two or more terminal devices may be included. The communication system shown in Figure 1 includes, for example, a network device 101 and a terminal device 102.
[0067] It should be noted that the technical solutions of the embodiments of the present application can be applied to various communication systems. For example, the third generation (3G) universal mobile telecommunications system (UMTS) long term evolution (LTE) system, the fifth generation (5G) mobile communication system, the 5G new radio (NR) system, the sixth generation (6G) mobile communication system, or other future new mobile communication systems.
[0068] The network device 101 in the embodiment of the present application is an entity on the network side for transmitting or receiving signals. For example, the network device 101 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device. The network device provided in the embodiment of the present application can be composed of a centralized unit (CU) and a distributed unit (DU), wherein the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the network device, such as the base station, and the functions of some protocol layers are placed in the CU for centralized control, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.
[0069] The terminal device 102 in the embodiment of the present application is an entity on the user side for receiving or transmitting signals, such as a mobile phone. The terminal device can also be called a terminal device (terminal), user equipment (UE), mobile station (MS), mobile terminal device (MT), etc. The terminal device can be a car with communication function, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in smart city (smart city), a wireless terminal device in smart home (smart home), etc. The embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal device.
[0070] It can be understood that the communication system described in the embodiment of the present application is for the purpose of more clearly illustrating the technical solution of the embodiment of the present application, and does not constitute a limitation on the technical solution provided by the embodiment of the present application. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present application is also applicable to similar technical problems.
[0071] It should be noted that the authorization revocation method provided in any embodiment of the present application can be executed alone, or in combination with possible implementation methods in other embodiments, or in combination with any technical solution in related technologies.
[0072] The authorization revocation method and device provided by this application are described in detail below with reference to the accompanying drawings.
[0073] Please refer to Figure 2, which is a flow chart of a method for revoking authorization provided in an embodiment of the present application. The method for revoking authorization may be performed by a second entity. As shown in Figure 2, the method may include but is not limited to the following steps:
[0074] S201: Send a first authorization revocation request to a first entity in a CAPIF framework, where the first authorization revocation request is used to indicate a refresh token related to a resource owner.
[0075] In some implementations, the second entity may be an API caller. Optionally, the API caller may be an application function or a client running on a terminal.
[0076] In some implementations, the first entity in the CAPIF framework may include a CAPIF core function (CCF) or an authorization function in the Common API Framework (CAPIF). It should be noted that the first entity is a CCF network element or an authorization function. The CCF network element or the authorization function will be integrated under certain conditions, that is, the CCF network element can also assume the responsibilities of the authorization function at the same time.
[0077] In some implementations, the API caller can obtain a refresh token associated with the resource owner from the CCF or authorization function in CAPIF. In some implementations, the API caller can perform authorization interaction with the CCF or authorization function based on a network protocol to obtain a refresh token associated with the resource owner.
[0078] In some implementations, the refresh token associated with the resource owner is a refresh token including identification information of the resource owner. Optionally, the resource owner identification may be a generic public subscription identifier (GPSI).
[0079] In some implementations, a refresh token associated with a resource owner can be used to generate an access token for a resource, so that an API caller can access the corresponding resource based on the access token.
[0080] In some implementations, the API caller may send a first authorization revocation request to the first entity, wherein the first authorization revocation request is used to indicate a refresh token associated with the resource owner.
[0081] In some implementations, if the first authorization revocation request includes a refresh token, the refresh token includes the resource owner identifier.
[0082] Optionally, the first authorization revocation request may explicitly indicate a refresh token associated with the resource owner. The API caller may directly send the refresh token associated with the resource owner to the first entity in the first authorization revocation request.
[0083] Optionally, the first authorization revocation request may implicitly indicate a refresh token associated with the resource owner. The first authorization revocation request sent by the API caller may carry parameter information related to the refresh token, and the first entity may indicate the refresh token based on the parameter information. For example, the first authorization revocation request may include at least one of the following information: the resource identifier of the authorized resource; the operation identifier of the semantic operation that can be performed on the authorized resource; the identification information of the second entity; and the identification information of the resource owner.
[0084] In some implementations, the first authorization revocation request may include identification information of the resource owner. The first entity may determine the refresh token that needs to be revoked based on the identification information of the resource owner in the first revocation request, and revoke the refresh token.
[0085] In some implementations, the resource owner is an end user or a subscriber associated with an end user or a human being.
[0086] In some implementations, after obtaining a refresh token, the API caller can send an access token request to the first entity. Accordingly, upon receiving the access token request, the first entity can generate an access token based on the refresh token. The API caller can receive the access token sent by the first entity and send it to the resource owner. Furthermore, the API caller can access the corresponding resource based on the access token.
[0087] In some implementations, the API caller can send a refresh token and / or a token type of the refresh token to the first entity via the first authorization revocation request.
[0088] In an embodiment of the present application, the API caller sends an authorization revocation request indicating a refresh token to the first entity to achieve the purpose of revoking authorization, thereby deleting a large amount of security and authorization information stored in the CCF, reducing the burden on the CCF, improving the performance of the CAPIF framework, and thereby improving the speed and efficiency of data processing.
[0089] Please refer to Figure 3, which is a flowchart of a method for revoking authorization provided by an embodiment of the present application. The method for revoking authorization can be performed by a second entity. As shown in Figure 3, the method can include but is not limited to the following steps:
[0090] S301: Send a first authorization revocation request to a first entity in the CAPIF framework.
[0091] In some implementations, the second entity may be an API caller. Optionally, the API caller may be an application function or a client running on a terminal.
[0092] In the embodiment of the present application, the implementation method of step S301 can be implemented by any method in the various embodiments of the present application, which is not limited here and will not be repeated.
[0093] S302: Receive a revocation response message corresponding to a first authorization revocation request sent by a first entity.
[0094] In some implementations, after receiving the first authorization revocation request, the first entity can perform a revocation operation based on the refresh token indicated by the first authorization revocation request. After completing the revocation operation, the first entity can generate a revocation response message corresponding to the first authorization revocation request and feedback it to the API caller. The API caller can determine whether the refresh token is successfully revoked based on the revocation response message. If the revocation is not successful, the refresh token can be sent again for authorization revocation.
[0095] Based on the above embodiment, the authorization revocation method may further include the following steps:
[0096] S303: Send a revocation response message to the terminal device or the resource owner client or the resource owner.
[0097] In some implementations, after receiving the revocation response message corresponding to the first authorization revocation request sent by the first entity, the API caller should also send a revocation response message to the terminal device, resource owner client, or resource owner. The terminal device, resource owner client, or resource owner can determine whether the refresh token is successfully revoked based on the revocation response message. If not, the refresh token can be reauthorized again.
[0098] In an embodiment of the present application, the API caller sends an authorization revocation request indicating a refresh token to the first entity. The API caller also needs to accept the revocation response message sent by the first entity and send a revocation response message to the terminal device or resource owner client or resource owner to achieve the purpose of revoking the authorization. This deletes a large amount of security and authorization information stored in the CCF, reduces the burden on the CCF, improves the performance of the CAPIF framework, and improves the speed and efficiency of data processing. The API caller and the terminal device or resource owner client or resource owner receive the revocation response message sent by the first entity, and can promptly understand whether the authorization revocation is successful, and then promptly terminate the authorization.
[0099] Please refer to Figure 4, which is a flowchart of a method for revoking authorization provided by an embodiment of the present application. The method for revoking authorization can be performed by the second entity. As shown in Figure 4, the method can include but is not limited to the following steps:
[0100] S401: Receive a second authorization revocation request.
[0101] In some implementations, the second entity may be an API caller. Optionally, the API caller may be an application function or a client running on a terminal.
[0102] It should be noted that, in order to obtain a refresh token associated with the resource owner, the API caller (API invoker) can perform an authorization interaction with the first entity through a network protocol to obtain the refresh token associated with the resource owner. Furthermore, the API caller can obtain an access token from the first entity based on the refresh token, so that the API caller can access the corresponding resource through the access token.
[0103] In some implementations, the API caller may receive a second authorization revocation request sent by the terminal device.
[0104] In some implementations, the API caller can receive a second authorization revocation request sent by a resource owner client running on a terminal device. In some implementations, the resource owner can send the second authorization revocation request to the API caller (APIinvoker) by controlling the terminal or the resource owner client. In an exemplary embodiment, the resource owner client runs on the terminal device, and the resource owner interacts with the server through the client on the terminal device. For example, the resource owner client is a browser, the API caller is a server accessed by the browser, and the resource owner interacts with the server through the browser.
[0105] In some implementations, the API caller may receive a second authorization revocation request sent by the end device, a resource owner client running on the end device, or the resource owner.
[0106] Optionally, the second authorization revocation request includes at least one of the following information: a resource identifier of the authorized resource; an operation identifier of a semantic operation executable on the authorized resource; identification information of the second entity; and identification information of the resource owner. For example, the identification information of the resource owner may be GPSI.
[0107] S402: Generate a first authorization revocation request based on the second authorization revocation request, and send the first authorization revocation request to the first entity.
[0108] In some implementations, the first authorization revocation request is configured to indicate to the first entity a refresh token associated with the resource owner.
[0109] In some implementations, the API caller may receive the second authorization revocation request, determine a refresh token associated with the resource owner based on the second authorization revocation request, and generate a first authorization revocation request based on the refresh token. After generating the first authorization revocation request, the API caller sends the first authorization revocation request to the first entity.
[0110] In some implementations, the second authorization revocation request may include identification information of the resource owner. The API invoker may determine the refresh token that needs to be revoked based on the identification information of the resource owner in the second revocation request, and send the refresh token to the first entity through the first authorization revocation request. The first entity revokes the refresh token.
[0111] In some implementations, the API caller receives a second authorization revocation request sent by a terminal device or a resource owner client or resource owner running on the terminal device, and converts the resource identification information and semantic operation in the second authorization revocation request into 3GPP domain information, thereby determining a refresh token based on the 3GPP domain information, and sending the first authorization revocation request to the first entity based on the refresh token. In some implementations, the 3GPP domain information can be a specific data type structure, for example, a Monitoring Event Report, and attribute information in this data structure type, wherein the attribute information includes but is not limited to: API name and monitoring type.
[0112] In some implementations, the first authorization revocation request may be the same as the second authorization revocation request. In the case where the first authorization revocation request is the same as the second authorization revocation request, the first entity may convert the resource identification information and semantic operation in the first authorization revocation request into information in the 3GPP domain, thereby determining the refresh token based on the information in the 3GPP domain, and further performing a revocation operation on the refresh token.
[0113] Based on the above embodiment, the authorization revocation method may further include the following steps:
[0114] S403: Receive a revocation response message corresponding to the first authorization revocation request sent by the first entity.
[0115] S404: Send a revocation response message to the terminal device, the resource owner client, or the resource owner.
[0116] In the embodiment of the present application, steps S403 to S404 may be implemented in any of the embodiments of the present application, which is not limited here and will not be described in detail.
[0117] In this embodiment of the present application, an API caller performs an authorization interaction with a first entity to obtain a refresh token. Furthermore, the API caller accepts a second authorization revocation request from the resource owner's client or terminal, determines the refresh token based on the second authorization revocation request, generates a first authorization revocation request, and sends the first authorization revocation request to the first entity to revoke the authorization. This removes a large amount of security and authorization information stored in the CCF, reduces the burden on the CCF, improves the performance of the CAPIF framework, and ultimately increases the speed and efficiency of data processing.
[0118] Please refer to Figure 5, which is a flowchart of a method for revoking authorization provided by an embodiment of the present application. The method for revoking authorization can be performed by the second entity. As shown in Figure 5, the method can include but is not limited to the following steps:
[0119] S501: Receive a second authorization revocation request.
[0120] In some implementations, the second entity may be an API caller. Optionally, the API caller may be an application function or a client running on a terminal.
[0121] In the embodiment of the present application, the implementation method of step S501 can be implemented by any method in the various embodiments of the present application, which is not limited here and will not be repeated.
[0122] S502: Determine a refresh token based on the second authorization revocation request.
[0123] In some implementations, the API caller can determine the refresh token based on parameter information related to the refresh token included in the second authorization revocation request. Optionally, the second authorization request includes a resource identifier and / or a semantic operation identifier, and the API caller can determine the refresh token based on the resource identifier and / or the semantic operation identifier. In some implementations, the resource identifier and / or the operation identifier are converted to generate 3GPP domain information, and the refresh token is determined based on the 3GPP domain information.
[0124] In some implementations, the information in the 3GPP field can be a specific data type structure, for example, a monitoring event report, and attribute information in this data structure type, wherein the attribute information includes but is not limited to: API name, monitoring type.
[0125] In some implementations, the second authorization revocation request may include identification information of the resource owner. The API invoker may determine the refresh token to be revoked based on the identification information of the resource owner in the second revocation request, and send the refresh token to the first entity via the first authorization revocation request. The first entity then revokes the refresh token. S503: Send the first authorization revocation request to the first entity based on the refresh token.
[0126] In some implementations, the API caller may generate a first authorization revocation request based on the refresh token determined by the second authorization revocation request, and send the first authorization revocation request to the first entity.
[0127] In some implementations, the API caller may send the refresh token and / or the token type of the refresh token to the first entity.
[0128] Based on the above embodiment, the authorization revocation method may further include the following steps:
[0129] S504: Receive a revocation response message corresponding to the first authorization revocation request sent by the first entity.
[0130] S505: Send a revocation response message to the terminal device or the resource owner client or the resource owner.
[0131] In the embodiment of the present application, steps S504 to S505 may be implemented in any of the embodiments of the present application, which is not limited here and will not be described in detail.
[0132] In an embodiment of the present application, an API caller performs an authorization interaction with a first entity to obtain a refresh token. Furthermore, the API caller accepts a second authorization revocation request sent by a resource owner client or terminal, determines the refresh token based on the second authorization revocation request, generates a first authorization revocation request based on the refresh token, and sends the first authorization revocation request to the first entity to achieve the purpose of revoking authorization, thereby deleting a large amount of security and authorization information stored in the first entity, reducing the burden on the CCF, improving the performance of the CAPIF framework, and increasing the speed and efficiency of data processing.
[0133] Please refer to Figure 6, which is a flowchart of a method for revoking authorization provided in an embodiment of the present application. The authorization revocation method can be executed by the first entity in the CAPIF framework. As shown in Figure 6, the method can include but is not limited to the following steps:
[0134] S601: Receive a first authorization revocation request or a third authorization revocation request, where the first authorization revocation request or the third authorization revocation request is used to indicate a refresh token related to a resource owner.
[0135] S602: Perform a revocation operation on the refresh token based on the first authorization revocation request or the third authorization revocation request.
[0136] It should be noted that the first or third authorization revocation request indicates a refresh token associated with the resource owner. The first entity needs to perform authorization interaction with the API caller via a network protocol and send the refresh token associated with the resource owner to the API caller. The first entity is either the CCF network element or the authorization function. Under certain conditions, the CCF network element and the authorization function are integrated, meaning that the CCF also assumes the responsibilities of the authorization function.
[0137] In some implementations, a refresh token associated with a resource owner can be used to generate an access token for a resource, so that the resource owner can access the corresponding resource based on the access token.
[0138] In some implementations, the first entity may receive a first authorization revocation request sent by an API caller. Optionally, the first authorization revocation request may directly indicate a refresh token associated with the resource owner, or indirectly indicate a refresh token associated with the resource owner through parameter information.
[0139] In some implementations, the first entity may receive a third authorization revocation request sent by a terminal device or a resource owner client running on the terminal device or the resource owner. In some implementations, the resource owner may send the third authorization revocation request to the first entity in the CAPIF framework by controlling the terminal or the resource owner client.
[0140] Optionally, the third authorization revocation request may directly include the refresh token related to the resource owner, or indirectly indicate the refresh token related to the resource owner through parameter information related to the refresh token.
[0141] In some implementations, if the first authorization revocation request or the third authorization revocation request includes a refresh token, the refresh token includes the resource owner identifier.
[0142] Optionally, the first authorization revocation request or the third authorization revocation request may implicitly indicate a refresh token to the first entity.
[0143] In some implementations, the first authorization revocation request or the third authorization revocation request includes at least one of the following information: a resource identifier of the authorized resource; an operation identifier of a semantic operation executable on the authorized resource; identification information of the second entity; and identification information of the resource owner.
[0144] In some implementations, the first entity may determine a refresh token based on at least one information in the first authorization revocation request or the third authorization revocation request, and perform a revocation operation on the refresh token.
[0145] Optionally, the first entity may determine the refresh token that needs to be revoked through identification information of the resource owner in the first authorization revocation request or the third authorization revocation request, and perform a revocation operation on the refresh token.
[0146] Optionally, the first entity may convert the resource owner's identification information and the operation identifier of the semantic operation in the first authorization revocation request or the third authorization revocation request into 3GPP domain information, and determine the refresh token based on the 3GPP domain information. Furthermore, after receiving the refresh token to be revoked, the first entity may perform a revocation operation on the refresh token.
[0147] In some implementations, the information in the 3GPP field can be a specific data type structure, for example, a monitoring event report, and attribute information in this data structure type, wherein the attribute information includes but is not limited to: API name, monitoring type.
[0148] In some implementations, the content of the first authorization revocation request may be the same as the content of the third authorization revocation request. In such cases, the first authorization revocation request and the third authorization revocation request may both optionally include the refresh token to be revoked. Optionally, the first authorization revocation request and the third authorization revocation request may both include parameter information related to the refresh token to be revoked. In the scenario where the parameter information related to the refresh token is carried, the first entity may determine the refresh token based on at least one piece of information in the received authorization revocation request and perform a revocation operation on the refresh token.
[0149] Optionally, the revocation operation may include, but is not limited to, deleting the refresh token, deleting information related to the refresh token, deleting an access token associated with the refresh token, etc. Optionally, the refresh token related information may include the identifier of the resource owner, the identifier of the authorized resource, and other information.
[0150] In some implementations, an access token can be determined based on a refresh token, and the first entity receives an access token application request sent by an API caller and generates a corresponding access token based on the refresh token. In this application, after the first entity performs a revocation operation on the refresh token based on the first authorization revocation request or the third authorization revocation request, if the first entity receives an access token application request sent by the API caller, the first entity stops generating access tokens based on the refresh token, thereby making the refresh token unable to be used to obtain a new access token. Accordingly, the resource owner cannot obtain a new access token and cannot access the resource, which effectively stops the authorized access rights associated with the refresh token.
[0151] In an embodiment of the present application, the first entity may receive a first authorization revocation request sent by an API caller, or may receive a third authorization revocation request sent by a terminal device or a resource owner client running on the terminal device or a resource owner. The first entity determines a refresh token based on the first authorization revocation request or the third authorization revocation request, and performs a revocation operation on the refresh token to achieve the purpose of revoking authorization. This can delete a large amount of security and authorization information stored in the CCF, reduce the burden on the CCF, improve the performance of the CAPIF framework, and thereby improve the speed and efficiency of data processing.
[0152] Please refer to Figure 7, which is a flowchart of a method for revoking authorization provided by an embodiment of the present application. The authorization revocation method can be executed by the first entity in the CAPIF framework. As shown in Figure 7, the method can include but is not limited to the following steps:
[0153] S701: Receive a first authorization revocation request.
[0154] In some implementations, the first entity may receive the first authorization revocation request sent by the second entity. Optionally, the second entity may be an API invoker, and optionally, the API invoker may be an application function or a client running on a terminal.
[0155] S702: Determine a refresh token based on the first authorization revocation request.
[0156] In some implementations, the first authorization revocation request may directly indicate or include a refresh token associated with the resource owner. Optionally, if the third authorization revocation request includes a refresh token, the refresh token includes resource owner identification information (eg, GPSI).
[0157] In some implementations, the first authorization revocation request may indirectly indicate the refresh token associated with the resource owner via parameter information associated with the refresh token. For example, the first authorization revocation request may include at least one of the following information: a resource identifier of the authorized resource; an operation identifier of a semantic operation executable on the authorized resource; identification information of the second entity; or identification information of the resource owner. The first entity may determine the refresh token based on the inclusion of the above information in the first authorization revocation request. The specific process for determining the refresh token based on the inclusion of the above information in the first authorization revocation request can be found in the relevant description of the above embodiments and will not be further described here.
[0158] S703: Perform a revocation operation on the refresh token.
[0159] In the embodiment of the present application, the implementation method of step S703 can be implemented by any method in the various embodiments of the present application, which is not limited here and will not be repeated.
[0160] Based on the above embodiment, the authorization revocation method may further include the following steps:
[0161] S704: Send a revocation response message corresponding to the first authorization revocation request to the second entity.
[0162] In some implementations, the first entity receives a first revocation authorization request from an API caller, determines the refresh token, performs a revocation operation on the refresh token, and generates a corresponding revocation response message. After performing the revocation operation, the first entity also sends a corresponding revocation response message to the API caller. The API caller can determine whether the refresh token was successfully revoked based on the revocation response message. If not, the API caller can reauthorize the refresh token again.
[0163] In an embodiment of the present application, the first entity can receive a first authorization revocation request sent by an API caller and perform a revocation operation on the refresh token based on the first authorization revocation request to achieve the purpose of revoking authorization. This can delete a large amount of security and authorization information stored in the CCF, reduce the burden on the CCF, improve the performance of the CAPIF framework, and thus improve the speed and efficiency of data processing. Furthermore, a response message corresponding to the authorization revocation request is sent to the API caller, so that the API caller can promptly understand whether the authorization revocation is successful, and then promptly revoke the authorization again if it is unsuccessful, so as to achieve the purpose of revoking authorization.
[0164] Please refer to Figure 8, which is a flowchart of a method for revoking authorization provided by an embodiment of the present application. The authorization revocation method can be executed by the first entity in the CAPIF framework. As shown in Figure 8, the method may include but is not limited to the following steps:
[0165] S801: Receive a third authorization revocation request.
[0166] In some implementations, the first entity may receive a third authorization revocation request sent by the terminal device, a resource owner client running on the terminal device, or the resource owner.
[0167] S802: Determine a refresh token based on the third authorization revocation request.
[0168] In some implementations, the third authorization revocation request may directly indicate or include a refresh token associated with the resource owner. Optionally, if the third authorization revocation request includes a refresh token, the refresh token includes resource owner identification information (GPSI).
[0169] In some implementations, the third authorization revocation request may indirectly indicate the refresh token associated with the resource owner via parameter information related to the refresh token. For example, the third authorization revocation request may include at least one of the following information: a resource identifier of the authorized resource; an operation identifier of a semantic operation executable on the authorized resource; identification information of the second entity; and identification information of the resource owner. The first entity may determine the refresh token based on the third authorization revocation request including the above information. The specific process for determining the refresh token based on the third authorization revocation request including the above information can be found in the relevant description of the above embodiments and will not be repeated here.
[0170] S803: Perform a revocation operation on the refresh token.
[0171] In the embodiment of the present application, the implementation method of step S803 can be implemented by any method in the various embodiments of the present application, which is not limited here and will not be repeated.
[0172] Based on the above embodiment, the authorization revocation method may further include the following steps:
[0173] S804: Send a revocation response message corresponding to the third authorization revocation request to the terminal device, the resource owner client, or the resource owner.
[0174] In some implementations, the first entity receives a third authorization revocation request from a terminal device, resource owner client, or resource owner, determines the refresh token, performs a revocation operation on the refresh token, and generates a corresponding revocation response message. After performing the revocation operation, the first entity should also send a corresponding revocation response message to the terminal device, resource owner client, or resource owner. The terminal device, resource owner client, or resource owner can determine whether the refresh token is successfully revoked based on the revocation response message. If not, the first entity can perform another authorization revocation on the refresh token.
[0175] In an embodiment of the present application, the first entity can receive a third authorization revocation request sent by a terminal device or a resource owner client or resource owner running on the terminal device. The first entity performs a revocation operation on the refresh token related to the resource owner according to the third authorization revocation request, thereby deleting a large amount of security and authorization information stored in the CCF, reducing the burden on the CCF, improving the performance of the CAPIF framework, and thus improving the speed and efficiency of data processing. Furthermore, the response message corresponding to the authorization revocation request is sent to the terminal device or the resource owner client or the resource owner, so that the terminal device or the resource owner client or the resource owner can promptly understand whether the authorization revocation is successful, and then promptly revoke the authorization again if it is unsuccessful, so as to achieve the purpose of authorization revocation.
[0176] Please refer to Figure 9, which is a flowchart of a method for revoking authorization provided by an embodiment of the present application. The authorization revocation method can be executed by the resource owner client or terminal device. As shown in Figure 9, the method may include but is not limited to the following steps:
[0177] S901: Send a second authorization revocation request to the second entity; or send a third authorization revocation request to the first entity in the CAPIF framework.
[0178] In some implementations, the second entity may be an API caller. Optionally, the API caller may be an application function or a client running on a terminal.
[0179] In some implementations, the first entity is one of a CCF network element or an authorization function.
[0180] In some implementations, the resource owner may send a second authorization revocation request to the API caller (API invoker) through a control terminal or a resource owner client, or send a third authorization revocation request to the first entity in the CAPIF framework.
[0181] In some implementations, the resource owner client or terminal device may send a second authorization revocation request to the API caller, where the second authorization revocation request is used to determine the first authorization revocation request sent to the first entity.
[0182] In some implementations, the resource owner client or terminal device may send a third authorization revocation request to the first entity in the CAPIF framework. The first authorization revocation request, the second authorization revocation request, or the third authorization revocation request is used to indicate a refresh token associated with the resource owner. Optionally, the first authorization revocation request, the second authorization revocation request, or the third authorization revocation request may directly indicate the refresh token associated with the resource owner, or indirectly indicate the refresh token associated with the resource owner through parameter information related to the refresh token.
[0183] It is understood that the resource owner is an end user, a subscriber associated with the end user, or a human. The resource owner's client runs on the end device, and the resource owner interacts with the server through the client on the end device. For example, the resource owner's client is a browser, and the API caller is the server accessed by the browser. The resource owner interacts with the server through the browser.
[0184] Optionally, the second authorization revocation request or the third authorization revocation request includes at least one of the following information: a resource identifier of the authorized resource; an operation identifier of a semantic operation executable on the authorized resource; identification information of the second entity; and identification information of the resource owner.
[0185] The first entity may determine the refresh token based on the above information included in the authorization revocation request, and perform a revocation operation on the refresh token.
[0186] In this embodiment of the present application, the resource owner client or terminal can generate a first authorization revocation request to the first entity by sending a second authorization revocation request to the API caller. A third authorization revocation request can also be sent directly to the first entity to revoke authorization. This can delete a large amount of security and authorization information stored in the CCF, reducing the burden on the CCF, improving the performance of the CAPIF framework, and thereby increasing the speed and efficiency of data processing.
[0187] Please refer to Figure 10, which is a flowchart of a method for revoking authorization provided by an embodiment of the present application. The authorization revocation method can be executed by the resource owner client or terminal device. As shown in Figure 10, the method may include but is not limited to the following steps:
[0188] S1001: Send a second authorization revocation request to a second entity.
[0189] In some implementations, the second entity may be an API caller. Optionally, the API caller may be an application function or a client running on a terminal.
[0190] In some implementations, the resource owner may send a second authorization revocation request to the API caller by controlling the terminal or the resource owner client.
[0191] In some implementations, the resource owner client or terminal device may send a second authorization revocation request to the API caller, where the second authorization revocation request is used to determine the first authorization revocation request sent to the first entity.
[0192] S1002: Receive a revocation response message corresponding to the first authorization revocation request sent by the API caller.
[0193] In some implementations, the resource owner client or terminal may send a second authorization revocation request to the API caller, and the API caller generates a first authorization revocation request based on the second authorization revocation request. After receiving the first authorization revocation request, the first entity may perform a revocation operation on the refresh token based on the refresh token indicated by the first authorization revocation request. After completing the revocation operation, the first entity may generate a revocation response message corresponding to the first authorization revocation request and feedback it to the API caller. The API caller feedbacks the revocation response message corresponding to the first authorization revocation request to the resource owner client or terminal device. The resource owner client or terminal device may determine whether the refresh token is successfully revoked based on the revocation response message. If it is not successfully revoked, it may send the authorization revocation for the refresh token again. Optionally, the first entity is one of the CCF network elements or the authorization function.
[0194] Optionally, the second authorization revocation request includes at least one of the following information: a resource identifier of the authorized resource; an operation identifier of a semantic operation executable on the authorized resource; identification information of the second entity and identification information of the resource owner.
[0195] In an embodiment of the present application, the first entity can delete a large amount of security and authorization information stored in the CCF or authorization function, reducing the burden on the CCF, improving the performance of the CAPIF framework, and increasing the speed and efficiency of data processing. Furthermore, a corresponding revocation response message is generated and fed back to the resource owner client or terminal device or resource owner, so that the terminal device or resource owner client or resource owner can promptly understand whether the revocation of authorization is successful, and then, if unsuccessful, promptly revoke the authorization again to achieve the purpose of the authorization revocation response message.
[0196] Please refer to Figure 11, which is a flowchart of a method for revoking authorization provided by an embodiment of the present application. The authorization revocation method can be executed by the resource owner client or terminal device. As shown in Figure 11, the method may include but is not limited to the following steps:
[0197] S1101: Send a third authorization revocation request to the first entity.
[0198] In some implementations, the resource owner may send a third authorization revocation request to the first entity by controlling the terminal or the resource owner client.
[0199] S1102: Receive a revocation response message corresponding to the third authorization revocation request sent by the first entity.
[0200] In some implementations, the resource owner client or terminal device may send a third authorization revocation request to the first entity in the CAPIF framework. The third authorization revocation request is used to indicate a refresh token associated with the resource owner. Optionally, the third authorization revocation request may directly indicate or include a refresh token associated with the resource owner, or indirectly indicate a refresh token associated with the resource owner through parameter information associated with the refresh token. For example, the third authorization revocation request includes at least one of the following information: a resource identifier of the authorized resource; an operation identifier that identifies a semantic operation that can be performed on the authorized resource; identification information of the second entity and identification information of the resource owner.
[0201] In some implementations, the resource owner client or terminal device or resource owner can send a third authorization revocation request to the first entity. After receiving the third authorization revocation request, the first entity can perform a revocation operation on the refresh token based on the refresh token indicated by the third authorization revocation request.
[0202] After completing the revocation operation, the first entity may generate a revocation response message corresponding to the third authorization revocation request and feedback it to the resource owner client or terminal device or resource owner. The resource owner client or terminal device or resource owner may determine whether the refresh token is successfully revoked based on the revocation response message. If the revocation is unsuccessful, the resource owner may resend the authorization revocation request for the refresh token.
[0203] In an embodiment of the present application, the first entity can delete a large amount of security and authorization information stored in the CCF or authorization function, reducing the burden on the CCF, improving the performance of the CAPIF framework, and increasing the speed and efficiency of data processing. Furthermore, a corresponding revocation response message is generated and fed back to the resource owner client, terminal device, or resource owner, so that the terminal device, resource owner client, or resource owner can promptly understand whether the revocation of authorization is successful, and then, if unsuccessful, promptly revoke the authorization again to achieve the purpose of revoking the authorization.
[0204] Please refer to Figure 12, which is an interactive diagram of an authorization revocation method provided by an embodiment of the present application. As shown in Figure 12, the method may include but is not limited to the following steps:
[0205] S1201: The resource owner client or terminal device or resource owner sends a second authorization revocation request to a second entity.
[0206] In some implementations, the second entity may be an API caller. Optionally, the API caller may be an application function or a client running on a terminal.
[0207] S1202: The second entity sends a first authorization revocation request to the first entity. The first authorization revocation request may directly indicate or include a refresh token related to the resource owner.
[0208] S1203: The first entity revokes the refresh token related to the resource owner.
[0209] S1204: The first entity sends a revocation response message corresponding to the first authorization revocation request to the second entity.
[0210] S1205: The second entity sends a revocation response message to the resource owner client or terminal device or the resource owner.
[0211] In an embodiment of the present application, the first entity can delete a large amount of security and authorization information stored in the CCF or authorization function, reducing the burden on the CCF, improving the performance of the CAPIF framework, and increasing the speed and efficiency of data processing. Furthermore, a corresponding revocation response message is generated and fed back to the resource owner client, terminal device, or resource owner, so that the terminal device, resource owner client, or resource owner can promptly understand whether the revocation of authorization is successful, and then, if unsuccessful, promptly revoke the authorization again to achieve the purpose of revoking the authorization.
[0212] Please refer to Figure 13, which is an interactive diagram of an authorization revocation method provided by an embodiment of the present application. As shown in Figure 13, the method may include but is not limited to the following steps:
[0213] S1301: The second entity sends a first authorization revocation request to the first entity.
[0214] S1302: The first entity revokes the refresh token related to the resource owner.
[0215] S1303: The first entity sends a revocation response message corresponding to the first authorization revocation request to the second entity.
[0216] In an embodiment of the present application, the first entity can delete a large amount of security and authorization information stored in the CCF or authorization function, reducing the burden on the CCF, improving the performance of the CAPIF framework, and increasing the speed and efficiency of data processing. Furthermore, a corresponding revocation response message is generated and fed back to the resource owner client, terminal device, or resource owner, so that the terminal device, resource owner client, or resource owner can promptly understand whether the revocation of authorization is successful, and then, if unsuccessful, promptly revoke the authorization again to achieve the purpose of revoking the authorization.
[0217] In the embodiments provided above, the methods provided in the embodiments of the present application are described from the perspectives of network devices and terminal devices, respectively. In order to implement the various functions in the methods provided in the embodiments of the present application, the network devices and terminal devices may include hardware structures and software modules, and the aforementioned functions may be implemented in the form of hardware structures, software modules, or hardware structures plus software modules. A particular function among the aforementioned functions may be implemented in the form of hardware structures, software modules, or hardware structures plus software modules.
[0218] Please refer to Figure 14, which is a schematic diagram of the structure of a communication device 1400 provided in an embodiment of the present application. The communication device 1400 shown in Figure 14 may include a transceiver module 1401 and a processing module 1402. The transceiver module 1401 may include a sending module and / or a receiving module. The sending module is used to implement a sending function, and the receiving module is used to implement a receiving function. The transceiver module 1401 can implement the sending function and / or the receiving function.
[0219] The communication device 1400 may be a second entity, or a device in the second entity, or a device that can be used in conjunction with the second entity. Alternatively, the communication device 1400 may be a first entity in the CAPIF framework, or a device in the first entity in the CAPIF framework, or a device that can be used in conjunction with the first entity in the CAPIF framework. Alternatively, the communication device 1400 may be a resource owner client or terminal device, or a device in the resource owner client or terminal device, or a device that can be used in conjunction with the resource owner client or terminal device.
[0220] The communication device 1400 is a second entity:
[0221] The transceiver module 1401 is configured to send a first authorization revocation request to a first entity in the CAPIF framework, wherein the first authorization revocation request is used to indicate a refresh token related to a resource owner.
[0222] In some implementations, the transceiver module 1401 is further configured to receive a second authorization revocation request; generate the first authorization revocation request based on the second authorization revocation request, and send the first authorization revocation request to the first entity.
[0223] In some implementations, the transceiver module 1401 is further configured to receive a revocation response message corresponding to the first authorization revocation request sent by the first entity.
[0224] In some implementations, the second authorization revocation request is sent by the terminal device or a resource owner client running on the terminal device or the resource owner.
[0225] In some implementations, the transceiver module 1401 is further configured to send the revocation response message to the terminal device or the resource owner client or the resource owner.
[0226] In some implementations, the second authorization revocation request includes at least one of the following information: a resource identifier of the authorized resource; an operation identifier of a semantic operation executable on the authorized resource; identification information of the second entity; and identification information of the resource owner.
[0227] In some implementations, the transceiver module 1401 is further configured to determine the refresh token based on the second authorization revocation request; and send the first authorization revocation request to the first entity based on the refresh token.
[0228] In some implementations, the processing module 1402 is further configured to convert the resource identifier and / or the operation identifier to generate 3GPP domain information; and determine the refresh token based on the 3GPP domain information.
[0229] In some implementations, the transceiver module 1401 is further configured to send the refresh token and / or the token type of the refresh token to the first entity via the first authorization revocation request.
[0230] In some implementations, before sending the first authorization revocation request, the transceiver module 1401 is further configured to: perform authorization interaction with the first entity to obtain the refresh token associated with the resource owner.
[0231] In some implementations, the first entity is a core function CCF or an authorization function in the CAPIF framework.
[0232] The communication device 1400 is the first entity in the CAPIF framework:
[0233] The transceiver module 1401 is configured to receive a first authorization revocation request or a third authorization revocation request, wherein the first authorization revocation request or the third authorization revocation request may indicate a refresh token associated with a resource owner;
[0234] The processing module 1402 is configured to perform a revocation operation on the refresh token based on the first revocation authorization request or the third revocation authorization request.
[0235] In some implementations, the transceiver module 1401 is further configured to receive a first authorization revocation request sent by the second entity.
[0236] In some implementations, the transceiver module 1401 is further configured to receive the third authorization revocation request sent by the terminal device or the resource owner client running on the terminal device or the resource owner.
[0237] In some implementations, the transceiver module 1401 is further configured to send a revocation response message corresponding to the first authorization revocation request to the second entity; or send a revocation response message corresponding to the third authorization revocation request to the terminal device or the resource owner client or the resource owner.
[0238] In some implementations, the third authorization revocation request includes at least one of the following information: a resource identifier of the authorized resource; an operation identifier of a semantic operation executable on the authorized resource; identification information of the second entity; and identification information of the resource owner.
[0239] In some implementations, the processing module 1402 is further configured to convert the resource identifier and / or the operation identifier to generate 3GPP domain information; and determine the refresh token based on the 3GPP domain information.
[0240] In some implementations, the transceiver module 1401 is further configured to perform authorization interaction with the second entity and send the refresh token associated with the resource owner to the second entity.
[0241] In some implementations, the processing module 1402 is further configured to determine the refresh token and / or the token type of the refresh token based on the first authorization revocation request or the third authorization revocation request.
[0242] In some implementations, the first entity is one of the core function CCF network element or the authorization function in the CAPIF framework.
[0243] In some implementations, the transceiver module 1401 is further configured to stop generating an access token based on the refresh token upon receiving an access token application request sent by the second entity.
[0244] The communication device 1400 is a resource owner client or terminal device:
[0245] The transceiver module 1401 is used to send a second authorization revocation request to a second entity, wherein the second authorization revocation request is used to determine the first authorization revocation request sent to the first entity; or, to send a third authorization revocation request to the first entity in the CAPIF framework; wherein the second authorization revocation or the third authorization revocation request can indicate a refresh token related to the resource owner.
[0246] In some implementations, the transceiver module 1401 is further configured to receive a revocation response message corresponding to the first authorization revocation request sent by the second entity; or receive a revocation response message corresponding to the third authorization revocation request sent by the first entity.
[0247] In some implementations, the second authorization revocation request or the third authorization revocation request includes at least one of the following information: a resource identifier of the authorized resource; an operation identifier of a semantic operation executable on the authorized resource; identification information of the second entity; and identification information of the resource owner.
[0248] In some implementations, the resource owner client runs on a terminal device.
[0249] In an embodiment of the present application, the second entity sends an authorization revocation request indicating a refresh token to the first entity to achieve the purpose of revoking authorization, thereby deleting a large amount of security and authorization information stored in the CCF, reducing the burden on the CCF, improving the performance of the CAPIF framework, and thereby improving the speed and efficiency of data processing.
[0250] Please refer to Figure 15, which is a structural diagram of another communication device 1500 provided in an embodiment of the present application. The communication device 1500 can be a second entity, or a first entity in the CAPIF framework, or a resource owner client or terminal device, or a chip, chip system, or processor that supports the second entity to implement the above method, or a chip, chip system, or processor that supports the first entity in the CAPIF framework to implement the above method, or a chip, chip system, or processor that supports the resource owner client or terminal device to implement the above method. This device can be used to implement the method described in the above method embodiment, and for details, please refer to the description in the above method embodiment.
[0251] The communication device 1500 may include one or more processors 1501. The processor 1501 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control the communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or CU, etc.), execute computer programs, and process computer program data.
[0252] Optionally, the communication device 1500 may further include one or more memories 1502, on which a computer program 1504 may be stored. The processor 1501 executes the computer program 1504 to cause the communication device 1500 to perform the method described in the above method embodiment. Optionally, the memory 1502 may also store data. The communication device 1500 and the memory 1502 may be provided separately or integrated together.
[0253] Optionally, the communication device 1500 may further include a transceiver 1505 and an antenna 1506. The transceiver 1505 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, and is configured to implement transceiver functions. The transceiver 1505 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, and is configured to implement a transmitting function.
[0254] Optionally, the communication device 1500 may further include one or more interface circuits 1507. The interface circuit 1507 is configured to receive code instructions and transmit the code instructions to the processor 1501. The processor 1501 executes the code instructions to enable the communication device 1500 to perform the method described in the above method embodiment.
[0255] In one implementation, processor 1501 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or may be used for transmitting or delivering signals.
[0256] In one implementation, processor 1501 may store a computer program 1503. Computer program 1503, when executed on processor 1501, enables communication device 1500 to perform the method described in the above method embodiment. Computer program 1503 may be embedded in processor 1501, in which case processor 1501 may be implemented by hardware.
[0257] In one implementation, the communication device 1500 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in this application can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
[0258] The communication device described in the above embodiments may be a second entity or a first entity in the CAPIF framework or a resource owner client or terminal device, but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited to FIG14. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:
[0259] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;
[0260] (2) a collection of one or more ICs, optionally including a storage component for storing data and computer programs;
[0261] (3) ASIC, such as modem;
[0262] (4) Modules that can be embedded in other devices;
[0263] (5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;
[0264] (6)Others, etc.
[0265] If the communication device can be a chip or a chip system, please refer to the schematic diagram of the chip structure shown in Figure 16. The chip shown in Figure 16 includes a processor 1601 and an interface 1602. The number of processors 1601 can be one or more, and the number of interfaces 1602 can be multiple.
[0266] Optionally, the chip further includes a memory 1603, which is used to store necessary computer programs and data.
[0267] In some implementations, the chip can be used to implement the functions of the second entity in the above-mentioned embodiments of the present application.
[0268] In some implementations, the chip can be used to implement the functions of the first entity in the CAPIF framework in the above-mentioned embodiments of the present application.
[0269] In some implementations, the chip can be used to implement the functions of the resource owner client or terminal device in the above-mentioned embodiments of the present application.
[0270] In this embodiment of the present application, the second entity first performs an authorization interaction with the first entity to obtain a refresh token. Furthermore, the second entity receives a second authorization revocation request sent by the resource owner's client or terminal, thereby generating a first authorization revocation request, and then sends the first authorization revocation request to the first entity to revoke the authorization, thereby reducing the burden on the CCF, improving the performance of the CAPIF framework, and increasing the speed and efficiency of data processing.
[0271] Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed in the embodiments of the present application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functions for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present application.
[0272] The embodiment of the present application also provides a communication system 1700 for authorization revocation, which includes a first entity 1701 and a second entity 1702 in a CAPIF framework.
[0273] The second entity 1702 is configured to send a first authorization revocation request to the first entity, wherein the first authorization revocation request is used to indicate a refresh token associated with the resource owner;
[0274] The first entity 1701 is configured to perform a revocation operation on the refresh token based on the first revocation authorization request.
[0275] In some implementations, the communication system further includes: a resource owner client or terminal device 1703, the resource owner client or terminal device configured to send a second authorization revocation request to the second entity;
[0276] The second entity 1702 is configured to generate the first authorization revocation request based on the second authorization revocation request, and send the first authorization revocation request to the first entity.
[0277] The embodiment of the present application also provides a communication system 1800 for authorization revocation, which includes a first entity 1801 in the CAPIF framework and a resource owner client or terminal device 1802.
[0278] The resource owner client or terminal device 1802 is configured to send a third authorization revocation request to the first entity in the CAPIF framework, wherein the third authorization revocation request is used to indicate a refresh token associated with the resource owner;
[0279] The first entity 1801 is configured to perform a revocation operation on the refresh token based on the first revocation authorization request.
[0280] Optionally, the communication device in the embodiment of Figure 14 above can serve as a communication device of the second entity, as a communication device of the first entity in the CAPIF framework, and as a communication device of the resource owner client or terminal device, or the communication device in the embodiment of Figure 15 above can serve as a communication device of the second entity, as a communication device of the first entity in the CAPIF framework, and as a communication device of the resource owner client or terminal device.
[0281] The present application also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.
[0282] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.
[0283] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).
[0284] Those skilled in the art will understand that the various numerical numbers such as first and second involved in this application are only for the convenience of description and are not used to limit the scope of the embodiments of this application, and also indicate the order of precedence.
[0285] In this application, at least one can also be described as one or more, and multiple can be two, three, four or more, which is not limited in this application. In the embodiments of this application, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order of precedence or size between the technical features described by "first", "second", "third", "A", "B", "C" and "D".
[0286] The correspondences shown in the tables in this application can be configured or predefined. The values of the information in each table are examples only and can be configured to other values, which are not limited by this application. When configuring the correspondence between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, in the tables in this application, the correspondences shown in certain rows may not be configured. For another example, appropriate deformation adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables can also use other names that can be understood by the communication device, and the values or representations of the parameters can also use other values or representations that can be understood by the communication device. When implementing the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables, etc.
[0287] The predefined in this application may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.
[0288] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0289] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0290] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
Claims
1. A method for revoking authorization, characterized in that: Executed by a second entity, the method comprises: A first authorization revocation request is sent to a first entity in a common application programming interface CAPIF framework, wherein the first authorization revocation request is used to indicate a refresh token related to a resource owner.
2. The method according to claim 1, characterized in that The sending a first authorization revocation request to a first entity in a general application programming interface CAPIF framework comprises: receiving a second authorization revocation request; The first authorization revocation request is generated based on the second authorization revocation request, and the first authorization revocation request is sent to the first entity.
3. The method according to claim 1 or 2, characterized in that: After sending the first authorization revocation request to the first entity, the method further includes: Receive a revocation response message corresponding to the first authorization revocation request sent by the first entity.
4. The method according to claim 2 or 3, characterized in that: The second authorization revocation request is sent by the terminal device or a resource owner client running on the terminal device or a resource owner.
5. The method according to claim 4, characterized in that After receiving the revocation response message corresponding to the first authorization revocation request sent by the first entity, the method further includes: The revocation response message is sent to the terminal device or the resource owner client or the resource owner.
6. The method according to any one of claims 2 to 5, characterized in that: The second authorization revocation request includes at least one of the following information: The resource identifier of the authorized resource; An operation identifier of a semantic operation executable on the authorized resource; identification information of the second entity; The identification information of the resource owner.
7. The method according to any one of claims 2 to 6, characterized in that: The sending, based on the second authorization revocation request, a first authorization revocation request to a first entity in the CAPIF framework comprises: determining the refresh token based on the second authorization revocation request; The first authorization revocation request is sent to the first entity based on the refresh token.
8. The method according to claim 7, characterized in that The determining the refresh token based on the second authorization revocation request comprises: Convert the resource identifier and / or the operation identifier to generate 3GPP domain information; The refresh token is determined based on the information of the 3GPP domain.
9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: The refresh token and / or the token type of the refresh token is sent to the first entity through the first authorization revocation request.
10. The method according to any one of claims 1 to 8, characterized in that Before sending the first authorization revocation request, the method further includes: Perform an authorization interaction with the first entity to obtain the refresh token associated with the resource owner.
11. The method according to any one of claims 1 to 10, characterized in that The first entity is the core function CCF or authorization function in the CAPIF framework.
12. A method for revoking authorization, characterized in that: Executed by a first entity in the CAPIF framework, the method comprises: receiving a first authorization revocation request or a third authorization revocation request, wherein the first authorization revocation request or the third authorization revocation request may indicate a refresh token associated with a resource owner; Based on the first revocation authorization request or the third revocation authorization request, a revocation operation is performed on the refresh token.
13. The method according to claim 12, characterized in that Receiving a first authorization revocation request, including: A first authorization revocation request sent by a second entity is received.
14. The method according to claim 12, characterized in that Receiving a third-party authorization revocation request, including: The third authorization revocation request sent by the terminal device or the resource owner client running on the terminal device or the resource owner is received.
15. The method according to any one of claims 12 to 14, characterized in that: After performing a revocation operation on the refresh token based on the first revocation authorization request or the third revocation authorization request, the method further includes: Sending a revocation response message corresponding to the first authorization revocation request to the second entity; or, Send a revocation response message corresponding to the third authorization revocation request to the terminal device or the resource owner client or the resource owner.
16. The method according to any one of claims 12 to 15, characterized in that: The third authorization revocation request includes at least one of the following information: The resource identifier of the authorized resource; An operation identifier of a semantic operation executable on the authorized resource; identification information of the second entity; The identification information of the resource owner.
17. The method according to claim 16, before performing a revocation operation on the refresh token based on the third revocation authorization request, further comprising: Convert the resource identifier and / or the operation identifier to generate 3GPP domain information; The refresh token is determined based on the information of the 3GPP domain.
18. The method according to any one of claims 12 to 16, characterized in that: Before receiving the first authorization revocation request or the third authorization revocation request, the method further includes: An authorization interaction is performed with the second entity, and the refresh token associated with the resource owner is sent to the second entity.
19. The method according to any one of claims 12 to 18, characterized in that: The method further comprises: Based on the first authorization revocation request or the third authorization revocation request, the refresh token and / or a token type of the refresh token is determined.
20. The method according to any one of claims 12 to 19, characterized in that The first entity is one of the core function CCF network elements or authorization functions in the CAPIF framework.
21. The method according to any one of claims 12 to 20, characterized in that After performing the revocation operation on the refresh token based on the first authorization revocation request or the third authorization revocation request, the method includes: When receiving the access token application request sent by the second entity, stop generating the access token based on the refresh token.
22. A method for revoking authorization in a CAPIF framework, characterized in that: The method is executed by a resource owner client or a terminal device, and includes: Sending a second authorization revocation request to a second entity, wherein the second authorization revocation request is used to determine the first authorization revocation request sent to the first entity in the CAPIF framework; or, A third authorization revocation request is sent to the first entity in the CAPIF framework; wherein the second authorization revocation or the third authorization revocation request is used to indicate a refresh token associated with a resource owner.
23. The method according to claim 22, characterized in that The method further comprises: receiving a revocation response message corresponding to the first authorization revocation request sent by the second entity; or, Receive a revocation response message corresponding to the third authorization revocation request sent by the first entity.
24. The method according to claim 22 or 23, characterized in that The second authorization revocation request or the third authorization revocation request includes at least one of the following information: The resource identifier of the authorized resource; An operation identifier of a semantic operation identifier executable on the authorized resource; identification information of the second entity; The identification information of the resource owner.
25. The method according to any one of claims 22 to 24, characterized in that The resource owner client runs on the terminal device.
26. A communication system, characterized in that: include: The first and second entities in the CAPIF framework; The second entity is configured to send a first authorization revocation request to the first entity, wherein the first authorization revocation request is used to indicate a refresh token associated with a resource owner; The first entity is configured to perform a revocation operation on the refresh token based on the first revocation authorization request.
27. The communication system according to claim 26, characterized in that Also includes: a resource owner client or terminal device, the resource owner client or terminal device being configured to send a second authorization revocation request to the second entity; The second entity is configured to generate the first authorization revocation request based on the second authorization revocation request, and send the first authorization revocation request to the first entity.
28. A communication system, characterized in that: include: The first entity and resource owner client or terminal device in the CAPIF framework; The resource owner client or terminal device is used to send a third authorization revocation request to the first entity in the CAPIF framework, wherein the third authorization revocation request is used to indicate a refresh token related to the resource owner; The first entity is configured to perform a revocation operation on the refresh token based on the first revocation authorization request.
29. A communication device, characterized in that: include: The processing module is used to send a first authorization revocation request to a first entity in a common application programming interface CAPIF framework, wherein the first authorization revocation request is used to indicate a refresh token related to a resource owner.
30. A communication device, characterized in that: include: a transceiver module, configured to receive a first authorization revocation request or a third authorization revocation request, wherein the first authorization revocation request or the second authorization revocation request may indicate a refresh token associated with a resource owner; A processing module is used to perform a revocation operation on the refresh token based on the first revocation authorization request or the third revocation authorization request.
31. A communication device, characterized in that: include: A transceiver module is used to send a second authorization revocation request to a second entity, wherein the second authorization revocation request is used to determine the first authorization revocation request sent to the first entity; or, to send a third authorization revocation request to the first entity in the CAPIF framework; wherein the second authorization revocation or the third authorization revocation request is used to indicate a refresh token associated with a resource owner.
32. A communication device, characterized in that: The device comprises a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory so that the device performs the method according to any one of claims 1 to 11.
33. A communication device, characterized in that: The device comprises a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory so that the device performs the method according to any one of claims 12 to 21.
34. A communication device, characterized in that: The device comprises a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory so that the device performs the method according to any one of claims 22 to 25.
35. A communication device, characterized in that: include: processor and interface circuits; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to execute the method according to any one of claims 1 to 11.
36. A communication device, characterized in that: include: processor and interface circuits; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to execute the method according to any one of claims 12 to 21.
37. A communication device, characterized in that: include: processor and interface circuits; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to execute the method according to any one of claims 22 to 25.
38. A computer-readable storage medium, used for storing instructions, which, when executed, enable the method according to any one of claims 1 to 11 to be implemented.
39. A computer-readable storage medium, used for storing instructions, which, when executed, enable the method according to any one of claims 12 to 21 to be implemented.
40. A computer-readable storage medium storing instructions, which, when executed, implement the method according to any one of claims 22 to 25.
Citation Information
Patent Citations
Authorization withdrawing method and device
CN110046001A
Method and appratus for revoking authorization of API invoker
CN112470444A
Multifunctional security authorization API Key implementation system and method
CN113821783A
Security procedures for common API framework in next generation networks
US20210144550A1
Cited By
METHOD AND APPARATUS OF SUPPORTING INTERNET OF THINGS (IoT)
WO2026091673A1
