CN113114575A - Network forwarding device and data forwarding method - Google Patents
Network forwarding device and data forwarding method Download PDFInfo
- Publication number
- CN113114575A CN113114575A CN202110338373.XA CN202110338373A CN113114575A CN 113114575 A CN113114575 A CN 113114575A CN 202110338373 A CN202110338373 A CN 202110338373A CN 113114575 A CN113114575 A CN 113114575A
- Authority
- CN
- China
- Prior art keywords
- data
- message
- cache
- table entry
- response
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/563—Data redirection of data network streams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present disclosure provides a network forwarding device and a data forwarding method. According to a specific implementation of the network forwarding device and the data forwarding method, the distributed function description table entry cache and the data processing module are added in the network forwarding device, so that data processing is realized on the network forwarding device, distributed intra-network calculation is further realized, and data can be processed in network flow.
Description
Technical Field
The present disclosure relates to the field of network data switching devices, and in particular, to a network forwarding device and a data forwarding method.
Background
After decades of rapid development, the world Internet has become an important infrastructure of the information era, the traditional packet exchange based on the IP Protocol (Internet Protocol) only provides best effort data packet delivery service, the IP address essentially describes hierarchical "location" information, the traditional network only needs to establish a communication session between a device and a terminal according to the IP address, and the IP address itself does not have any association with the "content" of the message. Today, applications that dominate the internet offer mainly two services to users: content and services. Meanwhile, the user no longer pays attention to the location of the content and the service, but the acquisition of the content and the service per se, including the retrieval, transmission rate, service quality, security and the like of the content and the service. The IP protocol at the bottom layer of the information network does not make targeted changes, and the IP layer only completes the forwarding of the data packet according to the 'position' information, so that the upper layer application is needed to complete the mapping from 'content' to 'position', and the overall efficiency of the network is lowered. For this reason, a content-centric NDN network (Named Data Networking) is proposed in the industry, and this network uses a name (name) as a unique basis for content indexing and uses the name to replace IP for routing and forwarding, so that network devices have the possibility of perceiving message content.
Disclosure of Invention
The present disclosure proposes a network forwarding device and a data forwarding method.
In a first aspect, the present disclosure provides a network forwarding device, including: a message cache, a message parsing module, a data storage location table entry cache, a to-be-processed data description table entry cache, a distributed function description table entry cache, a data processing module, a forwarding routing table entry cache and a message encapsulation module, wherein the message parsing module is respectively in communication connection with the message cache, the data storage location table entry cache and the to-be-processed data description table entry cache, the data processing module is respectively in communication connection with the message cache, the to-be-processed data description table entry cache and the distributed function description table entry cache, the message encapsulation module is respectively in communication connection with the message cache, the data storage location table entry cache, the distributed function description table entry cache and the forwarding routing table entry cache, and the data storage location table entry cache is respectively in communication connection with the message cache, the distributed function description table entry cache and the to-be-processed data description table entry cache, the data description table entry cache to be processed is communicatively connected to the distributed function description table entry cache, and the distributed function description table entry cache is communicatively connected to the forwarding routing table entry cache, where:
the message cache is used for storing data messages, adding the data messages to the data messages at the storage position of the message cache and then sending the data messages to the message analysis module;
the message analysis module is configured to analyze a data message to obtain description information of the data message, where the description information includes at least one of the following: data name, message type, message length, ingress port information and storage location in the message cache;
the data storage location table entry cache is used for caching a data storage location table entry, wherein the data storage location table entry comprises a data name and a storage location of a data message stored in the message cache;
the to-be-processed data description table entry cache is used for caching the to-be-processed data description table entry, wherein the to-be-processed data description table entry comprises a data name and a corresponding ingress port information set in a data request message which is received by the network forwarding equipment and does not return corresponding response data;
the distributed function description table entry cache is used for caching the distributed function description table entry, and the distributed function description table entry comprises at least one input data name, an operation function name and an output data name;
the data processing module is used for calculating the data stored in the message cache according to a preset operation logic and sending an operation result to the message cache for storage;
the forwarding routing table entry cache is used for caching a routing table entry, and the routing table entry comprises a data name and corresponding output port information;
and the message encapsulation module is used for encapsulating the data taken out from the message cache and then sending the encapsulated data to the output port indicated by the output port information received from the forwarding routing table entry cache.
In some optional embodiments, the data processing module comprises at least one of: a Central Processing Unit (CPU), a Graphics Processing Unit (GPU) and a reconstruction or heterogeneous processing core.
In some optional embodiments, the data storage location entry cache, the forwarding routing entry cache, and the distributed function description entry cache are ternary content addressable memory or random access memory.
In some optional embodiments, the message cache is a distributed cache.
In some optional embodiments, the routing table entry is a routing table entry issued by an upper layer protocol stack or a network manager.
In some optional embodiments, the packet parsing module and the packet encapsulation module are state machine circuits.
In some optional embodiments, the message parsing module and the message cache, and the message cache and the message encapsulation module are in communication connection via an AXI-Stream interface, and an input end of the message parsing module and an output end of the message encapsulation module are AXI-Stream interfaces.
In a second aspect, the present disclosure provides a data forwarding method applied to a network forwarding device as described in any implementation manner of the first aspect, where the method includes:
the message cache stores data messages, and the data messages are added to the data messages at the storage position of the message cache and then sent to the message analysis module;
the message analysis module responds to the received data request message, and sends the data request message to the data storage location table entry cache, wherein the data request message comprises: requesting a data name, ingress port information and a storage location in the message cache;
the data storage position table entry cache responds to the received data request message and determines whether a request data name in the data request message exists in the data storage position table entry cache or not; in response to determining that the data request message exists, sending the data request message to the message encapsulation module; responding to the data request message and sending the data request message to the to-be-processed data description table entry cache;
the message encapsulation module reads a message from the message cache according to the storage position in the received data message in response to the received data message, encapsulates the message into a data response message and sends the data response message to a target output port, wherein the target output port is an output port indicated by output port information corresponding to the received data message and received by the message encapsulation module from the forwarding routing table entry cache;
responding to the received data request message by the to-be-processed data description table entry cache, and determining whether a request data name in the data request message exists in the to-be-processed data description table entry cache or not; in response to determining that the data request message does not exist, sending the data request message to the distributed function description table entry cache; in response to determining that the request message exists, adding ingress port information in the data request message to an ingress port information set corresponding to a request data name in the data request message in the to-be-processed data description table entry cache, and discarding the data request message;
the distributed function description table entry cache responds to the received data request message, and inquires a distributed function description table entry matching the output data name with the request data name in the data request message in the distributed function description table entry cache; responding to the data request message which is not found, and sending the data request message to the forwarding routing table entry cache; and responding to the searching, generating a new data request message for requesting data corresponding to each input data name in the searched distributed function description table item, and sending each generated data request message to the data storage position table item cache.
In some optional embodiments, the method further comprises:
the message analysis module responds to the received data response message, and sends the data response message to the to-be-processed data description table entry cache, wherein the data response message comprises: responding to a data name, a data name required by operation, input port information and a storage position in the message cache;
responding to the received data response message by the to-be-processed data description table entry cache, and determining whether a response data name in the data response message exists in the to-be-processed data description table entry cache or not; responding to the determination of existence, and sending a first signal and the data response message to the data storage position table entry cache; responding to the data storage position table entry cache and sending a second signal and the data response message in response to the determination of absence;
the data storage location table entry cache responds to the first signal and the data response message and determines that the data response message is correct, generates a data storage location table entry by using a response data name and a storage location in the data response message, stores the data storage location table entry into the data storage location table entry cache, and sends the data response message to the distributed function description table entry cache;
the data storage location table entry cache sends a third signal and the data response message to the message cache in response to receiving the second signal and the data response message;
the message cache responds to the third signal and the data response message and releases the space occupied by the data response message;
the distributed function description table entry cache responds to the received data response message, and inquires a distributed function description table entry of which the output data name is matched with the response data name in the data response message in the distributed function description table entry cache; responding to the inquiry, and sending the data response message to the message packaging module; in response to the query, querying a distributed function description table entry of which the input data name comprises a response data name in the data response message in the distributed function description table entry cache; responding to the query, and sending the searched distributed function description table entry and the storage position in the data response message to the data processing module as a calculation task;
the data processing module responds to the received calculation task and checks the calculation task, reads data from the message cache according to the storage position in the calculation task, executes an instruction sequence corresponding to the name of an operation function in a distributed function description table item in the calculation task based on the read data, stores an operation result into the message cache as data corresponding to the name of output data in the distributed function description table item in the calculation task, generates a new data response message based on the data response message in the calculation task and the operation result, and sends the new data response message to the data description table item to be processed.
In some optional embodiments, the method further comprises:
responding to the received data message by the forwarding routing table entry cache, and inquiring the output port information corresponding to the data name in the received data message in the forwarding routing table entry cache; responding to the finding, and sending the found output port information to the message packaging module; in response to not being found, the received data packet is discarded.
The applicant finds through practical analysis that in the conventional NDN network device, the forwarding of the packet does not involve content modification, so that the content of the packet is only statically stored in the network device, and the content of the data packet entering and exiting the network forwarding device is not substantially changed. However, with the development of edge computing, 5G (5th Generation mobile networks or 5th Generation wireless systems, 5 th-Generation), and internet of things, the location of mass data Generation and the location of processing are not natural. Data is likely to be generated on the end side, but the data can be processed only after being transmitted to the cloud side, valuable network bandwidth consumed by transmission and moving of a large amount of data is consumed, and meanwhile, the increase of processing delay caused by data transmission also becomes an obstacle for blocking service application and development.
In order to solve the above-mentioned defects in the prior art, the network forwarding device and the data forwarding method provided by the present disclosure add a distributed function description table entry cache and a data processing module in the network forwarding device, where the data processing module is respectively in communication connection with the packet cache, the to-be-processed data description table entry cache, and the distributed function description table entry cache is respectively in communication connection with the to-be-processed data description table entry cache, the data storage location table entry cache, the forwarding routing table entry cache, the packet encapsulation module, and the data processing module. The distributed function description table entry is cached in the cached distributed function description table entry, and the distributed function description table entry comprises at least one input data name, an operation function name and an output data name. And the data processing module is used for calculating the data stored in the message cache according to the preset calculation logic and sending the calculation result to the message cache for storage. The data content processing can be carried out in the data transmission process, and the forwarding efficiency and the intelligent level of the whole network can be obviously improved.
The network forwarding device and the data forwarding method can achieve the following technical effects:
1. by adopting the name of the data as the message identification and carrying out routing forwarding and table look-up processing according to the data, the problem of inflexibility of service support caused by the index of the traditional Internet by taking the IP address as the address (position) is solved, the mapping process of the IP address to the message content by an upper layer protocol is avoided, the system efficiency is improved, and the undifferentiated network service of any service type at any position becomes possible.
2. By caching the message with large capacity on the network forwarding equipment (network node) based on the data name, the service and the content are not required to be acquired from a place where the content is generated through a longer access path, especially for the content which needs to be read frequently, by adopting the scheme, the related content can be directly cached on the network node which is very close to the user, the network communication bandwidth cost is effectively reduced, and the network service with lower delay can be provided for the user.
3. By integrating the data processing module on the network forwarding equipment and according to the distributed function description table entry in the distributed function description table entry cache, the data processing is realized on the network forwarding equipment, and further, the distributed intra-network calculation is realized, so that the data can be processed in the network flow.
Drawings
Other features, objects and advantages of the disclosure will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
fig. 1 is a schematic block diagram of one embodiment of a network forwarding device according to the present disclosure;
fig. 2A is a flow diagram of one embodiment of a data forwarding method applied to a network forwarding device, according to the present disclosure;
fig. 2B is a flowchart of another embodiment of a data forwarding method applied to a network forwarding device according to the present disclosure.
Detailed Description
The present disclosure is described in further detail below with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that, in the present disclosure, the embodiments and features of the embodiments may be combined with each other without conflict. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 shows a schematic structural diagram of an embodiment of a network forwarding device according to the present disclosure.
As shown in fig. 1, the network forwarding device 100 may include a packet cache 101, a packet parsing module 102, a data storage location table entry cache 103, a to-be-processed data description table entry cache 104, a distributed function description table entry cache 105, a data processing module 106, a forwarding routing table entry cache 107, and a packet encapsulation module 108. Wherein:
the message parsing module 102 is respectively in communication connection with the message cache 101, the data storage location table entry cache 103, and the to-be-processed data description table entry cache 104.
The data processing module 106 is respectively connected in communication with the message cache 101, the to-be-processed data description table entry cache 104, and the distributed function description table entry cache 105.
The packet encapsulation module 108 is respectively connected in communication with the packet cache 101, the data storage location entry cache 103, the distributed function description entry cache 105, and the forwarding routing entry cache 107.
The data storage location table entry cache 103 is respectively in communication connection with the message cache 101, the distributed function description table entry cache 105 and the to-be-processed data description table entry cache 104.
The pending data description entry cache 104 is communicatively coupled to the distributed function description entry cache 105.
The distributed function depicts the table entry cache 105 and the forwarding routing table entry cache 107 in communicative connection.
The message cache 101 is configured to store the data message, add the data message to the data message at a storage location of the message cache 102, and send the data message to the message analysis module 102. For example, as shown in fig. 1, a data packet pkt _ in may enter the packet parsing module 101 from an o interface of the packet parsing module 101, and is sent to the packet cache 102 by the packet parsing module 101 through an interface p, the packet cache 102 stores the data packet pkt _ in the packet cache 102, writes a storage location of the data packet pkt _ in the packet cache 102 into a storage location field of the data packet pkt _ in, and then returns the data packet pkt _ in written into the storage location field to the packet parsing module 101 through the interface p.
In some optional embodiments, the message cache 101 may be a distributed cache. The distributed cache can enlarge the number of data messages which can be accessed by the message cache 101, so that the service and the content can be obtained without passing through a longer access path to a place where the content is generated, especially for the content which needs to be read frequently, the content can be directly cached in a network node which is very close to a user, the network communication bandwidth requirement is effectively reduced, and the network service with lower delay can be provided for the user.
The message parsing module 102 is configured to parse the data message to obtain description information of the data message. Here, the description information may include at least one of: data name, message type, message length, ingress port information, and storage location in the message cache. The message type is used for indicating whether the data message is a data request message or a data response message, and correspondingly, when the data message is the data request message, the data name can be a request data name; when the data packet is a data response packet, the data name may be a response data name. The message length may be the length of the data message, the ingress port information may be the port information from which the data message comes, and the storage location is the storage location of the data message in the message cache 101. The message parsing module 102 may transfer data to the data storage location entry cache 103 through an a interface, and may transfer data to the pending data description entry cache 104 through an b interface.
To implement the message parsing function, the message parsing module 102 may be implemented by a state machine circuit.
And the data storage location table entry cache 103 is used for caching a data storage location table entry, and the data storage location table entry may include a data name and a storage location of the data message stored in the message cache. That is, the cache data storage location table entry records a request data name or a response data name corresponding to the data packet stored in the packet cache 101 and a storage location of the corresponding data packet in the packet cache 101.
The to-be-processed data description entry cache 104 is configured to cache the to-be-processed data description entry, where the to-be-processed data description entry may include a data name and a corresponding ingress port information set in a data request packet that has been received by the network forwarding device 100 and does not return corresponding response data. That is, the pending data description entry cache 104 records the name of the data that has issued the data request but not responded to and from which port the data request came.
A distributed function description table entry cache 105 for caching distributed function description table entries, which may include at least one input data name, an operation function name, and an output data name. That is, the distributed function description entry describes an input parameter name, a function name, and an output parameter name required for performing data operations. The input parameter name and the output parameter name may correspond to a data name in a data response message or a data request message.
If the data name in the data request message is matched with the input parameter name in the description of the distributed function, it is indicated that the data requested by the data request message is actually the input parameter corresponding to the distributed function, that is, the data requested by the data request message can be used as the input parameter of the distributed function after the data response message corresponding to the data request message is returned.
If the data name in the data request message matches the output parameter name in the distributed function description, it indicates that the data requested by the data request message is the output parameter corresponding to the distributed function, and an operation result obtained by operating with the distributed function based on the input parameter corresponding to the distributed function may be used as the data requested by the data request message.
If the data name in the data response message is matched with the input parameter name in the distributed function description, it is indicated that the data responded by the data response message is the input parameter required by the distributed function, that is, after the data response messages corresponding to the input parameter of the distributed function are all returned, the operation is performed by using the distributed function based on the input parameter of the distributed function, and the result is returned as the data request message corresponding to the output parameter.
If the data name in the data response message is matched with the output parameter name in the distributed function description, the data responded by the data response message is the output parameter corresponding to the distributed function, and the data response message can be directly forwarded without calculating the data corresponding to the data response message.
The data processing module 106 is configured to perform operations on data stored in the message cache 101 according to a preset operation logic, and send an operation result to the message cache 101 for storage. Here, each preset operation logic may correspond to a corresponding operation function name in the distributed function description table entry stored in the distributed function description table entry cache 105. The instruction sequence corresponding to the preset operation logic may be stored in the data processing module 106, or may be stored in the distributed function description table entry cache 105. The data processing module 106 may be a module having functions of data processing, calculation, and computation.
In some optional embodiments, the data processing module 105 may include at least one of: a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), and a reconfigurable or heterogeneous Processing core.
The forwarding routing table entry cache 107 is configured to cache a routing table entry, which may include a data name and corresponding egress port information. That is, the routing table entry records which egress port different data is to be forwarded from. Here, the routing table entry cached in the forwarding routing table entry cache 107 may be specifically issued by an upper layer protocol stack or a network manager.
A packet encapsulation module 108, configured to encapsulate the data fetched from the packet cache 101 and send the encapsulated data to the egress port indicated by the egress port information received from the forwarding routing table entry cache 107.
To implement the message encapsulation function, the message encapsulation module 108 can be implemented by a state machine circuit.
In some optional embodiments, data storage location entry cache 103, forwarding routing entry cache 107, and distributed function description entry cache 105 may be TCAM (Ternary Content Addressable Memory) or RAM (Random Access Memory). When the TCAM is adopted, the method can realize accurate matching search and fuzzy matching search, and can improve the search efficiency.
The p interface for communication between the message parsing module 102 and the message cache 101, and the r interface for communication between the message cache 101 and the message encapsulation module 108 may be an AXI-Stream interface. The o interface of the input end of the message parsing module 102 and the s interface of the output end of the message encapsulation module 108 may also be AXI-Stream interfaces. While other interfaces shown in fig. 1, such as the following, may be bus interfaces:
the message analysis module 102 transmits data or signals to the a interface of the data storage location table entry cache 103;
the message analysis module 102 transmits data or signals to the b interface of the data description table entry cache 104 to be processed;
the distributed function describes a c-interface for the table entry cache 105 to transmit data or signals to the data storage location table entry cache 103;
the distributed function describes the d interface where the table entry cache 105 transfers data or signals to the forwarding routing table entry cache 107;
an e interface for transmitting data or signals to the data description table entry cache 104 to be processed by the data storage location table entry cache 103;
an f interface for transmitting data or signals to the data description table entry cache 104 to be processed by the distributed function description table entry cache 105;
a g interface for forwarding the data or signal transmitted from the routing table entry cache 107 to the message encapsulation module 108;
an h interface for transmitting data or signals from the data description table entry cache 104 to the data storage location table entry cache 103;
an i interface for transmitting data or signals to the message cache 101 by the data storage location table entry cache 103;
a j interface for transmitting data or signals to the message encapsulation module 108 by the data storage location table entry cache 103;
an m interface for transmitting data or signals to the message cache 101 by the data processing module 106;
the message cache 101 communicates n interfaces of data or signals to the data processing module 106.
As a main function of the network forwarding apparatus, a data forwarding operation is indispensable. To implement data forwarding, please refer to fig. 2A, fig. 2A shows a flow 200 of a data forwarding method applied to a network forwarding device according to the present disclosure. The process 200 may be applied to a network forwarding device as shown in fig. 1. The data forwarding operation flow 200 applied to the network forwarding device includes the following steps:
In this embodiment, the message cache 101 in the network forwarding device 100 may store the data message after receiving the data message, obtain the storage location of the data message in the message cache 101, write the storage location into the corresponding storage location field in the data message, and send the storage message written into the storage location to the message parsing module 102.
In some optional embodiments, the data packet received by the packet cache 101 may be received by the packet parsing module 102 from its packet input interface, i.e. the o interface, and forwarded to the packet cache 101.
In step 202, the message parsing module sends the data request message to the data storage location table entry cache in response to receiving the data request message.
Here, the message parsing module 102 may first parse the data message after receiving the data message. It should be noted that the message parsing module 102 may parse the data message to obtain the following information: message type, data name, ingress port information and storage location. The message types may include two types, a data request message type and a data response message type. That is, the message type is used to indicate whether the data message is a data request message or a data response message. When the data message is a data request message, the data name is the data name of the data requested by the data message, and when the data message is a data response message, the data name is the data name of the data carried or included by the data message. And ingress port information indicates from which ingress port the data message came. The storage location indicates a storage location of the data packet in the packet cache. If the data message is determined to be a data request message through the analysis, the data request message may be sent to the data storage location table entry cache 103 through the a interface.
Because the cache data storage location table entry records the request data name or the response data name corresponding to the data packet stored in the packet cache 101 and the storage location of the corresponding data packet in the packet cache 101, if it is determined that the request data name in the data request packet exists in the data storage location table entry cache, which indicates that the data requested by the data request packet is already stored in the packet cache 101, the process may go to step 204, where the data request packet is directly sent to the packet encapsulation module 108 for encapsulation and then sent out. On the contrary, if it is determined that the requested data name in the data request message does not exist in the data storage location table entry cache, which indicates that the message cache 101 does not have the data requested by the data request message, the process may go to step 206 to further determine whether the data requested by the data request message has been requested.
Here, the data storage location table entry cache may send the data request message to the message encapsulation module 108 through the j interface and go to step 205 to execute, when it is determined that the data requested by the data request message is already stored in the message cache 101.
In step 205, in response to receiving the data packet, the packet encapsulation module reads the packet from the packet cache according to the storage location in the received data packet, encapsulates the packet into a data response packet, and sends the data response packet to the target egress port.
Here, the message encapsulation module 108 may, after receiving a data message (e.g., a data request message or a data response message), read a message from the message cache 101 through the r interface according to a storage location in the received data message, encapsulate the message into a data response message, and then send the data response message to the target egress port through the s interface, thereby completing a data forwarding operation on the data message. The target egress port is an egress port indicated by egress port information corresponding to the received data packet, which is received by the packet encapsulation module 108 from the forwarding routing table entry cache 107.
In step 206, the data storage location table entry cache sends the data request message to the pending data description table entry cache.
Here, the data storage location entry cache 103 may send the data request message to the pending data description entry cache 104 through the e interface in case that it is determined that there is no data requested by the data request message in the message cache 101, so as to further determine whether the data requested by the data request message has been requested.
Since the data name that has sent the data request but has not received a response and which port the data request comes from are recorded in the pending data description table entry cache 104, if it is determined that the request data name in the data request message exists in the pending data description table entry cache 104, which indicates that the data requested by the data request message has been requested and forwarded, but the corresponding data response message has not been returned, step 208 may be performed to record that the ingress port corresponding to the data request message also requests the corresponding data of the data request message in the pending data description table entry cache 104.
On the contrary, if it is determined that the requested data name in the data request message does not exist in the pending data description table entry cache 104, which indicates that the data request message is received for the first time, then the process goes to step 209 to further determine whether the data requested by the data request message needs to be obtained after the operation.
Here, it may be determined in step 207 that the data requested by the data request packet has been requested and forwarded, and only if the corresponding data response packet has not been returned, the requested data response packet is continuously waited, and the ingress port information in the data request packet is added to the ingress port information set corresponding to the request data name in the data request packet in the to-be-processed data description entry cache 104, and may be forwarded to each ingress port requesting the data corresponding to the data response packet after a subsequent corresponding data response packet is returned. Since the port entry information in the data request message is recorded, the data request message can be discarded only by waiting for the corresponding data response message.
Here, in step 207, when determining that the data request message is received for the first time, the pending data description entry cache 104 may send the data request message to the distributed function description entry cache 105 through the f interface, so as to further determine whether the data requested by the data request message needs to be obtained after operation.
Since the distributed function description table entry is stored in the distributed function description table entry cache 105, the distributed function description table entry may include at least one input data name, an operation function name, and an output data name.
If the distributed function description table entry matching the output data name with the request data name in the data request message is found in the distributed function description table entry cache 105, it indicates that the data requested by the data request message needs to be subjected to the function operation corresponding to the found distributed function description table entry, and the corresponding operation result is the data requested by the data request message. In order to perform the function operation, it is necessary to first obtain data corresponding to the input parameters required by the function operation, and therefore, the process goes to step 211 to generate a new data request message requesting corresponding data parameters.
If the distributed function description table entry matching the output data name with the request data name in the data request message is not found in the distributed function description table entry cache 105, it indicates that the data requested by the data request message does not need to be operated, that is, the data request message is not stored in the message cache of the network forwarding device 100, the data request message is received for the first time, and the data requested by the data request message does not need to be operated, it indicates that the data request message needs to be forwarded, and the data requested by the data request message is requested to the forwarded target network node. In this case, step 212 may be transferred to query forwarding routing table entry cache 107 for the egress port to which the data request message should be forwarded.
Here, the distributed function description table entry cache 105 may generate a new data request packet requesting data corresponding to each input data name in the distributed function description table entry looked up in step 210, and send each generated data request packet to the data storage location table entry cache 103 through the c interface. Further, step 207 may be returned, that is, the to-be-processed data description entry cache 104 may determine, in response to receiving the new data request packet generated in step 211, whether a request data name in the new data request packet exists in the to-be-processed data description entry cache 104, and the execution of subsequent other corresponding steps may be based on the new data request packet, and finally, the data response packet corresponding to the data corresponding to each input data name in the distributed function description entry found in step 210 is stored in the packet cache 101.
Here, if it is determined in step 210 that the data requested by the data request packet is not stored in the packet cache 101 of the network forwarding device 100, the data request packet is received for the first time, and the data requested by the data request packet does not need to be operated, it indicates that the data request packet needs to be forwarded to request the data requested by the data request packet from other network nodes, so that the distributed function description table entry cache 105 may send the data request packet to the forwarding routing table entry cache 107 through the d interface.
Since the forwarding routing table entry cache 107 stores routing table entries, which egress port different data is to be forwarded from is recorded in the routing table entry, the forwarding routing table entry cache 107 may query egress port information corresponding to the data name in the received data packet. It can be understood that, if the forwarding routing table entry cache 107 receives a data request message, it queries the egress port information corresponding to the requested data name in the data request message. If the forwarding routing table entry cache 107 receives the data response message, the queried egress port information corresponding to the response data name in the data response message.
If the egress port information is found, it indicates that the data packet received by the forwarding routing table entry cache 107 specifies an egress port to be forwarded, and the process may go to step 214.
If the egress port information is not found, it indicates that the data packet received by the forwarding routing table entry cache 107 does not specify the egress port to be forwarded, and the process may go to step 215.
Here, if the forwarding routing table entry cache 107 finds the egress port information, the found egress port information may be sent to the packet encapsulation module 108 through the g interface. Further, the message encapsulation module 108
In response to not being found, step 215, discards the received data packet.
Here, if the egress port information is not found in the forwarding routing table entry cache 107, the received data packet may be discarded. Optionally, preset error information may also be reported.
Through the steps 201 to 215, the data request message can be forwarded if the requested data does not need to be processed by calculation. And if the operation processing is required, generating a data response message corresponding to the input parameter required by the operation processing. And then, the method is ready for carrying out operation and returning the operation result after the data of the subsequent parameters to be input all arrive.
In some optional embodiments, the above flow 200 may further include the following steps 216 to 227 as shown in fig. 2B, and it should be noted that the flow 200 shown in fig. 2B may further include the steps 201 to 215 shown in fig. 2A.
In step 216, the message parsing module sends the data response message to the to-be-processed data description table entry cache in response to receiving the data response message.
Here, the message parsing module 102 may parse the data message after receiving the data message. If the analyzed message type is corresponding to the data response message, it indicates that the data response message is requested by the input port. To determine which ingress ports have requested the data response message, the message parsing module 102 may send the data response message to the pending data description table entry cache 104 through the b interface. And analyzing the data response message can also obtain: responding data name, data name needed by operation, input port information and storage position in message buffer.
Since the data name that has sent the data request but has not obtained a response and which port the data request comes from are recorded in the pending data description table entry cache 104, if it is determined that the response data name in the data response message exists in the pending data description table entry cache 104, which indicates that the data response message matches with at least one data request message previously recorded in the pending data description table entry cache 104, that is, at least one ingress port has requested the data response message and has not obtained corresponding response data, the process may go to step 221 to notify the data storage location table entry cache 103 to accept the received data response message.
If it is determined that the response data name in the data response message does not exist in the to-be-processed data description entry cache 104, indicating that the data response message has not been requested by any ingress port, step 218 may be performed to notify the data storage location entry cache 103 not to accept storage of the data response message, release the space occupied by the data response message, and report an exception to the network manager.
Here, if it is determined in step 217 that the data response packet has not been requested by any ingress port, the pending data description table entry cache 104 may send a second signal and the data response packet to the data storage location table entry cache 103 through the h-interface.
In step 219, the data storage location table entry cache sends a third signal and a data response message to the message cache in response to receiving the second signal and the data response message.
Data storage location table entry cache 103 may send a third signal and data response message to message cache 101 via the i interface in response to receiving the second signal and data response message.
Here, the message cache 101 may release the space occupied by the data response message in response to receiving the third signal and the data response message, that is, after the data storage location table entry cache receives the second signal and the data response message, the storage of the data response message is not accepted, and the space already occupied by the data response message is released. Optionally, the data storage location table entry cache 103 may also report an exception to the network manager after receiving the second signal and the data response message. Or, the message cache 101 may report an exception to the network manager in response to receiving the third signal and the data response message.
Here, if it is determined in step 217 that at least one ingress port has requested the data response packet and has not obtained corresponding response data, the pending data description table entry cache may send a first signal and a data response packet to the data storage location table entry cache 103 through the h interface, so as to notify the data storage location table entry cache 103 of receiving the received data response packet.
It should be noted that the first signal and the second signal may be different signals to distinguish the data storage location table entry buffer.
In step 222, in response to receiving the first signal and the data response message and in response to determining that the data response message is correct, the data storage location table entry cache generates and stores the data storage location table entry into the data storage location table entry cache using the response data name and the storage location in the data response message, and sends the data response message to the distributed function description table entry cache.
Here, after receiving the first signal and the data response message, the data storage location table entry cache 103 may first determine whether the data response message is correct, for example, various checks may be performed on the data response message in order to receive the data response message. If the determination is correct, a data storage location table entry may be generated by using the response data name and the storage location in the data response message and stored in the data storage location table entry cache 103, and the data response message may be sent to the distributed function description table entry cache 105 to determine whether to perform calculation on the data in the data response message.
In step 223, in response to receiving the data response message, the distributed function description table entry cache queries the distributed function description table entry in which the output data name matches the response data name in the data response message.
Here, if the distributed function description table entry matching the output data name with the response data name in the data response message is found in the distributed function description table entry cache, it indicates that the data corresponding to the data response message is the output parameter corresponding to the found distributed function table entry, and the data corresponding to the data response message does not need to be calculated, and the step 224 may be switched to, so that the message encapsulation module 108 may forward the data response message.
If the distributed function description table entry matching the output data name with the response data name in the data response message is not found in the distributed function description table entry cache, the process further goes to step 225 to determine whether the data corresponding to the response data message is the operation data required by other data request messages.
Here, the distributed function description entry cache 105 may send the data response message to the message encapsulation module 108 through the k interface in the case that it is determined in step 223 that the calculation of the data in the data response message is not needed. Further, the message encapsulation module may execute step 205 to read a message from the message cache according to the storage location in the received data response message, encapsulate the message into a new data response message, and send the new data response message to the target egress port, where the target egress port is an egress port indicated by the egress port information corresponding to the data response message and received by the message encapsulation module 108 from the forwarding routing table entry cache 107.
Here, in the case that the distributed function description entry cache 105 determines that the calculation of the data in the data response message is not needed in step 223, the distributed function description entry cache 105 may query the distributed function description entry whose input data name includes the response data name in the data response message.
If the query indicates that the data corresponding to the data response packet corresponds to the input parameter in the searched distributed function expression entry and the data corresponding to the data response packet needs to be calculated by using the searched distributed function, the process may go to step 226 for further execution.
In step 226, the distributed function description table entry cache sends the found storage locations in the distributed function description table entry and the data response message to the data processing module as a calculation task.
Here, if it is determined in step 225 that the data corresponding to the data response packet needs to be operated by using the found distributed function, the found distributed function description entry and the storage location in the data response packet may be sent to the data processing module 106 as a calculation task through the q interface, so as to implement operation on the data corresponding to the data response packet.
The data processing module 106 may perform the following in response to receiving a computing task:
first, the computational task is examined. For example, the checking the completeness of the domain may specifically include: and calculating whether the input parameters required by the operation function corresponding to the operation function name in the distributed function description table entry in the task are in the message cache 101, whether the data types required by the input parameters are matched with the data types of the corresponding data in the message cache 101, and the like.
Secondly, if the computing task is checked to pass, data can be read from the message cache 101 through the n interface according to the storage position in the computing task.
And then, executing an instruction sequence corresponding to the operation function name in the distributed function description table entry in the calculation task based on the read data. That is, the corresponding instruction sequence described above is executed with the read data as an input parameter.
And then, storing the operation result as data corresponding to the name of the output data in the distributed function description table entry in the calculation task into the message cache 101 through the m interface.
Finally, a new data response message is generated based on the data response message in the calculation task and the calculation result, and the new data response message is sent to the data description table entry cache 104 to be processed through the t interface. In this way, the pending data description entry cache 104 may continue to perform step 217 and corresponding subsequent steps to further determine which ports have requested the new data response packet, and so on, which is not described herein again. For example, if at least one ingress port has requested the new data response packet and has not obtained corresponding response data, the pending data description table entry cache 104 may send a first signal and a data response packet to the data storage location table entry cache 103 through the h interface, so as to notify the data storage location table entry cache 103 to accept the received data response packet, and the like.
The network forwarding device and the data forwarding method provided by the above embodiments of the present disclosure may achieve the following technical effects, including but not limited to:
1. by adopting the name of the data as the message identification and carrying out routing forwarding and table look-up processing according to the data, the problem of inflexibility of service support caused by the index of the traditional Internet by taking the IP address as the address (position) is solved, the mapping process of the IP address to the message content by an upper layer protocol is avoided, the system efficiency is improved, and the undifferentiated network service of any service type at any position becomes possible.
2. By caching the message with large capacity on the network forwarding equipment (network node) based on the data name, the service and the content are not required to be acquired from a place where the content is generated through a longer access path, especially for the content which needs to be read frequently, by adopting the scheme, the related content can be directly cached on the network node which is very close to the user, the network communication bandwidth cost is effectively reduced, and the network service with lower delay can be provided for the user.
3. By integrating the data processing module on the network forwarding device and according to the distributed function description table entry in the distributed function description table entry cache, the data processing is realized on the network forwarding device, so that distributed intra-network calculation is realized, and the data can be processed in the network flow.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention in the present disclosure is not limited to the specific combination of the above-mentioned features, but also encompasses other embodiments in which any combination of the above-mentioned features or their equivalents is possible without departing from the inventive concept as defined above. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Claims (10)
1. A network forwarding device comprising: a message cache, a message parsing module, a data storage location table entry cache, a to-be-processed data description table entry cache, a distributed function description table entry cache, a data processing module, a forwarding routing table entry cache and a message encapsulation module, wherein the message parsing module is respectively in communication connection with the message cache, the data storage location table entry cache and the to-be-processed data description table entry cache, the data processing module is respectively in communication connection with the message cache, the to-be-processed data description table entry cache and the distributed function description table entry cache, the message encapsulation module is respectively in communication connection with the message cache, the data storage location table entry cache, the distributed function description table entry cache and the forwarding routing table entry cache, and the data storage location table entry cache is respectively in communication connection with the message cache, the distributed function description table entry cache and the to-be-processed data description table entry cache, the data description table entry cache to be processed is communicatively connected to the distributed function description table entry cache, and the distributed function description table entry cache is communicatively connected to the forwarding routing table entry cache, where:
the message cache is used for storing data messages, adding the data messages to the data messages at the storage position of the message cache and then sending the data messages to the message analysis module;
the message analysis module is configured to analyze a data message to obtain description information of the data message, where the description information includes at least one of the following: data name, message type, message length, ingress port information and storage location in the message cache;
the data storage location table entry cache is used for caching a data storage location table entry, wherein the data storage location table entry comprises a data name and a storage location of a data message stored in the message cache;
the to-be-processed data description table entry cache is used for caching the to-be-processed data description table entry, wherein the to-be-processed data description table entry comprises a data name and a corresponding ingress port information set in a data request message which is received by the network forwarding equipment and does not return corresponding response data;
the distributed function description table entry cache is used for caching the distributed function description table entry, and the distributed function description table entry comprises at least one input data name, an operation function name and an output data name;
the data processing module is used for calculating the data stored in the message cache according to a preset operation logic and sending an operation result to the message cache for storage;
the forwarding routing table entry cache is used for caching a routing table entry, and the routing table entry comprises a data name and corresponding output port information;
and the message encapsulation module is used for encapsulating the data taken out from the message cache and then sending the encapsulated data to the output port indicated by the output port information received from the forwarding routing table entry cache.
2. The network forwarding device of claim 1, wherein the data processing module comprises at least one of: a Central Processing Unit (CPU), a Graphics Processing Unit (GPU) and a reconstruction or heterogeneous processing core.
3. The network forwarding device of claim 1, wherein the data storage location entry cache, the forwarding routing entry cache, and the distributed function description entry cache are ternary content addressable memory or random access memory.
4. The network forwarding device of claim 1, wherein the packet cache is a distributed cache.
5. The network forwarding device of claim 1, wherein the routing table entry is a routing table entry issued by an upper protocol stack or a network manager.
6. The network forwarding device of claim 1, wherein the packet parsing module and the packet encapsulation module are state machine circuits.
7. The network forwarding device of claim 1, wherein the message parsing module and the message cache and the message encapsulation module are communicatively connected via an AXI-Stream interface, and an input of the message parsing module and an output of the message encapsulation module are AXI-Stream interfaces.
8. A data forwarding method applied to the network forwarding device according to any one of claims 1 to 7, the method comprising:
the message cache stores data messages, and the data messages are added to the data messages at the storage position of the message cache and then sent to the message analysis module;
the message analysis module responds to the received data request message, and sends the data request message to the data storage location table entry cache, wherein the data request message comprises: requesting a data name, ingress port information and a storage location in the message cache;
the data storage position table entry cache responds to the received data request message and determines whether a request data name in the data request message exists in the data storage position table entry cache or not; in response to determining that the data request message exists, sending the data request message to the message encapsulation module; responding to the data request message and sending the data request message to the to-be-processed data description table entry cache;
the message encapsulation module reads a message from the message cache according to the storage position in the received data message in response to the received data message, encapsulates the message into a data response message and sends the data response message to a target output port, wherein the target output port is an output port indicated by output port information corresponding to the received data message and received by the message encapsulation module from the forwarding routing table entry cache;
responding to the received data request message by the to-be-processed data description table entry cache, and determining whether a request data name in the data request message exists in the to-be-processed data description table entry cache or not; in response to determining that the data request message does not exist, sending the data request message to the distributed function description table entry cache; in response to determining that the request message exists, adding ingress port information in the data request message to an ingress port information set corresponding to a request data name in the data request message in the to-be-processed data description table entry cache, and discarding the data request message;
the distributed function description table entry cache responds to the received data request message, and inquires a distributed function description table entry matching the output data name with the request data name in the data request message in the distributed function description table entry cache; responding to the data request message which is not found, and sending the data request message to the forwarding routing table entry cache; and responding to the searching, generating a new data request message for requesting data corresponding to each input data name in the searched distributed function description table item, and sending each generated data request message to the data storage position table item cache.
9. The method of claim 8, wherein the method further comprises:
the message analysis module responds to the received data response message, and sends the data response message to the to-be-processed data description table entry cache, wherein the data response message comprises: responding to a data name, a data name required by operation, input port information and a storage position in the message cache;
responding to the received data response message by the to-be-processed data description table entry cache, and determining whether a response data name in the data response message exists in the to-be-processed data description table entry cache or not; responding to the determination of existence, and sending a first signal and the data response message to the data storage position table entry cache; responding to the data storage position table entry cache and sending a second signal and the data response message in response to the determination of absence;
the data storage location table entry cache responds to the first signal and the data response message and determines that the data response message is correct, generates a data storage location table entry by using a response data name and a storage location in the data response message, stores the data storage location table entry into the data storage location table entry cache, and sends the data response message to the distributed function description table entry cache;
the data storage location table entry cache sends a third signal and the data response message to the message cache in response to receiving the second signal and the data response message;
the message cache responds to the third signal and the data response message and releases the space occupied by the data response message;
the distributed function description table entry cache responds to the received data response message, and inquires a distributed function description table entry of which the output data name is matched with the response data name in the data response message in the distributed function description table entry cache; responding to the inquiry, and sending the data response message to the message packaging module; in response to the query, querying a distributed function description table entry of which the input data name comprises a response data name in the data response message in the distributed function description table entry cache; responding to the query, and sending the searched distributed function description table entry and the storage position in the data response message to the data processing module as a calculation task;
the data processing module responds to the received calculation task and checks the calculation task, reads data from the message cache according to the storage position in the calculation task, executes an instruction sequence corresponding to the name of an operation function in a distributed function description table item in the calculation task based on the read data, stores an operation result into the message cache as data corresponding to the name of output data in the distributed function description table item in the calculation task, generates a new data response message based on the data response message in the calculation task and the operation result, and sends the new data response message to the data description table item to be processed.
10. The method of claim 9, wherein the method further comprises:
responding to the received data message by the forwarding routing table entry cache, and inquiring the output port information corresponding to the data name in the received data message in the forwarding routing table entry cache; responding to the finding, and sending the found output port information to the message packaging module; in response to not being found, the received data packet is discarded.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110338373.XA CN113114575A (en) | 2021-03-26 | 2021-03-26 | Network forwarding device and data forwarding method |
| CN202210059131.1A CN114363240B (en) | 2021-03-26 | 2022-01-19 | Network forwarding device and data forwarding method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110338373.XA CN113114575A (en) | 2021-03-26 | 2021-03-26 | Network forwarding device and data forwarding method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113114575A true CN113114575A (en) | 2021-07-13 |
Family
ID=76713111
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110338373.XA Pending CN113114575A (en) | 2021-03-26 | 2021-03-26 | Network forwarding device and data forwarding method |
| CN202210059131.1A Active CN114363240B (en) | 2021-03-26 | 2022-01-19 | Network forwarding device and data forwarding method |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210059131.1A Active CN114363240B (en) | 2021-03-26 | 2022-01-19 | Network forwarding device and data forwarding method |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN113114575A (en) |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103620576B (en) * | 2010-11-01 | 2016-11-09 | 七网络公司 | It is applicable to the caching of mobile applications behavior and network condition |
| CN104410655B (en) * | 2014-09-26 | 2018-02-09 | 清华大学 | The storage system and method for distributed network based on naming mechanism |
| CN108322343A (en) * | 2018-02-05 | 2018-07-24 | 西安电子科技大学 | Web monitoring devices and method based on distributed SNMP |
| CN110191148B (en) * | 2019-03-29 | 2020-11-03 | 中国科学院计算技术研究所 | Statistical function distributed execution method and system for edge calculation |
-
2021
- 2021-03-26 CN CN202110338373.XA patent/CN113114575A/en active Pending
-
2022
- 2022-01-19 CN CN202210059131.1A patent/CN114363240B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN114363240B (en) | 2023-11-21 |
| CN114363240A (en) | 2022-04-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3320670B1 (en) | Method and apparatus for pushing data in a content-centric networking (ccn) network | |
| JP4556761B2 (en) | Packet transfer device | |
| US20150350078A1 (en) | Flow-driven forwarding architecture for information centric networks | |
| CN108737278A (en) | A kind of look-up method and device | |
| CN113556413A (en) | Message processing method and device | |
| CN113946587A (en) | Handle identifier analysis caching method, query method and handle identifier analysis system | |
| CN114363240B (en) | Network forwarding device and data forwarding method | |
| CN115996203B (en) | Network traffic domain division method, device, equipment and storage medium | |
| CN115834472B (en) | Message processing method, forwarding strategy acquisition method and device | |
| CN109309711B (en) | Virtual cache sharing method and system | |
| CN117714372A (en) | Data message forwarding method and device and network equipment | |
| CN114697347B (en) | Data transmission system with network memory capacity | |
| US20030061337A1 (en) | Data transfer scheme using caching technique for reducing network load | |
| WO2018233579A1 (en) | Information centric networking over multi-access network interfaces | |
| US7653070B2 (en) | Method and system for supporting efficient and cache-friendly TCP session lookup operations based on canonicalization tags | |
| CN111125493B (en) | High-speed data query system and method based on protocol non-perception forwarding | |
| CN112688880A (en) | Method for reducing redundant data packet transmission in named data network | |
| CN114157684A (en) | Message processing method, device and storage medium | |
| CN107196985B (en) | Data management method and device and network equipment | |
| CN114827655B (en) | Content storing and forwarding method and device, electronic equipment and storage medium | |
| US11882039B1 (en) | UDF-based traffic offloading methods and systems | |
| CN110399539B (en) | Data processing method, device and computer readable storage medium | |
| CN118972366A (en) | IP transparent transmission method, equipment and computer readable medium | |
| CN115941602A (en) | Message processing method, system, device and storage medium | |
| CN115002039A (en) | Traffic unloading method and system based on UDF |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20210713 |
|
| WD01 | Invention patent application deemed withdrawn after publication |