WO2015180560A1 - Service router packet processing method and service node - Google Patents

Abstract

Disclosed is a service router (SR) packet processing method, comprising: a socket unit in a service node (SN) creating a first socket, the first socket being used to listen for a first packet, and the first packet comprising SR information and a packet to be processed; storing the correspondence between the packet to be processed and a second socket, the second socket corresponding to the SR information; receiving a packet acquisition request from an application (APP) unit in the SN, and determining, according to the packet acquisition request and the correspondence, that the packet to be processed is the requested packet; and transmitting the packet to be processed to the APP unit by transmitting to the APP unit a response to the packet acquisition request. The SR packet processing method of the present invention prevents related information of the SR from being disclosed to the APP unit in the SN, and improves the security of the SR.

Description

Method and service node for processing service routing message

This application claims the priority of the Chinese Patent Application filed on May 30, 2014, the Chinese Patent Office, the application number is CN 201410240822.7, and the invention name is “a method and service node for processing service routing messages”. The content is incorporated herein by reference.

Technical field

The present invention relates to the field of data processing technologies, and in particular, to a method and a service node for processing a service routing message.

Background technique

The service chain (Service Chaining) technology is a forwarding technology that guides the order of network service packets through multiple service nodes (English is Service Node, English abbreviated as SN), where service packets are between nodes. The forwarding behavior is called a service route.

At the same time, when the service packet is forwarded between the SNs, the original packet is encapsulated in the service routing header. The service routing header is used to guide the forwarding of the service packet and also carries the element in the encapsulation information. The data (metadata in English), the metadata can be generated by the service router (English Service Router, abbreviated as SR) or generated by the SN itself, and can be modified.

The SN entry message standards can be generally divided into two categories. One type is: when the message arriving at the SN is the original message, the SN can directly receive, process, and send. The other type is that the packet arriving at the SN is a service routing packet with the service routing header information and the metadata. In this case, the SN needs to identify and strip the service routing header when receiving the service routing packet. After the packet is processed, the appropriate service routing header can be encapsulated for the original packet and sent to the SR.

In the prior art solution, the application in the SN (Application in English is APP) directly obtains service routing packets through the network driver layer, strips the service routing headers, identifies the original packets, and processes them. After the processing is completed, the APP The layer encapsulates the appropriate service routing headers for the packets and sends them through the network driver layer.

The inventors of the present invention have found that all related information of service routing in the prior art is exposed to the APP. Layer, there are security risks.

Summary of the invention

The embodiment of the present invention provides a method for processing a service routing message, which may be processed by a socket unit in the service node SN for service routing information, and the application unit in the SN does not need to learn the service. The information related to the route is processed only to prevent the related information of the service route from being exposed to the application unit in the SN, thereby improving the security of the service route. The embodiment of the invention also provides a corresponding service node.

A first aspect of the present invention provides a method for processing a service routing message, including:

The socket unit in the service node SN creates a first socket, and the first socket is used to listen to the first packet, where the first packet is a service routing report belonging to the first service routing type. The first packet includes the service routing information and the to-be-processed packet.

Determining, by the socket unit, that the SN receives the first packet according to the first socket;

The socket unit stores a correspondence between the to-be-processed message and the second socket, where the second socket corresponds to the service routing information;

The socket unit receives a message acquisition request from an application unit in the SN, where the message acquisition request is used to request the to-be-processed message corresponding to the second socket;

Determining, by the socket unit, the to-be-processed message as the requested message according to the packet obtaining request and the corresponding relationship;

The socket unit sends the to-be-processed message to the application unit by sending a response to the message acquisition request to the application unit.

In conjunction with the first aspect, in a first possible implementation, the method further includes:

Receiving, by the application unit, a processed message corresponding to the second socket, where the processed message is processed by the application unit to process the to-be-processed message Obtained

The socket unit determines the service routing information according to the second socket corresponding to the processed message;

Sending a second packet to the service router SR, where the second packet is a service routing packet that includes the processed packet, and the service routing information of the second packet includes the service routing information.

With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner, the socket unit saves a correspondence between the to-be-processed message and the second socket Specifically include:

When the socket unit receives the first packet, if the second socket is not saved in the socket unit, the second socket is created, and the The processing message is added to the message queue corresponding to the second socket.

With reference to the first aspect or the first possible implementation manner of the first aspect, in a third possible implementation, the socket unit saves a correspondence between the to-be-processed message and the second socket Specifically include:

When the socket unit receives the first packet, if the second socket is saved in the socket unit, the to-be-processed message is added to the second The queue corresponding to the socket in the message.

With reference to the first aspect, any one of the first to third possible implementation manners of the first aspect, in a fourth possible implementation, the socket unit is from an application unit in the SN Before receiving the packet obtaining request including the second socket, the method further includes:

The socket unit sends the second socket to the application unit.

With reference to the first aspect, any one of the first to fourth possible implementation manners of the first aspect, in a fifth possible implementation, the socket unit is configured to send to the application unit And sending, by the application unit, the to-be-processed message, the method includes:

The socket unit sends a response to the message acquisition request to the application unit, where the response carries a storage address of the to-be-processed message;

The application unit acquires the to-be-processed message according to the storage address.

With reference to the first aspect, any one of the first to fifth possible implementation manners of the first aspect, in a sixth possible implementation, the socket unit is sent by using the application unit And sending, to the application unit, the to-be-processed message, in the manner of the response of the packet obtaining request, including:

The socket unit sends a response to the message acquisition request to the application unit, where the response carries the to-be-processed message.

A second aspect of the present invention provides a service node, including: a socket unit and an application unit;

The socket unit includes:

Creating a sub-unit, configured to create a first socket, where the first packet is used to listen to the first packet, where the first packet is a service routing packet belonging to the first service routing type. The first packet includes service routing information and pending packets;

Determining a subunit, configured to determine, according to the first socket created by the creating subunit, that the SN receives the first packet;

a saving subunit, configured to save a correspondence between the to-be-processed message and the second socket, where the second socket corresponds to the service routing information;

a receiving subunit, configured to receive a message obtaining request from an application unit in the SN, where the message obtaining request is used to request the to-be-processed message corresponding to the second socket;

The determining subunit is further configured to determine, according to the packet obtaining request that is received by the receiving subunit and the corresponding relationship that is saved by the saving subunit, that the to-be-processed packet is the requested packet;

And a sending subunit, configured to send the to-be-processed message determined by the determining subunit to the application unit by sending a response to the packet request to the application unit.

In combination with the second aspect, in a first possible implementation manner,

The receiving subunit is further configured to receive, from the application unit, a processed message corresponding to the second socket, where the processed message is sent by the application unit to the to-be-processed message Obtained by processing the text;

The determining subunit is further configured to determine the service routing information according to the second socket corresponding to the processed message received by the receiving subunit;

The sending subunit is further configured to send a second packet to the service router SR, where the second packet is a service routing packet that includes the processed packet, and the service routing information of the second packet includes Determining the service routing information determined by the subunit.

With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner,

The creating subunit is further configured to: when the receiving subunit receives the first packet, if the second socket is not saved in the saving subunit, create the second socket word;

The saving subunit is specifically configured to add the to-be-processed message to a message queue corresponding to the second socket created by the creating subunit.

With reference to the second aspect or the first possible implementation manner of the second aspect, in a third possible implementation manner,

The saving subunit is configured to: when the receiving subunit receives the first packet, if the second socket is saved in the saving subunit, the to-be-processed packet is sent Add to the message queue corresponding to the second socket.

With reference to the second aspect, any one of the first to third possible implementation manners of the second aspect, in a fourth possible implementation manner,

The sending subunit is further configured to send the second socket to the application unit before receiving a message obtaining request including the second socket from an application unit in the SN.

With reference to the second aspect, any one of the first to fourth possible implementation manners of the second aspect, in a fifth possible implementation manner,

The sending subunit is configured to send a response to the packet obtaining request to the application unit, where the response carries a storage address of the to-be-processed packet;

The application unit is configured to acquire the to-be-processed message according to the storage address.

With reference to the second aspect, any one of the first to fifth possible implementation manners of the second aspect, in a sixth possible implementation manner,

The sending subunit is configured to send a response to the packet obtaining request to the application unit, where the response carries the to-be-processed message.

In the embodiment of the present invention, the socket unit in the service node SN creates a first socket, and the first socket is used to listen to the first packet, where the first packet belongs to the first service routing type. The service routing message, the first packet includes service routing information and a to-be-processed message; the socket unit determines, according to the first socket, that the SN receives the first packet; The socket unit saves a correspondence between the to-be-processed message and the second socket, where the second socket corresponds to the service routing information; the socket unit is from the SN The application unit receives a message acquisition request, and the message acquisition request is used to request the to-be-processed message corresponding to the second socket; the socket unit acquires a request according to the message and Determining, by the correspondence, the to-be-processed message is a requested message; the socket unit sends the response to the message acquisition request to the application unit to the application unit Send the to-be-processed message. The method for processing the service routing packet provided by the embodiment of the present invention may be performed by the socket unit pair in the service node SN, as compared with the information about the service routing in the prior art. The service routing message is processed by the service routing information, and the application unit in the SN does not need to know the relevant information of the service routing, and only processes the service, thereby preventing the related information of the service routing from being exposed to the application unit in the SN, thereby improving Security of service routing.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. Other drawings can also be obtained from those skilled in the art based on these drawings without paying any creative effort.

1 is a schematic diagram of an embodiment of a method for processing a service routing message according to an embodiment of the present invention;

2 is a schematic diagram of an embodiment of a method for processing a service routing message according to an embodiment of the present invention;

3 is a schematic diagram of an embodiment of a method for processing a service routing message according to an embodiment of the present invention;

4 is a schematic diagram of a service node in an embodiment of the present invention;

FIG. 5 is a schematic diagram of a service node in an embodiment of the present invention.

detailed description

The embodiment of the present invention provides a method for processing a service routing message, which may be processed by a socket unit in the service node SN for service routing information, and the application unit in the SN does not know the service route. The related information is processed only to prevent the related information of the service route from being exposed to the application unit in the SN, thereby improving the security of the service route. The embodiment of the invention also provides a corresponding service node. The details are described below separately.

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

Referring to FIG. 1, an embodiment of a method for processing a service routing packet according to an embodiment of the present invention includes:

The embodiment of the present invention provides a new first socket (English socket) protocol family, which is used to assist the application layer to complete partial processing of service routing messages at the driver layer, and can route the new service to the socket protocol family. Named AF_SR, of course, can also be named with other names.

When the service router SR transmits the service routing message between the service node and the service node SN, the embodiment of the present invention introduces a new service routing socket protocol stack in the SN, and the application program interface provided by the protocol stack to the APP (English name is Application) The Programming Interface (abbreviated as API) collection is defined as the SR socket API.

The processing module of the API is a service router socket module (SR socket module in English), hereinafter referred to as SRM.

As shown in FIG. 1, the service node SN includes two parts, one part is a socket unit, one part is an application unit, and the socket unit includes two parts: an SR socket API and an SRM.

Referring to FIG. 2, an implementation of a method for processing a service routing message according to an embodiment of the present invention is provided. Examples include:

S100. The socket unit 301 in the service node SN30 creates a first socket.

The first socket is configured to listen to the first packet, where the first packet is a service routing packet that belongs to the first service routing type, and the first packet includes the service routing information and the to-be-processed packet. Text.

The specific process of the socket unit 301 to create the first socket may include the following.

The application unit 302 sends a first socket creation instruction to the socket unit 301. This step can be understood in conjunction with FIG. 1 as: the application unit calls the service routing socket API in the SR socket API.

The socket unit 301 creates the first socket according to the creation instruction of the first socket.

After the socket unit 301 creates the first socket, it can start receiving the first message belonging to the first service route type, and the instruction for receiving the first message can be invoked by the application unit 302 through the first socket. The instruction is triggered to the socket unit 301. After receiving the call instruction of the first socket, the socket unit 301 can learn that the first message of the first service route type can be received.

For example, the service routing type in the embodiment of the present invention may be: a transmission type and/or a transmission mode of the service routing bearer layer.

Generally, an application unit has the processing capability of the to-be-processed packet in the service routing packet belonging to a service routing type, and of course, it can also have the to-be-processed packet in the service routing packet belonging to multiple service routing types. Processing power, there can be multiple application units in one SN.

The specific process of the socket unit 301 to create the first socket may further include: the creation process is not initiated by the application unit, but the socket unit actively creates the first socket according to the first service route type. word. For example, the socket unit may actively create the first socket after the SN where it is started, or may actively create the first socket after reaching a predetermined time.

In addition, the socket unit 301 can also create the first socket according to an instruction of a controller in the network.

The process of creating the first socket may include an operation of creating a socket, and may continue to include an operation of configuring the created socket.

S102. The service router SR40 sends the first packet to the service node 30.

S105. The socket unit 301 determines, according to the first socket, that the SN30 receives the first packet.

The first socket corresponds to the first service routing type, and the first packet is a service routing packet of the first service routing type, and the service routing type of the packet received by the socket unit 301 is the first service. When the route type is used, the packet can be determined to be the first packet.

Optionally, the socket unit 301 starts to receive the first packet of the first service route type from the SR after the first service route type is learned.

This step can be understood by referring to FIG. 1 as follows: The SRM receives the first packet from the SR according to the first service route type.

S110. The socket unit determines, when the first packet is received, whether the second socket is saved in the socket unit. If otherwise, step S115 is performed, and if yes, step S120 is performed.

The second socket in the embodiment of the present invention is attached to the first socket, the first socket corresponds to the first service routing type, and the second socket corresponds to a session of the first service routing type. There may be multiple sessions belonging to the first service route type.

In the embodiment of the present invention, after receiving the first packet, the socket unit may parse the first packet and separate the service routing information and the to-be-processed packet in the first packet. The process of separation may not be performed.

The service routing information is carried in the service routing header of the first packet. The to-be-processed packet may include the original packet without any routing information, and may also include the original packet and metadata without any routing information.

This step can be understood as a process performed by SRM with reference to FIG.

S115. If the second socket is not saved in the socket unit, create the second socket, and add the to-be-processed message to the second socket. In the message queue.

The correspondence between the service routing information and the second socket is unique, and each service routing information uniquely corresponds to a second socket. A service routing information can correspond to multiple pending packets, and a queue of pending packets can be established for a second socket, and the same service routing letter is used. The pending message in the message is stored in the queue.

You can refer to the service route mapping table provided in Table 1 to understand the correspondence between the second socket, service route type, service routing information, and pending message queue.

Table 1: Service Route Mapping Table

Second socket	Service routing information	Pending message queue
			1	Service routing information 1	Q1
2	Service routing information 2	Q2
			3	Service routing information 3	Q3
...	...	...
			N	Service routing information N	QN

It can be seen from Table 1 that each second socket corresponds to one service routing information, and the service routing information belongs to the first service routing type in S100. Each second socket identifier also corresponds to a queue of all pending packets under the service routing information.

When the socket unit determines that the service routing information in the first packet does not exist in the socket unit, it can be understood that the entry of the service routing information does not exist in the table 1, and the Table 1 lists the entries corresponding to the service routing information.

This step can be understood as a process performed by SRM with reference to FIG.

Table 1 can also include the service route type. After adding the service route type, refer to Table 2 for understanding.

Table 2: Service Route Mapping Table

Second socket	Route type	Routing information	Message queue
				1	Type1	Routing information 1	Q1
2	Type2	Routing information 2	Q2
				3	Type3	Routing information 3	Q3
...	...	...	...
				N	TypeN	Routing information N	QN

S120. When receiving the first packet, the socket unit adds the to-be-processed message to the same if the second socket is saved in the socket unit. The packet queue corresponding to the second socket.

When the service routing information exists in the socket unit, it can be understood that the entry of the service routing information already exists in the table 1 and does not need to be re-established, and only the to-be-processed message needs to be stored in the The queue of pending packets corresponding to the service routing information. For example, when the correspondence between the second socket 1 and the message queue Q1 is saved in the table 1, the to-be-processed message can be added to the Q1 queue.

This step can be understood as a process performed by SRM with reference to FIG.

S125. The socket unit 301 sends the second socket to the application unit 302.

This step may be: the socket unit 301 receives the second socket acquisition instruction sent by the application unit 302, and then the socket unit 301 sends the instruction to the application unit according to the second socket acquisition instruction. 302 transmits the second socket.

For example, when the application unit 302 needs to process the to-be-processed message, it first sends a second socket acquisition instruction to the socket unit.

This step, in conjunction with Figure 1, can be understood as: the application unit calls the second socket creation interface in the SR socket API.

After receiving the second socket acquisition instruction, the socket unit 301 generally sends the second socket identifier to the application unit 302 in the order in which the second socket is generated.

Of course, other preset strategies may also be used, for example, sending the second socket first is odd, and then sending the second socket is even.

This step can be understood as a process performed by SRM with reference to FIG.

The sending, by the socket unit, the second socket to the application unit may further include: after the second socket is generated, the socket unit 301 does not receive the second socket. In the case of an instruction, the second socket is actively sent to the application unit 302.

S130. The socket unit 301 receives a message from the application unit 302 in the SN. And taking the request, the message obtaining request is used to request the to-be-processed message corresponding to the second socket.

The packet obtaining request in the embodiment of the present invention may directly carry the packet obtaining request, or may not carry the second socket, but the socket unit 301 corresponds to the second socket. The dedicated interface receives the message acquisition request. In the above two manners, the socket unit 301 can determine the relationship between the request and the second socket, that is, to request the to-be-processed message corresponding to the second socket.

S135. The socket unit 301 determines, according to the packet obtaining request and the correspondence, that the to-be-processed packet is the requested packet.

Determining, by the socket unit, the second socket according to the packet obtaining request, and then according to the second socket, the second socket, and the to-be-processed message. The corresponding relationship may determine a to-be-processed message corresponding to the second socket. The corresponding relationship between the second socket and the to-be-processed message may also be expressed as the second socket and the foregoing, because the to-be-processed message is saved in the message queue. Correspondence between packet queue identifiers. Correspondingly, the to-be-processed message may be determined according to the correspondence between the second socket and the second socket and the message queue identifier. For example, according to the second socket 1, it can be determined that the message queue is the pending message in Q1 as the requested message.

S140. The socket unit sends the to-be-processed message to the application unit by sending a response to the message acquiring request to the application unit.

A solution of step S140 may be:

The socket unit sends a response to the message acquisition request to the application unit, where the response carries a storage address of the to-be-processed message; the application unit acquires according to the storage address. The to-be-processed message. In this way, the socket unit and the application unit do not need to directly transmit the data to be processed, and the response speed to the request can be improved.

Another solution of step S140 may be:

The socket unit sends a response to the message acquisition request to the application unit, where the response carries the to-be-processed message. In this scheme, the socket unit can be targeted The response to the request directly carries the to-be-processed message, and the application unit is not required to search for the to-be-processed message.

Because there can be a large number of pending packets in a packet queue, when sending a response to the packet request, the packet may be sent to the queue first according to the order in which the packets are to be processed. The response of the pending message until the queue pending message is sent.

This step can be understood as a process performed by SRM with reference to FIG.

S145. The application unit 302 processes the to-be-processed message into a processed message.

After the application unit obtains the to-be-processed message, the to-be-processed message is processed into the processed message.

S150. The socket unit 301 receives, from the application unit 302, a processed message corresponding to the second socket.

The processed message is obtained by the application unit 302 processing the to-be-processed message.

The solution that the socket unit 301 receives the processed message corresponding to the second socket from the application unit 302 may be:

The socket unit 301 receives, from the application unit 302, a message or a message including the storage address of the processed message and the second socket, and may also receive the processed text body and the second socket. Word message or message. Since the processed message and the second socket are both obtained by the socket unit 301, the socket unit 301 can determine that the processed message and the second socket are corresponding. .

Another scheme for the socket unit 301 to receive the processed message corresponding to the second socket from the application unit 302 may also be: the socket unit 301 from the application unit 302 a second socket-specific interface between the storage address of the processed message or the processed message, and determining, according to the dedicated interface of the second socket, that the processed message is the same as the first The two sets of connectors correspond to each other.

S155. The socket unit 301 determines the service routing information according to the second socket corresponding to the processed message.

As shown in Table 1, when the second socket is determined, the corresponding service routing information can be determined. If the second socket is 1, the corresponding service routing information may be determined as the service routing information 1.

S160. The socket unit sends a second packet to the service router SR, where the second packet is a service routing packet that includes the processed packet, and the service routing information of the second packet includes the service. Routing information.

The socket unit 301 may encapsulate the processed message by using the service routing information determined in step S155, or may directly send the processed message and the service routing information to the SR without encapsulation, but The processed message and the service routing information are separately identified, so that the SR 40 can separately identify the processed message and the service routing information.

It should be noted that steps S130 to S140 have no sequence with steps S150 to S160. Steps S130 to S140 and steps S150 to S160 may be performed simultaneously for different service routing messages, or steps S150 to S160 may be performed first.

S170. The socket unit 301 receives the second socket close instruction sent by the application unit 302.

The second socket closing instruction may carry the second socket, or may receive the second socket closing instruction through the dedicated interface of the second socket.

S175. The socket unit 301 deletes the correspondence between the second socket, the service routing information, and the packet queue in the first service routing type according to the second socket closing instruction.

After a session ends, if the application unit instructs to close the session, the entries related to the session in Table 1 or Table 2 can be deleted.

S180. The socket unit 301 receives the first socket close instruction sent by the application unit 302.

The first socket close command may carry the first service route type, or may not carry the first service route type, but receive the second socket by using a dedicated interface of the first socket. instruction.

S185. The corresponding relationship between the second socket, the service routing information, and the packet queue in the first service routing type is deleted according to the first socket closing instruction.

Delete Table 1 or Table if the application unit indicates to close the service routing socket that has been created The entry related to the first service route type in 2.

The service node SN30 and the service router SR in this embodiment may be two physical devices that are independent of each other, or two virtual devices that are implemented in the same physical device or physical system. In addition, as technology evolves, the names of service nodes and service routers may change. Therefore, as long as a physical or virtual device performs the operations performed by the service node SN30 in this embodiment, even if the name of the physical or virtual device is not a "service node", it should be understood as The service node SN30 in the embodiment of the present invention. The determination criterion of the service router is the same as the standard of the service node 30, that is, as long as one device performs the operation performed by the service router SR40 in this embodiment, the device should be understood as a service router. Whether a target device can be understood as the device in this embodiment is independent of the name of the target device in the industry, and is related to the operations and functions performed by the target device.

The method for processing the service routing packet provided by the embodiment of the present invention may be performed by the socket unit pair in the service node SN, as compared with the information about the service routing in the prior art. The service routing message is processed by the service routing information, and the application unit in the SN does not need to know the relevant information of the service routing, and only processes the service, thereby preventing the related information of the service routing from being exposed to the application unit in the SN, thereby improving Security of service routing.

Referring to FIG. 3, another embodiment of a method for processing a service routing packet according to an embodiment of the present invention includes:

201. The socket unit in the service node SN creates a first socket, where the first socket is used to listen to the first packet, and the first packet is a service belonging to the first service routing type. The routing packet includes the service routing information and the to-be-processed packet.

202. The socket unit determines, according to the first socket, that the SN receives the first packet.

203. The socket unit saves a correspondence between the to-be-processed message and a second socket, where the second socket corresponds to the service routing information.

204. The socket unit receives a message acquisition request from an application unit in the SN, where the message acquisition request is used to request the to-be-processed message corresponding to the second socket.

205. The socket unit determines, according to the packet obtaining request and the correspondence, that the to-be-processed packet is the requested packet.

206. The socket unit sends the to-be-processed message to the application unit by sending a response to the message acquisition request to the application unit.

In the embodiment of the present invention, the socket unit in the service node SN creates a first socket, and the first socket is used to listen to the first packet, where the first packet belongs to the first service routing type. The service routing message, the first packet includes service routing information and a to-be-processed message; the socket unit determines, according to the first socket, that the SN receives the first packet; The socket unit saves a correspondence between the to-be-processed message and the second socket, where the second socket corresponds to the service routing information; the socket unit is from the SN The application unit receives a message acquisition request, and the message acquisition request is used to request the to-be-processed message corresponding to the second socket; the socket unit acquires a request according to the message and Determining, by the correspondence, the to-be-processed message is a requested message; the socket unit sends the response to the message acquisition request to the application unit to the application unit Send the to-be-processed message. The method for processing the service routing packet provided by the embodiment of the present invention may be performed by the socket unit pair in the service node SN, as compared with the information about the service routing in the prior art. The service routing message is processed by the service routing information, and the application unit in the SN does not need to know the relevant information of the service routing, and only processes the service, thereby preventing the related information of the service routing from being exposed to the application unit in the SN, thereby improving Security of service routing.

Optionally, in another embodiment of the method for processing a service routing packet according to the embodiment of the present disclosure, the method may further include:

Receiving, by the application unit, a processed message corresponding to the second socket, where the processed message is processed by the application unit to process the to-be-processed message Obtained

The socket unit determines the service routing information according to the second socket corresponding to the processed message;

Sending a second packet to the service router SR, where the second packet is the packet that includes the processed packet The service routing message, where the service routing information of the second packet includes the service routing information.

Optionally, in another embodiment of the packet processing method provided by the embodiment of the present invention, the socket unit saves the to-be-processed on the basis of the foregoing embodiment or the optional embodiment of FIG. The correspondence between the packet and the second socket may specifically include:

When the socket unit receives the first packet, if the second socket is not saved in the socket unit, the second socket is created, and the The processing message is added to the message queue corresponding to the second socket.

Optionally, in another embodiment of the packet processing method provided by the embodiment of the present invention, the socket unit saves the to-be-processed on the basis of the foregoing embodiment or the optional embodiment of FIG. The correspondence between the packet and the second socket may specifically include:

When the socket unit receives the first packet, if the second socket is saved in the socket unit, the to-be-processed message is added to the second The queue corresponding to the socket in the message.

Optionally, in another embodiment of the packet processing method provided by the embodiment of the present invention, the socket unit is from the SN, according to the foregoing embodiment or the optional embodiment of FIG. The method may further include: before the application unit receives the message acquisition request including the second socket, the method may further include:

The socket unit sends the second socket to the application unit.

Optionally, in another embodiment of the method for processing a packet according to the embodiment of the present invention, the socket unit is configured to be applied to the application, according to the foregoing embodiment or the optional embodiment. And sending, by the program unit, the to-be-processed message to the application unit, where the program unit sends the response to the message requesting request, which may include:

The socket unit sends a response to the message acquisition request to the application unit, where the response carries a storage address of the to-be-processed message;

The application unit acquires the to-be-processed message according to the storage address.

Optionally, in another embodiment of the method for processing a packet according to the embodiment of the present invention, the socket unit is configured to be applied to the application, according to the foregoing embodiment or the optional embodiment. And sending, by the program unit, the to-be-processed message to the application unit, where the program unit sends the response to the message requesting request, which may include:

The socket unit sends a response to the message acquisition request to the application unit, where the response carries the to-be-processed message.

The method for processing the service routing message described in the embodiment of the present invention can be understood by referring to the description in the parts of FIG. 1 and FIG. 2, and details are not described in the embodiment of the present invention.

FIG. 4 is a schematic diagram of a service node SN30 according to an embodiment of the present invention. The service node SN30 shown in FIG. 4 is the service node SN30 shown in FIG. 1 and FIG. 2, and may also be the service node in the embodiment corresponding to FIG. 3. Individual units and subunits in the schematic diagram can be understood as logical units that are divided according to different logical functions. The service node SN30 includes a socket unit 301 and an application unit 302.

The socket unit 301 includes:

The sub-unit 3011 is configured to create a first socket, where the first packet is used to monitor the first packet, and the first packet is a service routing packet belonging to the first service routing type. The first packet includes the service routing information and the to-be-processed packet, and the first packet may be sent by the service router SR40 to the service node SN30, and the service node SN30 and the service router SN40 belong to the same system;

a determining subunit 3012, configured to determine, according to the first socket created by the creating subunit 3011, that the SN receives the first packet;

a saving subunit 3013, configured to save a correspondence between the to-be-processed message and the second socket, where the second socket corresponds to the service routing information;

The receiving subunit 3014 is configured to receive a message obtaining request from the application unit 302 in the SN, where the message obtaining request is used to request the to-be-processed message corresponding to the second socket;

The determining subunit 3012 is further configured to determine, according to the packet obtaining request received by the receiving subunit 3014 and the corresponding relationship saved by the saving subunit, that the to-be-processed packet is the requested packet. ;

a sending subunit 3015, configured to send, by using the application unit 302, the message And obtaining, by the application unit, the to-be-processed message determined by the determining subunit.

The above can be understood as the first part of the SN 30 shown in FIG.

According to the above, the information about the service routing in the prior art is all exposed to the APP layer, and the service node SN can provide the service routing information of the service routing message by the socket unit. The processing unit of the SN does not need to know the information about the service route, and only processes the service, so as to prevent the related information of the service route from being exposed to the application unit in the SN, thereby improving the security of the service route.

The embodiment may further include a first alternative, the first alternative comprising the first part of the content of the SN 30. In addition, in a first alternative, the receiving subunit 3014 is further configured to receive, from the application unit 302, a processed message corresponding to the second socket, where the processed message is The application unit is configured to process the to-be-processed message; the determining sub-unit 3012 is further configured to use the second corresponding to the processed message received by the receiving sub-unit 3014 a socket, the service routing information is determined; the sending sub-unit 3015 is further configured to send a second packet to the service router SR, where the second packet is a service routing packet that includes the processed packet, The service routing information of the second packet includes the service routing information determined by the determining subunit 3012.

This embodiment may further include a second alternative, the second alternative comprising the first part of the content of the SN 30 or the first alternative. In addition, in the second implementation, the creating subunit 3011 is further configured to: when the receiving subunit 3014 receives the first packet, if the saving subunit 3013 does not save the second a socket, the second socket is created; the saving sub-unit 3013 is specifically configured to add the to-be-processed message to the second socket created by the creating sub-unit 3011. In the message queue.

The embodiment may further include a third optional solution, where the third optional solution includes the first part of the content of the SN 30, the first option, or the second option. In addition, in a third alternative, the saving subunit 3013 is specifically configured to: when the receiving subunit 3014 receives the first packet, if the saving subunit 3013 holds the first Two sockets, then Adding the to-be-processed message to a message queue corresponding to the second socket.

The embodiment may further include a fourth optional solution, where the fourth optional solution includes the first part content of the SN 30, the first optional solution, the second optional solution, or the third optional Program. In addition, in a fourth implementation, the sending subunit 3015 is further configured to: before receiving, by the application unit 302 in the SN, the packet obtaining request including the second socket, to the application The unit transmits the second socket.

The embodiment may further include a fifth optional solution, where the fifth optional solution includes the first part content of the SN 30, the first optional solution, the second optional solution, and the third optional Scheme or the fourth alternative. In addition, in a fifth alternative, the sending sub-unit 3015 is configured to send, to the application unit, a response to the message acquiring request, where the response carries a storage address of the to-be-processed message; The application unit 302 is configured to acquire the to-be-processed message according to the storage address.

The sending subunit 3015 is configured to send a response to the packet acquiring request to the application unit 302, where the response carries the to-be-processed, based on the foregoing part of the content of the SN 30 or any optional solution. Message.

The service node described in the embodiment of the present invention can be understood by referring to the description in the parts of FIG. 1 and FIG. 2, and details are not described in the embodiment of the present invention.

It should be noted that the service node 30 shown in FIG. 4 can implement all the operations and functions of the service node 30 shown in FIG. 1 and FIG. 2 and the service node in the embodiment corresponding to FIG. 3. Since FIG. 4 embodies a service node from the perspective of logical functions, all of the operations and functions can be implemented by the respective units and sub-units shown in FIG. As to which unit and sub-unit are implemented by the whole operation and function respectively, this is only a logical division, that is, the service node 30 is divided into operations or added to a logical unit in FIG. 1, FIG. 2 or FIG. The method of division is very flexible. Any of the divisions should be considered as part of this embodiment.

FIG. 5 is a schematic structural diagram of the service node 30. The service node 30 can include an input device 310, an output device 320, a processor 330, and a memory 340. The service node 30 shown in FIG. 5 and the service node 30 shown in FIG. 4 may be the same service node, but FIG. 4 is embodied from the perspective of logical functions. This service node, and Figure 5 shows this service node from a physical implementation perspective.

Memory 340 can include read only memory and/or random access memory and provides instructions and data to processor 330. A portion of the memory 340 may also include non-volatile random access memory (NVRAM).

The memory 340 stores the following elements, executable modules or data structures, or a subset thereof, or an extended set thereof:

Operation instructions: include various operation instructions for implementing various operations.

Operating system: Includes a variety of system programs for implementing various basic services and handling hardware-based tasks.

In the embodiment of the present invention, the processor 330 performs the following operations by calling an operation instruction stored in the memory 340, which can be stored in the operating system:

Creating a first socket, where the first packet is used to monitor the first packet, and the first packet is a service routing packet belonging to the first service routing type, where the first packet includes Service routing information and pending messages;

Determining, according to the first socket, that the SN receives the first packet;

Saving a correspondence between the to-be-processed message and the second socket by using a memory 340, where the second socket corresponds to the service routing information;

Receiving, by the input device 310, a message acquisition request from an application unit in the SN, where the message acquisition request is used to request the to-be-processed message corresponding to the second socket;

Determining, by the socket unit, the to-be-processed message as the requested message according to the packet obtaining request and the corresponding relationship;

Transmitting the to-be-processed message to the application unit by the output device 320 transmitting a response to the message acquisition request to the application unit.

The socket unit in the service node SN provides the service routing information processing on the service routing packet, and the application unit in the SN does not need to know the related information of the service routing, and only processes the service, thereby avoiding The information about the service route is exposed to the application unit in the SN, which improves the security of the service route.

The processor 330 controls the operation of the service node SN30, which may also be referred to as a CPU (Central Processing Unit). Memory 340 can include read only memory and random access memory and provides instructions and data to processor 330. A portion of the memory 340 may also include non-volatile random access memory (NVRAM). In a specific application, the components of the service node SN30 are coupled together by a bus system 350. The bus system 350 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 350 in the figure.

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 330 or implemented by the processor 330. Processor 330 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 330 or an instruction in a form of software. The processor 330 described above 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, a discrete gate or transistor logic device, or discrete hardware. Component. The methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in memory 340, and processor 330 reads the information in memory 340 and, in conjunction with its hardware, performs the steps of the above method.

Optionally, the input device 310 is further configured to receive, from the application unit, a processed message corresponding to the second socket, where the processed message is configured by the application unit The processed message is processed;

The processor 330 is further configured to determine the service routing information according to the second socket corresponding to the processed message;

The output device 320 is further configured to send a second packet to the service router SR, where the second packet is a service routing packet that includes the processed packet, and the service routing information of the second packet includes The service routing information.

Optionally, the processor is specifically configured to: when the socket unit receives the first packet, if the second socket is not saved in the socket unit, create a Said second socket;

The memory 340 is specifically configured to add the to-be-processed message to a message queue corresponding to the second socket.

Optionally, the memory 340 is specifically configured to: when the socket unit receives the first packet, if the second socket is saved in the socket unit, The pending processing message is added to the message queue corresponding to the second socket.

Optionally, the output device 320 is configured to send the second socket to the application unit.

Optionally, the output device 320 is specifically configured to send, by the socket unit, a response to the message acquiring request to the application unit, where the response carries a storage address of the to-be-processed message;

The application unit acquires the to-be-processed message according to the storage address.

Optionally, the output device 320 is specifically configured to send, to the application unit, a response to the message acquisition request, where the response carries the to-be-processed message.

Moreover, the socket unit 301 and application unit 302 in the service node 30 shown in FIG. 4 can be implemented as being implemented by the processor 330 based on readable instructions stored in the memory 340 and data that needs to be used. All of the instructions and data needed to implement the socket unit 301 and the application unit 302 can be stored in the memory 340. The processing reads the corresponding instruction and operates in accordance with the instruction, thereby implementing the socket unit 301 and the application unit 302.

A person skilled in the art may understand that all or part of the various steps of the foregoing embodiments may be performed by a program to instruct related hardware. The program may be stored in a computer readable storage medium, and the storage medium may include: ROM, RAM, disk or CD.

The method and the service node for processing the service routing message provided by the embodiment of the present invention are described in detail. The principle and the implementation manner of the present invention are described in the following. The description of the above embodiment is only used. To help understand the method of the present invention and its core ideas; In the meantime, the present invention is not limited by the scope of the present invention.

Claims (14)

1. A method for processing a service routing packet, which is characterized by:

   The socket unit in the service node SN creates a first socket, and the first socket is used to listen to the first packet, where the first packet is a service routing report belonging to the first service routing type. The first packet includes the service routing information and the to-be-processed packet.

   Determining, by the socket unit, that the SN receives the first packet according to the first socket;

   The socket unit stores a correspondence between the to-be-processed message and the second socket, where the second socket corresponds to the service routing information;

   The socket unit receives a message acquisition request from an application unit in the SN, where the message acquisition request is used to request the to-be-processed message corresponding to the second socket;

   Determining, by the socket unit, the to-be-processed message as the requested message according to the packet obtaining request and the corresponding relationship;

   The socket unit sends the to-be-processed message to the application unit by sending a response to the message acquisition request to the application unit.
2. The method of claim 1 further comprising:

   Receiving, by the application unit, a processed message corresponding to the second socket, where the processed message is processed by the application unit to process the to-be-processed message Obtained

   The socket unit determines the service routing information according to the second socket corresponding to the processed message;

   Sending a second packet to the service router SR, where the second packet is a service routing packet that includes the processed packet, and the service routing information of the second packet includes the service routing information.
3. The method according to claim 1 or 2, wherein the storing the correspondence between the to-be-processed message and the second socket comprises:

   When the socket unit receives the first packet, if the second socket is not saved in the socket unit, the second socket is created, and the Processing messages added to and The packet queue corresponding to the second socket.
4. The method according to claim 1 or 2, wherein the storing the correspondence between the to-be-processed message and the second socket comprises:

   When the socket unit receives the first packet, if the second socket is saved in the socket unit, the to-be-processed message is added to the second The queue corresponding to the socket in the message.
5. The method according to any one of claims 1 to 4, wherein the socket unit receives a message acquisition request including the second socket from an application unit in the SN, The method further includes:

   The socket unit sends the second socket to the application unit.
6. The method according to any one of claims 1 to 5, wherein the socket unit is to the application by transmitting a response to the message acquisition request to the application unit The unit sends the to-be-processed message, including:

   The socket unit sends a response to the message acquisition request to the application unit, where the response carries a storage address of the to-be-processed message;

   The application unit acquires the to-be-processed message according to the storage address.
7. The method according to any one of claims 1 to 6, wherein the socket unit is to the application by transmitting a response to the message acquisition request to the application unit The unit sends the to-be-processed message, including:

   The socket unit sends a response to the message acquisition request to the application unit, where the response carries the to-be-processed message.
8. A service node, comprising: a socket unit and an application unit;

   The socket unit includes:

   Creating a sub-unit, configured to create a first socket, where the first packet is used to listen to the first packet, where the first packet is a service routing packet belonging to the first service routing type. The first packet includes service routing information and pending packets;

   Determining a subunit, configured to determine, according to the first socket created by the creating subunit Receiving, by the SN, the first packet;

   a saving subunit, configured to save a correspondence between the to-be-processed message and the second socket, where the second socket corresponds to the service routing information;

   a receiving subunit, configured to receive a message obtaining request from an application unit in the SN, where the message obtaining request is used to request the to-be-processed message corresponding to the second socket;

   The determining subunit is further configured to determine, according to the packet obtaining request that is received by the receiving subunit and the corresponding relationship that is saved by the saving subunit, that the to-be-processed packet is the requested packet;

   And a sending subunit, configured to send the to-be-processed message determined by the determining subunit to the application unit by sending a response to the packet request to the application unit.
9. The service node according to claim 8

   The receiving subunit is further configured to receive, from the application unit, a processed message corresponding to the second socket, where the processed message is sent by the application unit to the to-be-processed message Obtained by processing the text;

   The determining subunit is further configured to determine the service routing information according to the second socket corresponding to the processed message received by the receiving subunit;

   The sending subunit is further configured to send a second packet to the service router SR, where the second packet is a service routing packet that includes the processed packet, and the service routing information of the second packet includes Determining the service routing information determined by the subunit.
10. A service node according to claim 8 or 9,

    The creating subunit is further configured to: when the receiving subunit receives the first packet, if the second socket is not saved in the saving subunit, create the second socket word;

    The saving subunit is specifically configured to add the to-be-processed message to a message queue corresponding to the second socket created by the creating subunit.
11. A service node according to claim 8 or 9,

    The saving subunit is specifically configured to: when the receiving subunit receives the first packet, If the second socket is saved in the save subunit, the to-be-processed message is added to the message queue corresponding to the second socket.
12. A service node according to any of claims 8-11, characterized in that

    The sending subunit is further configured to send the second socket to the application unit before receiving a message obtaining request including the second socket from an application unit in the SN.
13. A service node according to any of claims 8-12, characterized in that

    The sending subunit is configured to send a response to the packet obtaining request to the application unit, where the response carries a storage address of the to-be-processed packet;

    The application unit is configured to acquire the to-be-processed message according to the storage address.
14. A service node according to any of claims 8-13, characterized in that

    The sending subunit is configured to send a response to the packet obtaining request to the application unit, where the response carries the to-be-processed message.

Images