Image acquisition method, device, system, server, terminal and medium

By processing the authentication failure information of the image acquisition device on the server and feeding back the proprietary authentication information to the web, the browser pop-up problem is solved, improving the user experience and image acquisition fluency.

CN118764474BActive Publication Date: 2024-12-03HANGZHOU HIKVISION DIGITAL TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411252308.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-09-06
Publication Date
2024-12-03
Estimated Expiration
2044-09-06

AI Technical Summary

Technical Problem

During the image acquisition process between the image acquisition device and the web, the authentication failure message caused by the browser does not carry valid authentication information intercepts pop-up windows, affecting the user experience.

Method used

When the server receives an image acquisition request from the web side, it sends a request that does not carry the proprietary authentication information to the image acquisition device, receives and processes the authentication failure information to avoid triggering the browser's blocking pop-up window and sends the proprietary authentication information back The web side makes it resend a request carrying authentication information.

Benefits of technology

It effectively avoids the browser's blocking pop-up windows, improves the user experience, and ensures that the web side can obtain images of the image acquisition device.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118764474B_ABST
    Figure CN118764474B_ABST
Patent Text Reader

Abstract

The embodiment of the present application provides a method, device, system, server, terminal and medium for image acquisition, which is applied to a server in an image acquisition system, and includes: upon receiving a first image acquisition request sent by a web terminal, sending the first image acquisition request to an image acquisition device, the first image acquisition request not carrying proprietary authentication information of the image acquisition device, receiving proprietary authentication information and authentication failure information sent by the image acquisition device, processing the authentication failure information so that the authentication failure information does not trigger an interception pop-up window of the browser, sending the proprietary authentication information to the web terminal so that the web terminal sends a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and the web terminal receives the image indicated by the second image acquisition request returned by the image acquisition device. The embodiment of the present application can solve the problem of browser pop-up windows and improve user experience.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of multimedia data processing technology, and in particular to a method, device, system, server, terminal and medium for image acquisition. Background Art

[0002] When users need to view images captured by image acquisition devices, they can obtain images from image acquisition devices through the web (webpage). The image acquisition request sent by the web end to the image acquisition device needs to carry authentication information. The image acquisition device will return the image to the web end only when the authentication information is authenticated.

[0003] If the image retrieval request sent by the Web end does not carry valid authentication information, an authentication failure message will be returned. The browser will intercept the authentication failure message and display a pop-up window, resulting in a poor user experience. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a method, device, system, server, terminal and medium for image acquisition to solve the problem of browser pop-up windows and improve user experience. The specific technical solution is as follows:

[0005] In a first aspect, an embodiment of the present application provides a first image acquisition method, which is applied to a server in an image acquisition system, wherein the system further includes a web terminal and an image acquisition device, wherein the web terminal is applied to a browser, and the method includes:

[0006] When receiving the first image acquisition request sent by the web terminal, sending the first image acquisition request to the image acquisition device, wherein the first image acquisition request does not carry proprietary authentication information of the image acquisition device;

[0007] Receiving proprietary authentication information and authentication failure information sent by the image acquisition device;

[0008] Processing the authentication failure information so that the authentication failure information does not trigger an interception pop-up window of the browser;

[0009] The proprietary authentication information is sent to the web end, so that the web end sends a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and the web end receives the image indicated by the second image acquisition request returned by the image acquisition device.

[0010] Optionally, the authentication failure information is an error status code;

[0011] The step of processing the authentication failure information so that the authentication failure information does not trigger the browser's pop-up window interception includes:

[0012] Processing the error status code to obtain a processed authentication status code so that the authentication failure information does not trigger an interception pop-up window of the browser;

[0013] The step of sending the proprietary authentication information to the web terminal includes:

[0014] The processed authentication status code and the proprietary authentication information are sent to the web end.

[0015] In a second aspect, an embodiment of the present application provides a second method for image acquisition, which is applied to a server in an image acquisition system, wherein the system further includes a web terminal and an image acquisition device, wherein the web terminal is applied to a browser, and the method includes:

[0016] When receiving the first image acquisition request sent by the web terminal, sending the first image acquisition request to the image acquisition device, wherein the first image acquisition request does not carry proprietary authentication information of the image acquisition device;

[0017] Receiving proprietary authentication information and authentication failure information sent by the image acquisition device;

[0018] Processing the authentication failure information so that the authentication failure information does not trigger an interception pop-up window of the browser;

[0019] Sending a second image acquisition request carrying the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server;

[0020] Send the image to the web end.

[0021] Optionally, the step of processing the authentication failure information so that the authentication failure information does not trigger an interception pop-up window of the browser includes:

[0022] The authentication failure information is not sent to the web end, so that the authentication failure information does not trigger the interception pop-up window of the browser.

[0023] Optionally, the step of sending a second image acquisition request carrying the proprietary authentication information to the image acquisition device so that the image acquisition device returns the image indicated by the second image acquisition request to the server includes:

[0024] Sending a second image acquisition request including the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server if the proprietary authentication information is authenticated; or

[0025] A second image acquisition request including the proprietary authentication information and the user authentication information is sent to the image acquisition device. When the image acquisition device authenticates both the proprietary authentication information and the user authentication information, the image indicated by the second image acquisition request is returned to the server, wherein the user authentication information includes an account number and a password.

[0026] Optionally, the proprietary authentication information is a pre-set proprietary field stored in the image acquisition device, or the proprietary authentication information is a proprietary field updated by the image acquisition device according to a preset period.

[0027] Optionally, when receiving the first image acquisition request sent by the web end, the step of sending the first image acquisition request to the image acquisition device includes:

[0028] Receive an image acquisition request sent by the web terminal and start timing;

[0029] When the timing duration reaches a first preset duration, based on the image acquisition request received within the timing duration, the image acquisition request is sent to the image acquisition device.

[0030] Optionally, the image acquisition requests received within the timing period are multiple requests for the same image acquisition device;

[0031] The step of sending the image acquisition request to the image acquisition device based on the image acquisition request received within the timing duration includes:

[0032] Selecting an image acquisition request from a plurality of image acquisition requests as a first image acquisition request, and sending the first image acquisition request to the image acquisition device; or,

[0033] The multiple image acquisition requests are combined into one image acquisition request as a first image acquisition request, and the first image acquisition request is sent to the image acquisition device.

[0034] In a third aspect, an embodiment of the present application provides a third method for image acquisition, which is applied to a web end in an image acquisition system, wherein the system further includes a server and an image acquisition device, and the web end is applied to a browser, and the method includes:

[0035] Sending a first image acquisition request to the server so that the server sends the first image acquisition request to the image acquisition device, receiving proprietary authentication information and authentication failure information sent by the image acquisition device, processing the authentication failure information so that the authentication failure information does not trigger an interception pop-up window of the browser, and sending the processed authentication failure information and the proprietary authentication information to the web end;

[0036] Sending a second image acquisition request carrying the proprietary authentication information to the image acquisition device;

[0037] Receive the image indicated by the second image acquisition request returned by the image acquisition device.

[0038] Optionally, the step of sending the second image acquisition request carrying the proprietary authentication information to the image acquisition device includes:

[0039] Sending a second image acquisition request including the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the web end when the proprietary authentication information is authenticated; or,

[0040] A second image acquisition request including the proprietary authentication information and the user authentication information is sent to the image acquisition device. When the image acquisition device authenticates both the proprietary authentication information and the user authentication information, the image indicated by the second image acquisition request is returned to the web end, wherein the user authentication information includes an account number and a password.

[0041] Optionally, the proprietary authentication information is a pre-set proprietary field stored in the image acquisition device, or the proprietary authentication information is a proprietary field updated by the image acquisition device according to a preset period.

[0042] Optionally, the step of sending the first image acquisition request to the server includes:

[0043] In the case where multiple image acquisition instructions for the same image acquisition device are acquired, generating an image acquisition request as a first image acquisition request;

[0044] Sending the first image acquisition request to the server.

[0045] Optionally, the proprietary authentication information has a validity period;

[0046] Before the step of sending the first image acquisition request to the server, the method further includes:

[0047] Determine whether the proprietary authentication information for the image acquisition device is stored locally, wherein the proprietary authentication information is the proprietary authentication information of the image acquisition device acquired and stored before the image acquisition device was last acquired;

[0048] In the case where the proprietary authentication information for the image acquisition device is not stored locally, executing the step of sending the first image acquisition request to the server;

[0049] The method further comprises:

[0050] When receiving the proprietary authentication information sent by the server, storing the proprietary authentication information and starting timing;

[0051] When the timing duration reaches a second preset duration, the stored proprietary authentication information is deleted, wherein the second preset duration is shorter than the effective duration.

[0052] In a fourth aspect, an embodiment of the present application provides a first image acquisition device, which is applied to a server in an image acquisition system, wherein the system further includes a web terminal and an image acquisition device, wherein the web terminal is applied to a browser, and the device includes:

[0053] A first request sending module, configured to send the first image acquisition request to the image acquisition device when receiving the first image acquisition request sent by the web terminal, wherein the first image acquisition request does not carry proprietary authentication information of the image acquisition device;

[0054] A first information receiving module, used for receiving proprietary authentication information and authentication failure information sent by the image acquisition device;

[0055] A first information processing module, used for processing the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser;

[0056] The first information sending module is used to send the processed authentication failure information and the proprietary authentication information to the web end, so that the web end sends a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and the web end receives the image indicated by the second image acquisition request returned by the image acquisition device.

[0057] In a fifth aspect, an embodiment of the present application provides a second image acquisition device, which is applied to a server in an image acquisition system, wherein the system further includes a web terminal and an image acquisition device, wherein the web terminal is applied to a browser, and the device includes:

[0058] A second request sending module is used to send the first image acquisition request to the image acquisition device when receiving the first image acquisition request sent by the web end, wherein the first image acquisition request does not carry the proprietary authentication information of the image acquisition device;

[0059] A second information receiving module, used to receive the proprietary authentication information and authentication failure information sent by the image acquisition device;

[0060] A second information processing module, used for processing the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser;

[0061] A third request sending module, configured to send a second image acquisition request carrying the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server;

[0062] An image sending module is used to send the image to the web end.

[0063] In a sixth aspect, an embodiment of the present application provides a third image acquisition device, which is applied to a web end in an image acquisition system, wherein the system further includes a server and an image acquisition device, and the web end is applied to a browser, and the device includes:

[0064] a fourth request sending module, configured to send a first image acquisition request to the server, so that the server sends the first image acquisition request to the image acquisition device, receive proprietary authentication information and authentication failure information sent by the image acquisition device, process the authentication failure information so that the authentication failure information does not trigger an interception pop-up window of the browser, and send the processed authentication failure information and the proprietary authentication information to the web end;

[0065] a fifth request sending module, configured to send a second image acquisition request carrying the proprietary authentication information to the image acquisition device;

[0066] The image receiving module is used to receive the image indicated by the second image acquisition request returned by the image acquisition device.

[0067] In a seventh aspect, an embodiment of the present application provides a first image acquisition system, the system comprising a server, a web terminal and an image acquisition device, the web terminal being applied to a browser, wherein:

[0068] The web end is used to send a first image acquisition request to the server, wherein the first image acquisition request does not carry proprietary authentication information of the image acquisition device;

[0069] The server is configured to send the first image acquisition request to the image acquisition device when receiving the first image acquisition request sent by the web terminal;

[0070] The image acquisition device is used to send proprietary authentication information and authentication failure information to the server when receiving the first image acquisition request;

[0071] The server is further configured to receive the proprietary authentication information and authentication failure information sent by the image acquisition device; process the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser; and send the proprietary authentication information to the web end;

[0072] The web end is further used to send a second image acquisition request carrying the proprietary authentication information to the image acquisition device;

[0073] The image acquisition device is further configured to, upon receiving a second image acquisition request carrying the proprietary authentication information, send the image indicated by the second image acquisition request to the web end.

[0074] In an eighth aspect, an embodiment of the present application provides a second image acquisition system, the system comprising a server, a web terminal and an image acquisition device, the web terminal being applied to a browser, wherein:

[0075] The web end is used to send a first image acquisition request to the server, wherein the first image acquisition request does not carry proprietary authentication information of the image acquisition device;

[0076] The server is configured to send the first image acquisition request to the image acquisition device when receiving the first image acquisition request sent by the web terminal;

[0077] The image acquisition device is used to send proprietary authentication information and authentication failure information to the server when receiving the first image acquisition request;

[0078] The server is further configured to receive the proprietary authentication information and authentication failure information sent by the image acquisition device; process the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser; and send a second image acquisition request carrying the proprietary authentication information to the image acquisition device;

[0079] The image acquisition device is further configured to, upon receiving a second image acquisition request carrying the proprietary authentication information, send the image indicated by the second image acquisition request to the server;

[0080] The server is also used to send the image to the web end.

[0081] In a ninth aspect, an embodiment of the present application provides a server, including:

[0082] Memory, used to store computer programs;

[0083] The processor is used to implement any one of the methods described in the first and second aspects above when executing the program stored in the memory.

[0084] In a tenth aspect, an embodiment of the present application provides a terminal, including:

[0085] Memory, used to store computer programs;

[0086] The processor is used to implement any method described in the third aspect when executing a program stored in the memory.

[0087] In the eleventh aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the method described in the first aspect, the second aspect, or any one of the third aspects is implemented.

[0088] Beneficial effects of the embodiments of the present application:

[0089] In the solution provided in the embodiment of the present application, the image acquisition system includes a server, a web terminal and an image acquisition device, the web terminal is applied to a browser, and the above-mentioned image acquisition method can be applied to the server. When the server receives a first image acquisition request sent by the web terminal, the server sends the first image acquisition request to the image acquisition device, wherein the first image acquisition request does not carry proprietary authentication information of the image acquisition device, receives the proprietary authentication information and authentication failure information sent by the image acquisition device, processes the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser, sends the proprietary authentication information to the web terminal, so that the web terminal sends a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and the web terminal receives the image indicated by the second image acquisition request returned by the image acquisition device. Because when the server sends the first image acquisition request to the image acquisition device, the proprietary authentication information and authentication failure information returned by the image acquisition device can be received, and the authentication failure information can be processed so that the authentication failure information does not trigger the browser's interception pop-up window, and the proprietary authentication information is sent to the web end, so that the web end can send a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and then the web end receives the image indicated by the second image acquisition request returned by the image acquisition device. In this way, not only the browser will not intercept the authentication failure information to pop up a window, solving the problem of browser pop-up windows, but the web end can also obtain the proprietary authentication information to obtain the image required by the user, improving the user experience. Of course, implementing any product or method of the present application does not necessarily require all of the advantages described above to be achieved at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0090] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other embodiments can also be obtained based on these drawings.

[0091] Figure 1 A schematic diagram of the structure of an image acquisition system provided in an embodiment of the present application;

[0092] Figure 2 A flowchart of a first image acquisition method provided in an embodiment of the present application;

[0093] Figure 3 A schematic diagram of a browser pop-up window provided in an embodiment of the present application;

[0094] Figure 4 Based on Figure 2 A first signaling diagram for acquiring an image in the illustrated embodiment;

[0095] Figure 5 A flowchart of a second image acquisition method provided in an embodiment of the present application;

[0096] Figure 6 Based on Figure 5 A second signaling diagram for acquiring an image in the illustrated embodiment;

[0097] Figure 7 Based on Figure 5 A third signaling diagram for acquiring an image in the illustrated embodiment;

[0098] Figure 8 A specific flow chart of sending an image acquisition request provided in an embodiment of the present application;

[0099] Fig. 9 A specific flow chart of notifying a web terminal of a failure to obtain an image provided in an embodiment of the present application;

[0100] Fig.10 A flowchart of a third image acquisition method provided in an embodiment of the present application;

[0101] Fig.11 Based on Fig.10 A fourth signaling diagram for acquiring an image in the illustrated embodiment;

[0102] Fig.12 A schematic diagram of the structure of a first image acquisition device provided in an embodiment of the present application;

[0103] Fig.13 A schematic diagram of the structure of a second image acquisition device provided in an embodiment of the present application;

[0104] Fig.14 A schematic diagram of the structure of a third image acquisition device provided in an embodiment of the present application;

[0105] Fig.15 A schematic diagram of the structure of a server provided in an embodiment of the present application;

[0106] Fig.16 A schematic diagram of the structure of a terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0107] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions 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 based on the present application belong to the scope of protection of the present application.

[0108] In order to solve the problem of browser pop-up windows and improve user experience, the embodiments of the present application provide a method, device, server, terminal, computer-readable storage medium and computer program product for image acquisition. The following first introduces the first image acquisition method provided in the embodiments of the present application.

[0109] The first image acquisition method provided in the embodiment of the present application is as follows: Figure 1 As shown, a server 101 can be applied to an image acquisition system. The system also includes a web terminal 102 and an image acquisition device 103. The web terminal 102 is applied to a browser.

[0110] like Figure 2 As shown, a method for image acquisition, the method comprising:

[0111] S201, when receiving a first image acquisition request sent by the web terminal, sending the first image acquisition request to the image acquisition device;

[0112] The first image acquisition request does not carry proprietary authentication information of the image acquisition device.

[0113] S202, receiving proprietary authentication information and authentication failure information sent by the image acquisition device;

[0114] S203, processing the authentication failure information so that the authentication failure information does not trigger an interception pop-up window of the browser;

[0115] S204, sending the proprietary authentication information to the web end, so that the web end sends a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and the web end receives the image indicated by the second image acquisition request returned by the image acquisition device.

[0116] It can be seen that in the solution provided in the embodiment of the present application, since the server can receive proprietary authentication information and authentication failure information returned by the image acquisition device when sending the first image acquisition request to the image acquisition device, and can process the authentication failure information so that the authentication failure information does not trigger the browser's interception pop-up window, and send the proprietary authentication information to the web end, so that the web end can send a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and then the web end receives the image indicated by the second image acquisition request returned by the image acquisition device. In this way, not only will the browser not intercept the authentication failure information to pop up a window, thus solving the problem of browser pop-up windows, but the web end can also obtain the proprietary authentication information for obtaining the image required by the user, thereby improving the user experience.

[0117] When a user views an image captured by an image acquisition device, there is a scenario where the image acquisition device is a proprietary device. In this case, when the user obtains the image from the image acquisition device through the web, the web needs to send an image acquisition request carrying proprietary authentication information to the image acquisition device. If the image acquisition request sent by the web does not carry proprietary authentication information, the image acquisition device will fail to authenticate the proprietary authentication information, and will return authentication failure information. The browser will intercept the authentication failure information and display a pop-up window.

[0118] For example, Figure 3 As shown, the page accessed by the user through the browser includes multiple executable functions, namely, function 1 to function 6. When function 1 is clicked, the page can display multiple sub-functions under function 1, including file type, search dimension, time and user. If the user obtains an image through function 1, the page can display the image acquisition results, such as pictures 1 to 6. If the user obtains an image, the image acquisition request sent by the web end does not carry proprietary authentication information, and the browser will pop up a login box, displaying the message "http: / / 10.42.161.xxx Your connection to this website is not a private connection", and requires the user to enter a user name and password. The user can click to log in after entering the corresponding information, or cancel directly without entering any information. At this time, the address bar displays "10.42.161.xxx / # / portal" as an unsafe address.

[0119] Therefore, for such a scenario, an embodiment of the present application provides a method for obtaining proprietary authentication information of an image acquisition device through a server, so that when the image acquisition device receives an image acquisition request carrying the proprietary authentication information, the proprietary authentication information can be authenticated and the image indicated by the image acquisition request can be returned, and the server can process the received authentication failure information so that the authentication failure information does not trigger the browser's interception pop-up window.

[0120] In step S201, when the server receives the first image acquisition request sent by the web end, it can send the first image acquisition request to the image acquisition device, wherein the first image acquisition request is a request that does not carry the proprietary authentication information of the image acquisition device, then when the image acquisition device receives the first image acquisition request, it can return the proprietary authentication information and authentication failure information at the same time. The image acquisition device can be a video camera, a camera, a still camera, etc., which is not specifically limited here.

[0121] In one embodiment, the first image acquisition request may be set in a pre-set format. When the image acquisition device receives the first image acquisition request set in a pre-set format, it may determine that the first image acquisition request does not carry proprietary authentication information, and thus returns the proprietary authentication information. For example, the first image acquisition request only includes the address of the image to be acquired, and then when the image acquisition device receives the first image acquisition request, the proprietary authentication information may be returned. For another example, the first image acquisition request only includes the identifier of the image to be acquired, and then when the image acquisition device receives the first image acquisition request, the proprietary authentication information may be returned.

[0122] The proprietary authentication information may be special information included in the image acquisition device. In one embodiment, the proprietary authentication information may be a pre-set proprietary field stored in the image acquisition device. For example, if the pre-set proprietary field stored in the image acquisition device is key field 1, then the proprietary authentication information required for authentication by the image acquisition device is key field 1.

[0123] In another embodiment, the proprietary authentication information changes periodically, and the proprietary authentication information can be a proprietary field that the image acquisition device updates according to a preset period. For example, the image acquisition device can update the proprietary field at a frequency of once a week. As the proprietary authentication information, the proprietary field can be updated by the user as required, or by the image acquisition device according to certain preset rules, which is reasonable.

[0124] When the image acquisition device receives the first image acquisition request that does not carry the proprietary authentication information of the image acquisition device, it can send the proprietary authentication information and authentication failure information to the server. The server can then receive the proprietary authentication information and authentication failure information sent by the image acquisition device, and execute step S202.

[0125] The authentication failure information can be used to inform the server that the correct proprietary authentication information is not provided or does not carry the proprietary authentication information, that is, to inform the server that the current first image acquisition request does not have the authority to access the image acquisition device. Exemplarily, the authentication failure information can be an error status code.

[0126] For example, the proprietary authentication information of the image acquisition device is key field 1. The server only sends the first image acquisition request carrying the identification of the image to be acquired to the image acquisition device. The image acquisition device does not recognize the key field 1 required for authentication and can send a 401 status code and key field 1 to the server. The server can receive the 401 status code and key field 1 sent by the image acquisition device.

[0127] In step S203, the server can process the authentication failure information so that the authentication failure information does not trigger the browser's pop-up window. In other words, as long as the web end does not receive the authentication failure information after the server processes the authentication failure information, the browser will not intercept the authentication failure information to pop up a window.

[0128] In one embodiment, when the server receives authentication failure information, it can process the authentication failure information to obtain processed authentication information, and then send the processed authentication information to the web end, so that the browser will not display a pop-up window when it intercepts the processed authentication information. Exemplarily, the server adds pre-set information at the beginning or end of the authentication failure information, so that the authentication failure information is no longer the original authentication failure information, so that the browser will not display a pop-up window when it intercepts the processed authentication information.

[0129] The server can obtain proprietary authentication information while obtaining authentication failure information, and then the proprietary authentication information can be sent to the web end, so that the web end sends a second image acquisition request carrying the proprietary authentication information to the image acquisition device. When the image acquisition device receives the second image acquisition request carrying the proprietary authentication information, the proprietary authentication information can be authenticated, and the image indicated by the second image acquisition request can be sent to the web end, so that the web end receives the image indicated by the second image acquisition request returned by the image acquisition device, that is, executes step S204.

[0130] Among them, the second image acquisition request can be set in a preset form. When the image acquisition device receives the second image acquisition request set in a preset form, it can determine that the second image acquisition request carries proprietary authentication information, thereby authenticating the proprietary authentication information and returning the image indicated by the second image acquisition request.

[0131] For example, the second image acquisition request includes the address of the image to be acquired and the proprietary authentication information, then when the image acquisition device receives the second image acquisition request, the image indicated by the second image acquisition request can be returned. For another example, the second image acquisition request includes the identifier of the image to be acquired and the proprietary authentication information, then when the image acquisition device receives the second image acquisition request, the image indicated by the second image acquisition request can be returned.

[0132] In the scheme of this embodiment, when the server sends a first image acquisition request to the image acquisition device, it can receive proprietary authentication information and authentication failure information returned by the image acquisition device, and can process the authentication failure information so that the authentication failure information does not trigger the browser's interception pop-up window, and send the proprietary authentication information to the web end, so that the web end can send a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and then the web end receives the image indicated by the second image acquisition request returned by the image acquisition device. This not only prevents the browser from intercepting the authentication failure information to pop up a window, thereby solving the problem of browser pop-ups, but also the web end can obtain the proprietary authentication information for obtaining the image required by the user, thereby improving the user experience.

[0133] Although there is currently a method in which a plug-in forwards an image acquisition request sent by a web terminal to an image acquisition device, receives proprietary authentication information and authentication failure information returned by the image acquisition device, and then based on the proprietary authentication information and authentication failure information returned by the image acquisition device, enables the web terminal to obtain the image that the user needs to view, but since the plug-in does not have only a single function, but integrates multiple functions, the development process is more complicated and the maintenance cost is higher. In addition, when the user needs to view the image of the image acquisition device, the plug-in needs to be downloaded. If the user does not download the plug-in, the image cannot be viewed, which affects the user experience. Therefore, the embodiment of the present application can complete the functions performed by the plug-in only using the server, which is not only low-cost and easy to maintain, but also does not require the user to download the plug-in, the operation is simple, and the user experience is greatly improved.

[0134] As an implementation of an embodiment of the present application, the above authentication failure information is an error status code, and the error status code can trigger a browser interception pop-up window. The error status code can be used to inform the browser that the current first image acquisition request does not authorize access rights. Exemplarily, the error status code can be a 401 status code.

[0135] The above-mentioned step of processing the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser may include:

[0136] The error status code is processed to obtain a processed authentication status code so that the authentication failure information does not trigger the browser's pop-up window for interception.

[0137] Since the error status code can trigger the browser's interception pop-up window, if the server sends the error status code to the web end, the browser will intercept the error status code and pop up a window. Therefore, in one embodiment, the server can process the error status code to obtain a processed authentication status code so that the authentication status information will not trigger the browser's interception pop-up window. In other words, the processed authentication status code obtained by the server is no longer an error status code, and the processed authentication status code is a status code that will not be intercepted by the browser. Among them, the processed authentication status code can be set according to actual needs, such as adding a preset number to the preset position of the error status code, adding a preset letter to the preset position of the error status code, etc., which is not specifically limited here.

[0138] For example, if the error status code is 401, the server can process the 401 status code by adding the number 40 to the 401 status code, and the processed authentication status code is 40401. The processed authentication status code 40401 will not be intercepted by the browser, that is, it will not trigger the browser's interception pop-up window. For another example, the server can add the letter A to the 401 status code, and the processed authentication status code is A401. The processed authentication status code A401 will also not be intercepted by the browser.

[0139] The above step of sending the proprietary authentication information to the web terminal may include:

[0140] The processed authentication status code and the proprietary authentication information are sent to the web end.

[0141] After the server obtains the processed authentication status code, it can send the authentication status code and the proprietary authentication information to the web end. When the web end receives the authentication status code, the browser will not intercept the processed authentication status code to pop up a window. And when the web end receives the proprietary authentication information, it can send a second image acquisition request carrying the proprietary authentication information to the image acquisition device. When the image acquisition device receives the second image acquisition request, it can return the image indicated by the second image acquisition request, and then the web end can receive the image returned by the image acquisition device.

[0142] For example, Figure 4 As shown, the web end sends a first image acquisition request to the server, and the first image acquisition request does not carry proprietary authentication information, and the proprietary authentication information can be obtained through the server. When the server receives the first image acquisition request, it can send the first image acquisition request to the image acquisition device. When the image acquisition device receives the first image acquisition request, since the first image acquisition request does not carry proprietary authentication information, a 401 status code and proprietary authentication information can be returned to the server.

[0143] After receiving the 401 status code and proprietary authentication information, the server processes the 401 status code to obtain the authentication status code 40401, and sends the authentication status code 40401 and the proprietary authentication information to the web end. The web end receives the authentication status code and the proprietary authentication information. Since the browser will not intercept the authentication status code, no pop-up window will appear. Then the web end can generate a second image acquisition request based on the proprietary authentication information, and send the second image acquisition request carrying the proprietary authentication information to the image acquisition device. The image acquisition device receives the second image acquisition request, which carries the proprietary authentication information. Then the image acquisition device can authenticate the proprietary authentication information and return the image indicated by the second image acquisition request to the web end, so that the web end can receive the image and display it.

[0144] It can be seen that in this embodiment, the server can process the error status code, and the processed authentication status code authentication failure information will not trigger the browser's interception pop-up window. In this way, after the server sends the processed authentication status code and proprietary authentication information to the web end, when the web end receives the processed authentication status code, the browser will not pop up a window, and the web end can send a second image acquisition request carrying proprietary authentication information to the image acquisition device to receive the image indicated by the second image acquisition request returned by the image acquisition device. In this way, while the web end can obtain the image, the problem of browser pop-up windows is solved, and the user experience is improved.

[0145] The present application also provides a second method for acquiring an image. The second method for acquiring an image provided by the present application is as follows: Figure 1 As shown, a server 101 can be applied to an image acquisition system. The system also includes a web terminal 102 and an image acquisition device 103. The web terminal 102 is applied to a browser.

[0146] like Figure 5 As shown, a method for image acquisition, the method comprising:

[0147] S501, when receiving a first image acquisition request sent by the web terminal, sending the first image acquisition request to the image acquisition device;

[0148] The first image acquisition request does not carry proprietary authentication information of the image acquisition device.

[0149] S502, receiving proprietary authentication information and authentication failure information sent by the image acquisition device;

[0150] S503, processing the authentication failure information so that the authentication failure information does not trigger an interception pop-up window of the browser;

[0151] S504, sending a second image acquisition request carrying the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server;

[0152] S505: Send the image to the web end.

[0153] It can be seen that in the solution provided by the embodiment of the present application, when the server sends the first image acquisition request to the image acquisition device, the proprietary authentication information and authentication failure information returned by the image acquisition device can be received, and the authentication failure information can be processed so that the authentication failure information will not trigger the browser's interception pop-up window, and the second image acquisition request carrying the proprietary authentication information can be sent to the image acquisition device so that the image acquisition device returns the image indicated by the second image acquisition request, and then sends the image to the web end. In this way, not only will the browser not intercept the authentication failure information to pop up a window, solving the problem of browser pop-up windows, but the web end can also obtain the image required by the user, improving the user experience, and the server sending the second image acquisition request to the image acquisition device can reduce the pressure on the browser.

[0154] Among them, the specific implementation of step S501-step S502 is the same as the corresponding part in each embodiment of the above-mentioned first image acquisition method. Please refer to the description of the specific implementation of each embodiment of the above-mentioned first image acquisition method, and no further details will be given here.

[0155] In step S503, the server processes the authentication failure information so that the authentication failure information does not trigger the browser's pop-up window. In other words, as long as the web end does not receive the authentication failure information after the server processes the authentication failure information, the browser will not intercept the authentication failure information to pop up a window.

[0156] In one implementation, when the server receives authentication failure information, it may not send the authentication failure information to the web end, so that the web end does not receive the authentication failure information, and the authentication failure information will not trigger the browser's interception pop-up window.

[0157] Exemplarily, the authentication failure information may be an error status code, such as a 401 status code. Since the error status code is sent to the web end, the browser will intercept the error status code and display a pop-up window. Therefore, the server may not send the error status code to the web end. In this way, the web end does not receive the error status code, and the browser will not intercept the error status code to display a pop-up window.

[0158] In order to reduce the interaction between the web terminal and the image acquisition device, the server can generate a second image acquisition request based on the proprietary authentication information, and then send the second image acquisition request carrying the proprietary authentication information to the image acquisition device, so that when the image acquisition device receives the second image acquisition request carrying the proprietary authentication information, it can authenticate the proprietary authentication information and return the image indicated by the second image acquisition request, that is, execute step S504.

[0159] Among them, the second image acquisition request can be set in a preset form. When the image acquisition device receives the second image acquisition request set in a preset form, it can determine that the second image acquisition request carries proprietary authentication information, thereby authenticating the proprietary authentication information and returning the image indicated by the second image acquisition request.

[0160] For example, the second image acquisition request includes the address of the image to be acquired and the proprietary authentication information, then when the image acquisition device receives the second image acquisition request, the image indicated by the second image acquisition request can be returned. For another example, the second image acquisition request includes the identifier of the image to be acquired and the proprietary authentication information, then when the image acquisition device receives the second image acquisition request, the image indicated by the second image acquisition request can be returned.

[0161] When the server receives the image returned by the image acquisition device, it can send the image to the web end so that the web end can display the image at the same time as it receives it, that is, execute step S505.

[0162] For example, Figure 6 As shown, the web terminal sends a first image acquisition request to the server, and the first image acquisition request does not carry proprietary authentication information. When the server receives the first image acquisition request, it can send the first image acquisition request to the image acquisition device. When the image acquisition device receives the first image acquisition request, since the first image acquisition request does not carry proprietary authentication information, it can return a 401 status code and proprietary authentication information to the server.

[0163] After receiving the 401 status code and proprietary authentication information, the server may not do anything with the 401 status code, that is, it neither sends the 401 status code to the web end nor processes the 401 status code. In this way, the web end does not receive the error status code, and the browser will not intercept the error status code to pop up a window. The server receives the 401 status code and proprietary authentication information, generates a second image acquisition request based on the proprietary authentication information, and sends the second image acquisition request carrying the proprietary authentication information to the image acquisition device. The image acquisition device receives the second image acquisition request, which carries the proprietary authentication information, and can authenticate the proprietary authentication information and return the image indicated by the second image acquisition request to the server. The server can send the image to the web end after receiving the image, so that the web end receives the image and displays it.

[0164] In the scheme of this embodiment, when the server sends the first image acquisition request to the image acquisition device, the proprietary authentication information and authentication failure information returned by the image acquisition device can be received, and the authentication failure information can be processed so that the authentication failure information does not trigger the browser's interception pop-up window, and the second image acquisition request carrying the proprietary authentication information can be sent to the image acquisition device so that the image acquisition device returns the image indicated by the second image acquisition request, and then sends the image to the web end. In this way, not only will the browser not intercept the authentication failure information to pop up a window, solving the problem of browser pop-up windows, but the web end can also obtain the image required by the user, improving the user experience, and the server sending the second image acquisition request to the image acquisition device can reduce the pressure on the browser.

[0165] As an implementation of an embodiment of the present application, the step of sending the second image acquisition request carrying the proprietary authentication information to the image acquisition device so that the image acquisition device returns the image indicated by the second image acquisition request to the server may include:

[0166] Send a second image acquisition request including the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server if the proprietary authentication information is authenticated; or send a second image acquisition request including the proprietary authentication information and user authentication information to the image acquisition device, and return the image indicated by the second image acquisition request to the server if the image acquisition device authenticates both the proprietary authentication information and the user authentication information, wherein the user authentication information includes an account number and a password.

[0167] There are two situations in which the server sends a second image acquisition request carrying proprietary authentication information to the image acquisition device. The first situation is that before the server sends the second image acquisition request, the image acquisition device has authenticated the user's user authentication information and the user authentication information has been authenticated, that is, the user has logged in to the image acquisition device, then the image acquisition device only needs to authenticate the proprietary authentication information, so that the server can send a second image acquisition request including the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server when the proprietary authentication information is authenticated.

[0168] The second situation is that before the server sends the second image acquisition request, the image acquisition device has not authenticated the user's user authentication information, that is, the user has not logged into the image acquisition device, then the server can send a second image acquisition request including proprietary authentication information and user authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server when both the proprietary authentication information and the user authentication information are authenticated. The user authentication information includes an account number and a password.

[0169] In one embodiment, the server can obtain user authentication information when receiving a first image acquisition request sent by the web end, and when sending the first image acquisition request to the image acquisition device, the image acquisition device will not authenticate the user authentication information, but only return proprietary authentication information and authentication failure information.

[0170] For example, Figure 7 As shown, the web terminal sends a first image acquisition request to the server, and the first image acquisition request does not carry proprietary authentication information, but carries user authentication information. When the server receives the first image acquisition request sent by the web terminal, it obtains the user authentication information and sends the first image acquisition request to the image acquisition device. When the image acquisition device receives the first image acquisition request, since the first image acquisition request does not carry proprietary authentication information, it can return a 401 status code and proprietary authentication information to the server, and will not authenticate the user authentication information.

[0171] After receiving the 401 status code and proprietary authentication information, the server may not do anything with the 401 status code. The server receives the 401 status code and proprietary authentication information, generates a second image acquisition request based on the proprietary authentication information and the user authentication information, and sends the second image acquisition request including the proprietary authentication information and the user authentication information to the image acquisition device. The image acquisition device receives the second image acquisition request, which includes the proprietary authentication information and the user authentication information. The image acquisition device can authenticate both the proprietary authentication information and the user authentication information, and return the image indicated by the second image acquisition request to the server. Then, when the server receives the image, it sends the image to the web end, so that the web end receives the image and displays it.

[0172] As an implementation, the server may perform encryption processing on proprietary authentication information and user authentication information to obtain a second image acquisition request including valid authentication information required by the image acquisition device, and send the second image acquisition request including the valid authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server when the valid authentication information is authenticated.

[0173] For example, the proprietary authentication information is key field 1, and the user authentication information is account 123 and password 123. The server can encrypt key field 1, account 123 and password 123 to obtain a second image acquisition request including key field 1, account 123 and password 123 required by the image acquisition device, and then send the second image request to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server when key field 1, account 123 and password 123 are authenticated.

[0174] It can be seen that in this embodiment, there is no need for the server to send proprietary authentication information to the web end, so that the web end sends a second image acquisition request carrying the proprietary authentication information to the image acquisition device. Instead, the server sends a second image acquisition request including the proprietary authentication information to the image acquisition device, or sends a second image acquisition request including the proprietary authentication information and the user authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server when the required authentication information is authenticated. In this way, the server can reduce the pressure on the browser.

[0175] Furthermore, the image acquisition device not only needs to authenticate proprietary authentication information, but also needs to authenticate user authentication information, which can ensure the security, privacy and reliability of images obtained from the image acquisition device.

[0176] As an implementation method of the present application, Figure 8As shown, the above step of sending the first image acquisition request to the image acquisition device upon receiving the first image acquisition request sent by the web terminal may include:

[0177] S801, receiving an image acquisition request sent by the web terminal and starting timing;

[0178] S802: When the timing duration reaches a first preset duration, based on the image acquisition requests received within the timing duration, sending the image acquisition request to the image acquisition device.

[0179] If the web terminal frequently sends image acquisition requests to the server within a certain period of time, the server needs to frequently send the acquired image acquisition requests to the image acquisition device, which causes a large workload for the server. Therefore, in order to reduce the workload of the server, the server can wait for a certain period of time after receiving an image acquisition request, and then send the image acquisition request to the image acquisition device based on the image acquisition requests received within a certain period of time.

[0180] In one embodiment, when the server receives an image acquisition request sent by the web end, it can start timing, and when the timing duration reaches a first preset duration, based on the image acquisition request received within the timing duration, send the image acquisition request to the image acquisition device. The first preset duration can be set according to actual conditions, for example, the first preset duration is 0.5s, 1s, etc., which is not specifically limited here. The server may receive one or more image acquisition requests within the timing duration.

[0181] If the server receives multiple image acquisition requests within the timing duration, the multiple image acquisition requests may be directed to different image acquisition devices or to the same image acquisition device. If the image acquisition requests received by the server within the timing duration are directed to different image acquisition devices, the server may send the image acquisition requests received within the timing duration to different image acquisition devices respectively. If the image acquisition requests received by the server within the timing duration are directed to the same image acquisition device, the server may send the multiple image acquisition requests received within the timing duration to the image acquisition device together.

[0182] For example, the first preset duration is 1 second. When the server receives the first image acquisition request, it starts timing. The first image acquisition request is for image acquisition device A. At 0.1 second, the server receives the second image acquisition request, which is for image acquisition device B. At 0.5 second, the server receives the third image acquisition request, which is for image acquisition device C. Then, when the timing duration reaches 1 second, the server may send the first image acquisition request to image acquisition device A, the second image acquisition request to image acquisition device B, and the third image acquisition request to image acquisition device C.

[0183] It can be seen that in this embodiment, the server can receive an image acquisition request sent by the web terminal and start timing. When the timing duration reaches the first preset duration, the server sends an image acquisition request to the image acquisition device based on the image acquisition request received within the timing duration. In this way, the server does not need to send an image acquisition request to the image acquisition device when it receives an image acquisition request sent by the web terminal, which can reduce the workload of the server and thus alleviate the pressure on the server.

[0184] As an implementation manner of an embodiment of the present application, the image acquisition requests received within the above timing period are multiple requests for the same image acquisition device.

[0185] The step of sending the image acquisition request to the image acquisition device based on the image acquisition request received within the timing period may include:

[0186] Select an image acquisition request from multiple image acquisition requests as a first image acquisition request, and send the first image acquisition request to the image acquisition device; or merge multiple image acquisition requests into one image acquisition request as a first image acquisition request, and send the first image acquisition request to the image acquisition device.

[0187] Since the image acquisition requests received within the server timing period are multiple requests for the same image acquisition device, even if the multiple received image acquisition requests are sent to the image acquisition device, the proprietary authentication information returned by the image acquisition device is the same. Therefore, in order to quickly and accurately obtain the proprietary authentication information returned by the same image acquisition device, only one image acquisition request can be sent to the image acquisition device.

[0188] In the case where the multiple image acquisition requests received by the server are all for the same image acquisition device, in one embodiment, the server may select one image acquisition request from the multiple image acquisition requests as the first image acquisition request, and send the first image acquisition request to the image acquisition device. When the image acquisition device receives the first image acquisition request, it may return proprietary authentication information, so that the server may send multiple second image acquisition requests to the image acquisition device based on the proprietary authentication information, and receive the image returned by the image acquisition device for each second image acquisition request.

[0189] In another embodiment, the server may merge multiple image acquisition requests into one image acquisition request as a first image acquisition request, and send the first image acquisition request to the image acquisition device. When the image acquisition device receives the first image acquisition request, it may return proprietary authentication information, so that the server may send a second image acquisition request based on the proprietary authentication information, and receive the image returned by the image acquisition device for the image indicated by the second image acquisition request. The merged image acquisition request may carry the address, identifier, etc. of each image to be acquired, which is not specifically limited here.

[0190] Different scenarios in which users acquire images may use different methods. For example, if different users initiate multiple image acquisition requests to the same image acquisition device through the web terminal, the server may select an image from the multiple image acquisition requests as the first image acquisition request and send it to the image acquisition device.

[0191] If the same user initiates multiple image acquisition requests to the same image acquisition device through the web, the server can select one image acquisition request from the multiple image acquisition requests as the first image acquisition request and send it to the image acquisition device, or it can merge the multiple image acquisition requests into one image acquisition request as the first image acquisition request and send it to the image acquisition device.

[0192] For example, if user A, user B, and user C respectively send image acquisition request 1, image acquisition request 2, and image acquisition request 3 based on the web, then after receiving the three image acquisition requests sent by the web, the server can send image acquisition request 1 as the first image acquisition request to the image acquisition device, and after receiving the proprietary authentication information returned by the image acquisition device, send image acquisition request 11, image acquisition request 21, and image acquisition request 31 carrying the proprietary authentication information to the image acquisition device to obtain the images requested by user A, user B, and user C.

[0193] If user A sends image acquisition request 1, image acquisition request 2 and image acquisition request 3 based on the web, then after receiving the three image acquisition requests, the server can merge image acquisition request 1 to image acquisition request 3 as the first image acquisition request, and send it to the image acquisition device. Then, after receiving the proprietary authentication information returned by the image acquisition device, the server sends the merged image acquisition request carrying the proprietary authentication information to the image acquisition device to obtain the image requested by user A.

[0194] It can be seen that in this embodiment, when the server receives multiple requests for the same image acquisition device within the timing period, it can select one image acquisition request from the multiple image acquisition requests as the first image acquisition request and send it to the image acquisition device, or it can merge the multiple image acquisition requests into one image acquisition request and send it to the image acquisition device as the first image acquisition request. In this way, the server only needs to send a request to the image acquisition device once. After receiving the proprietary authentication information, it can send image acquisition requests carrying the proprietary authentication information in batches, which can reduce the workload of the server and thereby reduce the pressure on the server.

[0195] As an implementation of the embodiment of the present application, the above-mentioned proprietary authentication information has a validity period, which can be set according to actual needs, for example, 3 minutes, 5 minutes, etc., and is not specifically limited here.

[0196] like Fig. 9 As shown, the above method may also include:

[0197] S901, receiving an invalidation prompt message sent by the image acquisition device;

[0198] The expiration prompt message is sent by the image acquisition device when it is determined that the time from the time when the proprietary authentication information is issued to the time when the second image acquisition request is received exceeds the valid time.

[0199] S902, sending the failure prompt message to the web end to inform the web end that image acquisition fails.

[0200] The proprietary authentication information returned by the image acquisition device has a valid period. If the proprietary authentication information is within the valid period, as long as the server carries the proprietary authentication information in the second image acquisition request sent by the image acquisition device, the authentication of the image acquisition device can be passed. If the proprietary authentication information has expired, when the server sends the second image acquisition request carrying the proprietary authentication information to the image acquisition device, the server can receive an invalidation prompt message sent by the image acquisition device. The server can then send an invalidation prompt message to the web end to inform the web end that the image acquisition failed.

[0201] The expiration prompt message is sent by the image acquisition device when it is determined that the time from the time when the proprietary authentication information is issued to the time when the second image acquisition request is received exceeds the valid time. The expiration prompt message can be set according to actual needs, such as "valid time has timed out", "timeout" and other expiration prompt messages, which are not specifically limited here.

[0202] For example, the validity period of the proprietary authentication information is 3 minutes, and the image acquisition device determines that the time when the proprietary authentication information is issued is 5:00. If the time when the image acquisition device receives the second image acquisition request is 5:05, the time from the time when the proprietary authentication information is issued to the time when the second image acquisition request is received exceeds 5 minutes. In this case, the image acquisition device can send a "timeout" failure prompt message to the server. When the server receives the "timeout" sent by the image acquisition device, it sends "timeout" to the web end to inform the web end that the image acquisition fails. Then, the web end needs to resend the image acquisition request to obtain the proprietary authentication information to the server.

[0203] It can be seen that in this embodiment, the proprietary authentication information has a valid period, and the server can receive the invalidation prompt message sent by the image acquisition device, and send the invalidation prompt message to the web end to inform the web end of the failure to obtain the image. In this way, it can be ensured that the web end can only obtain the image when the proprietary authentication information is within the valid period, ensuring the security and reliability of obtaining the image from the device. At the same time, the invalidation prompt message is sent to the web end, so that the user can understand the reason for the failure to obtain the image, thereby improving the user experience.

[0204] The present application also provides a third method for acquiring an image. The third method for acquiring an image provided by the present application is as follows: Figure 1 As shown, a web terminal 102 is applied to an image acquisition system, the system also includes a server 101 and an image acquisition device 103, and the web terminal 102 is applied to a browser.

[0205] like Fig.10 As shown, a method for image acquisition, the method comprising:

[0206] S1001, sending a first image acquisition request to the server, so that the server sends the first image acquisition request to the image acquisition device, receiving proprietary authentication information and authentication failure information sent by the image acquisition device, and processing the authentication failure information so that the authentication failure information does not trigger an interception pop-up window of the browser, and sending the processed authentication failure information and the proprietary authentication information to the web end;

[0207] S1002, sending a second image acquisition request carrying the proprietary authentication information to the image acquisition device;

[0208] S1003: Receive the image indicated by the second image acquisition request returned by the image acquisition device.

[0209] It can be seen that in the solution provided in the embodiment of the present application, since the Web end sends the first image acquisition request to the server, the server can send the first image acquisition request to the image acquisition device, receive the proprietary authentication information returned by the image acquisition device, and process the authentication failure information so that the authentication failure information does not trigger the browser's interception pop-up window, and send the proprietary authentication information to the web end, so that the web end can send a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and then receive the image when the image acquisition device returns the image indicated by the second image acquisition request. In this way, not only will the browser not intercept the authentication failure information to pop up a window, thereby solving the problem of browser pop-ups, but the web end can also obtain the proprietary authentication information for obtaining the image required by the user, thereby improving the user experience.

[0210] Among them, the specific implementation of step S1001 is the same as the corresponding part in each embodiment of the above-mentioned first image acquisition method or the second image acquisition method. Please refer to the description of the specific implementation in each embodiment of the above-mentioned first image acquisition method or the second image acquisition method, and no further details will be given here.

[0211] Since when the server receives the authentication failure information, the authentication failure information can be processed so that the authentication failure information does not trigger the browser's interception pop-up window, and the proprietary authentication information is sent to the web end, then the web end does not receive the authentication failure information, the browser will not pop up a window, and the web end can send a second image acquisition request carrying the proprietary authentication information to the image acquisition device, that is, execute step S1002.

[0212] When the image acquisition device receives a second image acquisition request carrying proprietary authentication information sent by the web end, the proprietary authentication information can be authenticated and the image indicated by the second image acquisition request can be sent to the web end. In this way, the web end can receive the image indicated by the second image acquisition request returned by the image acquisition device, that is, execute step S1003.

[0213] For example, if the authentication failure information is an error status code, such as a 401 status code, and the proprietary authentication information is key field 1, the server can process the 401 status code, add the number 40 in front of the 401 status code, and obtain a processed authentication status code 40401, which will not trigger the browser's interception pop-up window. When the web end receives the processed authentication status code 40401 sent by the server, the browser will not pop up a window, and the web end can generate a second image acquisition request based on key field 1, send the second image acquisition request carrying key field 1 to the image acquisition device, and then receive the image indicated by the second image acquisition request returned by the image acquisition device.

[0214] In the scheme of this embodiment, since the web end sends the first image acquisition request to the server, the server can send the first image acquisition request to the image acquisition device, receive the proprietary authentication information returned by the image acquisition device, and process the authentication failure information so that the authentication failure information does not trigger the browser's interception pop-up window, and send the proprietary authentication information to the web end, so that the web end can send a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and then receive the image when the image acquisition device returns the image indicated by the second image acquisition request. This not only prevents the browser from intercepting the authentication failure information to pop up a window, thereby solving the problem of browser pop-ups, but also the web end can obtain the proprietary authentication information for obtaining the image required by the user, thereby improving the user experience.

[0215] As an implementation of an embodiment of the present application, the step of sending the second image acquisition request carrying the proprietary authentication information to the image acquisition device may include:

[0216] Send a second image acquisition request including the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the web end if the proprietary authentication information is authenticated; or, send a second image acquisition request including the proprietary authentication information and user authentication information to the image acquisition device, and return the image indicated by the second image acquisition request to the web end if the image acquisition device authenticates both the proprietary authentication information and the user authentication information, wherein the user authentication information includes an account number and a password.

[0217] There are two situations in which the Web terminal sends a second image acquisition request carrying proprietary authentication information to the image acquisition device. The first situation is that before the server sends the second image acquisition request, the image acquisition device has authenticated the user's user authentication information and the user authentication information has been authenticated, that is, the user has logged in to the image acquisition device, then the image acquisition device only needs to authenticate the proprietary authentication information, so that the Web terminal can send a second image acquisition request including the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the Web terminal when the proprietary authentication information is authenticated, so that the image acquisition device can display the image when the web terminal receives the image.

[0218] The second situation is that before the Web terminal sends the second image acquisition request, the image acquisition device has not authenticated the user's user authentication information, that is, the user has not logged in to the image acquisition device, then the server can send a second image acquisition request including proprietary authentication information and user authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the Web terminal when both the proprietary authentication information and the user authentication information are authenticated, so as to display it when the Web terminal receives the image. Among them, the user authentication information includes the account number and password.

[0219] In one implementation, the first image acquisition request sent by the Web end does not carry user authentication information, so when the server sends the first image acquisition request to the image acquisition device, the image acquisition device directly returns proprietary authentication information and authentication failure information.

[0220] In another embodiment, the Web end sends a first image acquisition request carrying user authentication information. When the server sends the first image acquisition request to the image acquisition device, the image acquisition device does not authenticate the user authentication information, and only returns proprietary authentication information and authentication failure information.

[0221] For example, Fig.11 As shown, the web terminal sends a first image acquisition request to the server, and the first image acquisition request does not carry proprietary authentication information, but carries user authentication information. When the server receives the first image acquisition request, it sends the first image acquisition request to the image acquisition device. When the image acquisition device receives the first image acquisition request, since the first image acquisition request does not carry proprietary authentication information, a 401 status code and proprietary authentication information can be returned to the server, and the user authentication information will not be authenticated.

[0222] The server receives the 401 status code and the proprietary authentication information, processes the 401 status code, obtains the authentication status code 40401, and sends the authentication status code 40401 and the proprietary authentication information to the web end. When the web end receives the authentication status code, the browser will not pop up a window. When the web end receives the proprietary authentication information, it can generate a second image acquisition request based on the proprietary authentication information and the user authentication information, and send the second image acquisition request including the proprietary authentication information and the user authentication information to the image acquisition device. When the image acquisition device receives the second image acquisition request, which includes the proprietary authentication information and the user authentication information, the image acquisition device can authenticate both the proprietary authentication information and the user authentication information, and return the image indicated by the second image acquisition request to the web end, so that the web end receives the image and displays it.

[0223] In one embodiment, the web end can perform encryption processing on proprietary authentication information and user authentication information to obtain a request including valid authentication information required by the image acquisition device, and send the request including the valid authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the web end when the valid authentication information is authenticated.

[0224] For example, the proprietary authentication information is key field 1, and the user authentication information is account 123 and password 123. The web end can encrypt key field 1, account 123 and password 123 to obtain a second image acquisition request including key field 1, account 123 and password 123 required by the image acquisition device, and then send the second image request to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the web end when the key field 1, account 123 and password 123 are authenticated.

[0225] It can be seen that in this embodiment, when the user logs in to the image acquisition device, the web end can send a second image acquisition request including proprietary authentication information to the image acquisition device, or when the user is not logged in to the image acquisition device, send a second image acquisition request including proprietary authentication information and user authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the web end if the required authentication information is authenticated. In this way, the image acquisition device not only authenticates the proprietary authentication information, but also authenticates the user authentication information, thereby ensuring the security, privacy and reliability of obtaining images from the image acquisition device.

[0226] As an implementation of the embodiment of the present application, the above method may also include:

[0227] receiving the image indicated by the second image acquisition request sent by the server;

[0228] The image is returned to the server by the image acquisition device when the image acquisition device receives a second image acquisition request carrying the proprietary authentication information sent by the server.

[0229] In one embodiment, the second image acquisition request is generated by the server when the web terminal does not receive the authentication failure information. Since the second image acquisition request is generated by the server, the server sends the second image acquisition request to the image acquisition device. When the image acquisition device receives the second image acquisition request carrying the proprietary authentication information, it can send the image indicated by the second image acquisition request to the server, and then the server sends the image to the web terminal, so that the web terminal receives the image sent by the server and displays the image.

[0230] It can be seen that in this embodiment, there is no need for the server to send proprietary authentication information to the web end, so that the web end sends a second image acquisition request carrying the proprietary authentication information to the image acquisition device. Instead, the server sends a second image acquisition request carrying the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server when the proprietary authentication information is authenticated, and the server then sends the image to the web end. In this way, the server can reduce the pressure on the browser.

[0231] As an implementation method of an embodiment of the present application, the proprietary authentication information is a pre-set proprietary field stored in the image acquisition device, or the proprietary authentication information is a proprietary field updated by the image acquisition device according to a preset period.

[0232] In one embodiment, the proprietary authentication information may be a pre-set proprietary field stored in the image acquisition device. For example, the pre-set proprietary field stored in the image acquisition device is key field 1, and the proprietary authentication information required for authentication by the image acquisition device is key field 1.

[0233] In another embodiment, the proprietary authentication information changes periodically, and the proprietary authentication information can be a proprietary field that the image acquisition device updates according to a preset period. For example, the image acquisition device can update the proprietary field at a frequency of once a week. As the proprietary authentication information, the proprietary field can be updated by the user as required, or by the image acquisition device according to a certain rule, which is reasonable.

[0234] It can be seen that in this embodiment, the proprietary authentication information can be a pre-set proprietary field stored in the image acquisition device, or the proprietary authentication information can be a proprietary field updated by the image acquisition device according to a preset period. The image acquisition device authenticates the proprietary authentication information to ensure the security, reliability and accuracy of the images obtained by the user from the image acquisition device.

[0235] As an implementation of an embodiment of the present application, the step of sending the first image acquisition request to the server may include:

[0236] In the case where multiple image acquisition instructions for the same image acquisition device are acquired, an image acquisition request is generated as a first image acquisition request; and the first image acquisition request is sent to the server.

[0237] When a user needs to view images from an image acquisition device, he or she may need to view multiple images from the same image acquisition device. In this case, the user can send multiple image acquisition instructions for the same image acquisition device to the web end, so that the web end can obtain multiple image acquisition instructions for the same image acquisition device.

[0238] In one embodiment, when the web end obtains multiple image acquisition instructions for the same image acquisition device, it can generate an image acquisition request as the first image acquisition request, and send the first image acquisition request to the server. In this way, only one image acquisition request is sent, which can reduce the workload of the web end and the server. Among them, the first image acquisition request can carry the address, identification, etc. of each image to be acquired, which is not specifically limited here.

[0239] For example, user A sends image acquisition instruction 1, image acquisition instruction 2 and image acquisition instruction 3 to the web end, then the web end can generate an image acquisition request based on image acquisition instruction 1, image acquisition instruction 2 and image acquisition instruction 3 as the first image acquisition request, and send the first image acquisition request to the server.

[0240] It can be seen that in this embodiment, when the web terminal obtains multiple image acquisition instructions for the same image acquisition device, it can generate an image acquisition request as the first image acquisition request, and send the first image acquisition request to the server. In this way, only one image acquisition request is sent to the server, which can reduce the workload of the web terminal and the server, relieve the pressure on the web terminal and the server, and enable users to obtain multiple images at one time, thereby improving user experience.

[0241] As an implementation of the embodiment of the present application, the above-mentioned proprietary authentication information has a validity period, which can be set according to actual needs, for example, 3 minutes, 5 minutes, etc., and is not specifically limited here.

[0242] The above method may further include:

[0243] An expiration prompt message sent by the image acquisition device is received, wherein the expiration prompt message is sent by the image acquisition device when it is determined that the time length from the time when the proprietary authentication information is issued to the time when the second image acquisition request is received exceeds the valid time length.

[0244] The proprietary authentication information returned by the image acquisition device has a valid period. If the proprietary authentication information is within the valid period, as long as the second image acquisition request sent by the web end to the image acquisition device carries the proprietary authentication information, the authentication of the image acquisition device can be passed. If the proprietary authentication information has expired, when the web end sends a second image acquisition request carrying the proprietary authentication information to the image acquisition device, the expiration prompt message sent by the image acquisition device can be received.

[0245] The expiration prompt message is sent by the image acquisition device when it is determined that the time from the time when the proprietary authentication information is issued to the time when the second image acquisition request is received exceeds the valid time. The expiration prompt message can be set according to actual needs, such as "valid time has timed out", "timeout" and other expiration prompt messages, which are not specifically limited here.

[0246] For example, if the validity period of the proprietary authentication information is 3 minutes, and the image acquisition device determines that the time when the proprietary authentication information is issued is 5:00, if the time when the image acquisition device receives the second image acquisition request sent by the web end is 5:05, and the time from the issuance of the proprietary authentication information to the receipt of the second image acquisition request exceeds 3 minutes, then the image acquisition device can send a "timeout" failure prompt message to the web end. Then, the web end needs to resend the image acquisition request for obtaining the proprietary authentication information to the server.

[0247] It can be seen that in this embodiment, the proprietary authentication information has a valid period, and the we end can receive the invalidation prompt message sent by the image acquisition device, so that the web end can only obtain the image when the proprietary authentication information is within the valid period, ensuring the security and reliability of obtaining the image from the device. At the same time, the invalidation prompt message is sent to the web end, so that the user can understand the reason for the failure to obtain the image, thereby improving the user experience.

[0248] As an implementation of the embodiment of the present application, the above-mentioned proprietary authentication information has a validity period, which can be set according to actual needs, for example, 3 minutes, 5 minutes, etc., and is not specifically limited here.

[0249] The above method may further include:

[0250] Receive an expiration prompt message sent by the server, wherein the expiration prompt message is sent to the server by the image acquisition device when it is determined that the time length from the time when the proprietary authentication information is issued to the time when the second image acquisition request is received exceeds the valid time length.

[0251] The specific way in which the web side receives the invalidation prompt message sent by the server is similar to the specific way in which the web side receives the invalidation prompt message sent by the image acquisition device. Please refer to the description of the corresponding part of the web side, and will not be repeated here.

[0252] It can be seen that in this embodiment, the proprietary authentication information has a valid period, and the we end can receive the invalidation prompt message sent by the server, so that the web end can only obtain the image when the proprietary authentication information is within the valid period, ensuring the security and reliability of obtaining the image from the device. At the same time, the invalidation prompt message is sent to the web end, so that the user can understand the reason for the failure to obtain the image, thereby improving the user experience.

[0253] As an implementation method of an embodiment of the present application, the proprietary authentication information has a valid period, and the valid period can be set according to actual needs, for example, it can be 3 minutes, 5 minutes, etc., and is not specifically limited here.

[0254] Before the step of sending the first image acquisition request to the server, the method may further include:

[0255] Determine whether proprietary authentication information for the image acquisition device is stored locally; if the proprietary authentication information for the image acquisition device is not stored locally, execute the step of sending a first image acquisition request to the server; wherein the proprietary authentication information is the proprietary authentication information of the image acquisition device acquired and stored before the last image acquisition from the image acquisition device.

[0256] The proprietary authentication information returned by the image acquisition device is time-sensitive, that is, it has a valid period. The valid period of the proprietary authentication information obtained by the web end is consistent with the valid period of the proprietary authentication information returned by the image acquisition device. The proprietary authentication information is valid within its valid period. Therefore, within the valid period of the proprietary authentication information, the web end can directly send an image acquisition request to the image acquisition device based on the proprietary authentication information, so that the image acquisition device can authenticate the proprietary authentication information and return the image indicated by the image acquisition request to the web end.

[0257] In order for the web end to send an image acquisition request based on the proprietary authentication information at any time within the validity period of the proprietary authentication information, the web end can store the proprietary authentication information locally when receiving the proprietary authentication information.

[0258] In this way, before the web terminal sends the first image acquisition request to the server, it can first determine whether the proprietary authentication information for the image acquisition device is stored locally. If the proprietary authentication information for the image acquisition device is not stored locally, the web terminal sends the first image acquisition request to the server to obtain the proprietary authentication information through the server. If the proprietary authentication information for the image acquisition device is stored locally, the web terminal can obtain the proprietary authentication information from the local.

[0259] The proprietary authentication information is the proprietary authentication information of the image acquisition device acquired and stored before the last image acquisition from the image acquisition device. In other words, the locally stored proprietary authentication information is the proprietary authentication information of the image acquisition device acquired and stored by sending the image acquisition request before sending the first image acquisition request to the server.

[0260] Exemplarily, if the web terminal initiates 10 image acquisition requests, and if the first image acquisition request sent is the sixth image acquisition request, then the proprietary authentication information is the proprietary authentication information obtained by the five image acquisition requests sent before sending the first image acquisition request.

[0261] If the web end obtains the proprietary authentication information when sending the first image acquisition request, the proprietary authentication information is stored locally. Then, when the web end sends the fifth image acquisition request, the acquired proprietary authentication information is the same as the proprietary authentication information acquired when sending the first image acquisition request. If the proprietary authentication information still exists locally, the proprietary authentication information can be directly obtained locally. When the web end sends the sixth image acquisition request, if the proprietary authentication information does not exist locally, an image acquisition request can be sent to the server to obtain the proprietary authentication information.

[0262] The above method may further include:

[0263] When the proprietary authentication information sent by the server is received, the proprietary authentication information is stored and timing is started; when the timing duration reaches a second preset duration, the stored proprietary authentication information is deleted, wherein the second preset duration is less than the effective duration.

[0264] In one embodiment, when the web terminal receives the proprietary authentication information sent by the server, the web terminal can store the proprietary authentication information in a preset storage location and start timing, and when the timing time reaches a second preset time, delete the stored proprietary authentication information. In other words, the web terminal stores the proprietary authentication information, and when the storage time of the proprietary authentication information reaches the second preset time, the web terminal can delete the proprietary authentication information.

[0265] Among them, the second preset duration is less than the effective duration of the proprietary authentication information, and the preset storage location may be a local cache, etc. Since it takes a certain amount of time for the image acquisition device to return the proprietary authentication information to the server and for the server to send the proprietary authentication information to the web end, the current effective duration of the proprietary authentication information received by the web end will be less than its effective duration, and the duration of storing the proprietary authentication information may be less than the effective duration of the proprietary authentication information, that is, the second preset duration is less than the effective duration of the proprietary authentication information.

[0266] If the proprietary authentication information is deleted, the web end can no longer directly send an image acquisition request carrying the proprietary authentication information based on the proprietary authentication information, so an image acquisition request without the proprietary authentication information can be sent to the server to obtain the proprietary authentication information again and store it locally. Before the web end sends the first image acquisition request, it is determined whether the proprietary authentication information for the image acquisition device is stored locally.

[0267] For example, the proprietary authentication information returned by the image acquisition device has a validity period of 3 minutes. When the server receives the proprietary authentication information and sends it to the web end, the web end can store the proprietary authentication information in the local cache and start timing, and the second preset time is 2.5 minutes. When the timing time is 2 minutes, the web end is ready to send an image acquisition request. At this time, the timing time of the proprietary authentication information, 2 minutes, has not reached the second preset time of 2.5 minutes. Therefore, the web end can obtain the proprietary authentication information from the local cache, that is, send an image acquisition request carrying the proprietary authentication information to the image acquisition device based on the proprietary authentication information.

[0268] For another example, the second preset time length is 2.5 minutes, and the web end needs to send 10 image acquisition requests. Before sending the first image acquisition request, it can first determine whether proprietary authentication information is stored locally. If there is no proprietary authentication information, it means that the storage time of the last stored proprietary authentication information has reached the second preset time length of 2.5 minutes and has been deleted. Then the web end can block the 9 image acquisition requests after the first image acquisition request, and send an image acquisition request without proprietary authentication information to the server to obtain the proprietary authentication information.

[0269] When the server sends the proprietary authentication information returned by the image acquisition device to the web end, the web end can store the proprietary authentication information locally and start timing. Since the proprietary authentication information is currently stored locally, the web end can send the first image acquisition request to the image acquisition device based on the proprietary authentication information, and then send the second image acquisition request based on the proprietary authentication information, until the tenth image acquisition request is sent based on the proprietary authentication information.

[0270] When the storage time of the proprietary authentication information reaches the second preset time of 2.5 minutes, the proprietary authentication information is deleted. At this time, the web end is ready to send the next image acquisition request. Since the proprietary authentication information no longer exists locally, the image acquisition request after the image acquisition request can be blocked, and the image acquisition request carrying the proprietary authentication information is sent to the server to obtain the proprietary authentication information. When the web end obtains the proprietary authentication information, it is stored locally and the timing starts, starting a new round of image acquisition.

[0271] That is to say, the image acquisition process is a cyclic process. If the web end determines whether the proprietary authentication information is stored locally before sending the first image acquisition request, if it exists, the proprietary authentication information is directly obtained from the local. If it does not exist, the subsequent image acquisition request can be blocked, and the image acquisition request without the proprietary authentication information is sent to the server to obtain the proprietary authentication information. Then the proprietary authentication information is stored locally, and the image acquisition request is sent based on the proprietary authentication information until the timing duration of the proprietary authentication information reaches the second preset duration and is deleted, and then the proprietary authentication information is continued to be obtained.

[0272] It can be seen that in this embodiment, when the server sends the proprietary authentication information to the web end, the web end can store the proprietary authentication information locally and start timing, so that when the proprietary authentication information does not reach the second preset time length, the web end can obtain the proprietary authentication information from the local. This can reduce the interaction between devices and improve the efficiency of acquiring images.

[0273] Corresponding to the first image acquisition method described above, the embodiment of the present application further provides a first image acquisition device. The first image acquisition device provided by the embodiment of the present application is introduced below.

[0274] like Fig.12 As shown, an image acquisition device is applied to a server in an image acquisition system, the system also includes a web terminal and an image acquisition device, the web terminal is applied to a browser, and the device includes:

[0275] A first request sending module 1210 is configured to send the first image acquisition request to the image acquisition device when receiving the first image acquisition request sent by the web terminal, wherein the first image acquisition request does not carry proprietary authentication information of the image acquisition device;

[0276] The first information receiving module 1220 is used to receive the proprietary authentication information and authentication failure information sent by the image acquisition device;

[0277] A first information processing module 1230 is used to process the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser;

[0278] The first information sending module 1240 is used to send the processed authentication failure information and the proprietary authentication information to the web end, so that the web end sends a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and the web end receives the image indicated by the second image acquisition request returned by the image acquisition device.

[0279] It can be seen that in the solution provided in the embodiment of the present application, since the server can receive proprietary authentication information and authentication failure information returned by the image acquisition device when sending the first image acquisition request to the image acquisition device, and can process the authentication failure information so that the authentication failure information does not trigger the browser's interception pop-up window, and send the proprietary authentication information to the web end, so that the web end can send a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and then the web end receives the image indicated by the second image acquisition request returned by the image acquisition device. In this way, not only will the browser not intercept the authentication failure information to pop up a window, thus solving the problem of browser pop-up windows, but the web end can also obtain the proprietary authentication information for obtaining the image required by the user, thereby improving the user experience.

[0280] As an implementation method of the embodiment of the present application, the authentication failure information is an error status code;

[0281] The first information processing module 1230 may include:

[0282] An authentication status code acquisition submodule is used to process the error status code to obtain a processed authentication status code so that the authentication failure information will not trigger an interception pop-up window of the browser;

[0283] The first information sending module 1240 includes:

[0284] The first information sending submodule is used to send the processed authentication status code and the proprietary authentication information to the web end.

[0285] Corresponding to the above-mentioned second image acquisition method, the embodiment of the present application further provides a second image acquisition device. The second image acquisition device provided by the embodiment of the present application is introduced below.

[0286] like Fig.13 As shown, an image acquisition device is applied to a server in an image acquisition system, the system also includes a web terminal and an image acquisition device, the web terminal is applied to a browser, and the device includes:

[0287] A second request sending module 1310 is configured to send the first image acquisition request to the image acquisition device when receiving the first image acquisition request sent by the web terminal, wherein the first image acquisition request does not carry proprietary authentication information of the image acquisition device;

[0288] The second information receiving module 1320 is used to receive the proprietary authentication information and authentication failure information sent by the image acquisition device;

[0289] The second information processing module 1330 is used to process the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser;

[0290] A third request sending module 1340 is used to send a second image acquisition request carrying the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server;

[0291] The image sending module 1350 is used to send the image to the web end.

[0292] It can be seen that in the solution provided by the embodiment of the present application, when the server sends the first image acquisition request to the image acquisition device, the proprietary authentication information and authentication failure information returned by the image acquisition device can be received, and the authentication failure information can be processed so that the authentication failure information will not trigger the browser's interception pop-up window, and the second image acquisition request carrying the proprietary authentication information can be sent to the image acquisition device so that the image acquisition device returns the image indicated by the second image acquisition request, and then sends the image to the web end. In this way, not only will the browser not intercept the authentication failure information to pop up a window, solving the problem of browser pop-up windows, but the web end can also obtain the image required by the user, improving the user experience, and the server sending the second image acquisition request to the image acquisition device can reduce the pressure on the browser.

[0293] As an implementation of the embodiment of the present application, the second information processing module 1330 may include:

[0294] The second information processing submodule is used for not sending the authentication failure information to the web end, so that the authentication failure information will not trigger the interception pop-up window of the browser.

[0295] As an implementation of the embodiment of the present application, the third request sending module 1340 may include:

[0296] a third request sending submodule, configured to send a second image acquisition request including the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server if the proprietary authentication information is authenticated; or

[0297] Used to send a second image acquisition request including the proprietary authentication information and the user authentication information to the image acquisition device, and when the image acquisition device authenticates both the proprietary authentication information and the user authentication information, return the image indicated by the second image acquisition request to the server, wherein the user authentication information includes an account number and a password.

[0298] As an implementation of an embodiment of the present application, the above-mentioned proprietary authentication information is a pre-set proprietary field stored in the image acquisition device, or the above-mentioned proprietary authentication information is a proprietary field updated by the image acquisition device according to a preset period.

[0299] As an implementation of the embodiment of the present application, the first request sending module 1210 or the second request sending module 1310 may include:

[0300] The duration timing submodule is used to receive the image acquisition request sent by the web terminal and start timing;

[0301] The image acquisition request sending submodule is used to send the image acquisition request to the image acquisition device based on the image acquisition request received within the timing time when the timing time reaches a first preset time.

[0302] As an implementation of the embodiment of the present application, the image acquisition requests received within the above timing period are multiple requests for the same image acquisition device;

[0303] The above-mentioned image acquisition request sending submodule may include:

[0304] A first request sending unit is configured to select an image acquisition request from a plurality of image acquisition requests as a first image acquisition request, and send the first image acquisition request to the image acquisition device; or

[0305] Used to merge multiple image acquisition requests into one image acquisition request as a first image acquisition request, and send the first image acquisition request to the image acquisition device.

[0306] Corresponding to the third image acquisition method described above, the embodiment of the present application further provides a third image acquisition device. The third image acquisition device provided by the embodiment of the present application is introduced below.

[0307] like Fig.14 As shown, an image acquisition device is applied to a web end in an image acquisition system, the system also includes a server and an image acquisition device, the web end is applied to a browser, and the device includes:

[0308] The fourth request sending module 1410 is used to send a first image acquisition request to the server, so that the server sends the first image acquisition request to the image acquisition device, receives the proprietary authentication information and authentication failure information sent by the image acquisition device, processes the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser, and sends the processed authentication failure information and the proprietary authentication information to the web end;

[0309] A fifth request sending module 1420, configured to send a second image acquisition request carrying the proprietary authentication information to the image acquisition device;

[0310] The image receiving module 1430 is configured to receive the image indicated by the second image acquisition request returned by the image acquisition device.

[0311] It can be seen that in the solution provided in the embodiment of the present application, since the Web end sends the first image acquisition request to the server, the server can send the first image acquisition request to the image acquisition device, receive the proprietary authentication information returned by the image acquisition device, and process the authentication failure information so that the authentication failure information does not trigger the browser's interception pop-up window, and send the proprietary authentication information to the web end, so that the web end can send a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and then receive the image when the image acquisition device returns the image indicated by the second image acquisition request. In this way, not only will the browser not intercept the authentication failure information to pop up a window, thereby solving the problem of browser pop-ups, but the web end can also obtain the proprietary authentication information for obtaining the image required by the user, thereby improving the user experience.

[0312] As an implementation of the embodiment of the present application, the fifth request sending module 1420 includes:

[0313] a fifth request sending submodule, configured to send a second image acquisition request including the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the web end when the proprietary authentication information is authenticated; or

[0314] Used to send a second image acquisition request including the proprietary authentication information and the user authentication information to the image acquisition device, and when the image acquisition device authenticates both the proprietary authentication information and the user authentication information, return the image indicated by the second image acquisition request to the web end, wherein the user authentication information includes an account number and a password.

[0315] As an implementation of an embodiment of the present application, the above-mentioned proprietary authentication information is a pre-set proprietary field stored in the image acquisition device, or the above-mentioned proprietary authentication information is a proprietary field updated by the image acquisition device according to a preset period.

[0316] As an implementation of the embodiment of the present application, the fourth request sending module 1410 may include:

[0317] A first image acquisition request generating submodule, configured to generate an image acquisition request as a first image acquisition request when multiple image acquisition instructions for the same image acquisition device are acquired;

[0318] The first image acquisition request sending submodule is used to send the first image acquisition request to the server.

[0319] As an implementation method of the present application, the above-mentioned proprietary authentication information has a validity period;

[0320] The above device may also include:

[0321] A proprietary authentication information determination module, used to determine whether proprietary authentication information for the image acquisition device is stored locally before the step of sending the first image acquisition request to the server, wherein the proprietary authentication information is the proprietary authentication information of the image acquisition device acquired and stored before the image acquisition device was last acquired;

[0322] A fourth request sending execution module, configured to execute the fourth request sending module 1410 when the proprietary authentication information for the image acquisition device is not stored locally;

[0323] The above method may further include:

[0324] A duration timing module, configured to store the proprietary authentication information and start timing when receiving the proprietary authentication information sent by the server;

[0325] The dedicated authentication information deletion module is used to delete the stored dedicated authentication information when the timing duration reaches a second preset duration, wherein the second preset duration is less than the effective duration.

[0326] The present application also provides a first image acquisition system, such as Figure 1 As shown, the system includes a server 101, a web terminal 102 and an image acquisition device 103, wherein the web terminal is applied to a browser, wherein:

[0327] The web terminal 102 is used to send a first image acquisition request to the server, wherein the first image acquisition request does not carry the proprietary authentication information of the image acquisition device;

[0328] The server 101 is configured to send the first image acquisition request to the image acquisition device upon receiving the first image acquisition request sent by the web terminal;

[0329] The image acquisition device 103 is used to send proprietary authentication information and authentication failure information to the server when receiving the first image acquisition request;

[0330] The server 101 is further configured to receive the proprietary authentication information and authentication failure information sent by the image acquisition device; process the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser; and send the proprietary authentication information to the web end;

[0331] The web terminal 102 is further used to send a second image acquisition request carrying the proprietary authentication information to the image acquisition device;

[0332] The image acquisition device 103 is further configured to, upon receiving a second image acquisition request carrying the proprietary authentication information, send the image indicated by the second image acquisition request to the web end.

[0333] It can be seen that in the solution provided in the embodiment of the present application, since the server can receive proprietary authentication information and authentication failure information returned by the image acquisition device when sending the first image acquisition request to the image acquisition device, and can process the authentication failure information so that the authentication failure information does not trigger the browser's interception pop-up window, and send the proprietary authentication information to the web end, so that the web end can send a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and then the web end receives the image indicated by the second image acquisition request returned by the image acquisition device. In this way, not only will the browser not intercept the authentication failure information to pop up a window, thus solving the problem of browser pop-up windows, but the web end can also obtain the proprietary authentication information for obtaining the image required by the user, thereby improving the user experience.

[0334] The present application also provides a second image acquisition system, such as Figure 1 As shown, the system includes a server 101, a web terminal 102 and an image acquisition device 103, wherein the web terminal 102 is applied to a browser, wherein:

[0335] The web terminal 102 is used to send a first image acquisition request to the server, wherein the first image acquisition request does not carry the proprietary authentication information of the image acquisition device;

[0336] The server 101 is configured to send the first image acquisition request to the image acquisition device upon receiving the first image acquisition request sent by the web terminal;

[0337] The image acquisition device 103 is used to send proprietary authentication information and authentication failure information to the server when receiving the first image acquisition request;

[0338] The server 101 is further configured to receive the proprietary authentication information and authentication failure information sent by the image acquisition device; process the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser; and send a second image acquisition request carrying the proprietary authentication information to the image acquisition device;

[0339] The image acquisition device 103 is further configured to, upon receiving a second image acquisition request carrying the proprietary authentication information, send the image indicated by the second image acquisition request to the server;

[0340] The server 101 is also used to send the image to the web end.

[0341] It can be seen that in the solution provided by the embodiment of the present application, when the server sends the first image acquisition request to the image acquisition device, the proprietary authentication information and authentication failure information returned by the image acquisition device can be received, and the authentication failure information can be processed so that the authentication failure information will not trigger the browser's interception pop-up window, and the second image acquisition request carrying the proprietary authentication information can be sent to the image acquisition device so that the image acquisition device returns the image indicated by the second image acquisition request, and then sends the image to the web end. In this way, not only will the browser not intercept the authentication failure information to pop up a window, solving the problem of browser pop-up windows, but the web end can also obtain the image required by the user, improving the user experience, and the server sending the second image acquisition request to the image acquisition device can reduce the pressure on the browser.

[0342] The present application also provides a server, such as Fig.15 As shown, including:

[0343] Memory 1501, used for storing computer programs;

[0344] The processor 1502 is used to implement the first image acquisition method and the second image acquisition method described in any of the above embodiments when executing the program stored in the memory 1501.

[0345] In addition, the server may further include a communication bus and / or a communication interface, and the processor 1502, the communication interface, and the memory 1501 communicate with each other via the communication bus.

[0346] It can be seen that in the solution provided by the embodiment of the present application, when the server sends the first image acquisition request to the image acquisition device, the proprietary authentication information and authentication failure information returned by the image acquisition device can be received, and the authentication failure information can be processed so that the authentication failure information will not trigger the browser's interception pop-up window, and the proprietary authentication information is sent to the web end, so that the web end can send a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and then the web end receives the image indicated by the second image acquisition request returned by the image acquisition device, or the server sends a second image acquisition request carrying the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request, and then sends the image to the web end. In this way, not only will the browser not intercept the authentication failure information to pop up a window, solving the problem of browser pop-up windows, but the web end can also obtain the proprietary authentication information to obtain the image required by the user, improving the user experience, and the server sending the second image acquisition request to the image acquisition device can reduce the pressure on the browser.

[0347] The present application also provides a terminal, such as Fig.16 As shown, including:

[0348] Memory 1601, used for storing computer programs;

[0349] The processor 1602 is used to implement the third image acquisition method described in any of the above embodiments when executing the program stored in the memory 1601.

[0350] In addition, the terminal may further include a communication bus and / or a communication interface, and the processor 1602, the communication interface, and the memory 1601 communicate with each other via the communication bus.

[0351] It can be seen that in the solution provided in the embodiment of the present application, since the Web end sends the first image acquisition request to the server, the server can send the first image acquisition request to the image acquisition device, receive the proprietary authentication information returned by the image acquisition device, and process the authentication failure information so that the authentication failure information does not trigger the browser's interception pop-up window, and send the proprietary authentication information to the web end, so that the web end can send a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and then receive the image when the image acquisition device returns the image indicated by the second image acquisition request. In this way, not only will the browser not intercept the authentication failure information to pop up a window, thereby solving the problem of browser pop-ups, but the web end can also obtain the proprietary authentication information for obtaining the image required by the user, thereby improving the user experience.

[0352] The communication bus mentioned in the above server or terminal can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0353] The communication interface is used for communication between the above-mentioned server or terminal and other devices.

[0354] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0355] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0356] In another embodiment provided in the present application, a computer-readable storage medium is also provided, in which a computer program is stored. When the computer program is executed by a processor, the computer program implements the steps of any one of the first image acquisition method and the second image acquisition method, or the steps of the third image acquisition method.

[0357] In another embodiment provided in the present application, a computer program product comprising instructions is also provided, which, when executed on a computer, enables the computer to execute any one of the first image acquisition method and the second image acquisition method, or the third image acquisition method in the above-mentioned embodiments.

[0358] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a solid-state hard disk (SSD), etc.

[0359] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0360] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, system, server, terminal, computer-readable storage medium, and computer program product embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0361] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A method for image acquisition, characterized in that: A server applied to an image acquisition system, the system further comprising a web terminal and an image acquisition device, the web terminal being applied to a browser, the method comprising: In the case of receiving the first image acquisition request sent by the web end, sending the first image acquisition request to the image acquisition device, wherein the first image acquisition request does not carry the proprietary authentication information of the image acquisition device, the proprietary authentication information is a pre-set proprietary field stored in the image acquisition device, or the proprietary authentication information is a proprietary field updated by the image acquisition device according to a preset period; Receiving proprietary authentication information and authentication failure information sent by the image acquisition device; Processing the authentication failure information so that the authentication failure information does not trigger an interception pop-up window of the browser; The proprietary authentication information is sent to the web end, so that the web end sends a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and the web end receives the image indicated by the second image acquisition request returned by the image acquisition device.

2. The method according to claim 1, characterized in that The authentication failure information is an error status code; The step of processing the authentication failure information so that the authentication failure information does not trigger the browser's pop-up window interception includes: Processing the error status code to obtain a processed authentication status code so that the authentication failure information does not trigger an interception pop-up window of the browser; The step of sending the proprietary authentication information to the web terminal includes: The processed authentication status code and the proprietary authentication information are sent to the web end.

3. The method according to claim 1, characterized in that The step of sending the first image acquisition request to the image acquisition device upon receiving the first image acquisition request sent by the web terminal comprises: Receive an image acquisition request sent by the web terminal and start timing; When the timing duration reaches a first preset duration, based on the image acquisition request received within the timing duration, the image acquisition request is sent to the image acquisition device.

4. The method according to claim 3, characterized in that The image acquisition requests received within the timing period are multiple requests for the same image acquisition device; The step of sending the image acquisition request to the image acquisition device based on the image acquisition request received within the timing duration includes: Selecting an image acquisition request from a plurality of image acquisition requests as a first image acquisition request, and sending the first image acquisition request to the image acquisition device; or, The multiple image acquisition requests are combined into one image acquisition request as a first image acquisition request, and the first image acquisition request is sent to the image acquisition device.

5. A method for acquiring an image, characterized in that: A server applied to an image acquisition system, the system further comprising a web terminal and an image acquisition device, the web terminal being applied to a browser, the method comprising: In the case of receiving the first image acquisition request sent by the web end, sending the first image acquisition request to the image acquisition device, wherein the first image acquisition request does not carry the proprietary authentication information of the image acquisition device, the proprietary authentication information is a pre-set proprietary field stored in the image acquisition device, or the proprietary authentication information is a proprietary field updated by the image acquisition device according to a preset period; Receiving proprietary authentication information and authentication failure information sent by the image acquisition device; Processing the authentication failure information so that the authentication failure information does not trigger an interception pop-up window of the browser; Sending a second image acquisition request carrying the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server; Send the image to the web end.

6. The method according to claim 5, characterized in that The step of processing the authentication failure information so that the authentication failure information does not trigger the browser's pop-up window interception includes: The authentication failure information is not sent to the web end, so that the authentication failure information does not trigger the interception pop-up window of the browser.

7. The method according to claim 5, characterized in that The step of sending a second image acquisition request carrying the proprietary authentication information to the image acquisition device so that the image acquisition device returns the image indicated by the second image acquisition request to the server includes: Sending a second image acquisition request including the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server if the proprietary authentication information is authenticated; or A second image acquisition request including the proprietary authentication information and the user authentication information is sent to the image acquisition device. When the image acquisition device authenticates both the proprietary authentication information and the user authentication information, the image indicated by the second image acquisition request is returned to the server, wherein the user authentication information includes an account number and a password.

8. The method according to claim 5, characterized in that The step of sending the first image acquisition request to the image acquisition device upon receiving the first image acquisition request sent by the web terminal comprises: Receive an image acquisition request sent by the web terminal and start timing; When the timing duration reaches a first preset duration, based on the image acquisition request received within the timing duration, the image acquisition request is sent to the image acquisition device.

9. The method according to claim 8, characterized in that The image acquisition requests received within the timing period are multiple requests for the same image acquisition device; The step of sending the image acquisition request to the image acquisition device based on the image acquisition request received within the timing duration includes: Selecting an image acquisition request from a plurality of image acquisition requests as a first image acquisition request, and sending the first image acquisition request to the image acquisition device; or, The multiple image acquisition requests are combined into one image acquisition request as a first image acquisition request, and the first image acquisition request is sent to the image acquisition device.

10. A method for acquiring an image, characterized in that: A web terminal applied to an image acquisition system, the system further comprising a server and an image acquisition device, the web terminal being applied to a browser, the method comprising: Sending a first image acquisition request to the server so that the server sends the first image acquisition request to the image acquisition device, receiving proprietary authentication information and authentication failure information sent by the image acquisition device, and processing the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser, and sending the processed authentication failure information and the proprietary authentication information to the web end, wherein the proprietary authentication information is a pre-set proprietary field stored in the image acquisition device, or the proprietary authentication information is a proprietary field updated by the image acquisition device according to a preset period; Sending a second image acquisition request carrying the proprietary authentication information to the image acquisition device; Receive the image indicated by the second image acquisition request returned by the image acquisition device.

11. The method according to claim 10, characterized in that The step of sending a second image acquisition request carrying the proprietary authentication information to the image acquisition device comprises: Sending a second image acquisition request including the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the web end when the proprietary authentication information is authenticated; or, A second image acquisition request including the proprietary authentication information and the user authentication information is sent to the image acquisition device. When the image acquisition device authenticates both the proprietary authentication information and the user authentication information, the image indicated by the second image acquisition request is returned to the web end, wherein the user authentication information includes an account number and a password.

12. The method according to claim 10 or 11, characterized in that: The step of sending the first image acquisition request to the server comprises: In the case where multiple image acquisition instructions for the same image acquisition device are acquired, generating an image acquisition request as a first image acquisition request; Sending the first image acquisition request to the server.

13. The method according to claim 10 or 11, characterized in that: The proprietary authentication information has a validity period; Before the step of sending the first image acquisition request to the server, the method further includes: Determine whether the proprietary authentication information for the image acquisition device is stored locally, wherein the proprietary authentication information is the proprietary authentication information of the image acquisition device acquired and stored before the image acquisition device was last acquired; In the case where the proprietary authentication information for the image acquisition device is not stored locally, executing the step of sending the first image acquisition request to the server; The method further comprises: When receiving the proprietary authentication information sent by the server, storing the proprietary authentication information and starting timing; When the timing duration reaches a second preset duration, the stored proprietary authentication information is deleted, wherein the second preset duration is shorter than the effective duration.

14. An image acquisition device, characterized in that: A server applied to an image acquisition system, the system further comprising a web terminal and an image acquisition device, the web terminal being applied to a browser, the device comprising: A first request sending module, configured to send the first image acquisition request to the image acquisition device when receiving the first image acquisition request sent by the web terminal, wherein the first image acquisition request does not carry proprietary authentication information of the image acquisition device, the proprietary authentication information is a pre-set proprietary field stored in the image acquisition device, or the proprietary authentication information is a proprietary field updated by the image acquisition device according to a preset period; A first information receiving module, used for receiving proprietary authentication information and authentication failure information sent by the image acquisition device; A first information processing module, used for processing the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser; The first information sending module is used to send the processed authentication failure information and the proprietary authentication information to the web end, so that the web end sends a second image acquisition request carrying the proprietary authentication information to the image acquisition device, and the web end receives the image indicated by the second image acquisition request returned by the image acquisition device.

15. An image acquisition device, characterized in that: A server applied to an image acquisition system, the system further comprising a web terminal and an image acquisition device, the web terminal being applied to a browser, the device comprising: a second request sending module, configured to send the first image acquisition request to the image acquisition device upon receiving the first image acquisition request sent by the web terminal, wherein the first image acquisition request does not carry proprietary authentication information of the image acquisition device, the proprietary authentication information is a pre-set proprietary field stored in the image acquisition device, or the proprietary authentication information is a proprietary field updated by the image acquisition device according to a preset period; A second information receiving module, used to receive the proprietary authentication information and authentication failure information sent by the image acquisition device; A second information processing module, used for processing the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser; A third request sending module, configured to send a second image acquisition request carrying the proprietary authentication information to the image acquisition device, so that the image acquisition device returns the image indicated by the second image acquisition request to the server; An image sending module is used to send the image to the web end.

16. An image acquisition device, characterized in that: A web terminal applied to an image acquisition system, the system further comprising a server and an image acquisition device, the web terminal being applied to a browser, the device comprising: A fourth request sending module, used to send a first image acquisition request to the server, so that the server sends the first image acquisition request to the image acquisition device, receives proprietary authentication information and authentication failure information sent by the image acquisition device, processes the authentication failure information, so that the authentication failure information does not trigger the interception pop-up window of the browser, and sends the processed authentication failure information and the proprietary authentication information to the web end, wherein the proprietary authentication information is a pre-set proprietary field stored in the image acquisition device, or the proprietary authentication information is a proprietary field updated by the image acquisition device according to a preset period; a fifth request sending module, configured to send a second image acquisition request carrying the proprietary authentication information to the image acquisition device; The image receiving module is used to receive the image indicated by the second image acquisition request returned by the image acquisition device.

17. An image acquisition system, characterized in that: The system includes a server, a web terminal and an image acquisition device, wherein the web terminal is applied to a browser, wherein: The web end is used to send a first image acquisition request to the server, wherein the first image acquisition request does not carry the proprietary authentication information of the image acquisition device, and the proprietary authentication information is a pre-set proprietary field stored in the image acquisition device, or the proprietary authentication information is a proprietary field updated by the image acquisition device according to a preset period; The server is configured to send the first image acquisition request to the image acquisition device when receiving the first image acquisition request sent by the web terminal; The image acquisition device is used to send proprietary authentication information and authentication failure information to the server when receiving the first image acquisition request; The server is further configured to receive the proprietary authentication information and authentication failure information sent by the image acquisition device; process the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser; and send the proprietary authentication information to the web end; The web end is further used to send a second image acquisition request carrying the proprietary authentication information to the image acquisition device; The image acquisition device is further configured to, upon receiving a second image acquisition request carrying the proprietary authentication information, send the image indicated by the second image acquisition request to the web end.

18. An image acquisition system, characterized in that: The system includes a server, a web terminal and an image acquisition device, wherein the web terminal is applied to a browser, wherein: The web end is used to send a first image acquisition request to the server, wherein the first image acquisition request does not carry the proprietary authentication information of the image acquisition device, and the proprietary authentication information is a pre-set proprietary field stored in the image acquisition device, or the proprietary authentication information is a proprietary field updated by the image acquisition device according to a preset period; The server is configured to send the first image acquisition request to the image acquisition device when receiving the first image acquisition request sent by the web terminal; The image acquisition device is used to send proprietary authentication information and authentication failure information to the server when receiving the first image acquisition request; The server is further configured to receive the proprietary authentication information and authentication failure information sent by the image acquisition device; process the authentication failure information so that the authentication failure information does not trigger the interception pop-up window of the browser; and send a second image acquisition request carrying the proprietary authentication information to the image acquisition device; The image acquisition device is further configured to, upon receiving a second image acquisition request carrying the proprietary authentication information, send the image indicated by the second image acquisition request to the server; The server is also used to send the image to the web end.

19. A server, characterized in that: include: Memory, used to store computer programs; A processor, for implementing any of the methods described in claims 1-9 when executing a program stored in a memory.

20. A terminal, characterized in that: include: Memory, used to store computer programs; A processor, for implementing any of the methods described in claims 10-13 when executing a program stored in a memory.

21. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described in any one of claims 1 to 9 or any one of claims 10 to 13 is implemented.