Method, apparatus and device for determining service traffic, and storage medium

Abstract

The application discloses a service traffic determination method, device, equipment and storage medium, which comprises the following steps: obtaining a traffic message of a cloud private network; determining a cloud private network connection scenario of the cloud private network according to the data format of the traffic message; performing data rewriting on the traffic message according to the cloud private network connection scenario to obtain a destination Internet Protocol address of the traffic message; and determining that a service corresponding to the destination Internet Protocol address is a target service. Based on this, the data format of the traffic message is rewritten in different cloud private network connection scenarios to obtain the destination Internet Protocol address, so that the corresponding target service is determined. Compared with the prior art, the Internet Protocol address cannot be accurately identified in the cloud private network, so that the service corresponding to the traffic in the cloud private network cannot be determined, and the traffic service identification and further processing in the cloud private network are realized.

Description

TECHNICAL FIELD

[0001] The present application belongs to the field of business traffic identification, and particularly relates to a business traffic determination method and device, equipment and a storage medium. BACKGROUND

[0002] Cloud line services are widely used based on cloud networks. Cloud lines provide private network connections of physical lines, and network link users are exclusive, without data leakage risks, meeting high-level network connection needs of finance, government and enterprises.

[0003] In the application process, in order to ensure the execution safety of the business in the cloud line, the cloud line service needs to be monitored and protected, that is, the traffic of the cloud line service needs to be monitored and protected. However, the existing network traffic analysis technology distinguishes the executed business according to the IP address (Internet Protocol Address). However, due to the same IP address traffic encapsulated by VPN (Virtual Private Network) or MPLS (Multi-Protocol Label Switching) in the cloud private network, the existing network analysis technology cannot accurately obtain the cloud network business detailed information in the cloud private network traffic for further detailed analysis and protection.

[0004] Therefore, in the prior art, the address information of the traffic in the cloud private network cannot be obtained, so the executed business corresponding to the traffic cannot be determined. SUMMARY

[0005] The embodiments of the present application provide a business traffic determination method, device, equipment and storage medium, which determines the executed business corresponding to the traffic by obtaining the address information in the traffic.

[0006] According to a first aspect of the present application, the embodiments of the present application provide a business traffic determination method, which can include:

[0007] Obtaining a traffic packet of a cloud private network;

[0008] According to the data format of the traffic packet, determining a cloud private network connection scenario of the cloud private network;

[0009] According to the cloud private network connection scenario, performing data rewriting on the traffic packet to obtain a destination Internet Protocol Address of the traffic packet;

[0010] Determining that the business corresponding to the destination Internet Protocol Address is a target business.

[0011] Optionally, according to the data format of the traffic packet, determining the cloud private network connection scenario of the cloud private network can include:

[0012] If a communication interface address is present in the traffic packet, the cloud private network connection scenario is determined to be a cloud private network edge access scenario.

[0013] If a communication protocol tag message is present in the traffic packet, the cloud private network connection scenario is determined to be a communication scenario within the cloud private network domain.

[0014] Optionally, the cloud private network connection scenario is a cloud private network edge access scenario;

[0015] Based on the cloud private network connection scenario, the traffic packets are rewritten to obtain the destination Internet Protocol address, which may include:

[0016] Obtain the first address packet information from the traffic packet;

[0017] The first hardware address is extracted from the first address message information;

[0018] The first hardware address is rewritten to obtain the destination Internet Protocol address.

[0019] Optionally, the first hardware address is rewritten to obtain the destination Internet Protocol address, including:

[0020] The first hardware address is decomposed into multiple first address character segments;

[0021] Each of the first address character segments is rewritten to obtain the second address character segment;

[0022] Each second address character segment is combined to generate the destination Internet Protocol address.

[0023] Optionally, the cloud private network connection scenario is a communication scenario within the cloud private network domain;

[0024] Based on the cloud private network connection scenario, the traffic packets are rewritten to obtain the destination Internet Protocol address, which may include:

[0025] Parse the communication protocol tag message to obtain the header tag message;

[0026] The initial Internet Protocol address in the header label message is rewritten to obtain the destination Internet Protocol address.

[0027] Optionally, rewriting the initial packet Internet Protocol address in the header label message to obtain the destination Internet Protocol address may include:

[0028] Remove the top-level tag message from the header tag message to obtain the bottom-level tag message;

[0029] Obtain the initial packet Internet Protocol address from the underlying tag packet;

[0030] Add padding characters to the initial packet's Internet Protocol address to obtain the target packet's Internet Protocol address;

[0031] Decompose the target message Internet Protocol address into multiple third-address character fields;

[0032] Each third address character segment is rewritten to obtain the fourth address character segment;

[0033] Each fourth address character segment is combined to generate the destination Internet Protocol address.

[0034] Optionally, after determining that the service corresponding to the destination Internet Protocol address is the target service, the method may further include:

[0035] Send the traffic packets to the execution program corresponding to the target service.

[0036] According to a second aspect of this application, embodiments of this application provide a service traffic determination apparatus, which may include:

[0037] The acquisition module is used to acquire traffic packets from the cloud private network;

[0038] The first determining module is used to determine the cloud private network connection scenario of the cloud private network based on the data format of the traffic packet;

[0039] The data rewriting module is used to rewrite the traffic packets according to the cloud private network connection scenario to obtain the destination Internet Protocol address;

[0040] The second determining module is used to determine that the service corresponding to the destination Internet Protocol address is the target service.

[0041] According to a third aspect of this application, a device for determining traffic flow is provided, the device comprising: a processor and a memory storing computer program instructions;

[0042] The method for determining the business flow of any one of the first aspects when the processor executes computer program instructions.

[0043] According to a fourth aspect of this application, embodiments of this application provide a computer storage medium storing computer program instructions, which, when executed by a processor, implement a method for determining service traffic according to any one of the first aspects.

[0044] According to a fifth aspect of this application, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform a method for determining service traffic of any one of the first aspects.

[0045] The method, apparatus, device, and storage medium for determining service traffic in this application embodiment acquire traffic packets and determine the cloud private network connection scenario of the traffic packets based on the data format of the traffic packets. This allows for data rewriting of the traffic packets under different cloud private network connection scenarios to obtain the destination Internet Protocol address (IPA) of the traffic packets. Based on this destination IPA, the target service corresponding to the traffic packets can be determined. Therefore, by rewriting the data format of traffic packets in different cloud private network connection scenarios to obtain their destination IPA and thus determine the corresponding target service, this method achieves service identification of traffic within cloud private networks, compared to existing cloud private networks where the IPA cannot be accurately identified, thus preventing the determination of the service corresponding to traffic within the cloud private network. Attached Figure Description

[0046] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0047] Figure 1 This is a flowchart illustrating a method for determining service traffic according to an exemplary embodiment;

[0048] Figure 2 This is a schematic diagram of packet transmission in a cloud network illustrating a method for determining service traffic according to an exemplary embodiment;

[0049] Figure 3 This is a structural block diagram of a service traffic determination apparatus according to an exemplary embodiment;

[0050] Figure 4 This is a schematic diagram of the hardware structure of a device for determining service traffic according to an exemplary embodiment. Detailed Implementation

[0051] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0052] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-external inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0053] As described in the background section, existing network analysis techniques cannot accurately obtain detailed information about cloud network services within the traffic of existing cloud private networks that are encapsulated by VPN (Virtual Private Network) or MPLS (Multi-Protocol Label Switching) with the same IP address, allowing for further detailed analysis and protection.

[0054] To address the existing technical problems, this application rewrites the data format of traffic packets in different cloud private network connection scenarios to obtain their destination Internet Protocol address, thereby determining the corresponding target service. Compared with the existing cloud private network, which cannot accurately identify the Internet Protocol address and thus cannot determine the service corresponding to traffic in the cloud private network, this application realizes traffic service identification in the cloud private network.

[0055] Based on this, this application provides a method, apparatus, device, and storage medium for determining service traffic. The method for determining service traffic provided in the embodiments of this application will be described first below.

[0056] Figure 1 A flowchart illustrating a method for determining service traffic according to an embodiment of this application is shown. Figure 1 As shown, the method may include the following steps:

[0057] S101, retrieve traffic packets from the cloud private network;

[0058] S102, Determine the cloud private network connection scenario based on the data format of the traffic packets;

[0059] S103, based on the cloud private network connection scenario, rewrite the data of the traffic packets to obtain the destination Internet Protocol address of the traffic packets;

[0060] S104, determine the service corresponding to the destination Internet Protocol address as the target service.

[0061] Based on the above embodiments, this application obtains traffic packets and determines the cloud private network connection scenario of the traffic packets according to their data format. This allows for data rewriting of the traffic packets under different cloud private network connection scenarios to obtain the destination Internet Protocol address (IPA) of the traffic packets. Therefore, the target service corresponding to the traffic packets can be determined based on the destination IPA. In this way, by rewriting the data format of traffic packets in different cloud private network connection scenarios to obtain their destination IPA and thus determine the corresponding target service, this application achieves traffic service identification in cloud private networks, compared to existing cloud private networks where the IPA cannot be accurately identified, thus preventing the determination of the service corresponding to traffic within the cloud private network.

[0062] In the above S101, by connecting the hardware probe to the network transmission channel of the cloud private network, the traffic packets of the network connection channel in the cloud private network can be obtained.

[0063] In S102 above, by analyzing the data format of the traffic packets, the application scenario of the traffic packets is determined based on the data format, that is, the cloud private network connection scenario of the cloud private network.

[0064] As an example, S102 above may include:

[0065] S1021, if a communication interface address exists in the traffic packet, the cloud private network connection scenario is determined to be a cloud private network edge access scenario;

[0066] S1022, if a communication protocol tag message exists in the traffic message, the cloud private network connection scenario is determined to be a cloud private network domain communication scenario.

[0067] In S1021 above, since traffic packets are analyzed, if there is a packet about the communication interface address, it means that the traffic packet is a traffic packet in the cloud private network edge access scenario of the cloud private network.

[0068] As an example, the communication interface address can include: MAC address + VLAN address, where the VLAN address is mainly represented by the VLAN account (VLANID).

[0069] like Figure 2As shown, in a cloud private network, the forwarded traffic packets support forwarding communication ports of multiple different VLANs, i.e., aggregation links. Under the same aggregation link containing multiple VLANs, one VLAN corresponds to one service. Based on the MAC+VLANID combination, the source of traffic executing different services can be traced back to different upstream network devices. Data frames on the aggregation link are appended with special information to identify which VLAN they belong to. When a data frame sent by A travels from switch 1 through the aggregation link to switch 2, a tag indicating that it belongs to the red VLAN is appended to the data frame.

[0070] After receiving a data frame, switch 2 checks the VLAN tag and finds that the data frame belongs to the red VLAN. Therefore, after removing the tag, it forwards the restored data frame only to other ports belonging to the red VLAN, as needed. In this case, forwarding means confirming the destination MAC address and comparing it with the MAC address list, then only forwarding it to the port connected to the destination MAC address. Only when the data frame is a broadcast frame, multicast frame, or a frame with an unknown destination will it be forwarded to all ports belonging to the red VLAN.

[0071] If a traffic packet contains a communication interface address that combines a MAC address and a VLAN address, then the traffic packet is used for edge access scenarios in a cloud private network. Therefore, the cloud private network connection scenario is also a cloud private network edge access scenario.

[0072] In the above S102, in the case of intra-domain communication in the cloud private network, when the traffic packet enters the MPLS layer, the LER (Label Edge Router) of the MPLS ingress pushes the traffic packet into the MPLS label stack, so that the traffic packet carries two layers of MPLS labels into the MPLS routing domain.

[0073] Therefore, if the traffic packet contains MPLS-related communication protocol tag packets, the traffic packet is a packet used for communication within the cloud private network domain, that is, the cloud private network connection scenario is a cloud private network domain communication scenario.

[0074] In S103 above, the data format of traffic packets under different cloud private network connection scenarios is rewritten according to the different cloud private network connection scenarios, so as to obtain the destination Internet Protocol address of the traffic packet.

[0075] Specifically, in one embodiment, when the cloud private network connection scenario is a cloud private network edge access scenario, the above S103 may include:

[0076] S1031, Obtain the first address packet information in the traffic packet;

[0077] S1032, extract the first hardware address from the first address message information;

[0078] S1033, rewrite the data of the first hardware address to obtain the destination Internet Protocol address.

[0079] In S1031 above, first address packet information about the communication address is extracted from the traffic packet, wherein the first address packet information may include MAC address + VLAN address.

[0080] In S1032 above, the first hardware address, i.e. MAC address, for executing services related to traffic packets is extracted from the first address message information.

[0081] In S1033 above, the data of the first hardware address is rewritten and converted in format to obtain the destination Internet Protocol address that can be read in the traffic packet.

[0082] Specifically, the methods for rewriting data at the first hardware address can include:

[0083] The first hardware address is decomposed into multiple first address character segments;

[0084] Each of the first address character segments is rewritten to obtain the second address character segment;

[0085] Each second address character segment is combined to generate the destination Internet Protocol address.

[0086] Specifically, the first hardware address is divided into multiple character segments to obtain the first address character segment.

[0087] For example, if the MAC address information in the traffic packet is identified as 01-01-11-12-13-14, it can be split into 11, 12, 13, and 14.

[0088] Each first character segment is rewritten, and the rewriting method can include format replacement, order replacement, etc., to obtain the second address character segment corresponding to each first address character segment.

[0089] For example, A=11, B=12, C=13, D=14.

[0090] Then, by combining each second address character segment according to the preset communication protocol requirements, the destination Internet Protocol address can be generated.

[0091] For example, filling in the above information in the IPv4 address format such as ABCD will give you the destination Internet Protocol address 11.12.13.14.

[0092] Specifically, in another embodiment, when the cloud private network connection scenario is a communication scenario within the cloud private network domain, the above-mentioned S103 may further include:

[0093] S1035, parse the communication protocol tag message to obtain the header tag message;

[0094] S1036, rewrite the initial message Internet Protocol address in the header label message to obtain the destination Internet Protocol address.

[0095] In the case of cloud private network connection scenarios where communication occurs within the cloud private network domain, the communication protocol label message is an MPLS label information message. The MPLS label information message is removed to obtain the header label message.

[0096] Then, the initial packet Internet Protocol address contained in the header label message is rewritten to obtain the destination Internet Protocol address.

[0097] Specifically, rewriting methods can include:

[0098] Remove the top-level tag message from the header tag message to obtain the bottom-level tag message;

[0099] Obtain the initial packet Internet Protocol address from the underlying tag packet;

[0100] Add padding characters to the initial packet's Internet Protocol address to obtain the target packet's Internet Protocol address;

[0101] Decompose the target message Internet Protocol address into multiple third-address character fields;

[0102] Each third address character segment is rewritten to obtain the fourth address character segment;

[0103] Each fourth address character segment is combined to generate the destination Internet Protocol address of the traffic packet.

[0104] The MPLS label stack header labels consist of two layers. The bottom layer labels are assigned by the BGP protocol, and the top layer labels are assigned by the underlying network IGP protocol. Since the cloud-network aggregation device is the penultimate hop LSR for any path within the MPLS VPN (Virtual Private Network) routing domain, when an MPLS VPN packet enters the cloud-network aggregation device, the top layer IGP label packet is popped, leaving only the bottom layer VPN label packet in the label stack. The MPLS layer service identification module parses the MPLS header label information in the MPLS VPN packet to obtain the corresponding VPN bottom layer label packet.

[0105] The initial packet Internet Protocol address is extracted from the VPN underlying label packet.

[0106] Since the initial message Internet Protocol address has a limited number of characters, padding characters need to be added to the initial message Internet Protocol address to better determine the decomposition of the initial message Internet Protocol address, thereby obtaining the target message Internet Protocol address.

[0107] For example, if the tag value in the Internet Protocol address of the initial message is identified as 48175, the value is padded with zeros to become 048175.

[0108] The target message Internet Protocol address, which has been padded with padding characters, is split to obtain multiple third address character segments.

[0109] For example, 048175 can be recorded as fields 04, 81, and 75.

[0110] Each third character segment is rewritten, and the rewriting method can include format replacement, order replacement, etc., to obtain the fourth address character segment corresponding to each third address character segment.

[0111] For example, A=04, B=81, C=75.

[0112] Since the traffic packets are transmitted within the cloud private network domain, and there is a fixed Internet Protocol address character within the domain, the final destination Internet Protocol address needs to be generated by combining the fixed Internet Protocol address character and the fourth address character segment after splitting.

[0113] For example, entering the format 10.ABC will give you the destination Internet Protocol address 10.04.81.75. Here, 10 represents the fixed Internet Protocol address characters.

[0114] In step S104 above, after determining the destination Internet Protocol (IP) address, the target service corresponding to the destination IP address can be determined based on the mapping relationship between services and IP addresses. Furthermore, if the traffic packet contains errors, appropriate solutions can be implemented for the target service in a timely manner.

[0115] As an example, by predefining the mapping relationship between Internet Protocol addresses and services in the probe's traffic parsing module, the probe's traffic parsing module can, after obtaining the destination Internet Protocol address, query the predefined mapping relationship based on the destination Internet Protocol address, thereby identifying the service to which the traffic packet belongs.

[0116] In one embodiment, in order to execute a target service, the service traffic determination method provided in one embodiment of this application, after the above-described S104, may further include:

[0117] S201, send the traffic packet to the execution program corresponding to the target service.

[0118] By sending traffic packets to the execution program corresponding to the target service, the execution program can execute the corresponding target service based on the traffic packets, thereby completing the execution of the target service.

[0119] It should be noted that, in addition to confirming the destination Internet Protocol address of traffic packets and thus identifying the target service in the aforementioned cloud private network edge access scenarios, this method is also applied to traffic analysis and protection during traffic packet monitoring in the following scenarios:

[0120] (1) Based on the business dimensions (including different scenarios, cloud private network edge access scenario and cloud private network MPLS domain detection scenario), the data collected by the probe is parsed and organized. Based on the business requirements, functions such as traffic statistics, latency jitter analysis, packet loss analysis, protocol type analysis, business response latency analysis, and retransmission rate analysis of cloud private line services are displayed to realize service quality monitoring in the cloud private line dimension.

[0121] (2) In a specific cloud private network MPLS domain detection scenario, a traffic cleaning module can be loaded to clean the attack traffic in the cloud-to-cloud interconnection scenario.

[0122] (3) In specific scenarios, the traffic detection device identifies and matches traffic based on the abnormal traffic identification threshold and related feature library. It determines whether there is abnormal attack behavior in the business traffic by the condition that the message meets the feature or the attack sending rate reaches the threshold. If there is abnormal attack behavior, an alarm is sent to the security management center to trigger cleaning. After the abnormal traffic enters the cleaning center, the cleaning device cleans the abnormal traffic according to the preset security policy, identifies the attack message and discards it. The remaining normal business traffic messages continue to go through the forwarding process and are transferred back to the cloud private network.

[0123] It should be noted that the application scenarios described in the above embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems; and, the new embodiments of this application can be combined with each other, and the new solutions formed by the combination of various embodiments are all within the protection scope of this application.

[0124] Based on the same inventive concept, this application also provides a business flow determination device 300. (Specifically combined with...) Figure 3 To provide a detailed description, the business traffic determination device 300 may include:

[0125] The acquisition module 310 is used to acquire traffic packets of the cloud private network;

[0126] The first determining module 320 is used to determine the cloud private network connection scenario of the cloud private network based on the data format of the traffic packet;

[0127] The data rewriting module 320 is used to rewrite traffic packets according to the cloud private network connection scenario to obtain the destination Internet Protocol address;

[0128] The second determining module 340 is used to determine that the service corresponding to the destination Internet Protocol address is the target service.

[0129] In the service traffic determination device 300 provided in this embodiment, the acquisition module 310 acquires traffic packets, the first determination module 320 determines the cloud private network connection scenario of the traffic packet based on the data format of the traffic packet, and the data rewriting module 320 can then rewrite the data of the traffic packet according to different cloud private network connection scenarios to obtain the destination Internet Protocol address of the traffic packet. The second determination module 340 can then determine the target service corresponding to the traffic packet based on the destination Internet Protocol address. Based on this, by rewriting the data format of traffic packets in different cloud private network connection scenarios to obtain their destination Internet Protocol address and thus determine the corresponding target service, this method achieves service identification of traffic in cloud private networks, compared to the existing cloud private networks where the Internet Protocol address cannot be accurately identified, thus preventing the determination of the service corresponding to traffic in the cloud private network.

[0130] Optionally, the first determining module 320 may include:

[0131] The first determining unit is used to determine the cloud private network connection scenario as a cloud private network edge access scenario when a communication interface address exists in the traffic packet.

[0132] The second determining unit is used to determine that the cloud private network connection scenario is a communication scenario within the cloud private network domain when a communication protocol tag message exists in the traffic message.

[0133] Optionally, the cloud private network connection scenario is a cloud private network edge access scenario;

[0134] The data rewriting module 320 may include:

[0135] The first acquisition unit is used to acquire the first address packet information in the traffic packet;

[0136] The first extraction unit is used to extract the first hardware address from the first address message information;

[0137] The first data rewriting unit is used to rewrite the data of the first hardware address to obtain the destination Internet Protocol address.

[0138] Optionally, the first data rewriting unit may include:

[0139] The first decomposition subunit is used to decompose the first hardware address into multiple first address character segments;

[0140] The first data rewriting subunit is used to rewrite the data of each first address character segment to obtain the second address character segment;

[0141] The first combination subunit is used to combine each second address character segment to generate the destination Internet Protocol address.

[0142] Optionally, the cloud private network connection scenario is a communication scenario within the cloud private network domain;

[0143] The data rewriting module 320 may include:

[0144] The parsing unit is used to parse the communication protocol tag message to obtain the header tag message;

[0145] The second data rewriting unit is used to rewrite the initial packet Internet Protocol address in the header label message to obtain the destination Internet Protocol address.

[0146] Optionally, the second data rewriting unit may include:

[0147] The sub-unit is used to remove the top-level tag message from the header tag message to obtain the bottom-level tag message.

[0148] The first acquisition word unit is used to acquire the initial message Internet Protocol address in the underlying label message;

[0149] Add a sub-unit to add padding characters to the initial message Internet Protocol address to obtain the target message Internet Protocol address;

[0150] The decomposition subunit is used to decompose the target message Internet Protocol address into multiple third address character fields;

[0151] The second data rewriting subunit is used to rewrite the data of each third address character segment to obtain the fourth address character segment;

[0152] The combination subunit is used to combine each fourth address character segment to generate the destination Internet Protocol address.

[0153] Optionally, the service traffic determination device 300 may include:

[0154] The sending module is used to send traffic packets to the execution program corresponding to the target service.

[0155] The service traffic determination device 300 provided in this application embodiment can achieve Figure 3 The various processes implemented in the method embodiments can achieve the same technical effect, and will not be described again here to avoid repetition.

[0156] Figure 4 A schematic diagram of the hardware structure of the device for determining service traffic provided in an embodiment of this application is shown.

[0157] The device for determining business traffic may include a processor 401 and a memory 402 storing computer program instructions.

[0158] Specifically, the processor 401 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0159] Memory 402 may include mass storage for data or instructions. For example, and not limitingly, memory 402 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 402 may include removable or non-removable (or fixed) media. Where appropriate, memory 402 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 402 is non-volatile solid-state memory.

[0160] In a particular embodiment, memory 402 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Thus, generally, memory 402 includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors 401), it is operable to perform the operations described with reference to the method according to one aspect of this application.

[0161] The processor 401 reads and executes computer program instructions stored in the memory 402 to implement any of the service traffic determination methods in the above embodiments.

[0162] In one example, the device for determining service traffic may also include a communication interface 403 and a bus 403. As shown in the figure, the processor 401, memory 402, and communication interface 403 are connected via the bus 403 and communicate with each other.

[0163] The communication interface 403 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0164] Bus 403 includes hardware, software, or both, that couples components of a defined device to each other for traffic flow. For example, and not as a limitation, bus 403 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, a Wireless Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Control Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 403 may include one or more buses 403. Although specific bus 403s are described and illustrated in embodiments of this application, this application contemplates any suitable bus 403 or interconnect.

[0165] The service traffic determination device can execute the service traffic determination method in this application embodiment based on the service traffic determination device 400, thereby achieving a combination Figure 1 The method for determining business traffic is described.

[0166] Furthermore, in conjunction with the methods for determining service traffic in the above embodiments, this application embodiment can provide a computer storage medium for implementation. This computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the service traffic determination methods in the above embodiments.

[0167] This application also provides a computer program product, including a computer program, which, when executed, implements any of the methods for determining business traffic in the above embodiments.

[0168] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0169] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0170] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0171] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable traffic determination device to produce a machine such that these instructions, executable via the processor of the computer or other programmable traffic determination device, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0172] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A method for determining business traffic, characterized in that, The method includes: Obtain traffic packets from the cloud private network; Based on the data format of the traffic packets, the cloud private network connection scenario of the cloud private network is determined; Based on the cloud private network connection scenario, the traffic packets are rewritten to obtain the destination Internet Protocol address of the traffic packets; The service corresponding to the target Internet Protocol address is identified as the target service; The step of determining the cloud private network connection scenario based on the data format of the traffic packets includes: If a communication interface address exists in the traffic packet, the cloud private network connection scenario is determined to be a cloud private network edge access scenario. The communication interface address includes: MAC address and VLAN address. If the traffic packets contain communication protocol tag packets related to MPLS, the cloud private network connection scenario is determined to be a cloud private network domain communication scenario.

2. The method as described in claim 1, characterized in that, The cloud private network connection scenario is the cloud private network edge access scenario; The step of rewriting the traffic packets to obtain the destination Internet Protocol address based on the cloud private network connection scenario includes: Obtain the first address packet information from the traffic packet; The first hardware address is extracted from the first address message information; The first hardware address is rewritten to obtain the destination Internet Protocol address.

3. The method as described in claim 2, characterized in that, The step of rewriting the first hardware address to obtain the destination Internet Protocol address includes: The first hardware address is decomposed into multiple first address character segments; Each of the first address character segments is rewritten to obtain the second address character segment; The destination Internet Protocol address is generated by combining each of the second address character segments.

4. The method as described in claim 1, characterized in that, The cloud private network connection scenario refers to a communication scenario within the cloud private network domain. The step of rewriting the traffic packets to obtain the destination Internet Protocol address based on the cloud private network connection scenario includes: Parse the communication protocol tag message to obtain the header tag message; The initial packet Internet Protocol address in the header tag message is rewritten to obtain the destination Internet Protocol address.

5. The method as described in claim 4, characterized in that, The step of rewriting the initial packet Internet Protocol address in the header tag message to obtain the destination Internet Protocol address includes: Remove the top-level tag message from the header tag message to obtain the bottom-level tag message; Obtain the initial packet Internet Protocol address from the underlying tag packet; Add padding characters to the initial packet Internet Protocol address to obtain the target packet Internet Protocol address; The target message Internet Protocol address is decomposed into multiple third address character segments; Each third address character segment is rewritten to obtain the fourth address character segment; The destination Internet Protocol address is generated by combining each of the fourth address character segments.

6. The method as described in claim 1, characterized in that, After determining that the service corresponding to the destination Internet Protocol address is the target service, the method further includes: The traffic message is sent to the execution program corresponding to the target service.

7. A device for determining business traffic, characterized in that, The device includes: The acquisition module is used to acquire traffic packets from the cloud private network; The first determining module is used to determine the cloud private network connection scenario of the cloud private network based on the data format of the traffic packet; The data rewriting module is used to rewrite the traffic packets according to the cloud private network connection scenario to obtain the destination Internet Protocol address; The second determining module is used to determine that the service corresponding to the destination Internet Protocol address is the target service; The first determining module includes: The first determining unit is used to determine, when a communication interface address exists in the traffic packet, that the cloud private network connection scenario is a cloud private network edge access scenario, wherein the communication interface address includes a MAC address and a VLAN address. The second determining unit is used to determine that the cloud private network connection scenario is a communication scenario within the cloud private network domain when there are communication protocol tag messages related to MPLS in the traffic packets.

8. A device for determining service traffic, characterized in that, The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the method as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the method as described in any one of claims 1-6.

10. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device causes the electronic device to perform the method as described in any one of claims 1-6.

Images