Communication method and device

Abstract

A communication method and apparatus, the method comprising: after receiving a first request, a first apparatus determines at least one level of a first service according to the first request; wherein the first request is used for requesting a first user to cancel authorization of a first level of a first service, the first service comprises a plurality of levels, the plurality of levels comprise a first level and a second level, and a resource corresponding to the second level of the first service is a first resource used for providing the first service for the first user. According to the method, after the first request for authorization of the first level of the first service is revoked for the first user, the network side can provide the first service for the first user through the first resource corresponding to the second level of the first service, so that interruption of the first service for the first user can be avoided, and denial of service of the first user is avoided.

Description

Technical Field

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

[0002] The capability open architecture of the 3rd generation partnership project (3GPP) network provides a way for the 3GPP network to provide services to the outside world. Under this architecture, the application function (AF) can use the capabilities provided by the 3GPP network to process and / or obtain 3GPP-related data information, which may include processing and / or obtaining 3GPP network data, as well as processing and / or obtaining 3GPP network user-related data. When processing and / or obtaining user-related data, the AF must obtain the user's authorization. For example, the AF can request the 3GPP network to send the user's location information to the outside world. If the user's authorization is not obtained, the user's privacy information may be exposed. For another example, the AF can request the 3GPP network to change the user's network service quality (quality of service, QoS). If the user's authorization is not obtained, the user experience will be inconsistent with the expected value, and the user may also be charged additional fees.

[0003] How to improve the performance of services provided by the capability exposure architecture requires further research. Summary of the invention

[0004] The present application provides a communication method and device for improving the performance of services provided by a capability open architecture.

[0005] In a first aspect, an embodiment of the present application provides a communication method, which can be applied to a first device, and the first device can be AzF, CCF or AEF, or a module applied to AzF, CCF or AEF, such as a chip, a chip system or a processor, or a logical node, a logical module or software that can implement all or part of the functions of AzF, CCF or AEF. Among them, the method may include: the first device receives a first request, and the first request is used to request the revocation of the authorization of the first level of the first service for the first user, and the first service includes multiple levels, and the multiple levels include the first level. The first device can determine at least one level of the first service based on the first request, and the at least one level includes a second level, and the resources corresponding to the second level of the first service are the first resources used to provide the first service to the first user.

[0006] Through this method, after receiving a first request for requesting to revoke authorization of a first level of a first service for a first user, the first device can determine at least one level of the first service. The resource corresponding to the second level in the at least one level is a first resource for providing the first service to the first user. In this way, after revoking authorization of the first level of the first service for the first user, the network side can still provide the first service to the first user through the first resource, thereby avoiding interruption of the first service for the first user and avoiding denial of service to the first user.

[0007] In one possible design, the effective authorization for the first service of the first user includes at least two levels of authorization for the first service, and the at least two levels include the first level. The first device may determine one or more levels of the at least two levels except the first level as at least one level. With this design, the first device can quickly determine at least one level of the first service based on the effective authorization for the first service of the first user.

[0008] In one possible design, the first device may send information for indicating at least one level. With this design, the first device may accurately indicate at least one level.

[0009] Optionally, the information for indicating at least one level includes at least one of the following: indication information of at least one level; or information corresponding to at least one level. In this way, the first device can flexibly indicate at least one level.

[0010] In one possible design, at least one level includes N levels other than the first level in at least two levels, where N is an integer greater than or equal to 2. The first device may also send first indication information, where the first indication information is used to indicate a first rule for selecting the second level from the N levels. With this design, the first device may accurately indicate the first rule, and the receiving party may quickly and accurately determine the first rule based on the first at least information.

[0011] In one possible design, at least one level includes N levels other than the first level in at least two levels, where N is an integer greater than or equal to 2. The first device may select the second level from the N levels according to the first rule. With this design, the first device may determine at least one level and the second level. In this way, the first device may transmit information for indicating the second level without transmitting indication information of the level other than the second level in at least one level, thereby saving transmission resources and reducing signaling overhead.

[0012] Optionally, the first rule includes at least one of the following: the second level is the highest quality level that can be met by the network where the first device is located among the N levels; or the second level is the latest authorized level among the N levels.

[0013] In one possible design, the effective authorization of the first service for the first user includes one level of authorization of the first service, where the one level is the first level. The first device may determine the set second level as at least one level. With this design, the first device may determine the set second level as at least one level. In this way, after revoking the authorization of the first level of the first service for the first user, the network may provide the first service to the first user through the first resource corresponding to the second level, thereby avoiding interruption of the first service of the first user.

[0014] In one possible design, the first request also includes the first information, or the first device may also receive the first information. The first information is used to indicate the second level. The first device may determine the second level as at least one level. With this design, the first information received by the first device may indicate the second level, so that the first device does not need to determine the second level by calculation, thereby reducing the amount of calculation of the first device and saving the computing resources of the first device. Furthermore, after revoking the authorization of the first level of the first service for the first user, the network may provide the first service to the first user through the first resource corresponding to the second level, thereby avoiding interruption of the first service of the first user.

[0015] In one possible design, the first information is indicative information of the second level, or the first information is information corresponding to the second level. The valid authorization of the first service for the first user includes the authorization of the second level of the first service. With this design, the first information can flexibly indicate the second level.

[0016] In a possible design, the first device may also send information for indicating the second level. With this design, the first device may accurately indicate the second level.

[0017] Optionally, the information used to indicate the second level includes at least one of the following: indication information of the second level; or information corresponding to the second level. In this way, the first device can flexibly indicate the second level.

[0018] In a possible design, the first device may also send at least one of the following: indication information of the first user or indication information of the first service. In this way, the receiving party may determine the authorization information corresponding to the first user and the first service.

[0019] In one possible design, the first request includes at least one of the following: first authorization information or indication information of the first authorization information. The first authorization information is authorization information of the first level for authorizing the first user to provide the first service. In this way, the recipient can quickly determine that the first request is used to request the revocation of the authorization corresponding to the first authorization information based on the first authorization information or the indication information of the first authorization information.

[0020] In one possible design, the first request includes at least one of the following: indication information of the first user; or indication information of the first service. In this way, the recipient can quickly determine that the first request is used to request the revocation of authorization for the first service of the first user based on the indication information of the first user and / or the indication information of the first service.

[0021] In one possible design, the first request includes first authorization information. The first authorization information is authorization information of a first level for authorizing the first user to provide the first service, and the first authorization information includes at least one of the following: indication information of the first user or indication information of the first service. In this design, the indication information of the first user and / or the indication information of the first service may be included in the first authorization information, thereby eliminating the need to set an additional field in the first request for carrying the indication information of the first user and / or the indication information of the first service.

[0022] In one possible design, the first device may determine at least one level of the first service for the first user based on the indication information of the first user and the indication information of the first service. With this design, the first device may quickly and accurately determine at least one level of the first service for the first user.

[0023] In one possible design, the first device may determine at least one authorization information based on the indication information of the first user and the indication information of the first service, wherein each authorization information in the at least one authorization information includes the indication information of the first user and the indication information of the first service, and each authorization information in the at least one authorization information is authorization information for authorizing one or more levels of the first service to the first user. Then, the first device may determine at least one level of the first service based on the at least one authorization information. With this design, the first device may quickly and accurately determine at least one level of the first service for the first user.

[0024] Optionally, the first service is a QoS service, the level of the first service is a QoS level or a QoS level corresponding to a 5QI value, and the first resource is a PDU session.

[0025] In a second aspect, an embodiment of the present application provides a communication method, which can be applied to a first device, and the first device can be an API caller or a device including an API caller (for example, a terminal or AF), or a module applied to an API caller or a device including an API caller, such as a chip, a chip system, or a processor, or a logical node, a logical module, or software that can implement all or part of the functions of the API caller or the device including the API caller. Among them, the method may include: the second device sends a first request, and the first request is used to request the revocation of the authorization of the first level of the first service for the first user, and the first service includes multiple levels, and the multiple levels include the first level. The first request also includes first information, or the second device also sends the first information. Among them, the first information is used to indicate the second level, and the resources corresponding to the second level of the first service are the first resources used to provide the first service to the first user.

[0026] In one possible design, the first information is indication information of the second level, or the first information is information corresponding to the second level; wherein the valid authorization of the first service for the first user includes the second level authorization of the first service.

[0027] In a possible design, the first request includes at least one of the following: first authorization information or indication information of the first authorization information. The first authorization information is authorization information of a first level for authorizing the first user to provide the first service.

[0028] In one possible design, the first request includes at least one of the following: indication information of the first user; or indication information of the first service.

[0029] In a possible design, the first request includes first authorization information. The first authorization information is first level authorization information for authorizing the first user to use the first service, and the first authorization information includes at least one of the following: indication information of the first user or indication information of the first service.

[0030] In one possible design, the first service is a QoS service, the level of the first service is the QoS level or the QoS level corresponding to the 5QIvalue, and the first resource is a PDU session.

[0031] In a third aspect, the present application provides a communication device, which may be a terminal or a module in a terminal (such as a circuit or a chip), or a logical node, a logical module or software that can implement all or part of the terminal functions. The communication device has the function of implementing the first aspect. For example, the communication device includes a module or unit or means corresponding to the operation involved in the first aspect, and the module or unit or means may be implemented by software, or by hardware, or the corresponding software may be implemented by hardware.

[0032] In a possible design, the communication device includes a processing unit and an interface unit, wherein the interface unit can be used to send and receive signals to achieve communication between the communication device and other devices; the processing unit can be used to perform some internal operations of the communication device. The functions performed by the processing unit and the interface unit can correspond to the operations involved in the first aspect above.

[0033] In one possible design, the communication device includes a processor, which can be used to couple with a memory. The memory can store necessary computer programs or instructions for implementing the functions involved in the first aspect. The processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the communication device implements the method in any possible design of the first aspect.

[0034] In one possible design, the communication device includes a processor and a memory, and the memory can store necessary computer programs or instructions for implementing the functions involved in the first aspect. The processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the communication device implements the method in any possible design of the first aspect.

[0035] In one possible design, the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and execute the method in any possible design of the first aspect above.

[0036] In a fourth aspect, the present application provides a communication device, which may be an API caller or a device including an API caller (e.g., a terminal or AF), or a module applied to an API caller or a device including an API caller, such as a chip, a chip system, or a processor, or a logical node, a logical module, or software that can implement all or part of the functions of an API caller or a device including an API caller. For example, the communication device includes a module or unit or means corresponding to the operation involved in the second aspect above, and the module or unit or means may be implemented by software, or by hardware, or the corresponding software may be implemented by hardware.

[0037] In a possible design, the communication device includes a processing unit and an interface unit, wherein the interface unit can be used to send and receive signals to achieve communication between the communication device and other devices; the processing unit can be used to perform some internal operations of the communication device. The functions performed by the processing unit and the interface unit can correspond to the operations involved in the second aspect above.

[0038] In one possible design, the communication device includes a processor, which can be used to couple with a memory. The memory can store necessary computer programs or instructions for implementing the functions involved in the second aspect. The processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the communication device implements the method in any possible design of the second aspect.

[0039] In one possible design, the communication device includes a processor and a memory, and the memory can store necessary computer programs or instructions for implementing the functions involved in the second aspect. The processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the communication device implements the method in any possible design of the second aspect.

[0040] In one possible design, the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and execute the method in any possible design of the second aspect above.

[0041] It can be understood that in the third aspect or the fourth aspect above, the processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. In addition, the above processors can be one or more, and the memories can be one or more. The memory can be integrated with the processor, or the memory can be separately set from the processor. In the specific implementation process, the memory can be integrated with the processor on the same chip, or can be set on different chips respectively. The embodiment of the present application does not limit the type of memory and the setting method of the memory and the processor.

[0042] In a fifth aspect, the present application provides a communication system, which may include the communication device described in the third aspect and the communication device described in the fourth aspect.

[0043] In a sixth aspect, the present application provides a computer-readable storage medium, in which computer-readable instructions are stored. When a computer reads and executes the computer-readable instructions, the computer executes a method in any possible design of any one of the first to second aspects above.

[0044] In a seventh aspect, the present application provides a computer program product. When a computer reads and executes the computer program product, the computer executes a method in any possible design of any one of the first to second aspects above.

[0045] In an eighth aspect, the present application provides a chip, wherein the chip is used to read a computer program stored in a memory to execute a method in any possible design of any one of the first to second aspects above.

[0046] The technical effects that can be achieved in any of the second to eighth aspects mentioned above can refer to the description of the technical effects that can be achieved by any possible design in the first aspect mentioned above, and the repetitions will not be discussed here. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 An architecture diagram of a communication system provided in an embodiment of the present application;

[0048] Figure 2 An architecture diagram of another communication system provided in an embodiment of the present application;

[0049] Figure 3 A flowchart of a first communication method provided in an embodiment of the present application;

[0050] Figure 4 A flowchart of a second communication method provided in an embodiment of the present application;

[0051] Figure 5 A flowchart of a third communication method provided in an embodiment of the present application;

[0052] Figure 6 A flowchart of a fourth communication method provided in an embodiment of the present application;

[0053] Figure 7 A flowchart of a fifth communication method provided in an embodiment of the present application;

[0054] Figure 8 A structural diagram of a communication device provided in an embodiment of the present application;

[0055] Fig. 9 A structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0056] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0057] The following introduces the architecture of the communication system to which the method provided in this application is applied.

[0058] Figure 1 The present invention is applicable to a communication system architecture diagram, which shows the fifth generation (the5 th generation, 5G) network architecture. Figure 1As shown, the communication system may include three parts, namely, a terminal part, an operator network part and a data network (DN). The functions of some network elements are described below.

[0059] A terminal, also known as a terminal device or user equipment (UE), is a device with wireless transceiver capabilities that can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water (such as ships); it can also be deployed in the air (such as airplanes, balloons, and satellites). A terminal can be a mobile phone, a tablet computer (pad), a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc.

[0060] The above-mentioned terminal can establish a connection with the operator network through the interface provided by the operator network (such as N1, etc.), and use the data and / or voice services provided by the operator network. The terminal can also access the DN through the operator network, use the operator services deployed on the DN, and / or services provided by a third party. Among them, the above-mentioned third party may be a service provider other than the operator network and the terminal, and can provide data and / or voice services to the terminal. Among them, the specific form of expression of the above-mentioned third party can be determined according to the actual application scenario, and is not limited here.

[0061] The operator network may be a network deployed by an operator, and may include access network equipment and core network equipment. In a possible implementation method, the operator network also includes an AF network element. Alternatively, the AF network element may not belong to the operator network, but to a third party.

[0062] Access network equipment is equipment in a wireless network, such as a radio access network (RAN) node or a radio access network device that connects a terminal to a wireless network. At present, some examples of access network equipment include: next-generation base stations (gNodeB, gNB) in 5G, transmission reception points (TRP), evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home Node B, HNB), base band unit (BBU), wireless fidelity (Wifi) access point (AP), integrated access and backhaul (IAB), etc. In one implementation, the access network equipment may also be a future communication system (e.g., the 6th generation (the 7th generation) of the wireless communication system). th Access network equipment in generation, 6G) communication system.

[0063] The core network device may include at least one of the following network elements: a mobility management network element, a session management network element, a user plane network element (e.g., a user plane function (UPF) network element), a data management network element (e.g., a unified data management (UDM) network element), a unified data repository (UDR) network element, a network exposure network element (e.g., a network exposure function (NEF) network element), a policy control network element (e.g., a policy control function (PCF) network element), or an authentication function network element (e.g., an authentication server function (AUSF) network element), etc. Some of the network elements are described below.

[0064] In this application, the mobility management network element is a control plane network element provided by the operator network, which is responsible for the access control and mobility management of the terminal accessing the operator network, such as mobile state management, allocation of user temporary identity, authentication and authorization of users, etc. In 5G, the mobility management network element can be an access and mobility management function (AMF) network element. In future communications such as 6G, the mobility management network element can still be an AMF network element, or have other names, which are not limited in this application.

[0065] In this application, the session management network element is a control plane network element provided by the operator network, which is responsible for managing the protocol data unit (PDU) session of the terminal. The PDU session is a channel for transmitting PDUs, and the terminal needs to transmit PDUs to each other with the DN through the PDU session. The SMF network element is responsible for establishing, maintaining and deleting the PDU session. The functions of the session management network element include: session management (such as session establishment, modification and release, including tunnel maintenance between user plane network elements and access network devices), selection and control of user plane network elements, service and session continuity (SSC) mode selection, roaming, etc. In 5G, the session management network element can be a session management function (SMF) network element. In future communications such as 6G, the session management network element can still be an SMF network element, or a network element with other names but with all or part of the functions of a session management network element, which is not limited in this application.

[0066] In this application, the network open network element is a control plane network element provided by the operator. The network open network element opens the external interface of the operator network to the third party in a secure manner, and the interface is, for example, an application programming interface (API). For example, when the session management network element needs to communicate with the network element of the third party, the network open network element can serve as a relay for the communication between the session management network element and the network element of the third party. When the network open network element acts as a relay, it can be used as a translator of the identification information of the contracted user, as well as the translation of the identification information of the third-party network element. For example, when the network open network element sends the subscriber permanent identifier (SUPI) of the contracted user from the operator network to the third party, the SUPI can be translated into its corresponding external identity (ID). Conversely, when the network open network element sends the external ID (network element ID of the third party) to the operator network, it can be translated into SUPI. In 5G, the network open network element can be a NEF network element. In future communications such as 6G, the network open network element can still be a NEF network element, or have other names, which are not limited in this application.

[0067] In the embodiments of the present application, the communication device for realizing the function of the access network device, terminal or core network device may be the access network device, terminal or core network device itself, or may be a device capable of supporting the access network device, terminal or core network device to realize the function, such as a chip system, which may be installed in the access network device, terminal or core network device. In the technical solution provided in the embodiments of the present application, the technical solution provided in the embodiments of the present application is described by taking the device for realizing the function of the access network device as the access network device, the device for realizing the function of the terminal as the terminal, and the device for realizing the function of the core network device as the core network device as an example.

[0068] DN is a network outside the operator network. The operator network can access multiple DNs. Multiple services can be deployed on DN, which can provide data and / or voice services to terminals. For example, DN is the private network of a smart factory. The sensors installed in the workshop of the smart factory can be terminals. The control server of the sensors is deployed in DN, and the control server can provide services for the sensors. The sensors can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions. For another example, DN is the internal office network of a company. The mobile phones or computers of the company's employees can be terminals. The employees' mobile phones or computers can access information, data resources, etc. on the company's internal office network.

[0069] Figure 1N1, N2, N3 and N4 are interface serial numbers. The meanings of these interface serial numbers can be found in the meanings defined in the 3GPP standard protocol and are not limited here.

[0070] Figure 2 An API system architecture that may be applicable to the embodiments of the present application is exemplarily given, and the architecture may be a common API framework (CAPIF) architecture. Figure 2 As shown, the CAPIF architecture may include: API invoker, CAPIF core function (CCF) network element, authorization function (AuF or AzF) network element and API exposing function (AEF) network element. Optionally, the CAPIF architecture may also include at least one of the following: API publishing function (APF) network element, API management function (API management function) network element or resource owner client (RO Client). The components of the CAPIF architecture are described below.

[0071] API callers are generally third-party applications that have signed service agreements with public land mobile network (PLMN) operators. These applications can run in the terminal or AF, so the API caller can be part of the terminal or part of the AF. The API caller can have the following functions: provide the identity information of the API caller and other information required to authenticate the API caller; support mutual authentication with the CCF; obtain authorization before accessing the service API; discover the service API; find and call the service API, etc. The location of the API caller in the communication network can be seen in Figure 1 AF network element or UE in.

[0072] CCF may have the following functions: authenticate API callers based on their identity information and other information required to authenticate API callers; support mutual authentication with API callers; provide authorization to API callers before they access service APIs; publish and store service API information, and support discovery of service APIs; control access to service APIs based on policies configured by PLMN operators; monitor service API calls; store service API call logs, and provide service API call logs to authorization function network elements; perform billing based on service API call logs; add new API callers and delete API callers; store CAPIF and service API-related policy configurations; support auditing based on access logs (e.g., detecting whether there is abuse); support publishing and / or discovering service APIs using another CAPIF core function in CAPIF docking. Optionally, CCF may be a device in the core network or in other networks, and this application does not limit this.

[0073] AzF is used to obtain user authorization. In this application, AuF and AzF can be replaced with each other. In addition, both AzF and CCF have authorization functions, and AzF and CCF can be set in the same device or in different devices. The following is an example of AzF and CCF being set in the same device. At this time, AzF and CCF can be used without distinction. That is to say, AzF and CCF can be replaced with each other in the following, and can also be called authorization server.

[0074] AEF is used to provide service API and is the entry point for API callers to call service API. AEF can have the following functions: authenticate API callers based on the identity information and other information required for API caller authentication provided by CCF; verify the authorization provided by CCF; record the number of times the service API in CCF is called. For example, AEF can be NEF, that is, the location of AEF in the communication network can be seen in Figure 1 NEF network element in.

[0075] The API publishing function network element is a function network element that enables API providers to publish APIs. It can publish service API information to CCF so that API callers can find service API information in CCF. It should be noted that the API publishing function network element and NEF can be set together.

[0076] The API management function network element performs management of the service API, such as monitoring the status of the service API, recording call information, etc. It should be noted that the API management function network element can be co-located with the NEF.

[0077] RO Client is an application client used by users, which can display the operation interface to users. RO Client is, for example, an operating system or a browser. RO Client can be Figure 1 Application on the UE.

[0078] Figure 2 CAPIF-1, CAPIF-1e, CAPIF-2, CAPIF-2e, etc. are reference points. The meanings of these reference points can be found in the meanings defined in the 3GPP standard protocol and are not limited here.

[0079] It should be noted that Figure 1 and Figure 2 The communication system shown does not constitute a limitation on the communication system to which the embodiments of the present application can be applied. Therefore, the communication method provided in the embodiments of the present application can also be applied to communication systems of various standards, such as: long term evolution (LTE) communication system, 5G communication system, 6G communication system and future communication system, vehicle to everything (V2X), long term evolution-vehicle network (LTE-vehicle, LTE-V), vehicle to vehicle (V2V), vehicle network, machine type communication (MTC), Internet of things (IoT), long term evolution-machine to machine (LTE-machine to machine, LTE-M), machine to machine (machine to machine, M2M), Internet of things, etc. In addition, the communication system provided in the present application can be used in terrestrial network (TN) and / or non-terrestrial network (NTN), without limitation. In addition, it should be noted that the embodiments of the present application do not limit the names of the network elements in the communication system. For example, in communication systems of different standards, each network element may have other names; for example, when multiple network elements are integrated into the same physical device, the physical device may also have other names.

[0080] To facilitate understanding of the present application, the terms used in the present application are explained below.

[0081] 1) A token is a digital object, data field, or string that contains authorization information or authentication information. For example, a token can be used to indicate authorization of one or more services or resources for one or more users.

[0082] There are many types of tokens according to their usage, such as access tokens (access_token), refresh tokens (refresh_token), identity tokens (ID token), etc. Among them, the access token is a credential used to access protected resources. For example, it can be used to authorize API callers to access the API services corresponding to the access token through AEF, such as QoS services. The refresh token is a credential used to obtain an access token. For example, it can be used to authorize API callers to request a new token from CCF when the current access token expires, that is, the refresh token can be used to update the usage time of the current token. In addition, the refresh token can also be used to shorten the validity period of the current access token or reduce the scope of the current access token.

[0083] A token may include a claim. The claim is a short piece of asserted information about the subject of the token and may include at least one of the following:

[0084] 1. Timeout: It can be used to determine the timeout of the token. For example, in the token declaration, the timeout: {December 2, 23} means that the token will be invalid from December 2, 2023.

[0085] 2. API caller identifier (ID): used to indicate the API caller corresponding to the token. For example, the token declaration includes API Invoker ID#1. If the token is an access token, it means that the API caller corresponding to API Invoker ID#1 is authorized to access the API service corresponding to the access token through AEF. If the token is an update token, it means that the API caller corresponding to API Invoker ID#1 is authorized to request an updated token from CCF.

[0086] 3. AEF ID: used to indicate the AEF corresponding to the token. For example, the token declaration includes AEF ID#1. If the token is an access token, it means that the API caller is authorized to access the API service corresponding to the access token through the AEF corresponding to AEF ID#1.

[0087] 4. Service indication information: used to indicate the service authorized by the token. The service indication information can be an API service ID (API service ID), which can also be called a service API ID (service API ID) or a service ID (serviceID). For example, the token declaration includes API service ID#1. If the token is an access token, it means that the API caller is authorized to access the API service corresponding to API service ID#1 through AEF.

[0088] 5. User indication information: used to indicate the user corresponding to the token. The user indication information can be the user ID or the terminal ID corresponding to the user, such as the user's generic public subscription identifier (GPSI) or SUPI.

[0089] 6. Scope: used to determine the authorization scope of the token. For example, the scope declared in the token includes AEFID#1: API service ID#1, API service ID#2, which means that the API caller is authorized to access the API services corresponding to API service ID#1 and API service ID#2 through AEF#1.

[0090] Optionally, each information in the above declaration can be a separate declaration. For example, the timeout period is one declaration, and the scope is another declaration. It should be noted that the indication information of the service can be a separate declaration or included in the declaration scope. This application does not limit in which declaration the indication information of the service is included.

[0091] It should be noted that tokens can also be classified according to whether they include information such as declarations. For example, a structured type token includes one or more of the above declaration information. The recipient or verifier of the token (such as AEF) can obtain the declaration information from the token. For another example, an opaque type token does not include the above declaration information, and the recipient or verifier of the token (such as AEF) needs to request other network elements through other information in the token to indirectly obtain the declaration information or verify the declaration information. Optionally, the other information may be index information, and the index information is, for example, a token ID or a reference ID. Tokens can also be classified in other ways. For example, a bearer type token means that the owner of the token is authorized to use the resources or services corresponding to the token; a message authentication code (MAC) type token requires the owner of the token to further prove that he has the corresponding MAC key before being authorized to use the resources or services corresponding to the token. This application does not limit the classification method of tokens.

[0092] Optionally, the token may further include a signature, which may be a signature of the CCF's statement on the token, and may be used to protect the integrity and / or confidentiality of the token.

[0093] In this application, the token can be encrypted; or, the token can also be unencrypted. If the token is encrypted, the holder of the token (for example, the API caller) needs to obtain the decryption key to read the statement in the token. This application does not restrict whether the token is encrypted.

[0094] 2) QoS flow: used to transmit data with the same QoS characteristics (requirements such as reliability or latency) in a service.

[0095] The mobile communication system manages QoS through QoS flows. For each service flow, the mobile communication system can select the corresponding QoS flow according to the QoS requirements of the service. QoS flows include guaranteed bit rate (GBR) QoS flows and non-guaranteed bit rate (non-GBR) QoS flows.

[0096] In the 5G system, the configuration information (also referred to as parameters) of a QoS flow may include: 5G QoS identifier (5G QoS identifier, 5QI). 5QI can be used to index the QoS features set by the 5G system for a QoS flow. The QoS features may include at least one of the following: resource type (resource type, where the resource type is divided into GBR resources and non-GBR resources), priority, packet delay budget (packet delay budget, for example, the delay of a data packet from a terminal device to a user-side network element), packet error probability (packet error rate), MFBR, averaging window (averaging window, used to calculate the rate corresponding to GBR). Table 1 shows several possible correspondences between 5QI and QoS features.

[0097] Table 1

[0098]

[0099] In the following text of this application, "sending information to...(terminal)" can be understood as the destination of the information being the terminal, and can include directly or indirectly sending information to the terminal. "Receiving information from...(terminal)" can be understood as the source of the information being the terminal, and can include directly or indirectly receiving information from the terminal. The information may be processed as necessary between the source and destination of the information, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood similarly and will not be repeated here.

[0100] Currently, the 3GPP network can provide services to the outside world. For example, the services provided by the 3GPP network to the outside world include providing user location information. After the API caller obtains authorization for the user's location information, the user's location information can be obtained through the 3GPP network. For another example, the services provided by the 3GPP network to the outside world include QoS services. The API caller can request the 3GPP network to change the QoS service level of the user or terminal. After obtaining authorization for a certain level of QoS service, the API caller can establish or modify a PDU session corresponding to the level for the user or terminal through the 3GPP network, so that the quality of communication of the user or terminal meets the requirements of the level.

[0101] After the API caller obtains authorization, the authorization may be revoked. Currently, when the authorization is revoked, the resources related to the service corresponding to the authorization are released. For example, after obtaining authorization to obtain the user's location information, the API caller can send a revocation request to AzF, which is used to request the revocation of the authorization of the user's location information. Then, AzF can revoke the authorization of the user's location information for the API caller and notify the 3GPP network (such as AEF) to release the resources corresponding to the authorization.

[0102] However, the service corresponding to the authorization may be a service with multiple levels. If an authorization is for a certain level of service, when the authorization is withdrawn, all resources related to the service corresponding to the authorization will be released, which may cause service interruption. The following is an example of a service with multiple levels being a QoS service. For example, the API caller obtains token #a, and token #a is used to indicate that the authorized QoS service for a certain user is QoS level 3. If the API caller sends a revocation request to AzF to request the revocation of token #a, AzF can revoke the authorization for the QoS service for the user and notify AEF to release all resources corresponding to the QoS service. In this way, the PDU session corresponding to the user's QoS service will be released, resulting in an interruption of the user's service, that is, denial of service (Denial of service, DoS).

[0103] In view of this, an embodiment of the present application provides a communication method. Figure 3 A flow chart corresponding to the communication method provided in the embodiment of the present application. Figure 3 The method is illustrated by taking the first device and the second device as the execution subject of the interaction as an example, but the present application does not limit the execution subject of the interaction. For example, the first device can be AzF, CCF or AEF, or a module applied to AzF, CCF or AEF, such as a chip, a chip system or a processor, or a logical node, a logical module or software that can realize all or part of the functions of AzF, CCF or AEF; the second device can also be an API caller, or a module applied to an API caller, such as a chip, a chip system or a processor, or a logical node, a logical module or software that can realize all or part of the functions of an API caller.

[0104] like Figure 3 As shown, the method comprises the following steps:

[0105] S301: The second device sends a first request; correspondingly, the first device receives the first request.

[0106] The first request is used to request to revoke authorization of a first level of a first service for a first user, and the first service may include multiple levels, including the first level. The first service is, for example, a QoS service; the level of the first service is, for example, a QoS level corresponding to a value of a QoS level or a 5QI value (5QI value) or a QoS flow identifier (QoS flow identifier, QFI) value (QFI value) corresponding to a QoS level.

[0107] In some examples, the first request may include: first authorization information, which is authorization information of the first level for authorizing the first user to provide the first service. In this way, the first device can determine that the second device requests to revoke the first level of authorization for the first service for the first user based on the first authorization information in the first request. Among them, the first authorization information may be expressed in a variety of forms, for example, the first authorization information may be expressed in at least one of the following forms: token, ticket, voucher, certificate or assertion, credential, authorization information element, authorization information container. The following is an example of the first authorization information being expressed in the form of a token. For example (hereinafter referred to as Example 1), the first authorization information is token #1, the user indication information in token #1 is the indication information of the first user, wherein the indication information of the first user may be the GPSI or SUPI of the first user, the service indication information in token #1 is the indication information of the QoS service, and token #1 also includes: scope:{QoS: level=3}, which means that token #1 is the authorization information of QoS level 3 for authorizing the first user to provide the QoS service. When the first request includes token #1, the first request is used to request the first user to revoke authorization for QoS level 3 of the QoS service. It should be understood that Example 1 is described by taking the first level included in the scope in token #1 as an example. The first level may also be included in other information of token #1, for example, included in the indication information of the service, which is not limited in the present application.

[0108] In some other examples, the first request may include: indication information of the first authorization information. The specific content of the first authorization information can refer to the description in the previous paragraph and will not be repeated here. The indication information of the first authorization information is, for example, the ID of the first authorization information. In this way, the first device can determine the specific content of the first authorization information based on the indication information of the first authorization information, thereby determining to revoke the first level of authorization for the first service for the first user. For example, the first authorization information is token #1 in Example 1. When the first request includes the ID of token #1, the first device determines, based on the ID of token #1, that token #1 includes: scope:{QoS:level=3}, thereby determining that the first request is used to request the revocation of authorization for QoS level 3 of the QoS service for the first user.

[0109] The following example illustrates how the first device determines the first authorization information based on the indication information of the first authorization information. For example, the first device stores the first authorization information, and optionally, the first device also stores the correspondence between the first authorization information and the indication information of the first authorization information. The first device may obtain the first authorization information stored locally based on the indication information of the first authorization information. In this example, the first device may be CCF or AEF. For another example, the first authorization information is not stored in the first device, and the first authorization information is stored in device #1. The first device may obtain the first authorization information from device #1 based on the indication information of the first authorization information. In this example, the first device may be AEF, and device #1 may be CCF; or, the first device may be CCF or AEF, and device #1 is a device that stores a database of authorization information.

[0110] In some possible ways, the first request further includes at least one of the following: indication information of the first user, or indication information of the first service. The indication information of the first user may be an ID of the first user, or an ID of a terminal corresponding to the first user, such as the GPSI or SUPI of the first user. The indication information of the first service may be an API service ID corresponding to the first service.

[0111] In some examples, at least one of the indication information of the first user or the indication information of the first service may be included in the first authorization information in the first request. The specific content of the first authorization information can refer to the description of the first authorization information above, which will not be repeated here. For example, the first authorization information is token #1, the indication information of the first user may be the user ID in the declaration of token #1, and the indication information of the first service may be the API service ID in the declaration of token #1 or the API service ID in the declaration scope of token #1.

[0112] In some other examples, at least one of the indication information of the first user or the indication information of the first service may be included in an information element (IE) other than the first authorization information in the first request. In this way, the first device can determine that the first request is a request for the first service of the first user without parsing the first authorization information.

[0113] Optionally, in S301, when the first device is a CCF, the first device may directly receive the first request from the second device. When the first device is an AEF, the first device may directly receive the first request from the second device, or may receive the first request from the second device through the CCF.

[0114] It should be understood that the first request may be an existing message (eg, a revocation request) or a new message, and this application does not limit this.

[0115] S302: The first device determines at least one level of a first service according to the first request.

[0116] The at least one level includes a second level, and the resource corresponding to the second level of the first service is a first resource for providing the first service to the first user, and the first resource is, for example, a PDU session. Optionally, the second level is different from the first level.

[0117] For example, the first service is a QoS service. The first level of the first service is QoS level 3, and the resource corresponding to QoS level 3 is PDU session #1. The second level of the first service is QoS level 4, and the resource corresponding to QoS level 4 is PDU session #2. In this way, after receiving the first request, the authorization for QoS level 3 for the first user is revoked, PDU session #1 is released, and the resource corresponding to QoS level 4 is PDU session #2, which is established. The network side can provide QoS service to the first user through PDU session #2, thereby avoiding interruption of QoS service for the first user and preventing the first user from being denied service.

[0118] For another example, the first service is a QoS service. The first level of the first service is QoS level 3, and the resource corresponding to QoS level 3 is QoS flow #1 of PDU session #1. The second level of the first service is QoS level 4. In this way, after receiving the first request, the authorization for QoS level 3 for the first user is revoked, and QoS flow #1 in PDU session #1 (corresponding level QoS level 3) is updated to QoS flow #2 in PDU session #1 (corresponding QoS level 4). The network side can provide QoS service to the first user through QoS flow #2 in PDU session #1, thereby avoiding interruption of QoS service for the first user and preventing the first user from being denied service.

[0119] pass Figure 3 In the method shown, after receiving a first request for requesting to revoke authorization of a first level of a first service for a first user, the first device may determine at least one level of the first service. The resource corresponding to the second level in the at least one level is the first resource used to provide the first service to the first user. In this way, after revoking authorization of the first level of the first service for the first user, the network side can still provide the first service to the first user through the first resource, thereby avoiding interruption of the first service for the first user and avoiding denial of service to the first user.

[0120] In S302, the first device may determine at least one level of the first service in a variety of ways, for example, way a1, way a2, or way a3.

[0121] Mode a1: The valid authorization for the first service of the first user includes authorization of at least two levels of the first service, the at least two levels including the first level. The first device may determine one or more levels of the at least two levels except the first level as at least one level.

[0122] In the present application, the valid authorization for the first service of the first user refers to: before receiving the first request, the authorization for the first service of the first user is still valid and has not been revoked. For example (hereinafter referred to as Example 2), the authorization for the first service of the first user includes the authorization indicated by token #1 to token #3. Among them, token #1 includes: scope:{QoS:level=3}, timeout period:{December 2, 23}, which means that token #1 is the authorization information for QoS level 3 of the QoS service authorized for the first user, and the validity period is December 1, 2023. Token #2 includes: scope:{QoS:level=4}, timeout period:{May 31, 23}, which means that token #2 is the authorization information for QoS level 4 of the QoS service authorized for the first user, and the validity period is May 30, 2023. Token #3 includes: scope:{QoS:level=2}, timeout:{September 9, 23}, which means that Token #3 is the authorization information for QoS level 2 of the QoS service authorized for the first user, and is valid until September 8, 2023. If the first device receives the first request on July 22, 2023, the valid authorization for the first service of the first user includes the authorization indicated by Token #1 and Token #3, that is, the authorization for QoS level 3 and QoS level 2 of the QoS service authorized for the first user. At this time, the above-mentioned at least two levels include QoS level 3 and QoS level 2.

[0123] Optionally, in method a1, the first device may determine at least one level of the first service through the following steps A1 to A3.

[0124] A1: The first device determines the first user according to the first request.

[0125] In some examples, the first request includes the indication information of the first user. The specific content of the indication information of the first user can refer to the description of the indication information of the first user in S301, which will not be repeated here. In this way, the first device can determine the first user according to the indication information of the first user.

[0126] In some other examples, the first request includes indication information of the first authorization information. The first device determines the first authorization information based on the indication information of the first authorization information. The determination method can refer to S301 and will not be repeated here. Then, the first device can determine the first user based on the indication information of the first user in the first authorization information. For example, the first authorization information is token #1, and the indication information of the first user is user ID #1 in the declaration of token #1. The first device can determine that the first user is the user corresponding to user ID #1.

[0127] A2: The first device determines the first service according to the first request.

[0128] In some examples, the first request includes indication information of the first service. The specific content of the indication information of the first service can refer to the description of the indication information of the first service in S301, which will not be repeated here. In this way, the first device can determine the first service according to the indication information of the first service.

[0129] In some other examples, the first request includes indication information of the first authorization information. The first device determines the first authorization information based on the indication information of the first authorization information. The determination method can refer to S301 and will not be repeated here. Then, the first device can determine the first service based on the indication information of the first service in the first authorization information. For example, the first authorization information is token #1, and the indication information of the first service is API service ID #1 in the declaration of token #1. The first device can determine that the first service is the service corresponding to API service ID #1.

[0130] This application does not limit the execution order of steps A1 and A2.

[0131] A3: The first device determines at least one level of the first service for the first user according to the first user and the first service.

[0132] Optionally, step A3 includes steps A3-1 to A3-2:

[0133] A3-1: The first device determines at least one authorization information according to the first user and the first service.

[0134] Each of the at least one authorization information may include indication information of the first user and indication information of the first service, and each of the at least one authorization information is authorization information for authorizing one or more levels of the first service to the first user. For example, the first user is the user corresponding to user ID#1, and the first service is the service corresponding to API service ID#1. The first device may select M tokens, each of the M tokens includes user ID#1 and API service ID#1, and each of the M tokens is a token for authorizing one or more levels of the first service to the first user, and M is a positive integer. In this case, the first device may determine the M tokens as at least one authorization information.

[0135] Optionally, the at least one authorization information is authorization information corresponding to a valid authorization for the first service of the first user. For example, the first user is the user corresponding to user ID#1, and the first service is the service corresponding to API service ID#1. The first device may select M tokens, each of the M tokens includes user ID#1 and API service ID#1, and each of the M tokens is a token that authorizes the first user to use the first service at one or more levels. If the M tokens are tokens #1 to #3 in Example 2, and the time when the first device receives the first request is July 22, 2023, the first device may determine that the at least one authorization information includes token #1 and token #3.

[0136] A3-2: The first device determines at least one level of the first service based on at least one authorization information.

[0137] The at least one level may be: a union of the levels of the first service authorized to the first user indicated by at least one authorization information and a difference between the first level. For example, the at least one authorization information includes token #1 and token #3 in Example 2, token #1 is authorization information for QoS level 3 of the QoS service authorized to the first user, and token #3 is authorization information for QoS level 2 of the QoS service authorized to the first user. If the first level is QoS level 3, the first device may determine that at least one level of the first service includes QoS level 2.

[0138] Optionally, the first device may first determine the difference between the union of at least one authorization information and the first authorization information to obtain a first set of authorization information, and then determine the at least one level based on the first set. The specific content of the first authorization information can refer to the description of the first authorization information in S301, which will not be repeated here. For example, the at least one authorization information includes token #1 and token #3 in Example 2, and the first authorization information is token #1. In this case, the union of at least one authorization information is {token #1, token #3}; the difference between the union of at least one authorization information and the first authorization information is {token #3}, and the difference is the first set. Token #3 is the authorization information for QoS level 2 of the QoS service authorized for the first user. Therefore, the first device can determine that at least one level of the first service includes QoS level 2.

[0139] Through the manner a1, the first device can quickly determine at least one level of the first service according to the valid authorization of the first service for the first user.

[0140] As mentioned above, the at least one level may include the second level. There may be multiple ways to determine the second level, for example, way b1 or way b2.

[0141] Mode b1: The first device sends information indicating at least one level; accordingly, the third device receives the information indicating at least one level, so that the third device can select the second level from the at least one level.

[0142] Optionally, the first device may be a CCF, and the third device may be an AEF.

[0143] Exemplarily, the information for indicating at least one level includes at least one of the following:

[0144] 1. At least one level of indication information: In some possible ways, the level of the first service is QoS level, and the at least one level of indication information may be the value of QoS level. For example, when at least one level includes QoS level 2, the at least one level of indication information includes 2. In some other possible ways, the level of the first service is 5QI value or QFI value, and the at least one level of indication information may be 5QI or QFI value. For example, when at least one level includes 5QI=3 (or QFI=3), the at least one level of indication information includes 3.

[0145] 2. Information corresponding to at least one level: Exemplarily, the level of the first service is 5QI value, and the information corresponding to at least one level may be a value corresponding to the 5QI value. For example, when at least one level includes 5QI=6, and 5QI=6 corresponds to indication information 3, the indication information of at least one level may include 3. In this way, the information transmitted between the communication devices is not 5QI value, and the second device does not need to know the 5QI value actually used in the network, thereby avoiding the leakage of 5QI value information.

[0146] The following describes how the third means selects the second level from the at least one level.

[0147] In some possible manners, the at least one level includes one level, and the one level is the second level. For example, the at least one level includes QoS level 2, and the second level is QoS level 2.

[0148] In some other possible ways, the valid authorization of the first service for the first user includes authorization of at least two levels of the first service, and the at least one level includes N levels other than the first level in the at least two levels, where N is an integer greater than or equal to 2. That is, the at least one level includes two or more levels. The third device may select a second level from the N levels according to a first rule, and the first rule is a rule for selecting the second level from the N levels.

[0149] Exemplarily, the first rule includes at least one of the following:

[0150] Rule 1: The second level is the highest quality level that the network where the first device is located can meet among the N levels: Rule 1 can also be called a best effort rule. For example, the N levels include QoS level 3 and QoS level 1, and the third device can first determine whether the network can meet QoS level 3. If the network can meet QoS level 3, the third device can determine that the second level is QoS level 3; if the network cannot meet QoS level 3, the third device can determine that the second level is QoS level 1.

[0151] Rule 2: The second level is the latest authorized level among the N levels: For example, the N levels include QoS level 3 and QoS level 1. The issuance time of the token corresponding to QoS level 3 is later than the issuance time of the token corresponding to QoS level 1. In other words, the authorization time of QoS level 3 is later than the authorization time of QoS level 1. The third device may determine that the second level is QoS level 3.

[0152] Rule 3: The second level is any one of N levels: for example, the N levels include QoS level 3 and QoS level 1. The third device may randomly select one level from QoS level 3 and QoS level 1 as the second level.

[0153] The third device may determine the first rule in various ways, for example, way c1 or way c2.

[0154] Mode c1: The first device sends first indication information, wherein the first indication information is used to indicate the first rule. Correspondingly, the third device receives the first indication information. In this way, the third device can determine the first rule according to the first indication information.

[0155] The first indication information may directly indicate the first rule. For example, the first indication information includes the first rule. The first indication information may also indirectly indicate the first rule, for example, the first indication information corresponds to the first rule.

[0156] It should be understood that the information for indicating at least one level and the first indication information may be carried in the same message (eg, a revocation request) or in different messages.

[0157] Through manner c1, the third device can quickly and accurately determine the first rule according to the first indication information.

[0158] Mode c2: The first rule is preset. For example, the first rule is specified by a protocol. In this way, the third device can obtain the preset first rule.

[0159] In some possible ways, in way b1, after the second level is selected, the third device may trigger the establishment of a first resource corresponding to the second level. The third device is, for example, AEF. After selecting the second level, AEF may interact with the 3GPP core network to update the resources. For example, AEF may negotiate with network elements such as PCF to establish or update a PDU session or QoS flow corresponding to the second level. The present application does not limit the process of establishing the first resource corresponding to the second level. For another example, for QoS service API, AEF may notify network elements such as PCF and / or SMF to modify the corresponding PDU session according to the selected QoS level. Among them, the selected QoS level may be the second level selected after revoking the authorization of the first QoS level.

[0160] Through this mode b1, the first device can send information indicating at least one level related to the first service, so that the third device can select the second level from the at least one level. In this way, after revoking the authorization of the first level of the first service, the network can provide the first service to the first user through the first resource corresponding to the second level of the first service, avoiding the interruption of the first service of the first user.

[0161] Furthermore, in this manner, the second level can be determined by the third device, and the first device does not need to determine the second level, thereby reducing the amount of calculation of the first device and saving the computing resources of the first device.

[0162] Mode b2: The first device selects the second level from at least one level.

[0163] For the specific content of the first device selecting the second level from at least one level, please refer to the description of "the third device selecting the second level from the at least one level" in mode b1, except that the third device is replaced by the first device, and the repeated parts are not repeated. When the first device selects the second level from the N levels according to the first rule, the first rule can be pre-set or obtained by the first device from other devices.

[0164] In some possible ways, after selecting the second level, the first device may trigger the establishment of the first resource corresponding to the second level. The first device is, for example, AEF. After selecting the second level, AEF may interact with the 3GPP core network to update the resource. For the specific content of AEF interacting with the 3GPP core network to update the resource, please refer to the description of AEF interacting with the 3GPP core network to update the resource in way b1, which will not be repeated here.

[0165] In some other possible ways, after selecting the second level, the first device may send information indicating the second level. Correspondingly, the third device may receive information indicating the second level. In this way, the third device may determine the second level based on the information indicating the second level. Optionally, the first device may be CCF and the third device may be AEF. Exemplarily, the information indicating the second level includes at least one of the following: indication information of the second level; or, information corresponding to the second level. For the specific content of the information indicating the second level, refer to the description of "information indicating at least one level" in method b1, except that at least one level is replaced by the second level, which will not be repeated here.

[0166] Optionally, after determining the second level, the third device may trigger the establishment of the first resource corresponding to the second level. The third device is, for example, AEF. After determining the second level, AEF may interact with the 3GPP core network to update the resource. For the specific content of AEF interacting with the 3GPP core network to update the resource, refer to the description of AEF interacting with the 3GPP core network to update the resource in mode b1, which will not be repeated here.

[0167] Through this method b2, the first device can select the second level from at least one level. In this way, after revoking the authorization of the first level of the first service, the network can provide the first service to the first user through the first resource corresponding to the second level of the first service, avoiding interruption of the first service of the first user.

[0168] Furthermore, in this manner, the first device determines at least one level and the second level. Thus, the first device can transmit information indicating the second level without transmitting information indicating the level other than the second level in at least one level, thereby saving transmission resources and reducing signaling overhead.

[0169] Mode a2: The valid authorization for the first service of the first user includes authorization for one level of the first service, the one level being the first level. The first device may determine the set second level as at least one level of the first service.

[0170] Among them, for the specific content of the valid authorization for the first service of the first user, please refer to the description of "valid authorization for the first service of the first user" in method a1, which will not be repeated here. The second level of this setting may be a default level. For example, the valid authorization for the first service of the first user includes the authorization indicated by token #1, and token #1 includes: scope:{QoS:level=3}, timeout period: {December 2, 2023}. The set second level is QoS level 1. If the first request is used to request the revocation of QoS level 3 authorization for the QoS service for the first user, the first device may determine QoS level 1 as at least one level of the first service.

[0171] In some possible ways, after the set second level is determined as at least one level, the first device may trigger the establishment of a first resource corresponding to the second level. The first device is, for example, an AEF. After the set second level is determined as at least one level, the AEF may interact with the 3GPP core network to update the resource. For the specific content of the AEF interacting with the 3GPP core network to update the resource, reference may be made to the description of the AEF interacting with the 3GPP core network to update the resource in way b1, which will not be repeated here.

[0172] In some other possible ways, after determining the set second level as at least one level, the first device may send information indicating the second level. Correspondingly, the third device may receive the information indicating the second level. In this way, the third device may determine the second level according to the information indicating the second level. The specific content of this method can refer to the description of "the first device may send information indicating the second level" in method b2, which will not be repeated here.

[0173] By means of mode a2, the first device can determine the set second level as at least one level. In this way, after revoking the authorization of the first level of the first service for the first user, the network can provide the first service to the first user through the first resource corresponding to the second level, thereby avoiding interruption of the first service of the first user.

[0174] Mode a3: The second device sends first information to the first device, where the first information is used to indicate the second level. The first information may be carried in the first request or in other messages. The first device determines the second level as at least one level.

[0175] Optionally, the first information is indication information of the second level, or the first information is information corresponding to the second level; wherein the effective authorization of the first service for the first user includes the second level authorization of the first service. For the specific content of the effective authorization of the first service for the first user, refer to the description of "effective authorization of the first service for the first user" in method a1.

[0176] In some examples, the first information is a value of the second level. For example, the first information is 3, indicating that the second level is QoS level 3.

[0177] In some other examples, the first information may be the second authorization information or the indication information of the second authorization information. The second authorization information is the authorization information of the second level for authorizing the first user to use the first service. The indication information of the second authorization information is, for example, the ID of the second authorization information. For example, if the first information is token #3 or the indication information of token #3, and token #3 is the authorization information of QoS level 2 for authorizing the first user to use the QoS service, then the second level is QoS level 2.

[0178] In some other examples, the first information is a "default" value. The correspondence between the default value and the second level may be preconfigured. For example, if the default value corresponds to QoS level 1, the second level is QoS level 1. For another example, if the default value corresponds to 5QI 1, the second level is 5QI 1.

[0179] In some possible ways, after the second level is determined to be at least one level, the first device may trigger the establishment of a first resource corresponding to the second level. The first device is, for example, an AEF. After the second level is determined to be at least one level, the AEF may interact with the 3GPP core network to update the resource. For the specific content of the AEF interacting with the 3GPP core network to update the resource, reference may be made to the description of the AEF interacting with the 3GPP core network to update the resource in way b1, which will not be repeated here.

[0180] In some other possible ways, after determining the set second level as at least one level, the first device may send information indicating the second level. Correspondingly, the third device may receive the information indicating the second level. In this way, the third device may determine the second level according to the information indicating the second level. The specific content of this method can refer to the description of "the first device may send information indicating the second level" in method b2, which will not be repeated here.

[0181] Through the method a3, the second device can send information indicating the second level to the first device, so that the first device does not need to determine the second level through calculation, thereby reducing the amount of calculation of the first device and saving the calculation resources of the first device. In addition, after revoking the authorization of the first level of the first service for the first user, the network can provide the first service to the first user through the first resource corresponding to the second level, thereby avoiding the interruption of the first service of the first user.

[0182] In some possible ways, in the above-mentioned way a1, way a2 or way a3, the first device may also send at least one of the following: indication information of the first user or indication information of the first service. Correspondingly, the third device may receive at least one of the following: indication information of the first user or indication information of the first service. In this way, the third device may determine the first service for the first user and trigger the establishment of the first resource corresponding to the second level. Among them, the specific contents of the indication information of the first user and the indication information of the first service can refer to the description of the indication information of the first user and the indication information of the first service in S301 respectively, and will not be repeated here.

[0183] The present application embodiment provides another communication method. Figure 3 One possible example of the method shown is shown below. Figure 4 The flowchart shown takes the first device as CCF, the second device as API caller, and the third device as AEF as an example to specifically illustrate the process of the method.

[0184] S401: The API caller obtains a token #a1 from the CCF, and the token #a1 is a token for the first user. The API caller provides the token #a1 to the AEF, and the AEF, PCF and SMF negotiate to allocate resources to the terminal corresponding to the first user.

[0185] Optionally, the API caller may be a device that can perform at least one of the following operations on behalf of the first user: initiate a request to call a service API, obtain service API information, call a service API, or obtain a corresponding service. Before performing the above operations, the API caller may first obtain authorization from the first user.

[0186] Among them, the service #a1 corresponding to the token #a1 can be a first type of service or a second type of service. The first type of service can also be called a switch type of service, and the network side can authorize or not authorize the first type of service to the first user. For example, the first type of service includes providing the user's location information, and the network side can authorize or not authorize the first user to provide the user's location information. The second type of service can also be called a multi-level service, and the network side can authorize one or more levels of the second type of service to the first user. For example, the second type of service includes a QoS service, and the network side can authorize the first level of the QoS service to the first user.

[0187] When the service #a1 corresponding to the token #a1 is a first type of service, the token #a1 may be a token that authorizes the first user to use the service #a1. When the service #a1 corresponding to the token #a1 is a second type of service, the token #a1 may be a first level token that authorizes the first user to use the service #a1.

[0188] S402: The API caller sends a revocation request #1 to the CCF, where the revocation request #1 is used to request the revocation of token #a1.

[0189] There may be multiple triggering conditions for the API caller to send the revocation request #1. For example, when the terminal detects at least one of the following operations of the first user, the API caller may send the revocation request #1: log out, revoke or modify the API service. This application does not limit the triggering conditions for the API caller to send the revocation request #1.

[0190] The specific content of the cancellation request #1 can be found in the description of the first request in S301, which will not be repeated here.

[0191] Optionally, the revocation request #1 also includes indication information #1, which is used to indicate whether the type of service #a1 corresponding to the token #a1 is the first type or the second type. For example, when the value of the indication information #1 is the first value (for example, 0), the type of service #a1 corresponding to the token #a1 is the first type; when the value of the indication information #1 is the second value (for example, 1), the type of service #a1 corresponding to the token #a1 is the second type.

[0192] In some possible ways, after receiving the revocation request #a1, the CCF may revoke the token #a1. For example, when the token #a1 is a token for authorizing the service #a1 for the first user, the CCF may revoke the authorization of the service #a1 for the first user. For another example, when the token #a1 is a first-level token for authorizing the service #a1 for the first user, the CCF may revoke the first-level authorization of the service #a1 for the first user.

[0193] S403: CCF determines whether the type of service #a1 corresponding to token #a1 is the first type or the second type. When the type of service #a1 is the first type, Figure 4 The method further includes S404. When the type of service #a1 is the second type, Figure 4 The method shown also includes S405 to S413.

[0194] In some examples, CCF may determine whether the type of service #a1 is the first type or the second type according to the API service ID in the declaration of token #a1. For example, when the API service ID indicates that service #a1 is to provide user location information, CCF may determine that the type of service #a1 is the first type. For another example, when the API service ID indicates that service #a1 is a QoS service, CCF may determine that the type of service #a1 is the second type.

[0195] In other examples, the CCF may determine whether the type of service #a1 is the first type or the second type according to the indication information #1 in S402. The correspondence between the indication information #1 and the type of service #a1 can refer to the description in S402, which will not be repeated here.

[0196] S403 is an optional step. For example, in some possible implementations, regardless of whether the type of service #a1 is the first type or the second type, S405 to S413 can be performed on token #a1. In other possible implementations, the CCF only supports the second type of service, so that after S402, S405 to S413 can be performed.

[0197] S404: CCF sends a cancellation request #a2 to AEF.

[0198] The AEF may be the AEF corresponding to the AEF ID in the declaration of token #a1. It should be understood that the AEF ID in the declaration of token #a1 may correspond to one or more AEFs, and each AEF may be Figure 4 Processing is performed using the method shown.

[0199] In some examples, the revocation request #a2 may include the token #a1 or indication information of the token #a1 (eg, token ID). Thus, after receiving the revocation request #a2, the AEF may determine that the revocation request #a2 is used to request the release of the resource corresponding to the token #a1.

[0200] In some other examples, the revocation request #a2 may include: the indication information of the first user and the indication information of the service #a1. Thus, after receiving the revocation request #a2, the AEF may determine the token #a1 according to the indication information of the first user and the indication information of the service #a1, thereby determining that the revocation request #a2 is used to request the release of the resources corresponding to the token #a1. The specific contents of the indication information of the first user and the indication information of the service #a1 may refer to the description of the indication information of the first user and the indication information of the first service in S301, respectively, and will not be repeated here.

[0201] Optionally, after receiving the revocation request #a2, the AEF may trigger the release of resources corresponding to the token #a1, for example, starting the process of canceling the first user's subscription service #a1. This application does not limit the specific process of releasing the resources corresponding to the token #a1, and starting the specific process of canceling the first user's subscription service #a1.

[0202] S405: CCF determines at least one level of service #a1 corresponding to token #a1.

[0203] The specific content of S405 can refer to method a1 and method a2, except that service #a1 is replaced by the first service, which will not be repeated here.

[0204] S406: The CCF sends a service update request to the AEF.

[0205] In some possible ways, the service update request may include information for indicating at least one level. The specific content of the information for indicating at least one level can refer to the description of the information for indicating at least one level in way b1, which will not be repeated here.

[0206] Optionally, the service update request also includes the indication information of the first user and / or the indication information of service #a1. The specific contents of the indication information of the first user and the indication information of service #a1 can refer to the description of the indication information of the first user and the indication information of the first service in S301, and will not be repeated here.

[0207] In some examples, the valid authorization for the service #a1 of the first user includes authorization for at least two levels of service #a1, and the at least one level includes N levels of the at least two levels except the first level, where N is an integer greater than or equal to 2. The service update request also includes: first indication information, and the first indication information is used to indicate a first rule. The first rule is a rule for selecting the second level from the N levels. The specific content of the first rule can refer to the description of the first rule in method b1, and will not be repeated here.

[0208] After receiving information indicating at least one level, AEF may select a second level from the at least one level. The selection method may refer to the description of "a third device selects a second level from the at least one level" in method b1, which will not be repeated here.

[0209] In some other possible ways, the service update request may include information for indicating the second level. The second level may be selected by the CCF from at least one of the above levels. The selection method may refer to method b2, which will not be described in detail here. The specific content of the information for indicating the second level may refer to the description of the information for indicating the second level in method b2, which will not be described in detail here.

[0210] S407: AEF sends a policy update request #1 to PCF. The policy update request #1 may be used to request execution of the following policy: modify the resources corresponding to service #a1 to resources corresponding to the second level.

[0211] Optionally, the policy update request #1 includes at least one of the following: indication information of the first user, indication information of service #a1, or information indicating the second level. Exemplarily, in the policy update request #1, the indication information of the first user is the indication information of user #1, the indication information of service #a1 is used to indicate that service #a1 is a QoS service, and the information indicating the second level indicates that the second level is QoS level 3. In this way, the PCF can determine to establish resources corresponding to QoS level 3 of the QoS service for user #1.

[0212] In the present application, the information used to indicate the second level in the policy update request #1 may be the same as or different from the information used to indicate the second level obtained by the AEF from the CCF.

[0213] In some examples, the information indicating the second level obtained by the AEF from the CCF is a value of QoS level 3. In the policy update request #1, the information indicating the second level is a value of QoS level 3. According to Table 1 above, the PCF can map QoS level 3 to 5QI 6. In this way, the PCF can determine to establish resources corresponding to 5QI 6 of the QoS service.

[0214] In other examples, the information indicating the second level received by the AEF from the CCF may be information corresponding to the value of 5QI, and the information indicating the second level in the policy update request #1 may be the value of 5QI. For example, the information indicating the second level obtained by the AEF from the CCF is the value of QoS level 3. According to Table 1 above, the AEF may map QoS level 3 to 5QI 6. The information indicating the second level in the policy update request #1 may be the value of 5QI 6.

[0215] S408: PCF sends a policy update request #2 to SMF, where the policy update request #2 may be used to request execution of the following policy: modifying the resources corresponding to service #a1 to resources corresponding to the second level.

[0216] Optionally, the policy update request #2 may include at least one of the following: indication information of the first user, indication information of the service #a1, or information for indicating the second level.

[0217] In some possible ways, the information used to indicate the second level in the policy update request #1 and the policy update request #2 may be the same or different. For example, the information used to indicate the second level in the policy update request #1 and the policy update request #2 is QoS level 3. For another example, in the policy update request #1, the information used to indicate the second level is QoS level 3; in the policy update request #2, the information used to indicate the second level is the value of 5QI 6 corresponding to QoS level 3.

[0218] S409: SMF initiates a resource modification process to modify the resources corresponding to service #a1 to the resources corresponding to the second level.

[0219] Exemplarily, the resource modification process is a PDU session establishment or a PDU session modification process; in the resource modification process, the QoS is modified to the second level 5QI 6.

[0220] In a possible implementation, the SMF initiates a PDU session establishment process, sets the QoS of the PDU session or the QoS flow in the PDU session corresponding to the service #a1 of the first user to the second level, and initiates a release process for the first-level PDU session or the QoS flow of the PDU session for service #a1, and releases the PDU session or QoS flow corresponding to the first level. For example, the first level of the service #a1 of the first user is 5QI 3, and 5QI3 corresponds to PDU session #1. The second level of the service #a1 of the first user is 5QI 6. The SMF initiates a PDU session establishment process to establish PDU session #2, and the QoS of PDU session #2 is 5QI 6. The first user can obtain service #a1 through PDU session #2. The SMF can also initiate a PDU session release process to release PDU session #1. For another example, the first level of the service #a1 of the first user is 5QI 3, and 5QI 3 corresponds to QoS flow #1 of PDU session #1. The second level of the service #a1 of the first user is 5QI 6. SMF initiates the PDU session establishment process to establish QoS flow #2 in PDU session #2, and the QoS of QoS flow #2 is 5QI 6. The first user can obtain service #a1 through PDU session #2. SMF can also initiate the PDU session release process to release QoS flow #1 in PDU session #1.

[0221] In another possible implementation, the SMF initiates a PDU session modification process to modify the QoS of the PDU session or the QoS flow of the PDU session corresponding to the first user's service #a1 to the second level. For example, the first level of the first user's service #a1 is 5QI 3, and 5QI3 corresponds to PDU session #1. The second level of the first user's service #a1 is 5QI 6. The SMF initiates a PDU session modification process to modify the QoS of PDU session #1 to 5QI 6. The first user can obtain service #a1 through PDU session #1. For another example, the first level of the first user's service #a1 is 5QI 3, and 5QI 3 corresponds to QoS flow #1 of PDU session #1. The second level of the first user's service #a1 is 5QI 6. The SMF initiates a PDU session modification process to modify the QoS of QoS flow #1 to 5QI6. The first user can obtain service #a1 through QoS flow #1.

[0222] S410: SMF sends a policy update response #2 to PCF.

[0223] Among them, the policy update response #2 is a response message of the policy update request #2, which can be used to indicate that the policy requested by the policy update request #2 has been executed, that is, the resources corresponding to the service #a1 have been modified to the resources corresponding to the second level.

[0224] S411: PCF sends a policy update response #1 to AEF.

[0225] Among them, the policy update response #1 is a response message of the policy update request #1, which can be used to indicate that the policy requested by the policy update request #1 has been executed, that is, the resources corresponding to the service #a1 have been modified to the resources corresponding to the second level.

[0226] S412: AEF sends a service update response to CCF.

[0227] The service update response is a response message to the service update request, which can be used to indicate that the resources corresponding to service #a1 have been modified to the resources corresponding to the second level. Optionally, the service update response includes: indication information of service #a1. In this way, after receiving the service update response, the CCF can determine that the resources corresponding to service #a1 have been modified to the resources corresponding to the second level.

[0228] S413: CCF sends a revocation response #1 to the API caller, where the revocation response #1 is used to indicate that the token #a1 has been revoked.

[0229] S401 to S413 are optional steps.

[0230] exist Figure 4 In the method shown, for token #a1, AEF may receive revocation request #a2 in S404, or may receive service update request in S406. The operation after AEF receives revocation request #a2 is different from the operation after AEF receives service update request. Therefore, AEF needs to determine whether the received message is revocation request #a2 or service update request. In some examples, revocation request #a2 and service update request have different message types, and AEF can determine whether the received message is revocation request #a2 or service update request based on the type of the received message. In other examples, revocation request #a2 may include indication information #2, and service update request may include indication information #3, and indication information #2 and indication information #3 are different. If the message received by AEF includes indication information #2, AEF can determine that the received message is revocation request #a2. If the message received by AEF includes indication information #3, AEF can determine that the received message is service update request. The present application does not limit the specific forms of indication information #2 and indication information #3.

[0231] pass Figure 4In the method shown, when service #a1 is a service of multiple levels, after receiving a request for requesting to revoke the authorization of the first level of service #a1 for the first user, the CCF can determine at least one level of service #a1. The resources corresponding to the second level in the at least one level are the resources used to provide service #a1 to the first user. In this way, after revoking the authorization of the first level of service #a1 for the first user, the network side can still provide service #a1 to the first user through the resources corresponding to the second level, thereby avoiding interruption of service #a1 for the first user and avoiding denial of service to the first user.

[0232] The present application embodiment provides another communication method, which is Figure 3 Another possible example of the method shown is shown below. Figure 5 The flowchart shown takes the first device as AEF and the second device as API caller as an example to specifically illustrate the process of the method.

[0233] S501: The API caller obtains a token #a1 from the CCF, and the token #a1 is a token for the first user. The API caller provides the token #a1 to the AEF, and the AEF, PCF and SMF negotiate to allocate resources to the terminal corresponding to the first user.

[0234] S502: The API caller sends a revocation request #1 to the CCF, where the revocation request #1 is used to request the revocation of token #a1.

[0235] The specific contents of S501 to S502 may refer to S401 to S402 and will not be repeated here.

[0236] In some possible ways, after receiving the revocation request #1, CCF may determine the service indication information (e.g., API service ID) of service #a1 corresponding to token #a1 and the indication information of the first user (e.g., the ID of the first user or the ID of the terminal corresponding to the first user). In some examples, CCF may determine the service indication information of service #a1 based on the service indication information declaration of token #a1. In other examples, CCF may determine the service indication information of service #a1 based on the scope declaration of token #a1, which scope declaration includes the service indication information of service #a1. This application is not limited to this.

[0237] S503: CCF sends a cancellation request #3 to AEF.

[0238] In some possible ways, the revocation request #3 is used to request the revocation of the token #a1. The specific content of the revocation request #3 can refer to the revocation request #1, which will not be repeated here.

[0239] In some other possible ways, the revocation request #3 is used to request the revocation of the service authorized by the token #a1. The revocation request #3 may include the service indication information of the service #a1 and the indication information of the first user. The specific contents of the service indication information of the service #a1 and the indication information of the first user can be found in the description of S502, which will not be repeated here.

[0240] S504: AEF determines the second level of service #a1.

[0241] Among them, service #a1 corresponds to token #a1 or API service ID. Since service #a1 corresponding to API service ID actually corresponds to token #a1, for the sake of simplicity, the following description does not make a distinction between them, and service #a1 is generally referred to as service #a1 corresponding to token #a1.

[0242] AEF determines at least one level of service #a1 corresponding to token #a1, and selects a second level from the at least one level. The specific content of AEF determining the at least one level can refer to method a1 and method a2, except that service #a1 is replaced by the first service; the specific content of AEF selecting the second level from the at least one level can refer to the description of "the third device selects the second level from the at least one level" in method b1, which will not be repeated here.

[0243] Optionally, before determining the at least one level, the AEF may first determine that the type of service #a1 corresponding to the token #a1 is the second type. The specific content of the AEF determining that the type of service #a1 is the second type can be referred to S403, which will not be repeated here.

[0244] S505: AEF sends a policy update request #1 to PCF. The policy update request #1 may be used to request execution of the following policy: modifying resources corresponding to service #a1 to resources corresponding to the second level.

[0245] S506: PCF sends a policy update request #2 to SMF. The policy update request #2 may be used to request execution of the following policy: modify the resources corresponding to service #a1 to resources corresponding to the second level.

[0246] S507: SMF initiates a resource modification process to modify the resources corresponding to service #a1 to the resources corresponding to the second level.

[0247] S508: SMF sends a policy update response #2 to PCF.

[0248] S509: PCF sends a policy update response #1 to AEF.

[0249] S508 to S509 are optional steps.

[0250] The specific contents of S505 to S509 can be referred to S407 to S411 and will not be repeated here.

[0251] S510: AEF sends a revocation response #3 to CCF.

[0252] The revocation response #3 is a response message to the revocation request #3, which can be used to indicate that the resources corresponding to the service #a1 have been modified to the resources corresponding to the second level. Optionally, the revocation response #3 includes: indication information of the service #a1. In this way, after receiving the revocation response #3, the CCF can determine that the resources corresponding to the service #a1 have been modified to the resources corresponding to the second level.

[0253] S511: CCF sends a revocation response #1 to the API caller, where the revocation response #1 is used to indicate that the token #a1 has been revoked.

[0254] Figure 5 In the method shown, S502 to S503 and S510 to S511 are optional steps. For example, S502 and S503 can be replaced by: the API caller directly sends a revocation request #4 to the AEF, and the revocation request #4 is used to request the revocation of token #a1. The specific content of the revocation request #4 can refer to the revocation request #1, which will not be repeated here. S510 and S511 can be replaced by: the AEF directly sends a revocation response #4 to the API caller. The specific content of the revocation response #4 can refer to the revocation response #1, which will not be repeated here. In this way, there is no need for the CCF to forward information between the API caller and the AEF, thereby saving the communication resources of the CCF and reducing the energy consumption of the CCF.

[0255] pass Figure 5 In the method shown, when service #a1 is a service of multiple levels, after receiving a request for requesting to revoke the authorization of the first level of service #a1 for the first user, the AEF can determine the second level of service #a1. The resources corresponding to the second level are the resources used to provide service #a1 to the first user. In this way, after revoking the authorization of the first level of service #a1 for the first user, the network side can still provide service #a1 to the first user through the resources corresponding to the second level, thereby avoiding interruption of service #a1 for the first user and avoiding denial of service to the first user.

[0256] The present application embodiment provides another communication method. Figure 3 Another possible example of the method shown is shown below. Figure 6 The flowchart shown in the figure takes the first device as CCF, the second device as API caller, and the third device as AEF as an example to specifically illustrate the process of the method. Figure 4 Compared with the method shown in Figure 6In the illustrated method, the second level is indicated by the API caller rather than selected by the CCF or AEF from at least one level.

[0257] S601: The API caller obtains a token #a1 from the CCF, and the token #a1 is a token for the first user. The API caller provides the token #a1 to the AEF, and the AEF, PCF and SMF negotiate to allocate resources to the terminal corresponding to the first user.

[0258] The specific content of S601 can refer to S401, and the repeated parts are not repeated. When the service #a1 corresponding to the token #a1 is the second type of service, the token #a1 can be a first-level token that authorizes the first user to use the service #a1.

[0259] S602: The API caller sends a revocation request #1 to the CCF, where the revocation request #1 is used to request the revocation of the token #a1. The revocation request #1 includes indication information #4.

[0260] The specific content of S602 can refer to S402, and the repeated parts will not be repeated.

[0261] In some examples, indication information #4 may be first information for indicating the second level. The specific content of the first information may refer to the description of the first information in method a3, which will not be repeated here. When indication information #4 is the first information, CCF may perform the operation in S603.

[0262] In some other examples, indication information #4 may include an invalid (null) value to indicate that after revoking token #a1, authorization for service #a1 corresponding to token #a1 is revoked for the first user. When indication information #4 includes an invalid value, CCF revokes authorization for service #a1 for the first user.

[0263] S603: The CCF determines the second level of the service #a1 corresponding to the token #a1 based on the first information.

[0264] Optionally, before determining the second level, the CCF may determine that the type of service #a1 is the second type. The specific content of the CCF determining that the type of service #a1 is the second type can be referred to S403, which will not be repeated here.

[0265] S604: The CCF sends a service update request to the AEF.

[0266] S605: AEF sends a policy update request #1 to PCF. The policy update request #1 may be used to request execution of the following policy: modifying resources corresponding to service #a1 to resources corresponding to the second level.

[0267] S606: PCF sends a policy update request #2 to SMF. The policy update request #2 may be used to request execution of the following policy: modify the resources corresponding to service #a1 to resources corresponding to the second level.

[0268] S607: SMF initiates a resource modification process to modify the resources corresponding to service #a1 to the resources corresponding to the second level.

[0269] S608: SMF sends a policy update response #2 to PCF.

[0270] S609: The PCF sends a policy update response #1 to the AEF.

[0271] S610: AEF sends a service update response to CCF.

[0272] S611: CCF sends a revocation response #1 to the API caller, where the revocation response #1 is used to indicate that token #a1 has been revoked.

[0273] S608 to S611 are optional steps.

[0274] The specific contents of S604 to S611 can be referred to S406 to S413 and will not be repeated here.

[0275] pass Figure 6 In the method shown, when service #a1 is a service of multiple levels, after sending a request for requesting to revoke the authorization of the first level of service #a1 for the first user, the API caller unit may also send first information indicating the second level to the CCF. In this way, after revoking the authorization of the first level of service #a1 for the first user, the network side can still provide service #a1 to the first user through the resources corresponding to the second level, thereby avoiding interruption of service #a1 for the first user and avoiding denial of service to the first user.

[0276] The present application embodiment provides another communication method. Figure 3 Another possible example of the method shown is shown below. Figure 7 The flowchart shown in FIG. 1 takes the first device as AEF and the second device as API caller as an example to specifically illustrate the process of the method. Figure 5 Compared with the method shown in Figure 7 In the illustrated method, the second level is indicated by the API caller rather than selected by the CCF or AEF from at least one level.

[0277] S701: The API caller obtains a token #a1 from the CCF, and the token #a1 is a token for the first user. The API caller provides the token #a1 to the AEF, and the AEF, PCF and SMF negotiate to allocate resources to the terminal corresponding to the first user.

[0278] S702: The API caller sends a revocation request #1 to the CCF, where the revocation request #1 is used to request the revocation of token #a1.

[0279] The specific contents of S701 to S702 can be referred to S601 to S602 and will not be repeated here.

[0280] In some possible ways, after receiving the revocation request #1, the CCF may determine the service indication information (e.g., API service ID) of the service #a1 corresponding to the token #a1 and the indication information of the first user (e.g., the ID of the first user or the ID of the terminal corresponding to the first user). The way in which the CCF determines the service indication information of the service #a1 and the indication information of the first user can be referred to S502, which will not be repeated here.

[0281] S703: CCF sends a cancellation request #3 to AEF.

[0282] In some possible ways, the revocation request #3 is used to request the revocation of the token #a1. The specific content of the revocation request #3 can refer to the revocation request #1, and the repeated parts will not be repeated.

[0283] In some other possible ways, the revocation request #3 is used to request the revocation of the service authorized by the token #a1. The revocation request #3 may include the service indication information of the service #a1 and the indication information of the first user. The specific contents of the service indication information of the service #a1 and the indication information of the first user can be found in the description of S502, which will not be repeated here.

[0284] In S703, the cancellation request #3 may include indication information #4. The following example illustrates the implementation of indication information #4.

[0285] In some examples, in the revocation request #3, the indication information #4 may be the first information for indicating the second level. The specific content of the first information may refer to the description of the first information in the method a3, which will not be repeated here. When the indication information #4 is the first information, the AEF may perform the operation in S704.

[0286] In some other examples, in the revocation request #3, the indication information #4 may include an invalid null value, which indicates that after revoking the token #a1, the authorization of the service #a1 corresponding to the token #a1 is revoked for the first user. When the indication information #4 includes an invalid value, the AEF may release the resources of the service #a1 for the first user.

[0287] S704: The AEF determines the second level of the service #a1 corresponding to the token #a1 according to the first information.

[0288] Optionally, before determining the second level, the AEF may determine that the type of service #a1 is the second type. The specific content of the AEF determining that the type of service #a1 is the second type may be referred to S403, which will not be described in detail here.

[0289] S705: AEF sends a policy update request #1 to PCF. The policy update request #1 may be used to request execution of the following policy: modifying resources corresponding to service #a1 to resources corresponding to the second level.

[0290] S706: PCF sends a policy update request #2 to SMF. The policy update request #2 may be used to request execution of the following policy: modify the resources corresponding to service #a1 to resources corresponding to the second level.

[0291] S707: SMF initiates a resource modification process to modify the resources corresponding to service #a1 to the resources corresponding to the second level.

[0292] S708: SMF sends a policy update response #2 to PCF.

[0293] S709: PCF sends a policy update response #1 to AEF.

[0294] S710: AEF sends a revocation response #3 to CCF.

[0295] S711: CCF sends a revocation response #1 to the API caller, where the revocation response #1 is used to indicate that token #a1 has been revoked.

[0296] S708 to S711 are optional steps.

[0297] The specific contents of S705 to S711 can be referred to S505 to S511 and will not be repeated here.

[0298] pass Figure 7 In the method shown, when service #a1 is a service of multiple levels, after sending a request for requesting to revoke the authorization of the first level of service #a1 for the first user, the API caller unit may also send first information indicating the second level to the AEF. In this way, after revoking the authorization of the first level of service #a1 for the first user, the network side may still provide service #a1 to the first user through resources corresponding to the second level, thereby avoiding interruption of service #a1 for the first user and preventing the first user from being denied service.

[0299] Based on the same technical concept as the above method embodiment, the embodiment of the present application is Figure 8A communication device is provided, which can be used to perform the functions of the relevant steps in the above method embodiment. The functions can be implemented by hardware, or by software or hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. The structure of the communication device is as follows Figure 8 As shown, it includes an interface unit 801 and a processing unit 802. The communication device 800 can be an AzF, CCF, AEF, an API caller, or a device including an API caller (for example, a terminal or AF), or a module applied to an AzF, CCF, AEF, an API caller, or a device including an API caller, such as a chip, a chip system, or a processor, or a logical node, a logical module, or software that can implement all or part of the functions of an AzF, CCF, AEF, an API caller, or a device including an API caller. In addition, the communication device 800 can implement the communication method provided in the above embodiments and examples of the present application. The functions of each unit in the communication device 800 are introduced below.

[0300] The interface unit 801 is used to input and / or output information. When outputting information, the interface unit 801 can output information to other devices outside the communication device 800, or can output information to other units in the communication device 800. In some embodiments, the interface unit 801 can be implemented by at least one of a physical interface, a communication module, a communication interface, and an input / output interface. In other embodiments, the interface unit 801 can be implemented by an interface circuit, for example, a mobile communication module. Among them, the mobile communication module may include one or more of at least one antenna, at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc.

[0301] The processing unit 802 can be used to support the communication device 800 to perform the processing actions in the above method embodiment. The processing unit 802 can be implemented by a processor. For example, the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor.

[0302] In one embodiment, the communication device 800 is applied to Figure 3 The first device in the embodiment of the present application is shown. The specific functions of the processing unit 802 in this implementation are introduced below.

[0303] The processing unit 802 is used to: receive a first request through the interface unit 801, the first request is used to request to revoke authorization of a first level of a first service for a first user, the first service includes multiple levels, and the multiple levels include the first level; according to the first request, determine at least one level of the first service, the at least one level includes a second level, and the resources corresponding to the second level of the first service are first resources used to provide the first service to the first user.

[0304] In some possible embodiments, the effective authorization for the first service of the first user includes at least two levels of authorization for the first service, and the at least two levels include the first level; the processing unit 802 is used to: determine one or more levels of the at least two levels except the first level as at least one level.

[0305] Optionally, the processing unit 802 is further used to: send information indicating at least one level through the interface unit 801.

[0306] In some examples, at least one level includes N levels other than the first level in at least two levels, where N is an integer greater than or equal to 2, and the processing unit 802 is also used to: send first indication information through the interface unit 801, and the first indication information is used to indicate a first rule for selecting a second level from the N levels.

[0307] In some other examples, at least one level includes N levels of at least two levels except the first level, N is an integer greater than or equal to 2, and the processing unit 802 is further used to: select the second level from the N levels according to the first rule.

[0308] Optionally, the first rule includes at least one of the following: the second level is the highest quality level that can be met by the network where the first device is located among the N levels; or the second level is the latest authorized level among the N levels.

[0309] In some other possible embodiments, the effective authorization for the first service of the first user includes one level of authorization for the first service, where the one level is a first level; and the processing unit 802 is used to determine the set second level as at least one level.

[0310] In some other possible manners, the first request further includes first information, or the processing unit 802 is further configured to: receive the first information through the interface unit 801, wherein the first information is used to indicate the second level. The processing unit 802 is further configured to: determine the second level as at least one level.

[0311] Optionally, the processing unit 802 is further used to: send information indicating the second level through the interface unit 801.

[0312] In some implementations, the processing unit 802 is further used to: send at least one of the following through the interface unit 801: indication information of the first user or indication information of the first service.

[0313] In some possible embodiments, the processing unit 802 is configured to: determine at least one level of the first service for the first user according to the indication information of the first user and the indication information of the first service.

[0314] Optionally, the processing unit 802 is used to: determine at least one authorization information based on the indication information of the first user and the indication information of the first service, each authorization information in the at least one authorization information includes the indication information of the first user and the indication information of the first service, and each authorization information in the at least one authorization information is authorization information for authorizing one or more levels of the first service to the first user; determine at least one level of the first service based on the at least one authorization information.

[0315] In another embodiment, the communication device 800 is applied to Figure 3 The second device in the embodiment of the present application is shown. The specific functions of the processing unit 802 in this implementation are introduced below.

[0316] The processing unit 802 is used to: send a first request through the interface unit 801, the first request is used to request to revoke the authorization of the first level of the first service for the first user, the first service includes multiple levels, and the multiple levels include the first level. The first request also includes first information, or the processing unit 802 is further used to: send first information through the interface unit 801; wherein the first information is used to indicate the second level, and the resource corresponding to the second level of the first service is the first resource used to provide the first service for the first user.

[0317] For a more detailed description of the processing unit 802 and the interface unit 801, please refer to Figure 3 and Figure 5 The relevant description in the method embodiment shown is directly obtained and will not be repeated here.

[0318] It should be noted that the division of modules in the above embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0319] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0320] Based on the same technical concept, the embodiments of the present application are Fig. 9 A communication device is provided as shown, which can be used to execute the relevant steps in the above method embodiments. The communication device can be an AzF, CCF, AEF, an API caller, or a device including an API caller (for example, a terminal or AF), or a module applied to an AzF, CCF, AEF, an API caller, or a device including an API caller, such as a chip, a chip system, or a processor, or a logical node, a logical module, or software that can implement all or part of the functions of an AzF, CCF, AEF, an API caller, or a device including an API caller. Furthermore, the communication device can implement the communication method provided in the above embodiments and examples of the present application, having Figure 8 The functions of the communication device shown. Fig. 9 As shown, the communication device 900 includes: a processor 902. Optionally, the communication device 900 also includes: an interface circuit 901 and a memory 903. The interface circuit 901, the processor 902 and the memory 903 are coupled to each other.

[0321] Optionally, the interface circuit 901, the processor 902 and the memory 903 are coupled to each other via a bus 904. The bus 904 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig. 9 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0322] The interface circuit 901 is used to input and / or output information. When outputting information, the interface circuit 901 can output information to other devices outside the communication device 900, or can output information to other units in the communication device 900. Exemplarily, the interface circuit 901 can be implemented by at least one of a physical interface, a communication module, a communication interface, an input / output interface, and a mobile communication module. The mobile communication module may include one or more of at least one antenna, at least one filter, a switch, a power amplifier, an LNA, etc.

[0323] The processor 902 may be used to support the communication device 900 in executing the processing actions in the above method embodiment. When the communication device 900 is used to implement the above method embodiment, the processor 902 may also be used to implement the functions of the above processing unit 802. The processor 902 may be a CPU, or other general-purpose processors, DSPs, ASICs, FPGAs, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, or any conventional processor.

[0324] In one embodiment, the communication device 900 is applied to Figure 3 The first device in the embodiment of the present application is shown. The specific functions of the processor 902 in this implementation are introduced below.

[0325] The processor 902 is used to: receive a first request through the interface circuit 901, the first request is used to request to revoke authorization of a first level of a first service for a first user, the first service includes multiple levels, and the multiple levels include the first level; according to the first request, determine at least one level of the first service, the at least one level includes a second level, and the resources corresponding to the second level of the first service are first resources used to provide the first service to the first user.

[0326] In another embodiment, the communication device 900 is applied to Figure 3The second device in the embodiment of the present application is shown. The specific functions of the processor 902 in this implementation are introduced below.

[0327] The processor 902 is configured to: send a first request through the interface circuit 901, the first request is used to request to revoke authorization of a first level of a first service for a first user, the first service includes multiple levels, and the multiple levels include the first level. The first request also includes first information, or the processor 902 is further configured to: send first information through the interface circuit 901; wherein the first information is used to indicate the second level, and the resource corresponding to the second level of the first service is the first resource used to provide the first service to the first user.

[0328] The specific functions of the processor 902 may refer to the description of the communication method provided in the above embodiments and examples of the present application, and Figure 8 The specific functional description of the communication device 800 in the embodiment of the present application is not repeated here.

[0329] The memory 903 is used to store program instructions and / or data, etc. Specifically, the program instructions may include program codes, and the program codes include computer operation instructions. The memory 903 may include RAM, and may also include non-volatile memory (non-volatile memory), such as at least one disk storage. The processor 902 executes the program instructions stored in the memory 903, and uses the data stored in the memory 903 to implement the above functions, thereby realizing the communication method provided in the above embodiment of the present application. The memory 903 can be integrated with the processor 902, or it can be a memory outside the communication device.

[0330] It is understandable that this application Fig. 9The memory 903 in can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memory. Among them, the non-volatile memory can be a ROM, a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. The volatile memory can be a RAM, which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (DoubleData Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

[0331] Based on the above embodiments, the embodiments of the present application further provide a computer program product including computer executable instructions. When the computer program product is run, the method provided in the above embodiments is executed.

[0332] Based on the above embodiments, the embodiments of the present application further provide a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a computer, the computer executes the method provided in the above embodiments.

[0333] The storage medium may be any available medium that can be accessed by a computer. For example, but not limited to, a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer.

[0334] Based on the above embodiments, an embodiment of the present application further provides a chip, which is used to read a computer program stored in a memory to implement the method provided in the above embodiments.

[0335] Based on the above embodiments, the embodiments of the present application provide a chip system, which includes a processor for supporting a computer device to implement the functions involved in each device in the above embodiments. In a possible design, the chip system also includes a memory, which is used to store the necessary programs and data for the computer device. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0336] In the various embodiments of the present application, unless otherwise specified or provided for in any logical conflict, the terms and / or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.

[0337] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0338] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0339] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0340] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0341] In the various embodiments of the present application, unless otherwise specified or provided for in any logical conflict, the terms and / or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.

[0342] In this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0343] It is understood that the various numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic.

[0344] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A communication method, applied to a first device, characterized in that: include: receiving a first request, the first request being used to request revocation of authorization of a first level of a first service for a first user, the first service comprising a plurality of levels, the plurality of levels including the first level; At least one level of the first service is determined according to the first request, the at least one level includes a second level, and resources corresponding to the second level of the first service are first resources used to provide the first service to the first user.

2. The method according to claim 1, characterized in that The valid authorization for the first service of the first user includes at least two levels of authorization for the first service, the at least two levels including the first level; Determining at least one level of the first service according to the first request includes: One or more of the at least two levels other than the first level are determined as the at least one level.

3. The method according to claim 2, characterized in that Also includes: Information indicating the at least one level is transmitted.

4. The method according to claim 3, characterized in that The at least one level includes N levels of the at least two levels except the first level, where N is an integer greater than or equal to 2, and further includes: First indication information is sent, where the first indication information is used to indicate a first rule for selecting the second level from the N levels.

5. The method according to claim 3 or 4, characterized in that The information indicating the at least one level includes at least one of the following: indicative information of the at least one level; or Information corresponding to the at least one level.

6. The method according to claim 2, characterized in that The at least one level includes N levels of the at least two levels except the first level, where N is an integer greater than or equal to 2, and further includes: The second level is selected from the N levels according to a first rule.

7. The method according to claim 4 or 6, characterized in that The first rule includes at least one of the following: The second level is the highest quality level that can be met by the network where the first device is located among the N levels; or The second level is the level authorized latest among the N levels.

8. The method according to claim 1, characterized in that The valid authorization for the first service of the first user includes authorization for one level of the first service, the one level being the first level; Determining at least one level according to the first request, including: The set second level is determined as the at least one level.

9. The method according to claim 1, characterized in that The first request further includes first information, or the method further includes: receiving the first information; wherein the first information is used to indicate the second level; Determining at least one level according to the first request, including: The second level is determined as the at least one level.

10. The method according to claim 9, characterized in that The first information is indication information of the second level, or the first information is information corresponding to the second level; wherein the valid authorization of the first service for the first user includes the authorization of the second level of the first service.

11. The method according to any one of claims 6, 8 to 10, characterized in that: Also includes: Information indicating the second level is transmitted.

12. The method according to claim 11, characterized in that The information indicating the second level includes at least one of the following: the second level of indicative information; or Information corresponding to the second level.

13. The method according to any one of claims 3 to 5, 11 to 12, characterized in that: Also includes: Send at least one of the following: indication information of the first user or indication information of the first service.

14. The method according to any one of claims 1 to 13, characterized in that The first request includes at least one of the following: The first authorization information or information indicating the first authorization information, wherein the first authorization information is authorization information of the first level for authorizing the first user to provide the first service.

15. The method according to any one of claims 1 to 14, characterized in that: The first request includes at least one of the following: Indication information of the first user; or Indication information of the first service.

16. The method according to claim 15, characterized in that The first request includes first authorization information, where the first authorization information is authorization information of the first level for authorizing the first user to provide the first service, and the first authorization information includes at least one of the following: indication information of the first user or indication information of the first service.

17. The method according to claim 15 or 16, characterized in that Determining at least one level of the first service according to the first request includes: The at least one level of the first service for the first user is determined according to the indication information of the first user and the indication information of the first service.

18. The method according to claim 17, characterized in that Determining, according to the indication information of the first user and the indication information of the first service, the at least one level of the first service for the first user includes: Determine, according to the indication information of the first user and the indication information of the first service, at least one piece of authorization information, each piece of authorization information in the at least one piece of authorization information includes the indication information of the first user and the indication information of the first service, and each piece of authorization information in the at least one piece of authorization information is authorization information of one or more levels for authorizing the first user to provide the first service; At least one level of the first service is determined according to the at least one authorization information.

19. The method according to any one of claims 1 to 18, characterized in that The first service is a quality of service QoS service, the level of the first service is a quality of service level QoS level or a QoS level corresponding to the value 5QIvalue of the fifth generation 5G service quality identifier, and the first resource is a protocol data unit PDU session.

20. A communication method, applied to a second device, characterized in that: include: Sending a first request, the first request being used to request revoking authorization of a first level of a first service for a first user, the first service including multiple levels, the multiple levels including the first level; The first request also includes first information, or the method further includes: sending the first information; wherein the first information is used to indicate a second level, and the resources corresponding to the second level of the first service are first resources used to provide the first service to the first user.

21. The method of claim 20, wherein: The first information is indication information of the second level, or the first information is information corresponding to the second level; wherein the valid authorization of the first service for the first user includes the authorization of the second level of the first service.

22. The method according to claim 20 or 21, characterized in that The first request includes at least one of the following: The first authorization information or information indicating the first authorization information, wherein the first authorization information is authorization information of the first level for authorizing the first user to provide the first service.

23. The method according to any one of claims 20 to 22, characterized in that The first request includes at least one of the following: Indication information of the first user; or Indication information of the first service.

24. The method of claim 23, wherein: The first request includes first authorization information, where the first authorization information is authorization information of the first level for authorizing the first user to provide the first service, and the first authorization information includes at least one of the following: indication information of the first user or indication information of the first service.

25. The method according to any one of claims 20 to 24, characterized in that The first service is a quality of service QoS service, the level of the first service is a quality of service level QoS level or a QoS level corresponding to the value 5QIvalue of the fifth generation 5G service quality identifier, and the first resource is a protocol data unit PDU session.

26. A communication device, characterized in that: include: An interface unit for receiving and sending information; A processing unit, configured to execute the method according to any one of claims 1 to 25 through the communication unit.

27. A communication device, characterized in that: The method comprises a processor configured to execute the method according to any one of claims 1 to 25.

28. A communication system, characterized in that: include: A first device, configured to implement the method according to any one of claims 1 to 19; A second device is used to implement the method according to any one of claims 20 to 25.

29. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are executed by the communication device, the method according to any one of claims 1 to 25 is implemented.

30. A computer program product, characterized in that The computer program product comprises: a computer program code, and when the computer program code is executed, the method according to any one of claims 1 to 25 is implemented.

Images