Network resource request processing method, system, medium and equipment

Abstract

The invention provides a network resource request processing method and system, a medium and equipment, and relates to the field of servers, and the method comprises the steps that an edge end host receives a resource management request; if the resource management request is a query request, performing routing lookup on address information in the resource management request; matching a request type of the resource management request to determine an interface processing program; the application interface processing program queries used resource information and stored object counting information; pre-verification is carried out on the used resource information and the stored object counting information; if yes, calling a resource processing interface corresponding to the request type to obtain management data corresponding to the resource management request; and responding to the resource management request according to the management data. When edge resource scheduling is executed, resource scheduling is carried out through routing lookup, request type matching and information verification of resource objects, and the working efficiency in the network device resource management and allocation process can be improved.

Description

Technical Field

[0001] The present application relates to the field of servers, and in particular to a method, system, medium and device for processing network resource requests. Background Art

[0002] In the traditional way, the centralized management and allocation and scheduling of network resources are more about unified planning in the early stage by professional maintenance personnel, and the maintenance personnel allocate and manage on demand; however, as the network environment operates and continues to expand, the allocation and management efficiency of network equipment resource objects gradually declines due to common factors such as the increase in the number of devices, collaborative maintenance by multiple people, and changes in planning information; it is even necessary to collect and obtain data from the network environment to manually confirm the availability and uniqueness of network resources, which reduces the efficiency of network resource allocation and management; at the same time, manual operation and maintenance are inevitably negligent and involve certain human risks; there are also certain technical threshold requirements for maintenance personnel; when cross-domain distributed scenarios occur, manual management and maintenance become even more stretched, which will not only generate more communication costs, but also make deployment and maintenance more inconvenient.

[0003] By introducing mainstream vendors' network management software or more professional SDN controllers for management and allocation, the device hardware can be managed or virtualized through standard SNMP / SSH / NETCONF protocols, and then managed and allocated on demand; however, it is necessary to purchase corresponding equipment for related deployment, and the existing network equipment must support the corresponding protocol and version matching; and the subsequent operation also puts forward new requirements for maintenance personnel; at the same time, in order to avoid restrictions such as vendor binding or heterogeneous isolation, enterprises often use multiple different vendors' equipment to operate in combination in the network environment, and there are certain heterogeneous scenario compatibility requirements. Such management software / equipment needs to provide compatibility support with other vendors, which will lead to certain heterogeneous compatibility, inconvenient docking and adaptation, and other derivative problems. Therefore, how to efficiently and conveniently manage and allocate the resource objects of network devices (such as IP, VLAN, RouterID, Virtual MAC, Area and other resources) with finer granularity, so as to achieve efficient, controllable and reliable management and scheduling allocation of network device resource objects in a distributed network environment, is a technical problem that technicians in this field need to solve urgently. Summary of the invention

[0004] The purpose of this application is to provide a method, system, computer-readable storage medium, edge electronic device and computer program product for processing network resource requests, which can achieve efficient and reliable management of network device resources.

[0005] In order to solve the above technical problems, the present application provides a method for processing network resource requests, which is applied to the edge host side. The specific technical solution is as follows:

[0006] Receive resource management requests;

[0007] Performing a routing search on the address information in the resource management request to determine a target edge host;

[0008] Matching the request type of the resource management request to determine the interface processing program corresponding to the request type;

[0009] Applying the interface processing program to query the used resource information and stored object count information of the target edge host;

[0010] Pre-check the used resource information and the stored object count information; if the check is consistent, call the resource processing interface corresponding to the request type to obtain the management data corresponding to the resource management request;

[0011] The resource management request is responded to according to the management data.

[0012] Optionally, before the edge host receives the resource management request, the following steps are further included:

[0013] The platform end obtains the network resource request sent by the user front end, and sends an acquisition request corresponding to the network resource request to the central end;

[0014] The central end calls the device information library to determine the edge host corresponding to the network resource request, and displays the view information of the edge host on the user front end of the platform end, so that the user can issue the resource management request managed by the edge host through the user front end;

[0015] The platform end sends the resource management request to the central end as a submission request, so that the central end sends the resource management request to the edge end host.

[0016] Optionally, when the used resource information and the stored object count information are pre-verified, if the verification is inconsistent, the method further includes:

[0017] Updating the interface processing program to obtain network device information from the device information database;

[0018] After receiving the network device information returned by the device information library, the network device information edge is stored in the library for persistent storage, and offline network devices are discarded;

[0019] Initialize the used database, generate the local configuration file of the resource management request, and concurrently obtain the network resource metadata information through nornir;

[0020] After the information acquisition query is completed, the metadata information of the network resource is formatted and the resource is labeled based on the boundary of the resource available range;

[0021] The used resource information is stored persistently in the used resource form.

[0022] Optionally, responding to the resource management request according to the management data includes:

[0023] Transmitting the management data network to the central end;

[0024] After the management data is processed by standard formatting at the center end, the processed management data is cached, and the management data is visualized on the user front end of the platform end.

[0025] Optionally, after responding to the resource management request according to the management data, the method further includes:

[0026] Determining resource tag field information carried in the management data;

[0027] Determine resource objects and associated network devices for resource allocation based on the resource tag field information;

[0028] The resource allocation algorithm is set to optimize the resource available boundaries of the resource object and the associated network device to avoid non-standard resource allocation crossing the boundary.

[0029] Optionally, labeling resources based on the boundaries of their available range includes:

[0030] Determining whether the resource object allocation matches the resource available range boundary;

[0031] If they do not match, the resource is determined to be out of bounds and the resource tag is marked as out of bounds.

[0032] If they match, it is determined that the resource is within the bounds and the resource tag is marked with the corresponding resource tag name.

[0033] Optionally, the deployment process of the edge host includes:

[0034] Configure a preset host or a virtual machine as an edge host, and set the system environment and public network access environment of the edge host; deploy a service module on the edge host;

[0035] The service module includes a resource scheduling module, an edge-network communication module, a resource planning module, a data storage module and a device control module.

[0036] The present application also provides a network resource request processing system, which is applied to an edge host end, including:

[0037] A request receiving unit, used for receiving a resource management request;

[0038] A routing search unit, used to perform routing search on the address information in the resource management request to determine a target edge host;

[0039] A type matching unit, used for matching the request type of the resource management request to determine the interface processing program corresponding to the request type;

[0040] A resource information query unit, used to query the used resource information and stored object count information of the target edge host by applying the interface processing program;

[0041] A verification unit, configured to perform a pre-verification on the used resource information and the stored object count information; if the verification is consistent, calling a resource processing interface corresponding to the request type to obtain management data corresponding to the resource management request;

[0042] A request response unit is used to respond to the resource management request according to the management data.

[0043] The present application also provides a computer-readable storage medium having a computer program stored thereon, and the computer program implements the steps of the above-mentioned method when executed by a processor.

[0044] The present application also provides an edge electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps of the method described above when calling the computer program in the memory.

[0045] The present application provides a method for processing a network resource request, comprising: an edge host receives a resource management request; performs a routing search on address information in the resource management request to determine a target edge host; matches a request type of the resource management request to determine an interface processing program corresponding to the request type; applies the interface processing program to query used resource information and stored object count information of the target edge host; performs a pre-check on the used resource information and the stored object count information; if the check is consistent, calls a resource processing interface corresponding to the request type to obtain management data corresponding to the resource management request; and responds to the resource management request according to the management data.

[0046] This application sets the host at the edge, and the central end is responsible for executing the centralized scheduling and distribution of resource management requests, so that the edge host can execute the corresponding edge resource scheduling according to the resource management request. Specifically, when executing edge resource scheduling, resource scheduling is performed through processes such as routing lookup, request type matching, and information verification of resource objects to achieve automatic resource allocation, which can improve the work efficiency in the process of network device resource management and allocation, and has a system and method for pooled management and allocation of network device resources with ease of use, compatibility, flexibility, and scalability; making network device resource management and allocation flexible, autonomous, and easy to operate, and the information visualization presentation is more centralized and clear; at the same time, it also reduces the technical threshold for network resource allocation, and the first planning and deployment is convenient for any subsequent maintenance personnel to realize the allocation and management of network resources.

[0047] The present application also provides a network resource request processing system, a computer-readable storage medium, an edge electronic device and a computer program product, which have the above-mentioned beneficial effects and are not further described here. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0049] Figure 1 A flowchart of a method for processing a network resource request provided in an embodiment of the present application;

[0050] Figure 2 A schematic diagram of the network structure framework provided in the embodiment of the present application;

[0051] Figure 3 A schematic diagram of the processing process of a network resource query request provided in an embodiment of the present application;

[0052] Figure 4 A schematic diagram of the processing process of a network resource allocation request provided in an embodiment of the present application;

[0053] Figure 5 A schematic diagram of the structure of a system for processing network resource requests provided in an embodiment of the present application. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0055] The purpose of this application is to perform differential verification of data baselines such as the number of devices at different edge nodes based on time differences, to solve the problem of incomplete resource data acquisition caused by differences in the number of device levels. This is specifically achieved through counting verification and triggering update mechanism functions. On this basis, resource management is not only the data baseline for resource visualization, but also a key factor in supporting the subsequent resource allocation function.

[0056] Please refer to Figure 1 , Figure 1 A flowchart of a method for processing a network resource request provided in an embodiment of the present application, the method comprising:

[0057] S101: receiving a resource management request;

[0058] S102: performing a routing search on the address information in the resource management request to determine a target edge host;

[0059] S103: matching the request type of the resource management request to determine an interface processing program corresponding to the request type;

[0060] S104: Apply the interface processing program to query the used resource information and stored object count information of the target edge host;

[0061] S105: Pre-check the used resource information and the stored object count information; if the check is consistent, call the resource processing interface corresponding to the request type to obtain the management data corresponding to the resource management request;

[0062] S106: Respond to the resource management request according to the management data.

[0063] The objects described in step S105 refer to all known manageable network devices of the edge node.

[0064] To better understand the application scenarios of this application, see Figure 2 , Figure 2 This is a schematic diagram of the network structure framework provided by the embodiment of the present application. The network structure can be divided into three parts: platform end, center end, and edge end.

[0065] The platform is mainly used for resource management and visualization, standardized automatic allocation of resources, and personalized planning of resource boundaries. It can be used as the user front end through the user WEB view.

[0066] The center end is mainly used for the northbound docking platform, centralized scheduling and distribution of resource requests, establishment and maintenance of edge communication connections, equipment information baseline library, resource planning definition and storage, and resource data caching.

[0067] The edge is mainly used for initial query and storage of used resource objects at the edge, automatic resource allocation for edge computing, and return of request results for edge queries.

[0068] Secondly, this application is mainly deployed and implemented based on the following seven component modules: resource scheduling module, resource caching module, device information library, network communication module, resource planning module, data storage module, and device control module.

[0069] The resource scheduling module is divided into the central-resource scheduling module and the edge-resource scheduling module. Its main functions include initial acquisition of used resource object storage, resource object identification definition, resource allocation request pre-query, resource object data formatting processing, resource object edge computing and pre-allocation, resource management query request traversal processing, resource allocation conflict detection pre-verification, etc.

[0070] The resource cache module is located at the center end and mainly provides hot resource information cache function to improve program performance and processing efficiency;

[0071] The device information database is located at the center end and is mainly used to store the baseline information of edge network devices (including but not limited to device manufacturers, device models, device roles, management IP, etc.) and device information interface query function;

[0072] The network communication module includes the center-network communication module and the edge-network communication module. Its main functions are to provide a channel for edge-center connection and data interaction, issue platform operation requests, and securely transmit resource data.

[0073] The resource planning module is located at the edge. Its main function is to provide a data baseline of the allocatable range of network resources and to customize and update the available boundaries of resource objects.

[0074] The data storage module is located at the edge. Its main function is to serve as a storage device to persistently store manageable network device information, used network device resource object information, and allocated network device resource object information on the edge side, and provide CRUD (create, query, modify, and delete) functions on demand.

[0075] The device control module is located at the edge. Its main function is to act as a queryer to query the resource object data of manageable network devices and provide multi-threaded concurrent connection network device functions.

[0076] First, the center is deployed by presetting a general Linux virtual machine on the cloud, providing a basic system environment and public network access environment, and updating the software manager content in advance; secondly, the relevant service modules are deployed.

[0077] For the resource scheduling module: a resource pooling APP developed based on the Django architecture, and newly added API interfaces and corresponding program functions for resource allocation and resource management. This is a functional module independently developed within this framework. It mainly processes platform-side requests, matches edge-side information and passes parameters, and then schedules to the corresponding edge-side computing node or traverses the matching resource information. After formatting, it finally provides the corresponding resource content information to the platform for presentation.

[0078] For the resource cache module: the data cache function is realized by adopting the Redis memory data structure storage system. First, download the latest stable version of the Redis source code package from the Redis official website through wget, install Redis compilation dependencies such as gcc and make, decompress the source code package and compile and install it, modify the redis configuration file / etc / redis / redis.conf as needed, preset the access port - the default is 6379, configure the management password, enable AOF persistence, enable protection mode, etc., use the configuration file to start the Redis service, and use it to cache hot resource data to improve the overall performance and response speed of the application;

[0079] For the device information library: through the service-oriented deployment of the relational database MySQL, the relevant network device information is stored, providing the basic network device information baseline query and data storage functions;

[0080] For the center-network communication module: According to the preset system type, use apt-get or Yum install salt-master through the package manager (YUM\APT, etc.) to install the Salt service, and start the salt-master service on the center side as a center-resource scheduling module to provide data communication services with the edge side.

[0081] Edge deployment can be done by presetting a Linux host or a virtual machine, providing a basic system environment and a public network access environment, and pre-updating the package manager content; then deploying related service modules, which can include the following:

[0082] Resource scheduling module: Developed based on Django architecture, after the development is completed, the network resource pooling APP is deployed, and the corresponding API interface and corresponding program functions for resource allocation and resource management are added. This is a function module independently developed within the framework; it mainly receives the POST request scheduled by the central end, automatically routes to the corresponding View view interface, matches the type in the request parameter, calls the corresponding type of handler to perform resource pre-query, resource pre-allocation, used resources, allocated resources, resource initialization update and other handlers, and returns the corresponding resource information to the central end for processing after the processing is completed; secondly, for resource management and allocation requests, the project program compares the device base and the storage base by judging the pre-check library. If there is no match, the resource initialization update interface is automatically called to complete the trigger update action, otherwise the query operation is performed; at the same time, the integrity and consistency of resource data are ensured through periodic scheduled update tasks; for resource allocation, the edge database objects are checked and the uniqueness of resources is determined by traversing level by level. After the verification is passed, the fping detection is used for secondary verification to quickly detect and ensure the unique availability of resource objects to avoid resource conflicts; for concurrent resource allocation requests, the write-time locking mechanism is used to avoid problems such as resource duplication and resource allocation duplication.

[0083] Edge-network communication module: According to the preset Linux system type, use apt-get or Yum install salt-master through the package manager (YUM\APT, etc.), edit the / etc / salt / minion file, set the master address, start and enable the Salt-minion service on the edge, realize network communication and request interaction with the center, and provide data communication services with the edge;

[0084] Resource planning module: By presetting the default resource objects (IP\VLAN\VirtualMac\RouterID\Area) and the available range of resource objects, it provides an available range boundary baseline for edge computing such as edge pre-allocation and edge pre-query to achieve standardized resource output; it can also adjust the default resource range boundary to provide personalized resource information output.

[0085] Data storage module: Execute mysql -uroot -pPassword -e "CREATE DATABASE netPool DEFAULT CHARACTER SET utf8mb4;" on the edge Linux host / virtual machine. Then, use Django's database migration mechanism manage.py migrate to initialize the database and automatically create the relevant data table structure. These tables are used to store manageable network device information, used resources, allocated resources and other data, and realize the data persistence storage function in the edge environment, providing basic storage support for subsequent data operations and queries;

[0086] The device control module connects to manageable network devices based on the standard SSH protocol, circumvents the relevant limitations of specific protocol compatibility and simplifies the connection with network devices and related resource object information query operations. This module is implemented through the Nornir framework in the project file and integrates the Netmiko library, and provides multi-threaded concurrent acquisition of device resource object information capabilities, improves the concurrent processing efficiency in scenarios with a large number of devices, and improves the program flow response performance, thereby improving the work efficiency of resource management and allocation processes; finally, the deployed host can be made into a system image / containerized template based on mainstream resource management tools (Kubesphere / DockerSwarm, etc.), and distributed deployment and plug-and-play integration can be performed in scenarios that are expanded to or involve distributed edge nodes; this framework supports centralized management scheduling and presentation in single-user and multi-user distributed scenarios, and only requires edge image cloning to be deployed to other distributed edge nodes.

[0087] When the edge host receives the resource management request sent by the center, it first performs a routing lookup for the resource management request to determine the target edge host managed by the resource management request, and then performs resource scheduling processing. When performing a routing lookup, a routing lookup can be performed based on the URL address information in the resource management request. Specifically, the URL can be parsed: First, the URL needs to be parsed to extract its components, including the protocol (such as HTTP or HTTPS), domain name, port (if specified), path, query parameters, and anchor. According to the protocol part in the URL address information, determine which protocol to use for communication. Use DNS (Domain Name System) to resolve the domain name into an IP address so that you know which target edge host the data should be sent to. The path part of the URL will apply the routing table to match the routing rules.

[0088] After that, it is necessary to further match the request type of the resource management request to determine the corresponding interface handler. The request type mainly includes different request requirements for resources, such as resource query type and resource allocation type. The resource query type can be further divided into used type and allocated type. The resource allocation type includes but is not limited to equipment expansion, address addition and other types. In specific processing, it is necessary to call the interface handler that matches the request type. The interface handler is used to perform specific resource management operations.

[0089] The used resource information and the count information of the stored objects are used to perform pre-validation. Pre-validation refers to a series of checks and verifications performed before processing a request. If the pre-validation fails, the resource management request may have an abnormal problem with the available resource boundary range. The available resource boundary range refers to the limiting conditions and scope under which resources can be accessed and used, and refers to the definition of network resources for applicable objects. For example, the IP address range has a corresponding available resource boundary range, and it is not possible to allocate corresponding IP address resources to each device indefinitely. That is, the available resource boundary range is determined for the resource management object of the resource management request. If it does not exceed the available resource boundary range, the resource processing interface corresponding to the request type can be called to obtain the management data corresponding to the resource management request. Otherwise, it is regarded as a resource out of bounds, and the response to the resource management request can be refused.

[0090] Specifically, when the used resource information and the stored object count information are pre-verified, if the verification is inconsistent, the following steps may be included:

[0091] The first step is to update the interface processing program and obtain network device information from the device information library;

[0092] Step 2: After receiving the network device information returned by the device information database, the network device information edge is stored in the database for persistent storage, and offline network devices are discarded;

[0093] Step 3: Initialize the used database, generate a local configuration file for the resource management request, and concurrently obtain network resource metadata information through nornir;

[0094] Step 4: After completing the information acquisition query, the metadata information of the network resource is formatted and the resource is labeled based on the boundary of the resource available range;

[0095] Step 5: Store the used resource information persistently in the used resource form.

[0096] Nornir's concurrency mechanism means that it can execute tasks on multiple devices at the same time, which can significantly improve the efficiency when processing a large number of devices.

[0097] Verification of used resource information can effectively prevent application conflicts of network resources, while verification of stored object count information can ensure data increment synchronization between network devices. When pre-verifying stored object count information, what can be compared is whether there are differences in the statistical data of the last (historical) number of devices that need to be stored, the last (historical) actual number of devices that are stored, and the number of devices that need to be stored this time. If there is no difference, the stored resource information is returned. If there is a difference, the stored resource information is reset to empty, and the resource information is automatically re-acquired based on the number of devices that need to be stored this time, and iteratively updated and stored in the allocated resources to ensure the accuracy and reliability of the used resources.

[0098] By verifying the number of devices last entered into the database and the number of network devices currently executing resource management requests, resource management anomalies caused by device offline or newly added network devices can be avoided.

[0099] If the verification is consistent, the resource management interface of the corresponding type can be directly called to obtain the management data corresponding to the resource management request, and finally the resource management request can be responded to according to the management data.

[0100] In the embodiment of the present application, the host is set at the edge end, and the central end is responsible for executing the centralized scheduling and issuing of resource management requests, so that the edge end host can execute the corresponding edge resource scheduling according to the resource management request. Specifically, when executing edge resource scheduling, resource scheduling is performed through processes such as route search, request type matching, and information verification of resource objects to achieve automatic resource allocation, which can improve the work efficiency in the process of network device resource management and allocation, and has a system and method for network device resource pooling management and allocation with ease of use, compatibility, flexibility, and scalability; network device resource management and allocation are flexible, autonomous, and easy to operate, and information visualization is more centralized and clear; at the same time, it also reduces the technical threshold of network resource management, and its planning and deployment facilitates any subsequent maintenance personnel to implement the allocation and management of network resources.

[0101] See also Figure 3 , Figure 3 A schematic diagram of the processing process of a network resource query request provided in an embodiment of the present application includes the processing interaction process between a user device on the platform side, a platform side, a central side, an edge side, a data storage module, a device information library and a network device.

[0102] Taking the resource query request as an example, in step 0, the user can enter the preset platform user view. After selecting "Computer Room View-Computer Room Name" in step 0.1, the platform triggers the edge host name query process in step 0.2 (used for point-to-point transmission to the edge of the specified computer room when issuing resource management requests later), and automatically sends a GET request to the center. In step 0.3, after the center hears the corresponding request, it calls the internal interface and initiates a query request to the device information library based on the computer room name. Step 0.4 is for the device information library to process the resource query request and return the result to the center. It should be noted that if the edge host name is obtained, the next step 0.4 will be entered; otherwise, the edge host information query failure will be output.

[0103] At this time, in step 0.5, the device information library first feeds back the edge host included in the query results to the platform side, and then executes step 0.6 to return the edge host name to the platform side. In step 0.6, the platform side presents the host name, switches to the operation view, and then starts step 1 resource management query.

[0104] In step 1.1, the user selects 'Resource Management' and can choose the type of 'Used' or 'Allocated'. In step 1.2, the user can trigger the query process by clicking the 'Query' button. In step 1.3, the platform sends a resource management query POST request, and the query type is: used type or allocated type.

[0105] In step 1.4 and step 1.5, after the center detects the port request, it matches the corresponding interface according to the request type, calls the network communication module to send the POST interface request to the edge host under the corresponding computer room name for processing.

[0106] Step 1.6: After the edge network communication module receives the command sent by the central Master, it automatically executes it, performs routing lookup on the URL information in the command, and forwards it to the edge resource scheduling module for processing; the corresponding view interface automatically matches whether the request type exists, and if so, it proceeds to step 1.7; otherwise, an error is reported, indicating an internal method error.

[0107] In step 1.7, the edge resource scheduling module matches the request type and calls the corresponding interface handler; first, it queries the count information of the objects that have been used and the device information that has been stored in the warehouse, and performs a pre-verification on the two query counts. If the verification is not empty and the counts are consistent, the verification is considered to have passed, otherwise it is considered to have failed.

[0108] In step 1.8, the data storage module processes the query request and returns the result. Specifically, the following process can be performed according to the query result:

[0109] Step 1.8.1.1: If the verification fails / is inconsistent, execute step 1.8.1.2 to automatically call the resource initialization update interface handler, and then execute step 1.8.1.2 to obtain the network device information from the device information library; after the device information library returns the network device information under the computer room, step 1.8.1.3 requires the device information edge to be stored in the warehouse for persistence. If the storage fails, execute step 1.8.1.4 and throw an exception. If the storage is successful, execute step 1.8.1.5 to return the storage result.

[0110] At the same time, execute step 1.8.1.6 to filter out the network devices in the offline state, initialize the used database, and then generate the local configuration file for this query operation, such as the local hosts.yaml file. In step 1.8.1.7, the edge device control module can be called to obtain the metadata information of the network resources in the computer room through nornir multi-threaded concurrent access, and after completing the information acquisition query, the network resource information of the computer room is returned in step 1.8.1.8.

[0111] The resource scheduling module formats the metadata information and determines whether the resource object allocation matches the currently defined resource available boundary based on the resource available range boundary. If it is out of bounds, the resource tag is marked as 'resource out of bounds'. Otherwise, step 1.8.1.9 is marked as the corresponding resource tag name (e.g. business interconnection, management interconnection, etc.). After completing the resource tagging and resource data formatting, the used resource information is stored in the used resource form through the data storage module. At this time, if the storage is successful, execute step 1.8.1.11 to return the storage result. If the storage fails, execute step 1.8.1.10 and throw an exception.

[0112] If the verification passes, execute step 1.8.1, that is, the query result is not empty and consistent, and you can further execute step 1.9 to call the resource query interface of the corresponding type (used, allocated), and send a request to obtain the full data of the corresponding type (used, allocated) form; in step 1.10, the data storage module performs traversal query and returns the query data.

[0113] After that, execute step 1.11. The edge resource scheduling module returns the returned query data to the central end through the network communication module; the central end formats the returned data and caches the resource data to the resource cache module; step 1.12 needs to be returned to the corresponding resource management view of the platform to visualize the resources.

[0114] The platform can query and export the queried data in the resource management interface for further processing; and can filter and distinguish resource objects with non-standard resource allocation and associated network devices based on the resource tag field information carried in the returned data. Users can rectify the resource object as needed, or reasonably optimize the available resource boundaries to avoid such non-standard resource allocation out-of-bounds problems.

[0115] See also Figure 4 , Figure 4 This is a schematic diagram of the processing process of the resource allocation request provided in the embodiment of the present application. The resource allocation request is used as an exemplary resource management request to illustrate the processing method of the network resource request provided in the present application. The process may include the following steps:

[0116] When implementing resource allocation requests, we mainly classify and label resource objects based on the finiteness of resources, and give measurable boundaries of corresponding resources to form the boundaries of the allocatable resource pool. When allocating resources, we perform allocation calculations and conflict checking mechanisms based on the available resource value range of label mapping to complete the resource allocation request implementation.

[0117] The conflict check mechanism refers to the use of the information in resource management. It compares the used resources and the information in the allocated warehouse through polling, and performs resource availability detection in a loop to output the available resources to avoid resource allocation conflicts and duplicate allocations.

[0118] The object is the edge node network equipment, including but not limited to application scenarios such as resource expansion, resource addition, resource allocation, and resource update.

[0119] In addition, in order to solve the information difference at the device resource level, a flexible resource recovery mechanism is used. The resource recovery mechanism refers to the allocated data, the corresponding allocation time is recorded in the warehouse, and the corresponding resources are automatically recovered after the default recovery time is reached, thus solving the problem of resources not being used for a long time after allocation and the resource occupation not being released.

[0120] Through the conflict verification mechanism and resource recovery mechanism, self-service resource allocation planning can be achieved, improving the efficiency of equipment resource planning and allocation.

[0121] The specific steps include:

[0122] Step 1: The user enters the preset platform user view and selects "Computer Room View-Computer Room Name". The platform triggers the edge host name query process (used for point-to-point transmission to the edge of the specified computer room when issuing resource management requests later) and automatically sends a GET request to the center. After the center hears the corresponding request, it calls the internal interface and initiates a query request to the device information library based on the computer room name. After obtaining the edge host name, it proceeds to the next step. Otherwise, an error is reported and the edge host information query fails.

[0123] Step 2: The platform returns to the platform based on the query results. The platform presents the host name and switches to the operation view before entering step 3.

[0124] Step 3. Start the resource allocation query. The user selects 'Resource Allocation' and can choose the type of 'Device Expansion' or 'Address Allocation'. After selecting the type, select the corresponding device purpose. You can choose 'Core Switch', 'Node Switch' or 'Computing Power Switch'. Then click the 'Query' button to trigger the resource allocation pre-query process (the query here is not stored in the database to avoid repeated queries caused by erroneous operations, thereby occupying allocable network resources). The platform sends a resource allocation pre-query POST request. The pre-query type is: device expansion or address addition. Go to step 4.

[0125] Step 4: After the center detects the port request, it matches the corresponding interface according to the request type, calls the network communication module to send the POST interface request to the edge host under the corresponding computer room name for processing; proceed to step 5.

[0126] Step 5: The edge network communication module receives the command sent by the central Master, executes it automatically, performs routing lookup on the URL information in the command, and forwards it to the edge resource scheduling module for processing; the resource scheduling module calls the corresponding view interface to determine whether there is a corresponding method for the request type. If it exists, it goes to step 6; otherwise, an error is reported, indicating an internal method error.

[0127] Step 6. The edge resource scheduling module matches the request type and calls the corresponding interface handler. First, the count information of the objects that have been used and the device information that has been stored in the database is queried, and the two query counts are pre-checked. If the verification is not empty and the counts are consistent, it will enter step 8, otherwise it will enter step 7.

[0128] Step 7: If the verification fails or is inconsistent, the resource initialization update interface handler is automatically called; first, the device information library is requested to obtain the network device information. After the device information library performs a search query, the network device information in the computer room is returned, and the network devices with the status field of offline / destory are filtered out. Then, the network device information is called to the edge data storage module for storage operation to complete the persistent storage of resource data. At the same time, the network device information is formatted and the local hosts.yaml file of the network device information is automatically initialized. At this time, the update of the network device information resource is completed; and the used database data is automatically initialized, and the edge device control module is called. Based on the hosts.yaml information, the used resource metadata information of the network devices in the computer room is concurrently queried through nornir; After completing the information acquisition, the resource scheduling module formats the metadata information and obtains the resource available range boundary of the resource planning module to determine whether the resource object allocation complies with the currently defined resource available boundary range. If not, the resource object label is marked as 'resource out of bounds'. Otherwise, the corresponding resource label name that complies with the definition is used (for example: business interconnection, management interconnection, etc.); after completing the resource marking and resource data formatting, the used resource information is stored in the used resource form through the data storage module. At this point, the triggered update of the used resource data and network equipment information data is completed (scheduled update function: based on the cron scheduled task edge local call resource initialization update interface to ensure that the baseline data is dynamically updated when the resource allocation performs edge query or allocation calculation); then proceed to step eight.

[0129] Step 8: Call the resource allocation interface of the corresponding type (equipment expansion, address addition), obtain the available boundary data of the corresponding resource object through the resource planning module based on the resource object ID parameter carried in the resource allocation request; then proceed to step 9.

[0130] Step 9. Enter the corresponding interface processing program (equipment expansion, address addition), loop the resource object allocation process based on the available edge data information of the resource object, generate resource object data, and then traverse and query through the data storage module based on the resource object data. If the query result is None or False, the resource is marked as available. Otherwise, a new data is generated to continue the above query process until the result True is returned or an exception prompt is thrown; then determine whether it is a detectable resource object (such as IP / RouterID, etc.), if so, perform conflict check, first traverse and search through the hierarchical levels: based on the resource object information as the filter item, query whether the key information of the resource exists in the corresponding form fields that have been used and allocated; if the query result is False, enter the next level of verification, otherwise check other available resource objects; finally enter the connectivity check: if the detection connectivity is True, other available resource objects will be checked, otherwise the corresponding resource object data will be returned; after the above cycle completes the generation and verification of all requested resource object data, enter step 10.

[0131] Step 10: The resource scheduling module at the edge returns the query data to the central end through the network communication module; the central end formats the returned data and caches the resource data to the resource cache module; and returns it to the corresponding resource management view at the platform end for visual presentation of the resources; then proceeds to step 11.

[0132] Step 11. After the platform presents the corresponding resource object data according to the selected resource allocation and equipment usage request, the user needs to click "Confirm Allocation" to complete the resource pre-allocation operation of this resource allocation request by sending an interface callback to the resource allocation POST request on the platform;

[0133] The specific process flow repeats 'Step 4' to 'Step 9', and then calls the data storage module for the generated resource object data to complete the edge persistent storage of the data to the allocated form. After the storage is completed, the storage result is returned to the central end; if the storage is successful, it goes to step 12, otherwise an error is reported. If the resource storage fails, an alarm message can be generated to notify the administrator.

[0134] Step 12: After the center receives the successful request for resource storage, it returns the result to the platform for prompting; then the platform can query and export the queried data in the resource management interface, and can use and process it as needed later.

[0135] In addition, the resource allocation algorithm can be used to optimize the resource available boundaries of the resource object and the associated network device to avoid non-standard resource allocation crossing the boundary. There is no limitation on which resource allocation algorithm to use. The heuristic algorithm based on block coordinate descent can be used to decouple the resource allocation problem into multiple sub-problems (such as UAV position optimization, bandwidth allocation, and user-edge server association decision). The particle swarm optimization algorithm, differential evolution algorithm, exhaustive algorithm and other algorithms can be used to obtain the optimal solution of the sub-problem, and finally the approximate optimal solution of the resource allocation problem is obtained by iterating between sub-problems.

[0136] It can be seen that when processing different network resource requests, the request types of resource management requests are different, and the interface processing procedures applied are also different. At the same time, there are differences in the resource processing interface processing methods for different types of network resource request processing. For resource query requests, the resource processing interface applied is the resource query interface, which sends a request to obtain the full amount of data of the corresponding type (used, allocated) form to the data storage module so that the data storage module can traverse the query and return the query data, and then respond to the resource query request. For resource allocation requests, the resource processing interface applied is the resource allocation interface, which requests the allocated resource object through the resource planning module based on the resource object ID parameter carried in the resource allocation request. At the same time, due to the different object data managed, the verification methods executed are also different.

[0137] The embodiments of the present application can improve the work efficiency in the process of network device resource management and allocation, and have a system and method for network device resource pooling management and allocation that is easy to use, compatible, flexible, and extensible; it makes network device resource management and allocation flexible, autonomous, and easy to operate, and the information visualization presentation is more centralized and clear; it also lowers the technical threshold for network resource allocation, and the first planning and deployment can be done by any subsequent maintenance personnel. Based on this application, standardized allocation and management of network resource objects can be achieved. At the same time, this application also provides a conflict verification mechanism method to reduce resource conflicts that exist in artificial allocation (when the number of existing network devices is large, the allocated global network resources must be globally unique, otherwise it will affect the service of a single device at the least, and even affect the service of the entire network environment at the worst).

[0138] See also Figure 5 , Figure 5 A structural schematic diagram of a network resource request processing system provided in an embodiment of the present application is provided below. The network resource request processing system provided in an embodiment of the present application is introduced below. The network resource request processing system described below and the network resource request processing method described above can be referenced to each other.

[0139] The present application also provides a network resource request processing system, which is applied to an edge host end, including:

[0140] A request receiving unit, used for receiving a resource management request;

[0141] A routing search unit, used to perform routing search on the address information in the resource management request to determine a target edge host;

[0142] A type matching unit, used for matching the request type of the resource management request to determine the interface processing program corresponding to the request type;

[0143] A resource information query unit, used to query the used resource information and stored object count information of the target edge host by applying the interface processing program;

[0144] A verification unit, configured to perform a pre-verification on the used resource information and the stored object count information; if the verification is consistent, calling a resource processing interface corresponding to the request type to obtain management data corresponding to the resource management request;

[0145] A request response unit is used to respond to the resource management request according to the management data.

[0146] Based on the above embodiment, as a preferred embodiment, the processing system further includes:

[0147] A request processing unit, applied to the platform end, is used to obtain the network resource request issued by the user front end, and send the acquisition request corresponding to the network resource request to the central end; and is used to send the resource management request to the central end as a submission request, so that the central end sends the resource management request to the edge end host;

[0148] The request calling unit is applied to the central end and is used to call the device information library to determine the edge host corresponding to the network resource request, and display the view information of the edge host on the user front end of the platform end so that the user can send the resource management request managed by the edge host through the user front end.

[0149] Based on the above embodiment, as a preferred embodiment, the verification unit is further used to perform the following steps when the verification is inconsistent:

[0150] Updating the interface processing program to obtain network device information from the device information database;

[0151] After receiving the network device information returned by the device information library, the network device information edge is stored in the library for persistent storage, and offline network devices are discarded;

[0152] Initialize the used database, generate the local configuration file of the resource management request, and concurrently obtain the network resource metadata information through nornir;

[0153] After the information acquisition query is completed, the metadata information of the network resource is formatted and the resource is labeled based on the boundary of the resource available range;

[0154] The used resource information is stored persistently in the used resource form.

[0155] Based on the above embodiment, as a preferred embodiment, the system for processing network resource requests may further include:

[0156] A resource boundary optimization unit is used to determine the resource tag field information carried in the management data; determine the resource objects and associated network devices with non-standard resource allocation based on the resource tag field information; and use a set resource allocation algorithm to optimize the resource available boundaries of the resource objects and the associated network devices to avoid non-standard resource allocation crossing the boundary.

[0157] The present application also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed, the steps provided in the above embodiment can be implemented. The storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.

[0158] The present application also provides an edge electronic device, which may include a memory and a processor, wherein a computer program is stored in the memory, and when the processor calls the computer program in the memory, the steps provided in the above embodiment may be implemented. Of course, the edge electronic device may also include various network interfaces, power supplies and other components.

[0159] The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other. For the system provided in the embodiment, since it corresponds to the method provided in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0160] Specific examples are used herein to illustrate the principles and implementation methods of the present application, and the description of the above embodiments is only used to help understand the method and core ideas of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the present application.

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

Claims

1. A method for processing a network resource request, characterized in that: Applied to edge host side, including: Receive resource management requests; Performing a routing search on the address information in the resource management request to determine a target edge host; Matching the request type of the resource management request to determine the interface processing program corresponding to the request type; Applying the interface processing program to query the used resource information and stored object count information of the target edge host; Pre-check the used resource information and the stored object count information; if the check is consistent, call the resource processing interface corresponding to the request type to obtain the management data corresponding to the resource management request; The resource management request is responded to according to the management data.

2. The processing method according to claim 1, characterized in that: Before the edge host receives the resource management request, it also includes: The platform end obtains the network resource request sent by the user front end, and sends an acquisition request corresponding to the network resource request to the central end; The central end calls the device information library to determine the edge host corresponding to the network resource request, and displays the view information of the edge host on the user front end of the platform end, so that the user can issue the resource management request managed by the edge host through the user front end; The platform end sends the resource management request to the central end as a submission request, so that the central end sends the resource management request to the edge end host.

3. The processing method according to claim 2, characterized in that: When the used resource information and the stored object count information are pre-verified, if the verification is inconsistent, the method further includes: Updating the interface processing program to obtain network device information from the device information database; After receiving the network device information returned by the device information library, the network device information edge is stored in the library for persistent storage, and offline network devices are discarded; Initialize the used database, generate the local configuration file of the resource management request, and concurrently obtain the network resource metadata information through nornir; After the information acquisition query is completed, the metadata information of the network resource is formatted and the resource is labeled based on the boundary of the resource available range; The used resource information is stored persistently in the used resource form.

4. The processing method according to claim 2, characterized in that: Responding to the resource management request according to the management data includes: Transmitting the management data network to the central end; After the management data is processed by standard formatting at the center end, the processed management data is cached, and the management data is visualized on the user front end of the platform end.

5. The processing method according to claim 1, characterized in that: If the resource management request is a resource allocation request, after responding to the resource management request according to the management data, the method further includes: Determining resource tag field information carried in the management data; Determine resource objects and associated network devices for resource allocation based on the resource tag field information; The resource allocation algorithm is set to optimize the resource available boundaries of the resource object and the associated network device to avoid non-standard resource allocation crossing the boundary.

6. The processing method according to claim 3, characterized in that: Tagging resources based on the boundaries of their available range includes: Determining whether the resource object allocation matches the resource available range boundary; If they do not match, the resource is determined to be out of bounds and the resource tag is marked as out of bounds. If they match, it is determined that the resource is within the bounds and the resource tag is marked with the corresponding resource tag name.

7. The processing method according to claim 1, characterized in that: The deployment process of the edge host includes: Configure a preset host or a virtual machine as an edge host, and set the system environment and public network access environment of the edge host; deploy a service module on the edge host; The service module includes a resource scheduling module, an edge-network communication module, a resource planning module, a data storage module and a device control module.

8. A system for processing network resource requests, characterized in that: Applied to edge host side, including: A request receiving unit, used for receiving a resource management request; A routing search unit, used to perform routing search on the address information in the resource management request to determine a target edge host; A type matching unit, used for matching the request type of the resource management request to determine the interface processing program corresponding to the request type; A resource information query unit, used to query the used resource information and stored object count information of the target edge host by applying the interface processing program; A verification unit, configured to perform a pre-verification on the used resource information and the stored object count information; if the verification is consistent, calling a resource processing interface corresponding to the request type to obtain management data corresponding to the resource management request; A request response unit is used to respond to the resource management request according to the management data.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

10. An edge electronic device, characterized in that: The method comprises a memory and a processor, wherein a computer program is stored in the memory, and when the processor calls the computer program in the memory, the steps of the method according to any one of claims 1 to 7 are implemented.

Images