CN114866519B - Call forwarding method and device - Google Patents

Call forwarding method and device Download PDF

Info

Publication number
CN114866519B
CN114866519B CN202210768085.2A CN202210768085A CN114866519B CN 114866519 B CN114866519 B CN 114866519B CN 202210768085 A CN202210768085 A CN 202210768085A CN 114866519 B CN114866519 B CN 114866519B
Authority
CN
China
Prior art keywords
party
call forwarding
call
identity
belongs
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202210768085.2A
Other languages
Chinese (zh)
Other versions
CN114866519A (en
Inventor
彭艺
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Technologies Co Ltd
Original Assignee
New H3C Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by New H3C Technologies Co Ltd filed Critical New H3C Technologies Co Ltd
Priority to CN202210768085.2A priority Critical patent/CN114866519B/en
Publication of CN114866519A publication Critical patent/CN114866519A/en
Application granted granted Critical
Publication of CN114866519B publication Critical patent/CN114866519B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1096—Supplementary features, e.g. call forwarding or call holding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1076—Screening of IP real time communications, e.g. spam over Internet telephony [SPIT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
    • H04L9/0822—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) using key encryption key

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Power Engineering (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The present specification provides a call forwarding method and apparatus, when the call forwarding method is applied to a key management service KMS server, and the KMS server is a KMS server to which a third party terminal belongs, the method includes: receiving a call transfer message initiated by a third party terminal; the third party terminal is a call transfer party which is appointed in advance when the calling party calls the called party; the call transfer message at least carries a call transfer type, a bill used when a calling party and a called party are communicated and an identity of a third party terminal; after the third party terminal passes the verification, determining a call forwarding relation when the calling party calls the called party according to the identity of the third party terminal, the call forwarding type carried by the call forwarding message and the identity of the called party carried by the Ticket; and when the call forwarding relation is confirmed to pass the verification, controlling the third-party terminal to start the communication with the calling party. By implementing the invention, the safety of call transfer conversation is improved.

Description

Call forwarding method and device
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a call forwarding method and apparatus.
Background
With the development of communication services, call forwarding has become one of the common supplementary services for telecommunications, which allows a called party to forward an incoming call to a designated other telephone, which the called party uses to talk with a calling party. An IMS (IP Multimedia Subsystem) as a SIP (Session initiation Protocol) based telephone system also provides a call transfer Service, and in order to ensure privacy of an end-to-end call, the IMS supports a KMS (Key Management Service) based media plane secure communication technology.
In the related art, the KMS server needs to perform authentication (by verifying whether the identity of the called party in the Ticket is consistent with the identity of the answering party), and if so, verifies and approves the request of the answering party for decrypting the IMS media surface key in the Ticket, because the final identity of the answering party in the call transfer service is definitely inconsistent with the identity of the called party, and the KMS server can verify the call transfer.
Disclosure of Invention
To overcome the problems in the related art, the present specification provides a call forwarding method and apparatus.
According to a first aspect of embodiments of the present specification, there is provided a call forwarding method applied to a key management service KMS server, where the KMS server is a KMS server to which a third party terminal belongs, the method including the steps of: receiving a call transfer message initiated by a third party terminal; the third party terminal is a call forwarding party which is appointed in advance when the calling party calls the called party; the call transfer message at least carries a call transfer type, a Ticket used when the calling party and the called party are communicated and an identity of a third party terminal; after the third-party terminal passes the verification, determining a call transfer relationship when the calling party calls the called party according to the identity of the third-party terminal, the call transfer type carried by the call transfer message and the identity of the called party carried by the Ticket; and when the call forwarding relation is confirmed to pass the verification, controlling the third-party terminal to start the communication with the calling party.
Optionally, a KMS server to which the third party terminal belongs is different from a KMS server to which the called party belongs; verifying the call forwarding relationship by: sending the call forwarding relation to a KMS server to which the called party belongs so as to verify the call forwarding relation by the KMS server to which the called party belongs; and receiving a verification result returned by the KMS server to which the called party belongs, and determining that the call forwarding relation passes the verification if the verification result passes.
Optionally, the controlling the third-party terminal to open a call with the calling party includes: sending a decryption request message to a KMS server to which the calling party belongs, wherein the decryption request message carries the identity of the third party terminal and the Ticket, so that the KMS server to which the calling party belongs decrypts the Ticket; receiving a communication key sent by a KMS (Key Messaging System) server to which the calling party belongs; and controlling the third party terminal to open the call with the calling party through the communication key.
Optionally, the KMS server to which the third party terminal belongs is the same as the KMS server to which the called party belongs; the call forwarding relationship is verified by: and inquiring a call forwarding party identity identifier matched with the identity identifier of the called party and the call forwarding type in the obtained call forwarding information table, and if the call forwarding party identity identifier is the identity identifier of the third-party terminal, determining that the call forwarding relation passes verification.
According to a second aspect of embodiments of the present specification, there is provided a call forwarding method applied to a KMS server serving as a KMS server to which a called party belongs, the method including the steps of: receiving a call forwarding relationship sent by a KMS server to which a call forwarding party belongs, wherein the call forwarding relationship is determined by the KMS server to which the call forwarding party belongs according to an identity of the call forwarding party, a call forwarding type carried by a call forwarding message initiated by the call forwarding party and an identity of a called party carried by a Ticket used when a calling party and the called party are in conversation; and verifying the call forwarding relation, and returning a verification result to a KMS server to which the call forwarding party belongs so that the KMS server to which the call forwarding party belongs controls the call forwarding party to open the call with the calling party based on the verification result.
Optionally, the call forwarding message carries at least two call forwarding types, and an order of the call forwarding types corresponds to an order of callers called by the caller, where the order of callers called by the caller is: the called party and the calling party are appointed to carry out at least two call forwarding parties for call forwarding in sequence when calling the called party;
the verifying the call forwarding relationship comprises: according to the identity of the called party and the call forwarding type corresponding to the called party, verifying whether a target call forwarding party of the calling party for the call forwarding of the called party is the call forwarding party sending the call forwarding relationship; if yes, determining that the verification is passed; if not, according to the identity of the target call forwarding party, the call forwarding type corresponding to the target call forwarding party and the identity of the call forwarding party sending the call forwarding relationship, constructing information to be verified, sending the information to be verified to a KMS server to which the target call forwarding party belongs, verifying the information to be verified by the KMS server to which the target call forwarding party belongs and returning a verification instruction to the KMS server to which the called party belongs, wherein the verification instruction comprises passing verification or failing verification; and determining whether the target transfer party passes the verification according to a verification instruction returned by the KMS server to which the target transfer party belongs.
According to a third aspect of embodiments herein, there is provided a call transfer apparatus applied to a key management service KMS server as a KMS server to which a third party terminal belongs, including: the call transfer message receiving module is used for receiving a call transfer message initiated by a third-party terminal; the third party terminal is a call transfer party which is appointed in advance when a calling party calls a called party; the call forwarding message at least carries a call forwarding type, a Ticket and an identity of a third party terminal; a call transfer relationship determining module, configured to determine, after the third-party terminal passes verification, a call transfer relationship when the calling party calls the called party according to an identity of the third-party terminal, a call transfer type carried in the call transfer message, and an identity of the called party carried in the Ticket used when the calling party and the called party talk; and the control module is used for controlling the third-party terminal to open the call with the calling party when the call transfer relation is determined to pass the verification.
Optionally, a KMS server to which the third party terminal belongs is different from a KMS server to which the called party belongs; the device further comprises: a call forwarding relation sending module, configured to send the call forwarding relation to a KMS server to which the called party belongs, so that the KMS server to which the called party belongs verifies the call forwarding relation; and the verification result receiving module is used for receiving the verification result returned by the KMS server to which the called party belongs, and if the verification result is passed, determining that the call forwarding relation is verified.
According to a fourth aspect of embodiments of the present specification, there is provided a call transfer apparatus applied to a KMS server as a KMS server to which a called party belongs, including: the call forwarding relation receiving module is used for receiving a call forwarding relation sent by a KMS server to which a call forwarding party belongs, wherein the call forwarding relation is determined by the KMS server to which the call forwarding party belongs according to an identity of the call forwarding party, a call forwarding type carried by a call forwarding message initiated by the call forwarding party and an identity of a called party carried in a Ticket used when the calling party and the called party are in conversation; and the call forwarding relation verification module is used for verifying the call forwarding relation and returning a verification result to the KMS server to which the call forwarding party belongs so that the KMS server to which the call forwarding party belongs controls the call forwarding party to open the call with the calling party based on the verification result.
Optionally, the call forwarding message carries at least two call forwarding types, and an order of the call forwarding types corresponds to an order of callers called by the caller, where the order of callers called by the caller is: the called party and the calling party are appointed to carry out at least two call forwarding parties for call forwarding in sequence when calling the called party;
the call forwarding relationship verification module is specifically configured to: verifying whether a target call forwarding party of the calling party aiming at the call forwarding of the called party is a call forwarding party sending the call forwarding relation or not according to the identity of the called party and the call forwarding type corresponding to the called party; if yes, determining that the verification is passed; if not, according to the identity of the target call forwarding party, the call forwarding type corresponding to the target call forwarding party and the identity of the call forwarding party sending the call forwarding relationship, constructing information to be verified, sending the information to be verified to a KMS server to which the target call forwarding party belongs, verifying the information to be verified by the KMS server to which the target call forwarding party belongs and returning a verification instruction to the KMS server to which the called party belongs, wherein the verification instruction comprises passing verification or failing verification; and determining whether the target transfer party passes the verification according to a verification instruction returned by the KMS server to which the target transfer party belongs.
The technical scheme provided by the embodiment of the specification can have the following beneficial effects:
in the embodiment of the description, the call transfer message initiated by the third-party terminal is received, the call transfer relationship determined according to the identity of the third-party terminal, the call transfer type carried by the call transfer message and the identity of the called party carried by packet is verified, and after the verification is passed, the third-party terminal is controlled to start the call with the calling party, so that the validity of the call transfer relationship is ensured, and the security of the call transfer call is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the specification.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present specification and together with the description, serve to explain the principles of the specification.
Fig. 1 is an interactive flow diagram illustrating a single call forwarding system in accordance with an exemplary embodiment of the present specification.
Fig. 2 is a diagram illustrating one particular example of call forwarding information setup in accordance with one illustrative embodiment.
Fig. 3 is an interaction flow diagram of a multiple call forwarding system shown in accordance with an exemplary embodiment.
Fig. 4 is a flow chart illustrating a call forwarding method according to an exemplary embodiment of the present description.
Fig. 5 is a flow chart illustrating another call forwarding method in accordance with an exemplary embodiment of the present description.
Fig. 6 is a block diagram of a call forwarding device shown in accordance with an exemplary embodiment of the present description.
Fig. 7 is a block diagram of another call forwarding device shown in accordance with an exemplary embodiment of the present description.
Fig. 8 is a hardware configuration diagram of a computer device in which the call transfer apparatus according to the embodiment of the present disclosure is located.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings in which the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if," as used herein, may be interpreted as "at \8230; \8230when" or "when 8230; \823030when" or "in response to a determination," depending on the context.
The following provides a detailed description of examples of the present specification.
As shown in fig. 1, fig. 1 is a call forwarding system for single call forwarding according to an exemplary embodiment shown in this specification, including: a calling party (corresponding to UE a in fig. 1), a called party (corresponding to UE B in fig. 1), a third party terminal (i.e. a call transfer party pre-designated when the calling party calls the called party), an IMS (IP Multimedia Subsystem), a KMS Server (corresponding to KMS Server1 in fig. 1) to which the calling party belongs, a KMS Server (corresponding to KMS Server2 in fig. 1) to which the called party belongs, and a KMS Server (corresponding to KMS Server3 in fig. 1) to which the third party terminal belongs, wherein the KMS Server to which the calling party belongs and the KMS Server to which the called party belongs, and the KMS Server to which the third party terminal belongs may be three different servers, or may be the same Server, or 2 of the KMS servers may be the same Server, and the other is a separate Server, for example, the KMS Server to which the calling party belongs and the KMS Server to which the called party belongs are the same Server, and the KMS Server to which the third party terminal belongs is a separate Server. The deployment method of the KMS server in the embodiment of the present invention is not particularly limited, and those skilled in the art may determine the deployment method according to actual situations. The embodiment of the invention is described by taking only the KMS server to which the calling party belongs and the KMS server to which the called party belongs as examples, and the KMS server to which the third party terminal belongs is a single server.
As shown in fig. 1, for a call process, a calling party first sends a request message to a KMS server to which the calling party belongs, where the request message may carry an identity of the calling party and an identity of a called party, the KMS server to which the calling party belongs sends a feedback message to the calling party according to the request message, where the feedback message carries a communication key (i.e., an IMS media surface key) and a Ticket, and the calling party sends the received Ticket to the called party through the IMS to request for a call.
In an embodiment of the present invention, the Ticket may include: the embodiment of the invention does not specifically limit the identity of the calling party and the identity of the called party, which can be determined by a person skilled in the art according to actual conditions. The communication key is used for communication between the calling party and the called party.
As an optional embodiment of the present invention, the communication key in Ticket is encrypted by a private key of a KMS server to which the calling party belongs, and integrity of the communication key is protected, so that tampering and forgery are avoided, and the security of the call is improved.
When the called party can not answer the call temporarily, the call can be transferred to a third party terminal for answering, and the third party terminal can be set in advance by the user according to the call habit. In particular, different third party terminals may be provided according to different call forwarding types. In an embodiment of the present invention, the call forwarding types may include: always transfer, transfer when busy, transfer when no one answers, transfer when connection is unavailable, and the like. For different call forwarding types, the same third-party terminal may be provided for them, or different third-party terminals may be provided for them. The embodiment of the invention does not specifically limit the call forwarding type and the third-party terminals corresponding to different call types, and can be determined by a person skilled in the art according to actual situations.
Specifically, the call forwarding information of each called party may be preset in advance, each piece of call forwarding information is represented by a call forwarding relationship composed of an identity of the called party, a call forwarding type, and an identity of a third party terminal to which the call forwarding type is correspondingly forwarded, and a call forwarding information table is formed according to a preset storage format and then stored in a KMS server to which the called party belongs so as to facilitate subsequent verification of the call forwarding relationship.
For example, as shown in fig. 2, after the called party may set call forwarding information to the IMS, the IMS sends the call forwarding information to the KMS server to which the called party belongs; the called party can also directly send the call forwarding information to the KMS server to which the called party belongs for storage, and the setting method of the call forwarding information is not particularly limited in the embodiment of the invention and can be determined by a person skilled in the art according to the actual situation.
In an embodiment of the present invention, the preset storage format may be { an identity of a called party: { call forwarding type: identity of the call-forwarding party } ] }. Wherein [ ] represents an array, {: denotes a mapping relation.
As shown in fig. 1, when receiving a message that a called party is temporarily unavailable, the IMS sends a call forwarding type and a Ticket to a call forwarding party (i.e., a third party terminal) of the called party at the same time, and because a communication key in the Ticket is encrypted by using a private key of a KMS server to which the calling party belongs, the third party terminal sends a call forwarding message to the KMS server to which the third party terminal belongs, where the call forwarding message at least carries the call forwarding type, the Ticket, and an identifier of the third party terminal. After receiving the call forwarding information, the KMS server to which the third party terminal belongs firstly verifies the identity of the third party terminal, and after the verification is passed, analyzes the Ticket to obtain the identity of the called party of the call forwarding, so that the fact that the identity of the called party is different from the identity of the third party terminal can be known, but the call forwarding information carries a call forwarding type, and the call forwarding identity of the third party terminal is verified, so that the KMS server to which the third party terminal belongs determines and verifies the call forwarding relation when the calling party calls the called party according to the identity of the third party terminal, the call forwarding type carried by the call forwarding information and the identity of the called party carried by the Ticket.
The authentication of the call forwarding relationship may be performed by a KMS server to which the called party belongs, or may be performed by a KMS server to which a third party terminal belongs.
When the call forwarding relationship is verified by the KMS server to which the called party belongs, as shown in fig. 1, the KMS server to which the third party terminal belongs sends the call forwarding relationship to the KMS server to which the called party belongs, the KMS server to which the called party belongs queries the obtained call forwarding information table for the identity identifier of the call forwarding party matching the identity identifier of the called party and the call forwarding type, if the identity identifier of the call forwarding party is the identity identifier of the third party terminal, it is determined that the call forwarding relationship passes verification, and if the identity identifier of the call forwarding party is not the identity identifier of the third party terminal, it is determined that the call forwarding relationship does not pass verification, and a verification result is fed back to the KMS server to which the third party terminal belongs.
When the call forwarding relation is verified by a KMS server to which the third-party terminal belongs, the KMS server to which the third-party terminal belongs sends a call forwarding information table acquisition request to the KMS server to which the called party belongs, when the call forwarding information table sent by the KMS server to which the called party belongs is received, a call forwarding party identity which is matched with the identity of the called party and the call forwarding type is inquired in the acquired call forwarding information table, if the call forwarding party identity is the identity of the third-party terminal, the call forwarding relation is determined to be verified, and if the call forwarding party identity is not the identity of the third-party terminal, the call forwarding relation is determined not to be verified.
When the call forwarding relation is confirmed to pass the verification, the KMS server to which the third party terminal belongs sends the identity and the Ticket of the third party terminal to the KMS server to which the calling party belongs for decryption, the KMS server to which the calling party belongs sends the communication key to the KMS server to which the third party terminal belongs after decrypting the Ticket, the third party terminal sends a response message to the calling party through the IMS, and then the third party terminal starts the communication with the calling party according to the communication key.
When the third party terminal cannot be connected, the call can be transferred to the call transfer party corresponding to the third party terminal for answering, the call transfer party of the third party terminal can also be set in advance by the user according to the call transfer type, the specific setting method is the same as that of the called party, and the detailed description is omitted here.
The call forwarding system for multiple call forwarding may include: the method comprises the steps of calling, called and third party terminals (namely, the calling party is appointed to be used as a call transfer party of the called party in advance when the calling party calls the called party), a fourth party terminal (the call transfer party appointed by the call transfer party of the called party) \8230; (the terminal which is to answer the call finally, namely, the final call transfer party after multiple call transfers), a KMS server to which the calling party belongs, a KMS server to which the called party belongs, a KMS server to which the third party terminal belongs, a KMS server to which the fourth party terminal belongs, \8230;, and a KMS server to which the answering party belongs. The KMS server to which the calling party belongs, the KMS server to which the called party belongs, the KMS server to which the third party terminal belongs, the KMS server to which the fourth party terminal belongs, \8230, and the KMS server to which the answering party belongs have the same deployment method as that of the KMS server for single call transfer, can be deployed independently, centrally or partially, and the deployment method is not particularly limited in the embodiment of the invention, and can be determined by a person skilled in the art according to actual conditions.
It should be noted that the number of call forwarding may be preset in advance, for example, when 3 call forwarding operations are not connected, the IMS feeds back a message of call failure to the calling party.
After receiving the call forwarding message, the KMS server to which the receiver belongs needs to verify the call forwarding message, and for the multiple call forwarding messages, the multiple call forwarding messages carry a call forwarding type list, where the call forwarding type list includes the call forwarding type of each call forwarding. The specific verification method comprises the following steps:
the call forwarding relationship verification may be performed from front to back according to the call types in the call forwarding type list, and is referred to as a first call forwarding type and a first call forwarding relationship (called party to third party terminal), a second call forwarding type and a second call forwarding relationship (third party terminal to fourth party terminal), a third call forwarding type and a third call forwarding relationship (fourth party terminal to fifth party terminal), and so on.
The specific verification method can be divided into the following two types, the selection of the verification method is not specifically limited in the embodiment of the present invention, and the selection can be determined by a person skilled in the art according to actual situations.
The method comprises the following steps that 1, a KMS server to which a receiver belongs repeatedly inquires:
the KMS server to which the answering party belongs sends the first call forwarding type and the identity of the called party to the KMS server to which the called party belongs, and the KMS server to which the called party belongs can obtain and return the identity of the third party terminal by matching the first call forwarding type and the identity of the called party; then the KMS server to which the answering party belongs sends the second call forwarding type and the identity of the third party terminal to the KMS server to which the third party terminal belongs, and the KMS server to which the third party terminal belongs can obtain and return the identity of the fourth party terminal by matching the second call forwarding type and the identity of the third party terminal; then the KMS server to which the answering party belongs sends the third call forwarding type and the identity of the fourth party terminal to the KMS server to which the fourth party terminal belongs, and the KMS server to which the fourth party terminal belongs can obtain and return the identity of the fifth party terminal by matching the third call forwarding type and the identity of the fourth party terminal; and repeating the steps until the last call forwarding type query in the call forwarding type list returns to obtain the final identity identifier of the forwarding party, comparing the final identity identifier of the forwarding party with the identity identifier of the answering party, if the final identity identifier of the forwarding party is consistent with the final identity identifier of the answering party, the authentication is passed, and if the final identity identifier of the forwarding party is inconsistent with the final identity identifier of the answering party, the authentication is not passed.
As an optional implementation manner of the embodiment of the present invention, the KMS server to which the answering party belongs may also send all call forwarding relationships to the corresponding KMS server at one time.
And 2, a verification method 2. The KMS server to which the receiver belongs carries out chain inquiry:
the KMS server to which the answering party belongs sends the call forwarding type list, the identity of the called party and the identity of the answering party to the KMS server to which the called party belongs, and the KMS server to which the called party belongs matches the first call forwarding type and the identity of the called party to obtain the identity of a third party terminal; then the KMS server of the called party terminal sends the call forwarding type list after the first call forwarding type is removed, the identity of the third party terminal and the identity of the answering party to the KMS server of the third party terminal, and the KMS server of the third party terminal matches the second call forwarding type and the identity of the third party terminal to obtain the identity of the fourth party terminal; then the KMS server corresponding to the third party terminal sends the call forwarding type list without the first call forwarding type and the second call forwarding type, the identity of the fourth party terminal and the identity of the answering party to the KMS server to which the fourth party terminal belongs, and the KMS server to which the fourth party terminal belongs matches the third call forwarding type and the identity of the fourth party terminal to obtain the identity of the fifth party terminal; and repeating the steps until the last call forwarding type in the call forwarding type list is inquired by a KMS server to obtain the final identity of the forwarding party, comparing the final identity of the forwarding party with the identity of the answering party, if the final identity of the forwarding party is consistent with the final identity of the answering party, the verification is passed, and if the final identity of the forwarding party is inconsistent with the final identity of the answering party, the verification is not passed.
Fig. 3 shows only two call forwarding examples, and as shown in fig. 3, when the IMS does not receive the feedback information for a preset time (e.g., 20 s), the IMS sends a call forwarding type list including 2 call forwarding types and a packet to a call forwarding party (a fourth party terminal in fig. 3) of the third party terminal. After receiving the call forwarding type list and the Ticket, the fourth party terminal sends a call forwarding message to a KMS server to which the fourth party terminal belongs, where the call forwarding message includes: identity of the fourth party terminal, call forwarding type list and Ticket.
And the KMS server to which the fourth party terminal belongs verifies the identity of the fourth party terminal, determines a first call forwarding relation according to the identity of the fourth party terminal, the call forwarding type list carried by the call forwarding message and the identity of the called party carried by the Ticket after the verification is passed, and sends the first call forwarding relation to the KMS server to which the called party belongs so as to verify the KMS server to which the called party belongs.
If a call forwarding relationship matched with the identity of the called party and the call forwarding type of the called party in the call forwarding type list exists in the obtained call forwarding information table, but the identity of the call forwarding party corresponding to the call forwarding relationship in the call forwarding information table is different from the identity of the fourth party terminal, determining that the first call forwarding relationship is not verified, determining a corresponding second call forwarding relationship according to the identity of the call forwarding party (namely, the third party terminal) corresponding to the call forwarding relationship in the call forwarding information table of the called party, the call forwarding type after the first call forwarding type is removed from the call forwarding type list, and the identity of the called party carried by the Ticket, sending the second call forwarding relationship to a KMS server to which the third party terminal belongs, verifying the second call forwarding relationship by the KMS server to which the third party terminal belongs, wherein the verification process is the same as the verification process of the first call forwarding relationship, and is not repeated. And the KMS server belonging to the third party terminal feeds back the authentication result to the KMS server belonging to the called party after determining the authentication result, and then the KMS server belonging to the called party feeds back the authentication result to the KMS server belonging to the fourth party terminal according to the authentication result. And when the verification result is that the communication key is passed, the KMS server to which the fourth terminal belongs sends a decryption request to the KMS server to which the calling party belongs to acquire the communication key, after the KMS server to which the fourth terminal belongs receives the communication key, the communication key is sent to the fourth terminal, the fourth terminal sends a response message to the calling party, and then the fourth terminal and the calling party carry out communication according to the communication key.
The call transfer system provided by the embodiment of the invention has small change on the existing IMS call flow, only under the scene of call transfer for many times, the existing call transfer type carried latest is modified to carry all the call transfer type information experienced in the call process for verification, and the KMS server stores the call transfer information table in advance, so that the validity verification of the identity of the final answering party of call transfer is realized, the communication can be ensured only by the answering party with the call transfer relation in the call transfer process, and the safety of the call transfer communication is improved.
As shown in fig. 4, fig. 4 is a flowchart of a call forwarding method shown in this specification according to an exemplary embodiment, and is applied to a key management service KMS server, where the KMS server may be a server integrating a KMS server to which a calling party belongs, a KMS server to which a called party belongs, and a KMS server to which a call forwarding party belongs, or may be only a KMS server to which a call forwarding party (i.e., a following third-party terminal) belongs.
The call forwarding method comprises the following steps:
s11: receiving a call transfer message initiated by a third party terminal; the third party terminal is a call transfer party which is appointed in advance when the calling party calls the called party; the call transfer message at least carries a call transfer type, a Ticket used when the calling party and the called party are in a conversation, and an identity of a third party terminal.
For example, for a call process, a calling party first sends a request message to a KMS server to which the calling party belongs, where the request message may carry an identity of the calling party and an identity of a called party, the KMS server to which the calling party belongs feeds back a communication key (i.e., an IMS media plane key) and a Ticket to the calling party according to the request message, and the calling party sends the received Ticket to the called party to request for a call. When the called party can not answer the call temporarily, the call is transferred to the third terminal according to the call transfer type to carry out the call.
The call forwarding message at least carries a call forwarding type, a Ticket and an identity of a third party terminal, and the identity of the third party terminal can be a user telephone number or a user domain name. The receiving method of the call transfer message initiated by the third party terminal may be receiving through a wireless network, and may also be receiving through a serial port.
S12: and after the third-party terminal passes the verification, determining the call forwarding relation when the calling party calls the called party according to the identity of the third-party terminal, the call forwarding type carried by the call forwarding message and the identity of the called party carried by the Ticket.
The verification of the third party terminal may refer to authenticating the identity of the third party terminal to determine whether the third party terminal is a valid terminal. And after the third-party terminal passes the verification, analyzing the Ticket to obtain the identity of the called party, analyzing the call transfer message to obtain the call transfer type, and determining the corresponding call transfer relationship according to the identity of the third-party terminal, the call transfer type carried by the call transfer message and the identity of the called party carried by the Ticket.
S13: and when the call forwarding relation is confirmed to pass the verification, controlling the third-party terminal to start the communication with the calling party.
For example, when it is determined that the call forwarding relationship is verified, the KMS server to which the third party terminal belongs may send a communication key to the third party terminal, and then control the third party terminal to open a call with the calling party through the communication key.
The verification process of the call forwarding relationship comprises the following processes:
1. the KMS server to which the third party terminal belongs is different from the KMS server to which the called party belongs:
1.1 the authentication process is performed by a KMS server to which the called party belongs, and specifically, the determining that the call forwarding relationship passes the authentication includes:
sending the call forwarding relation to a KMS server to which the called party belongs so as to verify the call forwarding relation by the KMS server to which the called party belongs;
and receiving a verification result returned by the KMS server to which the called party belongs, and determining that the call forwarding relation passes the verification if the verification result is passed.
1.2 the authentication process is performed by a KMS server to which the third party terminal belongs, and specifically, the determining that the call forwarding relationship passes the authentication includes:
sending a call forwarding information table acquisition request to a KMS server to which a called party belongs, wherein the call forwarding information table is used for acquiring a call forwarding information table of the called party, which is stored in the KMS server to which the called party belongs;
after receiving the call forwarding information table, inquiring the identity of the call forwarding party matched with the identity of the called party and the call forwarding type in the obtained call forwarding information table, and if the identity of the call forwarding party is the identity of the third party terminal, determining that the call forwarding relation passes verification.
2. The KMS server to which the third party terminal belongs is the same as the KMS server to which the called party belongs; the step of determining that the call forwarding relationship is verified comprises:
and inquiring the identity identification of the call transfer party matched with the identity identification and the call transfer type of the called party in the obtained call transfer information table, and if the identity identification of the call transfer party is the identity identification of the third party terminal, determining that the call transfer relationship passes the verification.
Illustratively, when the KMS server to which the third party terminal belongs is the same as the KMS server to which the called party belongs, the KMS server to which the third party terminal belongs directly retrieves the call forwarding information table of the called party from the local, and then performs authentication.
In the embodiment of the specification, the call transfer relationship determined according to the identity of the third-party terminal, the call transfer type carried by the call transfer message and the identity of the called party carried by Ticket is verified by receiving the call transfer message initiated by the third-party terminal, and after the verification is passed, the third-party terminal is controlled to start the call with the calling party, so that the validity of the call transfer relationship is ensured, and the security of the call transfer call is improved.
As an optional implementation manner of the embodiment of the present invention, the controlling the third party terminal to open a call with the calling party, where the KMS server to which the third party terminal belongs is different from the KMS server to which the calling party belongs, includes:
firstly, a decryption request message is sent to a KMS server to which a calling party belongs, the decryption request message carries an identity and a Ticket of a third party terminal, and the KMS server to which the calling party belongs decrypts the Ticket.
And secondly, receiving the communication key sent by the KMS server to which the calling party belongs.
And thirdly, controlling the third-party terminal to open the call with the calling party through the communication key.
Illustratively, since the communication key in the Ticket is encrypted by the private key of the KMS server to which the calling party belongs, the KMS server to which the third party terminal belongs simultaneously sends the identifier of the third party terminal and the Ticket to the KMS server to which the calling party belongs, so that the KMS server to which the calling party belongs can decrypt the Ticket. The decryption request message and the communication key can be sent through a wireless network or through a serial port.
And when the KMS server to which the third party terminal belongs is the same as the KMS server to which the calling party belongs, the call transfer relation is confirmed to be verified and then directly decrypted to obtain the communication key.
For specific implementation and effects, reference is made to the description of the call forwarding system, and details are not described herein again.
As shown in fig. 5, fig. 5 is a flowchart of a call forwarding method according to an exemplary embodiment shown in this specification, applied to a KMS server, which serves as a KMS server to which a called party belongs, and includes the following steps:
s21: and receiving a call forwarding relation sent by a KMS server to which the call forwarding party belongs, wherein the call forwarding relation is determined by the KMS server to which the call forwarding party belongs according to the identity of the call forwarding party, the call forwarding type carried by a call forwarding message initiated by the call forwarding party and the identity of a called party carried in a Ticket used when the calling party and the called party are in conversation.
S22: and verifying the call forwarding relation, and returning a verification result to the KMS server to which the call forwarding party belongs so that the KMS server to which the call forwarding party belongs controls the call forwarding party to open the call with the calling party based on the verification result.
For example, the number of call forwarding types carried by the call forwarding message is not specifically limited in the embodiment of the present invention, and may be determined by a person skilled in the art according to an actual situation.
When the call forwarding type is one, the method for verifying the call forwarding relationship may refer to the verification process in the case that the KMS server to which the third party terminal belongs is different from the KMS server to which the called party belongs, and is not described herein again.
When the number of call forwarding types is at least two, as an optional implementation manner of the embodiment of the present invention, the call forwarding message carries at least two call forwarding types, and an order of the call forwarding types corresponds to an order of callers called by the caller, where the order of the callers called by the caller is: at least two call transfer parties which are appointed to carry out call transfer in sequence when the called party and the calling party call the called party;
the verifying the call forwarding relationship includes:
verifying whether a target call forwarding party of the calling party aiming at the call forwarding of the called party is a call forwarding party sending a call forwarding relation or not according to the identity of the called party and the call forwarding type corresponding to the called party;
if yes, determining that the verification is passed;
if not, according to the identity of the target call forwarding party, the call forwarding type corresponding to the target call forwarding party and the identity of the call forwarding party sending the call forwarding relation, constructing information to be verified, sending the information to be verified to a KMS server to which the target call forwarding party belongs, verifying the information to be verified by the KMS server to which the target call forwarding party belongs and returning a verification instruction to the KMS server to which the called party belongs, wherein the verification instruction comprises passing verification or failing verification; whether the target transferor is authenticated is determined according to the authentication indication returned by the KMS server to which the target transferor belongs.
In a specific embodiment, reference is made to a specific process of performing chain query by a KMS server to which the answering party belongs, and details are not described herein again.
For a specific embodiment, reference is made to the related description of the call forwarding system, which is not described herein again.
Corresponding to the embodiments of the method, the present specification also provides embodiments of the apparatus and the terminal applied thereto.
As shown in fig. 6, fig. 6 is a block diagram of a call transfer apparatus shown in the present specification according to an exemplary embodiment, applied to a key management service KMS server as a KMS server to which a third party terminal belongs, the call transfer apparatus including:
a call forwarding message receiving module 31, configured to receive a call forwarding message initiated by a third party terminal; the third party terminal is a call forwarding party which is appointed in advance when the calling party calls the called party; the call transfer message at least carries a call transfer type, a bill and an identity of a third party terminal;
a call transfer relationship determining module 32, configured to determine, after the third-party terminal passes the verification, a call transfer relationship when the calling party calls the called party according to the identity of the third-party terminal, the call transfer type carried in the call transfer message, and the identity of the called party carried in a Ticket used when the calling party and the called party talk;
and the control module 33 is configured to control the third-party terminal to open a call with the calling party when it is determined that the call forwarding relationship is verified.
In the embodiment of the description, the call transfer message initiated by the third-party terminal is received, the call transfer relationship determined according to the identity of the third-party terminal, the call transfer type carried by the call transfer message and the identity of the called party carried by packet is verified, and after the verification is passed, the third-party terminal is controlled to start the call with the calling party, so that the validity of the call transfer relationship is ensured, and the security of the call transfer call is improved.
As an optional implementation manner of the embodiment of the present invention, a KMS server to which the third party terminal belongs is different from a KMS server to which the called party belongs; the call transfer apparatus further comprises:
the call forwarding relation sending module is used for sending the call forwarding relation to the KMS server to which the called party belongs so as to verify the call forwarding relation by the KMS server to which the called party belongs;
and the verification result receiving module is used for receiving the verification result returned by the KMS server to which the called party belongs, and if the verification result is passed, determining that the call forwarding relation is passed through verification.
As an optional implementation manner of the embodiment of the present invention, the KMS server to which the third party terminal belongs is different from the KMS server to which the calling party belongs, and the first control module 33 is specifically configured to:
and sending a decryption request message to a KMS server to which the calling party belongs, wherein the decryption request message carries the identity and the Ticket of the third party terminal, so that the KMS server to which the calling party belongs decrypts the Ticket.
And receiving the communication key sent by the KMS server to which the calling party belongs.
And controlling the third party terminal to open the call with the calling party through the communication key.
As an optional implementation manner of the embodiment of the present invention, a KMS server to which the third party terminal belongs is the same as a KMS server to which the called party belongs; the call transfer device further comprises:
and the query module is used for querying the identity identification of the call forwarding party matched with the identity identification of the called party and the call forwarding type in the obtained call forwarding information table, and if the identity identification of the call forwarding party is the identity identification of the third-party terminal, determining that the call forwarding relation passes the verification.
For the specific implementation and effects of each module, reference is made to the description of the method embodiment, and details are not repeated here.
As shown in fig. 7, fig. 7 is a block diagram of a call forwarding device according to an exemplary embodiment, which is applied to a KMS server, where the KMS server is a KMS server to which a called party belongs, and includes the following steps:
a call forwarding relation receiving module 41, configured to receive a call forwarding relation sent by a KMS server to which a call forwarding party belongs, where the call forwarding relation is determined by the KMS server to which the call forwarding party belongs according to an identity of the call forwarding party, a call forwarding type carried in a call forwarding message initiated by the call forwarding party, and an identity of a called party carried in a Ticket used when a calling party and the called party talk;
and the call forwarding relation verification module 42 is configured to verify the call forwarding relation and return a verification result to the KMS server to which the call forwarding party belongs, so that the KMS server to which the call forwarding party belongs controls the call forwarding party to open a call with the calling party based on the verification result.
As an optional implementation manner of the embodiment of the present invention, the call forwarding message carries at least two call forwarding types, and the sequence of the call forwarding types corresponds to the sequence of the calling party called by the calling party, where the sequence of the calling party called by the calling party is: at least two call transfer parties which are appointed to carry out call transfer in sequence when the called party and the calling party call the called party;
the call transfer relationship verification module 42 is specifically configured to:
according to the identity of the called party and the call transfer type corresponding to the called party, verifying whether a target call transfer party of the calling party aiming at the call transfer of the called party is a call transfer party sending a call transfer relationship;
if yes, determining that the verification is passed;
if not, according to the identity of the target call transfer party, the call transfer type corresponding to the target call transfer party and the identity of the call transfer party sending the call transfer relationship, constructing information to be verified, sending the information to be verified to a KMS (KMS) server to which the target call transfer party belongs, verifying the information to be verified by the KMS server to which the target call transfer party belongs, and returning a verification instruction to the KMS server to which the called party belongs, wherein the verification instruction comprises passing verification or failing verification; whether the target transferor is authenticated is determined according to the authentication indication returned by the KMS server to which the target transferor belongs.
For the specific implementation and effects of the above modules, reference is made to the description of the above method embodiments, and details are not repeated here.
For the device embodiment, since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the modules described as separate components may or may not be physically separate, and the components displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.
The embodiments of the call transfer apparatus of the present specification can be applied to a computer device, such as a server or a terminal device. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a logical device, the device is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the call forwarding device. From a hardware aspect, as shown in fig. 8, which is a hardware structure diagram of a computer device in which a call forwarding apparatus is located in an embodiment of this specification, except for the processor 310, the memory 330, the network interface 320, and the nonvolatile memory 340 shown in fig. 8, a server or an electronic device in which an apparatus 331 is located in an embodiment may also include other hardware according to an actual function of the computer device, and details of this are not described again.
The present application also provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of any of the call forwarding methods provided herein.
In particular, computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disk or removable disks), magneto-optical disks, and CD ROM and DVD-ROM disks.
The foregoing description of specific embodiments has been presented for purposes of illustration and description. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This specification is intended to cover any variations, uses, or adaptations of the specification following, in general, the principles of the specification and including such departures from the present disclosure as come within known or customary practice within the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.
It will be understood that the present description is not limited to the precise arrangements described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.
The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present disclosure should be included in the protection scope of the present disclosure.

Claims (7)

1. A call forwarding method is applied to a KMS server serving as a KMS server to which a third party terminal belongs, and comprises the following steps:
receiving a call forwarding message initiated by a third party terminal; the third party terminal is a call transfer party which is appointed in advance when a calling party calls a called party; the call transfer message at least carries a call transfer type, a Ticket used when the calling party and the called party are communicated and an identity identifier of a third party terminal, and the call transfer type carried by the call transfer message and the Ticket used when the calling party and the called party are communicated are sent to the third party terminal by an IMS (IP multimedia subsystem); the call forwarding type is always forwarding, forwarding when busy, forwarding when no one answers or forwarding when connection cannot be achieved;
after the third-party terminal passes the verification, determining a call transfer relationship when the calling party calls the called party according to the identity of the third-party terminal, the call transfer type carried by the call transfer message and the identity of the called party carried by the Ticket;
when the call forwarding relationship is confirmed to pass verification, controlling the third party terminal to start the call with the calling party;
wherein, the KMS server to which the third party terminal belongs is different from the KMS server to which the called party belongs; verifying the call forwarding relationship by:
sending the call forwarding relationship to a KMS server to which the called party belongs, inquiring a call forwarding party identity which is matched with the called party identity and the call forwarding type carried by the packet in an obtained call forwarding information table by the KMS server to which the called party belongs, determining that the call forwarding relationship passes verification if the call forwarding party identity is the identity of the third-party terminal, determining that the call forwarding relationship does not pass verification if the call forwarding party identity is not the identity of the third-party terminal, and feeding back a verification result to the KMS server to which the third-party terminal belongs;
receiving a verification result returned by the KMS server to which the called party belongs, and if the verification result is passed, determining that the call forwarding relation is verified;
the KMS server to which the third party terminal belongs is the same as the KMS server to which the called party belongs; verifying the call forwarding relationship by:
and inquiring a call forwarding party identity which is matched with the identity of the called party and the call forwarding type in the obtained call forwarding information table, and if the call forwarding party identity is the identity of the third-party terminal, determining that the call forwarding relation passes verification.
2. The method as claimed in claim 1, wherein the KMS server to which the third party terminal belongs is different from the KMS server to which the calling party belongs, and the controlling the third party terminal to open the call with the calling party comprises:
sending a decryption request message to a KMS server to which the calling party belongs, wherein the decryption request message carries the identity of the third party terminal and the Ticket, so that the KMS server to which the calling party belongs decrypts the Ticket;
receiving a communication key sent by a KMS server to which the calling party belongs;
and controlling the third party terminal to open the call with the calling party through the communication key.
3. A call forwarding method applied to a KMS server, the KMS server serving as a KMS server to which a called party belongs, comprising the steps of:
receiving a call forwarding relation sent by a KMS server to which a call forwarding party belongs, wherein the call forwarding relation is determined by the KMS server to which the call forwarding party belongs according to an identity of the call forwarding party, a call forwarding type carried by a call forwarding message initiated by the call forwarding party and an identity of a called party carried in a Ticket used when a calling party and the called party are in communication, and the call forwarding type carried by the call forwarding message and the Ticket used when the calling party and the called party are in communication are sent to the call forwarding party by an IMS; the call transfer type is transfer all the time, transfer when busy, transfer when no one answers or transfer when connection is unavailable;
verifying the call forwarding relation, and returning a verification result to a KMS (KMS server) to which the call forwarding party belongs so that the KMS to which the call forwarding party belongs controls the call forwarding party to open a call with the calling party based on the verification result;
when the call forwarding message carries a call forwarding type, the verifying the call forwarding relationship includes:
and inquiring the identity identification of the call forwarding party matched with the identity identification and the call forwarding type of the called party in the obtained call forwarding information table, if the inquired identity identification of the call forwarding party is the identity identification of the call forwarding party, determining that the call forwarding relation passes the verification, and if the inquired identity identification of the call forwarding party is not the identity identification of the call forwarding party, determining that the call forwarding relation does not pass the verification.
4. The method of claim 3, wherein when the call forwarding message carries at least two call forwarding types, an order of the call forwarding types corresponds to an order of the calling parties called by the calling party, wherein the order of the calling parties called by the calling party is: the called party and the calling party are appointed at least two call forwarding parties for performing call forwarding in sequence when calling the called party;
the verifying the call forwarding relationship comprises:
verifying whether a target call forwarding party of the calling party aiming at the call forwarding of the called party is a call forwarding party sending the call forwarding relation or not according to the identity of the called party and the call forwarding type corresponding to the called party;
if yes, determining that the verification is passed;
if not, according to the identity of the target call forwarding party, the call forwarding type corresponding to the target call forwarding party and the identity of the call forwarding party sending the call forwarding relationship, constructing information to be verified, sending the information to be verified to a KMS server to which the target call forwarding party belongs, verifying the information to be verified by the KMS server to which the target call forwarding party belongs and returning a verification instruction to the KMS server to which the called party belongs, wherein the verification instruction comprises passing verification or failing verification; and determining whether the target transferer passes the authentication according to the authentication indication returned by the KMS server to which the target transferer belongs.
5. A call transfer apparatus applied to a key management service KMS server as a KMS server to which a third party terminal belongs, comprising:
the call transfer message receiving module is used for receiving a call transfer message initiated by a third-party terminal; the third party terminal is a call forwarding party which is appointed in advance when the calling party calls the called party; the call forwarding message at least carries a call forwarding type, a Ticket and an identity identifier of a third party terminal, and the call forwarding type carried by the call forwarding message and the Ticket used when the calling party and the called party are communicated are sent to the third party terminal by an IMS; the call forwarding type is always forwarding, forwarding when busy, forwarding when no one answers or forwarding when connection cannot be achieved;
a call transfer relationship determining module, configured to determine, after the third-party terminal passes verification, a call transfer relationship when the calling party calls the called party according to an identity of the third-party terminal, a call transfer type carried in the call transfer message, and an identity of the called party carried in the Ticket used when the calling party and the called party talk;
the control module is used for controlling the third-party terminal to start the communication with the calling party when the call transfer relationship is determined to pass the verification;
wherein the KMS server to which the third party terminal belongs is different from the KMS server to which the called party belongs; the device further comprises:
a call forwarding relation sending module, configured to send the call forwarding relation to a KMS server to which the called party belongs, query, in an obtained call forwarding information table, a KMS server to which the called party belongs, a call forwarding party identity that matches the called party identity and the call forwarding type carried by Ticket, determine that the call forwarding relation passes verification if the call forwarding party identity is an identity of the third-party terminal, determine that the call forwarding relation fails verification if the call forwarding party identity is not an identity of the third-party terminal, and feed back a verification result to the KMS server to which the third-party terminal belongs;
the authentication result receiving module is used for receiving an authentication result returned by the KMS server to which the called party belongs, and if the authentication result is passed, determining that the call forwarding relation is authenticated;
the KMS server to which the third party terminal belongs is the same as the KMS server to which the called party belongs; the device further comprises:
and the query module is used for querying the identity identification of the call forwarding party matched with the identity identification of the called party and the call forwarding type in the obtained call forwarding information table, and if the identity identification of the call forwarding party is the identity identification of the third-party terminal, determining that the call forwarding relation passes verification.
6. A call transfer apparatus applied to a KMS server as a KMS server to which a called party belongs, comprising:
a call forwarding relation receiving module, configured to receive a call forwarding relation sent by a KMS server to which a call forwarding party belongs, where the call forwarding relation is determined by the KMS server to which the call forwarding party belongs according to an identity of the call forwarding party, a call forwarding type carried in a call forwarding message initiated by the call forwarding party, and an identity of a called party carried in a Ticket used when a calling party and the called party are in a call, and the call forwarding type carried in the call forwarding message and the Ticket used when the calling party and the called party are in a call are sent to the call forwarding party by an IMS; the call forwarding type is always forwarding, forwarding when busy, forwarding when no one answers or forwarding when connection cannot be achieved;
the call forwarding relation verification module is used for verifying the call forwarding relation and returning a verification result to the KMS server to which the call forwarding party belongs so that the KMS server to which the call forwarding party belongs controls the call forwarding party to open a call with the calling party based on the verification result;
when the call forwarding message carries a call forwarding type, the call forwarding relation verification module is specifically configured to:
and inquiring the identity identification of the call forwarding party matched with the identity identification and the call forwarding type of the called party in the obtained call forwarding information table, if the inquired identity identification of the call forwarding party is the identity identification of the call forwarding party, determining that the call forwarding relation passes the verification, and if the inquired identity identification of the call forwarding party is not the identity identification of the call forwarding party, determining that the call forwarding relation does not pass the verification.
7. The apparatus of claim 6, wherein when the call forwarding message carries at least two call forwarding types, an order of the call forwarding types corresponds to an order of callers of the calling party, wherein the order of callers of the calling party is: the called party and the calling party are appointed to carry out at least two call forwarding parties for call forwarding in sequence when calling the called party;
the call transfer relationship verification module is specifically configured to:
verifying whether a target call forwarding party of the calling party aiming at the call forwarding of the called party is a call forwarding party sending the call forwarding relation or not according to the identity of the called party and the call forwarding type corresponding to the called party;
if yes, determining that the verification is passed;
if not, according to the identity of the target call transfer party, the call transfer type corresponding to the target call transfer party and the identity of the call transfer party sending the call transfer relationship, constructing information to be verified, sending the information to be verified to a KMS (KMS) server to which the target call transfer party belongs, verifying the information to be verified by the KMS server to which the target call transfer party belongs, and returning a verification instruction to the KMS server to which the called party belongs, wherein the verification instruction comprises passing verification or failing verification; and determining whether the target transferer passes the authentication according to the authentication indication returned by the KMS server to which the target transferer belongs.
CN202210768085.2A 2022-07-01 2022-07-01 Call forwarding method and device Active CN114866519B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210768085.2A CN114866519B (en) 2022-07-01 2022-07-01 Call forwarding method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210768085.2A CN114866519B (en) 2022-07-01 2022-07-01 Call forwarding method and device

Publications (2)

Publication Number Publication Date
CN114866519A CN114866519A (en) 2022-08-05
CN114866519B true CN114866519B (en) 2022-11-01

Family

ID=82625888

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210768085.2A Active CN114866519B (en) 2022-07-01 2022-07-01 Call forwarding method and device

Country Status (1)

Country Link
CN (1) CN114866519B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101150631A (en) * 2007-09-20 2008-03-26 华为技术有限公司 A method and device for setting call forward
CN102238500A (en) * 2010-04-21 2011-11-09 中兴通讯股份有限公司 Method and system for forwarding calls safely
CN102752263A (en) * 2011-04-18 2012-10-24 中兴通讯股份有限公司 Method and system for realizing end-to-end safety call forwarding
CN103841534A (en) * 2012-11-20 2014-06-04 中国移动通信集团公司 Call transfer method, call transfer setting method, and mobile terminal
CN105227788A (en) * 2015-10-12 2016-01-06 中国联合网络通信集团有限公司 Call verification methods and applications server
CN113890906A (en) * 2021-11-02 2022-01-04 中国联合网络通信集团有限公司 Call forwarding method and device, electronic equipment and computer readable storage medium

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101420668B (en) * 2007-10-25 2010-10-13 华为技术有限公司 Method, system and apparatus for implementing call forwarding
US8850203B2 (en) * 2009-08-28 2014-09-30 Alcatel Lucent Secure key management in multimedia communication system
CN104010286B (en) * 2013-02-25 2018-01-02 上海斐讯数据通信技术有限公司 Call transferring method and mobile terminal
CN106973372A (en) * 2017-04-28 2017-07-21 努比亚技术有限公司 Call forwarding implementation method, terminal, core net and computer-readable recording medium
CN110418299B (en) * 2019-09-12 2022-02-11 中国联合网络通信集团有限公司 Call forwarding method and system

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101150631A (en) * 2007-09-20 2008-03-26 华为技术有限公司 A method and device for setting call forward
CN102238500A (en) * 2010-04-21 2011-11-09 中兴通讯股份有限公司 Method and system for forwarding calls safely
CN102752263A (en) * 2011-04-18 2012-10-24 中兴通讯股份有限公司 Method and system for realizing end-to-end safety call forwarding
CN103841534A (en) * 2012-11-20 2014-06-04 中国移动通信集团公司 Call transfer method, call transfer setting method, and mobile terminal
CN105227788A (en) * 2015-10-12 2016-01-06 中国联合网络通信集团有限公司 Call verification methods and applications server
CN113890906A (en) * 2021-11-02 2022-01-04 中国联合网络通信集团有限公司 Call forwarding method and device, electronic equipment and computer readable storage medium

Also Published As

Publication number Publication date
CN114866519A (en) 2022-08-05

Similar Documents

Publication Publication Date Title
US7739196B2 (en) Policy control and billing support for call transfer in a session initiation protocol (SIP) network
US20090025075A1 (en) On-demand authentication of call session party information during a telephone call
US7406306B2 (en) Method for billing in a telecommunications network
US8488775B2 (en) Method and system for recording automatic call distributor calls
US9185214B2 (en) Method and apparatus for providing enhanced communications
US20090046839A1 (en) Verifying authenticity of called party in telephony networks
US9077806B2 (en) Method, system and apparatus for implementing secure call forwarding
US10778841B2 (en) Method and system for implementing telephone solicitation prevention
US20050234829A1 (en) Method and system for content delivery control using a parallel network
CN112671864B (en) Privacy number dynamic allocation system based on active request
Mustafa et al. End-to-end detection of caller ID spoofing attacks
WO2008089626A1 (en) A method for identifying a malicious call
US20090025062A1 (en) Verifying authenticity of conference call invitees
CN114866519B (en) Call forwarding method and device
Du et al. {UCBlocker}: Unwanted call blocking using anonymous authentication
US20060147038A1 (en) Method and installation for controlling a telephone call transmitter on an internet network and telephone terminal therefor
CN111163465B (en) Method and device for connecting user terminal and local terminal and call center system
CN114630000A (en) Authentication information management and identity verification method, device and storage medium
JP2006005880A (en) Notification number verification system
CN114726843A (en) Telephone verification method, related device and communication equipment
CN114760625A (en) Encrypted call method, device and system
CN114727243A (en) VoLTE encryption communication method, device, system, terminal and storage medium
EP2014075A1 (en) Spit defence by positive lists protected by cryptographic keys
WO2008011837A2 (en) Method of remote authentication of the telephone network subscriber

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant