Network resource calling method, apparatus, device, medium and computer program product

By layering and encapsulating network resources, various API calling strategies are formed, which solves the problems of low efficiency and low accuracy in fulfilling business requirements in existing technologies, and achieves efficient and accurate processing of network service business requirements.

CN119011506BActive Publication Date: 2026-01-13INSPUR TIANYUAN COMM INFORMATION SYST CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202410672811.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-05-28
Publication Date
2026-01-13
Estimated Expiration
2044-05-28

AI Technical Summary

Technical Problem

The low efficiency and accuracy of implementing business requirements in existing technologies are mainly due to the time-consuming, labor-intensive, and error-prone nature of manually parsing and compiling code.

Method used

By layering network resources in the network resource capability library, determining the characteristics of different resources, and encapsulating each layer of resources to obtain callable API interfaces, the APIs of different layers are finally combined to form API calling strategies for various network services.

Benefits of technology

It improves the efficiency and accuracy of fulfilling network service business requirements, and adapts to various network service needs through resource encapsulation and API combination.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119011506B_ABST
    Figure CN119011506B_ABST
Patent Text Reader

Abstract

The application provides a network resource calling method, device, equipment, medium and computer program product. The method comprises the following steps: layering network resources in a network resource capability library, and determining that network resources with different resource characteristics belong to different layers; encapsulating network resources in each layer to obtain callable application programming interfaces (APIs) of network resources with each characteristic; and combining the callable APIs of network resources in different layers to obtain API calling strategies of multiple network services. The application obtains the callable APIs through resource encapsulation, and obtains the network resource calling strategies suitable for various network services through various combinations of the callable APIs, thereby improving the implementation efficiency and accuracy of network service business requirements.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of network communication technology, and in particular to a method, apparatus, device, medium, and computer program product for accessing network resources. Background Technology

[0002] In today's digital economy, as businesses grow, diverse business needs present greater challenges to product services. Current technical solutions often involve manually analyzing these needs to determine the required functionalities and logic, followed by manual compilation of executable code. This process, which also requires maintenance, is time-consuming, labor-intensive, and prone to errors, reducing the efficiency and accuracy of fulfilling business requirements. Summary of the Invention

[0003] This invention provides a method, apparatus, device, medium, and computer program product for retrieving network resources, which addresses the shortcomings of low efficiency and low accuracy in fulfilling business requirements in the prior art, thereby improving the efficiency and accuracy of fulfilling business requirements.

[0004] This invention provides a method for retrieving network resources, comprising:

[0005] The network resources in the network resource capability library are layered to determine which layers network resources with different characteristics belong to; each layer of network resources is encapsulated to obtain a callable application programming interface (API) for each type of network resource; the callable APIs of network resources from different layers are combined to obtain API calling strategies for various network services.

[0006] According to a network resource retrieval method provided by the present invention, the layering includes a first layer, a second layer, and a third layer; the layering of network resources in the network resource capability library, and the determination that network resources with different resource characteristics belong to different layers, includes:

[0007] Network resources with different characteristics include network physical resources, network element resources, and system function resources.

[0008] The network physical resources are determined to belong to the first layer, the network element resources to belong to the second layer, and the system function resources to belong to the third layer.

[0009] According to a network resource invocation method provided by the present invention, the encapsulation of network resources at each layer to obtain callable application programming interfaces (APIs) for network resources with each characteristic includes:

[0010] The network physical resources of the first layer are encapsulated to obtain the callable APIs of the network physical resources; the network physical resources include gateways and user plane functions (UPFs).

[0011] The network element resources of the second layer are encapsulated and packaged to obtain the callable APIs of the network element resources; the network element resources include wireless network elements, access network elements and transmission network elements;

[0012] The system function resources of the third layer are encapsulated to obtain the callable APIs of the system function resources; the system function resources include resource monitoring functions, fault location functions, and quality analysis functions.

[0013] According to a network resource invocation method provided by the present invention, the combination of callable APIs of network resources at different layers to obtain API invocation strategies for various network services includes:

[0014] Identify the first resource in the first layer, the second resource in the second layer, and the third resource in the third layer; combine the first API of the first resource, the first API of the second resource, and the third API of the third resource to obtain the API calling strategy of the first network service; the calling order of the API calling strategy of the first network service is the third API, the second API, and the first API in sequence.

[0015] According to a network resource invocation method provided by the present invention, the method involves combining callable APIs of network resources at different layers to obtain API invocation strategies for various network services, and then includes:

[0016] Based on the received service requests, determine the network services to be processed;

[0017] Based on the network service to be processed, determine the packaging product to be used and the API call path corresponding to the packaging product;

[0018] Call each API on the API call path to obtain the service result of the network service to be processed.

[0019] According to a network resource invocation method provided by the present invention, the step of determining the network service to be processed based on the received service request, and then including:

[0020] Locate the packaged product corresponding to the network service to be processed;

[0021] If there is no corresponding encapsulated product for the network service to be processed, determine the target resource corresponding to the network service to be processed.

[0022] Add the target resource to the network resource capability library.

[0023] The present invention also provides a network resource retrieval device, comprising the following modules:

[0024] The network resource layering module is used to layer network resources in the network resource capability library and determine which layers network resources with different characteristics belong to.

[0025] The network resource encapsulation module is used to encapsulate network resources at each layer to obtain callable application programming interfaces (APIs) for each type of network resource.

[0026] The network resource invocation module is used to combine callable APIs of network resources at different layers to obtain API invocation strategies for various network services.

[0027] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement any of the network resource access methods described above.

[0028] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the network resource access method as described above.

[0029] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements any of the network resource invocation methods described above.

[0030] The network resource invocation method, apparatus, device, medium, and computer program product provided by this invention layer the network resources in a constructed network resource capability library, based on the different resource characteristics of different types of network resources. After layering the network resources, each layer of network resources is encapsulated to obtain callable API interfaces for each type of network resource. Finally, the callable APIs of network resources from different layers are combined to obtain API invocation strategies corresponding to various network services. This invention improves the efficiency and accuracy of implementing network service business requirements by encapsulating resources to obtain callable APIs and by combining these callable APIs in various ways to obtain network resource invocation strategies suitable for various network services. Attached Figure Description

[0031] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0032] Figure 1 This is one of the flowcharts illustrating the network resource retrieval method provided by the present invention.

[0033] Figure 2 This is the second flowchart of the network resource invocation method provided by the present invention.

[0034] Figure 3 This is a schematic diagram of the network resource retrieval device provided by the present invention.

[0035] Figure 4 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0036] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0037] Figure 1 This is one of the flowcharts illustrating the network resource retrieval method provided by the present invention, such as... Figure 1 As shown, the method includes the following steps 100, 200 and 300.

[0038] Step 100: Divide the network resources in the network resource capability library into layers to determine which layers network resources with different characteristics belong to.

[0039] Specifically, according to the description in the background section of this invention, the technical problem solved by this invention is how to quickly and accurately implement different business requirements. Therefore, based on this problem, this invention proposes a network resource capability library for storing different types of network resources, including directly callable network resources, such as storage resources represented by storage addresses, wireless connection resources represented by physical addresses, and wired transmission resources represented by ports and transmission protocols. The network resource capability library may also include models and algorithms, such as algorithms for task scheduling, models for fault detection, and algorithms for quality analysis.

[0040] After obtaining a network resource capability library that stores various types of network resources, the stored network resources are layered. The layering can be based on different resource characteristics, such as network physical resources, network element resources, and system function resources. Resources with different characteristics belong to different layers.

[0041] Step 200: Encapsulate the network resources of each layer to obtain the callable application programming interface (API) for each type of network resource.

[0042] Specifically, after layering the network resources in the network resource capability library, each layer's network resources are encapsulated to obtain a callable Application Programming Interface (API) for each type of network resource at each layer. Calling the API allows users to obtain and use the corresponding network resource.

[0043] Step 300: Combine the callable APIs of network resources at different layers to obtain API calling strategies for various network services.

[0044] Specifically, the APIs corresponding to different network resources at each layer are combined to obtain an API invocation strategy for each network service. The API invocation strategy of this invention refers to the rules for invoking the APIs corresponding to each layer of network resources. These rules can be the order in which the APIs are invoked, or an algorithm for invoking the APIs at each layer. Different types of network services can be implemented based on this API invocation strategy.

[0045] This embodiment stratifies the network resources in the constructed network resource capability library into layers, based on the different resource characteristics of different types of network resources. After layering the network resources, each layer is encapsulated to obtain callable API interfaces for each type of network resource. Finally, the callable APIs of different layers are combined to obtain API calling strategies corresponding to various network services. This invention improves the efficiency and accuracy of implementing network service business requirements by encapsulating resources to obtain callable APIs and combining these APIs in various ways to obtain network resource calling strategies suitable for various network services.

[0046] In one embodiment, the network resource invocation method provided in this application may further include the following steps 110 and 120.

[0047] Step 110: Determine the network resources with different resource characteristics, including network physical resources, network element resources, and system function resources.

[0048] Step 120: Determine that the network physical resources belong to the first layer, the network element resources belong to the second layer, and the system function resources belong to the third layer.

[0049] Specifically, the network resources in the network resource capability library can be divided into three layers: the first layer, the second layer, and the third layer. Then, the network resources in the network resource capability library are further divided into layers based on their resource characteristics, with network resources of different characteristics belonging to different layers.

[0050] Different resource characteristics include network physical resource characteristics, network element resource characteristics, and system function resource characteristics. For example, network resources with network physical resource characteristics are classified as Layer 1, network resources with network element resource characteristics are classified as Layer 2, and network resources with system function resource characteristics are classified as Layer 3. This hierarchical structure is because network physical resources are fundamental network resources, and network physical resources, network element resources, and system function resources have a certain hierarchy. For example, after calling system function resources, network element resources can be called, and then network physical resources can be called.

[0051] This embodiment determines the architectural foundation for building API call strategies by layering network resources in the network resource capability library.

[0052] Figure 2 This is the second flowchart of the network resource invocation method provided by the present invention, as shown below. Figure 2 As shown, the method may further include the following steps 210, 220 and 230.

[0053] Step 210: Encapsulate the network physical resources of the first layer to obtain the callable APIs of the network physical resources; the network physical resources include gateways and user plane functions (UPFs).

[0054] Step 220: Deposit and encapsulate the network element resources of the second layer to obtain the callable APIs of the network element resources; the network element resources include wireless network elements, access network elements and transmission network elements.

[0055] Step 230: Encapsulate the system function resources of the third layer to obtain the callable APIs of the system function resources; the system function resources include resource monitoring functions, fault location functions, and quality analysis functions.

[0056] Specifically, after layering network resources with different characteristics to obtain multi-layered network resources, the first-layer network physical resources are encapsulated to obtain callable APIs for network physical resources; the second-layer network element resources are encapsulated to obtain callable APIs for network element resources; and the third-layer system function resources are encapsulated to obtain callable APIs for system function resources. By obtaining the APIs corresponding to each layer of network resources, they can be combined to solve various network services.

[0057] This embodiment encapsulates the network resources of each layer to obtain the APIs corresponding to the network resources of each layer, laying the architectural foundation for API calling strategies for various network services.

[0058] In one embodiment, the network resource invocation method provided in this application may further include the following steps 310 and 320.

[0059] Step 310: Determine the first resource in the first layer, the second resource in the second layer, and the third resource in the third layer.

[0060] Step 320: Combine the first API of the first resource, the first API of the second resource, and the third API of the third resource to obtain the API calling strategy of the first network service; the calling order of the API calling strategy of the first network service is the third API, the second API, and the first API in sequence.

[0061] Specifically, the resources in the layered network resources are defined as follows: resources in the first layer are called first network resources, resources in the second layer are called second network resources, and resources in the third layer are called third network resources. First network resources are physical network resources, such as gateways and User Plane Functions (UPFs); second network resources are network element resources, such as wireless network elements, access network elements, and transmission network elements; and third network resources are system function resources, such as resource monitoring functions, fault location functions, and quality analysis functions.

[0062] By encapsulating the network resources at each layer, we obtain the first API of the first network resource, the second API of the second network resource, and the third API of the third network resource. Combining the APIs corresponding to the three layers of network resources yields the API invocation strategy for the first network service. For example, the invocation order of the API invocation strategy for the first network service can be the third API, the second API, and the first API, in that order.

[0063] This embodiment combines and calls the APIs corresponding to network resources at each layer to obtain API calling strategies for various network services, corresponding to multiple network services.

[0064] In one embodiment, the network resource invocation method provided in this application may further include the following steps 400, 500 and 600.

[0065] Step 400: Based on the received service request, determine the network service to be processed.

[0066] Step 500: Based on the network service to be processed, determine the packaging product to be used and the API call path corresponding to the packaging product.

[0067] Step 600: Call each API on the API call path to obtain the service result of the network service to be processed.

[0068] Specifically, after combining the APIs corresponding to multiple layers of network resources to obtain API calling strategies for various network services, a service request is received, and based on the received service request, the network service to be processed is determined. By analyzing the network service, the characteristics of the network service and the corresponding encapsulation product are determined. The encapsulation product proposed in this invention refers to the combination and encapsulation of APIs corresponding to various network resources. When the product to be used can be determined through analysis of the network service to be processed, the API calling path corresponding to the encapsulation product to be used is queried. The API calling path corresponding to the encapsulation product to be used includes the APIs corresponding to various network resources and their calling sequence logic. Based on the API calling path, each API on the API calling path is called to obtain the service result of the network service to be processed.

[0069] This embodiment improves the efficiency and accuracy of fulfilling network service business requirements by calling each API on the API call path corresponding to the network service to be processed.

[0070] In one embodiment, the network resource invocation method provided in this application may further include the following steps.

[0071] Step 700: Locate the packaging product corresponding to the network service to be processed.

[0072] Step 800: If there is no encapsulated product corresponding to the network service to be processed, determine the target resource corresponding to the network service to be processed.

[0073] Step 900: Add the target resource to the network resource capability library.

[0074] Specifically, based on the above, if a query for the encapsulated product corresponding to the network service to be processed cannot find one, it indicates that the encapsulated product for the network service to be processed does not yet exist. The network service to be processed is a new network service, and its corresponding API calling strategy does not yet exist. In this case, the target resource corresponding to the network service to be processed is determined, i.e., the network resources required to implement the network service. After determining the required network resources, the target resource is added to the network resource capability library, and then the target resource is encapsulated to obtain the corresponding API. Finally, the APIs corresponding to the target resource are combined to obtain the API calling strategy for the network service to be processed.

[0075] If the target resource already exists in the network resource capability library, it means that the API calling strategy was not built based on the target resource in the early stage. In this case, the target resource is encapsulated to obtain the API corresponding to the target resource, and then the API corresponding to the target resource is combined to obtain the API calling strategy of the network service to be processed.

[0076] This embodiment processes network resources in the network resource capability library by searching for the query results of the packaged products corresponding to the network services to be processed, so as to realize various network services to be processed.

[0077] The network resource retrieval device provided by the present invention is described below. The network resource retrieval device described below can be referred to in correspondence with the network resource retrieval method described above.

[0078] Please refer to Figure 3 The present invention also provides a network resource retrieval device, comprising:

[0079] The network resource layering module 301 is used to layer network resources in the network resource capability library and determine which layers network resources with different resource characteristics belong to.

[0080] The network resource encapsulation module 302 is used to encapsulate the network resources of each layer to obtain the callable application programming interface (API) of the network resources with each characteristic.

[0081] The network resource invocation module 303 is used to combine the callable APIs of network resources at different layers to obtain API invocation strategies for various network services.

[0082] Optionally, the layering includes a first layer, a second layer, and a third layer; the network resource layering module includes: a resource characteristic determination unit, used to determine network resources with different resource characteristics, including network physical resources, network element resources, and system function resources;

[0083] The resource layering determination unit is used to determine that the network physical resources belong to the first layer, the network element resources belong to the second layer, and the system function resources belong to the third layer.

[0084] Optionally, the network resource encapsulation module includes:

[0085] A network physical resource encapsulation unit is used to encapsulate the network physical resources of the first layer to obtain the callable APIs of the network physical resources; the network physical resources include gateways and user plane functions (UPFs);

[0086] The network element resource encapsulation unit is used to encapsulate and package the network element resources of the second layer to obtain the callable APIs of the network element resources; the network element resources include wireless network elements, access network elements and transmission network elements;

[0087] The system function resource encapsulation unit is used to encapsulate the system function resources of the third layer to obtain the callable APIs of the system function resources; the system function resources include resource monitoring functions, fault location functions, and quality analysis functions.

[0088] Optionally, the network resource invocation module includes:

[0089] A hierarchical resource determination unit is used to determine a first resource in the first layer, a second resource in the second layer, and a third resource in the third layer;

[0090] The API combination unit is used to combine the first API of the first resource, the first API of the second resource, and the third API of the third resource to obtain the API calling strategy of the first network service; the calling order of the API calling strategy of the first network service is the third API, the second API, and the first API in sequence.

[0091] Optionally, the combination of callable APIs for network resources at different layers to obtain API calling strategies for various network services includes:

[0092] The pending network service determination module is used to determine the pending network service based on the received service request.

[0093] The API call path determination module is used to determine the packaging product to be used and the API call path corresponding to the packaging product based on the network service to be processed.

[0094] The service result determination module is used to call each API on the API call path to obtain the service result of the network service to be processed.

[0095] Optionally, the step of determining the network service to be processed based on the received service request includes:

[0096] The packaged product search module is used to search for the packaged product corresponding to the network service to be processed.

[0097] The target resource determination module is used to determine the target resource corresponding to the network service to be processed when there is no encapsulated product corresponding to the network service to be processed.

[0098] The target resource entry module is used to add the target resource to the network resource capability library.

[0099] Figure 4 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 4 As shown, the electronic device may include a processor 410, a communications interface 420, a memory 830, and a communication bus 840. The processor 410, communications interface 420, and memory 430 communicate with each other via the communication bus 440. The processor 410 can call logical instructions in the memory 430 to execute a network resource invocation method. This method includes: layering network resources in the network resource capability library to determine which layers network resources with different characteristics belong to; encapsulating the network resources in each layer to obtain a callable application programming interface (API) for each type of network resource; and combining the callable APIs of different layers of network resources to obtain API invocation strategies for various network services.

[0100] Furthermore, the logical instructions in the aforementioned memory 430 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0101] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the network resource invocation method provided by the above methods. The method includes: layering network resources in a network resource capability library to determine that network resources with different resource characteristics belong to different layers; encapsulating the network resources of each layer to obtain a callable application programming interface (API) for each type of network resource; and combining the callable APIs of network resources from different layers to obtain API invocation strategies for various network services.

[0102] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements a network resource invocation method provided by the above methods. The method includes: layering network resources in a network resource capability library to determine that network resources with different resource characteristics belong to different layers; encapsulating the network resources of each layer to obtain a callable application programming interface (API) for each type of network resource; and combining the callable APIs of network resources from different layers to obtain API invocation strategies for various network services.

[0103] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0104] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0105] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for retrieving network resources, characterized in that, include: The network resources in the network resource capability library are stratified to determine which strata network resources with different characteristics belong to. Encapsulate the network resources at each layer to obtain callable application programming interfaces (APIs) for each type of network resource. By combining the callable APIs of network resources at different layers, a variety of API calling strategies for network services can be obtained. The layering includes a first layer, a second layer, and a third layer; the layering of network resources in the network resource capability library, and the determination that network resources with different resource characteristics belong to different layers, includes: Network resources with different characteristics include network physical resources, network element resources, and system function resources. The network physical resources are determined to belong to the first layer, the network element resources to belong to the second layer, and the system function resources to belong to the third layer. The encapsulation of network resources at each layer to obtain callable application programming interface (API) for each type of network resource includes: The network physical resources of the first layer are encapsulated to obtain the callable APIs of the network physical resources; the network physical resources include gateways and user plane functions (UPFs). The network element resources of the second layer are encapsulated and packaged to obtain the callable APIs of the network element resources; the network element resources include wireless network elements, access network elements and transmission network elements; The system function resources of the third layer are encapsulated to obtain the callable APIs of the system function resources; the system function resources include resource monitoring functions, fault location functions, and quality analysis functions. The strategy for combining callable APIs of network resources at different layers to obtain API calling strategies for various network services includes: Identify the first resource in the first layer, the second resource in the second layer, and the third resource in the third layer; The first API of the first resource, the first API of the second resource, and the third API of the third resource are combined to obtain the API calling strategy of the first network service; the calling order of the API calling strategy of the first network service is the third API, the second API, and the first API in sequence. The method of combining callable APIs of network resources at different layers to obtain API calling strategies for various network services includes: Based on the received service requests, determine the network services to be processed; Based on the network service to be processed, determine the packaging product to be used and the API call path corresponding to the packaging product; Call each API on the API call path to obtain the service result of the network service to be processed.

2. The network resource invocation method according to claim 1, characterized in that, The process of determining the network service to be processed based on the received service request then includes: Locate the packaged product corresponding to the network service to be processed; If there is no corresponding encapsulated product for the network service to be processed, determine the target resource corresponding to the network service to be processed. Add the target resource to the network resource capability library.

3. A network resource retrieval device, characterized in that, The device performs the network resource invocation method as described in any one of claims 1 to 2.

4. An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the network resource invocation method as described in any one of claims 1 to 2.

5. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the network resource invocation method as described in any one of claims 1 to 2.

6. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the network resource invocation method as described in any one of claims 1 to 2.

Citation Information

Patent Citations

  • Model-driven network resource service design method and system

    CN116232913A

  • Method and system for determining design and segmentation for robust network access security

    US20240089294A1