Method and device for identifying service instance and storage medium

Abstract

The invention discloses a method and device for identifying a service instance and a storage medium, relates to the technical field of communication, and is used for improving the identification efficiency of the service instance. The method comprises the steps of obtaining a name of a target service chain; the name of the target service chain comprises a plurality of 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 for indicating the position of a target field corresponding to the service instance information in the multiple fields. The method and the device are applied to a service instance identification process.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, device and storage medium for identifying a service instance. Background Art

[0002] The segment routing (segment routing IPv6, SRv6) service function chain (SFC) based on the Internet Protocol version 6 (IPv6) forwarding plane is a technology that guides the message to pass through the application layer service devices in sequence along the specified path by adding SRv6 path information to the original message.

[0003] In the related art, the orchestration and scheduling layer needs to obtain the information of the service instances in the service chain in order to determine the forwarding order of each service instance and write the service instance and the forwarding order of the service instance into the message. However, the way of recording the service instance information in the service instance is complicated, and the orchestration and scheduling layer needs to obtain the recording method of each instance information in order to identify the service instance. Therefore, how to improve the efficiency of identifying service instances is a technical problem that still needs to be solved. Summary of the invention

[0004] The present application provides a method, device and storage medium for identifying a service instance, which are used to improve the efficiency of identifying a service instance.

[0005] In order to achieve the above purpose, this application adopts the following technical solutions:

[0006] In the first aspect, an embodiment of the present application provides a method for identifying a service instance, where 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 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 a target field corresponding to the service instance information in multiple fields.

[0007] In a possible implementation, based on the name of the target service chain and a preset naming rule, the start identification position and the end identification position of the target field in multiple fields are determined; based on the multiple fields, the start identification position and the end identification position, the target field is obtained; 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 service instance information corresponding to each field in at least one field.

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

[0009] In one possible implementation, second request information is received from a terminal device, where the second request is used to indicate a service requirement 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 a service requirement 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 a data packet; and the service instance information includes at least one service instance.

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

[0012] In the second aspect, the present application provides a device for identifying a service instance, including: a processing unit; a processing unit for obtaining the name of a target service chain; the name of the target service chain includes multiple fields; the processing unit is also used to 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 in multiple fields.

[0013] In a possible implementation, the processing unit is also used to: determine the start identification position and the end identification position of the target field in multiple fields based on the name of the target service chain and a preset naming rule; obtain the target field based on multiple fields, the start identification position and the end identification position; determine the 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 field in at least one field.

[0014] In a possible implementation, it includes a communication unit, which is used to receive a first request information from a terminal device; the first request information is used to request the generation of a name of a target service chain; the first request information includes at least one first sub-request information; a processing unit is also used to determine the field corresponding to each first sub-request information in at least one first sub-request information; the first sub-request information includes any of the following items: type information of the target service chain, the initial name of the target service chain, the service instance called by the target service chain, description information of the target service chain, and the initial creation account of the target service chain; the processing unit is also used to determine the position of the field corresponding to each first sub-request information in at least one first sub-request information in multiple fields based on at least one first sub-request information and a preset naming rule; the processing unit is also used to generate the name of the target service chain according to the field 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 used to receive second request information from the terminal device, where the second request is used to indicate the service requirements of the terminal device; the processing unit is further used to determine the target service chain based on the service requirement information and the service requirement mapping table; the service requirement mapping table includes at least one service chain and at least one service requirement corresponding to the service chain.

[0016] In one possible implementation, the processing unit is also used 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 packet 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 of the identified service instance includes at least one of the following: identifying the scenario of the target service chain of the identified service instance, identifying the latency of the target service chain of the identified service instance, identifying the bandwidth of the target service chain of the identified service instance, and identifying the packet loss rate of the target service chain of the identified service instance.

[0018] In a third aspect, the present application provides a device for identifying a service instance, the device for identifying a service instance comprising: a processor and a memory; wherein the memory is used to store computer-executable instructions, and when the device for identifying a service instance is running, the processor executes the computer-executable instructions stored in the memory to enable the device for identifying a service instance to perform a method for identifying a service instance as described in the first aspect and any possible implementation of the first aspect.

[0019] In a fourth aspect, the present application provides a computer-readable storage medium, which stores instructions. When the instructions in the computer-readable storage medium are executed by a processor of a device for identifying a service instance, the device for identifying a service instance is able to perform a method for identifying a service instance as described in the first aspect and any possible implementation of the first aspect.

[0020] In a fifth aspect, an embodiment of the present application provides a chip, the chip including a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run a computer program or instructions to implement the method for identifying a service instance described in the above-mentioned first aspect and any possible implementation method of the first aspect.

[0021] In a sixth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the method for identifying a service instance described in the first aspect and any possible implementation of the first aspect.

[0022] These and other aspects of the present application will become more apparent from the following description.

[0023] The above scheme brings at least the following beneficial effects: In the embodiment of the present application, the service instance identification device obtains the name of the target service chain. Since the preset rule is used to indicate the position of the target field corresponding to the service instance information in the 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. Thus, the service instance identification device can identify the service instance according to 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 method of recording the service instance information in the service instance, but only needs to quickly identify the service instance according to the name of the target service chain, thereby improving the efficiency of service instance identification. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0025] Figure 1 A schematic diagram of the structure of a system for identifying a service instance provided in an embodiment of the present application;

[0026] Figure 2 A schematic diagram of the structure of a device for identifying a service instance provided in an embodiment of the present application;

[0027] Figure 3 A flowchart of a method for identifying a service instance provided in an embodiment of the present application;

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

[0029] Figure 5 A computing power network architecture diagram provided for an embodiment of the present application;

[0030] Figure 6 A flowchart of a method for identifying a service instance provided in an embodiment of the present application;

[0031] Figure 7 A flowchart of a method for identifying a service instance provided in an embodiment of the present application;

[0032] Figure 8 A flowchart of a method for identifying a service instance provided in an embodiment of the present application;

[0033] Fig. 9 A schematic diagram of the structure of a device for identifying a service instance provided in an embodiment of the present application. DETAILED DESCRIPTION

[0034] The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

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

[0036] In addition, the terms "including" and "having" and any variations thereof mentioned in the description of the present application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices.

[0037] It should be noted that, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0038] In the description of the present application, unless otherwise specified, “plurality” means two or more.

[0039] Glossary

[0040] 1. Computing network

[0041] Computing network refers to a new paradigm that uses network means to effectively allocate basic resources such as computing and storage between cloud, edge and end to provide digital technology and application integration services based on the continuous ubiquitous development of computing power. The SFC technology in the computing network originated in the field of computer networks and is an important part of the Network Function Virtualization (NFV) technology.

[0042] 2. SFC technology

[0043] The core idea of ​​SFC technology is to force the data flow to pass through a series of network service function nodes (such as firewalls, load balancers, deep packet inspection, etc.) in the process of packet forwarding according to the pre-defined service link sequence, so as to achieve orderly arrangement and deployment of network service functions. In the computing network, these network service functions can be virtualized or provided by physical devices. Through SFC technology, service functions distributed in different geographical locations and different computing nodes can be effectively connected in series to meet the requirements of business processes for network functions, while improving the utilization of network resources and business processing efficiency.

[0044] In computer networks, SFC is mainly used to define and implement the orderly delivery of network service functions. The main implementation methods include:

[0045] Tag-based forwarding: This process inserts special tags into data packets to indicate the service chain path that the data packet should follow. Policy-driven: This process defines the service chain policy in the network controller and then pushes the policy to the network device or virtual network function; API-driven: This process interacts with the high-level business orchestration system through the northbound API interface to dynamically create, modify or delete service chain instances to ensure that network functions are executed on demand and in order.

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

[0047] The SRv6 service chain based on the IPv6 forwarding plane is a technology that adds SRv6 path information to the original message to guide the message to pass through the application layer service device in sequence along the specified path.

[0048] In the related art, the orchestration and scheduling layer needs to obtain the information of the service instances in the service chain in order to determine the forwarding order of each service instance and write the service instance and the forwarding order of the service instance into the message. However, the way of recording the service instance information in the service instance is complicated, and the orchestration and scheduling layer needs to obtain the recording method of each instance information in order to identify the service instance. Therefore, how to improve the efficiency of identifying service instances is a technical problem that still needs to be solved.

[0049] In order to solve the technical problems existing in the related art, in the embodiment of the present application, the service instance identification device obtains the name of the target service chain. Since the preset rule is used to indicate the position of the target field corresponding to the service instance information in the 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. Thus, the service instance identification device can identify the service instance according to 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 method of recording the service instance information in the service instance, but only needs to quickly identify the service instance according to the name of the target service chain, thereby improving the efficiency of service instance identification.

[0050] Below, combined with the attached Figure 1 A system 10 for identifying a service instance provided in an embodiment of the present application is described in detail. Figure 1 As shown, the system 10 for identifying a service instance includes: a device 11 for identifying a service instance and a terminal device 12 .

[0051] Among them, 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; based on the name of the target service chain and a preset naming rule, determine the service instance information in the target service chain; the preset naming rule is used to indicate the position of the target field corresponding to the service instance information in multiple fields.

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

[0053] It should be noted that the terminal device 12 is a device with wireless communication function, which can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted. It can also be deployed on the water surface (such as ships, etc.). It can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.). User terminal equipment is also called mobile station (mobile station, MS), terminal equipment (mobile terminal, MT) and terminal equipment, etc., which is a device that provides voice and / or data connectivity to users. For example, terminal equipment includes handheld devices with wireless connection function, vehicle-mounted devices, etc. At present, the terminal device can be: a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device (such as a smart watch, a smart bracelet, a pedometer, etc.), a vehicle-mounted device (such as a car, a bicycle, an electric car, an airplane, a ship, a train, a high-speed train, etc.), a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal device in industrial control, a smart home device (such as a refrigerator, a television, an air conditioner, an electric meter, etc.), an intelligent robot, a workshop device, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, a flying device (such as an intelligent robot, a hot air balloon, a drone, an airplane), etc. In one possible application scenario of the present application, the terminal device 12 is a terminal device that often works on the ground, such as a vehicle-mounted device. In the present application, for the convenience of description, the chip deployed in the above-mentioned device, such as the system-on-a-chip (SOC), baseband chip, etc., or other chips with communication functions can also be referred to as user terminal devices.

[0054] Optionally, the terminal device 12 may be an embedded communication device or a user's handheld communication device, including a mobile phone, a tablet computer, etc.

[0055] As an example, in the embodiment of the present application, the terminal device 12 can also be a wearable device. Wearable devices can also be called wearable smart devices, which are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices for daily wear, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also realize powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0056] The embodiment of the present application provides a device for identifying a service instance, which is used to execute the system for identifying a service instance provided by the embodiment of the present application. Figure 2 This is a schematic diagram of the structure of a device for identifying a service instance provided in an embodiment of the present 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, the memory 203 and the communication interface 204 may 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 the present application, such as one or more digital signal processors (DSP), or one or more field programmable gate arrays (FPGA).

[0058] The communication link 202 may include a pathway for transmitting information between the above-mentioned 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 types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to include or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to these.

[0061] In one possible design, the memory 203 can exist independently of the processor 201, that is, the memory 203 can be a memory outside the processor 201. In this case, the memory 203 can be connected to the processor 201 through the communication line 202, and is used to store execution instructions or application code, and the processor 201 controls the execution to implement the method for identifying service instances provided in the following embodiments of the present application. In another possible design, the memory 203 can also be integrated with the processor 201, that is, the memory 203 can be the internal memory of the processor 201, for example, the memory 203 is a high-speed cache, which can be used to temporarily store some data and instruction information, etc.

[0062] As an implementation method, the processor 201 may include one or more CPUs, for example Figure 2 As another possible implementation, the service instance identification device 200 may include multiple processors, such as Figure 2 As another implementation, the service instance identification apparatus 200 may further include an output device 205 and an input device 206.

[0063] Below, combined with the attached Figure 3 The method for identifying a service instance provided in the embodiment of the present application is described in detail. Figure 3 As shown, the method for identifying a service instance includes S301-S302.

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

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

[0066] In a 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, 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. Among them, the SFC ID type option table includes multiple classification factors, and the multiple classification factors include: the name of the service chain, the service instance called by the service chain, the description information of the service chain, and the initial creation account of 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 (Identity document, ID) of the service instance.

[0069] S302: 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.

[0070] The preset naming rule is used to indicate the position of the target field corresponding to the service instance information in the multiple fields.

[0071] In a 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 in 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 rule, the service instance identification device obtains the preset naming rule 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, selects a preset naming rule from the server if the name of the target service chain is valid, 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 service instance identification device is located in the orchestration and scheduling layer of the computing power network architecture.

[0075] It needs to be explained that Figure 5As shown in the figure, the computing network architecture includes the orchestration and scheduling layer, the cloud network management layer, the cloud network access layer, and the infrastructure layer. The orchestration and scheduling layer includes: computing network perception and computing network scheduling. Computing network perception includes business perception, computing power perception, and network perception. 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 current deployment of computing power networks, the orchestration and scheduling layer completes the SFC factor identification and service SFCID creation functions, and can generate the best service link call route based on SFC service requirements, which is sent by the network controller to the network equipment at the infrastructure layer to perform forwarding operations. The computing network perception 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 scheme brings at least the following beneficial effects: In the embodiment of the present application, the service instance identification device obtains the name of the target service chain. Since the preset rule is used to indicate the position of the target field corresponding to the service instance information in the 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. Thus, the service instance identification device can identify the service instance according to 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 method of recording the service instance information in the service instance, but only needs to quickly identify the service instance according to the name of the target service chain, thereby improving the efficiency of service instance identification.

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

[0079] S601: The service instance identification device determines a start identification position and an end identification position of a target field in a plurality of fields based on a name of a target service chain and a preset naming rule.

[0080] Exemplarily, the name of the target service chain includes S digits, the start identification position of the target field in the multiple fields is the Mth digit, and the end identification position of the target field in the 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 service instance identification device obtains a target field based on multiple fields, a start identification position, and an end identification position.

[0082] For example, the name of the target service chain is 2000:0000:2561:AAAA, the name of the target service chain includes 24 digits, the start identification position of the target field in multiple fields is the 11th digit, and the end identification 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 in the at least one 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 sub-fields in the target field represents the linking order of the server.

[0087] The above scheme brings at least the following beneficial effects: in the embodiment of the present application, the service instance identification device determines the start identification position and the end identification position 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 identification position and the end identification position, thereby improving the efficiency of identifying the service instance.

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

[0089] S701: An apparatus for identifying a service instance receives first request information from a terminal device.

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

[0091] It should be explained that the administrator generates the first request information on the control page of the terminal device, and 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 receives input request information from the administrator and generates the first request information based on the input request information; the control page receives selection request information from the administrator, selects at least one target information from the component based on the selection request information, and generates the first request information based on the at least one target information.

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

[0094] The first sub-request information includes any 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. The description information of the target service chain includes at least one of the following: scenario of the target service chain, latency of the target service chain, bandwidth of the target service chain, and packet loss rate of the target service chain.

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

[0096] Exemplarily, the identification information of the creator may be the name of the creator.

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

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

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

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

[0101] In a possible implementation, the service instance identification device determines the start marker position and the end marker position of the field corresponding to each first sub-request information in the at least one first sub-request information in the multiple fields based on the 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 in the multiple fields includes: a start marker position, an end marker position, and a field length.

[0103] Exemplarily, the field length is 64 bits.

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

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

[0106] The above scheme brings at least the following beneficial effects: In the embodiment of the present application, the service instance identification device generates the name of the target service chain according to the field corresponding to each first sub-request information and the position of each first sub-request information in multiple fields. In this way, the service instance identification device uses a unified preset naming rule to name the service chain, so as to facilitate the subsequent parsing of the service chain name.

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

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

[0109] In a possible implementation, the service instance identification device obtains the network service quality of the target service chain through a network measuring 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, the network service quality includes at least one of the following: latency, packet loss rate, and bandwidth.

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

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

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

[0115] Exemplarily, 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 the network quality of path 2, the service instance identification device uses path 3 as the optimal route between service instance A and service instance B.

[0116] In another possible implementation, the service instance identification device determines 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 a possible implementation, the service instance identification device writes the best route of at least one service instance into a header of a data packet.

[0119] Optionally, the path information of at least one service instance may be a SID list.

[0120] It should be explained that the service instance identification device guides the original message to pass through the service instance in sequence along the specified path by adding the best route of at least one service instance in the original message. The service instance identification device sends the original message 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 the chain call path into the packet header using SRv6, and finally uses SRv6 technology to access the services represented by each SID list in turn. Each routing node on the path searches the local SID list routing table for forwarding based on the destination address SID list or the SRv6 next hop address SID list of the packet.

[0122] Exemplarily, 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. SID list

[0124]

[0125] The above scheme brings at least the following beneficial effects: In the embodiment of the present application, the service instance identification device determines the path information of at least one service instance based on the network service quality and at least one service instance. In this way, the service instance identification device can configure the best route for the service instance and improve the communication efficiency of the service chain.

[0126] It can be seen that the technical solution provided by the embodiment of the present application is introduced above mainly from the perspective of the method. In order to realize the above functions, it includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should be easily aware that, in combination with the modules and algorithm steps of each example described in the embodiment disclosed herein, the embodiment of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0127] An embodiment of the present application also provides a computer-readable storage medium, in which instructions are stored. When a computer executes the instructions, the computer executes each step in the method flow shown in the above method embodiment.

[0128] like Fig. 9 FIG. 1 is a schematic diagram of a structure of a device for identifying service instances provided in an embodiment of the present application. The device for identifying service instances can be used to perform Figure 3 , Figure 6 , Figure 7 , Figure 8 The method for identifying a service instance is shown. Fig. 9 The service instance identification 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 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 multiple fields.

[0130] In a possible implementation, the processing unit 901 is also used to: determine the start identifier position and the end identifier position of the target field in multiple fields based on the name of the target service chain and a preset naming rule; obtain the target field based on multiple fields, the start identifier position and the end identifier position; determine the 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 field in at least one field.

[0131] In a possible implementation, the communication unit 902 is used to receive a first request message from a terminal device; the first request message is used to request generation of a name of a target service chain; the first request message includes at least one first sub-request message; the processing unit 901 is also used to determine the field corresponding to each first sub-request message in at least one first sub-request message; the first sub-request message includes any of the following items: 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 901 is also used to determine the position of the field corresponding to each first sub-request message in at least one first sub-request message in multiple fields based on at least one first sub-request message and a preset naming rule; the processing unit 901 is also used to generate the name of the target service chain according to the field corresponding to each first sub-request message and the position of each first sub-request message in multiple fields.

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

[0133] In one possible implementation, processing unit 901 is also used 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 packet 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 of the identified service instance includes at least one of the following: identifying the scenario of the target service chain of the identified service instance, identifying the latency of the target service chain of the identified service instance, identifying the bandwidth of the target service chain of the identified service instance, and identifying the packet loss rate of the target service chain of the identified service instance.

[0135] An embodiment of the present application also provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run a computer program or instruction to implement the method for identifying a service instance in the above method embodiment.

[0136] An embodiment of the present application provides a computer program product including instructions. When the instructions are executed on a computer, the computer is enabled to execute the method for identifying a service instance in the above method embodiment.

[0137] Among them, the computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable computer disk, and a hard disk. Random Access Memory (RAM), Read-Only Memory (ROM), Erasable Programmable Read Only Memory (EPROM), registers, hard disks, optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any other form of computer-readable storage medium in a suitable combination of the above, or numerical values ​​in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an Application Specific Integrated Circuit (ASIC). In embodiments of the present invention, computer-readable storage media may be any tangible media 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-mentioned method, the technical effects that can be obtained can also refer to the above-mentioned method embodiments, and the embodiments of the present application will not be repeated here.

[0139] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for identifying a service instance, characterized in that: The method comprises: Obtaining a name of a target service chain; the name of the target service chain includes multiple fields; Based on the name of the target service chain and a preset naming rule, the service instance information in the target service chain is determined; the preset naming rule is used to indicate the position of the target field corresponding to the service instance information in the multiple fields.

2. The method according to claim 1, characterized in that The determining, based on the name of the target service chain and a preset naming rule, service instance information in the target service chain includes: Based on the name of the target service chain and the preset naming rule, determining a start identification position and an end identification position of the target field in the multiple fields; Based on the multiple fields, the start marker position and the end marker position, acquiring 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 service instance information corresponding to each field in the at least one field.

3. The method according to claim 1, characterized in that: Before obtaining the name of the target service chain, the method further includes: Receiving a first request message from a terminal device; the first request message is used to request generation of a name of a target service chain; the first request message includes at least one first sub-request message; Determine a field corresponding to each first sub-request information in the at least one first sub-request information; the first sub-request information includes any one of the following: type information of the target service chain, an initial name of the target service chain, a service instance called by the target service chain, description information of the target service chain, and an initial creation account of the target service chain; Based on the at least one first sub-request information and the preset naming rule, determining a position of a field corresponding to each first sub-request information in the at least one first sub-request information in the plurality of fields; 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 the multiple fields.

4. The method according to claim 1, characterized in that: Before obtaining the name of the target service chain, the method further includes: receiving second request information from a terminal device, where the second request is used to indicate a service requirement of the terminal device; The target service chain is determined based on the service demand information and a service demand mapping table; the service demand mapping table includes at least one service chain and a service demand corresponding to the at least one service chain.

5. The method according to claim 4, characterized in that The service instance information includes at least one service instance. After determining the service instance in the target service chain based on the name of the target service chain and a preset naming rule, the method further includes: Obtaining the network service quality of the target service chain; Determining path information of the at least one service instance based on the network service quality and the at least one service instance; The path information of the at least one service instance is written into the header of the data packet.

6. The method according to claim 3, 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.

7. A device for identifying a service instance, characterized in that: The device comprises: a processing unit; The processing unit is used to obtain a name of a target service chain; the name of the target service chain includes multiple fields; The processing unit is further used to 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 in the multiple fields.

8. A device for identifying a service instance, characterized in that: include: A processor and a memory; wherein the memory is used to store computer-executable instructions, and when the device for identifying a service instance is running, the processor executes the computer-executable instructions stored in the memory to enable the device for identifying a service instance to perform the method for identifying a service instance described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes instructions, which, when executed by a device for identifying a service instance, cause the computer to perform the method for identifying a service instance according to any one of claims 1 to 6.

10. A computer program product, comprising computer instructions, characterized in that: When the computer instructions are executed by a processor, the method for identifying a service instance according to any one of claims 1 to 6 is implemented.

Images