Method, device and system for sending message

Abstract

The present application discloses a method, device and system for sending a message, which belongs to the field of communication. The method includes: a first network element receives a first service message from a first network, the message header of the first service message includes IFIT message header information, the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, the target service flow is the service flow to which the first service message belongs, the first network element is used to connect the first network and the second network, the first network and the second network are two different types of networks; the first network element moves the IFIT message header information from the message header to the payload part of the first service message to obtain a second service message; the first network element sends the second service message to the second network. The present application can extend the maintenance of the service path.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a method, device and system for sending a message. Background Art

[0002] The service path between the base station and the core network passes through multiple different networks. For example, the service path between the base station and the core network can pass through a first multi-protocol label switching (MPLS) network, an Internet protocol (IP) network, and a second MPLS network, and the IP network is located between the first MPLS network and the second MPLS network. The base station is connected to the first MPLS network, and the core network is connected to the second MPLS network. The service path includes a first service path located in the first MPLS network, a second service path located in the IP network, and a third service path located in the second MPLS network.

[0003] For a service message sent by a base station to a core network, when the service message is transmitted in the first MPLS network, the message header of the service message includes an in-situ flow information telemetry (IFIT) message header, the IFIT message header is a special MPLS message header, the IFIT message header includes identification information and indication information of the service flow to which the service message belongs, and the indication information is used to indicate at least one performance parameter of the service flow to be collected. In this way, when the network element in the first MPLS network receives the service message, it collects the parameter value of the at least one performance parameter according to the IFIT message header and sends the parameter value of the at least one performance parameter to the controller. When the service message leaves the first MPLS network, the IFIT message header in the service message is deleted, that is, when the service message is transmitted in the IP network and the second MPLS network, the message header of the service message does not include the IFIT message header. The controller receives the parameter value of the performance parameter sent by the network element in the first MPLS network, and maintains the first service path in the first MPLS network according to the received parameter value.

[0004] For a service message sent from the core network to the base station, when the service message is transmitted in the second MPLS network, the message header of the service message includes an IFIT message header, and the IFIT message header includes identification information and indication information of the service flow to which the service message belongs, and the indication information is used to indicate at least one performance parameter of the service flow to be collected. In this way, when the network element in the second MPLS network receives the service message, it collects the parameter value of the at least one performance parameter according to the IFIT message header and sends the parameter value of the at least one performance parameter to the controller. When the service message leaves the second MPLS network, the IFIT message header in the service message is deleted, that is, when the service message is transmitted in the IP network and the first MPLS network, the message header of the service message does not include the IFIT message header. The controller receives the parameter value of the performance parameter sent by the network element in the second MPLS network, and maintains the third segment of the service path located in the second MPLS network according to the received parameter value.

[0005] In the process of implementing this application, the inventor found that the prior art has at least the following problems:

[0006] For service messages sent by the base station to the core network, only the network elements in the first MPLS network can collect the parameter values ​​of the performance parameters of the service flow; and for service messages sent by the base station to the core network, only the network elements in the second MPLS network can collect the parameter values ​​of the performance parameters of the service flow. This results in the controller being able to maintain only a section of the service path in one network, and the maintained path is too short. Summary of the invention

[0007] The present application provides a method, device and system for sending a message to extend the maintenance of a service path. The technical solution is as follows:

[0008] In a first aspect, an embodiment of the present application provides a method for sending a message, in which: a first network element receives a first service message from a first network, a message header of the first service message includes an IFIT message header information that identifies the flow detection scheme, and the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, the target service flow is the service flow to which the first service message belongs, and the first network element is used to connect the first network and the second network, and the first network and the second network are two different types of networks. The first network element moves the IFIT message header information from the message header to the payload part of the first service message to obtain a second service message. The first network element sends the second service message to the second network. Since the first network element moves the IFIT message header information from the message header to the payload part of the first service message, and then sends the second service message to the second network, for other network elements located after the first network element on the service path used to transmit the second service message, when other network elements receive the service message sent by the first network element, they collect the parameter values ​​of the performance parameters of the target service flow according to the IFIT message header information in the service message, and send them to the controller. The controller maintains the service path after the first network element according to the parameter values, thereby extending the length of the maintained service path.

[0009] In a possible implementation, the message header of the first service message also includes indication information, and the indication information is used to indicate that the first service message includes IFIT message header information. When the first network element determines that the first service message includes IFIT message header information based on the indication information, the first network element moves the IFIT message header information from the message header to the payload part of the first service message to obtain a second service message. Since the first network element first determines whether the first service message includes IFIT message header information based on the indication information in the message header of the first service message, and only moves the IFIT message header information when it is determined that the first service message includes IFIT message header information, it avoids the first network element performing a move operation when the IFIT message header information is not included in the first service message, thereby improving the success rate of the move and avoiding invalid operations.

[0010] In another possible implementation, the first network element moves the indication information from the message header to the payload part of the first service message, so that other network elements after the first network element determine whether to move the IFIT message header information according to the indication information, thereby improving the success rate of movement and avoiding invalid operations.

[0011] In another possible implementation, the first network element obtains IFIT message header information from the message header, adds the IFIT message header information at the start position of the payload part of the first service message, and deletes the IFIT message header information from the message header to obtain the second service message. Since the IFIT message header information is added at the start position of the payload part of the first service message, it is convenient for other network elements to read the IFIT message header information from the first service message.

[0012] In another possible implementation, the first network element collects the parameter value of at least one performance parameter of the target service flow according to the IFIT message header information; the first network element sends the parameter value of at least one performance parameter to the controller. The first network element also sends the parameter value to the controller, and other network elements on the service path for transmitting the first service message also send the parameter value to the controller, so that the controller can perform end-to-end maintenance on the service path.

[0013] In another possible implementation, the first network is a Multi-Protocol Label Switching (MPLS) network, and the second network is an Internet Protocol (IP) network.

[0014] In a second aspect, an embodiment of the present application provides a method for sending a message, in which a second network element receives a second service message from a second network, a payload portion of the second service message includes an IFIT message header information that identifies a flow detection scheme, and the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, the target service flow is a service flow to which the second service message belongs, and the second network element is used to connect the second network and the third network, and the second network and the third network are two different types of networks. The second network element moves the IFIT message header information from the payload portion to the message header of the second service message to obtain a first service message. The second network element sends the first service message to the third network. Since the second network element moves the IFIT message header information from the payload part to the message header of the first service message, and then sends the first service message to the third network, for other network elements located after the second network element on the service path used to transmit the first service message, when other network elements receive the service message sent by the second network element, they collect the parameter values ​​of the performance parameters of the target service flow according to the IFIT message header information in the service message, and send them to the controller. The controller maintains the service path after the second network element according to the parameter values, thereby extending the length of the maintained service path.

[0015] In a possible implementation, the payload part also includes indication information, and the indication information is used to indicate that the second service message includes IFIT message header information. When the first network element determines that the second service message includes IFIT message header information based on the indication information, the first network element moves the IFIT message header information from the payload part to the message header of the second service message to obtain the first service message. Since the second network element first determines whether the second service message includes IFIT message header information based on the indication information in the second service message, and only moves the IFIT message header information when it is determined that the second service message includes IFIT message header information, it avoids the second network element performing a move operation when the second service message does not include IFIT message header information, thereby improving the success rate of the move and avoiding invalid operations.

[0016] In another possible implementation, the second network element collects the parameter value of at least one performance parameter of the target service flow according to the IFIT message header information, and sends the parameter value of at least one performance parameter to the controller. The second network element also sends the parameter value to the controller, and other network elements on the service path for transmitting the service message also send the parameter value to the controller, so that the controller can perform end-to-end maintenance on the service path.

[0017] In another possible implementation, the third network is a Multi-Protocol Label Switching (MPLS) network, and the second network is an Internet Protocol (IP) network.

[0018] In a third aspect, an embodiment of the present application provides a method for sending a message, in which a third network element receives a second service message, and the payload portion of the second service message includes an IFIT message header information that identifies the flow detection scheme, and the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, and the target service flow is the service flow to which the second service message belongs. The third network element collects the parameter value of the at least one performance parameter of the target service flow according to the IFIT message header information. The third network element sends the parameter value of at least one performance parameter to the controller and sends the second service message. Since the payload portion of the second service message includes the IFIT message header information, the third network element can collect the parameter value according to the IFIT message header information and send the parameter value to the controller, so that the controller can maintain the service path used to transmit the second service message according to the parameter value sent by the third network element, thereby extending the length of the maintenance service path.

[0019] In a possible implementation, the payload part also includes indication information, and the indication information is used to indicate that the second service message includes the IFIT message header information. When the third network element determines that the second service message includes the IFIT message header information based on the indication information, the third network element collects the parameter value of at least one performance parameter of the target service flow based on the IFIT message header information. Since the third network element first determines whether the second service message includes the IFIT message header information based on the indication information in the second service message, the parameter value of at least one performance parameter of the target service flow is collected only when it is determined that the second service message includes the IFIT message header information, thereby improving the collection success rate.

[0020] In a fourth aspect, the present application provides a device for sending a message, which is used to execute the method in the first aspect or any possible implementation of the first aspect. Specifically, the device includes a unit for executing the method in the first aspect or any possible implementation of the first aspect.

[0021] In a fifth aspect, the present application provides a device for sending a message, which is used to execute the method in the second aspect or any possible implementation of the second aspect. Specifically, the device includes a unit for executing the method in the second aspect or any possible implementation of the second aspect.

[0022] In a sixth aspect, the present application provides a device for sending a message, which is used to execute the method in the third aspect or any possible implementation of the third aspect. Specifically, the device includes a unit for executing the method in the third aspect or any possible implementation of the third aspect.

[0023] In a seventh aspect, the present application provides a device for sending a message, the device comprising: a processor, a memory, and a transceiver. The processor, the memory, and the transceiver may be connected via a bus system. The memory is used to store one or more programs, and the processor is used to execute one or more programs in the memory, so that the migration device completes the method in the first aspect or any possible implementation of the first aspect.

[0024] In an eighth aspect, the present application provides a device for sending a message, the device comprising: a processor, a memory, and a transceiver. The processor, the memory, and the transceiver may be connected via a bus system. The memory is used to store one or more programs, and the processor is used to execute one or more programs in the memory, so that the migration device completes the method in the second aspect or any possible implementation of the second aspect.

[0025] In a ninth aspect, the present application provides a device for sending a message, the device comprising: a processor, a memory, and a transceiver. The processor, the memory, and the transceiver may be connected via a bus system. The memory is used to store one or more programs, and the processor is used to execute one or more programs in the memory, so that the migration device completes the method in the third aspect or any possible implementation of the third aspect.

[0026] In the tenth aspect, the present application provides a computer-readable storage medium, which stores program code. When the computer-readable storage medium is run on a computer, it enables the computer to execute the method in the above-mentioned first aspect, second aspect, third aspect, any possible implementation of the first aspect, any possible implementation of the second aspect, or any possible implementation of the third aspect.

[0027] In the eleventh aspect, the present application provides a computer program product comprising program code, which, when running on a computer, enables the computer to execute the method in the above-mentioned first aspect, second aspect, third aspect, any possible implementation of the first aspect, any possible implementation of the second aspect, or any possible implementation of the third aspect.

[0028] In a twelfth aspect, the present application provides a system for sending a message, the system comprising the device described in the fourth aspect and the device described in the fifth aspect; or, the system comprising the device described in the seventh aspect and the device described in the eighth aspect.

[0029] In a possible implementation, the system further includes the device described in the sixth aspect or the device described in the ninth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 This is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0031] Figure 2 This is another network architecture diagram provided by an embodiment of the present application;

[0032] Figure 3 This is a flow chart of a method for sending a message provided by an embodiment of the present application;

[0033] Figure 4 It is a schematic diagram of a transmission service message provided in an embodiment of the present application;

[0034] Figure 5 It is a schematic diagram of the structure of the message header provided in the embodiment of the present application;

[0035] Figure 6 It is a flow chart of another method for sending a message provided in an embodiment of the present application;

[0036] Figure 7 It is a flow chart of another method for sending a message provided in an embodiment of the present application;

[0037] Figure 8 It is a schematic diagram of another transmission service message provided in an embodiment of the present application;

[0038] Fig. 9 It is a flow chart of another method for sending a message provided in an embodiment of the present application;

[0039] Fig.10 It is a schematic diagram of the structure of a device for sending a message provided in an embodiment of the present application;

[0040] Fig.11 It is a schematic diagram of the structure of another device for sending a message provided in an embodiment of the present application;

[0041] Fig.12 It is a schematic diagram of the structure of another device for sending a message provided in an embodiment of the present application;

[0042] Fig.13 It is a schematic diagram of the structure of another device for sending a message provided in an embodiment of the present application;

[0043] Fig.14 It is a schematic diagram of the structure of another device for sending a message provided in an embodiment of the present application;

[0044] Fig.15 It is a schematic diagram of the structure of another device for sending a message provided in an embodiment of the present application;

[0045] Fig.16 It is a schematic diagram of the system structure for sending messages provided in an embodiment of the present application. DETAILED DESCRIPTION

[0046] The implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0047] The service path between the base station and the core network passes through multiple different networks. Optionally, in the embodiment of the present application, the following two network architectures are listed, namely:

[0048] In the first network architecture, the service path between the base station and the core network can pass through two MPLS networks and an IP network located between the two MPLS networks. Figure 1 The service path between the base station and the core network may pass through the first MPLS network, the IP network and the second MPLS network in sequence, and the IP network is located between the first MPLS network and the second MPLS network.

[0049] In the second network architecture, the service path between the base station and the core network can pass through two IP networks and an MPLS network located between the two IP networks. Figure 2 The service path between the base station and the core network may pass through the first IP network, the MPLS network and the second IP network in sequence, and the MPLS network is located between the first IP network and the second IP network.

[0050] In the above-mentioned first network architecture or second network architecture, the service path between the base station and the core network passes through the wireless site gateway (cell site gateway, CSG), the aggregation site gateway (aggregation site gateway, ASG), the aggregation side autonomous system border router (aggregation autonomous system borderrouter, A-ASBR), the core side autonomous system border router (core autonomous system borderrouter, C-ASBR) and the mobile aggregation side site gateway (mobile aggregation site gateway, MASG) and other network elements in sequence.

[0051] For example, see Figure 1 In the first network architecture shown, A-ASBR is located at the edge of the first MPLS network and the edge of the IP network, that is, it is an edge device of the first MPLS network and also an edge device of the IP network, and is used to connect the first MPLS network and the IP network. C-ASBR is located at the edge of the second MPLS network and the edge of the IP network, that is, it is an edge device of the second MPLS network and also an edge device of the IP network, and is used to connect the second MPLS network and the IP network. CSG is located at the edge of the first MPLS network and is another edge device of the first MPLS network. The base station is connected to CSG. ASG belongs to the first MPLS network and is located between CSG and A-ASBR. MASG is located at the edge of the second MPLS network and is another edge device of the second MPLS network. The core network is connected to MASG.

[0052] For example, see Figure 2In the second network architecture shown, A-ASBR is located at the edge of the first IP network and the edge of the MPLS network, that is, it is an edge device of the first IP network and also an edge device of the MPLS network, and is used to connect the first IP network and the MPLS network. C-ASBR is located at the edge of the second IP network and the edge of the MPLS network, that is, it is an edge device of the second IP network and also an edge device of the MPLS network, and is used to connect the second IP network and the MPLS network. CSG is located at the edge of the first IP network and is another edge device of the first IP network. The base station is connected to CSG. ASG belongs to the first IP network and is located between CSG and A-ASBR. MASG is located at the edge of the second IP network and is another edge device of the second IP network. The core network is connected to MASG.

[0053] The A-ASBR includes at least one first communication interface and at least one second communication interface, and the C-ASBR includes at least one first communication interface and at least one second communication interface.

[0054] The so-called A-ASBR connecting the first MPLS network and the IP network means that: the first communication interface of the A-ASBR is connected to the network element in the first MPLS network, and the second communication interface of the A-ASBR is connected to the network element in the IP network.

[0055] The so-called C-ASBR connecting the second MPLS network and the IP network means that: the first communication interface of the C-ASBR is connected to the network element in the second MPLS network, and the second communication interface of the C-ASBR is connected to the network element in the IP network.

[0056] The so-called A-ASBR connecting the first IP network and the MPLS network means that: the first communication interface of the A-ASBR is connected to the network element in the first IP network, and the second communication interface of the A-ASBR is connected to the network element in the MPLS network.

[0057] The so-called C-ASBR connecting the second IP network and the MPLS network means that: the first communication interface of the C-ASBR is connected to the network element in the second IP network, and the second communication interface of the C-ASBR is connected to the network element in the MPLS network.

[0058] The first network architecture or the second network architecture also includes a controller, and the controller is used to maintain a service path between the base station and the core network.

[0059] With respect to the multiple network elements through which the service path between the base station and the core network passes, the multiple network elements may include two types of network elements, namely, first type network elements and second type network elements.

[0060] For the first type of network element, the first type of network element not only has the function of receiving and sending service messages, but also has the function of collecting parameter values ​​of performance parameters, and the function of sending the parameter values ​​of the performance parameters to the controller. The service message is a service message sent by the base station to the core network or a service message sent by the core network to the base station, and the at least one performance parameter is also a performance parameter of the service flow to which the service message belongs. The first type of network element can be a CSG, ASG, A-ASBR, C-ASBR, MASG and other network elements. For the second type of network element, the second type of network element has the function of receiving and sending service messages.

[0061] The controller receives parameter values ​​of performance parameters sent by the first type of network element, and maintains a service path between the base station and the core network according to the received parameter values ​​of the performance parameters.

[0062] For the first type of network element, the detailed process of receiving and sending service messages by the first type of network element will be described later. Figure 3 The illustrated embodiment is described in detail.

[0063] Optionally, the core network includes network elements such as SGW or MME, and the service path between the base station and the core network is the service path between the base station and the SGW, or the service path between the base station and the core network is the service path between the base station and the MME.

[0064] Optionally, the controller is NEC-IP etc.

[0065] See also Figure 3 The present application embodiment provides a method for sending a message, which can be applied Figure 1 The first network architecture shown in the figure, in which the first type of network element is used to receive a service message sent by a base station to a core network, and then send the service message to the core network, including:

[0066] Step 101: The CSG receives a third service message sent by a base station, the third service message including a message header and a payload part, adds IFIT message header information to the message header of the third service message, and obtains a first service message.

[0067] In this step, see Figure 4 , CSG is connected to the base station. When the base station needs to send the third service message to the core network, the base station first sends the third service message to the CSG. The third service message includes a message header and a payload part. The message header of the third service message includes an Ethernet (ETH) message header and an IP message header. The IP message header is located between the ETH message header and the payload part.

[0068] CSG receives the third service message, adds an MPLS message header to the message header of the third service message, and obtains the first service message. The MPLS message header can be located between the ETH message header and the IP message header. The MPLS message header includes IFIT message header information. The IFIT message header information is used to indicate at least one performance parameter of the target service flow to be collected. The target service flow is the service flow to which the first service message belongs.

[0069] Optionally, the MPLS message header further includes indication information, where the indication information is used to indicate whether the message header of the first service message includes IFIT message header information.

[0070] Optionally, the IFIT message header information includes identification information of the target service flow to be collected and at least one parameter identifier. Each parameter identifier is used to indicate a performance parameter of the target service flow. For example, the performance parameter of the target service flow may include at least one of a packet loss rate and a delay, and a packet loss rate identifier may be used to indicate the packet loss rate of the target service flow, and a delay identifier may be used to indicate the delay of the target service flow. In other words, the indication information includes identification information of the target service flow to be collected, as well as a packet loss rate identifier and / or a delay identifier of the target service flow.

[0071] Optionally, the indication information includes at least one preset information. In order to prevent the indication information from being identical to part of the content in the payload part, the indication information may include multiple preset information. For example, the indication information may include two preset information or three preset information.

[0072] The preset information may be an IFIT Mark, that is, the indication information may include one IFIT Mark or multiple IFIT Marks.

[0073] Optionally, the MPLS message header includes an IFIT message header, and the IFIT message header includes the IFIT message header information.

[0074] Optional, see Figure 5 The IFIT message header includes a flow information header (FIH) header and an information extensive header (FIEH) header. The FIH header includes a flow identification (Flow id) field, a packet loss rate identification (L) field, a delay identification (D) field, two reserved (R) fields and a header type identification (HTI) field.

[0075] The Flow id field may include identification information of the target service flow, the L field may include a packet loss rate identifier, and the D field may include a delay identifier. The length of the Flow id field may be 20 bits, the length of the L field may be 1 bit, the length of the D field may be one bit, the length of each R field may also be one bit, and the length of the HTI field may be 8 bits.

[0076] Optionally, when the IFIT message header information includes a packet loss rate identifier, the value of the L field can be set to a first bit value to indicate that the L field includes a packet loss rate identifier. When the IFIT message header information includes a delay identifier, the value of the D field can be set to a first bit value to indicate that the D field includes a delay identifier. The first bit value can be 0 or 1.

[0077] Optionally, the HTI field includes the type of the FIH header. When the value of the HTI field is 1, it indicates that the FIH header type is a basic end-to-end flow information message header (E2E FIH) header. When the value of the HTI field is 2, it indicates that the FIH header type is a basic hop-by-hop FIH header. When the value of the HTI field is 3, it indicates that the FIH header type is an extended E2E FIH header. When the value of the HTI field is 4, it indicates that the FIH header type is an extended hop-by-hop FIH header.

[0078] When the FIH header type is an extended E2E FIH header or an extended hop-by-hop FIH header, the FIEH header is valid. The FIEH header includes a flow identification extension field (Flow ID Ext), a Flow id field, a reverse flow learning use flag (V Flag) field, a detection period (period, P) field, a target IP flag (DIP Mask) field, a source IP flag (SIP Mask) field, and a reserved (Reserved) field.

[0079] Optionally, the MPLS header may further include an MPLS label. In the MPLS header, the MPLS label is located in a field close to the ETH header, the IFIT header is close to the IP header, and the indication information is located between the MPLS label and the IFIT header.

[0080] Optionally, before executing this step, the controller sends an IFIT instance to the first type of network element, where the IFIT instance includes a parameter identifier of at least one performance parameter of the target service flow to be collected, five-tuple information of the target service flow, identification information of the target service flow and the indication information.

[0081] The five-tuple information may include the source address, destination address, source port number, destination port number and protocol type of the target service flow. The source address may be an IP address or a media access control layer (MAC) address, and the destination address may be an IP address or a MAC address.

[0082] Thus, in this step, after receiving the third service message, CSG detects whether the third service message belongs to the target service flow to be detected according to the five-tuple information included in the IFIT instance. When detecting that the third service message belongs to the target service flow, CSG generates IFIT message header information according to the parameter identifier, the identifier information and the indication information of the IFIT instance, adds an MPLS message header to the message header of the third service message, and obtains a first service message, wherein the MPLS message header includes the generated IFIT message header information.

[0083] Optionally, the service path between the base station and the core network is also used to transmit the follow-up flow, and the controller can obtain the parameter value of at least one performance parameter of the follow-up flow. When the parameter value of a certain performance parameter reaches the parameter threshold, the controller determines the service flow transmitted between the base station and the core network as the target service flow to be collected, and generates an IFIT instance corresponding to the target service flow to be collected.

[0084] The parameter value of the performance parameter of the follow-up flow can be delay or packet loss rate. When the packet loss rate of the follow-up flow reaches the packet loss rate threshold or the delay of the follow-up flow reaches the delay threshold, the controller determines the service flow transmitted between the base station and the core network as the target service flow to be collected.

[0085] Step 102: The CSG collects a parameter value of at least one performance parameter of a target service flow according to the IFIT message header information included in the first service message, where the target service flow is the service flow to which the first service message belongs.

[0086] Optionally, the IFIT message header information includes identification information of the target service flow to be collected and at least one parameter identifier. For any parameter identifier among the at least one parameter identifier, the CSG collects the parameter value of the performance parameter indicated by any parameter identifier based on the identification information of the target service flow to be collected, thereby obtaining the parameter value of at least one performance parameter of the target service flow to be collected.

[0087] Optionally, the at least one parameter identifier may include a packet loss rate identifier and / or a delay identifier, etc. The CSG collects the packet loss rate indicated by the packet loss rate identifier and / or the delay indicated by the delay identifier based on the identification information of the target service flow to be collected, thereby obtaining the packet loss rate and / or delay of the target service flow to be collected.

[0088] Step 103: The CSG sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a first service message to the ASG.

[0089] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0090] There may be at least one network element between CSG and ASG. When the at least one network element includes a first type of network element, the first type of network element, like the ASG, after receiving the first service message, collects the parameter value of at least one performance parameter of the target service flow, sends the collection information including the parameter value to the controller, and sends the first service message to the next hop network element in the first MPLS network. The detailed implementation will be introduced in the following steps 104 to 105. When the at least one network element includes a second type of network element, the second type of network element sends the first service message to the next hop network element in the first MPLS network after receiving the first service message.

[0091] Step 104: The ASG receives the first service message, and collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information included in the first service message.

[0092] In this step, the ASG receives the first service message, parses the message header of the first service message, and when the MPLS message header in the message header is parsed, the content included in the MPLS message header is parsed. When the indication information included in the MPLS message header is parsed, it is determined according to the indication information that the first service message includes the IFIT message header information, and then the MPLS message header is further parsed, and the IFIT message header information is parsed from the MPLS message header, and the parameter value of at least one performance parameter of the target service flow is collected according to the IFIT message header information.

[0093] Optionally, the IFIT message header information includes identification information of the target service flow to be collected and at least one parameter identifier. For any parameter identifier among the at least one parameter identifier, the ASG collects the parameter value of the performance parameter indicated by any parameter identifier according to the identification information of the target service flow to be collected, thereby obtaining the parameter value of at least one performance parameter of the target service flow to be collected.

[0094] Optionally, the at least one parameter identifier may include a packet loss rate identifier and / or a delay identifier, etc. The ASG collects the packet loss rate indicated by the packet loss rate identifier and / or the delay indicated by the delay identifier based on the identification information of the target service flow to be collected, thereby obtaining the packet loss rate and / or delay of the target service flow to be collected.

[0095] Step 105: The ASG sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a first service message to the A-ASBR.

[0096] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0097] Optionally, when parsing the MPLS packet header of the first service packet, the ASG may parse the MPLS label in the MPLS packet header, and the ASG may send the first service packet according to the MPLS label.

[0098] There may be at least one network element between the ASG and the A-ASBR. When the at least one network element includes a first-type network element, the first-type network element performs the same operation as the ASG. When the at least one network element includes a second-type network element, the second-type network element sends the first service message to the next-hop network element in the first MPLS network after receiving the first service message.

[0099] Step 106: The A-ASBR receives the first service message, and moves the IFIT message header information included in the first service message from the message header included in the first service message to the payload part of the first service message, thereby obtaining a second service message.

[0100] In this step, the A-ASBR receives a first service message, reads indication information from the first service message, and when determining based on the indication information that the message header of the first service message includes IFIT message header information, moves the IFIT message header information included in the first service message from the message header included in the first service message to the payload part of the first service message to obtain a second service message.

[0101] Optionally, the IFIT message header information may be moved from the message header of the first service message to the payload part of the first service message in the following manner:

[0102] When the A-ASBR determines, based on the indication information, that the message header of the first service message includes IFIT message header information, it obtains the IFIT message header information from the message header of the first service message, adds the IFIT message header information to the starting position of the payload part of the first service message, and deletes the IFIT message header information from the message header of the first service message to obtain a second service message.

[0103] Optionally, the A-ASBR may also add the indication information at the beginning position of the payload part of the first service message, and delete the indication information from the message header of the first service message.

[0104] In implementation, after receiving the first service message, the A-ASBR parses the message header of the first service message, and when parsing the MPLS message header in the message header, parses the content included in the MPLS message header. After parsing the indication information included in the MPLS message header, it is determined that the first service message includes the IFIT message header information according to the indication information, and then continues to parse the MPLS message header, and parses the IFIT message header information from the MPLS message header, adds the indication information and the IFIT message header information to the starting position of the payload part of the first service message, and deletes the MPLS message header from the message header of the first service message, so refer to Figure 4 The obtained message header of the second service message includes an ETH message header and an IP message header.

[0105] Step 107: The A-ASBR collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information.

[0106] In this step, the A-ASBR includes a first communication interface and a second communication interface. The A-ASBR receives a first service message through the first communication interface. The A-ASBR then moves the IFIT message header information included in the first service message from the message header included in the first service message to the payload part of the first service message to obtain a second service message, and transmits the second service message to the second communication interface. The second communication interface of the A-ASBR can parse the payload part of the second service message, parse the IFIT message header information from the payload part, and collect the parameter value of at least one performance parameter of the target service flow according to the IFIT message header information. The detailed implementation process of collecting the parameter value of the at least one performance parameter can refer to the detailed implementation process of the CSG collecting the at least one performance parameter in step 102, which will not be described in detail here.

[0107] The second communication interface includes a processing chip, so the second communication interface can perform operations such as parsing the payload part of the second service message.

[0108] Step 108: The A-ASBR sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a second service message to the IP network.

[0109] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0110] The A-ASBR is located at the edge of the first MPLS network and at the edge of the IP network. For the transmission direction of the service message sent by the base station to the core network, the A-ASBR is both the egress device of the first MPLS network and the ingress device of the IP network.

[0111] After the A-ASBR sends the second service message to the IP network, the second service message will be transmitted to the C-CSBR in the IP network. For the transmission direction of the base station sending service messages to the core network, the C-ASBR is both the egress device of the IP network and the ingress device of the second MPLS network.

[0112] There may be at least one network element between the A-ASBR and the C-ASBR.

[0113] When the at least one network element includes a first type of network element, the first type of network element receives a second service message, collects the parameter value of at least one performance parameter of the target service flow according to the IFIT message header information; sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter; and sends the second service message to the next-hop network element.

[0114] During implementation, the first type of network element receives the second service message, parses the payload message of the second service message, and when the indication information is parsed from the payload part, if it is determined according to the indication information that the second service message includes the IFIT message header information, the IFIT message header information is continued to be parsed from the payload part, and the parameter value of at least one performance parameter of the target service flow is collected according to the IFIT message header information. The detailed implementation process of collecting the parameter value of the at least one performance parameter can be referred to the detailed implementation process of the CSG collecting the at least one performance parameter in step 102, which will not be described in detail here.

[0115] When the at least one network element includes a second type of network element, the second type of network element sends the second service message to a next-hop network element in the IP network after receiving the second service message.

[0116] Step 109: The C-ASBR receives the second service message, and moves the IFIT message header information included in the payload part of the second service message from the payload part to the message header of the second service message, thereby obtaining the first service message.

[0117] The payload part also includes indication information, which is used to indicate that the second service message includes the IFIT message header information; when the C-ASBR determines that the second service message includes the IFIT message header information based on the indication information, it moves the IFIT message header information from the payload part to the message header of the second service message to obtain the first service message.

[0118] Optionally, the C-ASBR further moves the indication information from the payload part to the message header of the second service message.

[0119] Optionally, in this step, the C-ASBR receives the second service message, parses the payload message of the second service message, and when the indication information is parsed from the payload part, if it is determined according to the indication information that the second service message includes the IFIT message header information, continues to parse the IFIT message header information from the payload part. Figure 4 , adding an MPLS header to the header of the second service message, the MPLS header including the MPLS label, the indication information and the IFIT header information, and deleting the indication information and the IFIT header information from the payload part of the second service message, thereby obtaining the first service message.

[0120] Step 110: The C-ASBR collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information.

[0121] In this step, the C-ASBR parses the message header of the first service message, parses the IFIT message header information from the message header, and collects the parameter value of at least one performance parameter of the target service flow according to the IFIT message header information. The detailed implementation process of collecting the parameter value of the at least one performance parameter can refer to the detailed implementation process of the CSG collecting the at least one performance parameter in step 102, which will not be described in detail here.

[0122] Step 111: The C-ASBR sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a first service message to the MASG of the second MPLS network.

[0123] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0124] There may be at least one network element between the C-ASBR and the MASG. When the at least one network element includes a first type of network element, the first type of network element, like the ASG, after receiving the first service message, collects the parameter value of at least one performance parameter of the target service flow, sends the collection information including the parameter value to the controller, and sends the first service message to the next hop network element in the second MPLS network. When the at least one network element includes a second type of network element, the second type of network element, after receiving the first service message, sends the first service message to the next hop network element in the second MPLS network.

[0125] Step 112: The MASG receives the first service message, and collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information included in the first service message.

[0126] In this step, the MASG receives the first service message, parses the message header of the first service message, and when the MPLS message header in the message header is parsed, the content included in the MPLS message header is parsed. When the indication information included in the MPLS message header is parsed, it is determined according to the indication information that the first service message includes the IFIT message header information, and then the MPLS message header is further parsed, and the IFIT message header information is parsed from the MPLS message header, and the parameter value of at least one performance parameter of the target service flow is collected according to the IFIT message header information.

[0127] The detailed implementation process of collecting the parameter value of the at least one performance parameter can be referred to the detailed implementation process of the CSG collecting the at least one performance parameter in step 102, which will not be described in detail here.

[0128] Step 113: The MASG sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a first service message to the core network.

[0129] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0130] Optionally, the MASG may delete the MPLS packet header from the packet header of the first service packet, and then send the deleted first service packet to the core network.

[0131] The controller includes a topological structure of a service path between a base station and a core network, and the topological structure includes icons corresponding to each network element through which the service path passes.

[0132] The controller can receive the collection information sent by the first type of network elements through which the service path passes, that is, receive the collection information sent by CSG, the collection information sent by ASG, the collection information sent by A-ASBR, the collection information sent by C-ASBR, and the collection information sent by MASG. The service path between the base station and the core network is maintained based on the collection information sent by each first type of network element. For example, the controller performs fault location based on the collection information sent by each first type of network element. When a fault is located in a first type of network element, the collection information sent by the first type of network element can be displayed in the icon corresponding to the first type of network element.

[0133] Optionally, the collection information sent by the first type of network element includes delay and / or packet loss rate. When the delay exceeds a delay threshold or the packet loss rate exceeds a packet loss rate threshold, it is determined that the first type of network element is faulty.

[0134] In the embodiment of the present application, the A-ASBR receives the first service message, moves the IFIT message header information in the message header of the first service message from the message header to the payload part of the first service message, obtains the second service message, and sends the second service message to the IP network. In this way, among the network elements through which the service path between the base station and the core network passes, each network element (such as C-ASBR and MASG network elements) located after the A-ASBR collects the parameter value of at least one performance parameter of the service flow according to the IFIT message header information in the service message when receiving the service message sent by the A-ASBR, and sends the collection information including the parameter value of the at least one performance parameter to the controller, so that the controller can maintain the service path after the A-ASBR according to the collection information sent by each network element after the A-ASBR, and extend the length of the maintenance service path. In addition, since each first-class network element through which the service path between the base station and the core network passes can parse the IFIT message header information in the received service message, each first-class network element can send the collection information to the controller according to the IFIT message header information, so that the controller can perform end-to-end maintenance on the service path.

[0135] See also Figure 6 The present application embodiment provides a method for sending a message, which can be applied Figure 1 The first network architecture shown in the figure, in which the first type of network element is used to receive a service message sent by the core network to the base station, and then send the service message to the base station, including:

[0136] Step 201: MASG receives a third service message sent by the core network, the third service message includes a message header and a payload part, adds IFIT message header information to the message header of the third service message, and obtains the first service message.

[0137] Optionally, the detailed implementation process of MASG adding IFIT message header information can be found in Figure 3 The detailed implementation process of the CSG adding the IFIT message header information in step 101 of the illustrated embodiment will not be described in detail here.

[0138] Step 202: The MASG collects a parameter value of at least one performance parameter of a target service flow according to the IFIT message header information included in the first service message, where the target service flow is the service flow to which the first service message belongs.

[0139] Optional, the detailed implementation process of MASG acquisition parameter values ​​can be found in Figure 3 The detailed implementation process of CSG collecting parameter values ​​in step 102 of the illustrated embodiment will not be described in detail here.

[0140] Step 203: The MASG sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a first service message to the C-ASBR.

[0141] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0142] There may be at least one network element between the MASG and the C-ASBR. When the at least one network element includes a first type of network element, the first type of network element, like the MASG, after receiving the first service message, collects the parameter value of at least one performance parameter of the target service flow, sends the collection information including the parameter value to the controller, and sends the first service message to the next hop network element in the second MPLS network. When the at least one network element includes a second type of network element, the second type of network element, after receiving the first service message, sends the first service message to the next hop network element in the second MPLS network.

[0143] Step 204: The C-ASBR receives the first service message, and moves the IFIT message header information included in the first service message from the message header included in the first service message to the payload part of the first service message, thereby obtaining a second service message.

[0144] Optional, the detailed implementation process of C-ASBR moving IFIT message header information can be found in Figure 3 The detailed implementation process of the A-ASBR moving the IFIT message header information in step 106 of the illustrated embodiment will not be described in detail here.

[0145] Step 205: The C-ASBR collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information.

[0146] Optional, the detailed implementation process of C-ASBR collection parameter values ​​can be found in Figure 3 The detailed implementation process of the A-ASBR collecting parameter values ​​in step 107 of the illustrated embodiment will not be described in detail here.

[0147] Step 206: The C-ASBR sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a second service message to the IP network.

[0148] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0149] The C-ASBR is located at the edge of the second MPLS network and at the edge of the IP network. For the transmission direction of service messages sent from the core network to the base station, the C-ASBR is both the egress device of the second MPLS network and the ingress device of the IP network.

[0150] After C-ASBR sends the second service message to the IP network, the second service message will be transmitted to A-CSBR in the IP network. For the transmission direction of the service message sent from the core network to the base station, A-ASBR is both the egress device of the IP network and the ingress device of the first MPLS network.

[0151] Step 207: The A-ASBR receives the second service message, and moves the IFIT message header information included in the payload part of the second service message from the payload part to the message header of the second service message, thereby obtaining the first service message.

[0152] Optional, the detailed implementation process of A-ASBR moving IFIT message header information can be found in Figure 3 The detailed implementation process of the C-ASBR moving the IFIT message header information in step 109 of the illustrated embodiment will not be described in detail here.

[0153] Step 208: The A-ASBR collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information.

[0154] In this step, the A-ASBR parses the message header of the first service message, parses IFIT message header information from the message header, and collects the parameter value of at least one performance parameter of the target service flow according to the IFIT message header information.

[0155] Step 209: The A-ASBR sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a first service message to the ASG of the first MPLS network.

[0156] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0157] Step 210: The ASG receives the first service message, and collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information included in the first service message.

[0158] Optional, the detailed implementation process of ASG collection parameter values ​​can be found in Figure 3 The detailed implementation process of the ASG collecting parameter values ​​in step 104 of the illustrated embodiment will not be described in detail here.

[0159] Step 211: The ASG sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a first service message to the CSG.

[0160] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0161] Step 212: The CSG receives the first service message, and collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information included in the first service message.

[0162] Optional, the detailed implementation process of CSG collection parameter values ​​can be found in Figure 3 The detailed implementation process of the MASG acquisition parameter value in step 112 of the illustrated embodiment will not be described in detail here.

[0163] Step 213: The CSG sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a first service message to the base station.

[0164] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0165] Optionally, the CSG may delete the MPLS header from the header of the first service message, and then send the deleted first service message to the base station.

[0166] The controller can receive the collection information sent by the first type of network elements through which the service path passes, that is, receive the collection information sent by MASG, the collection information sent by C-ASBR, the collection information sent by A-ASBR, the collection information sent by ASG, and the collection information sent by CSG. The service path between the base station and the core network is maintained according to the collection information sent by each first type of network element.

[0167] In the embodiment of the present application, the C-ASBR receives the first service message, moves the IFIT message header information in the message header of the first service message from the message header to the payload part of the first service message, obtains the second service message, and sends the second service message to the IP network. In this way, among the network elements through which the service path between the base station and the core network passes, each network element after the C-ASBR (such as the A-ASBR, ASG and CSG network elements) collects the parameter value of at least one performance parameter of the service flow according to the IFIT message header information in the service message when receiving the service message sent by the C-ASBR, and sends the collection information including the parameter value of the at least one performance parameter to the controller, so that the controller can maintain the service path after the C-ASBR according to the collection information sent by each network element after the C-ASBR, thereby extending the length of the maintenance service path. In addition, since each first-class network element through which the service path between the base station and the core network passes can parse the IFIT message header information in the received service message, each first-class network element can send collection information to the controller based on the IFIT message header information, so that the controller can perform end-to-end maintenance on the service path.

[0168] See also Figure 7The present application embodiment provides a method for sending a message, which can be applied Figure 2 The second network architecture shown in the figure, in which the first type of network element is used to receive a service message sent by the base station to the core network, and then send the service message to the core network, including:

[0169] Step 301: The CSG receives a third service message sent by a base station, the third service message including a message header and a payload part, adds IFIT message header information to the payload part of the third service message, and obtains a second service message.

[0170] In this step, see Figure 8 , CSG is connected to the base station. When the base station needs to send the third service message to the core network, the base station first sends the third service message to the CSG. The third service message includes a message header and a payload part. The message header of the third service message includes an ETH message header and an IP message header. The IP message header is located between the ETH message header and the payload part.

[0171] The CSG receives the third service message, and adds IFIT message header information at the start position of the payload part of the third service message, wherein the IFIT message header information is used to indicate at least one performance parameter of the target service flow to be collected, and the target service flow is the service flow to which the first service message belongs.

[0172] Optionally, indication information is also added to the payload part of the third service message, where the indication information is used to indicate whether the payload part of the second service message includes IFIT message header information.

[0173] Optionally, the IFIT message header information includes identification information of the target service flow to be collected and at least one parameter identifier. Each parameter identifier is used to indicate a performance parameter of the target service flow. For example, the performance parameter of the target service flow may include at least one of a packet loss rate and a delay, and a packet loss rate identifier may be used to indicate the packet loss rate of the target service flow, and a delay identifier may be used to indicate the delay of the target service flow. In other words, the indication information includes identification information of the target service flow to be collected, as well as a packet loss rate identifier and / or a delay identifier of the target service flow.

[0174] Optionally, before executing this step, the controller sends an IFIT instance to the first type of network element, where the IFIT instance includes a parameter identifier of at least one performance parameter of the target service flow to be collected, five-tuple information of the target service flow, identification information of the target service flow and the indication information.

[0175] In this way, in this step, after receiving the third service message, CSG detects whether the third service message belongs to the target service flow to be detected based on the five-tuple information included in the IFIT instance. When it is detected that the third service message belongs to the target service flow, the IFIT message header information is generated based on the IFIT instance including the parameter identifier, the identifier information and the indication information, and the generated IFIT message header information is added to the payload part of the third service message.

[0176] Step 302: The CSG collects a parameter value of at least one performance parameter of a target service flow according to the IFIT message header information included in the second service message, where the target service flow is the service flow to which the second service message belongs.

[0177] Optionally, the IFIT message header information includes identification information of the target service flow to be collected and at least one parameter identifier. For any parameter identifier among the at least one parameter identifier, the CSG collects the parameter value of the performance parameter indicated by any parameter identifier based on the identification information of the target service flow to be collected, thereby obtaining the parameter value of at least one performance parameter of the target service flow to be collected.

[0178] Optionally, the at least one parameter identifier may include a packet loss rate identifier and / or a delay identifier, etc. The CSG collects the packet loss rate indicated by the packet loss rate identifier and / or the delay indicated by the delay identifier based on the identification information of the target service flow to be collected, thereby obtaining the packet loss rate and / or delay of the target service flow to be collected.

[0179] Step 303: The CSG sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a second service message to the ASG.

[0180] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0181] There may be at least one network element between CSG and ASG. When the at least one network element includes a first type of network element, the first type of network element, like the ASG, after receiving the second service message, collects the parameter value of at least one performance parameter of the target service flow, sends the collection information including the parameter value to the controller, and sends the first service message to the next hop network element in the first IP network. When the at least one network element includes a second type of network element, the second type of network element, after receiving the first service message, sends the first service message to the next hop network element in the first IP network.

[0182] Step 304: The ASG receives the second service message, and collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information included in the second service message.

[0183] In this step, the ASG receives the second service message, parses the payload part of the second service message, and after parsing the indication information included in the payload part, determines that the second service message includes the IFIT message header information based on the indication information, and then continues to parse the payload part, and parses out the IFIT message header information from the payload part, and collects the parameter value of at least one performance parameter of the target service flow based on the IFIT message header information.

[0184] Step 305: The ASG sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a second service message to the A-ASBR.

[0185] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0186] There may be at least one network element between the ASG and the A-ASBR. When the at least one network element includes a first-type network element, the first-type network element performs the same operation as the ASG. When the at least one network element includes a second-type network element, the second-type network element sends the second service message to the next-hop network element in the first IP network after receiving the second service message.

[0187] Step 306: The A-ASBR receives the second service message, and moves the IFIT message header information included in the second service message from the payload part included in the second service message to the message header of the second service message, thereby obtaining the first service message.

[0188] In this step, the payload part also includes indication information, which is used to indicate that the second service message includes the IFIT message header information; when the A-ASBR determines that the second service message includes the IFIT message header information based on the indication information, it moves the IFIT message header information from the payload part to the message header of the second service message to obtain the first service message.

[0189] Optionally, the A-ASBR further moves the indication information from the payload part to the message header of the second service message.

[0190] Optionally, in this step, the A-ASBR receives the second service message, parses the payload message of the second service message, and when the indication information is parsed from the payload part, if it is determined according to the indication information that the second service message includes the IFIT message header information, continues to parse the IFIT message header information from the payload part. Figure 8 , adding an MPLS header to the header of the second service message, the MPLS header including the MPLS label, the indication information and the IFIT header information, and deleting the indication information and the IFIT header information from the payload part of the second service message, thereby obtaining the first service message.

[0191] Step 307: The A-ASBR collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information.

[0192] In this step, the A-ASBR includes a first communication interface and a second communication interface. The A-ASBR receives the second service message through the first communication interface. The A-ASBR then moves the IFIT message header information included in the second service message from the payload part of the second service message to the message header of the first service message, obtains the first service message, and transmits the first service message to the second communication interface. The second communication interface of the A-ASBR can parse the message header of the first service message, parse out the IFIT message header information from the message header, and collect the parameter value of at least one performance parameter of the target service flow according to the IFIT message header information.

[0193] Step 308: The A-ASBR sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a first service message to the MPLS network.

[0194] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0195] The A-ASBR is located at the edge of the first IP network and at the edge of the MPLS network. For the transmission direction of the service message sent by the base station to the core network, the A-ASBR is both the egress device of the first IP network and the ingress device of the MPLS network.

[0196] After the A-ASBR sends the first service message to the MPLS network, the first service message will be transmitted to the C-CSBR in the MPLS network. For the transmission direction of the base station sending service messages to the core network, the C-ASBR is both the egress device of the MPLS network and the ingress device of the second IP network.

[0197] Step 309: The C-ASBR receives the first service message, and moves the IFIT message header information included in the message header of the first service message from the message header to the payload part of the first service message, thereby obtaining a second service message.

[0198] The message header also includes indication information, which is used to indicate that the first service message includes the IFIT message header information; when the C-ASBR determines that the first service message includes the IFIT message header information based on the indication information, it moves the IFIT message header information from the message header to the payload part of the first service message to obtain a second service message.

[0199] Optionally, the C-ASBR further moves the indication information from the message header to the payload part of the first service message.

[0200] Optionally, in this step, the C-ASBR receives the first service message, parses the MPLS message header included in the message header of the first service message, and when the indication information is parsed from the MPLS message header, if it is determined according to the indication information that the first service message includes the IFIT message header information, continues to parse the IFIT message header information from the MPLS message header. Figure 8 , adding the indication information and the IFIT message header information at the starting position of the payload part of the first service message, and deleting the indication information and the IFIT message header information from the message header of the first service message, thereby obtaining a second service message.

[0201] Step 310: The C-ASBR collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information.

[0202] In this step, the C-ASBR parses the payload part of the second service message, parses the IFIT message header information from the payload part, and collects the parameter value of at least one performance parameter of the target service flow according to the IFIT message header information.

[0203] Step 311: The C-ASBR sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a second service message to the MASG of the second IP network.

[0204] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0205] Step 312: The MASG receives the second service message, and collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information included in the second service message.

[0206] In this step, MASG receives the second business message, parses the payload part of the second business message, and after parsing the indication information included in the payload part, determines that the first business message includes the IFIT message header information based on the indication information, and then continues to parse the payload part, and parses out the IFIT message header information from the payload part, and collects the parameter value of at least one performance parameter of the target business flow based on the IFIT message header information.

[0207] Step 313: The MASG sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a second service message to the core network.

[0208] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0209] The controller can receive the collection information sent by the first type of network elements through which the service path between the base station and the core network passes, that is, receive the collection information sent by the CSG, the collection information sent by the ASG, the collection information sent by the A-ASBR, the collection information sent by the C-ASBR, and the collection information sent by the MASG. The service path between the base station and the core network is maintained according to the collection information sent by each first type of network element. For example, the controller performs fault location according to the collection information sent by each first type of network element. When a fault is located in a first type of network element, the collection information sent by the first type of network element can be displayed in the icon corresponding to the first type of network element.

[0210] In the embodiment of the present application, the A-ASBR receives the second service message, moves the IFIT message header information in the payload part of the second service message from the message header to the message header of the second service message, obtains the first service message, and sends the first service message to the MPLS network. In this way, among the network elements through which the service path between the base station and the core network passes, each network element (such as C-ASBR and MASG network elements) located after the A-ASBR collects the parameter value of at least one performance parameter of the service flow according to the IFIT message header information in the service message when receiving the service message sent by the A-ASBR, and sends the collection information including the parameter value of the at least one performance parameter to the controller, so that the controller can maintain the service path after the A-ASBR according to the collection information sent by each network element after the A-ASBR, and extend the length of the maintenance service path. In addition, since each first-class network element through which the service path between the base station and the core network passes can parse the IFIT message header information in the received service message, each first-class network element can send the collection information to the controller according to the IFIT message header information, so that the controller can perform end-to-end maintenance on the service path.

[0211] See also Fig. 9 The present application embodiment provides a method for sending a message, which can be applied Figure 2 The second network architecture shown in the figure, in which the first type of network element is used to receive a service message sent by the core network to the base station, and then send the service message to the base station, including:

[0212] Step 401: MASG receives a third service message sent by the core network, the third service message includes a message header and a payload part, adds IFIT message header information to the payload part of the third service message, and obtains a second service message.

[0213] Optionally, the detailed implementation process of MASG adding IFIT message header information can be found in Figure 7 The detailed implementation process of the CSG adding the IFIT message header information in step 301 of the illustrated embodiment will not be described in detail here.

[0214] Step 402: The MASG collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information included in the second service message.

[0215] Optional, the detailed implementation process of MASG acquisition parameter values ​​can be found in Figure 7 The detailed implementation process of CSG collecting parameter values ​​in step 302 of the illustrated embodiment will not be described in detail here.

[0216] Step 403: The MASG sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a second service message to the C-ASBR.

[0217] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0218] Step 404: The C-ASBR receives the second service message, and moves the IFIT message header information included in the second service message from the payload part included in the second service message to the message header of the second service message, thereby obtaining the first service message.

[0219] Optional, the detailed implementation process of C-ASBR moving IFIT message header information can be found in Figure 7 The detailed implementation process of the A-ASBR moving the IFIT message header information in step 306 of the illustrated embodiment will not be described in detail here.

[0220] Step 405: The C-ASBR collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information.

[0221] Optional, the detailed implementation process of C-ASBR collection parameter values ​​can be found in Figure 7 The detailed implementation process of the A-ASBR collecting parameter values ​​in step 307 of the illustrated embodiment will not be described in detail here.

[0222] Step 406: The C-ASBR sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a first service message to the MPLS network.

[0223] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0224] The C-ASBR is located at the edge of the second IP network and at the edge of the MPLS network. For the transmission direction of service messages sent from the core network to the base station, the C-ASBR is both the egress device of the second IP network and the ingress device of the MPLS network.

[0225] After C-ASBR sends the first service message to the MPLS network, the first service message will be transmitted to A-CSBR in the MPLS network. For the transmission direction of the service message sent from the core network to the base station, A-ASBR is both the egress device of the MPLS network and the ingress device of the first IP network.

[0226] Step 407: The A-ASBR receives the first service message, and moves the IFIT message header information included in the message header of the first service message from the message header to the payload part of the first service message, thereby obtaining a second service message.

[0227] Optional, the detailed implementation process of A-ASBR moving IFIT message header information can be found in Figure 7 The detailed implementation process of the C-ASBR moving the IFIT message header information in step 309 of the illustrated embodiment will not be described in detail here.

[0228] Step 408: The A-ASBR collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information.

[0229] In this step, the A-ASBR parses the payload part of the first service message, parses the IFIT message header information from the payload part, and collects the parameter value of at least one performance parameter of the target service flow according to the IFIT message header information.

[0230] Step 409: The A-ASBR sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a second service message to the ASG of the first IP network.

[0231] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0232] Step 410: The ASG receives the second service message, and collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information included in the second service message.

[0233] Optional, the detailed implementation process of ASG collection parameter values ​​can be found in Figure 7 The detailed implementation process of the ASG collecting parameter values ​​in step 304 of the illustrated embodiment will not be described in detail here.

[0234] Step 411: The ASG sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a second service message to the CSG.

[0235] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0236] Step 412: The CSG receives the second service message, and collects a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information included in the second service message.

[0237] Optional, the detailed implementation process of CSG collection parameter values ​​can be found in Figure 7 The detailed implementation process of the MASG acquisition parameter value in step 312 of the illustrated embodiment will not be described in detail here.

[0238] Step 413: The CSG sends collection information to the controller, where the collection information includes the parameter value of the at least one performance parameter, and sends a second service message to the base station.

[0239] Optionally, the collected information may also include identification information of the target service flow to be collected.

[0240] The controller can receive the collection information sent by the first type of network elements through which the service path passes, that is, receive the collection information sent by MASG, the collection information sent by C-ASBR, the collection information sent by A-ASBR, the collection information sent by ASG, and the collection information sent by CSG. The service path between the base station and the core network is maintained according to the collection information sent by each first type of network element.

[0241] In the embodiment of the present application, the C-ASBR receives the second service message, moves the IFIT message header information in the payload part of the second service message to the message header of the second service message, obtains the first service message, and sends the first service message to the MPLS network. In this way, among the network elements through which the service path between the base station and the core network passes, each network element (such as A-ASBR, ASG and CSG network elements) located after the C-ASBR collects the parameter value of at least one performance parameter of the service flow according to the IFIT message header information in the service message when receiving the service message sent by the C-ASBR, and sends the collection information including the parameter value of the at least one performance parameter to the controller, so that the controller can maintain the service path after the C-ASBR according to the collection information sent by each network element after the C-ASBR, thereby extending the length of the maintenance service path. In addition, since each first-class network element through which the service path between the base station and the core network passes can parse the IFIT message header information in the received service message, each first-class network element can send the collection information to the controller according to the IFIT message header information, so that the controller can perform end-to-end maintenance on the service path.

[0242] See also Fig.10 The embodiment of the present application provides a device 500 for sending a message, and the device 500 can be deployed in a first network element, and the first network element can be the above-mentioned Figure 3 or Figure 7The A-ASBR in the embodiment; or, the first network element may be the above Figure 6 or Fig. 9 The C-CSBR in the embodiment includes:

[0243] The receiving unit 501 is used to receive a first service message from a first network, wherein the message header of the first service message includes IFIT message header information, and the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, and the target service flow is a service flow to which the first service message belongs, and the device 500 is used to connect the first network and the second network, and the first network and the second network are two different types of networks;

[0244] The processing unit 502 is used to move the IFIT message header information from the message header to the payload part of the first service message to obtain a second service message;

[0245] The sending unit 503 is configured to send a second service message to the second network.

[0246] Optionally, the detailed implementation process of the processing unit 502 moving the IFIT message header information can be found in Figure 3 Step 106 of the illustrated embodiment or see Fig. 9 The detailed implementation process of the A-ASBR moving the IFIT message header information in step 407 of the embodiment shown in the figure. Alternatively, the detailed implementation process of the processing unit 502 moving the IFIT message header information can be found in Figure 6 Step 204 of the illustrated embodiment or see Figure 7 The detailed implementation process of the C-ASBR moving the IFIT message header information in step 309 of the illustrated embodiment.

[0247] Optionally, the message header of the first service message further includes indication information, where the indication information is used to indicate that the first service message includes IFIT message header information;

[0248] The processing unit 502 is configured to, when it is determined according to the indication information that the first service message includes the IFIT message header information, move the IFIT message header information from the message header to the payload part of the first service message to obtain a second service message.

[0249] Optionally, the detailed implementation process of the processing unit 502 moving the indication information can be found in Figure 3 Step 106 in the illustrated embodiment or Fig. 9 In the embodiment shown in step 407, the A-ASBR moves the instruction information for detailed implementation. Alternatively, the processing unit 502 moves the instruction information for detailed implementation, which can be found in Figure 6 Step 204 in the embodiment described or Figure 7Step 309 in the illustrated embodiment, the detailed implementation process of C-ASBR moving the indication information

[0250] Optionally, the processing unit 502 is further configured to move the indication information from the message header to the payload portion of the first service message.

[0251] Optionally, the processing unit 502 is configured to:

[0252] The IFIT message header information is obtained from the message header, the IFIT message header information is added to the starting position of the payload part of the first service message, and the IFIT message header information is deleted from the message header to obtain a second service message.

[0253] Optionally, the processing unit 502 is further configured to collect a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information;

[0254] The sending unit 503 is further configured to send a parameter value of at least one performance parameter to the controller.

[0255] Optionally, the detailed implementation process of the processing unit 502 collecting and sending parameter values ​​can be found in Figure 3 Steps 107-108 in the illustrated embodiment or Fig. 9 In the embodiment shown, steps 408-409, the detailed implementation process of A-ASBR collecting and sending parameter values; or the detailed implementation process of processing unit 502 collecting and sending parameter values, can be found in Figure 6 Steps 205-206 in the illustrated embodiment or Figure 7 The detailed implementation process of steps 310-311 in the illustrated embodiment, in which the C-ASBR moves the indication information, will not be described in detail here.

[0256] Optionally, the first network is a Multi-Protocol Label Switching (MPLS) network, and the second network is an Internet Protocol (IP) network.

[0257] In an embodiment of the present application, a receiving unit receives a first service message from a first network, and a message header of the first service message includes IFIT message header information, and the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, and the target service flow is a service flow to which the first service message belongs. The processing unit moves the IFIT message header information from the message header to the payload part of the first service message to obtain a second service message. The sending unit sends the second service message to the second network. Since the processing unit moves the IFIT message header information from the message header to the payload part of the first service message, and then the sending unit sends the second service message to the second network, for other network elements located after the device on the service path for transmitting the second service message, when other network elements receive the service message sent by the sending unit, the parameter value of the performance parameter of the target service flow is collected according to the IFIT message header information in the service message, and sent to the controller, and the controller maintains the service path after the device according to the parameter value, thereby extending the length of the maintenance service path.

[0258] See also Fig.11 The embodiment of the present application provides a device 600 for sending a message, and the device 600 can be deployed in a second network element, and the second network element can be the above-mentioned Figure 3 or Figure 7 The C-ASBR in the embodiment; or, the second network element may be the above Figure 6 or Fig. 9 The A-CSBR in the embodiment includes:

[0259] The receiving unit 601 is used to receive a second service message from a second network, wherein the payload portion of the second service message includes IFIT message header information, wherein the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, wherein the target service flow is a service flow to which the second service message belongs, and wherein the apparatus 600 is used to connect the second network and the third network, wherein the second network and the third network are two different types of networks;

[0260] The processing unit 602 is configured to move the IFIT message header information from the payload part to the message header of the second service message to obtain the first service message;

[0261] The sending unit 603 is configured to send a first service message to the third network.

[0262] Optionally, the detailed implementation process of the processing unit 602 moving the IFIT message header information can be found in Figure 3 Step 109 in the illustrated embodiment or Fig. 9In step 404 of the embodiment shown, the C-ASBR moves the IFIT message header information in detail. Alternatively, the processing unit 602 moves the IFIT message header information in detail, which can be found in Figure 6 Step 207 in the illustrated embodiment or Figure 7 Step 306 in the illustrated embodiment is the detailed implementation process of the A-ASBR moving the IFIT message header information.

[0263] Optionally, the payload part further includes indication information, where the indication information is used to indicate that the second service message includes IFIT message header information;

[0264] The processing unit 602 is configured to move the IFIT message header information from the payload part to the message header of the second service message to obtain the first service message when it is determined according to the indication information that the second service message includes the IFIT message header information.

[0265] Optionally, the processing unit 602 is further configured to collect a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information;

[0266] The sending unit 603 is further configured to send a parameter value of at least one performance parameter to the controller.

[0267] Optionally, the detailed implementation process of the processing unit 602 collecting and sending parameter values ​​can be found in Figure 3 Steps 110-111 in the illustrated embodiment or Fig. 9 In the embodiment shown in FIG. 4, steps 405-406, C-ASBR collects and sends the detailed implementation process of the parameter value; or the detailed implementation process of the processing unit 602 collecting and sending the parameter value, can be found in FIG. Figure 6 Steps 208-209 in the illustrated embodiment or Figure 7 The detailed implementation process of steps 307-308 in the illustrated embodiment, in which the A-ASBR moves the indication information, will not be described in detail here.

[0268] Optionally, the third network is a Multi-Protocol Label Switching MPLS network, and the second network is an Internet Protocol IP network.

[0269] In an embodiment of the present application, a receiving unit receives a second service message from a second network, and a payload portion of the second service message includes IFIT message header information, and the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, and the target service flow is a service flow to which the second service message belongs. The processing unit moves the IFIT message header information from the payload portion to the message header of the second service message to obtain a first service message. The sending unit sends the first service message to a third network. Since the processing unit moves the IFIT message header information from the payload portion to the message header of the first service message, and then the sending unit sends the first service message to the third network, for other network elements located after the device on the service path for transmitting the first service message, when other network elements receive the service message sent by the sending unit, the parameter value of the performance parameter of the target service flow is collected according to the IFIT message header information in the service message, and sent to the controller, and the controller maintains the service path after the second network element according to the parameter value, thereby extending the length of the maintenance service path.

[0270] See also Fig.12 The embodiment of the present application provides a device 700 for sending a message, and the device 700 can be deployed in a third network element, and the third network element can be the above-mentioned Figure 3 or Figure 7 The first type of network element located between the A-ASBR and the C-ASBR in the embodiment, the device 700 includes:

[0271] The receiving unit 701 is used to receive a second service message, wherein the payload part of the second service message includes IFIT message header information, wherein the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, and the target service flow is the service flow to which the second service message belongs;

[0272] The processing unit 702 is configured to collect a parameter value of at least one performance parameter of a target service flow according to the IFIT message header information;

[0273] A sending unit 703, configured to send a parameter value of the at least one performance parameter to a controller;

[0274] The sending unit 703 is further configured to send a second service message.

[0275] Optionally, the detailed implementation process of the processing unit 702 collecting and sending parameter values ​​can be found in Figure 3 Step 108 in the illustrated embodiment or Figure 7 The detailed implementation process of step 308 in the illustrated embodiment, in which the first type of network element collects and sends parameter values, will not be described in detail here.

[0276] Optionally, the payload part further includes indication information, where the indication information is used to indicate that the second service message includes the IFIT message header information;

[0277] The processing unit 702 is configured to collect a parameter value of at least one performance parameter of the target service flow according to the IFIT message header information when it is determined according to the indication information that the second service message includes the IFIT message header information.

[0278] In an embodiment of the present application, a receiving unit receives a second service message, and the payload portion of the second service message includes IFIT message header information, and the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, and the target service flow is the service flow to which the second service message belongs. The processing unit collects the parameter value of the at least one performance parameter of the target service flow according to the IFIT message header information. The sending unit sends the parameter value of at least one performance parameter to the controller and sends the second service message. Since the payload portion of the second service message includes the IFIT message header information, the processing unit can collect the parameter value according to the IFIT message header information and send the parameter value to the controller, so that the controller can maintain the service path used to transmit the second service message according to the parameter value sent by the sending unit, thereby extending the length of the maintenance service path.

[0279] See also Fig.13 , the present application embodiment provides a schematic diagram of a device 800 for sending a message. The device 800 may be a first network element in any of the above embodiments, and the first network element is Figure 3 The embodiment shown or Fig. 9 A-ASBR in the embodiment shown; or, the first network element is Figure 6 The embodiment shown or Figure 7 The C-ASBR in the embodiment shown in the figure includes at least one processor 801 , a bus system 802 , a memory 803 and at least one transceiver 804 .

[0280] The device 800 is a hardware structure device that can be used to implement Fig.10 The functional modules in the device 500 are as follows. For example, those skilled in the art may think of Fig.10 The processing unit 502 in the device 500 shown can be implemented by the at least one processor 801 calling the code in the memory 803. Fig.10 The receiving unit 501 and the sending unit 503 in the device 500 shown can be implemented by the transceiver 804 .

[0281] Optionally, the processor 801 may be a general-purpose central processing unit (CPU), a network processor (NP), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0282] The bus system 802 may include a path for transmitting information between the components.

[0283] The transceiver 804 is used to communicate with other devices or communication networks.

[0284] The above-mentioned memory 803 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this. The memory can exist independently and be connected to the processor through a bus. The memory can also be integrated with the processor.

[0285] The memory 803 is used to store the application code for executing the solution of the present application, and the execution is controlled by the processor 801. The processor 801 is used to execute the application code stored in the memory 803, thereby realizing the functions in the method of the present patent.

[0286] In a specific implementation, as an embodiment, the processor 801 may include one or more CPUs, such as Fig.13 CPU0 and CPU1 in.

[0287] In a specific implementation, as an embodiment, the device 800 may include multiple processors, such as Fig.13801 and processor 807 in the embodiment of the present invention. Each of these processors may be a single-CPU processor or a multi-CPU processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0288] In a specific embodiment, the processor 801 is used to receive a first business message from a first network through the transceiver 804, the message header of the first business message includes IFIT message header information, and the IFIT message header information is used to indicate at least one performance parameter of a target business flow to be collected, the target business flow is the business flow to which the first business message belongs, and the device 800 is used to connect a first network and a second network, the first network and the second network are two different types of networks; the processor 801 moves the IFIT message header information from the message header to the payload part of the first business message to obtain a second business message; and then sends the second business message to the second network through the transceiver 804.

[0289] For the detailed processing process of the processor 801, please refer to the detailed description of processes S106 to 107, S204 to 205, S309 to 310, and S407 to 408 in the above embodiments, which will not be repeated here.

[0290] The transceiver 804 is used for the device 800 to receive and send messages through the network system. For the specific process, please refer to the detailed description of S108, S206, S311, and S409 in the above embodiment, which will not be repeated here.

[0291] See also Fig.14 , the present application embodiment provides a schematic diagram of a device 900 for sending a message. The device 900 may be a second network element in any of the above embodiments, and the second network element is Figure 3 The embodiment shown or Fig. 9 The C-ASBR in the embodiment shown; or, the second network element is Figure 6 The embodiment shown or Figure 7 The A-ASBR in the embodiment shown in the figure includes at least one processor 901 , a bus system 902 , a memory 903 and at least one transceiver 904 .

[0292] The device 900 is a hardware structure device that can be used to implement Fig.11 The functional modules in the device 600 are as follows. For example, those skilled in the art may think of Fig.11 The processing unit 602 in the device 600 shown can be implemented by the at least one processor 901 calling the code in the memory 903. Fig.11The receiving unit 601 and the sending unit 603 in the device 600 shown can be implemented by the transceiver 904 .

[0293] Optionally, the processor 901 may be a general-purpose central processing unit (CPU), a network processor (NP), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0294] The bus system 902 may include a path for transmitting information between the components.

[0295] The transceiver 904 is used to communicate with other devices or communication networks.

[0296] The memory 903 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may exist independently and be connected to the processor via a bus. The memory may also be integrated with the processor.

[0297] The memory 903 is used to store the application code for executing the solution of the present application, and the execution is controlled by the processor 901. The processor 901 is used to execute the application code stored in the memory 903, thereby realizing the functions in the method of the present patent.

[0298] In a specific implementation, as an embodiment, the processor 901 may include one or more CPUs, such as Fig.14 CPU0 and CPU1 in.

[0299] In a specific implementation, as an embodiment, the device 900 may include multiple processors, such as Fig.14 901 and processor 907 in the embodiment. Each of these processors may be a single-CPU processor or a multi-CPU processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0300] In a specific embodiment, the processor 901 is used to receive a second service message from the second network through the transceiver 904, the payload part of the second service message includes IFIT message header information, the IFIT message header information is used to indicate at least one performance parameter of the target service flow to be collected, the target service flow is the service flow to which the second service message belongs, the device 900 is used to connect the second network and the third network, the second network and the third network are two different types of networks. The processor 901 moves the IFIT message header information from the payload part to the message header of the second service message to obtain the first service message, and then sends the first service message to the third network through the transceiver 904.

[0301] For the detailed processing process of the processor 901, please refer to the detailed description of processes S109 to 110, S207 to 208, S306 to 307, and S404 to 405 in the above embodiments, which will not be repeated here.

[0302] The transceiver 904 is used for the device 900 to receive and send messages through the network system. For the specific process, please refer to the detailed description of S111, S209, S308, and S406 in the above embodiment, which will not be repeated here.

[0303] See also Fig.15 , an embodiment of the present application provides a schematic diagram of a device 1000 for sending a message. The device 1000 includes at least one processor 1001 , a bus system 1002 , a memory 1003 and at least one transceiver 1004 .

[0304] The device 1000 is a hardware structure device that can be used to implement Fig.12 The functional modules in the device 700 are as follows. For example, those skilled in the art may think of Fig.12 The processing unit 702 in the device 700 shown can be implemented by the at least one processor 1001 calling the code in the memory 1003. Fig.12 The receiving unit 701 and the sending unit 703 in the device 700 shown can be implemented by the transceiver 1004 .

[0305] Optionally, the processor 1001 may be a general-purpose central processing unit (CPU), a network processor (NP), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0306] The bus system 1002 may include a channel for transmitting information between the components.

[0307] The transceiver 1004 is used to communicate with other devices or communication networks.

[0308] The memory 1003 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may exist independently and be connected to the processor via a bus. The memory may also be integrated with the processor.

[0309] The memory 1003 is used to store the application code for executing the solution of the present application, and the execution is controlled by the processor 1001. The processor 1001 is used to execute the application code stored in the memory 1003, thereby realizing the functions in the method of the present patent.

[0310] In a specific implementation, as an embodiment, the processor 1001 may include one or more CPUs, such as Fig.15 CPU0 and CPU1 in.

[0311] In a specific implementation, as an embodiment, the apparatus 1000 may include multiple processors, for example Fig.151001 and 1007 in the embodiment of the present invention. Each of these processors may be a single-CPU processor or a multi-CPU processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0312] In a specific embodiment, the processor 1001 is used to receive a second business message through the transceiver 1004, the payload part of the second business message includes IFIT message header information, the IFIT message header information is used to indicate at least one performance parameter of the target business flow to be collected, the target business flow is the business flow to which the second business message belongs; the processor 1001 collects the parameter value of at least one performance parameter of the target business flow according to the IFIT message header information; then the transceiver 1004 sends the parameter value of at least one performance parameter to the controller; and sends the second business message.

[0313] See also Fig.16 , the present application embodiment provides a schematic diagram of a system 1100 for sending a message. The system 1100 includes: Fig.10 The device 500 or Fig.11 The device 600; or, the system 1100 includes Fig.13 The device 800 and Fig.14 The device 900.

[0314] Optional, such as Fig.10 The device 500 or Fig.13 The device 800 may be a first network element 1101, such as Fig.11 The device 600 or Fig.14 The device 900 may be the second network element 1102 .

[0315] Optionally, the system 1100 further includes: Fig.12 The device 700 or Fig.15 The device 1000, as Fig.12 The device 700 or Fig.15 The device 1000 may be a third network element 1103 .

[0316] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0317] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method for sending a message, characterized in that: The method comprises: A first network element receives a first service message from a first network, wherein a message header of the first service message includes an IFIT message header information of an in-flow detection scheme identifier, wherein the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, wherein the target service flow is a service flow to which the first service message belongs, and the first network element is used to connect the first network and a second network, wherein the first network and the second network are two different types of networks; The first network element moves the IFIT message header information from the message header to the payload part of the first service message to obtain a second service message; The first network element sends the second service message to the second network.

2. The method according to claim 1, characterized in that The message header of the first service message further includes indication information, where the indication information is used to indicate that the first service message includes the IFIT message header information; The first network element moves the IFIT message header information from the message header to the payload part of the first service message to obtain a second service message, including: When the first network element determines according to the indication information that the first service message includes the IFIT message header information, the first network element moves the IFIT message header information from the message header to the payload part of the first service message to obtain a second service message.

3. The method according to claim 2, characterized in that The first network element moves the IFIT message header information from the message header to the payload part of the first service message, further comprising: The first network element moves the indication information from the message header to the payload part of the first service message.

4. The method according to any one of claims 1 to 3, characterized in that The first network element moves the IFIT message header information from the message header to the payload part of the first service message to obtain a second service message, including: The first network element obtains the IFIT message header information from the message header, adds the IFIT message header information at the start position of the payload part of the first service message, and deletes the IFIT message header information from the message header to obtain a second service message.

5. The method according to any one of claims 1 to 3, characterized in that: After the first network element receives the first service message, the method further includes: The first network element collects a parameter value of the at least one performance parameter of the target service flow according to the IFIT message header information; The first network element sends a parameter value of the at least one performance parameter to the controller.

6. The method according to any one of claims 1 to 3, characterized in that: The first network is a Multi-Protocol Label Switching (MPLS) network, and the second network is an Internet Protocol (IP) network.

7. A method for sending a message, characterized in that: The method comprises: The second network element receives a second service message from a second network, wherein a payload portion of the second service message includes an IFIT message header information of an in-flow detection scheme identifier, wherein the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, wherein the target service flow is a service flow to which the second service message belongs, and the second network element is used to connect the second network and a third network, wherein the second network and the third network are two different types of networks; The second network element moves the IFIT message header information from the payload part to the message header of the second service message to obtain a first service message; The second network element sends the first service message to the third network.

8. The method according to claim 7, characterized in that The payload part also includes indication information, and the indication information is used to indicate that the second service message includes the IFIT message header information; The second network element moves the IFIT message header information from the payload part to the message header of the second service message to obtain a first service message, including: When the second network element determines according to the indication information that the second service message includes the IFIT message header information, the second network element moves the IFIT message header information from the payload part to the message header of the second service message to obtain the first service message.

9. The method according to claim 7 or 8, characterized in that After the second network element receives the second service message, the method further includes: The second network element collects the parameter value of the at least one performance parameter of the target service flow according to the IFIT message header information, and sends the parameter value of the at least one performance parameter to the controller.

10. The method according to claim 7 or 8, characterized in that The third network is a Multi-Protocol Label Switching (MPLS) network, and the second network is an Internet Protocol (IP) network.

11. A method for sending a message, characterized in that: The method comprises: The third network element receives a second service message, the payload part of the second service message includes an IFIT message header information of an in-flow detection scheme identifier, the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, the target service flow is a service flow to which the second service message belongs, the second service message is sent by the first network element, the second service message is a message obtained by the first network element receiving a first service message from a first network, and moving the IFIT message header information included in a message header of the first service message from the message header to the payload part of the first service message, the first network element is used to connect the first network and the second network, the first network and the second network are two different types of networks, and the third network element is located in the second network; The third network element collects a parameter value of the at least one performance parameter of the target service flow according to the IFIT message header information; The third network element sends a parameter value of the at least one performance parameter to the controller; The third network element sends the second service message.

12. The method according to claim 11, characterized in that The payload part also includes indication information, and the indication information is used to indicate that the second service message includes the IFIT message header information; The third network element collects the parameter value of the at least one performance parameter of the target service flow according to the IFIT message header information, including: When the third network element determines according to the indication information that the second service message includes the IFIT message header information, the third network element collects the parameter value of the at least one performance parameter of the target service flow according to the IFIT message header information.

13. A device for sending a message, characterized in that: The device comprises: A receiving unit, configured to receive a first service message from a first network, wherein a message header of the first service message includes an IFIT message header information of an in-flow detection scheme identifier, wherein the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, wherein the target service flow is a service flow to which the first service message belongs, and wherein the device is used to connect the first network and a second network, wherein the first network and the second network are two different types of networks; A processing unit, configured to move the IFIT message header information from the message header to the payload portion of the first service message to obtain a second service message; A sending unit is used to send the second service message to the second network.

14. The device according to claim 13, characterized in that The message header of the first service message further includes indication information, where the indication information is used to indicate that the first service message includes the IFIT message header information; The processing unit is configured to, when it is determined according to the indication information that the first service message includes the IFIT message header information, move the IFIT message header information from the message header to the payload part of the first service message to obtain a second service message.

15. The device according to claim 14, characterized in that The processing unit is further configured to move the indication information from the message header to the payload portion of the first service message.

16. The device according to any one of claims 13 to 15, characterized in that The processing unit is used for: The IFIT message header information is obtained from the message header, the IFIT message header information is added to the starting position of the payload part of the first service message, and the IFIT message header information is deleted from the message header to obtain a second service message.

17. The device according to any one of claims 13 to 15, characterized in that The processing unit is further configured to collect a parameter value of the at least one performance parameter of the target service flow according to the IFIT message header information; The sending unit is further used to send the parameter value of the at least one performance parameter to the controller.

18. The device according to any one of claims 13 to 15, characterized in that The first network is a Multi-Protocol Label Switching (MPLS) network, and the second network is an Internet Protocol (IP) network.

19. A device for sending a message, characterized in that: The device comprises: A receiving unit, configured to receive a second service message from a second network, wherein a payload portion of the second service message includes an IFIT message header information of an in-flow detection scheme identifier, wherein the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, wherein the target service flow is a service flow to which the second service message belongs, and wherein the device is used to connect the second network and a third network, wherein the second network and the third network are two different types of networks; A processing unit, configured to move the IFIT message header information from the payload part to the message header of the second service message to obtain a first service message; A sending unit, configured to send the first service message to the third network.

20. The device according to claim 19, characterized in that The payload part also includes indication information, and the indication information is used to indicate that the second service message includes the IFIT message header information; The processing unit is configured to move the IFIT message header information from the payload part to the message header of the second service message to obtain the first service message when it is determined according to the indication information that the second service message includes the IFIT message header information.

21. The device according to claim 19 or 20, characterized in that The processing unit is further configured to collect a parameter value of the at least one performance parameter of the target service flow according to the IFIT message header information; The sending unit is further used to send the parameter value of the at least one performance parameter to the controller.

22. The device according to claim 19 or 20, characterized in that The third network is a Multi-Protocol Label Switching (MPLS) network, and the second network is an Internet Protocol (IP) network.

23. A device for sending a message, characterized in that: The device comprises: a receiving unit, configured to receive a second service message, wherein the payload portion of the second service message includes an IFIT message header information identifying an in-flow detection scheme, wherein the IFIT message header information is used to indicate at least one performance parameter of a target service flow to be collected, wherein the target service flow is a service flow to which the second service message belongs, wherein the second service message is sent by a first network element, wherein the second service message is a message obtained by receiving a first service message from a first network by the first network element and moving the IFIT message header information included in a message header of the first service message from the message header to the payload portion of the first service message, wherein the first network element is used to connect the first network and a second network, wherein the first network and the second network are two different types of networks, and wherein the device is located in the second network; A processing unit, configured to collect a parameter value of the at least one performance parameter of the target service flow according to the IFIT message header information; a sending unit, configured to send a parameter value of the at least one performance parameter to the controller; The sending unit is further used to send the second service message.

24. The device according to claim 23, characterized in that The payload part also includes indication information, and the indication information is used to indicate that the second service message includes the IFIT message header information; The processing unit is used to collect the parameter value of the at least one performance parameter of the target service flow according to the IFIT message header information when it is determined according to the indication information that the second service message includes the IFIT message header information.

25. A system for sending a message, characterized in that: The system comprises: the device according to any one of claims 13 to 18 and the device according to any one of claims 19 to 22.

26. The system of claim 25, wherein: The system further comprises: an apparatus as claimed in claim 23 or 24.

27. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions. When the computer instructions in the computer-readable storage medium are executed by a computer device, the computer device executes the method according to any one of claims 1 to 12.

28. A computer program product, characterized in that The computer program product comprises a computer program stored in a computer-readable storage medium, and the computer program is loaded by a processor to implement the method according to any one of claims 1 to 12.

Images