Conference call forwarding method and system
By deploying conference registration and calls on different servers, and using call forwarding methods, the problem of high server pressure in traditional systems is solved, and the number of concurrent accesses and real-time performance of conferences is improved.
Patent Information
- Application Number
- CN202411386347.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-30
- Publication Date
- 2025-01-07
AI Technical Summary
Traditional conference call systems have high pressure on the server's processor and memory, resulting in a limited number of meeting terminals to be accessed, affecting the concurrency and real-time nature of the conference.
By deploying conference registration and calls on different servers, the call forwarding method can reduce the pressure on a single server and increase the number of concurrent access. The specific implementation includes a first microcontroller registering the conference terminal and generating registration information, and the second microcontroller sending a redirection instruction message based on the registration information, causing the conference terminal to notify the second microcontroller to join the conference.
It effectively improves the number of concurrent accesses and real-time performance of conferences, reduces the pressure on a single server, and solves the problem of limited accesses in traditional systems.
Smart Images
Figure CN119276841A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of multimedia conferences, and in particular to a conference call transfer method and system. Background Art
[0002] With the continuous development of video conferencing, users have more and more demands for video conferencing functions, and the number of participants is also increasing.
[0003] In the traditional conference call system, the server mainly receives the registration of the conference terminal and calls the conference terminal. The traditional conference call system has a great pressure on the server's processor and memory. The number of participants is severely limited by the server performance, and the number of conference terminals that can be successfully connected in a short period of time is very limited. As the number of participants continues to increase, it will have a negative impact on the effect of the meeting, and even affect the fluency and integrity of the audio and video of the meeting, making it difficult to ensure the concurrency and real-time performance of the meeting. Summary of the invention
[0004] The present application provides a conference call transfer method and system to solve the problem that the traditional conference call system has a great pressure on the processor and memory of the server and the number of connected conference terminals is very limited; by deploying conference registration and conference calls on different servers, call transfer is used to reduce the pressure on a single server and increase the number of concurrent conference accesses.
[0005] In a first aspect, an embodiment of the present application provides a conference call transfer method, which is applied to a conference call transfer system for transferring calls to conference terminals, wherein the conference call transfer system includes: a first microcontroller for conference registration and a second microcontroller for conference calls, and the method includes:
[0006] The first microcontroller registers the conference terminal for the conference and generates conference registration information;
[0007] The second microcontroller sends a redirection indication message to the first microcontroller according to the conference registration information;
[0008] The first microcontroller forwards the redirection indication message to the conference terminal, so that the conference terminal notifies the second microcontroller to call the conference terminal to join the conference.
[0009] In a second aspect, an embodiment of the present application provides a conference call transfer system, comprising: a first microcontroller for conference registration and a second microcontroller for conference calling; wherein:
[0010] The first microcontroller is used to register the conference terminal for the conference and generate conference registration information;
[0011] The second microcontroller is used for sending a redirection indication message to the first microcontroller according to the conference registration information;
[0012] The first microcontroller is further configured to forward the redirection indication message to the conference terminal, so that the conference terminal notifies the second microcontroller to call the conference terminal to join the conference.
[0013] The technical solution of the embodiment of the present application is to register the conference terminal for the conference through the first microcontroller and generate conference registration information; the second microcontroller sends a redirection indication message to the first microcontroller according to the conference registration information; the first microcontroller forwards the redirection indication message to the conference terminal, so that the conference terminal notifies the second microcontroller to call the conference terminal to join the conference; by deploying the conference registration and conference call on different servers, the second microcontroller calls the conference terminal registered on the first microcontroller to join the conference by means of conference call transfer, thereby solving the problem that the traditional conference call system has a great pressure on the processor and memory of the server and the number of connected conference terminals is very limited, reducing the pressure on a single server and increasing the number of concurrent conference accesses.
[0014] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0016] Figure 1 A flowchart of a conference call transfer method provided in an embodiment of the present application;
[0017] Figure 2 A schematic diagram of information interaction of conference call transfer based on identity authentication provided in an embodiment of the present application;
[0018] Figure 3 A schematic diagram of the principle of a conference call transfer process based on quantum key and two-way identity authentication provided in an embodiment of the present application;
[0019] Figure 4 A data frame structure diagram of an identity authentication command message in a conference call transfer method provided in an embodiment of the present application;
[0020] Figure 5A data frame structure diagram of an identity authentication request message in a conference call transfer method provided in an embodiment of the present application;
[0021] Figure 6 A data frame structure diagram of an identity authentication response message in a conference call transfer method provided in an embodiment of the present application;
[0022] Figure 7 A schematic diagram of the structure of a conference call transfer system provided in an embodiment of the present application. DETAILED DESCRIPTION
[0023] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.
[0024] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0025] Embodiment 1
[0026] Figure 1 A flowchart of a conference call transfer method provided in Example 1 of the present application. This embodiment is applicable to the case of calling a batch of conference terminals to join a conference. The method can be executed by a conference call transfer system. The conference call transfer system is used to register and call conference terminals so that the conference system joins the conference, and the conference terminals serve as the call objects of the conference call transfer system. The conference call transfer system includes: a first microcontroller and a second microcontroller; wherein the first microcontroller is used to register the conference terminal for the conference, and the second microcontroller is used to make conference calls to the conference terminal.
[0027] like Figure 1 As shown, the method includes:
[0028] S110: The first microcontroller registers the conference terminal and generates conference registration information.
[0029] Among them, the first microcontroller MCU1 can be considered as a microcontroller responsible for conference registration. The conference terminal (Meeting Terminal, MT) can be understood as a terminal device that needs to access the conference, and in this embodiment, it is the object of conference call transfer. The conference registration information can be understood as the information generated by the conference terminal for conference registration, for example, it can include: conference terminal registration address, ID of the device to which the conference terminal belongs, conference terminal registration number, conference registration time, user name and password registered by the conference terminal, etc. The registration address of the conference terminal can be considered as the address of the first microcontroller that registers the conference terminal.
[0030] Specifically, the first microcontroller receives a conference registration request initiated by the conference registration terminal, responds to the conference registration request, and generates conference registration information.
[0031] It should be noted that after the first microcontroller registers the conference terminal and generates a conference registration message, the conference registration message will be stored in a specified database, allowing the second microcontroller to read it. The second microcontroller obtains the conference terminal registration number in the conference registration information from the database, and imports the conference terminal registration number into the call server through the address book. The call server can call the conference terminal at any time based on the obtained conference terminal number.
[0032] Exemplarily, the first microcontroller and the conference terminal communicate using the Transport Layer Security (TLS) protocol. The conference terminal and the first microcontroller need to first establish communication based on TLS, and then the conference registration terminal sends a conference registration request message to the first microcontroller via TLS to register at the address where the first microcontroller is located. The first microcontroller returns a conference registration response message to the conference terminal to inform the conference terminal of the registration result. The specific method for the conference terminal and the first microcontroller to establish communication based on TLS can be: the conference terminal has a certificate loaded into the conference terminal, and the conference terminal certificate includes: CA certificate, the private key certificate MT pri and public key certificate MT pub The first microcontroller is preloaded with the certificate of the first microcontroller, which includes: CA certificate, private key certificate MCU1 pri and public key certificate MCU1 pubIt should be noted that the CA certificate is an electronic certificate used to encrypt and authenticate electronic information. It uses public key encryption to transmit and sign data. It is issued by an organization or individual to prove the legal identity of the authenticated party. The CA certificates of the first microcontroller, the second microcontroller and the conference terminal are all the same.
[0033] When the conference terminal and the first microcontroller need to communicate, the conference terminal establishes a TLS handshake connection to the first microcontroller according to the address of the first microcontroller. In the process of establishing the TLS handshake connection by the first microcontroller, it is necessary to verify each other's certificates, and store the certificate verification result locally, waiting to be read when the certificate verification result is needed.
[0034] S120: The second microcontroller sends a redirection indication message to the first microcontroller according to the conference registration information.
[0035] The second microcontroller MCU2 can be considered as a microcontroller responsible for conference calls. The first microcontroller MCU1 and the second microcontroller MCU2 can be deployed in the same server or in different servers. The redirection indication message can be understood as a message for indicating that a call request is redefined to another location, for example, it can be expressed as RedirectInd.
[0036] Specifically, the second microcontroller obtains the conference registration message generated by the first microcontroller for registering the conference terminal, generates a redirection indication message according to the obtained conference registration information, and sends the redirection indication message to the first microcontroller.
[0037] Exemplarily, the first microcontroller and the second microcontroller communicate with each other using the Transport Layer Security (TLS) protocol. The first microcontroller and the second microcontroller first establish communication based on TLS, and then the second microcontroller sends a redirection indication message to the first microcontroller through TLS. The specific method for the first microcontroller and the second microcontroller to establish communication based on TLS is basically the same as the specific method for the conference terminal and the first microcontroller to establish communication based on TLS. The certificate of the second microcontroller also needs to be loaded in the second microcontroller. The certificate of the second microcontroller includes: CA certificate, private key certificate MCU1 of the party. pri and public key certificate MCU1 pub The specific manner in which the first microcontroller and the second microcontroller establish communication based on TLS is not described in detail in the embodiment of the present invention.
[0038] S130: The first microcontroller forwards the redirection indication message to the conference terminal, so that the conference terminal notifies the second microcontroller to call the conference terminal to join the conference.
[0039] Specifically, after the first microcontroller finds the conference terminal locally based on the received redirection indication message, it forwards the redirection indication message to the conference terminal, so that the conference terminal notifies the second microcontroller that it is ready to call after receiving the redirection indication message. After receiving the notification, the second microcontroller calls the conference terminal to join the conference, thereby realizing that the second microcontroller calls the conference terminal registered on the first microcontroller to join the conference.
[0040] Exemplarily, the second microcontroller and the conference terminal communicate using the Transport Layer Security (TLS) protocol. The conference terminal and the second microcontroller need to first establish communication based on TLS, then the conference terminal notifies the second microcontroller that it is ready to call, and then the second microcontroller calls the conference terminal to join the conference. The specific manner in which the conference terminal and the second microcontroller establish communication based on TLS is basically the same as the specific manner in which the conference terminal and the first microcontroller establish communication based on TLS. The specific manner in which the conference terminal and the first microcontroller establish communication based on TLS is not described in detail in the embodiment of the present invention.
[0041] For example, the second microcontroller and the conference terminal can implement a conference call based on the Session Initiation Protocol SIP. The second microcontroller sends a conference call request message to the conference terminal, and the conference terminal replies with a conference confirmation message, such as a 200OK message, to the second microcontroller; the second microcontroller returns a conference call response message to the conference terminal.
[0042] The technical solution of the embodiment of the present application is to register the conference terminal for the conference through the first microcontroller and generate conference registration information; the second microcontroller sends a redirection indication message to the first microcontroller according to the conference registration information; the first microcontroller forwards the redirection indication message to the conference terminal, so that the conference terminal notifies the second microcontroller to call the conference terminal to join the conference; by deploying the conference registration and conference call on different servers, the second microcontroller calls the conference terminal registered on the first microcontroller to join the conference by means of conference call transfer, thereby reducing the pressure on a single server and increasing the number of concurrent conference accesses.
[0043] As an optional implementation of an embodiment of the present application, the first microcontroller is a microcontroller selected from a first microcontroller cluster based on a load balancing strategy for registering the conference terminal for a conference; the second microcontroller is a microcontroller selected from a second microcontroller cluster based on a load balancing strategy for making a conference call to the conference terminal.
[0044] Among them, the first microcontroller can be considered as a group of microcontrollers that are loosely or tightly connected and work together, and are set to perform conference registration. The second microcontroller cluster can be considered as a group of microcontrollers that are loosely or tightly connected and work together, and are set to perform conference calls. The first microcontroller cluster and the second microcontroller cluster are controlled and scheduled by software. The number of first microcontrollers in the first microcontroller cluster and the number of second microcontrollers in the second microcontroller cluster can be determined according to actual needs such as the number of concurrently accessed conference terminals, and the embodiments of the present invention do not impose any restrictions on this.
[0045] Specifically, when receiving a conference registration request initiated by a conference terminal, a first microcontroller is selected from the first microcontroller cluster based on a load balancing strategy for conference registration of the conference terminal. A second microcontroller is selected from the second microcontroller cluster based on a load balancing strategy for conference calling the conference terminal.
[0046] In this embodiment, a conference call transfer system composed of a first microcontroller cluster and a second microcontroller cluster is used to make conference calls to conference terminals, which can successfully connect a large number of conference terminals in a short period of time, further improving the concurrency and real-time performance of the conference, and is a great breakthrough compared to the restrictions on the number of conference terminals in traditional conferences.
[0047] As an optional implementation of the embodiment of the present application, the step of the second microcontroller sending a redirection indication message to the first microcontroller according to the conference registration information includes:
[0048] The second microcontroller parses the conference terminal registration address from the conference registration information, and sends a redirection indication message to the first microcontroller according to the conference terminal registration address.
[0049] The redirection indication message includes: the address of the second microcontroller, the conference terminal registration number and the conference call identification number. Exemplarily, the address of the second microcontroller can be an Internet Protocol Address (IP address). The conference terminal registration number can be considered as the number assigned to the conference terminal when registering, for example, an E164 number can be used. The E164 number is the number that the caller needs to call when the conference terminal is called, and the format is, for example, 960000001. The conference call identification number callid can be considered as a unique identifier used to identify the conference during the conference call transfer process. The redirection indication message can also include: an identity authentication enable field; if the identity authentication enable field indicates that the identity authentication is enabled, the second microcontroller needs to perform identity authentication before calling the conference terminal. If the identity authentication enable field indicates that the identity authentication is not enabled, the second microcontroller can directly call the conference terminal. Exemplarily, the redirection indication message can also include: an identity authentication mode field, indicating the identity authentication mode, such as one-way identity authentication or two-way identity authentication. Enabling the two-way identity authentication mode can improve the security of the conference call.
[0050] It is understandable that whether identity authentication needs to be enabled and the method of identity authentication can be set based on the configuration information, or identity authentication can be enabled or disabled by default. The embodiment of the present invention does not limit the setting method of whether identity authentication is enabled and the specific implementation method of identity authentication, which can be set based on actual needs. The method of identity authentication can be two-way identity authentication, the second microcontroller authenticates the conference terminal, or the conference terminal authenticates the second microcontroller.
[0051] Specifically, after obtaining the conference registration information, the second microcontroller parses the conference terminal registration number from the conference registration information, determines the conference terminal to be called based on the conference terminal registration number, and parses the conference terminal registration address from the conference registration information, establishes a connection with the first microcontroller that registers the conference terminal based on the conference terminal registration address, and sends a redirection indication message to the first microcontroller.
[0052] As an optional implementation of the embodiment of the present application, the step of the first microcontroller forwarding the redirection indication message to the conference terminal so that the conference terminal notifies the second microcontroller to call the conference terminal to join the conference includes:
[0053] S131. The first microcontroller locally searches for the conference terminal registration number included in the redirection indication message; if the conference terminal registration number is found, the redirection indication message is forwarded to the conference terminal based on the conference terminal registration number.
[0054] Specifically, after receiving the redirection indication message sent by the second microcontroller, the first microcontroller parses the conference terminal registration number from the redirection indication message and searches for the conference terminal registration number locally. If the conference terminal is successfully registered in the first microcontroller, the first microcontroller should be able to find the conference terminal registration number locally. The first microcontroller determines the conference terminal registration address of the conference terminal to be called based on the conference terminal registration number, and sends the redirection indication message to the conference terminal based on the conference terminal registration address. The purpose is to allow the conference terminal to actively establish a connection with the second microcontroller and wait for the call from the second microcontroller. If the conference terminal does not receive the redirection indication message, subsequent calls cannot be made smoothly.
[0055] In an optional implementation, after the first microcontroller locally searches for the conference terminal registration number included in the redirection indication message, the method further includes: the first microcontroller sends a redirection response message to the second microcontroller, wherein the redirection response message is used to inform the second microcontroller whether the conference terminal registration number is found.
[0056] The redirection response message may be considered as a message generated in response to the instruction of the redirection indication message, and the redirection response message may include: a search result; the search result may include: found or not found. In this embodiment, the redirection response message is used to inform the second microcontroller whether the first microcontroller has found the conference terminal registration number locally.
[0057] Specifically, the first microcontroller receives the redirection indication message sent by the second microcontroller and searches for the conference terminal registration number contained in the redirection indication message locally. Regardless of whether the conference terminal registration number is found, the first microcontroller sends a redirection response message to the second microcontroller to inform the second microcontroller whether the first microcontroller has found the conference terminal registration number. If the first microcontroller finds the conference terminal registration number locally, it means that the conference terminal has successfully registered on the first microcontroller; if the first microcontroller does not find the conference terminal registration number locally, it means that the conference terminal has not successfully registered on the first microcontroller, and the second microcontroller can terminate the call process.
[0058] It is understandable that regardless of whether the first microcontroller finds the conference terminal registration number locally, after the first microcontroller and the second microcontroller end the message interaction, the connection between the first microcontroller and the second microcontroller can be opened, and the connection needs to be re-established when the next information interaction is performed.
[0059] S132: The conference terminal sends a redirection call activation message to the second microcontroller based on the redirection indication message.
[0060] The redirected call activation message may be understood as a message for activating the second microcontroller to transfer a conference call. The redirected call activation message may include: a conference call identification number, which is used to enable the second microcontroller to distinguish calls from different conference terminals.
[0061] Specifically, after receiving the redirection indication message, the conference terminal parses the address of the second microcontroller and the conference call identification number from the redirection indication message, generates a redirection call activation message according to the conference call identification number, and sends the redirection call activation message to the second microcontroller based on the address of the second microcontroller.
[0062] S133: After receiving the redirected call activation message, the second microcontroller calls the conference terminal to join the conference according to the conference call identification number included in the redirected call activation message.
[0063] Specifically, after receiving the redirected call activation message sent by the conference terminal, the second microcontroller parses the conference call identification number from the redirected call activation message and prepares for the call, and calls the conference terminal according to the conference call identification number, so that the conference terminal joins the conference after receiving the call.
[0064] In an optional implementation manner, after receiving the redirected call activation message, the second microcontroller calls the conference terminal to join the conference according to the conference call identification number included in the redirected call activation message, including:
[0065] S1331. After receiving the redirected call activation message, the second microcontroller performs identity authentication with the conference terminal: the identity authentication includes: the second microcontroller, as the authenticating party, performs identity authentication on the conference terminal, as the authenticated party; and / or the conference terminal, as the authenticating party, performs identity authentication on the second microcontroller, as the authenticated party.
[0066] The authenticated party may be understood as the party whose identity is authenticated by others, and the authenticating party may be understood as the party that authenticates the identity of others.
[0067] In this embodiment, the identity authentication may include: the second microcontroller performs one-way identity authentication on the conference terminal, or the conference terminal performs one-way identity authentication on the second microcontroller; it may also be two-way identity authentication between the second microcontroller and the conference terminal.
[0068] Specifically, after receiving the redirected call activation message, the second microcontroller authenticates the identity of the conference terminal; and / or, the conference terminal sends a redirected call activation message to the second microcontroller, so that after receiving the redirected call activation message, the second microcontroller sends a redirected call activation message to the second microcontroller to authenticate the identity of the second microcontroller.
[0069] It can be understood that, in the process of the second microcontroller authenticating the conference terminal, the second microcontroller acts as the authenticator and the conference terminal acts as the authenticated party; in the process of the conference terminal authenticating the second microcontroller, the conference terminal acts as the authenticator and the second microcontroller acts as the authenticated party. In the process of two-way authentication, the process of the second microcontroller authenticating the conference terminal and the process of the conference terminal authenticating the second microcontroller are independent of each other and can be executed successively or simultaneously. This embodiment does not limit the order of two-way authentication.
[0070] S1332: If the identity authentication is successful, the second microcontroller will call the conference terminal to join the conference according to the conference call identification number included in the redirected call activation message.
[0071] Specifically, if the identity authentication is passed, the second microcontroller parses the conference call identification number from the received directional call activation message, and calls the conference call identification number so that the conference terminal receives the call and joins the conference.
[0072] The traditional conference encryption method using user name and password requires manual input of user name and password, which is not only inconvenient but also has the risk of account leakage. In this embodiment, the identity of both the second microcontroller and the conference terminal is authenticated by a two-way identity authentication mechanism. Compared with the traditional conference encryption method using user name and password, it has stronger security, reliability and convenience, and improves the security of conference calls. After the identity authentication is passed, the conference terminal is called to join the conference, which reduces the waste of resources of the conference call transfer system caused by invalid calls that have not been authenticated, and improves the execution efficiency of the conference call transfer system.
[0073] In an optional embodiment, the identity authentication includes: the authenticating party sending an identity authentication command message to the authenticated party;
[0074] After receiving the identity authentication command message, the authenticated party sends an identity authentication request message to the authenticating party;
[0075] After receiving the identity authentication request message, the authenticating party authenticates the identity of the authenticated party based on the identity authentication request message, and sends an identity authentication response message to the authenticated party.
[0076] The identity authentication command message can be understood as a command message for initiating identity authentication. The identity authentication request message can be understood as a message for requesting the other party to authenticate the identity of the other party. The identity authentication response message can be understood as a message for returning the identity authentication result to the other party.
[0077] Specifically, during the identity authentication process between the second microcontroller and the conference terminal, one party as the authenticating party sends an identity authentication command message to the other party as the authenticated party, indicating that the identity of the authenticated party needs to be authenticated. After receiving the identity authentication command message, the other party as the authenticated party sends an identity authentication request message to the one party as the authenticating party, indicating that the identity authentication of the authenticating party is requested. After receiving the identity authentication request message, the one party as the authenticating party parses the identity authentication request message, obtains the identity authentication information, authenticates the identity of the other party as the authenticated party based on the identity authentication information, and sends an identity authentication response message to the other party as the authenticated party, informing the authenticated party of the identity authentication result.
[0078] In a specific embodiment, Figure 2 This is a schematic diagram of message interaction in a conference call transfer method based on two-way identity authentication. Figure 2As shown, the conference call transfer method based on two-way identity authentication is applied to a conference call transfer system, and the conference call transfer system includes: a first microcontroller and a second microcontroller, and the object of the conference call transfer system is a conference terminal. The conference call transfer method based on two-way identity authentication specifically includes: four parts of execution process: 1. Conference registration process: the conference terminal sends a conference registration request message to the first microcontroller, so that the first microcontroller registers the conference terminal for the conference to generate conference registration information, and sends a conference registration response message to the conference terminal to inform the conference terminal of the conference registration solution result. 2. Redirection process: the first microcontroller generates a directional indication message according to the conference registration information generated by the first microcontroller, and sends a redirection indication message to the first microcontroller; redirection response and forwarding redirection indication: after receiving the redirection indication message, the first microcontroller forwards the redirection indication message to the conference terminal, and sends a redirection response message to the second microcontroller; after receiving the redirection indication message, the conference terminal sends a redirection call activation message to the second microcontroller. 3. Two-way identity authentication process: the identity authentication process of the conference terminal to the second microcontroller and the identity authentication process of the second microcontroller to the conference terminal. It should be noted that the two processes are independent of each other, regardless of the order, and can also be executed simultaneously. In the process of identity authentication of the conference terminal to the second microcontroller, the conference terminal acts as the authenticator and the second microcontroller acts as the authenticated party; in the process of identity authentication of the conference terminal by the second microcontroller, the second microcontroller acts as the authenticator and the conference terminal acts as the authenticated party. The message interaction process of the identity authentication of the authenticator to the authenticated party specifically includes: the authenticator sends an identity authentication command message to the authenticated party; the authenticated party returns an identity authentication request message to the authenticator, and the authenticator sends an identity authentication response message to the authenticated party; at this point, the identity authentication of the authenticater to the authenticated party is completed. 4. Conference call process. The second microcontroller sends a call request message to the conference terminal, the conference terminal returns a conference call confirmation message to the second microcontroller, and the second microcontroller sends a call answer message to the conference terminal. Finally, conference registration of the conference terminal is realized on the first microcontroller, and conference call transfer of the conference terminal is realized on the second microcontroller based on two-way identity authentication.
[0079] In another optional embodiment, in order to further improve the information security of conference call transfer, the identity authentication message transmitted during the identity authentication process is encrypted using a quantum key. The identity authentication message includes: the identity authentication command message, the identity authentication response message, and the identity authentication request message. The specific implementation method is that the identity authentication also includes:
[0080] 1) The authenticator applies for a quantum key private key and a quantum key public key from a quantum key machine, and sends the quantum key public key to the authenticated party;
[0081] Among them, the quantum key machine is a device for generating, distributing and managing quantum keys. In this embodiment, the quantum key machine can be deployed in the conference call transfer system or outside the conference call transfer system, allowing the conference call transfer system to apply for quantum keys. The quantum key private key and the quantum key public key can be considered as a pair of quantum keys assigned by the quantum key machine; the quantum key private key is used by the authenticating party to encrypt and decrypt messages, and the quantum key public key is sent to the authenticated party for the authenticated party to encrypt and decrypt messages.
[0082] Specifically, during the identity authentication process between the second microcontroller and the conference terminal, the authenticator applies for a pair of quantum keys from the quantum key machine, and the quantum keys include: a quantum key private key and a quantum key public key. During the identity authentication process between the second microcontroller and the conference terminal, both the authenticator and the authenticated party need to use their own quantum keys to encrypt messages before sending them, and need to use their own quantum keys to decrypt messages after receiving them. The authenticator has its own quantum key private key, and the authenticated party has its own quantum key public key.
[0083] In a specific embodiment, during the process of the second microcontroller authenticating the conference terminal, that is, when the second microcontroller acts as the authenticator and the conference terminal acts as the authenticated party, the second microcontroller has its own quantum key private key, such as QtMCU2 pri , the conference terminal has the quantum key public key sent by the second microcontroller, such as QtMCU2 pub In the process of the conference terminal authenticating the second microcontroller, the conference terminal acts as the authenticator and the second microcontroller acts as the authenticated party. The conference terminal has its own quantum key private key, such as QtMT pri , the second microcontroller has the quantum key public key sent by the conference terminal, such as QtMT pub .
[0084] 2) Before sending a first identity authentication message to the authenticated party, the authenticating party uses the quantum key private key to encrypt the first identity authentication message; after receiving the first identity authentication message sent by the authenticating party, the authenticated party uses the quantum key public key to decrypt the first identity authentication message.
[0085] The first identity authentication message can be understood as a message sent by the authenticating party to the authenticated party during the identity authentication process between the second microcontroller and the conference terminal. The first identity authentication message includes: the identity authentication command message and the identity authentication response message.
[0086] Specifically, before sending a first identity authentication message to the authenticated party, the authenticating party uses its own quantum key private key to encrypt the first identity authentication message; then the first identity authentication message is sent to the authenticated party. After receiving the first identity authentication message sent by the authenticating party, the authenticated party uses its own quantum key public key of the authenticating party to decrypt the first identity authentication message, and then parses and processes the first identity authentication message.
[0087] 3) Before the authenticated party sends the second identity authentication message to the authenticating party, the authenticated party uses the quantum key public key to encrypt the second identity authentication message; after receiving the second identity authentication message sent by the authenticated party, the authenticating party uses the quantum key private key to decrypt the second identity authentication message.
[0088] The second identity authentication message can be understood as a message sent by the authenticated party to the authenticating party during the identity authentication process between the second microcontroller and the conference terminal. The second identity authentication message includes: the identity authentication request message.
[0089] Specifically, before the authenticated party sends the second identity authentication message to the authenticating party, the authenticated party uses the authenticating party's quantum key public key to encrypt the second identity authentication message; then the second identity authentication message is sent to the authenticating party. After receiving the second identity authentication message sent by the authenticated party, the authenticating party uses its own quantum key private key to decrypt the second identity authentication message, and then parses and processes the second identity authentication message.
[0090] This embodiment uses quantum keys to encrypt the identity authentication messages transmitted during the identity authentication process, ensuring that the transmitted data is not tampered with, further improving the transmission security of the identity authentication messages, and thus further improving the information security of conference call transfers.
[0091] In a specific example, Figure 3 The schematic diagram of the principle of a conference call transfer process based on quantum key and two-way identity authentication provided in this embodiment. Figure 3As shown, the conference call transfer process based on quantum key and two-way identity authentication may specifically include: 1. Conference registration: the conference terminal sends a conference registration request message to the first microcontroller, so that the first microcontroller registers the conference terminal and generates conference registration information; 2. Redirection indication: the first microcontroller generates a directional indication message according to the conference registration information generated by the first microcontroller, and sends a redirection indication message to the first microcontroller; 3. Redirection response and forwarding redirection indication: after receiving the redirection indication message, the first microcontroller forwards the redirection indication message to the conference terminal, and sends a redirection response message to the second microcontroller; it should be noted that the redirection response and forwarding redirection indication processes can be performed in no particular order or at the same time; 4. Redirection call activation: after receiving the redirection indication message, the conference terminal sends a redirection call activation message to the second microcontroller; 5-9. Two-way identity authentication between the conference terminal and the second microcontroller: it should be noted that the identity authentication process of the conference terminal to the second microcontroller and the identity authentication process of the second microcontroller to the conference terminal are independent of each other, and can be performed in no particular order or at the same time. In the process of the conference terminal authenticating the second microcontroller, the conference terminal acts as the authenticator and the second microcontroller acts as the authenticated party; in the process of the second microcontroller authenticating the conference terminal, the second microcontroller acts as the authenticator and the conference terminal acts as the authenticated party. The authentication process of the authenticator authenticating the authenticated party specifically includes: 5. Applying for quantum key: the authenticator requests the quantum key machine to obtain a pair of quantum keys; 6. Authentication command: the authenticator generates an authentication command message, and encrypts the authentication command message with the quantum key private key and sends it to the authenticated party; 7. Authentication request: the authenticated party generates an authentication request message after decrypting the received authentication command message based on the quantum key public key, and encrypts the authentication request message based on the quantum key public key and sends it to the authenticator; 8. Authentication response: the authenticator generates an authentication response message after decrypting the received authentication request message based on the quantum key private key, and encrypts the authentication response message based on the quantum key private key and sends it to the authenticated party; at this point, the authentication of the authenticated party by the authenticator is completed. 10. The second microcontroller makes a conference call to the conference terminal. Finally, conference registration of the conference terminal is achieved on the first microcontroller, and conference call transfer of the conference terminal is performed on the second microcontroller based on two-way identity authentication and quantum key.
[0092] Optionally, the identity authentication command message includes: a message identification number, an identity authentication summary algorithm, a message sending device type, a message sequence number, a conference number, a conference terminal registration number, a conference call identification number, and a message summary;
[0093] The identity authentication request message includes: a message identification number, a message sending device type, a message sequence number, a conference number, a conference terminal registration number, a conference call identification number, identity authentication information, and a message summary; the identity authentication information includes: a user name and password assigned by the first microcontroller to the conference terminal, and a quantum authentication code assigned by a quantum key machine;
[0094] The identity authentication response message includes: a message identification number, a message sending device type, a message sequence number, a conference number, a conference terminal registration number, a conference call identification number, an identity authentication result and a message summary.
[0095] Among them, in the identity authentication process between the second microcontroller and the conference terminal, all interactive identity authentication messages include a message identification number, a message sending device type, a message sequence number, a conference number, a conference terminal registration number, a conference call identification number and a message digest. The message identification number can be understood as a unique identifier for distinguishing identity authentication messages, such as a message ID. The message sequence number can be understood as a sequence number assigned based on the order of message generation or transmission, generally a natural number sequence, such as 1, 2, 3, .... The message sending device type can be understood as the type of device that sends information, which can be, for example, the second microcontroller MCU2 or the conference terminal MT in the identity authentication process between the second microcontroller and the conference terminal. The conference number can be understood as the number assigned when creating a conference, which is used to identify different conferences. The message digest can be understood as converting a message of any length into a short message of a fixed length, which is used to verify the integrity and correctness of the message, for example, it can be a hash function. The conference call identification number can be understood as the identification number of the call in the conference, which is used to distinguish different call processes in the conference.
[0096] The identity authentication command message also includes: an identity authentication digest algorithm. The identity authentication digest algorithm can be understood as a digest algorithm specified by the authenticator, such as an SM2 algorithm or an SM3 algorithm. Figure 4 A data frame structure diagram of an identity authentication command message in a conference call transfer method provided in an embodiment of the present application. Figure 4 In the field, TerAuthCmd ID indicates the message identification number of the authentication command message, SM3 indicates that the authentication digest algorithm used is SM3, and SM2 or other algorithms can also be specified; Role indicates the type of device sending the message, Seq indicates the message sequence number, ConfID indicates the conference number, E164 indicates the conference terminal registration number, Callid indicates the conference call number, and Hash(Data) indicates the message digest, and a hash algorithm can be used.
[0097] The identity authentication request message also includes: identity authentication information. The identity authentication information can be understood as the identity information that needs to be authenticated. The identity authentication information includes: the user name and password assigned by the first microcontroller to the conference terminal, and the quantum authentication code assigned by the quantum key machine. The quantum authentication code can be understood as the authentication code assigned by the quantum key to each message sent by the message sender, which is used to calculate the message digest. The quantum authentication code assigned by the quantum key machine to the second microcontroller MCU2 can be expressed as QtCode, for example. MCU2 ; The quantum authentication code assigned by the quantum key machine to the conference terminal MT can be expressed as QtCode MT It should be noted that the quantum authentication code contained in each identity authentication request message sent is different. Figure 5 A data frame structure diagram of an identity authentication request message in a conference call transfer method provided in an embodiment of the present application. Figure 5 In the data frame, TerAuthReq ID indicates the message identification number of the identity authentication request message, username indicates the user name, password indicates the password, and QtAuthCode indicates the quantum authentication code; the other information contained in the data frame is the same as Figure 4 The same is not repeated here.
[0098] The identity authentication response message also includes: an identity authentication result. The identity authentication result is used to indicate whether the identity authentication is passed, and may include: identity authentication passed and identity authentication failed. Figure 6 A data frame structure diagram of an identity authentication response message in a conference call transfer method provided in an embodiment of the present application. Figure 6 The TerAuthRsp ID in the data frame indicates the message identification number of the authentication response message. The other information contained in the data frame is the same as Figure 4 The same is not repeated here.
[0099] Figure 7 A schematic diagram of the structure of a call transfer system provided in an embodiment of the present application. Figure 7 As shown, the system includes: a first microcontroller 710 for conference registration and a second microcontroller 720 for conference call; wherein,
[0100] The first microcontroller 710 is used to register the conference terminal for the conference and generate conference registration information;
[0101] The second microcontroller 720 is used to send a redirection indication message to the first microcontroller according to the conference registration information;
[0102] The first microcontroller 710 is further configured to forward the redirection indication message to the conference terminal, so that the conference terminal notifies the second microcontroller to call the conference terminal to join the conference.
[0103] Optionally, the second microcontroller is used to parse the conference terminal registration address from the conference registration information, and send a redirection indication message to the first microcontroller according to the conference terminal registration address; wherein the redirection indication message includes: the address of the second microcontroller, the conference terminal registration number, and the conference call identification number.
[0104] Optionally, the first microcontroller 710 is configured to locally search for the conference terminal registration number contained in the redirection indication message; if the conference terminal registration number is found, forward the redirection indication message to the conference terminal based on the conference terminal registration number;
[0105] The conference terminal 730 is used for the conference terminal to send a redirection call activation message to the second microcontroller based on the redirection indication message;
[0106] The second microcontroller 720 is configured to, after receiving the redirected call activation message, call the conference terminal to join the conference according to the conference call identification number included in the redirected call activation message.
[0107] Optionally, the first microcontroller 710 is further used for:
[0108] A redirection response message is sent to the second microcontroller, where the redirection response message is used to inform the second microcontroller whether the conference terminal registration number is found.
[0109] Optionally, the second microcontroller 720 is further used for:
[0110] After receiving the redirected call activation message, identity authentication is performed with the conference terminal: if the identity authentication is successful, the conference terminal is called to join the conference according to the conference call identification number included in the redirected call activation message;
[0111] The identity authentication includes: the second microcontroller as the authenticating party performs identity authentication on the conference terminal as the authenticated party; and / or the conference terminal as the authenticating party performs identity authentication on the second microcontroller as the authenticated party.
[0112] Optionally, the identity authentication includes:
[0113] The authenticating party sends an identity authentication command message to the authenticating party;
[0114] After receiving the identity authentication command message, the authenticated party sends an identity authentication request message to the authenticating party;
[0115] After receiving the identity authentication request message, the authenticating party authenticates the identity of the authenticated party based on the identity authentication request message, and sends an identity authentication response message to the authenticated party.
[0116] Optionally, the identity authentication further includes:
[0117] The authenticator applies for a quantum key private key and a quantum key public key from a quantum key machine, and sends the quantum key public key to the authenticated party;
[0118] Before the authenticator sends a first identity authentication message to the authenticated party, the authenticator uses the quantum key private key to encrypt the first identity authentication message; after receiving the first identity authentication message sent by the authenticator, the authenticated party uses the quantum key public key to decrypt the first identity authentication message; wherein the first identity authentication message includes: the identity authentication command message and the identity authentication response message;
[0119] Before the authenticated party sends a second identity authentication message to the authenticating party, the authenticated party uses the quantum key public key to encrypt the second identity authentication message; after receiving the second identity authentication message sent by the authenticated party, the authenticating party uses the quantum key private key to decrypt the second identity authentication message; wherein the second identity authentication message includes: the identity authentication request message.
[0120] Optionally, the identity authentication command message includes: a message identification number, an identity authentication summary algorithm, a message sending device type, a message sequence number, a conference number, a conference terminal registration number, a conference call identification number, and a message summary;
[0121] The identity authentication request message includes: a message identification number, a message sending device type, a message sequence number, a conference number, a conference terminal registration number, a conference call identification number, identity authentication information, and a message summary; the identity authentication information includes: a user name and password assigned by the first microcontroller to the conference terminal, and a quantum authentication code assigned by a quantum key machine;
[0122] The identity authentication response message includes: a message identification number, a message sending device type, a message sequence number, a conference number, a conference terminal registration number, a conference call identification number, an identity authentication result and a message summary.
[0123] Optionally, the first microcontroller is a microcontroller selected from a first microcontroller cluster based on a load balancing strategy and used to perform conference registration for the conference terminal;
[0124] The second microcontroller is a microcontroller selected from a second microcontroller cluster based on a load balancing strategy and used to make a conference call to the conference terminal.
[0125] The conference call transfer system provided in the embodiment of the present application can execute the conference call transfer method provided in any embodiment of the present application, and has the corresponding functional modules and beneficial effects of the execution method.
[0126] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this application can be executed in parallel, sequentially or in different orders, as long as the expected results of the technical solution of this application can be achieved, and this document is not limited here.
[0127] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.
Claims
1. A conference call transfer method, characterized in that: The invention is applied to a conference call transfer system for transferring calls to conference terminals, the conference call transfer system comprising: a first microcontroller for conference registration and a second microcontroller for conference calls, and the method comprises: The first microcontroller registers the conference terminal for the conference and generates conference registration information; The second microcontroller sends a redirection indication message to the first microcontroller according to the conference registration information; The first microcontroller forwards the redirection indication message to the conference terminal, so that the conference terminal notifies the second microcontroller to call the conference terminal to join the conference.
2. The conference call transfer method according to claim 1, characterized in that: The step of the second microcontroller sending a redirection indication message to the first microcontroller according to the conference registration information comprises: The second microcontroller parses the conference terminal registration address from the conference registration information, and sends a redirection indication message to the first microcontroller according to the conference terminal registration address; The redirection indication message includes: the address of the second microcontroller, the conference terminal registration number, and the conference call identification number.
3. The conference call transfer method according to claim 1, characterized in that: The step of the first microcontroller forwarding the redirection indication message to the conference terminal so that the conference terminal notifies the second microcontroller to call the conference terminal to join the conference includes: The first microcontroller locally searches for the conference terminal registration number contained in the redirection indication message; if the conference terminal registration number is found, the redirection indication message is forwarded to the conference terminal based on the conference terminal registration number; The conference terminal sends a redirection call activation message to the second microcontroller based on the redirection indication message; After receiving the redirected call activation message, the second microcontroller calls the conference terminal to join the conference according to the conference call identification number included in the redirected call activation message.
4. The conference call transfer method according to claim 3, characterized in that: Also includes: The first microcontroller sends a redirection response message to the second microcontroller, where the redirection response message is used to inform the second microcontroller whether the conference terminal registration number is found.
5. The conference call transfer method according to claim 3, characterized in that: After receiving the redirected call activation message, the second microcontroller calls the conference terminal to join the conference according to the conference call identification number contained in the redirected call activation message, including: After receiving the redirected call activation message, the second microcontroller performs identity authentication with the conference terminal: if the identity authentication is successful, the conference terminal is called to join the conference according to the conference call identification number included in the redirected call activation message; The identity authentication includes: the second microcontroller as the authenticating party performs identity authentication on the conference terminal as the authenticated party; and / or the conference terminal as the authenticating party performs identity authentication on the second microcontroller as the authenticated party.
6. The conference call transfer method according to claim 5, characterized in that: The identity authentication includes: The authenticating party sends an identity authentication command message to the authenticating party; After receiving the identity authentication command message, the authenticated party sends an identity authentication request message to the authenticating party; After receiving the identity authentication request message, the authenticating party authenticates the identity of the authenticated party based on the identity authentication request message, and sends an identity authentication response message to the authenticated party.
7. The conference call transfer method according to claim 6, characterized in that: The identity authentication also includes: The authenticator applies for a quantum key private key and a quantum key public key from a quantum key machine, and sends the quantum key public key to the authenticated party; Before the authenticator sends a first identity authentication message to the authenticated party, the authenticator uses the quantum key private key to encrypt the first identity authentication message; after receiving the first identity authentication message sent by the authenticator, the authenticated party uses the quantum key public key to decrypt the first identity authentication message; wherein the first identity authentication message includes: the identity authentication command message and the identity authentication response message; Before the authenticated party sends a second identity authentication message to the authenticating party, the authenticated party uses the quantum key public key to encrypt the second identity authentication message; after receiving the second identity authentication message sent by the authenticated party, the authenticating party uses the quantum key private key to decrypt the second identity authentication message; wherein the second identity authentication message includes: the identity authentication request message.
8. The method according to claim 7, characterized in that The identity authentication command message includes: a message identification number, an identity authentication summary algorithm, a message sending device type, a message sequence number, a conference number, a conference terminal registration number, a conference call identification number, and a message summary; The identity authentication request message includes: a message identification number, a message sending device type, a message sequence number, a conference number, a conference terminal registration number, a conference call identification number, identity authentication information, and a message summary; the identity authentication information includes: a user name and password assigned by the first microcontroller to the conference terminal, and a quantum authentication code assigned by a quantum key machine; The identity authentication response message includes: a message identification number, a message sending device type, a message sequence number, a conference number, a conference terminal registration number, a conference call identification number, an identity authentication result and a message summary.
9. The conference call transfer method according to claim 1, characterized in that: The first microcontroller is a microcontroller selected from a first microcontroller cluster based on a load balancing strategy and used for registering the conference terminal for a conference; The second microcontroller is a microcontroller selected from a second microcontroller cluster based on a load balancing strategy and used to make a conference call to the conference terminal.
10. A conference call transfer system, characterized in that: include: A first microcontroller for conference registration and a second microcontroller for conference calling; wherein, The first microcontroller is used to register the conference terminal for the conference and generate conference registration information; The second microcontroller is used for sending a redirection indication message to the first microcontroller according to the conference registration information; The first microcontroller is further configured to notify the second microcontroller to call the conference terminal to join the conference based on the redirection indication message.