CN116915669A

CN116915669A - Message management method, device, related equipment, chip and storage medium

Info

Publication number: CN116915669A
Application number: CN202311177789.3A
Authority: CN
Inventors: 郑好; 赵洋洋; 曹彬; 谢洁意; 谢佳
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Suzhou Software Technology Co Ltd
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Suzhou Software Technology Co Ltd
Priority date: 2023-09-13
Filing date: 2023-09-13
Publication date: 2023-10-20
Anticipated expiration: 2043-09-13
Also published as: CN116915669B

Abstract

The disclosure provides a message management method, a message management device, a related device, a chip and a storage medium, and relates to the field of data transmission. The method comprises the following steps: the first equipment receives a first message sent by the second equipment; the first message includes a sample stream (sFlow); managing the first message based on first information of the first message; the first information includes information of a first destination port for receiving the first message or information of a first source port for transmitting the first message. According to the scheme provided by the disclosure, the resource utilization rate of the server can be improved, and the deployment difficulty is reduced.

Description

Message management method, device, related equipment, chip and storage medium

Technical Field

The present disclosure relates to the field of data transmission, and in particular, to a method, an apparatus, a related device, a chip, and a storage medium for managing a message.

Background

The Sampled Flow (sFlow) technology is a network traffic monitoring technology based on message sampling. The sFlow client can be deployed in a switch/router in the form of software and hardware; by subscribing cloud log service at the sFlow server or separately deploying sFlow collectors (collectors) in different servers, sFlow clients distributed at different positions of the network can report collected traffic logs to the sFlow server, and the sFlow server can analyze and store the traffic logs.

Disclosure of Invention

The disclosure provides a message management method, a device, related equipment, a chip and a storage medium, which can improve the resource utilization rate of a server and reduce the deployment difficulty.

An embodiment of a first aspect of the present disclosure provides a method for message management, applied to a first device, where the method includes:

receiving a first message sent by second equipment; the first message comprises sFlow;

managing the first message based on first information of the first message; the first information includes information of a first destination port for receiving the first message or information of a first source port for transmitting the first message.

In the above solution, the first information includes information of a first destination port for receiving the first packet, and the method further includes:

configuring a first user datagram protocol (User Datagram Protocol, UDP) port and a first instance; the first UDP port is used for receiving a first message sent by the second device;

and monitoring a first message received by the first UDP port by using the first instance, and determining the first information.

In the above solution, the first information includes information of a first source port for sending the first packet, and the method further includes:

Sending a first request; the first request is used for requesting the second device to determine the first source port from at least one source port;

receiving acknowledgement information sent by the second equipment in response to the first request;

and determining the first information based on the confirmation information.

In the above scheme, the first request includes second information and third information; the second information includes information of all source ports configured by the first device, and the third information includes information of occupied source ports in all source ports configured by the first device.

In the above scheme, before receiving the first message sent by the second device, the method further includes:

transmitting configuration information to the second device by utilizing the bidirectional streaming connection established by the first device and the second device based on gRPC; the configuration information comprises address information, message length information and sampling information of the first equipment.

An embodiment of a second aspect of the present disclosure provides a method for message management, applied to a second device, where the method includes:

receiving a first request sent by first equipment; the first request is used for requesting the second device to determine a first source port, which is used by the second device to send a first message, from at least one source port; the first message comprises sFlow;

Determining the first source port from the at least one source port in response to the first request, generating acknowledgement information;

and sending the confirmation information.

In the above scheme, the first request includes second information and third information; the second information comprises information of all source ports configured by the first device, and the third information comprises information of occupied source ports in all source ports configured by the first device; the method further comprises the steps of:

the at least one source port is determined based on the second information and the third information.

In the above scheme, the method further comprises:

receiving configuration information sent by the first equipment by utilizing bidirectional streaming connection established by the first equipment and the second equipment based on gRPC; the configuration information comprises address information, message length information and sampling information of the first equipment.

An embodiment of a third aspect of the present disclosure provides a packet management apparatus, including:

the first receiving unit is used for receiving a first message sent by the second equipment; the first message comprises sFlow;

the first processing unit is used for managing the first message based on the first information of the first message; the first information includes information of a first destination port for receiving the first message or information of a first source port for transmitting the first message.

A fourth aspect of the present disclosure proposes a message management device, the device comprising:

the second receiving unit is used for receiving a first request sent by the first equipment; the first request is used for requesting the second device to determine a first source port, which is used by the second device to send a first message, from at least one source port; the first message comprises sFlow;

a second processing unit, configured to determine, in response to the first request, the first source port from the at least one source port, and generate acknowledgement information;

and the second sending unit is used for sending the confirmation information.

A fifth aspect embodiment of the present disclosure proposes an electronic device including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method described in embodiments of the first aspect of the present disclosure or to perform the method described in embodiments of the second aspect of the present disclosure.

A sixth aspect embodiment of the present disclosure proposes a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the method described in the first aspect embodiment of the present disclosure or to perform the method described in the second aspect embodiment of the present disclosure.

A seventh aspect of the present disclosure provides a chip comprising one or more interfaces and one or more processors; the interface is for receiving a signal from a memory of the electronic device and sending the signal to the processor, the signal comprising computer instructions stored in the memory, which when executed by the processor, cause the electronic device to perform the method described in the embodiments of the first aspect of the disclosure or to perform the method described in the embodiments of the second aspect of the disclosure.

In summary, a method, a device, a related device, a chip and a storage medium for managing a message are provided, where a first device receives a first message sent by a second device; the first message comprises sFlow; managing the first message based on first information of the first message; the first information includes information of a first destination port for receiving the first message or information of a first source port for transmitting the first message. According to the technical scheme provided by the embodiment of the disclosure, the server distinguishes different forwarding devices according to the source port or the destination port of the sFlow, so that the different forwarding devices can be isolated and the flow logs of the different forwarding devices can be managed independently, centralized management and control of the flow logs of the different forwarding devices by the server are realized, and the centralized management of the different forwarding devices is realized by the same server, so that the utilization rate of server resources can be improved, and the equipment cost is reduced; meanwhile, the sFlow Collector is not required to be deployed on different servers for each forwarding device or cloud log service is not required to be subscribed independently, so that deployment difficulty and complexity are reduced, and deployment time is saved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.

Fig. 1 is a flow chart of a message management method according to an embodiment of the disclosure;

fig. 2 is a flow chart of a message management method according to an embodiment of the disclosure;

fig. 3 is a flow chart of a message management method according to an embodiment of the disclosure;

fig. 4 is a flow chart of a message management method according to an embodiment of the disclosure;

fig. 5 is a flow chart of a message management method according to an embodiment of the disclosure;

fig. 6 is a schematic flow chart of a device flow log collection method provided by an embodiment of the disclosure;

fig. 7 is a flowchart of another device flow log collection method provided by an embodiment of the disclosure;

fig. 8 is a schematic structural diagram of a message management device according to an embodiment of the disclosure;

fig. 9 is a schematic structural diagram of a message management device according to an embodiment of the disclosure;

Fig. 10 is a schematic structural diagram of a first device according to an embodiment of the disclosure;

fig. 11 is a schematic structural diagram of a second device according to an embodiment of the disclosure;

fig. 12 is a schematic diagram of a message management system according to an embodiment of the disclosure;

fig. 13 is a schematic diagram of a chip structure according to an embodiment of the disclosure.

Detailed Description

Embodiments of the present disclosure are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are exemplary and intended for the purpose of explaining the present disclosure and are not to be construed as limiting the present disclosure.

The network traffic monitoring technology is to analyze and predict the traffic log according to the collected user traffic log, for example, netflow and sFlow technologies. The sFlow is applied to the process of network monitoring, and can provide complete flow information from the second layer to the seventh layer by utilizing a data flow random sampling technology, so that more comprehensive and accurate flow information can be provided for a user side in the process of monitoring network flow and troubleshooting network faults by capturing incoming and outgoing flow information by user side equipment, and the user side can analyze the performance, trend, existence problem and the like of the network transmission flow in more detail and accurately in the process of analyzing the performance, trend and existence problem of the network transmission flow by the user side.

In the related art, a client of an sFlow system is generally implemented by using an sFlow proxy service with an open source, and an sFlow server is generally implemented by using an sFlow Collector with an open source.

Software Defined Wide Area Network (SDWAN) is a network application technology applied to wide area network (Wide Area Network, WAN) transport connections that can be used to integrate and virtualize wide area network connections and functions into a centralized strategy to simplify the deployment and management of complex WAN topologies. Under the SDWAN application scene, the sFlow proxy service needs to subscribe to the cloud log service independently at the client, or the sFlow Collector is deployed independently; in order to effectively isolate the flow logs of different user terminal devices, the sFlow Collector is independently deployed on different servers; however, the cloud log service is separately subscribed and the sFlow Collector is separately deployed, the deployment complexity and deployment difficulty are high, and the sFlow Collector is separately deployed on different servers, which causes waste of server resources and increases equipment cost.

Based on the above, in each embodiment of the disclosure, the server distinguishes different forwarding devices according to the source port or the destination port of sFlow, so that different forwarding devices can be isolated and different forwarding device flow logs can be managed independently, centralized management and control of the different forwarding device flow logs by the server are realized, and the centralized management of different forwarding devices is realized by the same server, so that the utilization rate of server resources can be improved, and the equipment cost is reduced; meanwhile, the sFlow Collector is not required to be deployed on different servers for each forwarding device or cloud log service is not required to be subscribed independently, so that deployment difficulty and complexity are reduced, and deployment time is saved.

Fig. 1 provides a flow chart of a message management method, which is applied to a first device. As shown in fig. 1, the method may include:

step 101: receiving a first message sent by second equipment; the first message includes sFlow.

In practical application, the first device may be a server device, and in particular, may be a server device, such as a server, where an sFlow Collector is deployed; the first device may also be referred to as a control plane device, and the embodiments of the present disclosure are not limited thereto, as long as the functions thereof can be implemented.

In practical application, the second device may be a client device, specifically, may be a device where an sFlow proxy service is deployed, for example, a forwarding device such as a customer premise equipment (CPE, customer Premise Equipment), a switch, a router, and the like; the sFlow proxy service may also be referred to as an sFlow proxy service, and may also be referred to as an sFlow Agent, which is not limited in the embodiments of the present disclosure, as long as the functions thereof can be implemented.

In practical application, the first message may be a user datagram protocol (UDP, user Datagram Protocol) message; the sFlow may also be referred to as a flow log, and may also be referred to as a flow log, which is not limited by the embodiments of the present disclosure, so long as the functions thereof can be implemented.

In actual application, the first message may be transmitted in a passive mode; specifically, the second device uses a random port to send the first message, and the first device uses a fixed port to monitor the message sent by the second device.

Based on this, in an embodiment, the first information includes information of a first destination port for receiving the first packet, and the method further includes:

configuring a first UDP port and a first instance; the first UDP port is used for receiving a first message sent by the second device;

In practical application, for each second device, the first device may randomly use one port as a UDP port for monitoring a message sent by the device, i.e., the first destination port, and create an sFlow Collector instance for monitoring a message received by a corresponding UDP port; wherein, an sFlow Collector instance may correspond to a second device; the first destination port may also be referred to as an sFlow message destination port, which is not limited in this embodiment of the disclosure, as long as the function thereof can be implemented.

In practical application, the first device may create a first association relationship between the second device and the UDP port, so that the second device corresponding to the first UDP port may be determined according to the first association relationship.

In the embodiment of the disclosure, the first device may determine the identity information of the forwarding device (i.e., the second device) of the monitored first UDP port packet according to the first association relationship, so that the packets sent by different devices may be managed respectively, and isolation of the traffic logs of different client devices is implemented on the basis of centralized management of the traffic logs of different client devices by using one server device.

In practical application, the first message may also be transmitted in an active mode; specifically, the second device sends the message by using a conditional random source port, and the first device can determine the corresponding second device according to the source port of the sent message by knowing the second association relationship between the source port and the second device, so as to distinguish and manage the messages sent by different second devices.

Based on this, in an embodiment, the first information includes information of a first source port for sending the first packet, and the method may further include:

and determining the first information based on the confirmation information.

In practical applications, the at least one source port may be configured by the first device.

In an embodiment, the first request may include second information and third information; the second information includes information of all source ports configured by the first device, and the third information includes information of occupied source ports in all source ports configured by the first device.

In actual application, after receiving the second information and the third information, the second device may determine an unoccupied source port, that is, an idle source port, in source ports configured by the first device according to the second information and the third information, and determine, in the unoccupied source ports, one port as a source port, that is, the first source port, of the second device sending a message; the first source port may also be referred to as an sFlow message source port, which is not limited in this embodiment of the disclosure, as long as the function thereof can be implemented.

In practical application, the second information may include a first list of all source ports configured by the first device, the third information may include a second list of occupied source ports, and the second device may randomly select one port from a difference set of the first list and the second list as the first source port based on the second information and the third information.

In actual application, the second device may send the determined information of the first source port (i.e. the acknowledgement information) to the first device; after receiving the confirmation information, the first device can update the second association relation between the second device and the source port according to the confirmation information, so that after receiving the first message sent by the first source port, the first device can determine the identity information of the second device sending the first message according to the source port information and the second association relation carried in the message, and therefore flow logs of different sFlow clients are distinguished.

In practical application, after the second device confirms the first source port, the first device may update the information of the occupied source port in all the configured source ports, that is, update the third information, based on the confirmation information of the second device.

In the embodiment of the disclosure, since the first device can distinguish the flow logs of different second devices through the source port obtained by negotiating with the second device, centralized management of concurrently processing the flow logs of a plurality of second devices can be realized by only running one sFlow Collector instance.

In practical application, the first device and the second device may first establish a connection; in particular, the second device may first send a request to the first device, such as a hypertext transfer security protocol (HTTPS, hypertext Transfer Protocol Secure) request, to request registration with the first device; the first device may send response information to the second device in response to the registration request of the second device, and establish a connection with the second device.

In actual application, the first device and the second device may establish a bidirectional streaming connection based on gRPC; wherein gRPC is a remote procedure call protocol (RPC, remote Procedure Call) for communication between a client and a server; specifically, after the first device returns the response information to the second device, the second device may initialize a gRPC client according to a local gRPC certificate, and establish a bidirectional streaming connection with the first device based on gRPC, that is, establish a gRPC bidirectional streaming connection.

Here, after the bidirectional flow connection is established, the connection is established when the second device is on line, and the connection is disconnected when the second device is off line, so that the bidirectional flow connection state can reflect the on-line state of the second device, and the first device can sense the on-line state of the second device; meanwhile, by establishing the bidirectional flow connection, both the sFlow client and the sFlow server can send data flows to the other side, and the simultaneous sending of the data of the two sides is supported, so that real-time interaction is realized, and the efficiency of data transmission is improved.

In practical application, the first device may send configuration information to the second device.

Based on this, in an embodiment, before receiving the first packet sent by the second device, the method may further include:

In practical application, the configuration information may include address information, message length information and sampling information of the first device; the address information of the first device may be address information of an sFlow Collector; the message length information may be a UDP message length, and specifically may be a length of a UDP message that may be sent by the second device; the sampling information may be a sampling rate, and in particular, may be a sampling rate of the second device sampling the packet.

In practical application, after receiving the configuration information, the second device may create the sFlow client, i.e. the sFlow Agent, based on the configuration information.

Step 102: managing the first message based on first information of the first message; the first information includes information of a first destination port for receiving the first message or information of a first source port for transmitting the first message.

In actual application, the first device may store, analyze, predict, etc. the first message; specifically, the first device may determine the identity information of the second devices according to the first information, and manage the flow logs reported by each second device according to the identity information, so as to ensure mutual isolation between the flow logs of different user side devices.

In practical application, the first device may store the traffic log uploaded by the second device in a distributed database, and provide an http interface or a grpc interface for the user device to call the traffic log.

In sum, the server distinguishes different forwarding devices according to the source port or the destination port of the sFlow, can isolate the different forwarding devices and independently manage the flow logs of the different forwarding devices, so that the centralized management and control of the flow logs of the different forwarding devices by the server are realized, and the centralized management of the different forwarding devices is realized by the same server, so that the utilization rate of server resources can be improved, and the equipment cost is reduced; meanwhile, the sFlow Collector is not required to be deployed on different servers for each forwarding device or cloud log service is not required to be subscribed independently, so that deployment difficulty and complexity are reduced, and deployment time is saved.

Fig. 2 provides a flow chart of a message management method applied to a second device. As shown in fig. 2, the method may include:

step 201: receiving a first request sent by first equipment; the first request is used for requesting the second device to determine a first source port, which is used by the second device to send a first message, from at least one source port; the first message includes sFlow.

In an embodiment, the first request may include second information and third information; the second information comprises information of all source ports configured by the first device, and the third information comprises information of occupied source ports in all source ports configured by the first device; the method may further comprise:

In practical application, the second information may include a first list of all source ports configured by the first device, and the third information may include a second list of occupied source ports.

Step 202: in response to the first request, determining the first source port from the at least one source port, generating acknowledgement information.

In practical application, the second device may randomly select one port from the difference set of the first list and the second list as the first source port based on the second information and the third information.

Step 203: and sending the confirmation information.

In practical application, the method may further include:

and sending the first message by using the first source port.

In practical application, the confirmation information may include information of the first source port determined by the second device.

In an embodiment, the method may further include:

Fig. 3 provides a flow chart of a message management method, which is applied to a first device. As shown in fig. 3, the method may include:

step 301: configuring a first UDP port and a first instance;

step 302: receiving a first message sent by a second device by using the first UDP port; the first message comprises sFlow;

step 303: monitoring a first message received by the first UDP port by using the first instance, and determining first information; the first information comprises information of a first destination port for receiving the first message;

Step 304: and managing the first message based on the first information.

In an embodiment, before receiving the first packet sent by the second device, the method further includes:

Fig. 4 provides a flow chart of a message management method, which is applied to a first device. As shown in fig. 4, the method may include:

step 401: sending a first request; the first request is used for requesting the second device to determine a first source port, which is used by the second device to send a first message, from at least one source port; the first message comprises sFlow;

step 402: receiving acknowledgement information sent by the second equipment in response to the first request;

step 403: determining first information based on the confirmation information; the first information comprises information of a first source port used for sending the first message;

step 404: receiving a first message sent by second equipment;

step 405: and managing the first message based on the first information.

In an embodiment, before receiving the first packet sent by the second device, the method may further include:

Fig. 5 provides a flow chart of a message management method. As shown in fig. 5, the method may include:

step 501: the first device sends a first request; the first request is used for requesting the second device to determine a first source port, which is used by the second device to send a first message, from at least one source port;

step 502: in response to the first request, the second device determines the first source port from the at least one source port, generating acknowledgement information;

step 503: the second device sends the confirmation information;

Step 504: the first device determines first information based on the confirmation information; the first information comprises information of a first source port used for sending the first message;

step 505: the first device receives a first message sent by the second device;

step 506: the first device manages the first message based on the first information; wherein,

the first message includes sFlow.

Here, it should be noted that: the specific processing procedures of the first device and the second device are described in detail above, and are not described in detail here.

The technical scheme of the present disclosure is described in further detail below in connection with specific application examples.

Fig. 6 is a flow chart of a device flow log collection method provided by an embodiment of the disclosure. As shown in fig. 6, the method includes:

step 601: the forwarding plane device (i.e., the second device) sends a https request of HelloReq to the control plane device (i.e., the first device) when the forwarding plane device is online to report the online status of the forwarding plane device.

The control plane device may also be referred to as a control device, in particular a controller.

Step 602: the control plane device responds to the online registration result of the forwarding plane device and returns response information HelloResp.

Step 603: and initializing a grpc client by the forwarding plane equipment according to the local grpc certificate, and establishing grpc bidirectional stream connection with the server.

Wherein the gRPC may include the following four request/response modes:

(1) Simple mode (English may be expressed as Simple RPC)

Specifically, the client initiates a request, and the server responds to a data.

(2) Service end data flow mode (English may be expressed as Server-side streaming RPC)

Specifically, a client initiates a request, and a server returns a section of continuous data stream; for example, the client sends a query request of an account to the server, and the server continuously returns real-time data of the account to the client.

(3) Client data stream mode (English may be expressed as Client-side streaming RPC)

In contrast to the server-side data stream mode, the client-side data stream mode is that the client-side continuously transmits the data stream to the server-side, and after the transmission is finished, the server-side returns a response; for example, the terminal of the internet of things reports data to the server.

(4) Bidirectional data flow mode (English may be expressed as Bidirectional streaming RPC)

Specifically, both the client and the server can send data streams to each other, and the data of both sides can be sent to each other at the same time, that is, real-time interaction can be realized. Such as a mobile terminal that has deployed a chat application.

Step 604: the control plane device randomly uses one port as a UDP port (namely a first UDP port) monitored by the sFlow Collector, and sends sFlow Agent basic configuration (comprising sFlow Collector address, UDP message length, sampling rate and the like) to the forwarding plane device so that the forwarding plane device creates the sFlow Agent, namely sends a request for creating the sFlow Agent.

The control plane device creates an sFlow Collector instance to monitor sFlow messages of the UDP port while issuing configuration, and one instance corresponds to one device.

Step 605: the forwarding plane device creates the sFlow Agent according to the issued configuration and responds to the creation result, that is, returns a response including the sFlow Agent creation result.

Step 601 to step 605 are processes of controlling connection by the control plane device, wherein step 601 to step 603 are establishing flows of gRPC bidirectional flow connection; steps 604 and 605 are the process of the control plane device issuing the server port.

Step 606: and the forwarding plane equipment transmits the sFlow message to the control plane equipment according to the issued sFlow Collector address so as to transmit the flow log.

Here, the control plane device saves the uploaded flow log to the distributed database and provides an http/grpc interface for the user to call.

Steps 601 to 606 are processes of transmitting sFlow in a passive mode, and flow logs of different devices are distinguished by adopting a port monitored by a server sFlow collector instance, wherein one instance corresponds to one device.

The application embodiments of the present disclosure have the advantages that: the user flow log is managed and controlled through the control plane equipment, and the user does not need to independently deploy a sflow collector or order a flow log service, so that the deployment time is saved, and the user cost is reduced; since the sflow agent in the Open source virtual switch (ovs, open vSwitch) of the Open source can be multiplexed without concern for the sflow agent details, the deployment difficulty and complexity are reduced.

Fig. 7 is a flowchart of another device flow log collection method provided by an embodiment of the present disclosure. As shown in fig. 7, the method includes:

step 701: and the forwarding plane device sends an https request of HelloReq to the control plane device when the forwarding plane device is online so as to report the online state of the forwarding plane device.

Step 702: the control plane device responds to the online registration result of the forwarding plane device and returns response information HelloResp.

Step 703: and initializing a grpc client by the forwarding plane equipment according to the local grpc certificate, and establishing grpc bidirectional stream connection with the server.

Step 704: the control plane device sends the basic configuration of the sFlow Agent (including the sFlow collector address, the UDP message length, the sampling rate, etc.) and the sFlow message source port list occupied by other devices to the forwarding plane device, so that the forwarding plane device creates the sFlow Agent, that is, sends a request for creating the sFlow Agent.

Step 705: the forwarding plane device randomly selects one port from the difference set of the occupied sflow message source port list (namely the second list) and the idle port list (namely the first list) of other devices as the sflow message source port; and the forwarding plane equipment establishes an sFlow Agent according to the issued configuration, and responds the establishment result and the reported sFlow message source port to the control plane equipment, namely returns a response comprising the sFlow Agent establishment result.

After receiving the response returned by the forwarding plane device, the control plane device updates the corresponding relationship between the sFlow message source port and the forwarding plane device in the database, that is, the second association relationship, and distinguishes the flow logs of different devices according to the corresponding relationship.

Steps 701 to 705 are processes of controlling connection by the control plane device, wherein steps 701 to 703 are establishment flows of the gppc bidirectional flow connection; steps 704 and 705 are the process by which the control plane device negotiates a client port with the forwarding plane device.

Step 706: and the forwarding plane equipment transmits the sflow message to the control plane equipment according to the issued sflow collector address so as to transmit the stream log.

The control plane device may fix a 6379 port to receive the sFlow message sent by the forwarding plane device.

The control plane device stores the uploaded stream log in a distributed database and provides an http/grpc interface for the user to call.

Steps 701 to 706 are the process of transmitting sFlow in the active mode, and the source ports of the sFlow messages negotiated by the control plane device and the forwarding plane device are used to distinguish the flow logs of different devices, where one source port corresponds to one device.

The application embodiments of the present disclosure have the advantages that: the user flow log is managed and controlled through the control plane equipment, and the user does not need to independently deploy a sflow collector or order a flow log service, so that the deployment time is saved, and the user cost is reduced; meanwhile, the control plane device can concurrently process the flow logs of the different forwarding plane devices only by running one sflow collector instance, so that the deployment difficulty and complexity are reduced.

In order to implement the above method for managing the messages on the first device side, the embodiment of the disclosure further provides a device for managing the messages, which is disposed on the first device. As shown in fig. 8, the apparatus 800 includes:

A first receiving unit 801, configured to receive a first packet sent by a second device; the first message comprises sFlow;

a first processing unit 802, configured to manage the first packet based on first information of the first packet; the first information includes information of a first destination port for receiving the first message or information of a first source port for transmitting the first message.

In an embodiment, the first information includes information of a first destination port for receiving the first packet, and the first processing unit 802 may be further configured to:

In an embodiment, the first information includes information of a first source port for sending the first packet, and the first processing unit 802 may be further configured to:

And determining the first information based on the confirmation information.

In an embodiment, the first request includes second information and third information; the second information includes information of all source ports configured by the first device, and the third information includes information of occupied source ports in all source ports configured by the first device.

In an embodiment, the apparatus may further include:

a first sending unit, configured to send configuration information to a second device by using a bidirectional streaming connection established by the first device and the second device based on gRPC before receiving a first packet sent by the second device; the configuration information comprises address information, message length information and sampling information of the first equipment.

In order to implement the above method for managing the messages on the second device side, the embodiment of the disclosure further provides a device for managing the messages, which is disposed on the second device. As shown in fig. 9, the apparatus 900 includes:

a second receiving unit 901, configured to receive a first request sent by a first device; the first request is used for requesting the second device to determine a first source port, which is used by the second device to send a first message, from at least one source port; the first message comprises sFlow;

A second processing unit 902, configured to determine, in response to the first request, the first source port from the at least one source port, and generate acknowledgement information;

a second sending unit 903, configured to send the acknowledgement information.

In an embodiment, the first request includes second information and third information; the second information comprises information of all source ports configured by the first device, and the third information comprises information of occupied source ports in all source ports configured by the first device; the second processing unit 902 may be further configured to:

In an embodiment, the second receiving unit 901 may be further configured to:

It should be noted that: in the packet management device provided in the above embodiment, only the division of each program module is used for illustration, and in practical application, the processing allocation may be performed by different program modules according to needs, that is, the internal structure of the device is divided into different program modules, so as to complete all or part of the processing described above. In addition, the message management device and the message management method embodiment provided in the foregoing embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiment and are not repeated herein.

Based on the hardware implementation of the program modules, and in order to implement the method of the embodiments of the present disclosure, the embodiments of the present disclosure further provide a first device, as shown in fig. 10, where the first device 1000 includes:

the first communication interface 1001 is capable of performing information interaction with other devices, for example, receiving a first message sent by the second device;

the first processor 1002 is connected to the first communication interface 1001, so as to implement information interaction with other devices, and is configured to execute the methods provided by one or more of the above technical solutions when running a computer program;

a first memory 1003, said computer program being stored on said first memory 1003.

Specifically, the first communication interface 1001 is configured to receive a first packet sent by the second device; the first message comprises sFlow;

the first processor 1002 is configured to manage the first packet based on first information of the first packet; the first information includes information of a first destination port for receiving the first message or information of a first source port for transmitting the first message.

In an embodiment, the first information includes information of a first destination port for receiving the first packet, and the first processor 1002 may be further configured to:

In an embodiment, the first information includes information of a first source port for sending the first packet, and the first processor 1002 may be further configured to:

transmitting a first request using the first communication interface 1001; the first request is used for requesting the second device to determine the first source port from at least one source port;

receiving, by using the first communication interface 1001, acknowledgement information sent by the second device in response to the first request;

and determining the first information based on the confirmation information.

In an embodiment, before receiving the first packet sent by the second device, the first communication interface 1001 may be further configured to:

It should be noted that: the specific processing of the first communication interface 1001 and the first processor 1002 can be understood with reference to the above-described method.

Of course, in actual practice, the various components of the first device 1000 would be coupled together by a bus system 1004. It is to be appreciated that the bus system 1004 serves to facilitate connective communication between these components. The bus system 1004 includes a power bus, a control bus, and a status signal bus in addition to the data bus. The various buses are labeled in fig. 10 as bus system 1004 for clarity of illustration.

The first memory 1003 in the embodiment of the present application is used to store various types of data to support the operation of the first device 1000. Examples of such data include: any computer program for operating on the first device 1000.

The method disclosed in the above embodiment of the present application may be applied to the first processor 1002 or implemented by the first processor 1002. The first processor 1002 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the method described above may be performed by integrated logic circuits of hardware or instructions in software form in the first processor 1002. The first processor 1002 described above may be a general purpose processor, a digital signal processor (DSP, digital Signal Processor), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The first processor 1002 may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiment of the application can be directly embodied in the hardware of the decoding processor or can be implemented by combining hardware and software modules in the decoding processor. The software modules may be located in a storage medium located in the first memory 1003, and the first processor 1002 reads information in the first memory 1003, in combination with its hardware, to perform the steps of the method as described above.

In an exemplary embodiment, the first device 1000 can be implemented by one or more application specific integrated circuits (ASIC, application Specific Integrated Circuit), DSPs, programmable logic devices (PLD, programmable Logic Device), complex programmable logic devices (CPLD, complex Programmable Logic Device), field-programmable gate arrays (FPGA, field-Programmable Gate Array), general purpose processors, controllers, microcontrollers (MCU, micro Controller Unit), microprocessors (Microprocessor), or other electronic components for performing the aforementioned methods.

Based on the hardware implementation of the program modules, and in order to implement the method on the second device side in the embodiment of the present application, the embodiment of the present application further provides a second device, as shown in fig. 11, where the second device 1100 includes:

a second communication interface 1101 capable of information interaction with the first device; for example, a first message is sent to a first device;

a second processor 1102, connected to the second communication interface 1101, for implementing information interaction with the first device, and configured to execute, when executing the computer program, a method provided by one or more technical solutions on the second device side;

A second memory 1103, said computer program being stored on said second memory 1103.

Specifically, the second communication interface 1101 is configured to receive a first request sent by a first device; the first request is used for requesting the second device to determine a first source port, which is used by the second device to send a first message, from at least one source port; the first message comprises sFlow; and, for transmitting the acknowledgement information;

the second processor 1102 is configured to determine, in response to the first request, the first source port from the at least one source port, and generate the acknowledgement information.

In an embodiment, the first request includes second information and third information; the second information comprises information of all source ports configured by the first device, and the third information comprises information of occupied source ports in all source ports configured by the first device; the second processor 1102 may also be configured to:

In an embodiment, the second communication interface 1101 may be further configured to:

It should be noted that: the specific processing of the second communication interface 1101 and the second processor 1102 may be understood with reference to the methods described above.

Of course, in actual practice, the various components in the second device 1100 would be coupled together by a bus system 1104. It is to be appreciated that the bus system 1104 is employed to facilitate connected communications between the components. The bus system 1104 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration, the various buses are labeled as bus system 1104 in fig. 11.

The second memory 1103 in the embodiment of the present application is used to store various types of data to support the operation of the second device 1100. Examples of such data include: any computer program for operating on the second device 1100.

The method disclosed in the above embodiment of the present application may be applied to the second processor 1102 or implemented by the second processor 1102. The second processor 1102 may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the method may be implemented by an integrated logic circuit of hardware or an instruction in software form in the second processor 1102. The second processor 1102 described above may be a general purpose processor, DSP, or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The second processor 1102 may implement or perform the methods, steps and logic blocks disclosed in embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiment of the application can be directly embodied in the hardware of the decoding processor or can be implemented by combining hardware and software modules in the decoding processor. The software module may be located in a storage medium located in the second memory 1103, said second processor 1102 reading information in the second memory 1103, performing the steps of the method described above in connection with its hardware.

In an exemplary embodiment, the second device 1100 can be implemented by one or more ASIC, DSP, PLD, CPLD, FPGA, general-purpose processors, controllers, MCU, microprocessor, or other electronic elements for performing the aforementioned methods.

It is to be understood that the memories (the first memory 1003 and the second memory 1103) of the embodiment of the present application may be volatile memories or nonvolatile memories, and may include both volatile memories and nonvolatile memories. Wherein the nonvolatile Memory may be Read Only Memory (ROM), programmable Read Only Memory (PROM, programmable Read-Only Memory), erasable programmable Read Only Memory (EPROM, erasable Programmable Read-Only Memory), electrically erasable programmable Read Only Memory (EEPROM, electrically Erasable Programmable Read-Only Memory), magnetic random access Memory (FRAM, ferromagnetic random access Memory), flash Memory (Flash Memory), magnetic surface Memory, optical disk, or compact disk Read Only Memory (CD-ROM, compact Disc Read-Only Memory); the magnetic surface memory may be a disk memory or a tape memory. The volatile memory may be random access memory (RAM, random Access Memory), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (SRAM, static Random Access Memory), synchronous static random access memory (SSRAM, synchronous Static Random Access Memory), dynamic random access memory (DRAM, dynamic Random Access Memory), synchronous dynamic random access memory (SDRAM, synchronous Dynamic Random Access Memory), double data rate synchronous dynamic random access memory (ddr SDRAM, double Data Rate Synchronous Dynamic Random Access Memory), enhanced synchronous dynamic random access memory (ESDRAM, enhanced Synchronous Dynamic Random Access Memory), synchronous link dynamic random access memory (SLDRAM, syncLink Dynamic Random Access Memory), direct memory bus random access memory (DRRAM, direct Rambus Random Access Memory). The memory described by embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

To implement the method of the embodiment of the present disclosure, the embodiment of the present disclosure further provides a message management system 1200, as shown in fig. 12, including: a first device 1201 and a second device 1202.

Here, it should be noted that: the specific processing procedures of the first device 1201 and the second device 1202 are described in detail above, and are not described here again.

Embodiments of the present disclosure also provide a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the message management method described in the above embodiments of the present disclosure.

Embodiments of the present disclosure also provide a computer program product comprising a computer program which, when executed by a processor, performs the message management method described in the above embodiments of the present disclosure.

The embodiment of the disclosure also provides a chip, and the chip can be seen from the schematic structural diagram of the chip shown in fig. 13. The chip shown in fig. 13 includes a processor 1301 and an interface 1302. Wherein the number of processors 1301 may be one or more and the number of interfaces 1302 may be one or more.

Optionally, the chip further comprises a memory 1303, the memory 1303 being configured to store necessary computer programs and data; the interface 1302 is configured to receive a signal from the memory 1303 and send the signal to the processor 1301, where the signal includes computer instructions stored in the memory 1303, and when the processor 1301 executes the computer instructions, cause the electronic device to execute the method for managing a message described in the foregoing embodiments of the disclosure.

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.

In the description of the present specification, reference is made to the terms "one embodiment," "some embodiments," "illustrative embodiments," "examples," "specific examples," or "some examples," etc., meaning that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.

Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, system that includes a processing module, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: electrical connections (control methods) with one or more wires, portable computer cartridges (magnetic devices), RAM, ROM, EPROM or flash memory, optical fiber devices, and portable Compact Disc Read Only Memory (CDROM). Additionally, the computer-readable medium may even be paper or other suitable medium upon which the program is printed, as the program may be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.

It is to be understood that portions of embodiments of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.

Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, and the program may be stored in a computer readable storage medium, where the program when executed includes one or a combination of the steps of the method embodiments.

Furthermore, functional units in various embodiments of the present invention may be integrated into one processing module, or each unit may exist alone physically, or two or more units may be integrated into one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented as software functional modules and sold or used as a stand-alone product. The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, or the like.

While embodiments of the present invention have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the invention, and that variations, modifications, alternatives, and variations of the above embodiments may be made by those of ordinary skill in the art within the scope of the invention.

Claims

1. A method for managing a message, applied to a first device, the method comprising:

receiving a first message sent by second equipment; the first message comprises a sampling flow;

2. The method of claim 1, wherein the first information comprises information for a first destination port that receives the first message, the method further comprising:

configuring a first User Datagram Protocol (UDP) port and a first instance; the first UDP port is used for receiving a first message sent by the second device;

3. The method of claim 1, wherein the first information comprises information of a first source port for transmitting the first message, the method further comprising:

and determining the first information based on the confirmation information.

4. A method according to claim 3, wherein the first request comprises second information and third information; the second information includes information of all source ports configured by the first device, and the third information includes information of occupied source ports in all source ports configured by the first device.

5. The method according to any one of claims 1 to 4, wherein prior to receiving the first message sent by the second device, the method further comprises:

6. A method for managing a message, the method being applied to a second device, the method comprising:

and sending the confirmation information.

7. The method of claim 6, wherein the first request includes second information and third information; the second information comprises information of all source ports configured by the first device, and the third information comprises information of occupied source ports in all source ports configured by the first device; the method further comprises the steps of:

8. The method according to claim 6 or 7, characterized in that the method further comprises:

9. A message management apparatus, the apparatus comprising:

10. A message management apparatus, the apparatus comprising:

the second receiving unit is used for receiving a first request sent by the first equipment; the first request is used for requesting the second device to determine a first source port, which is used for sending a first message, of the second device from at least one source port; the first message comprises sFlow;

and the second sending unit is used for sending the confirmation information.

11. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 5 or to perform the method of any one of claims 6 to 8.

12. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1 to 5 or to perform the method of any one of claims 6 to 8.

13. A chip comprising one or more interfaces and one or more processors; the interface is for receiving a signal from a memory of an electronic device and sending the signal to the processor, the signal comprising computer instructions stored in the memory, which when executed by the processor, cause the electronic device to perform the method of any one of claims 1 to 5 or to perform the method of any one of claims 6 to 8.