Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
Fig. 1 is a schematic diagram of a system for replicating and sharing multicast table configuration information according to an embodiment of the present application. As shown in fig. 1, the system includes a client, a service server (back-end-server), a signaling server (signal-server), and an underlying server (engine-server).
According to some embodiments, the multicast table is actually a component responsible for different services in the process of setting up a scene, and performs connection assembly. For example, an on-demand INPUT signal source seen on a cloud director client consists of an INPUT component and an OUTPUT preview OUTPUT component; for another example, a four-split mixed-stream picture with subtitles seen on a client consists of 4 INPUT components, a mixed-stream ME component, a subtitle CG component and an OUTPUT preview OUTPUT component.
The switching of the live broadcast scene of the cloud guide platform is realized by continuously changing the connection relation among related components. The client is responsible for sending the creation component, maintaining the connection relation between the components, and previewing the audio and video signals processed by the cloud service (comprising the signaling server and the bottom server). The cloud service creates a real component instance according to the instruction on the client, and performs decoding, mixed streaming, rendering, switching and encoding plug streaming of the input source signals.
According to some embodiments, each step of operation on the client interacts with the signaling server in real time, and the signaling server maintains a configuration information for each running multicast table, where the configuration information may be a configuration detail data structure (switchdetailinfo), and the configuration detail data structure may be constructed by a component connection management algorithm, and records the input source, layout, subtitle, output, PVW, PGM component details of the multicast table, configuration information of a program guide, a tuning table, a transition special effect, and connection relations between components, etc. The signaling server pushes the configuration detail data structure to the service server at regular time; after the guide station stops running, the service server stores the latest configuration detail data structure in storage.
According to some embodiments, a director is created, configuration information is generated for the director, then the director is stopped, when the client re-enables the director again, the client sends a request for recovering the director, for example, an offline recovery director request, to a signaling server, the signaling server sends an instruction for requesting the configuration information of the current director to a service server, after the service server obtains the configuration information of the current director, reverse analysis is performed according to the component connection relation, components corresponding to the configuration information are re-created, and the connection relation between the components is re-established. After the reverse parsing is finished, the signaling server also sends the configuration information of the current guiding and broadcasting station to the client, so that the client restores the scene according to the configuration information, and in the process of restoring the component, the client needs to restore the streaming rendering of the UI (User Interface) display part and the preview picture, thereby restoring the scene before the guiding and broadcasting station stops. Specifically, after receiving a reply of a request for recovering a current multicast table, the client displays information such as an input source, a layout, a subtitle and the like on an interface according to configuration information of the current multicast table in the reply, and after receiving the reply of the request for recovering the current multicast table, the client establishes connection with an RTC (Real-Time Communication ) conference platform (for example, 100RTC conference platform), for example, WS (Web Socket) long connection, joins an RTC room, searches an audio and video stream corresponding to a preview picture of each small window through a component ID corresponding to the small picture, and performs pull stream rendering.
According to some embodiments, each multicast table has a unique identifier or unique ID (Identity), which may be referred to as a SwitcherId; each component has a component identification or component ID, which may be referred to as ComponentId. The component identification or component ID under the same multicast table is not duplicated.
According to some embodiments, a new director is created under the same account of the client, and it is desirable that the configuration information of the new director be the same as the configuration information of the existing director. To this end, the client sends a request to the service server to copy the configuration information of the existing director (e.g., the first director), for example, a copied HTTP (Hyper Text Transfer Protocol ) request via an API (Application Programming Interface, application programming interface) of the service server. After receiving the copy request, the service server first creates a new director, for example, a second director; generating a new set of configuration information for a second multicast guiding station according to the configuration information of the first multicast guiding station, wherein the configuration information of the second multicast guiding station is the same as the configuration information of the first multicast guiding station; and then, the service server puts the second guiding and broadcasting station into a guiding and broadcasting station list and stores the second guiding and broadcasting station in a warehouse. The service server sends information of the second guiding and broadcasting station to the client, including the identification of the second guiding and broadcasting station, and the client sends a request for recovering the second guiding and broadcasting station to the signaling server; the signaling server sends an instruction for requesting the configuration information of the second multicast table to the service server, the signaling server receives the configuration information of the second multicast table and sends a Response (Response) including the configuration information of the second multicast table to the client, and the signaling server restores the corresponding scene according to the configuration information of the second multicast table, for example, reversely analyzes the configuration information, re-creates all components, re-establishes the connection relationship between the components, and the bottom server creates a component instance of the second multicast table to perform operations such as audio and video processing, mixed stream synthesis, stream pushing and the like. In the process of restoring the component according to the configuration information of the second guiding platform, the client needs to restore the UI display part and the pull stream rendering of the preview picture, and the restored scene comprises the scene before the first guiding platform stops. Specifically, after receiving a reply of a request for recovering the second multicast table, the client displays information such as an input source, a layout, a subtitle and the like on the interface according to configuration information of the second multicast table in the reply, and after receiving the reply of the request for recovering the second multicast table, the client establishes connection with the RTC conference platform, such as WS long connection, joins the RTC room, searches an audio and video stream corresponding to a preview picture of each small window through a component ID corresponding to the small picture, and performs pull stream rendering.
According to some embodiments, a new director is created under one account (e.g., a second account) of the client, and it is desirable that the configuration information of the new director be the same as the configuration information of an existing director under a different account (e.g., a first account). To this end, the client sends a create director instruction to the traffic server, wherein the create director instruction contains information of an existing director (e.g., a first director), such as an identification of the first director. After receiving the request for creating the director, the service server creates a new director, for example, a third director; generating a new set of configuration information for a third multicast guiding station according to the configuration information of the first multicast guiding station, wherein the configuration information of the third multicast guiding station is the same as the configuration information of the first multicast guiding station; and then, the service server puts the third guiding and broadcasting station into a guiding and broadcasting station list and stores the third guiding and broadcasting station in a warehouse. The service server sends information of the third guiding and broadcasting station to the client, including the identification of the third guiding and broadcasting station, and the client sends a request for recovering the third guiding and broadcasting station to the signaling server; the signaling server sends an instruction for requesting the configuration information of the third multicast station to the service server, the signaling server receives the configuration information of the third multicast station and sends a reply comprising the configuration information of the third multicast station to the client, and the signaling server restores the corresponding scene according to the configuration information of the third multicast station, for example, reversely analyzes the configuration information, re-creates all components, re-establishes the connection relationship between the components, and the bottom server creates a third multicast station component instance to perform operations such as audio and video processing, mixed stream synthesis, push stream and the like. In the process of restoring the component according to the configuration information of the third multicast table, the client needs to restore the UI display part and the pull stream rendering of the preview picture, and the restored scene includes the scene before the first multicast table stops. Specifically, after receiving a reply of a request for recovering the third multicast table, the client displays information such as an input source, a layout, a subtitle and the like on the interface according to configuration information of the third multicast table in the reply, and after receiving the reply of the request for recovering the third multicast table, the client establishes connection with the RTC conference platform, such as WS long connection, joins the RTC room, searches an audio and video stream corresponding to a preview picture of each small window through a component ID corresponding to the small picture, and performs pull stream rendering.
According to other embodiments, a new director is created under one account (e.g., a second account) of the client, where it is desired that the configuration information of the new director be the same as the configuration information of an existing director under a different account (e.g., a first account). After the first account corresponding multicast table (first multicast table) is created, the client of the first account sends a request for sharing the first multicast table to the service server, where the request may carry the representation and verification code of the first multicast table and the validity period information thereof. According to some embodiments, a user at a client of a first account clicks a share button of a first multicast table operating function area, and a validity period (e.g., within 1 minute) of the multicast table being added by other accounts is set in a share popup. After clicking, a request for sharing the first guiding and broadcasting station is sent to the service server, wherein the request carries the identification and verification code of the first guiding and broadcasting station and the validity period information of the first guiding and broadcasting station.
After receiving the request of the first account sharing guide table, the service server generates a verification code with timeliness, stores the verification code into the configuration information of the first guide table, and returns the verification code to the client of the first account.
After receiving the verification code returned by the service server, the client of the first account shares the identification of the first guide table and the verification code according to the specified rule, for example, generates a shared document, and automatically copies the shared document to the clipboard.
And the client of the first account sends the identification and the verification code file of the first multicast table to the second user.
The second user logs in the client, clicks the add cross-account guide table button, inputs the identification and verification code of the first guide table after adding the cross-account guide table window, and sends an instruction for creating the guide table to the service server after clicking to confirm, wherein the instruction carries the identification and verification code of the first guide table.
After receiving the instruction of creating the guiding and broadcasting station at the client of the second account, the service server checks the identification of the first guiding and broadcasting station and the validity of the verification code information, for example, whether the verification code corresponds to the identification of the first guiding and broadcasting station or not, and whether the verification code exceeds the set validity period or not.
And if the verification is not passed, returning to the second user to create the instruction failure information of the guide station, wherein the information comprises a request error code and error description information.
Checking passes, firstly creating a new guide table, such as a third guide table; generating a new set of configuration information for a third multicast guiding station according to the configuration information of the first multicast guiding station, wherein the configuration information of the third multicast guiding station is the same as the configuration information of the first multicast guiding station; and then, the service server puts the third guiding and broadcasting station into a guiding and broadcasting station list and stores the third guiding and broadcasting station in a warehouse. And the service server sends information of the third guiding and broadcasting station to the client side of the second account, wherein the information comprises the identification of the third guiding and broadcasting station. Then, the client sends a request for recovering the third multicast table to the signaling server; the signaling server sends an instruction for requesting the configuration information of the third multicast station to the service server, the signaling server receives the configuration information of the third multicast station and sends a reply comprising the configuration information of the third multicast station to the client, and the signaling server restores the corresponding scene according to the configuration information of the third multicast station, for example, reversely analyzes the configuration information, re-creates all components, re-establishes the connection relationship between the components, and the bottom server creates a third multicast station component instance to perform operations such as audio and video processing, mixed stream synthesis, push stream and the like. In the process of restoring the component according to the configuration information of the third multicast table, the client needs to restore the UI display part and the pull stream rendering of the preview picture, and the restored scene includes the scene before the first multicast table stops. Specifically, after receiving a reply of a request for recovering the third multicast table, the client displays information such as an input source, a layout, a subtitle and the like on the interface according to configuration information of the third multicast table in the reply, and after receiving the reply of the request for recovering the third multicast table, the client establishes connection with the RTC conference platform, such as WS long connection, joins the RTC room, searches an audio and video stream corresponding to a preview picture of each small window through a component ID corresponding to the small picture, and performs pull stream rendering.
Fig. 2 (a) is a schematic diagram of a system for sharing configuration information of a multicast table according to one embodiment of the present application. As shown in FIG. 2 (a), the client corresponds to two accounts, user A (user-A) and user B (user-B). In the client, the user a firstly sends a request for creating the director AS1 to the service server, then the user a operates and configures the director AS1, each step of operation on the client interacts with the signaling server in real time, the signaling server maintains a configuration information for each running director, and the configuration information can be a configuration detail data structure (switchdetailinfo), and records the detailed information of each component of the director, such AS an input source, a layout, a subtitle, an output, PVW, PGM, a program list, a tuning table, configuration information of a transition special effect, a connection relation among each component, and the like. The signaling server can push the configuration information of the guide broadcasting station to the service server at regular time; after the guide station stops running, the service server stores configuration information of the guide station in storage. When the user a shares the director AS1, the service server assigns a unique identifier, which may be a serial number, to the director AS 1. The user a shares the unique identification of the director AS1 to the user B. When the user B wishes to establish a new director station consistent with the configuration of the director station AS1 of the user a, an instruction to create the director station may be sent to the service server, where the instruction to create the director station includes information about the director station AS1, such AS a unique identification of the director station AS 1. After receiving the instruction for creating the guiding and broadcasting station, the service server creates a new guiding and broadcasting station BS1; generating a new set of configuration information for the guide station BS1 according to the configuration information of the guide station AS1, wherein the configuration information of the guide station BS1 is the same AS the configuration information of the guide station AS 1; then, the service server puts the multicast station BS1 into the multicast station list and puts it into storage. The service server sends information of the guiding and broadcasting station BS1 to the client, wherein the information comprises a unique identifier of the guiding and broadcasting station, and the client sends a request for recovering the guiding and broadcasting station BS1 to the signaling server; the signaling server sends an instruction for requesting the configuration information of the director BS1 to the service server, the signaling server receives the configuration information of the director BS1 and sends a reply including the configuration information of the director BS1 to the client, and the signaling server restores the corresponding scene according to the configuration information of the director BS1, for example, reversely analyzes the configuration information, re-creates all components, re-establishes the connection relationship between the components, and the bottom server creates a component instance of the director BS1 to perform operations such as audio and video processing, mixed stream synthesis, push stream and the like. In the process of restoring the component according to the configuration information of the multicast station BS1, the client needs to restore the UI display part and the pull stream rendering of the preview screen, and the restored scene is the scene before the multicast station AS1 stops. Specifically, after receiving a reply of a request for recovering the director BS1, the client displays information such as an input source, a layout, a subtitle and the like on an interface according to configuration information of the director BS1 in the reply, and after receiving the reply of the request for recovering the director BS1, the client establishes a connection with the RTC conference platform, for example, WS long connection, joins the RTC room, searches an audio/video stream corresponding to a preview picture of each small window through a component ID corresponding to the small picture, and performs pull stream rendering.
Fig. 2 (b) is a schematic diagram of a system for sharing configuration information of a multicast table according to another embodiment of the present application. Compared with fig. 2 (a), the difference is that in the process of sharing the configuration information of the multicast table shown in fig. 2 (B), the process of generating the verification code of the multicast table AS1 and verifying the verification code of the multicast table AS1 by the service server is added, and the user B sends the instruction for creating the multicast table to the service server, which includes the verification code information verification code-A1 in addition to the information including the multicast table AS 1.
According to the system for copying and sharing configuration information of a multicast table shown in fig. 1, the present application also provides a method for copying and sharing configuration information of a multicast table, as shown in fig. 3, fig. 4, and fig. 5.
Fig. 3 is a flowchart of a method performed by a client to replicate and share podcast configuration information in accordance with an embodiment of the present application.
According to one aspect, for the case where the newly created director replicates the existing director configuration under the same account, the method as shown in fig. 3 includes the steps of:
step S301, a request for copying configuration information of a first guiding and broadcasting station is sent to a service server, wherein the configuration information of the first guiding and broadcasting station is generated according to the operation of a client in the interaction process of a signaling server and the client under a first account;
Step S302, receiving identification information of a second guiding and broadcasting station from the service server, wherein the second guiding and broadcasting station is created by the service server according to the request for copying the configuration information of the first guiding and broadcasting station;
step S303, a request for recovering the second guiding broadcast station is sent to the signaling server;
step S304, receiving configuration information of the second multicast guiding station from the signaling server, wherein the configuration information of the second multicast guiding station is the same as the configuration information of the first multicast guiding station;
step S305, restoring the corresponding scene according to the configuration information of the second multicast table.
According to another aspect, for the situation that the existing multicast table is restored to its configuration after stopping the existing multicast table under the same account, the method shown in fig. 3 includes the following steps:
step S306, under the condition of recovering the first guiding and broadcasting station again, a request for recovering the first guiding and broadcasting station is sent to the signaling server;
step S307, receiving configuration information of the first multicast table from the signaling server;
step S308, restoring the scene before stopping the first guiding platform according to the configuration information of the first guiding platform.
According to yet another aspect, for a different account, sharing an existing under-account director configuration to another under-account director, the method as shown in fig. 3 includes the steps of:
Step S309, under the condition that the second account is logged in, sending an instruction for creating the guide table to the service server, wherein the instruction for creating the guide table comprises identification information of the first guide table;
step S310, receiving identification information of a third guiding and broadcasting station from the service server, wherein the third guiding and broadcasting station is created by the service server according to the instruction of creating the guiding and broadcasting station;
step S311, a request for recovering the third guiding broadcast station is sent to the signaling server;
step S312, receiving the configuration information of the third multicast guiding station from the signaling server, wherein the configuration information of the third multicast guiding station is the same as the configuration information of the first multicast guiding station;
step S313, restoring the corresponding scene according to the configuration information of the third multicast table.
Fig. 4 is a flowchart of a method of replicating and sharing multicast table configuration information performed by a service server according to an embodiment of the present application.
According to one aspect, for the case where the newly created director replicates the existing director configuration under the same account, the method as shown in fig. 4 includes the steps of:
step S401, receiving configuration information of a first multicast table of a first account from a signaling server, wherein the configuration information of the first multicast table is generated according to the operation of a client in the interaction process of the signaling server and the client under the first account;
Step S402, a second guiding platform is created in response to a request of copying configuration information of the first guiding platform from a client under the first account;
step S403, generating configuration information of the second multicast table, which is identical to the configuration information of the first multicast table, for the second multicast table;
step S404, the identification information of the second guiding broadcast station is sent to the client;
step S405, in response to an instruction from the signaling server to query the configuration information of the second multicast table, sends the configuration information of the second multicast table to the signaling server.
According to another aspect, for the situation that the existing multicast table is restored to its configuration after the existing multicast table is stopped under the same account, the method shown in fig. 4 includes the following steps:
step S406, receiving an instruction from the signaling server requesting the configuration information of the first multicast table;
step S407, sending the configuration information of the first multicast table to the signaling server.
According to yet another aspect, for a situation in which an existing under-account director configuration is shared to another under-account director for different accounts, the method as shown in fig. 4 includes the steps of:
Step S408, receiving an instruction of creating a guide table of the client under the second account, wherein the instruction of creating the guide table comprises identification information of the first guide table;
step S409, a third guiding platform is created for the second account according to the instruction for creating the guiding platform;
step S410, generating configuration information of the third multicast table, which is identical to the configuration information of the first multicast table;
step S411, sending the identification information of the third multicast guiding station to the client; and
step S412, in response to the request of the signaling server for querying the configuration information of the third multicast table, sending the configuration information of the third multicast table to the signaling server.
Wherein, the instruction for creating the director station further includes verification code information of the first director station, and step S409 may further include:
determining whether the client passes the verification under the second account according to the verification code information;
and under the condition that the client side under the second account passes the verification, a third guide table is created for the second account according to the instruction for creating the guide table.
Fig. 5 is a flowchart of a method of replicating and sharing multicast table configuration information performed by a signaling server according to an embodiment of the present application.
According to one aspect, for the case where the newly created director replicates the existing director configuration under the same account, the method as shown in fig. 5 includes the steps of:
step S501, in the interaction process with the client under the first account, generating configuration information related to the configuration information of the first multicast table under the first account according to the operation of the client;
step S502, the configuration information of the first guiding and broadcasting station is sent to a service server;
step S503, in response to a request from the client to recover the second multicast table, sending an instruction for requesting configuration information of the second multicast table to the service server, where the configuration information of the second multicast table is the same as the configuration information of the first multicast table;
step S504, receiving configuration information of the second guiding broadcast station from the service server;
step S505, transmitting the configuration information of the second multicast guiding station to the client;
step S506, analyzing the configuration information of the second guiding and broadcasting station, creating the components corresponding to the configuration information of the second guiding and broadcasting station and establishing the connection relation between the components.
According to another aspect, for the situation that the existing multicast table is restored to its configuration after the existing multicast table is stopped under the same account, the method shown in fig. 5 includes the following steps:
Step S507, in response to a request from the first account client to recover the first multicast table, sending an instruction for requesting configuration information of the first multicast table to the service server;
step S508, receiving configuration information of a first multicast table from the service server;
step S509, transmitting the configuration information of the first multicast table to the client;
step S510, analyzing the configuration information of the first multicast table, re-creating a component corresponding to the configuration information of the first multicast table, and establishing a connection relationship between the components.
According to yet another aspect, for a situation in which an existing under-account director configuration is shared to another under-account director for different accounts, the method shown in fig. 5 includes the steps of:
step S511, receiving a request for recovering a third guiding and broadcasting station from the client under the second account, and sending an instruction for requesting configuration information of the third guiding and broadcasting station to the service server, wherein the configuration information of the third guiding and broadcasting station is the same as the configuration information of the first guiding and broadcasting station;
step S512, receiving configuration information of a third multicast guiding station from the service server;
Step S513, transmitting the configuration information of the third multicast guiding station to the client;
step S514, analyzing the configuration information of the third multicast table, creating a component corresponding to the configuration information of the third multicast table, and establishing a connection relationship between the components.
According to the system and method for copying and sharing configuration information of a multicast table shown in fig. 1 to 5, in a practical application process, a process of sharing configuration information of a multicast table of a user a to a user B according to some embodiments is approximately as follows:
1. the user-a logs in and creates the director AS1.
2. The user-A starts the guide broadcast station AS1 to perform scene configuration. And after the configuration is finished, returning to the list page of the broadcasting guide table.
3. The user-a clicks the share button of the function area of the director AS1, and sets the validity period (for example, 1 minute, 5 minutes or 30 minutes) of the verification code added by other accounts of the director in the share popup window. After clicking, a request of sharing the guide station AS1 is sent to the service server back-end-server, and the request carries the serial number of the guide station AS1 and the validity period information of the verification code.
4. After receiving the request of the user-A sharing guide table, the service server back-end-server generates a verification code verificationCode-A1 with timeliness, stores the verification code verificationCode-A1 into the configuration information of the guide table AS1, and returns the verification code verificationCode-A1 to the user-A.
5. After receiving the verification code-A1 returned by the service server back-end-server, the user-A generates a sharing document according to a specified rule by the serial number Seq-A1 of the broadcasting station AS1 and the verification code-A1, and automatically copies the sharing document to the clipboard.
6. And the user-A sends the serial number Seq-A1 of the guide station AS1 and the verification code-A1 file to the user-B.
7. The user-B logs in, clicks the add cross-account guide table button, inputs the serial number Seq-A1 of the guide table AS1 and the verification code-A1 in the add cross-account guide table window, and sends a request for adding the cross-account guide table AS1 to the service server back-end-server after clicking to determine, wherein the request carries the serial number Seq-A1 of the cross-account guide table AS1 and the verification code-A1 information.
8. After receiving the user-B adding request, the service server checks the validity of the serial number Seq-A1 and the verification code-A1 information. And if the verification passes, returning the serial number and the basic configuration information of the new guiding station BS1 to the User-B, and adding a new guiding station BS1 to the guiding station list of the User-B. And if the verification is not passed, returning to the user-B to add the cross-account multicast table failure information, including the request error code and the error description information.
After the user-B successfully adds the cross-account guiding and broadcasting station AS1, the BS1 guiding and broadcasting station is started, and the server side can recover all configuration information owned by the AS1 guiding and broadcasting station before. And realizing the cross-account copy of the guide station.
According to the method and the system for copying and sharing the configuration information of the guide table, the signaling server records the configuration information of the guide table formed by the operation of the client in the interaction process with the client, and sends the configuration information of the guide table to the service server for storage; in case that the configuration of a new guiding station is the same as that of an existing guiding station, creating configuration information which is the same as that of the existing guiding station for the new guiding station in a service server, sending the configuration information of the new guiding station to a client through a signaling server, and restoring a scene according to the configuration information of the new guiding station by the client. According to the scheme, the configuration information of the guide table can be quickly copied and shared, and the configuration complexity of the guide table is effectively reduced.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments.
It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of action combinations, but it should be understood by those skilled in the art that the present application is not limited by the order of actions described, as some steps may be performed in other order or simultaneously in accordance with the present application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all alternative embodiments, and that the acts and modules referred to are not necessarily required in the present application.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, such as the division of the units, merely a logical function division, and there may be additional manners of dividing the actual implementation, such as multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, may be in the form of electrical connection or otherwise.
Referring to fig. 6, fig. 6 provides an electronic device including a processor and a memory. The memory stores computer instructions that, when executed by the processor, cause the processor to execute the computer instructions to implement the methods and refinements shown in fig. 3, 4 and 5.
It should be understood that the above-described device embodiments are illustrative only and that the disclosed device may be implemented in other ways. For example, the division of the units/modules in the above embodiments is merely a logic function division, and there may be another division manner in actual implementation. For example, multiple units, modules, or components may be combined, or may be integrated into another system, or some features may be omitted or not performed.
In addition, unless specifically described, each functional unit/module in each embodiment of the present invention may be integrated into one unit/module, or each unit/module may exist alone physically, or two or more units/modules may be integrated together. The integrated units/modules described above may be implemented either in hardware or in software program modules.
The integrated units/modules, if implemented in hardware, may be digital circuits, analog circuits, etc. Physical implementations of hardware structures include, but are not limited to, transistors, memristors, and the like. The processor or chip may be any suitable hardware processor, such as CPU, GPU, FPGA, DSP and ASIC, etc., unless otherwise specified. The on-chip cache, off-chip Memory, memory may be any suitable magnetic or magneto-optical storage medium, such as resistive Random Access Memory RRAM (Resistive Random Access Memory), dynamic Random Access Memory DRAM (Dynamic Random Access Memory), static Random Access Memory SRAM (Static Random Access Memory), enhanced dynamic Random Access Memory EDRAM (Enhanced Dynamic Random Access Memory), high-Bandwidth Memory HBM (High-Bandwidth Memory), hybrid Memory cube HMC (Hybrid Memory Cube), and the like, unless otherwise indicated.
The integrated units/modules may be stored in a computer readable memory if implemented in the form of software program modules and sold or used as a stand-alone product. Based on such understanding, the technical solution of the present invention may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a memory, comprising several instructions for causing a computer electronic device (which may be a personal computer, a server or a network electronic device, etc.) to perform all or part of the steps of the method described in the various embodiments of the disclosure. And the aforementioned memory includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The embodiments also provide a non-transitory computer storage medium storing a computer program that, when executed by a plurality of processors, causes the processors to perform the methods and refinements shown in fig. 3, 4 and 5.
The foregoing has outlined rather broadly the more detailed description of embodiments of the present application, wherein specific examples have been provided herein to illustrate the principles and embodiments of the present application, and wherein the above examples are provided to assist in the understanding of the methods and concepts of the present application. Meanwhile, based on the ideas of the present application, those skilled in the art can make changes or modifications on the specific embodiments and application scope of the present application, which belong to the scope of the protection of the present application. In view of the foregoing, this description should not be construed as limiting the application.