CN106533973B

CN106533973B - Method, equipment and system for distributing service message

Info

Publication number: CN106533973B
Application number: CN201610978453.0A
Authority: CN
Inventors: 朱承旭; 陶东成; 王月华
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2016-11-04
Filing date: 2016-11-04
Publication date: 2021-01-29
Anticipated expiration: 2036-11-04
Also published as: CN106533973A

Abstract

The embodiment of the application provides a method, equipment and a system for distributing service messages, wherein the method comprises the following steps: the network equipment receives a first service message sent by first service initiating terminal equipment; the network equipment determines a candidate service node with the highest priority in the N candidate service nodes as a first target service node for processing the first service message, wherein the candidate service node is a service node capable of processing the first service message, and N is a positive integer greater than or equal to 2; the network device sends the first traffic message to the first target serving node. The technical scheme can ensure that the service node selected by the network equipment is the optimal service node capable of processing the service message.

Description

Method, equipment and system for distributing service message

Technical Field

The embodiments of the present application relate to the field of communications technologies, and in particular, to a method, a device, and a system for distributing service messages.

Background

With the development of information technology, more and more user equipments can access to the network. The identity of the user device is divided into an individual user and an enterprise user. User equipment (hereinafter referred to as "personal user") with an identity of a personal user needs to Access a network through a Broadband Remote Access Server (BRAS). User equipment identified as enterprise users (hereinafter referred to as "enterprise users") can directly access the network without going through the BRAS. These user devices may be referred to as enterprise users.

In the scenario where users (including individual users and enterprise users) access the network, some service nodes are needed to handle the traffic involved when the user equipment accesses the network. Currently, after receiving a data Frame (english: Frame) sent by a user equipment to request a data link layer service, a network device (e.g., a gateway device) broadcasts the data Frame to all service nodes capable of processing the data Frame. Each serving node responds to the data frame and sends a response to the network device. The network device sends the response to the user device after receiving the response. The ue may select a serving node as a target serving node for processing the data frame according to the response delay. In this case, the data frame sent by the network device to the other serving node is a useless data frame. The responses sent by the other serving nodes are also useless responses, which increases system overhead. In addition, the factors affecting the response delay are excessive, and therefore, the target service node selected based on the response delay is not necessarily the optimal service node. For example, the target serving node has a low latency but a large traffic load.

In addition, for a Packet (english: Packet) in the network layer, the ue needs to maintain the state of a service node for processing the Packet sent by the ue, and select the service node by itself, which increases the workload of the ue and is difficult to implement and maintain.

Disclosure of Invention

The embodiment of the application provides a method, equipment and a system for distributing service messages, so that a service node selected by network equipment is an optimal service node capable of processing the service messages.

In a first aspect, an embodiment of the present application provides a method for distributing service messages, where the method is applied in a scenario where a user accesses a network, and the method includes: the network equipment receives a first service message sent by first service initiating terminal equipment; the network equipment determines a candidate service node with the highest priority in the N candidate service nodes as a first target service node for processing the first service message, wherein the candidate service node is a service node capable of processing the first service message, and N is a positive integer greater than or equal to 2; the network device sends the first traffic message to the first target serving node. Based on the above technical solution, if the service message is a data frame of a data link layer, the network device may select a service node for processing the service message sent by the service originating device according to the priority of the service node, so that the service message does not need to be sent to each service node in the system. Thus, system overhead caused by useless service messages and responses can be avoided. If the service message is a data packet of the network side, the service initiating terminal device does not need to maintain the state of the service node. The selection of the serving node may be performed by the network device. Thus, the workload of the service initiating terminal equipment can be reduced. In the process of deploying the service node for selecting and processing the service message, the service node can be deployed on the side of the network equipment. In the process of maintaining the corresponding relationship between the service message and the service node, only the network device may be maintained, without maintaining each service initiating device. In addition, the priority level of a service node indicates the ability of the service node to process traffic messages. The higher the priority level, the more powerful the capability to process traffic messages. Therefore, the service node selected by the network device is the optimal service node capable of processing the traffic message.

With reference to the first aspect, in a first possible implementation manner of the first aspect, before the network device determines that a candidate serving node with a highest priority among the N candidate serving nodes is a first target serving node for processing the service message, the method further includes: the network equipment receives service range indication information sent by each service node in M service nodes, wherein the service range indication information sent by each service node is used for indicating a service range which can be processed by each service node, the M service nodes comprise the N candidate service nodes, and M is a positive integer greater than or equal to N; the network equipment receives first priority indication information sent by each service node, wherein the first priority indication information sent by each service node is used for indicating the priority of each service node; the network device determines the N candidate service nodes and the priority of each candidate service node in the N candidate service nodes according to the service range indication information sent by each service node and the first priority indication information sent by each service node. Based on the technical scheme, the network device can acquire the service range and the priority which can be processed by each service node, so that a proper service node can be selected for the service message sent by the service initiator based on the service range and the priority which can be processed by each service node.

With reference to the first aspect or any one of the foregoing possible implementations of the first aspect, in a second possible implementation of the first aspect, the method further includes: the network device stores the identity information of the first service initiating terminal device, the service type of the first service message and the corresponding relation of the first target service node. Based on the above technical solution, if the network device receives the service message sent by the first service originating device and having the same service type as the first service message again, the network device may directly send the service message to the first target service node without re-determining the target service node for processing the service message.

With reference to the second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, before the network device determines that a candidate serving node with a highest priority among the N candidate serving nodes is a first target serving node for processing the first service message, the method further includes: the network device determines that the network device does not store the identity information of the first service initiating terminal device, the service type of the first service message and the corresponding relationship of the first target service node. Based on the above technical solution, if the network device does not store the identity information of the first service originating device, the service type of the first service message, and the corresponding relationship of the first target service node, a process of determining the first target service node for processing the first service message may be started.

With reference to the first aspect or any one of the foregoing possible implementation manners of the first aspect, in a fourth possible implementation manner of the first aspect, the method further includes: the network device receives second priority indication information sent by the first target service node, wherein the second priority indication information sent by the first target service node is used for indicating the priority of the first target service node, and the priority of the first target service node indicated by the second priority indication information sent by the first target service node is lower than the priority of the first target service node indicated by the first priority indication information sent by the first target service node; the network equipment receives a second service message sent by second service initiating terminal equipment; and the network equipment sends the second service message to the first target service node under the condition that the identity information of the second service initiating terminal equipment is determined to be the same as the identity information of the first service initiating terminal equipment and the service type of the second service message is determined to be the same as the service type of the first service message. Based on the technical scheme, even if the priority of the service node changes, the established sharing strategy still remains unchanged. Therefore, the times of determining the sharing strategy can be reduced, and the burden of the network equipment can be reduced.

With reference to the second possible implementation manner of the first aspect or the third possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the method further includes: the network equipment determines that the first target service node does not participate in the sharing of the service message any more; the network device deletes the identity information of the first service initiating terminal device, the service type of the first service message and the corresponding relation of the first target service node, which are stored by the network device. Based on the above technical solution, the network device may not send the service message sent by the first service originating device to the first target service node using the same sharing policy any more under the condition that the first target service node does not participate in the service message sharing any more.

With reference to the first aspect or any one of the foregoing possible implementation manners of the first aspect, in a sixth possible implementation manner of the first aspect, the first service initiating device is a user equipment or a first service node, where the first service node is a service node for processing a data link layer service or a network layer service.

With reference to the first aspect or any one possible implementation manner of the first possible implementation manner to the fifth possible implementation manner of the first aspect, in a seventh possible implementation manner of the first aspect, the service message is a data link layer service message or a network layer service message.

With reference to the first possible implementation manner of the first aspect, in an eighth possible implementation manner of the first aspect, the method further includes: the network device receives keep-alive information sent by each of the M serving nodes.

With reference to the eighth possible implementation manner of the first aspect, in a ninth possible implementation manner of the first aspect, the network device receives an LLDP packet sent by each service node of the M service nodes, where the LLDP packet carries the service range indication information and the first priority indication information, or the LLDP packet carries the service range indication information, the first priority indication information, and the keep-alive information.

In a second aspect, an embodiment of the present application provides a method for distributing service messages, where the method is applied in a scenario where a user accesses a network, and the method includes: the service node sends service range indicating information to the network equipment, wherein the service range indicating information is used for indicating the service range which can be processed by the service node; the service node sends priority indication information to the network equipment, wherein the priority indication information is used for indicating the priority of the service node; the service node receives a service message sent by the network equipment; the service node processes the traffic message.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the method further includes: the serving node sends keep-alive information to the network device.

With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the service node sends an LLDP packet to the network device, where the LLDP packet carries the service range indication information, the priority indication information, and the keep-alive information.

In a third aspect, an embodiment of the present application provides a network device, where the network device includes a unit configured to execute the first aspect or any possible implementation manner of the first aspect.

In a fourth aspect, an embodiment of the present application provides a service node, where the service node includes a unit configured to execute any possible implementation manner of the second aspect.

In a fifth aspect, an embodiment of the present application further provides a network device, where the network device includes a processor, a memory, and a transceiver. The memory is for storing instructions for implementing the method of the first aspect. The processor is configured to perform the method of the first aspect in conjunction with the transceiver executing instructions stored by the memory.

In a sixth aspect, an embodiment of the present application further provides a service node, where the service node includes a processor, a memory, and a transceiver. The memory is for storing instructions for implementing the method of the second aspect. The processor is configured to perform the method of the second aspect in conjunction with the transceiver executing the instructions stored by the memory.

In a seventh aspect, an embodiment of the present application further provides a system for distributing service messages, where the system includes the network device in the third aspect and at least two service nodes in the fourth aspect.

Drawings

Fig. 1 is a schematic diagram of a system provided according to an embodiment of the present application.

Fig. 2 is a schematic flow chart of a method for distributing service messages provided according to an embodiment of the present application.

Fig. 3 is a block diagram of a network device according to an embodiment of the present application.

Fig. 4 is a block diagram of a service node provided according to an embodiment of the present application.

Fig. 5 is a block diagram of a network device according to an embodiment of the present application.

Fig. 6 is a block diagram of a service node provided according to an embodiment of the present application.

Fig. 7 is a schematic diagram of a system for distributing service messages provided according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

The user Equipment referred to in this application is all Equipment capable of accessing to a network, including but not limited to a computer, a mobile phone, a tablet computer, a client terminal Equipment (CPE for short), and the like.

In the scenario that an individual user accesses the network, besides the BRAS needs to be responsible for the work of authentication, charging and the like of the individual user, some other service nodes are involved to process the services involved when the individual user accesses the network. For example, if the individual user has been assigned an intranet Internet Protocol (IP) Address, but wishes to communicate with an extranet host (including but not limited to a server, a user device, etc.), then access to the extranet may be provided by way of providing Network Address Translation (NAT). The service node providing NAT service will translate the IP address used by the individual user on the intranet into a global IP address for the individual user to communicate with the extranet host. As another example, in some cases, when the individual user accesses the network, it may be necessary to perform detection analysis on the traffic of the individual user accessing the network, so as to perform filtering control on the detected traffic according to a predefined policy. In this case, the network layer service message of the individual user access network is sent to a service node capable of Deep Packet Inspection (DPI). The service node performing DPI performs inspection and analysis on the traffic of the individual user accessing the network.

In the network access scene of the enterprise user, the works such as verification, charging and the like do not need to be carried out through the BRAS. But it may also require some service nodes to provide corresponding services for the enterprise user access network. For example, a service node that needs to provide NAT services translates an intranet IP to an extranet IP. As another example, a service node that needs to perform DPI performs inspection analysis on the traffic of the enterprise user.

For convenience of description, nodes handling traffic involved when users (including personal users and enterprise users) access the network are collectively referred to as service nodes in this application, including but not limited to BRAS, service nodes providing NAT service, service nodes performing DPI. These service nodes may be physical devices, such as servers, routers, etc., running respective business functions (e.g., BRAS, NAT, DPI, etc.); the Virtual service node may also be a Virtual Machine (VM) running a corresponding service Function program (e.g., BRAS, NAT, DPI, etc.) in a Network Function Virtualization (NFV) scenario, where the VM is deployed on a hardware device (e.g., a physical server). A virtual machine refers to a complete computer system with complete hardware system functionality, which is emulated by software, running in a completely isolated environment. In which, a physical server is virtualized into a plurality of logical computers by virtualization technology, each logical computer is a virtual machine on the physical server, and each virtual machine can run a different operating system, so that the application programs of the virtual machines can run in the spaces of the operating systems independent of each other. Depending on the type of traffic provided for processing, the service nodes may be divided into service nodes that handle data link layer traffic (e.g., BRAS) and service nodes that handle network layer traffic (e.g., service nodes that perform DPI, service nodes that provide NAT services).

The user access network scenario referred to in the present application includes an individual user access network scenario and an enterprise user access network scenario.

Fig. 1 is a schematic diagram of a system provided according to an embodiment of the present application. As shown in fig. 1, system 100 includes network device 101, service node 111, service node 112, service node 113, service node 121, service node 122, and service node 123. Also included in system 100 shown in fig. 1 are user device 131 and user device 132. Service node 111, service node 112, and service node 113 are service nodes that provide services that handle the data link layer. Service node 121, service node 122, and service node 123 are service nodes for providing network layer services. Embodiments of the present application will be further described below in conjunction with the system 100 shown in fig. 1.

Fig. 2 is a schematic flow chart of a method for distributing service messages provided according to an embodiment of the present application. The method shown in fig. 2 may be applied in a user access network scenario.

Network device 101 receives traffic indication information sent by serving node 121.

Network device 101 may receive traffic indication information sent by serving node 121, and may also receive traffic indication information sent by other serving nodes in system 100. In other words, the network device 101 may receive the service range indication information sent by each service node in the system 100, where the service range indication information sent by each service node is used to indicate the service range that each service node can handle.

Optionally, in some embodiments, the service range that can be processed by each service node indicated by the service range indication information sent by each service node includes a service type that can be processed by each service node. Assuming that the service node 111, the service node 112, and the service node 113 are service nodes for processing data link layer traffic, the traffic range indication information sent by the service node 111, the service node 112, and the service node 113 may be used to indicate that the service node sending the traffic range indication information may provide services for processing data link layer traffic. Assuming that service node 121, service node 122, and service node 123 are service nodes for processing DPI traffic, the traffic range indication information sent by service node 121, service node 122, and service node 123 may be used to indicate that the service node sending the traffic range indication information may provide services for processing DPI traffic. In this way, network device 101 may determine, according to the service range indication information sent by service node 111, service node 112, and service node 113, that service node 111, service node 112, and service node 113 are service nodes capable of providing services for processing data link layer services. Network device 101 may further determine, according to the service range indication information sent by service node 121, service node 122, and service node 123, that service node 121, service node 122, and service node 123 are service nodes for providing and processing DPI services.

For convenience of description, if a service corresponding to a service type needs to be provided for a service message, the service message may be referred to as a service message requesting the service type. For example, if a service message needs to be provided with a data link layer service, the service message may be referred to as a service message requesting the data link layer service. If deep packet inspection needs to be performed on the service message, the service message may be called a service message requesting a DPI service.

Optionally, in other embodiments, the service scope that can be processed by each service node indicated by the service scope indication information sent by each service node includes the type of service that can be processed by each service node and the identity information of the service originating device that sends the service message that can be processed by each service node.

It is assumed that the service node 111 can process a service message requesting a data link layer service sent by a service initiating device within a first Media Access Control (MAC) address range. In this case, the service node 111 may send the service range indication information to indicate that the service node 111 may provide the data link layer service for the service initiating device having the MAC address within the first MAC address range. The service node 112 may process a service message requesting data link layer service sent by a service originating device within the second MAC address range. In this case, the service node 112 may send the service range indication information to indicate that the service node 112 may provide data link layer service for the service initiating device having the MAC address within the second MAC address range. The service node 113 may process a service message requesting data link layer service sent by the service initiating device in the third MAC address range. In this case, the service node 113 may send the service range indication information to indicate that the service node 113 may provide the data link layer service for the service initiating device having the MAC address within the third MAC address range. The first MAC address range, the second MAC address range, and the third MAC address range may or may not include an intersection, which is not limited in the embodiment of the present application. In this way, the network device 101 may determine, according to the service range indication information sent by the service node 111, a service message requesting a data link layer service, sent by a service initiator device within the first MAC address range that can be processed by the service node 111. The network device 101 may determine, according to the service range indication information sent by the service node 112, a service message requesting data link layer service sent by a service initiator device in the second MAC address range that can be processed by the service node 112. The network device 101 may determine, according to the service range indication information sent by the service node 113, a service message requesting a data link layer service, sent by a service initiator device within a third MAC address range that can be processed by the service node 113.

Assume that service node 121 can process a traffic message requesting DPI traffic sent by a traffic originating device having a source IP address within a first IP address range. In this case, the service node 121 may send the service range indication information to indicate that the service node 121 may provide the DPI service for the service initiating device having the source IP address in the first IP address range. Service node 122 may process a traffic message requesting DPI traffic sent by a traffic originating device having a source IP address within the second IP address range. In this case, the service node 122 may send the service range indication information to indicate that the service node 122 may provide the DPI service for the service initiating device having the source IP address in the second IP address range. Service node 123 may process a traffic message requesting DPI traffic sent by a traffic originator device having a source IP address within the third IP address range. In this case, the service node 123 may send the service range indication information to indicate that the service node 123 may provide the DPI service for the service initiating device having the source IP address in the third IP address range. Similarly, the first IP address range, the second IP address range, and the third IP address range may or may not include an intersection, which is not limited in this embodiment of the present application. It is to be understood that the above-mentioned identity information is only some specific embodiments, and the service scope indication information includes the identity information of the service originating device sending the service message, and may also be other information capable of distinguishing the identity of the service originating device, for example, if the service message sent by the service originating device is a service message for requesting DPI service, the identity information of the service originating device included in the service type may be any one or more of five-tuple information or seven-tuple information. In this way, network device 101 may determine, according to the service range indication information sent by serving node 121, that serving node 121 may process a service message, which is sent by a service originating device having a source IP address within a first IP address range and is used for requesting DPI service, where the service originating device is located within the first IP address range. Network device 101 may determine, according to the service range indication information sent by service node 122, that service node 122 may process a service message, which is sent by a service originating device having a source IP address within a second IP address range and is used for requesting DPI service. Network device 101 may determine, according to the service range indication information sent by service node 123, that service node 123 may process a service message, which is sent by a service originating device having a source IP address within a third IP address range and is used for requesting DPI service.

202, network device 101 receives the first priority indication information sent by serving node 121.

Network device 101 may receive first priority indication information sent by other serving nodes in system 100, in addition to first priority indication information sent by serving node 121. In other words, the network device 101 may receive the first priority indication information sent by each service node in the system 100, where the first priority indication information sent by each service node is used to indicate the priority of each service node.

Assume that the priority of the service nodes in system 100 has eight levels in total. The eight priorities are 0, 1, 2, 3, 4, 5, 6 and 7 respectively, wherein the priority of 0 means the lowest priority and the priority of 7 means the highest priority. Assume in the embodiment shown in fig. 2 that each serving node in system 100 has a priority of 7 in the initial state. In this case, the priority indicated by the first priority indication information sent by each serving node in the system 100 is 7. In this way, the network device 101 may determine that the priority of each service node in the system 100 is 7 according to the first priority indication information sent by each service node in the system 100.

Optionally, in some embodiments, each service node in the system 100 may send the first priority indication information and the traffic range indication information to the network device 101 through one message. The technical scheme can reduce the signaling overhead between the service node and the network equipment.

Optionally, in other embodiments, each service node in the system 100 may send the first priority indication information and the traffic range indication information to the network device 101 through two messages.

203, the network device 101 receives the first service message sent by the user equipment 131.

The network device 101 may determine a candidate serving node with a highest priority among N candidate serving nodes as a first target serving node for processing the first traffic message, where the candidate serving node is a serving node capable of processing the first traffic message, and N is a positive integer greater than or equal to 2. After which network device 101 may send the first traffic message to the first target serving node.

Assuming that, in the embodiment shown in fig. 2, the traffic range that can be processed by each service node indicated by the traffic range indication information sent by each service node only includes the type of traffic message that can be processed by each service node, and the first traffic message that needs to be sent by user equipment 131 is a traffic message for requesting DPI service, network device 101 may determine that service node 121, service node 122, and service node 123 in system 100 are candidate service nodes. Also according to the assumption in step 202 that the priorities of the three candidate service nodes are the same and 7, the network device 101 may determine that any candidate service node of the three candidate service nodes is the first target service node. Assuming that network device 101 determines that the first target candidate serving node is serving node 121, the method shown in fig. 2 may further include step 204 and step 205.

Network device 101 determines a first target serving node for serving node 121 to process the first traffic message 204.

Network device 101 sends 205 the first traffic message to serving node 121.

According to the method shown in fig. 2, if the service message is a data frame of a data link layer, the network device may select a service node for processing the service message sent by the service originating device according to the priority of the service node, so that the service message does not need to be sent to each service node in the system. Thus, system overhead caused by useless service messages and responses can be avoided.

If the service message is a data packet of a network layer, the service initiating terminal device does not need to maintain the state of the service node. The selection of the serving node may be performed by the network device. Thus, the workload of the service initiating terminal equipment can be reduced. In the process of deploying the service node for selecting and processing the service message, the service node can be deployed on the side of the network equipment. In the process of maintaining the corresponding relationship between the service message and the service node, only the network device may be maintained, without maintaining each service initiating device.

In addition, the priority level of a service node indicates the ability of the service node to process traffic messages. The higher the priority level, the more powerful the capability to process traffic messages. Therefore, the service node selected by the network device is the optimal service node capable of processing the traffic message.

It will be appreciated that the granularity of the traffic type of the traffic message is the same as the granularity of the traffic type that the serving node is capable of handling. For example, if one serving node can handle all data link layer traffic. In this case, it is only necessary to determine whether the first service message is a message for requesting a data link layer service. If a service node is a service node for providing and processing the DPI service, under the condition that the first service message is determined to be a service message requesting a network layer service, it is further required to determine whether the first service message is a service message requesting a DPI service.

Optionally, in other embodiments, the service scope that can be processed by each service node indicated by the service scope indication information sent by each service node includes a type of a service message that can be processed by each service node and identity information of a service originating device that sends the service message that can be processed by each service node. If the first service message that needs to be sent to user equipment 131 is a service message for requesting DPI service and the IP address of user equipment 131 is within the first IP address range and the second IP address range, network device 101 may determine that serving node 121 and serving node 122 in system 100 are candidate serving nodes. In this case, N is equal to 2. Since the priorities of the two candidate service nodes are the same, the network device 101 may determine that any one of the two candidate service nodes is the first target service node. Assuming that network device 101 determines that the first target candidate serving node is serving node 121, network device 101 may send the first traffic message to serving node 121.

Optionally, in some embodiments, the network device 101 may further store the identity information of the first service originating device, the service type of the first service message, and the corresponding relationship of the first target service node. Specifically, the network device 101 may establish a sharing information table, where the sharing information table is used to store the identity information of the service initiating device, the service type of the service message sent by the service initiating device, and the corresponding relationship between the target service nodes. Thus, after receiving the service message sent by the service initiating device, the network device 101 may determine whether the corresponding relationship between the identity information of the service initiating device, the service type requested by the service message, and the service node is stored in the sharing information table. If yes, the target service node for processing the service message can be determined directly according to the sharing information table. If not, the target service node for processing the service message may be determined by referring to the method shown in fig. 2, and after the target service node is determined, the identity information of the service originating device, the service type requested by the service message, and the corresponding relationship of the service node are added to the sharing information table.

Table 1 is an illustration of a sharing information table.

TABLE 1

Table 2 is an illustration of another allocation information table.

TABLE 2

As shown in table 1, a service message for requesting a data link layer service, which is transmitted by the user equipment 131, is shared to the service node 111. As shown in table 2, a traffic message for requesting DPI service, which is transmitted by the user equipment 131, is shared to the service node 121.

Alternatively, in some embodiments, network device 101 may be used only for allocating service messages for requesting data link layer services or only for requesting network layer services. In this case, the network device 101 may include only the allocation information table as shown in table 1, or only the allocation information table as shown in table 2.

Optionally, in other embodiments, the network device 101 may be configured to allocate service messages for requesting data link layer services as well as for requesting network layer services. In this case, the network device 101 may include two sharing information tables as shown in table 1 and table 2. Alternatively, the network device 101 may include one allocation information table that includes all of the contents of tables 1 and 2.

It is assumed that the allocation information tables shown in table 1 and table 2 are allocation information tables held by the network device 101. Network device 101 may also receive a second service message. If the network device 101 determines that the service type requested by the second service message is data link layer service and the MAC address of the service originating device sending the second service message is the MAC address of the user equipment 131, the network device 101 may directly send the second service message to the service node 111. If the network device 101 determines that the service type of the second service request message is a data link layer service and the MAC address of the service originating device sending the second service message is the MAC address of the user equipment 132, the network device 101 needs to determine a target service node for processing the second service message. Similarly, if the network device determines that the service type of the second service message request is DPI service and the source IP address of the second service message is the IP address of user equipment 131, network device 101 may directly send the second service message to service node 121. If the network device 101 determines that the service type requested by the second service message is the NAT service, the network device 101 needs to determine a target service node for processing the second service message. If network device 131 determines that the service type of the second service message request is DPI service and the source IP address of the second service message is the IP address of user equipment 132, network device 101 needs to determine a target service node for processing the second service message. Network device 101 may determine a target serving node for processing the second traffic message with reference to the method illustrated in fig. 2.

For convenience of description, the corresponding relationship between the identity information of the service initiating device, the service type of the service message sent by the service initiating device, and the service node processing the service message may be referred to as a sharing policy.

Alternatively, in some embodiments, the priority of the service nodes in system 100 may change. For example, the priority of a serving node may change if the traffic load handled by the serving node exceeds a certain threshold. As another example, the priority of a serving node may change if the delay of the serving node to network device 101 exceeds a certain threshold. The serving node may send the updated priority to network device 101.

Optionally, in some embodiments, the network device 101 may further receive second priority indication information sent by the first target serving node, where the priority indicated by the second priority indication information is lower than the priority indicated by the first priority indication information.

It is continuously assumed that the network device 101 holds the allocation information table shown in table 1. Service node 111, service node 112, service node 113, service node 121, service node 122, and service node 123 all have a priority level of 7. Assume that network device 101 receives second priority indication information sent by serving node 111, where the second priority indication information is used to indicate that serving node 111 has a priority level of 6. In this case, if the network device 101 determines that the service type of the received second service message request is data link layer service and the MAC address of the service originating device sending the second service message is the MAC address of the user equipment 131, the network device 101 may continue to execute the established measurement sharing policy, that is, directly send the second service message to the service node 111. If the network device 101 determines that the service type of the received second service request message is data link layer service and the MAC address of the service originating device that sent the second service message is the MAC address of the user equipment 132, the network device 101 needs to determine a target service node for processing the second service message. Specifically, it is assumed that a service message requesting data link layer service sent by a service initiator device in a first MAC address range can be processed by service node 111, a service message requesting data link layer service sent by a service initiator device in a second MAC address range can be processed by service node 112, a service message requesting data link layer service sent by a service initiator device in a third MAC address range can be processed by service node 113, and a MAC address of user equipment 132 is in the first MAC address range, the second MAC address range, and the third MAC address range. At this time, the priority level of serving node 111 is 6, and the priority levels of serving node 112 and serving node 113 are both 7. In other words, serving node 111 has a lower priority level than serving nodes 112 and 113. In this case, network device 101 may determine a serving node from serving node 112 and serving node 113 as a second target serving node to process the second traffic message. Assume that network device 101 can determine that serving node 112 is the second target serving node.

Further, it is assumed that network device 101 receives second priority indication information sent by serving node 112, where the second priority indication information is used to indicate that the priority level of serving node 112 is 6. Assume that network device 101 receives second priority indication information sent by serving node 113, where the second priority indication information is used to indicate that serving node 113 has a priority level of 6. In this case, if the network device 101 determines that the service type of the received third service message request is data link layer service and the MAC address of the service originating device sending the third service message is the MAC address of the user equipment 131, the network device 101 may continue to execute the established sharing policy. If the network device 101 determines that the service type of the received third service message request is a data link layer service and the MAC address of the service originating device sending the third service message is the MAC address of the user equipment 132, the network device 101 may continue to execute the established sharing policy. If the network device 101 determines that the service type of the received third service message request is data link layer service and the MAC address of the service originating device sending the third service message is the MAC address of the user equipment 133 (not shown in fig. 1), the network device 101 may determine a third target service node for processing the third service message according to the method shown in fig. 2.

Further, if the priority level of the service node is the lowest priority level, the network device 101 does not allocate the service message to the service node any more. But the serving node may continue to enforce the established sharing policy.

Specifically, it is assumed that network device 101 receives third priority indication information sent by serving node 111, where the first priority indication information is used to indicate that the priority level of serving node 111 is 0 (i.e., the lowest priority level). In this case, if the network device 101 receives a service message for requesting a data link layer service sent by the user equipment 131, the network device 101 may continue to send the service message to the service node 111. If a service message received by network device 101 for requesting data link layer service is sent by user equipment 134 (not shown in fig. 1), network device 101 may determine that one serving node is a serving node for processing the service message from serving nodes 112 and 113 (assuming that the priority levels of serving nodes 112 and 113 are the same and are not 0).

In addition to the above-described embodiments in which the priority level of the serving node is lowered, in some embodiments the priority of the serving node may also be raised. It is to be understood that the serving node must not exceed the highest priority level, either. Similar to the above embodiment, in the case that the priority of the service node is raised, for the service message with the established sharing policy, the network device 101 still sends the service message to the corresponding target service node by using the established sharing policy. For a traffic message for which a sharing policy is not established, the network device 101 may determine a service node for providing a service for the traffic message with reference to the method shown in fig. 2.

Optionally, in some embodiments, the network device 101 may determine that the first target serving node is no longer involved in the traffic message sharing. In this case, the network device 101 may delete the identity information of the first service originating device, the service type of the first service message, and the corresponding relationship of the first target service node, which are stored in the network device 101.

Optionally, in some embodiments, a serving node in system 100 can periodically (which can be referred to as a keep-alive period) send keep-alive information to network device 101. If the network device 101 does not receive the keep-alive information sent by one service node in the keep-alive period, it may be determined that the service node does not participate in the traffic message sharing any more. Further, in order to avoid misjudgment caused by network packet loss, the network device 101 may determine that a service node no longer participates in sharing of the service message when determining that keep-alive information sent by the service node in a plurality of continuous keep-alive periods is not received.

In some embodiments, the keep-alive information sent by the serving node may be sent in the same message as the priority indication information indicating the priority of the serving node and the traffic range indication information. That is, the serving node may periodically send the priority and traffic range of the serving node to the network device 101.

Specifically, the service range indication information, the priority indication information, and the keep-alive information may be carried by a Link Layer Discovery Protocol (LLDP). The data portion of the LLDP packet may include a Type Length Value (TLV), a priority TLV, and a Time To Live (TTL) TLV. It can be understood that the traffic range TLV is configured to carry the traffic range indication information, the priority TLV is configured to carry the priority indication information, and the TTL TLV is configured to carry the keep-alive information. In addition, the data portion of the LLDP packet may also carry TLVs carried by the LLDP data portion in the prior art, such as a bridge identifier (english: chasis ID) TLV, a Port identifier (english: Port ID) TLV, and the like.

Optionally, in other embodiments, the network device 101 may periodically (may be referred to as a keep-alive period) send one keep-alive message to each service node, and if the network device 101 does not receive a response sent by the service node, it may be determined that the service node is no longer involved in the traffic message sharing. Similarly, in order to avoid misjudgment caused by network packet loss, the network device 101 may determine that a service node no longer participates in traffic message sharing when determining that no response sent by the service node in a plurality of consecutive keep-alive periods is received.

Optionally, in other embodiments, network device 101 may measure the transmission delay from each serving node to network device 101. If the transmission delay from a service node to the network device 101 exceeds a preset threshold, it may be determined that the service node does not participate in the sharing of the service message any more.

Assume that the network device 101 holds a sharing information table as shown in table 1. In a case that it is determined that the service node 111 is no longer involved in the sharing of the service message, the network device 101 may delete the sharing policy corresponding to the service node 111 from the sharing information table. In this case, if the network device 101 receives a service message for requesting a data link layer service sent by the user equipment 131, the network device 101 re-determines a service node for processing the service message from the candidate service nodes with the highest priority. It will be appreciated that the candidate serving node now no longer includes serving node 111.

Through the technical scheme, the network device 101 can sense the change (for example, the priority change, whether the service can be provided, and the like) of the service node at the first time. In this way, the network device 101 may adjust the sharing policy of the traffic message at the first time, which does not cause the network device 101 to send the traffic message to a service node with low priority or to a service node that cannot provide service.

Optionally, in some embodiments, the network device 101 may receive, in addition to the first service message sent by the user equipment, a service message sent by the service node. In other words, the service initiating device may be a user equipment or a service node. The service node may be a service node for processing data link layer traffic or a service node for processing network layer traffic.

Specifically, the network device 101 may determine, according to a preset management policy, a service that needs to be involved when the user accesses the network. The specific content and the making method of the management policy can refer to the description in the prior art, and need not be described herein.

For example, in some embodiments, the network device 101 may determine that deep packet inspection needs to be performed on a service message sent by the user equipment 131 after the user equipment 131 is on line through the BRAS. In this case, the network device 101 may determine that the service node 111 is a first target service node for processing the traffic message requesting to go online sent by the user equipment 131, by referring to the method shown in fig. 2. After completing the online service processing of the user equipment 131, the service node 111 may send the processed service message to the network device 101. Network device 101 may determine that service node 121 is a service node for performing deep packet inspection on a service message sent by service node 111 with reference to the method shown in fig. 2, and send the processed service message sent by service node 111 to service node 121.

For another example, in some embodiments, the network device 101 may determine that network address translation is required before deep packet inspection when the user equipment 131 accesses the network. In this case, the network device 101 may determine a serving node (hereinafter, referred to as a target NAT serving node, which is not shown in fig. 1) that can provide NAT service and has the highest priority, by referring to the method shown in fig. 2, and send the service message sent by the user equipment 131 to the target NAT serving node. After completing the IP address translation service, the target NAT service node sends the processed service message to the network device 101. The network device 101 may determine that the service node 121 is a service node for performing deep packet inspection with reference to the method shown in fig. 2, and send the processed service message sent by the target NAT service node to the service node 121.

Network device 101 may be a switch if network device 101 is only responsible for sharing traffic messages requesting data link layer traffic. Network device 101 may be a router or a switch if network device 101 is responsible for sharing traffic messages requesting network layer traffic. It can be understood that the network device 101 may be a switch if the network device 101 is responsible for sharing a service message requesting a data link layer service, or is responsible for sharing a service message requesting a network side service.

Fig. 3 is a block diagram of a network device according to an embodiment of the present application. As shown in fig. 3, the network device 300 includes a receiving unit 301, a processing unit 302, and a transmitting unit 303.

A receiving unit 301, configured to receive a first service message sent by a first service originating device.

A processing unit 302, configured to determine a candidate service node with a highest priority in the N candidate service nodes as a first target service node for processing the first service message, where the candidate service node is a service node capable of processing the first service message, where N is a positive integer greater than or equal to 2.

A sending unit 303, configured to send the first service message to the first target serving node.

Optionally, in some embodiments, the receiving unit 301 is further configured to receive service range indication information sent by each service node of M service nodes, where the service range indication information sent by each service node is used to indicate a service range that can be processed by each service node, where the M service nodes include the N candidate service nodes, and M is a positive integer greater than or equal to N. The receiving unit 301 is further configured to receive first priority indication information sent by each serving node, where the first priority indication information sent by each serving node is used to indicate a priority of each serving node. The processing unit 302 is further configured to determine the N candidate service nodes and the priority of each candidate service node in the N candidate service nodes according to the service range indication information sent by each service node and the first priority indication information sent by each service node.

Optionally, in some embodiments, the processing unit 302 stores the identity information of the first service originating device, the service type of the first service message, and the corresponding relationship of the first target service node.

Optionally, in some embodiments, the processing unit 302 is further configured to determine that the processing unit 302 does not store the identity information of the first service originating device, the service type of the first service message, and the corresponding relationship of the first target service node before determining that a candidate service node with a highest priority among the N candidate service nodes is the first target service node for processing the first service message.

Optionally, in some embodiments, the receiving unit 301 is further configured to receive second priority indication information sent by the first target serving node, where the second priority indication information sent by the first target serving node is used to indicate a priority of the first target serving node, and the priority of the first target serving node indicated by the second priority indication information sent by the first target serving node is lower than the priority of the first target serving node indicated by the first priority indication information sent by the first target serving node. The receiving unit 301 is further configured to receive a second service message sent by the second service originating device. The processing unit 302 is further configured to determine that the identity information of the second service originating device is the same as the identity information of the first service originating device, and that the service type of the second service message is the same as the service type of the first service message. The sending unit 303 is further configured to send the second service message to the first target service node when the processing unit 302 determines that the identity information of the second service originating device is the same as the identity information of the first service originating device and the service type of the second service message is the same as the service type of the first service message.

Optionally, in some embodiments, the processing unit 302 is further configured to determine that the first target serving node is no longer involved in the traffic message sharing. The processing unit 302 is further configured to delete the identity information of the first service originating device, the service type of the first service message, and the corresponding relationship between the first target service node, which are stored in the processing unit 302.

The operations and functions of the receiving unit 301, the processing unit 302, and the sending unit 303 of the network device 300 may refer to the method of fig. 2, and are not described herein again to avoid repetition.

The receiving unit 301 and the transmitting unit 303 may be implemented by transceivers. The processing unit 302 may be implemented by a processor.

Similarly, if network device 300 is responsible only for sharing traffic messages requesting data link layer traffic, network device 300 may be a switch. Network device 300 may be a router or a switch if network device 300 is responsible for sharing traffic messages requesting network layer traffic. It is understood that the network device 300 may be a switch if the network device 300 is responsible for sharing service messages requesting a data link layer service, or is responsible for sharing service messages requesting a network side service.

Fig. 4 is a block diagram of a service node provided according to an embodiment of the present application. As shown in fig. 4, the service node 400 includes a transmitting unit 401, a receiving unit 402, and a processing unit 403.

A sending unit 401, configured to send service range indication information to a network device, where the service range indication information is used to indicate a service range that can be processed by the service node 400;

the sending unit 401 is further configured to send priority indication information to the network device, where the priority indication information is used to indicate the priority of the serving node 400.

A receiving unit 402, configured to receive a service message sent by the network device.

A processing unit 403, configured to process the service message.

Optionally, in some embodiments, processing unit 403 is further configured to determine a priority of serving node 400 according to the current state of serving node 400.

Optionally, in some embodiments, the sending unit 403 is further configured to send keep-alive information to the serving node 400.

The service message may be the first service message, the second service message or the third service message in the above method.

The operations and functions of the sending unit 401, the receiving unit 402 and the processing unit 403 of the service node 400 may refer to the method of fig. 2, and are not described herein again to avoid repetition.

The transmitting unit 401 and the receiving unit 402 may be implemented by transceivers. The processing unit 403 may be implemented by a processor.

Fig. 5 is a block diagram of a network device according to an embodiment of the present application. The network device 500 shown in fig. 5 includes: a processor 501, a memory 502, and a transceiver 503.

The various components in network device 500 are coupled together by a bus system 504, where bus system 504 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are labeled as bus system 504 in fig. 5.

The method disclosed in the embodiments of the present application may be applied to the processor 501, or implemented by the processor 501. The processor 501 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 501. The Processor 501 may be a general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in a Random Access Memory (RAM), a flash Memory, a Read-Only Memory (ROM), a programmable ROM, an electrically erasable programmable Memory, a register, or other storage media that are well known in the art. The storage medium is located in the memory 502, and the processor 501 reads the instructions in the memory 502, and completes the steps of the method in combination with the hardware thereof.

Memory 502 may store instructions for performing a method performed by a network device, such as the method shown in fig. 2. The processor 501 may execute the instructions stored in the memory 502 to complete the steps performed by the access node device in the method shown in fig. 2 in combination with other hardware (e.g., the transceiver 503), and the specific working process and beneficial effects may refer to the description of the access node device in the embodiment shown in fig. 2.

Similarly, if the network device 500 is only responsible for sharing traffic messages requesting data link layer traffic, the network device 500 may be a switch. The network device 500 may be a router and a switch if the network device 500 is responsible for sharing traffic messages requesting network layer traffic. It is to be understood that the network device 500 may be a switch if the network device 500 is responsible for sharing service messages requesting a data link layer service, or is responsible for sharing service messages requesting a network side service.

Fig. 6 is a block diagram of a service node provided according to an embodiment of the present application. The service node 600 shown in fig. 6 includes: a processor 601, a memory 602, and a transceiver 603.

The various components in service node 600 are coupled together by a bus system 604, where bus system 604 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are labeled as bus system 604 in fig. 6.

The method disclosed in the embodiments of the present application may be applied to the processor 601, or implemented by the processor 601. The processor 601 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 601. The Processor 601 may be a general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in a Random Access Memory (RAM), a flash Memory, a Read-Only Memory (ROM), a programmable ROM, an electrically erasable programmable Memory, a register, or other storage media that are well known in the art. The storage medium is located in the memory 602, and the processor 601 reads the instructions in the memory 602, and performs the steps of the above method in combination with the hardware thereof.

The memory 602 may store instructions for performing a method performed by a service node as in the method of fig. 2. The processor 601 may execute the instructions stored in the memory 602, and in combination with other hardware (e.g. the transceiver 603), to complete the steps performed by the access node apparatus in the method shown in fig. 2, and specific working procedures and beneficial effects may refer to the description of the access node apparatus in the embodiment shown in fig. 2.

Fig. 7 is a schematic diagram of a system for distributing service messages provided according to an embodiment of the present invention. As shown in fig. 7, system 700 includes a network device 701 and N serving nodes 702, where N is a positive integer greater than or equal to 2.

In some embodiments, the types of traffic that the N serving nodes 702 are capable of handling are the same. For example, the N service nodes are all service nodes that handle data link layer traffic. For another example, the N service nodes are all service nodes providing NAT service.

In other embodiments, the types of traffic that the N service nodes 702 can handle may be different, but at least two of the N service nodes 702 can handle traffic messages requesting the same type of traffic.

For example, the N serving nodes may include at least two serving nodes that handle data link layer traffic and at least two serving nodes that provide NAT services.

As another example, the N service nodes can include at least two service nodes that handle data link layer traffic, at least two service nodes that provide NAT services, and one service node for handling DPI traffic. In this case, if the network device 701 determines that the service message sent by the service originating device needs to request the NAT service, one service node may be selected from the at least two service nodes providing the NAT service with reference to the method shown in fig. 2. If the network device 701 determines that deep packet inspection needs to be performed on the service message sent by the service initiating device, the service message may be directly sent to the service node for processing the DPI service. It is to be understood that the service initiating device may be a user equipment, or may be a service node, and the service node may be a service node for processing data link layer services, or may be a service node for processing network layer services.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application shall be covered by the scope of the present application, and therefore the scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for distributing service messages is applied to a user access network scene, and is characterized in that the method comprises the following steps:

the network equipment receives a first service message sent by first service initiating terminal equipment;

the network device receives service range indication information and first priority indication information sent by each service node in M service nodes, wherein the service range indication information sent by each service node is used for indicating a service range which can be processed by each service node, the first priority indication information sent by each service node is used for indicating the priority of each service node, the service range indication information is carried in a service range type length value TLV of a link layer discovery protocol LLDP message, the first priority indication information is carried in the priority TLV of the LLDP message, and M is a positive integer greater than or equal to 2;

the network equipment determines N candidate service nodes for processing the services related to the user access network and the priority of each candidate service node in the N candidate service nodes according to the service range indication information and the first priority indication information sent by each service node, wherein the candidate service nodes are service nodes capable of processing the first service message, N is a positive integer greater than or equal to 2 and is less than or equal to M, and the N candidate service nodes belong to the M service nodes;

the network equipment determines a candidate service node with the highest priority in the N candidate service nodes as a first target service node for processing the first service message;

and the network equipment sends the first service message to the first target service node.

2. The method of claim 1, wherein the method further comprises: the network device stores the identity information of the first service initiating terminal device, the service type of the first service message and the corresponding relation of the first target service node.

3. The method of claim 2, wherein prior to the network device determining a highest priority one of the N candidate serving nodes to be a first target serving node for processing the first traffic message, the method further comprises: and the network equipment determines that the network equipment does not store the corresponding relation among the identity information of the first service initiating terminal equipment, the service type of the first service message and the first target service node.

4. The method of any of claims 1 to 3, further comprising: the network device receives second priority indication information sent by the first target service node, wherein the second priority indication information sent by the first target service node is used for indicating the priority of the first target service node, and the priority of the first target service node indicated by the second priority indication information sent by the first target service node is lower than the priority of the first target service node indicated by the first priority indication information sent by the first target service node;

the network equipment receives a second service message sent by second service initiating terminal equipment;

and the network equipment sends the second service message to the first target service node under the condition that the identity information of the second service initiating terminal equipment is determined to be the same as the identity information of the first service initiating terminal equipment and the service type of the second service message is determined to be the same as the service type of the first service message.

5. The method of claim 2 or 3, wherein the method further comprises: the network equipment determines that the first target service node does not participate in the sharing of the service message any more;

and the network equipment deletes the identity information of the first service initiating terminal equipment, the service type of the first service message and the corresponding relation of the first target service node, which are stored by the network equipment.

6. The method according to any of claims 1 to 3, wherein the first service originating device is a user equipment or a first service node, wherein the first service node is a service node for handling data link layer traffic or network layer traffic.

7. A method according to any one of claims 1 to 3, wherein the service messages are data link layer service messages or network layer service messages.

8. A method for distributing service messages, the method being applied to a user access network scenario, the method comprising:

a service node sends a Link Layer Discovery Protocol (LLDP) message to a network device, wherein a service range Type Length Value (TLV) of the LLDP message carries service range indication information, a priority TLV of the LLDP message carries priority indication information, the service range indication information is used for indicating a service range related to a service of a user access network which can be processed by the service node, and the priority indication information is used for indicating the priority of the service node, so that the network device determines the priority of the service node according to the service range indication information and the priority indication information;

the service node receives a service message sent by the network equipment;

the service node processes the service message.

9. The method of claim 8, wherein the method further comprises: the service node sends keep-alive information to the network device.

10. A network device, characterized in that the network device comprises:

a receiving unit, configured to receive a first service message sent by a first service originating device;

the receiving unit is further configured to receive service range indication information and first priority indication information sent by each service node of the M service nodes, where the service range indication information sent by each service node is used to indicate a service range that can be processed by each service node, the first priority indication information sent by each service node is used to indicate a priority of each service node, the service range indication information is carried in a service range type length value TLV of a link layer discovery protocol LLDP packet, the first priority indication information is carried in a priority TLV of the LLDP packet, and M is a positive integer greater than or equal to 2;

a processing unit, configured to determine, according to the service range indication information and the first priority indication information sent by each service node, N candidate service nodes for processing a service related to a user access network and a priority of each candidate service node in the N candidate service nodes, where the candidate service nodes are service nodes capable of processing the first service message, N is a positive integer greater than or equal to 2 and is less than or equal to M, and the N candidate service nodes belong to the M service nodes;

the processing unit is further configured to determine a candidate service node with a highest priority in the N candidate service nodes as a first target service node for processing the first service message;

a sending unit, configured to send the first service message to the first target service node.

11. The network device of claim 10, wherein the processing unit stores the identity information of the first service originating device, the service type of the first service message, and the correspondence of the first target service node.

12. The network device of claim 11, wherein the processing unit is further configured to determine that the processing unit does not store the identity information of the first service originating device, the service type of the first service message, and the corresponding relationship of the first target service node before determining that a candidate service node with a highest priority among the N candidate service nodes is the first target service node for processing the first service message.

13. The network device according to any one of claims 10 to 12, wherein the receiving unit is further configured to receive second priority indication information sent by the first target serving node, where the second priority indication information sent by the first target serving node is used to indicate a priority of the first target serving node, and the priority of the first target serving node indicated by the second priority indication information sent by the first target serving node is lower than the priority of the first target serving node indicated by the first priority indication information sent by the first target serving node;

the receiving unit is further configured to receive a second service message sent by a second service originating device;

the processing unit is further configured to determine that the identity information of the second service originating device is the same as the identity information of the first service originating device and that the service type of the second service message is the same as the service type of the first service message;

the sending unit is further configured to send the second service message to the first target service node when the processing unit determines that the identity information of the second service originating device is the same as the identity information of the first service originating device and the service type of the second service message is the same as the service type of the first service message.

14. The network device of claim 11 or 12, wherein the processing unit is further configured to determine that the first target serving node is no longer involved in traffic message sharing;

the processing unit is further configured to delete the identity information of the first service originating device, the service type of the first service message, and the correspondence between the first target service node and the service type of the first service message, which are stored in the processing unit.

15. A serving node, characterized in that the serving node comprises:

a sending unit, configured to send a link layer discovery protocol LLDP packet to a network device, where a service range type length value TLV of the LLDP packet carries service range indication information, a priority TLV of the LLDP packet carries priority indication information, the service range indication information is used to indicate a service range related to a service of a user access network that can be processed by a service node, and the priority indication information is used to indicate a priority of the service node, so that the network device determines the priority of the service node according to the service range indication information and the priority indication information;

a receiving unit, configured to receive a service message sent by the network device;

and the processing unit is used for processing the service message.

16. The serving node of claim 15, wherein the sending unit is further configured to send keep-alive information to the network device.

17. A system for distributing service messages, characterized in that the system comprises a network device according to any of claims 10 to 14 and at least two service nodes according to claim 15 or claim 16.