Equipment upgrading method and system and server

Abstract

The invention discloses an equipment upgrading method and system and a server, and belongs to the field of communication, and the method mainly comprises the steps that a front-end cross-domain component deployed in a user terminal browser sends a first request to a first server deployed in a private network to obtain recommended upgrading task information of managed equipment; the front-end cross-domain component constructs and sends a second request to a second server deployed in the public network based on the recommended upgrade task information, and performs cross-domain authentication; after the authentication is passed, the front-end cross-domain component initiates a third request and a fourth request to the second server for querying and downloading the recommended upgrading file; and the front-end cross-domain component uploads the recommended upgrading file to the first server, notifies the first server to update the state of the recommended upgrading task, and prompts a user to confirm the execution of the recommended upgrading task. According to the method, the browser cross-domain request technology is ingeniously utilized, and the pushing function of network equipment upgrading in the private network deployment environment is achieved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of data communication, in particular to a device upgrading method, system and server. BACKGROUND

[0002] When a device manufacturer discovers that a network device has a major defect or functional update, the user needs to be recommended to upgrade the network device, and the upgrade instruction, upgrade file and file transfer service need to be provided when the network device is upgraded. The current network device upgrading method mainly includes manual upgrading and network management system upgrading.

[0003] Manual upgrading refers to that the maintenance personnel first uploads the upgrade file from the local to the file transfer service, and then logs in to the network device through the command line interface to execute the upgrade instruction. When the upgrade instruction is executed, the latest uploaded upgrade file is updated to the network device from the file transfer service, so as to complete the upgrading.

[0004] The network management system generally has a built-in file transfer service. The maintenance personnel creates a network device upgrade task through the graphical interface provided by the network management system, selects the device range to be upgraded, executes the time, and uploads the upgrade file. The network management system replaces the maintenance personnel to complete the upgrading of a batch of network devices. The network management system upgrading can be batch and simultaneous compared with manual upgrading, which solves the efficiency problem of a large number of device upgrading, but has the following defects: During the after-sales maintenance stage of the device manufacturer, the network device is usually deployed in a private network environment. Neither the network device itself nor the network management system can access public network resources. The device manufacturer needs to manually inform the maintenance personnel which network devices are recommended to upgrade, and provide the upgrade file for the maintenance personnel. The maintenance personnel operates on the network management system to complete the upgrading. There are problems of high manual communication cost, low efficiency and easy to make mistakes. Moreover, as the after-sales range of the device manufacturer becomes larger and the number of devices sold increases, the communication cost will linearly increase.

[0005] Therefore, there is an urgent need for a technology that can automatically upgrade or update the network device in a private network environment. SUMMARY

[0006] The purpose of the present application is to solve the problems of high communication cost, low efficiency and easy to make mistakes in the traditional manual communication and sending upgrade file by the maintenance personnel or in the network management system when the device manufacturer initiates the recommended upgrading activity in the private network deployment scenario, and to provide a device upgrading method, system and server.

[0007] The purpose of the present application is achieved by the following technical solutions: In a first aspect, a device upgrading method is provided, comprising the following steps: S1. A front-end cross-domain component deployed in a user terminal browser sends a first request to a first service deployed in a private network to obtain recommended upgrade task information of a managed device; S2. The first service returns the recommended upgrade task information to the front-end cross-domain component; S3. The front-end cross-domain component constructs and sends a second request to a second service deployed in a public network based on the recommended upgrade task information; S4. The second service performs cross-domain authentication based on the second request and returns a response to the front-end cross-domain component as to whether the authentication is passed; S5. After the authentication is passed, the front-end cross-domain component initiates a third request to the second service based on the recommended upgrade task information to query whether there is recommended upgrade software matching the recommended upgrade task information, and if so, performs step S6, otherwise waits for the next scheduling; S6. The second service returns the matching recommended upgrade software information including a software download URL to the front-end cross-domain component; S7. The front-end cross-domain component initiates a fourth request to the second service for requesting to download the recommended upgrade file; S8. The second service returns the downloaded recommended upgrade file to the front-end cross-domain component; S9. The front-end cross-domain component uploads the recommended upgrade file to the first service, notifies the first service to update the status of the recommended upgrade task, and prompts the user to confirm the execution of the recommended upgrade task; S10. The first service performs device upgrade based on the recommended upgrade file.

[0008] In some embodiments, the front-end cross-domain component periodically initiates the first request to the first service and the third request to the second service in a polling manner.

[0009] In some embodiments, the recommended upgrade task information includes a device software version release service address, a device software version release service authentication username, and a password; and the second service performs cross-domain authentication based on the second request, including: The second service checks whether the device software version release service address, the device software version release service authentication username, and the password are correct, and if so, the authentication is passed, allowing the front-end cross-domain component to cross-domain access the second service; otherwise, the authentication fails, and cross-domain access to the second service is not allowed.

[0010] In a second aspect, a device upgrade method is provided, including the following steps: S1. A front-end cross-domain component deployed in a user terminal browser sends a first request to a first service end deployed in a private network to obtain recommended upgrade task information of a managed device; S2. The front-end cross-domain component constructs and sends a second request to a second service end deployed in a public network based on the recommended upgrade task information; the second request is a cross-domain authentication request, and the recommended upgrade task information includes a device software version publishing service address, a device software version publishing service authentication username, a password, and a list of devices to be upgraded; S3. The front-end cross-domain component receives an authentication response from the second service end, and after authentication passes, initiates a third request to the second service end based on the recommended upgrade task information to query whether there is recommended upgrade software matching the recommended upgrade task information, and if so, performs step S4, otherwise waits for the next scheduling; S4. The front-end cross-domain component initiates a fourth request to the second service end for requesting to download recommended upgrade files; S5. The front-end cross-domain component receives the downloaded recommended upgrade files and uploads them to the first service end; notifies the first service end to update the state of the recommended upgrade task, and prompts the user to confirm the execution of the recommended upgrade task.

[0011] In a third aspect, a device upgrade method is provided, including the following steps: S1. A second service end deployed in a public network receives a second request sent by a front-end cross-domain component based on obtained recommended upgrade task information for cross-domain authentication, and returns a response to the front-end cross-domain component about whether the authentication passes; the recommended upgrade task information includes a device software version publishing service address, a device software version publishing service authentication username, a password, and a list of devices to be upgraded; S2. The second service end receives a third request sent by the front-end cross-domain component based on the recommended upgrade task information, queries whether there is recommended upgrade software matching the recommended upgrade task information, and if so, performs step S3, otherwise waits for the next scheduling; S3. The second service end returns matching recommended upgrade software information including a software download URL to the front-end cross-domain component; S4. The second service end receives a fourth request for requesting to download recommended upgrade files from the front-end cross-domain component, downloads and returns the recommended upgrade files to the front-end cross-domain component.

[0012] In a fourth aspect, a device upgrade method is provided, including the following steps: S1. A first service deployed in a private network receives a first request of a front-end cross-domain component, and returns recommended upgrade task information to the front-end cross-domain component; the recommended upgrade task information includes a device software version release service address, a device software version release service authentication username, a password, and a list of devices to be upgraded. S2. The first service receives a recommended upgrade file uploaded by the front-end cross-domain component, and updates a state of the recommended upgrade task. S3. The first service performs device upgrade based on the recommended upgrade file.

[0013] In a fifth aspect, a device upgrade system is provided, comprising: A front-end cross-domain component deployed in a user terminal browser, configured to perform the method in the second aspect; A first service deployed in a private network, configured to perform the method in the third aspect; A second service deployed in a public network, configured to perform the method in the fourth aspect.

[0014] In a sixth aspect, a front-end cross-domain component is provided, comprising: A first request unit configured to send a first request to a first service deployed in a private network to obtain recommended upgrade task information of a managed device; A second request unit configured to construct and send a second request to a second service deployed in a public network based on the recommended upgrade task information; the second request is a cross-domain authentication request, and the recommended upgrade task information includes a device software version release service address, a device software version release service authentication username, a password, and a list of devices to be upgraded; A third request unit configured to receive an authentication response from the second service, and initiate a third request to the second service based on the recommended upgrade task information after authentication is passed to query whether there is recommended upgrade software matching the recommended upgrade task information; A fourth request unit configured to initiate a fourth request to the second service to request downloading of a recommended upgrade file when there is recommended upgrade software matching the recommended upgrade task information; An upgrade file receiving unit configured to receive the downloaded recommended upgrade file and upload it to the first service; A task update notification unit configured to notify the first service to update a state of the recommended upgrade task; A prompt unit configured to prompt a user to confirm execution of the recommended upgrade task.

[0015] In a seventh aspect, a service end for providing a device software version release service is provided, comprising: An authentication unit is configured to receive a second request of a front-end cross-domain component for cross-domain authentication, and return a response of whether the authentication is passed to the front-end cross-domain component; the second request is a cross-domain authentication request constructed based on obtained recommended upgrade task information, and the recommended upgrade task information includes a device software version publishing service address, a device software version publishing service authentication username, a password, and a list of devices to be upgraded; A matching query unit is configured to receive a third request sent by the front-end cross-domain component based on the recommended upgrade task information, query whether there is recommended upgrade software matching the recommended upgrade task information, and return the matching recommended upgrade software information to the front-end cross-domain component; An upgrade file downloading unit is configured to receive a fourth request of the front-end cross-domain component for requesting to download recommended upgrade files, download and return the recommended upgrade files to the front-end cross-domain component.

[0016] In an eighth aspect, a server is provided for providing a device software version upgrade service, comprising: A recommended upgrade task information query unit is configured to receive a first request of a front-end cross-domain component, and return recommended upgrade task information to the front-end cross-domain component; the recommended upgrade task information includes a device software version publishing service address, a device software version publishing service authentication username, a password, and a list of devices to be upgraded; An upgrade file receiving unit is configured to receive recommended upgrade files uploaded by the front-end cross-domain component; An upgrade task state updating unit is configured to update a state of a recommended upgrade task; A device upgrade executing unit is configured to perform device upgrade based on the recommended upgrade files.

[0017] It should be further explained that the technical features of the above aspects can be combined or replaced with each other to form new technical solutions without conflict.

[0018] Compared with the prior art, the present application has the following advantages: The front-end component running in the user terminal browser queries a recommended upgrade task from a first server in a private network, then constructs a cross-domain request based on the recommended upgrade task information, queries and downloads matching upgrade files from a second server on a public network, and finally uploads the files back to the first server and updates the task state. By using the cross-domain request mechanism of the browser, the user terminal is ingeniously used as a bridge to realize automatic and safe transmission of the upgrade files from the public network to the private network, and effectively solve the technical problems of low efficiency, high cost and error-prone caused by manual operation of device upgrade in the private network isolation environment. BRIEF DESCRIPTION OF DRAWINGS

[0019] Figure 1The device upgrade method flowchart in the embodiment 1 of the present application; Figure 2 The device upgrade method flowchart in the embodiment 2 of the present application; Figure 3 The device upgrade method flowchart in the embodiment 3 of the present application; Figure 4 The device upgrade method flowchart in the embodiment 4 of the present application; Figure 5 The device upgrade system structure diagram in the embodiment 5 of the present application; Figure 6 The device upgrade system working flowchart. DETAILED DESCRIPTION

[0020] The technical solutions of the present application will be described clearly and completely below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the accompanying drawings can be arranged and designed in various different configurations. Based on the embodiments in the present application, all the other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0021] It should be noted that the defects of the above prior art solutions are the results obtained by the inventors after practice and careful study. Therefore, the discovery process of the above problems and the solutions proposed by the embodiments of the present application to the above problems should be the contributions made by the inventors to the present application in the process of invention and creation, and should not be understood as technical content known to those skilled in the art.

[0022] Embodiment 1 Referring to Figure 1 A device upgrade method, comprising the following steps: S1. A front-end cross-domain component deployed in a user terminal browser sends a first request to a first service end deployed in a private network to obtain recommended upgrade task information of a managed device; S2. The first service end returns the recommended upgrade task information to the front-end cross-domain component; S3. The front-end cross-domain component constructs and sends a second request to a second service end deployed in a public network based on the recommended upgrade task information; S4. The second service end performs cross-domain authentication based on the second request, and returns a response of whether the authentication is passed to the front-end cross-domain component; S5. The front-end cross-domain component initiates a third request to the second server based on the recommended upgrade task information after authentication passes, queries whether there is recommended upgrade software matching the recommended upgrade task information, if yes, step S6 is executed, otherwise waits for next scheduling; S6. The second server returns the matching recommended upgrade software information containing software download URL to the front-end cross-domain component; S7. The front-end cross-domain component initiates a fourth request to the second server for requesting to download recommended upgrade file; S8. The second server returns the downloaded recommended upgrade file to the front-end cross-domain component; S9. The front-end cross-domain component uploads the recommended upgrade file to the first server, notifies the first server to update the state of the recommended upgrade task, and prompts the user to confirm the execution of the recommended upgrade task (such as prompting that the recommended upgrade task is ready, waiting for upgrade); S10. After the user confirms, the first server performs device upgrade based on the recommended upgrade file.

[0023] Exemplarily, the front-end cross-domain component periodically initiates the first request to the first server and the third request to the second server in a polling manner. The third request carries the device model and current software version information in the to-be-upgraded device list included in the recommended upgrade task information.

[0024] Exemplarily, the recommended upgrade task information includes device software version publishing service address (URL address), device software version publishing service authentication username, password, and to-be-upgraded device list, wherein the to-be-upgraded device list gives corresponding device model and current software version information; the second server performs cross-domain authentication based on the second request, including: The second server checks whether the device software version publishing service address, device software version publishing service authentication username, and password are correct, if yes, authentication passes, and the front-end cross-domain component is allowed to access the second server cross-domain; otherwise, authentication fails, and cross-domain access to the second server is not allowed.

[0025] Exemplarily, in step S8, the second server downloads the recommended upgrade file corresponding to the URL address, and returns the binary stream of the recommended upgrade file to the user terminal browser for storage. The implementation can be that the front-end cross-domain component sets a queue on the local storage for storing the downloaded recommended upgrade file binary stream.

[0026] Embodiment 2 Referring to Figure 2 A device upgrade method is provided, including the following steps: S1. A front-end cross-domain component deployed in a user terminal browser sends a first request to a first service end deployed in a private network to obtain recommended upgrade task information of a managed device; S2. The front-end cross-domain component constructs and sends a second request to a second service end deployed in a public network based on the recommended upgrade task information; the second request is a cross-domain authentication request, and the recommended upgrade task information includes a device software version publishing service address, a device software version publishing service authentication username, a password, and a list of devices to be upgraded. S3. The front-end cross-domain component receives an authentication response from the second service end and initiates a third request to the second service end based on the recommended upgrade task information after authentication passes to query whether there is recommended upgrade software matching the recommended upgrade task information, and if so, step S4 is executed, otherwise, the next scheduling is waited. S4. The front-end cross-domain component initiates a fourth request to the second service end for requesting to download recommended upgrade files. S5. The front-end cross-domain component receives the downloaded recommended upgrade files and uploads them to the first service end; notifies the first service end to update the state of the recommended upgrade task, and prompts the user to confirm the execution of the recommended upgrade task.

[0027] Specifically, the front-end cross-domain component supports initiating requests to the second service end and the first service end at different URL addresses, which can query recommended upgrade task information from the first service end and query and download recommended upgrade files from the second service end.

[0028] Embodiment 3 With reference to Figure 3 A device upgrade method is provided, comprising the following steps: S1. A second service end deployed in a public network receives a second request constructed by a front-end cross-domain component based on obtained recommended upgrade task information for cross-domain authentication, and returns a response to the front-end cross-domain component about whether the authentication passes; the second request is a cross-domain authentication request, and the recommended upgrade task information includes a device software version publishing service address, a device software version publishing service authentication username, a password, and a list of devices to be upgraded. S2. The second service end receives a third request constructed by the front-end cross-domain component based on obtained recommended upgrade task information to query whether there is recommended upgrade software matching the recommended upgrade task information, and if so, step S3 is executed, otherwise, the next scheduling is waited; in this S2 step, the list of devices to be upgraded in the recommended upgrade task information can be carried in the third request, and the list of devices to be upgraded includes device models and current software version information.

[0029] S3. The second server returns the matched recommended upgrade software information containing the software download URL to the front-end cross-domain component; S4. The second server receives the fourth request of the front-end cross-domain component for requesting to download the recommended upgrade file, downloads and returns the recommended upgrade file to the front-end cross-domain component.

[0030] Embodiment 4 With reference to Figure 4 , a device upgrade method is provided, comprising the following steps: S1. The first server deployed in a private network receives a first request of a front-end cross-domain component, and returns recommended upgrade task information to the front-end cross-domain component; the recommended upgrade task information comprises a device software version release service address, a device software version release service authentication username, a password, and a list of devices to be upgraded. S2. The first server receives a recommended upgrade file uploaded by the front-end cross-domain component, and updates the state of the recommended upgrade task. S3. The first server performs device upgrade based on the recommended upgrade file.

[0031] Embodiment 5 With reference to Figure 5 , a device upgrade system is provided, comprising: A front-end cross-domain component deployed in a user terminal browser, configured to perform the method described in Embodiment 2; A first server deployed in a private network, configured to perform the method described in Embodiment 3; A second server deployed in a public network, configured to perform the method described in Embodiment 4.

[0032] Specifically, the networking feature of the present application requires that the PC of the user (operation and maintenance personnel) can access the public network and the private network. This networking feature is universal. Through the PC where the browser is located, the cross-public network and private network, the large screen or the homepage is always open. The cross-domain request technology is used to complete the recommended upgrade effect of the private network deployment device.

[0033] Exemplarily, as Figure 6 shown, the working process of the system is given: The front-end cross-domain component requests the device software version upgrade service from the first server, and queries the recommended upgrade task information. The first server returns the recommended upgrade task information. The recommended upgrade task information comprises a device software release service URL address, a username for an authentication interface, a password, a device model corresponding to a list of devices to be upgraded in a current task, and current software version information.

[0034] The front-end cross-domain component requests a device software version publishing service from a second service end, first performs authentication (cross-domain authentication), the second service end responds to the front-end cross-domain component whether the authentication is passed: after the authentication is passed, the front-end cross-domain component again carries device model and current software version information, and queries whether there is recommended upgrade software information meeting the condition, and if yes, corresponding upgrade file URL address is obtained.

[0035] The front-end cross-domain component requests to download the recommended upgrade file from the second service end, the second service end downloads the recommended upgrade file of the corresponding URL address to the local browser storage, and the front-end cross-domain component exists a queue in the local storage, and stores the binary stream of the downloaded recommended upgrade file.

[0036] The front-end cross-domain component requests to upload the recommended upgrade file to the first service end, and synchronously uploads the binary stream of the recommended upgrade file to the first service end. The first service end returns a mark of successful uploading.

[0037] After the front-end cross-domain component uploads the recommended upgrade file, the front-end cross-domain component requests the first service end to update the state of the recommended upgrade task, the first service end updates the state of the recommended upgrade task, and returns a mark of successful modification; The front-end cross-domain component synchronously sends a notification to the user (operation and maintenance personnel), prompts that the recommended upgrade task is ready for upgrade, and waits for upgrade. After the operation and maintenance personnel confirm, the recommended upgrade task performs upgrade.

[0038] Embodiment 6 A front-end cross-domain component is provided, comprising: A first request unit configured to send a first request to a first service end deployed in a private network to obtain recommended upgrade task information of a managed device; A second request unit configured to construct and send a second request to a second service end deployed in a public network based on the recommended upgrade task information; the second request is a cross-domain authentication request, and the recommended upgrade task information includes a device software version publishing service address, a device software version publishing service authentication username, a password, and a list of devices to be upgraded; A third request unit configured to receive an authentication response from the second service end, and initiate a third request to the second service end based on the obtained recommended upgrade task information to query whether there is recommended upgrade software matching the recommended upgrade task information after the authentication is passed; A fourth request unit configured to initiate a fourth request for requesting to download a recommended upgrade file to the second service end when there is recommended upgrade software matching the recommended upgrade task information; An upgrade file receiving unit configured to receive the downloaded recommended upgrade file and upload to the first service end; A task update notification unit configured to notify the first service end to update the state of the recommended upgrade task; The prompt unit is used to prompt the user to confirm the execution of the recommended upgrade task.

[0039] Example 7 Provide a server for providing device software version release services, including: The authentication unit is used to receive a second request from the front-end cross-domain component to perform cross-domain authentication, and return a response to the front-end cross-domain component indicating whether the authentication is successful; the second request is a cross-domain authentication request constructed based on the obtained recommended upgrade task information, which includes the device software version release service address, device software version release service authentication username, password, and a list of devices to be upgraded; The matching query unit is used to receive a third request constructed by the front-end cross-domain component based on the obtained recommended upgrade task information, query whether there is a recommended upgrade software that matches the recommended upgrade task information, and return the matched recommended upgrade software information to the front-end cross-domain component; The upgrade file download unit is used to receive a fourth request from the front-end cross-domain component to request the download of a recommended upgrade file, download the recommended upgrade file and return it to the front-end cross-domain component.

[0040] The server-side device software version release service is responsible for releasing recommended upgrade files and corresponding compatible models. This service includes functions such as authentication, business query, and device upgrade file download. The authentication unit sets up an authentication interface to provide authentication services, ensuring the information security of the device software version release service deployed on the public internet; the matching query unit sets up a business query interface to receive query parameters such as device model and current software version, and returns links to recommended device upgrade files that meet the criteria; the upgrade file download unit sets up a device upgrade file download interface to receive download link parameters and return the binary stream of the recommended upgrade file.

[0041] Example 8 Provide a server for providing device software version upgrade services, including: The recommended upgrade task information query unit is used to receive the first request from the front-end cross-domain component and return the recommended upgrade task information to the front-end cross-domain component; the recommended upgrade task information includes the device software version release service address, the device software version release service authentication username and password, and the list of devices to be upgraded; The upgrade file receiving unit is used to receive recommended upgrade files uploaded by front-end cross-domain components; The upgrade task status update unit is used to update the status of recommended upgrade tasks; The device upgrade execution unit is used to perform device upgrades based on the recommended upgrade file. The Recommended Upgrade Task Creation Unit is used to create recommended upgrade tasks.

[0042] Exemplarily, the service end is a controller service end of the device, and in addition to providing the device upgrade task logic similar to the selection of the device, uploading of the upgrade file, and selection of the upgrade time in the prior art, the device software version upgrade service also provides recommended upgrade task configuration and logic. The device software version upgrade service contains functions such as recommended upgrade task creation, query, state update, and upgrade file uploading. Specifically, a recommended upgrade task creation unit sets a recommended upgrade task creation interface, provides a creation task function, and task parameters contain a device software version release service address, a device software version release service authentication username, a password, a list of devices to be upgraded, and the like; a recommended upgrade task information query unit sets a recommended upgrade task query interface connected with a front-end cross-domain component, and provides query of task related information; an upgrade task state update unit sets a recommended upgrade task update interface, and provides update of task state information. An upgrade file receiving unit sets an upgrade file uploading interface, and provides a function of receiving upgrade file uploading.

[0043] The above detailed description is a detailed description of the present application, and cannot be considered as limiting the specific embodiments of the present application to these descriptions. For ordinary skilled persons in the technical field to which the present application belongs, a number of simple deductions and substitutions can be made without departing from the concept of the present application, and all of them should be considered as falling within the protection scope of the present application.

Claims

1. A method for upgrading equipment, characterized in that, Includes the following steps: S1. The front-end cross-domain component deployed in the user terminal browser sends a first request to the first server deployed in the private network to obtain the recommended upgrade task information of the managed device; S2. The first server returns recommended upgrade task information to the front-end cross-domain component; S3. The front-end cross-domain component, based on the recommended upgrade task information, constructs and sends a second request to the second server deployed on the public network; S4. The second server performs cross-domain authentication based on the second request and returns a response to the front-end cross-domain component indicating whether the authentication is successful; S5. After successful authentication, the front-end cross-domain component initiates a third request to the second server based on the recommended upgrade task information to query whether there is a recommended upgrade software that matches the recommended upgrade task information. If there is, step S6 is executed; otherwise, the system waits for the next scheduling. S6. The second server returns recommended upgrade software information containing the matching software download URL to the front-end cross-domain component; S7. The front-end cross-domain component initiates a fourth request to the second server to request the download of the recommended upgrade file; S8. The second server returns a recommended upgrade file to the front-end cross-domain component; S9. The front-end cross-domain component uploads the recommended upgrade file to the first server, notifies the first server to update the status of the recommended upgrade task, and prompts the user to confirm the execution of the recommended upgrade task; S10. The first server upgrades the device based on the recommended upgrade file.

2. The equipment upgrade method according to claim 1, characterized in that, The front-end cross-domain component periodically sends the first request to the first server and the third request to the second server in a polling manner.

3. The equipment upgrade method according to claim 1, characterized in that, The recommended upgrade task information includes the device software version release service address, device software version release service authentication username, and password; The second server performs cross-domain authentication based on the second request, including: The second server checks whether the device software version release service address, device software version release service authentication username, and password are correct. If correct, authentication is successful, and the front-end cross-domain component is allowed to access the second server across domains; otherwise, authentication fails, and cross-domain access to the second server is not allowed.

4. A method for upgrading equipment, characterized in that, Includes the following steps: S1. The front-end cross-domain component deployed in the user terminal browser sends a first request to the first server deployed in the private network to obtain the recommended upgrade task information of the managed device; S2. The front-end cross-domain component, based on the recommended upgrade task information, constructs and sends a second request to the second server deployed on the public network; S3. The front-end cross-domain component receives the authentication response from the second server, and after successful authentication, initiates a third request to the second server based on the recommended upgrade task information to query whether there is a recommended upgrade software that matches the recommended upgrade task information. If there is, step S4 is executed; otherwise, wait for the next scheduling. S4. The front-end cross-domain component initiates a fourth request to the second server to request the download of the recommended upgrade file; S5. The front-end cross-domain component receives the recommended upgrade file and uploads it to the first server; it notifies the first server to update the status of the recommended upgrade task and prompts the user to confirm the execution of the recommended upgrade task.

5. A method for upgrading equipment, characterized in that, Includes the following steps: S1. The second server deployed on the public network receives the second request sent by the front-end cross-domain component based on the obtained recommended upgrade task information, performs cross-domain authentication, and returns a response to the front-end cross-domain component indicating whether the authentication is successful. S2. The second server receives the third request sent by the front-end cross-domain component based on the recommended upgrade task information, and queries whether there is a recommended upgrade software that matches the recommended upgrade task information. If there is, step S3 is executed; otherwise, wait for the next scheduling. S3. The second server returns recommended upgrade software information containing the matching software download URL to the front-end cross-domain component; S4. The second server receives the fourth request from the front-end cross-domain component to request the download of the recommended upgrade file, downloads and returns the recommended upgrade file to the front-end cross-domain component.

6. A method for upgrading equipment, characterized in that, Includes the following steps: S1. The first server deployed on the private network receives the first request from the front-end cross-domain component and returns recommended upgrade task information to the front-end cross-domain component; S2. The first server receives the recommended upgrade file uploaded by the front-end cross-domain component and updates the status of the recommended upgrade task; S3. The first server performs a device upgrade based on the recommended upgrade file.

7. A device upgrade system, characterized in that, include: A front-end cross-domain component deployed in a user terminal browser is configured to perform the method described in claim 4; The first server, deployed on a private network, is configured to execute the method described in claim 5. A second server deployed on a public network is configured to execute the method described in claim 6.

8. A front-end cross-domain component, characterized in that, include: The first request unit is used to send a first request to the first server deployed on the private network in order to obtain recommended upgrade task information for the managed device. The second request unit is used to construct and send a second request to a second server deployed on a public network based on the recommended upgrade task information. The third request unit is used to receive the authentication response from the second server, and after the authentication is successful, to initiate a third request to the second server based on the recommended upgrade task information to query whether there is a recommended upgrade software that matches the recommended upgrade task information; The fourth request unit is used to initiate a fourth request to the second server to request the download of the recommended upgrade file when there is a recommended upgrade software that matches the recommended upgrade task information. An upgrade file receiving unit is used to receive recommended upgrade files and upload them to the first server. The task update notification unit is used to notify the first server to update the status of the recommended upgrade task. The prompt unit is used to prompt the user to confirm the execution of the recommended upgrade task.

9. A server for providing device software version release services, characterized in that, include: The authentication unit is used to receive the second request from the front-end cross-domain component to perform cross-domain authentication, and return a response to the front-end cross-domain component to indicate whether the authentication is successful. The second request is a cross-domain authentication request; The matching query unit is used to receive a third request sent by the front-end cross-domain component based on the recommended upgrade task information, and to query whether there is a recommended upgrade software that matches the recommended upgrade task information; And return matching recommended upgrade software information to the front-end cross-domain component; The upgrade file download unit is used to receive a fourth request from the front-end cross-domain component to request the download of a recommended upgrade file, download the recommended upgrade file and return it to the front-end cross-domain component.

10. A server for providing device software version upgrade services, characterized in that, include: The recommended upgrade task information query unit is used to receive the first request from the front-end cross-domain component and return the recommended upgrade task information to the front-end cross-domain component. The recommended upgrade task information includes the device software version release service address, device software version release service authentication username and password, and a list of devices to be upgraded. The upgrade file receiving unit is used to receive recommended upgrade files uploaded by front-end cross-domain components; The upgrade task status update unit is used to update the status of recommended upgrade tasks; The device upgrade execution unit is used to perform device upgrades based on the recommended upgrade file.

Images