Method, device and storage medium for identifying service instances

Abstract

This application discloses a method, apparatus, and storage medium for identifying service instances, relating to the field of communication technology, and is used to improve the efficiency of service instance identification. The method includes: obtaining the name of a target service chain; the name of the target service chain includes multiple fields; determining service instance information in the target service chain based on the name of the target service chain and a preset naming rule; the preset naming rule is used to indicate the position of the target field corresponding to the service instance information among the multiple fields. This application is applied in the process of identifying service instances.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus and storage medium for identifying service instances. Background Technology

[0002] Segment routing IPv6 (SRv6) service function chain (SFC) based on the Internet Protocol version 6 (IPv6) forwarding plane is a technology that guides packets through application layer service devices sequentially along a specified path by adding SRv6 path information to the original packets.

[0003] In related technologies, the orchestration and scheduling layer needs to obtain information about service instances in the service chain to determine the forwarding order of each service instance and write this order into the packet. However, the way service instance information is recorded is complex, and the orchestration and scheduling layer needs to obtain the recording method of each instance's information to identify the service instance. Therefore, how to improve the efficiency of service instance identification remains a technical problem to be solved. Summary of the Invention

[0004] This application provides a method, apparatus, and storage medium for identifying service instances, which improves the efficiency of service instance identification.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] In a first aspect, embodiments of this application provide a method for identifying service instances, wherein a service instance identification device obtains the name of a target service chain; the name of the target service chain includes multiple fields; the service instance identification device determines service instance information in the target service chain based on the name of the target service chain and a preset naming rule; the preset naming rule is used to indicate the position of the target field corresponding to the service instance information among multiple fields.

[0007] In one possible implementation, the start and end positions of the target field among multiple fields are determined based on the name of the target service chain and a preset naming rule; the target field is obtained based on the multiple fields, the start and end positions; and the service instance information in the target service chain is determined based on the target field and a service instance mapping table. The service instance mapping table includes at least one field and the service instance information corresponding to each field in the at least one field.

[0008] In one possible implementation, a first request information from a terminal device is received; the first request information is used to request the generation of a name for a target service chain; the first request information includes at least one first sub-request information; the fields corresponding to each of the at least one first sub-request information are determined; the first sub-request information includes any one of the following: type information of the target service chain, initial name of the target service chain, service instance called by the target service chain, description information of the target service chain, and initial creation account of the target service chain; based on the at least one first sub-request information and a preset naming rule, the position of the field corresponding to each of the at least one first sub-request information in multiple fields is determined; the name of the target service chain is generated according to the field corresponding to each first sub-request information and the position of each first sub-request information in multiple fields.

[0009] In one possible implementation, a second request information from a terminal device is received, the second request indicating the service requirements of the terminal device; a target service chain is determined based on the service requirement information and a service requirement mapping table; the service requirement mapping table includes at least one service chain and the service requirements corresponding to at least one service chain.

[0010] In one possible implementation, the network service quality of the target service chain is obtained; based on the network service quality and at least one service instance, the path information of at least one service instance is determined; the path information of at least one service instance is written into the header of the data packet; the service instance information includes at least one service instance.

[0011] In one possible implementation, the descriptive information of the target service chain for identifying the service instance includes at least one of the following: the scenario of identifying the target service chain for the service instance, the latency of the target service chain for identifying the service instance, the bandwidth of the target service chain for identifying the service instance, and the packet loss rate of the target service chain for identifying the service instance.

[0012] Secondly, this application provides a service instance identification device, comprising: a processing unit; the processing unit is configured to obtain the name of a target service chain; the name of the target service chain includes multiple fields; the processing unit is further configured to determine service instance information in the target service chain based on the name of the target service chain and a preset naming rule; the preset naming rule is used to indicate the position of the target field corresponding to the service instance information among multiple fields.

[0013] In one possible implementation, the processing unit is further configured to: determine the start and end identifier positions of the target field among multiple fields based on the name of the target service chain and a preset naming rule; obtain the target field based on the multiple fields, the start identifier position, and the end identifier position; and determine the service instance information in the target service chain based on the target field and a service instance mapping table; the service instance mapping table includes at least one field and service instance information corresponding to each field in the at least one field.

[0014] In one possible implementation, a communication unit is included, configured to receive first request information from a terminal device; the first request information is used to request the generation of a target service chain name; the first request information includes at least one first sub-request information; a processing unit is further configured to determine the fields corresponding to each of the at least one first sub-request information; the first sub-request information includes any one of the following: target service chain type information, initial name of the target service chain, service instance invoked by the target service chain, description information of the target service chain, and initial creation account of the target service chain; the processing unit is further configured to determine the position of the fields corresponding to each of the at least one first sub-request information in multiple fields based on the at least one first sub-request information and a preset naming rule; the processing unit is further configured to generate the name of the target service chain according to the fields corresponding to each first sub-request information and the position of each first sub-request information in multiple fields.

[0015] In one possible implementation, the communication unit is further configured to receive second request information from the terminal device, the second request indicating the service requirements of the terminal device; the processing unit is further configured to determine a target service chain based on the service requirement information and a service requirement mapping table; the service requirement mapping table includes at least one service chain and the service requirements corresponding to at least one service chain.

[0016] In one possible implementation, the processing unit is further configured to: obtain the network service quality of the target service chain; determine the path information of at least one service instance based on the network service quality and at least one service instance; write the path information of at least one service instance into the header of the data packet; the service instance information includes at least one service instance.

[0017] In one possible implementation, the descriptive information of the target service chain for identifying the service instance includes at least one of the following: the scenario of identifying the target service chain for the service instance, the latency of the target service chain for identifying the service instance, the bandwidth of the target service chain for identifying the service instance, and the packet loss rate of the target service chain for identifying the service instance.

[0018] Thirdly, this application provides an apparatus for identifying service instances, the apparatus comprising: a processor and a memory; wherein the memory is used to store computer execution instructions, and when the apparatus for identifying service instances is running, the processor executes the computer execution instructions stored in the memory to cause the apparatus for identifying service instances to perform the method for identifying service instances as described in the first aspect and any possible implementation thereof.

[0019] Fourthly, this application provides a computer-readable storage medium storing instructions that, when executed by a processor of a device for identifying service instances, enable the device for identifying service instances to perform the method for identifying service instances as described in the first aspect and any possible implementation thereof.

[0020] Fifthly, embodiments of this application provide a chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run computer programs or instructions to implement the method for identifying service instances described in the first aspect and any possible implementation of the first aspect.

[0021] In a sixth aspect, a computer program product containing instructions is provided that, when run on a computer, enables the computer to perform the method for identifying service instances described in the first aspect and any possible implementation thereof.

[0022] These or other aspects of this application will become more readily apparent in the following description.

[0023] The above solution offers at least the following advantages: In this embodiment, the service instance identification device obtains the name of the target service chain. Since preset rules are used to indicate the position of the target field corresponding to the service instance information within preset fields, the service instance identification device can obtain the target field corresponding to the service instance information from the preset fields based on the name of the target service chain and the preset rules. Therefore, the service instance identification device can identify the service instance based on the target field corresponding to the service instance information. Compared with existing technologies, the service instance identification device does not need to obtain the service instance information recorded in the service instance; it only needs to identify the service instance based on the name of the target service chain to quickly identify the service instance, thus improving the efficiency of service instance identification. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0025] Figure 1 This application provides a schematic diagram of the structure of a system for identifying service instances.

[0026] Figure 2 This is a schematic diagram of the structure of an identification service instance device provided in an embodiment of this application;

[0027] Figure 3 A flowchart illustrating a method for identifying service instances provided in this application embodiment;

[0028] Figure 4 A server structure diagram provided for an embodiment of this application;

[0029] Figure 5 A computing network architecture diagram provided for embodiments of this application;

[0030] Figure 6 A flowchart illustrating a method for identifying service instances provided in this application embodiment;

[0031] Figure 7 A flowchart illustrating a method for identifying service instances provided in this application embodiment;

[0032] Figure 8 A flowchart illustrating a method for identifying service instances provided in this application embodiment;

[0033] Figure 9 This is a schematic diagram of the structure of an identification service example device provided in an embodiment of this application. Detailed Implementation

[0034] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0035] The terms "first" and "second," etc., used in the specification and drawings of this application are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a specific order of objects.

[0036] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0037] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0038] In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0039] Glossary

[0040] 1. Computing power network

[0041] Computing power networks refer to a new paradigm that leverages network technology to effectively allocate basic resources such as computing and storage across the cloud, edge, and endpoint, collaboratively providing integrated digital technology and application services, based on the continuous ubiquitous development of computing power. SFC technology in computing power networks originated in the field of computer networks and is an important component of Network Functions Virtualization (NFV) technology.

[0042] 2. SFC technology

[0043] The core idea of ​​SFC (Service Flow Forwarding) technology is to force data flow through a series of network service function nodes (such as firewalls, load balancers, and deep packet inspection) according to a predefined service link order during packet forwarding, thereby achieving the orderly orchestration and deployment of network service functions. In computing networks, these network service functions can be virtualized or provided by physical devices. Through SFC technology, service functions distributed across different geographical locations and computing nodes can be effectively linked together to meet the network function requirements of business processes, while improving network resource utilization and business processing efficiency.

[0044] In computer networks, Service Controllers (SFCs) are primarily used to define and implement the orderly delivery of network service functions. Implementation methods mainly include:

[0045] Tag-based forwarding: This process indicates the service chain path that the packet should follow by inserting special tags into the packet. Policy-driven: This process defines service chain policies in the network controller and then pushes the policies to network devices or virtual network functions. API-driven: This process interacts with the higher-level service orchestration system through the northbound API interface to dynamically create, modify, or delete service chain instances, ensuring that network functions are executed on demand and in sequence.

[0046] The above is an explanation of the terms used in this application.

[0047] SRv6 service chaining based on the IPv6 forwarding plane is a technology that guides packets through application layer service devices sequentially along a specified path by adding SRv6 path information to the original packets.

[0048] In related technologies, the orchestration and scheduling layer needs to obtain information about service instances in the service chain to determine the forwarding order of each service instance and write this order into the packet. However, the way service instance information is recorded is complex, and the orchestration and scheduling layer needs to obtain the recording method of each instance's information to identify the service instance. Therefore, how to improve the efficiency of service instance identification remains a technical problem to be solved.

[0049] To address the technical problems existing in related technologies, in this embodiment, the service instance identification device obtains the name of the target service chain. Since a preset rule is used to indicate the position of the target field corresponding to the service instance information within a preset field, the service instance identification device can obtain the target field corresponding to the service instance information from the preset field based on the name of the target service chain and the preset rule. Therefore, the service instance identification device can identify the service instance based on the target field corresponding to the service instance information. Compared with the prior art, the service instance identification device does not need to obtain the service instance information recorded in the service instance; it only needs to identify the service instance based on the name of the target service chain to quickly identify the service instance, thus improving the efficiency of service instance identification.

[0050] The following, in conjunction with the appendix Figure 1 The system 10, which provides an example of an identification service according to an embodiment of this application, will be described in detail below. Figure 1 As shown, the system 10 for identifying service instances includes: an identification service instance device 11 and a terminal device 12.

[0051] The service instance identification device 11 is configured to: obtain the name of the target service chain; the name of the target service chain includes multiple fields; determine the service instance information in the target service chain based on the name of the target service chain and a preset naming rule; the preset naming rule is used to indicate the position of the target field corresponding to the service instance information among multiple fields.

[0052] Terminal device 12 is configured to send a first request message to identification service instance device 11; the first request message is used to request the name of the target service chain.

[0053] It should be noted in this application that the terminal device 12 is a device with wireless communication capabilities, which can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted. It can also be deployed on water (such as on ships). Furthermore, it can be deployed in the air (e.g., on airplanes, balloons, and satellites). The user terminal device, also known as a mobile station (MS), mobile terminal (MT), or other terminal equipment, is a device that provides voice and / or data connectivity to a user. For example, terminal devices include handheld devices with wireless connectivity, vehicle-mounted devices, etc. Currently, terminal devices can include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), in-vehicle devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminal devices in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, workshop equipment, wireless terminal devices in self-driving, wireless terminal devices in remote medical surgery, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, or wireless terminal devices in smart homes, and flying devices (such as intelligent robots, hot air balloons, drones, airplanes), etc. In one possible application scenario of this application, the terminal device 12 is a terminal device that frequently operates on the ground, such as an in-vehicle device. In this application, for ease of description, the chip deployed in the above-mentioned device, such as a system-on-a-chip (SOC), a baseband chip, or other chips with communication functions, can also be referred to as a user terminal device.

[0054] Optionally, the terminal device 12 can be an embedded communication device or a user handheld communication device, including mobile phones, tablets, etc.

[0055] As an example, in this embodiment, the terminal device 12 can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0056] This application provides an identification service instance apparatus for executing the identification service instance provided in this application. Figure 2 This is a schematic diagram of the structure of an identification service example device provided in an embodiment of this application. Figure 2 As shown, the identification service instance device 200 includes at least one processor 201, a communication line 202, and at least one communication interface 204, and may also include a memory 203. The processor 201, memory 203, and communication interface 204 can be connected via the communication line 202.

[0057] The processor 201 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0058] Communication line 202 may include a path for transmitting information between the aforementioned components.

[0059] The communication interface 204 is used to communicate with other devices or communication networks and can use any transceiver-like device, such as Ethernet, radio access network (RAN), WLAN, etc.

[0060] The memory 203 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of including or storing desired program code having the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0061] In one possible design, the memory 203 can exist independently of the processor 201, meaning the memory 203 can be an external memory of the processor 201. In this case, the memory 203 can be connected to the processor 201 via a communication line 202 to store execution instructions or application code, and its execution is controlled by the processor 201 to implement the identification service example method provided in the following embodiments of this application. In another possible design, the memory 203 can also be integrated with the processor 201, meaning the memory 203 can be an internal memory of the processor 201. For example, the memory 203 can be a cache, which can be used to temporarily store some data and instruction information.

[0062] As one possible implementation, processor 201 may include one or more CPUs, for example Figure 2 CPU0 and CPU1 in the example. Alternatively, the identification service instance device 200 may include multiple processors, such as... Figure 2 The processors 201 and 207 are included. Alternatively, the identification service instance apparatus 200 may also include an output device 205 and an input device 206.

[0063] The following, in conjunction with the appendix Figure 3 The method for the identification service example provided in the embodiments of this application will be described in detail, such as... Figure 3 As shown, the method for identifying service instances includes S301-S302.

[0064] S301, The identification service instance device obtains the name of the target service chain.

[0065] The name of the target service chain includes multiple fields.

[0066] In one possible implementation, the service instance identification device obtains the name of the target service chain from the server.

[0067] It should be explained that the server includes at least one of the following: a service function chain identity (SFCID) naming rule table, an SFCID table, and a security identifier (SID) table.

[0068] For example, such as Figure 4 As shown, the server includes an SFC ID type option table, an SFC ID naming rule table, an SFC ID table, and a SID table. The SFC ID type option table includes multiple classification factors, including: the name of the service chain, the service instance called by the service chain, the description information of the service chain, and the initial account that created the service chain. The SFC ID naming rule table is used to select a preset naming rule. The SFC ID table includes the name of the service chain. The SID table includes the (IdentityDocument, ID) of the service instance.

[0069] S302, The service instance identification device determines the service instance information in the target service chain based on the name of the target service chain and the preset naming rules.

[0070] The preset naming rules are used to indicate the position of the target field corresponding to the service instance information among multiple fields.

[0071] In one possible implementation, the service instance identification device splits the name of the target service chain according to a preset naming rule to obtain the position of the target field corresponding to the service instance information among multiple fields.

[0072] It should be explained that before the service instance identification device determines the service instance information in the target service chain based on the name of the target service chain and the preset naming rules, the service instance identification device obtains the preset naming rules of the current system from the server.

[0073] In another possible implementation, the service instance identification device determines whether the name of the target service chain is valid. If the name of the target service chain is valid, it selects a preset naming rule from the server and determines the service instance information in the target service chain based on the name of the target service chain and the preset naming rule.

[0074] Optionally, the identification service instance device is located in the orchestration and scheduling layer of the computing power network architecture.

[0075] It needs to be explained that, such as Figure 5As shown, the computing network architecture includes an orchestration and scheduling layer, a cloud-network management layer, a cloud-network access layer, and an infrastructure layer. The orchestration and scheduling layer includes computing network awareness and computing network scheduling. Computing network awareness includes service awareness, computing power awareness, and network awareness. Computing network scheduling includes SFC orchestration, SFC instance management, and SID management. The network management layer includes application management and API management. Application management includes application package management, application instance management, and image management. API management includes group management, API management, policy management, and credential management. The cloud-network access layer includes network resource access and cloud resource access. The infrastructure layer includes network resources and cloud-edge computing resources.

[0076] Furthermore, in the live deployment of the computing power network, the orchestration and scheduling layer completes the functions of SFC factor identification and service SFCID creation, and can generate the optimal service link call route based on SFC service requirements, which is then distributed by the network controller to the network devices in the infrastructure layer for forwarding operations. The network awareness of the orchestration and scheduling layer is used to complete the service abstraction of computing power and the measurement and calibration of computing power.

[0077] The above solution offers at least the following advantages: In this embodiment, the service instance identification device obtains the name of the target service chain. Since preset rules are used to indicate the position of the target field corresponding to the service instance information within preset fields, the service instance identification device can obtain the target field corresponding to the service instance information from the preset fields based on the name of the target service chain and the preset rules. Therefore, the service instance identification device can identify the service instance based on the target field corresponding to the service instance information. Compared with existing technologies, the service instance identification device does not need to obtain the service instance information recorded in the service instance; it only needs to identify the service instance based on the name of the target service chain to quickly identify the service instance, thus improving the efficiency of service instance identification.

[0078] In one possible implementation, combining Figure 3 ,like Figure 6 As shown, the process of identifying service instance information in the target service chain based on the name of the target service chain and the preset naming rules can be specifically implemented through the following steps S601-S603.

[0079] S601, the service instance identification device determines the start and end identifier positions of the target field in multiple fields based on the name of the target service chain and the preset naming rules.

[0080] For example, the name of the target service chain includes S digits, the start position of the target field among multiple fields is the Mth digit, and the end position of the target field among multiple fields is the Nth digit. M is greater than or equal to 1, N is greater than M, and N is less than S.

[0081] S602, The identification service instance device obtains the target field based on multiple fields, the start identifier position, and the end identifier position.

[0082] For example, if the name of the target service chain is 2000:0000:2561:AAAA, the name of the target service chain includes 24 digits, the starting position of the target field in multiple fields is the 11th digit, and the ending position of the target field in multiple fields is the 14th digit, then the target field is 2561.

[0083] S603. The service instance identification device determines the service instance information in the target service chain based on the target field and the service instance mapping table.

[0084] The service instance mapping table includes at least one field and service instance information corresponding to each field.

[0085] For example, in the service instance mapping table, field 1 corresponds to service instance A, field 2 corresponds to service instance B, field 5 corresponds to service instance P, and field 6 corresponds to service instance Q. When the target field is 2561, the service instance information in the target service chain is: service instance A, service instance B, service instance P, and service instance Q.

[0086] Optionally, the linking order of the segments in the target field represents the linking order of the server.

[0087] The above solution brings at least the following beneficial effects: In this embodiment of the application, the service instance identification device determines the start and end positions of the target field in multiple fields based on the name of the target service chain and the preset naming rules. In this way, the service instance identification device can quickly identify the target field according to the start and end positions, thereby improving the efficiency of service instance identification.

[0088] In one possible implementation, combining Figure 3 ,like Figure 7 As shown, before the identification service instance device obtains the name of the target service chain in S301, the identification service instance device generates the name of the target service chain. The process of the identification service instance device generating the name of the target service chain can be specifically implemented through the following S701-S704.

[0089] S701, the identification service instance device receives the first request information from the terminal device.

[0090] The first request information is used to request the name of the target service chain to be generated; the first request information includes at least one first sub-request information.

[0091] It needs to be explained that the administrator generates the first request information on the control page of the terminal device, and then sends the first request information to the identification service instance device through the terminal device.

[0092] Furthermore, there are many ways for the control page to generate the first request information. For example, the control page can receive input request information from the administrator and generate the first request information based on the input request information; or the control page can receive selection request information from the administrator, select at least one target information from the components based on the selection request information, and generate the first request information based on at least one target information.

[0093] S702, the identification service instance device determines the field corresponding to each first sub-request information in at least one first sub-request information.

[0094] The first sub-request information includes any one of the following: the type information of the target service chain, the initial name of the target service chain, the service instance called by the target service chain, the description information of the target service chain, and the initial account for creating the target service chain. The description information of the target service chain includes at least one of the following: the scenario of the target service chain, the latency of the target service chain, the bandwidth of the target service chain, and the packet loss rate of the target service chain.

[0095] Optionally, the initial account creation includes the creator's identification information.

[0096] For example, the creator's identification information could be the creator's name.

[0097] In one possible implementation, the service instance identification device determines a field corresponding to each of the first sub-request information in at least one first sub-request information based on the first sub-request information in the first sub-request information and a preset relationship.

[0098] Optionally, the preset relationship includes at least one first sub-request information and at least one field corresponding to the first sub-request information.

[0099] In another possible approach, the identification service instance device performs vectorization processing on the first sub-request information in the first sub-request information to obtain at least one field corresponding to each first sub-request information in the first sub-request information.

[0100] S703, the identification service instance device determines the position of the field corresponding to each first sub-request information in the at least one first sub-request information among multiple fields based on at least one first sub-request information and a preset naming rule.

[0101] In one possible implementation, the service instance identification device determines the start and end identifier positions of the fields corresponding to each of the at least one first sub-request information in multiple fields based on at least one first sub-request information and a preset naming rule.

[0102] Optionally, the position of the field corresponding to the first sub-request information among multiple fields includes: the start identifier position, the end identifier position, and the field length.

[0103] For example, the field length is 64 bits.

[0104] S704. The service instance identification device generates the name of the target service chain based on the fields corresponding to each first sub-request information and the position of each first sub-request information in multiple fields.

[0105] Optionally, the identification service instance device generates the name of the target service chain and saves the name of the target service chain to the server.

[0106] The above solution offers at least the following advantages: In this embodiment, the service instance identification device generates the name of the target service chain based on the fields corresponding to each first sub-request information and the position of each first sub-request information within multiple fields. This allows the service instance identification device to name the service chain using a unified preset naming rule, facilitating later resolution of the service chain name.

[0107] In one possible implementation, combining Figure 3 ,like Figure 8 As shown, before the identification service instance device obtains the name of the target service chain in S301, the identification service instance device determines the target service chain. The process of the identification service instance device determining the target service chain can be specifically implemented through the following S801-S803.

[0108] S801, The identification service instance device obtains the network service quality of the target service chain.

[0109] In one possible implementation, the service instance identification device obtains the network service quality of the target service chain through a network measurement instrument.

[0110] In another possible implementation, the service instance identification device obtains the network service quality of the target service chain from the network monitoring platform.

[0111] Optionally, network service quality includes at least one of the following: latency, packet loss rate, and bandwidth.

[0112] Optionally, network service quality may also include quality of experience (QoE).

[0113] S802, The service instance identification device determines the path information of at least one service instance based on network service quality and at least one service instance.

[0114] In one possible implementation, the service instance identification device obtains at least one path between each service instance in at least one service instance, and selects the route with the best network quality from the at least one path.

[0115] For example, if the path between service instance A and service instance B includes path 1, path 2, and path 3, and the network quality of path 3 is greater than the network quality of path 1 and path 2, then the service instance identification device will take path 3 as the best route between service instance A and service instance B.

[0116] In another possible implementation, the service instance identification device determines the path information of at least one service instance based on network service quality, computing load, and at least one service instance.

[0117] S803, The service instance identification device writes the path information of at least one service instance into the header of the data packet.

[0118] In one possible implementation, the service instance identification device writes the optimal route for at least one service instance into the packet header.

[0119] Optionally, the path information for at least one service instance can be a list of SIDs.

[0120] It should be explained that the service instance identification device guides the original packet through the service instances sequentially along the specified path by adding the best route for at least one service instance to the original packet. The service instance identification device sends the original packet to the network controller, and the network controller forwards the path information of at least one service instance to each routing node.

[0121] In another possible implementation, the service instance identification device writes a chained call path using SRv6 and adds it to the packet header. Finally, SRv6 technology is used to sequentially access the services represented by each SID list. Each routing node on the path looks up its local SID list routing table based on the packet's destination address SID list or SRv6 next-hop address SID list and forwards the packet.

[0122] For example, as shown in Table 1, the associated device SID in the SID list is 2000:0000:0001:AAAA:0001:0005:0000:0000; the gateway is fd:192:168:2::2; the outgoing interface is eth1; the metric is 10; and the routing table is main.

[0123] Table 1. List of SIDs

[0124]

[0125] The above solution offers at least the following advantages: In this embodiment, the service instance identification device determines the path information of at least one service instance based on network service quality and the at least one service instance. This allows the service instance identification device to configure the optimal route for the service instance, improving the communication efficiency of the service chain.

[0126] As can be seen, the above mainly describes the technical solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, it includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, in conjunction with the modules and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this invention.

[0127] This application also provides a computer-readable storage medium storing instructions. When a computer executes these instructions, the computer performs each step of the method flow shown in the above-described method embodiments.

[0128] like Figure 9 The diagram shown is a structural schematic of an identification service instance device provided in an embodiment of this application. This identification service instance device can be used to perform... Figure 3 , Figure 6 , Figure 7 , Figure 8 The method shown is for identifying service instances. Figure 9 The identification service instance device 90 shown includes a processing unit 901 and a communication unit 902.

[0129] Processing unit 901 is used to obtain the name of the target service chain; the name of the target service chain includes multiple fields; processing unit 901 is also used to determine the service instance information in the target service chain based on the name of the target service chain and the preset naming rules; the preset naming rules are used to indicate the position of the target field corresponding to the service instance information among multiple fields.

[0130] In one possible implementation, the processing unit 901 is further configured to: determine the start and end identifier positions of the target field among multiple fields based on the name of the target service chain and a preset naming rule; obtain the target field based on the multiple fields, the start identifier position, and the end identifier position; and determine the service instance information in the target service chain based on the target field and a service instance mapping table; the service instance mapping table includes at least one field and service instance information corresponding to each field in the at least one field.

[0131] In one possible implementation, the communication unit 902 is configured to receive first request information from a terminal device; the first request information is used to request the generation of a target service chain name; the first request information includes at least one first sub-request information; the processing unit 901 is further configured to determine the fields corresponding to each of the at least one first sub-request information; the first sub-request information includes any one of the following: target service chain type information, target service chain initial name, service instance called by the target service chain, target service chain description information, and target service chain initial creation account; the processing unit 901 is further configured to determine the position of the fields corresponding to each of the at least one first sub-request information in multiple fields based on the at least one first sub-request information and a preset naming rule; the processing unit 901 is further configured to generate the name of the target service chain according to the fields corresponding to each first sub-request information and the position of each first sub-request information in multiple fields.

[0132] In one possible implementation, the communication unit 902 is further configured to receive second request information from the terminal device, the second request being used to indicate the service requirements of the terminal device; the processing unit 901 is further configured to determine a target service chain based on the service requirement information and a service requirement mapping table; the service requirement mapping table includes at least one service chain and the service requirements corresponding to at least one service chain.

[0133] In one possible implementation, the processing unit 901 is further configured to: obtain the network service quality of the target service chain; determine the path information of at least one service instance based on the network service quality and at least one service instance; write the path information of at least one service instance into the header of the data packet; the service instance information includes at least one service instance.

[0134] In one possible implementation, the descriptive information of the target service chain for identifying the service instance includes at least one of the following: the scenario of identifying the target service chain for the service instance, the latency of the target service chain for identifying the service instance, the bandwidth of the target service chain for identifying the service instance, and the packet loss rate of the target service chain for identifying the service instance.

[0135] This application also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run computer programs or instructions to implement the method for identifying service instances in the above method embodiments.

[0136] Embodiments of this application provide a computer program product containing instructions that, when executed on a computer, cause the computer to perform the method for identifying service instances as described in the above method embodiments.

[0137] The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), registers, hard disks, optical fibers, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing, or any other form of computer-readable storage medium in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may reside in an application-specific integrated circuit (ASIC). In embodiments of the present invention, a computer-readable storage medium may be any tangible medium that contains or stores a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0138] Since the apparatus, device, computer-readable storage medium, and computer program product in the embodiments of the present invention can be applied to the above methods, the technical effects that can be obtained can also be referred to the above method embodiments. The embodiments of this application will not be repeated here.

[0139] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for identifying service instances, characterized in that, The method includes: Receive first request information from a terminal device; the first request information is used to request the generation of a target service chain name; the first request information includes at least one first sub-request information; the target service chain is an IPv6-based service chain. Determine the fields corresponding to each of the at least one first sub-request information; the first sub-request information includes any one of the following: the type information of the target service chain, the initial name of the target service chain, the service instance called by the target service chain, the description information of the target service chain, and the initial creation account of the target service chain; Based on the at least one first sub-request information and the preset naming rule, the position of the field corresponding to each first sub-request information in the at least one first sub-request information in the multiple fields is determined; the preset naming rule is used to indicate the position of the target field corresponding to the service instance information in the target service chain in the multiple fields; The name of the target service chain is generated based on the fields corresponding to each first sub-request information and the position of each first sub-request information in the plurality of fields; Obtain the name of the target service chain; the name of the target service chain includes multiple fields; Based on the name of the target service chain and the preset naming rules, determine the start and end positions of the target field among the multiple fields; Based on the multiple fields, the start identifier position, and the end identifier position, obtain the target field; Based on the target field and the service instance mapping table, the service instance information in the target service chain is determined; the service instance mapping table includes at least one field and the service instance information corresponding to each of the at least one field.

2. The method according to claim 1, characterized in that, Before obtaining the name of the target service chain, the method further includes: Receive a second request from a terminal device, the second request being used to indicate the service needs of the terminal device; Based on the service demand information and the service demand mapping table, the target service chain is determined; the service demand mapping table includes at least one service chain and the service demands corresponding to the at least one service chain.

3. The method according to claim 2, characterized in that, The service instance information includes at least one service instance. After determining the service instance information in the target service chain based on the target field and the service instance mapping table, the method further includes: Obtain the network service quality of the target service chain; Based on the network service quality and the at least one service instance, determine the path information of the at least one service instance; Write the path information of the at least one service instance into the header of the data packet.

4. The method according to claim 1, characterized in that, The description information of the target service chain includes at least one of the following: the scenario of the target service chain, the latency of the target service chain, the bandwidth of the target service chain, and the packet loss rate of the target service chain.

5. An apparatus for identifying service instances, characterized in that, The device includes: a processing unit; The processing unit is configured to receive first request information from a terminal device; the first request information is used to request the generation of a target service chain name; the first request information includes at least one first sub-request information; the target service chain is an IPv6-based service chain; The processing unit is configured to determine the fields corresponding to each of the at least one first sub-request information; the first sub-request information includes any one of the following: the type information of the target service chain, the initial name of the target service chain, the service instance called by the target service chain, the description information of the target service chain, and the initial creation account of the target service chain; The processing unit is configured to determine the position of the field corresponding to each of the at least one first sub-request information in the at least one first sub-request information among multiple fields based on the at least one first sub-request information and a preset naming rule; the preset naming rule is used to indicate the position of the target field corresponding to the service instance information in the target service chain among the multiple fields; The processing unit is configured to generate the name of the target service chain based on the fields corresponding to each first sub-request information and the position of each first sub-request information in the plurality of fields; The processing unit is also used to obtain the name of the target service chain; the name of the target service chain includes multiple fields; The processing unit is further configured to determine the start and end identifier positions of the target field among the plurality of fields based on the name of the target service chain and the preset naming rules; The processing unit is further configured to obtain the target field based on the plurality of fields, the start identifier position, and the end identifier position; The processing unit is further configured to determine service instance information in the target service chain based on the target field and the service instance mapping table; the service instance mapping table includes at least one field and service instance information corresponding to each of the at least one field.

6. An apparatus for identifying service instances, characterized in that, include: A processor and a memory; wherein the memory is used to store computer execution instructions, and when the apparatus for identifying the service instance is running, the processor executes the computer execution instructions stored in the memory to cause the apparatus for identifying the service instance to perform the method of identifying the service instance as described in any one of claims 1-4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes instructions that, when executed by a device for identifying a service instance, cause the computer to perform the method for identifying a service instance as described in any one of claims 1-4.

8. A computer program product, the computer program product comprising computer instructions, characterized in that, When executed by a processor, the computer instructions implement the method of any one of claims 1-4 for the identification service instance.

Images