WO2024082143A1

WO2024082143A1 - Device service role verification method and apparatus and device, and storage medium

Info

Publication number: WO2024082143A1
Application number: PCT/CN2022/125974
Authority: WO
Inventors: 陆伟; 商正仪
Original assignee: 北京小米移动软件有限公司
Priority date: 2022-10-18
Filing date: 2022-10-18
Publication date: 2024-04-25

Abstract

The present disclosure provides a device service role verification method and apparatus and device, and a storage medium. The method comprises: sending a discovery request message; receiving a discovery response message sent by a second UE, the discovery response message comprising an authorization token of the second UE; and when the authorization token of the second UE passes verification, establishing a connection with the second UE. The method provided by the present disclosure avoids spoofing between UEs, improves service execution accuracy, and improves information security.

Description

A device business role verification method/device/equipment and storage medium

Technical Field

The present disclosure relates to the field of communication technology, and in particular to a method/device/equipment for verifying a device business role and a storage medium.

Background technique

In a communication system, when performing ranging services and/or sidelink (SL) positioning services, multiple user equipment (UE) are usually required to play different service roles to complete the services, wherein the service roles of UE may include reference UE (such as sidelink reference UE (SL Reference UE)), target UE (Target UE), assistant UE (Assistant UE), located UE (Located UE), server UE (such as sidelink positioning server UE (SL Positioning Server UE)), client UE (such as sidelink positioning client UE (SL Positioning Client UE)), etc. In the process of discovering and connecting multiple UEs, how to improve the communication security between multiple UEs needs to be solved urgently.

Summary of the invention

The device service role verification method/device/equipment and storage medium proposed in the present disclosure are used to verify the service role declared by the UE to ensure the accuracy of service execution and information security.

In a first aspect, an embodiment of the present disclosure provides a method for verifying a service role of a device, the method being executed by a first user device, including:

Send a discovery request message;

receiving a discovery response message sent by the second UE, wherein the discovery response message includes an authorization token of the second UE;

After the authorization token of the second UE is verified, a connection is established with the second UE.

In the present disclosure, the first UE will send a discovery request message, and then the first UE will receive a discovery response message sent by the second UE, the discovery response message including the authorization token of the second UE; and, when the authorization token of the second UE is verified, the first UE will establish a connection with the second UE. It can be seen that the present disclosure provides a specific method for verifying the business role of the UE based on the authorization token, and provides the specific information included in the authorization token and the specific details of the verification based on the authorization token. When the discovery process is performed between UEs, the two UEs can exchange their respective authorization tokens, and use the method of the present disclosure to verify the business role declared by the UE based on the authorization token of the UE, thereby avoiding mutual deception between UEs, improving the accuracy of service execution, and improving information security.

In a second aspect, an embodiment of the present disclosure provides a method for verifying a service role of a device, the method being executed by a second user device, including:

Receiving a discovery request message sent by the first UE, where the discovery request message includes an authorization token of the first UE;

When the authorization token of the first UE is verified, a discovery response message is sent to the first UE, and the discovery response message includes the authorization token of the second UE.

In a third aspect, an embodiment of the present disclosure provides a communication device, which is configured in a first user equipment, including:

A transceiver module, used for sending a discovery request message;

The transceiver module is further configured to receive a discovery response message sent by the second UE, wherein the discovery response message includes an authorization token of the second UE;

The processing module is also used to establish a connection with the second UE after the authorization token of the second UE is verified.

In a fourth aspect, an embodiment of the present disclosure provides a communication device, which is configured in a second user equipment, including:

A transceiver module, configured to receive a discovery request message sent by a first UE, wherein the discovery request message includes an authorization token of the first UE;

The transceiver module is further used to send a discovery response message to the first UE after the authorization token of the first UE is verified, and the discovery response message includes the authorization token of the second UE.

In a fifth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the first aspect or the second aspect is executed.

In a sixth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the first aspect or the second aspect above.

In a seventh aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the first or second aspect above.

In an eighth aspect, an embodiment of the present disclosure provides a communication system, the system includes the communication device described in the third to fourth aspects, or the system includes the communication device described in the fifth aspect, or the system includes the communication device described in the sixth aspect, or the system includes the communication device described in the seventh aspect.

In a ninth aspect, an embodiment of the present disclosure provides a computer-readable storage medium for storing instructions used by the above-mentioned network device, and when the instructions are executed, the terminal device executes the method described in the first or second aspect above.

In a tenth aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect or the second aspect above.

In the eleventh aspect, the present disclosure provides a chip system, which includes at least one processor and an interface, for supporting a network device to implement the functions involved in the method described in the first aspect or the second aspect, for example, determining or processing at least one of the data and information involved in the above method. In one possible design, the chip system also includes a memory, which is used to store computer programs and data necessary for the source auxiliary node. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

In a twelfth aspect, the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the first or second aspect above.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and/or additional aspects and advantages of the present disclosure will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

FIG1 is a schematic diagram of the architecture of some communication systems provided by embodiments of the present disclosure;

FIG2 is a schematic diagram of a flow chart of a method for verifying a device service role according to another embodiment of the present disclosure;

3a-3c are schematic flow charts of a method for verifying a device service role according to another embodiment of the present disclosure;

4a-4b are schematic structural diagrams of a communication device provided by another embodiment of the present disclosure;

FIG5 is a block diagram of a communication device provided by an embodiment of the present disclosure;

FIG6 is a schematic diagram of the structure of a chip provided by an embodiment of the present disclosure.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the embodiments of the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the embodiments of the present disclosure as detailed in the appended claims.

The terms used in the disclosed embodiments are only for the purpose of describing specific embodiments and are not intended to limit the disclosed embodiments. The singular forms of "a" and "the" used in the disclosed embodiments and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and/or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

It should be understood that although the terms first, second, third, etc. may be used to describe various information in the disclosed embodiments, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the disclosed embodiments, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the words "if" and "if" as used herein may be interpreted as "at" or "when" or "in response to determination".

Embodiments of the present disclosure are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be construed as limiting the present disclosure.

To facilitate understanding, the terms involved in this application are first introduced.

1. Sidelink positioning service

Sidelink positioning service, also known as sidelink positioning service or ranging service, refers to determining the distance between two UEs and/or the direction from one UE to another UE through a direct communication connection.

In order to better understand a method for verifying a device service role disclosed in an embodiment of the present disclosure, a communication system to which the embodiment of the present disclosure is applicable is first described below.

Please refer to Figure 1, which is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure. The communication system may include but is not limited to a network device and at least two UEs. The number and form of devices shown in Figure 1 are only used for example and do not constitute a limitation on the embodiment of the present disclosure. The application may include two or more network devices and more than two UEs. The communication system shown in Figure 1 includes a network device 11, a first UE 12, and a second UE 13 as an example.

It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems, such as long term evolution (LTE) system, fifth generation (5G) mobile communication system, 5G new radio (NR) system, or other future new mobile communication systems.

The network device 11 in the embodiment of the present disclosure is an entity on the network side for transmitting or receiving signals. For example, the network device 11 may be an evolved NodeB (eNB), a transmission reception point (TRP), a Radio Remote Head (RRH), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiment of the present disclosure does not limit the specific technology and specific device form adopted by the base station. The base station provided in the embodiment of the present disclosure may be composed of a central unit (CU) and a distributed unit (DU), wherein the CU may also be referred to as a control unit. The CU-DU structure may be used to split the base station, such as the protocol layer of the base station, and the functions of some protocol layers are placed in the CU for centralized control, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.

The first UE12 and the second UE13 in the embodiment of the present disclosure are both entities for receiving or transmitting signals on the user side, such as a mobile phone. The terminal device may also be referred to as a terminal device (terminal), a user equipment (UE), a mobile station (MS), a mobile terminal device (MT), etc. The terminal device may be a car with communication function, a smart car, a mobile phone (mobile phone), a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in a smart city (smart city), a wireless terminal device in a smart home (smart home), etc. The embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal device.

It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. A person skilled in the art can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

The following describes in detail the device service role verification method/device/equipment and storage medium provided by the embodiments of the present disclosure with reference to the accompanying drawings.

It should be noted that the naming of the following messages (including request messages, response messages, etc.) is only for convenience, and the naming itself does not constitute a limitation on the function of the message.

FIG2 is a flow chart of a method for verifying a device service role provided by an embodiment of the present disclosure. The method is executed by a first UE. As shown in FIG2 , the method for verifying a device service role may include the following steps:

Step 201: Send a discovery request message.

In one embodiment of the present disclosure, the discovery request message may be, for example, a broadcast discovery message or a direct communication message.

In one embodiment of the present disclosure, the discovery request message may include service information (such as a service identifier and/or a service type, etc.) requested by the first UE to discover to the second UE, and/or a service role declared by the first UE. The service role declared by the first UE can be understood as the service role that the first UE wants to play in the service it requests to discover. The service role declared by the first UE may be any one or several of the service roles that the network device pre-authorizes for the first UE in the service it requests to discover, or may not be a service role that the network device pre-authorizes for the first UE. When the service role declared by the first UE is not a service role that the network device pre-authorizes for it, when the second UE and the first UE perform the service, an error may occur due to the mismatch of the service roles of the two UEs, thereby causing service interruption or low service execution efficiency. Alternatively, when the first UE is a malicious UE and deliberately declares a service role that is not authorized by the network device, that is, the first UE deceives the second UE, then for the second UE, the communication between the second UE and the malicious UE may bring communication security issues.

In one embodiment of the present disclosure, the discovery request message may also include an authorization token of the first UE, and the authorization token of the first UE is used for: the second UE verifies the business role of the first UE based on the authorization token of the first UE to verify whether the business role declared by the first UE is its authorized business role, and/or further verifies other information of the first UE to prevent the first UE from deceiving the second UE.

Among them, in one embodiment of the present disclosure, the service roles of UE may include, for example: reference UE (such as sidelink reference UE (SL Reference UE)), target UE (Target UE), assistant UE (Assistant UE), located UE (Located UE), UE as a server (such as UE as a sidelink positioning server (SL Positioning Server UE)), client UE (such as sidelink positioning client UE (SL Positioning Client UE)), etc. Among them, the above-mentioned target UE may be a UE to be located or measured; the above-mentioned positioning UE may be a UE to obtain the positioning position of the target UE; the above-mentioned reference UE may be: a UE that can determine the positioning position or ranging distance of the target UE based on the position of the reference UE or the distance between the reference UE and the target UE; the above-mentioned assistant UE may be: a UE used to assist in forwarding messages in ranging service or sidelink positioning service; the above-mentioned UE as a server may be: a UE with positioning calculation capability or ranging calculation capability; the above-mentioned client UE may be: a UE that can act as a client in ranging service or sidelink positioning service.

In one embodiment of the present disclosure, the authorization token of the first UE may include at least one of the following:

The ID of the network device that generates the authorization token of the first UE;

ID of the first UE;

The conditions of the peer UE;

The service requested to be discovered by the first UE;

The service role that the first UE is authorized to use in the service requested for discovery;

A condition for allowing execution of a service requested to be discovered by the first UE;

The validity period of the authorization token of the first UE.

The above-mentioned "network device for generating authorization token" may include at least one of a ProSe key management function (PKMF) network element, a direct discovery name management function (DDNMF) network element, a server including proximity services, and a Unified Data Management (UDM) network element. It is understandable that the network device for generating authorization token is generally a network device for authorizing a service role for the first UE.

The above-mentioned conditions of the opposite end UE include any one of the following: allowing any UE to be the opposite end UE of the first UE; allowing any UE to be the opposite end UE of the first UE in the service requested to be discovered by the first UE; the business role and/or ID of the opposite end UE expected by the first UE; the business role and/or ID of the opposite end UE expected by the first UE to be the first UE in the service requested to be discovered by the first UE, etc.

The above-mentioned “allowing any UE to serve as the opposite UE of the first UE in the service requested to be discovered by the first UE” can be understood as: in the service requested to be discovered by the first UE, any UE playing any business role can be allowed to serve as the opposite UE of the first UE.

The above-mentioned "service role and/or ID of the opposite UE expected by the UE" may be determined by the UE based on its own authorized service role in the requested discovery service. For example, if the service role authorized by the UE itself is the target UE, the service role of the opposite UE expected by the UE may include at least one of a reference UE, an auxiliary UE, a positioning UE, etc., and the ID of the opposite UE expected by the UE may be: the ID of a UE whose service role is at least one of a reference UE, an auxiliary UE, a positioning UE, etc.

The above-mentioned “service requested to be discovered by the UE” may be, for example, a ranging service and/or a sidelink positioning service.

The above-mentioned "service role authorized by the UE in the service requested for discovery" may be authorized by a network device, wherein the network device that authorizes the service role may be at least one of a server including proximity service and a unified data management function (UDM) network element.

The above-mentioned "conditions for allowing execution of services requested by the UE to be discovered" may include time conditions for allowing execution and/or geographical conditions for allowing execution. Among them, the time conditions for allowing execution may include: the time period for allowing execution of services requested by the UE to be discovered, such as allowing execution of services requested by the UE to be discovered during daytime hours of 8:00-16:00; the geographical conditions for allowing execution may include: the geographical area for allowing execution of services requested by the UE to be discovered, such as allowing execution of services requested by the UE to be discovered in Beijing. It is understandable that the conditions for allowing execution may also be other conditions, for example, the distance between the opposite UE and the first UE is within a preset distance range, etc., and the embodiments of the present disclosure do not specifically limit this.

The above-mentioned "validity period of the authorization token" may include the validity period of the authorization token, or the invalid period of the authorization token. In one example, the authorization token of the first UE may carry the start time and valid duration of the validity period of the authorization token. Among them, the generation time and valid duration of the token are used to indicate the validity period of the authorization token. Alternatively, the authorization token of the first UE may carry the validity start time and end time of the authorization token. Alternatively, the authorization token of the first UE may carry the expiration time of the authorization token, which is used to indicate the validity period of the authorization token or to indicate the invalid period of the authorization token. In short, the embodiments of the present disclosure do not specifically limit the method of specifically indicating the validity period or invalid period of the authorization token.

In one embodiment of the present disclosure, the authorization token of the first UE in the above-mentioned discovery request message may be: the authorization token of the first UE signed by the first key. And, after the second UE receives the authorization token of the first UE signed by the first key, it may use the second key to decode and verify the received authorization token of the first UE. Among them, the first key may be used to: digitally sign and protect the authorization token to ensure that the authorization token will not be forged or tampered with during transmission by an attacker (such as a malicious UE), thereby improving the accuracy of service execution and information security. Among them, malicious UEs may include, for example: UEs requesting discovery of services different from UEs receiving authorization tokens, UEs that have not requested services, UEs whose roles are not authorized by network devices, UEs that have not obtained authorization tokens from network devices, etc.

In one embodiment of the present disclosure, the above-mentioned first key may be a private key of a network device, and the second key may be a public key of the network device. In some embodiments, the first key and the second key may be a public-private key pair generated by a network device, and the network device sends the second key to the first UE. For example, the network device may generate and send the second key to the first UE when authorizing a service role for any UE (e.g., the first UE). In one example, the network device may send the second key together with the authorization token generated for the UE to the UE. In another embodiment of the present disclosure, both the first key and the second key may be a shared key between the UE and the network device; wherein the shared key between the UE and the network device may be pre-agreed and configured by the UE and the network device. For example, it may be pre-agreed and configured when the network device authorizes a service role for the UE.

Optionally, in one embodiment of the present disclosure, when the network device sends the authorization token generated for the UE to the UE, the authorization token may also be signed using the first key, and the UE may decode the authorization token signed by the first key received from the network device based on the second key received from the network device and/or the pre-agreed configured second key.

It should be noted that the embodiment of the present disclosure does not specifically limit the encryption method of the authorization token, nor does it specifically limit the method for generating the first key and the second key.

In addition, in one embodiment of the present disclosure, after the second UE receives the authorization token of the first UE sent by the first UE, the service role of the first UE can be verified based on the authorization token of the first UE. Specifically, at least one of the following can be verified:

Verify whether the service role of the opposite UE expected by the first UE in the authorization token of the first UE is consistent with the service role authorized by the second UE;

Verify whether the ID of the opposite UE expected by the first UE in the authorization token of the first UE is consistent with the ID of the second UE;

Verify whether the service requested to be discovered by the first UE in the authorization token of the first UE is consistent with the service that the first UE needs to request to be discovered by the second UE;

Verify whether the service role authorized by the first UE in the service requested for discovery in the authorization token of the first UE is consistent with the service role declared by the first UE;

Verify whether the execution permission condition of the service requested to be discovered in the authorization token of the first UE is met;

Verify whether the authorization token of the first UE has expired.

In response to satisfying a specific condition, determining that the second UE successfully authenticates the service role of the first UE (i.e., the authentication is passed);

The specific conditions include at least one of the following:

Specific condition 1: The business role of the opposite UE expected by the first UE in the authorization token of the first UE is consistent with the business role authorized for the second UE. For example: the business role of the opposite UE expected by the first UE in the authorization token of the first UE is reference UE and positioning UE, and the business role authorized for the second UE is reference UE, then the second UE successfully verifies the authorization token of the first UE. For another example: the business role of the opposite UE expected by the first UE in the authorization token of the first UE is reference UE and positioning UE, and the business role authorized for the second UE is target UE, then the second UE fails to verify the authorization token of the first UE.

Specific condition 2: The ID of the opposite UE expected by the first UE in the authorization token of the first UE is consistent with the ID of the second UE. For example, the ID of the opposite UE expected by the first UE in the authorization token of the first UE includes UE#1 and UE#2, and the ID of the second UE is UE#1, then the second UE successfully verifies the authorization token of the first UE. For another example: the ID of the opposite UE expected by the first UE in the authorization token of the first UE includes UE#1 and UE#2, and the ID of the second UE is UE#3, then the second UE fails to verify the authorization token of the first UE.

Specific condition 3: The service requested by the first UE to be discovered in the authorization token of the first UE is consistent with the service that the first UE needs to discover from the second UE. For example, the service requested by the first UE to be discovered in the authorization token of the first UE is: ranging service, and the service that the first UE needs to discover from the second UE is also: ranging service, then the second UE successfully verifies the authorization token of the first UE. For another example: the service requested by the first UE to be discovered in the authorization token of the first UE is: ranging service, and the service that the first UE needs to discover from the second UE is: side link, then the second UE fails to verify the authorization token of the first UE.

Specific condition 4: The business role authorized by the first UE in the authorization token of the first UE in the service requested to be discovered is consistent with the business role declared by the first UE. For example: the business role authorized by the first UE in the authorization token of the first UE in the service requested to be discovered is the target UE, and the business role declared by the first UE is also the target UE, then the second UE successfully verifies the authorization token of the first UE. For another example: the business role authorized by the first UE in the authorization token of the first UE in the service requested to be discovered is the target UE, and the business role declared by the first UE is the reference UE, then the second UE fails to verify the authorization token of the first UE.

Specific condition 5: the execution condition of the service requested to be discovered in the authorization token of the first UE is met (for example, the execution condition of the service requested to be discovered in the authorization token of the first UE is: the service requested to be discovered by the first UE is allowed to be executed during 8:00-16:00 in Beijing during the day, and the second UE determines that the first UE and the second UE are both located in Beijing, and the time point when the first UE requests to discover the service is 9:00);

Specific condition 6: The authorization token of the first UE has not expired (for example, the authorization token of the first UE is valid from October 1, 2022 to October 9, 2022, and the time when the first UE requests discovery service is October 8, 2022).

Further, in an embodiment of the present disclosure, after the second UE successfully authenticates the service role of the first UE, the second UE may send a discovery response message to the first UE.

Step 202: Receive a discovery response message sent by the second UE, where the discovery response message includes an authorization token of the second UE.

In one embodiment of the present disclosure, the authorization token of the second UE may include at least one of the following:

The ID of the network device that generates the authorization token of the second UE;

ID of the second UE;

Conditions of the opposite UE; wherein the conditions of the opposite UE include: allowing any UE to serve as the opposite UE of the second UE in the service requested to be discovered by the second UE, or the conditions of the opposite UE include the service role and/or ID of the opposite UE expected by the second UE;

The service requested to be discovered by the second UE;

The service role that the second UE is authorized to use in the service requested for discovery;

The conditions for allowing execution of the service requested to be discovered by the second UE;

The validity period of the authorization token of the second UE.

For the introduction of the authorization token of the second UE, reference may be made to the introduction of the authorization token of the first UE mentioned above.

Further, in one embodiment of the present disclosure, the authorization token of the second UE may be an authorization token of the second UE signed by the first key. After the first UE receives the authorization token of the second UE signed by the first key, it may use the second key to decode and verify the received authorization token of the second UE. For the relevant introduction of the first key and the second key, reference may be made to the description of the above embodiment.

In addition, in one embodiment of the present disclosure, the discovery response message may include service information (such as the identifier of the service, and/or the type of service, etc.) requested by the second UE to discover to the first UE, and/or the service role declared by the second UE. The meaning of the service role declared by the second UE can be described with reference to the above embodiment. It can be understood that, when the service role declared by the second UE is not a service role pre-authorized by the network device, when the first UE and the second UE perform the service, an error may occur due to the mismatch between the service roles of the two UEs, resulting in service interruption or low service execution efficiency. Alternatively, when the second UE is a malicious UE and deliberately declares a service role that is not authorized by the network device, that is, the second UE deceives the first UE, then for the first UE, communicating with the malicious UE may bring communication security issues.

Step 203: After the authorization token of the second UE is verified, a connection is established with the second UE.

In one embodiment of the present disclosure, when the first UE receives a discovery response message sent by the second UE, it can first verify the service role of the second UE based on the authorization token of the second UE, and when the authorization token of the second UE is verified, establish a connection with the second UE.

Among them, in one embodiment of the present disclosure, the method for verifying the service role of the second UE based on the authorization token of the second UE may include at least one of the following:

Verify whether the service role of the opposite UE expected by the second UE in the authorization token of the second UE is consistent with the service role authorized by the first UE;

Verify whether the ID of the opposite UE expected by the second UE in the authorization token of the second UE is consistent with the ID of the first UE;

Verify whether the service requested to be discovered by the second UE in the authorization token of the second UE is consistent with the service that the second UE needs to discover from the first UE;

Verify whether the service role authorized by the second UE in the service requested for discovery in the authorization token of the second UE is consistent with the service role declared by the second UE;

Verify whether the execution permission condition of the service requested to be discovered in the authorization token of the second UE is met;

Verify whether the authorization token of the second UE is expired.

wherein, in response to satisfying a specific condition, determining that the service role verification of the second UE is successful;

The specific conditions include at least one of the following:

The service role of the opposite UE expected by the second UE in the authorization token of the second UE is consistent with the service role authorized by the first UE;

The ID of the opposite UE expected by the second UE in the authorization token of the second UE is consistent with the ID of the first UE;

The service requested to be discovered by the second UE in the authorization token of the second UE is consistent with the service that the second UE needs to discover from the first UE;

The service role authorized by the second UE in the service requested for discovery in the authorization token of the second UE is consistent with the service role declared by the second UE;

The execution permission condition of the service requested to be discovered in the authorization token of the second UE is met;

The authorization token of the second UE has not expired.

The principle of the above verification process is similar to the principle of the aforementioned verification process of the service role of the first UE by the second UE, and will not be repeated in the embodiment of the present disclosure.

From the above content, it can be seen that the present disclosure provides the specific information included in the authorization token and provides a specific detailed process of how a first UE verifies the business role of the second UE based on the authorization token of the second UE. The verification method of the present disclosure can realize the verification of the business role of the UE, thereby avoiding mutual deception between UEs, improving the accuracy of service execution, and improving information security.

Furthermore, it should be noted that, in one embodiment of the present disclosure, for the first UE, the first UE will respond to the message of the second UE, or communicate with the second UE, or send the authorization token of the first UE to the second UE, or establish a communication connection with the second UE, only after the first UE successfully verifies the business role of the second UE; at the same time, for the second UE, the second UE will respond to the message of the first UE, or communicate with the first UE, or send the authorization token of the second UE to the first UE, or establish a communication connection with the first UE, only after the second UE successfully verifies the business role of the first UE.

In summary, in the verification method of the device business role provided in the embodiment of the present disclosure, the first UE will send a discovery request message, and then the first UE will receive a discovery response message sent by the second UE, and the discovery response message includes the authorization token of the second UE; and, when the authorization token of the second UE is verified, the first UE will establish a connection with the second UE. It can be seen that the present disclosure provides a specific method for verifying the business role of the UE based on the authorization token, and provides the specific information included in the authorization token and the specific details of the verification based on the authorization token. When the discovery process is performed between UEs, the two UEs can exchange their respective authorization tokens, and use the method of the present disclosure to verify the business role declared by the UE based on the authorization token of the UE, thereby avoiding mutual deception between UEs, improving the accuracy of service execution, and improving information security.

FIG3a is a flow chart of a method for verifying a device service role provided by an embodiment of the present disclosure. The method is executed by a first UE. As shown in FIG3a , the method for verifying a device service role may include the following steps:

Step 301a: Receive an authorization token of the first UE sent by the network device.

In one embodiment of the present disclosure, the authorization token of the UE is generated by a network device and then sent to the UE. Also, the network device that generates the authorization token may be described in the above embodiment.

Further, in one embodiment of the present disclosure, the authorization token sent by the network device to the UE may be an authorization token signed by the first key, and when the first UE receives the authorization token of the first UE signed by the first key, the second key may be used to decode and verify the received authorization token of the first UE. For the introduction of the first key and the second key, reference may be made to the description of the above embodiment.

In addition, in one embodiment of the present disclosure, after the first UE obtains the authorization token of the first UE sent by the network device, the first UE can store the authorization token of the first UE in association with the service requested to be discovered corresponding to the authorization token of the first UE. When the first UE subsequently sends the authorization token of the first UE to the second UE, the authorization token of the first UE associated with the service currently requested to be discovered by the first UE is sent to the second UE. That is, in one embodiment of the present disclosure, the authorization token is used to verify the business role of the UE in the service requested to be discovered corresponding to the authorization token.

FIG3b is a flow chart of a method for verifying a device service role provided by an embodiment of the present disclosure. The method is executed by a second UE. As shown in FIG3b , the method for verifying a device service role may include the following steps:

Step 301b: Receive a discovery request message sent by the first UE, where the discovery request message includes an authorization token of the first UE.

Step 302b: After the authorization token of the first UE is verified, a discovery response message is sent to the first UE, where the discovery response message includes the authorization token of the second UE.

For a detailed description of steps 301b - 302b, please refer to the above embodiment description.

In summary, in the device business role verification method provided in the embodiment of the present disclosure, the second UE will receive a discovery request message sent by the first UE, and the discovery request message includes the authorization token of the first UE. Afterwards, when the authorization token of the first UE is verified, the second UE will send a discovery response message to the first UE, and the discovery response message includes the authorization token of the second UE. It can be seen that the present disclosure provides a specific method for verifying the business role of the UE based on the authorization token, and provides the specific information included in the authorization token and the specific details of the verification based on the authorization token. When the discovery process is performed between UEs, the two UEs can exchange their respective authorization tokens, and use the method of the present disclosure to verify the business role declared by the UE based on the authorization token of the UE, thereby avoiding mutual deception between UEs, improving the accuracy of service execution, and improving information security.

FIG3c is a flow chart of a method for verifying a device service role provided in an embodiment of the present disclosure. The method is executed by a second UE. As shown in FIG3c , the method for verifying a device service role may include the following steps:

Step 301c: Receive the authorization token of the second UE sent by the network device.

For a detailed description of step 301c, please refer to the above embodiment description.

FIG4a is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure. As shown in FIG4a , the device may include:

A transceiver module, used for sending a discovery request message;

In summary, in the communication device provided in the embodiment of the present disclosure, the first UE will send a discovery request message, and then the first UE will receive a discovery response message sent by the second UE, the discovery response message including the authorization token of the second UE; and, when the authorization token of the second UE is verified, the first UE will establish a connection with the second UE. It can be seen that the present disclosure provides a specific method for verifying the business role of the UE based on the authorization token, and provides the specific information included in the authorization token and the specific details of the verification based on the authorization token. When the discovery process is performed between UEs, the two UEs can exchange their respective authorization tokens, and use the method of the present disclosure to verify the business role declared by the UE based on the authorization token of the UE, thereby avoiding mutual deception between UEs, improving the accuracy of service execution, and improving information security.

Optionally, in an embodiment of the present disclosure, the discovery request message includes an authorization token of the first UE, and the authorization token of the first UE is used for: the second UE to verify the service role of the first UE based on the authorization token of the first UE.

Optionally, in an embodiment of the present disclosure, the authorization token of the first UE includes at least one of the following:

The identification ID of the network device that generates the authorization token;

an ID of the first UE;

The conditions of the peer UE;

The service requested to be discovered by the first UE;

A service role authorized by the first UE in the service requested for discovery;

A condition for allowing execution of the service requested to be discovered by the first UE;

The validity period of the authorization token.

Optionally, in an embodiment of the present disclosure, the condition of the opposite end UE includes: allowing any UE to be the opposite end UE of the first UE, or, the condition of the opposite end UE includes the service role and/or ID of the opposite end UE expected by the first UE.

Optionally, in one embodiment of the present disclosure, the device is further used for:

Receive an authorization token of the first UE sent by a network device.

Optionally, in an embodiment of the present disclosure, the transceiver module is further used to:

An authorization token of the first UE signed by the first key and sent by the network device is received.

Optionally, in an embodiment of the present disclosure, the authorization token of the first UE in the discovery request message is: the authorization token of the first UE signed by the first key.

Optionally, in an embodiment of the present disclosure, the authorization token of the second UE in the discovery response message is: the authorization token of the second UE signed by the first key;

The device is also used for:

The received authorization token of the second UE is decoded and verified using the second key.

Optionally, in an embodiment of the present disclosure, the first key is a private key of the network device, and the second key is a public key of the network device; or

The first key and the second key are both shared keys between the UE and the network device.

Optionally, in an embodiment of the present disclosure, the device is further used for at least one of the following:

Verify whether the service requested to be discovered by the second UE in the authorization token of the second UE is consistent with the service that the second UE needs to request to discover from the first UE;

Verifying whether the execution permission condition of the service requested to be discovered in the authorization token of the second UE is met;

Verify whether the authorization token of the second UE has expired.

FIG4b is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure. As shown in FIG4b , the device may include:

In summary, in the communication device provided in the embodiment of the present disclosure, the second UE will receive a discovery request message sent by the first UE, and the discovery request message includes the authorization token of the first UE. Afterwards, when the authorization token of the first UE is verified, the second UE will send a discovery response message to the first UE, and the discovery response message includes the authorization token of the second UE. It can be seen that the present disclosure provides a specific method for verifying the business role of the UE based on the authorization token, and provides the specific information included in the authorization token and the specific details of the verification based on the authorization token. When the discovery process is performed between UEs, the two UEs can exchange their respective authorization tokens, and use the method of the present disclosure to verify the business role declared by the UE based on the authorization token of the UE, thereby avoiding mutual deception between UEs, improving the accuracy of service execution, and improving information security.

Optionally, in an embodiment of the present disclosure, the authorization token of the second UE includes at least one of the following:

The ID of the network device that generated the authorization token;

an ID of the second UE;

The conditions of the peer UE;

The service requested to be discovered by the second UE;

a service role authorized by the second UE in the service requested for discovery;

A condition for allowing execution of the service requested to be discovered by the second UE;

The validity period of the authorization token.

Optionally, in an embodiment of the present disclosure, the condition of the opposite UE includes: allowing any UE to serve as the opposite UE of the second UE, or, the condition of the opposite UE includes the service role and/or ID of the opposite UE expected by the second UE.

Receive an authorization token of the second UE sent by a network device.

Optionally, in an embodiment of the present disclosure, the transceiver module is further used for:

An authorization token of the second UE signed by the first key and sent by the network device is received.

Optionally, in an embodiment of the present disclosure, the authorization token of the first UE in the discovery request message is: the authorization token of the second UE signed by the first key;

The device is also used for:

The received authorization token of the first UE is decoded and verified using the second key.

Optionally, in an embodiment of the present disclosure, the authorization token of the second UE in the discovery response message is: the authorization token of the second UE signed by the first key.

Optionally, in an embodiment of the present disclosure, the first key is a private key of the network device, and the second key is a public key of the network device; or,

Verifying whether the execution permission condition of the service requested to be discovered in the authorization token of the first UE is met;

Verify whether the authorization token of the first UE has expired.

Please refer to Figure 5, which is a schematic diagram of the structure of a communication device 500 provided in an embodiment of the present application. The communication device 500 can be a base station, or a terminal device, or a chip, a chip system, or a processor that supports the base station to implement the above method, or a chip, a chip system, or a processor that supports the terminal device to implement the above method. The device can be used to implement the method described in the above method embodiment, and the details can be referred to the description in the above method embodiment.

The communication device 500 may include one or more processors 501. The processor 501 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process the communication protocol and communication data, and the central processing unit may be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a computer program, and process the data of the computer program.

Optionally, the communication device 500 may further include one or more memories 502, on which a computer program 504 may be stored, and the processor 501 executes the computer program 504 so that the communication device 500 performs the method described in the above method embodiment. Optionally, data may also be stored in the memory 502. The communication device 500 and the memory 502 may be provided separately or integrated together.

Optionally, the communication device 500 may further include a transceiver 505 and an antenna 506. The transceiver 505 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing a transceiver function. The transceiver 505 may include a receiver and a transmitter, the receiver may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.

Optionally, the communication device 500 may further include one or more interface circuits 507. The interface circuit 507 is used to receive code instructions and transmit them to the processor 501. The processor 501 runs the code instructions to enable the communication device 500 to perform the method described in the above method embodiment.

In one implementation, the processor 501 may include a transceiver for implementing the receiving and sending functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated. The above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

In one implementation, the processor 501 may store a computer program 503, which runs on the processor 501 and enables the communication device 500 to perform the method described in the above method embodiment. The computer program 503 may be fixed in the processor 501, in which case the processor 501 may be implemented by hardware.

In one implementation, the communication device 500 may include a circuit that can implement the functions of sending or receiving or communicating in the aforementioned method embodiments. The processor and transceiver described in the present application can be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

The communication device described in the above embodiments may be a base station or a terminal device, but the scope of the communication device described in the present application is not limited thereto, and the structure of the communication device may not be limited by FIG. 5. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

(1) Independent integrated circuit IC, or chip, or chip system or subsystem;

(2) having a set of one or more ICs, and optionally, the IC set may also include a storage component for storing data and computer programs;

(3) ASIC, such as modem;

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

(5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, base stations, cloud devices, artificial intelligence devices, etc.;

(6)Others

In the case where the communication device can be a chip or a chip system, reference can be made to the schematic diagram of the chip structure shown in Figure 6. The chip shown in Figure 6 includes a processor 601 and an interface 602. The number of the processor 601 can be one or more, and the number of the interface 602 can be multiple.

Optionally, the chip further includes a memory 603, and the memory 603 is used to store necessary computer programs and data.

Those skilled in the art may also understand that the various illustrative logical blocks and steps listed in the embodiments of the present application may be implemented by electronic hardware, computer software, or a combination of the two. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functions for each specific application, but such implementation should not be understood as exceeding the scope of protection of the embodiments of the present application.

The present application also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

A person skilled in the art may understand that the various numerical numbers such as first and second involved in the present application are only used for the convenience of description and are not used to limit the scope of the embodiments of the present application, but also indicate the order of precedence.

At least one in the present application can also be described as one or more, and a plurality can be two, three, four or more, which is not limited in the present application. In the embodiments of the present application, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no order of precedence or size between the technical features described by the "first", "second", "third", "A", "B", "C" and "D".

The corresponding relationships shown in each table in the present application can be configured or predefined. The values of the information in each table are only examples and can be configured as other values, which are not limited by the present application. When configuring the corresponding relationship between the information and each parameter, it is not necessarily required to configure all the corresponding relationships illustrated in each table. For example, in the table in the present application, the corresponding relationships shown in some rows may not be configured. For another example, appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc. The names of the parameters shown in the titles in the above tables can also use other names that can be understood by the communication device, and the values or representations of the parameters can also be other values or representations that can be understood by the communication device. When implementing the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables.

The predefined in the present application may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

A method for verifying a device service role, characterized in that it is executed by a first user equipment UE, and the method comprises:

Send a discovery request message;

receiving a discovery response message sent by the second UE, wherein the discovery response message includes an authorization token of the second UE;

After the authorization token of the second UE is verified, a connection is established with the second UE.
The method as claimed in claim 1 is characterized in that the discovery request message includes an authorization token of the first UE, and the authorization token of the first UE is used for: the second UE to verify the service role of the first UE based on the authorization token of the first UE.
The method according to claim 1 or 2, characterized in that the authorization token of the first UE includes at least one of the following:

The identification ID of the network device that generates the authorization token;

an ID of the first UE;

The conditions of the peer UE;

The service requested to be discovered by the first UE;

A service role authorized by the first UE in the service requested for discovery;

A condition for allowing execution of the service requested to be discovered by the first UE;

The validity period of the authorization token.
The method as claimed in claim 3 is characterized in that the condition of the opposite UE includes: allowing any UE to be the opposite UE of the first UE, or the condition of the opposite UE includes the service role and/or ID of the opposite UE expected by the first UE.
The method according to claim 1, characterized in that the method further comprises:

Receive an authorization token of the first UE sent by a network device.
The method according to claim 5, wherein the receiving the authorization token of the first UE sent by the network device comprises:

An authorization token of the first UE signed by the first key and sent by the network device is received.
The method as claimed in claim 2 is characterized in that the authorization token of the first UE in the discovery request message is: the authorization token of the first UE signed by the first key.
The method according to claim 1, characterized in that the authorization token of the second UE in the discovery response message is: the authorization token of the second UE signed by the first key;

The method further comprises:

The received authorization token of the second UE is decoded and verified using the second key.
The method according to claim 6, 7 or 8, characterized in that the first key is a private key of the network device, and the second key is a public key of the network device; or

The first key and the second key are both shared keys between the UE and the network device.
The method according to claim 1 or 2, characterized in that the verification of the authorization token of the second UE includes at least one of the following:

Verify whether the service role of the opposite UE expected by the second UE in the authorization token of the second UE is consistent with the service role authorized by the first UE;

Verify whether the ID of the opposite UE expected by the second UE in the authorization token of the second UE is consistent with the ID of the first UE;

Verify whether the service requested to be discovered by the second UE in the authorization token of the second UE is consistent with the service that the second UE needs to request to discover from the first UE;

Verify whether the service role authorized by the second UE in the service requested for discovery in the authorization token of the second UE is consistent with the service role declared by the second UE;

Verifying whether the execution permission condition of the service requested to be discovered in the authorization token of the second UE is met;

Verify whether the authorization token of the second UE has expired.
A method for verifying a device service role, characterized in that it is executed by a second UE, and the method comprises:

Receiving a discovery request message sent by a first UE, where the discovery request message includes an authorization token of the first UE;

When the authorization token of the first UE is verified, a discovery response message is sent to the first UE, and the discovery response message includes the authorization token of the second UE.
The method according to claim 11, wherein the authorization token of the second UE includes at least one of the following:

The ID of the network device that generated the authorization token;

an ID of the second UE;

The conditions of the peer UE;

The service requested to be discovered by the second UE;

A service role authorized by the second UE in the service requested for discovery;

A condition for allowing execution of the service requested to be discovered by the second UE;

The validity period of the authorization token.
The method as claimed in claim 12 is characterized in that the condition of the opposite UE includes: allowing any UE to be the opposite UE of the second UE, or the condition of the opposite UE includes the service role and/or ID of the opposite UE expected by the second UE.
The method according to claim 11, characterized in that the method further comprises:

Receive an authorization token of the second UE sent by a network device.
The method according to claim 14, wherein the receiving the authorization token of the second UE sent by the network device comprises:

An authorization token of the second UE signed by the first key and sent by the network device is received.
The method according to claim 11, characterized in that the authorization token of the first UE in the discovery request message is: the authorization token of the second UE signed by the first key;

The method further comprises:

The received authorization token of the first UE is decoded and verified using the second key.
The method as claimed in claim 11 is characterized in that the authorization token of the second UE in the discovery response message is: the authorization token of the second UE signed by the first key.
The method according to claim 15, 16 or 17, wherein the first key is a private key of the network device and the second key is a public key of the network device; or

The first key and the second key are both shared keys between the UE and the network device.
The method according to claim 11, wherein the verification of the authorization token of the first UE comprises at least one of the following:

Verify whether the service role of the opposite UE expected by the first UE in the authorization token of the first UE is consistent with the service role authorized by the second UE;

Verify whether the ID of the opposite UE expected by the first UE in the authorization token of the first UE is consistent with the ID of the second UE;

Verify whether the service requested to be discovered by the first UE in the authorization token of the first UE is consistent with the service that the first UE needs to request to be discovered by the second UE;

Verify whether the service role authorized by the first UE in the service requested for discovery in the authorization token of the first UE is consistent with the service role declared by the first UE;

Verifying whether the execution permission condition of the service requested to be discovered in the authorization token of the first UE is met;

Verify whether the authorization token of the first UE has expired.
A communication device, comprising:

A transceiver module, used for sending a discovery request message;

The transceiver module is further configured to receive a discovery response message sent by the second UE, wherein the discovery response message includes an authorization token of the second UE;

The processing module is also used to establish a connection with the second UE after the authorization token of the second UE is verified.
A communication device, comprising:

A transceiver module, configured to receive a discovery request message sent by a first UE, wherein the discovery request message includes an authorization token of the first UE;

The transceiver module is also used to send a discovery response message to the first UE after the authorization token of the first UE is verified, and the discovery response message includes the authorization token of the second UE.
A communication device, characterized in that the device comprises a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory so that the device performs the method as described in any one of claims 1 to 10, or the processor executes the computer program stored in the memory so that the device performs the method as described in any one of claims 11 to 19.
A communication device, comprising: a processor and an interface circuit, wherein

The interface circuit is used to receive code instructions and transmit them to the processor;

The processor is configured to execute the code instructions to perform the method according to any one of claims 1 to 10, or execute the code instructions to perform the method according to any one of claims 11 to 19.
A computer-readable storage medium for storing instructions, which, when executed, enables the method according to any one of claims 1 to 10 to be implemented, or, when executed, enables the method according to any one of claims 11 to 19 to be implemented.