Communication method and apparatus for service awareness network, and communication device

By using a combination of service identification and flow identification in the service perception network, the network quality requirements of different sub-services are distinguished, and the problem of poor communication flexibility in the prior art is solved, and flexible perception and scheduling of multiple service types is realized. It meets the differentiated needs of different sub-services and improves network resource utilization efficiency.

WO2024230226A1PCT designated stage expired Publication Date: 2024-11-14ZTE CORP

Patent Information

Application Number
PCT/CN2024/071531
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-08
Filing Date
2024-01-10
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

The prior art cannot differentiate the network quality requirements of different subservices, and has poor communication flexibility and cannot meet the diversified needs of network quality in different sessions (such as voice and images).

Method used

By designing a communication method for a service-aware network, using the combination of service identification and flow identification, the distinction and differentiation of network quality requirements of different flow identifications are realized, including receiving and processing session messages, generating northbound policy configuration of SAN traffic engineering, and realizing Flexible perception and scheduling of multiple service types.

Benefits of technology

It realizes the differentiated service quality requirements of different sub-services under the same service type, provides network service capabilities that are unified in perception and differentiated in service quality, maximizes network resource utilization, simplifies the identification resource space, and has strong implementation ability. and scalability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024071531_14112024_PF_FP_ABST
    Figure CN2024071531_14112024_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the embodiments of the present application are a communication method and apparatus for a service awareness network, and a communication device. The method comprises: a first network device receiving a session message, wherein the session message comprises a first identifier, and the first identifier comprises a service identifier and a target flow identifier; and the first network device performing flow-guidance processing on the session message on the basis of 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.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method, device and communication equipment of service-aware network

[0001] Cross-references

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on May 8, 2023, with application number 202310512716.9 and application name “Communication method, device and communication equipment for service-aware network”. The entire contents of the application are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method, apparatus, and communication equipment for a Service Awareness Network (SAN). Background Art

[0004] Computing network technologies in related technologies generally use anycast addresses as a unified identifier for computing power and network services. This utilizes network-aware computing power to implement routing and services, achieving Layer 3 (L3) load balancing at the network level. Most computing service instances (such as cloud desktops, extended reality (XR), and virtual reality (VR)) typically publish multiple sub-services over different Transmission Control Protocol (TCP) / User Datagram Protocol (UDP) ports under a specific IP address. Different sub-services are accessed through different ports.

[0005] However, the above solutions have the following problems: different sessions under a service instance (such as voice and image) have different network quality requirements. Layer 3 load balancing technologies such as Domain Name System (DNS) or Compute First Networking (CFN) only provide uniform network quality for all sessions under a specific IP address, such as the Service Level Agreement (SLA). They cannot differentiate the network quality requirements for different sub-services, resulting in poor communication flexibility.

[0006] Summary of the Invention

[0007] 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.

[0008] To solve the above technical problems, the embodiments of the present application are implemented through the following aspects.

[0009] In a first aspect, an embodiment of the present application provides a communication method for a service-aware network, including: 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.

[0010] In the second aspect, an embodiment of the present application provides a communication method for a service-aware network, including: 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.

[0011] In a third aspect, an embodiment of the present application provides a communication method for a service-aware network, including: 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 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 corresponding network quality requirements.

[0012] In a fourth aspect, an embodiment of the present application provides a communication device for a service-aware network, comprising: a receiving module for receiving a session message, the session message including a first identifier, the first identifier including a service identifier and a target flow identifier; a processing module for performing 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.

[0013] In the fifth aspect, an embodiment of the present application provides a communication device of a service-aware network, including: a sending module for sending 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.

[0014] In the sixth aspect, an embodiment of the present application provides a communication device for a service-aware network, including: a sending module for triggering 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 corresponding network quality requirements.

[0015] In the seventh aspect, an embodiment of the present application provides an electronic device, comprising: a memory, a processor, and computer-executable instructions stored on 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.

[0016] 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0018] FIG1 is a schematic diagram showing a flow chart of a communication method of a service-aware network provided in an embodiment of the present application;

[0019] FIG2 is 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;

[0020] FIG3 is a diagram illustrating service requirements of a communication method for a service-aware network provided in an embodiment of the present application;

[0021] FIG4 shows a schematic diagram of the system architecture and operation of the communication method of the service-aware network provided in an embodiment of the present application;

[0022] FIG5 is a schematic diagram showing service registration information of a communication method of a service-aware network provided in an embodiment of the present application;

[0023] FIG6 is 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;

[0024] FIG7 is a schematic diagram showing service instance registration information of a communication method of a service-aware network provided in an embodiment of the present application;

[0025] FIG8 is 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;

[0026] FIG9 shows a schematic diagram of a terminal using a service in a communication method of a service-aware network according to an embodiment of the present application;

[0027] FIG10 shows a comparative diagram of conventional identification schemes;

[0028] FIG11 is a flow chart showing a communication method of a service-aware network according to an embodiment of the present application;

[0029] FIG12 is a flow chart showing a communication method of a service-aware network provided in an embodiment of the present application;

[0030] FIG13 is a schematic diagram showing the structure of a communication device of a service-aware network provided in an embodiment of the present application;

[0031] FIG14 is a schematic diagram showing the structure of a communication device of a service-aware network provided in an embodiment of the present application;

[0032] FIG15 is a schematic diagram showing the structure of a communication device of a service-aware network provided in an embodiment of the present application;

[0033] Figure 16 is a schematic diagram of the hardware structure of an electronic device that executes the communication method of the service-aware network provided in an embodiment of the present application. DETAILED DESCRIPTION

[0034] 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 the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0035] Figure 1 shows a flow chart of a communication method for a service-aware network provided in an embodiment of the present application, which can be performed by a first network device. In other words, the method can be performed by software or hardware installed on the first network device. The first network device includes but is not limited to an ingress gateway (IGW), etc. As shown in Figure 1, the method may include the following steps.

[0036] 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.

[0037] In this embodiment, the first network device may be an ingress gateway, and the session message may come from a terminal.

[0038] Optionally, the session message may further include at least one of the following: the destination IP address of the service instance corresponding to the service identifier; and the port information associated with the target flow identifier. Prior to S102, the first network device may further provide the terminal with the destination IP address of the service instance, the port information associated with the target flow identifier, and the like, which are stored locally by the terminal. Since the terminal side can obtain the correspondence between the port (or port + content) and the flow, programming errors such as service definition adjustments and agreement protocol errors are avoided, thereby improving communication reliability.

[0039] 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 includes the service identifier; the first network device sends a service response message (to the terminal), 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 (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.

[0040] Optionally, the method further includes: the first network device obtaining 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 flow identifier. Thus, 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, the port information associated with each flow identifier, and the like based on the information table.

[0041] Optionally, the first identifier further includes a service type identifier; wherein one service type identifier corresponds to at least one service identifier.

[0042] Optionally, the service type identifier may be used to indicate one of the following:

[0043] 1) L3 service, wherein the service identifier is associated with a flow identifier (ie, target flow identifier), the session message further includes a destination IP address of the service instance corresponding to the service identifier, and the L3 service does not distinguish all sessions under the destination IP address.

[0044] 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.

[0045] 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.

[0046] 4) Network as a service (NAAS), wherein the target flow identifier is invalid.

[0047] 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.

[0048] 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.

[0049] 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. When 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).

[0050] Optionally, the above network quality requirements may include service level agreement (SLA) quality of service, including but not limited to requirements on bandwidth, delay, jitter, packet loss, etc.

[0051] Optionally, in this step, the first network device may perform flow routing 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 the service instance corresponding to the service identifier; an IP address of a service egress gateway; and segment routing policy information (SR POLICY).

[0052] Optionally, the embodiment shown in FIG1 further 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.

[0053] 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.

[0054] 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 resource connected to the service export gateway.

[0055] 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. 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 network resource utilization, 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 implementability and scalability.

[0056] 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 identification design and service identification use.

[0057] 1. Service Logo Design

[0058] Referring to Figure 2, the embodiment of the present application can divide the 128-bit identification (ID) space into two segments: the first segment is the service segment (SAN-ID, abbreviated as SID), and the second segment is used for the flow identification segment (FID). The SID includes at least but not limited to a reserved field, a service type, and a service identification (ID); the FID includes at least but not limited to a flow identification and a reserved field.

[0059] 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.

[0060] According to the service identification design constraints, the allocation of SID is negotiated between the cloud service operator and the operator and is globally unique. FID has local semantics and can be flexibly adjusted through planning and negotiation. The relevant usage process is described below.

[0061] Service Segment (SID): As a global semantic identification field, it is an abstract identifier for similar services and is globally unique within the computing network domain. The reserved fields are reserved for future expansion. The service type field is used to identify the relevant service type (including but not limited to L3 services, L4 services, L7 services, and NAAS services), and is used to differentiate service processing that may involve system processing logic. The service identifier field is used to identify the abstract identifier of the service under a specific service type.

[0062] Flow Identifier (FID): This field has local semantics based on a specific SID and is used to differentiate different network SLA service qualities (including but not limited to bandwidth, latency, jitter, and packet loss) for a specific SID. This field is reserved for future expansion. The FID field is used in conjunction with the SID during a terminal session and is primarily used for differentiated network service traffic diversion.

[0063] The service identifier provided in this embodiment has the following identification capabilities:

[0064] 1) L3 service: There is only one FID under a specific L3 service SID. L3 service does not distinguish all sessions under IP.

[0065] 2) Identify L4 services. A specific L4 service SID has one or more FIDs. Different FIDs represent the differentiated network quality requirements of sessions (groups) corresponding to different ports or port combinations.

[0066] 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 delivery with different combinations of port and content identifiers.

[0067] 4) Identify the NAAS service. It does not involve computing power awareness. It is distinguished by SID. The FID field is invalid.

[0068] Figure 3 shows an introduction to the aforementioned L3 services, L4 services, L7 services, and NAAS services.

[0069] II. Use of Service Logo

[0070] The use of service identification includes the service provision and access process, involving three components: terminal, network, and cloud side. Referring to Figure 4, the overall mechanism and process are described in the following eight parts.

[0071] (1) Service Registration

[0072] Service registration is initiated by the cloud side to the network side's computing network brain, and the relevant content is received and processed by the computing network brain.

[0073] The cloud side can send registration information to the operator's network brain. Based on the received SID and FID list information, the network brain registers the FID list information for the service, using the SID as the index. This includes the mapping relationship between each FID and its corresponding network quality requirements (including but not limited to bandwidth, latency, jitter, packet loss, etc.), service port, content identifier, etc. The network brain sends the SID and the port list corresponding to the FID to the service ingress gateway (IGW) and service egress gateway (EGW).

[0074] Refer to Figure 5. Taking a Layer 4 service (T2) as an example, the registration information obtained by the computing network brain is shown in Figure 5. The flow identifiers for SLA21 and SLA22 mappings are F21 and F22, respectively. F21 is required to participate in the computing network's joint computing decision-making for computing power selection. Subservice ports 1 (port 1 in Figure 5) and 3 (port 2 in Figure 5) use F21 for connections, corresponding to the flow processing SLA network quality requirements. Port 2 (port 2 in Figure 5) uses F22 for connections, corresponding to the flow processing SLA network quality requirements.

[0075] (2) Configuration policy delivery

[0076] After receiving a legitimate service registration request, the network brain generates a relevant 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).

[0077] As shown in Figure 6, 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. Using SID as an index for search supports efficient storage and variable-length management, which will not be described here. This information table is used for service request processing, search, and response, as shown in subsequent steps (7) and (8).

[0078] (3) Service instance registration

[0079] Based on cloud resource deployment, the cloud side registers the SID, service IP address, and egress gateway (EGW) IP address for each service instance with the Computing Network Brain. Based on this registration information, the Computing Network Brain converts the network quality requirements associated with the SID and FID into northbound SAN Traffic Engineering (TE) policy configurations and distributes them to the relevant IGWs and EGWs. Simultaneously, the cloud side initiates health monitoring of the corresponding resources and updates the EGWs with the service instance health status.

[0080] When a new service instance is added, as shown in Figure 7, the cloud side registers it with the computing network brain based on the service type. The registered elements include the service instance IP, the service gateway IP, etc. As shown in Figure 7, 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.

[0081] (4) Service status perception

[0082] 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.

[0083] (5) Service route generation

[0084] After sensing the status of a service instance, the EGW extends its health information to the entire network via the bearer network. Each IGW triggers the generation of service routing and forwarding tables based on the northbound configuration of the SAN traffic engineering policy generated by the corresponding SAN-ID registration and registration. Specifically, based on route reachability and service instance health indicators, and in accordance with the northbound configuration of the SAN traffic engineering policy, the IGW uses a local distributed algorithm or leverages the centralized routing capabilities 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).

[0085] During this process, the IGW00 gateway generates a computing power information table based on the received computing power information and updates its status. The update cycle depends on the notification speed of the cloud-side monitoring to the network side. Referring to Figure 8, the IGW00 gateway SAN-TE module performs traffic engineering calculations based on the local SAN traffic engineering northbound configuration policy and the computing power information table, and according to relevant constraints, generates SFIB updates to the forwarding plane for SAN service provision and traffic forwarding.

[0086] (6) Obtaining service identification

[0087] 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.

[0088] The following describes the service access process. Service access consists of two main phases: service request and service invocation. To avoid duplication of development, specific development libraries are encapsulated at the application layer, hiding implementation details and maintaining consistency in the terminal programming interface. This reduces the workload associated with modifications on the peer side (both the client and the server) and minimizes the chance of system errors.

[0089] (7) Service Request

[0090] By extending the Simple Request and Response Protocol, the terminal sends a service request message to the IGW based on the SID. The IGW then queries the table to retrieve at least one of the following responses: the destination IP address of the service instance corresponding to the SID; the mapping between the SID and the FID; and the port information associated with each FID. The terminal caches this information locally for session initiation. Because the terminal obtains the specific destination IP address, the network no longer needs to maintain session-specific flow affinity information, achieving a stateless network.

[0091] Specifically, referring to the service initiation process in Figure 9, the terminal uses SID to initiate a service request (SAN-REQ) to IGW00, carrying SID2; IGW00 queries SFIB according to SID2 based on the service request to provide service instance information, and responds to the terminal with a service response (SAN-RSP) message using the specific IP12, together with the flow identifiers F21 and F22 associated with SID2, and the port information associated with F21 and F22.

[0092] (8)Service call

[0093] 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 in 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.

[0094] Referring to Figure 9, after completing the services SAN-REQ and SAN-RSP, the terminal uses IP12 as the destination address, searches for the relevant 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.

[0095] IGW00 receives a message carrying a SID. Based on the combination of the message SID and flow identifier, SID2|FID21 or SID2|FID22 queries the SFIB table and directs the message to different SR-POLICY-F21 / SR-POLICY-F22 to provide differentiated quality of service.

[0096] 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.

[0097] In order to expand the scope of services 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 (abbreviated as SID) and a flow identification segment (abbreviated as FID) within a limited ID space. The SID is used to identify different service types and service IDs, and the 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 scalability.

[0098] Different from other existing proposed methods, the service identification design described in the embodiments of this application has the following obvious characteristics:

[0099] 1) Within a limited service identification space, service scope is expanded by defining and extending it according to service type. Other similar solutions often use service identification IDs that only represent IP, IP+port services, or network services, and their service scope expansion capabilities are limited.

[0100] 2) Divide the identification space into two segments, SID and FID. Use SID for abstract identification of computing power and selection of service instances, and combine it with multiple FIDs under the service to carry network traffic, realizing service identification aggregation and differentiated network quality provision. Existing solutions use a single service identifier to simultaneously map service instances and network quality requirements, which limits the scalability of identification, wastes identification resources for complex services, and increases the complexity of device configuration and computing power modeling.

[0101] The specific implementation of the existing solution is shown in Figure 10. 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 this application can solve the above problems.

[0102] 3) By using SID-based identification to uniformly initiate service requests, the real service instance IP and the FID and port correspondence table are obtained. When different TCP / UDP and other sub-service sessions are initiated, the service identifier (SID|FID) is searched and carried according to different ports, reducing the probability of corresponding errors between sub-services and identifiers. At the same time, it realizes stateless forwarding of network nodes and network differentiated service capabilities for different sub-services under the same service.

[0103] In the related art, the ANYCAST solution uses the anycast address to guide the service instance selection in the first packet. Since the computing power routing of the network node is updated in real time according to the computing power status, subsequent packets may be forwarded to other service instances at the network node after table lookup, causing service interruption. To solve this problem, a flow affinity table is introduced into the network device to perform subsequent packet lookup and forwarding, resulting in complex problems such as flow table resource overhead and network status. The embodiments of the present application can solve the above problems.

[0104] From the perspective of beneficial effects, the overall advantage of the embodiments of the present application compared to existing technologies and solutions is that it utilizes a limited global service identification space and scope to meet the demand for service differentiation, and has strong feasibility, adaptability to different scenarios, and scalability. The technical solution of the embodiments of the present application can accelerate the rapid implementation of the service-aware network in the existing network environment. Specifically, there are four points:

[0105] 1) Based on the service segment and flow identification segment model, it supports arbitrary extension of service types and satisfies the natural aggregation of atomic services, simplifying the complex aggregation configuration of services and computing power routing design.

[0106] 2) Based on the combined service identification design, the horizontal expansion of flow identification is achieved, and the identification space is compact, which has good feasibility.

[0107] 3) Complete decoupling of SAN traffic diversion and Layer 4 port flows is achieved, avoiding complex QOS to DSCP mapping configuration. The quality of service model is completely determined by service registration decisions and supports dynamic adjustment, reducing network configuration efficiency and complexity, saving resources and costs.

[0108] 4) The terminal side obtains the correspondence between the port (or port + content) and the stream, avoiding possible programming errors such as service definition adjustments and agreement errors.

[0109] It should be noted that the above embodiments are described using SRV6 as a bearer network as an example, 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.

[0110] The above describes in detail the communication method of the service-aware network according to the embodiment of the present application in conjunction with Figures 1 to 10. The following describes in detail the communication method of the service-aware network according to the embodiment of the present application in conjunction with Figures 11 and 12. It can be understood that the description from the terminal side and the second network device side is the same as or corresponds to the description of the first network device side in the method shown in Figures 1 to 10. To avoid repetition, the relevant description is appropriately omitted.

[0111] FIG11 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 on a terminal side. As shown in FIG11 , the method 1100 includes the following steps.

[0112] 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.

[0113] 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. 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 network resource utilization, 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 implementability and scalability.

[0114] Optionally, as an embodiment, the session message further includes: a destination IP address of the service instance corresponding to the service identifier.

[0115] 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: the at least one flow identifier associated with the service identifier; the port information associated with each flow identifier; the destination IP address of the service instance corresponding to the service identifier.

[0116] Optionally, as an embodiment, the first identifier further includes a service type identifier; wherein one service type identifier corresponds to at least one service identifier.

[0117] Optionally, as an embodiment, the service type identifier is used to indicate one of the following:

[0118] 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 all sessions under the destination IP address.

[0119] 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.

[0120] 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.

[0121] 4) Network Service (NAAS), wherein the target flow identifier is invalid.

[0122] FIG12 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, which can be an egress gateway. As shown in FIG12 , the method 1200 includes the following steps.

[0123] 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.

[0124] 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. 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 network resource utilization, 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 implementability and scalability.

[0125] Optionally, as an embodiment, the method further 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 exit gateway IP address.

[0126] 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.

[0127] 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.

[0128] Figure 13 shows a structural diagram of a communication device of a service-aware network provided in an embodiment of the present application. The device corresponds to the first network device in other embodiments. The device 1300 includes: a receiving module 1302 and a processing module 1304.

[0129] 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.

[0130] 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.

[0131] 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 network resource utilization, 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 implementability and scalability.

[0132] Optionally, as an embodiment, the session message further includes: a destination IP address of the service instance corresponding to the service identifier.

[0133] 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: the at least one flow identifier associated with the service identifier; the port information associated with each flow identifier; the destination IP address of the service instance corresponding to the service identifier.

[0134] 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.

[0135] 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 exit 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; the 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 exit gateway; the measurement value of the computing power resources connected to the service exit gateway.

[0136] Optionally, as an embodiment, the receiving module 1302 is further used to obtain an information table; wherein, the information table is used for service request processing lookup, and the information table includes: the at least one flow identifier associated with the service identifier; and port information associated with each flow identifier.

[0137] Optionally, as an embodiment, the first identifier further includes a service type identifier; wherein one service type identifier corresponds to at least one service identifier.

[0138] Optionally, as an embodiment, the service type identifier is used to indicate one of the following:

[0139] 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 all sessions under the destination IP address.

[0140] 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.

[0141] 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.

[0142] 4) Network Service (NAAS), wherein the target flow identifier is invalid.

[0143] The device 1300 provided in the embodiment of the present application can execute the various methods described in the method embodiment 100 above, and realize the functions and beneficial effects of the various methods described in the method embodiment above, which will not be repeated here.

[0144] Figure 14 shows a structural diagram of a communication device of a service-aware network provided in an embodiment of the present application. The device corresponds to the terminal in other embodiments. The device 1400 includes: a sending module 1402.

[0145] The sending module 1402 is used 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; 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.

[0146] Optionally, the device 1400 further includes a processing module, etc.

[0147] 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 network resource utilization, 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 implementability and scalability.

[0148] Optionally, as an embodiment, the session message further includes: a destination IP address of the service instance corresponding to the service identifier.

[0149] 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: the at least one flow identifier associated with the service identifier; the port information associated with each flow identifier; the destination IP address of the service instance corresponding to the service identifier.

[0150] Optionally, as an embodiment, the first identifier further includes a service type identifier; wherein one service type identifier corresponds to at least one service identifier.

[0151] Optionally, as an embodiment, the service type identifier is used to indicate one of the following:

[0152] 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 all sessions under the destination IP address.

[0153] 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.

[0154] 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.

[0155] 4) Network Service (NAAS), wherein the target flow identifier is invalid.

[0156] 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.

[0157] Figure 15 shows a structural diagram of a communication device of a service-aware network provided in an embodiment of the present application. The device corresponds to the second network device in other embodiments. The device 1500 includes: a sending module 1502.

[0158] 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; and network quality requirement information corresponding to the flow identifier, wherein at least two different flow identifiers have different corresponding network quality requirements.

[0159] Optionally, the device 1500 further includes a processing module, etc.

[0160] 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 network resource utilization, 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 implementability and scalability.

[0161] 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.

[0162] Optionally, as an embodiment, the sending module 1502 is further 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.

[0163] 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; and port information corresponding to the flow identifier.

[0164] 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.

[0165] FIG16 shows a schematic diagram of the hardware structure of an electronic device that implements an embodiment of the present application. 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. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage device. Of course, the electronic device may also include hardware required for other services.

[0166] The processor, network interface, and memory can be interconnected via an internal bus, such as an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. These buses can be classified as address buses, data buses, and control buses. For ease of illustration, the figure uses only one bidirectional arrow, but this does not imply that there is only one bus or only one type of bus.

[0167] The memory is used to store programs. Specifically, the program may include program code, which includes computer operating instructions. The memory may include internal memory and non-volatile memory, and provides instructions and data to the processor.

[0168] The processor reads the corresponding computer program from the non-volatile memory into the internal memory and then runs it, forming a device for locating the target user at a logical level. The processor executes the program stored in the memory and is specifically configured to perform the methods disclosed in the embodiments shown in Figures 1-12 and to achieve the functions and benefits of the various methods described in the method embodiments above, which will not be further described here.

[0169] The methods disclosed in the embodiments shown in Figures 1-12 of the present application can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits in the processor or software instructions. 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 gate or transistor logic devices, or discrete hardware components. The various 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 any conventional processor. The steps of the methods disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0170] The electronic device can also execute the methods described in the above method embodiments and realize the functions and beneficial effects of the methods described in the above method embodiments, which will not be described in detail here.

[0171] Of course, in addition to software implementation, the electronic device of this 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.

[0172] An embodiment of the present application also proposes a computer-readable storage medium, which stores one or more programs. When the one or more programs are executed by an electronic device including multiple applications, the electronic device executes the method disclosed in the embodiments shown in Figures 1-12 and realizes the functions and beneficial effects of the various methods described in the previous method embodiments, which will not be repeated here.

[0173] The computer-readable storage medium includes a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0174] Furthermore, an embodiment of the present application also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the following process is implemented: the method disclosed in the embodiment shown in Figures 1-12 and the functions and beneficial effects of the various methods described in the previous method embodiments are implemented, which will not be repeated here.

[0175] In short, the above description is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

[0176] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having 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 smartphone, 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.

[0177] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The 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 disc read-only memory (CD-ROM), digital versatile disc (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 transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0178] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0179] The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the method embodiments.

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 also includes the destination IP address of the service instance corresponding to the service identifier, and the L3 service does not distinguish between all sessions under the destination IP address. talk; 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 is used to receive a session message, wherein the session message includes a first identifier, wherein the first identifier includes Including service identification and target flow identification; 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, used for sending 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.

Citation Information

Patent Citations

  • Message forwarding method, device and system and computer readable storage medium

    CN115226073A

  • Message forwarding method and device and communication network

    CN115442300A

  • Node scheduling method and device for computing power network, equipment and medium

    CN115695281A

  • Accessing an application based on a level of service quality

    US20130044614A1

  • Data processing method and apparatus, and data sending method and apparatus

    US20210014739A1

Cited By

  • Cloud network service information acquisition method and device, computer equipment and storage medium

    CN119743517A

  • Calculation network resource identifier management method and system

    CN121743066A