CN110830477B - Service identification method, device, gateway, system and storage medium - Google Patents
Service identification method, device, gateway, system and storage medium Download PDFInfo
- Publication number
- CN110830477B CN110830477B CN201911097395.0A CN201911097395A CN110830477B CN 110830477 B CN110830477 B CN 110830477B CN 201911097395 A CN201911097395 A CN 201911097395A CN 110830477 B CN110830477 B CN 110830477B
- Authority
- CN
- China
- Prior art keywords
- service
- gateway
- packet message
- packet
- state
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
Abstract
The application provides a service identification method, a service identification device, a gateway, a service identification system and a storage medium. The method is applied to a first gateway connected with a first network device and a second network device, wherein the first network device and the second network device are also connected with the second gateway, and the method comprises the following steps: acquiring a non-first packet message of a service sent by a second network device to a first network device through a first gateway; acquiring relevant information of a service, wherein the relevant information is generated by a second gateway based on an acquired first packet message of the service; when the related information indicates that the first gateway cannot process the non-first packet message, the non-first packet message is forwarded to the second gateway, so that the service can be processed normally when the first gateway cannot process the non-first packet message, and the data of the service can be processed normally under the HA environment.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, a gateway, a system, and a storage medium for identifying a service.
Background
In an HA (High Available) environment for data forwarding, multiple forwarding devices are usually required to forward a data stream of a service in order to achieve load balancing. For example, after the platform a sends data of a service X to the platform B through the security gateway a, the platform B returns the data of the service X to the platform a through the security gateway B.
However, in this way, some problems may sometimes be encountered, for example, in the case that the service X can only be processed by the security gateway a, if the service X is sent to the security gateway B, the security gateway B may not correctly process the data of the service X, and thus the service is affected.
Disclosure of Invention
An object of the embodiments of the present application is to provide a method, an apparatus, a gateway, a system, and a storage medium for identifying a service, so as to ensure that data of the service can be normally processed in an HA environment.
In a first aspect, an embodiment of the present application provides a service identification method, which is applied to a first gateway connected to a first network device and a second network device, where the first network device and the second network device are further connected to the second gateway, and the method includes:
acquiring a non-first packet message of a service sent by the second network equipment to the first network equipment through the first gateway;
acquiring related information of the service, wherein the related information is generated by the second gateway based on the acquired first packet message of the service;
and when the related information indicates that the first gateway cannot process the non-first packet message, forwarding the non-first packet message to the second gateway.
In this embodiment, after the second gateway obtains the first packet of the service, the second gateway can analyze the relevant information of the service based on the first packet of the service and synchronize the relevant information to the first gateway. Therefore, when the first gateway acquires the non-first packet message of the service, the first gateway can determine whether the first gateway can not process the non-first packet message based on the relevant information. If the relevant information indicates that the first gateway cannot process the non-first packet message, the first gateway forwards the non-first packet message to the second gateway for processing so as to ensure that the service can be processed normally when the first gateway cannot process the non-first packet message, and thus, the data of the service can be processed normally under the HA environment.
With reference to the first aspect, in a first possible implementation manner, the acquiring related information of the service includes:
and acquiring the state of the service, wherein the state comprises an unidentified state which indicates that the first gateway cannot process the non-first packet message.
In this embodiment of the application, when the second gateway does not recognize the service based on the first packet message, if the first gateway directly forwards the non-first packet message of the service to the destination device, the second gateway may not recognize the service, and then the second gateway may not execute a corresponding management policy for the service, so that the service may not be processed normally. Therefore, when the unidentified state indicates that the first gateway cannot process the non-first packet message, the first gateway can forward the non-first packet message to the second gateway, so that the second gateway can identify the service based on the non-first packet message, and the service can be processed normally.
With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner, the acquiring the state of the service includes:
and determining the service state associated with the address carried in the non-first packet message from the preset service states, wherein the associated service state is the service state.
In the embodiment of the application, because the association between the service state and the address is established in advance, the state of the service corresponding to the non-first packet message can be quickly determined based on the association.
With reference to the second possible implementation manner of the first aspect, in a third possible implementation manner, before determining, from preset service states, a service state associated with an address carried in the non-first packet message, the method further includes:
receiving the address carried in the first packet message sent by the second gateway, and receiving the state of the service sent by the second gateway;
associating the address with the state of the service.
In the embodiment of the application, because the states of the address and the service are synchronized by the second gateway, the association between the address and the service can be quickly and conveniently established.
With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation manner, a first service entry and a second service entry are preset in the second gateway, where the first service entry is used to record information required for processing a service that needs to be processed by the first gateway, and the second service entry is used to record data sent by the second gateway, and the associating the address with the state of the service includes:
establishing association between the address and the state of the service in the second service table entry;
correspondingly, determining the service state associated with the address carried in the non-first packet message from the preset service states includes:
determining that the address is not recorded in the first service table entry;
and determining the address from the second service table entry, and determining the service state associated with the address from the service states recorded by the second service table entry.
In the embodiment of the application, since the first service table entry records information required for processing the service that can be processed by the first gateway, when the non-first packet message is acquired, traversing the first service table entry first can ensure the processing efficiency of the service for the first time.
With reference to the first possible implementation manner of the first aspect, in a fifth possible implementation manner, after forwarding the non-first packet to the second gateway for processing, the method further includes:
receiving the latest state of the service sent by the second gateway, wherein the latest state is determined by the second gateway based on the first packet message and the non-first packet message;
and correspondingly updating the state of the service by utilizing the latest state.
In the embodiment of the application, the first gateway can update the state of the service in real time by synchronizing the latest state of the service to the first gateway, so that the first gateway can process the service by using the latest state of the service at any time.
With reference to the first possible implementation manner of the first aspect, in a sixth possible implementation manner, after obtaining the state of the service, the method further includes:
and when the state is the identification state, directly forwarding the non-first packet message to the first network equipment.
In this embodiment, if the service status is an identification status, which indicates that the second gateway has identified the service, the first gateway does not need to forward the non-first packet to the second gateway. Therefore, the first gateway can directly forward the non-first packet message to the first network equipment, so as to realize efficient forwarding.
With reference to the first aspect, in a seventh possible implementation manner, the acquiring related information of the service includes:
and acquiring the type of the management strategy for processing the service, wherein the type of the management strategy not comprising the first gateway configuration in the type indicates that the first gateway can not process the non-first packet message.
In this embodiment of the present application, if the management policy of the service is not configured on the first gateway, the first gateway cannot normally process the non-first packet message of the service. Therefore, the first gateway can forward the non-first packet message of the service to the second gateway capable of processing the service, so as to ensure that the service can be processed normally.
With reference to the seventh possible implementation manner of the first aspect, in an eighth possible implementation manner, after obtaining the type of the management policy for processing the service, the method further includes:
and when the first gateway is determined to be configured with the type of management strategy, processing the non-first packet message by using the management strategy.
In this embodiment of the present application, if the first gateway is configured with a management policy for configuring the service, the first gateway may directly process the non-first packet of the service, so as to implement efficient processing of the service.
In a second aspect, an embodiment of the present application provides a service identification method, which is applied to a second gateway connected to a first network device and a second network device, where the first network device and the second network device are further connected to the first gateway, and the method includes:
acquiring a data message sent by the first network equipment to the second network equipment;
when the data message belongs to a first packet message of a service, generating related information of a non-first packet message for indicating whether the first gateway can process the service;
synchronizing the relevant information to the first gateway;
receiving the non-first packet message forwarded by the first gateway, wherein the second gateway receiving the non-first packet message indicates that the first gateway determines that the first gateway cannot process the non-first packet message based on the relevant information;
and processing the non-first packet message.
With reference to the second aspect, in a first possible implementation manner, generating relevant information used for indicating whether the first gateway can process a non-first packet of the service includes:
generating the related information for representing the state of the service, wherein the state is an unidentified state.
With reference to the second aspect, in a first possible implementation manner, the processing the non-first packet includes:
and identifying the service by using the first packet message and the non-first packet message.
With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner, after identifying the service by using the first packet and the non-first packet, the method further includes:
updating the state of the service to an identification state;
and synchronizing the service state as the identification state to the first gateway, so that after the first gateway receives a new non-first packet message of the service sent to the first network equipment by the second network equipment through the first gateway, the first gateway directly forwards the new non-first packet message to the first network equipment.
With reference to the second aspect, in a third possible implementation manner, the generating related information used for indicating whether the first gateway can process the non-first packet of the service includes:
generating the related information for indicating the type of the management policy of the service, wherein the type of the management policy configured by the first gateway is not included in the type.
In a third aspect, an embodiment of the present application provides an apparatus for identifying a service, where the apparatus is applied to a first gateway connected to a first network device and a second network device, and the first network device and the second network device are further connected to the second gateway, and the apparatus includes:
the data receiving and sending module is used for acquiring a non-first packet message of a service sent to the first network equipment by the second network equipment through the first gateway;
the data processing module is used for acquiring relevant information of the service, wherein the relevant information is generated by the second gateway based on the acquired first packet message of the service;
the data transceiver module is further configured to forward the non-first packet message to the second gateway when the relevant information indicates that the first gateway cannot process the non-first packet message.
With reference to the third aspect, in a first possible implementation manner,
the data processing module is configured to acquire a state of the service, where the state includes an unidentified state, and the unidentified state indicates that the first gateway cannot process the non-first packet.
With reference to the first possible implementation manner of the third aspect, in a second possible implementation manner,
and the data processing module is used for determining the address-associated service state carried in the non-first packet message from all preset service states, wherein the associated service state is the service state.
With reference to the second possible implementation manner of the third aspect, in a third possible implementation manner, before the data processing module determines, from preset service states, a service state associated with an address carried in the non-first packet message,
the data transceiver module is further configured to receive the address carried in the first packet message sent by the second gateway, and receive the state of the service sent by the second gateway;
the data processing module is further configured to associate the address with the state of the service.
With reference to the third possible implementation manner of the third aspect, in a fourth possible implementation manner, a first service table entry and a second service table entry are preset in the second gateway, where the first service table entry is used to record information required for processing a service that needs to be processed by the first gateway, the second service table entry is used to record data sent by the second gateway,
the data processing module is configured to establish association between the address and the state of the service in the second service table entry;
correspondingly, the data processing module is configured to determine that the address is not recorded in the first service table entry; and determining the address from the second service table entry, and determining the service state associated with the address from the service states recorded by the second service table entry.
With reference to the first possible implementation manner of the third aspect, in a fifth possible implementation manner, after the data transceiver module forwards the non-first packet to the second gateway for processing,
the data transceiver module is further configured to receive a latest state of the service sent by the second gateway, where the latest state is determined by the second gateway based on the first packet message and the non-first packet message;
and the data processing module is also used for correspondingly updating the state of the service by utilizing the latest state.
With reference to the first possible implementation manner of the third aspect, in a sixth possible implementation manner, after the data processing module obtains the state of the service,
the data transceiver module is further configured to directly forward the non-first packet message to the first network device when the status is an identification status.
With reference to the third aspect, in a seventh possible implementation manner, the acquiring related information of the service includes:
the data processing module is configured to acquire a type of a management policy for processing the service, where the type that does not include the management policy configured by the first gateway indicates that the first gateway cannot process the non-first packet.
With reference to the seventh possible implementation manner of the third aspect, in an eighth possible implementation manner, after the data processing module obtains the type of the management policy for processing the service, the method further includes:
the data processing module is further configured to, when it is determined that the first gateway is configured with the type of management policy, process the non-first packet using the management policy.
In a fourth aspect, an embodiment of the present application provides an apparatus for identifying a service, where the apparatus is applied to a second gateway connected to a first network device and a second network device, where the first network device and the second network device are further connected to the first gateway, and the apparatus includes:
a data transceiver module, configured to acquire a data packet sent by the first network device to the second network device;
a data processing module, configured to generate, when the data packet belongs to a first packet of a service, related information used for indicating whether the first gateway can process a non-first packet of the service;
the data transceiver module is further configured to synchronize the relevant information to the first gateway; receiving the non-first packet message forwarded by the first gateway, wherein the second gateway receiving the non-first packet message indicates that the first gateway determines that the first gateway cannot process the non-first packet message based on the relevant information;
the data processing module is further configured to process the non-first packet message.
With reference to the fourth aspect, in a first possible implementation manner, the method includes:
generating the related information for representing the state of the service, wherein the state is an unidentified state.
With reference to the fourth aspect, in a first possible implementation manner, the processing the non-first packet includes:
and the data processing module is used for identifying the service by utilizing the first packet message and the non-first packet message.
With reference to the first possible implementation manner of the fourth aspect, in a second possible implementation manner, after the data processing module identifies the service by using the first packet message and the non-first packet message,
the data processing module is further configured to update the state of the service to an identification state;
the data transceiver module is further configured to synchronize the service state as the identification state to the first gateway, so that after the first gateway receives a new non-first packet of the service, which is sent to the first network device by the second network device through the first gateway, the first gateway directly forwards the new non-first packet to the first network device.
With reference to the fourth aspect, in a third possible implementation manner,
the data processing module is configured to generate the relevant information indicating a type of a management policy of the service, where the type of the management policy configured by the first gateway is not included in the relevant information.
In a fifth aspect, an embodiment of the present application provides a gateway, including: the system comprises a processor, a memory, a network card and a mainboard, wherein the processor, the memory and the network card are arranged on the mainboard,
the memory is used for storing programs;
the processor is configured to call and run the stored program, and interact with other gateways through the network card to execute the service identification method according to any one of the first aspect, any one of the possible implementation manners of the first aspect, the second aspect, or any one of the possible implementation manners of the second aspect.
In a sixth aspect, an embodiment of the present application provides a service identification system, including: the system comprises a first gateway and a second gateway, wherein the first gateway is connected with a first network device and a second network device, and the second gateway is also connected with the first network device and the second network device;
the first gateway is configured to perform the method for identifying a service according to the first aspect or any possible implementation manner of the first aspect;
the second gateway is configured to execute the service identification method according to the second aspect or any possible implementation manner of the second aspect.
In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, on which a program code is stored, where the program code, when executed by a computer, performs a method for identifying a service according to the first aspect, any possible implementation manner of the first aspect, the second aspect, or any possible implementation manner of the second aspect.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a block diagram illustrating a service identification system according to an embodiment of the present disclosure;
fig. 2 is a block diagram of a gateway according to an embodiment of the present application;
fig. 3 is a first flowchart of a service identification method according to an embodiment of the present application;
fig. 4 is a second flowchart of a service identification method provided in the embodiment of the present application;
fig. 5 is a third flowchart of a service identification method according to an embodiment of the present application;
fig. 6 is a first block diagram of a service identification apparatus according to an embodiment of the present disclosure;
fig. 7 is a second structural block diagram of a service identification apparatus according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
Referring to fig. 1 and fig. 2, an embodiment of the present application provides a service identification system 10, where the service identification system 10 may be deployed between network devices that need service interaction, and the network devices may be terminals and/or servers, for example. In this way, the service identification system 10 may provide the interactive service with a corresponding management policy, such as a security policy, so as to ensure the security of the interaction between the network devices by managing the service via the service identification system 10 through the management policy.
Illustratively, the identification system 10 of the service may include: a plurality of gateways 20, each gateway 20 may be directly or indirectly connected with a network device requiring interaction, so that the network devices requiring interaction may perform service interaction via any one gateway 20. In addition, the plurality of gateways 20 may be connected to each other in order to realize communication between the plurality of gateways 20. Optionally, when the number of the gateways 20 is small, the number of the ports on the gateway 20 is sufficient for the plurality of gateways 20 to be connected to each other. For example, the heartbeat interface of each gateway 20 may be correspondingly connected with the heartbeat interfaces of other gateways 20. However, when the number of gateways 20 is large, the number of ports on the gateway 20 is limited to satisfy the requirement for the interconnection between the gateways 20, so that the gateways 20 can be connected to each other by connecting switches. For example, the heartbeat interface of each gateway 20 is connected to a corresponding interface on the switch to enable heartbeat interface connections with other gateways 20 through the switch.
As shown in fig. 2, the gateway 20 may include: processor 21, memory 22, network card 23 and motherboard 24. The processor 21, the memory 22 and the network card 23 may be disposed on a motherboard 24.
In this embodiment, the memory 22 may be, for example, a magnetic disk, a ROM, or a RAM, or any combination thereof, and the memory 22 is used for storing programs. And the processor is used for calling and running the program in the memory 22 so as to control the network card 23 to interact with other gateways 20 in the plurality of gateways 20.
In the interaction, in order to ensure that the service identification system 10 can normally process various services interacted through the service identification system 10, when each gateway 20 acquires a first packet message of a service, each gateway 20 normally processes the first packet message, for example, normally forwards the first packet message, and each gateway 20 may further acquire related information of the service based on the first packet message and synchronize the related information to all other gateways 20. In this way, when each gateway 20 acquires the non-first packet message of the service, each gateway 20 may determine whether it has the capability of processing the non-first packet message based on the relevant information. If it is determined that the gateway 20 is capable of processing the non-first packet message, each gateway 20 normally processes the non-first packet message, otherwise, the gateway 20 forwards the non-first packet message to the gateway 20 that acquires the first packet message of the service, so that the gateway 20 that acquires the first packet message of the service normally processes the non-first packet message, thereby ensuring normal processing of the service.
For the sake of clarity of the interaction between the gateways 20, the following description will use the interaction between two gateways 20, i.e. the interaction between the first gateway 21 and the second gateway 22, as an example to describe how the two gateways 20 handle the traffic through the interaction.
Referring to fig. 3, an embodiment of the present application provides a method for identifying a service, which may be executed by a first gateway 21 and a second gateway 22 cooperatively, where the first gateway 21 is connected to a first network device and a second network device, and the second gateway 22 is also connected to the first network device and the second network device.
Specifically, the service identification method may include:
step S11: the second gateway obtains the data message sent by the first network equipment to the second network equipment.
Step S12: when the data message belongs to the first packet message of a service, the second gateway generates related information for indicating whether the first gateway can process the non-first packet message of the service.
Step S13: the second gateway synchronizes the relevant information to the first gateway.
Step S14: the first gateway obtains a non-first packet message of the service sent by the second network equipment to the first network equipment through the first gateway.
Step S15: the first gateway obtains the relevant information of the service.
Step S16: and when the related information indicates that the first gateway cannot process the non-first packet message, the first gateway forwards the non-first packet message to the second gateway.
Step S17: and the second gateway receives the non-first packet message forwarded by the first gateway.
Step S18: and the second gateway processes the non-first packet message.
The above-described flow will be described in detail below.
Step S11: the second gateway obtains the data message sent by the first network equipment to the second network equipment.
When the first network device needs to perform a new service interaction with the second network device, the first network device may send a first packet message of the service to the second network device through the service identification system 10. Then, the second gateway 22 in the service identification system 10 can intercept the first packet message (this embodiment takes the interception by the second gateway 22 as an example, but not by way of limitation).
It should be noted that, since the service is a new service, the second gateway 22 has not obtained any packet of the service, and therefore, when the first packet of the service is obtained for the first time, the second gateway 22 does not know that the obtained packet is the first packet of the service. In other words, for the second gateway 22, the second gateway 22 obtains a data packet sent by the first network device to the second network device.
Step S12: when the data message belongs to the first packet message of a service, the second gateway generates related information for indicating whether the first gateway can process the non-first packet message of the service.
After obtaining the data packet, the second gateway 22 decapsulates the data packet to obtain header information of the data packet. Since the header information carries identification information indicating that the data packet is a first packet of a service, the second gateway 22 can identify that the data packet belongs to the first packet of a service based on the identification information. The second gateway 22 may analyze the first packet message by using a policy configured in advance to identify a service to which the first packet message belongs.
In the first case, if the second gateway 22 analyzes the first packet message by using the policy and does not recognize the service to which the first packet message belongs, it is indicated that the first packet message only carries a part of information of the service, so that the second gateway 22 cannot recognize the service. Therefore, the second gateway 22 needs to obtain a non-first packet message carrying another part of the information of the service, so that the second gateway 22 can obtain all the information of the service, thereby identifying the service based on all the information. However, since the non-first packet message of the service may not be forwarded via the second gateway 22 but via the first gateway 21, to ensure that the second gateway 22 can obtain the non-first packet message of the service, the second gateway 22 may generate, based on the first packet message, related information used for indicating whether the first gateway 21 can process the non-first packet message, and synchronize the related information to the first gateway 21 while forwarding the first packet message to the second network device normally. In this way, when receiving the non-first packet message of the service, the first gateway 21 may forward the non-first packet message back to the second gateway 22 if it is determined that it cannot process the non-first packet message based on the related information.
Specifically, a first service table entry and a second service table entry are preset in the second gateway 22, where the first service table entry is used to record information required for processing a service that needs to be processed by the second gateway 22, and the second service table entry is used to record data sent by the first gateway 21. Since the service is processed by the second gateway 22 for the first time, which means that the service is a service that needs to be processed by the second gateway 22, the second gateway 22 can record the address (the address includes the source address and the destination address) carried in the first packet message into the first service table entry. In addition, since the second gateway 22 does not recognize the service, the second gateway 22 may determine that the status of the service is an unrecognized status, and thus record the status of the service as an unrecognized status into the first service entry. In this way, the second gateway 22 may subsequently continue to process the service based on the address and state of the service recorded in the first service table entry.
In addition to recording the address and status, on one hand, the second gateway 22 may also forward the first packet message to the second network device normally based on the address; on the other hand, the second gateway 22 also generates the relevant information carrying the address in the first packet message and the state of the service as an unidentified state.
In the second case, if the second gateway 22 analyzes the first packet message by using the policy to identify the service to which the first packet message belongs, the second gateway 22 may determine a management policy required for processing the service from a plurality of pre-configured management policies, and process the first packet message by using the determined management policy. After processing, the second gateway 22 may forward the processed initial packet message to the second network device based on the address carried in the initial packet message.
In this embodiment, the management policy configured by the first gateway 21 may not be the same as the management policy configured by the second gateway 22, and therefore, the management policy for processing the service may not be configured on the first gateway 21. In order to ensure that the non-top-packet message can be processed normally even if the first gateway 21 is not configured with a management policy for processing the service, the second gateway 22 may further generate related information of the non-top-packet message indicating whether the first gateway 21 can process the service, and also synchronize the related information with the first gateway 21. In this way, when receiving the non-first packet message of the service, if it is determined that the first gateway 21 cannot process the non-first packet message based on the related information, the first gateway may forward the non-first packet message back to the second gateway 22, so that the second gateway 22 can normally process the non-first packet message based on the management policy of the service.
As an alternative to generating the relevant information, the second gateway 22 may generate the relevant information carrying the address for processing the service and the type of management policy required for processing the service.
Further, after generating the related information, the second gateway 22 may further perform step S13.
Step S13: the second gateway 22 synchronizes the relevant information to the first gateway 21.
Since the second gateway 22 is connected to the first gateway 21 through the heartbeat interface, the second gateway 22 can synchronize the generated related information to the first gateway 21 through its own heartbeat interface in real time. Correspondingly, the first gateway 21 receives the relevant information through its heartbeat interface.
In this embodiment, a first service table entry and a second service table entry are also preset in the first gateway 21, where the first service table entry is used to record information required for processing a service that needs to be processed by the first gateway 21, and the second service table entry is used to record data sent by the second gateway 22. Obviously, since the related information is sent from the second gateway 22, the first gateway 21 can record the related information into the second service table entry.
Specifically, in the first case, the address of the service and the state of the service are carried in the related information and are in an unidentified state. Then the first gateway 21 receives the relevant information, that is, receives the address carried in the header packet message sent by the second gateway 22, and the state of the service sent by the second gateway 22 is the unidentified state. Further, the first gateway 21 may record the address of the service and the state of the service as an unidentified state in the second service table entry, and establish an association between the address of the service and the state of the service as the unidentified state in the second service table entry.
In the second case, carried in the relevant information is the address of the service and the type of management policy required to process the service. Further, the first gateway 21 may also record the address of the service and the type of the management policy required for processing the service into the second service table entry, and establish an association between the address of the service and the type of the management policy required for processing the service in the second service table entry.
Step S14: the first gateway 21 obtains the non-first packet message of the service sent by the second network device to the first network device through the first gateway 21.
Since the service interaction is performed between the first network device and the second network device, after the second network device receives the first packet message of the service, the second network device may generate and return a non-first packet message of the service to the first network device based on the first packet message of the service.
When the second network device sends the non-first packet message to the first network device, if the non-first packet message is acquired by the second gateway 22, the second gateway 22 may directly execute step S18; if the non-first packet message is acquired by the first gateway 21, the first gateway 21 may execute step S15 to analyze the non-first packet message.
Step S15: the first gateway 21 obtains the relevant information of the service.
After the first gateway 21 acquires the non-first packet message, since the first gateway 21 has not acquired any message of the service, when the non-first packet message of the service is acquired for the first time, the first gateway 21 does not know that the acquired message is the non-first packet message of the service. In other words, for the first gateway 21, the first gateway 21 obtains a data packet sent by the second network device to the first network device.
Therefore, the first gateway 21 may also decapsulate the data packet to obtain the header information of the data packet. Since the header information carries identification information for indicating that the data packet is a non-first packet of a service, based on the identification information, the first gateway 21 can identify that the data packet belongs to the non-first packet of the service, thereby determining that a processing logic for the non-first packet is to be executed subsequently.
Further, in order to implement efficient forwarding of the packet, the processing logic of the first gateway 21 on the packet may first analyze whether the packet can be directly processed and forwarded, and if not, analyze whether the packet needs to be forwarded to the second gateway 22. Therefore, after the first gateway 21 obtains the address carried in the non-first packet message by decapsulating the non-first packet message, the first gateway 21 may first traverse the first service table entry of the first gateway 21 by using the address carried in the non-first packet message, and determine that the address carried in the non-first packet message is not recorded in the first service table entry by traversal. Then, the first gateway 21 traverses the second service table entry of the first gateway 21 by using the address carried in the non-first packet message. Since the address carried in the non-first packet message is the same as the address carried in the first packet message, the first gateway 21 can determine the address carried in the non-first packet message from the addresses recorded in the second service table entry by traversing.
In the first case, since the second service table entry establishes the association between the address carried in the non-first packet message and the service state that is in the unidentified state, after the first gateway 21 determines the address carried in the non-first packet message, based on the association relationship, the first gateway 21 may further determine the state of the service associated with the address from the service states recorded in the second service table entry, and determine that the associated state is in the unidentified state.
In the second case, since the second service entry establishes the association between the address carried in the non-first packet message and the type of the management policy required for processing the service, after the first gateway 21 determines the address carried in the non-first packet message, based on the association relationship, the first gateway 21 may further determine the type of the management policy required for processing the service from the types of the management policies recorded in the second service entry.
It should be noted that, determining the state of the service or determining the type of the management policy required for processing the service by the first gateway 21 may be understood as that the first gateway 21 obtains the relevant information of the service. Further, after acquiring the related information, the first gateway 21 may further perform step S16.
Step S16: and when the related information indicates that the first gateway cannot process the non-first packet message, the first gateway forwards the non-first packet message to the second gateway.
In the first case, the service state is an unidentified state, which indicates that the first gateway 21 needs to identify the service again by using the non-first packet, and therefore, the service state is an unidentified state, which also indicates that the second gateway 22 cannot process the non-first packet, and needs to forward the non-first packet to the second gateway 22. Therefore, the first gateway 21 can forward the non-first packet message to the second gateway 22 in real time through its own heartbeat interface.
In the second case, the first gateway 21 may match the type of management policy required to process the service with the type of each management policy preconfigured by itself. Through matching, the first gateway 21 determines that the management policy of the service is not configured by itself, which indicates that the first gateway 21 cannot process the non-first packet, and therefore, the first gateway 21 may also forward the non-first packet to the second gateway 22 for processing in real time through its heartbeat interface.
Step S17: and the second gateway receives the non-first packet message forwarded by the first gateway.
Correspondingly, the second gateway 22 receives the non-first packet message forwarded by the first gateway 21 in real time through its own heartbeat interface.
Step S18: and the second gateway processes the non-first packet message.
In this embodiment, the processing logic of the second gateway 22 for the packet is the same as that of the first gateway 21, so that after receiving the non-first packet, the second gateway 22 obtains the address carried in the non-first packet, and traverses the first service table entry on the second gateway 22 by using the address.
For the first case, through traversal, the second gateway 22 may determine the address carried in the non-first packet message from each address recorded in the first service table entry of the second gateway 22, determine the state of the service associated with the address from each service state recorded in the first service table entry of the second gateway 22, and determine that the associated state is the unidentified state.
Further, since the service is in an unidentified state, the second gateway 22 may also identify the service by using information carried in a non-first packet message and information carried in the first packet message. Since the second network recognizes the service, the second gateway 22 may determine a management policy required for processing the service from a plurality of pre-configured management policies, process the non-first packet message by using the determined management policy, and forward the processed non-first packet message to the first network device.
For the second case, through traversal, the second gateway 22 may determine the address carried in the non-first packet message from each address recorded in the first service table entry of the second gateway 22, and then determine the management policy associated with the address from the types of the management policies recorded in the first service table entry of the second gateway 22, where the management policy associated with the address is the type of the management policy required for processing the service.
Further, the second gateway 22 may match the type of management policy required to process the service with the type of each management policy preconfigured in itself. Through matching, the second gateway 22 determines that the management policy of the service is configured in itself, so the second gateway 22 processes the non-first packet message by using the management policy of the service, and forwards the processed non-first packet message to the first network device.
Referring to fig. 4, for the first case, on the basis that the second gateway 22 identifies the service, in order to enable the first gateway 21 to subsequently obtain a new non-first packet message of the service, the first gateway 21 can directly process the non-first packet message, so as to reduce the load of the second gateway 22, where the method for identifying the service provided in this embodiment may further include:
step S21: the second gateway updates the state of the service to the identified state.
Step S22: and the second gateway synchronizes the state of the service as the identification state to the first gateway.
Step S23: and the first gateway correspondingly updates the state of the service into an identification state.
Step S24: the first gateway receives a new non-first packet message of the service sent by the second network equipment to the first network equipment through the first gateway.
Step S25: the first gateway acquires the state of the service as an identification state.
Step S26: and the first gateway directly forwards the new non-first packet message to the first network equipment.
The above-described flow will be described in detail below.
Step S21: the second gateway updates the state of the service to the identified state.
After the second gateway 22 recognizes the service, the second gateway 22 may update the state of the service in the first service table entry of the second gateway 22 to the latest state, that is, the state of the service in the first service table entry of the second gateway 22 is correspondingly updated from the unrecognized state to the recognized state.
Step S22: the second gateway synchronizes the state of the service to the first gateway 21 as the identified state.
In order to realize that the first gateway 21 can directly process the non-first packet message when the first gateway 21 subsequently obtains the new non-first packet message of the service. The second gateway 22 may synchronize the latest state of the service to the first gateway 21. Optionally, the second gateway 22 may generate new related information carrying the address of the service, the state of the service being an identification state, and the type identified by the service, and send the new related information to the first gateway 21 in real time through its own heartbeat interface.
Step S23: and the first gateway correspondingly updates the state of the service into an identification state.
The first gateway 21 receives this new relevant information through its own heartbeat interface. Based on the new related information, the first gateway 21 may determine that the state of the service associated with the address is an unidentified state from the second service table entry of the first gateway 21 by sequentially traversing the first service table entry and the second service table entry of the first gateway 21, and correspondingly update the state of the service in the second service table entry of the first gateway 21 to a latest identified state.
Step S24: the first gateway receives a new non-first packet message of the service sent by the second network equipment to the first network equipment through the first gateway.
When the second network device needs to continue the service interaction with the first network device, the second network device may send a new non-first packet message of the service to the first network device through the service identification system 10. Or, when the first network device needs to continue to interact with the second network device for the service, the first network device may send a new non-top packet message of the service to the second network device through the service identification system 10.
If the new non-first packet message is intercepted by the second gateway 22 in the service identification system 10, the second gateway 22 may directly process the new non-first packet message by using the management policy of the service, and forward the processed new non-first packet message to the first network device or the second network device. Otherwise, the new non-first packet message is intercepted by the first gateway 21 in the service identification system 10.
Step S25: the first gateway acquires the state of the service as an identification state.
After obtaining the new non-first packet message, the first gateway 21 may determine, based on the address carried in the new non-first packet message, that the state of the service associated with the address is the identification state from the second service table entry of the first gateway 21 by sequentially traversing the first service table entry and the second service table entry of the first gateway 21.
Step S26: and the first gateway directly forwards the new non-first packet message to the first network equipment.
Further, based on the type identified by the service, the second gateway 22 may determine, from the multiple management policies configured in advance, a management policy required for processing the service of the type, process the new non-first packet message by using the determined management policy, and forward the processed new non-first packet message to the first network device or the second network device.
Referring to fig. 5, for the second case, if the first gateway 21 obtains the management policy of the service before the first gateway 21 subsequently obtains the new non-first packet of the service, when the first gateway 21 obtains the new non-first packet of the service, the first gateway 21 can directly process the non-first packet of the service, so as to reduce the load of the second gateway 22. For this flow, the method for identifying a service provided in this embodiment may further include:
step S31: the first gateway obtains the management policy of the service.
Step S32: the first gateway receives a new non-first packet message of the service sent by the second network equipment to the first network equipment through the first gateway.
Step S33: the first gateway processes the non-first packet message by using the management strategy of the service;
step S34: and the first gateway forwards the processed new non-first packet message to the first network equipment.
It should be noted that the first gateway may obtain the management policy of the service from the third-party device, or the first gateway may also directly obtain the management policy of the service from the second gateway. In addition, the specific principle of the above flow can be referred to the above, and will not be described herein in a repeated manner.
Referring to fig. 6, based on the same inventive concept, an embodiment of the present application further provides an apparatus 100 for identifying a service, where the apparatus 100 for identifying a service can be applied to a first gateway 21, and the apparatus 100 for identifying a service includes:
a data transceiver module 110, configured to acquire a non-first packet message of a service that the second network device sends to the first network device through the first gateway 21.
A data processing module 120, configured to obtain relevant information of the service, where the relevant information is generated by the second gateway 22 based on the obtained first packet of the service.
The data transceiver module 110 is further configured to forward the non-first packet to the second gateway 22 when the relevant information indicates that the first gateway 21 cannot process the non-first packet.
Referring to fig. 7, based on the same inventive concept, in an embodiment of the present application, there is provided a service identification apparatus 200, where the service identification apparatus 200 is applicable to a second gateway 22, and the service identification apparatus 200 includes:
a data transceiver module 210, configured to acquire a data packet sent by the first network device to the second network device;
a data processing module 220, configured to generate, when the data packet belongs to a first packet of a service, relevant information used for indicating whether the first gateway 21 can process a non-first packet of the service;
the data transceiver module 210 is further configured to synchronize the relevant information to the first gateway 21; receiving the non-first packet message forwarded by the first gateway 21, where the second gateway 22 receiving the non-first packet message indicates that the first gateway 21 determines, based on the relevant information, that the first gateway 21 cannot process the non-first packet message;
the data processing module 220 is further configured to process the non-first packet message.
It should be noted that, as those skilled in the art can clearly understand, for convenience and brevity of description, the specific working process of the method described above may refer to the corresponding process in the embodiments of the system, the apparatus and the unit described above, and is not described herein again.
Some embodiments of the present application further provide a computer-readable storage medium of a computer-executable nonvolatile program code, which can be a general-purpose storage medium, such as a removable disk, a hard disk, or the like, and the computer-readable storage medium stores a program code thereon, and when the program code is executed by a computer, the program code performs the steps of the service identification method according to any of the above embodiments.
The program code product of the service identification method provided in the embodiment of the present application includes a computer-readable storage medium storing the program code, and instructions included in the program code may be used to execute the method in the foregoing method embodiment, and specific implementation may refer to the method embodiment, which is not described herein again.
In summary, embodiments of the present application provide a method, an apparatus, a gateway, a system, and a storage medium for service identification. After the second gateway obtains the first packet message of a service, the second gateway can analyze the relevant information of the service based on the first packet message and synchronize the relevant information to the first gateway. Therefore, when the first gateway acquires the non-first packet message of the service, the first gateway can determine whether the first gateway can not process the non-first packet message based on the relevant information. If the relevant information indicates that the first gateway cannot process the non-first packet message, the first gateway forwards the non-first packet message to the second gateway for processing so as to ensure that the service can be processed normally when the first gateway cannot process the non-first packet message, and thus, the data of the service can be processed normally under the HA environment.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
In addition, units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
Furthermore, the functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (19)
1. A method for identifying a service, the method being applied to a first gateway connected to a first network device and a second network device, the first network device and the second network device being further connected to the second gateway, the method comprising:
acquiring a non-first packet message of a service sent by the second network equipment to the first network equipment through the first gateway;
acquiring related information of the service, wherein the related information is generated by the second gateway based on the acquired first packet message of the service;
and when the related information indicates that the first gateway cannot process the non-first packet message, forwarding the non-first packet message to the second gateway.
2. The method for identifying a service according to claim 1, wherein obtaining the information related to the service comprises:
and acquiring the state of the service, wherein the state comprises an unidentified state which indicates that the first gateway cannot process the non-first packet message.
3. The method for identifying a service according to claim 2, wherein obtaining the status of the service comprises:
and determining the service state associated with the address carried in the non-first packet message from the preset service states, wherein the associated service state is the service state.
4. The method for identifying services according to claim 3, wherein before determining the service state associated with the address carried in the non-header packet from the preset service states, the method further comprises:
receiving the address carried in the first packet message sent by the second gateway, and receiving the state of the service sent by the second gateway;
associating the address with the state of the service.
5. The service identification method according to claim 4, wherein a first service table entry and a second service table entry are preset in the second gateway, the first service table entry is used to record information required for processing the service that needs to be processed by the first gateway, the second service table entry is used to record data sent by the second gateway, and the associating of the address with the service state includes:
establishing association between the address and the state of the service in the second service table entry;
correspondingly, determining the service state associated with the address carried in the non-first packet message from the preset service states includes:
determining that the address is not recorded in the first service table entry;
and determining the address from the second service table entry, and determining the service state associated with the address from the service states recorded by the second service table entry.
6. The method according to claim 2, wherein after forwarding the non-top packet to the second gateway for processing, the method further comprises:
receiving the latest state of the service sent by the second gateway, wherein the latest state is determined by the second gateway based on the first packet message and the non-first packet message;
and correspondingly updating the state of the service by utilizing the latest state.
7. The method of claim 2, wherein after obtaining the status of the service, the method further comprises:
and when the state is the identification state, directly forwarding the non-first packet message to the first network equipment.
8. The method for identifying a service according to claim 1, wherein obtaining the information related to the service comprises:
and acquiring the type of the management strategy for processing the service, wherein the type of the management strategy not comprising the first gateway configuration in the type indicates that the first gateway can not process the non-first packet message.
9. The method of claim 8, wherein after obtaining the type of management policy for processing the service, the method further comprises:
and when the first gateway is determined to be configured with the type of management strategy, processing the non-first packet message by using the management strategy.
10. A service identification method, applied to a second gateway connected to a first network device and a second network device, where the first network device and the second network device are further connected to the first gateway, the method comprising:
acquiring a data message sent by the first network equipment to the second network equipment;
when the data message belongs to a first packet message of a service, generating related information of a non-first packet message for indicating whether the first gateway can process the service;
synchronizing the relevant information to the first gateway;
receiving the non-first packet message forwarded by the first gateway, wherein the second gateway receiving the non-first packet message indicates that the first gateway determines that the first gateway cannot process the non-first packet message based on the relevant information;
and processing the non-first packet message.
11. The method according to claim 10, wherein generating the related information of the non-first packet message indicating whether the first gateway can handle the service comprises:
generating the related information for representing the state of the service, wherein the state is an unidentified state.
12. The method of claim 11, wherein processing the non-top packet comprises:
and identifying the service by using the first packet message and the non-first packet message.
13. The method of claim 12, wherein after identifying the service using the first packet and the non-first packet, the method further comprises:
updating the state of the service to an identification state;
and synchronizing the service state as the identification state to the first gateway, so that after the first gateway receives a new non-first packet message of the service sent to the first network equipment by the second network equipment through the first gateway, the first gateway directly forwards the new non-first packet message to the first network equipment.
14. The method according to claim 10, wherein generating the related information of the non-first packet message indicating whether the first gateway can handle the service comprises:
generating the related information for indicating the type of the management policy of the service, wherein the type of the management policy configured by the first gateway is not included in the type.
15. An apparatus for identifying a service, the apparatus being applied to a first gateway connected to a first network device and a second network device, the first network device and the second network device being further connected to the second gateway, the apparatus comprising:
the data receiving and sending module is used for acquiring a non-first packet message of a service sent to the first network equipment by the second network equipment through the first gateway;
the data processing module is used for acquiring relevant information of the service, wherein the relevant information is generated by the second gateway based on the acquired first packet message of the service;
the data transceiver module is further configured to forward the non-first packet message to the second gateway when the relevant information indicates that the first gateway cannot process the non-first packet message.
16. An apparatus for identifying a service, the apparatus being applied to a second gateway connected to a first network device and a second network device, the first network device and the second network device being further connected to the first gateway, the apparatus comprising:
a data transceiver module, configured to acquire a data packet sent by the first network device to the second network device;
a data processing module, configured to generate, when the data packet belongs to a first packet of a service, related information used for indicating whether the first gateway can process a non-first packet of the service;
the data transceiver module is further configured to synchronize the relevant information to the first gateway; receiving the non-first packet message forwarded by the first gateway, wherein the second gateway receiving the non-first packet message indicates that the first gateway determines that the first gateway cannot process the non-first packet message based on the relevant information;
the data processing module is further configured to process the non-first packet message.
17. A gateway, comprising: the system comprises a processor, a memory, a network card and a mainboard, wherein the processor, the memory and the network card are arranged on the mainboard,
the memory is used for storing programs;
the processor is used for calling and running the stored program, and interacting with other gateways through the network card to execute the service identification method according to any one of claims 1 to 14.
18. A system for identifying a service, comprising: the system comprises a first gateway and a second gateway, wherein the first gateway is connected with a first network device and a second network device, and the second gateway is also connected with the first network device and the second network device;
the first gateway, configured to perform the service identification method according to any one of claims 1 to 9;
the second gateway is configured to perform the service identification method according to any one of claims 10 to 14.
19. A computer-readable storage medium having stored thereon program code which, when executed by a computer, performs a method of identifying a service according to any one of claims 1 to 14.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911097395.0A CN110830477B (en) | 2019-11-11 | 2019-11-11 | Service identification method, device, gateway, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911097395.0A CN110830477B (en) | 2019-11-11 | 2019-11-11 | Service identification method, device, gateway, system and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110830477A CN110830477A (en) | 2020-02-21 |
| CN110830477B true CN110830477B (en) | 2022-03-11 |
Family
ID=69553974
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911097395.0A Active CN110830477B (en) | 2019-11-11 | 2019-11-11 | Service identification method, device, gateway, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110830477B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115695565B (en) * | 2021-07-13 | 2024-04-09 | 大唐移动通信设备有限公司 | Data message processing method and device and computer readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103139205A (en) * | 2013-01-30 | 2013-06-05 | 华为技术有限公司 | Message processing method, device and network server |
| WO2014101888A1 (en) * | 2012-12-31 | 2014-07-03 | 华为终端有限公司 | Data transmission method, device and gateway |
| CN109617735A (en) * | 2018-12-26 | 2019-04-12 | 华为技术有限公司 | Cloud computation data center system, gateway, server and message processing method |
-
2019
- 2019-11-11 CN CN201911097395.0A patent/CN110830477B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014101888A1 (en) * | 2012-12-31 | 2014-07-03 | 华为终端有限公司 | Data transmission method, device and gateway |
| CN103139205A (en) * | 2013-01-30 | 2013-06-05 | 华为技术有限公司 | Message processing method, device and network server |
| CN109617735A (en) * | 2018-12-26 | 2019-04-12 | 华为技术有限公司 | Cloud computation data center system, gateway, server and message processing method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110830477A (en) | 2020-02-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10750387B2 (en) | Configuration of rules in a network visibility system | |
| CN110506411B (en) | Method and system for providing packet enforcement using logical ports in a virtualized computing environment | |
| US20210029077A1 (en) | Managing network connectivity between cloud computing service endpoints and virtual machines | |
| CN106878199B (en) | Configuration method and device of access information | |
| US10530688B2 (en) | Configuration of load-sharing components of a network visibility router in a network visibility system | |
| US10911353B2 (en) | Architecture for a network visibility system | |
| US7532620B2 (en) | Routing table synchronization method, network apparatus, and routing table synchronization program | |
| CN110545230B (en) | Method and device for forwarding VXLAN message | |
| CN106911769B (en) | Cloud platform routing data processing method and physical server of cloud platform | |
| CN110830477B (en) | Service identification method, device, gateway, system and storage medium | |
| CN107995321A (en) | A kind of VPN client acts on behalf of the method and device of DNS | |
| US9521586B2 (en) | Mobile communication system, communication system, node, flow-control network, and communication-control method | |
| US10104018B2 (en) | Method, apparatus, and system for controlling forwarding of service data in virtual network | |
| CN107911496A (en) | A kind of VPN service terminal acts on behalf of the method and device of DNS | |
| KR101953584B1 (en) | NFV service provider, VNF service provider, system for extending service chaining including them and method for extending service chaining | |
| CN115174474B (en) | SRv 6-based SFC implementation method and device in private cloud | |
| CN104468767A (en) | Method and system for detecting cloud storage data collision | |
| US8731532B2 (en) | Method for delivering electronic documents using mobile telephony identifiers in a secure manner in conjunction with internet protocols and address systems | |
| CN113014664B (en) | Gateway adaptation method, device, electronic equipment and storage medium | |
| CN112165430B (en) | Data routing method, device, equipment and storage medium | |
| CN109413118A (en) | A kind of method, apparatus that realizing session synchronization and storage medium, program product | |
| CN110809033B (en) | Message forwarding method and device and switching server | |
| US20190028880A1 (en) | Method for accessing context data by network service component, apparatus, and system | |
| CN115190168B (en) | Edge server management system and server cluster | |
| CN112825524A (en) | Method, device and system for determining network service node |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |