WO2020000603A1 - 一种确定数据流的映射地址的方法及服务器 - Google Patents

一种确定数据流的映射地址的方法及服务器 Download PDF

Info

Publication number
WO2020000603A1
WO2020000603A1 PCT/CN2018/101522 CN2018101522W WO2020000603A1 WO 2020000603 A1 WO2020000603 A1 WO 2020000603A1 CN 2018101522 W CN2018101522 W CN 2018101522W WO 2020000603 A1 WO2020000603 A1 WO 2020000603A1
Authority
WO
WIPO (PCT)
Prior art keywords
data stream
current data
historical data
identifier
current
Prior art date
Application number
PCT/CN2018/101522
Other languages
English (en)
French (fr)
Inventor
杨尚斌
Original Assignee
网宿科技股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 网宿科技股份有限公司 filed Critical 网宿科技股份有限公司
Priority to EP18921289.7A priority Critical patent/EP3624428A4/en
Priority to US16/461,231 priority patent/US10924402B2/en
Publication of WO2020000603A1 publication Critical patent/WO2020000603A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2521—Translation architectures other than single NAT servers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2455—Query execution
    • G06F16/24568—Data stream processing; Continuous queries
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/255—Maintenance or indexing of mapping tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2557—Translation policies or rules

Definitions

  • the present invention relates to the field of Internet technologies, and in particular, to a method and a server for determining a mapping address of a data stream.
  • NAT Network Address Translation
  • the bysource mechanism can maintain the historical consistency of data streams, that is, data streams from the same source IP address should be mapped to the same IP address. For example, when the protocols are consistent, the source IP address of a data stream is 1.1.1.1:1, and when the data stream is sent to the destination IP address 114.114.114.114:53, the NAT device maps its source IP address to 3.3. .3.3: 3, resulting in a data stream from 3.3.3.3:3 to 114.114.114.114:53.
  • the NAT device also needs to map the source IP address 1.1.1.1:1 to 3.3.3.3:3. , Thus forming a data stream from 3.3.3.3:3 to 8.8.8.8:53.
  • the bysource mechanism may conflict with the actual service configuration.
  • the actual service configuration may need to determine the mapping address of the data stream according to the target IP, and the bysource mechanism determines the mapping address of the data stream according to the source information.
  • the bysource mechanism has a higher priority in the kernel, the situation that the address obtained by the final mapping does not match the actual service configuration. It can be seen that the current bysource mechanism followed by the NAT device is not flexible enough to be compatible with the actual service configuration.
  • the purpose of this application is to provide a method and a server for determining a mapping address of a data stream, which can be compatible with the actual service configuration.
  • the present application provides a method for determining a mapping address of a data stream, the method includes: receiving a newly created current data stream, and recording a configuration identifier and a routing identifier of the current data stream; Source information of the current data stream, query historical data streams that match the current data stream; wherein the source information includes at least a source transport protocol, a source address, and a source port, and the historical data stream has a destination mapping address; The configuration identifier and the routing identifier of the current data stream are compared with the configuration identifier and the routing identifier of the historical data stream, respectively, and according to the comparison result, it is determined whether the current data stream uses a target mapping address of the historical data stream.
  • another aspect of the present application further provides a server, which includes: a current data stream receiving unit, configured to receive a newly created current data stream, and record a configuration identifier and a routing identifier of the current data stream; A historical data stream matching unit, configured to query a historical data stream that matches the current data stream according to the source information of the current data stream; wherein the source information includes at least a source transmission protocol, a source address, and a source port, The historical data stream has a target mapping address; an information comparison unit is configured to compare the configuration identifier and routing identifier of the current data stream with the configuration identifier and routing identifier of the historical data stream, respectively, and judge based on the comparison result. Whether the current data stream uses the target mapping address of the historical data stream.
  • the server includes a memory and a processor.
  • the memory is used to store a computer program.
  • the computer program is executed by the processor, the foregoing method is implemented. .
  • the technical solution provided in this application can record the configuration identifier and routing identifier of the current data stream after receiving the newly created current data stream.
  • the configuration identifier may be used to characterize a version of service configuration information of the current data stream.
  • the route identifier may be used to characterize a transmission path of the current data stream.
  • mapping address of the historical data stream can be used. However, if the configuration identifiers are not consistent, the mapping address of the current data flow can be determined according to the actual service configuration. When the configuration identifiers are the same, if the route identifiers are inconsistent, the priorities of the current route and the historical route can be compared to select a mapped address.
  • the technical solution provided in this application will further compare the configuration identifier and the route identifier, so that the mapped address of the current data stream can be compared with the actual service configuration information Keep the same, thereby solving the problem of conflict between the bysource mechanism and business configuration information.
  • FIG. 1 is a schematic diagram of a method for determining a mapping address of a data stream in an embodiment of the present invention
  • FIG. 2 is a flowchart of determining a mapping address of a data stream in an embodiment of the present invention
  • FIG. 3 is a schematic diagram of function modules of a server in an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a server in an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a computer terminal in an embodiment of the present invention.
  • the embodiment of the present application provides a method for determining a mapping address of a data stream, and the method can be applied to a server having a NAT function.
  • the method may include the following steps.
  • S1 Receive a newly created current data stream, and record a configuration identifier and a route identifier of the current data stream.
  • the server can parse the quintuple information in the current data stream. In this way, the server can know the source address, source port, source transport protocol, destination address, and destination port of the current data stream.
  • the source address, source port, and source transmission protocol of the current data stream can be used as the source information of the current data stream.
  • the transmission path of the current data stream can be determined according to the characteristics of the data stream and according to the service configuration.
  • the transmission path can be characterized by a route identifier.
  • a routing identifier can be assigned to the current data stream.
  • the server can set a unique routing identifier for each transmission path. In this way, after determining the transmission path of the current data stream, the server can query and record the routing identifier corresponding to the transmission path. Because the routing ID is unique, the same transmission path will have the same routing ID, and different transmission paths will have different routing IDs.
  • the server may also record the configuration identifier of the current data stream.
  • the configuration identifier may be used to characterize a version of the service configuration information. Different versions of the service configuration information have different configuration identifiers. In this way, a configuration identifier can be assigned to the current data stream according to the configuration version adopted by the current data stream.
  • the above-mentioned configuration identifier and routing identifier may be character strings or digital codes, which are not limited in this application.
  • S3 Query a historical data stream matching the current data stream according to the source information of the current data stream; wherein the source information includes at least a source transport protocol, a source address, and a source port, and the historical data stream has Destination mapped address.
  • a control for controlling the onsource mechanism on or off can be set in advance.
  • the control may be a program component, and the opening or closing function implemented by the program component may be implemented by instructions.
  • the address mapping on function or the address mapping off function can be triggered by a command line or an interactive gesture.
  • the current state of the control indicates that the bysource mechanism is off, it indicates that the current data stream does not need to determine the mapping address according to the bysource mechanism, but can be determined according to the service configuration information of the current data stream.
  • a mapping address of the current data stream that is, when the bysource mechanism is closed, the history of address mapping can be saved at the application layer (not the kernel layer) according to the actual business configuration information, so that the bysource mechanism in the kernel layer can be separated.
  • the current state of the control indicates that the bysource mechanism is enabled, it indicates that the mapping address of the current data stream needs to be determined according to the bysource mechanism provided in this application. Specifically, first, a historical data stream matching the current data stream may be queried according to the source information of the current data stream. In actual applications, source information of the current data stream may be used as an index condition, and a historical data stream having the same source information as the current data stream may be determined as a historical data stream that matches the current data stream.
  • historical data streams that have been created are usually stored in the server as historical records, and in order not to occupy the storage space of the server for a long time, the server usually sets a specified tracking time when the historical data stream is created.
  • the specified tracking duration can be used to limit the length of time that the historical data stream is inactive. If the duration of the historical data stream in the inactive state reaches the specified tracking duration, the historical record of the historical data stream may be deleted from the server.
  • the specified tracking duration can be flexibly set according to the actual state of the data stream, so that the history record of the historical data stream in the inactive state can be deleted from the server in time.
  • the server when querying historical data streams that match the current data stream, the server can count the stagnation duration of each historical data stream in the inactive state in the historical data stream set, and determine the stagnation in the historical data stream set A candidate historical data stream whose duration is less than the specified tracking duration.
  • the aforementioned historical data stream set may be a database in the server for storing the historical data stream that has been established.
  • the candidate historical data streams selected from the historical data stream collection are currently alive.
  • the mapping addresses selected by these candidate historical data streams can have a retroactive effect on the newly created data streams.
  • a historical data stream that matches the current data stream may be determined from the candidate historical data streams. Specifically, source information of the current data stream may be used as an index condition, and a historical data stream having the same source information as the current data stream in the candidate historical data stream may be determined as historical data that matches the current data stream. flow.
  • the historical record of the historical data stream usually includes the target mapping address corresponding to the historical data stream during transmission.
  • the source address of the historical data stream is 1.1.1.1:1.
  • the source address is mapped to 3.3.3.3:3, and the mapped address can be used as the historical data stream. Destination mapping address. In this embodiment, it is possible to determine whether the current data stream uses the target mapping address through a subsequent determination strategy.
  • the configuration identifier and routing identifier of the current data stream and the historical data stream can be further compared.
  • the configuration identifier can represent the version of the service configuration information. If the configuration identifier is inconsistent, it indicates that although the current data stream and the historical data stream have the same source information, when the actual service configuration information has changed, at this time, the historical data The stream has a destination mapped address that is not applicable to the current data stream. Therefore, in this case, the current data stream does not inherit the target mapping address of the historical data stream, but determines the mapping address of the current data stream according to the service configuration information of the current data stream.
  • the configuration identifiers of the current data stream and the historical data stream are the same, it indicates that the two have the same service configuration information, and at this time, it can be further judged whether the path identifiers of the two are the same.
  • the path identifiers of the two are inconsistent, it indicates that the transmission paths selected by the current data stream and the historical data stream may be inconsistent. If the transmission paths are inconsistent, the actual mapped address corresponding to the source address of the current data stream may also be Inconsistent with the destination mapped address of the historical data stream. In this case, the mapping address of the current data stream may also be determined according to the service configuration information of the current data stream instead of following the traditional bysource mechanism.
  • the path identifiers of the current data stream and the historical data stream are inconsistent, it does not mean that the mapped addresses of the two are completely impossible to match.
  • the current data stream uses a transmission path that is not as cost-effective as the historical data stream, the current data stream and the historical data stream can be forced to maintain the same mapping address.
  • the transmission path selected for historical data streams is from Guangdong to Shanghai to Suzhou, and the transmission path selected for current data streams is from Guangdong to Wenzhou to Suzhou.
  • the communication cost consumed by the current data path may be High, so in this case, you can force the current data stream to still choose the transmission path from Guangdong to Shanghai to Suzhou, so that the mapping address of the current data stream and the historical data stream are maintained in the case of inconsistent routing identifiers
  • the mapped addresses are the same.
  • a priority may be set for each route identifier in advance. In this way, the route identifier itself can represent the priority of the route (transmission path). The higher the priority, the higher the cost performance of the transmission path corresponding to the routing identifier.
  • the priority represented by the route identifier of the current data stream and the priority represented by the route identifier of the historical data stream may be compared. And determine whether the current data stream follows the target mapping address of the historical data stream according to the comparison result. Specifically, if the priority represented by the route identifier of the current data stream is higher than the priority represented by the route identifier of the historical data stream, it indicates that the currently selected transmission path of the current data stream is relatively cost-effective, and therefore the history may not be used.
  • the target mapping address of the data stream, but the mapping address of the current data stream is determined according to the service configuration information of the current data stream.
  • the priority represented by the routing identifier of the current data stream is lower than or equal to the priority represented by the routing identifier of the historical data stream, it means that the current cost-effective transmission path is not as cost-effective as the historical data stream.
  • the cost performance of the transmission path is high, so the source address of the current data stream can be mapped to the destination mapping address of the historical data stream, thereby keeping the mapping address consistent with the historical data stream.
  • the configuration identifier and routing identifier of the current data stream correspond to the configuration identifier and routing identifier of the historical data stream, respectively, it indicates that the current data stream and the historical data stream have the same service configuration information. And the same transmission path is selected. At this time, the source address of the current data stream can be directly mapped to the destination mapping address of the historical data stream.
  • the technical solution provided in this application can flexibly adjust the designated tracking time according to the actual situation of the data flow, thereby alleviating problems such as unreasonable traffic load and improper routing of data flow.
  • the control that controls the onsource mechanism on or off can choose to follow the bysource mechanism or the actual service configuration information to determine the mapping address of the data stream. Furthermore, based on the source information, add an additional comparison process of the configuration identifier and the route identifier. The influence of service configuration information and transmission path on the mapping address can be fully considered, thereby making the mapping address selected by the current data stream more reasonable.
  • this application further provides a server, where the server includes:
  • a current data stream receiving unit configured to receive a newly created current data stream and record a configuration identifier and a routing identifier of the current data stream
  • a historical data stream matching unit configured to query a historical data stream that matches the current data stream according to the source information of the current data stream; wherein the source information includes at least a source transmission protocol, a source address, and a source port, The historical data stream has a target mapping address;
  • An information comparison unit configured to compare the configuration identifier and routing identifier of the current data stream with the configuration identifier and routing identifier of the historical data stream, and determine whether the current data stream uses the history according to the comparison result The destination mapped address of the data stream.
  • the server is provided with controls for controlling the onsource mechanism to be turned on or off; correspondingly, the server further includes:
  • a function determining unit configured to query a historical data stream that matches the current data stream according to the source information of the current data stream if the current state of the control indicates that the bysource mechanism is on; if the control The current state indicates that the bysource mechanism is closed, and the mapping address of the current data stream is determined according to the service configuration information of the current data stream.
  • the server sets a specified tracking duration in advance; accordingly, the historical data stream matching unit includes:
  • a dead time screening module configured to count the dead time of each historical data stream in an inactive state in the historical data stream set, and determine a candidate historical data stream whose dead time is less than the specified tracking time in the historical data stream set;
  • the historical data stream determining module is configured to determine a historical data stream in the candidate historical data stream that has the same source information as the current data stream as a historical data stream that matches the current data stream.
  • the route identifier is used to characterize the priority of a route; accordingly, the information comparison unit includes:
  • a priority comparison module is configured to compare the priority represented by the routing identifier of the current data stream with the historical data stream if the configuration identifier of the current data stream is consistent with the configuration identifier of the historical data stream. The priority represented by the route identifier, and according to the comparison result, it is judged whether the current data stream follows the target mapping address of the historical data stream.
  • the information comparison unit is configured to: if the priority represented by the routing identifier of the current data stream is higher than the priority represented by the routing identifier of the historical data stream, according to the service configuration of the current data stream The information determines the mapping address of the current data stream; if the priority represented by the routing identifier of the current data stream is lower than or equal to the priority represented by the routing identifier of the historical data stream, the source of the current data stream is identified
  • the address mapping is a target mapping address of the historical data stream.
  • the present application further provides a server.
  • the server includes a memory and a processor.
  • the memory is used to store a computer program.
  • the computer program is executed by the processor, the foregoing method may be implemented.
  • the computer terminal 10 may include one or more (only one shown in the figure) a processor 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), The memory 104 and the transmission module 106 for communication functions.
  • a processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA
  • the memory 104 and the transmission module 106 for communication functions.
  • the structure shown in FIG. 5 is only schematic, and it does not limit the structure of the electronic device.
  • the computer terminal 10 may further include more or fewer components than those shown in FIG. 5, or have a configuration different from that shown in FIG.
  • the memory 104 may be used to store software programs and modules of application software.
  • the processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104.
  • the memory 104 may include a high-speed random access memory, and may further include a non-volatile memory, such as one or more magnetic storage devices, a flash memory, or other non-volatile solid-state memory.
  • the memory 104 may further include memory remotely disposed with respect to the processor 102, and these remote memories may be connected to the computer terminal 10 through a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
  • the transmission device 106 is used for receiving or transmitting data via a network.
  • a specific example of the network described above may include a wireless network provided by a communication provider of the computer terminal 10.
  • the transmission device 106 includes a network adapter (NIC), which can be connected to other network devices through a base station so as to communicate with the Internet.
  • the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet in a wireless manner.
  • RF radio frequency
  • the technical solution provided in this application can record the configuration identifier and routing identifier of the current data stream after receiving the newly created current data stream.
  • the configuration identifier may be used to characterize a version of service configuration information of the current data stream.
  • the route identifier may be used to characterize a transmission path of the current data stream.
  • mapping address of the historical data stream can be used. However, if the configuration identifiers are not consistent, the mapping address of the current data flow can be determined according to the actual service configuration. When the configuration identifiers are the same, if the route identifiers are inconsistent, the priorities of the current route and the historical route can be compared to select a mapped address. It can be seen that, in addition to referring to the source information of the current data stream and the historical data stream, the technical solution provided in this application will further compare the configuration identifier and the route identifier, so that the mapped address of the current data stream can be compared with the actual service configuration information. Keep the same, thereby solving the problem of conflict between the bysource mechanism and business configuration information.
  • each embodiment can be implemented by means of software plus a necessary universal hardware platform, and of course, can also be implemented by hardware.
  • the above-mentioned technical solution essentially or part that contributes to the existing technology can be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic A disc, an optical disc, and the like include instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in various embodiments or certain parts of the embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Computational Linguistics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明公开了一种确定数据流的映射地址的方法及服务器，其中，所述方法包括：接收新建的当前数据流，并记录所述当前数据流的配置标识和路由标识；根据所述当前数据流的源信息，查询与所述当前数据流相匹配的历史数据流；其中，所述源信息包括源传输协议、源地址以及源端口，所述历史数据流具备目标映射地址；将所述当前数据流的配置标识和路由标识分别与所述历史数据流的配置标识和路由标识进行对比，并根据对比结果，判断所述当前数据流是否沿用所述历史数据流的目标映射地址。本申请提供的技术方案，能够与实际的业务配置相兼容。

Description

一种确定数据流的映射地址的方法及服务器 技术领域
本发明涉及互联网技术领域，特别涉及一种确定数据流的映射地址的方法及服务器。
背景技术
随着互联网技术的不断发展，互联网中终端设备的数量也在不断增多。为了缓解由于终端设备增多而导致的IP地址枯竭的问题，产生了NAT(Network Address Translation，网络地址转换)设备。NAT设备可以将专用网中部分终端设备的私有IP地址映射为因特网中的公有IP地址，从而可以使用少量的公有IP地址来代表较多的私有IP地址。
目前，NAT设备在运行时，通常需要遵循bysource机制。该bysource机制可以保持数据流的历史一致性，即来自同一个源IP地址的数据流应当被映射至同一个IP地址。例如，在协议一致的情况下，某个数据流的源IP地址为1.1.1.1：1，该数据流在发往目标IP地址114.114.114.114:53时,NAT设备将其源IP地址映射为3.3.3.3:3，从而形成了从3.3.3.3:3到114.114.114.114:53的数据流。那么当该源IP地址1.1.1.1:1后续发起去往8.8.8.8:53的数据流时，根据历史一致性，NAT设备同样需要将源IP地址1.1.1.1:1映射为3.3.3.3:3，从而形成了从3.3.3.3:3到8.8.8.8:53的数据流。
然而，在实际应用中，bysource机制与实际的业务配置可能会出现冲突。例如，实际的业务配置可能需要按照目标IP来确定数据流的映射地址，而bysource机制是按照源信息来确定数据流的映射地址。这样，由于bysource机制在内核中优先级较高，从而导致最终映射得到的地址与实际的业务配置不符的情况。由此可见，当前NAT设备遵循的bysource机制不够灵活，无法兼容实际的业务配置。
发明内容
本申请的目的在于提供一种确定数据流的映射地址的方法及服务器，能够与实际的业务配置相兼容。
为实现上述目的，本申请一方面提供一种确定数据流的映射地址的方法，所述方法包括：接收新建的当前数据流，并记录所述当前数据流的配置标识和路由标识；根据所述当前数据流的源信息，查询与所述当前数据流相匹配的历史数据流；其中，所述源信息至少包括源传输协议、源地址以及源端口，所述历史数据流具备目标映射地址；将所述当前数据流的配置标识和路由标识分别与所述历史数据流的配置标识和路由标识进行对比，并根据对比结果，判断所述当前数据流是否沿用所述历史数据流的目标映射地址。
为实现上述目的，本申请另一方面还提供一种服务器，所述服务器包括：当前数据流接收单元，用于接收新建的当前数据流，并记录所述当前数据流的配置标识和路由标识；历史数据流匹配单元，用于根据所述当前数据流的源信息，查询与所述当前数据流相匹配的历史数据流；其中，所述源信息至少包括源传输协议、源地址以及源端口，所述历史数据流具备目标映射地址；信息对比单元，用于将所述当前数据流的配置标识和路由标识分别与所述历史数据流的配置标识和路由标识进行对比，并根据对比结果，判断所述当前数据流是否沿用所述历史数据流的目标映射地址。
为实现上述目的，本申请另一方面还提供一种服务器，所述服务器包括存储器和处理器，所述存储器用于存储计算机程序，所述计算机程序被所述处理器执行时，实现上述的方法。
由上可见，本申请提供的技术方案，在接收到新建的当前数据流后，可以记录该当前数据流的配置标识和路由标识。其中，所述配置标识可以用于表征所述当前数据流的业务配置信息的版本。所述路由标识可以用于表征所述当前数据流的传输路径。在判断该当前数据流是否沿用历史数据流的映射地址时，可以将当前数据流的源信息作为索引条件，查询与该当前数据流相匹配的历史数据流。然后，可以进一步地将当前数据流的配置标识和路由标识分别与该历史数据流的配置标识和路由标识进行比较，如果两者均对应一致，则表明当前数据流的业务配置信息以及传输路径均没有发生改变，此时可以沿用历史数据流的映射地址。但是，如果配置标识不一致，则可以按照实际的业务配置来确定当前数据流的映射地址。在配置标识相同的情况下，如果路由标识不一致， 则可以比较当前路由和历史路由的优先级来选择映射地址。由此可见，本申请提供的技术方案，除了参考当前数据流和历史数据流的源信息，还会进一步地对比配置标识以及路由标识，从而使得当前数据流的映射地址可以与实际的业务配置信息保持一致，从而解决了bysource机制与业务配置信息相冲突的问题。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例中确定数据流的映射地址的方法示意图；
图2是本发明实施例中确定数据流的映射地址的流程图；
图3是本发明实施例中服务器的功能模块示意图；
图4是本发明实施例中服务器的结构示意图；
图5是本发明实施例中计算机终端的结构示意图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施方式作进一步地详细描述。
实施例一
本申请实施方式提供一种确定数据流的映射地址的方法，该方法可以应用于具备NAT功能的服务器中。具体地，请参阅图1和图2，所述方法可以包括以下步骤。
S1：接收新建的当前数据流，并记录所述当前数据流的配置标识和路由标识。
在本实施方式中，新建的当前数据流达到服务器后，服务器可以解析该当前数据流中的五元组信息。这样，服务器可以获知该当前数据流的源地址、源端口、源传输协议、目标地址以及目标端口等信息。其中，当前数据流的源地址、源端口以及源传输协议可以作为当前数据流的源信息。
在本实施方式中，，根据数据流的特征，按照业务配置，可以确定出该当前 数据流的传输路径。该传输路径可以通过路由标识来表征。这样，按照所述当前数据流的传输路径，可以为所述当前数据流分配路由标识。具体地，服务器中可以针对每条传输路径，可以分别设定唯一的路由标识。这样，在确定出当前数据流的传输路径之后，服务器便可以查询并记录该传输路径对应的路由标识。由于路由标识具备唯一性，因此，相同的传输路径会具备相同的路由标识，而不同的传输路径则会具备不同的路由标识。
在本实施方式中，考虑到数据流的实际业务配置信息会对数据流的传输有较大的影响，因此，服务器还可以记录所述当前数据流的配置标识。其中，所述配置标识可以用于表征所述业务配置信息的版本。不同版本的业务配置信息，其对应的配置标识也不相同。这样，可以按照所述当前数据流采用的配置版本，为所述当前数据流分配配置标识。在本实施方式中，上述的配置标识和路由标识可以是字符串，也可以是数字编码，本申请对此并不做限定。
S3：根据所述当前数据流的源信息，查询与所述当前数据流相匹配的历史数据流；其中，所述源信息至少包括源传输协议、源地址以及源端口，所述历史数据流具备目标映射地址。
在本实施方式中，可以预先设置用于控制bysource机制开启或关闭的控件。该控件可以是一个程序组件，该程序组件实现的开启或者关闭功能可以通过指令来实现。例如，可以通过命令行或者交互手势来触发地址映射开启功能或者地址映射关闭功能。
在本实施方式中，当所述控件当前所处的状态表征所述bysource机制关闭，则表明当前数据流无需按照bysource机制来确定映射地址，而是可以按照所述当前数据流的业务配置信息确定所述当前数据流的映射地址。也就是说，当bysource机制关闭时，可以根据实际的业务配置信息，在应用层(而非内核层)保存地址映射的历史记录，从而可以脱离内核层中的bysource机制。
在本实施方式中，若所述控件当前所处的状态表征所述bysource机制开启，则表明此时需要按照本申请提供的bysource机制来确定当前数据流的映射地址。具体地，首先可以根据所述当前数据流的源信息，查询与所述当前数据流相匹配的历史数据流。在实际应用中，可以将当前数据流的源信息作为索引条件，将与所述当前数据流具备相同源信息的历史数据流确定为与所述当前数据流相匹配的历史数据流。
一般而言，曾经创建过的历史数据流通常会作为历史记录保存在服务器中，而为了不长期占用服务器的存储空间，在历史数据流创建时，服务器通常会设定一个指定跟踪时长。该指定跟踪时长可以用于限制历史数据流处于未活动状态的时长。如果历史数据流处于未活动状态的时长达到所述指定跟踪时长，则可以将该历史数据流的历史记录从服务器中删除。通常而言，如果该指定跟踪时长过久，会导致流量负载不合理以及数据流路由不当等问题。因此，在本实施方式中，可以根据数据流的实际状态，灵活设置该指定跟踪时长，从而可以及时将处于未活动状态的历史数据流的历史记录从服务器中删除。
在本实施方式中，一旦历史数据流处于未活动状态的时长达到了指定跟踪时长，在服务器中便无法查询到该历史数据流。鉴于此，服务器在查询与所述当前数据流相匹配的历史数据流时，可以统计历史数据流集合中各个历史数据流处于未活动状态的停滞时长，并在所述历史数据流集合中确定停滞时长小于所述指定跟踪时长的候选历史数据流。上述的历史数据流集合可以是服务器中用于存放曾经建立的历史数据流的数据库。从历史数据流集合中筛选出的候选历史数据流当前均处于存活状态，这些候选历史数据流选用的映射地址对当前新建的数据流可以具备追溯效果。在确定所述当前数据流的映射地址时，可以从候选历史数据流中确定与所述当前数据流相匹配的历史数据流。具体地，可以将当前数据流的源信息作为索引条件，将所述候选历史数据流中与所述当前数据流具备相同源信息的历史数据流确定为与所述当前数据流相匹配的历史数据流。
在本实施方式中，历史数据流的历史记录中通常会包含该历史数据流在传输时对应的目标映射地址。例如，该历史数据流的源地址为1.1.1.1:1，NAT设备在对该历史数据流进行处理时，将源地址映射为3.3.3.3:3，那么映射后的地址便可以作为历史数据流的目标映射地址。在本实施方式中，可以通过后续的判断策略，来判断当前数据流是否沿用该目标映射地址。
S5：将所述当前数据流的配置标识和路由标识分别与所述历史数据流的配置标识和路由标识进行对比，并根据对比结果，判断所述当前数据流是否沿用所述历史数据流的目标映射地址。
在本实施方式中，在根据当前数据流的源信息查询出匹配的历史数据流之后，还可以进一步地对比当前数据流和历史数据流的配置标识和路由标识。其 中，由于配置标识可以表征业务配置信息的版本，如果配置标识不一致，则表明当前数据流与历史数据流尽管具备相同的源信息，当实际的业务配置信息已经发生了改变，此时，历史数据流具备的目标映射地址并不适用于当前数据流。因此，在这种情况下，当前数据流并不会沿用历史数据流的目标映射地址，而是会按照所述当前数据流的业务配置信息确定所述当前数据流的映射地址。
此外，如果当前数据流和历史数据流的配置标识一致，则表明两者具备相同的业务配置信息，此时可以进一步地判断两者的路径标识是否一致。通常而言，如果两者的路径标识不一致，则表明当前数据流和历史数据流选用的传输路径可能不一致，而传输路径不一致的情况下，当前数据流的源地址对应的实际映射地址可能也会与历史数据流的目标映射地址不一致。在这种情况下，也可以不遵循传统的bysource机制，而是按照所述当前数据流的业务配置信息确定所述当前数据流的映射地址。
当然，在实际应用中，当前数据流和历史数据流的路径标识不一致时，也并非表示两者的映射地址完全不可能一致。在某些场景下，如果当前数据流选用的传输路径并没有历史数据流选用的传输路径的性价比高，则可以强制使得当前数据流与历史数据流保持相同的映射地址。举例来说，历史数据流选用的传输路径是从广东到上海再到苏州，而当前数据流选用的传输路径是从广东到温州再到苏州，当前数据流选用的传输路径消耗的通信资费可能会较高，因此，在这种情况下，可以强制当前数据流依然选择从广东到上海再到苏州的传输路径，从而使得在路由标识不一致的情况下，保持当前数据流的映射地址与历史数据流的映射地址一致。具体地，在服务器中，可以预先为各个路由标识设定优先级。这样，路由标识本身便可以表征路由(传输路径)的优先级。其中，该优先级越高，表示路由标识对应的传输路径的性价比越高。那么在所述当前数据流的配置标识与所述历史数据流的配置标识一致的情况下，可以对比所述当前数据流的路由标识表征的优先级和所述历史数据流的路由标识表征的优先级，并根据对比结果判断所述当前数据流是否沿用所述历史数据流的目标映射地址。具体地，若所述当前数据流的路由标识表征的优先级高于所述历史数据流的路由标识表征的优先级，则表明当前数据流目前选用的传输路径性价比较高，因此可以不沿用历史数据流的目标映射地址，而是按照所述当前数据流的业务配置信息确定所述当前数据流的映射地址。相反，若所述当前数据流的路 由标识表征的优先级低于或者等同于所述历史数据流的路由标识表征的优先级，则表明当前数据流目前选用的传输路径性价比并不比历史数据流选用的传输路径的性价比高，因此可以将所述当前数据流的源地址映射为所述历史数据流的目标映射地址，从而与历史数据流保持映射地址一致。
在本实施方式中，若所述当前数据流的配置标识和路由标识分别与所述历史数据流的配置标识和路由标识对应一致，则表明当前数据流与历史数据流具备相同的业务配置信息，并且选用了相同的传输路径，此时，可以直接将所述当前数据流的源地址映射为所述历史数据流的目标映射地址。
由上可见，本申请提供的技术方案，一方面可以根据数据流的实际情况，灵活调整指定跟踪时长，从而缓解流量负载不合理以及数据流选路不当等问题；另一方面，通过设置用于控制bysource机制开启或关闭的控件，可以选择遵循bysource机制还是按照实际的业务配置信息来确定数据流的映射地址；再者，在源信息的基础上，添加配置标识和路由标识的额外对比过程，可以充分考虑业务配置信息和传输路径对映射地址的影响，进而使得当前数据流选用的映射地址更加合理。
实施例二
请参阅图3，本申请还提供一种服务器，所述服务器包括：
当前数据流接收单元，用于接收新建的当前数据流，并记录所述当前数据流的配置标识和路由标识；
历史数据流匹配单元，用于根据所述当前数据流的源信息，查询与所述当前数据流相匹配的历史数据流；其中，所述源信息至少包括源传输协议、源地址以及源端口，所述历史数据流具备目标映射地址；
信息对比单元，用于将所述当前数据流的配置标识和路由标识分别与所述历史数据流的配置标识和路由标识进行对比，并根据对比结果，判断所述当前数据流是否沿用所述历史数据流的目标映射地址。
在一个实施方式中，所述服务器提供有用于控制bysource机制开启或关闭的控件；相应地，所述服务器还包括：
功能判定单元，用于若所述控件当前所处的状态表征所述bysource机制开启，根据所述当前数据流的源信息，查询与所述当前数据流相匹配的历史数据 流；若所述控件当前所处的状态表征所述bysource机制关闭，按照所述当前数据流的业务配置信息确定所述当前数据流的映射地址。
在一个实施方式中，所述服务器预先设置指定跟踪时长；相应地，所述历史数据流匹配单元包括：
停滞时长筛选模块，用于统计历史数据流集合中各个历史数据流处于未活动状态的停滞时长，并在所述历史数据流集合中确定停滞时长小于所述指定跟踪时长的候选历史数据流；
历史数据流确定模块，用于将所述候选历史数据流中与所述当前数据流具备相同源信息的历史数据流确定为与所述当前数据流相匹配的历史数据流。
在一个实施方式中，所述路由标识用于表征路由的优先级；相应地，所述信息对比单元包括：
优先级对比模块，用于在所述当前数据流的配置标识与所述历史数据流的配置标识一致的情况下，对比所述当前数据流的路由标识表征的优先级和所述历史数据流的路由标识表征的优先级，并根据对比结果判断所述当前数据流是否沿用所述历史数据流的目标映射地址。
在一个实施方式中，所述信息对比单元用于若所述当前数据流的路由标识表征的优先级高于所述历史数据流的路由标识表征的优先级，按照所述当前数据流的业务配置信息确定所述当前数据流的映射地址；若所述当前数据流的路由标识表征的优先级低于或者等同于所述历史数据流的路由标识表征的优先级，将所述当前数据流的源地址映射为所述历史数据流的目标映射地址。
请参阅图4，本申请还提供一种服务器，所述服务器包括存储器和处理器，所述存储器用于存储计算机程序，所述计算机程序被所述处理器执行时，可以实现上述的方法。
请参阅图5，在本申请中，上述实施例中的技术方案可以应用于如图5所示的计算机终端10上。计算机终端10可以包括一个或多个(图中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)、用于存储数据的存储器104、以及用于通信功能的传输模块106。本领域普通技术人员可以理解，图5所示的结构仅为示意，其并不对上述电子装置的结构造成限定。例如，计算机终端10还可包括比图5中所示更多或 者更少的组件，或者具有与图5所示不同的配置。
存储器104可用于存储应用软件的软件程序以及模块，处理器102通过运行存储在存储器104内的软件程序以及模块，从而执行各种功能应用以及数据处理。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至计算机终端10。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106用于经由一个网络接收或者发送数据。上述的网络具体实例可包括计算机终端10的通信供应商提供的无线网络。在一个实例中，传输装置106包括一个网络适配器(Network Interface Controller，NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置106可以为射频(Radio Frequency，RF)模块，其用于通过无线方式与互联网进行通讯。
由上可见，本申请提供的技术方案，在接收到新建的当前数据流后，可以记录该当前数据流的配置标识和路由标识。其中，所述配置标识可以用于表征所述当前数据流的业务配置信息的版本。所述路由标识可以用于表征所述当前数据流的传输路径。在判断该当前数据流是否沿用历史数据流的映射地址时，可以将当前数据流的源信息作为索引条件，查询与该当前数据流相匹配的历史数据流。然后，可以进一步地将当前数据流的配置标识和路由标识分别与该历史数据流的配置标识和路由标识进行比较，如果两者均对应一致，则表明当前数据流的业务配置信息以及传输路径均没有发生改变，此时可以沿用历史数据流的映射地址。但是，如果配置标识不一致，则可以按照实际的业务配置来确定当前数据流的映射地址。在配置标识相同的情况下，如果路由标识不一致，则可以比较当前路由和历史路由的优先级来选择映射地址。由此可见，本申请提供的技术方案，除了参考当前数据流和历史数据流的源信息，还会进一步地对比配置标识以及路由标识，从而使得当前数据流的映射地址可以与实际的业务配置信息保持一致，从而解决了bysource机制与业务配置信息相冲突的问题。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到各实施方式可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件来 实现。基于这样的理解，上述技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行各个实施例或者实施例的某些部分所述的方法。
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (14)

  1. 一种确定数据流的映射地址的方法，其特征在于，所述方法包括：
    接收新建的当前数据流，并记录所述当前数据流的配置标识和路由标识；
    根据所述当前数据流的源信息，查询与所述当前数据流相匹配的历史数据流；其中，所述源信息至少包括源传输协议、源地址以及源端口，所述历史数据流具备目标映射地址；
    将所述当前数据流的配置标识和路由标识分别与所述历史数据流的配置标识和路由标识进行对比，并根据对比结果，判断所述当前数据流是否沿用所述历史数据流的目标映射地址。
  2. 根据权利要求1所述的方法，其特征在于，在接收新建的当前数据流之后，所述方法包括：
    若用于控制bysource机制开启或关闭的控件当前所处的状态表征所述bysource机制开启，根据所述当前数据流的源信息，查询与所述当前数据流相匹配的历史数据流；
    若所述控件当前所处的状态表征所述bysource机制关闭，按照所述当前数据流的业务配置信息确定所述当前数据流的映射地址。
  3. 根据权利要求1所述的方法，其特征在于，查询与所述当前数据流相匹配的历史数据流包括：
    将与所述当前数据流具备相同源信息的历史数据流确定为与所述当前数据流相匹配的历史数据流。
  4. 根据权利要求1所述的方法，其特征在于，所述方法预先设置指定跟踪时长；相应地，查询与所述当前数据流相匹配的历史数据流包括：
    统计历史数据流集合中各个历史数据流处于未活动状态的停滞时长，并在所述历史数据流集合中确定停滞时长小于所述指定跟踪时长的候选历史数据流；
    将所述候选历史数据流中与所述当前数据流具备相同源信息的历史数据流 确定为与所述当前数据流相匹配的历史数据流。
  5. 根据权利要求1所述的方法，其特征在于，判断所述当前数据流是否沿用所述历史数据流的目标映射地址包括：
    若所述当前数据流的配置标识和路由标识分别与所述历史数据流的配置标识和路由标识对应一致，将所述当前数据流的源地址映射为所述历史数据流的目标映射地址；
    若所述当前数据流的配置标识与所述历史数据流的配置标识不一致，或者所述当前数据流的路由标识与所述历史数据流的路由标识不一致，按照所述当前数据流的业务配置信息确定所述当前数据流的映射地址。
  6. 根据权利要求1所述的方法，其特征在于，所述路由标识用于表征路由的优先级；相应地，判断所述当前数据流是否沿用所述历史数据流的目标映射地址包括：
    在所述当前数据流的配置标识与所述历史数据流的配置标识一致的情况下，对比所述当前数据流的路由标识表征的优先级和所述历史数据流的路由标识表征的优先级，并根据对比结果判断所述当前数据流是否沿用所述历史数据流的目标映射地址。
  7. 根据权利要求6所述的方法，其特征在于，根据对比结果判断所述当前数据流是否沿用所述历史数据流的目标映射地址包括：
    若所述当前数据流的路由标识表征的优先级高于所述历史数据流的路由标识表征的优先级，按照所述当前数据流的业务配置信息确定所述当前数据流的映射地址；
    若所述当前数据流的路由标识表征的优先级低于或者等同于所述历史数据流的路由标识表征的优先级，将所述当前数据流的源地址映射为所述历史数据流的目标映射地址。
  8. 根据权利要求1所述的方法，其特征在于，在所述当前数据流新建之后，所述方法还包括：
    按照所述当前数据流采用的配置版本，为所述当前数据流分配配置标识，并按照所述当前数据流的传输路径，为所述当前数据流分配路由标识。
  9. 一种服务器，其特征在于，所述服务器包括：
    当前数据流接收单元，用于接收新建的当前数据流，并记录所述当前数据流的配置标识和路由标识；
    历史数据流匹配单元，用于根据所述当前数据流的源信息，查询与所述当前数据流相匹配的历史数据流；其中，所述源信息至少包括源传输协议、源地址以及源端口，所述历史数据流具备目标映射地址；
    信息对比单元，用于将所述当前数据流的配置标识和路由标识分别与所述历史数据流的配置标识和路由标识进行对比，并根据对比结果，判断所述当前数据流是否沿用所述历史数据流的目标映射地址。
  10. 根据权利要求9所述的服务器，其特征在于，所述服务器提供有用于控制bysource机制开启或关闭的控件；相应地，所述服务器还包括：
    功能判定单元，用于若所述控件当前所处的状态表征所述bysource机制开启，根据所述当前数据流的源信息，查询与所述当前数据流相匹配的历史数据流；若所述控件当前所处的状态表征所述bysource机制关闭，按照所述当前数据流的业务配置信息确定所述当前数据流的映射地址。
  11. 根据权利要求9所述的服务器，其特征在于，所述服务器预先设置指定跟踪时长；相应地，所述历史数据流匹配单元包括：
    停滞时长筛选模块，用于统计历史数据流集合中各个历史数据流处于未活动状态的停滞时长，并在所述历史数据流集合中确定停滞时长小于所述指定跟踪时长的候选历史数据流；
    历史数据流确定模块，用于将所述候选历史数据流中与所述当前数据流具备相同源信息的历史数据流确定为与所述当前数据流相匹配的历史数据流。
  12. 根据权利要求9所述的服务器，其特征在于，所述路由标识用于表征路由的优先级；相应地，所述信息对比单元包括：
    优先级对比模块，用于在所述当前数据流的配置标识与所述历史数据流的配置标识一致的情况下，对比所述当前数据流的路由标识表征的优先级和所述历史数据流的路由标识表征的优先级，并根据对比结果判断所述当前数据流是否沿用所述历史数据流的目标映射地址。
  13. 根据权利要求12所述的服务器，其特征在于，所述信息对比单元用于若所述当前数据流的路由标识表征的优先级高于所述历史数据流的路由标识表征的优先级，按照所述当前数据流的业务配置信息确定所述当前数据流的映射地址；若所述当前数据流的路由标识表征的优先级低于或者等同于所述历史数据流的路由标识表征的优先级，将所述当前数据流的源地址映射为所述历史数据流的目标映射地址。
  14. 一种服务器，其特征在于，所述服务器包括存储器和处理器，所述存储器用于存储计算机程序，所述计算机程序被所述处理器执行时，实现如权利要求1至8中任一权利要求所述的方法。
PCT/CN2018/101522 2018-06-29 2018-08-21 一种确定数据流的映射地址的方法及服务器 WO2020000603A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18921289.7A EP3624428A4 (en) 2018-06-29 2018-08-21 METHOD AND SERVER FOR DETERMINING THE MAPPING ADDRESS OF A DATA STREAM
US16/461,231 US10924402B2 (en) 2018-06-29 2018-08-21 Method and server for determining a mapping address of a data stream

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810701206.5 2018-06-29
CN201810701206.5A CN110661896B (zh) 2018-06-29 2018-06-29 一种确定数据流的映射地址的方法及服务器

Publications (1)

Publication Number Publication Date
WO2020000603A1 true WO2020000603A1 (zh) 2020-01-02

Family

ID=68985906

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/101522 WO2020000603A1 (zh) 2018-06-29 2018-08-21 一种确定数据流的映射地址的方法及服务器

Country Status (4)

Country Link
US (1) US10924402B2 (zh)
EP (1) EP3624428A4 (zh)
CN (1) CN110661896B (zh)
WO (1) WO2020000603A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109036425B (zh) * 2018-09-10 2019-12-24 百度在线网络技术（北京）有限公司 用于操作智能终端的方法和装置
CN111352642B (zh) * 2020-02-27 2023-08-18 厦门网宿有限公司 服务设备及服务软件升级的方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9178846B1 (en) * 2011-11-04 2015-11-03 Juniper Networks, Inc. Deterministic network address and port translation
CN105100300A (zh) * 2015-08-26 2015-11-25 北京星网锐捷网络技术有限公司 网络地址转换nat的方法及装置
CN106878179A (zh) * 2016-12-14 2017-06-20 新华三技术有限公司 一种报文转发方法及装置

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6154839A (en) * 1998-04-23 2000-11-28 Vpnet Technologies, Inc. Translating packet addresses based upon a user identifier
JP3619411B2 (ja) * 1999-12-03 2005-02-09 富士通株式会社 パケット中継装置
US9602404B2 (en) * 2011-08-17 2017-03-21 Nicira, Inc. Last-hop processing for reverse direction packets
CN103685395A (zh) * 2012-09-14 2014-03-26 腾讯科技（深圳）有限公司 对数据流进行分发处理的方法及系统
US9906436B2 (en) * 2013-08-05 2018-02-27 Futurewei Technologies, Inc. Scalable name-based centralized content routing
US10931478B2 (en) * 2014-10-14 2021-02-23 Mido Holdings Ltd. System and method for distributed flow state P2P setup in virtual networks
EP3248365A1 (en) * 2015-01-20 2017-11-29 Tata Communications (America) Inc. Service dependent ip addresses
US9906560B2 (en) * 2015-08-28 2018-02-27 Nicira, Inc. Distributing remote device management attributes to service nodes for service rule processing
CN110089146B (zh) * 2016-08-24 2022-07-01 维尔塞特公司 通信网络中的装置整形
US10681131B2 (en) * 2016-08-29 2020-06-09 Vmware, Inc. Source network address translation detection and dynamic tunnel creation
CN106603566B (zh) * 2016-12-30 2019-11-19 北京华为数字技术有限公司 一种数据流的检测方法及设备
US10698714B2 (en) * 2017-04-07 2020-06-30 Nicira, Inc. Application/context-based management of virtual networks using customizable workflows
US10534601B1 (en) * 2017-06-30 2020-01-14 Juniper Networks, Inc. In-service software upgrade of virtual router with reduced packet loss
US11102032B2 (en) * 2017-10-02 2021-08-24 Vmware, Inc. Routing data message flow through multiple public clouds
US10855588B2 (en) * 2018-12-21 2020-12-01 Juniper Networks, Inc. Facilitating flow symmetry for service chains in a computer network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9178846B1 (en) * 2011-11-04 2015-11-03 Juniper Networks, Inc. Deterministic network address and port translation
CN105100300A (zh) * 2015-08-26 2015-11-25 北京星网锐捷网络技术有限公司 网络地址转换nat的方法及装置
CN106878179A (zh) * 2016-12-14 2017-06-20 新华三技术有限公司 一种报文转发方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3624428A4 *

Also Published As

Publication number Publication date
US20200274803A1 (en) 2020-08-27
CN110661896A (zh) 2020-01-07
CN110661896B (zh) 2021-06-22
EP3624428A1 (en) 2020-03-18
US10924402B2 (en) 2021-02-16
EP3624428A4 (en) 2020-05-06

Similar Documents

Publication Publication Date Title
US11962501B2 (en) Extensible control plane for network management in a virtual infrastructure environment
US9547502B2 (en) Rebooting InfiniBand clusters
US20150304212A1 (en) Method and apparatus for matching flow table, and switch
US8897134B2 (en) Notifying a controller of a change to a packet forwarding configuration of a network element over a communication channel
TWI675572B (zh) 網路服務系統及網路服務方法
CN108287723B (zh) 一种应用交互方法、装置、物理机及系统
JP5652630B2 (ja) ネットワークシステム、スイッチ、及び接続端末検知方法
WO2018028606A1 (zh) 转发策略配置
US10608899B2 (en) Service directory for quick and simplified application identification
US20150120909A1 (en) Dns-assisted application identification
JP5662579B2 (ja) ネットワーク接続をアイドリングさせる方法及び装置
US10050859B2 (en) Apparatus for processing network packet using service function chaining and method for controlling the same
TWI674780B (zh) 網路服務系統及網路服務方法
WO2020000603A1 (zh) 一种确定数据流的映射地址的方法及服务器
US11012304B1 (en) Networking device replacement system
CN110581805A (zh) 路由表更新方法、装置、交换机及存储介质
WO2022062390A1 (zh) 一种多路径连接方法、装置及电子设备和存储介质
US10171306B2 (en) Automatic discovery and provisioning of multi-chassis etherchannel peers
US10659351B2 (en) Dataflow consistency verification
CN109995678B (zh) 报文传输方法及装置
US9083732B2 (en) Establishing communication between entities in a shared network
US9762661B1 (en) Managing networks in a virtualization system
US12028253B2 (en) Control plane driven summarization in a network
WO2024021896A1 (zh) 数据传输方法、切片关系映射方法、电子设备和介质
US20230198902A1 (en) Control plane driven summarization in a network

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2018921289

Country of ref document: EP

Effective date: 20191210

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18921289

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE