Communication method and device of service aware network and communication equipment
Through the combination of service identification and flow identification, differentiated distinction of network quality requirements for different sub-services is achieved, and the problem of poor communication flexibility in the existing technology is solved, network services with unified perception and differentiated service quality are provided, and network services are improved. Network resource utilization and solution simplification.
Patent Information
- Application Number
- CN202310512716.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-08
- Publication Date
- 2024-11-08
AI Technical Summary
The prior art cannot differentiate network quality requirements for different subservices, and has poor communication flexibility and cannot meet the differences in network quality requirements for different sessions (such as voice and images).
By designing a combination of service identification and flow identification, multiple flow identifications are associated with service identification. Each flow identification corresponds to different network quality requirements, achieving flexible perception and scheduling of multiple service types, providing unified perception and differentiated service quality Internet services.
It realizes the differentiated service quality requirements of different subservices under the same service type, maximizes network resource utilization, saves identification resource space, simplifies solutions, and has strong implementation and scalability.
Smart Images

Figure CN118921398A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a communication method, apparatus and communication equipment of a Service Awareness Network (SAN). Background Art
[0002] The computing power network technology in related technologies generally adopts anycast address as a unified identifier of computing power and network services, uses the network to perceive computing power and implement routing and services, and realizes layer 3 (L3) load balancing at the network level. Most computing power service instances (such as cloud desktops, extended reality XR, virtual reality VR, etc.) are usually based on multiple sub-services of different Transmission Control Protocol (TCP) / User Datagram Protocol (UDP) ports under specific IPs for external release, and different sub-services are accessed through different ports for session access.
[0003] However, the above solutions have the following problems: different sessions under service instances (such as voice and image) have different requirements for network quality. Technical load balancing such as L3 Domain Name System (DNS) or ComputeFirst Networking (CFN) only provides unified network quality for all sessions under a specific IP, such as the Service Level Agreement (SLA). It is impossible to differentiate the network quality requirements for different sub-services, and the communication flexibility is poor. Summary of the invention
[0004] The purpose of the embodiments of the present application is to provide a communication method, apparatus and communication equipment for a service-aware network, which can solve the problem of being unable to differentiate network quality requirements for different sub-services and poor communication flexibility.
[0005] To solve the above technical problems, the embodiments of the present application are implemented through the following aspects.
[0006] In a first aspect, an embodiment of the present application provides a communication method for a service-aware network, comprising: a first network device receives a session message, the session message includes a first identifier, the first identifier includes a service identifier and a target flow identifier; the first network device performs flow diversion processing on the session message based on the first identifier; wherein the service identifier is associated with at least one flow identifier, the target flow identifier belongs to the at least one flow identifier, and at least two different flow identifiers correspond to different network quality requirements.
[0007] In a second aspect, an embodiment of the present application provides a communication method for a service-aware network, comprising: a terminal sends a session message, the session message includes a first identifier, the first identifier includes a service identifier and a target flow identifier; wherein the service identifier is associated with at least one flow identifier, the target flow identifier belongs to the at least one flow identifier, and at least two different flow identifiers correspond to different network quality requirements.
[0008] In a third aspect, an embodiment of the present application provides a communication method for a service-aware network, comprising: a second network device triggers a first network device to generate a SAN traffic engineering northbound policy configuration; wherein the SAN traffic engineering northbound policy configuration comprises: a service identifier; at least one flow identifier associated with the service identifier; network quality requirement information corresponding to the flow identifier, wherein at least two different flow identifiers correspond to different network quality requirements.
[0009] In a fourth aspect, an embodiment of the present application provides a communication device of a service-aware network, comprising: a receiving module, used to receive a session message, the session message comprising a first identifier, the first identifier comprising a service identifier and a target flow identifier; a processing module, used to perform flow diversion processing on the session message based on the first identifier; wherein the service identifier is associated with at least one flow identifier, the target flow identifier belongs to the at least one flow identifier, and at least two different flow identifiers correspond to different network quality requirements.
[0010] In the fifth aspect, an embodiment of the present application provides a communication device of a service-aware network, including: a sending module, used to send a session message, the session message including a first identifier, the first identifier including a service identifier and a target flow identifier; wherein the service identifier is associated with at least one flow identifier, the target flow identifier belongs to the at least one flow identifier, and at least two different flow identifiers correspond to different network quality requirements.
[0011] In the sixth aspect, an embodiment of the present application provides a communication device for a service-aware network, including: a sending module, used to trigger a first network device to generate a SAN traffic engineering northbound policy configuration; wherein the SAN traffic engineering northbound policy configuration includes: a service identifier; at least one flow identifier associated with the service identifier; network quality requirement information corresponding to the flow identifier, and at least two different flow identifiers have different network quality requirements.
[0012] In the seventh aspect, an embodiment of the present application provides an electronic device, comprising: a memory, a processor, and computer executable instructions stored in the memory and executable on the processor, wherein the computer executable instructions, when executed by the processor, implement the steps of executing the method described in the first aspect, the second aspect, or the third aspect.
[0013] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store computer-executable instructions. When the computer-executable instructions are executed by a processor, the steps of the method described in the first aspect, the second aspect or the third aspect are implemented.
[0014] The communication method of the service-aware network provided in the embodiment of the present application can realize flexible perception and scheduling of multiple service types by designing a combination of service identifiers and flow identifiers and different flow identifiers corresponding to different network quality requirements, and can also realize differentiated service quality requirements of different sub-services under the same service type, thereby providing network service capabilities with unified perception and differentiated service quality, maximizing the utilization of network resources, and the service-aware network has a good implementation foundation and significant practical value; at the same time, it can also save identification resource space, realize solution simplification, and have strong feasibility and scalability. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.
[0016] Figure 1 A schematic diagram showing a flow chart of a communication method of a service-aware network provided in an embodiment of the present application;
[0017] Figure 2 A schematic diagram showing a service identification segmentation of a communication method of a service-aware network provided in an embodiment of the present application;
[0018] Figure 3 A diagram illustrating service requirements of a communication method of a service-aware network provided in an embodiment of the present application;
[0019] Figure 4 A schematic diagram showing the system architecture composition and operation of the communication method of the service-aware network provided in an embodiment of the present application;
[0020] Figure 5 A schematic diagram showing service registration information of a communication method of a service-aware network provided in an embodiment of the present application;
[0021] Figure 6 A schematic diagram showing a service information list of an ingress gateway node of a communication method of a service-aware network provided in an embodiment of the present application;
[0022] Figure 7A schematic diagram showing service instance registration information of a communication method of a service-aware network provided in an embodiment of the present application;
[0023] Figure 8 A schematic diagram showing the SFIB generation relationship of the communication method of the service-aware network provided in an embodiment of the present application;
[0024] Fig. 9 A schematic diagram showing a terminal using a service in a communication method of a service-aware network provided in an embodiment of the present application;
[0025] Fig.10 A comparative illustration of existing conventional identification schemes is shown;
[0026] Fig.11 A schematic diagram showing a flow chart of a communication method of a service-aware network provided in an embodiment of the present application;
[0027] Fig.12 A schematic diagram showing a flow chart of a communication method of a service-aware network provided in an embodiment of the present application;
[0028] Fig.13 A schematic diagram showing the structure of a communication device of a service-aware network provided in an embodiment of the present application;
[0029] Fig.14 A schematic diagram showing the structure of a communication device of a service-aware network provided in an embodiment of the present application;
[0030] Fig.15 A schematic diagram showing the structure of a communication device of a service-aware network provided in an embodiment of the present application;
[0031] Fig.16 A schematic diagram of the hardware structure of an electronic device for executing the communication method of the service-aware network provided in an embodiment of the present application. DETAILED DESCRIPTION
[0032] In order to enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.
[0033] Figure 1A flow chart of a communication method of a service-aware network provided in an embodiment of the present application is shown, and the method can be executed by a first network device. In other words, the method can be executed by software or hardware installed in the first network device. The first network device includes but is not limited to an ingress gateway (abbreviated as IGW), etc. Figure 1 As shown, the method may include the following steps.
[0034] S102: The first network device receives a session message, where the session message includes a first identifier, and the first identifier includes a service identifier and a target flow identifier.
[0035] The first network device in this embodiment may be an ingress gateway, and the session message may come from a terminal.
[0036] Optionally, the session message may also include at least one of the following: the destination IP address of the service instance corresponding to the service identifier; the port information associated with the target flow identifier. Before S102, the first network device may also provide the terminal with the destination IP address of the service instance, the port information associated with the target flow identifier, etc., which are stored locally by the terminal. Since the terminal side can obtain the correspondence between the port (or port + content) and the flow, the possibility of programming errors such as service definition adjustment and agreed protocol errors is avoided, thereby improving communication reliability.
[0037] Optionally, before the first network device receives the session message, the method also includes: the first network device receives a service request message (from the terminal), the service request message including the service identifier; the first network device sends a service response message (to the terminal), the service response message including at least one of the following: the at least one flow identifier associated with the service identifier; the port information associated with each of the flow identifiers (of course including the port information associated with the target flow identifier); the destination IP address of the service instance corresponding to the service identifier.
[0038] Optionally, the method further includes: the first network device obtains an information table; wherein the information table is used for service request processing and lookup, and the information table includes: the at least one flow identifier associated with the service identifier; and port information associated with each of the flow identifiers. In this way, when the first network device receives a service request message from a terminal, it can provide the terminal with the at least one flow identifier associated with the service identifier; and port information associated with each of the flow identifiers, etc. based on the above information table.
[0039] Optionally, the first identifier also includes a service type identifier; wherein one service type identifier corresponds to at least one service identifier.
[0040] Optionally, the service type identifier may be used to indicate one of the following:
[0041] 1) L3 service, wherein the service identifier is associated with a flow identifier (ie, a target flow identifier), the session message further includes a destination IP address of a service instance corresponding to the service identifier, and the L3 service does not distinguish between all sessions under the destination IP address.
[0042] 2) L4 service, wherein the service identifier is associated with at least one flow identifier, and different flow identifiers represent different network quality requirements corresponding to sessions corresponding to different ports or port combinations.
[0043] 3) L7 service, wherein the service identifier is associated with at least one flow identifier, and different flow identifiers represent different network quality requirements corresponding to application-level content transmission with different combinations of port and content identifiers.
[0044] 4) Network as a service (NAAS), wherein the target flow identifier is invalid.
[0045] It should be noted that, in some examples, the first identifier may include only the service identifier but not the flow identifier, or the first identifier includes the service identifier and the target flow identifier, but the target flow identifier is invalid. This example is mainly applicable to the NAAS service scenario.
[0046] S104: The first network device performs flow diversion processing on the session message based on the first identifier; wherein the service identifier is associated with at least one flow identifier, the target flow identifier belongs to the at least one flow identifier, and at least two different flow identifiers correspond to different network quality requirements.
[0047] In this embodiment, the service identifier can be associated with at least one flow identifier, and the target flow identifier is one of the at least one flow identifier. In the case where the service identifier is associated with at least two flow identifiers, at least two different flow identifiers correspond to different network quality requirements, for example, different flow identifiers correspond to different network quality requirements, thereby achieving differentiated service quality requirements for different sub-services under the same service type (i.e., the same service identifier).
[0048] Optionally, the above network quality requirements may include service level agreement (SLA) service quality, including but not limited to requirements such as bandwidth, delay, jitter, and packet loss.
[0049] Optionally, in this step, the first network device may perform flow diversion processing on the session message based on the first identifier and a service-aware network forwarding information base (SAN forwarding information base, SFIB). The SFIB includes at least one of the following: a combination of the service identifier and the target flow identifier; a destination IP address of a service instance corresponding to the service identifier; an IP address of a service egress gateway; and segment routing policy information (SR POLICY).
[0050] Optionally, Figure 1 The illustrated embodiment also includes the following steps: the first network device generates a SFIB based on the SAN traffic engineering northbound policy configuration and computing power information and updates it to the forwarding plane.
[0051] The SAN traffic engineering northbound policy configuration may include at least one of the following: the service identifier; the target flow identifier; information indicating whether the target flow identifier participates in joint calculation; network quality requirement information corresponding to the target flow identifier; and the IP address of the first network device node.
[0052] The computing power information may include at least one of the following: the service identifier; the destination IP address of the service instance corresponding to the service identifier; the IP address of the service export gateway; and the measurement value of the computing power resources connected to the service export gateway.
[0053] The communication method of the service-aware network provided in the embodiment of the present application can realize flexible perception and scheduling of multiple service types by designing a combination of service identifiers and flow identifiers and different flow identifiers corresponding to different network quality requirements, and can also realize differentiated service quality requirements of different sub-services under the same service type, thereby providing network service capabilities with unified perception and differentiated service quality, maximizing the utilization of network resources, and the service-aware network has a good implementation foundation and significant practical value; at the same time, it can also save identification resource space, realize solution simplification, and have strong feasibility and scalability.
[0054] To explain in detail the communication method of the service-aware network provided in the embodiment of the present application, the following will further explain it in two parts: service identifier design and service identifier usage.
[0055] 1. Service Logo Design
[0056] refer to Figure 2In the embodiment of the present application, the 128-bit identification (ID) space can be divided into two sections, the first section is the service section (SAN-ID, referred to as SID), and the second section is used for the flow identification section (FID). The SID at least includes but is not limited to the reserved field, service type, and service identification (ID); the FID at least includes but is not limited to the flow identification and reserved field.
[0057] SID is an abstract identifier for a specific service type, and is used for unique indexing of service registration, service status, service routing, service subscription, and service initiation. FID is a unique index for the traffic engineering attributes and service indicators of the corresponding subservice. Depending on the corresponding service, there may be one or more flow identifiers under a specific service identifier.
[0058] According to the service identification design constraints, the allocation of SID is negotiated between the cloud service operator and the operator and has the global uniqueness. FID has local semantics and can be flexibly adjusted through planning and negotiation. The relevant usage process is explained as follows.
[0059] Service segment (SID): As a global semantic identification field, it is an abstract identification of similar services and has the global uniqueness of the computing network domain. The reserved fields are reserved for subsequent expansion; the service type field is used to identify the relevant service type (including but not limited to L3 services, L4 services, L7 services, NAAS services), which may involve differentiated system processing logic for service processing; the service identification field is used to identify the abstract identification of the service under a specific service type.
[0060] Flow Identification Segment (FID): It has local semantics based on a specific SID and is used to distinguish different network SLA service qualities (including but not limited to bandwidth, latency, jitter, and packet loss) under a specific SID. The reserved field is used for subsequent expansion; the FID field is used to carry the SID in combination when the terminal is conducting a session, and is mainly used for differentiated network service diversion.
[0061] The service identifier provided in this embodiment has the following identification capabilities:
[0062] 1) L3 service: There is only one FID under a specific L3 service SID. L3 service does not distinguish all sessions under IP.
[0063] 2) Identify L4 services. There is one or more FIDs under a specific L4 service SID. Different FIDs represent the differentiated network quality requirements of sessions (groups) corresponding to different ports or port combinations.
[0064] 3) Identify L7 services. There is one or more FIDs under the SID. Different FIDs represent different network quality requirements corresponding to application-level content transmission with different combinations of port and content identifiers.
[0065] 4) Identify the NAAS service, which does not involve computing power awareness. It is distinguished by SID, and the FID field is invalid.
[0066] The introduction of the above L3 services, L4 services, L7 services and NAAS services is as follows: Figure 3 shown.
[0067] 2. Use of Service Logo
[0068] The use of service identification includes the service provision and access process, involving three components: terminal, network, and cloud side. Figure 4 ,The overall mechanism and process are described in the following eight parts.
[0069] (1) Service Registration
[0070] Service registration is initiated by the cloud side to the network side's computing brain, and the relevant content is received and processed by the computing brain.
[0071] The cloud side can send registration information to the operator's computing brain. The computing brain registers the FID list information under the service based on the received SID and FID list information, with SID as the index, including the mapping relationship between each FID and its corresponding network quality requirements (including but not limited to bandwidth, latency, jitter, packet loss, etc.), service ports, content identifiers, etc. The computing brain sends the SID and the port list corresponding to the FID to the service entry gateway (abbreviated as IGW) and service exit gateway (EGW).
[0072] refer to Figure 5 Taking the fourth layer service (T2) as an example, the registration information obtained by the network brain is as follows Figure 5 As shown, the flow identifiers mapped to SLA21 and SLA22 are F21 and F22 respectively, and F21 needs to participate in the joint computing decision of the computing network for computing power selection. Figure 5 port1) and 3( Figure 5 Port 2) is connected using F21 corresponding to the flow processing SLA network quality requirements, port 2 ( Figure 5 The port 2) connection adopts F22 corresponding to the flow processing SLA network quality requirements.
[0073] (2) Configuration policy delivery
[0074] After receiving a legitimate service registration request, the computing network brain generates a related service database record and sends it to IGW00 according to the specific service SID and FID associated port list. IGW00 (corresponding to the first network device in the previous embodiment) generates a SID, FID and port correspondence table (corresponding to the information table in the previous embodiment).
[0075] like Figure 6 As shown, the number of entries recorded in the information table is only related to the number of service identifiers (SIDs), and has nothing to do with the number of service instances. SIDs are used as indexes for search, which supports efficient storage and variable-length management. This is not described here. The information table is used for service request processing, search, and response, see subsequent steps (7) and (8).
[0076] (3) Service instance registration
[0077] Based on the cloud resource deployment, the cloud side registers the SID, service IP address, and service egress gateway EGW IP address corresponding to each service instance with the computing network brain. Based on the registration information, the computing network brain converts the network quality requirements associated with the SID and FID into SAN traffic engineering (TE) policy northbound configuration and sends it to the relevant IGW and EGW. At the same time, the cloud side starts the corresponding resource monitoring health and updates the service instance health status to the EGW.
[0078] When adding a new service instance, follow Figure 7 Schematic content, the cloud side registers with the computing network brain according to different service types. The registration elements include the service instance IP, service gateway IP, etc. Figure 7 As shown in the figure, the computing network brain triggers the generation of the corresponding SAN traffic engineering (TE) policy northbound configuration on IGW00 based on the registered service instance and gateway IP information.
[0079] (4) Service status perception
[0080] After receiving a normal response from the computing network brain service instance registration, the cloud-side management system starts monitoring the service instance and periodically refreshes the computing power status to the EGW01 or EGW02 gateway. The service instance status information is expanded to the IGW00 gateway through the SRv6 bearer network.
[0081] (5) Service route generation
[0082] After sensing the status of the service instance, the EGW extends its health information to the entire network through the bearer network. Each IGW triggers the generation of service routing and forwarding tables according to the northbound configuration of the SAN traffic engineering policy generated by the corresponding SAN-ID registration and registration. Specifically, the IGW uses the local distributed algorithm or the centralized routing capability of the computing network brain to generate a traffic forwarding table for a specific SID and its flexible combination of multiple FIDs, namely the Service-Aware Network Forwarding Information Base (SFIB), based on the routing reachability and service instance health indicators and the northbound configuration of the SAN traffic engineering policy.
[0083] In this process, the IGW00 gateway forms a computing power information table and updates the status based on the received computing power information. Its update cycle depends on the speed at which the cloud-side monitoring system notifies the network side. Figure 8,Based on the local SAN traffic engineering northbound configuration policy and computing power information table, the SAN-TE module of the IGW00 gateway performs traffic engineering calculations according to relevant constraints and generates SFIB updates to the forwarding plane for SAN service provision and traffic forwarding.
[0084] (6) Obtaining service identification
[0085] The terminal subscribes to the service identifier from the computing network brain. When the identifier that meets the subscription conditions exists and is updated, the service identifier SID will be responded to the terminal.
[0086] The following will introduce the service access process. Service access includes two main stages: service request and service call. To avoid repeated development, a specific development library is encapsulated in the application layer to hide the implementation details, maintain the consistency of the terminal programming interface, avoid the workload caused by modifications on the other side (including the client and the server), and reduce the chance of system errors.
[0087] (7) Service Request
[0088] By extending the simple request and response protocol, the terminal sends a service request message to the IGW based on the SID. The IGW obtains at least one of the following responses based on the table lookup: the destination IP address of the service instance corresponding to the SID; the mapping information between the SID and the FID, and the port information associated with each FID. After receiving the above information, the terminal caches it locally for connection session initiation. Since the terminal obtains the specific destination IP address information, the subsequent network does not need to maintain the specific session flow affinity information of the session, realizing the stateless network.
[0089] Specifically, please refer to Fig. 9 In the service initiation process, the terminal uses SID to initiate a service request (SAN-REQ) to IGW00, carrying SID2; IGW00 queries SFIB for service instance information according to SID2 based on the service request, and responds to the terminal with a service response (SAN-RSP) message with the specific IP12, together with the flow identifiers F21 and F22 associated with SID2, and the port information associated with F21 and F22.
[0090] (8) Service call
[0091] The terminal uses the service instance IP as the destination IP, uses the port (or content) to search for the corresponding FID based on the local cache, and carries the SAN-ID composite identifier of the SID|FID combination (corresponding to the first identifier of the previous embodiment) for different connections. The carrying method carries the combined SAN-ID through the IPv6 extension header, and implements differentiated network service quality assurance by parsing the SAN-ID identifier through the data plane.
[0092] refer to Fig. 9,After completing the services SAN-REQ and SAN-RSP, the terminal uses IP12 as the destination address, searches for the ,related FID according to the sub-service port, encapsulates the SID diversion identifier SID2|FID21, establishes a real session connection, and sends ,the session message to IGW00.
[0093] IGW00 receives a message carrying SID. Based on the combination of message SID and flow identifier, SID2|FID21 or SID2|FID22 queries the SFIB table to direct the message to different SR-POLICY-F21 / SR-POLICY-F22 to provide differentiated service quality.
[0094] The embodiments of the present application are applicable to innovative enhancements of service-aware networks based on IPv6 networks. The key points of the method are summarized as follows: Under the SAN architecture, the SAN service identifier (SID for short) can be used as both a service routable ID and an interface for service requirements and service-related cloud resources.
[0095] In order to expand the service scope and differentiate the network quality requirements of sub-services, the embodiment of the present application divides the SAN-ID space into a service identification segment (SID for short) and a flow identification segment (FID for short) under a limited ID space, where SID is used to identify different service types and service IDs, and FID is used to identify the network quality SLA requirements of a specific sub-service or sub-service set under the SID service. While increasing the scope of services (covering L3-L7 and network services), natural atomic service aggregation and differentiated network quality differentiation are achieved, and flexible planning and adjustment of service quality can be performed, reducing the complexity of the system and improving the scalability.
[0096] Different from other existing proposed methods, the service identification design described in the embodiments of the present application has the following obvious characteristics:
[0097] 1) In a limited service identification space, the service scope is expanded by defining and extending it according to the service type. Other similar solutions often have service identification IDs that only represent IP, IP+port services or network services, and their service scope expansion capabilities are limited.
[0098] 2) The identification space is divided into two segments, SID and FID. SID is used to abstractly identify computing power and select service instances, and combined with multiple FIDs under the service to carry network traffic, so as to achieve service identification aggregation and differentiated network quality provision. The existing scheme uses a single service identification to map service instances and network quality requirements at the same time, which limits the scalability of identification, wastes identification resources for complex services, and increases the complexity of device configuration and computing power modeling.
[0099] The specific implementation of the existing solution is as follows Fig.10As shown, there are many solutions for directly using the ports of different sub-services to define atomic services and then aggregating them. There are generally problems such as complex design, complex configuration, and horizontal expansion. The embodiments of the present application can solve the above problems.
[0100] 3) Initiate service requests uniformly based on SID identification to obtain the real service instance IP and the correspondence table between FID and port. When different TCP / UDP and other sub-service sessions are initiated, the service identification (SID|FID) is searched and carried according to different ports, which reduces the probability of corresponding errors between sub-services and identifications. At the same time, it realizes stateless forwarding of network nodes and differentiated network service capabilities for different sub-services under the same service.
[0101] In the related art, the first packet of the ANYCAST solution guides the service instance selection through the anycast address. Since the computing power routing of the network node is updated in real time according to the computing power status, the subsequent packets may be forwarded to other service instances at the network node after the table lookup, causing the current service interruption. To solve this problem, the flow affinity table is introduced into the network device to search and forward the subsequent packets, resulting in complex problems such as flow table resource overhead and network status. The embodiments of the present application can solve the above problems.
[0102] From the perspective of beneficial effects, compared with existing technologies and solutions, the overall advantage of the embodiments of this application is that it uses a limited global service identification space and range to meet the demand for service differentiation, and has strong feasibility, adaptability to different scenarios, and scalability. The technical solution of the embodiments of this application can accelerate the rapid implementation of the service-aware network in the existing network environment. Specifically, there are four points:
[0103] 1) Based on the service segment and flow identification segment model, it supports arbitrary extension of service types and satisfies the aggregation of natural atomic services, simplifying the complex aggregation configuration and computing power routing design of services.
[0104] 2) Based on the combined service identification design, the horizontal expansion of flow identification is realized, and the identification space is compact and has good feasibility.
[0105] 3) It realizes complete decoupling of SAN diversion and Layer 4 port flow, avoiding complex QOS to DSCP mapping configuration. Its service quality model is completely determined by service registration decisions and supports dynamic adjustment, which reduces network configuration efficiency and complexity, and saves resources and costs.
[0106] 4) The terminal side obtains the correspondence between the port (or port + content) and the stream, avoiding possible programming errors such as service definition adjustment and agreement error.
[0107] It should be noted that the above embodiments are described using SRV6 as a bearer network, and the length of the first identifier is designed to be 128 bits. In fact, the various embodiments of the present application are also applicable to Multi-Protocol Label Switching (MPLS) networks, etc., and the length of the first identifier is not limited to 128 bits, and can be flexibly designed as needed.
[0108] Combination of the above Figures 1 to 10 The communication method of the service-aware network according to the embodiment of the present application is described in detail. Fig.11 combine Fig.12 The communication method of the service-aware network according to the embodiment of the present application is described in detail. It can be understood that the description of the terminal side and the second network device side is the same as Figures 1 to 10 The description of the first network device side in the method shown is the same or corresponding, and to avoid repetition, the relevant description is appropriately omitted.
[0109] Fig.11 This is a schematic diagram of the communication method implementation flow of the service-aware network of the embodiment of the present application, which can be applied on the terminal side. Fig.11 As shown, the method 1100 includes the following steps.
[0110] S1102: The terminal sends a session message, wherein the session message includes a first identifier, wherein the first identifier includes a service identifier and a target flow identifier; wherein the service identifier is associated with at least one flow identifier, the target flow identifier belongs to the at least one flow identifier, and at least two different flow identifiers correspond to different network quality requirements.
[0111] The communication method of the service-aware network provided in the embodiment of the present application can realize flexible perception and scheduling of multiple service types by designing a combination of service identifiers and flow identifiers and different flow identifiers corresponding to different network quality requirements, and can also realize differentiated service quality requirements of different sub-services under the same service type, thereby providing network service capabilities with unified perception and differentiated service quality, maximizing the utilization of network resources, and the service-aware network has a good implementation foundation and significant practical value; at the same time, it can also save identification resource space, realize solution simplification, and have strong feasibility and scalability.
[0112] Optionally, as an embodiment, the session message further includes: a destination IP address of a service instance corresponding to the service identifier.
[0113] Optionally, as an embodiment, before the terminal sends a session message, the method also includes: the terminal sends a service request message, the service request message includes the service identifier; the terminal receives a service response message, the service response message includes at least one of the following: at least one flow identifier associated with the service identifier; port information associated with each of the flow identifiers; and the destination IP address of the service instance corresponding to the service identifier.
[0114] Optionally, as an embodiment, the first identifier also includes a service type identifier; wherein one service type identifier corresponds to at least one service identifier.
[0115] Optionally, as an embodiment, the service type identifier is used to indicate one of the following:
[0116] 1) L3 service, wherein the service identifier is associated with a flow identifier, the session message further includes a destination IP address of a service instance corresponding to the service identifier, and the L3 service does not distinguish between all sessions under the destination IP address.
[0117] 2) L4 service, wherein the service identifier is associated with at least one flow identifier, and different flow identifiers represent different network quality requirements corresponding to sessions corresponding to different ports or port combinations.
[0118] 3) L7 service, wherein the service identifier is associated with at least one flow identifier, and different flow identifiers represent different network quality requirements corresponding to application-level content transmission with different combinations of port and content identifiers.
[0119] 4) Network service NAAS, wherein the target flow identifier is invalid.
[0120] Fig.12 1 is a flow chart of a communication method for a service-aware network according to an embodiment of the present application, which can be applied to a second network device, where the second network device can be an egress gateway. Fig.12 As shown, the method 1200 includes the following steps.
[0121] S1202: The second network device triggers the first network device to generate a SAN traffic engineering northbound policy configuration; wherein the SAN traffic engineering northbound policy configuration includes: a service identifier; at least one flow identifier associated with the service identifier; network quality requirement information corresponding to the flow identifier, and at least two different flow identifiers correspond to different network quality requirements.
[0122] The communication method of the service-aware network provided in the embodiment of the present application can realize flexible perception and scheduling of multiple service types by designing a combination of service identifiers and flow identifiers and different flow identifiers corresponding to different network quality requirements, and can also realize differentiated service quality requirements of different sub-services under the same service type, thereby providing network service capabilities with unified perception and differentiated service quality, maximizing the utilization of network resources, and the service-aware network has a good implementation foundation and significant practical value; at the same time, it can also save identification resource space, realize solution simplification, and have strong feasibility and scalability.
[0123] Optionally, as an embodiment, the method also includes: the second network side device receives a service instance registration message; wherein, the second network device triggers the first network device to generate a SAN traffic engineering northbound policy configuration, including: the second network device triggers the first network device to generate a SAN traffic engineering northbound policy configuration based on the service instance registration message; the service instance registration message includes at least one of the following: the destination IP address of the service instance corresponding to the service identifier; the service export gateway IP address.
[0124] Optionally, as an embodiment, the method further includes: the second network device sends an information table; wherein the information table is used for service request processing lookup, and the information table includes: at least one flow identifier associated with the service identifier; and port information associated with each flow identifier.
[0125] Optionally, as an embodiment, the method also includes: the second network device receives a service registration message; wherein, the second network device sends an information table including: the second network device sends an information table based on the service registration message; the service registration message includes at least one of the following: the service identifier; the service identifier is associated with at least one flow identifier; information indicating whether the flow identifier participates in joint calculation; port information corresponding to the flow identifier.
[0126] Fig.13 A structural schematic diagram of a communication device of a service-aware network provided in an embodiment of the present application is shown. The device corresponds to the first network device in other embodiments. The device 1300 includes: a receiving module 1302 and a processing module 1304.
[0127] The receiving module 1302 is configured to receive a session message, where the session message includes a first identifier, and the first identifier includes a service identifier and a target flow identifier.
[0128] The processing module 1304 is used to perform flow diversion processing on the session message based on the first identifier; wherein the service identifier is associated with at least one flow identifier, the target flow identifier belongs to the at least one flow identifier, and at least two different flow identifiers correspond to different network quality requirements.
[0129] The communication device of the service-aware network provided in the embodiment of the present application can realize flexible perception and scheduling of multiple service types by designing a combination of service identifiers and flow identifiers and different flow identifiers corresponding to different network quality requirements. It can also realize differentiated service quality requirements of different sub-services under the same service type, thereby providing network service capabilities with unified perception and differentiated service quality, maximizing the utilization of network resources, and the service-aware network has a good implementation foundation and significant practical value; at the same time, it can also save identification resource space, realize solution simplification, and have strong feasibility and scalability.
[0130] Optionally, as an embodiment, the session message further includes: a destination IP address of a service instance corresponding to the service identifier.
[0131] Optionally, as an embodiment, the receiving module 1302 is also used to receive a service request message, and the service request message includes the service identifier; the device also includes a sending module, used to send a service response message, and the service response message includes at least one of the following: at least one flow identifier associated with the service identifier; port information associated with each of the flow identifiers; and the destination IP address of the service instance corresponding to the service identifier.
[0132] Optionally, as an embodiment, the processing module 1304 is also used to generate a service-aware network forwarding information base SFIB and update it to the forwarding plane based on the service-aware network SAN traffic engineering northbound policy configuration and computing power information; the processing module 1304 is specifically used to divert the session message based on the first identifier and the SFIB.
[0133] Optionally, as an embodiment, the SFIB includes at least one of the following: a combination of the service identifier and the target flow identifier; the destination IP address of the service instance corresponding to the service identifier; the IP address of the service egress gateway; segmented routing policy information; or, the SAN traffic engineering northbound policy configuration includes at least one of the following: the service identifier; the target flow identifier; information indicating whether the target flow identifier participates in joint calculation; network quality requirement information corresponding to the target flow identifier; the IP address of the first network device node; or, the computing power information includes at least one of the following: the service identifier; the destination IP address of the service instance corresponding to the service identifier; the IP address of the service egress gateway; the measurement value of the computing power resources connected to the service egress gateway.
[0134] Optionally, as an embodiment, the receiving module 1302 is also used to obtain an information table; wherein the information table is used for service request processing lookup, and the information table includes: at least one flow identifier associated with the service identifier; and port information associated with each flow identifier.
[0135] Optionally, as an embodiment, the first identifier also includes a service type identifier; wherein one service type identifier corresponds to at least one service identifier.
[0136] Optionally, as an embodiment, the service type identifier is used to indicate one of the following:
[0137] 1) L3 service, wherein the service identifier is associated with a flow identifier, the session message further includes a destination IP address of a service instance corresponding to the service identifier, and the L3 service does not distinguish between all sessions under the destination IP address.
[0138] 2) L4 service, wherein the service identifier is associated with at least one flow identifier, and different flow identifiers represent different network quality requirements corresponding to sessions corresponding to different ports or port combinations.
[0139] 3) L7 service, wherein the service identifier is associated with at least one flow identifier, and different flow identifiers represent different network quality requirements corresponding to application-level content transmission with different combinations of port and content identifiers.
[0140] 4) Network service NAAS, wherein the target flow identifier is invalid.
[0141] The device 1300 provided in the embodiment of the present application can execute the methods described in the above method embodiment 100, and realize the functions and beneficial effects of the methods described in the above method embodiment, which will not be repeated here.
[0142] Fig.14 A structural schematic diagram of a communication device of a service-aware network provided in an embodiment of the present application is shown. The device corresponds to a terminal in other embodiments. The device 1400 includes: a sending module 1402.
[0143] The sending module 1402 is used to send a session message, wherein the session message includes a first identifier, wherein the first identifier includes a service identifier and a target flow identifier; wherein the service identifier is associated with at least one flow identifier, the target flow identifier belongs to the at least one flow identifier, and at least two different flow identifiers correspond to different network quality requirements.
[0144] Optionally, the device 1400 also includes a processing module and the like.
[0145] The communication device of the service-aware network provided in the embodiment of the present application can realize flexible perception and scheduling of multiple service types by designing a combination of service identifiers and flow identifiers and different flow identifiers corresponding to different network quality requirements. It can also realize differentiated service quality requirements of different sub-services under the same service type, thereby providing network service capabilities with unified perception and differentiated service quality, maximizing the utilization of network resources, and the service-aware network has a good implementation foundation and significant practical value; at the same time, it can also save identification resource space, realize solution simplification, and have strong feasibility and scalability.
[0146] Optionally, as an embodiment, the session message further includes: a destination IP address of a service instance corresponding to the service identifier.
[0147] Optionally, as an embodiment, the sending module 1402 is also used to send a service request message, and the service request message includes the service identifier; the device also includes a receiving module, used to receive a service response message, and the service response message includes at least one of the following: at least one flow identifier associated with the service identifier; port information associated with each of the flow identifiers; and the destination IP address of the service instance corresponding to the service identifier.
[0148] Optionally, as an embodiment, the first identifier also includes a service type identifier; wherein one service type identifier corresponds to at least one service identifier.
[0149] Optionally, as an embodiment, the service type identifier is used to indicate one of the following:
[0150] 1) L3 service, wherein the service identifier is associated with a flow identifier, the session message further includes a destination IP address of a service instance corresponding to the service identifier, and the L3 service does not distinguish between all sessions under the destination IP address.
[0151] 2) L4 service, wherein the service identifier is associated with at least one flow identifier, and different flow identifiers represent different network quality requirements corresponding to sessions corresponding to different ports or port combinations.
[0152] 3) L7 service, wherein the service identifier is associated with at least one flow identifier, and different flow identifiers represent different network quality requirements corresponding to application-level content transmission with different combinations of port and content identifiers.
[0153] 4) Network service NAAS, wherein the target flow identifier is invalid.
[0154] The device 1400 provided in the embodiment of the present application can execute the various methods described in the method embodiment 1100 above, and realize the functions and beneficial effects of the various methods described in the method embodiment above, which will not be repeated here.
[0155] Fig.15 A structural schematic diagram of a communication device of a service-aware network provided in an embodiment of the present application is shown. The device corresponds to the second network device in other embodiments. The device 1500 includes: a sending module 1502.
[0156] The sending module 1502 is used to trigger the first network device to generate a SAN traffic engineering northbound policy configuration; wherein the SAN traffic engineering northbound policy configuration includes: a service identifier; at least one flow identifier associated with the service identifier; network quality requirement information corresponding to the flow identifier, and at least two different flow identifiers have different network quality requirements.
[0157] Optionally, the device 1500 also includes a processing module and the like.
[0158] The communication device of the service-aware network provided in the embodiment of the present application can realize flexible perception and scheduling of multiple service types by designing a combination of service identifiers and flow identifiers and different flow identifiers corresponding to different network quality requirements. It can also realize differentiated service quality requirements of different sub-services under the same service type, thereby providing network service capabilities with unified perception and differentiated service quality, maximizing the utilization of network resources, and the service-aware network has a good implementation foundation and significant practical value; at the same time, it can also save identification resource space, realize solution simplification, and have strong feasibility and scalability.
[0159] Optionally, as an embodiment, the device also includes a receiving module for receiving a service instance registration message; wherein the sending module 1502 is specifically used to trigger the first network device to generate a SAN traffic engineering northbound policy configuration based on the service instance registration message; the service instance registration message includes at least one of the following: the destination IP address of the service instance corresponding to the service identifier; the service export gateway IP address.
[0160] Optionally, as an embodiment, the sending module 1502 is also used to send an information table; wherein the information table is used for service request processing lookup, and the information table includes: at least one flow identifier associated with the service identifier; and port information associated with each flow identifier.
[0161] Optionally, as an embodiment, the device also includes a receiving module for receiving a service registration message; wherein the sending module 1502 is specifically used to send an information table based on the service registration message; the service registration message includes at least one of the following: the service identifier; the service identifier is associated with at least one flow identifier; information indicating whether the flow identifier participates in joint calculation; port information corresponding to the flow identifier.
[0162] The device 1500 provided in the embodiment of the present application can execute the various methods described in the above method embodiment 1200, and realize the functions and beneficial effects of the various methods described in the above method embodiment, which will not be repeated here.
[0163] Fig.16 A schematic diagram of the hardware structure of an electronic device that implements the embodiment of the present application is shown. Referring to the figure, at the hardware level, the electronic device includes a processor, and optionally, an internal bus, a network interface, and a memory. Among them, the memory may include a memory, such as a high-speed random access memory (Random-Access Memory, RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage, etc. Of course, the electronic device may also include hardware required for other services.
[0164] The processor, the network interface and the memory may be interconnected through an internal bus, which may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bidirectional arrow is used in the figure, but it does not mean that there is only one bus or one type of bus.
[0165] The memory is used to store the program. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory may include a memory and a non-volatile memory, and provides instructions and data to the processor.
[0166] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a device for locating the target user at the logical level. The processor executes the program stored in the memory and is specifically used to execute: Figure 1-12 The method disclosed in the illustrated embodiment realizes the functions and beneficial effects of each method described in the foregoing method embodiments, which will not be described in detail here.
[0167] The above application Figure 1-12 The method disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor for execution, or a combination of hardware and software modules in the decoding processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
[0168] The electronic device can also execute the methods described in the foregoing method embodiments, and realize the functions and beneficial effects of the methods described in the foregoing method embodiments, which will not be repeated here.
[0169] Of course, in addition to software implementation methods, the electronic device of the present application does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.
[0170] The embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable medium stores one or more programs, and when the one or more programs are executed by an electronic device including multiple application programs, the electronic device executes Figure 1-12 The method disclosed in the illustrated embodiment realizes the functions and beneficial effects of each method described in the foregoing method embodiments, which will not be described in detail here.
[0171] The computer-readable storage medium includes a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.
[0172] Furthermore, an embodiment of the present application also provides a computer program product, the computer program product comprising a computer program stored on a non-transitory computer-readable storage medium, the computer program comprising program instructions, and when the program instructions are executed by a computer, the following process is implemented: Figure 1-12 The method disclosed in the illustrated embodiment realizes the functions and beneficial effects of each method described in the foregoing method embodiments, which will not be described in detail here.
[0173] In short, the above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.
[0174] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
[0175] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
[0176] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0177] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
Claims
1. A communication method for a service-aware network, comprising: The first network device receives a session message, wherein the session message includes a first identifier, and the first identifier includes a service identifier and a target flow identifier; The first network device performs flow diversion processing on the session message based on the first identifier; wherein the service identifier is associated with at least one flow identifier, the target flow identifier belongs to the at least one flow identifier, and at least two different flow identifiers correspond to different network quality requirements.
2. The method according to claim 1, wherein: The session message also includes: a destination IP address of the service instance corresponding to the service identifier.
3. The method according to claim 2, wherein: Before the first network device receives the session message, the method further includes: The first network device receives a service request message, where the service request message includes the service identifier; The first network device sends a service response message, and the service response message includes at least one of the following: the at least one flow identifier associated with the service identifier; the port information associated with each of the flow identifiers; and the destination IP address of the service instance corresponding to the service identifier.
4. The method according to any one of claims 1 to 3, wherein: The method further comprises: The first network device generates a service-aware network forwarding information base SFIB based on the service-aware network SAN traffic engineering northbound policy configuration and computing power information and updates it to the forwarding plane; The first network device performing a flow diversion process on the session message based on the first identifier includes: the first network device performing a flow diversion process on the session message based on the first identifier and the SFIB.
5. The method according to claim 4, wherein: The SFIB includes at least one of the following: a combination of the service identifier and the target flow identifier; a destination IP address of a service instance corresponding to the service identifier; an IP address of a service egress gateway; segment routing policy information; or The SAN traffic engineering northbound policy configuration includes at least one of the following: the service identifier; the target flow identifier; information indicating whether the target flow identifier participates in joint calculation; network quality requirement information corresponding to the target flow identifier; the IP address of the first network device node; or The computing power information includes at least one of the following: the service identifier; the destination IP address of the service instance corresponding to the service identifier; the IP address of the service export gateway; and the measurement value of the computing power resources connected to the service export gateway.
6. The method according to any one of claims 1 to 3, wherein: The method further comprises: the first network device obtaining an information table; The information table is used for service request processing and searching, and includes: the at least one flow identifier associated with the service identifier; and port information associated with each flow identifier.
7. The method according to any one of claims 1 to 6, wherein: The first identifier also includes a service type identifier; wherein one service type identifier corresponds to at least one service identifier.
8. The method according to claim 7, wherein: The service type identifier is used to indicate one of the following: L3 service, wherein the service identifier is associated with a flow identifier, the session message further includes a destination IP address of a service instance corresponding to the service identifier, and the L3 service does not distinguish between all sessions under the destination IP address; L4 service, wherein the service identifier is associated with at least one flow identifier, and different flow identifiers represent: different network quality requirements corresponding to sessions corresponding to different ports or port combinations; L7 service, wherein the service identifier is associated with at least one flow identifier, and different flow identifiers represent: different network quality requirements corresponding to application-level content delivery of different combinations of port and content identifiers; Network service NAAS, wherein the target flow identifier is invalid.
9. A communication method for a service-aware network, comprising: The terminal sends a session message, where the session message includes a first identifier, where the first identifier includes a service identifier and a target flow identifier; The service identifier is associated with at least one flow identifier, the target flow identifier belongs to the at least one flow identifier, and at least two different flow identifiers correspond to different network quality requirements.
10. The method according to claim 9, wherein: The session message also includes: a destination IP address of the service instance corresponding to the service identifier.
11. The method according to claim 10, wherein: Before the terminal sends the session message, the method further includes: The terminal sends a service request message, where the service request message includes the service identifier; The terminal receives a service response message, wherein the service response message includes at least one of the following: the at least one flow identifier associated with the service identifier; the port information associated with each flow identifier; and the destination IP address of the service instance corresponding to the service identifier.
12. The method according to claim 9, wherein: The first identifier also includes a service type identifier; wherein one service type identifier corresponds to at least one service identifier.
13. The method according to claim 12, wherein: The service type identifier is used to indicate one of the following: L3 service, wherein the service identifier is associated with a flow identifier, the session message further includes a destination IP address of a service instance corresponding to the service identifier, and the L3 service does not distinguish between all sessions under the destination IP address; L4 service, wherein the service identifier is associated with at least one flow identifier, and different flow identifiers represent: different network quality requirements corresponding to sessions corresponding to different ports or port combinations; L7 service, wherein the service identifier is associated with at least one flow identifier, and different flow identifiers represent: different network quality requirements corresponding to application-level content delivery of different combinations of port and content identifiers; Network service NAAS, wherein the target flow identifier is invalid.
14. A communication method for a service-aware network, comprising: The second network device triggers the first network device to generate a SAN traffic engineering northbound policy configuration; The SAN traffic engineering northbound policy configuration includes: a service identifier; at least one flow identifier associated with the service identifier; and network quality requirement information corresponding to the flow identifier, wherein at least two different flow identifiers correspond to different network quality requirements.
15. The method according to claim 14, wherein: The method further comprises: The second network side device receives a service instance registration message; The second network device triggering the first network device to generate a SAN traffic engineering northbound policy configuration includes: the second network device triggering the first network device to generate a SAN traffic engineering northbound policy configuration based on the service instance registration message; The service instance registration message includes at least one of the following: a destination IP address of the service instance corresponding to the service identifier; and an IP address of a service egress gateway.
16. The method according to claim 14, wherein: The method further comprises: The second network device sends an information table; The information table is used for service request processing and searching, and includes: at least one flow identifier associated with the service identifier; and port information associated with each flow identifier.
17. The method according to claim 16, wherein: The method further comprises: The second network device receives a service registration message; Wherein, the second network device sending information table includes: the second network device sending information table based on the service registration message; The service registration message includes at least one of the following: the service identifier; at least one flow identifier associated with the service identifier; information indicating whether the flow identifier participates in joint calculation; and port information corresponding to the flow identifier.
18. A communication device for a service-aware network, comprising: A receiving module, configured to receive a session message, wherein the session message includes a first identifier, and the first identifier includes a service identifier and a target flow identifier; A processing module is used to perform flow diversion processing on the session message based on the first identifier; wherein the service identifier is associated with at least one flow identifier, the target flow identifier belongs to the at least one flow identifier, and at least two different flow identifiers correspond to different network quality requirements.
19. A communication device for a service-aware network, comprising: A sending module, configured to send a session message, wherein the session message includes a first identifier, and the first identifier includes a service identifier and a target flow identifier; The service identifier is associated with at least one flow identifier, the target flow identifier belongs to the at least one flow identifier, and at least two different flow identifiers correspond to different network quality requirements.
20. A communication device for a service-aware network, comprising: A sending module, used for triggering the first network device to generate a SAN traffic engineering northbound policy configuration; The SAN traffic engineering northbound policy configuration includes: a service identifier; at least one flow identifier associated with the service identifier; and network quality requirement information corresponding to the flow identifier, wherein at least two different flow identifiers correspond to different network quality requirements.
21. A communication device comprising: processor; as well as A memory arranged to store computer executable instructions which, when executed, cause the processor to perform the steps of the method of any one of claims 1 to 17.
22. A computer-readable medium storing one or more programs, which, when executed by an electronic device including a plurality of application programs, causes the electronic device to perform the steps of the method according to any one of claims 1 to 17.
