WO2022105631A1 - 配置页面的请求方法、装置及电子设备 - Google Patents

配置页面的请求方法、装置及电子设备 Download PDF

Info

Publication number
WO2022105631A1
WO2022105631A1 PCT/CN2021/129241 CN2021129241W WO2022105631A1 WO 2022105631 A1 WO2022105631 A1 WO 2022105631A1 CN 2021129241 W CN2021129241 W CN 2021129241W WO 2022105631 A1 WO2022105631 A1 WO 2022105631A1
Authority
WO
WIPO (PCT)
Prior art keywords
capability set
configuration page
target device
configuration
request
Prior art date
Application number
PCT/CN2021/129241
Other languages
English (en)
French (fr)
Inventor
徐峰
Original Assignee
杭州海康威视数字技术股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 杭州海康威视数字技术股份有限公司 filed Critical 杭州海康威视数字技术股份有限公司
Priority to MX2023005995A priority Critical patent/MX2023005995A/es
Priority to EP21893778.7A priority patent/EP4250683A1/en
Publication of WO2022105631A1 publication Critical patent/WO2022105631A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/303—Terminal profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5683—Storage of data provided by user terminals, i.e. reverse caching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0253—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using browsers or web-pages for accessing management information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Definitions

  • the present application relates to the field of computer communication, and in particular, to a configuration page request method, apparatus and electronic device.
  • the equipment remote configuration system includes: user terminal, management platform and equipment.
  • the management platform manages at least one device.
  • the user terminal can configure the device through the management platform.
  • the user terminal may provide a configuration page to the user, and the user may complete corresponding configuration operations on the configuration page. It can be seen that the configuration page is indispensable in remote configuration, so in the remote configuration technology, how to quickly obtain the configuration page is an ongoing issue.
  • each time the user terminal requests the configuration page (for example, the user terminal requests the configuration page for the first time, or the user terminal switches back to the configuration page from the sub-configuration page, and the user requests the sub-configuration page associated with the first configuration page) etc.), all need to send a request to the management platform, and after acquiring the requested capability set of the configuration page from the target device, the management platform returns the capability set of the configuration page to the user terminal.
  • the user terminal can only display the configuration page based on the capability set, thereby greatly increasing the acquisition time of the configuration page.
  • each time a user requests a configuration page it takes a long time to see the configuration page, resulting in poor user experience.
  • the present application provides a configuration page request method, apparatus and electronic device, which are used to improve the request efficiency of the configuration page.
  • a method for requesting a configuration page is provided, and the method is applied to a user terminal, including:
  • the corresponding configuration page is displayed by using the acquired capability set.
  • the method further includes:
  • the capability set corresponding to the first configuration page of each accessible device is pulled and cached.
  • the method further includes:
  • the capability set displays the first configuration page, and caches the capability set corresponding to the first configuration page of the target device;
  • the method further includes:
  • a capability set corresponding to the sub-configuration page is requested from the target device and cached, and the sub-configuration page is displayed according to the capability set of the sub-configuration page.
  • the method further includes:
  • the cached capability set of the configuration page is updated according to the capability set returned by the target device.
  • the capability set corresponding to the first configuration page of each accessible device is pulled, including:
  • the preset duration is extended, and the capability set request marked as a failed request is sent to the accessible device again,
  • M and N are integers greater than 0, and M is greater than or equal to N.
  • the method further includes:
  • an apparatus for requesting a configuration page is provided, and the apparatus is applied to a user terminal, including:
  • an obtaining unit configured to obtain the configuration page corresponding to the target device from the cached capability set of at least one accessible device accessible to the user terminal in the case of detecting a page display event for the configuration page of the target device capability set;
  • the display unit is configured to display the corresponding configuration page by using the acquired capability set if the capability set corresponding to the configuration page of the target device is acquired.
  • an electronic device comprising a machine-readable storage medium and a processor
  • machine-readable storage medium is used to store machine-executable instructions
  • the processor is configured to read the machine-executable instructions on the machine-readable storage medium, and execute the instructions to implement a page configuration request method.
  • a machine-readable storage medium wherein machine-executable instructions are stored in the machine-readable storage medium, and when the machine-executable instructions are executed by a processor, the above-mentioned page configuration request method is implemented.
  • a computer program is provided, the computer program is stored in a computer-readable storage medium, and when a processor executes the computer program, the processor is caused to implement the above-mentioned page configuration request method.
  • the user terminal detects the page display event of the configuration page of the target device, if the capability set of the configuration page is cached locally, the corresponding configuration page can be displayed based on the locally cached capability set without obtaining the target device from the management platform. capability set, so the request efficiency of the configuration page of the target device is improved.
  • the method of the present application can greatly reduce the display delay of the configuration page and greatly improve the user experience.
  • FIG. 1 is a schematic diagram of a configuration page shown in an exemplary embodiment of the present application
  • FIG. 2 is a networking architecture diagram of a device remote configuration system shown in an exemplary embodiment of the present application
  • FIG. 3 is a flowchart of a method for requesting a configuration page according to an exemplary embodiment of the present application
  • FIG. 4 is a flowchart of a capability set caching method for a first configuration page shown in an exemplary embodiment of the present application
  • FIG. 5 is a schematic diagram of a capability set configuration file of a first configuration page shown in an exemplary embodiment of the present application
  • FIG. 6 is a schematic diagram of a capability set for pulling a first configuration page according to an exemplary embodiment of the present application
  • FIG. 7 is a flowchart of a method for requesting a first configuration page according to an exemplary embodiment of the present application
  • FIG. 8 is a flowchart of a method for requesting a sub-configuration page according to an exemplary embodiment of the present application
  • FIG. 9 is a schematic diagram illustrating a corresponding relationship between a specified configuration parameter and a capability set request according to an exemplary embodiment of the present application.
  • FIG. 10 is a flowchart of a method for requesting a first configuration page according to an exemplary embodiment of the present application
  • FIG. 11 is a flowchart of a method for requesting a sub-configuration page according to an exemplary embodiment of the present application
  • FIG. 12 is a hardware structure diagram of a user terminal shown in an exemplary embodiment of the present application.
  • Fig. 13 is a block diagram of an apparatus for requesting a configuration page according to an exemplary embodiment of the present application.
  • first, second, third, etc. may be used in this application to describe various information, such information should not be limited by these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information without departing from the scope of the present application.
  • word "if” as used herein can be interpreted as "at the time of” or "when” or "in response to determining.”
  • a capability set is a collection of data related to a certain function of a device.
  • the device function is a face detection function
  • the capability set refers to a collection of data related to the face detection function.
  • the functions of the device are displayed on the configuration page of the device, so the display of the configuration page of the device is related to the capability set of the device.
  • the capability set of the device determines which functions (such as picture functions, storage functions, etc.) are included in the directory bar displayed on the left side of Figure 1.
  • the capability set of the device also determines the configuration on the right side of Figure 1.
  • the entry column specifically displays which entries, etc.
  • configuration page of the device usually includes static resources and dynamic data. Static resources are generally stored on the user terminal.
  • the static resources may include: style files, html files, and script files.
  • style file and the html file determine the style of the configuration page
  • script file determines some operations of the configuration page.
  • Dynamic data may include: a capability set associated with the configuration page. This dynamic data is typically stored on the device to be configured.
  • the user terminal When the user terminal needs to display the configuration page, it can obtain the capability set corresponding to the configuration page from the device to be configured, and display the configuration page based on the obtained capability set and local static resources.
  • the specific process of displaying the first configuration page or the sub-configuration page includes: the user terminal is based on the static resources of the locally cached first configuration page or the sub-configuration page, And the acquired capability set of the first configuration page or sub-configuration page, displaying the first configuration page or sub-configuration page.
  • the first configuration page refers to the configuration page requested by the user terminal for the first time, which can also be understood as the initial configuration page.
  • FIG. 2 is a network architecture diagram of a device remote configuration system shown in an exemplary embodiment of the present application.
  • the equipment remote configuration system includes: user terminal, management platform and equipment.
  • the user terminal may be any one of various terminal devices including smart phones, PCs, servers, and the like.
  • the management platform may be, for example, a cloud platform or the like.
  • the management platform manages at least one device (for example, the device may include an IPC device and an NVR device, and the device is only exemplarily described here, and is not specifically limited).
  • the user terminal can configure the device through the management platform.
  • the user terminal maintains the static resources (such as style files, html files, script files) of the configuration pages (including the first configuration page and sub-configuration pages) of each device.
  • the user terminal can obtain the capability set of the configuration page of the target device from the management platform, and then the user terminal can display the configuration page of the target device based on the capability set of the configuration page and the static resources of the configuration page of the target device .
  • the user terminal can send the configuration information input by the user through the configuration page to the management platform, and the management platform can deliver the configuration information to the target device, thereby completing the configuration of the target device.
  • the user terminal when the user terminal detects a page display event for the configuration page of the target device, it obtains the capability set of the configuration page from the management platform, and the user terminal displays the configuration page based on the capability set. . Since the user terminal needs to acquire the capability set of the configuration page from the management platform every time it detects a page display event for the configuration page, the acquisition time of the configuration page is greatly increased. In addition, from the user's point of view, after triggering a request for the configuration page, the user has to wait for a long time to see the configuration page, which makes the user experience poor.
  • the present application proposes a configuration page request method, in which a user terminal actively pulls (GET) the capability set of the first configuration page of all accessible devices accessible to the user terminal and caches it.
  • GET the capability set of the first configuration page of all accessible devices accessible to the user terminal and caches it.
  • the operation of "pulling” can be understood as: sending a request, obtaining data and then caching the data.
  • the configuration page is displayed based on the capability set of the configuration page of the target device.
  • the user terminal detects the page display event of the configuration page of the target device, if the capability set of the configuration page is cached locally, the corresponding configuration page can be displayed based on the locally cached capability set without obtaining the configuration from the management platform.
  • the capability set of the page so the request efficiency of the configuration page of the target device is improved.
  • the method of the present application can greatly reduce the display delay of the configuration page and greatly improve the user experience.
  • FIG. 3 is a flowchart of a method for requesting a configuration page according to an exemplary embodiment of the present application. The method may be applied to a user terminal and may include the following steps.
  • Step 301 In the case of detecting a page display event for the configuration page of the target device, the user terminal obtains the configuration page corresponding to the target device from the cached capability set of at least one accessible device that can be accessed by the user terminal. capability set;
  • Step 302 If the capability set corresponding to the configuration page of the target device is acquired, the user terminal displays the corresponding configuration page by using the acquired capability set.
  • the above configuration page may be the first configuration page of the target device, or may be a sub-configuration page associated with the first configuration page of the target device. It is only exemplified here, and is not specifically limited.
  • the configuration page request method provided by the present application is exemplarily described below from the above configuration page as the first configuration page and the above configuration page as a sub-configuration page.
  • the configuration page is the first configuration page
  • FIG. 4 is a flowchart of a capability set caching method for a first configuration page shown in an exemplary embodiment of the present application. The method may be applied to a user terminal and may include the following steps.
  • Step 401 The user terminal obtains the device information of the accessible devices accessible by the user terminal from the management platform.
  • the user terminal may send an acquisition request for acquiring the device information of the accessible device to the management platform (eg, the management device), where the acquisition request carries the identifier of the user terminal.
  • the management device may determine accessible devices accessible to the user terminal from among all devices managed by the management device, and send device information of the determined accessible devices to the user terminal.
  • the device information of the accessible device may include: device identification.
  • the device information of the accessible device may also include other information, such as device working state information, etc., which are only illustratively described here, and are not specifically limited.
  • the user terminal may notify a local service (eg, a web control) of the received device information of the accessible device, and then the local service pulls the capability set corresponding to the first configuration page of each accessible device.
  • a local service eg, a web control
  • Step 402 According to the device information of the accessible device, the user terminal pulls the capability set corresponding to the first configuration page of each accessible device and caches it.
  • the user terminal may add the device identifier of the accessible device to the pull queue, and sequentially pull the capability set of the first configuration page of the device in the queue according to the queue sequence.
  • the pulled capability set is cached locally.
  • the user terminal may pull the capability sets of the first configuration pages of multiple accessible devices in parallel, and the pulling processes of the capability sets of the first configuration pages of each accessible device are independent of each other.
  • the capability set configuration file (ie cache.json) of the first configuration page of the accessible device is configured on the user terminal.
  • the capability set configuration file includes a capability set request for at least one capability set of the device. It should be noted that the capability set configuration files of the first configuration page of different types of devices are different, and the first configuration page of the same type of device can reuse one capability set configuration file, for example, all front-end devices reuse one capability set configuration file, all Back-end devices reuse a capability set configuration file.
  • FIG. 5 is a schematic diagram of a capability set configuration file of a first configuration page shown in an exemplary embodiment of the present application.
  • the content in the box is a capability set request.
  • the user terminal may execute the capability set configuration file, and sequentially send M capability set requests in the capability set configuration file.
  • M is an integer greater than 0.
  • the user terminal may also send N capability set requests in parallel each time.
  • N is an integer greater than 0.
  • M may be greater than N, and M may also be equal to N, which is not specifically limited here.
  • the user terminal may send N capability set requests to the accessible device in parallel, so that the accessible device may receive and process the N capability set requests in parallel.
  • the user terminal For each capability set request, if the capability set requested for the capability set request is received within a preset time period and there is a capability set request to be sent, the user terminal obtains the next or more capability set requests from the M capability set requests. send a capability set request to be sent. If the capability set requested for the capability set request is received within the preset time period and there is no capability set request to be sent, it is determined that the sending of the M capability set requests is completed. If the capability set requested by the capability set request is not received within the preset time period, the capability set request is marked as a failed request.
  • the preset duration is extended, and the capability set request marked as a failed request is sent to the accessible device.
  • a request queue pool with a capacity of N requests can be set.
  • N capability set requests may be added to the request queue pool.
  • the user terminal may send the capability set request in the request queue pool to the accessible device.
  • the capability set request For each capability set request in the request queue pool, if the user terminal receives the capability set requested by the capability set request within the preset time period, the capability set request will be deleted from the request queue pool, and the next capability set request will be deleted. The capability set request to be sent is added to the request queue pool.
  • the capability set request will be deleted from the request queue pool, and the capability set request will be marked as a failed request.
  • the preset duration is extended, and the capability set request marked as a failed request is sent to the accessible device.
  • the user terminal may add capability set request 1, capability set request 2, capability set request 3, and capability set request 4 to the request queue pool.
  • the user terminal may send the four capability set requests in the request queue pool in parallel.
  • the user terminal first receives the capability sets corresponding to capability set request 1 and capability set request 3 within the preset time period, and then deletes capability set request 1 and capability set request 3 from the request queue pool, and removes capability set request 1 and capability set request 3 from the request queue pool.
  • Request 5 and Capability Set Request 6 are added to the request queue pool.
  • the user terminal sends capability set request 5 and capability set request 6 in the request queue pool.
  • the user terminal may mark capability set request 2 and capability set request 4 as failed requests, and mark capability set request 2 and capability set request 4 as failed requests. Removed from the request queue pool and added capability set requests 7 and 8 to the request queue pool.
  • a user terminal when a user terminal sends a capability set request to an accessible device, the user can directly send a capability set request to an accessible device directly connected to the user terminal, and receive a capability set directly returned by the accessible device.
  • the user terminal can also send a capability set request to the accessible device through the management platform to implement "send a capability set request to the accessible device".
  • the user terminal sends a capability set request to the management platform, and the management platform may forward the capability set request to the device after receiving the capability set request sent by the user terminal.
  • the device returns the requested capability set to the management platform, and the management platform forwards the capability set returned by the device to the user terminal.
  • sending the capability set request by the user terminal to the management platform or the accessible device may be implemented in the following manner: after the user performs a triggering operation on the configuration page through the browser window on the user terminal, the browser sends the local service (for example, a Web control) sends a capability set request for the configuration page, and if the local service determines that the user terminal does not cache the capability set for the configuration page locally, the local service sends the request to the accessible device, or the local service The request is sent to the management platform, which forwards the request to the accessible device.
  • the local service For example, a Web control
  • the user terminal sends a capability set request to the accessible device, and receives the capability set returned by the accessible device. After receiving the capability set, the user terminal can rewrite the capability set request to obtain the file name where the user stores the capability set.
  • the user terminal can convert the backslash in the capability set request into a symbol (such as underscore) supported by the file name, and then add the data format at the end of the capability set request to form the file name.
  • a symbol such as underscore
  • the file name obtained by rewriting the capability set request is: ISAPI_Security_capabilities.xml.
  • xml is the data format.
  • the file name obtained by rewriting the capability set request is: ISAPI_Security_capabilities.json.
  • json is the data format.
  • FIG. 7 is a flowchart of a method for requesting a first configuration page according to an exemplary embodiment of the present application.
  • the method may be applied to a user terminal and may include the following steps.
  • Step 701 In the case where the user terminal detects a page display event for the first configuration page of the target device, obtains the first configuration of the target device from the cached capability set of at least one accessible device that can be accessed by the user terminal The capability set corresponding to the page.
  • the user terminal when the user terminal acquires the device information that is accessible to the user terminal sent by the management platform, the user terminal can display the identifiers of the accessible devices to the user.
  • the user will select the target device to be accessed this time according to the identifiers of each accessible device displayed by the user terminal. After the user selects the target device, the display of the first configuration page of the target device will be triggered.
  • the display of the first configuration page of the target device is also triggered.
  • the user terminal When the user terminal detects the page display event of the first configuration page of the target device, it can detect the cached capability concentration of at least one accessible device that can be accessed by the user terminal, and whether there is a capability corresponding to the first configuration page of the target device. set.
  • the user terminal when detecting the cached capability set of at least one accessible device accessible to the user terminal and whether there is a capability set corresponding to the first configuration page of the target device, the user terminal can detect the locally cached capability set of the accessible device Whether there is a capability set folder corresponding to the target device in the file.
  • the capability set folder corresponding to the target device is cached locally, it is further searched in the capability set folder whether there is a capability set corresponding to the first configuration page of the target device cached; if so, it is determined that the first configuration is cached locally. The capability set corresponding to the page, if not, it is determined that the capability set corresponding to the first configuration page is not cached locally.
  • the capability set folder corresponding to the target device is not cached locally, it is determined that the capability set corresponding to the first configuration page is not cached locally.
  • Step 702 If the capability set corresponding to the first configuration page of the target device is obtained, the user terminal uses the obtained capability set to display the corresponding first configuration page.
  • the capability set corresponding to the first configuration page of the target device can be obtained from the capability set of at least one accessible device locally cached, and the user terminal Then use the acquired capability set to display the corresponding first configuration page.
  • the user terminal may display the corresponding first configuration page based on the locally stored static resources of the first configuration page of the target device and the acquired capability set corresponding to the first configuration page of the target device.
  • the user terminal when the user terminal has not obtained the capability set corresponding to the first configuration page of the target device in the cached capability set of at least one accessible device that can be accessed by the user terminal, if the If the capability set corresponding to the first configuration page of the target device is in the process of being pulled, after the capability set corresponding to the first configuration page of the target device is successfully pulled, the first configuration page of the target device is displayed according to the capability set corresponding to the first configuration page of the target device. configuration page, and cache the capability set corresponding to the first configuration page of the target device; otherwise, send a request to the target device to obtain the first configuration page capability set of the target device and cache it, and display the corresponding capability set according to the obtained capability set the first configuration page.
  • the user terminal may detect whether the capability set of the first configuration page of the target device is in the process of pulling.
  • the user terminal may configure a pulling flag for the device that is pulling the capability set of the first configuration page.
  • the user terminal can detect whether the target device in the pull queue is configured with a pulling flag, and if so, determine the first configuration of the target device. The configuration page capability set is being pulled. If the target device does not have the pulling mark, it is determined that the first configuration page capability set of the target device is not being pulled.
  • the capability set corresponding to the first configuration page of the target device is in the process of being pulled, after the capability set corresponding to the first configuration page of the target device is successfully pulled, the capability set corresponding to the first configuration page of the target device is displayed.
  • the first configuration page is described, and the capability set corresponding to the first configuration page of the target device is cached.
  • the user terminal can wait. Then, the user terminal can monitor the pull mark of the target device in real time, and if the pull mark of the target device changes from being pulled to being pulled, it is determined that the pull of the capability set of the first configuration page of the target device is complete. Then, the user terminal may display the target configuration page based on the capability set of the first configuration page, and cache the capability set corresponding to the first configuration page of the target device.
  • the user terminal sends a request to the target device to obtain the capability set of the first configuration page of the target device and caches it. Display the corresponding first configuration page.
  • the user terminal when the user terminal sends the request to the target device, the user terminal may directly send the request to the target device.
  • the user terminal may also send the request to the management platform, so that the management platform forwards the request to the target device, so as to implement "sending a request to the target device". It is only exemplified here, and is not specifically limited.
  • the user terminal may further mark the target device as a pulled device.
  • the user terminal may delete the target device identifier from the above-mentioned pull queue, and so on. This is just an exemplary description of the marking manner, and it is not specifically limited.
  • FIG. 8 is a flowchart of a method for requesting a sub-configuration page according to an exemplary embodiment of the present application.
  • the method may be applied to a user terminal and may include the following steps.
  • Step 801 In the case where the user terminal detects a page presentation event for the sub-configuration page of the target device, obtains the sub-configuration of the target device from the cached capability set of at least one accessible device that can be accessed by the user terminal The capability set corresponding to the page;
  • Step 802 If the capability set corresponding to the sub-configuration page of the target device is acquired, the user terminal uses the acquired capability set to display the corresponding sub-configuration page;
  • Step 803 If the capability set corresponding to the sub-configuration page of the target device is not obtained, request the target device for the capability set corresponding to the sub-configuration page and cache it.
  • the user terminal may directly send the request to the target device to obtain the capability set directly returned by the target device.
  • the user terminal can also send the request to the management platform, so that the management platform can send the request to the target device to obtain the capability set corresponding to the sub-configuration page, so as to realize "request the capability set corresponding to the sub-configuration page to the target device" ". It is not specifically limited here.
  • the capability set of the configuration page (including the first configuration page or sub-configuration page) maintained on the target device is not static.
  • the capability set of the configuration page is consistent, and the present application also adopts the following method to update the capability set cached on the user terminal.
  • configuration parameters on some first configuration pages or sub-configuration pages are associated with capability sets (for convenience of description here, these configuration parameters are referred to as specified configuration parameters).
  • the specified configuration parameter can be a capability set enable configuration parameter.
  • the device When the capability set enable configuration parameter indicates that the capability set is enabled, the device will enable the capability set, and when the capability set enable configuration parameter indicates that the capability set cannot be enabled, The device turns off the capability set.
  • the user terminal After the administrator modifies the specified configuration parameters on the first configuration page or sub-configuration page of the target device, the user terminal will send the modification instruction of the specified configuration parameters to the target device through the management platform, and the target device will modify the device based on the instruction. If the specified configuration parameter is modified, the current maintenance capability set of the target device will change.
  • the first situation is: other users modify the specified configuration parameters on the first configuration page or sub-configuration page of the target device through other user terminals, resulting in a change in the currently maintained capability set of the target device.
  • the second situation is that the user modifies the specified configuration parameters of the first configuration page or sub-configuration page of the target device by using the user terminal, which causes the current maintenance capability set of the target device to change.
  • the first situation other users modify the specified configuration parameters of the first configuration page or sub-configuration page of the target device through other user terminals, which causes the current maintenance capability set of the target device to change.
  • the user terminal since the modification of the specified configuration parameters occurs on other user terminals, the user terminal cannot know which specified parameters on the target device have been modified and which capability sets on the target device have changed. Therefore, in order to ensure that in this case, the capability set of the first configuration page or sub-configuration page of the target device cached by the user terminal is consistent with the capability set corresponding to the first configuration page or sub-configuration page maintained on the target device.
  • the user terminal needs to obtain the capability set of the first configuration page or sub-configuration page currently maintained by the target device after displaying the corresponding first configuration page or sub-configuration page based on the capability set of the cached first configuration page or sub-configuration page, so as to Based on the capability set of the first configuration page or the sub-configuration page currently maintained by the target device, the capability set of the locally cached first configuration page or the sub-configuration page is updated to keep the two capability sets consistent.
  • the user terminal when the user terminal detects a page display event for the first configuration page or sub-configuration page of the target device, if the cached capability set includes the capability set of the first configuration page or sub-configuration page of the target device, After displaying the first configuration page or the sub-configuration page according to the capability set of the cached first configuration page or the sub-configuration page, the user terminal also needs to request the target device for the capability corresponding to the first configuration page or the sub-configuration page of the target device. set.
  • the target device may return the capability set of the first configuration page or sub-configuration page currently maintained locally to the user terminal.
  • the user terminal can use the returned capability set of the first configuration page or sub-configuration page currently maintained by the target device to update the locally cached capability set of the first configuration page or sub-configuration page of the target device, so that the locally cached first configuration page of the target device is configured first.
  • the capability set of the page or sub-configuration page is consistent with the capability set of the first configuration page or sub-configuration page currently maintained by the target device.
  • the user modifies the specified configuration parameters of the first configuration page or sub-configuration page of the target device by using the user terminal, which causes the current maintenance capability set of the target device to change.
  • the user terminal since the modification of the specified configuration parameters occurs on the user terminal, the user terminal can learn which specified configuration parameters have been modified. Therefore, the user terminal can adopt an active update method, so that the user terminal The capability set corresponding to the first configuration page or sub-configuration page cached on the target device is consistent with the capability set corresponding to the main configuration page or sub-configuration page maintained on the target device.
  • the corresponding relationship between the specified configuration parameter and at least one capability set is also configured on the user terminal.
  • the corresponding relationship indicates that the change of the configuration parameter will cause the change of the capability set maintained on the device.
  • the dotted box represents a configuration parameter
  • the content enclosed by the solid line represents the capability set request associated with the configuration parameter.
  • the user terminal detects a modification event for the configuration parameters on the first configuration page or the sub-configuration page, the preset configuration In the corresponding relationship between the parameter and the capability set request (ie, refresh.json), the capability set request corresponding to the modified configuration parameter is searched, and the capability set request is sent to the target device.
  • the preset configuration In the corresponding relationship between the parameter and the capability set request (ie, refresh.json)
  • the capability set request corresponding to the modified configuration parameter is searched, and the capability set request is sent to the target device.
  • the target device may return the capability set requested by the capability set request to the user terminal.
  • the user terminal may update the locally cached capability set corresponding to the specified configuration parameter based on the capability set returned by the management platform.
  • the user terminal when the user terminal sends the capability set request to the target device, the user terminal may directly send the capability set request to the target device, and receive the capability set directly returned by the target device.
  • the user terminal can also send the capability set request to the target device through the management platform, and receive the capability set forwarded by the management platform, so as to realize "send the found capability set request to the target device, and receive the returned capability set request from the target device. Request the requested capability set for the found capability set”.
  • the user terminal sends the capability set request to the management platform, and after receiving the capability set request sent by the user terminal, the management platform may forward the capability set request to the target device.
  • the device returns the requested capability set to the management platform, and the management platform forwards the capability set returned by the target device to the user terminal.
  • the user terminal since the user terminal actively pulls and caches the capability sets of the first configuration pages of all accessible devices of the user terminal after logging in to the management platform, so when a target device is detected
  • the page of the first configuration page displays the event
  • the capability set of the first configuration page can be obtained from the local cache, and there is no need to request the management platform to obtain the target capability set.
  • the request efficiency of the target configuration page is improved.
  • the method of the present application can greatly reduce the display delay of the first configuration page and greatly improve the user experience.
  • the sub-configuration page can be directly based on the capability set of the sub-configuration page in the cache. It is not necessary to download the capability set of the sub-configuration page, which improves the request efficiency of the capability set of the sub-configuration page.
  • the device capability set can be updated by the administrator, so this application also designs an update method for the locally cached capability set corresponding to the above two situations, so that the locally cached capability set and the capability set maintained by the device can be updated. Consistent.
  • FIG. 10 is a flowchart of a method for requesting a first configuration page according to an exemplary embodiment of the present application.
  • the method may be applied to a user terminal and may include the following steps.
  • Step 1001 The user terminal obtains device information of at least one accessible device accessible by the user terminal from the management platform.
  • Step 1002 The user terminal sequentially pulls and caches the capability set of the first configuration page of each accessible device according to the device information of at least one accessible device.
  • the user terminal may pull and cache the capability sets of the first configuration pages of multiple accessible devices in parallel.
  • Step 1003 When detecting a page display event for the first configuration page of the target device, the user terminal detects whether the capability set of the first configuration page of the target device is included in the locally cached capability set.
  • steps 1006-1008 are executed.
  • step 1002 and step 1003 are independent of each other and do not affect each other. In other words, when one of the user terminals executes step 1003, the pulling process of step 1002 may still be executed.
  • Step 1004 If the locally cached capability set includes the capability set of the first configuration page of the target device, display the first configuration page based on the capability set of the first configuration page of the target device.
  • Step 1005 The user terminal obtains the capability set of the first configuration page of the target device from the management platform, and uses the obtained capability set of the first configuration page of the target device to update the locally cached capability set of the first configuration page of the target device.
  • Step 1006 If the locally cached capability set does not include the capability set of the first configuration page of the target device, the user terminal can detect whether the capability set of the first configuration page of the target device is in the process of pulling.
  • step 1007 is executed.
  • step 1008 is executed.
  • Step 1007 If the capability set of the first configuration page of the target device is not in the pulling process, request the management platform for the capability set of the first configuration page of the target device and cache it, and display it based on the capability set of the first configuration page of the target device The first configuration page.
  • Step 1008 If the capability set of the first configuration page of the target device is in the pulling process, the user terminal waits until the capability set of the first configuration page is pulled, and displays the first configuration page of the target device based on the capability set of the first configuration page.
  • the user terminal when detecting a modification event for a specified configuration parameter on the first configuration page of the target device, the user terminal searches for the specified configuration parameter in the preset corresponding relationship between the specified configuration parameter and the capability set request. The capability set request corresponding to the modified specified configuration parameter. Then, the user terminal may send the found capability set request to the management platform, receive the capability set requested for the found capability set request returned by the management platform, and update the local cache based on the returned capability set The capability set corresponding to the modified specified configuration parameter.
  • FIG. 11 is a flowchart of a method for requesting a sub-configuration page according to an exemplary embodiment of the present application.
  • the method may be applied to a user terminal and may include the following steps.
  • Step 1101 In the case of detecting a page presentation event for a sub-configuration page associated with the first configuration page, the user terminal detects whether a capability set corresponding to the sub-configuration page is included in a locally cached capability set.
  • the capability set of the local cache includes the capability set corresponding to the sub-configuration page, perform steps 1102 to 1103;
  • step 1104 is executed.
  • Step 1102 If the locally cached capability set includes the capability set corresponding to the sub-configuration page, display the sub-configuration page based on the locally cached capability set of the sub-configuration page.
  • Step 1103 The user terminal requests the management platform for the capability set of the sub-configuration page, and updates the locally cached capability set corresponding to the sub-configuration page based on the requested capability set of the sub-configuration page.
  • Step 1104 If the locally cached capability set does not contain the capability set of the sub-configuration page, request the management platform for the capability set corresponding to the sub-configuration page.
  • the user terminal when detecting a modification event for a specified configuration parameter on the sub-configuration page of the target device, the user terminal searches for the specified configuration parameter in the preset corresponding relationship between the specified configuration parameter and the capability set request. The capability set request corresponding to the modified specified configuration parameter. Then, the user terminal may send the found capability set request to the management platform, receive the capability set requested for the found capability set request returned by the management platform, and update the local cache based on the returned capability set The capability set corresponding to the modified specified configuration parameter.
  • the present application also provides an electronic device, the electronic device may include: a machine-readable storage medium and a processor;
  • machine-readable storage medium is used to store machine-executable instructions
  • the processor is configured to read the machine-executable instructions on the machine-readable storage medium, and execute the instructions to implement the steps of the configuration page request method.
  • the electronic device may further include a communication interface 1201 and a bus 1204 ; wherein the communication interface 1201 , the processor 1202 and the machine-readable storage medium 1204 The storage media 1203 communicate with each other through the bus 1204 .
  • the processor 1202 can perform the configuration page request method described above by reading and executing the machine-executable instructions in the machine-readable storage medium 1203 .
  • FIG. 12 does not constitute a limitation on the electronic device, and may include more or less components than the one shown, or combine some components, or adopt different component arrangements.
  • FIG. 13 is a block diagram of a device for requesting a configuration page according to an exemplary embodiment of the present application.
  • the device can be applied to a user terminal, and generally includes the following units.
  • the obtaining unit 1301 is configured to obtain the configuration page of the target device from the cached capability set of at least one accessible device accessible to the user terminal in the case of detecting a page display event for the configuration page of the target device the corresponding capability set;
  • the displaying unit 1302 is configured to display the corresponding configuration page by using the acquired capability set if the capability set corresponding to the configuration page of the target device is acquired.
  • the device further includes:
  • the pulling unit 1303 is configured to obtain the target from the cached capability set of at least one accessible device accessible by the user terminal in the case of detecting a page presentation event for the target device configuration page Before the capability set corresponding to the configuration page of the device, the device information of the accessible device is obtained from the management platform; according to the device information of the accessible device, the capability set corresponding to the first configuration page of each accessible device is pulled and cached.
  • the display unit 1302 is further configured to, if the configuration page is the first configuration page, if the capability set corresponding to the configuration page of the target device is not obtained, if the first configuration page of the target device is The capability set corresponding to the page is in the process of being pulled, after the capability set corresponding to the first configuration page of the target device is successfully pulled, the first configuration page is displayed according to the capability set corresponding to the first configuration page of the target device and cached. the capability set corresponding to the first configuration page of the target device; otherwise, send a request to the target device to obtain the capability set corresponding to the first configuration page of the target device and cache it, and display the corresponding first configuration page according to the obtained capability set .
  • the display unit 1302 is further configured to, if the configuration page is a sub-configuration page associated with the first configuration page, in the case where the capability set corresponding to the configuration page of the target device is not obtained, to The target device requests and caches the capability set corresponding to the sub-configuration page, and displays the sub-configuration page according to the capability set of the sub-configuration page.
  • the device further includes:
  • the updating unit 1304 is used for the capability set corresponding to the configuration page exists in the cached capability set, then after displaying the capability set of the configuration page, request the target device for the capability set corresponding to the configuration page; The capability set returned by the target device updates the cached capability set of the configuration page;
  • the pulling unit 1303 when pulling the capability set corresponding to the first configuration page of each accessible device, is configured to, for each accessible device, determine the capability for requesting the first configuration page of the accessible device.
  • the M capability set requests in the set are sent to the accessible device in parallel with N capability set requests.
  • For each capability set request that has been sent if the capability set requested by the capability set request is not received within the preset time period, then Mark the capability set request as a failed request; after sending M capability set requests, expand the preset duration, and send the capability set request marked as a failed request to the accessible device again, where M and N are Integer greater than 0, M is greater than or equal to N.
  • FIG. 13 does not constitute a limitation on the means for requesting the configuration page, and may include more or less units than those shown.
  • the present application also provides a machine-readable storage medium, where machine-executable instructions are stored in the machine-readable storage medium, and when the machine-executable instructions are executed by a processor, the above method for requesting a configuration page is implemented.
  • a machine-readable storage medium referred to herein can be any electronic, magnetic, optical, or other physical storage device that can contain or store information, such as executable instructions, data, and the like.
  • the machine-readable storage medium may be: volatile memory, non-volatile memory, or similar storage medium.
  • the machine-readable storage medium may be a RAM (Radom Access Memory, random access memory), a flash memory, a storage drive (such as a hard disk drive), a solid state drive, any type of storage disk (such as an optical disc, DVD, etc.), or the like storage media, or a combination thereof.
  • the present application also provides a computer program, the computer program is stored in a computer-readable storage medium, and when a processor executes the computer program, the processor is prompted to implement the above method for requesting a configuration page.

Abstract

本申请提供一种配置页面的请求方法、装置及电子设备，包括：在检测到针对目标设备配置页面的页面展示事件的情况下，从已缓存的所述用户终端可访问的至少一个可访问设备的能力集中，获取所述目标设备的配置页面对应的能力集；若获取到所述目标设备的配置页面对应的能力集，则利用获取到的该能力集展示对应的配置页面。

Description

配置页面的请求方法、装置及电子设备
相关申请的交叉引用
本专利申请要求于2020年11月20日提交的、申请号为202011311721.6、发明名称为“一种配置页面的请求方法、装置及电子设备”的中国专利申请的优先权，该申请的全文以引用的方式并入本文中。
技术领域
本申请涉及计算机通信领域，尤其涉及一种配置页面的请求方法、装置及电子设备。
背景技术
设备远程配置系统包括：用户终端、管理平台和设备。
管理平台管理了至少一个设备。用户终端可通过管理平台对设备进行配置。
在配置时，用户终端可向用户提供配置页面，用户可在配置页面上完成相应的配置操作。由此可见，配置页面在远程配置中是不可或缺的，所以在远程配置技术中，如何快速获取配置页面是持续探讨的问题。
然而，在现有的获取配置页面的方式中，用户终端每请求一次配置页面(比如用户终端首次请求配置页面，或者用户终端由子配置页面切换回首配置页面，用户请求首配置页面关联的子配置页面等)，都需要向管理平台发送请求，管理平台在从目标设备获取到所请求的配置页面的能力集后，向用户终端返回该配置页面的能力集。用户终端基于该能力集才能显示配置页面，从而大大增加了配置页面的获取时间。此外，从用户角度来说，用户每请求一次配置页面后，要等待很长时间才能看到配置页面，使得用户体验较差。
发明内容
有鉴于此，本申请提供一种配置页面的请求方法、装置及电子设备，用于提高配置页面的请求效率。
具体地，本申请是通过如下技术方案实现的：
根据本申请的第一方面，提供一种配置页面的请求方法，所述方法应用于用户终端，包括：
在检测到针对目标设备配置页面的页面展示事件的情况下，从已缓存的所述用户终端可访问的至少一个可访问设备的能力集中，获取所述目标设备的配置页面对应的能力集；
若获取到所述目标设备的配置页面对应的能力集，则利用获取到的该能力集展示对应的配置页面。
可选的，在所述在检测到针对目标设备配置页面的页面展示事件的情况下，从已缓存的所述用户终端可访问的至少一个可访问设备的能力集中，获取所述目标设备的配置 页面对应的能力集之前，所述方法还包括：
从管理平台获得所述可访问设备的设备信息；
依据所述可访问设备的设备信息，拉取各可访问设备的首配置页面对应的能力集并缓存。
可选的，若所述配置页面为首配置页面，则在未获取到所述目标设备的配置页面对应的能力集的情况下，所述方法还包括：
若所述目标设备的首配置页面对应的能力集正在拉取过程中，则在所述目标设备的首配置页面对应的能力集被拉取成功后，依据所述目标设备的首配置页面对应的能力集展示所述首配置页面，并缓存所述目标设备的首配置页面对应的能力集；
否则，向所述目标设备发送请求以获得所述目标设备的首配置页面对应的能力集并缓存，依据已获得的能力集展示对应的首配置页面。
可选的，若所述配置页面为与目标设备的首配置页面关联的子配置页面，则在未获取到所述目标设备的配置页面对应的能力集的情况下，所述方法还包括：
向所述目标设备请求所述子配置页面对应的能力集并缓存，并依据所述子配置页面的能力集展示所述子配置页面。
可选的，若已缓存的能力集中存在所述配置页面对应的能力集，则在展示所述配置页面的能力集后，所述方法还包括：
向所述目标设备请求所述配置页面对应的能力集；
依据所述目标设备返回的能力集更新已缓存的所述配置页面的能力集。
可选的，所述拉取各可访问设备的首配置页面对应的能力集，包括：
针对每一可访问设备，确定用于请求该可访问设备首配置页面的能力集的M个能力集请求
向该可访问设备并行发送N个能力集请求，针对已发送的每一个能力集请求，若在预设时长内未接收到该能力集请求所请求的能力集，则将该能力集请求标记为失败请求；
在发送完M个能力集请求后，扩大该预设时长，并向该可访问设备再次发送该标记为失败请求的能力集请求，
其中，M、N为大于0的整数，M大于等于N。
可选的，所述方法还包括：
在检测到针对所述配置页面上的指定配置参数的修改事件时，在预设的指定配置参数与能力集请求的对应关系中，查找该被修改的指定配置参数对应的能力集请求；
向所述目标设备发送查找到的能力集请求，并接收所述目标设备返回的针对该查找到的能力集请求所请求的能力集；
基于返回的能力集，更新本地缓存的与修改的指定配置参数对应的能力集。
根据本申请的第二方面，提供一种配置页面的请求装置，所述装置应用于用户终端，包括：
获取单元，用于在检测到针对目标设备配置页面的页面展示事件的情况下，从已缓存的所述用户终端可访问的至少一个可访问设备的能力集中，获取所述目标设备的配置页面对应的能力集；
展示单元，用于若获取到所述目标设备的配置页面对应的能力集，则利用获取到的该能力集展示对应的配置页面。
根据本申请的第三方面，提供一种电子设备，所述电子设备包括机器可读存储介质和处理器；
其中，所述机器可读存储介质，用于存储机器可执行指令；
所述处理器，用于读取所述机器可读存储介质上的所述机器可执行指令，并执行所述指令以实现页面配置请求方法。
根据本申请的第四方面，提供一种机器可读存储介质，所述机器可读存储介质内存储有机器可执行指令，所述机器可执行指令被处理器执行时实现上述页面配置请求方法。
根据本申请的第五方面，提供一种计算机程序，计算机程序存储于计算机可读存储介质，并且当处理器执行计算机程序时，促使处理器实现上述页面配置请求方法。
由于用户终端在检测到目标设备的配置页面的页面展示事件时，若本地缓存了该配置页面的能力集，则可基于本地缓存的能力集展示对应的配置页面，而无需从管理平台获取该目标能力集，所以提高了目标设备的配置页面的请求效率。此外，对于用户而言，用户在触发配置页面的页面展示后，可以很快看到配置页面，所以采用本申请的方法可以大大降低配置页面的展示时延，大大提高了用户体验。
附图说明
图1是本申请一示例性实施例示出的一种配置页面的示意图；
图2是本申请一示例性实施例示出的一种设备远程配置系统的组网架构图；
图3是本申请一示例性实施例示出的一种配置页面的请求方法的流程图；
图4是本申请一示例性实施例示出的一种首配置页面的能力集缓存方法的流程图；
图5是本申请一示例性实施例示出的一种首配置页面的能力集配置文件的示意图；
图6是本申请一示例性实施例示出的一种拉取首配置页面能力集的示意图；
图7是本申请一示例性实施例示出的一种首配置页面请求方法的流程图；
图8是本申请一示例性实施例示出的一种子配置页面请求方法的流程图；
图9是本申请一示例性实施例示出的一种指定配置参数和能力集请求对应关系的示意图；
图10是本申请一示例性实施例示出的一种首配置页面的请求方法流程图；
图11是本申请一示例性实施例示出的一种子配置页面的请求方法流程图；
图12是本申请一示例性实施例示出的一种用户终端的硬件结构图；
图13是本申请一示例性实施例示出的一种配置页面的请求装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
在本申请使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。在本申请和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本申请可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本申请范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
在介绍本申请提供的方法之前，先对本申请涉及的概念进行介绍。
1、能力集
能力集是指与设备某一功能相关的数据集合。比如，设备功能为人脸检测功能，该能力集是指与人脸检测功能相关的数据的集合。
通常，设备的配置页面上会显示设备所具有的功能，所以设备的配置页面的显示是与设备的能力集相关的。
例如，如图1所示，设备的能力集决定了图1左侧显示的目录栏包含哪些功能(比如图片功能、存储功能等)，此外，设备的能力集还决定了图1右侧的配置条目栏具体显示哪些条目等。
此外，还需要说明的是，通常设备的配置页面包括静态资源和动态数据。静态资源一般储存在用户终端上。
其中，静态资源可包括：样式文件，html文件，脚本文件。其中，样式文件和html文件决定了配置页面的样式，脚本文件决定了配置页面的一些操作。
动态数据可包括：与该配置页面相关的能力集。该动态数据一般存储在要被配置的设备上。
当用户终端需要展示配置页面，可从要被配置的设备获取该配置页面对应的能力集，并基于获取的能力集和本地静态资源展示该配置页面。
下文所述的，基于首配置页面的能力集或者子配置页面的能力集，展示首配置页面或者子配置页面的具体过程包括：用户终端基于本地缓存的首配置页面或者子配置页面的静态资源，以及获取到的首配置页面或子配置页面的能力集，展示首配置页面或子配置页面。下文不再赘述。首配置页面指的是用户终端首次请求的配置页面，也可以理解为是初始配置页面。
参见图2，图2是本申请一示例性实施例示出的一种设备远程配置系统的组网架构 图。
设备远程配置系统包括：用户终端、管理平台和设备。
用户终端可以是包括智能手机、PC、服务器等在内的各种终端设备中的任意一个。管理平台可以是例如云平台等。管理平台管理了至少一个设备(比如该设备可包括IPC设备、NVR设备，这里只是对设备进行示例性地说明，不对其进行具体地限定)。用户终端可通过管理平台对设备进行配置。
在传统的配置方式中，用户终端维护了各设备的配置页面(包括首配置页面和子配置页面)的静态资源(比如样式文件，html文件，脚本文件)，当检测到针对目标设备的配置页面的页面展示事件时，用户终端可从管理平台获取该目标设备的配置页面的能力集，然后用户终端可基于配置页面的能力集以及该目标设备的配置页面的静态资源，展示该目标设备的配置页面。用户终端可将用户通过配置页面输入的配置信息发送给管理平台，管理平台可将配置信息下发给目标设备，从而完成目标设备的配置。
然而，在现有的获取配置页面的方式中，用户终端在检测到针对目标设备配置页面的页面展示事件时，都从管理平台获取该配置页面的能力集，用户终端基于该能力集显示配置页面。由于用户终端每一次在检测到针对配置页面的页面展示事件时，都需要从管理平台获取该配置页面的能力集，所以大大增加了配置页面的获取时间。此外，从用户角度来说，用户在触发配置页面的请求后，要等待很长时间才能看到配置页面，使得用户体验较差。
有鉴于此，本申请提出一种配置页面请求方法，用户终端主动拉取(GET)该用户终端可访问的所有可访问设备的首配置页面的能力集并缓存。在本申请文件中，“拉取”的操作可以理解为：发出请求，获取到数据然后缓存该数据。
当用户终端在检测到针对目标设备的配置页面的页面展示事件时，若本地缓存有该目标设备配置页面的能力集，则基于所述目标设备配置页面的能力集展示所述配置页面。
由于用户终端在检测到目标设备的配置页面的页面展示事件时，若本地缓存了该配置页面的能力集，则可基于本地缓存的能力集展示对应的配置页面，而无需从管理平台获取该配置页面的能力集，所以提高了目标设备的配置页面的请求效率。此外，对于用户而言，用户在触发配置页面的页面展示事件后，可以很快看到配置页面，所以采用本申请的方法可以大大降低配置页面的展示时延，大大提高了用户体验。
参见图3，图3是本申请一示例性实施例示出的一种配置页面的请求方法的流程图，该方法可应用在用户终端上，可包括如下所示步骤。
步骤301：用户终端在检测到针对目标设备配置页面的页面展示事件的情况下，从已缓存的所述用户终端可访问的至少一个可访问设备的能力集中，获取所述目标设备的配置页面对应的能力集；
步骤302：若获取到所述目标设备的配置页面对应的能力集，用户终端则利用获取到的该能力集展示对应的配置页面。
其中，上述配置页面可以是目标设备的首配置页面，也可以是目标设备的首配置页面关联的子配置页面。这里只是示例性地说明，不对其进行具体地限定。
下面从上述配置页面为首配置页面，上述配置页面为子配置页面两方面，对本申请 提供的配置页面请求方法进行示例性地说明。
1、配置页面为首配置页面
下面从首配置页面的能力集缓存，首配置页面展示这两方面，对首配置页面的请求方法进行详细地介绍。
1.1)首配置页面的能力集缓存
参见图4，图4是本申请一示例性实施例示出的一种首配置页面的能力集缓存方法的流程图，该方法可应用在用户终端上，可包括如下所示步骤。
步骤401：用户终端从管理平台获得该用户终端可访问的可访问设备的设备信息。
在一些示例中，用户终端可向管理平台(例如，管理设备)发送用于获取可访问设备的设备信息的获取请求，该获取请求中携带了用户终端的标识。管理设备在接收到该获取请求后，可在管理设备所管理的所有设备中，确定出该用户终端可访问的可访问设备，并将确定出的可访问设备的设备信息发送给该用户终端。
其中，可访问设备的设备信息可包括：设备标识。当然，可访问设备的设备信息还可包括其他信息，比如设备工作状态信息等等，这里只是示例性地说明，不对其进行具体地限定。
在一些示例中，用户终端可将接收到的可访问设备的设备信息通知给本地服务(例如，Web控件)，然后由本地服务来拉取各可访问设备的首配置页面对应的能力集。
步骤402：用户终端依据所述可访问设备的设备信息，拉取各可访问设备的首配置页面对应的能力集并缓存。
在一种可选的实现方式中，用户终端可将可访问设备的设备标识添加在拉取队列里，并按照队列顺序，依次拉取队列中的设备的首配置页面的能力集。
每拉取到一个设备的首配置页面的能力集，就将该拉取到的能力集缓存至本地。
在一种可选的实现方式中，用户终端可以并行对多个可访问设备的首配置页面的能力集进行拉取，各个可访问设备的首配置页面的能力集的拉取过程相互独立。
下面介绍拉取一个可访问设备的首配置页面的能力集的方式：
用户终端上配置了该可访问设备的首配置页面的能力集配置文件(即cache.json)。该能力集配置文件里包括针对该设备的至少一个能力集的能力集请求。需要说明的是，不同类型设备的首配置页面的能力集配置文件不同，相同类型设备的首配置页面可以复用一份能力集配置文件，例如所有前端设备复用一份能力集配置文件、所有后端设备复用一份能力集配置文件。
例如，如图5所示，图5是本申请一示例性实施例示出的一种首配置页面的能力集配置文件的示意图。
如图5所示，图5中的每一个框，框出的内容即为一个能力集请求。
在一种可选的实现方式中，用户终端可执行该能力集配置文件，依次发送该能力集配置文件中的M个能力集请求。其中，M为大于0的整数。
当然，为了提高能力集请求的发送速率，用户终端也可每次并行发送N个能力集请 求。其中，N为大于0的整数。M可以大于N，M也可以等于N，这里不进行具体地限定。
具体地，用户终端可向该可访问设备并行发送N个能力集请求，从而该可访问设备可以并行接收和处理该N个能力集请求。针对每一能力集请求，若在预设时长内接收到针对该能力集请求所请求的能力集、并且存在待发送的能力集请求，则用户终端从M个能力集请求中获取下一个或多个待发送的能力集请求进行发送。若在预设时长内接收到针对该能力集请求所请求的能力集、且不存在待发送的能力集请求，则确定M个能力集请求发送完成。若在预设时长内未接收到该能力集请求所请求的能力集，则将该能力集请求标记为失败请求。
在发送完该M个能力集请求后，扩大该预设时长，并向该可访问设备发送该标记为失败请求的能力集请求。
具体地，在本申请中，可设置容量为N个请求的请求队列池。在向可访问设备发送该能力集配置文件中的能力集请求时，可将N个能力集请求添加至请求队列池中。用户终端可将请求队列池中的能力集请求发送给可访问设备。
针对请求队列池中的每一能力集请求，若用户终端在预设时长内接收到该能力集请求所请求的能力集，则将该能力集请求从该请求队列池中删除，并将下一个待发送的能力集请求添加至该请求队列池。
若用户终端在预设时长内未接收到该能力集请求所请求的能力集，则将该能力集请求从该请求队列池中删除，并将该能力集请求标记为失败请求，在发送完用于请求该可访问设备首配置页面的能力集的所有能力集请求后，扩大该预设时长，并向该可访问设备发送该标记为失败请求的能力集请求。
例如，如图6所示，假设请求队列池的容量N为4。图6中的“ISAPI/1/capabilities”代表能力集请求1，“ISAPI/2/capabilities”代表能力集请求2，依次类推。
用户终端可将能力集请求1、能力集请求2、能力集请求3和能力集请求4添加在请求队列池中。用户终端可并行发送请求队列池中的这4个能力集请求。
假设，用户终端在预设时长内，先接收到了能力集请求1和能力集请求3对应的能力集，则将能力集请求1和能力集请求3从该请求队列池中删除，并将能力集请求5和能力集请求6添加至请求队列池中。用户终端发送请求队列池中的能力集请求5和能力集请求6。
假设在预设时长内未接收到能力集请求2和能力集请求4所请求的能力集，用户终端可将能力集请求2和能力集请求4标记为失败请求，并将能力集请求2和4从请求队列池中删除，将能力集请求7和8添加在请求队列池中。
在发送完所有能力集请求后，扩大预设时长，重新发送被标记为失败请求的能力集请求2和4。
此外，需要说明的是：用户终端在向可访问设备发送能力集请求时，用户可直接向与该用户终端直连的可访问设备发送能力集请求，并接收可访问设备直接返回的能力集。当然，用户终端也可通过管理平台向可访问设备发送能力集请求，来实现“向可访问设备发送能力集请求”。
具体地，用户终端向管理平台发送能力集请求，管理平台在接收到用户终端发送的能力集请求后，可将能力集请求转发给设备。设备向管理平台返回所请求的能力集，管理平台将设备返回的能力集转发给用户终端。
在一些示例中，用户终端向管理平台或可访问设备发送该能力集请求可通过如下方式实现：当用户在用户终端通过浏览器窗口执行了对配置页面的触发操作后，浏览器向本地服务(例如，Web控件)发送针对所述配置页面的能力集请求，如果本地服务判断用户终端本地没有缓存针对所述配置页面的能力集，则本地服务将该请求发送给可访问设备，或者由本地服务将该请求发送给管理平台，由管理平台将该请求转发给可访问设备。
此外，还需要说明的是，在本申请中，用户终端向可访问设备发送能力集请求，并接收可访问设备返回的能力集。用户终端在接收到能力集后，可对能力集请求进行改写，得到用户储存该能力集的文件名。
在改写时，用户终端可将能力集请求中的反斜杠转换为文件名支持的符号(比如下划线)，然后再在能力集请求的结尾增加数据格式，从而形成文件名。
例如，假设能力集请求为：http://127.0.0.1/ISAPI/Security/capabilities，对该能力集请求进行改写得到的文件名为：ISAPI_Security_capabilities.xml。其中，xml为数据格式。
再例如，假设能力集请求为：http://127.0.0.1/ISAPI/Security/capabilities？format＝json，对该能力集请求进行改写得到的文件名为：ISAPI_Security_capabilities.json。其中，json为数据格式。
1.2)首配置页面的展示
参见图7，图7是本申请一示例性实施例示出的一种首配置页面请求方法的流程图，该方法可应用在用户终端上，可包括如下所示步骤。
步骤701：用户终端在检测到针对目标设备首配置页面的页面展示事件的情况下，从已缓存的所述用户终端可访问的至少一个可访问设备的能力集中，获取所述目标设备的首配置页面对应的能力集。
在一些示例中，用户终端在获取该管理平台发送的该用户终端可访问的设备信息时，用户终端可向用户展示该各可访问设备的标识。
用户会依据用户终端展示出的各可访问设备的标识，选择出本次需要访问的目标设备，在用户选择出目标设备后，就会触发该目标设备的首配置页面的展示。
此外，当用户从目标设备的子配置页面返回首配置页面等一些操作时，也都会触发目标设备的首配置页面的展示。
当用户终端在检测到目标设备的首配置页面的页面展示事件时，可检测已缓存的该用户终端可访问的至少一个可访问设备的能力集中，是否存在该目标设备的首配置页面对应的能力集。
其中，在检测已缓存的该用户终端可访问的至少一个可访问设备的能力集中，是否存在该目标设备的首配置页面对应的能力集时，用户终端可检测本地缓存的可访问 设备的能力集文件中，是否存在该目标设备对应的能力集文件夹。
若本地缓存有该目标设备对应的能力集文件夹，则进一步在该能力集文件夹里查找是否缓存有与该目标设备的首配置页面对应的能力集；若是，则确定本地缓存了该首配置页面对应的能力集，若否，则确定本地未缓存该首配置页面对应的能力集。
若本地未缓存有该目标设备对应的能力集文件夹，则确定本地未缓存该首配置页面对应的能力集。
步骤702：若获取到所述目标设备的首配置页面对应的能力集，用户终端则利用获取到的该能力集展示对应的首配置页面。
在一些示例中，若本地缓存有该目标设备首配置页面对应的能力集，则可从本地缓存的至少一个可访问设备的能力集中，获取到该目标设备首配置页面对应的能力集，用户终端则利用获取到的该能力集展示对应的首配置页面。比如，用户终端可基于本地储存的该目标设备的首配置页面的静态资源、以及获取到的目标设备首配置页面对应的能力集，展示对应的首配置页面。
此外，在本申请实施例中，在用户终端在已缓存的该用户终端可访问的至少一个可访问设备的能力集中，未获取到所述目标设备的首配置页面对应的能力集时，若所述目标设备的首配置页面对应的能力集正在拉取过程中，则在目标设备的首配置页面对应的能力集被拉取成功后，依据目标设备的首配置页面对应的能力集展示所述首配置页面，并缓存所述目标设备的首配置页面对应的能力集；否则，向所述目标设备发送请求以获得所述目标设备的首配置页面能力集并缓存，依据已获得的能力集展示对应的首配置页面。
在一些示例中，若已缓存可访问设备的能力集中不存在目标设备首配置页面对应的能力集，则用户终端可检测该目标设备的首配置页面的能力集是否在拉取过程中。
在一种可选的检测方式中，用户终端可为正在进行首配置页面能力集拉取的设备配置正在拉取标记。在检测该目标设备的首配置页面的能力集是否在拉取过程时，用户终端可检测该拉取队列中的目标设备是否被配置有正在拉取标记，若有，则确定该目标设备的首配置页面能力集正在被拉取。若目标设备没有该正在拉取标记，则确定该目标设备的首配置页面能力集未正在被拉取。
1)若所述目标设备的首配置页面对应的能力集正在拉取过程中
若所述目标设备的首配置页面对应的能力集正在拉取过程中，则在目标设备的首配置页面对应的能力集被拉取成功后，依据目标设备的首配置页面对应的能力集展示所述首配置页面，并缓存所述目标设备的首配置页面对应的能力集。
在一种可选的实现方式中，在本申请中，若目标设备的首配置页面的能力集正在被拉取，用户终端可等待。然后，用户终端可实时监测该目标设备的拉取标记，若该目标设备的拉取标记从正在被拉取变为拉取完毕，则确定目标设备的首配置页面的能力集拉取完成。然后，用户终端可基于首配置页面的能力集展示目标配置页面，并缓存该目标设备首配置页面对应的能力集。
2)若所述目标设备的首配置页面对应的能力集不在拉取过程中
若所述目标设备的首配置页面对应的能力集不在拉取过程中，用户终端则向所 述目标设备发送请求以获得所述目标设备的首配置页面能力集并缓存，依据已获得的能力集展示对应的首配置页面。
其中，用户终端在向目标设备发送请求时，用户终端可以直接向目标设备发送请求。当然，用户终端也可将请求发送给管理平台，以由管理平台将该请求转发给目标设备，来实现“向目标设备发送请求”。这里只是示例性地说明，不对其进行具体地限定。
此外，在从目标设备请求到该目标设备首配置页面对应的能力集后，用户终端还可将所述目标设备标记为已拉取设备。在一种可选的标记方式中，用户终端可从上文所述拉取队列中将该目标设备标识删除等。这里只是对标记方式的一种示例性说明，不对其进行具体地限定。
2、子配置页面的展示
参见图8，图8是本申请一示例性实施例示出的一种子配置页面请求方法的流程图，该方法可应用在用户终端上，可包括如下所示步骤。
步骤801：用户终端在检测到针对目标设备子配置页面的页面展示事件的情况下，从已缓存的所述用户终端可访问的至少一个可访问设备的能力集中，获取所述目标设备的子配置页面对应的能力集；
步骤802：若获取到所述目标设备的子配置页面对应的能力集，用户终端则利用获取到的该能力集展示对应的子配置页面；
步骤803：若未获取到所述目标设备的子配置页面对应的能力集，则向目标设备请求所述子配置页面对应的能力集并缓存。
其中，在向目标设备请求所述子配置页面对应的能力集时，用户终端可直接将请求发送给目标设备，以获取目标设备直接返回的能力集。当然，用户终端也可将请求发送给管理平台，以由管理平台将该请求发送给目标设备，以获取子配置页面对应的能力集，实现“向目标设备请求所述子配置页面对应的能力集”。这里不进行具体地限定。
此外，在本申请实施例中，目标设备上维护的配置页面(包括首配置页面或子配置页面)的能力集并不是一成不变的，为了保证用户终端缓存的配置页面的能力集与目标设备上维护的配置页面的能力集一致，本申请还采用了如下方式对用户终端上缓存的能力集进行更新。
下面具体介绍更新方式：
在本申请实施例中，有些首配置页面或者子配置页面上的一些配置参数是与能力集关联的(这里为了方便叙述，将这些配置参数称为指定配置参数)。
比如，指定配置参数可以是能力集使能配置参数，当该能力集使能配置参数表示使能能力集时，设备会开启该能力集，当该能力集使能配置参数表示不能使能时，设备会关闭该能力集。
管理员修改了该目标设备的首配置页面或子配置页面的指定配置参数后，用户终端会将该指定配置参数的修改指令通过管理平台，发送给目标设备，目标设备基于该指令，修改本设备的指定配置参数，该指定配置参数修改后，会造成该目标设备的当前维护的能力集发生变化。
在本申请中，造成目标设备的当前维护的能力集发生变化包括两种情况。
第一种情况是：其他用户通过其他用户终端修改了目标设备的首配置页面或子配置页面上的指定配置参数，而造成了目标设备的当前维护的能力集发生变化。
第二种情况是：用户使用本用户终端修改了目标设备的首配置页面或子配置页面的指定配置参数而造成了目标设备的当前维护的能力集发生变化。
下面分别介绍这两种情况。
第一种情况：其他用户通过其他用户终端修改了目标设备的首配置页面或子配置页面的指定配置参数而造成了目标设备的当前维护的能力集发生变化。
在第一种情况下，由于指定配置参数的修改是发生在其他用户终端上的，所以本用户终端并不能获知目标设备上的哪些指定参数进行了修改，目标设备上的哪些能力集发生变化，所以为了保证在这种情况下，用户终端缓存的目标设备的首配置页面或子配置页面能力集与目标设备上维护的首配置页面或子配置页面对应的能力集一致。用户终端需要在每一次基于已缓存的首配置页面或子配置页面的能力集展示对应的首配置页面或子配置页面后，获取目标设备当前维护的首配置页面或子配置页面的能力集，以基于目标设备当前维护的首配置页面或子配置页面的能力集，来更新本地缓存的首配置页面或子配置页面的能力集，以保持两者能力集的一致。
具体地，在本申请中，在用户终端检测到针对目标设备首配置页面或子配置页面的页面展示事件时，若已缓存的能力集中存在目标设备的首配置页面或子配置页面的能力集，用户终端在依据该缓存的首配置页面或子配置页面的能力集展示所述首配置页面或子配置页面后，还需要向目标设备请求所述目标设备的首配置页面或子配置页面对应的能力集。
目标设备可将本地当前维护的首配置页面或子配置页面的能力集返回给用户终端。
用户终端可利用返回的该目标设备当前维护的首配置页面或子配置页面的能力集，更新本地已缓存的该目标设备首配置页面或子配置页面的能力集，使得本地缓存的目标设备首配置页面或子配置页面的能力集与目标设备当前维护的首配置页面或子配置页面的能力集保持一致。
第二种情况，用户使用本用户终端修改了目标设备的首配置页面或子配置页面的指定配置参数而造成了目标设备的当前维护的能力集发生变化。
在第二种情况中，由于指定配置参数的修改是发生在本用户终端上的，所以本用户终端可以获知哪些指定配置参数发生了修改，所以本用户终端可以采用主动更新的方式，使得用户终端上缓存的首配置页面或子配置页面对应的能力集与目标设备上维护的主配置页面或子配置页面对应的能力集一致。
具体地，用户终端上还配置了指定配置参数和至少一个能力集的对应关系。该对应关系表明，该配置参数的改变，会造成设备上维护的能力集的改变。
例如，如图9所示，虚线框表示配置参数，实线框框住的内容表示与该配置参数关联的能力集请求。
在本申请中，为了使得本地缓存的能力集与目标设备与上维护的能力集一致， 用户终端在检测到针对首配置页面或者子配置页面上的配置参数的修改事件时，在预设的配置参数与能力集请求的对应关系(即refresh.json)中，查找该被修改的配置参数对应的能力集请求，并向目标设备发送该能力集请求。
目标设备可将该能力集请求所请求的能力集返回给用户终端。用户终端可基于管理平台返回的能力集更新本地缓存的与该指定配置参数对应的能力集。
其中，用户终端在向目标设备发送能力集请求时，用户终端可直接向目标设备发送能力集请求，并接收目标设备直接返回的能力集。
当然，用户终端也可通过管理平台向目标设备发送能力集请求，并接收管理平台转发的能力集，来实现“向所述目标设备发送查找到的能力集请求，并接收所述目标设备返回的针对该查找到的能力集请求所请求的能力集”。
具体地，用户终端向管理平台发送能力集请求，管理平台在接收到用户终端发送的能力集请求后，可将能力集请求转发给目标设备。设备向管理平台返回所请求的能力集，管理平台将目标设备返回的能力集转发给用户终端。
由上述描述可知，一方面，由于用户终端在登录至管理平台后就主动拉取该用户终端的可访问的所有可访问设备的首配置页面的能力集并缓存，所以在检测到针对目标设备的首配置页面的页面展示事件时，若已拉取到该首配置页面的能力集，可从本地缓存里获取该首配置页面的能力集，不需要向管理平台请求获取该目标能力集，所以提高了目标配置页面的请求效率。此外，对于用户而言，用户在触发首配置页面的请求后，可以很快看到配置页面，所以采用本申请的方法可以大大降低首配置页面的展示时延，大大提高了用户体验。
另一方面，由于配置页面的能力集可以被复用，所以当缓存的首配置页面的能力集包含子配置页面的能力集时，可以直接基于缓存中的子配置页面的能力集进行子配置页面的显示，而无需再下载子配置页面的能力集，提高了子配置页面能力集的请求效率。
第三方面，设备能力集是可以被管理员更新的，所以本申请还设计了与上述两种情况对应的本地缓存的能力集的更新方式，以使得本地缓存的能力集与设备维护的能力集一致。
参见图10，图10是本申请一示例性实施例示出的一种首配置页面的请求方法流程图，该方法可应用在用户终端上，可包括如下所示步骤。
步骤1001：用户终端向管理平台获取该用户终端可访问的至少一个可访问设备的设备信息。
步骤1002：用户终端依据至少一个可访问设备的设备信息，依次拉取各可访问设备的首配置页面的能力集并缓存。
在一种可能的实施方式中，用户终端可以并行拉取多个可访问设备的首配置页面的能力集并缓存。
步骤1003：用户终端在检测到针对目标设备的首配置页面的页面展示事件时，检测本地缓存的能力集中是否包含该目标设备首配置页面的能力集。
若本地缓存的能力集中包含该目标设备首配置页面的能力集，则执行步骤 1004-1005。
若本地缓存的能力集中不包含该目标设备首配置页面的能力集，则执行步骤1006-1008。
需要说明的是，步骤1002和步骤1003的执行是相互独立，互不影响的。换句话来说，用户终端的一个在执行步骤1003时，步骤1002的拉取过程可能还在执行。
步骤1004：若本地缓存的能力集中包含该目标设备首配置页面的能力集，则基于所述目标设备首配置页面的能力集展示所述首配置页面。
步骤1005：用户终端向管理平台获取该目标设备首配置页面的能力集，并利用获取到的该目标设备首配置页面的能力集，更新本地缓存的该目标设备首配置页面的能力集。
步骤1006：若本地缓存的能力集中不包含该目标设备首配置页面的能力集，用户终端则可检测目标设备的首配置页面的能力集是否在拉取过程中。
若目标设备的首配置页面的能力集不在拉取过程中，则执行步骤1007。
若目标设备的首配置页面的能力集在被拉取过程中，则执行步骤1008。
步骤1007：若目标设备的首配置页面的能力集不在拉取过程中，则向管理平台请求所述目标设备的首配置页面的能力集并缓存，并基于目标设备的首配置页面的能力集展示首配置页面。
步骤1008：若该目标设备的首配置页面的能力集在拉取过程中，用户终端等待直至拉取到首配置页面的能力集，并基于首配置页面的能力集展示目标设备的首配置页面。
此外，在本申请中，用户终端在检测到针对所述目标设备的首配置页面上的指定配置参数的修改事件时，在预设的指定配置参数与能力集请求的对应关系中，查找该被修改的指定配置参数对应的能力集请求。然后，用户终端可向所述管理平台发送查找到的能力集请求，并接收所述管理平台返回的针对该查找到的能力集请求所请求的能力集，并基于返回的能力集，更新本地缓存的与修改的指定配置参数对应的能力集。
具体可参见上文描述，这里不再赘述。
参见图11，图11是本申请一示例性实施例示出的一种子配置页面的请求方法流程图，该方法可应用在用户终端上，可包括如下所示步骤。
步骤1101：用户终端在检测到针对所述首配置页面关联的子配置页面的页面展示事件的情况下，检测本地缓存的能力集中是否包含该子配置页面对应的能力集。
若本地缓存的能力集中包含该子配置页面对应的能力集，则执行步骤1102-步骤1103；
若本地缓存的能力集中不包含子配置页面的能力集，则执行步骤1104。
步骤1102：若本地缓存的能力集中包含该子配置页面对应的能力集，则基于本地缓存的该子配置页面的能力集展示该子配置页面。
步骤1103：用户终端向管理平台请求该子配置页面的能力集，并基于请求的该子配置页面的能力集更新本地缓存该子配置页面对应的能力集。
步骤1104：若本地缓存的能力集中不包含子配置页面的能力集，则向所述管理 平台请求所述子配置页面对应的能力集。
此外，在本申请中，用户终端在检测到针对所述目标设备的子配置页面上的指定配置参数的修改事件时，在预设的指定配置参数与能力集请求的对应关系中，查找该被修改的指定配置参数对应的能力集请求。然后，用户终端可向所述管理平台发送查找到的能力集请求，并接收所述管理平台返回的针对该查找到的能力集请求所请求的能力集，并基于返回的能力集，更新本地缓存的与修改的指定配置参数对应的能力集。
具体可参见上文描述，这里不再赘述。
此外，本申请还提供一种电子设备，该电子设备可包括：机器可读存储介质和处理器；
其中，所述机器可读存储介质，用于存储机器可执行指令；
所述处理器，用于读取所述机器可读存储介质上的所述机器可执行指令，并执行所述指令以实现上述配置页面请求方法的各步骤。
可选的，如图12所示，该电子设备除了包括处理器1202、机器可读存储介质1203外，还可包括通信接口1201、总线1204；其中，通信接口1201、处理器1202和机器可读存储介质1203通过总线1204完成相互间的通信。处理器1202通过读取并执行机器可读存储介质1203中的机器可执行指令，可执行上文描述的配置页面请求方法。
本领域技术人员可以理解，图12中示出的结构并不构成对电子设备的限定，可以包括比图示更多或更少的组件，或者组合某些组件，或者采用不同的组件布置。
参见图13，图13是本申请一示例性实施例示出的一种配置页面的请求装置的框图。该装置可应用在用户终端上，通常可包括如下所示单元。
获取单元1301，用于在检测到针对目标设备配置页面的页面展示事件的情况下，从已缓存的所述用户终端可访问的至少一个可访问设备的能力集中，获取所述目标设备的配置页面对应的能力集；
展示单元1302，用于若获取到所述目标设备的配置页面对应的能力集，则利用获取到的该能力集展示对应的配置页面。
可选的，所述装置还包括：
拉取单元1303，用于在所述在检测到针对目标设备配置页面的页面展示事件的情况下，从已缓存的所述用户终端可访问的至少一个可访问设备的能力集中，获取所述目标设备的配置页面对应的能力集之前，从管理平台获得所述可访问设备的设备信息；依据所述可访问设备的设备信息，拉取各可访问设备的首配置页面对应的能力集并缓存。
可选的，所述展示单元1302，还用于若所述配置页面为首配置页面，则在未获取到所述目标设备的配置页面对应的能力集的情况下，若所述目标设备的首配置页面对应的能力集正在拉取过程中，则在目标设备的首配置页面对应的能力集被拉取成功后，依据目标设备的首配置页面对应的能力集展示所述首配置页面，并缓存所述目标设备的首配置页面对应的能力集；否则，向所述目标设备发送请求以获得所述目标设备的首配置页面对应的能力集并缓存，依据已获得的能力集展示对应的首配置页面。
可选的，所述展示单元1302，还用于若所述配置页面为该首配置页面关联的子配置页面，则在未获取到所述目标设备的配置页面对应的能力集的情况下，向所述目标设备请求所述子配置页面对应的能力集并缓存，并依据所述子配置页面的能力集展示所述子配置页面。
可选的，所述装置还包括：
更新单元1304，用于已缓存的能力集中存在所述配置页面对应的能力集，则在展示所述配置页面的能力集后，向所述目标设备请求所述配置页面对应的能力集；依据 所述目标设备返回的能力集更新已缓存的所述配置页面的能力集；
和/或
用于在检测到针对所述配置页面上的指定配置参数的修改事件时，在预设的指定配置参数与能力集请求的对应关系中，查找该被修改的指定配置参数对应的能力集请求；向所述目标设备发送查找到的能力集请求，并接收所述目标设备返回的针对该查找到的能力集请求所请求的能力集。
可选的，所述拉取单元1303，在拉取各可访问设备的首配置页面对应的能力集时，用于针对每一可访问设备，确定用于请求该可访问设备首配置页面的能力集的M个能力集请求向该可访问设备并行发送N个能力集请求，针对已发送的每一个能力集请求，若在预设时长内未接收到该能力集请求所请求的能力集，则将该能力集请求标记为失败请求；在发送完M个能力集请求后，扩大该预设时长，并向该可访问设备再次发送该标记为失败请求的能力集请求，其中，M、N为大于0的整数，M大于等于N。
本领域技术人员可以理解，图13中示出的框图并不构成对配置页面的请求装置的限定，可以包括比图示更多或更少的单元。
此外，本申请还提供一种机器可读存储介质，所述机器可读存储介质内存储有机器可执行指令，所述机器可执行指令被处理器执行时实现上述配置页面的请求方法。
本文中提到的机器可读存储介质可以是任何电子、磁性、光学或其它物理存储装置，可以包含或存储信息，如可执行指令、数据，等等。例如，机器可读存储介质可以是：易失存储器、非易失性存储器或者类似的存储介质。具体地，机器可读存储介质可以是RAM(Radom Access Memory，随机存取存储器)、闪存、存储驱动器(如硬盘驱动器)、固态硬盘、任何类型的存储盘(如光盘、DVD等)，或者类似的存储介质，或者它们的组合。
此外，本申请还提供一种计算机程序，计算机程序存储于计算机可读存储介质，并且当处理器执行计算机程序时，促使处理器实现上述配置页面的请求方法。
上述装置中各个单元的功能和作用的实现过程具体详见上述方法中对应步骤的实现过程，在此不再赘述。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本申请方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
以上所述仅为本申请的较佳实施例而已，并不用以限制本申请，凡在本申请的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请保护的范围之内。

Claims (16)

  1. 一种配置页面的请求方法，其特征在于，所述方法应用于用户终端，包括：
    在检测到针对目标设备配置页面的页面展示事件的情况下，从已缓存的所述用户终端可访问的至少一个可访问设备的能力集中，获取所述目标设备的配置页面对应的能力集；
    若获取到所述目标设备的配置页面对应的能力集，则利用获取到的该能力集展示对应的配置页面。
  2. 根据权利要求1所述的方法，其特征在于，在所述在检测到针对目标设备配置页面的页面展示事件的情况下，从已缓存的所述用户终端可访问的至少一个可访问设备的能力集中，获取所述目标设备的配置页面对应的能力集之前，所述方法还包括：
    从管理平台获得所述可访问设备的设备信息；
    依据所述可访问设备的设备信息，拉取各可访问设备的首配置页面对应的能力集并缓存。
  3. 根据权利要求2所述的方法，其特征在于，若所述配置页面为首配置页面，则在未获取到所述目标设备的配置页面对应的能力集的情况下，所述方法还包括：
    若所述目标设备的首配置页面对应的能力集正在拉取过程中，则在所述目标设备的首配置页面对应的能力集被拉取成功后，依据所述目标设备的首配置页面对应的能力集展示所述首配置页面，并缓存所述目标设备的首配置页面对应的能力集；
    否则，向所述目标设备发送请求以获得所述目标设备的首配置页面对应的能力集并缓存，依据已获得的能力集展示对应的首配置页面。
  4. 根据权利要求1所述的方法，其特征在于，若所述配置页面为与目标设备的首配置页面关联的子配置页面，则在未获取到所述目标设备的配置页面对应的能力集的情况下，所述方法还包括：
    向所述目标设备请求所述子配置页面对应的能力集并缓存，并依据所述子配置页面的能力集展示所述子配置页面。
  5. 根据权利要求1所述的方法，其特征在于，若已缓存的能力集中存在所述配置页面对应的能力集，则在展示所述配置页面的能力集后，所述方法还包括：
    向所述目标设备请求所述配置页面对应的能力集；
    依据所述目标设备返回的能力集更新已缓存的所述配置页面的能力集。
  6. 根据权利要求2所述的方法，其特征在于，所述拉取各可访问设备的首配置页面对应的能力集，包括：
    针对每一可访问设备，确定用于请求该可访问设备首配置页面的能力集的M个能力集请求；
    向该可访问设备并行发送N个能力集请求，针对已发送的每一个能力集请求，若在预设时长内未接收到该能力集请求所请求的能力集，则将该能力集请求标记为失败请求；
    在发送完M个能力集请求后，扩大该预设时长，并向该可访问设备再次发送该标记为失败请求的能力集请求，
    其中，M、N为大于0的整数，M大于等于N。
  7. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    在检测到针对所述配置页面上的指定配置参数的修改事件时，在预设的指定配置参数与能力集请求的对应关系中，查找该被修改的指定配置参数对应的能力集请求；
    向所述目标设备发送查找到的能力集请求，并接收所述目标设备返回的针对该查找到的能力集请求所请求的能力集；
    基于返回的能力集，更新本地缓存的与修改的指定配置参数对应的能力集。
  8. 一种配置页面的请求装置，其特征在于，所述装置应用于用户终端，包括：
    获取单元，用于在检测到针对目标设备配置页面的页面展示事件的情况下，从已缓存的所述用户终端可访问的至少一个可访问设备的能力集中，获取所述目标设备的配置页面对应的能力集；
    展示单元，用于若获取到所述目标设备的配置页面对应的能力集，则利用获取到的该能力集展示对应的配置页面。
  9. 根据权利要求8所述的装置，其特征在于，所述装置还包括：
    拉取单元，用于在所述在检测到针对目标设备配置页面的页面展示事件的情况下，从已缓存的所述用户终端可访问的至少一个可访问设备的能力集中，获取所述目标设备的配置页面对应的能力集之前，从管理平台获得所述可访问设备的设备信息；依据所述可访问设备的设备信息，拉取各可访问设备的首配置页面对应的能力集并缓存。
  10. 根据权利要求9所述的装置，其特征在于，
    所述展示单元，还用于若所述配置页面为首配置页面，则在未获取到所述目标设备的配置页面对应的能力集的情况下，若所述目标设备的首配置页面对应的能力集正在拉取过程中，则在所述目标设备的首配置页面对应的能力集被拉取成功后，依据所述目标设备的首配置页面对应的能力集展示所述首配置页面，并缓存所述目标设备的首配置页面对应的能力集；否则，向所述目标设备发送请求以获得所述目标设备的首配置页面对应的能力集并缓存，依据已获得的能力集展示对应的首配置页面。
  11. 根据权利要求8所述的装置，其特征在于，
    所述展示单元，还用于若所述配置页面为与目标设备的首配置页面关联的子配置页面，则在未获取到所述目标设备的配置页面对应的能力集的情况下，向所述目标设备请求所述子配置页面对应的能力集并缓存，并依据所述子配置页面的能力集展示所述子配置页面。
  12. 根据权利要求9所述的装置，其特征在于，
    所述拉取单元，在拉取各可访问设备的首配置页面对应的能力集时，用于针对每一可访问设备，确定用于请求该可访问设备首配置页面的能力集的M个能力集请求；向该可访问设备并行发送N个能力集请求，针对已发送的每一个能力集请求，若在预设时长内未接收到该能力集请求所请求的能力集，则将该能力集请求标记为失败请求；在发送完M个能力集请求后，扩大该预设时长，并向可访问设备再次发送该标记为失败请求的能力集请求；
    其中，M、N为大于0的整数，M大于等于N。
  13. 根据权利要求8所述的装置，其特征在于，所述装置还包括：
    更新单元，用于若已缓存的能力集中存在所述配置页面对应的能力集，则在展示所述配置页面的能力集后，向所述目标设备请求所述配置页面对应的能力集；依据所述目标设备返回的能力集更新已缓存的所述配置页面的能力集；
    和/或，用于在检测到针对所述配置页面上的指定配置参数的修改事件时，在预设的指定配置参数与能力集请求的对应关系中，查找该被修改的指定配置参数对应的能力集请求；向所述目标设备发送查找到的能力集请求，并接收所述目标设备返回的针对该查找到的能力集请求所请求的能力集；基于返回的能力集，更新本地缓存的与修改的指定配置参数对应的能力集。
  14. 一种电子设备，其特征在于，所述电子设备包括非暂时性机器可读存储介质和处理器；
    其中，所述机器可读存储介质，用于存储机器可执行指令；
    所述处理器，用于读取所述机器可读存储介质上的所述机器可执行指令，并执行所述指令以实现权利要求1-7任一所述方法的步骤。
  15. 一种机器可读存储介质，其特征在于，其上存储有机器可读指令，所述机器可读指令被处理器执行时，实现如权利要求1-7中任意一项所述方法的步骤。
  16. 一种计算机程序，所述计算机程序存储于计算机可读存储介质，并且当处理器执行计算机程序时，促使处理器执行如权利要求1-7中任意一项所述方法的步骤。
PCT/CN2021/129241 2020-11-20 2021-11-08 配置页面的请求方法、装置及电子设备 WO2022105631A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
MX2023005995A MX2023005995A (es) 2020-11-20 2021-11-08 Metodo y aparato para solicitar pagina de configuracion, y dispositivo electronico.
EP21893778.7A EP4250683A1 (en) 2020-11-20 2021-11-08 Method and apparatus for requesting configuration page, and electronic device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011311721.6A CN112532703B (zh) 2020-11-20 2020-11-20 一种配置页面的请求方法、装置及电子设备
CN202011311721.6 2020-11-20

Publications (1)

Publication Number Publication Date
WO2022105631A1 true WO2022105631A1 (zh) 2022-05-27

Family

ID=74982034

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/129241 WO2022105631A1 (zh) 2020-11-20 2021-11-08 配置页面的请求方法、装置及电子设备

Country Status (4)

Country Link
EP (1) EP4250683A1 (zh)
CN (1) CN112532703B (zh)
MX (1) MX2023005995A (zh)
WO (1) WO2022105631A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112532703B (zh) * 2020-11-20 2022-05-27 杭州海康威视数字技术股份有限公司 一种配置页面的请求方法、装置及电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105282225A (zh) * 2015-08-31 2016-01-27 四川长虹电器股份有限公司 移动终端根据物联网设备能力集动态构建界面的方法
CN105591796A (zh) * 2015-07-21 2016-05-18 杭州华三通信技术有限公司 网络设备配置方法以及装置
CN108228305A (zh) * 2018-02-02 2018-06-29 广东欧珀移动通信有限公司 应用页面的显示方法、装置、存储介质及电子设备
CN110287432A (zh) * 2019-06-28 2019-09-27 北京金山安全软件有限公司 网络信息处理方法、装置和电子设备
CN112532703A (zh) * 2020-11-20 2021-03-19 杭州海康威视数字技术股份有限公司 一种配置页面的请求方法、装置及电子设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6947440B2 (en) * 2000-02-15 2005-09-20 Gilat Satellite Networks, Ltd. System and method for internet page acceleration including multicast transmissions
CN106559401A (zh) * 2015-09-30 2017-04-05 中兴通讯股份有限公司 一种能力探测装置和方法
CN109992337B (zh) * 2017-12-29 2022-03-11 杭州海康威视系统技术有限公司 网页页面展示方法、装置及存储介质
CN111506846B (zh) * 2019-01-30 2023-05-02 杭州海康威视数字技术股份有限公司 Web页面生成方法、装置、电子设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105591796A (zh) * 2015-07-21 2016-05-18 杭州华三通信技术有限公司 网络设备配置方法以及装置
CN105282225A (zh) * 2015-08-31 2016-01-27 四川长虹电器股份有限公司 移动终端根据物联网设备能力集动态构建界面的方法
CN108228305A (zh) * 2018-02-02 2018-06-29 广东欧珀移动通信有限公司 应用页面的显示方法、装置、存储介质及电子设备
CN110287432A (zh) * 2019-06-28 2019-09-27 北京金山安全软件有限公司 网络信息处理方法、装置和电子设备
CN112532703A (zh) * 2020-11-20 2021-03-19 杭州海康威视数字技术股份有限公司 一种配置页面的请求方法、装置及电子设备

Also Published As

Publication number Publication date
CN112532703A (zh) 2021-03-19
EP4250683A1 (en) 2023-09-27
MX2023005995A (es) 2023-06-08
CN112532703B (zh) 2022-05-27

Similar Documents

Publication Publication Date Title
CN107943594B (zh) 数据获取方法和装置
US9888058B2 (en) Sending files from one device to another device over a network
US10515058B2 (en) Unified file and object data storage
CN106302595B (zh) 一种对服务器进行健康检查的方法及设备
CN104077310B (zh) 加载资源文件的方法、设备和系统
US10645192B2 (en) Identifying content files in a cache using a response-based cache index
US9876846B2 (en) Data transmission
US9088462B2 (en) Common web accessible data store for client side page processing
US9053203B2 (en) Provider-specific parsing for content retrieval
US9407726B1 (en) Caching objects identified by dynamic resource identifiers
WO2017202255A1 (zh) 页面展示方法、装置和客户端设备
EP3902266A1 (en) Processing method for dragging video data and proxy server
CN106817388B (zh) 虚拟机、宿主机获取数据的方法、装置及访问数据的系统
CN108540510B (zh) 一种云主机创建方法、装置及云服务系统
CN108256014A (zh) 页面展示方法及装置
CN104376122A (zh) 浏览器客户端获得静态文件的方法及服务器
WO2022105631A1 (zh) 配置页面的请求方法、装置及电子设备
CN109284428B (zh) 数据处理方法、装置及存储介质
CN109218799B (zh) 安卓电视快速切换高清图的方法、存储介质、设备及系统
US9160804B2 (en) Web storage optimization
US10313469B2 (en) Method, apparatus and system for processing user generated content
CN107992489A (zh) 一种数据处理方法及服务器
US20170048344A1 (en) Webpage Loading Method and Apparatus
US20160164999A1 (en) Hybrid web storage model
KR20120016335A (ko) 오프라인 실행을 위한 웹 페이지 사전 캐싱 시스템 및 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21893778

Country of ref document: EP

Kind code of ref document: A1

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112023009754

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112023009754

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20230519

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021893778

Country of ref document: EP

Effective date: 20230620