WO2022193110A1 - 一种呼叫处理方法、相关设备以及存储介质 - Google Patents

一种呼叫处理方法、相关设备以及存储介质 Download PDF

Info

Publication number
WO2022193110A1
WO2022193110A1 PCT/CN2021/080939 CN2021080939W WO2022193110A1 WO 2022193110 A1 WO2022193110 A1 WO 2022193110A1 CN 2021080939 W CN2021080939 W CN 2021080939W WO 2022193110 A1 WO2022193110 A1 WO 2022193110A1
Authority
WO
WIPO (PCT)
Prior art keywords
called
calling
encrypted
user
temporary
Prior art date
Application number
PCT/CN2021/080939
Other languages
English (en)
French (fr)
Inventor
柳亮亮
叶进洲
李飞
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN202180095568.4A priority Critical patent/CN117015957A/zh
Priority to EP21930706.3A priority patent/EP4297386A4/en
Priority to PCT/CN2021/080939 priority patent/WO2022193110A1/zh
Publication of WO2022193110A1 publication Critical patent/WO2022193110A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H04W12/041—Key generation or derivation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/72—Subscriber identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/75—Temporary identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/57—Arrangements for indicating or recording the number of the calling subscriber at the called subscriber's set
    • H04M1/571—Blocking transmission of caller identification to called party
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42025—Calling or Called party identification service
    • H04M3/42034—Calling party identification service
    • H04M3/42042—Notifying the called party of information on the calling party

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a call processing method, related equipment and storage medium.
  • the calling user In the process of implementing the calling user to the called user, the calling user needs to send the calling user's calling number and the called user's called number to the audio and video communication network. However, in the process that the calling user calls the called user based on the audio and video communication network, the calling number and the called number are easily leaked, thereby causing leakage of user privacy information.
  • Embodiments of the present invention provide a call processing method, a related device, and a storage medium, which are used to avoid leakage of the user's private information in the process of a calling user calling a called user.
  • an embodiment of the present invention provides a method for processing a call.
  • the method includes: a first device receives an encrypted called identifier, the encrypted called identifier is generated by encrypting the called identifier, and the called identifier is encrypted.
  • the identifier is the identifier of the called user; the first device obtains the called temporary identifier corresponding to the encrypted called identifier, and the called temporary identifier is the identifier temporarily allocated for the called user;
  • the second device sends the called temporary identification, and the second device is used to call the called device used by the called user according to the called temporary identification.
  • the first device receives the encrypted and encrypted called ID, which avoids the possibility of the called ID being leaked. Moreover, in the process of the calling user calling the called user, each device does not need to decrypt the encrypted called party's identity, which avoids the need for each device to decrypt the encrypted called party's identity, which involves the private information of the called user. The risk of leakage of the called ID improves the security of the called ID during the call. In addition, during the calling process, each device does not need to decrypt the encrypted called ID, which improves the calling efficiency.
  • the method before the first device obtains the called temporary identity corresponding to the encrypted called identity, the method further includes: the first device obtains the called temporary identity corresponding to the called identity. the called temporary identification; the first device establishes the corresponding relationship between the encrypted called identification and the called temporary identification.
  • the called temporary identification does not involve the private information of the called user, for example, the temporary identification information is a series of random characters corresponding to the called user. It can be seen that, if the called temporary identification is leaked, because the called temporary identification does not involve the private information of the called user, the leakage of the private information of the called user can be effectively avoided.
  • the first device When the first device establishes the correspondence between the encrypted called ID and the called temporary ID, in the process of the calling user calling the called user, after receiving the encrypted called ID, the first device does not need to
  • the corresponding called temporary identification can be obtained by decrypting the encrypted called identification, and the called user can be called based on the called temporary identification.
  • the method further includes: the first device receives the encrypted data from the calling device. After the called ID, the encrypted called ID is generated by encrypting the called ID with the first key, and the calling device is the device used by the calling user; the first device uses the first key to pair The encrypted called ID is decrypted to obtain the called ID.
  • the method before the first device decrypts the encrypted called identifier by using the first key to obtain the called identifier, the method further includes: the first device The private key and the ephemeral public key from the calling device are calculated by elliptic curve cryptography ECC algorithm to obtain the first key.
  • the first device can obtain the called ID by decrypting the encrypted called ID with the first key, so as to establish the corresponding relationship between the encrypted called ID and the called temporary ID, and improve the communication between the calling device and the first device. Security of the called ID transmitted by the device.
  • the method before the first device sends the called temporary identifier to the second device, the method further includes: after the first device receives the first encrypted data from the calling device Caller ID, after the first encryption, the caller ID is encrypted by the first key to generate the caller ID, and the caller ID is the ID of the calling user; the first device uses the first key to pair The first encrypted caller ID is decrypted to obtain the caller ID; the first device establishes a corresponding relationship between the encrypted callee ID and the caller ID.
  • the method further includes: the first device receives an identification query request from the called device, The identification query request includes the encrypted caller identification; the first device obtains the caller identification corresponding to the encrypted caller identification; the first device sends the caller identification to the called device.
  • the first device when the first device establishes the corresponding relationship between the encrypted called ID and the calling ID, the first device can send the calling party to the called device according to the ID query request during the process of calling the called user. ID, the called device can display the calling ID during the ringing process.
  • the method further includes: the first device uses a second key to identify the called called The called ID is encrypted to generate the encrypted called ID; the first device sends the encrypted called ID to the calling device.
  • the method before the first device sends the called temporary identifier to the second device, the method further includes: after the first device receives the first encrypted data from the calling device Caller ID, after the first encryption, the caller ID is encrypted by the first key to generate the caller ID, and the caller ID is the ID of the calling user; the first device uses the first key to generate the caller ID.
  • the encrypted caller ID is decrypted to obtain the caller ID; the first device encrypts the caller ID through the second key to generate a second encrypted caller ID; the first device sends the encrypted caller ID to the recipient.
  • the calling device sends the second encrypted caller ID.
  • the called device can obtain the calling identity without sending an identity query request to the first device separately, which improves the calling efficiency.
  • the caller ID sent by the first device to the called device is encrypted, which improves the security of the caller ID.
  • the method further includes: the first device receives a first temporary ID application from the called device, the first A temporary identification application includes the identifier of the user identification card of the called device; the first device allocates the called temporary identification to the called user according to the first temporary identification application; the first device establishes the called identification and The corresponding relationship of the called temporary identification; the first device sends the called temporary identification and the encrypted called identification to the called device.
  • the called device can send a first temporary identification application including the identifier of the user identification card to the first device, and the first device according to the first temporary identification application is The called device allocates the called temporary identification, and the called temporary identification does not involve the private information of the called user, thereby ensuring the security of the private information of the called user.
  • the method further includes: the first device receives a second temporary identifier application from the called device, and the first device receives a second temporary identifier application from the called device.
  • the second temporary identification application includes the called identification; the first device allocates the called temporary identification to the called user according to the second temporary identification application; the first device establishes the correspondence between the called identification and the called temporary identification relationship; the first device sends the called temporary identification to the called device.
  • the called device sends a second temporary identification application including the user's identification to the first device, and the first device can apply for the second temporary identification according to the second temporary identification from the called device. , assigns a called temporary identification to the called device, and the called temporary identification does not involve the private information of the called user, thereby ensuring the security of the private information of the called user.
  • the method further includes: the first device receives a registration request from the called device, The registration request includes the called temporary identification; the first device sends a random number to the called device; the first device encrypts the random number with a third key to generate a first parameter; the first device receives a random number from The second parameter of the called device, the second parameter is a parameter generated by the called device by encrypting the random number with the third key; if the first device determines the first parameter and the second parameter If they are equal, the first device sends a registration response message to the called device, where the registration response message is used to indicate that the called device is successfully registered.
  • the called user does not need to send a registration request containing the privacy information of the called user to the first device.
  • the registration request shown in this aspect includes the registration request that does not involve the privacy information of the called user.
  • the called temporary identifier is used to effectively ensure the security of the called user's private information during the process of the called user's registration to the first device.
  • an embodiment of the present invention provides a call processing method.
  • the method includes: a calling device obtains a called identity corresponding to a called user to be called; the calling device encrypts the called identity to obtain The encrypted called identifier; the calling device sends a call request message to the second device, and the call request message includes the encrypted called identifier.
  • the calling device encrypting the called identifier to obtain the encrypted called identifier includes: the calling device encrypts the called identifier by using a first key to obtain the encrypted callee ID.
  • the method before the calling device sends the call request message to the second device, the method further includes: the calling device encrypts the caller ID by using the first key to obtain The encrypted caller ID, the caller ID is an ID of the calling user, wherein the call request message includes the encrypted caller ID.
  • the method further includes: the calling device calculates the temporary private key and the public key from the first device by using an elliptic curve cryptography ECC algorithm to obtain the first key.
  • an embodiment of the present invention provides a call processing method, the method includes: the second device receives a called temporary identifier from the first device, where the called temporary identifier is an identifier temporarily allocated to the called user ; the second device sends a call request message to the called device, where the call request message includes the called temporary identification, and the called device is the device used by the called user.
  • the second device implements the call to the called user according to the called temporary identification.
  • the called temporary identification does not involve the private information of the called user, effectively avoiding the called user. Disclosure of user's private information.
  • the second device directly calls the called user according to the called temporary identification without decryption, which improves the efficiency of calling the called user. Because the second device does not obtain the called identity related to the called user's private information, the leakage of the called user's private information at the second device is effectively avoided, and the security of the called user's private information is improved.
  • the method before the second device receives the called temporary identifier from the first device, the method further includes: the second device receives a call request message from the calling device, the The call request message includes the encrypted called ID, the encrypted called ID is generated by encrypting the called ID, and the called ID is the ID of the called user; the second device sends a query request to the first device , the query request includes the encrypted called ID, and the query request is used to request to obtain the called temporary ID corresponding to the encrypted called ID.
  • the sending of the call request message by the second device to the called device includes: the second device, according to the registered address of the called device corresponding to the called temporary identification, sends the call request message to the called device.
  • the called device sends the call request message.
  • an embodiment of the present invention provides a first device, including a memory and a transceiver respectively coupled to a processor, the memory stores computer program codes, and the processor calls and executes the computer program codes in the memory , so that the processor executes the steps related to processing according to any one of the first aspect above, and the transceiver is configured to execute the steps related to sending and receiving according to any one of the first aspect above.
  • an embodiment of the present invention provides a calling device, including a memory and a transceiver respectively coupled to a processor, the memory stores computer program codes, and the processor calls and executes the computer program codes in the memory , so that the processor executes the steps related to processing according to any one of the above-mentioned second aspect, and the transceiver is configured to execute any one of the above-mentioned steps related to receiving and sending in the second aspect.
  • an embodiment of the present invention provides a second device, comprising a memory and a transceiver respectively coupled to a processor, the memory stores computer program codes, and the processor calls and executes the computer program codes in the memory , so that the processor executes the steps related to processing according to any one of the above third aspects, and the transceiver is configured to execute the steps related to receiving and sending according to any one of the above third aspects.
  • an embodiment of the present invention provides a communication system, including a calling device, a first device, a second device, and a called device, where the calling device is configured to call the first device and the second device via the first device and the second device.
  • the called device, the calling device is shown in the fifth aspect, the first device is shown in the fourth aspect, and the second device is shown in the sixth aspect.
  • an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, any one of the first to third aspects can be accomplished the method.
  • FIG. 1 is an exemplary structural diagram of an embodiment of a communication system provided by the application
  • FIG. 2 is a flow chart of steps of the first embodiment of the call processing method provided by the present application.
  • FIG. 3 is a flowchart of steps of the second embodiment of the call processing method provided by the present application.
  • FIG. 5 is a flowchart of steps of a fourth embodiment of the call processing method provided by the present application.
  • FIG. 6 is an exemplary structural diagram of an embodiment of the network device provided by the application.
  • FIG. 7 is a structural example diagram of another embodiment of the network device provided by the present application.
  • the application provides a call processing method.
  • the following first describes the structure of the communication system to which the method shown in the application is applied with reference to FIG. 1 : Yes, this application does not limit the specific network architecture of the communication system, as long as the calling user can implement a call to the called user based on the communication system, and during the calling process, the calling user's privacy information and information can be effectively guaranteed. The security of the private information of the called user is sufficient.
  • the communication system 100 shown in this embodiment includes a calling device used by the calling user.
  • the calling device shown in this embodiment may be any device that can call the called user, such as an intelligent terminal and a computer.
  • the calling device 110 shown in this embodiment can call the called device 120 used by the called user based on the communication system 100.
  • the called device 120 please refer to the description of the calling device 110, and details are not repeated.
  • the calling device 110 and the called device 120 are both connected to a transport control function (transport control function, TCF) 130.
  • the calling unified control function (UCF) 111 is respectively connected with the calling device 110, the TCF 130, the called UCF 121, the calling service enabler function (SEF) 112 and the calling service user profile function (service user profile function, SUPF) 113 connection.
  • the called UCF 121 is respectively connected with the called device 120 , the TCF 130 , the calling UCF 111 , the called SEF 122 and the called SUPF 123 .
  • the calling SEF 112 is connected to the calling UCF 111, the calling service and application function (service and application function, SAF) 114 and the calling SUPF 113, respectively.
  • the called SEF122 is respectively connected with the called UCF121, the called SAF124 and the called SUPF123.
  • the calling SUPF113 is also connected to the called SUPF123.
  • the calling bootstrapping server function (BSF) 115 is respectively connected with the calling SUPF113, the calling UCF111 and the calling device 110, and the called BSF215 is connected with the called SUPF123, the called UCF121 and the called device 120 respectively.
  • the calling SUPF 113 and the called SUPF 123 can interact through a hypertext transfer protocol over secure socket layer (HTTPS).
  • HTTPS hypertext transfer protocol over secure socket layer
  • between calling SEF112 and calling UCF111, between calling UCF111 and calling device 110, between calling UCF111 and called UCF121, between calling UCF111 and called UCF121, between called SEF122 and called UCF121, and Both the called UCF 121 and the called device 120 can interact through a session initiation protocol (session initiation protocol, SIP).
  • SIP session initiation protocol
  • the calling SEF112 and the calling SUPF113 and between the called SUPF123 and the called SEF can communicate through the N71 interface.
  • Both the calling UCF111 and the calling SUPF113, and between the called SUPF123 and the called UCF121 can communicate through the N70 interface.
  • the calling BSF 115 and the calling device 110 and the called BSF 215 and the called device 120 can interact through HTTPS.
  • the functions performed by the calling UCF 111 may include: processing the process of the calling user registering to the communication system through the calling device 110 and the functions of performing identity verification and authorization on the calling user. Interacts with the calling SUPF 113 to store, update, delete and query the calling user's profile, which may be used for registration, authentication and authorization procedures.
  • the signaling messages from the calling device 110 are processed, and corresponding signaling routes are determined according to different strategies.
  • the corresponding service is triggered according to the user profile obtained from the calling SUPF 113 . Traffic optimization of the media plane is controlled through interaction with the TCF130.
  • Interacts with the calling SEF 112 to ensure the provision of services and applications.
  • For the description of the function of the called UCF121 please refer to the description of the function of the calling UCF111, and details are not repeated.
  • the calling SEF112 will not only perform service-related support functions, but also perform functions such as registration, authentication, and authorization for calling users at the application layer, and be responsible for service and application management.
  • functions of the called SEF122 please refer to the description of the calling SEF112, and details are not repeated.
  • the calling SUPF 113 is used to provide the maintenance and management functions of the calling user profile, mainly including storing, updating, deleting and querying the related data of the calling user according to the requirements of the calling UCF 111 . For example, a corresponding relationship between a caller identification (ID) and a caller profile is established.
  • the calling SUPF 113 can query the calling user configuration file according to the calling user ID, wherein the calling user configuration file can be provided by the operator or the calling user.
  • the calling user sends a call request message to the calling UCF through the calling device, and the call request message includes the calling ID (such as the real number of the calling user) and the called ID (such as the real number of the called user).
  • the calling UCF sends an addressing request to the calling SUPF, where the addressing request is used to request to obtain the address of the called UCF to which the called device belongs.
  • the calling SUPF returns the address of the called UCF to the calling UCF.
  • the calling UCF can send a call request message to the called UCF according to the address of the called UCF, and the called UCF forwards the call request message to the called device to implement a call to the called device.
  • the call request message includes a caller ID related to the calling user's private information and a called ID related to the called user's private information, and the caller ID included in the call request message and the called ID are included in the call request message.
  • Call IDs are sent in clear text.
  • the caller ID and the called ID included in the call request message are easy to be maliciously snooped, thereby revealing the private information of the calling user and the called user.
  • the existing solutions can also establish a secure connection between devices based on digital certificates, for example, establish a transport layer security (TLS) protocol between the devices.
  • TLS transport layer security
  • Secure connection ensures the transmission security of the call request message transmitted between the devices, the process of establishing the secure connection is relatively complicated, which greatly delays the efficiency of the calling user calling the called user.
  • the call processing method provided by the present application can effectively avoid the leakage of the caller ID and the callee ID involving private information, and can also avoid the establishment of complex security between different devices. connection to improve the efficiency of the calling user calling the called user.
  • the call processing method shown in this application involves two stages.
  • Stage 1 is the process of assigning the calling temporary identification of the calling user and the called temporary identification of the called user.
  • the calling user registers based on the calling temporary identification.
  • the called user registers based on the called temporary ID. Wherein, the calling temporary identification does not involve the private information of the calling user, and the called temporary identification does not involve the private information of the called user.
  • Stage 2 the calling user calls the called user through the calling temporary ID and the called temporary ID.
  • Step 201 The terminal device sends a first temporary identification application to the SUPF.
  • the terminal device shown in this embodiment may be the calling device or the called device shown in FIG. 1 , which is not specifically limited in this embodiment. That is, the calling user can obtain the calling temporary identity through the method shown in this embodiment, and the called user can obtain the called temporary identity through the method shown in this embodiment.
  • the SUPF shown in this embodiment is the SUPF to which the terminal device belongs. For example, if the terminal device is the calling device, the SUPF is the calling SUPF, and if the terminal device is the called device, the SUPF is the called SUPF.
  • the SUPF is used as an example for the device for allocating the temporary identifier to the terminal device. Or the device performs the SUPF function shown in this embodiment.
  • the SUPF shown in this embodiment may also be called the first device, and the specific name is not limited.
  • the terminal device in the initial stage does not store the identifier of the user who uses the terminal device as an example to illustrate:
  • the terminal device shown in this embodiment has already installed the user identification card, and the terminal device with the user identification card installed does not store the identifier of the user who uses the terminal device in the initial stage.
  • the subscriber identity card may be a subscriber identity module (subscriber identity module, SIM), a global subscriber identity card (universal subscriber identity module, USIM), or a virtual smart card (embedded-SIM, eSIM) etc., specifically in this embodiment is not limited.
  • the terminal device may send the first temporary identification application including the identifier of the subscriber identity card to the SUPF.
  • This embodiment does not limit the specific type of the identifier of the user identification card, as long as the identifier of the user identification card can uniquely identify the user. Specifically, if the terminal device is the called device, the identifier of the user identification card can uniquely identify the called user. If the terminal device is the calling device, the identifier of the subscriber identity card can uniquely identify the calling user.
  • the identifier of the subscriber identity card may be an international mobile subscriber identity (IMSI), a temporary mobile subscriber identity (TMSI), or a subscription permanent identifier (SUPI) Wait.
  • IMSI international mobile subscriber identity
  • TMSI temporary mobile subscriber identity
  • SUPI subscription permanent identifier
  • Step 202 the SUPF sends a temporary identifier to the terminal device.
  • the SUPF can apply for assigning a temporary identifier to the user according to the first temporary identifier.
  • This embodiment does not limit the specific content of the temporary identification, as long as the temporary identification does not involve the user's private information, and the private information may be the user's name and/or the user's identification, etc., so that even if the temporary identification is leaked , and will not cause the disclosure of users' private information.
  • the SUPF receives the first temporary identification application from the user "lisi", the first temporary identification application includes the identifier of the user identification card, and the SUPF determines that the user is "lisi". Specifically, in the process of opening an account by the operator, the SUPF can store the correspondence between the user, the user's identifier, and the identifier of the user identification card allocated to the user.
  • the user identifier shown in this embodiment may be the user's real number or the user's email address.
  • This embodiment takes the user's identifier as the user's email address as an example for illustrative description. Continuing with the above example, for the user "lisi” , the user's ID is "lisi@bj.cmcc.com".
  • SUPF can randomly assign a series of characters to users.
  • the temporary ID is "CSqGSIb3DQEBAQUAA4GNADCBiQKBgQCjfidregls@bj.cmcc.com”.
  • any private information of the user (such as the identification of the user or the identifier of the user identification card of the user) will not be leaked, and the security of the private information of the user is effectively guaranteed.
  • SUPF also needs to establish a corresponding relationship between the user's identity and the temporary identity, and needs to ensure that SUPF allocates different temporary identities for different users, so as to ensure that the user and the allocated temporary identity have a unique corresponding relationship.
  • SUPF can assign the temporary identifier "CSqGSIb3DQEBAQUAA4GNADCBiQKBgQCjfidregls@bj.cmcc.com” to the user with the user identifier "lisi@bj.cmcc.com”.
  • SUPF can also assign a temporary identity "f6T5ALJdUSIfzTH1ecIzft5BmaxujRLyPsQrsMBfidregzs@gd.ct.com” to a user with the user's identity "zhangsan@gd.ct.com”. It can be seen that the temporary identifiers assigned by SUPF to users “lisi” and “zhangsan” are different, and neither involves the private information of users “lisi” and "zhangsan”.
  • Step 203 The terminal device sends a registration request to the UCF.
  • the UCF shown in this embodiment is the UCF to which the terminal device belongs. Continuing to refer to FIG. 1 , if the terminal device is the called device, the UCF is the called UCF, and if the terminal device is the calling device, the UCF is the main UCF. It's called UCF.
  • the terminal device can receive the call request message from the UCF to which it belongs, so as to realize the call connection.
  • the functions performed by the UCF shown in this embodiment may also be performed by any other device or device, which is not specifically limited in this embodiment.
  • the UCF shown in this embodiment may also be called the second device, and the specific name is not limited.
  • the terminal device When the terminal device receives the temporary identifier from the SUPF, the terminal device sends the registration request to the UCF, where the registration request includes the temporary identifier and the registration address of the terminal device.
  • the UCF establishes a registered address query list, and the registered address query list stores the corresponding relationship between the temporary identifier and the registered address, so as to be used in the process of subsequent calls.
  • the UCF stores the registered address query list as shown in Table 2 below shown:
  • the registration address used for calling and corresponding to the temporary identifier is an internet protocol (internet protocol, IP) address as an example.
  • IP internet protocol
  • the IP address 1 is the registered address of the user "lisi”. If the user needs to call “lisi", the UCF sends a call request message to the IP address 1.
  • the IP address 2 is the registered address of the user "zhangsan”. If the user needs to call "zhangsan", the UCF sends a call request message to the IP address 2.
  • the registered address is an IP address as an example for illustrative description, and in other examples, the registered address may also be a domain name address or any other type of address.
  • Step 204 the UCF sends a registration request to the SUPF.
  • Step 205 the SUPF sends a response message to the UCF.
  • the SUPF When the SUPF receives the registration request, it can obtain the temporary identifier included in the registration request. SUPF obtains the user's ID corresponding to the temporary ID according to the corresponding relationship shown in Table 1.
  • SUPF can query the corresponding user's identifier as "lisi@bj.cmcc.com” based on Table 1.
  • SUPF generates a random number, and SUPF encrypts the random number with a third key to generate the first parameter.
  • the third key shown in this embodiment is a symmetric-key algorithm (symmetric-key algorithm).
  • This embodiment does not limit the specific algorithm of the symmetric key encryption, for example, the algorithm of the symmetric key encryption may be data encryption standard (data encryption standard, DES), triple data encryption standard (3DES), or international data encryption standard Algorithms (international data encryption algorithm, IDEA), etc.
  • the SUPF shown in this embodiment sends a response message including the random number to the UCF.
  • Step 206 the UCF sends a response message to the terminal device.
  • the UCF sends a response message including the random number to the terminal device.
  • Step 207 The terminal device sends a re-registration message to the UCF.
  • the random number can be encrypted according to the third key stored in the terminal device to generate the second parameter.
  • the third key stored in the terminal device shown in this embodiment is the same as the third key stored in the SUPF, and the SUPF and the terminal device perform corresponding encryption and decryption operations on the random number based on the same third key.
  • the terminal device sends a re-registration message including the second parameter to the UCF.
  • Step 208 the UCF sends a re-registration message to the SUPF.
  • Step 209 SUPF judges whether the first parameter and the second parameter are equal, if yes, execute step 210, if not, execute step 212.
  • the SUPF determines whether the first parameter and the second parameter are equal.
  • step 210 is executed.
  • step 212 is executed.
  • Step 210 The SUPF sends a registration success response message to the UCF.
  • the registration success response message may be sent to the UCF, and the registration success response message is used to indicate that the terminal device is successfully registered with the SUPF.
  • step 201 it can be known that the terminal device has installed the user identification card, and the terminal device does not store the identification of the user who uses the terminal device in the initial state.
  • the registration success response message sent by the SUPF includes the encrypted identity of the user, so as to ensure that the terminal device can obtain the identity of the user.
  • the encryption method of the user's identifier by the SUPF is not limited in this embodiment.
  • the SUPF encrypts the user's identifier by using the third key shown above.
  • the terminal device decrypts the encrypted identification of the user through the third key, and the terminal device can obtain the identification of the user.
  • Step 211 the UCF sends a registration success response message to the terminal device.
  • Step 212 the SUPF sends a registration failure response message to the UCF.
  • the registration failure response message can be sent to the UCF, and the registration failure response message is used to indicate that the terminal device fails to register.
  • Step 213 The UCF sends a registration failure response message to the terminal device.
  • the terminal device After the terminal device determines that the registration fails according to the registration failure response message, it can re-register with the SUPF.
  • the process of re-registration please refer to the above steps, and the details will not be repeated.
  • the terminal device when the terminal device has installed a subscriber identity card, the terminal device sends a first temporary identification application including the identifier of the subscriber identity card to SUPF, and SUPF can A temporary identification application, assigns a temporary identification to the terminal device, and the temporary identification does not involve any user's private information.
  • the terminal device registers with the SUPF through the temporary identification to facilitate subsequent calls. It can be seen that in the process of registering a terminal device through a temporary identification, since there is no need to send the real identification of the user to SUPF, such as the real number, email address, etc. involving private information, the security of the user's private information in the registration stage is effectively guaranteed.
  • the first embodiment describes the process of how to obtain a temporary identity and how to register to SUPF when the terminal device has installed a user identification card.
  • the process of how to obtain a temporary ID and how to register with SUPF is described below in conjunction with Figure 3:
  • Step 301 The terminal device sends a second temporary identification application to the SUPF.
  • the terminal device shown in this embodiment Since the terminal device shown in this embodiment is not installed with a user identification card, the terminal device has stored the user's identification in the initial state. The terminal device can then send a second temporary identity application including the identity of the user to the SUPF.
  • first temporary identification application shown in the first embodiment and the second temporary identification application shown in the second embodiment are the same.
  • the messages included in the two temporary identification applications are different, the first temporary identification application includes the identifier of the user identification card, and the second temporary identification application includes the user identification.
  • Step 302 the SUPF sends a temporary identifier to the terminal device.
  • the SUPF shown in this embodiment can apply for obtaining the user's ID directly according to the second temporary ID, and then allocate a temporary ID according to the ID.
  • a temporary ID For the description of the specific process, please refer to the step 202 in the first embodiment. The process of allocating the temporary identifier will not be described in detail in this embodiment.
  • Step 303 The terminal device sends a registration request to the UCF.
  • Step 304 the UCF sends a registration request to the SUPF.
  • Step 305 the SUPF sends a response message to the UCF.
  • Step 306 the UCF sends a response message to the terminal device.
  • Step 307 The terminal device sends a re-registration message to the UCF.
  • Step 308 the UCF sends a re-registration message to the SUPF.
  • Step 309 SUPF judges whether the first parameter and the second parameter are equal, if yes, execute step 310, if not, execute step 312.
  • step 303 to step 309 shown in this embodiment please refer to step 203 to step 209 shown in FIG. 2 for details, and the specific execution process will not be repeated.
  • Step 310 The SUPF sends a registration success response message to the UCF.
  • the terminal device since the terminal device does not have a user identification card installed, the terminal device has stored the user's identity in the initial state. It can be seen that the difference between this embodiment and the first embodiment is that the registration success response message shown in this embodiment does not need to carry User's ID. The registration success response message shown in this embodiment is only used to indicate to the terminal device that the terminal device has successfully registered with the SUPF.
  • Step 311 The UCF sends a registration success response message to the terminal device.
  • Step 312 the SUPF sends a registration failure response message to the UCF.
  • Step 313 The UCF sends a registration failure response message to the terminal device.
  • step 311 to step 313 shown in this embodiment please refer to step 211 to step 213 shown in FIG. 2 , and the specific execution process will not be repeated.
  • the terminal device sends a second temporary identification application including the user's identification to SUPF, and SUPF can use the second temporary identification from the terminal device according to the second temporary identification.
  • the terminal device registers with the SUPF through the temporary identification to facilitate subsequent calls. It can be seen that in the process of registering a terminal device through a temporary identification, since there is no need to send the user's real identification to SUPF, such as the real number, email address, etc. involving private information, the security of the user's private information in the registration stage is effectively guaranteed.
  • the terminal device has obtained the temporary identity corresponding to the identity of the user. As shown in FIG. 4 , for the second stage shown above, that is, the calling user passes the calling temporary identity and the called The process of calling the called user by calling the temporary ID will be described.
  • the calling user "zhangsan" located in Guangdong calls the called user "lisi” located in Beijing as an example for illustration.
  • the calling SUPF to which the calling user belongs is the SUPF located in Guangdong
  • the called SUPF to which the calling user belongs is the SUPF located in Beijing.
  • Step 401 The calling device sends a key request message to the calling SUPF.
  • the function performed by the calling SUPF shown in this embodiment may also be performed by any other device or device, which is not specifically limited in this embodiment.
  • the calling device sends a key request message to the calling SUPF to which the calling device belongs.
  • the key request message shown in this embodiment further includes routing information, where the routing information is used to indicate the IP address of the called SUPF to which the called user belongs.
  • Step 402 The calling SUPF sends a key request message to the called SUPF.
  • the function performed by the called SUPF shown in this embodiment may also be performed by any other device or device, which is not specifically limited in this embodiment.
  • the called SUPF shown in this embodiment may also be called the first device, and the specific name is not limited.
  • the calling SUPF sends the key request message to the called SUPF according to the routing information included in the key request message.
  • Step 403 The called SUPF sends a key response message to the calling SUPF.
  • the called SUPF obtains the called SUPF's own public key according to the key request message, and sends a key response message including the public key to the calling SUPF.
  • the called SUPF generates a pair of public key and private key according to the elliptic curve cryptography (ECC) algorithm, the called SUPF retains the private key, and will send the public key to the calling device through a key response message .
  • ECC elliptic curve cryptography
  • Step 404 The calling SUPF sends a key response message to the calling device.
  • Step 405 The calling device sends a first call request message to the calling UCF.
  • the function performed by the calling UCF shown in this embodiment may also be performed by any other device or device, which is not specifically limited in this embodiment.
  • the first call request message includes the first encrypted calling party identification and the first encrypted called party identification.
  • the first encrypted calling ID is generated by encrypting the calling ID with a first key
  • the first encrypted called ID is generated by encrypting the called ID with the first key.
  • the calling device generates a pair of temporary public key and temporary private key according to the ECC algorithm.
  • the pair of public and private keys generated by the called SUPF according to the ECC shown in this embodiment are A1 and A2
  • the pair of temporary public and private keys generated by the calling device according to the ECC algorithm are B1 and B2.
  • the calling device uses the temporary private key B2 and the public key A1 from the called SUPF to generate the first key.
  • A1, A2, B1, and B2 shown in this embodiment satisfy the following conditions:
  • the calling device can encrypt the calling ID to generate the first encrypted calling ID, and can also use the first key to perform encryption on the called ID. encryption to generate the first encrypted called party identification.
  • the calling device generates the first encrypted calling identity "t5BmaxujRLyPsQrsMBf6T5ALJdUSIfzTH1ecIzffiderzs@gd.ct.com” after encrypting the calling identity "zhangsan@gd.ct.com” with the first key.
  • the first encrypted called ID generated after the primary device encrypts the called ID "lisi@bj.cmcc.com” with the first key is "GNADCBiQKBgQCCSqGSIb3DQEBAQUAA4jfidedls@bj.cmcc.com".
  • this embodiment does not limit the specific content of the called ID after the first encryption and the calling ID after the first encryption, as long as the calling ID after the first encryption and the called ID after the first encryption are leaked.
  • the calling identity of the calling user and the called identity of the called user will not be disclosed, so as to ensure the security of the private information of the calling user and the private information of the called user.
  • the first call request message shown in this embodiment also includes the calling temporary identity of the calling user.
  • the calling temporary identity please refer to the description of the temporary identity shown in Embodiment 1 or Embodiment 2 for details. No further description is given in this embodiment.
  • the first call request message shown in this embodiment further includes the temporary public key generated by the calling device.
  • the description of the first key shown in this embodiment is an optional example, and the first key may also be a symmetric key encryption key, so as to ensure that the first key stored by the calling device is the same as that of the called SUPF.
  • the stored first key is the same.
  • the following is an example of taking the first call request message as a session initiation protocol (session initiation protocol, SIP) message, and the following is the packet header of the SIP message:
  • SIP session initiation protocol
  • line (1) the object to be sent by the first call request message
  • the object to be sent by the first call request message is the first encrypted called ID of the called user
  • SIP/2.0 indicates that the version specified in the first call request message is SIP version 2.0.
  • Line (2) indicates routing information, which is the IP address of the called SUPF.
  • Call-ID is the call identifier, which is a unique identifier that distinguishes a group of messages in a series of messages. user), no matter how many times the first call request message is forwarded by how many devices, all the interaction information includes the call identifier Call-ID.
  • the Call-ID is generated by the calling device and is guaranteed to be globally unique in the communication system.
  • TO includes the first encrypted called ID of the called user, namely:
  • FID-reg includes the calling temporary identification of the calling user, namely:
  • pub_key_UE includes the temporary public key generated by the calling device.
  • the description of the format of the first call request message in this embodiment is an optional example, and is not limited, as long as the first call request message shown in this embodiment includes the first encrypted caller ID, the third Once encrypted, the called ID, the calling temporary ID and the temporary public key are sufficient.
  • the first call request message is a message satisfying SIP as an example for illustrative description.
  • the first call request message may also satisfy other protocols, which is not specifically limited in this embodiment.
  • Step 406 The calling UCF sends an addressing request to the calling SUPF.
  • the calling UCF In order to implement the calling user to the called user, the calling UCF needs to obtain the IP address of the called UCF to which the called user belongs.
  • the addressing request shown in this embodiment is used to request to obtain the called UCF address.
  • the address of the called UCF is taken as an example for the IP address of the called UCF.
  • the address of the called UCF may also be a domain name address or any other type of address. There is no limitation in this embodiment.
  • the addressing request includes the first encrypted calling ID, the first encrypted called ID and the temporary public key.
  • Step 407 The calling SUPF sends an addressing request to the called SUPF.
  • Step 408 The called SUPF sends an addressing response message to the calling SUPF.
  • the first encrypted called identifier when the called SUPF receives the first encrypted called identifier included in the addressing request, the first encrypted called identifier can be decrypted by using the first key to obtain the called identifier.
  • the called ID of the calling user when the called SUPF receives the first encrypted called identifier included in the addressing request, the first encrypted called identifier can be decrypted by using the first key to obtain the called identifier.
  • the called ID of the calling user when the called SUPF receives the first encrypted called identifier included in the addressing request.
  • the called SUPF queries the IP address of the called UCF corresponding to the called identity, and sends an addressing response message including the IP address of the called UCF to the calling SUPF.
  • the called SUPF generates the first key according to the private key stored by itself and the temporary public key from the calling device.
  • the process of generating the first key by SUPF shown in this embodiment please refer to the process of generating the first key by the calling device shown above, and details are not repeated, as long as the process generated by the calling device shown in this embodiment is
  • the first key may be the same as the first key generated by the called SUPF.
  • the called SUPF can decrypt the first encrypted called identity to obtain the called identity, and can also decrypt the first encrypted calling identity to obtain the calling identity.
  • the called SUPF can establish a first query list as shown in Table 3. For details, see Table 3 below:
  • step 405 for the specific description of the call identifier, please refer to step 405 for details, and details are not repeated in this embodiment.
  • the called SUPF establishes a correspondence between the calling identity and the first encrypted calling identity.
  • the called SUPF decrypts the first encrypted calling identity through the first key to obtain the calling identity, and the called SUPF can establish a correspondence between the calling identity and the calling identity.
  • the called SUPF establishes a corresponding relationship between the calling ID and the first encrypted called ID.
  • the called SUPF decrypts the first encrypted called identity through the first key to obtain the called identity, and the called SUPF can establish a corresponding relationship between the called identity and the calling identity.
  • the called device used by the called user can obtain the called temporary ID allocated by the called SUPF.
  • the called SUPF has established the called ID and the called temporary ID.
  • the corresponding relationship is shown in Table 1. It can be seen that when the called device obtains the called ID, it can obtain the corresponding temporary ID by querying the corresponding relationship shown in Table 1.
  • the called SUPF is The corresponding relationship between the calling ID and the called temporary ID can be established.
  • the addressing response message shown in this embodiment includes the IP address of the called UCF, the called ID after the first encryption, and the calling ID after the first encryption.
  • Step 409 The calling SUPF sends an addressing response message to the calling UCF.
  • the calling UCF After the calling UCF receives the addressing response message, the calling UCF can obtain the IP address of the called UCF.
  • the calling UCF can also send a service request to the calling SEF to trigger the SEF to execute the corresponding calling service
  • the calling service that triggers the SEF to execute can be restricted services and supplementary service capabilities that the calling user calls. etc., which are not specifically limited in this embodiment.
  • the calling SEF In the process of triggering the calling service, the calling SEF needs to obtain a configuration file for implementing the calling service. To this end, the calling SEF sends a service request message to the calling SUPF, where the service request message includes the calling party's temporary identity. The calling SUPF queries the calling party identity corresponding to the calling party temporary identity, as shown in Table 1 for details, and details are not repeated.
  • the calling SUPF obtains the configuration file of the calling service corresponding to the calling ID, and sends a service response including the configuration file to the calling SEF, and the calling SEF can implement the calling service according to the configuration file.
  • the calling SEF when the calling SEF obtains the configuration file of the calling service from the calling SUPF, the calling SEF sends the calling temporary identity to the calling SUPF. It can be seen that the calling SEF does not obtain the identity of the calling user, which avoids the The identity of the calling user may be leaked at the calling SEF, so that even if the calling SEF is in an unsafe state, the calling identity will not be leaked, thereby improving the security of the calling user's private information.
  • steps 401 to 409 are executed during the process of calling the calling user to the called user. In other examples, before the calling user calls the called user, the execution shown in this embodiment may be performed in advance. Step 401 to Step 409.
  • Step 410 The calling UCF sends a second call request message to the called UCF.
  • the function performed by the called UCF shown in this embodiment may also be performed by any other device or device, which is not specifically limited in this embodiment.
  • the called UCF shown in this embodiment may also be called the second device, and the specific name is not limited.
  • the calling UCF sends a second call request message to the called UCF according to the IP address of the called UCF.
  • the calling UCF constructs a second call request message according to the first call request message from the calling device, and the second call request message shown in this embodiment includes the first encrypted caller ID and the first encrypted called callee logo.
  • first call request message and the second call request message shown in this embodiment are that both the first call request message and the second call request message include the first encrypted caller ID and the first encrypted callee logo.
  • the second call request does not include the caller's temporary identity and the temporary public key included in the first call request message.
  • Step 411 The called UCF sends a first query request to the called SUPF.
  • the called UCF determines that the called identifier included in the received second call request message is an encrypted identifier
  • the called UCF sends the first query request to the called SUPF, where the first query request is A query request includes the first encrypted called party identification.
  • the first query request is used to request to obtain a called temporary identity corresponding to the first encrypted called identity.
  • Step 412 The called SUPF sends a query response to the called UCF.
  • step 408 the called SUPF has created the first query list as shown in Table 3. It can be seen that the first query list has created the corresponding relationship between the called temporary ID and the first encrypted called ID. For a specific description of the first query list, please refer to step 408 for details, and details are not repeated.
  • the called temporary identity corresponding to the first encrypted called identity can be determined according to the first query list.
  • the called SUPF sends a query response including the called temporary identity to the called UCF.
  • Step 413 The called UCF sends a third call request message to the called device.
  • step 203 shown in the first embodiment that in the stage of the called device registration, the called UCF has created a registration address query list as shown in Table 2. Please refer to the specific description of the registration address query list. As shown in step 203, details are not repeated in this embodiment.
  • the called UCF when the called UCF receives the called temporary ID included in the query response, the called UCF can determine the registration address corresponding to the called temporary ID by querying the registration address query list shown in Table 2. , the called UCF can send a third call request message to the registered address.
  • the called temporary ID of the called user "lisi” is "CSqGSIb3DQEBAQUAA4GNADCBiQKBgQCjfidregls@bj.cmcc.com”
  • the called UCF determines from Table 2 that the registered address corresponding to the called temporary ID is IP address 1, then the called UCF
  • the third call request message can be sent to IP address 1.
  • the third call request message shown in this embodiment includes the called temporary identity.
  • the called device When the called device receives the third call request from the called UCF, it can realize the connection to the called device.
  • the process of calling the user's identity is exemplified.
  • This embodiment takes steps 414 to 415 shown below as an example to realize the display of the caller's identity by the called device. It should be clear that steps 414 to 415 shown in this embodiment are possible The steps to be performed are optional, and in other examples, the called device may not need to display the caller identification.
  • Step 414 The called device sends an identity query request to the called SUPF.
  • the third call request message sent by the called UCF to the called device further includes the first encrypted calling identity.
  • the called device For the called device to display the calling user's calling identity, the called device sends an identity query request to the called SUPF, where the identity query request includes the first encrypted calling identity.
  • Step 415 The called SUPF sends the calling ID to the called device.
  • the called SUPF When the called SUPF obtains the first encrypted caller ID included in the first query request, it can query the first encrypted caller ID according to the first query list shown in Table 3. Corresponding caller ID.
  • the called device sends the first encrypted calling identity to the called SUPF to request to obtain the calling identity as an example.
  • the called device may also directly send to the called SUPF.
  • the called temporary ID The query stored by the called SUPF is shown in Table 3. Both the called temporary ID and the calling ID correspond to the calling ID. It can be seen that the called SUPF can query the calling party corresponding to the called temporary ID through the called temporary ID. logo.
  • the called device When the called device receives the caller ID, it can display the caller ID during the ringing process.
  • a secure connection can be established between the called SUPF and the called device, and the called SUPF can send the calling ID to the called device based on the secure connection, thereby effectively improving the efficiency of the called SUPF to the called device.
  • Security of the caller ID sent by the device can be established between the called SUPF and the called device, and the called SUPF can send the calling ID to the called device based on the secure connection, thereby effectively improving the efficiency of the called SUPF to the called device.
  • the called SUPF sends the calling ID to the called device in plain text
  • the calling ID and the called ID involving privacy information are sent in cipher text.
  • the method shown in this embodiment does not require between the calling device and the calling SUPF, between the calling device and the calling UCF, between the calling UCF and the called UCF, between the called SUPF and the called UCF, Establishing a secure connection between the called UCF and the called device can effectively avoid the leakage of the calling ID and the called ID, thereby reducing the complexity of interaction between devices and improving call efficiency.
  • the intermediate device is the calling SUPF
  • the calling The UCF and the called UCF avoid the risk of leakage caused by the intermediate device decrypting the calling ID after the first encryption and the called ID after the first encryption, and improve the calling process, the calling ID and the called ID. security.
  • the intermediate device does not need a decryption process, the call efficiency is improved.
  • the calling and called identities obtained by the calling UCF and the called UCF shown in this embodiment are encrypted, which avoids the possibility of the calling and called identities being leaked at the calling UCF and the called UCF. It can be seen that even if the calling UCF and the called UCF are in an unsafe state, the calling ID and the called ID will not be leaked.
  • the called device needs to display the calling ID
  • the called device needs to send an ID query request to the called SUPF alone.
  • the called SUPF can send an ID query request to realize the implementation.
  • Step 501 The calling device requests a message from the calling SUPF key.
  • Step 502 The calling SUPF sends a key request message to the called SUPF.
  • Step 503 The called SUPF sends a key response message to the calling SUPF.
  • Step 504 The calling SUPF sends a key response message to the calling device.
  • Step 505 The calling device sends a first call request message to the calling UCF.
  • Step 506 The calling UCF sends an addressing request to the calling SUPF.
  • Step 507 The calling SUPF sends an addressing request to the called SUPF.
  • step 501 to step 507 shown in this embodiment please refer to step 401 to step 407 in Embodiment 3 for details, and the specific execution process will not be repeated in this embodiment.
  • Step 508 The called SUPF sends an addressing response message to the calling SUPF.
  • the called SUPF when the called SUPF receives the first encrypted calling ID and the first encrypted called ID included in the addressing request, the first encrypted called ID is processed by the first key.
  • Decryption to obtain the called ID of the called user and can also decrypt the first encrypted calling ID through the first key to obtain the calling ID of the calling user, and the called SUPF obtains the first key
  • step 408 in Embodiment 3 for details, and details are not repeated in this embodiment.
  • the called SUPF queries the IP address of the called UCF corresponding to the called identity, and sends an addressing response message including the IP address of the called UCF to the calling SUPF.
  • the called SUPF can establish a second query list as shown in Table 4. For details, see Table 4 below:
  • the called SUPF shown in this embodiment encrypts the called identity by using the second key to generate the second encrypted called identity, and the called SUPF also establishes the second encrypted called identity through the second query list shown in Table 4. The correspondence between the called ID and the calling ID.
  • the second key is the same as the second key stored by the called device.
  • This embodiment does not limit the process for the called SUPF to obtain the second key.
  • the called SUPF can receive the second key from the called device.
  • the second key shown in this embodiment may be a symmetric key encryption key.
  • the symmetric key encryption key please refer to Embodiment 1, which will not be repeated in this embodiment.
  • the called SUPF shown in this embodiment encrypts the calling identity by using the second key to generate the second encrypted calling identity, and the called SUPF also establishes the second encryption through the second query list shown in Table 4. The corresponding relationship between the called ID and the calling ID.
  • the addressing response message shown in this embodiment includes the IP address of the called UCF, the called ID after the second encryption, and the calling ID after the second encryption.
  • Step 509 The calling SUPF sends an addressing response message to the calling UCF.
  • step 509 shown in this embodiment please refer to step 409 shown in Embodiment 3 for details, and details are not repeated in this embodiment.
  • Step 510 The calling UCF sends a fourth call request message to the called UCF.
  • the calling UCF sends a fourth call request message to the called UCF according to the IP address of the called UCF.
  • the fourth call request message shown in this embodiment includes the second encrypted calling party identification and the second encrypted called party identification.
  • Step 511 The called UCF sends a second query request to the called SUPF.
  • the called UCF determines that the called identifier included in the received fourth call request message is an encrypted identifier
  • the called UCF sends the second query request to the called SUPF, wherein the fourth call request message is an encrypted identifier.
  • the second query request includes the second encrypted called party identifier.
  • the second query request is used to request to obtain a called temporary identity corresponding to the second encrypted called identity.
  • Step 512 The called SUPF sends a query response to the called UCF.
  • step 508 it can be seen that the called SUPF has created the second query list as shown in Table 4. It can be known that the second query list has created the corresponding relationship between the called temporary ID and the second encrypted called ID, and the second query list has created a corresponding relationship between the called temporary ID and the second encrypted called ID. For a specific description of the second query list, please refer to step 508 for details, and details are not repeated.
  • the called temporary ID corresponding to the second encrypted called ID can be determined according to the second query list.
  • the called SUPF sends a query response including the second encrypted called identifier to the called UCF.
  • Step 513 The called UCF sends a fifth call request message to the called device.
  • step 203 shown in the first embodiment that in the stage of the called device registration, the called UCF has created a registration address query list as shown in Table 2. Please refer to the specific description of the registration address query list. As shown in step 203, details are not repeated in this embodiment.
  • the called UCF when the called UCF receives the called temporary ID included in the query response, the called UCF can determine the registration address corresponding to the called temporary ID by querying the registration address query list shown in Table 2. , the called UCF can send the fifth call request message to the registered address.
  • the third call request message shown in this embodiment includes the called temporary ID and the second encrypted calling ID.
  • Step 514 The called device receives the fifth call request message.
  • the connection to the called device can be realized.
  • the called SUPF shown in this embodiment is the same as the second key stored by the called device. It can be known that when the called device receives the second encrypted calling ID, it can pass the encryption key. The second key decrypts the second encrypted caller ID to obtain the caller ID.
  • the called device After the called device successfully obtains the decrypted caller ID, the called device can display the caller ID.
  • the called device shown in this embodiment can obtain the calling party's identity according to the fifth call request message without sending an identity query request to the called SUPF separately, thereby improving call efficiency.
  • the calling ID sent by the called SUPF to the called device shown in this embodiment is also encrypted, which improves the security of the calling ID and avoids the possibility of leakage of the calling ID sent by the called SUPF to the called device. .
  • This embodiment describes the structure of the network device that executes the above call processing method with reference to FIG. 6 :
  • the network device 600 specifically includes: a processing unit 601 and a transceiver unit 602 , wherein the processing unit 601 is connected to the transceiver unit 602 .
  • the processing unit 601 is configured to perform the processing function performed by the UCF in either the first embodiment or the second embodiment.
  • the transceiving unit 602 is configured to perform the transceiving function performed by the UCF in either the first embodiment or the second embodiment.
  • the processing unit 601 is configured to execute the processing functions performed by the calling UCF in any of the third to fifth embodiments.
  • the transceiving unit 602 is configured to perform the transceiving function performed by the calling UCF in any of Embodiments 3 to 5.
  • the processing unit 601 is configured to execute the processing functions performed by the called UCF in any of the third to fifth embodiments.
  • the transceiver unit 602 is configured to perform the transceiver function performed by the called UCF in any one of the third embodiment to the fifth embodiment.
  • the processing unit 601 is configured to perform the processing function performed by the SUPF in either the first embodiment or the second embodiment.
  • the transceiving unit 602 is configured to perform the transceiving function performed by the SUPF in either Embodiment 1 or Embodiment 2.
  • the processing unit 601 is configured to execute the processing functions performed by the calling SUPF in any of the third to fifth embodiments.
  • the transceiving unit 602 is configured to perform the transceiving function performed by the calling SUPF in any one of Embodiments 3 to 5.
  • the processing unit 601 is configured to execute the processing function performed by the called SUPF in any of the third to fifth embodiments.
  • the transceiver unit 602 is configured to perform the transceiver function performed by the called SUPF in any one of Embodiments 3 to 5.
  • the processing unit 601 is configured to execute the processing function performed by the terminal device in any of the first embodiment or the second embodiment.
  • the transceiver unit 602 is configured to perform the transceiver function performed by the terminal device in any of the first embodiment or the second embodiment.
  • the processing unit 601 is configured to execute the processing functions performed by the calling device in any of the third to fifth embodiments.
  • the transceiving unit 602 is configured to perform the transceiving function performed by the calling device in any of Embodiments 3 to 5.
  • the processing unit 601 is configured to execute the processing function performed by the called device in any of the third to fifth embodiments.
  • the transceiving unit 602 is configured to perform the transceiving function performed by the called device in any of Embodiments 3 to 5.
  • the network device specifically includes: a processor 701 , a memory 702 , a bus 703 , a transceiver 704 and a network interface 706 .
  • memory 702 may include computer storage media in the form of volatile and/or non-volatile memory, such as read-only memory and/or random access memory.
  • Memory 702 may store operating systems, application programs, other program modules, executable code, and program data.
  • the transceiver 704 can be used to input commands and information to the network device, and the transceiver 704 can be connected to the processor 701 through the bus 703 . Transceiver 704 may also be used to output information from network devices, such as selected placeholder servers and/or placeholder virtual machines.
  • the network device may be connected to the communication network through the network interface 706.
  • the computer-executed instructions stored in the network device may be stored in a remote storage device, rather than being limited to local storage.
  • the network device executes the executable code or application program stored in the memory 702, the network device can perform the method operations of any one of the above method embodiments.
  • the specific execution process refer to the above method embodiments, and here No longer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种呼叫处理方法、相关设备以及存储介质，以保证用户隐私信息的安全。该方法包括第一设备接收加密后被叫标识，所述加密后被叫标识为对被叫标识进行加密以生成，所述被叫标识为被叫用户的标识；所述第一设备获取与所述加密后被叫标识对应的被叫临时标识，所述被叫临时标识为临时为所述被叫用户所分配的标识；所述第一设备向第二设备发送所述被叫临时标识，所述第二设备用于根据所述被叫临时标识呼叫所述被叫用户所使用的被叫设备。

Description

一种呼叫处理方法、相关设备以及存储介质 技术领域
本申请涉及通信技术领域，尤其涉及一种呼叫处理方法、相关设备以及存储介质。
背景技术
随着物联网设备的普及和各行业通信诉求的不断发展，要求运营商的音视频通信网络，为千行百业提供全程全网、随时任意可达、稳定可靠、低成本的音视频业务。
实现主叫用户对被叫用户呼叫的过程中，主叫用户需要向音视频通信网络发送主叫用户的主叫号码和被叫用户的被叫号码。但是，主叫用户基于音视频通信网络呼叫被叫用户的过程中，主叫号码和被叫号码容易泄露，从而造成用户隐私信息的泄露。
发明内容
本发明实施例提供了一种呼叫处理方法、相关设备以及存储介质，其用于避免主叫用户呼叫被叫用户的过程中，用户的隐私信息出现泄露的情况。
第一方面，本发明实施例提供了一种呼叫处理的方法，该方法包括：第一设备接收加密后被叫标识，该加密后被叫标识为对被叫标识进行加密以生成，该被叫标识为被叫用户的标识；该第一设备获取与该加密后被叫标识对应的被叫临时标识，该被叫临时标识为临时为该被叫用户所分配的标识；该第一设备向第二设备发送该被叫临时标识，该第二设备用于根据该被叫临时标识呼叫该被叫用户所使用的被叫设备。
可见，在主叫用户呼叫被叫用户的过程中，第一设备接收到经过加密的加密后被叫标识，避免了被叫标识出现泄露的可能。而且在主叫用户呼叫被叫用户的过程中，无需各设备对加密后被叫标识进行解密，避免了各设备因对加密后被叫标识进行解密所带来的，涉及被叫用户隐私信息的被叫标识泄露的风险，提高了呼叫过程中被叫标识的安全。而且因呼叫过程中，各设备无需对加密后被叫标识进行解密的过程，提高了呼叫的效率。
结合第一方面，一种可选地实现方式中，该第一设备获取与该加密后被叫标识对应的被叫临时标识之前，该方法还包括：该第一设备获取与该被叫标识对应的该被叫临时标识；该第一设备建立该加密后被叫标识和该被叫临时标识的对应关系。
该被叫临时标识不涉及被叫用户的隐私信息，例如，该临时标识信息为与被叫用户对应的一系列随机的字符。可见，若该被叫临时标识出现泄露，因该被叫临时标识不涉及被叫用户的隐私信息，则能有效地避免被叫用户的隐私信息出现泄露的情况。
在该第一设备建立该加密后被叫标识和该被叫临时标识的对应关系的情况下，在主叫用户呼叫被叫用户的过程中，第一设备接收到加密后被叫标识后，无需对加密后被叫标识进行解密即可获取到对应的被叫临时标识，基于该被叫临时标识即可实现对被叫用户的呼叫。
基于第一方面，一种可选地实现方式中，该第一设备获取与该被叫标识对应的该被叫临时标识之前，该方法还包括：该第一设备接收来自主叫设备的该加密后被叫标识，该加密后被叫标识为该被叫标识通过第一密钥进行加密以生成，该主叫设备为主叫用户所使用 的设备；该第一设备通过该第一密钥对该加密后被叫标识进行解密以获取该被叫标识。
基于第一方面，一种可选地实现方式中，该第一设备通过该第一密钥对该加密后被叫标识进行解密以获取该被叫标识之前，该方法还包括：该第一设备通过椭圆曲线密码编码学ECC算法对私钥和来自该主叫设备的临时公钥进行计算以获取该第一密钥。
该第一设备通过第一密钥对加密后被叫标识进行解密即可获取到被叫标识，以便于建立加密后被叫标识和被叫临时标识的对应关系，提高了主叫设备向第一设备所传输的被叫标识的安全。
基于第一方面，一种可选地实现方式中，该第一设备向第二设备发送该被叫临时标识之前，该方法还包括：该第一设备接收来自该主叫设备的第一加密后主叫标识，该第一加密后主叫标识为主叫标识通过该第一密钥进行加密以生成，该主叫标识为该主叫用户的标识；该第一设备通过该第一密钥对该第一加密后主叫标识进行解密以获取该主叫标识；该第一设备建立该加密后被叫标识和该主叫标识的对应关系。
基于第一方面，一种可选地实现方式中，该第一设备向第二设备发送该被叫临时标识之后，该方法还包括：该第一设备接收来自该被叫设备的标识查询请求，该标识查询请求包括该加密后主叫标识；该第一设备获取与该加密后主叫标识对应的该主叫标识；该第一设备向该被叫设备发送该主叫标识。
可见，在该第一设备建立该加密后被叫标识和该主叫标识的对应关系的情况下，第一设备在呼叫被叫用户的过程中，能够根据标识查询请求向被叫设备发送主叫标识，被叫设备即可在振铃的过程中，显示该主叫标识。
基于第一方面，一种可选地实现方式中，该第一设备获取与该被叫标识对应的该被叫临时标识之前，该方法还包括：该第一设备通过第二密钥对该被叫标识进行加密以生成该加密后被叫标识；该第一设备向主叫设备发送该加密后被叫标识。
基于第一方面，一种可选地实现方式中，该第一设备向第二设备发送该被叫临时标识之前，该方法还包括：该第一设备接收来自该主叫设备的第一加密后主叫标识，该第一加密后主叫标识为主叫标识通过第一密钥进行加密以生成，该主叫标识为主叫用户的标识；该第一设备通过该第一密钥对该第一加密后主叫标识进行解密以获取该主叫标识；该第一设备通过该第二密钥，对该主叫标识进行加密以生成第二加密后主叫标识；该第一设备向该被叫设备发送该第二加密后主叫标识。
可见，被叫设备无需单独向第一设备发送标识查询请求，即可获取主叫标识，提高了呼叫效率。而且第一设备向被叫设备所发送的主叫标识经过加密，提高了主叫标识的安全。
基于第一方面，一种可选地实现方式中，该第一设备接收加密后被叫标识之前，该方法还包括：该第一设备接收来自该被叫设备的第一临时标识申请，该第一临时标识申请包括该被叫设备的用户识别卡的标识符；该第一设备根据该第一临时标识申请为该被叫用户分配该被叫临时标识；该第一设备建立该被叫标识和该被叫临时标识的对应关系；该第一设备向该被叫设备发送该被叫临时标识以及加密后的该被叫标识。
可见，在被叫设备包括用户识别卡的情况下，被叫设备即可向第一设备发送包括该用户识别卡的标识符的第一临时标识申请，第一设备根据该第一临时标识申请为被叫设备分 配被叫临时标识，该被叫临时标识不涉及被叫用户的隐私信息，从而保证了被叫用户的隐私信息的安全。
基于第一方面，一种可选地实现方式中，该第一设备接收加密后被叫标识之前，该方法还包括：该第一设备接收来自该被叫设备的第二临时标识申请，该第二临时标识申请包括该被叫标识；该第一设备根据该第二临时标识申请为该被叫用户分配该被叫临时标识；该第一设备建立该被叫标识和该被叫临时标识的对应关系；该第一设备向该被叫设备发送该被叫临时标识。
可见，在被叫设备未安装用户识别卡的情况下，被叫设备向第一设备发送包括该用户的标识的第二临时标识申请，第一设备能够根据来自被叫设备的第二临时标识申请，为被叫设备分配被叫临时标识，该被叫临时标识不涉及被叫用户的隐私信息，从而保证了被叫用户的隐私信息的安全。
基于第一方面，一种可选地实现方式中，该第一设备向该被叫设备发送该被叫临时标识之后，该方法还包括：该第一设备接收来自该被叫设备的注册请求，该注册请求包括该被叫临时标识；该第一设备向该被叫设备发送随机数；该第一设备通过第三密钥对该随机数进行加密以生成第一参数；该第一设备接收来自该被叫设备的第二参数，该第二参数为该被叫设备通过该第三密钥对该随机数进行加密以生成的参数；若该第一设备确定该第一参数和该第二参数相等，则该第一设备向该被叫设备发送注册响应消息，该注册响应消息用于指示该被叫设备注册成功。
可见，在被叫用户注册至第一设备的过程中，被叫用户无需向第一设备发送包含被叫用户隐私信息的注册请求，本方面所示的注册请求包括不涉及被叫用户隐私信息的被叫临时标识，从而在被叫用户注册至第一设备的过程中，有效地保证了被叫用户的隐私信息的安全。
第二方面，本发明实施例提供了一种呼叫处理的方法，该方法包括：主叫设备获取待呼叫的被叫用户对应的被叫标识；该主叫设备对该被叫标识进行加密以获取加密后被叫标识；该主叫设备向第二设备发送呼叫请求消息，该呼叫请求消息包括该加密后被叫标识。
本方面所示的有益效果的说明，请详见第一方面所示，具体在本方面中不做赘述。
基于第二方面，一种可选地实现方式中，该主叫设备对该被叫标识进行加密以获取加密后被叫标识包括：该主叫设备通过第一密钥对该被叫标识进行加密以获取加密后被叫标识。
基于第二方面，一种可选地实现方式中，该主叫设备向第二设备发送呼叫请求消息之前，该方法还包括：该主叫设备通过第一密钥对主叫标识进行加密以获取加密后主叫标识，该主叫标识为主叫用户的标识，其中，该呼叫请求消息包括该加密后主叫标识。
基于第二方面，一种可选地实现方式中，该方法还包括：该主叫设备通过椭圆曲线密码编码学ECC算法对临时私钥和来自第一设备的公钥进行计算以获取该第一密钥。
第三方面，本发明实施例提供了一种呼叫处理的方法，该方法包括：第二设备接收来自第一设备的被叫临时标识，该被叫临时标识为临时为被叫用户所分配的标识；该第二设备向被叫设备发送呼叫请求消息，该呼叫请求消息包括该被叫临时标识，该被叫设备为被 叫用户所使用的设备。
可见，在主叫用户呼叫被叫用户的过程中，第二设备根据被叫临时标识实现对被叫用户的呼叫，该被叫临时标识不涉及被叫用户的隐私信息，有效地避免了被叫用户的隐私信息的泄露。而且第二设备无需解密，直接根据该被叫临时标识对被叫用户进行呼叫，提高了呼叫被叫用户的效率。因第二设备不会获取到涉及被叫用户隐私信息的被叫标识，有效地避免了被叫用户的隐私信息在第二设备处的泄露，提高了被叫用户的隐私信息的安全。
基于第三方面，一种可选地实现方式中，该第二设备接收来自第一设备的被叫临时标识之前，该方法还包括：该第二设备接收来自主叫设备的呼叫请求消息，该呼叫请求消息包括加密后被叫标识，该加密后被叫标识为对被叫标识进行加密以生成，该被叫标识为该被叫用户的标识；该第二设备向该第一设备发送查询请求，该查询请求包括该加密后被叫标识，该查询请求用于请求获取与该加密后被叫标识对应的该被叫临时标识。
基于第三方面，一种可选地实现方式中，该第二设备向被叫设备发送呼叫请求消息包括：该第二设备根据该被叫临时标识对应的该被叫设备的注册地址，向该被叫设备发送该呼叫请求消息。
第四方面，本发明实施例提供了一种第一设备，包括分别与处理器耦合的存储器和收发器，该存储器中存储了计算机程序代码，该处理器调用并执行该存储器中的计算机程序代码，使得该处理器执行如上述第一方面任一项与处理相关的步骤，该收发器用于执行如上述第一方面任一项与收发相关的步骤。
第五方面，本发明实施例提供了一种主叫设备，包括分别与处理器耦合的存储器和收发器，该存储器中存储了计算机程序代码，该处理器调用并执行该存储器中的计算机程序代码，使得该处理器执行如上述第二方面任一项与处理相关的步骤，该收发器用于执行如上述第二方面任一项与收发相关的步骤。
第六方面，本发明实施例提供了一种第二设备，包括分别与处理器耦合的存储器和收发器，该存储器中存储了计算机程序代码，该处理器调用并执行该存储器中的计算机程序代码，使得该处理器执行如上述第三方面任一项与处理相关的步骤，该收发器用于执行如上述第三方面任一项与收发相关的步骤。
第七方面，本发明实施例提供了一种通信系统，包括主叫设备、第一设备、第二设备以及被叫设备，该主叫设备用于经由该第一设备以及该第二设备呼叫该被叫设备，该主叫设备如上述第五方面所示，该第一设备如上述第四方面所示，该第二设备如上述第六方面所示。
第八方面，本发明实施例提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，该计算机程序被处理器执行时能够完成上述第一方面至第三方面任意一项该的方法。
附图说明
图1为本申请所提供的通信系统的一种实施例结构示例图；
图2为本申请所提供的呼叫处理方法的第一种实施例步骤流程图；
图3为本申请所提供的呼叫处理方法的第二种实施例步骤流程图；
图4为本申请所提供的呼叫处理方法的第三种实施例步骤流程图；
图5为本申请所提供的呼叫处理方法的第四种实施例步骤流程图；
图6为本申请所提供的网络设备的一种实施例结构示例图；
图7为本申请所提供的网络设备的另一种实施例结构示例图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本申请中出现的术语“和/或”，可以是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。
本申请提供了一种呼叫处理方法，为更好的理解本申请所提供的呼叫处理方法，以下首先结合图1所示对本申请所示的方法所应用的通信系统的结构进行说明：需明确的是，本申请对该通信系统的具体网络架构不做限定，只要主叫用户基于该通信系统能够实现对被叫用户的呼叫，而且呼叫的过程中，能够有效地保证主叫用户的隐私信息和被叫用户的隐私信息的安全即可。
以下对本实施例所示的通信系统100的架构进行介绍。
本实施例所示的通信系统100包括主叫用户所使用的主叫设备，本实施例所示的主叫设备可为智能终端、计算机等任意能够实现呼叫被叫用户的设备。
本实施例所示的主叫设备110能够基于该通信系统100呼叫被叫用户所使用的被叫设备120，对被叫设备120的说明，请参见主叫设备110的说明，具体不做赘述。
其中，主叫设备110和被叫设备120均与运输控制功能(transport control function，TCF)130连接。主叫统一控制功能(unified control function，UCF)111分别与主叫设备110、TCF130、被叫UCF121、主叫服务启用功能(service enabler function，SEF)112以及主叫服务用户配置文件功能(service user profile function，SUPF)113连接。被叫UCF121分别与被叫设备120、TCF130、主叫UCF111、被叫SEF122以及被叫SUPF123连接。
主叫SEF112分别与主叫UCF111、主叫服务和应用功能(service and application function，SAF)114以及主叫SUPF113连接。被叫SEF122分别与被叫UCF121、被叫SAF124以及被叫SUPF123连接。主叫SUPF113还与被叫SUPF123连接。
主叫引导服务器功能(bootstrapping server function，BSF)115分别与主叫SUPF113、 主叫UCF111以及主叫设备110连接，被叫BSF215分别与被叫SUPF123、被叫UCF121以及被叫设备120连接。
具体地，主叫SUPF113和被叫SUPF123之间可通过超文本传输安全协议(hypertext transfer protocol over secure socket layer，HTTPS)进行交互。主叫SEF112和主叫UCF111之间，主叫UCF111和主叫设备110之间，主叫UCF111和被叫UCF121，主叫UCF111和被叫UCF121之间，被叫SEF122和被叫UCF121之间，以及被叫UCF121和被叫设备120之间，均可通过会话初始协议(session initiation protocol，SIP)进行交互。主叫SEF112和主叫SUPF113之间以及被叫SUPF123和被叫SEF之间，均可通过N71接口进行交互。主叫UCF111和主叫SUPF113之间，以及被叫SUPF123和被叫UCF121之间均可通过N70接口进行交互。主叫BSF115和主叫设备110之间，被叫BSF215和被叫设备120之间，可通过HTTPS进行交互。
其中，主叫UCF111用于执行的功能可包括：处理主叫用户通过主叫设备110注册至通信系统的过程以及对主叫用户执行身份验证和授权的功能。与主叫SUPF113交互以存储、更新、删除和查询主叫用户的配置文件，其中，主叫用户配置文件可以用于注册、身份验证和授权过程。对来自主叫设备110的信令消息进行处理，并根据不同的策略确定相应的信令路由。根据从主叫SUPF113获取的用户配置文件进行对应服务的触发。通过与TCF130的交互控制媒体平面的流量优化。与主叫SEF112交互，以保证服务和应用的提供。对被叫UCF121的功能的说明，请参见主叫UCF111功能的说明，具体不做赘述。
随着基于服务的技术的引入，主叫SEF112不仅将履行服务相关的支持功能，还可履行在应用层完成对主叫用户的注册、认证、授权等功能，负责服务和应用的管理。对被叫SEF122的功能的说明，请参见主叫SEF112的说明，具体不做赘述。
主叫SUPF113用于提供主叫用户档案的维护和管理功能，主要包括根据主叫UCF111的要求对主叫用户相关数据进行存储、更新、删除和查询。例如，建立主叫用户标识(ID)和主叫用户配置文件的对应关系。主叫SUPF113即可根据主叫用户ID实现对主叫用户配置文件的查询，其中，主叫用户配置文件可由运营商或主叫用户提供。
为更好的理解图1所示的通信系统，以下对已有方案进行呼叫的过程进行示例性说明：
主叫用户为向被叫用户进行呼叫，则主叫用户通过主叫设备向主叫UCF发送呼叫请求消息，该呼叫请求消息包括主叫标识(如主叫用户的真实号码)以及被叫标识(如被叫用户的真实号码)。主叫UCF向主叫SUPF发送寻址请求，该寻址请求用于请求获取被叫设备所属的被叫UCF的地址。主叫SUPF向主叫UCF返回被叫UCF的地址。主叫UCF即可根据该被叫UCF的地址，向被叫UCF发送呼叫请求消息，被叫UCF将该呼叫请求消息转发给被叫设备，以实现对被叫设备的呼叫。
可见，已有方案所示的呼叫的过程，呼叫请求消息包括涉及主叫用户隐私信息的主叫标识以及涉及被叫用户隐私信息的被叫标识，且呼叫请求消息所包括的主叫标识以及被叫标识均为明文发送。呼叫请求消息在传输的过程中会存在很大的安全风险，呼叫请求消息所包括的主叫标识以及被叫标识容易被恶意窥探，从而泄露了主叫用户以及被叫用户的隐 私信息。
为保证主叫用户与被叫用户之间通信的安全，已有的方案还可基于数字证书在设备之间建立安全连接，例如，在设备之间建立安全传输层协议(transport layer security，TLS)安全连接。虽然安全连接保证了设备之间所传输的呼叫请求消息的传输安全，但是，建立安全连接的过程较为复杂，大大延迟了主叫用户呼叫被叫用户的效率。
基于已有方案呼叫过程的缺陷，本申请所提供的呼叫处理方法，能够有效地避免涉及隐私信息的主叫标识和被叫标识泄露的情况，还能够避免在不同的设备之间建立复杂的安全连接，提高主叫用户呼叫被叫用户的效率。
为更好的理解本申请所提供的呼叫处理方法，首先对本申请所示的呼叫处理方法进行概述性说明：
本申请所示的呼叫处理方法，涉及两个阶段，阶段一，主叫用户的主叫临时标识和被叫用户的被叫临时标识的分配过程，主叫用户基于该主叫临时标识进行注册，被叫用户基于该被叫临时标识进行注册。其中，该主叫临时标识不涉及主叫用户的隐私信息，被叫临时标识不涉及被叫用户的隐私信息。阶段二，主叫用户通过主叫临时标识以及被叫临时标识呼叫被叫用户的过程。
以下通过各个实施例，对本申请所提供的呼叫处理方法的具体执行过程进行示例性说明：
实施例一
以下首先结合图2所示的实施例一，对上述所示的阶段一进行说明。通过图2所示的实施例一，针对不同的用户，能够获取不同的临时标识，并基于该临时标识进行注册，以下对具体过程进行说明：
步骤201、终端设备向SUPF发送第一临时标识申请。
本实施例所示的终端设备可为图1所示的主叫设备或被叫设备，具体在本实施例中不做限定。即主叫用户通过本实施例所示的方法能够获取到主叫临时标识，被叫用户通过本实施例所示的方法能够获取到被叫临时标识。
本实施例所示的SUPF为该终端设备所属的SUPF，例如，若终端设备为主叫设备，则该SUPF为主叫SUPF，若终端设备为被叫设备，则该SUPF为被叫SUPF。
本实施例以用于为终端设备分配临时标识的设备为SUPF为例进行示例性说明，在其他示例中，SUPF和BSF可共同为终端设备分配临时标识，或者在其他示例中，可由其他任意设备或设备执行本实施例所示的SUPF的功能。本实施例所示的SUPF还可称之为第一设备，对具体的名称不做限定。
本实施例所示以终端设备在初始阶段，未存储使用该终端设备的用户的标识为例进行说明：
例如，本实施例所示的终端设备已安装用户识别卡，已安装用户识别卡的终端设备在初始阶段，未存储使用该终端设备的用户的标识。
其中，该用户识别卡可为用户身份识别模块(subscriber identity module，SIM)、 全球用户识别卡(universal subscriber identity module，USIM)、或虚拟智能卡(embedded-SIM，eSIM)等，具体在本实施例中不做限定。
在终端设备包括用户识别卡的情况下，终端设备即可向SUPF发送包括该用户识别卡的标识符的第一临时标识申请。
本实施例对该用户识别卡的标识符的具体类型不做限定，只要该用户识别卡的标识符能够唯一的标识用户即可。具体地，若终端设备为被叫设备，则该用户识别卡的标识符能够唯一的标识被叫用户。若终端设备为主叫设备，则该用户识别卡的标识符能够唯一的标识主叫用户。
例如，该用户识别卡的标识符可为国际移动用户识别码(international mobile subscriber identity，IMSI)、临时移动用户标识(temporary mobile subscriber identity，TMSI)、或用户永久性标识(subscription permanent identifier，SUPI)等。
步骤202、SUPF向终端设备发送临时标识。
本实施例中，SUPF能够根据第一临时标识申请为用户分配临时标识。
本实施例对临时标识的具体内容不做限定，只要该临时标识不涉及用户的隐私信息即可，该隐私信息可为用户的姓名、和/或用户的标识等，从而使得即便临时标识出现泄露，也不会造成用户的隐私信息的泄露。
例如，SUPF接收到来自用户“lisi”的该第一临时标识申请，该第一临时标识申请包括该用户识别卡的标识符，SUPF确定用户为“lisi”。具体地，用户在运营商开户的过程中，该SUPF即可存储用户、用户的标识以及为用户分配的用户识别卡的标识符之间的对应关系。
本实施例所示的用户的标识可为用户的真实号码或用户的邮箱地址，本实施例以用户的标识为用户的邮箱地址为例进行示例性说明，继续如上述示例，针对用户“lisi”，该用户的标识为“lisi@bj.cmcc.com”。
本实施例对SUPF具体分配临时标识的方式不做限定，例如，SUPF可随机为用户分配一系列的字符，如SUPF为具有用户的标识“lisi@bj.cmcc.com”的用户，所分配的临时标识为“CSqGSIb3DQEBAQUAA4GNADCBiQKBgQCjfidregls@bj.cmcc.com”。
可见，若该临时标识出现泄露，不会造成用户的任何隐私信息(如用户的标识或用户的用户识别卡的标识符)的泄露，有效地保证了用户的隐私信息的安全。
SUPF还需要建立用户的标识与临时标识的对应关系，而且需要保证SUPF针对不同的用户分配不同的临时标识，从而确保用户与所分配的临时标识具有唯一的对应关系。
本实施例所示的SUPF所建立的对应关系可参见如下所示的表1所示：
表1
用户的标识 临时标识
lisi@bj.cmcc.com CSqGSIb3DQEBAQUAA4GNADCBiQKBgQCjfidregls@bj.cmcc.com
zhangsan@gd.ct.com f6T5ALJdUSIfzTH1ecIzft5BmaxujRLyPsQrsMBfidregzs@gd.ct.com
如表1所示可知，SUPF能够针对具有用户的标识“lisi@bj.cmcc.com”的用户，分配临时标识“CSqGSIb3DQEBAQUAA4GNADCBiQKBgQCjfidregls@bj.cmcc.com”。SUPF还能够针 对具有用户的标识“zhangsan@gd.ct.com”的用户，分配临时标识“f6T5ALJdUSIfzTH1ecIzft5BmaxujRLyPsQrsMBfidregzs@gd.ct.com”。可见，SUPF对用户“lisi”和“zhangsan”所分配的临时标识不相同，而且均不涉及用户“lisi”和“zhangsan”的隐私信息。
步骤203、终端设备向UCF发送注册请求。
本实施例所示的UCF为终端设备所属的UCF，继续参见图1所示，若终端设备为被叫设备，则该UCF为被叫UCF，若终端设备为主叫设备，则该UCF为主叫UCF。终端设备能够接收来自自身所属的UCF的呼叫请求消息，以实现呼叫接续。
本实施例所示的由UCF所执行的功能，也可由其他任意设备或设备执行，具体在本实施例中不做限定。本实施例所示的UCF还可称之为第二设备，对具体的名称不做限定。
终端设备在接收到来自SUPF的临时标识的情况下，终端设备向UCF发送该注册请求，其中，该注册请求包括该临时标识以及该终端设备的注册地址。
UCF建立注册地址查询列表，该注册地址查询列表存储该临时标识和注册地址的对应关系，以便于后续呼叫的过程中使用。例如，UCF针对用户“lisi”的临时标识“CSqGSIb3DQEBAQUAA4GNADCBiQKBgQCjfidregls@bj.cmcc.com”以及针对用户“zhangsan”的临时标识“f6T5ALJdUSIfzTH1ecIzft5BmaxujRLyPsQrsMBfidregzs@gd.ct.com”，所存储的注册地址查询列表如下述表2所示：
表2
Figure PCTCN2021080939-appb-000001
本实施例以用于呼叫的，且与临时标识对应的注册地址为网际互连协议(internet protocol，IP)地址为例。例如，该IP地址1为用户“lisi”的注册地址，若需要呼叫“lisi”，则UCF向IP地址1发送呼叫请求消息。又如，IP地址2为用户“zhangsan”的注册地址，若需要呼叫“zhangsan”，则UCF向IP地址2发送呼叫请求消息。
需明确的是，本实施例以注册地址为IP地址为例进行示例性说明，在其他示例中，该注册地址也可为域名地址或者其他任意类型的地址。
步骤204、UCF向SUPF发送注册请求。
步骤205、SUPF向UCF发送响应消息。
SUPF接收到该注册请求的情况下，即可获取该注册请求所包括的临时标识。SUPF根据如表1所示的对应关系，获取与临时标识对应的用户的标识。
例如，若注册请求所包括的临时标识为“CSqGSIb3DQEBAQUAA4GNADCBiQKBgQCjfidregls@bj.cmcc.com”，则SUPF基于表1即可查询对应的用户的标识为“lisi@bj.cmcc.com”。
SUPF生成随机数，SUPF通过第三密钥对该随机数进行加密以生成第一参数。
本实施例所示的第三密钥为对称密钥加密(symmetric-key algorithm)密钥。本实施例对该对称密钥加密的具体算法不做限定，例如，该对称密钥加密的算法可为数据加密标准(data encryption standard，DES)、三重数据加密标准(3DES)、或国际数据加密算法(international data encrypt algorithm，IDEA)等。
本实施例所示的SUPF向UCF发送包括该随机数的响应消息。
步骤206、UCF向终端设备发送响应消息。
具体地，UCF向终端设备发送包括该随机数的响应消息。
步骤207、终端设备向UCF发送重注册消息。
终端设备获取到响应消息所包括的随机数的情况下，即可根据终端设备已存储的第三密钥对该随机数进行加密以生成第二参数。
本实施例所示的终端设备所存储的第三密钥和SUPF所存储的第三密钥相同，SUPF和终端设备，基于相同的第三密钥对该随机数进行相应的加密和解密运算。
终端设备向UCF发送包括该第二参数的重注册消息。
步骤208、UCF向SUPF发送重注册消息。
步骤209、SUPF判断第一参数和第二参数是否相等，若是，则执行步骤210，若否，则执行步骤212。
在SUPF获取到该重注册消息所包括的第二参数的情况下，SUPF判断该第一参数和第二参数是否相等。
若SUPF判断出第一参数和第二参数相等，则确定终端设备成功注册至SUPF，以执行步骤210。
若SUPF判断出第一参数和第二参数不相等，则确定终端设备注册失败，以执行步骤212。
步骤210、SUPF向UCF发送注册成功响应消息。
在SUPF确定终端设备成功注册至SUPF，即可向UCF发送该注册成功响应消息，注册成功响应消息用于指示终端设备成功注册至SUPF。
本实施例如步骤201所示可知，终端设备已安装用户识别卡，终端设备在初始状态并未存储使用该终端设备的用户的标识。SUPF所发送的该注册成功响应消息包括加密后的用户的标识，以保证终端设备能够获取到该用户的标识。
该SUPF对该用户的标识的加密方式，在本实施例中不做限定，例如，SUPF通过上述所示的第三密钥对用户的标识进行加密。终端设备通过第三密钥对加密后的用户的标识进行解密，终端设备即可获取到该用户的标识。
步骤211、UCF向终端设备发送注册成功响应消息。
步骤212、SUPF向UCF发送注册失败响应消息。
在SUPF确定终端设备注册失败，即可向UCF发送该注册失败响应消息，注册失败响应消息用于指示终端设备注册失败。
步骤213、UCF向终端设备发送注册失败响应消息。
终端设备根据注册失败响应消息确定注册失败后，可重新向SUPF进行注册，重新注册 的过程，请参见上述步骤所示，具体不做赘述。
采用本实施例所示的方法可知，在终端设备已安装用户识别卡的情况下，终端设备向SUPF发送包括该用户识别卡的标识符的第一临时标识申请，SUPF能够根据来自终端设备的第一临时标识申请，为终端设备分配临时标识，该临时标识不涉及任何用户的隐私信息。终端设备通过该临时标识注册至SUPF，以便于后续的呼叫。可见，终端设备通过临时标识进行注册的过程，因无需向SUPF发送用户真实的标识，如真实的号码，邮箱地址等涉及隐私信息，有效地保证了在注册阶段用户隐私信息的安全。
实施例二
实施例一说明的是终端设备已安装用户识别卡的情况下，是如何获取临时标识以及如何注册至SUPF的过程，本实施例说明的是，在终端设备未安装用户识别卡的情况下，是如何获取临时标识以及如何注册至SUPF的过程，以下结合图3所示对执行过程进行说明：
步骤301、终端设备向SUPF发送第二临时标识申请。
本实施例所示的对终端设备以及SUPF的具体说明，请详见实施例一所示，具体不做赘述。
本实施例所示的终端设备因未安装用户识别卡，则终端设备在初始状态已存储用户的标识。终端设备即可向SUPF发送包括该用户的标识的第二临时标识申请。
可见，实施例一所示的第一临时标识申请和实施例二所示的第二临时标识申请的作用是相同的，均为请求SUPF为用户分配临时标识，区别在于第一临时标识申请和第二临时标识申请所包括的消息是不同的，第一临时标识申请所包括的是用户识别卡的标识符，而第二临时标识申请包括用户的标识。
步骤302、SUPF向终端设备发送临时标识。
本实施例所示的SUPF，能够直接根据该第二临时标识申请获取用户的标识，进而根据该标识分配临时标识，具体过程的说明，请参见实施例一的步骤202所示的根据用户的标识分配临时标识的过程，具体在本实施例中不做赘述。
步骤303、终端设备向UCF发送注册请求。
步骤304、UCF向SUPF发送注册请求。
步骤305、SUPF向UCF发送响应消息。
步骤306、UCF向终端设备发送响应消息。
步骤307、终端设备向UCF发送重注册消息。
步骤308、UCF向SUPF发送重注册消息。
步骤309、SUPF判断第一参数和第二参数是否相等，若是，则执行步骤310，若否，则执行步骤312。
本实施例所示的步骤303至步骤309的执行过程的说明，请详见图2所示的步骤203至步骤209所示，具体执行过程不做赘述。
步骤310、SUPF向UCF发送注册成功响应消息。
本实施例因终端设备未安装用户识别卡，则终端设备在初始状态已存储用户的标识， 可知，在本实施例与实施例一的区别在于，本实施例所示的注册成功响应消息无需携带用户的标识。本实施例所示的注册成功响应消息仅用于向终端设备指示终端设备成功注册至SUPF即可。
步骤311、UCF向终端设备发送注册成功响应消息。
步骤312、SUPF向UCF发送注册失败响应消息。
步骤313、UCF向终端设备发送注册失败响应消息。
本实施例所示的步骤311至步骤313的执行过程的说明，请参见图2所示的步骤211至步骤213所示，具体执行过程不做赘述。
采用本实施例所示的方法可知，在终端设备未安装用户识别卡的情况下，终端设备向SUPF发送包括该用户的标识的第二临时标识申请，SUPF能够根据来自终端设备的第二临时标识申请，为终端设备分配临时标识，该临时标识不涉及任何用户的隐私信息。终端设备通过该临时标识注册至SUPF，以便于后续的呼叫。可见，终端设备通过临时标识进行注册的过程，因无需向SUPF发送用户真实的标识，如真实的号码，邮箱地址等涉及隐私信息，有效地保证了用户在注册阶段的隐私信息的安全。
实施例三
基于实施例一或实施例二所示，终端设备已获取与用户的标识对应的临时标识，以下结合图4所示，对上述所示的阶段二，即主叫用户通过主叫临时标识以及被叫临时标识呼叫被叫用户的过程进行说明。
本实施例以位于广东的主叫用户“zhangsan”呼叫位于北京的被叫用户“lisi”为例进行示例性说明，在该示例下，主叫用户所属的主叫SUPF为位于广东的SUPF，被叫用户所属的被叫SUPF为位于北京的SUPF。
步骤401、主叫设备向主叫SUPF发送密钥请求消息。
本实施例所示的由主叫SUPF所执行的功能，也可由其他任意设备或设备执行，具体在本实施例中不做限定。
本实施例所示的主叫用户在呼叫被叫用户的过程中，若希望开启防窥探功能，以保证主叫用户的主叫标识以及被叫用户的被叫标识，均不会出现泄露的情况，则主叫设备向主叫设备所属的主叫SUPF发送密钥请求消息。
本实施例所示的密钥请求消息还包括路由信息，该路由信息用于指示被叫用户所属的被叫SUPF的IP地址。
步骤402、主叫SUPF向被叫SUPF发送密钥请求消息。
本实施例所示的由被叫SUPF所执行的功能，也可由其他任意设备或设备执行，具体在本实施例中不做限定。本实施例所示的被叫SUPF还可称之为第一设备，对具体的名称不做限定。
主叫SUPF根据密钥请求消息所包括的路由信息，向被叫SUPF发送该密钥请求消息。
步骤403、被叫SUPF向主叫SUPF发送密钥响应消息。
被叫SUPF根据该密钥请求消息获取被叫SUPF自身的公钥，并向主叫SUPF发送包括该 公钥的密钥响应消息。
该被叫SUPF根据椭圆曲线密码编码学(elliptic curves cryptography，ECC)算法生成一对公钥和私钥，被叫SUPF保留该私钥，并将通过密钥响应消息向主叫设备发送该公钥。
步骤404、主叫SUPF向主叫设备发送密钥响应消息。
步骤405、主叫设备向主叫UCF发送第一呼叫请求消息。
本实施例所示的由主叫UCF所执行的功能，也可由其他任意设备或设备执行，具体在本实施例中不做限定。
该第一呼叫请求消息包括第一加密后主叫标识以及第一加密后被叫标识。其中，该第一加密后主叫标识为主叫标识通过第一密钥进行加密以生成，第一加密后被叫标识为被叫标识通过该第一密钥进行加密以生成。
以下对主叫设备获取第一密钥的过程进行说明：
主叫设备根据ECC算法生成一对临时公钥和临时私钥。本实施例所示的被叫SUPF根据ECC所生成的一对公钥和私钥为A1和A2，主叫设备根据ECC算法生成一对临时公钥和私钥为B1和B2。
主叫设备采用临时私钥B2和来自被叫SUPF的公钥A1，生成第一密钥。
本实施例所示的A1、A2、B1以及B2满足如下所示的条件：
A1*B2＝A2*B1。
在满足该A1*B2＝A2*B1的条件下，能够保证主叫设备所生成的第一密钥和被叫SUPF所生成的第一密钥是相同的。
在主叫设备获取到该第一密钥的情况下，主叫设备即可对主叫标识进行加密以生成该第一加密后主叫标识，还可通过该第一密钥对被叫标识进行加密以生成该第一加密后被叫标识。
例如，主叫设备通过第一密钥对主叫标识“zhangsan@gd.ct.com”进行加密后所生成的第一加密后主叫标识“t5BmaxujRLyPsQrsMBf6T5ALJdUSIfzTH1ecIzffiderzs@gd.ct.com”。又如，主要设备通过第一密钥对被叫标识“lisi@bj.cmcc.com”进行加密后所生成的第一加密后被叫标识为“GNADCBiQKBgQCCSqGSIb3DQEBAQUAA4jfidedls@bj.cmcc.com”。
需明确的是，本实施例对第一加密后被叫标识和第一加密后主叫标识的具体内容不做限定，只要在第一加密后主叫标识和第一加密后被叫标识出现泄露的情况，不会泄露主叫用户的主叫标识以及被叫用户的被叫标识，以保证主叫用户的隐私信息以及被叫用户的隐私信息的安全即可。
本实施例所示的第一呼叫请求消息还包括主叫用户的主叫临时标识，该主叫临时标识的具体说明，请详见实施例一或实施例二所示的临时标识的说明，具体在本实施例中不做赘述。
为保证被叫SUPF能够生成与主叫设备相同的第一密钥，则本实施例所示的第一呼叫请求消息还包括主叫设备所生成的临时公钥。
本实施例所示对第一密钥的说明为可选地示例，该第一密钥也可为对称密钥加密密钥， 以保证主叫设备所存储的第一密钥和被叫SUPF所存储的第一密钥相同。
为更好的理解本实施例所示的第一呼叫请求消息，以下对第一呼叫请求消息的具体内容进行如下的示例性说明：
下述为以第一呼叫请求消息为会话初始协议(session initiation protocol，SIP)消息为例，且下述为SIP消息的包头：
(1)INVITE GNADCBiQKBgQCCSqGSIb3DQEBAQUAA4jfidedls@bj.cmcc.com SIP/2.0
(2)Route:<sip:icscf105.domain1027.huawei.com；lr；orig>
(3)Call-ID:4b4f2093dc66b0907d8a8ebf96abcc6e
(4)From:<t5BmaxujRLyPsQrsMBf6T5ALJdUSIfzTH1ecIzffiderzs@gd.ct.com>；
(5)To:<GNADCBiQKBgQCCSqGSIb3DQEBAQUAA4jfidedls@bj.cmcc.com>
(6)FID-reg:f6T5ALJdUSIfzTH1ecIzft5BmaxujRLyPsQrsMBfidregzs@gd.ct.com
(7)pub_key_UE:OZwNeXIbkaa2RQ2l2vYRawuq+o7UOjDzrK
其中，第(1)行：该第一呼叫请求消息所要发送的对象，该第一呼叫请求消息所要发送的对象为被叫用户的第一加密后被叫标识，该第一加密后被叫标识可为：
GNADCBiQKBgQCCSqGSIb3DQEBAQUAA4jfidedls@bj.cmcc.com。
SIP/2.0表示该第一呼叫请求消息指定的版本为SIP版本2.0。
第(2)行：表示路由信息，该路由信息为被叫SUPF的IP地址。
第(3)行：Call-ID为呼叫标识，是一个在一系列消息中，区分一组消息的唯一标识，具体地，对于同一次呼叫(即本实施例所示的主叫用户呼叫被叫用户)，该第一呼叫请求消息无论经过多少个设备的多少次的转发，所有的交互信息中都包括该呼叫标识Call-ID。Call-ID由主叫设备生成，并保证在通信系统中的全局唯一性。
第(4)行：From包括主叫用户的第一加密后主叫标识，即：
t5BmaxujRLyPsQrsMBf6T5ALJdUSIfzTH1ecIzffiderzs@gd.ct.com。
第(5)行：TO包括被叫用户的第一加密后被叫标识，即：
GNADCBiQKBgQCCSqGSIb3DQEBAQUAA4jfidedls@bj.cmcc.com。
第(6)行：FID-reg包括主叫用户的主叫临时标识，即：
f6T5ALJdUSIfzTH1ecIzft5BmaxujRLyPsQrsMBfidregzs@gd.ct.com。
第(7)行：pub_key_UE包括主叫设备所生成的临时公钥。
需明确的是，本实施例对第一呼叫请求消息的格式的说明为可选地示例，不做限定，只要本实施例所示的第一呼叫请求消息包括第一加密后主叫标识、第一加密后被叫标识、主叫临时标识以及临时公钥即可。
本实施例以第一呼叫请求消息为满足SIP的消息为例进行示例性说明，在其他示例中，该第一呼叫请求消息还可满足其他协议，具体在本实施例中不做限定。
步骤406、主叫UCF向主叫SUPF发送寻址请求。
为实现主叫用户对被叫用户的呼叫，则主叫UCF需要获取被叫用户所属的被叫UCF的 IP地址，本实施例所示的寻址请求用于请求获取该被叫UCF地址。
本实施例所示以被叫UCF的地址为被叫UCF的IP地址为例进行示例性说明，在其他示例中，该被叫UCF的地址还可为域名地址或其他任意类型的地址，具体在本实施例中不做限定。
其中，该寻址请求包括第一加密后主叫标识、第一加密后被叫标识以及临时公钥。
步骤407、主叫SUPF向被叫SUPF发送寻址请求。
步骤408、被叫SUPF向主叫SUPF发送寻址响应消息。
本实施例中，在被叫SUPF接收到寻址请求所包括的第一加密后被叫标识的情况下，即可通过第一密钥对该第一加密后被叫标识进行解密，以获取被叫用户的被叫标识。
被叫SUPF查询出与被叫标识对应的被叫UCF的IP地址，并将包括该被叫UCF的IP地址的寻址响应消息向主叫SUPF发送。
以下对被叫SUPF获取第一密钥的过程进行说明：
本实施例中，被叫SUPF根据自身存储的私钥以及来自主叫设备的临时公钥，生成第一密钥。本实施例所示的SUPF生成第一密钥的过程，请参见上述所示的主叫设备生成第一密钥的过程，具体不做赘述，只要本实施例所示的主叫设备所生成的第一密钥和被叫SUPF所生成的第一密钥相同即可。
基于相同的第一密钥，被叫SUPF能够对第一加密后被叫标识进行解密以获取被叫标识，还能够对第一加密后主叫标识进行解密以获取主叫标识。
该被叫SUPF为便于对被叫用户的呼叫，则可建立如表3所示的第一查询列表，具体详见如下表3所示：
表3
Figure PCTCN2021080939-appb-000002
具体地，呼叫标识的具体说明，请详见步骤405所示，具体在本实施例中不做赘述。
针对主叫用户，被叫SUPF建立呼叫标识与第一加密后主叫标识的对应关系。被叫SUPF通过第一密钥对第一加密后主叫标识进行解密以获取主叫标识，被叫SUPF即可建立主叫标识与呼叫标识的对应关系。
针对被叫用户，被叫SUPF建立呼叫标识与第一加密后被叫标识的对应关系。被叫SUPF通过第一密钥对第一加密后被叫标识进行解密以获取被叫标识，被叫SUPF即可建立被叫标识与呼叫标识的对应关系。
基于实施例一或实施例二所示，被叫用户所使用的被叫设备能够获取被叫SUPF分配的被叫临时标识，在注册阶段，被叫SUPF已建立被叫标识和被叫临时标识的对应关系，具体 如表1所示，可知，被叫设备在获取到被叫标识的情况下，即可通过查询如表1所示的对应关系获取到对应的被叫临时标识，被叫SUPF即可建立呼叫标识和被叫临时标识的对应关系。
可知，本实施例所示的寻址响应消息包括被叫UCF的IP地址、第一加密后被叫标识以及第一加密后主叫标识。
步骤409、主叫SUPF向主叫UCF发送寻址响应消息。
在主叫UCF接收到该寻址响应消息后，主叫UCF即可获取到被叫UCF的IP地址。
可选地，主叫UCF还可向主叫SEF发送业务请求，以触发SEF执行对应的主叫业务，触发SEF执行的主叫业务可为主叫用户呼叫的被限制类的业务、补充业务能力等，具体在本实施例中不做限定。
主叫SEF在主叫业务触发过程中，需要获取用于实现该主叫业务的配置文件。为此，主叫SEF向主叫SUPF发送业务请求消息，该业务请求消息包括主叫临时标识。主叫SUPF查询出与主叫临时标识对应的主叫标识，具体可参见表1所示，具体不做赘述。
主叫SUPF获取与主叫标识对应的主叫业务的配置文件，并向主叫SEF发送包括该配置文件的业务响应，主叫SEF根据该配置文件即可实现该主叫业务。
可见，在主叫SEF向主叫SUPF获取主叫业务的配置文件的过程中，主叫SEF向主叫SUPF发送主叫临时标识，可见，主叫SEF不会获取主叫用户的标识，避免了主叫用户的标识在主叫SEF处泄露的可能，从而使得即便主叫SEF处于不安全的状态，主叫标识也不会泄露，提高了主叫用户的隐私信息的安全。
本实施例所示以步骤401至步骤409，为主叫用户向被叫用户呼叫的过程中执行，在其他示例中，也可在主叫用户呼叫被叫用户之前，预先执行本实施例所示的步骤401至步骤409。
步骤410、主叫UCF向被叫UCF发送第二呼叫请求消息。
本实施例所示的由被叫UCF所执行的功能，也可由其他任意设备或设备执行，具体在本实施例中不做限定。本实施例所示的被叫UCF还可称之为第二设备，对具体的名称不做限定。
为实现主叫用户对被叫用户的呼叫，则主叫UCF根据被叫UCF的IP地址，向被叫UCF发送第二呼叫请求消息。
具体地，主叫UCF根据来自主叫设备的第一呼叫请求消息构造第二呼叫请求消息，本实施例所示的第二呼叫请求消息包括第一加密后主叫标识以及第一加密后被叫标识。
可见，本实施例所示的第一呼叫请求消息和第二呼叫请求消息的区别在于，第一呼叫请求消息和第二呼叫请求消息均包括第一加密后主叫标识以及第一加密后被叫标识。而第二呼叫请求不包括第一呼叫请求消息所包括的主叫临时标识以及临时公钥。
步骤411、被叫UCF向被叫SUPF发送第一查询请求。
本实施例中，若被叫UCF判断出所接收到的第二呼叫请求消息所包括的被叫标识为经过加密的标识，则被叫UCF向被叫SUPF发送该第一查询请求，其中，该第一查询请求包括第一加密后被叫标识。
该第一查询请求用于请求获取与第一加密后被叫标识对应的被叫临时标识。
步骤412、被叫SUPF向被叫UCF发送查询响应。
由步骤408所示可知，被叫SUPF已创建如表3所示的第一查询列表，可知，该第一查询列表已创建被叫临时标识和第一加密后被叫标识的对应关系，对该第一查询列表的具体说明，请详见步骤408所示，具体不做赘述。
在被叫SUPF已接收到包括第一加密后被叫标识的第一查询请求的情况下，即可根据该第一查询列表确定与第一加密后被叫标识对应的被叫临时标识。
被叫SUPF向被叫UCF发送包括该被叫临时标识的查询响应。
步骤413、被叫UCF向被叫设备发送第三呼叫请求消息。
由实施例一所示的步骤203所示可知，在被叫设备注册的阶段中，被叫UCF已创建如表2所示的注册地址查询列表，对该注册地址查询列表的具体说明请详见步骤203所示，具体在本实施例中不做赘述。
可见，在被叫UCF接收到查询响应所包括的被叫临时标识的情况下，被叫UCF即可通过查询如表2所示的注册地址查询列表的方式确定与被叫临时标识对应的注册地址，被叫UCF即可向该注册地址发送第三呼叫请求消息。
例如，被叫用户“lisi”的被叫临时标识为“CSqGSIb3DQEBAQUAA4GNADCBiQKBgQCjfidregls@bj.cmcc.com”，被叫UCF通过表2确定与该被叫临时标识对应的注册地址为IP地址1，则被叫UCF即可向IP地址1发送该第三呼叫请求消息。
本实施例所示的第三呼叫请求消息包括被叫临时标识。
在被叫设备接收到来自被叫UCF的第三呼叫请求的情况下，即可实现对被叫设备的接续，以下对如何在主叫用户呼叫被叫用户的过程中，实现被叫设备显示主叫用户的标识的过程进行示例性说明。
本实施例以需要通过如下所示的步骤414至步骤415所示，以实现被叫设备对主叫标识的显示为例，需明确的是，本实施例所示的步骤414至步骤415为可选执行的步骤，在其他示例中，被叫设备也可无需显示主叫标识。
步骤414、被叫设备向被叫SUPF发送标识查询请求。
为支持被叫设备对主叫用户的主叫标识的查询功能，则被叫UCF向被叫设备发送的第三呼叫请求消息还包括第一加密后主叫标识。
被叫设备为显示主叫用户的主叫标识，则被叫设备向被叫SUPF发送标识查询请求，其中，该标识查询请求包括第一加密后主叫标识。
步骤415、被叫SUPF向被叫设备发送主叫标识。
被叫SUPF在获取到第一查询请求所包括的第一加密后主叫标识的情况下，即可根据如表3所示的第一查询列表，即可查询出与第一加密后主叫标识对应的主叫标识。
需明确的是，本实施例以被叫设备通过向被叫SUPF发送第一加密后主叫标识以请求获取主叫标识为例，在其他示例中，被叫设备也可直接向被叫SUPF发送被叫临时标识。被叫SUPF所存储的查询如表3所示，被叫临时标识和主叫标识均与呼叫标识对应，可见，被叫 SUPF能够通过被叫临时标识，查询出与被叫临时标识对应的主叫标识。
被叫设备接收到该主叫标识的情况下，即可在振铃的过程中，显示该主叫标识。
本实施例所示的被叫SUPF和被叫设备之间可建立安全连接，被叫SUPF即可基于该安全连接向被叫设备发送该主叫标识，从而有效地提高了被叫SUPF向被叫设备所发送的主叫标识的安全。
本实施例所示除了被叫SUPF向被叫设备明文发送主叫标识之外，在主叫用户呼叫被叫用户的过程中，涉及隐私信息的主叫标识以及被叫标识均为密文发送，从而有效地避免了主叫标识和被叫标识的泄露，有效地提高了主叫用户与被叫用户之间的通信安全。
而且本实施例所示的方法，无需主叫设备与主叫SUPF之间，主叫设备与主叫UCF之间，主叫UCF与被叫UCF之间，被叫SUPF与被叫UCF之间，被叫UCF与被叫设备之间建立安全连接，即可有效地避免主叫标识和被叫标识的泄露，从而降低了设备之间交互的复杂度，提高了呼叫效率。
本实施例所示在主叫用户呼叫被叫用户的过程中，无需中间设备对第一加密后主叫标识以及第一加密后被叫标识进行解密，如该中间设备为主叫SUPF、主叫UCF以及被叫UCF，避免了中间设备因对第一加密后主叫标识和第一加密后被叫标识进行解密所带来的泄露的风险，提高了呼叫过程中，主叫标识以及被叫标识的安全。而且因中间设备无需解密的过程，提高了呼叫的效率。
本实施例所示的主叫UCF以及被叫UCF所获取到的主叫标识和被叫标识均经过加密，避免了主叫标识和被叫标识在主叫UCF以及被叫UCF处泄露的可能，可见，即便主叫UCF以及被叫UCF处于不安全的状态，也不会造成主叫标识和被叫标识的泄露。
实施例四
在实施例三中，被叫设备若需要显示主叫标识，则被叫设备需要单独向被叫SUPF发送标识查询请求，而本实施例所示，被叫设备为显示主叫标识，无需单独向被叫SUPF发送标识查询请求即可实现，具体实现过程请参见如下图5所示：
步骤501、主叫设备向主叫SUPF密钥请求消息。
步骤502、主叫SUPF向被叫SUPF发送密钥请求消息。
步骤503、被叫SUPF向主叫SUPF发送密钥响应消息。
步骤504、主叫SUPF向主叫设备发送密钥响应消息。
步骤505、主叫设备向主叫UCF发送第一呼叫请求消息。
步骤506、主叫UCF向主叫SUPF发送寻址请求。
步骤507、主叫SUPF向被叫SUPF发送寻址请求。
本实施例所示的步骤501至步骤507的具体执行过程，请详见实施例三中的步骤401至步骤407所示，具体执行过程在本实施例中不做赘述。
步骤508、被叫SUPF向主叫SUPF发送寻址响应消息。
本实施例中，在被叫SUPF接收到寻址请求所包括第一加密后主叫标识、第一加密后被叫标识的情况下，通过第一密钥对该第一加密后被叫标识进行解密，以获取被叫用户的被 叫标识，还能够通过该第一密钥对该第一加密后主叫标识进行解密，以获取主叫用户的主叫标识，被叫SUPF获取第一密钥的过程，请详见实施例三的步骤408所示，具体在本实施例中不做赘述。
被叫SUPF查询出与被叫标识对应的被叫UCF的IP地址，并将包括该被叫UCF的IP地址的寻址响应消息向主叫SUPF发送。
该被叫SUPF为便于对被叫用户的呼叫，则可建立如表4所示的第二查询列表，具体详见如下表4所示：
表4
Figure PCTCN2021080939-appb-000003
对表4所包括的具体内容的说明，请详见实施例三的表3所示，具体在本实施例中不做赘述。
本实施例所示的被叫SUPF通过第二密钥对被叫标识进行加密以生成第二加密后被叫标识，被叫SUPF还通过表4所示的第二查询列表建立该第二加密后被叫标识与该呼叫标识的对应关系。
其中，该第二密钥和被叫设备所存储的第二密钥相同。本实施例对被叫SUPF获取第二密钥的过程不做限定，例如，被叫SUPF可接收来自被叫设备的第二密钥。本实施例所示的第二密钥可为对称密钥加密密钥，对该称密钥加密密钥的具体说明，请详见实施例一所示，具体在本实施例中不做赘述。
本实施例所示的被叫SUPF通过该第二密钥对主叫标识进行加密以生成第二加密后主叫标识，被叫SUPF还通过表4所示的第二查询列表建立该第二加密后被叫标识与该呼叫标识的对应关系。
本实施例所示的寻址响应消息包括被叫UCF的IP地址、第二加密后被叫标识以及第二加密后主叫标识。
步骤509、主叫SUPF向主叫UCF发送寻址响应消息。
本实施例所示的步骤509的执行过程，请详见实施例三所示的步骤409所示，具体在本实施例中不做赘述。
步骤510、主叫UCF向被叫UCF发送第四呼叫请求消息。
为实现主叫用户对被叫用户的呼叫，则主叫UCF根据被叫UCF的IP地址，向被叫UCF 发送第四呼叫请求消息。
具体地，本实施例所示的第四呼叫请求消息包括第二加密后主叫标识以及第二加密后被叫标识。
步骤511、被叫UCF向被叫SUPF发送第二查询请求。
本实施例中，若被叫UCF判断出所接收到的第四呼叫请求消息所包括的被叫标识为经过加密的标识，则被叫UCF向被叫SUPF发送该第二查询请求，其中，该第二查询请求包括第二加密后被叫标识。
该第二查询请求用于请求获取与第二加密后被叫标识对应的被叫临时标识。
步骤512、被叫SUPF向被叫UCF发送查询响应。
由步骤508所示可知，被叫SUPF已创建如表4所示的第二查询列表，可知，该第二查询列表已创建被叫临时标识和第二加密后被叫标识的对应关系，对该第二查询列表的具体说明，请详见步骤508所示，具体不做赘述。
在被叫SUPF已接收到包括第二加密后被叫标识的第二查询请求的情况下，即可根据该第二查询列表确定与第二加密后被叫标识对应的被叫临时标识。
被叫SUPF向被叫UCF发送包括该第二加密后被叫标识的查询响应。
步骤513、被叫UCF向被叫设备发送第五呼叫请求消息。
由实施例一所示的步骤203所示可知，在被叫设备注册的阶段中，被叫UCF已创建如表2所示的注册地址查询列表，对该注册地址查询列表的具体说明请详见步骤203所示，具体在本实施例中不做赘述。
可见，在被叫UCF接收到查询响应所包括的被叫临时标识的情况下，被叫UCF即可通过查询如表2所示的注册地址查询列表的方式确定与被叫临时标识对应的注册地址，被叫UCF即可向该注册地址发送第五呼叫请求消息。
本实施例所示的第三呼叫请求消息包括被叫临时标识以及第二加密后主叫标识。
步骤514、被叫设备接收第五呼叫请求消息。
在被叫设备接收到来自被叫UCF的第五呼叫请求的情况下，即可实现对被叫设备的接续。
由上述说明可知，本实施例所示的被叫SUPF和被叫设备所存储的第二密钥相同，则可知，被叫设备接收到第二加密后主叫标识的情况下，即可通过该第二密钥对该第二加密后主叫标识进行解密以获取该主叫标识。
被叫设备成功获取到解密后的主叫标识后，被叫设备即可对该主叫标识进行显示。
本实施例所示的呼叫处理方法的有益效果的说明，请详见实施例三所示，具体不做赘述。
本实施例进一步取得的有益效果为：本实施例所示的被叫设备无需单独向被叫SUPF发送标识查询请求，即可根据第五呼叫请求消息获取主叫标识，提高了呼叫效率。
而且本实施例所示的被叫SUPF向被叫设备所发送的主叫标识也经过加密，提高了主叫标识的安全，避免了在被叫SUPF向被叫设备发送主叫标识出现泄露的可能。
实施例五
本实施例结合图6所示对执行上述呼叫处理方法的网络设备的结构进行说明：
网络设备600具体包括：处理单元601和收发单元602，其中，处理单元601与收发单元602连接。
若本实施例所示的网络设备600为UCF，则处理单元601用于执行实施例一或实施例二中，任一实施例中由UCF执行的处理功能。收发单元602用于执行实施例一或实施例二中，任一实施例中由UCF执行的收发功能。
若本实施例所示的网络设备600为UCF，且该UCF为主叫UCF，则处理单元601用于执行实施例三至实施例五中，任一实施例中由主叫UCF执行的处理功能。收发单元602用于执行实施例三至实施例五中，任一实施例中由主叫UCF执行的收发功能。
若本实施例所示的网络设备600为UCF，且该UCF为被叫UCF，则处理单元601用于执行实施例三至实施例五中，任一实施例中由被叫UCF执行的处理功能。收发单元602用于执行实施例三至实施例五中，任一实施例中由被叫UCF执行的收发功能。
若本实施例所示的网络设备600为SUPF，则处理单元601用于执行实施例一或实施例二中，任一实施例中由SUPF执行的处理功能。收发单元602用于执行实施例一或实施例二中，任一实施例中由SUPF执行的收发功能。
若本实施例所示的网络设备600为SUPF，且该SUPF为主叫SUPF，则处理单元601用于执行实施例三至实施例五中，任一实施例中由主叫SUPF执行的处理功能。收发单元602用于执行实施例三至实施例五中，任一实施例中由主叫SUPF执行的收发功能。
若本实施例所示的网络设备600为SUPF，且该SUPF为被叫SUPF，则处理单元601用于执行实施例三至实施例五中，任一实施例中由被叫SUPF执行的处理功能。收发单元602用于执行实施例三至实施例五中，任一实施例中由被叫SUPF执行的收发功能。
若本实施例所示的网络设备600为终端设备，则处理单元601用于执行实施例一或实施例二中，任一实施例中由终端设备执行的处理功能。收发单元602用于执行实施例一或实施例二中，任一实施例中由终端设备执行的收发功能。
若本实施例所示的网络设备600为主叫设备，则处理单元601用于执行实施例三至实施例五中，任一实施例中由主叫设备执行的处理功能。收发单元602用于执行实施例三至实施例五中，任一实施例中由主叫设备执行的收发功能。
若本实施例所示的网络设备600为被叫设备，则处理单元601用于执行实施例三至实施例五中，任一实施例中由被叫设备执行的处理功能。收发单元602用于执行实施例三至实施例五中，任一实施例中由被叫设备执行的收发功能。
实施例六
本实施例结合图7所示，从实体硬件角度，对执行上述呼叫处理方法的网络设备的结构进行说明：
网络设备具体包括：处理器701、存储器702、总线703、收发器704以及网络接口706。
具体的，存储器702可以包括以易失性和/或非易失性存储器形式的计算机存储媒体， 如只读存储器和/或随机存取存储器。存储器702可以存储操作系统、应用程序、其他程序模块、可执行代码和程序数据。
收发器704可以用于向网络设备输入命令和信息，该收发器704可以通过总线703连接至处理器701。收发器704还可以用于网络设备输出信息，例如所选定的占位服务器和/或占位虚拟机。
网络设备可以通过网络接口706连接到通信网络中，在联网环境下，网络设备中存储的计算机执行指令可以存储在远程存储设备中，而不限于在本地存储。
当网络设备中的处理器701执行存储器702中存储的可执行代码或应用程序时，网络设备可以执行以上方法实施例中的任一侧的方法操作，具体执行过程参见上述方法实施例，在此不再赘述。
以上所述，以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (23)

  1. 一种呼叫处理的方法，其特征在于，所述方法包括：
    第一设备接收加密后被叫标识，所述加密后被叫标识为对被叫标识进行加密以生成，所述被叫标识为被叫用户的标识；
    所述第一设备获取与所述加密后被叫标识对应的被叫临时标识，所述被叫临时标识为临时为所述被叫用户所分配的标识；
    所述第一设备向第二设备发送所述被叫临时标识，所述第二设备用于根据所述被叫临时标识呼叫所述被叫用户所使用的被叫设备。
  2. 根据权利要求1所述的方法，其特征在于，所述第一设备获取与所述加密后被叫标识对应的被叫临时标识之前，所述方法还包括：
    所述第一设备获取与所述被叫标识对应的所述被叫临时标识；
    所述第一设备建立所述加密后被叫标识和所述被叫临时标识的对应关系。
  3. 根据权利要求2所述的方法，其特征在于，所述第一设备获取与所述被叫标识对应的所述被叫临时标识之前，所述方法还包括：
    所述第一设备接收来自主叫设备的所述加密后被叫标识，所述加密后被叫标识为所述被叫标识通过第一密钥进行加密以生成，所述主叫设备为主叫用户所使用的设备；
    所述第一设备通过所述第一密钥对所述加密后被叫标识进行解密以获取所述被叫标识。
  4. 根据权利要求3所述的方法，其特征在于，所述第一设备通过所述第一密钥对所述加密后被叫标识进行解密以获取所述被叫标识之前，所述方法还包括：
    所述第一设备通过椭圆曲线密码编码学ECC算法对私钥和来自所述主叫设备的临时公钥进行计算以获取所述第一密钥。
  5. 根据权利要求3或4所述的方法，其特征在于，所述第一设备向第二设备发送所述被叫临时标识之前，所述方法还包括：
    所述第一设备接收来自所述主叫设备的第一加密后主叫标识，所述第一加密后主叫标识为主叫标识通过所述第一密钥进行加密以生成，所述主叫标识为所述主叫用户的标识；
    所述第一设备通过所述第一密钥对所述第一加密后主叫标识进行解密以获取所述主叫标识；
    所述第一设备建立所述加密后被叫标识和所述主叫标识的对应关系。
  6. 根据权利要求5所述的方法，其特征在于，所述第一设备向第二设备发送所述被叫临时标识之后，所述方法还包括：
    所述第一设备接收来自所述被叫设备的标识查询请求，所述标识查询请求包括所述加密后主叫标识；
    所述第一设备获取与所述加密后主叫标识对应的所述主叫标识；
    所述第一设备向所述被叫设备发送所述主叫标识。
  7. 根据权利要求2所述的方法，其特征在于，所述第一设备获取与所述被叫标识对应的所述被叫临时标识之前，所述方法还包括：
    所述第一设备通过第二密钥对所述被叫标识进行加密以生成所述加密后被叫标识；
    所述第一设备向主叫设备发送所述加密后被叫标识。
  8. 根据权利要求7所述的方法，其特征在于，所述第一设备向第二设备发送所述被叫临时标识之前，所述方法还包括：
    所述第一设备接收来自所述主叫设备的第一加密后主叫标识，所述第一加密后主叫标识为主叫标识通过第一密钥进行加密以生成，所述主叫标识为主叫用户的标识；
    所述第一设备通过所述第一密钥对所述第一加密后主叫标识进行解密以获取所述主叫标识；
    所述第一设备通过所述第二密钥，对所述主叫标识进行加密以生成第二加密后主叫标识；
    所述第一设备向所述被叫设备发送所述第二加密后主叫标识。
  9. 根据权利要求1至8任一项所述的方法，其特征在于，所述第一设备接收加密后被叫标识之前，所述方法还包括：
    所述第一设备接收来自所述被叫设备的第一临时标识申请，所述第一临时标识申请包括所述被叫设备的用户识别卡的标识符；
    所述第一设备根据所述第一临时标识申请为所述被叫用户分配所述被叫临时标识；
    所述第一设备建立所述被叫标识和所述被叫临时标识的对应关系；
    所述第一设备向所述被叫设备发送所述被叫临时标识以及加密后的所述被叫标识。
  10. 根据权利要求1至8任一项所述的方法，其特征在于，所述第一设备接收加密后被叫标识之前，所述方法还包括：
    所述第一设备接收来自所述被叫设备的第二临时标识申请，所述第二临时标识申请包括所述被叫标识；
    所述第一设备根据所述第二临时标识申请为所述被叫用户分配所述被叫临时标识；
    所述第一设备建立所述被叫标识和所述被叫临时标识的对应关系；
    所述第一设备向所述被叫设备发送所述被叫临时标识。
  11. 根据权利要求1至10任一项所述的方法，其特征在于，所述第一设备向所述被叫设备发送所述被叫临时标识之后，所述方法还包括：
    所述第一设备接收来自所述被叫设备的注册请求，所述注册请求包括所述被叫临时标 识；
    所述第一设备向所述被叫设备发送随机数；
    所述第一设备通过第三密钥对所述随机数进行加密以生成第一参数；
    所述第一设备接收来自所述被叫设备的第二参数，所述第二参数为所述被叫设备通过所述第三密钥对所述随机数进行加密以生成的参数；
    若所述第一设备确定所述第一参数和所述第二参数相等，则所述第一设备向所述被叫设备发送注册响应消息，所述注册响应消息用于指示所述被叫设备注册成功。
  12. 一种呼叫处理的方法，其特征在于，所述方法包括：
    主叫设备获取待呼叫的被叫用户对应的被叫标识；
    所述主叫设备对所述被叫标识进行加密以获取加密后被叫标识；
    所述主叫设备向第二设备发送呼叫请求消息，所述呼叫请求消息包括所述加密后被叫标识。
  13. 根据权利要求12所述的方法，其特征在于，所述主叫设备对所述被叫标识进行加密以获取加密后被叫标识包括：
    所述主叫设备通过第一密钥对所述被叫标识进行加密以获取加密后被叫标识。
  14. 根据权利要求12所述的方法，其特征在于，所述主叫设备向第二设备发送呼叫请求消息之前，所述方法还包括：
    所述主叫设备通过第一密钥对主叫标识进行加密以获取加密后主叫标识，所述主叫标识为主叫用户的标识，其中，所述呼叫请求消息包括所述加密后主叫标识。
  15. 根据权利要求13或14所述的方法，其特征在于，所述方法还包括：
    所述主叫设备通过椭圆曲线密码编码学ECC算法对临时私钥和来自第一设备的公钥进行计算以获取所述第一密钥。
  16. 一种呼叫处理的方法，其特征在于，所述方法包括：
    第二设备接收来自第一设备的被叫临时标识，所述被叫临时标识为临时为被叫用户所分配的标识；
    所述第二设备向被叫设备发送呼叫请求消息，所述呼叫请求消息包括所述被叫临时标识，所述被叫设备为被叫用户所使用的设备。
  17. 根据权利要求16所述的方法，其特征在于，所述第二设备接收来自第一设备的被叫临时标识之前，所述方法还包括：
    所述第二设备接收来自主叫设备的呼叫请求消息，所述呼叫请求消息包括加密后被叫标识，所述加密后被叫标识为对被叫标识进行加密以生成，所述被叫标识为所述被叫用户 的标识；
    所述第二设备向所述第一设备发送查询请求，所述查询请求包括所述加密后被叫标识，所述查询请求用于请求获取与所述加密后被叫标识对应的所述被叫临时标识。
  18. 根据权利要求17所述的方法，其特征在于，所述第二设备向被叫设备发送呼叫请求消息包括：
    所述第二设备根据所述被叫临时标识对应的所述被叫设备的注册地址，向所述被叫设备发送所述呼叫请求消息。
  19. 一种第一设备，其特征在于，包括分别与处理器耦合的存储器和收发器，所述存储器中存储了计算机程序代码，所述处理器调用并执行所述存储器中的计算机程序代码，使得所述处理器执行如权利要求1-11任一项与处理相关的步骤，所述收发器用于执行如权利要求1-11任一项与收发相关的步骤。
  20. 一种主叫设备，其特征在于，包括分别与处理器耦合的存储器和收发器，所述存储器中存储了计算机程序代码，所述处理器调用并执行所述存储器中的计算机程序代码，使得所述处理器执行如权利要求12-15任一项与处理相关的步骤，所述收发器用于执行如权利要求12-15任一项与收发相关的步骤。
  21. 一种第二设备，其特征在于，包括分别与处理器耦合的存储器和收发器，所述存储器中存储了计算机程序代码，所述处理器调用并执行所述存储器中的计算机程序代码，使得所述处理器执行如权利要求16-18任一项与处理相关的步骤，所述收发器用于执行如权利要求16-18任一项与收发相关的步骤。
  22. 一种通信系统，其特征在于，包括主叫设备、第一设备、第二设备以及被叫设备，所述主叫设备用于经由所述第一设备以及所述第二设备呼叫所述被叫设备，所述主叫设备如权利要求20所述，所述第一设备如权利要求19所述，所述第二设备如权利要求21所述。
  23. 一种计算机可读存储介质，其特征在于，
    所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时能够完成权利要求1至18任意一项所述的方法。
PCT/CN2021/080939 2021-03-16 2021-03-16 一种呼叫处理方法、相关设备以及存储介质 WO2022193110A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN202180095568.4A CN117015957A (zh) 2021-03-16 2021-03-16 一种呼叫处理方法、相关设备以及存储介质
EP21930706.3A EP4297386A4 (en) 2021-03-16 2021-03-16 CALL PROCESSING METHOD, RELATED DEVICE AND STORAGE MEDIUM
PCT/CN2021/080939 WO2022193110A1 (zh) 2021-03-16 2021-03-16 一种呼叫处理方法、相关设备以及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/080939 WO2022193110A1 (zh) 2021-03-16 2021-03-16 一种呼叫处理方法、相关设备以及存储介质

Publications (1)

Publication Number Publication Date
WO2022193110A1 true WO2022193110A1 (zh) 2022-09-22

Family

ID=83321616

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/080939 WO2022193110A1 (zh) 2021-03-16 2021-03-16 一种呼叫处理方法、相关设备以及存储介质

Country Status (3)

Country Link
EP (1) EP4297386A4 (zh)
CN (1) CN117015957A (zh)
WO (1) WO2022193110A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101606372A (zh) * 2007-02-06 2009-12-16 诺基亚公司 支持无uicc呼叫
US9973625B1 (en) * 2016-10-04 2018-05-15 Amazon Technologies, Inc. System to share and present temporary contact information
CN109429328A (zh) * 2017-08-21 2019-03-05 华为技术有限公司 通信方法、相关装置及系统
CN111314919A (zh) * 2020-03-19 2020-06-19 西安电子科技大学 用于在认证服务端保护用户身份隐私的增强5g认证方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20110036301A (ko) * 2009-10-01 2011-04-07 삼성전자주식회사 아이엠에스 시스템에서 임시 그루 생성 방법 및 장치
US10993282B2 (en) * 2017-08-09 2021-04-27 Lenovo (Singapore) Pte. Ltd. Method and apparatus for short code dialing for restricted services for unauthenticated user equipment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101606372A (zh) * 2007-02-06 2009-12-16 诺基亚公司 支持无uicc呼叫
US9973625B1 (en) * 2016-10-04 2018-05-15 Amazon Technologies, Inc. System to share and present temporary contact information
CN109429328A (zh) * 2017-08-21 2019-03-05 华为技术有限公司 通信方法、相关装置及系统
CN111314919A (zh) * 2020-03-19 2020-06-19 西安电子科技大学 用于在认证服务端保护用户身份隐私的增强5g认证方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4297386A4 *

Also Published As

Publication number Publication date
EP4297386A1 (en) 2023-12-27
CN117015957A (zh) 2023-11-07
EP4297386A4 (en) 2024-04-03

Similar Documents

Publication Publication Date Title
US10091005B2 (en) Push notification service
US10419895B2 (en) Method and system for identity management across multiple planes
CN109981633B (zh) 访问服务器的方法、设备及计算机可读存储介质
US7574735B2 (en) Method and network element for providing secure access to a packet data network
JP3263878B2 (ja) 暗号通信システム
US8990569B2 (en) Secure communication session setup
US8104082B2 (en) Virtual security interface
EP1374533B1 (en) Facilitating legal interception of ip connections
US11297115B2 (en) Relaying media content via a relay server system without decryption
Festijo et al. Software-defined security controller-based group management and end-to-end security management
US11134088B2 (en) Secure next-hop communication
WO2022193110A1 (zh) 一种呼叫处理方法、相关设备以及存储介质
US20230199001A1 (en) Secure streaming media based on updating hypercontent in a secure peer-to-peer data network
EP3188402A1 (en) Method to establish a private and confidential connection
JP2008187686A (ja) トンネル通信システム、制御装置およびトンネル通信装置
CN115499825B (zh) 基于二次鉴权的5g报文头增强方法、设备和存储介质
WO2024012529A1 (zh) 密钥管理方法、装置、设备及存储介质
US20240097903A1 (en) Ipcon mcdata session establishment method
RU2517405C2 (ru) Способ обеспечения сопоставлений безопасности для зашифрованных пакетных данных
US10841283B2 (en) Smart sender anonymization in identity enabled networks
CN116711387A (zh) 利用边缘数据网络进行认证和授权的方法、设备和系统
WO2022048802A1 (en) Methods and nodes for deactivating server name indication, sni, encryption in a telecommunication network
CN115699681A (zh) 由中间实体实现的用于管理两个通信设备之间的通信的方法
WO2014094223A1 (zh) 计费方法及装置
Pietiäinen et al. Adapting SLP to ad-hoc environment

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202180095568.4

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2021930706

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021930706

Country of ref document: EP

Effective date: 20230919

NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21930706

Country of ref document: EP

Kind code of ref document: A1