Service function organization method, system, electronic device and storage medium

Abstract

The present disclosure provides a method, system, electronic device, and computer-readable storage medium for service function organization to solve the problem of service functions not being divided when processed by a server. The method includes the steps of receiving a traffic request from a client, including a service desired by a user; dividing a divisible service among the user-desired services based on the traffic request to obtain a plurality of divided sub-services; selecting resource nodes to provide services for the divided sub-services and the indivisible service among the user-desired services, respectively; generating traffic paths based on the selected resource nodes; and configuring related network devices based on the traffic paths to cause the resource nodes to provide the corresponding services to clients. The invention disclosed herein can divide services and effectively improve the efficiency of service processing.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This disclosure claims priority to a Chinese patent application filed on November 4, 2022, bearing application number CN202211376428.7 and entitled "Service function organization method, system, electronic device and storage medium."

[0002] The present disclosure relates to the field of communication technologies, but is not limited thereto, and in particular to a method of service function orchestration, a system of service function orchestration, an electronic device, and a computer-readable storage medium. [Background technology]

[0003] As networks and traffic develop, more and more value-added functions need to be deployed as needed. Originally, various services could be deployed in cloud resource pools. However, with the development of MEC (Mobile Edge Computing) technology and increasing user requirements for network performance such as network quality and required latency, as well as increasing user needs for flexible addition and deletion of service functions, carriers are deploying service functions in edge nodes and realizing the connection between edge nodes and service functions through network cooperation, satisfying users' needs for flexible scheduling of service functions and solving problems such as response time, resource optimization, and network efficiency. As shown in Figure 1, a carrier network is connected to a resource pool consisting of one or more servers via gateway nodes, and related service functions are deployed in the servers.

[0004] However, currently, all services respond to user traffic requests by responding to the service as a whole, rather than dividing and processing the service functions, resulting in low processing efficiency. Summary of the Invention [Means for solving the problem]

[0005] The technical problem that the present disclosure aims to solve is the inability of conventional technologies to divide service functions. To address this, a method for organizing service functions, a system for organizing service functions, an electronic device, and a computer-readable storage medium are provided that can divide services and effectively improve the efficiency of service processing.

[0006] In a first aspect, the present disclosure provides a method of service function orchestration, comprising: receiving a traffic request from a client, the traffic request including a service desired by the user; dividing a divisible service among the services desired by the user based on the traffic request, and obtaining a plurality of divided sub-services; selecting a resource node that provides a service for each of the divided sub-services and the indivisible service among the services desired by the user; generating a traffic path based on the selected resource node; and configuring related network devices based on the traffic paths to cause the resource nodes to provide corresponding services to the clients. A method is provided.

[0007] In one embodiment, the traffic request further includes a service type and service needs of a service desired by the user, the service needs including a requirement for network performance and a need for computational storage resources; The step of dividing divisible services among services desired by the user based on the traffic request includes: Dividing each of the divisible services into a plurality of sub-services based on the service types stored in each resource node and the service types of the services desired by the user, or based on the service needs of the services desired by the user; The method comprises: The method further includes recording service capability information including the service number, service features and service needs of each indivisible service and each sub-service.

[0008] In one embodiment, the method comprises: After obtaining a plurality of divided sub-services, classifying all the sub-services and the indivisible services into serializable services and parallelizable services based on the service function information; The method further includes performing service sorting on all sub-services and indivisible services according to the service logic after classification, and obtaining a service sequence including service classification information and service sorting information.

[0009] In one embodiment, the step of selecting a resource node to provide a service for each of the divided sub-services and the indivisible service among the services desired by the user includes: The method includes selecting a resource node that provides service for all the sub-services and the indivisible service, respectively, based on the service sequence and the service needs corresponding to each of the sub-services and the indivisible service.

[0010] In one embodiment, generating a traffic path based on the selected resource node comprises: The method includes a step of organizing a traffic path including resource nodes that provide selected services for all subservices and indivisible services based on the service sequence and the resource nodes, and selecting one node as a parallelizable service aggregation node for the path of the parallelizable service.

[0011] In one embodiment, the step of configuring related network devices based on the traffic path to cause resource nodes to provide corresponding services to clients includes: The method includes a step of generating a configuration file for the associated network devices based on the traffic route, sending the configuration file to the associated network devices, causing each associated network device to obtain a next hop address on the corresponding traffic route, and causing a resource node among the associated network devices to provide a corresponding service to the client.

[0012] In one embodiment, the method comprises: The method further includes registering existing and newly deployed service functions of the resource nodes and identifying the locations and computing resources of the resource nodes.

[0013] In one embodiment, the method comprises: authenticating user information; If the authentication is successful, receiving a traffic request from the client.

[0014] In one embodiment, the method comprises: The method further includes deploying a desired service function to an edge node corresponding to the client when the frequency of access to the desired service by the client exceeds a predetermined value.

[0015] In one embodiment, the method comprises: generating a traffic bill after distributing the traffic to corresponding resource nodes; The method further includes sending the traffic bill to the client and a service provider corresponding to the resource node providing the service, and having the client and the service provider confirm the traffic bill information to complete the service transaction.

[0016] In one embodiment, the service characteristics are for identifying service relationship logic including no requirement for a service relationship and a dependency relationship for a service relationship.

[0017] In a second aspect, the present disclosure provides a system for service function orchestration, comprising: a traffic needs management module configured to receive a traffic request from a client, the traffic request including a service desired by the user; a service division module configured to divide a divisible service among services desired by a user to obtain a plurality of divided sub-services; a service resource selection module configured to select a resource node providing a service for each of the divided sub-services and the indivisible service among the services desired by the user; a service orchestration module configured to generate a traffic path based on the selected resource node; a traffic configuration module for configuring related network devices based on the traffic path to allow the resource node to provide corresponding services to the client; Provide a system.

[0018] In one embodiment, the traffic request further includes a service type and service needs of a service desired by the user, the service needs including a requirement for network performance and a need for computational storage resources; The service division module specifically includes: Dividing each of the divisible services into a plurality of sub-services based on the service types stored in each resource node and the service types of the services desired by the users, or based on the service needs of the services desired by the users; It is configured to record service capability information including the service number, service features and service needs of each indivisible service and each sub-service.

[0019] In one embodiment, the system comprises: After the service division module obtains a plurality of divided sub-services, classifying all the sub-services and the indivisible services into serializable services and parallelizable services according to the service function information; It further includes a service sorting module configured to perform service sorting on all the sub-services and the indivisible service according to the service logic after classification, and obtain a service sequence including service classification information and service sorting information.

[0020] In one embodiment, the service resource selection module specifically: The network is configured to select a resource node providing service for every sub-service and indivisible service, respectively, based on the service sequence and service needs corresponding to each of the sub-service and indivisible service.

[0021] In one embodiment, the service orchestration module specifically: The system is configured to organize traffic paths including resource nodes that provide selected services for all subservices and indivisible services based on the service sequence and the resource nodes, and to select one node as a parallelizable service aggregation node for the path of a parallelizable service.

[0022] In one embodiment, the traffic configuration module specifically: Based on the traffic route, a configuration file for the associated network devices is generated and sent to the associated network devices, causing each associated network device to obtain a next hop address on the corresponding traffic route, and causing a resource node among the associated network devices to provide a corresponding service to the client.

[0023] In one embodiment, the system comprises: The system further includes a service registration module configured to register existing and newly deployed service functions of the resource nodes and identify the locations and computing resources of the resource nodes.

[0024] In one embodiment, the system comprises: further comprising a user information management module configured to authenticate user information; The traffic needs management module is specifically configured to receive a traffic request from a client when the user information management module successfully authenticates the user information.

[0025] In one embodiment, the system comprises: The system further includes a service deployment module configured to deploy a desired service function to an edge node corresponding to a client when the frequency of access to the desired service by the client exceeds a predetermined value.

[0026] In one embodiment, the system comprises: After providing computing power services to clients, generate traffic invoices; The method further includes a service transaction module configured to transmit the traffic bill to the client and a service provider corresponding to the resource node providing the service, and have the client and the service provider confirm the traffic bill information to complete the service transaction.

[0027] In one embodiment, the service characteristics are for identifying service relationship logic including no requirement for a service relationship and a dependency relationship for a service relationship.

[0028] In a third aspect, the present disclosure provides an electronic device including a memory having a computer program stored therein and a processor configured to execute the computer program to realize the method for service function organization described in the first aspect above.

[0029] In a fourth aspect, the present disclosure provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements the method for service capability orchestration set forth in the first aspect above.

[0030] The present disclosure provides a method, system, electronic device, and computer-readable storage medium for service function organization, which receive a user's traffic request to obtain the user's desired service, divide a divisible service among the user's desired services into multiple sub-services, select a service-providing resource node for each of the sub-services and the indivisible service, generate a traffic path, perform traffic distribution, realize the division of service functions, perform service processing using multiple resource pools, provide an optimal processing resource pool for each service, and effectively improve the efficiency of service function processing. [Brief explanation of the drawings]

[0031] [Figure 1] 1 is a schematic diagram of prior art service function networking; [Figure 2] FIG. 1 is a schematic diagram of a method flow for service function orchestration according to a first embodiment of the present disclosure. [Figure 3] FIG. 10 is an architecture diagram of a service function orchestration system according to a second embodiment of the present disclosure. [Figure 4] FIG. 10 is a schematic diagram of a method flow for service function orchestration according to a second embodiment of the present disclosure. [Figure 5] FIG. 10 is a schematic diagram of a service function classification result according to the second embodiment of the present disclosure. [Figure 6] FIG. 10 is a schematic diagram of resource pool selection according to a second embodiment of the present disclosure. [Figure 7] FIG. 11 is an architecture diagram of a service function orchestration system according to a third embodiment of the present disclosure. [Figure 8] FIG. 10 is an architecture diagram of an electronic device according to a fourth embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0032] In order to enable those skilled in the art to better understand the invention according to the present disclosure, the present disclosure will be described in more detail with reference to the accompanying drawings and examples. It should be understood that the specific examples and drawings described herein are for the purpose of illustrating the present disclosure and are not intended to limit the present disclosure.

[0033] In order to allow those skilled in the art to better understand the invention according to the present disclosure, the present disclosure will be described in more detail with reference to the accompanying drawings and examples. It should be understood that the specific examples and drawings described herein are for the purpose of illustrating the present disclosure, and are not intended to limit the present disclosure. It should be understood that the various examples and various features of the examples of the present disclosure can be combined as long as they do not conflict with each other.

[0034] It should be understood that for ease of illustration, only parts relevant to the present disclosure are shown in the drawings of the present disclosure, and parts not relevant to the present disclosure are not shown in the drawings.

[0035] It should be understood that each unit and module according to the embodiments of the present disclosure may correspond to only one entity structure, may be composed of multiple entity structures, or multiple units and modules may be integrated into one entity structure.

[0036] It should be understood that the functions and steps illustrated in the flowcharts and block diagrams of the present disclosure may occur in a different order than that shown in the figures, unless consistent with the present disclosure.

[0037] It should be understood that the flowcharts and block diagrams in the present disclosure illustrate the architecture, functionality, and operation of possible implementations of systems, devices, apparatuses, and methods according to embodiments of the present disclosure. Here, each block in the flowcharts or block diagrams may represent a unit, module, program segment, or code containing executable instructions for implementing a specific function. Furthermore, each block or combination of blocks in the block diagrams and flowcharts may be implemented in a hardware-based system that realizes a predetermined function, or may be implemented as a combination of hardware and computer instructions.

[0038] It should be understood that the units and modules according to the embodiments of the present disclosure may be implemented by software or by hardware, for example, the units and modules may be located within a processor.

[0039] Herein, the terms used in the embodiments of the present disclosure are for the purpose of describing particular embodiments only and are not intended to limit the present disclosure. As used in the embodiments of the present disclosure and the appended claims, the singular forms "a," "the," and "the" are also intended to include the plural forms unless the context clearly dictates otherwise.

[0040] In the following description, the suffixes used to denote elements such as "module," "element," or "unit" are merely for facilitating the description of the present disclosure and do not have any particular meaning in themselves. Therefore, "module," "element," or "unit" can be used interchangeably.

[0041] The invention according to the present disclosure and how the invention according to the present disclosure solves the above-mentioned technical problems in the prior art will be described in detail below through specific examples. Some of the following specific examples can be combined with each other, and the same or similar concepts or processes will not be described in some examples.

[0042] Example 1 As shown in FIG. 2, this embodiment provides a method for organizing service functions, including steps S101 to S105.

[0043] Step S101: Receive a traffic request from a client, the traffic request including a service desired by the user.

[0044] This embodiment is applied to a service orchestration system, which, after receiving a traffic request sent by a user, obtains the service functions (i.e., services) desired by the user, including the type of service to be accessed, the requirements for network performance, the needs for computing and storage resources, etc. Then, based on the information such as the service type and the resources required for the service, it is determined whether the service desired by the user includes a divisible service, and if so, proceeds to step S102.

[0045] Step S102: Based on the traffic request, divide a divisible service among the services desired by the user to obtain a plurality of divided sub-services.

[0046] Specifically, when dividing a service, each divisible service is divided into multiple subservices based on the service types stored in each resource node and the service type of the service desired by the user, or based on the service needs of the service desired by the user. When dividing, the service is divided into several subservices using a division algorithm, such as a distributed federated training algorithm, which is a method for dividing services of the same type. This is an obvious parallel division method. By decomposing the training task into several steps, training can be performed using a training method (such as convolution calculation, clustering, or correlation analysis) to divide the training into several steps, such as training task 1, task 2, and task 3 depending on the results of tasks 1 and 2. Therefore, a serial / parallel order is established after division. The service division algorithm can adopt various existing division algorithms, and is not limited thereto. After dividing a service, service function information for each indivisible service and each subservice is recorded, including service number, service features, and service needs. The service features identify service relationship logic, including, for example, no requirement for service relationship and dependency in service relationship. If there is dependency in service relationship, it is necessary to determine the relationship, such as the order of service processing.

[0047] The resource node is a resource pool. In the process of registering existing service functions and newly deployed service functions, the service types stored in each resource node are known in advance, and the service function types are recorded in a database, and their locations, computing resources, etc. are identified. The database can be recorded as shown in Table 1 below. [Table 1]

[0048] Step S103: A resource node that provides the service is selected for each of the divided sub-services and the indivisible service among the services desired by the user.

[0049] For each of the subservices and indivisible services, a resource node, i.e., a resource pool, that provides the service is selected based on the needs of each service and is selected using some evaluation method that comprehensively considers the network elements of each resource pool, including bandwidth, delay, and jitter, and the computing capacity elements, including the resource pool load rate.

[0050] In an alternative embodiment, after obtaining a plurality of divided sub-services, all the sub-services and indivisible services are classified into serializable services and parallelizable services based on the service capability information.

[0051] After classification, service sorting is performed on all subservices and indivisible services according to the service logic, and a service sequence including service classification information and service sorting information is obtained.

[0052] Subservices and indivisible services are classified into serial and parallel based on service logic, and then service sorting is performed to obtain multiple service sequences, thereby ensuring that services requiring serialization are performed in the correct order and that parallel services can be performed simultaneously by multiple resource pools, thereby improving service efficiency.

[0053] In one embodiment, after classification, a resource node providing the service is selected for every sub-service and indivisible service, respectively, based on the service sequence and the service needs corresponding to each of the sub-service and indivisible service.

[0054] After obtaining the service sequences, for each sequence, select a resource node for each service in the sequence based on the service needs, and then store the classification information and the resource node selection information.

[0055] Step S104: Generate a traffic path based on the selected resource node.

[0056] After selecting resource nodes for each of the subservices and indivisible services, traffic paths including resource pools are organized according to the service logic, and each service is processed by a traffic path.

[0057] In an alternative embodiment, after obtaining a service sequence by classifying and sorting the services, a traffic path including the resource nodes is organized based on the service sequence and the resource nodes that provide the selected services for all the subservices and the indivisible services, and one node is selected as a parallelizable service aggregation node for the parallelizable service path. After the parallelizable services are processed, the aggregation node performs service integration processing.

[0058] Step S105: Configure related network devices according to the traffic path to make the resource node provide corresponding services to the client.

[0059] Specifically, based on the traffic route, a configuration file for the associated network devices is generated and sent to the associated network devices, causing each associated network device to obtain the next hop address on the corresponding traffic route, and causing a resource node among the associated network devices to provide the corresponding service to the client.

[0060] The traffic path is the network path from the client to the selected resource node (resource pool), the relevant network devices are the specific devices that need to be traversed from the client to the resource pool, and the transmitted configuration file guides the network devices on how to forward the next hop to generate the specific network path. The resource node is included in the network devices.

[0061] In one embodiment, the method comprises: authenticating user information; If the authentication is successful, receiving a traffic request from the client.

[0062] The system mainly manages user information, including user authentication, authorization, and authority management, for users requesting traffic, corporate users providing services, general individual users, and carrier staff (operation and maintenance, administrators, etc.), and guarantees the security of transactions by receiving user traffic requests only after successful user authentication.

[0063] In one embodiment, the method comprises: The method further includes deploying a desired service function to an edge node corresponding to the client when the frequency of access to the desired service by the client exceeds a predetermined value.

[0064] The predetermined value can be selected according to actual circumstances, and for services that are frequently accessed based on the frequency of user requests, an appropriate edge node can be selected to pre-deploy the services, facilitating the processing of subsequent requests for the services.

[0065] In one embodiment, the method comprises: generating a traffic bill after distributing the traffic to corresponding resource nodes; The method further includes sending the traffic bill to the client and a service provider corresponding to the resource node providing the service, and having the client and the service provider confirm the traffic bill information to complete the service transaction.

[0066] Based on the traffic distribution result data, a traffic bill is generated, and relevant billing information is sent to the users requesting traffic and the users providing services, and these users are allowed to confirm and complete the service transaction.

[0067] In one embodiment, the service characteristics are for identifying service relationship logic including no requirement for a service relationship and a dependency relationship for a service relationship.

[0068] The service characteristic comprises a first identification bit and a second identification bit. Here, the first identification bit includes a first identifier or a second identifier. If the first identification bit is the first identifier, the service relationship logic indicating the service characteristic indicates no requirement for a service relationship. The second identification bit can take any value, for example, 000000. If the first identification bit is the second identifier, the service relationship logic indicating the service characteristic indicates dependency. The second identification bit identifies the number of a service that must be completed before this service can be executed, indicating that this service can only be executed after the service corresponding to the second identification bit is completed. The values ​​of the first identifier and the second identifier can be determined according to actual circumstances and are not limited here. For example, the first identifier can be 00, 000, etc., and the second identifier can be 01, 001, etc.

[0069] Service characteristics allow for better validation of the logic of service relationships, ensuring that services are processed in an optimal order.

[0070] The embodiments of the present disclosure can be applied to various service processing scenarios, realize service division, and improve service processing efficiency, and are applied to one scenario, for example, as follows:

[0071] The video surveillance service request can be divided into resource acquisition service, video data processing service, and data analysis service, or as some subsequent needs arise, modeling can be performed based on the analysis data to obtain user behavior predictions.

[0072] Therefore, according to the above description, one service request can be divided into several sub-service functions, and at the same time, for example, a video processing service function, because the amount of data is too large, it can be divided into multiple parts, distributed to multiple nodes for parallel processing, and finally integrated based on the service orchestration system.

[0073] This embodiment divides divisible services, classifies them according to service function types, sorts them according to service logic, and finally selects resource nodes to provide the services in order according to the service logic, and then generates traffic paths according to the sorted and selected resource nodes to complete the process of service function organization. At the same time, by classifying service requests according to their traffic types and sorting them logically, the efficiency of service function processing can be effectively improved.

[0074] Example 2 This embodiment provides a method for service function orchestration, which is realized by the service function orchestration system shown in FIG. 3. As shown in FIG. 3, the orchestration system includes three logical layers: service orchestration, service management, and external function.

[0075] External function layer: Used for receiving user service orchestration requests, managing users, and managing service transactions, this layer includes at least a user information management module, a service transaction module, and a traffic needs management module.

[0076] User information management module: This module is responsible for managing user information, including users requesting traffic, corporate users providing services, general individual users, and carrier staff (operation and maintenance, administrators, etc.). This module is mainly responsible for user authentication, authorization, and authority management.

[0077] Service transaction module: This module receives the result data from the traffic setting module of the service organization layer, generates a traffic bill, sends it to the user information management module, and confirms the relevant bill information with the user requesting the service and the user providing the service, thereby completing the service transaction.

[0078] Traffic Needs Management Module: This module obtains traffic needs information from users, including requests for services they need to access, their needs for network resources, and their needs for computational resources.

[0079] Service management layer: responsible for service resource management, service function deployment, etc. This layer includes at least a service registration module and a service deployment module.

[0080] Service Registration Module: This module mainly registers existing and newly deployed service functions, and identifies their locations, computing resources, etc.

[0081] Service deployment module: This module obtains information from the user information management module and traffic needs management module of the external function layer, mainly regarding user request frequency, and can select appropriate edge nodes to pre-deploy services for frequently accessed services, facilitating subsequent service requests.

[0082] The service orchestration layer is mainly responsible for dividing service capabilities and rationally scheduling resources, and includes at least a service division module, a service sorting module, a service resource selection module, a service orchestration module, and a traffic configuration module.

[0083] Service division module: This module mainly targets divisible services, which can be divided based on service type or amount of service tasks, and divides the divisible services into several sub-services.

[0084] Service sorting module: This module classifies the sub-services and indivisible services after division by the service function division module. The classification means displaying the order of processing each service function and displaying serial processing and parallel processing, that is, serial processing displays a precedence relationship, while parallel processing has no related precedence relationship.

[0085] Service resource selection module: This module mainly selects based on service functions, i.e., for divisible services, it selects resource pools for each subtask. The selection of subtask functions requires simultaneous consideration of the network resource and computational storage resource conditions. Network resource requirements include bandwidth, delay, and jitter requirements, while computational storage needs include resource pool load rates, computational task computation needs, and storage needs.

[0086] Service composition module: This module performs service composition in sequence based on the results of service function division, service function classification and service function selection, and performs traffic integration for parallel sequence services to designated gateway devices to complete service function composition.

[0087] Traffic configuration module: This module sends configuration instructions to relevant devices based on the results of the service orchestration module, completes network path configuration, and realizes service functions.

[0088] As shown in FIG. 4, the method includes the following steps:

[0089] Step 1: A user submits a desired service request, which includes at least the desired service type, network performance needs, and computational storage resource needs, such as the user's desired services F1, F2, F3, low latency, 100M bandwidth, and low resource pool load, and sends the service request information to the service division module of the service orchestration layer.

[0090] Step 2: Determine whether services F1, F2, and F3 can be split, and if they can be split, send them to the service splitting module to complete the splitting and maintain network performance needs and computational storage resource needs. If service F1 cannot be split, service F2 can be split into F2.1, F2.2, and F2.3, and service F3 can be split into F3.1 and F3.2, send service F1 to the service sorting module, and send services F2 and F3 to the service splitting module.

[0091] Step 3: Service F2 and service F3 are divided into F2.1, F2.2, F2.3 and F3.1, F3.2, respectively, and the division results are sent to the service sorting module.

[0092] The service function information obtained by the classification module is shown in Table 2 below. [Table 2]

[0093] The service feature identifies the service relationship logic and consists of two identification bits plus a service-dependent service number. If the identifier is 00, it indicates no request, and if the identifier is 01, it indicates a dependency. This service can only be executed once the service function corresponding to the service-dependent service number after the identifier 01 is completed. By default, numbers with all digits equal to 0 are service functions that are executed with priority.

[0094] Step 4: The service sorting module receives the service function information, needs to access services F1, F2.1, F2.2, F2.3, F3.1, F3.2, and then clarifies the interdependence of the service functions based on the service characteristics, performs classification, and sends the service sequence with the classification and sorting information to the service resource selection module. Please refer to the following. Subsequence 1: Service F1, Service F3.1, Service F3.2 Subsequence 2: Service F2.1, Service 2.2 Subsequence 2: Service F2.1, Service 2.3 Figure 5 shows the classification results of service functions.

[0095] Step 5: Based on the service needs in the service information, i.e., the user network performance requirements, the needs for computing and storage resources, as well as the service feature information and the service classification results, a resource pool that can provide the service is selected through an evaluation method, and the service sequence with the classification and sorting information and the selected resource pool information (network node ID, IP address) are sent to the service orchestration module. See Table 3 below. [Table 3]

[0096] The data received by the resource selection module are the indivisible service and the divided sub-services. As shown in Figure 6, taking sub-sequence 1 as an example, in the figure, service functions F1, F3.1 and F3.2 are deployed in two resource pools respectively.

[0097] The network factors considered in the evaluation method for resource pool selection include bandwidth, delay, and jitter, and the computational capability factors include resource pool load rate, etc., but may also include other factors.

[0098] Modeling can be done based on the above factors, and then evaluation results can be obtained.

[0099] For example, when selecting service function F1, distance affects the delay. Taking the above factors into consideration, the service function in Pool4 is selected to provide F1, and when selecting the provision of service F3.1, the distance from other resource pools to Pool4 (immediate delay factor) is taken into consideration, starting from the location of the resource pool in Pool4. At the same time, after a service function is occupied, the load of the resource pool also needs to be updated in real time. Therefore, when selecting a resource pool, the evaluation result is updated based on the order of services, and the service function is selected.

[0100] Step 6: The service orchestration module generates traffic paths according to the resource pool conditions selected based on the received service order and service needs in the service information, designates a service aggregation node (network node) at the end of the sequence for parallelizable services, and sends the aggregated traffic nodes and orchestrated traffic paths to the traffic setting module.

[0101] Step 7: The traffic configuration module generates configuration files for the aggregation node as well as the relevant network devices and resource pools according to the composition result, and sends them to the relevant devices to complete the service.

[0102] In this embodiment, a service request desired by a user is acquired, and the service division module of the service organization layer determines and divides divisible service functions, classifies them according to service function types, sorts them according to service logic, and finally selects resource nodes in order to provide the service according to the service logic, generates traffic paths, and completes the service function organization process, thereby effectively improving the efficiency of service function processing.

[0103] Example 3 As shown in FIG. 7, this embodiment is a service function orchestration system, a traffic needs management module 11 configured to receive a traffic request from a client, the traffic request including a service desired by the user; a service division module 12 configured to divide a divisible service among the services desired by the user to obtain a plurality of divided sub-services; a service resource selection module 13 configured to select resource nodes providing services for the divided sub-services and the indivisible services among the services desired by the user, respectively; a service orchestration module 14 configured to generate traffic paths based on the selected resource nodes; a traffic configuration module 15 for configuring related network devices based on the traffic path, and causing the resource node to provide corresponding services to the client; Provide a system.

[0104] In one embodiment, the traffic request further includes a service type and service needs of a service desired by the user, the service needs including a requirement for network performance and a need for computational storage resources; The service division module 12 specifically includes: Dividing each of the divisible services into a plurality of sub-services based on the service types stored in each resource node and the service types of the services desired by the users, or based on the service needs of the services desired by the users; It is configured to record service capability information including the service number, service features and service needs of each indivisible service and each sub-service.

[0105] In one embodiment, the system comprises: After the service division module 12 obtains a plurality of divided sub-services, classifying all the sub-services and indivisible services into serializable services and parallelizable services according to the service function information; It further includes a service sorting module 16 configured to perform service sorting on all the sub-services and the indivisible service according to the service logic after classification, and obtain a service sequence including service classification information and service sorting information.

[0106] In one embodiment, the service resource selection module 13 specifically: The network is configured to select a resource node providing service for every sub-service and indivisible service, respectively, based on the service sequence and service needs corresponding to each of the sub-service and indivisible service.

[0107] In one embodiment, the service orchestration module 14 specifically: The system is configured to organize traffic paths including resource nodes that provide selected services for all subservices and indivisible services based on the service sequence and the resource nodes, and to select one node as a parallelizable service aggregation node for the path of a parallelizable service.

[0108] In one embodiment, the traffic configuration module 15 specifically: Based on the traffic route, a configuration file for the associated network devices is generated and sent to the associated network devices, causing each associated network device to obtain a next hop address on the corresponding traffic route, and causing a resource node among the associated network devices to provide a corresponding service to the client.

[0109] In one embodiment, the system comprises: It further includes a service registration module 17 configured to register existing and newly deployed service functions of the resource nodes and to identify the locations and computing resources of the resource nodes.

[0110] In one embodiment, the system comprises: further comprising a user information management module 18 configured to authenticate user information; The traffic needs management module 11 is specifically configured to receive a traffic request from a client after the user information management module has successfully authenticated the user information.

[0111] In one embodiment, the system comprises: The system further includes a service deployment module 19 configured to deploy a desired service function to an edge node corresponding to a client when the frequency of access to the desired service by the client exceeds a predetermined value.

[0112] In one embodiment, the system comprises: After providing computing power services to clients, generate traffic invoices; The network further includes a service transaction module 20 configured to transmit the traffic bill to the client and a service provider corresponding to the resource node providing the service, and have the client and the service provider confirm the traffic bill information to complete the service transaction.

[0113] In one embodiment, the service characteristics are for identifying service relationship logic including no requirement for a service relationship and a dependency relationship for a service relationship.

[0114] The system for service function organization in the third embodiment of the present disclosure is for implementing the method for service function organization in the first and second embodiment of the method, so the description thereof is relatively simple. Specifically, reference may be made to the related description in the first embodiment of the method, and detailed description thereof will be omitted here.

[0115] Also, as shown in FIG. 8, the electronic device according to the fourth embodiment of the present disclosure includes a memory 100 and a processor 200 that executes the various possible methods described above when executing a computer program stored in the memory 100.

[0116] Here, a memory 100 is connected to a processor 200, and the memory 100 can be a flash memory or a read-only memory or other memory, and the processor 200 can be a central processing unit or a single-chip computer.

[0117] An embodiment of the present disclosure also provides a computer-readable storage medium that stores a computer program that, when executed by a processor, realizes the various possible methods described above.

[0118] Computer-readable storage media include volatile or nonvolatile, removable or non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, computer program modules, or other data, including, but not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium used to store the desired information and which can be accessed by a computer.

[0119] It should be understood that the above-described embodiments are merely exemplary embodiments used to explain the principles of the present disclosure, and the present disclosure is not limited thereto. Those skilled in the art can make various changes and modifications that are considered to be within the scope of the present disclosure without departing from the spirit and essence of the present disclosure.

Claims

1. 1. A method of service function orchestration, comprising: receiving a traffic request from a client, the traffic request including a service desired by the user; dividing a divisible service among the services desired by the user based on the traffic request, and obtaining a plurality of divided sub-services; selecting a resource node that provides a service for each of the divided sub-services and the indivisible service among the services desired by the user; generating a traffic path based on the selected resource node; and configuring related network devices based on the traffic paths to cause the resource nodes to provide corresponding services to the clients. method.

2. The traffic request further includes a service type and service needs of a service desired by the user, the service needs including a requirement for network performance and a need for computational storage resources; The step of dividing divisible services among services desired by the user based on the traffic request includes: Dividing each of the divisible services into a plurality of sub-services based on the service types stored in each resource node and the service types of the services desired by the user, or based on the service needs of the services desired by the user; The method comprises: further comprising recording service capability information including service numbers, service features and service needs of each indivisible service and each sub-service; The method of claim 1.

3. The method comprises: After obtaining a plurality of divided sub-services, classifying all the sub-services and the indivisible services into serializable services and parallelizable services based on the service function information; After classification, performing service sorting on all sub-services and indivisible services according to service logic to obtain a service sequence including service classification information and service sorting information; The method of claim 2.

4. The step of selecting a resource node to provide a service for each of the divided sub-services and the indivisible service among the services desired by the user includes: selecting a resource node to provide service for all the sub-services and the indivisible service, respectively, based on the service sequence and service needs corresponding to each of the sub-services and the indivisible service; The method of claim 3.

5. The step of generating a traffic path based on the selected resource node includes: The method includes a step of organizing a traffic path including resource nodes that provide selected services for all sub-services and the indivisible service based on the service sequence and the resource nodes, and selecting one node as a parallelizable service aggregation node for the path of the parallelizable service. The method of claim 4.

6. configuring related network devices based on the traffic paths to cause resource nodes to provide corresponding services to clients; generating a configuration file for each associated network device based on the traffic route, and transmitting the configuration file to the associated network device, causing each associated network device to obtain a next hop address on the corresponding traffic route, and causing a resource node among the associated network devices to provide a corresponding service to the client; The method of claim 1.

7. The method comprises: registering existing and newly deployed service functions of the resource nodes and identifying the locations and computing resources of the resource nodes; The method of claim 1.

8. The method comprises: authenticating user information; and upon successful authentication, receiving a traffic request from the client. The method of claim 1.

9. The method comprises: and further comprising the step of deploying a desired service function to an edge node corresponding to the client when the frequency of access to the desired service by the client exceeds a predetermined value. The method of claim 1.

10. The method comprises: generating a traffic bill after distributing the traffic to corresponding resource nodes; sending the traffic bill to the client and a service provider corresponding to the resource node providing the service, and having the client and the service provider confirm the traffic bill information and complete the service transaction; The method of claim 1.

11. The service characteristics are for identifying service relationship logic, including no requirements for the service relationship and dependency relationships for the service relationship. The method of claim 2.

12. 1. A system for organizing service functions, comprising: a traffic needs management module configured to receive a traffic request from a client, the traffic request including a service desired by the user; a service division module configured to divide a divisible service among services desired by a user to obtain a plurality of divided sub-services; a service resource selection module configured to select a resource node providing a service for each of the divided sub-services and the indivisible service among the services desired by the user; a service orchestration module configured to generate a traffic path based on the selected resource node; a traffic configuration module for configuring related network devices based on the traffic path to allow the resource node to provide corresponding services to the client; system.

13. The traffic request further includes a service type and service needs of a service desired by the user, the service needs including a requirement for network performance and a need for computational storage resources; The service division module specifically includes: Dividing each of the divisible services into a plurality of sub-services based on the service types stored in each resource node and the service types of the services desired by the users, or based on the service needs of the services desired by the users; configured to record service capability information including service numbers, service features and service needs of each indivisible service and each sub-service; The system of claim 12.

14. The system comprises: After the service division module obtains a plurality of divided sub-services, classifying all the sub-services and the indivisible services into serializable services and parallelizable services according to the service function information; a service sorting module configured to perform service sorting on all the sub-services and the indivisible service according to the service logic after classification, and obtain a service sequence including service classification information and service sorting information; The system of claim 13.

15. The service resource selection module specifically: and configured to select, for all the sub-services and the indivisible service, respectively, a resource node providing service based on the service sequence and service needs corresponding to each of the sub-services and the indivisible service. The system of claim 14.

16. The service orchestration module specifically includes: The network is configured to organize traffic paths including resource nodes based on the service sequence and the resource nodes that provide selected services for all subservices and the indivisible service, and to select one node as a parallelizable service aggregation node for the path of the parallelizable service. The system of claim 15.

17. The traffic setting module specifically includes: The network management system is configured to generate a configuration file for each associated network device based on the traffic path, and send the configuration file to the associated network device to cause each associated network device to obtain a next hop address on the corresponding traffic path, and cause a resource node among the associated network devices to provide a corresponding service to the client. The system of claim 12.

18. The system comprises: and a service registration module configured to register existing and newly deployed service functions of the resource nodes and identify locations and computing resources of the resource nodes. The system of claim 12.

19. The system comprises: further comprising a user information management module configured to authenticate user information; The traffic needs management module is specifically configured to receive a traffic request from a client when the user information management module successfully authenticates the user information; The system of claim 12.

20. The system comprises: a service deployment module configured to deploy a desired service function to an edge node corresponding to a client when the frequency of access to the desired service by the client exceeds a predetermined value; The system of claim 12.

21. The system comprises: After providing computing power services to clients, generate traffic invoices; a service transaction module configured to transmit the traffic bill to the client and a service provider corresponding to the resource node providing the service, to allow the client and the service provider to confirm the traffic bill information and complete the service transaction; The system of claim 12.

22. The service characteristics are for identifying service relationship logic, including no requirements for the service relationship and dependency relationships for the service relationship. The system of claim 12.

23. a memory having a computer program stored therein; and a processor configured to execute the computer program to implement the method for service function orchestration according to any one of claims 1 to 11, electronic equipment.

24. storing a computer program which, when executed by a processor, implements the method for service function orchestration according to any one of claims 1 to 11; A computer-readable storage medium.

Images