CN116074829A

CN116074829A - Communication method and device

Info

Publication number: CN116074829A
Application number: CN202111277579.2A
Authority: CN
Inventors: 张冠华; 林霖; 左俊
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-10-29
Filing date: 2021-10-29
Publication date: 2023-05-05
Also published as: WO2023071926A1

Abstract

The application provides a communication method and device for relieving privacy disturbance caused by number leakage. The method comprises the following steps: receiving a communication request message, wherein the communication request message comprises an additional communication identifier corresponding to communication authorization information, the communication authorization information characterizes a communication service which is authorized by a user and is directed to the additional communication identifier and corresponds to the additional communication identifier, and the communication authorization information comprises one or more of the following: the time range in which the point in time of initiation of the authorized communication service should be, the location range in which the initiator of the authorized communication service should be, the authentication code that the initiator of the authorized communication service should provide, the order number that the initiator of the authorized communication service should be associated with, and the device type that the initiator of the authorized communication service should be.

Description

Communication method and device

Technical Field

The present disclosure relates to the field of communications, and in particular, to a communication method and apparatus.

Background

With the development of social civilization, many situations of privacy leakage occur, so that the protection of privacy is more widely focused.

Telephone numbers are special privacy, users can choose to inform others of own telephone numbers to maintain communication between people, but do not want the own telephone numbers to be randomly spread, thereby causing the consequences of fraud telephones, various promotion advertisements, spam messages, and the like.

How to alleviate the privacy disturbance problem caused by the random spread of telephone numbers is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a communication method and device, which can relieve privacy disturbance caused by random propagation of an additional communication identifier (such as a telephone number) by communicating based on the additional communication identifier corresponding to communication authorization information.

In a first aspect, a communication method is provided, which may be performed by a communication server, or may also be performed by a component (e.g., a chip or a circuit) of the communication server, which is not limited, and for convenience of description, an example will be described below as being performed by the communication server.

The method may include: the communication server receives a communication request message, wherein the communication request message comprises an additional communication identifier of a target user, the additional communication identifier corresponds to communication authorization information set by the target user, and the communication authorization information is used for representing communication services authorized by the target user and directed to the additional communication identifier; the communication server releases or refuses the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identifier according to the communication authorization information; wherein the communication authorization information includes one or more of the following: the time range in which the point in time of initiation of the authorized communication service should be, the location range in which the initiator of the authorized communication service should be, the authentication code that the initiator of the authorized communication service should provide, the order number that the initiator of the authorized communication service should be associated with, and the device type that the initiator of the authorized communication service should be.

Based on the above technical solution, when the initiator requests to execute the communication service pointing to the additional communication identifier, the additional communication identifier may be carried in the communication request message, and the communication server performs verification (or referred to as detection or referred to as authorization) according to the communication authorization information corresponding to the additional communication identifier, and determines to release or reject the communication service requested to be executed by the communication request message according to the verification result. Therefore, the privacy disturbance problem caused by the leakage of the additional communication identification can be relieved. Taking the call service as an example, when the first device requests to call the second device, the communication request message may carry an additional communication identifier of the second device, and the communication server performs verification according to communication authorization information corresponding to the additional communication identifier, and triggers the first device to establish call connection with the second device according to the verification result, or rejects the call request of the first device according to the verification result. Thus, not only the privacy disturbance problem in the B2C scene, such as that the marketing/service call of an enterprise may disturb the privacy of a customer and be complained by the customer, but also the privacy disturbance problem in the C2C scene, such as that a person directly calls other people and may disturb the privacy of other people, and the problem that the privacy is disturbed due to the fact that the person registers own telephone number outside and the number is leaked, can be relieved.

With reference to the first aspect, in certain implementation manners of the first aspect, the communication server, according to the communication authorization information, puts through or refuses a communication service that is requested to be executed by the communication request message and is directed to the additional communication identifier, includes: the communication server determines that the communication service requested to be executed by the communication request message belongs to the communication service which is authorized by the target user and is pointed to the additional communication identifier according to the communication authorization information, and the communication server releases the communication service requested to be executed by the communication request message and is pointed to the additional communication identifier; and/or the communication server determines that the communication service requested to be executed by the communication request message does not belong to the communication service which is authorized by the target user and is directed to the additional communication identifier according to the communication authorization information, and the communication server refuses the communication service requested to be executed by the communication request message and is directed to the additional communication identifier.

The communication service requested to be executed by the communication request message belongs to the communication service authorized by the target user and directed to the additional communication identifier, namely the communication service requested to be executed by the communication request message meets the requirement of the communication service authorized by the target user and directed to the additional communication identifier.

For example, the communication service requested to be executed by the communication request message does not belong to the communication service authorized by the target user and directed to the additional communication identifier, that is, it means that the communication service requested to be executed by the communication request message does not satisfy the requirement of the communication service authorized by the target user and directed to the additional communication identifier.

With reference to the first aspect, in certain implementation manners of the first aspect, the communicating server, according to the communication authorization information, releases a communication service that is requested to be performed by the communication request message and is directed to the additional communication identifier, including: the communication server obtains the position of the initiator of the communication request message, and determines that the position of the initiator of the communication request message is in the position range where the initiator of the communication request message should be, and the communication server releases the communication service which is requested to be executed by the communication request message and points to the additional communication identifier.

With reference to the first aspect, in certain implementation manners of the first aspect, the communication server acquires an initiation time of the communication request message, determines that the initiation time is within the time range that should be in, and releases the communication service that is requested to be executed by the communication request message and is directed to the additional communication identifier.

With reference to the first aspect, in some implementation manners of the first aspect, the communication server acquires an authentication code carried in the communication request message, determines that the authentication code is the authentication code that should be provided, and releases the communication service that is requested to be executed by the communication request message and is directed to the additional communication identifier.

With reference to the first aspect, in certain implementation manners of the first aspect, the communication server acquires an order number associated with an initiator of the communication request message, determines the order number to be associated, and releases a communication service which is requested to be executed by the communication request message and is directed to the additional communication identifier.

With reference to the first aspect, in certain implementation manners of the first aspect, the communication server acquires a device type of an initiator of the communication request message, determines the device type as the due device type, and releases a communication service that is requested to be performed by the communication request message and is directed to the additional communication identifier.

With reference to the first aspect, in certain implementation manners of the first aspect, the communication authorization information further includes an initiator identifier that an initiator of the authorized communication service should have; the communication server obtains the identifier of the initiator of the communication request message, determines the identifier of the initiator as the due initiator identifier, and releases the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identifier.

With reference to the first aspect, in certain implementation manners of the first aspect, the method further includes: the communication server receives a first message from a terminal device corresponding to the additional communication identifier, wherein the first message comprises the communication authorization information; the communication server stores the corresponding relation between the communication authorization information and the additional communication identifier.

Based on the above scheme, the communication server can determine the corresponding communication authorization information according to the additional communication identifier carried in the communication request message.

With reference to the first aspect, in certain implementation manners of the first aspect, before the communication server puts through or refuses the communication service that is requested to be performed by the communication request message and is directed to the additional communication identifier according to the communication authorization information, the method further includes: and the communication server acquires the communication authorization information according to the additional communication identifier.

With reference to the first aspect, in certain implementations of the first aspect, the communication request message further includes a ciphertext of the communication authorization information, or the communication request message further includes a plaintext of the communication authorization information and a digital signature regarding the communication authorization information.

For example, regarding the digital signature of the communication authorization information, the device of the target user may digitally sign the communication authorization information, or may digitally sign the communication authorization information by the communication server.

Based on the scheme, the occurrence of tampering of the communication authorization information can be reduced or even relieved, and the safety of communication is improved.

With reference to the first aspect, in certain implementation manners of the first aspect, the method further includes: and the communication server sends the communication authorization information to the terminal equipment corresponding to the additional communication identifier.

Based on the above scheme, the communication server can generate the communication authorization information corresponding to the additional communication identifier and send the communication authorization information to the device corresponding to the additional communication identifier.

With reference to the first aspect, in certain implementation manners of the first aspect, before the communication server sends the communication authorization information to the terminal device corresponding to the additional communication identifier, the method further includes: the communication server receives a second message from the terminal equipment corresponding to the additional communication identifier, wherein the second message comprises authorization requirement information; the communication server generates the communication authorization information based on the authorization requirement information; the authorization requirement information is used for representing communication authorization information required by the target user.

Based on the above scheme, the communication server may generate the communication authorization information based on the information provided by the device corresponding to the additional communication identifier.

With reference to the first aspect, in certain implementations of the first aspect, the additional communication identifier is an additional number of the target user.

With reference to the first aspect, in certain implementation manners of the first aspect, the method further includes: and the communication server generates the additional communication identifier and transmits the additional communication identifier to the terminal equipment corresponding to the additional communication identifier.

Based on the scheme, the communication server can generate the additional communication identification and send the additional communication identification to the device corresponding to the additional communication identification, so that the device corresponding to the additional communication identification can provide the additional communication identification for other devices.

With reference to the first aspect, in certain implementation manners of the first aspect, the communication request message further includes an identifier that identifies an authorizer, where the identifier of the authorizer corresponds to identifier authorization information, where the identifier authorization information is used to characterize: the identification authority authorizes the initiator of the communication request message, takes the identification of the identification authority as the initiator identification, and initiates the communication service pointing to the additional communication identification.

Illustratively, identifying the authorizer may represent authorizing the sponsor to identify the authorizer as the sponsor, initiate organization (organization) or person (organization) directed to the target user; alternatively, identifying the authorizer may represent authorizing the sponsor to an organization or individual having the identification of the authorizer as the sponsor identification, initiating additional communication identification directed to the target user (or additional communication identification of the target user).

Based on the above scheme, the initiator may initiate the communication request message using the identity of the third party (i.e., identifying the authorizer).

In a second aspect, a communication method is provided, which may be performed by a terminal device, or may also be performed by a component (e.g., a chip or a circuit) of the terminal device, which is not limited, and for convenience of description, will be described below with reference to the embodiment performed by the terminal device.

The method may include: the terminal equipment acquires an additional communication identifier of a target user, wherein the additional communication identifier corresponds to communication authorization information set by the target user, and the communication authorization information is used for representing communication services authorized by the target user and pointing to the additional communication identifier; the terminal equipment sends a communication request message to a communication server, wherein the communication request message comprises the additional communication identifier; wherein the communication authorization information includes one or more of the following: the time range in which the point in time of initiation of the authorized communication service should be, the location range in which the initiator of the authorized communication service should be, the authentication code that the initiator of the authorized communication service should provide, the order number that the initiator of the authorized communication service should be associated with, and the device type that the initiator of the authorized communication service should be.

With reference to the second aspect, in certain implementation manners of the second aspect, the communication request message further includes a verification code, where the verification code is received by the terminal device, or the verification code is pre-agreed.

With reference to the second aspect, in certain implementations of the second aspect, the communication request message further includes a ciphertext of the communication authorization information, or the communication request message further includes a plaintext of the communication authorization information and a digital signature regarding the communication authorization information.

With reference to the second aspect, in some implementations of the second aspect, the obtaining, by the terminal device, an additional communication identifier corresponding to the communication authorization information includes: the terminal equipment scans the two-dimensional code, and acquires the additional communication identifier and the communication authorization information from the two-dimensional code.

With reference to the second aspect, in certain implementations of the second aspect, the additional communication is identified as an additional number of the target user.

With reference to the second aspect, in certain implementation manners of the second aspect, the communication request message further includes an identifier that identifies an authorizer, where the identifier corresponds to identifier authorization information, where the identifier authorization information is used to characterize: the identification authority authorizes the initiator of the communication request message, takes the identification of the identification authority as the initiator identification, and initiates the communication service pointing to the additional communication identification.

In a third aspect, a communication method is provided, which may be performed by a terminal device, or may also be performed by a component (e.g., a chip or a circuit) of the terminal device, which is not limited, and for convenience of description, an example of the method performed by the terminal device will be described below.

The method may include: the terminal equipment acquires an additional communication identifier of a target user, wherein the additional communication identifier corresponds to communication authorization information set by the target user, and the communication authorization information is used for representing communication services authorized by the target user and pointing to the additional communication identifier; the terminal equipment provides the additional communication identification to one or more other terminal equipment; wherein the communication authorization information includes one or more of the following: the time range in which the point in time of initiation of the authorized communication service should be, the location range in which the initiator of the authorized communication service should be, the authentication code that the initiator of the authorized communication service should provide, the order number that the initiator of the authorized communication service should be associated with, and the device type that the initiator of the authorized communication service should be.

With reference to the third aspect, in some implementations of the third aspect, the obtaining, by the terminal device, an additional communication identifier includes: the terminal equipment generates the additional communication identifier; alternatively, the terminal device receives the additional communication identity from a communication server.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the terminal device sends a first message to a communication server, wherein the first message comprises the communication authorization information.

With reference to the third aspect, in certain implementations of the third aspect, the providing, by the terminal device, the additional communication identifier to one or more other terminal devices includes: the terminal device provides the additional communication identity and the communication authorization information to the one or more other terminal devices.

With reference to the third aspect, in certain implementations of the third aspect, the providing, by the terminal device, the additional communication identifier and the communication authorization information to one or more other terminal devices includes: the terminal equipment sends the additional communication identification and the ciphertext of the communication authorization information to the one or more other terminal equipment; or the terminal device sends the additional communication identifier, the plaintext of the communication authorization information and the digital signature related to the communication authorization information to the one or more other terminal devices.

With reference to the third aspect, in certain implementations of the third aspect, before the terminal device provides the additional communication identifier and the communication authorization information to one or more other terminal devices, the method further includes: the terminal equipment sends a second message to the communication server, wherein the second message comprises authorization requirement information; the terminal device receives the communication authorization information from the communication server, wherein the communication authorization information is generated based on the authorization requirement information; the authorization requirement information is used for representing communication authorization information required by the target user.

With reference to the third aspect, in certain implementations of the third aspect, the terminal device generates communication authorization information.

With reference to the third aspect, in certain implementations of the third aspect, the providing, by the terminal device, the additional communication identifier and the communication authorization information to one or more other terminal devices includes: the terminal equipment encodes the additional communication identifier and the communication authorization information into a two-dimensional code; the terminal equipment displays the two-dimension code for the one or more other terminal equipment to scan, so that the one or more other terminal equipment obtains the additional communication identification and the communication authorization information.

With reference to the third aspect, in certain implementations of the third aspect, the two-dimensional code includes signature information, where the signature information includes: and digitally signing the communication authorization information or the additional communication identifier and the communication authorization information.

In a fourth aspect, a communication method is provided, which may be performed by a communication server, or may also be performed by a component (e.g., a chip or a circuit) of the communication server, which is not limited, and for convenience of description, an example will be described below as being performed by the communication server.

The method may include: the communication server receives a communication request message, wherein the communication request message comprises an additional communication identifier corresponding to communication authorization information, the communication authorization information is used for representing a communication service authorized by a target user and pointing to the additional communication identifier, and the target user is a user corresponding to the additional communication identifier; and the communication server releases or refuses the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identifier according to the communication authorization information.

Illustratively, the communication request message includes an additional communication identifier corresponding to the communication authorization information, including: the communication request message comprises an additional communication identifier of the target user, wherein the additional communication identifier corresponds to the communication authorization information set by the target user.

Illustratively, the target user is associated with at least one user identification module that is associated with at least one additional communication identity. Optionally, the subscriber identity module may also associate one or more underlying communication identities.

In one possible implementation, the method may include: the communication server receives a communication request message, wherein the communication request message comprises an additional communication identifier of a target user, the additional communication identifier and a basic communication identifier are commonly associated to a user identification module of the target user, and the additional communication identifier corresponds to communication authorization information which is used for representing a communication service authorized by the target user and directed to the additional communication identifier; and the communication server releases or refuses the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identifier according to the communication authorization information. In this case, the "communication service directed to the additional communication identifier" may be replaced by "communication service directed to the subscriber identity module", for example, in view of the fact that the additional communication identifier is associated to the subscriber identity module of the target subscriber.

In yet another possible implementation, the method may include: the communication server receives a communication request message, wherein the communication request message comprises an additional communication identifier of a target user; the communication server determines the additional communication identifier as an additional communication identifier, the additional communication identifier corresponds to communication authorization information set by a target user, the additional communication identifier and a basic communication identifier of the target user are commonly associated to a user identification module of the target user, and the communication authorization information is used for representing communication services authorized by the target user and directed to the additional communication identifier; and the communication server releases or refuses the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identifier according to the communication authorization information. In this case, the "communication service directed to the additional communication identifier" may be replaced by "communication service directed to the subscriber identity module", for example, in view of the fact that the additional communication identifier is associated to the subscriber identity module of the target subscriber.

Based on the above technical solution, when the initiator requests to execute the communication service pointing to the additional communication identifier, the additional communication identifier may be carried in the communication request message, and the communication server performs verification (or referred to as detection or referred to as authorization) according to the communication authorization information corresponding to the additional communication identifier, and determines to release or reject the communication service requested to be executed by the communication request message according to the verification result. Therefore, the privacy disturbance problem caused by the leakage of the additional communication identification can be relieved. Taking the call service as an example, when the first device requests to call the second device, the communication request message may carry the number (such as an authorized ID, and also such as a basic number) of the second device, and the communication server performs verification according to the communication authorization information corresponding to the number, and triggers the first device to establish call connection with the second device according to the verification result, or refuses the call request of the first device according to the verification result. Thus, not only the privacy disturbance problem in the B2C scene, such as that the marketing/service call of an enterprise may disturb the privacy of a customer and be complained by the customer, but also the privacy disturbance problem in the C2C scene, such as that a person directly calls other people and may disturb the privacy of other people, and the problem that the privacy is disturbed due to the fact that the person registers own telephone number outside and the number is leaked, can be relieved.

With reference to the fourth aspect, in some implementations of the fourth aspect, the communication server, according to the communication authorization information, puts through or rejects a communication service that is requested to be performed by the communication request message and is directed to the additional communication identifier, includes: the communication server determines that the communication service requested to be executed by the communication request message belongs to the communication service which is authorized by the target user and is pointed to the additional communication identifier according to the communication authorization information, and the communication server releases the communication service requested to be executed by the communication request message and is pointed to the additional communication identifier; and/or the communication server determines that the communication service requested to be executed by the communication request message does not belong to the communication service which is authorized by the target user and is directed to the additional communication identifier according to the communication authorization information, and the communication server refuses the communication service requested to be executed by the communication request message and is directed to the additional communication identifier.

With reference to the fourth aspect, in certain implementations of the fourth aspect, before the communication server receives the communication request message, the method further includes: the communication server receives a first message from a terminal device corresponding to the additional communication identifier, wherein the first message comprises the communication authorization information; the communication server stores the corresponding relation between the communication authorization information and the additional communication identifier.

With reference to the fourth aspect, in some implementations of the fourth aspect, before the communication server puts through or rejects the communication service directed to the additional communication identifier, which is requested to be performed by the communication request message, according to the communication authorization information, the method further includes: and the communication server acquires the communication authorization information according to the additional communication identifier.

With reference to the fourth aspect, in some implementations of the fourth aspect, the communication request message further includes a ciphertext of the communication authorization information, or the communication request message further includes a plaintext of the communication authorization information and a digital signature regarding the communication authorization information.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: and the communication server sends the communication authorization information to the terminal equipment corresponding to the additional communication identifier.

With reference to the fourth aspect, in some implementations of the fourth aspect, before the communication server sends the communication authorization information to the terminal device corresponding to the additional communication identifier, the method further includes: the communication server receives a second message from the terminal equipment corresponding to the additional communication identifier, wherein the second message comprises authorization requirement information; the communication server generates the communication authorization information based on the authorization requirement information; the authorization requirement information is used for representing communication authorization information required by the target user.

With reference to the fourth aspect, in some implementations of the fourth aspect, the additional communication is identified as an additional number of the target user.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: and the communication server generates the additional communication identifier and transmits the additional communication identifier to the terminal equipment corresponding to the additional communication identifier.

With reference to the fourth aspect, in certain implementation manners of the fourth aspect, the communication request message further includes an identifier identifying an authorizer, where the identifier identifying the authorizer corresponds to identifier authorization information, where the identifier authorization information is used to characterize: the identification authority authorizes the initiator of the communication request message, takes the identification of the identification authority as the initiator identification, and initiates the communication service pointing to the additional communication identification.

In a fifth aspect, a communication method is provided, which may be performed by a terminal device, or may also be performed by a component (e.g., a chip or a circuit) of the terminal device, which is not limited, and for convenience of description, will be described below with reference to the embodiment performed by the terminal device.

The method may include: the terminal equipment acquires an additional communication identifier corresponding to communication authorization information, wherein the communication authorization information is used for representing a communication service authorized by a target user and pointing to the additional communication identifier, and the target user is a user corresponding to the additional communication identifier; the terminal device sends a communication request message to a communication server, wherein the communication request message comprises the additional communication identifier.

The terminal device obtains an additional communication identifier corresponding to the communication authorization information, which includes: the terminal equipment acquires an additional communication identifier of a target user, wherein the additional communication identifier corresponds to communication authorization information set by the target user.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the communication request message further includes a ciphertext of the communication authorization information, or the communication request message further includes a plaintext of the communication authorization information and a digital signature regarding the communication authorization information.

With reference to the fifth aspect, in some implementations of the fifth aspect, the obtaining, by the terminal device, an additional communication identifier corresponding to the communication authorization information includes: the terminal equipment scans the two-dimensional code, and acquires the additional communication identifier and the communication authorization information from the two-dimensional code.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the additional communication is identified as an additional number of the target user.

With reference to the fifth aspect, in certain implementation manners of the fifth aspect, the communication request message further includes an identifier that identifies an authorizer, where the identifier corresponds to identifier authorization information, where the identifier authorization information is used to characterize: the identification authority authorizes the initiator of the communication request message, takes the identification of the identification authority as the initiator identification, and initiates the communication service pointing to the additional communication identification.

In a sixth aspect, a communication method is provided, which may be performed by a terminal device, or may also be performed by a component (e.g., a chip or a circuit) of the terminal device, which is not limited, and for convenience of description, will be described below with reference to the embodiment performed by the terminal device.

The method may include: the terminal equipment acquires an additional communication identifier corresponding to communication authorization information, wherein the communication authorization information is used for representing a communication service authorized by a target user and pointing to the additional communication identifier, and the target user is a user corresponding to the additional communication identifier; the terminal device provides the additional communication identity to one or more other terminal devices.

Illustratively, the target user is associated with at least one user identification module that is associated with at least one additional communication identity. Optionally, the target user may also associate one or more underlying communication identities.

With reference to the sixth aspect, in some implementations of the sixth aspect, the obtaining, by the terminal device, an additional communication identifier includes: the terminal equipment generates the additional communication identifier; alternatively, the terminal device receives the additional communication identity from a communication server.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the method further includes: the terminal device sends a first message to a communication server, wherein the first message comprises the communication authorization information.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the providing, by the terminal device, the additional communication identifier to one or more other terminal devices includes: the terminal device provides the additional communication identity and the communication authorization information to the one or more other terminal devices.

With reference to the sixth aspect, in certain implementation manners of the sixth aspect, the providing, by the terminal device, the additional communication identifier and the communication authorization information to one or more other terminal devices includes: the terminal equipment sends the additional communication identification and the ciphertext of the communication authorization information to the one or more other terminal equipment; or the terminal device sends the additional communication identifier, the plaintext of the communication authorization information and the digital signature related to the communication authorization information to the one or more other terminal devices.

With reference to the sixth aspect, in certain implementation manners of the sixth aspect, before the terminal device provides the additional communication identifier and the communication authorization information to one or more other terminal devices, the method further includes: the terminal equipment sends a second message to the communication server, wherein the second message comprises authorization requirement information; the terminal device receives the communication authorization information from the communication server, wherein the communication authorization information is generated based on the authorization requirement information; the authorization requirement information is used for representing communication authorization information required by the target user.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the terminal device generates communication authorization information.

With reference to the sixth aspect, in certain implementation manners of the sixth aspect, the providing, by the terminal device, the additional communication identifier and the communication authorization information to one or more other terminal devices includes: the terminal equipment encodes the additional communication identifier and the communication authorization information into a two-dimensional code; the terminal equipment displays the two-dimension code for the one or more other terminal equipment to scan, so that the one or more other terminal equipment obtains the additional communication identification and the communication authorization information.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the two-dimensional code includes signature information, where the signature information includes: and digitally signing the communication authorization information or the additional communication identifier and the communication authorization information.

In a seventh aspect, a communication method is provided, which may be executed by an application server, or may be executed by a component (e.g., a chip or a circuit) of the application server, which is not limited, and for convenience of description, an example will be described below as being executed by the application server.

The method may include: the application server determines identification authorization information, wherein the identification authorization information is used for representing: the identification authorizer authorizes the initiator of the communication request message, takes the identification of the identification authorizer as the identification of the initiator, and initiates the communication service pointing to the target user; the application server sends a request message to the communication server, wherein the request message comprises the identification authorization information.

With reference to the seventh aspect, in certain implementation manners of the seventh aspect, the identification authorization information includes authorization information corresponding to an identification of the identification authorizer.

With reference to the seventh aspect, in certain implementations of the seventh aspect, the identification authorization information includes an identification of the identification authorizer and/or an identification of the initiator.

With reference to the seventh aspect, in certain implementations of the seventh aspect, the identification authorization information further includes an additional communication identification of the target user, and the identification authorization information is used to characterize: the identification authority authorizes the initiator of the communication request message, takes the identification of the identification authority as the initiator identification, and initiates the communication service pointing to the additional communication identification.

In an eighth aspect, a communication method is provided, which may be performed by a communication server, or may also be performed by a component (e.g., a chip or a circuit) of the communication server, which is not limited, and for convenience of description, an example will be described below as being performed by the communication server.

The method may include: the communication server receives a request message from an application server, the request message including identification authorization information, the identification authorization information being used to characterize: the identification authorizer authorizes the initiator of the communication request message, takes the identification of the identification authorizer as the identification of the initiator, and initiates the communication service pointing to the target user; the communication server stores the identification authorization information.

Wherein the target user is associated with at least one user identification module, the user identification module being associated with at least one additional communication identity. Optionally, the subscriber identity module may also associate one or more underlying communication identities.

With reference to the eighth aspect, in some implementation manners of the eighth aspect, the identification authorization information includes authorization information corresponding to an identification of the identification authorized party, and the communication server stores the identification authorization information, including: the communication server stores the corresponding relation between the identification authorization information and the identification of the identification authorized party.

With reference to the eighth aspect, in certain implementations of the eighth aspect, the identification authorization information includes an identification of the identification authorized party and/or an identification of the initiator.

With reference to the eighth aspect, in certain implementations of the eighth aspect, the method further includes: the communication server receives the communication request message, wherein the communication request message comprises the identification of the identification authorized party; and the communication server releases or refuses the communication service requested to be executed by the communication request message according to the identification authorization information.

With reference to the eighth aspect, in certain implementation manners of the eighth aspect, the identification authorization information further includes an additional communication identification of the target user, and the identification authorization information is used to characterize: the identification authority authorizes an initiator of the communication request message, takes an identification of the identification authority as an initiator identification, initiates communication service pointing to the additional communication identification, and the at least one additional communication identification comprises the additional communication identification.

With reference to the fourth aspect to the eighth aspect, in certain implementations, the communication authorization information includes one or more of the following information: the time range in which the point in time of initiation of the authorized communication service should be, the location range in which the initiator of the authorized communication service should be, the authentication code that the initiator of the authorized communication service should provide, the order number that the initiator of the authorized communication service should be associated with, and the device type that the initiator of the authorized communication service should be.

With reference to the first to eighth aspects, in certain implementations, the communication server includes one or more of: the service-call session control function S-CSCF device, the application server AS, and the authorised communication light application server.

A ninth aspect provides a communication apparatus for performing the method of any one of the possible implementations of the first to eighth aspects. In particular, the apparatus may comprise means and/or modules, such as a processing unit and/or a communication unit, for performing the method in any of the possible implementations of the first to eighth aspects.

In one implementation, the apparatus is a communication device (e.g., a terminal device or a network device (e.g., an application server or a communication server)). When the apparatus is a communication device, the communication unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.

In another implementation, the apparatus is a chip, a system-on-chip, or a circuit for a communication device, such as a terminal device or a network device (e.g., an application server or a communication server). When the apparatus is a chip, a system-on-chip or a circuit for a communication device, the communication unit may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit, etc. on the chip, the system-on-chip or the circuit; the processing unit may be at least one processor, processing circuit or logic circuit, etc.

In a tenth aspect, there is provided an apparatus for communication, the apparatus comprising: at least one processor configured to execute a computer program or instructions stored in a memory to perform a method according to any one of the possible implementations of the first, fourth, or eighth aspects. Optionally, the apparatus further comprises a memory for storing a computer program or instructions. Optionally, the apparatus further comprises a communication interface through which the processor reads the computer program or instructions stored in the memory.

In one implementation, the apparatus is a communication server.

In another implementation, the apparatus is a chip, a system-on-chip, or a circuit for a communication server.

In an eleventh aspect, there is provided an apparatus for communication, the apparatus comprising: at least one processor configured to execute a computer program or instructions stored in a memory to perform the method according to any one of the possible implementations of the second, third, fifth, or sixth aspects described above. Optionally, the apparatus further comprises a memory for storing a computer program or instructions. Optionally, the apparatus further comprises a communication interface through which the processor reads the computer program or instructions stored in the memory.

In one implementation, the apparatus is a terminal device.

In another implementation, the apparatus is a chip, a system-on-chip or a circuit for a terminal device.

In a twelfth aspect, there is provided an apparatus for communication, the apparatus comprising: at least one processor configured to execute a computer program or instructions stored in a memory to perform a method according to any one of the possible implementations of the seventh aspect. Optionally, the apparatus further comprises a memory for storing a computer program or instructions. Optionally, the apparatus further comprises a communication interface through which the processor reads the computer program or instructions stored in the memory.

In one implementation, the apparatus applies a server.

In another implementation, the apparatus is a chip, a system-on-chip, or a circuit for an application server.

In a thirteenth aspect, a processor is provided for performing the method provided in the above aspects.

The operations such as transmitting and acquiring/receiving, etc. related to the processor may be understood as operations such as outputting and receiving, inputting, etc. by the processor, or may be understood as operations such as transmitting and receiving by the radio frequency circuit and the antenna, if not specifically stated, or if not contradicted by actual function or inherent logic in the related description, which is not limited in this application.

In a fourteenth aspect, a computer readable storage medium is provided, the computer readable medium storing program code for execution by a device, the program code comprising instructions for performing the method of any one of the possible implementations of the first to eighth aspects.

In a fifteenth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any one of the possible implementations of the first to eighth aspects described above.

In a sixteenth aspect, a communication system is provided, comprising one or more of the aforementioned terminal device, application server, communication server.

Drawings

Fig. 1 is a schematic diagram of a communication system suitable for use in embodiments of the present application.

Fig. 2 is a schematic diagram of a relationship between a base number and an authorized ID provided in an embodiment of the present application.

Fig. 3 is yet another illustration of the relationship between base numbers and authorization IDs provided by embodiments of the present application.

Fig. 4 is a schematic diagram of an authorization code provided in an embodiment of the present application.

Fig. 5 is a schematic diagram of call authorization provided in an embodiment of the present application.

Fig. 6 is a schematic diagram of a call authorization table according to an embodiment of the present application.

Fig. 7 is a schematic diagram of a callback call according to an embodiment of the present application.

Fig. 8 is a schematic diagram of identification authorization provided in an embodiment of the present application.

Fig. 9 is a further schematic diagram of identification authorization provided by an embodiment of the present application.

Fig. 10 is a schematic diagram of an identification authorization table provided in an embodiment of the present application.

Fig. 11 is a further schematic diagram of an identification authorization table provided in an embodiment of the present application.

Fig. 12 is a schematic diagram of an individual user automatically issuing an authorization ID or authorization code according to an embodiment of the present application.

Fig. 13 is a schematic diagram of a personal user manually issuing an authorization ID or an authorization code according to an embodiment of the present application.

Fig. 14 is a further schematic diagram of a personal user manually issuing an authorization ID or authorization code provided in an embodiment of the present application.

Fig. 15 is a schematic diagram of direct generation of an authorization code by a terminal device according to an embodiment of the present application.

Fig. 16 is a schematic diagram of person-to-person exchanging authorization codes provided by embodiments of the present application.

Fig. 17 is a schematic diagram of a communication method 1700 provided in an embodiment of the present application.

Fig. 18 is a schematic diagram of communication based on additional communication identification according to an embodiment of the present application.

Fig. 19 is a schematic diagram applicable to scheme 1 provided in an embodiment of the present application.

Fig. 20 is a schematic diagram applicable to scheme 2 provided in an embodiment of the present application.

Fig. 21 is a schematic diagram of a communication method 2100 provided in an embodiment of the present application.

Fig. 22 is a schematic flow chart diagram of a communication method 2200 provided by an embodiment of the present application.

Fig. 23 is a schematic flow chart diagram of a communication method 2300 provided by an embodiment of the application.

Fig. 24 is a schematic flow chart of a communication method 2400 provided in an embodiment of the present application.

Fig. 25 is a schematic flow chart of a communication method 2500 provided in an embodiment of the present application.

Fig. 26 is a schematic flow chart of a communication method 2600 provided in an embodiment of the present application.

Fig. 27 is a schematic flow chart of a communication method 2700 provided in an embodiment of the present application.

Fig. 28 is a schematic flow chart of a communication method 2800 provided in an embodiment of the present application.

Fig. 29 is a schematic flow chart diagram of a communication method 2900 provided by an embodiment of the present application.

Fig. 30 is a schematic flow chart of a communication method 3000 provided in an embodiment of the present application.

Fig. 31 is a schematic flow chart of a communication method 3100 provided in an embodiment of the present application.

Fig. 32 is a schematic flow chart of a communication method 3200 provided in an embodiment of the present application.

Fig. 33 is a schematic flow chart of a communication method 3300 provided in an embodiment of the present application.

Fig. 34 is a schematic diagram of a communication device 3400 according to an embodiment of the present application.

Fig. 35 is a schematic diagram of another communication device 3500 provided in an embodiment of the application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

The technical solution of the embodiment of the application can be applied to various communication systems, for example: fifth generation (5th generation,5G) or New Radio (NR) systems, long term evolution (long term evolution, LTE) systems, LTE frequency division duplex (frequency division duplex, FDD) systems, LTE time division duplex (time division duplex, TDD) systems, and the like. The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system. The technical solutions provided herein may also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (machine to machine, M2M) communication, machine type communication (machine type communication, MTC), and internet of things (internet of things, ioT) communication systems or other communication systems.

The terminal device in the embodiments of the present application may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment.

The terminal device may be a device that provides voice/data to a user, e.g., a handheld device with wireless connection, an in-vehicle device, etc. Currently, some examples of terminals are: a mobile phone, tablet, laptop, palmtop, mobile internet device (mobile internet device, MID), wearable device, virtual Reality (VR) device, augmented reality (augmented reality, AR) device, wireless terminal in industrial control (industrial control), wireless terminal in unmanned (self driving), wireless terminal in teleoperation (remote medical surgery), wireless terminal in smart grid (smart grid), wireless terminal in transportation security (transportation safety), wireless terminal in smart city (smart city), wireless terminal in smart home (smart home), cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with wireless communication function, computing device or other processing device connected to wireless modem, wearable device, terminal device in 5G network or terminal in future evolved land mobile communication network (public land mobile network), and the like, without limiting the present application.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In the embodiment of the present application, the device for implementing the function of the terminal device may be the terminal device, or may be a device capable of supporting the terminal device to implement the function, for example, a chip system or a chip, and the device may be installed in the terminal device. In the embodiment of the application, the chip system may be formed by a chip, and may also include a chip and other discrete devices.

The network device (e.g., a communication server) in the embodiments of the present application may be a device for communicating with a terminal device. As an example, the network device may be, for example, a device in a communication network for providing services to terminal devices. The network device may include, for example, one or more of the following: service-call session control function (S-CSCF), application server (application server, AS) (e.g. authorization management service AS), authorization communication light application server. In this application, the authorization management service AS may be used to process communication authorization information, for example, and may include, but is not limited to: storing the communication authorization, generating ciphertext of the communication authorization information, adding a digital signature on the communication authorization information, verifying the authorization (e.g., querying the communication authorization information), and so forth. As an example, the S-CSCF may be used to receive a communication request message from a sender. AS an example, the authorization communication light application server may be configured to receive and/or transmit communication authorization information, such AS communication authorization information provided by an authorized party, and such AS communication authorization information provided by an authorized party to the authorization management service AS. The above is an exemplary illustration, and embodiments of the present application are not limited thereto.

Hereinafter, for convenience of description, a communication server is collectively referred to.

Reference is made herein to a "communication network" for a number of times, and it is to be understood that the communication network described herein may include an operator IP multimedia subsystem (IP multimedia subsystem, IMS) network, may include a set-up communication network (e.g., a communication network set up for "instant messaging software"), or may include other communication networks, without limitation. In addition, the communication network and the communication server are sometimes used interchangeably hereinafter, and are used for network devices that serve communication devices (such as terminal devices) unless otherwise specifically described.

To facilitate an understanding of the embodiments of the present application, a communication system suitable for use in the embodiments of the present application will be described in detail with reference to fig. 1.

Fig. 1 shows a schematic diagram of a communication system suitable for use in embodiments of the present application. As shown in fig. 1, the communication system may include one or more terminal devices, such as terminal device 111 and terminal device 112 shown in fig. 1. The communication system may also include one or more network devices, such as the communication server 120 shown in fig. 1. The terminal equipment can communicate with each other, and the terminal equipment and the network equipment can also communicate with each other. For example, terminal device 111 may establish a call connection with terminal device 112 through communication server 120.

It should be understood that fig. 1 is a simplified schematic diagram merely illustrated for ease of understanding, and the present application is not limited thereto. The embodiment of the application can be applied to any communication scene of communication between the sending end equipment and the receiving end equipment.

In recent years, various nuisance calls are forbidden and not overruled, and people are not tired. In the prior art, a user can register own numbers in a database to indicate that marketing-type telephones, short messages and the like are not expected to be received; the enterprise can go to the database for inquiry before calling or sending the marketing information, so that the marketing calling, the marketing short message sending and the like are not initiated to the numbers in the database.

However, this approach also creates problems such as the possibility of missing a marketing phone that is actually associated with the user after registration; as another example, this approach is mainly concerned with privacy intrusion in business-to-consumer (B2C) scenarios, and not with personal-to-personal (C2C) scenarios.

The present application proposes a way to initiate a communication request based on an additional communication identity (e.g. an authorization ID or an authorization code) and to verify (or detect, or authorize) the communication request by a communication server when initiating a user oriented communication service (e.g. calling the user). Thus, not only the privacy disturbance problem in the B2C scene, such as that the marketing/service call of an enterprise may disturb the privacy of a customer and be complained by the customer, but also the privacy disturbance problem in the C2C scene, such as that a person directly calls other people and may disturb the privacy of other people, and the problem that the privacy is disturbed due to the fact that the person registers own telephone number outside and the number is leaked, can be relieved.

Various embodiments provided herein will be described in detail below with reference to the accompanying drawings.

First, to facilitate understanding of embodiments of the present application, terms referred to in the present application will be briefly described.

1. Basic communication identifier and additional communication identifier

The target user is associated with at least one user identification module, which may be, for example, a card (e.g., an internet card, a phone card, etc.). As an example, the user identification module may be, for example, any of the following: subscriber identity cards (subscriber identification module, SIM), universal subscriber identity cards (universal subscriber identification module, USIM), embedded SIM cards (eSIM), subscriber identity modules (user identity model, UIM), IP multimedia service identity modules (IP multimedia service identity module), code division multiple access (code division multiple access, CDMA) subscriber identity modules (CDMA subscriber identity module, CSIM), and the like.

In an embodiment of the present application, the subscriber identity module associates (or corresponds to, or binds) at least one additional communication identity. Optionally, the subscriber identity module may also associate one or more underlying communication identities. The base communication identity and the additional communication identity are understood to be identities that are bound to the subscriber identity module.

The basic communication identifier is a user identifier in a communication network and is used for communicating with other users. The additional communication identity may be understood as an identity that communicates with other users instead of the base communication identity. For example, the additional communication identifier corresponds to the communication authorization information, and the base communication identifier may not set the corresponding communication authorization information. For example, when other users call the basic communication identifier of the user, normal communication can be performed; if the additional communication identification of the user is called, the communication server checks according to the communication authorization information corresponding to the additional communication identification. As yet another example, it may be determined for a user whether to provide a base communication identity or an additional communication identity based on different scenarios or different users. For example, a user may provide a base communication identifier for contacts in the address book and an additional communication identifier for users outside the address book. For another example, the user may provide a base communication identity to a person who knows himself, and an additional communication identity to a stranger. As another example, the user may provide a base communication identification for the individual user and an additional communication identification for the enterprise user. It is to be understood that the foregoing is illustrative and that the embodiments of the present application are not limited thereto.

As an example, the specific form of the additional communication identifier or the base communication identifier may be any of the following: a communication number, a mailbox, a character string, a two-dimensional code (an authorization code as described later), and the like. The following is an exemplary description taking a communication number as an example. For example, the additional communication identification is an authorized identification number (identify document, ID), and the base communication identification is a base number.

The base number and the authorization ID may be understood as numbers bound to the subscriber identity module or to a separate communication unit. The basic number is a telephone number or a mobile phone number which is widely used currently, and is a user identifier in a communication network and is used for communicating with other users. An authorization ID may be understood as a number that is used to communicate with other users instead of the base number. Such as the called number is an authorized ID. The authorization ID, which may also be referred to as an additional number, may be referred to as a pairing number, or may be referred to as an authorization number, the specific naming of which does not limit the scope of protection of the present application. Hereinafter, description is made with an authorization ID for unification.

As an example, the authorization ID may be a number consisting of X digits, X being an integer greater than 1. For example, x=11; for another example, x=4; for another example, x=8; as another example, x=12, and so on. The value of X is not limited. It will be appreciated that the authorization ID may be in other forms, such as a character string, which is not limited thereto, and the present application mainly uses the number formed by the digits of X as an example for illustration.

The authorization ID does not affect the base number, i.e. the base number may remain compatible with the authorization ID and the behavior of the base number is unchanged. The authorization ID may be assigned, for example, by the communication network, in a manner that will be described in detail later. The authorization ID may be routable, the encoding rules may be the same as or similar to the encoding rules of the base number, for example, the authorization ID may include, but is not limited to: network identification number, region number, user number. For the user, the base number does not need to be filled in when the information is externally registered, and the authorization ID is provided. The authorized ID after authorization may be called.

It should be understood that the present application is not limited to the specific form and details of the base number and authorization ID.

Fig. 2 shows a schematic diagram of a relationship between a base number and an authorization ID provided in an embodiment of the present application.

As shown in fig. 2, an individual user may have one or more SIM cards, such as SIM card 1 and SIM card N. Each SIM card may correspond to one or more authorization IDs. Alternatively, each SIM card may correspond to one or more base numbers, and hereinafter, one SIM card corresponds to one base number, and one or more authorization IDs are mainly exemplified. As shown in fig. 2, for example, the base number corresponding to the SIM card 1 is 13812345678, and the authorization ID corresponding to the SIM card 1 includes: authorization ID1, authorization ID2, authorization IDN, wherein authorization ID1 may be 19912345678, for example.

Fig. 3 shows still another schematic diagram of the relationship between the base number and the authorization ID provided in the embodiment of the present application.

As shown in fig. 3, an enterprise user may have (or own, or correspond to, or be associated with, or bind to) one or more base numbers, such as base number 1 and base number N, and may also have one or more authorization IDs. As shown in fig. 3, as an example, the basic number 1 corresponding to the enterprise user is 85500, and the authorization ID corresponding to the enterprise user includes: authorization ID1, authorization ID2, authorization IDN, wherein authorization ID1 may be 075512345678, for example.

From the above, the user can communicate with other users using the base number or the authorized ID. With respect to the relationship of the base number and the authorization ID, reference may be made to examples as in fig. 2 or fig. 3. Or may be distinguished from several examples as follows. For example, the authorization ID corresponds to communication authorization information set by the user, and the base number may not need to set the corresponding communication authorization information. For example, when other users call the basic number of a user, normal communication can be performed; if the user's authorized ID is called, the communication server checks according to the communication authorized information corresponding to the authorized ID, and the communication can be normally performed only after the check. As yet another example, the user may determine whether to provide the base number or the authorization ID based on a different scenario or a different social object. For example, a user may provide a base number for contacts in the address book and an authorization ID for users outside the address book. For another example, the user may provide a base number for a person who knows himself, and an authorization ID for a stranger. For another example, the user may provide a base number to the individual user and an authorization ID to the business user. It is to be understood that the above is intended to be illustrative, and not restrictive.

It should be understood that the numbers mentioned in this application are merely illustrative, which does not limit the protection scope of this application, and the specific form and content of the numbers are not limited in this application. This will not be described further.

It will also be appreciated that reference hereinafter to an authorization ID corresponding to a device (or an authorization ID of a device) multiple times indicates that the user using the device corresponds to an authorization ID.

2. Authorization code

The authorization code may be used to communicate with other users in place of the base number. The authorization code belongs to one possible form of additional communication identity. When the user registers information, the user can provide the authorization code without filling in the basic number. The authorization code does not affect the base number (i.e., the telephone number that is currently in widespread use), i.e., the base number may remain compatible with the authorization code, and the behavior of the base number is unchanged.

As an example, the authorization code may include an authorization ID of the authorizer and communication authorization information (or may also be referred to as authorization information), which is authorization information corresponding to the authorization ID. The authorization code may be in the form of a coded authorization ID of the authorizer and communication authorization information, such as a two-dimensional code, or may be in other forms, without limitation. The authorization code may be assigned by the communication network and each user may be assigned one or more, without limitation, in a manner described in detail below.

As an example, the communication authorization information may include one or more of the following: the base number of the authorized party, the authorized ID of the authorized party, the callable time period, the callable location, the authorized validity period, whether to renew, the renewal mode, etc. The communication authorization information may also include other auxiliary information.

Wherein the base number of the authorized party and the authorized ID of the authorized party represent the number of the authorized party that can be called. For example, the communication authorization information includes the base number of the authorized party and is 85500, then 85500 may call the authorized party.

Wherein the callable time period indicates a time period during which an authorized party can be called. For example, the communication authorization information includes a callable time period of 10 pm to 20 pm on Saturday, then the authorizer may be called 10 pm to 20 pm on Saturday.

The authorization valid period may represent a valid time of the communication authorization information, or may also represent an expiration time of the communication authorization information.

Wherein, whether to renew indicates whether to renew after expiration. Whether the value of the duration is yes or no.

The renewal mode indicates how to renew, such as sending a short message or sending a mail to notify the authority Fang Xuqi, etc.

Wherein other auxiliary information such as verification codes and the like. If both parties agree on the verification code, the caller needs to input the correct verification code when the caller calls the callee.

It is to be understood that some of the information described above is merely an exemplary illustration and that embodiments of the present application are not limited thereto.

Optionally, the communication authorization information is processed so as to prevent tampering with the communication authorization information. For example, the communication authorization information may be encrypted, that is, the authorization code includes the authorization ID of the called user (that is, the authorization ID of the authorizing party) and the ciphertext of the communication authorization information. When the calling user's device sends a call request message to the called user's device, the authorization code can be analyzed first to obtain the authorization ID of the called user (i.e. the authorization ID of the authorized party) and the ciphertext of the communication authorization information; then sending a call request message to the equipment of the called user through the communication server, and carrying ciphertext of the communication authorization information in the call request message; the communication server decrypts the ciphertext of the communication authorization information and performs verification; after verification is passed, the calling user is connected, namely, the calling connection between the equipment of the calling user and the equipment of the called user is triggered. The encryption method and the key may be determined by the communication server, for example, a symmetric encryption algorithm (such as advanced encryption standard (advanced encryption standard, AES)), a key length of 128bits, an encryption block chain (cipher block chaining, CBC) mode, or the like may be used without limitation.

It will be appreciated that the above encryption processing of the communication authorization information is only one possible implementation, and embodiments of the present application are not limited thereto, and any manner that can prevent tampering of the communication authorization information is suitable for the present application. For example, when a digital signature is added and the device of the calling user sends a call request message to the device of the called user, the digital signature is carried in the call request message. There are many ways to add digital signatures, and there are no restrictions. In one possible way, a digital signature is added by the communication server on the communication authorization information. In another possible way, a digital signature on the communication authorization information is added by the device of the called user. If the device of the called user adds a digital signature on the communication authorization information, the device of the called user may send a key to the communication server, as an example, so that the communication server may obtain the communication authorization information.

It will also be appreciated that in the embodiments below, reference is made to a user's device a number of times, which represents the device to which the user corresponds, or the device used by the user, or the device is attributed to the user. This will not be described further below.

It should also be appreciated that the foregoing has been mainly described by taking the example in which the authorization code includes the authorization ID of the authorizer and the communication authorization information, and embodiments of the present application are not limited thereto. For example, the authorization code includes communication authorization information, where the communication authorization information includes plaintext and ciphertext, the plaintext is an authorization ID of an authorized party, and the ciphertext is information obtained by encrypting one or more of the above information (such as a base number of the authorized party, an authorization ID of the authorized party, a callable time period, a callable location, an authorization validity period, whether to renew, a renewing manner, other auxiliary information, etc.).

It should be noted that, in the present application, the transmission authorization code is mentioned for a plurality of times, and it can be understood that if the authorization code is in the form of a two-dimensional code, the transmission authorization code indicates that information in the two-dimensional code is transmitted; and after receiving, the receiver displays the two-dimensional code. If the authorization code is in another form, such as a Base64 code, that code may be followed by direct transmission.

Fig. 4 shows a schematic diagram of an authorization code provided in an embodiment of the present application. As shown in fig. 4, the authorization ID of the authorizer may be embodied in a plaintext manner, and the communication authorization information may be encrypted. The communication authorization information includes, for example, the number of the authorized party (e.g., the base number and/or the authorization ID), the callable time period, the calling location, the authorization valid period, whether to renew, the renewal mode, and other auxiliary information. The form of the authorization code may be a form of encoding the communication authorization information and the authorization ID of the authorizer, such as a form of a two-dimensional code shown in fig. 4.

3. Authorization

In this application, authorization may include at least the following three types: "call authorization", "identification authorization", "callback authorization", respectively, are described below.

(1) Call authorization

Call authorization may refer to an individual authorizing an enterprise (or other individual) to call itself. In this case, the individual may be referred to as an authorized party, and the enterprise or other individual may be referred to as an authorized party.

Call authorization for two scenarios is presented below: one authorizes the authorizer to the authorization ID and the other authorizes the authorizer to the base number, as exemplified below in connection with fig. 5.

Fig. 5 shows a schematic diagram of call authorization provided in an embodiment of the present application.

For example, as in scenario 1 shown in fig. 5, the authorizer may authorize the authorization ID, i.e., the call may be placed while the authorizer uses authorization ID1 (e.g., 19912345673) as the calling number to call authorization ID1 (e.g., 19912345670) of the authorizer.

As another example, as in scenario 2 of fig. 5, the party may authorize the base number, i.e., the party may place a call using the base number (e.g., 13812345671) as the calling number to call the authorized ID1 (i.e., 19912345670) of the party.

In call authorization, after the authorized party has made call authorization to the authorized party, the communication network may maintain an authorization relationship (e.g., may be maintained in a communication network serving the authorized party). For distinction, this authorization relationship is referred to as a call authorization table, which may include authorizer information and authorized party information. The call authorization table may be communication authorization information, in which case the communication authorization information includes authorizer information and authorized party information; or the call authorization table may be a correspondence between communication authorization information and authorizer information, in which case the communication authorization information includes authorizer information and may not include authorizer information.

For convenience of description, a communication network serving an authorizer is referred to as an authorizer communication network, and a communication network serving an authorized party is referred to as an authorized party communication network.

Fig. 6 shows a schematic diagram of a call authorization table provided in an embodiment of the present application.

As shown in fig. 6, the call may be placed assuming that the authorizer's personal user authorizes the authorization ID to the enterprise user, i.e., the authorized party's enterprise user uses authorization ID1 (e.g., 0755111001) as the calling number to call the authorizer's authorization ID1 (e.g., 0755000001). The call authorization table may be maintained at the authorizer communication network. The call authorization table may include: ID. An authorization ID of the authorizer (e.g., 0755000001), an authorization ID of the authorized party (e.g., 0755111001), other authorization information. Other authorization information may include, but is not limited to: the time period of the call, the call location, the validity period of the authorization, whether to renew, the renewal mode, and other auxiliary information. Wherein the ID may be used to distinguish between different call authorization records. For example, if an authorized party has call authorized a plurality of authorized parties, there may be one authorization record for each authorized party, and the plurality of authorization records may be numbered to distinguish between the different authorization records.

The home subscriber server (home subscriber server, HSS) subscriber information table in fig. 6 may include, but is not limited to: ID. Name (i.e., personal user name), identification number (i.e., personal user identification number), base number of the authorizer, authorization ID of the authorizer (e.g., 0755000001).

The related scheme of call authorization is introduced above, and callback authorization is introduced below.

(2) Callback authorization

Callback authorization, which may also be understood as one of call authorizations, is used in the context of an individual calling an enterprise or other individual as a caller. For ease of understanding, user #1 and user #2 are illustrated as examples. Suppose user #1 is an individual and user #2 is an enterprise (or may be an individual as well). If user #1 obtains the base number of user #2 (or user #1 has been authorized by user #2 and obtained the authorization ID of user # 2), user #1 may directly call user #2, i.e., the device of user #1 may establish a call connection with the device of user # 2. Considering that user #2 may need to call back user #1 after user #1 calls, before calling the device of user #2, the device of user #1 may set the callback authorization information (i.e., an example of the communication authorization information), and the call is restarted after setting, so that the callback authorization information is included in the call request message. At this time, after receiving the call request message, the communication network stores callback authorization information carried in the call request message, and the callback authorization information indicates the authorization ID of the user #1 as the called number. As an example, when the device of user #1 serves as the device of the originating call user #2, the S-CSCF may receive a call request message sent by the device of user #1, the call request message including callback authorization information; the S-CSCF may forward the callback authorization information to the authorization management service AS so that the authorization management service AS may save the callback authorization information. Specifically, the details of method 3100 are described below. By the method, privacy intrusion caused by leakage of the base number of the user #1 can be relieved, and the user #2 can call back the user #1 in an authorized range (such as a time range, a position range and the like).

Fig. 7 shows a schematic diagram of a callback call provided in an embodiment of the present application.

As shown in fig. 7, it is assumed that the user is authorized to the basic number of the enterprise employee, i.e., the authorized party enterprise employee uses the basic number (e.g., 85500) as the calling number to call the user, the call may be placed. The device of the user may set callback authorization information and carry the callback authorization information in a call request message of a staff member of the calling enterprise, and the communication network may store the callback authorization information, where the callback authorization information may include, for example: callback grant time. The callback authorization time indicates how long the callback can be performed. When the enterprise employee recalls the user's authorization ID, the communication network may determine whether the callback may be on based on the callback authorization information. AS an example, the S-CSCF receives a call request message from the user' S device, the call request message including callback authorization information, and the S-CSCF may forward the callback authorization information to the authorization management service AS, so that the authorization management service AS may save the callback authorization information.

The related schemes of call authorization and callback authorization are described above, and identification authorization is described below.

(3) Identification authorization

Identification authorization may refer to an enterprise authorizing an employee to initiate a call to the outside using an identification of the enterprise (or the identity of the enterprise), in which case the enterprise may be referred to as an authorized party and the employee may be referred to as an authorized party. Alternatively, identity authorization may also refer to an individual authorizing his identity (or identity of an individual) for use by other individuals, in which case the individual may be referred to as an authorized party and the other individuals may be referred to as authorized parties. The identifier may be an additional communication identifier or may be a basic communication identifier. Hereinafter, the explanation will be given mainly on the case that the enterprise authorizes the employee to make the external originating call using the basic number or the authorization ID of the enterprise.

Fig. 8 shows a schematic diagram of identification authorization provided in an embodiment of the present application.

As shown in fig. 8, when the enterprise authorizes the employee to make a call to the outside using the identity of the enterprise (e.g., using the base number or authorization ID of the enterprise), the enterprise employee may call the authorization ID of the individual user using the identity of the enterprise; when the enterprise is not authorized to send a call to the staff using the identity of the enterprise, the staff of the enterprise cannot call the authorized ID of the personal user using the identity of the enterprise.

The identification authorization for four scenarios is presented below: the base number of the authorizer is authorized to the base number of the authorizer, the base number of the authorizer is authorized to the authorized ID of the authorizer, the authorized ID of the authorizer is authorized to the base number of the authorizer, and the authorized ID of the authorizer is authorized to the authorized ID of the authorizer, as exemplified below in connection with fig. 9.

Fig. 9 shows a further schematic diagram of identification authorization provided by an embodiment of the present application.

For example, as shown in scenario 1 of fig. 9, the base number of the authorizer may be used when the base number of the authorizer is authorized to the base number of the authorized party, i.e., the authorized party uses the base number (e.g., 13812345671) as the calling number to place a call (e.g., 85500).

As another example, as shown in scenario 2 of fig. 9, the base number of the authorizer may be used when the base number of the authorizer authorizes to the authorized ID of the authorized party, i.e., the authorized party uses the authorized ID (e.g., 19912345673) as the calling number to place a call (e.g., 85500).

As another example, as shown in scenario 3 of fig. 9, the authorization ID of the authorizing party may be used when the authorizing party's authorization ID is authorized to the base number of the authorized party, i.e., the authorized party uses the base number (e.g., 13812345671) as the calling number to place a call (e.g., 07551234567).

As another example, as shown in scenario 4 of fig. 9, the authorized party's authorized ID may be used when the authorized party's authorized ID is authorized to the authorized party's authorized ID, i.e., the authorized party uses the authorized ID (e.g., 19912345673) as the calling number to place a call (e.g., 07551234567).

To facilitate understanding, specific examples are presented.

Assume that: the base number of user #1 is 13812345670 and the authorization ID of user #1 is 19912345670; the basic number of the enterprise is 85500, and the authorized ID of the enterprise is 07551234567; user #2 has a base number 13812345671 and user #2 has an authorization ID 19912345673.

Assume again that: user #1 is a customer of the enterprise, and user #2 is a staff of the enterprise; user #1 registers its own authorization ID (unreserved base number) with the corporation and user #1 has authorized the corporation's base number 85500 or authorization ID07551234567 to call its own authorization ID. Several possible scenarios are described below.

In case 1, the enterprise does not give any authorization to user #2, and user #2 calls user # 1's authorization ID19912345670 using its own base number 13812345671 or authorization ID 19912345673. In this case, the communication network may prompt the user that the #2 call is not authorized and that the call cannot be completed.

In case 2, the enterprise grants its own base number 85500 to user #2 for use by base number 13812345671, as in scenario 1 of fig. 9. In this case, if the user #2 calls the authorization ID19912345670 of the user #1 using the own base number 13812345671, the call request carries the base number 85500 of the enterprise, and the incoming number seen by the user #1 is 85500.

Case 3, the corporation grants its own base number 85500 to user #2 for use with grant ID19912345673, as in scenario 2 of fig. 9. In this case, if the user #2 calls the authorization ID19912345670 of the user #1 using the own authorization ID19912345673, the call request carries the basic number 85500 of the enterprise, the call is completed, and the incoming number seen by the user #1 is 85500.

Case 4, the enterprise grants its own grant ID07551234567 to the base number 13812345671 of user #2 for use, as in scenario 3 in fig. 9. In this case, if the user #2 calls the authorization ID19912345670 of the user #1 using the own base number 13812345671, the call request carries the enterprise authorization ID07551234567, the call is completed, and the incoming number seen by the user #1 is 07551234567.

Case 5, the corporation grants its own authorization ID07551234567 to the user #2 for use by the authorization ID19912345673, as in scenario 4 in fig. 9. In this case, if the user #2 calls the authorization ID19912345670 of the user #1 using the own authorization ID19912345673, the call request carries the enterprise authorization ID07551234567, the call is completed, and the caller number seen by the user #1 is 07551234567.

In the identification authorization, the communication network may maintain an authorization relationship after the authorized party has made the identification authorization to the authorized party. For distinction, this authorization relationship is referred to as an identification authorization table, which may include authorizer information and authorizer information. The identification authorization table may be identification authorization information, in which case the identification authorization information includes authorizer information and authorized party information; or the identification authority table may be a correspondence relationship between the identification authority information and the authority information, in which case the identification authority information includes the authorized party information and may not include the authority information.

One possible way may be to store an identification authorization table in the authorized party communication network. Taking the above example as an example, the identification authorization table may be stored in a communication network serving user #2, for example.

Fig. 10 shows a schematic diagram of an identification authorization table provided in an embodiment of the present application.

As shown in fig. 10, an example is an authorization ID (e.g., 0755111001) of an authorizer's enterprise user to an authorization ID (e.g., 0755111002) of an enterprise employee. The identification authorization table may be maintained in an authorized party communication network (i.e., a communication network that serves enterprise employees). The identification authorization table may include: ID. An authorization ID of the authorizer (e.g., 0755111001), an authorization ID of the authorized party (e.g., 0755111002), other authorization information. Other authorization information may include, but is not limited to: the time period of the call, the call location, the validity period of the authorization, whether to renew, the renewal mode, and other auxiliary information. Wherein the ID may be used to distinguish between different base numbers or authorization ID authorization records. The HSS subscriber information table in fig. 10 may include, but is not limited to: ID. Name (i.e., employee name), identification number (i.e., employee identification number), authorization ID of the authorized party (e.g., 0755111002).

In yet another possible way, the identification authorization table may be stored in a communication network serving an authorized party to authorize the call. Taking the above example as an example, the identification authorization table may be stored in a communication network serving user #1, for example.

Fig. 11 shows a further schematic diagram of an identification authorization table provided in an embodiment of the present application.

As shown in fig. 11, assume that the personal user's authorization ID (e.g., 0755000001) is authorized to the enterprise user's authorization ID (e.g., 0755111001), the authorizer's authorization ID (e.g., 0755111001) is authorized to the enterprise employee 1's authorization ID (e.g., 0755111002) and the enterprise employee 2's authorization ID (e.g., 0755111003). The identification authorization table, as well as the call authorization table, may be stored in the called communication network (i.e., the communication network serving the individual user). Regarding the call grant table, and the identification grant table, reference may be made to the foregoing description, and details thereof will not be repeated herein.

4. Method for obtaining authorization ID or authorization code

As previously mentioned, the authorization ID or authorization code may be assigned (either generated or published) by the communication network. Several possible ways are described below.

In a first possible way, the user's device issues an authorization ID or an authorization code, i.e. the user automatically issues an authorization ID or an authorization code.

Fig. 12 is a schematic diagram of an individual user automatically issuing an authorization ID or an authorization code according to an embodiment of the present application.

As shown in fig. 12, the individual user issuing the authorization ID or authorization code to the enterprise through the terminal device may include the steps of: 1. the terminal equipment (such as a smart phone) of the personal user detects the authorization operation of the personal user, namely the personal user executes the authorization operation on the terminal equipment; 2. the terminal equipment of the individual user sends communication authorization information to a communication network (namely a communication server); 3. the communication network returns a token to the terminal equipment of the personal user, wherein the token represents an encrypted character string which contains user identity information and has timeliness; 4. the terminal equipment of the personal user sends a request message to an enterprise server (server) to request an authorization ID or an authorization code, wherein the request message carries a token; 5. the enterprise server transmits the request message to the communication network, wherein the request message carries a token; 6. the communication network returns an authorization ID or authorization code to the enterprise server. Through the above operations, the enterprise server can learn the authorization ID or authorization code of the individual user. Wherein the communication network means a communication server, which may be, for example, an authorized communication light application.

In a second possible way, the user may register his own authorization ID or authorization code manually, i.e. the user issues the authorization ID or authorization code manually.

Fig. 13 shows a schematic diagram of a personal user manually issuing an authorization ID or an authorization code according to an embodiment of the present application.

As shown in fig. 13, the manual issuance of the authorization ID or authorization code by the individual user may include the steps of: 1. the terminal equipment (such as a smart phone) of the personal user detects the authorization operation of the personal user, namely the personal user executes the authorization operation on the terminal equipment (such as the smart phone); 2. the terminal equipment of the individual user sends communication authorization information to a communication network (namely a communication server); 3. the communication network sends an authorization ID or an authorization code to the terminal equipment of the personal user; 4. the individual user manually registers (e.g., by means of online or offline) the authorization ID or authorization code. Through the above operation, other users (such as enterprises) can learn the authorization ID or authorization code of the individual user. Wherein the communication network means a communication server, which may be, for example, an authorized communication light application.

In both the above two modes, the user can execute the operation of issuing the authorization ID or authorization code of the individual user through the terminal device, and there are various implementations concerning the operation in the terminal device. For example, it may be performed in an application (App) provided by a communication network (e.g., it may be performed in a Data Channel-based authorized call light application provided by a communication carrier). Taking the second possible manner described above as an example, this is illustrated in connection with fig. 14.

Fig. 14 shows still another schematic diagram of a personal user manually issuing an authorization ID or an authorization code provided in an embodiment of the present application.

As shown in fig. 14, after the terminal device detects the operation of the individual user, the issuing of the authorization ID or the authorization code, the operation of the individual user on the terminal device may include the steps of: (1) opening an authorized call light application based on a Data Channel on terminal equipment (such as a smart phone); (2) inputting a basic number or an authorized ID of an authorized party; (3) inputting communication authorization information; (4) click confirmation. If the authorization is successful, the terminal equipment of the personal user displays the authorization success and displays an authorization code or an authorization ID. The terminal device of the individual user can send the authorization code or the authorization ID to the device of the home enterprise, so that the enterprise can acquire the authorization code or the authorization ID of the individual user; and/or the terminal device of the individual user may send the authorization code or authorization ID to the device of the home individual user so that other users may learn the authorization code or authorization ID of the individual user. Wherein, (2) and (3) may be obtained, for example, by scanning, for example, a two-dimensional code of the authorized party. The communication network in fig. 14 represents a communication server, which may be, for example, an authorized communication light application.

In a third possible way, the terminal device directly generates the authorization code, the generation process may be independent of the communication network.

Fig. 15 shows a schematic diagram of direct generation of an authorization code by a terminal device according to an embodiment of the present application.

As shown in fig. 15, the terminal device directly generating the authorization code may include the steps of: (1) after detecting the operation of the personal user, the terminal equipment opens the authorized communication light application; (2) the terminal equipment scans the two-dimensional code of the counter, the page can display an authorization protocol template (namely one example of communication authorization information), and a user can check or modify the communication authorization information in the authorization protocol template; (3) the terminal device detects an operation of a user clicking the confirmation. The authorization protocol template may include, for example, one or more of the following communication authorization information: whether 85500 calls are allowed, the time period of callable, the location of callable, the validity period of authorization, whether to renew, the manner of renewing, other auxiliary information.

In a fourth possible way, authorization codes are exchanged face-to-face.

Fig. 16 illustrates a schematic diagram of person-to-person exchanging authorization codes provided by embodiments of the present application.

To distinguish, the device of the user 1 (e.g. the terminal device used by the user 1) is denoted as the device 1, the device of the user 2 (e.g. the terminal device used by the user 2) is denoted as the device 2, and as shown in fig. 16, the person-to-person exchanging the authorization code may comprise the steps of: 1. the device 1 detects the operation of the user 1, opens the authorized communication light application, and enters an 'authorized code-nearby exchange' page; 2. the device 1 detects the operation of the user 1 and clicks the icon of the device 2; 3. device 1 issues a notification to device 2; 4. the device 2 pops up a window; 5. the device 2 detects an operation accepted by the user 2 (e.g., the device 2 detects an operation in which the user 2 clicks an accept button); 6. the device 2 stores the authorization code of the user 1; 7. the device 2 sends an authorization code of the user 2 to the device 1; 8. the device 2 saves the authorization code of the user 1. Wherein if the device 2 detects an operation of rejection of the user 2 in step 5, steps 6 to 8 may not be performed in this case, and as an example, the device 2 may send a rejection message to the device 1 in this case.

It will be appreciated that the foregoing is illustrative only and that any modification falling within the scope of the present application is contemplated.

It will be appreciated that the term "and/or" is merely one association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

The terms referred to in the present application are briefly described above, and will not be repeated in the following examples. The communication method provided in the embodiment of the present application will be described in detail below with reference to the accompanying drawings.

Fig. 17 shows a schematic diagram of a communication method 1700 provided in an embodiment of the present application. The method 1700 may include the following steps.

1701, the communication server receives the communication request message.

Wherein the communication request message includes an additional communication identification of the target user. The additional communication identifier corresponds to communication authorization information set by the target user (such as the target user generates the communication authorization information; such as the target user provides authorization requirement information, and the communication server generates the communication authorization information based on the authorization requirement information), and the communication authorization information is used for characterizing communication services authorized by the target user and directed to the additional communication identifier. The additional communication identifier and communication authorization information will be described in detail later.

The communication service may be any service for communication between two devices (such as two terminal devices). As an example, communication traffic may include, but is not limited to: call services, instant messaging services, short message services, mail services, etc. This is not limited.

For example, if the communication service is a call service, the communication request message (or may also be called a call request message) may be used for the initiator to request to establish a call connection with the target user, that is, the initiator (or may also be called a calling user) to request to establish a call connection with the target user (or may be called a called user); if the communication service is a short message service, the communication request message can be used for the initiator to request the target user to transmit a short message, that is, the initiator requests to send the short message to the target user; if the communication service is a mail service, the communication request message may be used for the initiator to request a mail to be transmitted to the target user, that is, the initiator requests to send a mail to the target user.

Hereinafter, for distinction, the device of the initiator (i.e., the initiator of the communication request message) is denoted as a first device (i.e., the first device belongs to the initiator), and the device of the target user is denoted as a second device (i.e., the second device belongs to the target user). The first device and the second device may be terminal devices, or may be other communication devices, which is not limited.

1702, the communication server releases or denies the communication service requested to be executed by the communication request message according to the communication authorization information.

Wherein the communication server represents a network device that can provide services for the communication device. As an example, a communication server may represent a device in a communication network that provides services for a communication device. As an example, the communication server includes one or more of the following: an authorized communication light application server, an authorized management service AS and an S-CSCF.

The communication server is, for example, an S-CSCF. In step 1701, the S-CSCF receives a communication request message from the first device; in step 1702, the S-CSCF releases or denies the communication service requested to be performed by the communication request message according to the communication authorization information. For example, after receiving the communication request message from the first device, the S-CSCF may invoke an interface of the authorization management service AS, that is, the authorization management service AS determines whether the authorization is normal based on the communication authorization information, and notifies the S-CSCF of the authorization result; in step 1702, the S-CSCF releases or denies the communication service requested to be performed by the communication request message according to the authorization result.

AS another example, the communication server is an authorization management service AS. In step 1701, the authorization management service AS knows that the first device sends a communication request message; in step 1702, the authorization management service AS releases or denies the communication service requested to be executed by the communication request message according to the communication authorization information. For example, after receiving a communication request message from a first device, the S-CSCF invokes an interface of an authorization management service AS, where the authorization management service AS learns that the first device requests to establish a communication connection with a second device; the authorization management service AS judges whether the authorization is normal based on the communication authorization information. If the authorization is normal, the communication service requested to be executed by the communication request message can be put, for example, the authorization management service AS informs the S-CSCF of the result of the normal authorization, and then the communication service requested to be executed by the communication request message can be put through; if the authorization is abnormal, the communication service requested to be executed by the communication request message can be refused, for example, the authorization management service AS informs the S-CSCF of the abnormal authorization result, and further the communication service requested to be executed by the communication request message can be refused.

AS another example, the communication server includes an S-CSCF and an authorization management service AS. In step 1701, the S-CSCF receives a first device send communication request message; in step 1702, the authorization management service AS or S-CSCF releases or denies the communication service requested to be performed by the communication request message according to the communication authorization information.

It is to be understood that the foregoing is merely a simple exemplary illustration and that the embodiments of the present application are not limited thereto. The present application is not limited to the form of the device of the communication server, and any device that can implement its function is suitable for the present application.

Wherein the release may be replaced by permission (or authorization or agreement). The communication server releases the communication service requested to be executed by the communication request message according to the communication authorization information, and it is understood that the communication server determines that the communication service requested to be executed by the communication request message can be executed according to the communication authorization information. For example, if the communication service is a call service, the communication server may release the communication service requested to be executed by the communication request message according to the communication authorization information, and instead, the communication server may trigger the first device to establish a call connection with the second device (i.e., the initiator and the target user) according to the communication authorization information. For another example, if the communication service is an instant message service, the communication server may release the communication service requested to be executed by the communication request message according to the communication authorization information, and instead, the communication server triggers the first device to establish an instant message connection with the second device (i.e. the initiator and the target user) according to the communication authorization information. For another example, if the communication service is a short message service, the communication server may release the communication service requested to be executed by the communication request message according to the communication authorization information, and instead, the communication server forwards the short message in the communication request message to the second device (i.e., the target user) according to the communication authorization information.

Where rejection may be replaced with prohibition (either unauthorized or disagreeable). The communication server refuses the communication service requested to be executed by the communication request message according to the communication authorization information, which can be understood that the communication server determines that the communication service requested to be executed by the communication request message is not allowed to be executed according to the communication authorization information.

In a possible case, the communication server determines that the communication service requested to be executed by the communication request message belongs to the communication service which is authorized by the target user and is directed to the additional communication identifier according to the communication authorization information, and the communication server releases the communication service which is requested to be executed by the communication request message and is directed to the additional communication identifier.

In another possible case, the communication server determines, according to the communication authorization information, that the communication service requested to be performed by the communication request message does not belong to the communication service authorized by the target user and directed to the additional communication identifier, and the communication server rejects the communication service requested to be performed by the communication request message and directed to the additional communication identifier.

The communication service requested to be executed by the communication request message belongs to the communication service which is authorized by the target user and points to the additional communication identifier, namely the communication service requested to be executed by the communication request message meets the requirement of the communication service authorized by the target user and pointing to the additional communication identifier; the communication service requested to be executed by the communication request message does not belong to the communication service which is authorized by the target user and is directed to the additional communication identifier, namely the communication service requested to be executed by the communication request message does not meet the requirement of the communication service which is authorized by the target user and is directed to the additional communication identifier. In this regard, the description will not be repeated.

The specific implementation of step 1702 is described in detail below in connection with communication authorization information.

By the application, when the first device (or initiator) requests to execute the communication service pointing to the second device (or target user's identifier), the communication request message may carry an additional communication identifier of the second device, and the communication server performs verification (or referred to as detection or referred to as authorization) according to the communication authorization information corresponding to the additional communication identifier, and determines to release or reject the communication service requested to be executed by the communication request message according to the verification result. Therefore, the privacy disturbance problem caused by the leakage of the additional communication identification of the second equipment can be relieved. Taking the call service as an example, when the first device requests to call the second device, the communication request message may carry the number (such as the authorized ID) of the second device, and the communication server performs verification according to the communication authorization information corresponding to the number, and triggers the first device to establish call connection with the second device according to the verification result, or refuses the call request of the first device according to the verification result. Thus, not only the privacy disturbance problem in the B2C scene, such as the disturbance of a customer by marketing/service calls of an enterprise, but also the privacy disturbance problem in the C2C scene, such as the direct calling of a person by another person, can disturb the privacy of the other person, and can also relieve the problem that the privacy is disturbed due to the fact that the person registers own telephone number outside and the number is leaked.

Aspects of the present application are described in detail below.

First, additional communication identity

The additional communication identity may be used to indicate to which device the communication request message requests to perform a communication service directed. Taking the first device and the second device as an example, the additional communication identifier in step 1701 may be used to identify the second device to which the communication request message is directed.

Optionally, prior to step 1701, the method 1700 further comprises step 1710.

The second device provides 1710 an additional communication identification corresponding to the communication authorization information to the first device. Accordingly, the first device obtains the additional communication identity.

The second device may provide its own additional communication identity to one or more other devices, and the additional communication identity corresponds to the communication authorization information. The following mainly exemplifies the first device.

In one possible way, the second device sends its own additional communication identity to the first device, and the first device receives the additional communication identity of the second device accordingly.

In another possible manner, the second device displays a two-dimensional code (such as the two-dimensional code shown in fig. 4), and the first device scans the two-dimensional code and obtains the additional communication identifier and the communication authorization information of the second device from the two-dimensional code.

It should be appreciated that the above two ways are exemplary illustrations, and that the manner in which the first device can obtain the additional communication identifier of the second device is applicable to the present application.

The additional communication identity of the second device itself may be obtained in a number of ways. For example, the second device generates an additional communication identity. For another example, the communication server generates an additional communication identity and sends (or publishes) the additional communication identity to the second device. For example, reference may be made to the manner in which the authorization ID is obtained in the above explanation of terms, and details are not repeated here.

As an example, the additional communication identity may be in the form of: communication numbers, mailboxes, character strings, two-dimensional codes, authorization codes, and the like. The communication number may be a basic number or an authorized ID. With respect to the base number and the authorized ID, reference may be made to the previous term explanation, which is not repeated here.

For example, if the communication service is a call service (or a sms service, or an instant message service), that is, the first device requests to establish a call connection with the second device, the communication request message may include an authorized ID of the second device; if the communication service is a mail service, that is, the first device requests to send a mail to the second device, the communication request message may include a mailbox number of the second device.

In this application, reference is made to an additional communication identity of a device a number of times, which means an additional communication identity corresponding to the device, or to a user of the device. Hereinafter, for brevity, additional communication identification descriptions of the device are unified.

In this application, reference is made to a device corresponding to an additional communication identity a number of times, which represents the device used by the user corresponding to the additional communication identity. Hereinafter, for brevity, the device description corresponding to the additional communication identifier is unified.

In this application, the devices may communicate based on an additional communication identifier, where the additional communication identifier corresponds to communication authorization information, so that, when performing communication, the communication server may perform verification (or referred to as detection or referred to as authorization) based on the communication authorization information.

Fig. 18 shows a schematic diagram of communication based on additional communication identification according to an embodiment of the present application.

As shown in fig. 18, method 1800 may include the following steps.

1801, generating an additional communication identity.

The manner in which the additional communication identification is generated is not limited. For example, after detecting the operation of the user, the device of the user generates an additional communication identifier; for another example, the communication server generates an additional communication identity of the user and sends it to the user's device. In particular, reference may be made to the relevant description of the generation of the authorization ID or authorization code in the previous term explanation, which is not repeated here.

And 1802, determining communication authorization information corresponding to the additional communication identifier.

For example, using the additional communication identifier as the authorization ID, in step 1802, the authorization ID corresponds to communication authorization information, through which the communication service associated with the authorization ID may be verified. Specifically, the description will be made later in connection with the communication authorization information.

For another example, using the additional communication identifier as an authorization code, in step 1802, the authorization code may include communication authorization information in addition to the authorization ID of the authorizer, where the communication service associated with the authorization ID may be verified. For the authorization code, reference may be made to the description of the previous term interpretation section, which is not repeated here.

1803, issuing the additional communication identification.

The user's device provides the user's own additional communication identity to one or more other devices, and the other devices may communicate with the user's device based on the additional communication identity.

1804, checking the request to perform communication traffic directed to the additional communication identity.

In step 1804, the communication server receives a communication request message, where the communication request message is used to request to execute a communication service directed to the additional communication identifier, and the communication server performs verification authorization based on the communication authorization information corresponding to the additional communication identifier.

The communication service is exemplified as a call service. The calling user's device may call the called user's device based on the obtained additional communication identification (e.g., authorization ID or authorization code) of the called user. After receiving the call request from the caller's device, the communication server may verify the authorization based on the communication authorization information. If the authorization is normal, that is, the communication server knows that the calling user has the authorization of the called user based on the communication authorization information, the communication server can trigger the equipment of the calling user and the equipment of the called user to establish communication connection; if the authorization is abnormal, that is, the communication server knows that the calling user is not authorized by the called user based on the communication authorization information, the calling request of the equipment of the calling user can be refused. The specific manner of verification of the communication server will be described in detail later.

The additional communication identifier is introduced above, and an overall scheme for communicating based on the additional communication identifier is introduced below.

Second, communication authorization information

In this application, communication authorization information is used to characterize a communication service authorized by a target user and directed to an additional communication identifier, where the communication authorization information may represent authorization information corresponding to the additional communication identifier, and may be used to verify a communication request message directed to the additional communication identifier. As an example, the communication authorization information may include an additional communication identifier of the authorizer (such as an additional communication identifier of the second device), and the corresponding communication authorization information may be obtained based on the additional communication identifier of the authorizer; or the communication authorization information may have a correspondence with the additional communication identifier of the authorizing party, and further based on the additional communication identifier of the authorizing party and the correspondence, the corresponding communication authorization information may be obtained. The communication authorization information may be in the form of a table, such as a call authorization table similar to that described in the term interpretation section above, or an identification authorization table; or may be in the form of a two-dimensional code, such as an authorization code similar to that described in the term interpreting section above.

The communication authorization information of the second device may be obtained by a plurality of means for the first device. For example, the second device sends (or issues) communication authorization information to the first device. For another example, the second device displays a two-dimensional code (such as the two-dimensional code shown in fig. 4), and the first device scans the two-dimensional code and acquires communication authorization information from the two-dimensional code.

The second device may obtain its own communication authorization information in a variety of ways. For example, the second device generates communication authorization information. For another example, the authorization requirement information is provided by the second device, and the communication server generates communication authorization information based on the authorization requirement information and transmits (or issues) the communication authorization information to the second device. For example, the communication server generating the communication authorization information may include: the communication server receives a second message from the second device, wherein the second message comprises authorization requirement information and additional communication identification of the second device, and the authorization requirement information is used for representing communication authorization information required by the target user; the communication server encrypts the authorization requirement information to obtain ciphertext, wherein the ciphertext is encrypted authorization requirement information; coding the ciphertext and the additional communication identifier of the second device to obtain communication authorization information; and transmitting the communication authorization information to the second device. Regarding the generation of the communication authorization information by the communication server, reference may be made, for example, to the relevant description of the authorization code in the above explanation of terms, which is not repeated here.

Optionally, the communication authorization information includes one or more of the following: authorization object information, an authorization time range, and a validity period of communication authorization information. The following will describe each.

1) Authorization object information

Authorization object information usable to indicate an initiator or initiator of a communication service authorized by a target user to be directed to an additional communication identification.

As an example, the authorization object information includes any one or more of the following: the location range in which the sponsor of the authorized communication service should be located, the authentication code that the sponsor of the authorized communication service should provide, the order number that the sponsor of the authorized communication service should be associated with, the type of device that the sponsor of the authorized communication service should be, and the identity that the sponsor of the authorized communication service should be.

Example 1, the communication authorization information includes: the range of locations in which the initiator of the authorized communication service should be.

The location range in which the authorized initiator of the communication service should be located, that is, the location in which the authorized initiator of the communication service directed to the additional communication identifier is located, indicates the location in which the communication service directed to the additional communication identifier can be performed. Hereinafter, for brevity, "a location range in which an authorized initiator of communication service should be located" will be simply referred to as "a location range in which it should be located". Taking the communication service as a call service as an example, the location range to be located may represent a callable location. The callable location may be a distance, an area, or other information that characterizes the location, without limitation.

Optionally, in step 1702, the communication server puts through or refuses the communication service directed to the additional communication identifier requested to be executed by the communication request message according to the communication authorization information, including: the communication server releases or refuses the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identification according to the position range which is included in the communication authorization information and is supposed to be positioned.

For example, the communication server obtains the location of the initiator of the communication request message, and if the communication server determines that the location of the initiator of the communication request message is within the location range that should be included in the communication authorization information, the communication server releases the communication service that is requested to be executed by the communication request message and is directed to the additional communication identifier; if the communication server determines that the initiator of the communication request message is located and is not located in the location range which is included in the communication authorization information and is to be located, the communication server refuses the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identifier. The location of the initiator of the communication request message may be carried in the communication request message, for example, so that the communication server may learn the location of the initiator of the communication request message after receiving the communication request message; or the communication request message carries part of information (such as the absolute position of the initiator), and after the communication server receives the communication request message, the relative position of the initiator of the communication request message can be determined according to the part of information; or after receiving the communication request message, the communication server can identify the location of the initiator of the communication request message. This is not limited.

For example, taking a communication service as a call service, the location range that should be in, that is, the callable location, is assumed to be less than or equal to the preset distance.

If the distance between the first device and the preset position is smaller than or equal to the preset distance, the first device and the second device can establish call connection. For example, the communication server determines that the location of the initiator of the communication request message (i.e., the location of the first device) is located in the location range (i.e., the calling location is less than or equal to the preset distance) included in the communication authorization information, so in step 1702, the communication server releases the communication service that is requested to be executed by the communication request message and is directed to the additional communication identifier, i.e., the communication server triggers the first device to establish a call connection with the second device.

If the distance between the first device and the preset position is greater than the preset distance, the first device and the second device cannot establish call connection. For example, the communication server determines that the location of the initiator of the communication request message is not located in the location range that should be included in the communication authorization information, so in step 1702 the communication server refuses the communication service that is requested to be performed by the communication request message and directed to the additional communication identifier, i.e. the communication server refuses the call request of the first device.

The preset location may be, for example, a location of the second device, or may be a specific location (such as a location of the vehicle owner 1 in the method 3300), which is not limited thereto.

As another example, taking a communication service as a call service, the callable locations include city 1 and city 2.

If the first device requests to call the second device in city 1 or city 2, the first device and the second device may establish a call connection. For example, the communication server determines that the location of the initiator of the communication request message (i.e., the location of the first device) is within the location range (i.e., the calling location includes city 1 and city 2) included in the communication authorization information, so that the communication server releases the communication service directed to the additional communication identifier, which is requested to be performed by the communication request message, in step 1702, the communication server triggers the first device to establish a call connection with the second device.

If the first device requests to call the second device in a city outside of city 1 and city 2, the first device and the second device may not establish a call connection. For example, the communication server determines that the location of the initiator of the communication request message is not located in the location range that should be included in the communication authorization information, so in step 1702 the communication server refuses the communication service that is requested to be performed by the communication request message and directed to the additional communication identifier, i.e. the communication server refuses the call request of the first device.

Example 2, the communication authorization information includes: the identity that the initiator of the authorized communication service should have.

The identity that the initiator of the authorized communication service should have may for example represent an identity that is able to identify the initiator, such as an additional communication identity that may be the initiator. Hereinafter, for brevity, the "identification that the initiator of the authorized communication service should have" will be simply referred to as "identification that the initiator should have". The following mainly exemplifies a number that the initiator should have to identify as the initiator.

Wherein, the due identification of the initiator can be expressed as follows: the number of the communication service directed to the second device, such as the authorization ID and/or the base number, may be performed or may also be referred to as the number of the authorized party. Taking a communication service as a call service for example, a communication number of an initiator of the communication service pointing to the additional communication identifier, that is, a callable number (such as a base number of an authorized party and/or an authorized ID of the authorized party) is represented.

Optionally, in step 1702, the communication server puts through or refuses the communication service directed to the additional communication identifier requested to be executed by the communication request message according to the communication authorization information, including: and the communication server releases or refuses the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identifier according to the identifier which is included in the communication authorization information and is supposed to be the initiator.

For example, the communication server obtains the identifier of the initiator that initiates the communication request message, and if the communication server determines that the identifier of the initiator that initiates the communication request message is the identifier that the initiator included in the communication authorization information should be, the communication server releases the communication service that is requested to be executed by the communication request message and is directed to the additional communication identifier; if the communication server determines that the identifier of the initiator initiating the communication request message is not the identifier which the initiator should have, the communication server refuses the communication service which is requested to be executed by the communication request message and is directed to the additional communication identifier. The identifier of the initiator initiating the communication request message may be carried in the communication request message, for example, so that the communication server may learn the identifier of the initiator initiating the communication request message; or the communication server may recognize the identity of the initiator that initiated the communication request message after receiving the communication request message. This is not limited.

For example, taking a communication service as a call service, the callable number includes 85500.

If the number of the first device is 85500, the first device and the second device can establish a call connection. For example, the communication server determines the number of the initiator of the communication request message (i.e. 85500), the identity of the initiator (i.e. the calling number includes 85500) that is included in the communication authorization information, so that in step 1702 the communication server releases the communication service directed to the additional communication identity that is requested to be performed by the communication request message, i.e. the communication server triggers the first device to establish a call connection with the second device.

For another example, taking a communication service as a call service, the callable number is a number in the address book of the second device.

If the number of the first device is not the number in the address book of the second device, the first device and the second device cannot establish a call connection. For example, the communication server determines the number of the initiator of the communication request message, not the identity the initiator should have (i.e. the number in the address book of the second device), so in step 1702 the communication server denies the communication service directed to the additional communication identity, which the communication request message requested to perform, i.e. the communication server denies the call request of the first device.

If the number of the first device is the number in the address book of the second device, the first device and the second device can establish a call connection. Specifically, the communication server determines the number of the initiator of the communication request message as the identifier that the initiator should have, so in step 1702 the communication server releases the communication service that is requested to be performed by the communication request message and is directed to the additional communication identifier, i.e. the communication server triggers the first device to establish a call connection with the second device.

Example 3, the communication authorization information includes: the authentication code that should be provided by the initiator of the authorized communication service.

Wherein the authentication code that the authorized initiator of the communication service should provide, or the authentication code that the authorized initiator of the communication service directed to the additional communication identity provides, indicates the authentication code included in the communication request message that the communication service directed to the second device can be performed. The verification code may be in the form of a number, a character string, or other forms, which are not limited. Hereinafter, for brevity, the "authentication code that should be provided by the initiator of the authorized communication service" will be simply referred to as "authentication code that should be provided".

Optionally, in step 1702, the communication server puts through or refuses the communication service directed to the additional communication identifier requested to be executed by the communication request message according to the communication authorization information, including: and the communication server releases or refuses the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identifier according to the verification code which is included in the communication authorization information and is required to be provided. The verification code may be, for example, a verification code agreed by both parties (or a secret number agreed by both parties). The authentication code may be received from the second device for the first device or may be obtained according to a previous agreement.

For example, the communication server obtains the verification code provided when the first device sends the communication request message, and if the communication server determines that the verification code provided when the first device sends the communication request message is the verification code to be provided included in the communication authorization information, the communication server releases the communication service which is requested to be executed by the communication request message and is directed to the additional communication identifier; if the communication server determines that the verification code provided when the first device sends the communication request message is not the verification code to be provided, which is included in the communication authorization information, the communication server refuses the communication service which is requested to be executed by the communication request message and is directed to the additional communication identifier. The verification code provided when the first device sends the communication request message may be carried in the communication request message, for example, so that the communication server may learn the verification code provided when the first device sends the communication request message.

For example, the verification code that should be provided is 1234.

If the communication request message sent by the first device includes the verification code 1234, the first device and the second device may establish a communication connection. For example, the communication server determines that the verification code (i.e. 1234) carried in the communication request message sent by the first device is the verification code (i.e. 1234) that should be provided and is included in the communication authorization information, so that in step 1702 the communication service directed to the additional communication identifier, which is requested to be performed by the communication request message, is put through by the communication server.

If the communication request message sent by the first device does not include the verification code 1234 (e.g., 1256, and does not carry the verification code), then the first device and the second device may not establish a communication connection. For example, the communication server determines that the authentication code carried in the communication request message sent by the first device is not the authentication code to be provided included in the communication authorization information, so in step 1702 the communication server refuses the communication service directed to the additional communication identifier that is requested to be performed by the communication request message.

Example 4, the communication authorization information includes: the sponsor of the authorized communication service shall associate an order number.

Wherein the order number with which the initiator of the authorized communication service should be associated, or the order number with which the initiator of the authorized communication service directed to the additional communication identity is associated (or the order number involved), indicates the order number included in the communication request message with which the communication service directed to the second device can be performed. The order number may be in the form of a number, a character string, or other forms, without limitation. The order number may be an order number such as a package or a take-out, or may be a serial number (e.g., a serial number of a workflow), or may be a work order number, or the like, without limitation. For brevity, the "order number with which the initiator of the authorized communication service should be associated" will be referred to simply as "order number with which the initiator of the authorized communication service should be associated".

Optionally, in step 1702, the communication server puts through or refuses the communication service directed to the additional communication identifier requested to be executed by the communication request message according to the communication authorization information, including: and the communication server releases or refuses the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identifier according to the verification code which is included in the communication authorization information and is required to be associated.

For example, the communication server obtains the order number (or the related order number) associated with the communication request message, and if the communication server determines that the order number associated with the communication request message is the verification code to be associated included in the communication authorization information, the communication server releases the communication service which is requested to be executed by the communication request message and is directed to the additional communication identifier; if the communication server determines that the order number associated with the communication request message is not the verification code to be associated, which is included in the communication authorization information, the communication server refuses the communication service which is requested to be executed by the communication request message and is directed to the additional communication identifier. The order number associated with the communication request message may be carried in the communication request message, for example, so that the communication server may learn the order number associated with the first device when sending the communication request message; or the communication server may identify the order number associated when the first device sends the communication request message after receiving the communication request message. This is not limited.

For example, the verification code that should be associated is 123456.

If the order number 123456 is included in the communication request message sent by the first device, the first device may establish a communication connection with the second device. For example, the communication server determines that the order number (i.e. 123456) carried in the communication request message sent by the first device is the verification code (i.e. 123456) to be associated included in the communication authorization information, so in step 1702 the communication server releases the communication service directed to the additional communication identifier, which is requested to be performed by the communication request message.

If the order number 123456 is not included in the communication request message sent by the first device, the first device and the second device may not establish a communication connection. For example, the communication server determines that the order number carried in the communication request message sent by the first device is not the verification code included in the communication authorization information to be associated, so in step 1702 the communication server refuses the communication service directed to the additional communication identifier requested to be performed by the communication request message.

Example 5, the communication authorization information includes: the type of device that the initiator of the authorized communication service should be.

Wherein the device type that the authorized initiator of the communication service should have, or the device type that the authorized initiator of the communication service directed to the additional communication identity should be, means the device type that the initiator of the communication service directed to the additional communication identity can perform. Hereinafter, for brevity, "the device type that the initiator of the authorized communication service should have" will be simply referred to as "the device type that should have".

Optionally, in step 1702, the communication server puts through or refuses the communication service directed to the additional communication identifier requested to be executed by the communication request message according to the communication authorization information, including: the communication server releases or refuses the communication service which is requested to be executed by the communication request message and is directed to the additional communication identification according to the due equipment type included in the communication authorization information.

For example, the communication server obtains the device type of the initiator of the communication request message, and if the communication server determines that the device type of the initiator of the communication request message is the due device type included in the communication authorization information, the communication server releases the communication service which is requested to be executed by the communication request message and is directed to the additional communication identifier; if the communication server determines that the device type of the initiator of the communication request message is not the due device type included in the communication authorization information, the communication server refuses the communication service which is requested to be executed by the communication request message and is directed to the additional communication identifier. The device type of the initiator of the communication request message may be carried in the communication request message, for example, so that after the communication server receives the communication request message, the device type of the initiator of the communication request message may be known; or the communication server may identify the device type of the initiator of the communication request message after receiving the communication request message. This is not limited.

For example, taking a communication service as a call service as an example, the type of the device is a smart phone.

If the device type of the first device is a smart phone, the first device and the second device can establish call connection. For example, the communication server determines the device type (i.e. smart phone) of the initiator of the communication request message, which is the due device type (i.e. smart phone) included in the communication authorization information, so in step 1702 the communication server releases the communication service directed to the additional communication identifier, which is requested to be performed by the communication request message, i.e. the communication server triggers the first device to establish a call connection with the second device.

If the device type of the first device is voice relay (i.e. possibly through a software call), the first device and the second device may not establish a call connection. For example, the communication server determines the device type (i.e., voice relay) of the initiator of the communication request message, not the due device type (i.e., smart phone) included in the communication authorization information, so that the communication server denies the communication service directed to the additional communication identity, which the communication request message requested to perform, i.e., the communication server denies the call request of the first device, in step 1702.

The above examples of the authorization object information are exemplary descriptions, and the embodiments of the present application are not limited thereto.

2) Authorization time range

The authorization time range, i.e. the time range in which the point in time of initiation of the authorized communication service is indicated, may be used to indicate the range in which the point in time of initiation of the communication service, authorized by the target user, directed to the additional communication identity is located.

As an example, the authorization time range includes any one or more of the following: the start time of the authorized communication service initiation time point and the end time of the authorized communication service initiation time point.

Example 6, the communication authorization information includes: the start time of the point in time of initiation of the authorized communication service.

Wherein the start time of the authorized initiation point in time of the communication service indicates the start time at which the communication service directed to the second device can be performed. Taking the communication service as a call service for example, the start time of authorizing the execution of the communication service directed to the second device, i.e. the start time of the callable (e.g. also called callable time period) is indicated. The start time may be a certain time or a certain date, and is not limited thereto. Hereinafter, for brevity, "start time of initiation time point of authorized communication service" will be simply referred to as "start time to be at".

Optionally, in step 1702, the communication server puts through or refuses the communication service directed to the additional communication identifier requested to be executed by the communication request message according to the communication authorization information, including: the communication server releases or refuses the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identification according to the starting time which is included in the communication authorization information and is supposed to be at.

For example, the communication server obtains the time of sending the communication request message (i.e. the initiation time of the communication request message), and if the communication server determines that the time of sending the communication request message belongs to the initiation time (i.e. is located after or the same as the initiation time) included in the communication authorization information, the communication server releases the communication service which is requested to be executed by the communication request message and is directed to the additional communication identifier; if the communication server determines that the time of sending the communication request message does not belong to the start time (i.e., is located before) that should be included in the communication authorization information, the communication server refuses the communication service that is requested to be executed by the communication request message and is directed to the additional communication identifier. The time of sending the communication request message may be carried in the communication request message, for example, so that the communication server may know the time of sending the communication request message; or the communication server may recognize the time of transmitting the communication request message after receiving the communication request message. This is not limited.

For example, taking a communication service as a call service, the starting time of the callable is 9 a.m.

If the first device calls the second device after 9 a.m., the first device and the second device may establish a call connection. For example, the communication server determines the time of sending the communication request message (i.e. after 9 a.m.), which is the start time (i.e. 9 a.m.), which should be included in the communication authorization information, so that in step 1702 the communication server releases the communication service directed to the additional communication identity, which is requested to be performed by the communication request message, i.e. the communication server triggers the first device to establish a call connection with the second device.

If the first device calls the second device 9 a.m., the first device and the second device may not establish a call connection. For example, the communication server determines that the time at which the communication request message was sent (i.e., 9 a.m.), does not belong to the start time at which the communication authorization information should be included (i.e., 9 a.m.), so the communication server refuses the communication service directed to the additional communication identity, i.e., the communication server refuses the call request of the first device, which the communication request message requested to perform in step 1702.

Example 7, the communication authorization information includes: the end time of the point in time of initiation of the authorized communication service.

Wherein the end time of the authorized initiation point in time of the communication service indicates the end time at which the communication service directed to the second device can be performed. Taking the communication service as a call service for example, the end time of the communication service which is authorized to be performed towards the second device, i.e. the end time of the callable (e.g. also called callable time period) is indicated. Hereinafter, for brevity, "the end time of the initiation time point of the authorized communication service" will be simply referred to as "the end time that should be present".

Optionally, in step 1702, the communication server puts through or refuses the communication service directed to the additional communication identifier requested to be executed by the communication request message according to the communication authorization information, including: and the communication server releases or refuses the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identifier according to the ending time which is included in the communication authorization information and is supposed to be in.

For example, the communication server obtains the time of sending the communication request message, and if the communication server determines that the time of sending the communication request message meets the ending time (i.e. is located before or the same as the ending time) included in the communication authorization information, the communication server releases the communication service which is requested to be executed by the communication request message and is directed to the additional communication identifier; if the communication server determines that the time of sending the communication request message does not satisfy the ending time (i.e., is located after) that should be included in the communication authorization information, the communication server refuses the communication service that is requested to be executed by the communication request message and is directed to the additional communication identifier. The time of sending the communication request message may be carried in the communication request message, for example, so that the communication server may know the time of sending the communication request message; or the communication server may recognize the time of transmitting the communication request message after receiving the communication request message. This is not limited.

For example, taking a communication service as a call service, the end time of the callable is 9 pm.

If the first device calls the second device 9 pm before, the first device and the second device may establish a call connection. For example, the communication server determines when the communication request message is sent (i.e. 9 pm before), and satisfies the ending time that should be included in the communication authorization information (i.e. 9 pm), so in step 1702 the communication server releases the communication service that is requested to be performed by the communication request message and is directed to the additional communication identifier, i.e. the communication server triggers the first device to establish a call connection with the second device.

If the first device calls the second device after 9 pm, the first device and the second device may not establish a call connection. For example, the communication server determines that the time at which the communication request message was sent (i.e., 9 pm later) does not satisfy the ending time that should be included in the communication authorization information (i.e., 9 pm later), so the communication server denies the communication service directed to the additional communication identity that the communication request message requested to perform in step 1702, i.e., the communication server denies the call request of the first device.

It is to be understood that the above examples regarding the authorized time range are illustrative and embodiments of the present application are not limited thereto. For example, the communication authorization information includes a start time and a length of time that the target user is authorized to be. As another example, the communication authorization information includes an ending time and a length of time that the target user is authorized to be.

3) Validity period of communication authorization information

The validity period of the communication authorization information may indicate the validity period of the communication authorization information, that is, the time at which the communication authorization information can be used for verification, or may indicate the expiration time of the communication authorization information, that is, the time at which the communication authorization information cannot be used for verification.

As an example, the validity period of the communication authorization information may include one or more of the following: start time, end time, length of time.

Example 8, the communication authorization information includes: validity period of the communication authorization information.

Optionally, in step 1702, the communication server puts through or refuses the communication service directed to the additional communication identifier requested to be executed by the communication request message according to the communication authorization information, including: and the communication server releases or refuses the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identifier according to the validity period of the communication authorization information included in the communication authorization information.

For example, the communication server obtains the time of sending the communication request message, and if the communication server determines that the time of sending the communication request message belongs to the validity period of the communication authorization information included in the communication authorization information, the communication server releases or refuses the communication service which is requested to be executed by the communication request message and is directed to the additional communication identifier according to the communication authorization information; if the communication server determines that the time of sending the communication request message does not belong to the validity period of the communication authorization information included in the communication authorization information, the communication server may directly put through, or may directly reject, or may have other operations, which is not limited. The time of sending the communication request message may be carried in the communication request message, for example, so that the communication server may know the time of sending the communication request message; or the communication server may recognize the time of transmitting the communication request message after receiving the communication request message. This is not limited.

For example, taking a communication service as a call service, the expiration time of the validity period of the communication authorization information is 9 months and 16 days.

If the first device requests to call the second device before 9 months and 16 days, the communication server may put through or reject the communication service directed to the additional communication identifier, which is requested to be performed by the communication request message, according to the communication authorization information. For example, assume that an initiator is included in the communication authorization information and the initiator includes the first device. If the first device requests to call the second device before day 9 and 16, the first device and the second device may establish a call connection, i.e., the communication server triggers the first device to establish a call connection with the second device in step 1702. If the first device requests to call the second device after 9 months and 16 days, then the communication server may reject the call request of the first device in step 1702.

It will be appreciated that the above examples are merely simple illustrative illustrations, and that the embodiments of the application are not limited thereto, and that any variations belonging to the above examples are applicable to the embodiments of the application.

It will also be appreciated that the communication authorization information may also include other authorization-related information. In an example, the communication authorization information may further include whether to renew, that is, whether to renew after the expiration of the communication authorization information, where the value of whether to renew may be yes or no, for example. For example, the communication authorization information includes a validity period of the communication authorization information and whether to renew, and if the communication authorization information includes a renewal period, the renewal period may be performed after the validity period of the communication authorization information. As yet another example, the communication authorization information may further include a renewal manner, that is, how to renew after the communication authorization information expires, such as sending a sms message or sending a mail to notify the authorization Fang Xuqi, and so on.

It will be further appreciated that the present application is primarily illustrative and not limited in this regard, including information related to authorization. For example, the communication authorization information may also include information that prohibits (or does not permit) communication (e.g., information that does not permit a call, such as a time period that does not permit a call, such as a location that does not permit a call, etc.).

For example, the communication authorization information may include a location (e.g., a non-callable location) where an initiator of communication traffic directed to the additional communication identity is prohibited (either not allowed or unauthorized). For example, the non-callable locations include city 3. If the first device requests to call the second device in a city other than city 3, the first device and the second device may establish a call connection, i.e., in step 1702, the communication server triggers the first device and the second device to establish a call connection; if the first device requests to call the second device in city 3, the first device and the second device may not establish a call connection, i.e., the communication server denies the call request of the first device in step 1702.

As another example, the communication authorization information may include a communication number (e.g., a non-callable number) that prohibits (or does not permit, or is unauthorized) from directing to the originator of the communication service of the additional communication identity. For example, the non-callable number includes 85511. If the number of the first device is 85511, the first device and the second device cannot establish the call connection, i.e., the communication server refuses to establish the call connection between the first device and the second device in step 1702.

As another example, the communication authorization information may include a range in which the initiation point of communication traffic directed to the additional communication identity is prohibited (or not permitted, or unauthorized) (e.g., a range in which the non-callable point of time is located). For example, the non-callable period is 9 pm to 9 am. If the first device calls the second device from 9 pm to 9 am, the communication server denies the call request of the first device in step 1702.

It will also be appreciated that the above descriptions are provided separately for use with each information, and that each information may be used alone or in combination. For example, the communication authorization information includes a callable start time and a callable location, and then the call request initiated by the first device needs to satisfy the callable start time and the callable location at the same time to establish a call connection with the second device. For another example, the credit authorization information includes a start time and an end time of the callable, and the call request initiated by the first device may only establish a call connection with the second device for a period of time between the start time and the end time of the callable.

The communication authorization information is described above and the specific use of the communication authorization information is described below.

Thirdly, the communication server releases or refuses the communication service requested to be executed by the communication request message according to the communication authorization information.

Optionally, the communication server determines to check (or referred to as detection or referred to as authorization) the communication request message according to the additional communication identifier carried in the communication request message, that is, determines to decide to release or reject the communication service requested to be executed by the communication request message according to the communication authorization information. For example, if the communication server is the additional communication identifier according to the additional communication identifier carried in the communication request message, the communication service requested to be executed by the communication request message is released or refused according to the communication authorization information. For example, the communication request message includes an authorization ID, and if the authorization ID belongs to a preset number segment, the communication request message is checked, that is, the communication service requested to be executed by the communication request message is released or rejected according to the communication authorization information. It will be appreciated that the conditions for triggering the communication server to release or reject the communication service requested to be performed by the communication request message according to the communication authorization information are not limited. For example, a flag may be carried in the additional communication identifier, where the flag is used to trigger the communication server to release or reject the communication service requested to be executed by the communication request message according to the communication authorization information.

Two schemes by which the communication server can release or reject the communication service requested to be executed by the communication request message according to the communication authorization information are described below.

Scheme 1: and the communication server determines to put through or reject the communication service requested to be executed by the communication request message according to the stored communication authorization information.

Optionally, the method 1700 further includes: the communication server receives a first message from the second device, the first message including the communicated authorization information; the communication server stores the correspondence between the communication authorization information and the additional communication identifier. As an example, the communication server may locally save the correspondence between the communication authorization information and the additional communication identity.

The communication server stores the corresponding relation between the communication authorization information and the additional communication identifier, namely the communication server stores information, wherein the information comprises the additional communication identifier and the communication authorization information corresponding to the additional communication identifier, and the communication authorization information can be known to be the authorization information corresponding to the additional communication identifier based on the stored information. The correspondence may be in the form of a table, such as a call authorization table similar to that described in the above term interpretation section, or an identification authorization table; or may be in the form of a two-dimensional code, such as an authorization code similar to that described in the above section for term interpretation, etc., without limitation. In this regard, the description thereof will not be repeated.

For example, the communication server receives a communication request message from a first device, where the communication request message is used to request to establish a call connection with a second device, and the communication request message includes a call number of the second device, where the call number of the second device corresponds to communication authorization information; the communication server determines communication authorization information corresponding to the call number of the second device according to the call number of the second device and the corresponding relation between the stored communication authorization information and the call number; and triggering or refusing the first equipment to establish call connection with the second equipment by the communication server according to the corresponding communication authorization information.

Fig. 19 shows a schematic diagram applicable to scheme 1 provided in an embodiment of the present application.

Assuming that the second device has an authorization ID of 13912345671 and the first device has an authorization ID of 13912345670, the communication server is a network device that serves the first device and the second device. The method 1900 shown in fig. 19 may include the steps of:

1901, the first device sends a communication request message to a communication server.

Wherein the communication request message (or may also be called a call request message) includes: the authorization ID of the first device (i.e., 13912345670), and the authorization ID of the second device (i.e., 13912345671).

In step 1901, the user of the first device (e.g., user 1) calls the user of the second device (e.g., user 2) through the communication server, and the authorization ID of user 1 and the authorization ID of user 2 are carried in the call request.

1902, the communication server queries communication authorization information to confirm whether the authorization is normal.

After receiving the communication request message, the communication server may query the communication authorization information corresponding to the authorization ID (i.e. 13912345671) of the user 2, and confirm whether the user 1 has the authorization of the user 2.

For example, the communication server holds a correspondence between the communication authorization information and the authorization ID (i.e., 13912345671) of the user 2; the communication server determines communication authorization information corresponding to the authorization ID of the user 2 according to the authorization ID of the user 2 and the stored correspondence included in the communication request message, where the communication authorization information includes: the authorization ID of the authorized party. If the authorized party's authorization ID includes the user 1's authorization ID (i.e., 13912345670), then the communication server knows that the calling user (i.e., user 1) has authorization to the called user (i.e., user 2) based on the communication authorization information; if the authorized party's authorization ID does not include the user 1's authorization ID (i.e., 13912345670), then the communication server knows that the calling user (i.e., user 1) is not authorized by the called user (i.e., user 2) based on the communication authorization information.

For another example, the communication server holds communication authorization information; the communication server determines communication authorization information corresponding to the authorization ID of the user 2 according to the authorization ID of the user 2 included in the communication request message, where the communication authorization information includes: the authorization ID of the authorizer (i.e., the authorization ID of user 2 (i.e., 13912345671)) and the authorization ID of the authorized party. If the authorized party's authorization ID includes the user 1's authorization ID (i.e., 13912345670), then the communication server knows that the calling user (i.e., user 1) has authorization to the called user (i.e., user 2) based on the communication authorization information; if the authorized party's authorization ID does not include the user 1's authorization ID (i.e., 13912345670), then the communication server knows that the calling user (i.e., user 1) is not authorized by the called user (i.e., user 2) based on the communication authorization information.

Assuming in step 1902 that the communication server confirms that the authorization is normal, the method 1900 further includes step 1903.

1903, the communication server triggers the first device to establish a call connection with the second device.

The communication server may trigger the establishment of a call connection between the calling user (i.e., user 1) and the called user (i.e., user 2) based on the confirmation result, so that the calling user and the called user may make a call.

Based on the above scheme 1, the communication server may verify the communication request message of the first device based on the stored communication authorization information, so as to determine whether the second device is willing to accept the communication request message of the first device, and trigger the first device to establish a call connection with the second device after determining that the second device is willing to accept the communication request message of the first device.

Scheme 2: and the communication server determines to release or reject the communication service requested to be executed by the communication request message according to the communication authorization information carried in the communication request message.

For example, the communication request message may include a ciphertext of the communication authorization information (i.e., encrypted communication authorization information) in addition to the additional communication identification of the second device.

For another example, the communication request message includes a digital signature in addition to the additional communication identification of the second device. The digital signature may be a digital signature on the communication authorization information. The digital signature may be added by the communication server or the second device, without limitation.

Fig. 20 shows a schematic diagram applicable to scheme 2 provided in an embodiment of the present application.

As shown in fig. 20, assuming that the authorization ID of the second device is 13912345671, the communication server is a network device that provides services for the first device and the second device. The method 2000 shown in fig. 20 may include the steps of:

2002, the first device sends a communication request message to a communication server.

Wherein the communication request message (or may also be called a call request message) may include: the authorization ID of the second device (i.e., 13912345671) and the ciphertext of the communication authorization information. Alternatively, the communication request message may include an authorization ID (i.e., 13912345671) of the second device, where the authorization ID (i.e., 13912345671) of the second device has a binding relationship with a ciphertext of the communication authorization information, where the ciphertext of the communication authorization information is pre-stored in the background of the communication server, and if the authorization ID is dialed, the communication server displays the ciphertext of the communication authorization information.

In step 2002, a user of a first device (e.g., user 1) calls a user of a second device (e.g., user 2) through a communication server, and carries an authorization ID of user 2 and ciphertext of communication authorization information in a call request.

Optionally, before step 2002, the method 2000 further comprises step 2001: the first device parses the communication authorization information. By parsing the communication authorization information, the authorization ID (i.e., 13912345671) of the second device and the ciphertext of the communication authorization information may be obtained. For example, the communication authorization information may be in the form of an authorization code (the authorization code may be displayed in the form of a two-dimensional code, for example), and the first device obtains the authorization ID (i.e. 13912345671) of the second device and the ciphertext of the communication authorization information by parsing the authorization code. For the authorization code, reference is made to the description of the preceding term section, which is not repeated here.

2003, the communication server decrypts the ciphertext of the communication authorization information, and confirms whether the authorization is normal.

After receiving the communication request message, the communication server can decrypt the ciphertext of the communication authorization information to confirm whether the user 1 is authorized by the user 2.

For example, if the ciphertext of the communication authorization information includes the authorization ID of the authorized party. The communication server decrypts the ciphertext of the communication authorization information to obtain the authorization ID of the authorized party. If the authorized party's authorization ID includes the user 1 authorization ID (i.e., 13912345670), then the communication server confirms that the calling user (i.e., user 1) has authorization with the called user (i.e., user 2); if the authorized party's authorization ID does not include the user 1 authorization ID (i.e., 13912345670), the communication server confirms that the calling user (i.e., user 1) is not authorized by the called user (i.e., user 2).

Assume that in step 2003, the communication server confirms that the authorization is normal.

In step 2004, the communication server triggers the first device to establish a call connection with the second device.

Based on the above scheme 2, the communication server may check the communication request message of the first device based on the communication authorization information carried in the communication request message, so as to determine whether the second device is willing to accept the communication request message of the first device, and trigger the first device to establish a call connection with the second device after determining that the second device is willing to accept the communication request message of the first device.

Optionally, the communication request message further includes an identifier for identifying the authorized party, the identifier for identifying the authorized party corresponds to identification authorization information, and the identification authorization information is used for characterizing: the identification authorizer authorizes the initiator of the communication request message, takes the identification of the identification authorizer as the initiator identification, and initiates the communication service pointing to the additional communication identification. In this manner, the first device may send a communication request message to the second device on behalf of a third party (e.g., identifying an authorized party). The following description is made with reference to fig. 21. It will be appreciated that the scheme shown in fig. 21 may be used in combination with the scheme shown in fig. 17, or may be used alone, without limitation.

Fig. 21 is a schematic diagram of a communication method 2100 provided in an embodiment of the present application. Method 2100 may include the following steps.

2101, the application server determines identification authorization information, wherein the identification authorization information is used for characterizing: the identification authorizer authorizes the initiator of the communication request message, takes the identification of the identification authorizer as the initiator identification, and initiates the communication service pointing to the target user.

Wherein the target user may be associated with at least one subscriber identity module, the subscriber identity module being associated with at least one additional communication identity, and a base communication identity. Reference may be made specifically to the description in method 1700, which is not repeated here.

The identification authorization information may be authorization information corresponding to the identification of the authorized party, or may also be authorization information corresponding to the identification of the authorized party (or information identifying the authorized party), which is not limited. The following mainly takes the identification authorization information as the authorization information corresponding to the identification of the identification authorized party as an example for illustration.

The identifier of the identifying authority indicates that the identifier of the identifying authority can be identified, that is, the corresponding identifying authority information can be obtained through the identifier of the identifying authority. As an example, the identification of the authorized party may be an additional communication identification. For additional communication identifications, reference is made to the above description, and no further description is given here.

The application server sends 2102 a request message to the communication server, the request message including identification authorization information.

Accordingly, the communication server receives the request message from the application server. The communication server may store the identification authorization information, or store a correspondence between the identification authorization information and the identification of the identification authorizer.

Wherein identifying the authorizer may mean authorizing the first device (or initiator) to identify the authorizer as an initiator identification, initiate organization (organization) or person (identification) directed to the second device (or target user); alternatively, identifying the authorizer may represent an organization or individual authorizing the first device (or initiator) to identify the authorizer as an initiator identification, initiating an additional communication identification (or additional communication identification of the target user) directed to the second device. The user corresponding to the identification authorized party can be an individual user or an organization (such as an enterprise), and the identification authorized party is not limited. Hereinafter, for brevity, the device that identifies the authorized party is referred to as a third device. Accordingly, the application server may be, for example, a network device that provides services for a certain user or a certain organization.

For example, the enterprise (i.e., an instance of identifying an authorized party) is authorized to make a call to the employee (i.e., an instance of the user to which the first device corresponds) using the identity of the enterprise (i.e., using the base number or authorized ID of the enterprise).

Through the application, the application server sends the identification authorization information to the communication server. Thus, the first device may request to perform communication services directed to the second device on behalf of the third device when requesting to perform communication services directed to the second device.

Optionally, identifying the authorization information includes: an identification identifying the authorized party and/or an identification identifying the authorized party. As an example, the identification of the authorized party is an additional communication identification of the enterprise employee. As an example, the identification identifying the authorized party is an enterprise additional communication identification.

Optionally, the authorization request information further includes an additional communication identifier corresponding to the target user, and the identifier identifies the initiator of the authorization request message authorized by the authorizer, takes the identifier identifying the authorizer as the initiator identifier, and initiates the communication service directed to the additional communication identifier. Optionally, the additional communication identifier may correspond to communication authorization information. For the communication authorization information, reference may be made to the above description, and no further description is given here.

For example, if the authorization request information includes an authorization ID of the corporation employee, the corporation employee may call the second device using the identity of the corporation (i.e., using the corporation's base number or authorization ID). In particular, the related description of the basic number or the authorization ID usage authorization may be referred to in the previous term explanation section, and will not be repeated here.

Optionally, the communication server receives a communication request message from the first device, the communication request message including an identification identifying the authorizer; the communication server releases or refuses the communication service requested to be executed by the communication request message according to the stored identification authorization information or the corresponding relation between the stored authorization information and the identification of the identification authorized party.

For example, the communication server receives a communication request message from an employee of the enterprise, the communication request message requesting to perform a call service directed to the personal user (i.e., one example of a user corresponding to the second device), the communication request message including an authorization ID of the personal user and a base number of the enterprise (e.g., 85500); if the communication server knows that the staff member of the enterprise has the right to call the personal user by using the number (85500) of the enterprise based on the stored identification authorization information, the communication service requested to be executed by the communication request message is released.

In order to facilitate understanding, the following exemplifies a call service, and an embodiment of the present application will be described with reference to fig. 22 to 33. The steps involved therein may be referred to in particular as described above. In the following, for the distinction, the communication authorization information is denoted as authorization information #1, the identification authorization information is denoted as authorization information #2, the first message is denoted as message #1, and the second message is denoted as message #3.

Fig. 22 is a schematic flow chart diagram of a communication method 2200 provided by an embodiment of the present application. The method 2200 may be used in a scenario where B2C authorizes based on an authorization ID, where the enterprise and person are affiliated with the same operator. In method 2200, assume that the first device is a device (e.g., a terminal device (e.g., a smart phone)) of a home caller, e.g., an enterprise employee; the second device is a device (such as a terminal device (such as a smart phone)) belonging to a called user, and the called user is a personal user; the third device is a device (such as an application server) of the home enterprise; the communication server is a device in a communication network that provides services for the first device and the second device. The method 2200 may include the following steps.

2201, the second device sends a message #1 to the authorized communication light application server.

For example, the second device detects an operation of the individual user, authorizes the number (e.g., 85500) of the business (e.g., business bank) in the authorized communication light application, and after detecting an operation of the individual user to fill out the business number, authorization information #1, and click the ok button, the authorized communication light application sends a message #1 (i.e., an example of the first message) to an authorized communication light application server in the communication network serving the second device.

As an example, the message #1 may carry the authorization ID of the individual user and the authorization information #1. Message #1 may also be referred to as a request message or a notification message, the naming of which does not limit the scope of the present application.

Wherein the authorization ID of the individual user, i.e. the authorization ID representing the authorizing party. As previously described, the authorization ID may be a number consisting of X digits. For example, the personal user's authorization ID is a number consisting of 11 digits, as previously mentioned 19912445670 in the example of fig. 5; for another example, the personal user's authorization ID is a number consisting of 4 digits, such as 0001. For convenience of description, the authorization ID of the individual user is taken as 0001 as an example for illustration.

Wherein the authorization information #1 may include, but is not limited to, one or more of the following: the authorization ID of the authorizer, the base number of the authorizer (e.g., 85500), the authorization ID of the authorizer, the callable time period, the callable location, the authorization valid period, whether to renew, the renewal mode, other auxiliary information. Reference may be made specifically to the foregoing description, and details are not repeated here. The following mainly exemplifies that the authorization information #1 includes a basic number (for example, 85500) of an authorized party.

It will be appreciated that the authorization information #1 may include one or more numbers (such as a base number and/or an authorization ID) of the authorized party, which is not limited in this application.

2202, the authorization communication light application server forwards the message #1 to the authorization management service AS.

The authorized communication light application server receives the message #1 of the second device and forwards the authorization request to the authorization management service AS for processing.

2203, the authorization management service AS saves the correspondence between the authorization information #1 and the authorization ID of the individual user.

After receiving the message #1, the authorization management service AS establishes and stores a corresponding relationship between the authorization information #1 and the authorization ID (e.g. 0001) of the individual user, where the authorization information #1 includes a base number (e.g. 85500) of the authorized party, and the authorization information #1 may also include the authorization ID (e.g. 0001) of the authorized party. The authorization information #1 is authorization information corresponding to the individual user (or authorization information corresponding to the authorization ID of the individual user), and may be used to check (or detect) a call request message for calling the individual user (or may be used to check (or detect) a call request message for calling the authorization ID of the individual user). The authorization information #1 may be, for example, a call authorization table of the previous term interpretation section.

The second device issues 2204 an authorization ID of the individual user to the third device.

The personal user may issue an own authorization ID to the enterprise through the second device, or the personal user may register an own authorization ID in the enterprise, so that the enterprise may obtain the authorization ID of the personal user, and may call the personal user.

The third device sends 2205 a second message to the authorization management service AS.

The third device sending a second message to the authorization management service AS may for example comprise: the server of the enterprise sends a second message to the authorization management service AS. The third device may authorize the enterprise employee to call the client using the enterprise's number by sending a second message to the authorization management service AS.

The second message may include, for example: an authorization ID and/or base number of the business (e.g., 85500), an authorization ID of the employee of the business, an authorization ID of the individual user (e.g., 0001). If the second message includes the authorization ID of the corporation, it indicates that the corporation employee can use the corporation's authorization ID to call the client. If the second message includes the base number of the business, it indicates that the business employee can use the base number of the business to call the customer. If the second message includes the base number and the authorization ID of the business, it indicates that the business employee can use the base number of the business to call the customer, or use the authorization ID of the business to call the customer.

As previously described, the authorization ID may be a number consisting of X digits. For example, the employee's authorization ID is a number consisting of 11 digits, as in 19912445673 mentioned in the previous example; as another example, the employee's authorization ID is a number consisting of 4 digits, such as 0002. For convenience of description, an exemplary explanation will be given below taking an authority ID of an enterprise employee as 0002.

The authorization management service AS holds 2206 the authorization information #2.

After receiving the second message, the authorization management service AS establishes and saves authorization information #2, where the authorization information #2 includes: an authorization ID and/or base number of the business (e.g., 85500), an authorization ID of the employee of the business, an authorization ID of the individual user (e.g., 0001). The authorization information #2 is authorization information corresponding to the enterprise, and can be used to check (or detect) the call request message from the enterprise. The authorization information #2 may be, for example, an identification authorization table of the previous term interpretation section.

The third device sends 2207 the authorization ID of the individual user to the first device.

The third device sends the personal user's authorization ID to the first device so that the enterprise employee can obtain the personal user's authorization ID and can then call the personal user.

The first device sends 2208 a call request message (an example of a communication request message) to the S-CSCF.

The enterprise employee may call the personal user's authorization ID through the authorized communication light application of the first device. The call request is sent to an S-CSCF in the communication network.

The call request message may carry: an authorization ID of the individual user (e.g., 0001), an authorization ID of the employee of the enterprise (e.g., 0002), and a number of the enterprise (e.g., 85500).

The s-CSCF sends the query information to the authorization management service AS 2209.

The query information is used to instruct the authorization management service AS to check (or detect) the call request message. Regarding the condition for triggering the S-CSCF to send the query information to the authorization management service AS, or the condition for triggering whether the confirmation authorization is normal, reference may be made to the related description in the method 1700, which is not repeated here.

In step 2209, the S-CSCF may invoke an interface of the authorization management service AS to check the call request message according to the call request message.

2210, the authorization management service AS confirms whether the authorization is normal.

The authorization management service AS may confirm whether the enterprise employee has access to the enterprise's number and whether the enterprise has authorization to the individual user. The authorization management service AS may confirm whether the enterprise has authorization to the individual user based on the authorization information #1, and the authorization management service AS may confirm whether the employee of the enterprise has authority to use the number of the enterprise based on the authorization information # 2.

For example, the authorization management service AS determines the corresponding authorization information #1 according to the authorization ID (e.g. 0001) of the personal user carried in the call request message and the correspondence saved in step 2203, and if the authorization information #1 includes the base number (e.g. 85500) of the authorized party, the authorization management service AS learns that the enterprise has authorization of the personal user based on the authorization information # 1. For another example, assuming that the authorization information #1 includes an authorization ID of the authorized party and a basic number of the authorized party, the authorization management service AS searches for the corresponding authorization information #1 according to the authorization ID (e.g., 0001) of the personal user carried in the call request message, and if the basic number of the authorized party included in the authorization information #1 has 85500, the authorization management service AS learns that the enterprise has authorization of the personal user based on the authorization information # 1. 85500

For example, as in step 2206, the authorization information #2 includes the authorization ID and/or base number of the corporation (e.g., 85500), the authorization ID of the corporation's employee, and the authorization ID of the individual user (e.g., 0001). If the authorization management service AS knows based on the authorization information #2 that the employee of the enterprise (e.g. the authorization ID 0002) has access to the number of the enterprise (e.g. 85500).

Assume that in step 2210, the authorization management service AS confirms that the authorization is normal.

2211, the authorization management service AS returns a confirmation result to the S-CSCF.

After confirming the authorization, the authorization management service AS returns the confirmation result to the S-CSCF.

2212, the s-CSCF triggers the first device to establish a call connection with the second device.

The S-CSCF may trigger the establishment of a call connection between the first device and the second device based on the confirmation result, and thus the enterprise employee may talk with the individual user.

Based on the scheme, the personal user can authorize the enterprise to call itself, the enterprise can authorize the enterprise staff to call the personal user on behalf of the enterprise, and the communication server can verify the call request based on the saved authorization information #1, and after confirming that the authorization is normal, the establishment of call connection between the equipment of the home enterprise staff and the equipment of the home personal user is triggered. Therefore, privacy disturbance problems in the B2C scene, such as that marketing/service calls of enterprises possibly disturb customer privacy and are complained by customers, can be relieved.

Fig. 23 is a schematic flow chart diagram of a communication method 2300 provided by an embodiment of the application. The method 2300 may be used in a scenario where B2C authorizes based on an authorization ID, where businesses and individuals home different operators. In method 2300, assume that the first device is a device (e.g., a terminal device (e.g., a smart phone)) of a home caller, e.g., an enterprise employee; the second device is a device (such as a terminal device (such as a smart phone)) belonging to a called user, and the called user is a personal user; the third device is a device (such as an application server) of the home enterprise; the first communication server is a device in a communication network that serves the second device and the second communication server is a device in a communication network that serves the first device. Reference may be made to the description in method 2200 for the communication server, which is not further described herein. The method 2300 may include the following steps.

2301, the second device sends a message #1 to the first communication server.

As an example, the message #1 may carry the authorization ID of the individual user and the authorization information #1.

Step 2301 is similar to step 2201 and will not be described again here.

2302, the first communication server holds a correspondence relationship between the authorization information #1 and the authorization ID of the individual user.

After receiving the message #1, the first communication server establishes and saves a correspondence between the authorization information #1 and the authorization ID of the personal user, where the authorization information #1 includes a base number (for example 85500) of the authorized party, and the authorization information #1 may also include the authorization ID (for example 0001) of the authorized party. The authorization information #1 is authorization information corresponding to an individual user (or authorization information corresponding to an authorization ID of the individual user), and may be used to check (or detect) a call request message for calling the individual user (or may be used to check (or detect) a call request message for calling the authorization ID of the individual user). The authorization information #1 may be, for example, a call authorization table of the previous term interpretation section.

2303, the second device issues an authorization ID of the individual user to the third device.

Step 2303 is similar to step 2204 and is not described in detail herein.

2304, the third device sends a second message to the first communication server.

The third device sending a second message to the first communication server may include, for example: the server of the enterprise sends a second message to the first communication server. The third device may authorize the enterprise employee to call the client using the enterprise's number by sending a second message to the first communication server.

The second message may include, for example: an authorization ID and/or base number for the business (e.g., 85500), an authorization ID for the employee of the business (e.g., 0002), and an authorization ID for the individual user (e.g., 0001).

Step 2304 is similar to step 2205 and is not described in detail herein.

2305, the first communication server holds authorization information #2.

After receiving the second message, the first communication server establishes and saves authorization information #2, where the authorization information #2 includes: an authorization ID and/or base number for the business (e.g., 85500), an authorization ID for the employee of the business (e.g., 0001), an authorization ID for the individual user (e.g., 0001). The authorization information #2 is authorization information corresponding to the enterprise, and can be used to check (or detect) the call request message from the enterprise. The authorization information #2 may be, for example, an identification authorization table of the previous term interpretation section.

2306, the third device sends the authorization ID of the individual user to the first device.

Step 2306 is similar to step 2207 and is not described in detail herein.

2307, the first device transmits a call request message to the second communication server.

The enterprise employee may call the personal user's authorization ID through the authorized communication light application of the first device. The call request is sent to a second communication server, i.e. a communication network serving the enterprise employee.

2308, the second communication server forwards the call request message to the first communication server.

The communication network serving the first device forwards the call request message to the communication network serving the second device.

2309, the first communication server confirms whether the authorization is normal.

The first communication server may confirm whether the corporation employee has access to the corporation's number and whether the corporation has authorization to the individual user. The first communication server may confirm whether the corporation has authorization to the individual user based on the authorization information #1, and the first communication server may confirm whether the corporation employee has authority to use the corporation's number based on the authorization information # 2. Reference may be made specifically to the description in step 2210, and no further description is given here.

Assume that in step 2309, the first communication server confirms that the authorization is normal.

2310, the first communication server triggers the first device to establish a call connection with the second device.

The first communication server may trigger the establishment of a call connection between the first device and the second device based on the confirmation result, so that the enterprise employee and the individual user may make a call.

Fig. 24 is a schematic flow chart of a communication method 2400 provided in an embodiment of the present application. The method 2400 can be used in a scenario where B2C is authorized based on an authorization code, where the enterprise and the person belong to the same operator. In method 2400, assume that the first device is a device (e.g., a terminal device (e.g., a smart phone)) of a home caller, e.g., an enterprise employee; the second device is a device (such as a terminal device (such as a smart phone)) belonging to a called user, and the called user is a personal user; the third device is a device (such as an application server) of the home enterprise; the communication server is a device in a communication network that provides services for the first device and the second device. Reference may be made to the description in method 2200 for the communication server, which is not further described herein. The method 2400 may include the following steps.

2401, the second device sends a message #3 (i.e., an example of a second message) to the communication server.

As an example, the message #3 may carry the authorization ID (e.g., 0001) and authorization requirement information of the individual user.

The authorization requirement information may include, but is not limited to, one or more of the following: the authorization ID of the authorizer, the authorization ID of the authorizer (e.g., 0002), the callable time period, the callable location, the authorization valid period, whether to renew, the renewal mode, and other auxiliary information. Reference may be made specifically to the foregoing description, and details are not repeated here. The following description will be mainly given by taking an example in which the authorization requirement information includes an authorization ID (e.g., 0002) of an authorized party.

2402, the communication server generates authorization information #1.

The communication server generates authorization information #1 based on the authorization requirement information. As an example, the generated authorization information #1 includes ciphertext, which is encrypted authorization requirement information.

The communication server may process the authorization requirement information to prevent tampering with the information. For example, the communication server encrypts the authorization requirement information to obtain ciphertext; and obtains authorization information #1 based on the ciphertext and the authorization ID of the individual user, such as generating an authorization code (the authorization code may be presented in the form of a two-dimensional code, for example).

2403, the communication server returns the authorization information #1 to the second device.

The communication server returns authorization information #1 to the second device, which authorization information #1 may be presented to the individual user in a two-dimensional code.

2404, the second device transmits the authorization information #1 to the third device.

For example, the second device sends or issues authorization information #1 to the third device, and the authorization information #1 may be presented to the enterprise in a two-dimensional code manner. For another example, the second device sends or issues the two-dimensional code picture to the third device.

2405, the third device transmits the authorization information #1 to the first device.

For example, the third device may send or issue authorization information #1 to the second device, which authorization information #1 may be presented to the enterprise employee in a two-dimensional code.

For another example, the third device may send or issue the two-dimensional code picture to the second device.

2406, the first device parses the authorization information #1.

For example, if in step 2405, the third device sends or issues the authorization information #1 to the first device, and the authorization information #1 is presented to the enterprise employee in a two-dimensional code manner, then in step 2406, the first device may parse the two-dimensional code to obtain the authorization ID of the individual user and the ciphertext of the authorization information #1.

For another example, if in step 2405, the third device may send or issue the two-dimensional code picture to the first device, then in step 2406, the first device may scan the two-dimensional code picture to obtain the authorization ID of the individual user and the ciphertext of the authorization information # 1.

2407, the first device sends a call request message to the communication server.

The enterprise employee may call the personal user's authorization ID with the authorized communication light application of the first device, and the call request is sent to the communication server.

The call request message may carry: the authorization ID of the individual user (e.g., 0001) and the ciphertext of authorization information # 1. Or the call request message carries the authorization ID (such as 0001) of the individual user, and once the enterprise employee dials the authorization ID (such as 0001) of the individual user, the communication server displays the ciphertext of the authorization information # 1.

2408, the communication server decrypts the ciphertext of the authorization information #1, and confirms whether the authorization is normal.

The communication server may decrypt the ciphertext of authorization information #1 to confirm whether the enterprise employee has authorization from the individual user.

For example, if the ciphertext of the authorization information #1 includes: the authorized party's authorization ID (e.g., the enterprise employee's authorization ID 0002), then the communication server learns that the enterprise employee has authorization from the individual user based on the ciphertext of the authorization information # 1.

Assume that in step 2408, the communication server confirms that the authorization is normal.

2409, the communication server triggers the first device to establish a call connection with the second device.

The communication server may trigger the establishment of a call connection between the first device and the second device based on the confirmation result, so that the enterprise employee may communicate with the individual user.

Based on the scheme, the personal user can authorize the enterprise to call itself, and the communication server can decrypt and verify the authorization information encrypted in the call request, and after confirming that the authorization is normal, the establishment of call connection between the equipment of the staff of the home enterprise and the equipment of the home personal user is triggered. Therefore, privacy disturbance problems in the B2C scene, such as that marketing/service calls of enterprises possibly disturb customer privacy and are complained by customers, can be relieved.

Fig. 25 is a schematic flow chart of a communication method 2500 provided in an embodiment of the present application. The method 2500 may be used in B2C scenarios where enterprises and individuals home to different operators based on authorization code authorization. In method 2500, assume that the first device is a device (e.g., a terminal device (e.g., a smart phone)) of a home caller, e.g., an enterprise employee; the second device is a device (such as a terminal device (such as a smart phone)) belonging to a called user, and the called user is a personal user; the third device is a device (such as an application server) of the home enterprise; the first communication server is a device in a communication network that serves the second device and the second communication server is a device in a communication network that serves the first device. Reference may be made to the description in method 2200 for the communication server, which is not further described herein. The method 2500 may include the following steps.

2501, the second device sends a message #3 to the first communication server.

Step 2501 is similar to step 2401 and will not be described again.

2502, the first communication server generates authorization information #1.

Step 2502 is similar to step 2402 and will not be described again.

2503, the first communication server returns authorization information #1 to the second device.

2504, the second device transmits authorization information #1 to the third device.

2505, the third device transmits the authorization information #1 to the first device.

2506, the first device parses the authorization information #1.

Steps 2503-2506 are similar to steps 2403-2406, and are not repeated here.

2507, the first device sends a call request message to the second communication server.

The call request message may carry: the authorization ID of the individual user (e.g., 0001) and the ciphertext of authorization information #1.

2508, the second communication server forwards the call request message to the first communication server.

2509, the first communication server decrypts the ciphertext of the authorization information #1, and confirms whether the authorization is normal.

Step 2509 is similar to step 2408 and will not be described again.

Assume that in step 2509, the first communication server confirms that the authorization is normal.

2510, the first communication server triggers the first device to establish a call connection with the second device.

Fig. 26 is a schematic flow chart of a communication method 2600 provided in an embodiment of the present application. This method 2600 may be used in a scenario where the C2C authorizes based on the authorization ID that the calling user and the called user belong to the same operator. In method 2600, assume that the first device is a device of a home caller (e.g., a terminal device (e.g., a smart phone)); the second device is a device (such as a terminal device (such as a smart phone)) of the home called user; the communication server is a device in a communication network that provides services for the first device and the second device. Reference may be made to the description in method 2200 for the communication server, which is not further described herein. The method 2600 may include the following steps.

2601, the second device sends a message #1 to the communication server.

For example, the second device detects an operation of an individual user (i.e., a called user), authorizes an authorized ID of the other individual in the authorized communication light application, and after detecting an operation of the individual user to fill out an enterprise number, authorization information #1, and click of a determination button, the authorized communication light application transmits a message #1 to an authorized communication light application server in a communication network serving the second device.

As an example, the message #1 may carry the authorization ID of the called user and the authorization information #1. Message #1 may also be referred to as a request message or a notification message, the naming of which does not limit the scope of the present application.

Wherein, the authorization ID of the called user, namely, the authorization ID representing the authorized party. For convenience of description, the following will exemplify 0001 the authorization ID of the called user.

Wherein the authorization information #1 may include, but is not limited to, one or more of the following: an authorization ID of the authorizer (e.g., 0001), an authorization ID of the authorizer (e.g., 0003), a callable time period, a callable location, an authorization valid period, whether to renew, a renewal manner, and other auxiliary information. Reference may be made specifically to the foregoing description, and details are not repeated here. The following mainly exemplifies that the authorization information #1 includes an authorization ID (e.g., 0003) of the authorized party.

It will be appreciated that the authorization information #1 may include one or more authorized IDs of authorized parties, which is not limited in this application.

2602, the communication server holds a correspondence between the authorization information #1 and the authorization ID of the called user.

After receiving the message #1, the communication server establishes and saves a correspondence between the authorization information #1 and the authorization ID of the called user, where the authorization information #1 includes the authorization ID (e.g. 0003) of the authorized party, and the authorization information #1 may also include the authorization ID (e.g. 0001) of the authorized party. The authorization information #1 is authorization information corresponding to the called party (or authorization information corresponding to the authorization ID of the called party), and may be used to check (or detect) a call request message for calling the called party (or a call request message for checking (or detecting) the authorization ID of the called party). The authorization information #1 may be, for example, a call authorization table of the previous term interpretation section.

2603, the second device issues to the first device an authorization ID of the called user.

The called user can issue the authorization ID of the called user to one or more other devices through the second device, so that the one or more other devices can obtain the authorization ID of the called user, and then can call the calling user. The present application is mainly exemplified by a first device.

2604, the first device sends a call request message to the communication server.

The calling user can call the authorized ID of the called user through the authorized communication light application of the first device, and the call request is sent to the communication server.

The call request message may carry: the authorization ID of the called user (e.g., 0001), the authorization ID of the calling user (e.g., 0003).

2605, the communication server confirms whether the authorization is normal.

The communication server may confirm whether the calling subscriber has the authority to the called subscriber based on the authority information # 1.

For example, the communication server determines the corresponding authorization information #1 according to the authorization ID (e.g. 0001) of the called party carried in the call request message and the correspondence saved in step 2602, and if the authorization information #1 includes the authorization ID (e.g. 0003) of the caller, the communication server learns that the caller has authorization of the called party based on the authorization information # 1. For another example, assuming that the authorization information #1 includes an authorization ID of the authorized party and an authorization ID of the authorized party, the communication server searches for the corresponding authorization information #1 according to the authorization ID (e.g., 0001) of the called party carried in the call request message, and if the authorization information #1 includes an authorization ID of the authorized party, 0003, the communication server learns that the calling party has authorization of the called party based on the authorization information # 1.

Assume that in step 2605, the communication server confirms that the authorization is normal.

2606, the communication server triggers the first device to establish a call connection with the second device.

The communication server can trigger to establish call connection between the first equipment and the second equipment based on the confirmation result, so that the calling user and the called user can communicate.

Based on the scheme, the personal user can authorize other users to call themselves, and the communication server can also verify the call request of the calling user for the personal user based on the saved authorization information #1, and after confirming that the authorization is normal, the communication server triggers the establishment of the call connection between the equipment of the home calling user and the equipment of the home called user. Therefore, the privacy harassment problem in the C2C scene can be relieved, for example, the privacy of other people can be harassd when the person calls the other people directly, and the problem that the privacy is harassd due to the fact that the person registers own telephone numbers outside and the number leakage can be relieved.

Fig. 27 is a schematic flow chart of a communication method 2700 provided in an embodiment of the present application. The method 2700 may be used in scenarios where the C2C authorizes based on the authorization ID, the calling user and the called user belong to different operators. In method 2700, assume that the first device is a device (e.g., a terminal device (e.g., a smart phone)) of a home caller; the second device is a device (such as a terminal device (such as a smart phone)) of the home called user; the first communication server is a device in a communication network that serves the second device and the second communication server is a device in a communication network that serves the first device. Reference may be made to the description in method 2200 for the communication server, which is not further described herein. The method 2700 may include the following steps.

2701, the second device sends a message #1 to the first communication server.

As an example, the message #1 may carry the authorization ID of the called user and the authorization information #1.

Step 2701 is similar to step 2601 and will not be described again here.

2702, the first communication server saves the correspondence between the authorization information #1 and the authorization ID of the called user.

After receiving the message #1, the first communication server establishes and saves a corresponding relationship between the authorization information #1 and the authorization ID of the called user, where the authorization information #1 includes the authorization ID of the authorized party (e.g. 0003), and the authorization information #1 may also include the authorization ID of the authorized party (e.g. 0001). The authorization information #1 is authorization information corresponding to the called party (or authorization information corresponding to the authorization ID of the called party), and may be used to check (or detect) a call request message for calling the called party (or a call request message for checking (or detecting) the authorization ID of the called party). The authorization information #1 may be, for example, a call authorization table of the previous term interpretation section.

2703, the second device issues an authorization ID of the called user to the first device.

The called user can issue an own authorization ID to one or more other devices through the second device, so that the one or more other devices can obtain the authorization ID of the called user, and further can call the calling user. The present application is mainly exemplified by a first device.

2704, the first device sends a call request message to the second communication server.

The calling party may call the authorized ID of the called party through an authorized communication light application of the first device. The call request is sent to a second communication server, i.e. a communication network serving the first device.

The call request message may carry: an authorization ID of the called party (e.g., 0001) and an authorization ID of the calling party.

At 2705, the second communication server forwards the call request message to the first communication server.

At 2706, the first communication server confirms whether the authorization is normal.

Step 2706 is similar to step 2605 and is not repeated here.

Assume that in step 2706, the first communication server confirms that the authorization is normal.

2707, the first communication server triggers the first device to establish a call connection with the second device.

The first communication server can trigger to establish call connection between the first equipment and the second equipment based on the confirmation result, so that the calling user and the called user can communicate.

Fig. 28 is a schematic flow chart of a communication method 2800 provided in an embodiment of the present application. The method 2800 can be used in a scenario where the C2C is authorized based on an authorization code, where the calling subscriber and the called subscriber belong to the same operator. In method 2800, assume that the first device is a device (e.g., a terminal device (e.g., a smart phone)) of a home caller; the second device is a device (such as a terminal device (such as a smart phone)) of the home called user; the communication server is a device in a communication network that provides services for the first device and the second device. Reference may be made to the description in method 2200 for the communication server, which is not further described herein. The method 2800 may include the following steps.

2801, the second device sends a message #3 to the communication server.

As an example, the message #3 may carry the authorization ID (e.g., 0001) and authorization requirement information of the called user.

The authorization requirement information may include, but is not limited to, one or more of the following: an authorization ID of the authorizer (e.g., 0001), an authorization ID of the authorizer (e.g., 0003), a callable time period, a callable location, an authorization valid period, whether to renew, a renewal manner, and other auxiliary information. Reference may be made specifically to the foregoing description, and details are not repeated here. The following mainly exemplifies that the authorization requirement information includes an authorization ID (e.g., 0003) of the authorized party.

2802, the communication server generates authorization information #1.

The communication server may process the authorization requirement information to prevent tampering with the information. For example, the communication server encrypts the authorization requirement information to obtain ciphertext; and obtains authorization information #1 based on the ciphertext and the authorization ID of the called user, such as generating an authorization code (the authorization code may be presented in the form of a two-dimensional code, for example).

2803, the communication server returns authorization information #1 to the second device.

2804, the second device transmits authorization information #1 to the first device.

The second device sends or issues the authorization information #1 to one or more other devices, and the authorization information #1 can be presented to other users in a two-dimensional code manner. For another example, the second device may send or issue the two-dimensional code picture to one or more other devices. The present application is mainly exemplified by a first device.

2805, the first device parses the authorization information #1.

For example, if in step 2804 the second device sends or issues authorization information #1 to the first device, where the authorization information #1 is presented to the calling user in a two-dimensional code, then in step 2805 the first device may parse the two-dimensional code to obtain the authorization ID of the called user and the ciphertext of the authorization information #1.

For another example, if the second device may send or issue the two-dimensional code picture to the caller in step 2804, the first device may scan the two-dimensional code picture to obtain the authorization ID of the called user and the ciphertext of the authorization information #1 in step 2805.

2806, the first device sends a call request message to the communication server.

The call request message may carry: the authorization ID (e.g., 0001) of the called subscriber and the ciphertext of the authorization information #1.

2807, the communication server decrypts the ciphertext of the authorization information #1, and confirms whether the authorization is normal.

The communication server may decrypt the ciphertext of authorization information #1 to confirm whether the calling subscriber has been authorized by the called subscriber.

For example, if the ciphertext of the authorization information #1 includes: the authorized party's authorization ID (e.g., the caller's authorization ID 0003), then the communication server knows that the caller has authorization with the called party based on the ciphertext of the authorization information # 1.

Assume that in step 2807, the communication server confirms that the authorization is normal.

2808, the communication server triggers the first device to establish a call connection with the second device.

Based on the scheme, the personal user can authorize other users to call themselves, the communication server can decrypt and verify the authorization information encrypted in the call request, and after confirming that the authorization is normal, the call connection between the equipment of the home calling user and the equipment of the home called user is triggered to be established. Therefore, the privacy harassment problem in the C2C scene can be relieved, for example, the privacy of other people can be harassd when the person calls the other people directly, and the problem that the privacy is harassd due to the fact that the person registers own telephone numbers outside and the number leakage can be relieved.

Fig. 29 is a schematic flow chart diagram of a communication method 2900 provided by an embodiment of the present application. The method 2900 can be used in a scenario where the C2C authorizes based on the authorization code, and the calling user and the called user belong to different operators. In method 2900, assume that the first device is a device (e.g., a terminal device (e.g., a smart phone)) of a home caller; the second device is a device (such as a terminal device (such as a smart phone)) of the home called user; the first communication server is a device in a communication network that serves the second device and the second communication server is a device in a communication network that serves the first device. Reference may be made to the description in method 2200 for the communication server, which is not further described herein. The method 2900 may include the following steps.

2901, the second device sends a message #3 to the first communication server.

Step 2901 is similar to step 2801 and is not described in detail herein.

2902, the first communication server generates authorization information #1.

Step 2902 is similar to step 2802 and is not described in detail herein.

2903, the first communications server returns authorization information #1 to the second device.

2904, the second device sends authorization information #1 to the first device.

2905, the first device parses the authorization information #1.

Steps 2903-2905 are similar to steps 2803-2805 and are not repeated herein.

2906, the first device sends a call request message to the second communication server.

The call request message may carry: the caller's authorization ID (e.g., 0001) and the ciphertext of authorization information #1.

2907, the second communication server forwards the call request message to the first communication server.

2908, the first communication server decrypts the ciphertext of the authorization information #1, and confirms whether the authorization is normal.

Step 2908 is similar to step 2809 and is not repeated herein.

Assume that in step 2908, the first communication server confirms that the authorization is normal.

2909, the first communication server triggers the first device to establish a call connection with the second device.

Fig. 30 is a schematic flow chart of a communication method 3000 provided in an embodiment of the present application. The method 3000 may be used in a scenario for shopping on B2C networks. In the method 3000, it is assumed that the first device is a device (such as a terminal device (e.g., a smart phone)) of a home caller, and the caller is an courier; the second device is a device (e.g., a terminal device (e.g., a smart phone)) that is home to the called user, e.g., a personal user, and the communication server is a device in a communication network that serves the first device and the second device. Reference may be made to the description in method 2200 for the communication server, which is not further described herein. The method 3000 may include the following steps.

3001, the second device sends request information to create an order.

For example, the second device may send a request to create an order to the shopping platform after detecting some action by the individual user (e.g., entering the shopping platform to select an item and clicking on the purchase).

3002, the shopping platform returns order information #1 to the second device.

After receiving the request for creating the order sent by the second device, the shopping platform creates the order, and returns order information #1 to the second device, namely an order confirmation page is presented on the second device and used for confirming the order information #1.

Wherein the order information #1 includes an authorization ID order number (e.g., 123456) of the individual user and authorization requirement information. The authorization requirement information may include, but is not limited to, one or more of the following: an order number of the authorizer (e.g., 123456), a number of the authorizer (e.g., a courier's number), a callable time period, a callable location, an authorization valid period, whether to renew, a renewal mode, other auxiliary information. Reference may be made specifically to the foregoing description, and details are not repeated here.

3003, the second device processes order information #1.

Optionally, the second device may perform one or more of the following operations on information other than the order number in the authorization requirement information provided by the shopping platform: view, modify, supplement, delete, confirm, etc. As an example, if the authorization-required information includes a callable time period, the second device may modify the callable time period in the authorization-required information; or if the authorization requirement information does not include a callable period, the second device may supplement the callable period.

3004, the second device submits the confirmed order information (e.g., denoted as order information # 2) to the shopping platform.

After the second device processes the order information #1, an order may be submitted to the shopping platform, i.e., order information #2 is submitted, and the order information #2 may include the authorization requirement information after the second device processes.

As an example, the shopping platform may automatically invoke an interface of the authorized communication light application to obtain authorization information #1, where the authorization information #1 includes ciphertext, which is encrypted authorization requirement information. The ciphertext may be presented to the shopping platform in the form of an authorization code (the authorization code being presented, for example, in the form of a two-dimensional code). The authorization code may be considered to be the authorization code corresponding to the order number.

3005, the shopping platform prints the order number and the authorization code on the package box.

After receiving order information #2 from the second device, the shopping platform can package the selected articles of the second device. The shopping platform can print the order number corresponding to the article and the authorization code corresponding to the order number on the packaging box.

It is to be understood that step 3005 is merely exemplary and is not limiting in this regard.

3006, the first device obtains the order number and the authorization code corresponding to the order number.

For example, after the first device detects the operation of the express delivery, the authorization communication light application is used to scan the order number and the authorization code corresponding to the order number on the packaging box (or the express delivery box).

3007, the first device sends a call request message to the communication server.

The courier calls the authorization ID of the individual user through the first device using the authorized communication light application, and the call request is sent to the communication server.

The call request message may carry: the order number and the ciphertext of authorization information # 1.

3008, the communication server decrypts the ciphertext of the authorization information #1, and confirms whether the authorization is normal.

The communication server can decrypt the ciphertext of the authorization information #1 to confirm whether the courier has authorization of the individual user.

For example, the ciphertext of the authorization information #1 includes a order number, the communication server decrypts the ciphertext of the authorization information #1 to obtain the order number included in the ciphertext of the authorization information #1, and if the order number included in the ciphertext of the authorization information #1 is consistent with the order number carried in the call request message, it is confirmed that the courier has authorization to obtain the personal user.

Assume that in step 3008, the communication server confirms that the authorization is normal.

3009, the communication server triggers the first device to establish a call connection with the second device.

The communication server can trigger to establish call connection between the first equipment and the second equipment based on the confirmation result, so that the courier and the individual user can communicate.

It can be appreciated that the method 3000 is mainly exemplified by the first device and the second device belonging to the same operator, and the embodiments of the present application are not limited thereto, for example, the first device and the second device may also belong to different operators, and specific reference may be made to the foregoing description, which is not repeated herein.

Based on the scheme, the personal user can authorize other users (such as couriers) to call themselves, the communication server can decrypt and verify based on the authorization information encrypted in the call request, and after confirming that the authorization is normal, the call connection between the equipment of the attributive courier and the equipment of the attributive personal user is triggered and established. Therefore, privacy disturbance problems in the B2C scene, such as that marketing/service calls of enterprises possibly disturb customer privacy and are complained by customers, can be relieved.

Fig. 31 is a schematic flow chart of a communication method 3100 provided in an embodiment of the present application. The method 3100 may be used in the context of C2B callback authorization. In method 3100, assume that the first device is a device (e.g., a terminal device (e.g., a smart phone)) that belongs to a callback caller, e.g., an enterprise user; the second device is a device (such as a terminal device (such as a smart phone)) belonging to a callback called user, and the callback called user is a personal user; the third device is a device (such as an application server) of the home enterprise; the communication server is a device in a communication network that provides services for the first device and the second device. Reference may be made to the description in method 2200 for the communication server, which is not further described herein. The method 3100 may include the following steps.

3101, the second device determines authorization information #1.

For example, after detecting the operation of the individual user, the second device determines the authorization information #1, where the operation of the individual user includes, for example: opening an authorized communication light application, selecting the number of the enterprise in an address book (such as 85500), or inputting the number of the enterprise in a dial plate (such as 85500); clicking on the associated icon or button views or modifies the authorization information #1. The authorization information #1 is callback authorization information corresponding to the number (for example 85500) of the enterprise.

As an example, the authorization information #1 may include, for example: callback grant time. The callback authorization time indicates how long it is possible to callback, specifically, how long the number (e.g., 85500) of the enterprise can callback the individual user.

3102, the second device sends a call request message #1 to the communication server.

The individual user may call the number of the enterprise (e.g., 85500) through an authorized communication light application of the second device, and the call request is sent to the communication server.

The call request message #1 may carry: the number of the business (e.g., 85500), the authorization ID of the individual user, and authorization information #1. In the call request message #1, the caller is a personal user, and the callee is an enterprise.

3103, the communication server holds the authorization information #1.

3104, the communication server triggers the first device to establish a call connection with the second device.

3105, the first device sends a call request message #2 to the communication server.

As an example, the first device may send the call request message #2 after N days. Wherein N is a positive integer.

For example, an enterprise's authorized enterprise employee may call a personal user using the enterprise's number, and the enterprise employee may return (or call back) the personal user using the enterprise's number. In the call request message #2, the caller is the enterprise and the callee is the personal user.

The call request information #2 may include: the number of the business (e.g., 85500) and the authorization ID of the individual user.

3106, the communications server confirms whether the authorization is normal.

The communication server may confirm whether the individual user has authorized callback based on the authorization information #1 saved in step 3103.

For example, as in step 3103, the authorization information #1 includes: the callback authorization time is 7 days (i.e. the enterprise can callback to the individual user within seven days after the individual user calls the enterprise), if the enterprise callback to the individual user is within 7 days, the communication server confirms that the authorization is normal; if the business is calling back the individual user after 7 days, the communication server confirms that the authorization is not normal (or not authorized).

Assume that in step 3106 the communications server confirms that the authorization is normal.

3107, the communication server triggers the first device to establish a call connection with the second device.

The communication server may trigger the establishment of a call connection between the first device and the second device based on the confirmation result, so that the enterprise and the individual user may make a call.

It can be appreciated that the method 3100 is mainly illustrated by taking the example that the first device and the second device belong to the same operator as each other, and the embodiment of the present application is not limited thereto, for example, the first device and the second device may also belong to different operators, and specific reference may be made to the foregoing description, which is not repeated herein.

Based on the scheme, the individual user can authorize the enterprise to call himself by means of callback authorization. For example, after the personal user calls the enterprise, if the enterprise calls the personal user back, the communication server can judge whether the enterprise has the authorization of the personal user based on the back call authorization information, and after confirming that the authorization is normal, the communication server triggers to establish the call connection between the equipment of the home calling user and the equipment of the home called user. Therefore, the privacy harassment problem in the C2B scene can be relieved.

Fig. 32 is a schematic flow chart of a communication method 3200 provided in an embodiment of the present application. The method 3200 may be used in a C2C scenario, such as a scenario where two people are in contact with each other. In method 3200, assume that the first device is a device of home subscriber 1 (e.g., a terminal device (e.g., a smart phone)); the second device is a device (e.g. a terminal device (e.g. a smart phone)) of the home subscriber 2. The method 3200 may include the following steps.

3201, the first device sends a notification message to the second device.

The first device, upon detecting the operation of user 1, sends a notification message to the second device, which notification message can be used to notify the adding user 2 of the contact details.

For example, after detecting with the first device that the user 1 selects a page such as "authorization code-nearby exchange" in authorizing a communication light application, and clicking an operation of an icon of a terminal device of the user 2, a notification message is sent to the second device.

3202, the second device sends the authorization ID of user 2 to the first device.

For example, after the first device sends a notification message to the second device, the second device pops up a window, and after the second device detects an operation accepted by the user 2, sends the authorization ID of the user 2 to the first device.

3203, the first device generates communication authorization information (for distinction, denoted as authorization information # 11).

The authorization information #11 is communication authorization information corresponding to the user 1 (or authorization information corresponding to the authorization ID of the user 1), and may be used to check (or detect) a call request message for calling the user 1 (or a call request message for checking (or detecting) the authorization ID of the user 1). The authorization information #11 may include an authorization ID of the user 2 and an authorization ID of the user 1, and the authorization information #11 may be in the form of an authorization code, for example, where the authorization ID of the user 2 may be encrypted, for example. The manner in which the authorization code is generated may be referred to the description of the foregoing term interpretation section, and will not be repeated here.

3204, the first device transmits authorization information #11 to the second device.

In one possible way, the second device may obtain the authorization ID of the user 1 based on the authorization information #11.

Alternatively, in step 3204, the first device also sends the authorization ID of user 1 to the second device.

3205, the second device holds authorization information #11.

3206, the second device generates authorization information (denoted as authorization information #12 for differentiation).

The authorization information #12 is authorization information corresponding to the user 2 (or authorization information corresponding to the authorization ID of the user 2), and may be used to check (or detect) a call request message for calling the user 2 (or a call request message for checking (or detecting) the authorization ID of the user 2). The authorization information #12 may include an authorization ID of the user 2 and an authorization ID of the user 1, and the authorization information #12 may be in the form of an authorization code, for example, where the authorization ID of the user 1 may be encrypted, for example. The manner in which the authorization code is generated may be referred to the description of the foregoing term interpretation section, and will not be repeated here.

3207, the second device transmits authorization information #12 to the first device.

3208, the first device holds authorization information #12.

Through the steps, the first equipment and the second equipment can be communicated. For example, the first device transmits a call request message to the communication server, the call request message including the authorization ID of the user 2 and the authorization information #12; the communication server decrypts the ciphertext in the authorization information #12 (for example, the authorization information #12 is used for confirming that the user 2 authorizes the user 1 to call the user himself), and confirms that the authorization is normal; the communication server triggers the first device to establish a call connection with the second device. For another example, the user 2 transmits a call request message to the communication server, the call request message including the authorization ID of the user 1 and the authorization information #11; the communication server decrypts the ciphertext of the authorization information #11 (for example, the authorization information #11 is used for confirming that the user 1 authorizes the user 2 to call the user himself), and confirms that the authorization is normal; the communication server triggers the first device to establish a call connection with the second device.

Based on the above scheme, the two devices can mutually leave a contact way, such as providing the opposite party with the authorization ID and the corresponding authorization information #1. When one device calls another device, the communication server can determine whether the calling user has the authorization of the called user based on the corresponding authorization information, and after confirming that the authorization is normal, the communication server triggers the establishment of the call connection between the device of the home calling user and the device of the home called user. Therefore, the privacy harassment problem in the C2C scene can be relieved.

Fig. 33 is a schematic flow chart of a communication method 3300 provided in an embodiment of the present application. The method 3300 may be used in a C2C scenario, such as a stranger contact (e.g., move car) scenario. In method 3300, assume that the first device is a device (e.g., a terminal device (e.g., a smart phone)) of a home caller, e.g., owner 2; the second device is a device (e.g. a terminal device (e.g. a smart phone)) belonging to a called user, e.g. the owner 1 of the vehicle, and the communication server is a device in a communication network serving the first device and the second device. The method 3300 may include the following steps.

3301, the second device provides an authorization ID for the vehicle owner 1.

The second device may provide the authorization ID of the vehicle owner 1 to one or more other devices. For example, after detecting the operation of the vehicle owner 1, the second device checks the authorization ID of the authorization information #1 that has not been set in the authorized communication light application, and provides the authorization ID to one or more other devices, such as by being displayed on the vehicle (e.g., reserved in front of the windshield). It is to be understood that the foregoing is illustrative and not restrictive. For example, the second device may regenerate a new authorization ID, or may use an authorization ID that has been previously set with authorization information #1. For another example, the second device may reserve the authorization ID of the vehicle owner 1 in the form of a two-dimensional code.

3302, the second device generates authorization information #1.

In a possible case, the second device sets, through an App (e.g., an App related to a car), interface setting call authorization information (i.e., authorization information # 1) that allows the App to automatically invoke an authorized communication light application after sensing a stop. Assuming that the App perceives (or detects) that the vehicle of the vehicle owner 1 is in a stopped state, the App invokes the interface setting authorization information #1 authorizing the communication light application.

The authorization information #1 may include, for example, an authorization ID of the authorizer (i.e., an authorization ID of the vehicle owner 1 in step 3301), and the authorization information #1 may further include, but is not limited to, one or more of the following: callable time period, callable location, authorization valid period, whether to renew, renewal mode, other auxiliary information. Reference may be made specifically to the foregoing description, and details are not repeated here. The following mainly exemplifies that the authorization information #1 includes an authorization ID of the authorizer and a callable location.

3303, the second device sends authorization information #1 to the communication server.

After receiving the message #1, the communication server saves the authorization information #1.

If the authorization ID in step 3301 is the previous authorization ID that has been set with the authorization information #1, the following ways may be included. In one possible way, the communication server may default (or in accordance with a pre-agreement) to replacing the authorization information #1 prior to the authorization ID with the later received authorization information #1 (i.e., the authorization information #1 received in step 3303). In yet another possible way, the second device sends an indication to the communication server indicating that the authorization information #1 before the authorization ID is replaced with the authorization information #1 received in step 3303. In yet another possible manner, the communication server may save the authorization information #1 received in step 3303 and the authorization information #1 before the authorization ID, and confirm whether the authorization is normal using the authorization information #1 received in step 3303 when receiving the call request message carrying the location information. It is to be understood that the foregoing is illustrative and that the embodiments of the present application are not limited thereto.

3304, the first device sends a call request message to the communication server.

One possible scenario is that the vehicle owner 2 wants to inform the vehicle owner 1 about moving the vehicle, or inform the vehicle owner 1 about other information, and the vehicle owner 2 can call the vehicle owner 1 through the first device and the authorized ID reserved on the vehicle owner 1.

For example, the first device may call the authorized ID of the vehicle owner 1 using an authorized communication light application. The call request is sent to the communication server.

The call request message may carry: the authorized ID of the called user (i.e. the authorized ID reserved by the owner 1 of the vehicle on the vehicle), the location information of the first device.

3305, the communications server confirms whether the authorization is normal.

The communication server may confirm whether the vehicle owner 2 has been authorized by the vehicle owner 1 based on the authorization information # 1.

For example, as in step 3302, the authorization information #1 includes: and judging whether to trigger the first equipment to establish call connection with the second equipment or not by the communication server based on the callable position in the authorization information #1 and the position information of the first equipment carried in the call request message.

For example, callable locations include: less than or equal to a predetermined distance (e.g., M meters, M being greater than 0). If the communication server determines that the distance between the first equipment and the car of the car owner 1 is smaller than or equal to the preset distance based on the position information of the first equipment carried in the call request message, confirming that the authorization is normal; if the communication server determines that the distance between the first device and the vehicle of the vehicle owner 1 is greater than the preset distance based on the position information of the first device carried in the call request message, the authorization is confirmed to be abnormal.

Assume that in step 3305, the communication server confirms that the authorization is normal.

3306, the communication server triggers the first device to establish a call connection with the second device.

The communication server can trigger to establish call connection between the first device and the second device based on the confirmation result, so that the vehicle owner 2 and the vehicle owner 1 can communicate.

Based on the scheme, the personal user can provide the authorized ID for strangers and set the authorization information corresponding to the authorized ID. When other people call the user, the communication server can determine whether the calling user has the authorization of the called user based on the corresponding authorization information, and after confirming that the authorization is normal, the communication server triggers the establishment of the call connection between the equipment of the home calling user and the equipment of the home called user. Therefore, strangers can communicate with each other, and the privacy disturbance problem in the C2C scene can be relieved.

It will be appreciated that the examples in fig. 22-33 in the embodiments of the present application are merely for the convenience of those skilled in the art to understand the embodiments of the present application and are not intended to limit the embodiments of the present application to the specific scenarios illustrated. From the examples of fig. 22-33, it will be apparent to those skilled in the art that various equivalent modifications or variations may be made, and such modifications or variations are intended to be within the scope of the embodiments of the present application.

It should also be understood that in the embodiments of the present application, some information names, such as authorization information or communication authorization information, etc., are referred to, and that the naming thereof should not limit the scope of the embodiments of the present application.

It should also be understood that the numbers referred to in the embodiments of the present application are merely exemplary, and the specific numbers do not limit the scope of the embodiments of the present application.

It will also be appreciated that references to "device (e.g., terminal device)", "user", "additional communication identification (e.g., communication number)" are made herein. The user to which the device corresponds, i.e. the user who uses the device, or the device belongs to the user. The device of the user, i.e. the device corresponding to the user, or the device used by the user, or the device is attributed to the user. The additional communication identifier corresponding to the device, namely, the additional communication identifier corresponding to the user of the device.

It will also be appreciated that in some of the embodiments described above, interactions between users are mentioned multiple times, such as one user calling another user. Unless specifically described, interactions between users, that is, interactions between devices corresponding to users are represented. For example, if a user calls another user, it means that a device corresponding to the user calls another device corresponding to the user, or that a device corresponding to the user requests that a call connection be established with a device corresponding to the other user.

It will be further appreciated that in some of the above embodiments, the encryption processing of the information in the authorization information #1 (i.e., the communication authorization information) is mainly exemplified, and the embodiments of the present application are not limited thereto. Any tamper-resistant means is suitable for use in embodiments of the present application.

It will also be appreciated that some optional features of the various embodiments of the application may, in some circumstances, be independent of other features, or may, in some circumstances, be combined with other features, without limitation.

It is also to be understood that the aspects of the embodiments of the present application may be used in any reasonable combination, and that the explanation or illustration of the terms presented in the embodiments may be referred to or explained in the various embodiments without limitation.

It should be further understood that the magnitude of the various numerical numbers in the embodiments of the present application do not imply any order of execution, but are merely convenient to distinguish between the embodiments, and should not be construed as limiting the implementation of the embodiments of the present application.

It should also be understood that, in the foregoing embodiments of the methods and operations implemented by the terminal device, the methods and operations may also be implemented by component parts (e.g., chips or circuits) of the terminal device; in addition, the methods and operations implemented by a network device (e.g., a communication server) may also be implemented by, but not limited to, components (e.g., a chip or circuit) of the network device.

Corresponding to the methods given by the above method embodiments, the embodiments of the present application also provide corresponding apparatuses, where the apparatuses include corresponding modules for performing the above method embodiments. The module may be software, hardware, or a combination of software and hardware. It will be appreciated that the technical features described in the method embodiments described above are equally applicable to the device embodiments described below.

Fig. 34 is a schematic block diagram of a communication apparatus provided in an embodiment of the present application. The apparatus 3400 includes a transceiving unit 3410 and a processing unit 3420. The transceiving unit 3410 may be used to implement a corresponding communication function. The transceiver unit 3410 may also be referred to as a communication interface or a communication unit. The processing unit 3420 may be configured to perform processing operations such as generating communication authorization information, generating additional communication identifications, and the like.

Optionally, the apparatus 3400 further includes a storage unit, where the storage unit may be used to store instructions and/or data, and the processing unit 3420 may read the instructions and/or data in the storage unit, so that the apparatus implements the actions of the network device (such as the communication server or the application server) or the terminal device in the foregoing method embodiments.

In the first design, the device 3400 may be the communication server in the foregoing embodiment, or may be a component (such as a chip) of the communication server. The apparatus 3400 may implement steps or processes performed by the communication server in the above method embodiment, where the transceiving unit 3410 may be configured to perform transceiving related operations of the communication server in the above method embodiment, and the processing unit 3420 may be configured to perform processing related operations of the communication server in the above method embodiment.

A first possible implementation manner, the transceiver unit 3410 is configured to receive a communication request message, where the communication request message includes an additional communication identifier of the target user, and the additional communication identifier corresponds to communication authorization information set by the target user, and the communication authorization information is used to characterize a communication service authorized by the target user and directed to the additional communication identifier; the processing unit 3420 is configured to put through or reject the communication service directed to the additional communication identifier, which is requested to be executed by the communication request message, according to the communication authorization information. The communication authorization information may include, for example, one or more of the following: the time range in which the point in time of initiation of the authorized communication service should be, the location range in which the initiator of the authorized communication service should be, the authentication code that the initiator of the authorized communication service should provide, the order number that the initiator of the authorized communication service should be associated with, and the device type that the initiator of the authorized communication service should be.

The processing unit 3420 is specifically configured to obtain a location of an initiator of the communication request message, determine that the location of the initiator of the communication request message is within a location range where the initiator of the communication request message should be located, and put through a communication service that is requested to be executed by the communication request message and is directed to an additional communication identifier; or, acquiring the initiation time of the communication request message, determining that the initiation time is in a time range where the initiation time should be, and releasing the communication service which is requested to be executed by the communication request message and points to the additional communication identifier; or acquiring the verification code carried in the communication request message, determining the verification code as the verification code to be provided, and releasing the communication service which is requested to be executed by the communication request message and points to the additional communication identifier; or, acquiring an order number associated with the initiator of the communication request message, determining the order number as an order number to be associated, and releasing the communication service which is requested to be executed by the communication request message and points to the additional communication identifier; or, the device type of the initiator of the communication request message is obtained, the device type is determined to be the due device type, and the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identifier is put through.

As yet another example, the transceiver unit 3410 is further configured to receive a first message from a terminal device corresponding to the additional communication identifier, where the first message includes communication authorization information; the processing unit 3420 is further configured to save a correspondence between the communication authorization information and the additional communication identifier.

In yet another example, the processing unit 3420 is further configured to obtain the communication authorization information based on the additional communication identifier.

In yet another example, the communication request message further includes ciphertext of the communication authorization information, or the communication request message further includes plaintext of the communication authorization information and a digital signature for the communication authorization information.

As yet another example, the transceiver unit 3410 is further configured to send communication authorization information to a terminal device corresponding to the additional communication identifier.

As yet another example, the transceiver unit 3410 is further configured to receive a second message from the terminal device corresponding to the additional communication identifier, where the second message includes authorization requirement information; the processing unit 3420 is further configured to generate communication authorization information based on the authorization requirement information; the authorization requirement information is used for representing communication authorization information required by the target user.

As yet another example, the additional communication is identified as an additional number for the target user.

As yet another example, the processing unit 3420 is further configured to generate an additional communication identification; the transceiver 3410 is further configured to send the additional communication identifier to a terminal device corresponding to the additional communication identifier.

In yet another example, the communication request message further includes an identifier identifying the authorized party, the identifier identifying the authorized party corresponding to the identifying authorization information, the identifying authorization information being used to characterize: the identification authorizer authorizes the initiator of the communication request message, takes the identification of the identification authorizer as the initiator identification, and initiates the communication service pointing to the additional communication identification.

AS yet another example, the communication server comprises a serving-call session control function, S-CSCF, device and/or an application server, AS.

In a second possible implementation manner, the transceiver unit 3410 is configured to receive a request message from the application server, where the request message includes identification authorization information, and the identification authorization information is used to characterize: the method comprises the steps of identifying an initiator of an authorized party authorized communication request message, taking an identifier of the identified authorized party as an initiator identifier, and initiating communication service pointing to a target user; a processing unit 3420 for storing identification authorization information.

In an example, the identification authorization information includes authorization information corresponding to the identification of the identification authorized party, and the processing unit 3420 is specifically configured to store a correspondence between the identification authorization information and the identification of the identification authorized party.

In yet another example, the identifying authorization information includes an identification identifying the authorizer and/or an initiator identification.

As yet another example, the transceiver unit 3410 is further configured to receive a communication request message, where the communication request message includes an identifier for identifying the authorized party; the processing unit 3420 is further configured to put through or reject the communication service requested to be executed by the communication request message according to the identification authorization information.

In yet another example, the identifying authorization information further includes an additional communication identification of the target user, the identifying authorization information being used to characterize: the identification authorizer authorizes the initiator of the communication request message, takes the identification of the identification authorizer as the initiator identification, and initiates the communication service pointing to the additional communication identification.

In yet another example, the additional communication identifier corresponds to communication authorization information that characterizes communication traffic authorized by the target user that is directed to the additional communication identifier, the communication authorization information including one or more of: the time range in which the point in time of initiation of the authorized communication service should be, the location range in which the initiator of the authorized communication service should be, the authentication code that the initiator of the authorized communication service should provide, the order number that the initiator of the authorized communication service should be associated with, and the device type that the initiator of the authorized communication service should be.

In the second design, the device 3400 may be the terminal apparatus in the foregoing embodiment, or may be a component (such as a chip) of the terminal apparatus. The apparatus 3400 may implement steps or procedures performed corresponding to the terminal devices in the above method embodiments, where the transceiving unit 3410 may be configured to perform transceiving-related operations of the terminal devices in the above method embodiments, and the processing unit 3420 may be configured to perform processing-related operations of the terminal devices in the above method embodiments.

A first possible implementation manner, the processing unit 3420 is configured to obtain an additional communication identifier of the target user, where the additional communication identifier corresponds to communication authorization information set by the target user, and the communication authorization information is used to characterize a communication service authorized by the target user and directed to the additional communication identifier; the transceiver unit 3410 is configured to send a communication request message to the communication server, where the communication request message includes an additional communication identifier. The communication authorization information may include, for example, one or more of the following: the time range in which the point in time of initiation of the authorized communication service should be, the location range in which the initiator of the authorized communication service should be, the authentication code that the initiator of the authorized communication service should provide, the order number that the initiator of the authorized communication service should be associated with, and the device type that the initiator of the authorized communication service should be.

In an example, the communication request message further includes an authentication code, where the authentication code is received by the transceiver unit 3410, or the authentication code is predetermined.

In yet another example, the processing unit 3420 is specifically configured to scan a two-dimensional code, and obtain the additional communication identifier and the communication authorization information from the two-dimensional code.

A second possible implementation manner, the processing unit 3420 is configured to obtain an additional communication identifier of the target user, where the additional communication identifier corresponds to communication authorization information set by the target user, and the communication authorization information is used to characterize a communication service authorized by the target user and directed to the additional communication identifier; the transceiver unit 3410 is configured to provide the additional communication identifier to one or more other terminal devices. The communication authorization information may include, for example, one or more of the following: the time range in which the point in time of initiation of the authorized communication service should be, the location range in which the initiator of the authorized communication service should be, the authentication code that the initiator of the authorized communication service should provide, the order number that the initiator of the authorized communication service should be associated with, and the device type that the initiator of the authorized communication service should be.

A processing unit 3420, for example, is specifically configured to generate an additional communication identifier; alternatively, the transceiver unit 3410 is configured to receive the additional communication identifier from the communication server.

As yet another example, the transceiver unit 3410 is further configured to send a first message to the communication server, where the first message includes communication authorization information.

As yet another example, the transceiver unit 3410 is specifically configured to provide the additional communication identifier and the communication authorization information to one or more other terminal devices.

As yet another example, the transceiver unit 3410 is specifically configured to send the ciphertext of the additional communication identifier and the communication authorization information to one or more other terminal devices; or, the additional communication identification, the plaintext of the communication authorization information and the digital signature on the communication authorization information are transmitted to one or more other terminal devices.

As yet another example, the transceiver unit 3410 is further configured to send a second message to the communication server, where the second message includes authorization requirement information; receiving communication authorization information from a communication server, the communication authorization information being generated based on authorization requirement information; the authorization requirement information is used for representing communication authorization information required by the target user.

In yet another example, the processing unit 3420 is further configured to generate communication authorization information.

As yet another example, the processing unit 3420 is further configured to encode the additional communication identifier and the communication authorization information into a two-dimensional code; and displaying the two-dimensional code for one or more other terminal devices to scan so that the one or more other terminal devices acquire the additional communication identification and the communication authorization information.

In yet another example, the two-dimensional code includes signature information, the signature information including: a digital signature of the communication authorization information or a digital signature of the additional communication identification and the communication authorization information.

In a third design, the device 3400 may be an application server in the foregoing embodiment, or may be a component (such as a chip) of the application server. The apparatus 3400 may implement steps or processes performed by the application server in the above method embodiment, where the transceiving unit 3410 may be configured to perform transceiving related operations of the application server in the above method embodiment, and the processing unit 3420 may be configured to perform processing related operations of the application server in the above method embodiment.

In a possible implementation manner, the processing unit 3420 is configured to determine identification authorization information, where the identification authorization information is used to characterize: the method comprises the steps of identifying an initiator of an authorized party authorized communication request message, taking an identifier of the identified authorized party as an initiator identifier, and initiating communication service pointing to a target user; the transceiver unit 3410 is configured to send a request message to the communication server, where the request message includes identification authorization information.

In one example, the identification authorization information includes authorization information corresponding to an identification of the identified authorized party.

As yet another example, the additional communication identifier corresponds to communication authorization information that characterizes communication traffic authorized by the target user that is directed to the additional communication identifier, and the communication authorization information may include, for example, one or more of the following: the time range in which the point in time of initiation of the authorized communication service should be, the location range in which the initiator of the authorized communication service should be, the authentication code that the initiator of the authorized communication service should provide, the order number that the initiator of the authorized communication service should be associated with, and the device type that the initiator of the authorized communication service should be.

It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.

It should also be appreciated that the apparatus 3400 herein is embodied in the form of a functional unit. The term "unit" herein may refer to an application specific integrated circuit (application specific integrated circuit, ASIC), an electronic circuit, a processor (e.g., a shared, dedicated, or group processor, etc.) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality. In an alternative example, it will be understood by those skilled in the art that the apparatus 3400 may be specifically configured as the terminal device in the foregoing embodiment, and may be configured to perform each flow and/or step corresponding to the terminal device in the foregoing method embodiments; alternatively, the apparatus 3400 may be specifically a communication server in the foregoing embodiment, and may be configured to perform each flow and/or step corresponding to the communication server in the foregoing method embodiments; alternatively, the apparatus 3400 may be specifically an application server in the foregoing embodiment, and may be configured to perform each flow and/or step corresponding to the application server in the foregoing method embodiments. In order to avoid repetition, the description is omitted here.

The apparatus 3400 of each of the above aspects has a function of implementing a corresponding step performed by a terminal device in the above method, or the apparatus 3400 of each of the above aspects has a function of implementing a corresponding step performed by a network device (e.g., an application server, and also a communication server) in the above method. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions; for example, the transceiver unit may be replaced by a transceiver (e.g., a transmitting unit in the transceiver unit may be replaced by a transmitter, a receiving unit in the transceiver unit may be replaced by a receiver), and other units, such as a processing unit, etc., may be replaced by a processor, to perform the transceiver operations and related processing operations in the various method embodiments, respectively.

The transceiver 3410 may be a transceiver circuit (e.g., may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.

It should be noted that the apparatus in fig. 34 may be the device in the foregoing embodiment, or may be a chip or a chip system, for example: system on chip (SoC). The receiving and transmitting unit can be an input and output circuit and a communication interface; the processing unit is an integrated processor or microprocessor or integrated circuit on the chip. And are not limited herein.

Fig. 35 is a schematic diagram of another communication device 3500 provided in an embodiment of the application. The apparatus 3500 includes a processor 3510, the processor 3510 being configured to execute computer programs or instructions stored in a memory 3520 or to read data stored in the memory 3520 to perform the methods of the method embodiments above. Optionally, the processor 3510 is one or more.

Optionally, as shown in fig. 35, the apparatus 3500 further comprises a memory 3520, the memory 3520 for storing computer programs or instructions and/or data. The memory 3520 may be integral with the processor 3510 or may be separate. Optionally, memory 3520 is one or more.

Optionally, as shown in fig. 35, the apparatus 3500 further comprises a transceiver 3530, the transceiver 3530 being configured to receive and/or transmit signals. For example, the processor 3510 is configured to control the transceiver 3530 to receive and/or transmit signals.

As an aspect, the apparatus 3500 is configured to implement the operations performed by the terminal device in the above method embodiments.

Alternatively, the apparatus 3500 is configured to implement the operations performed by the communication server in the various method embodiments above.

Alternatively, the apparatus 3500 is configured to implement the operations performed by the application server in the various method embodiments above.

It should be appreciated that the processors referred to in the embodiments of the present application may be central processing units (central processing unit, CPU), but may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), off-the-shelf programmable gate arrays (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be understood that the memories mentioned in the embodiments of the present application may be volatile memories and/or nonvolatile memories. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM). For example, RAM may be used as an external cache. By way of example, and not limitation, RAM includes the following forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DR RAM).

It should be noted that when the processor is a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, the memory (storage module) may be integrated into the processor.

It should also be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

Embodiments of the present application also provide a computer readable storage medium having stored thereon computer instructions for implementing the method performed by a terminal device or a network device (e.g., a communication server, and also, e.g., an application server) in the above-described method embodiments.

Embodiments of the present application also provide a computer program product containing instructions that, when executed by a computer, implement a method performed by a terminal device or a network device (e.g., a communication server, and also e.g., an application server) in the above method embodiments.

The embodiment of the application also provides a communication system which comprises one or more of the terminal equipment, the communication server and the application server.

The explanation and beneficial effects of the related content in any of the above-mentioned devices can refer to the corresponding method embodiments provided above, and are not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Furthermore, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. For example, the computer may be a personal computer, a server, or a network device, etc. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. For example, the aforementioned usable media include, but are not limited to, U disk, removable hard disk, read-only memory (ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other various media that can store program code.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A communication method applied to a communication server, comprising:

the communication server receives a communication request message, wherein the communication request message comprises an additional communication identifier of a target user, the additional communication identifier corresponds to communication authorization information set by the target user, and the communication authorization information is used for representing communication services authorized by the target user and directed to the additional communication identifier;

the communication server releases or refuses the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identifier according to the communication authorization information;

wherein the communication authorization information includes one or more of the following: the time range in which the point in time of initiation of the authorized communication service should be, the location range in which the initiator of the authorized communication service should be, the authentication code that the initiator of the authorized communication service should provide, the order number that the initiator of the authorized communication service should be associated with, and the device type that the initiator of the authorized communication service should be.

2. The method according to claim 1, wherein the communication server releases the communication service directed to the additional communication identifier, which is requested to be performed by the communication request message, according to the communication authorization information, comprising:

the communication server obtains the position of the initiator of the communication request message, and determines that the position of the initiator of the communication request message is in the position range where the initiator of the communication request message should be, and the communication server releases the communication service which is requested to be executed by the communication request message and points to the additional communication identifier;

or alternatively, the process may be performed,

the communication server obtains the initiation time of the communication request message, determines that the initiation time is in the time range where the initiation time should be, and releases the communication service which is requested to be executed by the communication request message and points to the additional communication identifier;

or alternatively, the process may be performed,

the communication server acquires the verification code carried in the communication request message, determines the verification code to be provided, and releases the communication service which is requested to be executed by the communication request message and points to the additional communication identifier;

or alternatively, the process may be performed,

The communication server acquires an order number associated with the initiator of the communication request message, determines the order number as the order number to be associated, and releases the communication service which is requested to be executed by the communication request message and points to the additional communication identifier;

or alternatively, the process may be performed,

the communication server obtains the equipment type of the initiator of the communication request message, determines the equipment type to be the due equipment type, and releases the communication service which is requested to be executed by the communication request message and is pointed to the additional communication identifier.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

the communication server receives a first message from a terminal device corresponding to the additional communication identifier, wherein the first message comprises the communication authorization information;

the communication server stores the corresponding relation between the communication authorization information and the additional communication identifier.

4. A method according to claim 3, wherein before the communication server releases or denies the communication service directed to the additional communication identity, which the communication request message requests to perform, in accordance with the communication authorization information, the method further comprises:

And the communication server acquires the communication authorization information according to the additional communication identifier.

5. A method according to claims 1 to 3, characterized in that:

the communication request message also includes a ciphertext of the communication authorization information, or,

the communication request message also includes plaintext of the communication authorization information and a digital signature regarding the communication authorization information.

6. The method according to any one of claims 1 to 3 or 5, further comprising:

and the communication server sends the communication authorization information to the terminal equipment corresponding to the additional communication identifier.

7. The method of claim 6, wherein before the communication server sends the communication authorization information to the terminal device corresponding to the additional communication identifier, the method further comprises:

the communication server receives a second message from the terminal equipment corresponding to the additional communication identifier, wherein the second message comprises authorization requirement information;

the communication server generates the communication authorization information based on the authorization requirement information;

the authorization requirement information is used for representing communication authorization information required by the target user.

8. The method according to any of claims 1 to 7, wherein the additional communication identification is an additional number of the target user.

9. The method according to any one of claims 1 to 8, further comprising:

and the communication server generates the additional communication identifier and transmits the additional communication identifier to the terminal equipment corresponding to the additional communication identifier.

10. The method according to any of claims 1 to 9, wherein the communication request message further comprises an identification identifying the authorizer, the identification identifying the authorizer corresponding to identification authorization information, the identification authorization information being used to characterize: the identification authority authorizes the initiator of the communication request message, takes the identification of the identification authority as the initiator identification, and initiates the communication service pointing to the additional communication identification.

11. A communication method applied to a terminal device, comprising:

the terminal equipment acquires an additional communication identifier of a target user, wherein the additional communication identifier corresponds to communication authorization information set by the target user, and the communication authorization information is used for representing communication services authorized by the target user and pointing to the additional communication identifier;

The terminal equipment sends a communication request message to a communication server, wherein the communication request message comprises the additional communication identifier;

12. The method of claim 11, wherein the communication request message further comprises a verification code, wherein the verification code is received by the terminal device or the verification code is pre-agreed.

13. The method according to claim 11 or 12, wherein,

14. The method according to any one of claims 11 to 13, wherein the terminal device obtaining an additional communication identifier corresponding to the communication authorization information comprises:

The terminal equipment scans the two-dimensional code, and acquires the additional communication identifier and the communication authorization information from the two-dimensional code.

15. The method according to any of claims 11 to 14, wherein the additional communication identification is an additional number of the target user.

16. The method according to any of claims 11 to 15, wherein the communication request message further comprises an identification identifying the authorizer, the identification identifying the authorizer corresponding to identification authorization information characterizing: the identification authority authorizes the initiator of the communication request message, takes the identification of the identification authority as the initiator identification, and initiates the communication service pointing to the additional communication identification.

17. A communication method applied to a terminal device, comprising:

the terminal equipment provides the additional communication identification to one or more other terminal equipment;

18. The method of claim 17, wherein the terminal device obtains an additional communication identifier, comprising:

the terminal equipment generates the additional communication identifier; or alternatively, the process may be performed,

the terminal device receives the additional communication identity from the communication server.

19. The method according to claim 17 or 18, characterized in that the method further comprises:

the terminal device sends a first message to a communication server, wherein the first message comprises the communication authorization information.

20. The method according to claim 17 or 18, wherein the terminal device providing the additional communication identity to one or more other terminal devices comprises:

the terminal device provides the additional communication identity and the communication authorization information to the one or more other terminal devices.

21. The method of claim 20, wherein the terminal device providing the additional communication identity and the communication authorization information to one or more other terminal devices comprises:

the terminal equipment sends the additional communication identification and the ciphertext of the communication authorization information to the one or more other terminal equipment; or alternatively, the process may be performed,

the terminal device sends the additional communication identifier, the plaintext of the communication authorization information, and the digital signature for the communication authorization information to the one or more other terminal devices.

22. The method according to claim 20 or 21, wherein,

the terminal equipment generates the communication authorization information; or alternatively, the process may be performed,

before the terminal device provides the additional communication identifier and the communication authorization information to one or more other terminal devices, the method further includes:

the terminal equipment sends a second message to the communication server, wherein the second message comprises authorization requirement information;

the terminal device receives the communication authorization information from the communication server, wherein the communication authorization information is generated based on the authorization requirement information;

23. The method of claim 20, wherein the terminal device providing the additional communication identity and the communication authorization information to one or more other terminal devices comprises:

the terminal equipment encodes the additional communication identifier and the communication authorization information into a two-dimensional code;

the terminal equipment displays the two-dimension code for the one or more other terminal equipment to scan, so that the one or more other terminal equipment obtains the additional communication identification and the communication authorization information.

24. The method of claim 23, wherein the two-dimensional code includes signature information, the signature information including: and digitally signing the communication authorization information or the additional communication identifier and the communication authorization information.

25. A communication method applied to an application server, comprising:

the application server determines identification authorization information, wherein the identification authorization information is used for representing: the identification authorizer authorizes the initiator of the communication request message, takes the identification of the identification authorizer as the identification of the initiator, and initiates the communication service pointing to the target user;

The application server sends a request message to the communication server, wherein the request message comprises the identification authorization information.

26. The method of claim 25, wherein the identification authorization information includes authorization information corresponding to an identification of the identification authority.

27. Method according to claim 25 or 26, wherein said identification authorization information comprises an identification of said identification authorizer and/or an identification of said initiator.

28. The method according to any one of claims 25 to 27, wherein the identification authorization information further comprises an additional communication identification of the target user, the identification authorization information being used to characterize: the identification authority authorizes the initiator of the communication request message, takes the identification of the identification authority as the initiator identification, and initiates the communication service pointing to the additional communication identification.

29. The method of claim 28, wherein the additional communication identifier corresponds to communication authorization information, wherein the communication authorization information includes one or more of the following: the time range in which the point in time of initiation of the authorized communication service should be, the location range in which the initiator of the authorized communication service should be, the authentication code that the initiator of the authorized communication service should provide, the order number that the initiator of the authorized communication service should be associated with, and the device type that the initiator of the authorized communication service should be.

30. A communication method applied to a communication server, comprising:

the communication server receives a request message from an application server, the request message including identification authorization information, the identification authorization information being used to characterize: the identification authorizer authorizes the initiator of the communication request message, takes the identification of the identification authorizer as the identification of the initiator, and initiates the communication service pointing to the target user;

the communication server stores the identification authorization information.

31. The method of claim 30, wherein the identification authorization information includes authorization information corresponding to an identification of the identification authority,

the communication server stores the identification authorization information, including:

the communication server stores the corresponding relation between the identification authorization information and the identification of the identification authorized party.

32. Method according to claim 30 or 31, wherein said identification authorization information comprises an identification of said identification authorizer and/or an identification of said initiator.

33. The method according to any one of claims 30 to 32, further comprising:

the communication server receives the communication request message, wherein the communication request message comprises the identification of the identification authorized party;

And the communication server releases or refuses the communication service requested to be executed by the communication request message according to the identification authorization information.

34. The method according to any one of claims 30 to 33, wherein the identification authorization information further comprises an additional communication identification of the target user, the identification authorization information being used to characterize: the identification authority authorizes the initiator of the communication request message, takes the identification of the identification authority as the initiator identification, and initiates the communication service pointing to the additional communication identification.

35. The method of claim 34, wherein the communication authorization information includes one or more of the following: the time range in which the point in time of initiation of the authorized communication service should be, the location range in which the initiator of the authorized communication service should be, the authentication code that the initiator of the authorized communication service should provide, the order number that the initiator of the authorized communication service should be associated with, and the device type that the initiator of the authorized communication service should be.

36. The method of any one of claims 1 to 35, wherein the communication server comprises one or more of: the service-call session control function S-CSCF device, the application server AS, and the authorised communication light application server.

37. An apparatus for communication, comprising at least one processor for executing a computer program stored in a memory, to cause the apparatus to implement the method of any one of claims 1 to 10, or to cause the apparatus to implement the method of any one of claims 11 to 16, or to cause the apparatus to implement the method of any one of claims 17 to 29, or to cause the apparatus to implement the method of any one of claims 30 to 36.

38. A computer readable storage medium comprising a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 10, or causes the computer to perform the method of any one of claims 11 to 16, or causes the computer to perform the method of any one of claims 17 to 29, or causes the computer to perform the method of any one of claims 30 to 36.

39. A computer program product comprising computer program code, characterized in that the computer program code, when run on a computer, causes the computer to carry out the method of any one of the preceding claims 1 to 10 or to carry out the method of any one of the preceding claims 11 to 16 or to carry out the method of any one of the preceding claims 17 to 29 or to carry out the method of any one of the preceding claims 30 to 36.