A unified authentication method, device, system and storage medium for an audio and video platform

Abstract

The present invention provides a unified authentication method, device, system and storage medium for an audio and video platform, relating to the technical field of audio and video authentication calls. The unified authentication method for the audio and video platform includes: a front-end unified SDK module receives a call instruction for the client to call audio and video, and obtains the tag information of the client according to the call instruction; the front-end unified SDK module constructs a request URL according to the tag information; and a resource background corresponding to the request URL is determined according to the request URL. The present invention provides a front-end unified SDK module, which realizes that the version of the audio and video SDK is basically fixed, facilitating version maintenance; the development logic of the audio and video background is simpler, the coupling degree is logically reduced, the development manpower of the front-end SDK is released, and the inconvenience of frequent development and version update in conventional technologies is avoided.

Description

Technical Field

[0001] The present invention relates to the technical field of audio - video authentication and call, and more specifically, to a unified authentication method, device, system and storage medium for an audio - video platform. Background Art

[0002] Most financial institutions have audio - video platforms. For example, among the many platform resources of a bank, its audio - video platform usually undertakes and docks with many different business parties, such as insurance, auto financing, and securities, and each business party has its own application carrier for docking. However, regardless of the business party, when starting the initialization of the audio - video SDK, it is necessary to obtain the login status and user information of the user of the current carrier. If the user's login status is normal in the host application, the audio - video platform allows its initialization to succeed and then establishes a connection; otherwise, the audio - video initialization request should be rejected.

[0003] The audio - video platform of a bank often docks with multiple business parties, which means that it is necessary to connect to multiple authentication platforms according to multiple business parties. The existing method is (refer to Figure 8 ): For each authentication platform, write a corresponding set of logic for obtaining the login state, that is, through the session information (such as ticket, token, userId, etc.) passed through the front - end, query the login state of this session at the authentication interface provided by this business party.

[0004] From the perspective of an audio - video project, this method has the following drawbacks:

[0005] 1. Every time a new business party is added, a dedicated audio - video SDK (Software Development Kit) is developed for it to route the url (uniform resource locator) of its corresponding initialization interface; at the same time, it is also necessary to add a corresponding initialization interface in the audio - video background and call the background interface of the new business party to obtain the user login state information;

[0006] 2. Both the front - end and the back - end need to be modified, consuming development manpower; moreover, the front - end needs to maintain multiple SDK versions, and if subsequent SDK upgrades are involved, the version control is chaotic. Summary of the Invention

[0007] In view of this, in response to the above - mentioned technical problems, the present invention provides a unified authentication method for an audio - video platform that can be used in the field of fintech or other related fields, which is applied between a client and an audio - video platform. The audio - video platform is provided with a front - end unified SDK module and a resource background corresponding to the front - end unified SDK module;

[0008] The unified authentication method for the audio and video platform includes:

[0009] The front-end unified SDK module receives the call instruction for the client to call audio and video, and obtains the tag information of the client according to the call instruction;

[0010] The front-end unified SDK module constructs a request URL according to the tag information;

[0011] Determine the resource background corresponding to the request URL according to the request URL, so as to respond to the call instruction of the client through the resource background.

[0012] Preferably, the tag information includes the target business party identifier and the ticket information.

[0013] Preferably, the front-end unified SDK module constructs a request URL according to the tag information, including:

[0014] The front-end unified SDK module obtains the target tag by parsing the target business party identifier; wherein, the target tag corresponds to the client and can determine the corresponding resource background;

[0015] The front-end unified SDK module assembles a request URL with the target tag based on the URL template through the target tag.

[0016] Preferably, the resource background includes at least two unit audio and video back-ends; wherein, each unit audio and video back-end is provided with a corresponding back-end filter;

[0017] The determining the resource background corresponding to the request URL according to the request URL includes:

[0018] The resource background determines the corresponding back-end filter according to the request URL;

[0019] Through the back-end filter, determine the resource background based on the request URL.

[0020] Preferably, the determining the resource background based on the request URL through the back-end filter includes:

[0021] Through the back-end filter, call the authentication interface of the client corresponding to the request URL;

[0022] Determine the login state of the client according to the authentication interface;

[0023] If the login status of the client is valid, the client is determined to have passed the verification, and the unit audio and video backend in the resource backend is determined to correspond to the client; and user information corresponding to the client is obtained, and the user information is stored in the attribute block of the calling instruction;

[0024] If the login status of the client is login invalid, it is determined that the client has not passed the verification, and a response exception message is returned to the client.

[0025] Preferably, after determining the resource background corresponding to the request URL according to the request URL, the method further includes:

[0026] The front-end unified SDK module initiates an http request to the unit audio and video backend in the resource backend; wherein the http request contains the ticket information;

[0027] After receiving the http request, the unit audio and video backend responds to the client according to the http request using the ticket information as an input parameter.

[0028] Preferably, before the front-end unified SDK module receives the calling instruction of the client to call the audio and video and obtains the tag information of the client according to the calling instruction, it also includes:

[0029] The audio and video platform constructs the front-end unified SDK module shared by the client and the resource background;

[0030] The client sends the calling instruction for calling audio and video to the front-end unified SDK module, so as to determine the corresponding resource background according to the calling instruction.

[0031] In addition, to solve the above problems, the present invention also provides a unified authentication device for an audio and video platform, comprising:

[0032] The receiving module is used for the front-end unified SDK module to receive the calling instruction of the client to call the audio and video, and obtain the tag information of the client according to the calling instruction;

[0033] A construction module, used by the front-end unified SDK module to construct a request URL according to the tag information;

[0034] The determination module is used to determine the resource background corresponding to the request URL according to the request URL, so as to respond to the calling instruction of the client through the resource background.

[0035] In addition, to solve the above problems, the present invention further provides a unified authentication system for an audio and video platform, including a memory and a processor. The memory stores a unified authentication program for the audio and video platform, and the processor runs the unified authentication program for the audio and video platform so that the unified authentication system for the audio and video platform executes the unified authentication method for the audio and video platform as described above.

[0036] In addition, to solve the above problems, the present invention further provides a computer-readable storage medium. The computer-readable storage medium stores a unified authentication program for the audio and video platform. When the unified authentication program for the audio and video platform is executed by a processor, it implements the unified authentication method for the audio and video platform as described above.

[0037] The present invention provides a unified authentication method, device, system, and storage medium for an audio and video platform. Among them, the method includes: the front-end unified SDK module receives a call instruction for the client to call audio and video, and obtains the label information of the client according to the call instruction; the front-end unified SDK module constructs a request URL according to the label information; determines a resource background corresponding to the request URL according to the request URL, so as to respond to the call instruction of the client through the resource background. In the unified authentication method for the audio and video platform of the present invention, a front-end unified SDK module is provided, thereby realizing that the version of the audio and video SDK is basically fixed, and only one unified version can be provided without custom development for each business party, which is convenient for version maintenance; if there is a need for optimization and upgrade of the SDK in the future, it can also be upgraded uniformly without separate upgrade implementation for each business party; moreover, the development logic of the audio and video background is simpler, the coupling degree is logically reduced, the development manpower of the front-end SDK is released, and the inconvenience of frequent development and version update in conventional technologies is avoided. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is a schematic structural diagram of the hardware operating environment related to the embodiment of the unified authentication method for the audio and video platform of the present invention;

[0039] Figure 2 It is a schematic flowchart of the first embodiment of the unified authentication method for the audio and video platform of the present invention;

[0040] Figure 3 It is a schematic flowchart of the refinement of step S200 in the second embodiment of the unified authentication method for the audio and video platform of the present invention;

[0041] Figure 4 It is a schematic flowchart of the refinement of step S300 in the second embodiment of the unified authentication method for the audio and video platform of the present invention;

[0042] Figure 5Schematic diagram of the refined process of step S320 in the second embodiment of the unified authentication method for the audio - video platform of the present invention;

[0043] Figure 6 Schematic diagram of the process in the third embodiment of the unified authentication method for the audio - video platform of the present invention;

[0044] Figure 7 Schematic diagram of the module connection of the unified authentication device for the audio - video platform of the present invention;

[0045] Figure 8 Platform authentication method in conventional technology;

[0046] Figure 9 Schematic diagram of the functional modular connection of the unified authentication method for the audio - video platform of the present invention.

[0047] The realization of the object of the present invention, functional characteristics and advantages will be further described with reference to the embodiments and the accompanying drawings. Detailed implementation manners

[0048] The following details the embodiments of the present invention, where the same or similar reference numerals represent the same or similar elements or elements with the same or similar functions throughout.

[0049] In addition, the terms "first" and "second" are only used for descriptive purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more of such features. In the description of the present invention, "a plurality" means two or more, unless otherwise specifically defined.

[0050] In the present invention, unless otherwise clearly defined and limited, the terms "installed", "connected", "connected to", "fixed" and other terms should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or integrated; it can be a mechanical connection or an electrical connection; it can be directly connected or indirectly connected through an intermediate medium, and it can be the communication inside two elements or the interaction relationship between two elements. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific situations.

[0051] It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0052] As Figure 1 shown, it is a schematic diagram of the hardware operating environment structure of the terminal involved in the embodiments of the present invention.

[0053] The unified authentication system of the audio - video platform in the embodiments of the present invention can be a PC, or a mobile terminal device such as a smart phone, a tablet computer, or a portable computer, etc. The unified authentication system of the audio - video platform may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, and a communication bus 1002. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen, an input unit such as a keyboard, a remote control. Optionally, the user interface 1003 may further include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI - FI interface). The memory 1005 may be a high - speed RAM memory, or a stable memory, such as a disk memory. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001. Optionally, the unified authentication system of the audio - video platform may further include an RF (Radio Frequency) circuit, an audio circuit, a WiFi module, etc. In addition, the unified authentication system of the audio - video platform may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which will not be elaborated here.

[0054] Those skilled in the art can understand that Figure 1 the unified authentication system of the audio - video platform shown in Figure 1 does not constitute a limitation thereto, and may include more or fewer components than shown in the figure, or combine some components, or have different component arrangements. As

[0055] shown, in the memory 1005, as a computer - readable storage medium, there may be included an operating system, a data interface control program, a network connection program, and a unified authentication program for the audio - video platform.

[0056] Embodiment 1:

[0057] Referring to Figure 2 , the first embodiment of the present invention provides a unified authentication method for an audio - video platform, which is applied between a client and an audio - video platform. The audio - video platform is provided with a front - end unified SDK module and a resource background corresponding to the front - end unified SDK module;

[0058] Among them, the unified authentication method of the audio and video platform includes:

[0059] Step S100, the front-end unified SDK module receives the call instruction for the client to call the audio and video, and obtains the tag information of the client according to the call instruction;

[0060] In the above-mentioned application of the audio and video platform in the bank, there are generally multiple clients, and each client corresponds to a business party. For example, business party A, business party B, business party C... and so on.

[0061] In the above-mentioned audio and video platform, there is a front-end unified SDK module and a resource background.

[0062] Among them, the number of the front-end unified SDK modules can be one, which is used for the integration of all audio and video business parties (clients).

[0063] In the above-mentioned resource background, there can be multiple back-ends, and each back-end corresponds to a client. The front-end unified SDK module plays a role in routing and scheduling, achieving the bridging between the client and the back-end, so as to realize the call and acquisition of data, and the processing of data.

[0064] Step S200, the front-end unified SDK module constructs a request URL according to the tag information;

[0065] Step S300, determine the resource background corresponding to the request URL according to the request URL, so as to respond to the call instruction of the client through the resource background.

[0066] In the above-mentioned, the request URL has a certain rule format. The corresponding request URL is constructed through the tag information. That is, in the request URL, it contains the strings in the tag information pool.

[0067] In the above-mentioned, by parsing the constructed request URL, the specific back-end in the resource background corresponding to the client can be determined, so the back-end in the resource background can further respond to the call instruction, that is, the routing between the client and the corresponding resource background is realized through the front-end unified SDK module.

[0068] In this embodiment of the unified authentication method for the audio and video platform, a unified front-end SDK module is provided, so that the basic version of the audio and video SDK can be fixed. Only one unified version needs to be provided without custom development for each business party, which is convenient for version maintenance. If there is a need for optimization and upgrade of the SDK in the future, it can also be upgraded uniformly without separate upgrade implementation for each business party. Moreover, the development logic of the audio and video background is simpler, the logic implementation reduces the coupling degree, releases the development manpower of the front-end SDK, and avoids the inconvenience of frequent development and version update in the conventional technology.

[0069] Embodiment 2:

[0070] Referring to Figure 3 , the second embodiment of the present invention provides a unified authentication method for an audio and video platform, based on the above Embodiment 1. The tag information includes the target business party identifier and ticket information.

[0071] As described above, the tag information is the relevant information corresponding to the client included in the call instruction sent by the client.

[0072] As described above, each tag information includes a target business party identifier and ticket information.

[0073] As described above, the target business party identifier can be an appId.

[0074] As described above, the ticket information can be the login information of the client's current login.

[0075] In step S200, the unified front-end SDK module constructs a request URL according to the tag information, including:

[0076] Step S210, the unified front-end SDK module obtains a target tag by parsing the target business party identifier; wherein, the target tag corresponds to the client and can determine the corresponding resource background.

[0077] As described above, after the unified front-end SDK module obtains the target business party identifier, the target tag can be obtained by parsing the target business party identifier.

[0078] As described above, the target tag is the string corresponding to the client in the target business party identifier, and at the same time, this string can determine the uniquely corresponding resource background.

[0079] Step S220, the unified front-end SDK module assembles a request URL with the target tag based on the URL template through the target tag.

[0080] The above-mentioned request URL is constructed by the unified SDK module of the front end through a URL template with specifications, which contains target tags. Therefore, after generation, the corresponding string can be obtained through parsing to determine the corresponding relationship and achieve routing.

[0081] The above-mentioned URL template has a standardized string format. For example, it can be "request url = domain name / context / appN / init.do", where N is the ID in the target business party identifier.

[0082] Further, the resource background includes at least two unit audio-video back-ends; among them, each unit audio-video back-end is provided with a corresponding back-end filter.

[0083] The above-mentioned resource background contains multiple unit audio-video back-ends, and the number thereof is at least 2. It forms a one-to-many relationship with the unified SDK module of the front end in the audio-video platform.

[0084] The above-mentioned resource background also includes back-end filters, and there are multiple back-end filters corresponding to the unit audio-video back-ends. That is, each unit audio-video back-end is correspondingly provided with a back-end filter, and each back-end filter has different logical rules.

[0085] Further, referring to Figure 4 , step S300 of determining the resource background corresponding to the request URL according to the request URL includes:

[0086] Step S310, the resource background determines the corresponding back-end filter according to the request URL;

[0087] The above-mentioned, after obtaining the request URL, by parsing the fields therein, the corresponding back-end filter can be determined.

[0088] The above-mentioned call instruction can obtain the tag information of the client, and each tag information includes the target business party identifier and ticket information.

[0089] For example, the target business party identifier can be appId. For example, appId = appA, appId = appB, appId = appC.

[0090] The above-mentioned request URL constructed according to the URL template can be:

[0091] (1) If appId = appA, then the request URL = domain name / context / appA / init.do;

[0092] (2) If appId = appB, then the request URL = domain name / context / appB / init.do, and so on.

[0093] Therefore, from the above request URL, it can be determined which backend filter is started correspondingly.

[0094] Since a backend filter is provided for each client, when appId = appA and the client is client A, by parsing the request URL = domain name / context / appA / init.do, the logical rule for starting the A backend filter can be determined.

[0095] Similarly, when appId = appB and the client is client B, by parsing the request URL = domain name / context / appB / init.do, the logical rule for starting the B backend filter can be determined.

[0096] Therefore, in the audio and video platform, the background routes each request URL to the corresponding backend filter. For example, if the received url = domain name / context / appA / init.do, it enters the logic of the backend filter of filterA: call the authentication interface of the service provider (client) A for further login status verification. Similarly, if the received URL = domain name / context / appB / init.do, it enters the logic of the filterB filter and interacts with the authentication interface of the service provider (client) B, and so on.

[0097] Step S320, determine the resource background based on the request URL through the backend filter.

[0098] Therefore, through the logical rule of the backend filter, the uniquely corresponding resource background can be determined through the request URL.

[0099] Further, referring to Figure 5 , the step S320, determine the resource background based on the request URL through the backend filter, includes:

[0100] Step S321, call the authentication interface of the client corresponding to the request URL through the backend filter;

[0101] Step S322, determine the login status of the client according to the authentication interface;

[0102] Step S323, if the login status of the client is valid, it is determined that the client passes the verification, and it is determined that the corresponding one for the client is the unit audio-video backend in the resource backend; moreover, the user information corresponding to the client is obtained, and the user information is stored in the attribute block of the call instruction.

[0103] Step S324, if the login status of the client is invalid, it is determined that the client fails the verification, and response exception information is returned to the client.

[0104] As described above, under the logical rules of the backend filter, the login status of a specific client is verified.

[0105] There are two cases:

[0106] 1. If the login status = valid login, it can be determined that the client passes the verification.

[0107] 2. If the login status = invalid login, it can be determined that the client fails the verification.

[0108] When the login status is passing the verification, the resource backend corresponding to the client can be determined.

[0109] Furthermore, the acquisition of the user information of the client can be performed, that is, the acquisition of userInfo, and the userInfo is stored in the attribute block (attribute) of the call instruction.

[0110] In this embodiment, by self-assembling the request URL based on the URL template in the unified SDK module at the front end, a unique corresponding backend filter is first determined in the resource backend according to the request URL, and then the authentication interface is used to interact with the client according to the logical rules of the backend filter to establish a corresponding connection relationship between the client and the unit audio-video backend, thus solving the defects in the prior art: ① only affecting the old service providers when accessing new service providers, and ② having a large amount of new code when accessing new service providers, which is inconvenient for development and verification, etc., releasing the development manpower of the front-end SDK and eliminating the pain of frequent development and release. For the audio-video SDK version, only one unified version can be provided without custom development for each service provider. It is convenient for version maintenance; if there is a need for optimization and upgrade of the SDK in the future, it can also be upgraded uniformly without separate upgrade implementation for each service provider. For the audio-video backend development, the coupling degree is logically reduced. The authentication logic of each service provider is only related to its corresponding filter implementation and has nothing to do with the initialization interface. The two service logics of authentication and audio-video initialization are separated. If a new service provider needs to be added in the future, only the filter logic needs to be added to implement the new behavior.

[0111] Embodiment 3:

[0112] Refer to Figure 6 , Embodiment 3 of the present invention provides a unified authentication method for an audio - video platform. Based on Embodiment 2 above, after step S300, determining the resource background corresponding to the request URL according to the request URL, it further includes:

[0113] Step S400, the front - end unified SDK module sends an http request to the unit audio - video backend in the resource background; wherein, the ticket information is included in the http request;

[0114] As described above, under the logical rules of the backend filter, the unique corresponding unit audio - video backend in the resource background is determined. Furthermore, the connection relationship between the client and the corresponding unit audio - video backend is determined through the front - end unified SDK module.

[0115] As described above, the front - end unified SDK module sends an http request to the unit audio - video backend with which the connection relationship is established through the authentication interface, and puts the ticket information into the request header of the http request.

[0116] Step S500, after receiving the http request, the unit audio - video backend responds to the client with the ticket information as the input parameter according to the http request.

[0117] As described above, after the unit audio - video backend receives the http request, when calling the authentication interface of the client, it interacts with the input parameter according to the ticket information passed in by the http request.

[0118] Furthermore, before step S100, where the front - end unified SDK module receives the call instruction for the client to call the audio - video and obtains the label information of the client according to the call instruction, it further includes:

[0119] Step S600, the audio - video platform constructs the front - end unified SDK module shared by the client and the resource background;

[0120] Step S700, the client sends the call instruction for calling the audio - video to the front - end unified SDK module, so as to determine the corresponding resource background according to the call instruction.

[0121] As described above, the audio - video platform needs to provide a front - end unified SDK module in advance, which may include a software package of the SDK, a software framework, etc., a collection of development tools for building application software, and is integrated by all audio - video service providers.

[0122] As described above, the front-end unified SDK module is a module shared by the client and the resource background in the audio and video platform.

[0123] As described above, when the business-side client calls audio and video through the front-end unified SDK module, it is necessary to first initialize the authentication interface of the client and generate a call instruction for sending to the front-end unified SDK module. Based on the call instruction, in its input parameters, it is necessary to pass in the target business-side identifier appId in the label information of the client and the ticket information of the current session login, so as to perform further authentication actions.

[0124] In addition, referring to Figure 7 , this embodiment also provides a unified authentication device for an audio and video platform, including:

[0125] A receiving module 10, configured to receive, by the front-end unified SDK module, a call instruction for the client to call audio and video, and obtain the label information of the client according to the call instruction;

[0126] A construction module 20, configured to construct, by the front-end unified SDK module, a request URL according to the label information;

[0127] A determination module 30, configured to determine, according to the request URL, a resource background corresponding to the request URL, so as to respond to the call instruction of the client through the resource background.

[0128] In addition, this embodiment also provides a unified authentication system for an audio and video platform, including a memory and a processor. A unified authentication program for the audio and video platform is stored in the memory, and the processor runs the unified authentication program for the audio and video platform so that the unified authentication system for the audio and video platform executes the unified authentication method for the audio and video platform as described above.

[0129] In addition, this embodiment also provides a computer-readable storage medium. A unified authentication program for the audio and video platform is stored on the computer-readable storage medium. When the unified authentication program for the audio and video platform is executed by a processor, the unified authentication method for the audio and video platform as described above is implemented.

[0130] Regarding the platform authentication method in the conventional technology (refer to Figure 8 ), in order to solve the defects existing therein, the unified authentication method for the audio and video platform in the present invention is provided (refer to Figure 9) In summary, this embodiment provides a unified front-end SDK module, thus achieving a basically fixed version of the audio and video SDK. It is possible to provide only one unified version without custom development for each business party, which is convenient for version maintenance. If there are subsequent optimization and upgrade requirements for the SDK, it is also possible to upgrade uniformly without individual upgrades for each business party. Moreover, the development logic of the audio and video background is simpler, the logic implementation reduces the coupling degree, releases the development manpower of the front-end SDK, and avoids the inconvenience of frequent development and version updates in conventional technologies.

[0131] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0132] Through the description of the above embodiments, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, in essence, or the part that makes a contribution to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above and includes several instructions for causing a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in various embodiments of the present invention. The above is only the preferred embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made by using the content of the specification and drawings of the present invention, or directly or indirectly applied to other related technical fields, shall be equally included in the patent protection scope of the present invention.

Claims

1. A unified authentication method for an audio and video platform, applied between a client and an audio and video platform, It is characterized in that The audio and video platform is provided with a front-end unified SDK module and a resource background corresponding to the front-end unified SDK module; The unified authentication method of the audio and video platform includes: The front-end unified SDK module receives a call instruction from the client to call audio and video, and obtains the tag information of the client according to the call instruction; the tag information includes a target business party identifier and ticket information; The front-end unified SDK module obtains a target tag by parsing the target business party identifier; wherein the target tag corresponds to the client and can determine the corresponding resource backend; the resource backend includes at least two unit audio and video backends; wherein each unit audio and video backend is provided with a corresponding backend filter; The front-end unified SDK module assembles a request URL with the target tag based on the URL template through the target tag; The resource background corresponding to the request URL is determined according to the request URL, so as to respond to the calling instruction of the client through the resource background.

2. The unified authentication method for the audio and video platform as claimed in claim 1, It is characterized in that The determining the resource background corresponding to the request URL according to the request URL includes: The resource backend determines the corresponding backend filter according to the request URL; The resource backend is determined based on the request URL through the backend filter.

3. The unified authentication method for the audio and video platform as claimed in claim 2, It is characterized in that The determining the resource backend based on the request URL through the backend filter includes: Calling the authentication interface of the client corresponding to the request URL through the backend filter; Determining the login state of the client according to the authentication interface; If the login status of the client is valid, the client is determined to have passed the verification, and the unit audio and video backend in the resource backend is determined to correspond to the client; and user information corresponding to the client is obtained, and the user information is stored in the attribute block of the calling instruction; If the login status of the client is login invalid, it is determined that the client has not passed the verification, and a response exception message is returned to the client.

4. The unified authentication method for the audio and video platform as claimed in claim 3, It is characterized in that After determining the resource background corresponding to the request URL according to the request URL, the method further includes: The front-end unified SDK module initiates an http request to the unit audio and video backend in the resource backend; wherein the http request contains the ticket information; After receiving the http request, the unit audio and video backend responds to the client according to the http request using the ticket information as an input parameter.

5. The unified authentication method for the audio and video platform as claimed in claim 1, It is characterized in that Before the front-end unified SDK module receives the call instruction for calling audio and video from the client and obtains the tag information of the client according to the call instruction, it further includes: The audio and video platform constructs the front-end unified SDK module shared by the client and the resource background; The client sends the call instruction for calling audio and video to the front-end unified SDK module, so as to determine the corresponding resource background according to the call instruction.

6. A unified authentication device for an audio and video platform, Characterized in that, It includes: A receiving module, configured to receive, by the front-end unified SDK module, a call instruction for the client to call audio and video, and obtain the tag information of the client according to the call instruction; the tag information includes a target business party identifier and ticket information; A construction module, configured to obtain a target tag by the front-end unified SDK module parsing the target business party identifier; wherein, the target tag corresponds to the client and can determine the corresponding resource background; the resource background includes at least two unit audio and video back-ends; wherein, each unit audio and video back-end is provided with a corresponding back-end filter; the front-end unified SDK module assembles, based on a URL template and through the target tag, a request URL with the target tag; A determination module, configured to determine, according to the request URL, the resource background corresponding to the request URL, so as to respond to the call instruction of the client through the resource background.

7. A unified authentication system for an audio and video platform, Characterized in that, It includes a memory and a processor, and a unified authentication program for the audio and video platform is stored in the memory, and the processor runs the unified authentication program for the audio and video platform so that the unified authentication system for the audio and video platform executes the unified authentication method for the audio and video platform according to any one of claims 1-5.

8. A computer-readable storage medium, Characterized in that, A unified authentication program for the audio and video platform is stored on the computer-readable storage medium, and when the unified authentication program for the audio and video platform is executed by a processor, it implements the unified authentication method for the audio and video platform according to any one of claims 1-5.

Images