Communication method, network device, storage medium, and computer program product

Abstract

Provided in the embodiments of the present application are a communication method, a network device, a storage medium, and a computer program product, which are applied to a first edge network device of a current domain. The communication method comprises: receiving a first message which is sent by a second edge network device of a current domain and carries a first application identifier; querying a first preset cross-domain mapping relationship for a second application identifier mapped by the first application identifier in a target domain; replacing the first application identifier with the second application identifier or first deleting the first application identifier and then adding the second application identifier, so as to obtain a second message; and sending the second message to the target domain.

Description

A communication method, network device, storage medium and computer program product

[0001] Cross-reference to related applications

[0002] The present application is based on the Chinese patent application No. 2024104182816, filed on April 8, 2024, and claims priority to the Chinese patent application, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0003] The present application relates to the field of wireless communication, and in particular to a communication method, network device, storage medium and computer program product. BACKGROUND

[0004] In view of the problems of large network burden and user privacy caused by the existing application perception technology scheme, an (Application Response Networking, ARN) technology is proposed, which specifically realizes introducing an ARN identification field in an (Internet Protocol, IP) packet header for interconnecting networks, bonding the application and the network through the ARN identification, and expressing the calling relationship between the application and the network as well as the demand for the network path, such as time delay, packet loss, jitter, bandwidth, QoS, interface and other path constraints.

[0005] In order to protect the security and isolation of network information and prevent the leakage of user application information and network path information, the ARN identification in different network domains is only valid in the network domain, which will cause the ARN identification recognition failure in the cross-domain transmission process, and further cause the problem of poor business performance. SUMMARY

[0006] The embodiments of the present application provide a communication method, network device, storage medium and computer program product, which can successfully identify the application identification in the cross-domain transmission process and improve the business performance.

[0007] The technical solution of the present application is implemented as follows:

[0008] In a first aspect, the embodiments of the present application provide a communication method applied to a first edge network device of a current domain, and the method comprises the following steps:

[0009] receiving a first message carrying a first application identification sent by a second edge network device of the current domain;

[0010] querying a second application identification mapped in a target domain from the first application identification in a first preset cross-domain mapping relationship;

[0011] replace the first application identifier with the second application identifier or delete the first application identifier and then add the second application identifier, to obtain a second packet;

[0012] send the second packet to the target domain.

[0013] In a second aspect, an embodiment of the present application provides a communication method, applied to a second edge network device of a current domain, and the method comprises:

[0014] sending a first packet carrying a first application identifier to a first edge network device of the current domain, so that the first edge network device queries a second application identifier mapped in a target domain from the first application identifier in a first preset cross-domain mapping relationship, and replaces the first application identifier with the second application identifier or deletes the first application identifier and then adds the second application identifier, to obtain a second packet, and sends the second packet to the target domain.

[0015] In a third aspect, an embodiment of the present application provides a communication method, applied to a third edge network device of a target domain, and the method comprises:

[0016] receiving a first packet carrying a first application identifier sent by a first edge device of a current domain;

[0017] querying a second application identifier mapped in a target domain from the first application identifier in a second preset cross-domain mapping relationship;

[0018] mapping a segment routing policy tunnel and / or a slice in the target domain according to a policy corresponding to the second application identifier.

[0019] In a fourth aspect, an embodiment of the present application provides a first edge network device, which comprises:

[0020] a first receiving unit configured to receive a first packet carrying a first application identifier sent by a second edge network device of a current domain;

[0021] a first querying unit configured to query a second application identifier mapped in a target domain from the first application identifier in a first preset cross-domain mapping relationship;

[0022] a replacing unit configured to replace the first application identifier with the second application identifier or delete the first application identifier and then add the second application identifier, to obtain a second packet;

[0023] a first sending unit configured to send the second packet to the target domain.

[0024] In a fifth aspect, an embodiment of the present application provides a second edge network device, which comprises:

[0025] a second sending unit, configured to send a first message carrying a first application identifier to a first edge network device of a current domain, so that the first edge network device queries a second application identifier mapped by the first application identifier in a target domain from a first preset cross-domain mapping relationship, and replaces the first application identifier with the second application identifier or deletes the first application identifier and adds the second application identifier to obtain a second message, and sends the second message to the target domain.

[0026] In a sixth aspect, an embodiment of the present application provides a third edge network device, which comprises:

[0027] a third receiving unit, configured to receive a first message carrying a first application identifier sent by a first edge device of a current domain;

[0028] a second querying unit, configured to query a second application identifier mapped by the first application identifier in a target domain from a second preset cross-domain mapping relationship;

[0029] a mapping unit, configured to map a segment routing policy tunnel and / or a slice in the target domain according to a policy corresponding to the second application identifier.

[0030] In a seventh aspect, an embodiment of the present application provides a first edge network device, which comprises a first processor, a first memory and a first communication bus; the first processor implements the communication method when executing a running program stored in the first memory.

[0031] In an eighth aspect, an embodiment of the present application provides a second edge network device, which comprises a second processor, a second memory and a second communication bus; the second processor implements the communication method when executing a running program stored in the second memory.

[0032] In a ninth aspect, an embodiment of the present application provides a third edge network device, which comprises a third processor, a third memory and a third communication bus; the third processor implements the communication method when executing a running program stored in the third memory.

[0033] In a tenth aspect, an embodiment of the present application provides a storage medium, which stores a computer program; the computer program is executed by a first processor to implement the communication method applied to the first edge network device, or the computer program is executed by a second processor to implement the communication method applied to the second edge network device, or the computer program is executed by a third processor to implement the communication method applied to the third edge network device.

[0034] In a eleventh aspect, an embodiment of the present application provides a computer program product, comprising a computer program which, when executed by a first processor, implements the communication method applied to the first edge network device, or the computer program which, when executed by a second processor, implements the communication method applied to the second edge network device, or the computer program which, when executed by a third processor, implements the communication method applied to the third edge network device.

[0035] The embodiment of the present application provides a communication method and a network device, a storage medium and a computer program product, which are applied to a first edge network device in a current domain. The method comprises the following steps: receiving a first message carrying a first application program response network application identifier, which is sent by a second edge network device in the current domain; querying a second application identifier mapped in a target domain from the first application identifier in a first preset cross-domain mapping relationship; replacing the first application identifier with the second application identifier or deleting the first application identifier and then adding the second application identifier to obtain a second message; and sending the second message to the target domain. By using the first preset cross-domain mapping relationship, the second application identifier mapped from the first application identifier in the target domain is determined, the first application identifier in the first message is replaced with the second application identifier or the first application identifier is deleted and then the second application identifier is added to obtain the second message, and then the second message is sent to the target domain, so that the target domain can identify the second application identifier in the second message, and thus the application identifier can be successfully identified in the cross-domain transmission process, and the service performance is improved. BRIEF DESCRIPTION OF DRAWINGS

[0036] FIG. 1 is a schematic diagram of a network tunnel / slice identified by an ARN identifier;

[0037] FIG. 2 is a flowchart of a communication method according to an embodiment of the present application;

[0038] FIG. 3 is a schematic diagram of an exemplary APN networking according to an embodiment of the present application;

[0039] FIG. 4 is a flowchart of a communication method according to an embodiment of the present application;

[0040] FIG. 5 is a schematic diagram of an exemplary IPv6 message header conversion according to an embodiment of the present application;

[0041] FIG. 6 is a schematic diagram of an exemplary aggregation mapping according to an embodiment of the present application;

[0042] FIG. 7 is a flowchart of a communication method according to an embodiment of the present application;

[0043] FIG. 8 is a schematic diagram of a first edge network device according to an embodiment of the present application;

[0044] FIG. 9 is a structural schematic diagram of a first edge network device according to an embodiment of the present application;

[0045] FIG. 10 is a structural schematic diagram of a second edge network device according to an embodiment of the present application;

[0046] FIG. 11 is a structural schematic diagram of a second edge network device according to an embodiment of the present application;

[0047] FIG. 12 is a structural schematic diagram of a third edge network device according to an embodiment of the present application;

[0048] FIG. 13 is a structural schematic diagram of a third edge network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0049] In order to enable a person skilled in the art to more fully understand the features and technical contents of the embodiments of the present application, the implementation of the embodiments of the present application will be described in detail below with reference to the accompanying drawings, which are only used for reference and are not intended to limit the embodiments of the present application.

[0050] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present application belongs. The terms used herein are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0051] In the following description, "some embodiments" are described, which describe a subset of all possible embodiments, but it can be understood that "some embodiments" can be the same subset or different subsets of all possible embodiments, and can be combined with each other without conflict. It should be noted that the terms "first, second, third" involved in the embodiments of the present application are only used to distinguish similar objects, and do not represent a specific order of the objects. Understandably, "first, second, third" can be interchanged with a specific order or sequence as allowed, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0052] The current ARN identifier is mainly applied on network boundary service access points (such as edge routers (Provider Edge, PE), broadband remote access servers (Broadband Remote Access Server, BRAS) / broadband network gateways (Broadband Network Gateway, BNG)). After receiving the network service subscription demand of the user side device, the controller sets the corresponding color or Flex-Algo algorithm identifier according to the network service subscription demand to perform segment routing (Segment Routing, SR), SRv6 or slice policy routing, obtains the corresponding tunnel or slice, and generates the ARN identifier according to the source address information or link information, and then identifies the user side device, and then sends <terminal, ARN identifier> to the network boundary service access point, and associates it with the network resource <slice or tunnel, routing policy>, to complete the network side configuration. On the user side device, the controller sends the ARN identifier to the user side device, so that the user side device can mark the ARN identifier according to the application type in the subsequent application process, and when sending the message to the network boundary service access point, the legality can be checked to realize the calling of the corresponding network capability. The user side device can also bind the ARN identifier through the access control list (Access Control Lists, ACL), specify the link and the like, and mark the ARN identifier in the user side message.

[0053] Referring to FIG. 1, the controller can control the user network (CPE1), the service provider network and the user network (CPE2), the user side service information of the user and the contract corresponding relationship is configured in CPE1, the routing policy and the network side connection information of the tunnel or slice corresponding relationship are configured in the service provider network, wherein the contract in CPE1 is associated with the network side connection information, the user message carries the user ID and carries the contract ID, referring to FIG. 1, the ARN identifier can be equivalent to the routing policy color or the algorithm identifier of Flex-Algo, after the user message enters the network boundary service access node of the service provider network, the network boundary service access node can obtain the user side device information according to the source IP, and then the legality of the ARN identifier is checked, and then the ARN identifier is mapped to a specific network tunnel / slice.

[0054] In order to protect the security and isolation of network information, prevent the leakage of application information and network path information, consider that the scope of the label ARN identifier identifying network and application capability is only locally effective in the network domain, and different ARN identifier life cycles are independent of each other, and the customer needs to carry the local ARN identifier in the message.

[0055] The ARN identifier allocated in the network A domain can only be recognized in the network A domain and mapped to a corresponding Segment Routing IPv6 (SRv6) policy tunnel / slice, and cannot be recognized in the network B domain and the region of the cloud, which can cause the ARN identifier to fail to be recognized in the process of cross-domain transmission, and further cause the problem of poor service performance.

[0056] To solve the above problems, an embodiment of the present application provides a communication method, as shown in FIG. 2, applied to a first edge network device of a current domain, which can include the following steps:

[0057] S101, receiving a first message carrying a first application identifier sent by a second edge network device of the current domain.

[0058] In the embodiment of the present application, the second edge network device of the current domain sends the first message carrying the first application identifier to the first edge network device of the current domain. The second edge network device can directly send the first message to the first edge network device. The second edge network device can also aggregate and map the third application identifier after receiving the third message carrying the third application identifier sent by the terminal, and then send the first message generated by the aggregation and mapping to the first edge network device.

[0059] In the embodiment of the present application, the application identifier can be an ARN identifier.

[0060] S102, querying a second application identifier mapped by the first application identifier in a target domain from a first preset cross-domain mapping relationship.

[0061] In the embodiment of the present application, the first edge network device supports the ARN cross-domain mapping function.

[0062] It should be noted that the application identifier is allocated by a controller in each domain. Different application identifiers are allocated and issued in different domains for the same application requirement network path. The controller pulls the mapping relationship between the application identifiers allocated in different domains for the same application requirement network path, obtains the first preset cross-domain mapping relationship, and issues the first preset cross-domain mapping relationship to the first edge network device.

[0063] It should be noted that the controller can obtain the first preset cross-domain mapping relationship and issue it to the first edge network device by any one of the following two methods, which can be selected according to actual conditions, and the present application does not make specific limitations.

[0064] In an optional embodiment, the first preset cross-domain mapping relationship is that the domain controller of the current domain establishes a mapping relationship between the application identifier allocated in the current domain and the application identifier allocated in the target domain for a network path required by the same application after receiving the application identifier allocated in the target domain, and sends the mapping relationship to the first edge network device.

[0065] In another optional embodiment, the first preset cross-domain mapping relationship is that the service orchestration system establishes a mapping relationship between the application identifier allocated in the current domain and the application identifier allocated in the target domain for a network path required by the same application after receiving the application identifier allocated in the current domain and the application identifier allocated in the target domain, and sends the mapping relationship to the first edge network device through the domain controller of the current domain.

[0066] S103, replacing the first application identifier with the second application identifier or deleting the first application identifier and then adding the second application identifier to obtain a second packet.

[0067] It should be noted that the writing process of popping out the first application identifier and then pressing in the second application identifier can also be performed to realize the process of replacing the application identifier.

[0068] S104, sending the second packet to the target domain.

[0069] In the embodiment of the application, the target domain is a target network domain or a target cloud domain.

[0070] In an optional embodiment, if the target domain is a target network domain, the second packet is sent to a third edge network device of the target network domain, so that the third edge network device maps a segment routing policy tunnel and / or a slice in the target network domain according to a policy corresponding to the second application identifier.

[0071] It should be noted that in the above embodiment, the mapping from the first edge network device to the third edge network device of the target network domain is a network domain cross-domain mapping.

[0072] The ARN networking can be seen from FIG. 3. A user terminal accesses a BRAS of a network A domain through a passive optical network (PON), the network A domain establishes a network-cloud cross-domain connection between the cloud A domain through a Metro Backbone (MB) and a Virtual Gateway (vGW) of the cloud A domain, the network A domain establishes a network cross-domain connection between the network B domain through a landing PE and a cloud network PE of the network B domain, and the network B domain establishes a network-cloud cross-domain connection between the cloud B domain through a cloud PE and a vGW of the cloud B domain. The network A domain is a metropolitan area network, and the network B domain is a backbone network.

[0073] It should be noted that in the above embodiment, the first edge network device of the current domain can be a landing PE in the network A domain in FIG. 3, and the third edge network device can be a cloud network PE in the network B domain in FIG. 3.

[0074] In another optional embodiment, if the target domain is a target cloud domain, the second packet is sent to a fourth edge network device of the target cloud domain, so that the fourth edge network device implements corresponding services according to the second application identifier mapped to the target service chain node.

[0075] In the embodiment of the present application, the target service chain node can implement security value-added services such as firewall and traffic cleaning, application acceleration, audio and video processing, etc. through SRv6, Network Service Header (NSH), ACL redirection, etc.

[0076] It should be noted that the traditional SRv6 service chain segment identifier (Segment Identifier, SID) method needs to allocate a SID for each service and publish related routes. The application identifier method can greatly simplify this SID and route allocation method, and only use the application identifier to pull through the network and service capabilities. The SID only serves as a network path identifier, reducing the coupling degree with the service.

[0077] It should be noted that in the above embodiment, the mapping from the first edge network device to the fourth edge network device of the target cloud domain is a network-cloud cross-domain mapping.

[0078] It should be noted that in the above embodiment, the first edge network device of the current domain can be an MB in the network A domain in FIG. 3, or a cloud PE in the network B domain; correspondingly, the fourth edge network device can be a vGW of the cloud A domain in FIG. 3, or a vGW in the cloud B domain.

[0079] It should be noted that after S102, the application identifier can also be updated by a manual configuration method. Specifically, the first application identifier configured in the flow label, or the Destination Options Header (DOH), or the Hop-by-Hop Options header (HBH) of the first packet is changed to the second application identifier to obtain a modified first packet; and the modified first packet is sent to the target domain.

[0080] It should be noted that the application identifier can also be in the IPv6 extension option header DOH, HBH. Here, the first application identifier can be changed to the second application identifier by configuring the IPv6 extension option header DOH, HBH.

[0081] It can be understood that, by using the first preset cross-domain mapping relationship, the first application identifier of the current domain is determined to be mapped to the second application identifier after the target domain, and the first application identifier in the first message is replaced by the second application identifier or the first application identifier is deleted and then the second application identifier is added, to obtain a second message, and then the second message is sent to the target domain. The target domain can identify the second application identifier in the second message, so that the application identifier can be successfully identified in the cross-domain transmission process, and the service performance is improved.

[0082] Based on the above embodiments, the embodiments of the application also propose a communication method applied to a second edge network device of a current domain, as shown in FIG. 4, which can include:

[0083] S201, sending a first message carrying a first application identifier to a first edge network device of a current domain; querying, by the first edge network device, a second application identifier to which the first application identifier is mapped in a target domain from a first preset cross-domain mapping relationship; replacing the first application identifier by the second application identifier or deleting the first application identifier and then adding the second application identifier to obtain a second message; and sending the second message to the target domain.

[0084] In some embodiments, the terminal can be referred to as a user equipment (UE). The terminal can be a personal communication service (PCS) phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), and the like. The terminal device can also be a smart phone, a tablet computer, a palm computer, a mobile station (MS), a mobile terminal (MT), and the like. The terminal device can communicate with one or more network devices through a radio access network (RAN). For example, the terminal device can be a mobile phone (or called a "cellular" phone) or a computer with a terminal device, etc. For example, the terminal device can also be a portable, pocket, handheld, built-in computer, or vehicle-mounted mobile device that exchanges voice and / or data with a radio access network. The terminal device can also be a handheld device, a computing device, or other processing device connected to a wireless modem with wireless communication function, a vehicle-mounted device, a wearable device, a terminal device in a future evolved network, and the like. The application implementation is not limited.

[0085] In the embodiment of the present application, the terminal side carries the first application identifier through an existing message field (such as the flow label field (flow label) of SRv6, occupying 20 bits); the network side provides corresponding service guarantee by identifying the first application identifier and combining network new capabilities such as slices, G-SRv6 policies, etc.

[0086] In an optional embodiment, the carrying mode adopts an Internet Protocol Version 6 (IPv6) header escape mode, multiplexing the 20 bits of the flow label, as shown in FIG. 5, indicating whether to escape through 10-11 bits. If it is 1, the flow label is escaped into an ARN ID.

[0087] It should be noted that the 10-11 bits in the standard are the highest bits of the traffic class (TC), and the highest bits of TC have been defined as the explicit congestion notification (Traffic Class, ECN). Since ECN is not enabled in a wide area network, the present application does not conflict with ECN.

[0088] In the embodiment of the present application, the second edge network device of the current domain can be the BRAS in the network A domain in FIG. 3.

[0089] In the embodiment of the present application, on the one hand, the second edge network device can receive the first message carrying the first application identifier sent by the terminal, and then directly send the first message carrying the first application identifier to the first edge network device of the current domain. On the other hand, the second edge network device can also receive the third message carrying the third application identifier sent by the terminal; query the first application identifier aggregated and mapped by the third application identifier from the preset aggregation mapping relationship; replace the third application identifier with the first application identifier to obtain the first message; and then send the first message carrying the first application identifier to the first edge network device of the current domain.

[0090] In the embodiment of the present application, the preset aggregation mapping relationship is sent to the second edge node by the domain controller of the current domain after establishing the mapping relationship of the terminal side application identifier to the network side application identifier aggregation for the network path required by the same application.

[0091] It should be noted that the user side application identifier is allocated by the in-domain controller, and the corresponding user side to network side application identifier aggregation mapping relationship for the network path required by the same application is established, and the preset aggregation mapping relationship is downloaded to the second edge network device. The second edge network device supports the opening of the ARN aggregation mapping function.

[0092] It should be noted that the application identifier allocated by the user side can be one for each terminal (which can be a random number), but the network service level is limited, so it is necessary to aggregate the application identifiers in the scenario of multiple terminals but the same network service level, that is, the same SRv6 policy tunnel or slice can be provided for multiple terminals to ensure the simple operation and maintenance and reuse of network service capabilities. At the same time, the user side is different, which can ensure the privacy of the user side and the security of the network side service capability opening.

[0093] Referring to FIG. 6, the ARN ID1, ARN ID2 and ARN ID3 of the user side can be queried to correspond to the ARN ID10 of the network side by querying the ARN aggregation mapping relationship table (preset aggregation mapping relationship).

[0094] It should be noted that in addition to the aggregation mapping for the network domain cross-domain, the mapping can also be performed for the network-to-cloud scenario, and the aggregation processing is performed between the cloud PE and the cloud network device vGW.

[0095] In the embodiment of the application, the application identifier is carried by the user message, and when entering the large network, the SRv6 tunnel is generally encapsulated, which is copied from the flowlabel field of the inner layer IPv6 message to the outer layer, mainly including the uniform (Uniform) mode and the pipe (Pipe) mode.

[0096] In an optional embodiment, the Uniform mode is used for tunnel encapsulation post-processing, and specifically, the first application identifier is copied into the message header of the tunnel, and the first message is transmitted to the first edge network device through the tunnel.

[0097] It should be noted that the Uniform mode is adopted when the network side considers that the first application identifier is trusted, and the ARN value in the flowlabel field of the first message is directly copied into the flowlabel field of the SRv6 message header of the outer layer tunnel by the tunnel entry node (the second edge network device), and when the first message is out of the tunnel for IP forwarding, the ARN value in the flowlabel is copied back to the first message by the tunnel exit node (the first edge network device).

[0098] In another optional embodiment, the Pipe mode is used for tunnel encapsulation post-processing, and specifically, the application identifier is added to the message header of the tunnel, and the first message is transmitted to the first edge network device through the tunnel.

[0099] It should be noted that when the network side considers that the first application identifier is untrusted, the Pipe mode can be adopted; the first application identifier is ignored, the flowlabel field in the SRv6 message header is revalued at the tunnel entry node, and from the tunnel entry node to the tunnel exit node, the traffic is scheduled according to the network side configuration, and after the tunnel, the traffic is forwarded according to the first application identifier originally carried, without changing the inner message.

[0100] It can be understood that by using the first preset cross-domain mapping relationship, the first application identifier of the current domain is determined to be mapped to the second application identifier of the target domain, and the first application identifier in the first message is replaced by the second application identifier or the first application identifier is deleted and then the second application identifier is added to obtain the second message, and then the second message is sent to the target domain. The target domain can identify the second application identifier in the second message, so that the application identifier can be successfully identified in the cross-domain transmission process, and the service performance is improved.

[0101] Based on the above embodiments, the embodiments of the present application also propose a communication method applied to a third edge network device of a target domain, as shown in FIG. 7, the method comprises:

[0102] S301, receiving a first message carrying a first application identifier sent by a first edge device of a current domain.

[0103] S302, querying a second application identifier mapped by the first application identifier in the target domain from a second preset cross-domain mapping relationship.

[0104] In the embodiments of the present application, the third edge network device supports opening the ARN cross-domain mapping function.

[0105] It should be noted that the application identifier is allocated by the controller in each domain, and different application identifiers are allocated and issued in different domains for the same application requirement network path. The controller of the target domain pulls the mapping relationship between the application identifiers allocated in different domains for the same application requirement network path, obtains the second preset cross-domain mapping relationship, and the controller of the target domain issues the second preset cross-domain mapping relationship to the third edge network device.

[0106] It should be noted that the controller of the target domain obtains the second preset cross-domain mapping relationship and issues it to the third edge network device by any one of the following two methods, which can be selected according to actual conditions, and the embodiments of the present application do not make specific limitations.

[0107] In one embodiment, the second preset cross-domain mapping relationship is that the domain controller of the target domain establishes a mapping relationship between the application identifier allocated in the current domain and the application identifier allocated in the target domain for the same application requirement network path after receiving the application identifier allocated in the current domain, and sends it to the third edge network device.

[0108] In another embodiment, the second preset cross-domain mapping relationship is that, after receiving the application identifier allocated in the current domain and the application identifier allocated in the target domain, the service orchestration system establishes a mapping relationship between the application identifier allocated in the current domain and the application identifier allocated in the target domain for the network path required by the same application, and sends the mapping relationship to the third edge network device through the domain controller of the target domain.

[0109] S303, mapping the segment routing policy tunnel and / or slice in the target domain according to the policy corresponding to the second application identifier.

[0110] It should be noted that, after S302, the update of the application identifier can also be performed in a manual configuration manner, specifically, the first application identifier configured by the flow label, or DOH, or HBH of the first packet is changed to the second application identifier.

[0111] It should be noted that the application identifier can also be in the IPv6 extension option header DOH, HBH, and here the first application identifier can be changed to the second application identifier for the IPv6 extension option header DOH, HBH.

[0112] It can be understood that, after the first edge device of the current domain sends the first packet carrying the first application identifier to the third edge network device of the target domain, the third edge network device can determine the second application identifier of the first application identifier of the current domain after mapping to the target domain by using the second preset cross-domain mapping relationship, and then map the segment routing policy tunnel and / or slice in the target domain according to the policy corresponding to the second application identifier, thereby successfully identifying the application identifier in the cross-domain transmission process, and further improving the service performance.

[0113] Embodiments of the present application provide a first edge network device 1. As shown in FIG. 8, the first edge network device 1 comprises:

[0114] A first receiving unit 10 configured to receive a first packet carrying a first application identifier sent by a second edge network device of a current domain;

[0115] A first query unit 11 configured to query a second application identifier mapped in a target domain for the first application identifier from a first preset cross-domain mapping relationship;

[0116] A replacement unit 12 configured to replace the first application identifier with the second application identifier or delete the first application identifier and then add the second application identifier to obtain a second packet;

[0117] A first sending unit 13 configured to send the second packet to the target domain.

[0118] Optionally, the first preset cross-domain mapping relationship is that the domain controller of the current domain establishes a mapping relationship between the application identifier allocated in the current domain and the application identifier allocated in the target domain for a network path required by the same application after receiving the application identifier allocated in the target domain, and sends the mapping relationship to the first edge network device.

[0119] Optionally, the first preset cross-domain mapping relationship is that the service orchestration system establishes a mapping relationship between the application identifier allocated in the current domain and the application identifier allocated in the target domain for a network path required by the same application after receiving the application identifier allocated in the current domain and the application identifier allocated in the target domain, and sends the mapping relationship to the first edge network device through the domain controller of the current domain.

[0120] Optionally, the first edge network device further comprises a first changing unit.

[0121] The first changing unit is configured to change the first application identifier configured in the flow label, or the destination option header (DOH), or the hop-by-hop option header (HBH) of the first packet to a second application identifier, to obtain a modified first packet.

[0122] The first sending unit 13 is further configured to send the modified first packet to the target domain.

[0123] Optionally, the first sending unit 13 is further configured to send the second packet to a third edge network device of the target network domain, so that the third edge network device maps a segment routing policy tunnel and / or a slice in the target network domain according to a policy corresponding to the second application identifier; or send the second packet to a fourth edge network device of the target cloud domain, so that the fourth edge network device implements corresponding services by mapping the second application identifier to a target service chain node.

[0124] The first edge network device provided in the embodiment of the present application receives a first message carrying a first application identifier sent by a second edge network device of a current domain; queries a second application identifier to which the first application identifier is mapped in a target domain from a first preset cross-domain mapping relationship; replaces the first application identifier with the second application identifier or deletes the first application identifier and then adds the second application identifier to obtain a second message; and sends the second message to the target domain. It can be seen that the first edge network device provided in the embodiment determines the second application identifier to which the first application identifier of the current domain is mapped in the target domain by using the first preset cross-domain mapping relationship, replaces the first application identifier in the first message with the second application identifier or deletes the first application identifier and then adds the second application identifier to obtain the second message, and then sends the second message to the target domain. The target domain can identify the second application identifier in the second message, so that the application identifier can be successfully identified in the cross-domain transmission process, and the service performance is improved.

[0125] FIG. 9 is a schematic diagram of a second component structure of the first edge network device 1 provided in the embodiment of the present application. In actual application, based on the same disclosure concept of the above embodiment, as shown in FIG. 9, the first edge network device 1 of the embodiment includes a first processor 14, a first memory 15 and a first communication bus 16.

[0126] The first processor 14 can be at least one of an application specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), a field programmable gate array (FPGA), a CPU, a controller, a microcontroller, and a microprocessor. It can be understood that, for different devices, the electronic device used to implement the above processor functions can also be other devices, which is not specifically limited in the embodiment.

[0127] In the embodiment of the present application, the first communication bus 16 is used to realize the connection and communication between the first processor 14 and the first memory 15; and the first processor 14 realizes the following communication method when executing the running program stored in the first memory 15.

[0128] receive a first message carrying a first application identifier sent by a second edge network device of the current domain; query a second application identifier mapped in the target domain for the first application identifier from a first preset cross-domain mapping relationship; replace the first application identifier with the second application identifier or delete the first application identifier and then add the second application identifier to obtain a second message; and send the second message to the target domain.

[0129] Further, the first preset cross-domain mapping relationship is that a domain controller of the current domain establishes a mapping relationship between an application identifier allocated in the current domain and an application identifier allocated in the target domain for a network path required by the same application after receiving the application identifier allocated in the target domain, and sends the mapping relationship to the first edge network device.

[0130] Further, the first preset cross-domain mapping relationship is that a service orchestration system establishes a mapping relationship between an application identifier allocated in the current domain and an application identifier allocated in the target domain for a network path required by the same application after receiving the application identifier allocated in the current domain and the application identifier allocated in the target domain, and sends the mapping relationship to the first edge network device through the domain controller of the current domain.

[0131] Further, the first processor 14 is further configured to change the first application identifier configured in a flow label, or a destination option header DOH, or a hop-by-hop option header HBH of the first message to the second application identifier to obtain a modified first message; and send the modified first message to the target domain.

[0132] Further, the target domain is a target network domain or a target cloud domain.

[0133] The first processor 14 is further configured to send the second message to a third edge network device of the target network domain, so that the third edge network device maps a segment routing policy tunnel and / or a slice in the target network domain according to a policy corresponding to the second application identifier; or send the second message to a fourth edge network device of the target cloud domain, so that the fourth edge network device implements corresponding services by mapping the second application identifier to a target service chain node.

[0134] Based on the above embodiment, the embodiment of the application further proposes a second edge network device 2, as shown in FIG. 10, the second edge network device 2 comprises:

[0135] The second sending unit 21 is configured to send a first message carrying a first application identifier to a first edge network device of a current domain; the first edge network device is configured to query a second application identifier mapped by the first application identifier in a target domain from a first preset cross-domain mapping relationship; the second application identifier is used to replace the first application identifier or the first application identifier is deleted and then the second application identifier is added to obtain a second message; and the second message is sent to the target domain.

[0136] Optionally, the second edge network device further comprises a second receiving unit, a querying unit and a replacing unit.

[0137] The second receiving unit is configured to receive a third message carrying a third application identifier sent by a terminal.

[0138] The querying unit is configured to query the first application identifier aggregated and mapped by the third application identifier from a preset aggregated mapping relationship.

[0139] The replacing unit is configured to replace the third application identifier with the first application identifier to obtain the first message.

[0140] Optionally, the preset aggregated mapping relationship is sent to the second edge node after the domain controller of the current domain establishes the mapping relationship of the terminal-side application identifier to the network-side application identifier aggregation for the same application requirement network path.

[0141] Optionally, the second sending unit 21 is further configured to copy the first application identifier into a message header of a tunnel and transmit the first message to the first edge network device through the tunnel.

[0142] Optionally, the second sending unit 21 is further configured to add an application identifier to a message header of a tunnel and transmit the first message to the first edge network device through the tunnel.

[0143] Optionally, the second receiving unit is further configured to receive a first message carrying a first application identifier sent by a terminal.

[0144] The second edge network device provided in the embodiment of the present application sends a first message carrying a first application identifier to a first edge network device of a current domain; the first edge network device queries a second application identifier to which the first application identifier is mapped in a target domain from a first preset cross-domain mapping relationship; the second application identifier is used to replace the first application identifier or the first application identifier is deleted and then the second application identifier is added to obtain a second message; and the second message is sent to the target domain. As can be seen, the second edge network device provided in the embodiment uses the first preset cross-domain mapping relationship to determine the second application identifier to which the first application identifier of the current domain is mapped in the target domain, and replaces the first application identifier in the first message with the second application identifier or deletes the first application identifier and then adds the second application identifier to obtain the second message, and then sends the second message to the target domain, so that the target domain can identify the second application identifier in the second message, thereby successfully identifying the application identifier in the cross-domain transmission process and further improving the service performance.

[0145] Fig. 11 is a schematic diagram of a second edge network device 2 provided in an embodiment of the present application, in actual application, based on the same disclosure concept of the above-mentioned embodiment, as shown in Fig. 11, the second edge network device 2 of the embodiment comprises a second processor 22, a second memory 23 and a second communication bus 24.

[0146] The above-mentioned second processor 22 can be at least one of an ASIC, a DSP, a DSPD, a PLD, an FPGA, a CPU, a controller, a microcontroller, a microprocessor. It can be understood that for different devices, the electronic device used to realize the function of the above-mentioned processor can also be other, and the embodiment is not limited specifically.

[0147] In the embodiment of the present application, the above-mentioned second communication bus 24 is configured to realize the connection communication between the second processor 22 and the second memory 23; and the above-mentioned second processor 22 realizes the following communication method when executing the running program stored in the second memory 23:

[0148] sending a first message carrying a first application identifier to a first edge network device of a current domain; querying, by the first edge network device, a second application identifier to which the first application identifier is mapped in a target domain from a first preset cross-domain mapping relationship; using the second application identifier to replace the first application identifier or deleting the first application identifier and then adding the second application identifier to obtain a second message; and sending the second message to the target domain.

[0149] Further, the second processor 22 is further configured to receive a third message carrying a third application identifier sent by the terminal; query the first application identifier aggregated and mapped by the third application identifier from a preset aggregation mapping relationship; and replace the third application identifier with the first application identifier to obtain the first message.

[0150] Further, the preset aggregation mapping relationship is sent to the second edge node by a domain controller of the current domain after the domain controller establishes the mapping relationship of the terminal-side application identifier to the network-side application identifier aggregation for the network path required by the same application.

[0151] Further, the second processor 22 is further configured to copy the first application identifier into a message header of a tunnel, and transmit the first message to the first edge network device through the tunnel.

[0152] Further, the second processor 22 is further configured to add an application identifier to a message header of a tunnel, and transmit the first message to the first edge network device through the tunnel.

[0153] Further, the second processor 22 is further configured to receive a first message carrying a first application identifier sent by the terminal.

[0154] Based on the above embodiment, the embodiment of the application further proposes a third edge network device 3, as shown in FIG. 12, the third edge network device 3 comprises:

[0155] A third receiving unit 30 configured to receive a first message carrying a first application identifier sent by a first edge device of a current domain;

[0156] A second querying unit 31 configured to query a second application identifier mapped in a target domain by the first application identifier from a second preset cross-domain mapping relationship;

[0157] A mapping unit 32 configured to map a segment routing policy tunnel and / or a slice in the target domain according to a policy corresponding to the second application identifier.

[0158] Optionally, the second preset cross-domain mapping relationship is a mapping relationship between an application identifier allocated in the current domain and an application identifier allocated in the target domain established by a domain controller of the target domain after the domain controller receives the application identifier allocated in the current domain, and is sent to the third edge network device.

[0159] Optionally, the second preset cross-domain mapping relationship is a mapping relationship between the application identifier allocated in the current domain and the application identifier allocated in the target domain, which is established by the business arrangement system according to a network path required by the same application after the business arrangement system receives the application identifier allocated in the current domain and the application identifier allocated in the target domain, and is sent to the third edge network device through the domain controller of the target domain.

[0160] Optionally, the third edge network device further comprises a second changing unit.

[0161] The second changing unit is configured to change the first application identifier configured in the flow label, or the destination option header (DOH), or the hop-by-hop option header (HBH) of the first message to a second application identifier.

[0162] The third edge network device provided by the embodiment of the present application receives the first message carrying the first application identifier sent by the first edge device of the current domain; queries the second application identifier mapped in the target domain for the first application identifier from the second preset cross-domain mapping relationship; and maps the segment routing policy tunnel and / or slice in the target domain according to the policy corresponding to the second application identifier. As can be seen, the third edge network device provided by the embodiment of the present application can determine the second application identifier mapped in the target domain for the first application identifier of the current domain by using the second preset cross-domain mapping relationship after the first edge device of the current domain sends the first message carrying the first application identifier to the third edge network device of the target domain, and then map the segment routing policy tunnel and / or slice in the target domain according to the policy corresponding to the second application identifier, so that the application identifier can be successfully identified in the cross-domain transmission process, and the service performance is improved.

[0163] FIG. 13 is a schematic diagram of the composition structure of a third edge network device 3 provided by an embodiment of the present application. In actual application, based on the same disclosure concept of the above-mentioned embodiment, as shown in FIG. 13, the third edge network device 3 of the embodiment comprises a third processor 33, a third memory 34 and a third communication bus 35.

[0164] The third processor 33 can be at least one of an ASIC, a DSP, a DSPD, a PLD, a FPGA, a CPU, a controller, a microcontroller, and a microprocessor. It can be understood that for different devices, the electronic device used to realize the function of the processor can also be other devices, which is not specifically limited in the embodiment.

[0165] In the embodiment of the present application, the third communication bus 35 is configured to realize the connection communication between the third processor 33 and the third memory 34; and the third processor 33 realizes the following communication method when executing the running program stored in the third memory 34.

[0166] receive a first message carrying a first application identifier sent by a first edge device of a current domain;

[0167] query a second application identifier mapped in a target domain for the first application identifier from a second preset cross-domain mapping relationship;

[0168] map a segment routing policy tunnel and / or a slice in the target domain according to a policy corresponding to the second application identifier.

[0169] Further, the second preset cross-domain mapping relationship is a mapping relationship between the application identifier allocated in the current domain and the application identifier allocated in the target domain established by a domain controller of the target domain for a network path required by the same application after receiving the application identifier allocated in the current domain, and sent to the third edge network device.

[0170] Further, the second preset cross-domain mapping relationship is a mapping relationship between the application identifier allocated in the current domain and the application identifier allocated in the target domain established by a service orchestration system for a network path required by the same application after receiving the application identifier allocated in the current domain and the application identifier allocated in the target domain, and sent to the third edge network device through the domain controller of the target domain.

[0171] Further, the third processor 33 is further configured to change the first application identifier configured by the flow label, or DOH, or HBH of the first message to the second application identifier.

[0172] The embodiment of the present application provides a storage medium, which has a computer program stored thereon. The computer readable storage medium stores one or more programs, and the one or more programs can be executed by one or more first processors, second processors or third processors. The computer program implements the communication method as described above.

[0173] Based on the above embodiment, the embodiment of the present application provides a computer program product, which includes a computer program. The computer program can be executed by one or more first processors, second processors or third processors. The computer program implements the communication method as described above.

[0174] It should be noted that, in this document, the term "comprising" or "including" or any other variant thereof is intended to cover non-exclusive inclusions, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or further includes elements inherent to such a process, method, article or device. Without more limitations, the element defined by the statement "including a" does not exclude the presence of another identical element in the process, method, article or device including the element.

[0175] Those skilled in the art can clearly understand the above-mentioned embodiment method can be realized by means of software and the necessary general hardware platform, of course, can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present disclosure essentially or the part that contributes to the related art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes a plurality of instructions for causing an image display device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of the present disclosure.

[0176] The above merely describes preferred embodiments of the present application, but is not intended to limit the scope of protection of the present application.

Claims

1. A communication method applied to a first edge network device of a current domain, the method comprising: receiving a first packet carrying a first application identifier sent by a second edge network device of the current domain; inquiring a second application identifier mapped by the first application identifier in a target domain from a first preset cross-domain mapping relationship; replacing the first application identifier with the second application identifier or deleting the first application identifier and adding the second application identifier to obtain a second packet; sending the second packet to the target domain.

2. The method of claim 1, wherein, The first preset cross-domain mapping relationship is established by a domain controller of the current domain for a network path required by the same application after receiving an application identifier allocated in the target domain, and is sent to the first edge network device.

3. The method of claim 1, wherein, The first preset cross-domain mapping relationship is established by a service orchestration system for a network path required by the same application after receiving an application identifier allocated in the current domain and an application identifier allocated in the target domain, and is sent to the first edge network device through the domain controller of the current domain.

4. The method of claim 1, wherein, After inquiring the corresponding second application identifier of the first application identifier from the first preset cross-domain mapping relationship, the method further comprises: changing the first application identifier configured in a flow label, or a destination option header (DOH), or a hop-by-hop option header (HBH) of the first packet to the second application identifier to obtain a modified first packet; sending the modified first packet to the target domain.

5. The method of claim 1, wherein, The target domain is a target network domain or a target cloud domain; and the sending of the second packet to the target domain comprises: sending the second packet to a third edge network device of the target network domain, so that the third edge network device maps a segment routing policy tunnel and / or a slice in the target network domain according to a policy corresponding to the second application identifier; or, sending the second packet to a fourth edge network device of the target cloud domain, so that the fourth edge network device implements corresponding services by mapping the second application identifier to a target service chain node.

6. The method of claim 1, wherein, After receiving the first packet carrying the first application identifier sent by the second edge network device of the current domain, the method further comprises: sending the first packet carrying the first application identifier to the first edge device of the current domain.

7. A communication method applied to a second edge network device of a current domain, the method comprising: sending a first packet carrying a first application identifier to the first edge network device of the current domain; inquiring a second application identifier mapped by the first application identifier in a target domain from a first preset cross-domain mapping relationship by the first edge network device; replacing the first application identifier with the second application identifier or deleting the first application identifier and adding the second application identifier to obtain a second packet; sending the second packet to the target domain.

8. The method of claim 7, wherein, Before the first message carrying the first application identifier is sent to the first edge network device of the current domain, the method further comprises: receiving a third message carrying a third application identifier sent by a terminal; querying the first application identifier aggregated and mapped by the third application identifier from a preset aggregation mapping relationship; replacing the third application identifier with the first application identifier to obtain the first message.

9. The method of claim 8, wherein, The first preset aggregation mapping relationship is a mapping relationship between a terminal side application identifier and a network side application identifier aggregation established by a domain controller of the current domain for a network path required by the same application, and is sent to the second edge node.

10. The method of claim 7, wherein, The first message is sent to the first edge network device of the current domain, comprising: copying the first application identifier to the message header of the tunnel, and transmitting the first message to the first edge network device through the tunnel.

11. The method of claim 7, wherein, The first message is sent to the first edge network device of the current domain, comprising: adding an application identifier to the message header of the tunnel, and transmitting the first message to the first edge network device through the tunnel.

12. The method of claim 7, wherein, Before the first message carrying the first application identifier is sent to the first edge network device of the current domain, the method further comprises: receiving a first message carrying a first application identifier sent by a terminal.

13. A communication method applied to a third edge network device of a target domain, the method comprising: receiving a first message carrying a first application identifier sent by a first edge device of a current domain; querying a second application identifier mapped in the target domain by the first application identifier from a second preset cross-domain mapping relationship; mapping a segment routing policy tunnel and / or a slice in the target domain according to a policy corresponding to the second application identifier.

14. The method of claim 13, wherein, The second preset cross-domain mapping relationship is a mapping relationship between an application identifier allocated in the current domain and an application identifier allocated in the target domain established by a domain controller of the target domain after receiving the application identifier allocated in the current domain, and is sent to the third edge network device.

15. The method of claim 13, wherein, The second preset cross-domain mapping relationship is a mapping relationship between the application identifier allocated in the current domain and the application identifier allocated in the target domain established by a service orchestration system after receiving the application identifier allocated in the current domain and the application identifier allocated in the target domain, and is sent to the third edge network device through the domain controller of the target domain.

16. The method of claim 13, wherein, After querying the second application identifier corresponding to the first application identifier from the second preset cross-domain mapping relationship, the method further comprises: changing the first application identifier configured by a flow label, or DOH, or HBH of the first message to the second application identifier.

17. A first edge network device, comprising: a first receiving unit configured to receive a first message carrying a first application identifier sent by a second edge network device of a current domain; a first querying unit configured to query a second application identifier mapped in a target domain by the first application identifier from a first preset cross-domain mapping relationship; The replacing unit is configured to replace the first application identifier with the second application identifier or delete the first application identifier and add the second application identifier to obtain a second packet; The first sending unit is configured to send the second packet to the target domain.

18. A second edge network device, comprising: A second sending unit configured to send a first packet carrying a first application identifier to a first edge network device of a current domain; The first edge network device is configured to query a second application identifier mapped by the first application identifier in a target domain from a first preset cross-domain mapping relationship; The replacing unit is configured to replace the first application identifier with the second application identifier or delete the first application identifier and add the second application identifier to obtain a second packet; The first sending unit is configured to send the second packet to the target domain.

19. A third edge network device, comprising: A third receiving unit configured to receive a first packet carrying a first application identifier sent by a first edge device of a current domain; The second querying unit is configured to query a second application identifier mapped by the first application identifier in a target domain from a second preset cross-domain mapping relationship; The mapping unit is configured to map a segment routing policy tunnel and / or a slice in the target domain according to a policy corresponding to the second application identifier.

20. A first edge network device, the first edge network device comprising: A first processor, a first memory, and a first communication bus; The first processor executes a running program stored in the first memory to implement the method of any one of claims 1-6.

21. A second edge network device, the second edge network device comprising: A second processor, a second memory, and a second communication bus; The second processor executes a running program stored in the second memory to implement the method of any one of claims 7-12.

22. A third edge network device, the third edge network device comprising: A third processor, a third memory, and a third communication bus; The third processor executes a running program stored in the third memory to implement the method of any one of claims 13-16.

23. A storage medium having a computer program stored thereon, the computer program being executed by a first processor to implement the method of any one of claims 1-6, or the computer program being executed by a second processor to implement the method of any one of claims 7-12, or the computer program being executed by a third processor to implement the method of any one of claims 13-16.

24. A computer program product comprising a computer program, the computer program being executed by a first processor to implement the method of any one of claims 1-6, or the computer program being executed by a second processor to implement the method of any one of claims 7-12, or the computer program being executed by a third processor to implement the method of any one of claims 13-16.

Images