Request processing method and device

By refusing requests to carry resource owner identification but not carry tokens or tokens that do not contain resource owner identification in CAPIF, the issue of malicious API callers bypassing authorized access to resources is solved, improving the security of resource access.

WO2024234197A1PCT designated stage expired Publication Date: 2024-11-21BEIJING XIAOMI MOBILE SOFTWARE CO LTD

Patent Information

Application Number
PCT/CN2023/094074
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-12
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In the Common Application Programming Interface Framework (CAPIF), when the two authorization mechanisms are used together, malicious API callers can bypass the authorization of the resource owner through traditional tokens or authorization mechanisms based on traditional TLS-PSK/PKI , request access to any resource owner's resources, reducing the security of resource access.

Method used

Avoid malicious API callers by rejecting the request when the first entity receives a request that meets a specific condition, the condition is to carry the resource owner identification but not the token, or carry a token that does not contain the resource owner identification, thereby avoiding the malicious API caller Bypass authorization.

Benefits of technology

Improves the security of resource access and prevents malicious API callers from unauthorized access to resource owner's resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2023094074_21112024_PF_FP_ABST
    Figure CN2023094074_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Disclosed in embodiments of the present application are a request processing method and device, which can be applied to the technical field of communications. The method comprises: upon receipt of a first request satisfying a first condition, a first entity can reject the first request, wherein the first condition is that the first request carries a first resource owner identifier and does not carry a token; or the first condition is that the first request carries the first resource owner identifier and carries a token which does not comprise the resource owner identifier. In this way, malicious API callers are prevented from requesting to access, without the authorization of resource owners, resources of the resource owners by means of the first request, thereby improving the security of resource access.
Need to check novelty before this filing date? Find Prior Art

Description

Request processing method and device thereof Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a request processing method and device thereof. Background Art

[0002] In the Common Application Programming Interface Framework (CAPIF), there are two authorization mechanisms. One is based on the traditional Transport Layer Security pre-shared key (TLS-PSK) / Public Key Infrastructure (PKI) authorization mechanism, in which the token does not contain the resource owner identifier. The other is based on the subscriber-aware northbound Application Programming Interface access (SNA) scenario, in which the token contains the resource owner identifier.

[0003] Among them, when the two authorization mechanisms are used together, a malicious API caller can bypass the authorization of the resource owner and request the first entity to authorize access to the resources of any resource owner through a traditional token or an authorization mechanism based on traditional TLS-PSK / PKI, thereby realizing the requested access to the resources of the resource owner and reducing the security of resource access.

[0004] Summary of the Invention

[0005] An embodiment of the present application provides a request processing method and apparatus thereof, which can be applied to the field of communication technology. When a first entity receives a first request that satisfies a first condition, the first entity can reject the first request; wherein the first condition is that the first request carries the first resource owner identifier and does not carry a token; or, the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain the resource owner identifier, thereby preventing a malicious API caller from bypassing the resource owner's authorization through the first request and requesting access to the resource owner's resources, thereby improving the security of resource access.

[0006] In a first aspect, an embodiment of the present application provides a request processing method, which is executed by a first entity, and the method includes: in response to receiving a first request that meets a first condition, determining to reject the first request; wherein, the first condition is that the first request carries the first resource owner identifier and does not carry a token; or, the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain a resource owner identifier.

[0007] In an embodiment of the present application, when the first entity receives a first request that meets a first condition, it may reject the first request; wherein the first condition is that the first request carries the first resource owner identifier and does not carry a token; or, the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain the resource owner identifier, thereby preventing a malicious API caller from bypassing the resource owner's authorization through the first request and requesting access to the resource owner's resources, thereby improving the security of resource access.

[0008] In one implementation, the method further includes: returning a first response to an application programming interface (API) caller that initiates the first request; the first response is used to indicate a rejection of the API caller's request for the resource corresponding to the first resource owner identifier.

[0009] In one implementation, the first request also includes at least one of the following parameters: the identifier of the API caller who initiates the first request; the identifier of the service requested by the API caller; the identifier of the API requested by the API caller; and the identifier of the resource requested by the API caller.

[0010] In one implementation, the first entity is an API open function AEF network element or a network open function NEF network element in a common application programming interface framework CAPIF.

[0011] In one implementation, the resource owner identifier is the resource owner's General Public User Identity (GPSI).

[0012] In one implementation, the API caller that initiates the first request is a terminal device that requests the first resource owner to identify the corresponding resource.

[0013] In one implementation, the first entity uses at least two authorization mechanisms simultaneously; the authorization mechanisms include: an authorization mechanism based on traditional transport layer security pre-shared key TLS-PSK / public key infrastructure PKI, and an authorization mechanism in a subscription user-perceived API call scenario.

[0014] In a second aspect, an embodiment of the present application provides another request processing method, which is executed by an API caller, and the method includes: sending a first request to a first entity; receiving a first response returned by the first entity when the first request meets a first condition; the first response is used to indicate the rejection of the first request; wherein the first condition is that the first request carries the first resource owner identifier and does not carry a token; or, the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain a resource owner identifier.

[0015] In an embodiment of the present application, when the API caller sends a first request that meets the first condition, it will receive a response returned by the first entity indicating that the first request is rejected; wherein the first condition is that the first request carries the first resource owner identifier and does not carry a token; or, the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain the resource owner identifier, thereby preventing malicious API callers from bypassing the resource owner's authorization through the first request and requesting access to the resource owner's resources, thereby improving the security of resource access.

[0016] In one implementation, the first request also includes at least one of the following parameters: the identifier of the API caller who initiates the first request; the identifier of the service requested by the API caller; the identifier of the API requested by the API caller; and the identifier of the resource requested by the API caller.

[0017] In one implementation, the first entity is an API open function AEF network element or a network open function NEF network element in a common application programming interface framework CAPIF.

[0018] In one implementation, the resource owner identifier is the resource owner's General Public User Identity (GPSI).

[0019] In one implementation, the API caller that initiates the first request is a terminal device that requests the first resource owner to identify the corresponding resource.

[0020] In one implementation, the first entity uses at least two authorization mechanisms simultaneously; the authorization mechanisms include: an authorization mechanism based on traditional transport layer security pre-shared key TLS-PSK / public key infrastructure PKI, and an authorization mechanism in a subscription user-perceived API call scenario.

[0021] In a third 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 first 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.

[0022] In one implementation, the communication device may include a transceiver unit and a processing unit, wherein the processing unit is configured to support the communication device in performing the corresponding functions of the above method. The transceiver unit is used to support communication between the communication device and other devices. The communication device may also include a storage unit, which is coupled to the transceiver unit and the processing unit and stores computer programs and data necessary for the communication device.

[0023] As an example, the processing unit may be a processor, the transceiver unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0024] In a fourth aspect, an embodiment of the present application provides another communication device, which has some or all of the functions of the API caller in the method example described in the second aspect above. For example, the functions of the communication device may have some or all of the functions in the embodiments of the present application, or may have the functions of implementing any one of the embodiments of the present application separately. The functions can 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.

[0025] In one implementation, the communication device may include a transceiver unit and a processing unit, the processing unit configured to support the communication device in performing the corresponding functions of the above-described method. The transceiver unit is configured to support communication between the communication device and other devices. The communication device may also include a storage unit, coupled to the transceiver unit and the processing unit, which stores computer programs and data necessary for the communication device.

[0026] As an example, the processing unit may be a processor, the transceiver unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0027] In a fifth 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.

[0028] In a sixth 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.

[0029] In the seventh 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.

[0030] In an eighth 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.

[0031] In the ninth 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 first aspect above.

[0032] In the tenth 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 second aspect above.

[0033] In the eleventh aspect, an embodiment of the present application provides a communication system, which includes the communication device described in the third aspect and the communication device described in the fourth aspect, or the system includes 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 and the communication device described in the eighth aspect, or the system includes the communication device described in the ninth aspect and the communication device described in the tenth aspect.

[0034] In a twelfth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions for the above-mentioned first entity, and when the instructions are executed, the first entity executes the method described in the above-mentioned first aspect.

[0035] In a thirteenth aspect, an embodiment of the present invention provides a readable storage medium for storing instructions for the above-mentioned API caller, and when the instructions are executed, the API caller executes the method described in the above-mentioned second aspect.

[0036] In a fourteenth 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 first aspect above.

[0037] In a fifteenth 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.

[0038] In a sixteenth aspect, the present application provides a chip system, which includes at least one processor and an interface for supporting a first entity to implement the functions involved in the first 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 also includes a memory, which is used to store computer programs and data necessary for the first entity. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0039] In a seventeenth aspect, the present application provides a chip system comprising at least one processor and an interface for supporting an API caller in implementing the functions described in the second 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 API caller. The chip system may be comprised of a chip or may include a chip and other discrete components.

[0040] In an eighteenth 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 a nineteenth aspect, the present application provides a computer program which, when executed on a computer, enables the computer to execute the method described in the second aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] 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.

[0043] FIG1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0044] FIG2 is a flow chart of a request processing method provided in an embodiment of the present application;

[0045] FIG3 is a flow chart of another request processing method provided in an embodiment of the present application;

[0046] FIG4 is an interactive diagram of a request processing method provided in an embodiment of the present application;

[0047] FIG5 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0048] FIG6 is a schematic structural diagram of another communication device provided in an embodiment of the present application;

[0049] FIG7 is a schematic diagram of the structure of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] In order to better understand the request processing method and device 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.

[0051] 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.

[0052] It should be noted that the technical solutions of the embodiments of the present application can be applied to various communication systems. For example, long term evolution (LTE) systems, fifth generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems.

[0053] 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, or a non-access node in a communication system. Among them, the non-access node, for example, the API exposing function (AEF) network element in CAPIF, the network exposure function (NEF) network element in CAPIF, the CAPIF core function (CCF) network element in CAPIF, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.

[0054] 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. Among them, the API caller mentioned in this application is the terminal device.

[0055] In the Common Application Programming Interface Framework (CAPIF), there are two authorization mechanisms. One is based on the traditional Transport Layer Security pre-shared key (TLS-PSK) / Public Key Infrastructure (PKI) authorization mechanism, in which the token does not contain the resource owner identifier. The other is based on the subscriber-aware northbound Application Programming Interface access (SNA) scenario, in which the token contains the resource owner identifier.

[0056] One of the goals of SNA security research is to obtain authorization from resource owners. The corresponding Stage 1 requirement in TS 22.261, Section 6.10.2, states that "end devices are allowed to provide / revoke consent to share information (e.g., location, presence) with third parties."

[0057] In the SNA scenario, to access resources belonging to a specific resource owner (such as location information and Quality of Service (QoS) information), the API caller needs to interact with the CCF using the Authorization Code Grant Type and the Client Credential Grant Type. For both authorization mechanisms, the CCF needs to use the resource owner's authorization information / policy to generate a token for the API caller. The AEF will authorize the API caller to access the resources belonging to the specific resource owner if and only if the token contains the corresponding API caller identity and resource owner identity.

[0058] However, malicious API callers can still bypass the resource owner's authorization. Specifically, they can request a token by not triggering the authorization code grant mechanism or the client credentials grant mechanism that does not involve the resource owner. In this case, CCF will send a traditional token that does not contain the resource owner's identifier to the malicious API caller, or instruct the API caller to use the traditional TLS-PSK / PKI-based authorization mechanism.

[0059] Among them, for a malicious API caller who receives a traditional token, the malicious API caller will send an API call request to AEF, which includes the API caller ID, the ID of the requested API, the resource owner ID, and the traditional token. Since the traditional token does not contain the resource owner ID, AEF will authorize the malicious API caller to access the resources of any resource owner through the requested API.

[0060] For a malicious API caller requesting access to resources through a traditional TLS-PSK / PKI-based authorization mechanism, the malicious API caller will send an API call request to the AEF, which includes the API caller's identity, the identity of the requested API, and the identity of the resource owner. For authorization mechanisms based on traditional TLS-PSK / PKI, the AEF will use the API caller's identity to obtain authorization information from the CCF that is not associated with a specific resource owner. Therefore, the AEF will authorize the malicious API caller to access the resources of any resource owner through the requested API.

[0061] Among them, when the two authorization mechanisms are used together, a malicious API caller can bypass the authorization of the resource owner and request the first entity to authorize access to the resources of any resource owner through a traditional token or an authorization mechanism based on traditional TLS-PSK / PKI, thereby realizing the requested access to the resources of the resource owner and reducing the security of resource access.

[0062] 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.

[0063] It should be noted that the first entity described in any embodiment of the present application is a device for rejecting a received first request that meets the first condition, and may refer to, for example, the network device 101 in the communication system shown in Figure 1. The API caller described in any embodiment of the present application is a device for sending a first request to the first entity, and may refer to, for example, the terminal device 102 in the communication system shown in Figure 1.

[0064] It should be noted that the request processing 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.

[0065] The request processing method and device provided by this application are described in detail below with reference to the accompanying drawings.

[0066] Please refer to Figure 2, which is a flowchart of a request processing method provided in an embodiment of the present application. The request processing method is executed by the first entity. As shown in Figure 2, the method may include but is not limited to the following steps:

[0067] Step S201: In response to receiving a first request that meets a first condition, determine to reject the first request; wherein the first condition is that the first request carries the first resource owner identifier and does not carry a token; or the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain the resource owner identifier.

[0068] In an embodiment of the present application, the first entity uses at least two authorization mechanisms simultaneously; the authorization mechanisms may include: an authorization mechanism based on traditional transport layer security pre-shared key TLS-PSK / public key infrastructure PKI, and an authorization mechanism in a subscription user-perceived API call scenario. Where the first entity uses at least two authorization mechanisms simultaneously, step S201 may be performed. Where the first entity uses only a single authorization mechanism, the first entity may not receive a first request that meets the first condition; alternatively, the first request that meets the first condition may be processed according to a single authorization mechanism.

[0069] In an embodiment of the present application, a first request may be initiated by an application programming interface (API) caller requesting a resource of a resource owner and sent to a first entity. The resource owner may be, for example, an end user, a subscriber, or a human. The resource owner's resources, such as the resource owner's location and quality of service, may be configured as needed.

[0070] The API caller is a terminal device that requests the resource corresponding to the first resource owner identifier. For example, the API caller may be a terminal device used by a third party that needs to request and process the resource.

[0071] In an embodiment of the present application, the first entity may be an API exposure function AEF network element or a network exposure function NEF network element in the common application programming interface framework CAPIF. In one example, the AEF network element and the NEF network element may be located on different network devices. In another example, the AEF network element and the NEF network element may be located on the same network device.

[0072] In the embodiment of the present application, the resource owner identifier may be a Generic Public Subscription Identifier (GPSI) of the resource owner, wherein the GPSI may uniquely identify the resource owner.

[0073] In an embodiment of the present application, the first request may also include at least one of the following parameters: the identifier of the API caller who initiates the first request; the identifier of the service requested by the API caller; the identifier of the API requested by the API caller; the identifier of the resource requested by the API caller. Taking the UE reachability information of the resource owner as an example, the identifier of the API may be MonitoringEvent; the identifier of the resource may be the UE reachability of the first resource owner. CAPIF / NEF may include multiple APIs, and the identifier of the API requested by the API caller here is the identifier of the API used by the API caller when initiating the first request.

[0074] In an embodiment of the present application, taking the example that the first request also includes the identifier of the API caller who initiates the first request and the identifier of the API requested by the API caller, when the first condition is that the first request carries the identifier of the first resource owner and does not carry a token, the first request that meets the first condition may include: the identifier of the first resource owner, the identifier of the API caller who initiates the first request, and the identifier of the API requested by the API caller.

[0075] In this example, the first request does not carry a token, which may be because the API caller did not apply for a token. In other words, when the API caller requests authorization from CCF, CCF instructs the API caller to use the traditional TLS-PSK / PKI-based authorization mechanism. In other words, the API caller at this time bypasses the resource owner's authorization. Therefore, the first entity can consider the first request initiated by the API caller to be initiated by a malicious API caller who bypassed the resource owner's authorization. The first request needs to be rejected to prevent the API caller from successfully obtaining the resource owner's resources while bypassing the resource owner's authorization.

[0076] In this example, the token not carried in the first request may refer to a token that does not include the resource owner identifier, or may refer to a token that includes the resource owner identifier.

[0077] In an embodiment of the present application, taking the example in which the first request also includes the identifier of the API caller who initiates the first request and the identifier of the API requested by the API caller, when the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain the resource owner identifier, the first request that meets the first condition may include: the first resource owner identifier, the token that does not contain the resource owner identifier, the identifier of the API caller who initiates the first request, and the identifier of the API requested by the API caller.

[0078] In this example, the first request carries a token that does not contain the resource owner identifier, which may be because the API caller has not obtained the token that carries the resource owner identifier. For example, when the API caller requests a token from CCF, it applies for a token by not triggering the authorization code authorization mechanism (authorizationcodegranttype) or by not triggering the client credential authorization mechanism (clientcredentialgranttype) with the participation of the resource owner. At this time, CCF sends a token that does not contain the resource owner identifier to the API caller (for example, CCF uses the client credential authorization mechanism without the participation of the resource owner to send a token to the API caller). In other words, the API caller at this time bypasses the authorization of the resource owner. Therefore, for the first request initiated by the API caller, the first entity can be considered to be initiated by a malicious API caller who bypasses the authorization of the resource owner, and the first request needs to be rejected to prevent the API caller from successfully obtaining the resources of the resource owner while bypassing the authorization of the resource owner.

[0079] In an embodiment of the present application, the first entity may also receive a second request that does not meet the first condition. The second request may also include at least one of the following parameters: an identifier of the API caller initiating the second request; an identifier of the service requested by the API caller; an identifier of the API requested by the API caller; or an identifier of the resource requested by the API caller.

[0080] Among them, taking the example that the second request also includes the identifier of the API caller who initiated the second request and the identifier of the API requested by the API caller, in one example, the second request may include: the identifier of the first resource owner, the token containing the identifier of the first resource owner, the identifier of the API caller who initiated the second request, and the identifier of the API requested by the API caller. In this example, if the token contains the identifier of the first resource owner, it means that when the API caller requests the token from the CCF, the CCF uses the authorization code authorization mechanism or the client credential authorization mechanism with the participation of the resource owner to send the token containing the identifier of the first resource owner to the API caller. In other words, the API caller at this time is authorized by the resource owner. Therefore, for the second request initiated by the API caller, the first entity can authorize the API caller to access the resources of the resource owner corresponding to the first resource owner identifier. Among them, if the second request also includes: the identifier of the service requested by the API caller, the first entity can authorize the API caller to access the resources under the service of the resource owner corresponding to the first resource owner identifier.

[0081] Among them, taking the example that the second request also includes the identifier of the API caller who initiated the second request and the identifier of the API requested by the API caller, in another example, the second request may include: a token that does not include the identifier of the first resource owner, the identifier of the API caller who initiated the second request, and the identifier of the API requested by the API caller. In this example, if the token does not include the identifier of the first resource owner, and the second request does not carry the identifier of the first resource owner, it means that when the API caller requests authorization from the CCF, the CCF sends a token that does not include the identifier of the resource owner to the API caller. Therefore, for the second request initiated by the API caller, the first entity can authorize the API caller to access the API agreed in the token that does not include the identifier of the first resource owner. Among them, if the second request also includes: the identifier of the service requested by the API caller, the first entity can authorize the API caller to access the service agreed in the token that does not include the identifier of the first resource owner.

[0082] In an embodiment of the present application, after step S201, the first entity may further perform the following process: returning a first response to the API caller that initiated the first request; the first response is used to indicate a rejection of the API caller's request for the resource corresponding to the first resource owner identifier.

[0083] In this embodiment of the present application, the first response is further used to instruct the API caller to perform authorization with the resource owner, that is, to instruct the API caller to interact with the CCF to obtain a token containing the resource owner's identifier. Correspondingly, the API caller can interact with the CCF according to the instructions of the first response to obtain a token containing the resource owner's identifier; and then, using this token, initiate a second request that does not meet the first condition to obtain the resource corresponding to the resource owner's identifier.

[0084] In addition, if the first entity receives a second request that does not meet the first condition and determines to authorize the second request, the first entity can obtain the resources requested by the API caller and carry the requested resources in the second response and return it to the API caller.

[0085] In the request processing method provided in the embodiment of the present application, when the first entity receives a first request that meets the first condition, the first entity may reject the first request; wherein the first condition is that the first request carries the first resource owner identifier and does not carry a token; or, the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain the resource owner identifier, thereby preventing a malicious API caller from bypassing the resource owner's authorization through the first request and requesting access to the resource owner's resources, thereby improving the security of resource access.

[0086] Please refer to Figure 3, which is a flowchart of another request processing method provided by an embodiment of the present application. The request processing method is executed by the API caller. As shown in Figure 3, the method may include but is not limited to the following steps:

[0087] Step S301: Send a first request to a first entity.

[0088] In an embodiment of the present application, the first entity simultaneously uses at least two authorization mechanisms; the authorization mechanisms may include: an authorization mechanism based on traditional Transport Layer Security Pre-Shared Key TLS-PSK / Public Key Infrastructure (PKI), and an authorization mechanism for a subscription-based API call scenario. If the first entity simultaneously uses at least two authorization mechanisms, the API caller may perform steps S301 and S302. If the first entity uses a single authorization mechanism, the API caller may only perform step S301.

[0089] In an embodiment of the present application, a first request may be initiated by an application programming interface (API) caller requesting a resource of a resource owner and sent to a first entity. The resource owner may be, for example, an end user, a subscriber, or a human. The resource owner's resources, such as the resource owner's location and quality of service, may be configured as needed.

[0090] The API caller is a terminal device that requests the resource corresponding to the first resource owner identifier. For example, the API caller may be a terminal device used by a third party that needs to request and process the resource.

[0091] In an embodiment of the present application, the first entity may be an API exposure function AEF network element or a network exposure function NEF network element in the common application programming interface framework CAPIF. In one example, the AEF network element and the NEF network element may be located on different network devices. In another example, the AEF network element and the NEF network element may be located on the same network device.

[0092] Step S302: Receive a first response returned by the first entity when the first request meets the first condition; the first response is used to indicate the rejection of the first request; wherein the first condition is that the first request carries the first resource owner identifier and does not carry a token; or, the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain the resource owner identifier.

[0093] In the embodiment of the present application, the resource owner identifier may be a Generic Public Subscription Identifier (GPSI) of the resource owner, wherein the GPSI may uniquely identify the resource owner.

[0094] In an embodiment of the present application, the first request may also include at least one of the following parameters: the identifier of the API caller who initiates the first request; the identifier of the service requested by the API caller; the identifier of the API requested by the API caller; the identifier of the resource requested by the API caller. Taking the UE reachability information of the resource owner as an example, the identifier of the API may be MonitoringEvent; the identifier of the resource may be the UE reachability of the first resource owner. CAPIF / NEF may include multiple APIs, and the identifier of the API requested by the API caller here is the identifier of the API used by the API caller when initiating the first request.

[0095] In an embodiment of the present application, taking the example that the first request also includes the identifier of the API caller who initiates the first request and the identifier of the API requested by the API caller, when the first condition is that the first request carries the identifier of the first resource owner and does not carry a token, the first request that meets the first condition may include: the identifier of the first resource owner, the identifier of the API caller who initiates the first request, and the identifier of the API requested by the API caller.

[0096] In this example, the first request does not include a token, likely because the API caller did not request one. In other words, when the API caller requested authorization from the CCF, the CCF instructed the API caller to use a traditional TLS-PSK / PKI-based authorization mechanism. This means that the API caller bypassed the resource owner's authorization. Therefore, after the API caller initiated the first request and sent it to the first entity, the API caller might have received a first response rejecting the first request.

[0097] In this example, the token not carried in the first request may refer to a token that does not include the resource owner identifier, or may refer to a token that includes the resource owner identifier.

[0098] In an embodiment of the present application, taking the example in which the first request also includes the identifier of the API caller who initiates the first request and the identifier of the API requested by the API caller, when the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain the resource owner identifier, the first request that meets the first condition may include: the first resource owner identifier, the token that does not contain the resource owner identifier, the identifier of the API caller who initiates the first request, and the identifier of the API requested by the API caller.

[0099] In this example, the first request carries a token that does not contain the resource owner identifier, which may be because the API caller did not obtain the token that carries the resource owner identifier. For example, when the API caller requests a token from CCF, it applies for a token by not triggering the authorization code authorization mechanism (authorizationcodegranttype) or by not triggering the client credential authorization mechanism (clientcredentialgranttype) with the participation of the resource owner. At this time, CCF sends a token that does not contain the resource owner identifier to the API caller (for example, CCF uses the client credential authentication mechanism without the participation of the resource owner to send a token to the API caller). In other words, the API caller at this time bypasses the authorization of the resource owner. Therefore, after the API caller initiates the first request and sends it to the first entity, the API caller may receive a first response indicating the rejection of the first request.

[0100] In an embodiment of the present application, the first entity may also receive a second request that does not meet the first condition. The second request may also include at least one of the following parameters: an identifier of the API caller initiating the second request; an identifier of the service requested by the API caller; an identifier of the API requested by the API caller; or an identifier of the resource requested by the API caller.

[0101] Among them, taking the example that the second request also includes the identifier of the API caller who initiated the second request and the identifier of the API requested by the API caller, in one example, the second request may include: the identifier of the first resource owner, the token containing the identifier of the first resource owner, the identifier of the API caller who initiated the second request, and the identifier of the API requested by the API caller. In this example, if the token contains the identifier of the first resource owner, it means that when the API caller requests a token from the CCF, the CCF uses the authorization code authorization mechanism or the client credential authorization mechanism with the participation of the resource owner to send a token containing the identifier of the first resource owner to the API caller. In other words, the API caller at this time is authorized by the resource owner. Therefore, after the API caller initiates the second request and sends it to the first entity, the API caller may receive a second response containing the requested resource.

[0102] Taking the example of a second request that also includes the identifier of the API caller initiating the second request and the identifier of the API requested by the API caller, in another example, the second request may include: a token that does not include the identifier of the first resource owner, the identifier of the API caller initiating the second request, and the identifier of the API requested by the API caller. In this example, if the token does not include the identifier of the first resource owner, and the second request does not carry the identifier of the first resource owner, this means that when the API caller requests authorization from the CCF, the CCF sends the token that does not include the identifier of the resource owner to the API caller. Therefore, after the API caller initiates this second request and sends it to the first entity, the first entity can authorize the API caller to access the API specified in the token that does not include the identifier of the first resource owner, and the API caller may receive a second response that includes the requested resources. If the second request also includes the identifier of the service requested by the API caller, the first entity can authorize the API caller to access the service specified in the token that does not include the identifier of the first resource owner, and the API caller may receive a second response that includes the resources of the requested service.

[0103] In this embodiment of the present application, the first response is further used to instruct the API caller to perform authorization with the resource owner, that is, to instruct the API caller to interact with the CCF to obtain a token containing the resource owner's identifier. Correspondingly, the API caller can interact with the CCF according to the instructions of the first response to obtain a token containing the resource owner's identifier; and then, using this token, initiate a second request that does not meet the first condition to obtain the resource corresponding to the resource owner's identifier.

[0104] In the request processing method provided in the embodiment of the present application, an API caller sends a first request to a first entity; receives a first response returned by the first entity when the first request satisfies a first condition; the first response is used to indicate the rejection of the first request; wherein the first condition is that the first request carries the first resource owner identifier and does not carry a token; or, the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain the resource owner identifier, thereby preventing a malicious API caller from bypassing the resource owner's authorization through the first request and requesting access to the resource owner's resources, thereby improving the security of resource access.

[0105] Please refer to Figure 4, which is an interactive diagram of the request processing method provided by an embodiment of the present application. As shown in Figure 4, the method may include but is not limited to the following steps:

[0106] Step S401: The API caller sends a first request that meets a first condition to the first entity; wherein the first condition is that the first request carries the first resource owner identifier and does not carry a token; or, the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain the resource owner identifier.

[0107] In an embodiment of the present application, the first entity uses at least two authorization mechanisms at the same time; the authorization mechanisms may include: an authorization mechanism based on traditional transport layer security pre-shared key TLS-PSK / public key infrastructure PKI, and an authorization mechanism in an API call scenario perceived by the subscriber.

[0108] In the embodiments of the present application, the resource owner may be, for example, an end user, a subscriber, or a human being. The resource owner's resources, such as the resource owner's location and quality of service, may be configured as needed. The resource owner identifier may be the resource owner's Generic Public Subscription Identifier (GPSI). The GPSI uniquely identifies the resource owner.

[0109] In an embodiment of the present application, the first entity may be an API exposure function AEF network element or a network exposure function NEF network element in the common application programming interface framework CAPIF. In one example, the AEF network element and the NEF network element may be located on different network devices. In another example, the AEF network element and the NEF network element may be located on the same network device.

[0110] In an embodiment of the present application, the first request may also include at least one of the following parameters: the identifier of the API caller who initiates the first request; the identifier of the service requested by the API caller; the identifier of the API requested by the API caller; and the identifier of the resource requested by the API caller.

[0111] Step S402: The first entity determines to reject the first request.

[0112] In an embodiment of the present application, in one example, when the first condition is that the first request carries the first resource owner identifier and does not carry the token, the first request may carry the first resource owner identifier and does not carry the token. Among them, if the first request does not carry the token, it may be that the API caller has not applied for a token. That is to say, when the API caller requests authorization from the CCF, the CCF instructs the API caller to use the authorization mechanism based on the traditional TLS-PSK / PKI. In other words, the API caller at this time bypasses the authorization of the resource owner. Therefore, for the first request initiated by the API caller, the first entity can consider it to be initiated by a malicious API caller who bypasses the authorization of the resource owner, and needs to reject the first request to prevent the API caller from successfully obtaining the resources of the resource owner while bypassing the authorization of the resource owner.

[0113] In an embodiment of the present application, in another example, when the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain the resource owner identifier, the first request may carry the first resource owner identifier and carry a token that does not contain the resource owner identifier. Among them, the first request carries a token that does not contain the resource owner identifier, which may be because the API caller has not obtained the token carrying the resource owner identifier. For example, when the API caller requests a token from the CCF, it applies for a token by not triggering the authorization code authorization mechanism (authorizationcodegranttype) or by not triggering the client credential authorization mechanism (clientcredentialgranttype) with the participation of the resource owner. At this time, the CCF sends a token that does not contain the resource owner identifier to the API caller (for example, the CCF uses the client credential authorization mechanism without the participation of the resource owner to send a token to the API caller). In other words, the API caller at this time bypasses the authorization of the resource owner. Therefore, for the first request initiated by the API caller, the first entity can be considered to be initiated by a malicious API caller who bypasses the authorization of the resource owner, and the first request needs to be rejected to prevent the API caller from successfully obtaining the resources of the resource owner while bypassing the authorization of the resource owner.

[0114] Step S403: The first entity returns a first response to the API caller; the first response is used to indicate rejection of the first request.

[0115] In this embodiment of the present application, the first response is further used to instruct the API caller to perform authorization with the resource owner, that is, to instruct the API caller to interact with the CCF to obtain a token containing the resource owner's identifier. Correspondingly, the API caller can interact with the CCF according to the instructions of the first response to obtain a token containing the resource owner's identifier; and then, using this token, initiate a second request that does not meet the first condition to obtain the resource corresponding to the resource owner's identifier.

[0116] In the request processing method provided in the embodiment of the present application, an API caller sends a first request that meets a first condition to a first entity; wherein the first condition is that the first request carries a first resource owner identifier and does not carry a token; or, the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain the resource owner identifier; the first entity determines to reject the first request; the first entity returns a first response to the API caller; the first response is used to indicate the rejection of the first request, thereby preventing a malicious API caller from bypassing the resource owner's authorization through the first request and requesting access to the resource owner's resources, thereby improving the security of resource access.

[0117] The following is a specific example introduction to the request processing method of the present disclosure.

[0118] Article 1a, the API caller sends an API call request to the AEF / NEF, including the API caller ID (the API caller's identity), the name of the service's API, the resource owner identifier (e.g., GPSI), and the traditional token.

[0119] Article 1b: The API caller sends an API call request to the AEF / NEF, including the API caller ID, the name of the service API, and the resource owner identifier (e.g., GPSI).

[0120] Article 2a: If a traditional token is received that does not contain the resource owner's identity information (resource owner identifier), and the API call request contains the resource owner identifier, the AEF / NEF shall reject the request. Otherwise, the AEF / NEF shall authorize the API call request based on the token.

[0121] Article 2b: If an API call request is received without a token and the request contains the resource owner identity information, the AEF / NEF shall reject the API request. Otherwise, the AEF / NEF shall authorize the request based on the information requested by the CCF using the API caller ID.

[0122] Article 3, AEF / NEF sends an API call response to the API caller.

[0123] In the embodiments provided above, the methods provided in the embodiments of the present application are described from the perspectives of the first entity and the API caller, respectively. In order to implement the various functions in the methods provided in the embodiments of the present application, the first entity and the API caller may include hardware structures and software modules, and implement the aforementioned functions in the form of hardware structures, software modules, or hardware structures plus software modules. One of the aforementioned functions may be executed in the form of hardware structures, software modules, or hardware structures plus software modules.

[0124] Please refer to Figure 5, which is a schematic diagram of the structure of a communication device 50 provided in an embodiment of the present application. The communication device 50 shown in Figure 5 may include a transceiver unit 501 and a processing unit 502. The transceiver unit 501 may include a sending unit and / or a receiving unit, wherein the sending unit is used to implement a sending function and the receiving unit is used to implement a receiving function. The transceiver unit 501 can implement the sending function and / or the receiving function.

[0125] The communication device 50 may be a terminal device (such as the API caller in the aforementioned method embodiment), a device in the terminal device, or a device that can be used in conjunction with the terminal device. Alternatively, the communication device 50 may be a network device (such as the first entity in the aforementioned method embodiment), a device in the network device, or a device that can be used in conjunction with the network device.

[0126] The communication device 50 is a network device (such as the first entity in the aforementioned method embodiment):

[0127] Processing unit 502 is used to determine to reject a first request in response to receiving a first request that meets a first condition; wherein the first condition is that the first request carries the first resource owner identifier and does not carry a token; or, the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain a resource owner identifier.

[0128] Optionally, the transceiver unit 501 is used to return a first response to the application programming interface API caller who initiated the first request; the first response is used to indicate that the API caller's request for the resource corresponding to the first resource owner identifier is rejected.

[0129] Optionally, the first request also includes at least one of the following parameters: the identifier of the API caller who initiates the first request; the identifier of the service requested by the API caller; the identifier of the API requested by the API caller; and the identifier of the resource requested by the API caller.

[0130] Optionally, the first entity is an API open function AEF network element or a network open function NEF network element in a general application programming interface framework CAPIF.

[0131] Optionally, the resource owner identifier is a universal public user identifier (GPSI) of the resource owner.

[0132] Optionally, the API caller that initiates the first request is a terminal device that requests the first resource owner to identify the corresponding resource.

[0133] Optionally, the first entity uses at least two authorization mechanisms at the same time; the authorization mechanisms include: an authorization mechanism based on traditional transport layer security pre-shared key TLS-PSK / public key infrastructure PKI, and an authorization mechanism in an API call scenario perceived by the subscriber.

[0134] The communication device 50 may be a terminal device (such as the API caller in the aforementioned method embodiment):

[0135] The transceiver unit 501 is used to send a first request to a first entity; receive a first response returned by the first entity when the first request meets a first condition; the first response is used to indicate the rejection of the first request; wherein the first condition is that the first request carries the first resource owner identifier and does not carry a token; or, the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain a resource owner identifier.

[0136] Optionally, the first request also includes at least one of the following parameters: the identifier of the API caller who initiates the first request; the identifier of the service requested by the API caller; the identifier of the API requested by the API caller; and the identifier of the resource requested by the API caller.

[0137] Optionally, the first entity is an API open function AEF network element or a network open function NEF network element in a general application programming interface framework CAPIF.

[0138] Optionally, the resource owner identifier is a universal public user identifier (GPSI) of the resource owner.

[0139] Optionally, the API caller that initiates the first request is a terminal device that requests the first resource owner to identify the corresponding resource.

[0140] Optionally, the first entity uses at least two authorization mechanisms at the same time; the authorization mechanisms include: an authorization mechanism based on traditional transport layer security pre-shared key TLS-PSK / public key infrastructure PKI, and an authorization mechanism in an API call scenario perceived by the subscriber.

[0141] Please refer to Figure 6, which is a schematic diagram of the structure of another communication device 60 provided in an embodiment of the present application. Communication device 60 can be a network device (such as the first entity in the aforementioned method embodiment), or a terminal device (such as the API caller in the aforementioned method embodiment), or a chip, chip system, or processor that supports the network device to implement the aforementioned method, or a chip, chip system, or processor that supports the terminal device to implement the aforementioned method. This device can be used to implement the method described in the aforementioned method embodiment, and for details, please refer to the description of the aforementioned method embodiment.

[0142] The communication device 60 may include one or more processors 601. The processor 601 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.

[0143] Optionally, the communication device 60 may further include one or more memories 602, on which a computer program 604 may be stored. The processor 601 executes the computer program 604 to cause the communication device 60 to perform the method described in the above method embodiment. Optionally, the memory 602 may also store data. The communication device 60 and the memory 602 may be provided separately or integrated together.

[0144] Optionally, the communication device 60 may further include a transceiver 605 and an antenna 606. The transceiver 605 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., and is configured to implement transceiver functions. The transceiver 605 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, etc., and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., and is configured to implement a transmitting function.

[0145] Optionally, the communication device 60 may further include one or more interface circuits 607. The interface circuit 607 is configured to receive code instructions and transmit the code instructions to the processor 601. The processor 601 executes the code instructions to enable the communication device 60 to execute the method described in the above method embodiment.

[0146] The communication device 60 is a network device (such as the first entity in the aforementioned method embodiment): the processor 601 is configured to execute step S201.

[0147] The communication device 60 is a terminal device (such as the API caller in the aforementioned method embodiment): the transceiver 605 is used to execute step S301 and step S302 in Figure 3.

[0148] In one implementation, processor 601 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.

[0149] In one implementation, processor 601 may store a computer program 603. Computer program 603, when executed on processor 601, enables communication device 60 to perform the method described in the above method embodiment. Computer program 603 may be embedded in processor 601, in which case processor 601 may be implemented by hardware.

[0150] In one implementation, the communication device 60 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiment. 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.

[0151] The communication device described in the above embodiment may be a network device (such as the first entity in the aforementioned method embodiment) or a terminal device (such as the API caller in the aforementioned method embodiment), 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 Figure 6. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0152] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

[0153] (2) a collection of one or more ICs, optionally including a storage component for storing data and computer programs;

[0154] (3) ASIC, such as modem;

[0155] (4) Modules that can be embedded in other devices;

[0156] (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.;

[0157] (6)Others, etc.

[0158] 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 7. The chip shown in Figure 7 includes a processor 701 and an interface 702. The number of processors 701 can be one or more, and the number of interfaces 702 can be multiple.

[0159] For the case where the chip is used to implement the functions of the network device in the embodiment of the present application (such as the first entity in the aforementioned method embodiment):

[0160] Interface 702 is used to return a first response to the application programming interface (API) caller that initiated the first request; the first response is used to indicate a rejection of the API caller's request for the resource corresponding to the first resource owner identifier.

[0161] Optionally, the first request also includes at least one of the following parameters: the identifier of the API caller who initiates the first request; the identifier of the service requested by the API caller; the identifier of the API requested by the API caller; and the identifier of the resource requested by the API caller.

[0162] Optionally, the first entity is an API open function AEF network element or a network open function NEF network element in the general application programming interface framework CAPIF.

[0163] Optionally, the resource owner identifier is the resource owner's general public user identifier (GPSI).

[0164] Optionally, the API caller that initiates the first request is a terminal device that requests the first resource owner to identify the corresponding resource.

[0165] Optionally, the first entity uses at least two authorization mechanisms at the same time; the authorization mechanisms include: an authorization mechanism based on traditional transport layer security pre-shared key TLS-PSK / public key infrastructure PKI, and an authorization mechanism in an API call scenario perceived by the subscriber.

[0166] For the case where the chip is used to implement the functions of the terminal device in the embodiment of the present application (such as the API caller in the aforementioned method embodiment):

[0167] Interface 702 is used to send a first request to a first entity; receive a first response returned by the first entity when the first request meets a first condition; the first response is used to indicate rejection of the first request; wherein the first condition is that the first request carries the first resource owner identifier and does not carry a token; or, the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain a resource owner identifier.

[0168] Optionally, the first request also includes at least one of the following parameters: the identifier of the API caller who initiates the first request; the identifier of the service requested by the API caller; the identifier of the API requested by the API caller; and the identifier of the resource requested by the API caller.

[0169] Optionally, the first entity is an API open function AEF network element or a network open function NEF network element in the general application programming interface framework CAPIF.

[0170] Optionally, the resource owner identifier is the resource owner's general public user identifier (GPSI).

[0171] Optionally, the API caller that initiates the first request is a terminal device that requests the first resource owner to identify the corresponding resource.

[0172] Optionally, the first entity uses at least two authorization mechanisms at the same time; the authorization mechanisms include: an authorization mechanism based on traditional transport layer security pre-shared key TLS-PSK / public key infrastructure PKI, and an authorization mechanism in an API call scenario perceived by the subscriber.

[0173] Optionally, the chip further includes a memory 703, which is used to store necessary computer programs and data.

[0174] 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.

[0175] An embodiment of the present application also provides a communication system, which includes a communication device in the embodiment of Figure 5 as a terminal device (such as the API caller in the aforementioned method embodiment) and a communication device as a network device (such as the first entity in the aforementioned method embodiment), or, the system includes a communication device in the embodiment of Figure 6 as a terminal device (such as the API caller in the aforementioned method embodiment) and a communication device as a network device (such as the first entity in the aforementioned method embodiment).

[0176] 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.

[0177] 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.

[0178] 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)).

[0179] 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.

[0180] 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".

[0181] The predefined in this application may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0182] 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.

[0183] 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.

[0184] 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 request processing method, characterized in that: Executed by a first entity, the method comprises: In response to receiving a first request that meets a first condition, determining to reject the first request; The first condition is that the first request carries the first resource owner identifier but does not carry a token; or the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain a resource owner identifier.

2. The method according to claim 1, characterized in that The method further comprises: A first response is returned to the application programming interface API caller that initiated the first request; the first response is used to indicate that the API caller's request for the resource corresponding to the first resource owner identifier is rejected.

3. The method according to claim 1 or 2, characterized in that: The first request also includes at least one of the following parameters: The identifier of the API caller who initiated the first request; The identifier of the service requested by the API caller; The identifier of the API requested by the API caller; The identifier of the resource requested by the API caller.

4. The method according to any one of claims 1 to 3, characterized in that: The first entity is an API open function AEF network element or a network open function NEF network element in a general application programming interface framework CAPIF.

5. The method according to any one of claims 1 to 4, characterized in that: The resource owner identifier is the resource owner's general public user identifier (GPSI).

6. The method according to any one of claims 1 to 4, characterized in that: The API caller that initiates the first request is a terminal device that requests the first resource owner to identify the corresponding resource.

7. The method according to any one of claims 1 to 5, characterized in that: The first entity uses at least two authorization mechanisms at the same time; the authorization mechanisms include: an authorization mechanism based on traditional transport layer security pre-shared key TLS-PSK / public key infrastructure PKI, and an authorization mechanism in an API call scenario perceived by a subscriber.

8. A request processing method, characterized in that: Executed by an API caller, the method includes: Sending a first request to a first entity; receiving a first response returned by the first entity when the first request satisfies a first condition; the first response is used to indicate rejection of the first request; The first condition is that the first request carries the first resource owner identifier and does not carry a token; or the first condition is that the first request carries the first resource owner identifier and does not carry a token. Identification token.

9. The method according to claim 8, characterized in that The first request also includes at least one of the following parameters: The identifier of the API caller who initiated the first request; The identifier of the service requested by the API caller; The identifier of the API requested by the API caller; The identifier of the resource requested by the API caller.

10. The method according to claim 8 or 9, characterized in that: The first entity is an API open function AEF network element or a network open function NEF network element in a general application programming interface framework CAPIF.

11. The method according to any one of claims 8 to 10, characterized in that: The resource owner identifier is the resource owner's general public user identifier (GPSI).

12. The method according to any one of claims 8 to 10, characterized in that: The API caller that initiates the first request is a terminal device that requests the first resource owner to identify the corresponding resource.

13. The method according to any one of claims 8 to 10, characterized in that: The first entity uses at least two authorization mechanisms at the same time; the authorization mechanisms include: an authorization mechanism based on traditional transport layer security pre-shared key TLS-PSK / public key infrastructure PKI, and an authorization mechanism in an API call scenario perceived by a subscriber.

14. A communication device, characterized in that: Set in the first entity, the device includes: A processing unit, configured to, in response to receiving a first request that satisfies a first condition, determine to reject the first request; The first condition is that the first request carries the first resource owner identifier but does not carry a token; or the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain a resource owner identifier.

15. A communication device, characterized in that: Set at the API caller, the device includes: A transceiver unit, configured to send a first request to a first entity; The transceiver unit is further configured to receive a first response returned by the first entity when the first request satisfies a first condition; the first response is configured to indicate a rejection of the first request; The first condition is that the first request carries the first resource owner identifier but does not carry a token; or the first condition is that the first request carries the first resource owner identifier and carries a token that does not contain a resource owner identifier.

16. 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 7.

17. 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 8 to 13.

18. 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 used to run the code instructions to execute the method according to any one of claims 1-7.

19. 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 used to run the code instructions to execute the method according to any one of claims 8 to 13.

20. A computer-readable storage medium, used for storing instructions, which, when executed, enable the method according to any one of claims 1 to 7 to be implemented.

21. A computer-readable storage medium, used for storing instructions, which, when executed, enable the method according to any one of claims 8 to 13 to be implemented.

Citation Information

Patent Citations

  • Location-based access to controlled access resources

    CN111869179A

  • Distributed denial of service attack protection for internet of things devices

    US20180109554A1

  • System for efficient management of invalid access tokens

    US20190318115A1

  • Authorization method and device for proxy subscription

    WO2020220919A1

Cited By

  • Method and apparatus for providing or revoking resource owner's authorization information using oauth

    US20240224032A1