Data communication method

The method and system provide flexible and reliable data communication by using configurable data blocks to establish direct connections between computers, overcoming limitations of centralized tunneling methods and enhancing security and performance.

JP7584159B2Active Publication Date: 2024-11-15DULL PTY LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2022525595
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-10-30
Filing Date
2020-03-13
Publication Date
2024-11-15
Estimated Expiration
2040-03-13

AI Technical Summary

Technical Problem

Current network tunneling methods lack flexibility, versatility, and reliability, often requiring a centralized controller that can lead to performance limitations and a single point of failure.

Method used

A method and system for data communication over networks that utilize configurable data blocks to establish direct connections between computers, allowing for customizable and decentralized data transmission through encapsulated and non-encapsulated protocols, with optional relay or connection servers for facilitating communication.

Benefits of technology

Enables flexible, reliable, and secure data communication between computers without a centralized controller, reducing latency and improving throughput while allowing for customizable and secure data connections at the application level.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007584159000001
    Figure 0007584159000001
  • Figure 0007584159000002
    Figure 0007584159000002
  • Figure 0007584159000003
    Figure 0007584159000003
Patent Text Reader

Abstract

A method for data communication over a network is provided, comprising: configuring, on a first computer, a first sequence including an ordered plurality of first blocks associated with at least one segment; and initializing the first blocks to perform data communication between the first computer and a second computer, each first block representing a configurable data communication function. The blocks may be assigned to a plurality of segments and then interconnected. The communication may be between other computers and / or applications. A corresponding system is also provided.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates generally to methods and systems for data communication over a network, such as configurable network communication. [Background technology]

[0002] Network tunneling is known that can virtually connect two private networks through a public network. However, such tunneling methods generally lack flexibility and versatility, which limits latency, throughput, reliability, reach, and potential new features. Current tunneling techniques also typically require a centralized controller that restricts packets with a firewall that allows only authorized communication. This can result in limitations regarding performance (e.g., latency) and may also result in a central point of failure. Summary of the Invention

[0003] According to one aspect of the present disclosure, there is provided a method for data communication over a network, comprising: configuring, on a first computer, a first sequence including an ordered plurality of first blocks associated with at least one segment; and initializing the first blocks to perform data communication between the first computer and a second computer, wherein each first block represents a configurable data communication function.

[0004] In one embodiment, the method further includes the steps of allocating one or more first blocks to a first segment and allocating one or more other first blocks to a second segment, initializing the first blocks of the first segment and initializing the first blocks of the second segment, and then causing data communication between the first blocks of the first segment and the first blocks of the second segment. At least one segment may be associated with data communication with an application running on the first computer. At least one segment may be associated with data communication with the second computer or another computer over a data network.

[0005] In one embodiment, the method further includes configuring on the second computer a second sequence including an ordered plurality of second blocks associated with at least one segment, each of the one or more second blocks being uniquely associated with the first block, and initializing the second blocks to perform data communication between the first computer and the second computer, each second block representing a configurable data communication function.

[0006] Optionally, the at least one first block is an originating first block configured to interact with an application running on a first computer, and / or the at least one second block is an originating second block configured to interact with an application running on a second computer.

[0007] Optionally, initializing the first block of the segment and / or the second block of the segment comprises traversing one by one separately in a first direction followed by traversing in an opposite second direction, and traversing comprises activating communication functions associated with the first and second blocks according to an activation rule, wherein each first block and each second block may be configurable as a top-down block type or a bottom-up block type, and the activation rule may be such that only communication functions associated with the first and second blocks of the top-down block type are activated when traversed in the first direction and only communication functions associated with the first and second blocks of the bottom-up type are activated when traversed in the second direction.

[0008] Optionally, initializing the first block and / or the second block includes traversing each one separately in only the first direction, and traversing includes activating communication functions associated with the first block and the second block according to an activation rule.

[0009] Optionally, at least one first block and / or at least one second block are configured as an encapsulation block type, such that the communication functions associated with the defined first and second blocks perform data communication after initialization. At least one first block and at least one second block may be configured as a network protocol for communicating with an IP network, e.g. a public network such as the Internet.

[0010] Optionally, at least one first block and / or at least one second block are configured as a non-encapsulated block type such that communication functions associated with said defined first and second blocks are not involved in data communication after initialization.

[0011] In one embodiment, the method further comprises one or more first blocks and / or one or more second blocks associated with a communication function configured to communicate with at least one relay server. The first blocks of the first sequence and the second blocks of the second sequence may communicate with the network via the first blocks and the second blocks configured to communicate with at least one relay server.

[0012] In one embodiment, the method further comprises one or more first blocks and / or one or more second blocks associated with a communication function configured to communicate with the connection server. At least one first block and at least one second block associated with a communication function configured to communicate with the connection server may be used only for initializing data communication.

[0013] Optionally, the initialization of the first sequence is in response to receiving a wake-up command, and / or the initialization of the second sequence is in response to receiving a wake-up command.

[0014] Optionally, data communication occurs between a first application running on the first computer and a second application running on the second computer.

[0015] According to another aspect of the present disclosure, there is provided a method for generating data communication between a plurality of applications, the method comprising performing the method of the above aspect for each of one or more applications running on a first computer and one or more applications running on a second computer.

[0016] According to another aspect of the present disclosure, a system is provided that includes a first computer, the first computer configured to generate a first sequence including an ordered plurality of first blocks associated with at least one segment, initialize the first blocks based on the first sequence, and perform data communication with a second computer based on the initialization of the first blocks, each block representing a configurable data communication function.

[0017] In one embodiment, the first computer is further configured to assign one or more first blocks to the first segment and assign another one or more first blocks to the second segment, initialize the first blocks of the first segment and initialize the first blocks of the second segment, and then cause data communication to occur between the first blocks of the first segment and the first blocks of the second segment. At least one segment may be associated with data communication with an application running on the first computer. At least one segment may be associated with data communication with the second computer or another computer via a data network.

[0018] In one embodiment, the system further includes a second computer configured to generate a second sequence including an ordered plurality of second blocks associated with at least one segment, initialize the second blocks based on the second sequence, and perform data communication with the first computer based on the initialized second blocks, wherein each of the at least one second block is uniquely associated with the first block.

[0019] Optionally, the at least one first block is an originating first block configured to interact with an application running on a first computer, and / or the at least one second block is an originating second block configured to interact with an application running on a second computer.

[0020] Optionally, the first computer is configured to traverse the first block of the segment in a first direction and then in an opposite second direction when initializing the first block, and the second computer is configured to traverse the second block of the segment in the first direction and then in the opposite second direction when initializing the second block, and the traversing includes activating communication functions associated with the first block and the second block according to an activation rule. Each first block and each second block may be configurable as a top-down block type or a bottom-up block type, and the activation rule may be such that only communication functions associated with the first block and the second block of the top-down block type are activated when traversed in the first direction, and only communication functions associated with the first block and the second block of the bottom-up type are activated when traversed in the second direction.

[0021] Optionally, the first computer is configured to traverse a first block of the segment in only a first direction when initializing the first block, and the second computer is configured to traverse a second block of the segment in only the first direction when initializing the second block, the traversing including activating communication functions associated with the first block and the second block in accordance with an activation rule.

[0022] Optionally, at least one first block and / or at least one second block are configured as an encapsulation block type, such that communication functions associated with the defined first and second blocks allow the respective computers to perform data communication after initialization. At least one first block and at least one second block may be configured as a network protocol for communicating with an IP network, e.g. a public network such as the Internet.

[0023] Optionally, at least one first block and / or at least one second block are configured as a non-encapsulated block type such that communication functions associated with said defined first and second blocks are not involved in data communication after initialization.

[0024] In one embodiment, the system further includes one or more first blocks and / or one or more second blocks associated with a communication function configured to communicate with at least one relay server. The first blocks of the first sequence and the second blocks of the second sequence may communicate with the network via the first blocks and the second blocks configured to communicate with at least one relay server. The system may include at least one relay server.

[0025] In one embodiment, the system further includes one or more first blocks and / or one or more second blocks associated with a communication function configured to communicate with a connection server. At least one first block and at least one second block associated with a communication function configured to communicate with a connection server may be used only to initialize data communication. The system may include a connection server.

[0026] Optionally, the initialization of the first sequence is in response to receiving a wake-up command, and / or the initialization of the second sequence is in response to receiving a wake-up command.

[0027] Optionally, data communication occurs between a first application running on the first computer and a second application running on the second computer.

[0028] According to another aspect of the present disclosure there is provided a computer comprising a computer program configured to cause a computer to perform the method of the first aspect.

[0029] As used herein, the word "comprise" or variations such as "comprises" or "comprising" are used in the inclusive sense, i.e., to specify the presence of stated features but not to exclude the presence or addition of further features in various embodiments of the invention. [Brief description of the drawings]

[0030] In order that the invention may be more clearly understood, embodiments will now be described, by way of example, with reference to the accompanying drawings, in which:

[0031] [Figure 1] FIG. 1 illustrates a communication system according to one embodiment. [Diagram 2] FIG. 1 is a schematic diagram of a typical computer. [Diagram 3] FIG. 1 illustrates data communication between two computers. [Figure 4] FIG. 2 is a schematic diagram of a number of blocks. [Diagram 5] FIG. 2 illustrates a method for initiating data communication according to one embodiment. [Figure 6a] FIG. 11 is a diagram showing the order of processing of the first block. [Figure 6b] FIG. 11 is a diagram showing the order of processing of the second block. [Figure 7] FIG. 13 is a diagram illustrating an initialization method. [Figure 8] FIG. 2 is a schematic diagram of data communication in operation according to one embodiment. [Figure 9] FIG. 1 illustrates an embodiment including a relay server. [Figure 10] FIG. 1 illustrates an embodiment including a connection server. [Figure 11] FIG. 1 illustrates an embodiment including a connection server. [Figure 12a] FIG. 1 illustrates an embodiment including an inner sequence and a first sequence. [Figure 12b] FIG. 1 illustrates an embodiment including an inner sequence and a first sequence. [Figure 13a] FIG. 1 illustrates a prior art example of a connection via a VPN. [Figure 13b] FIG. 2 is a diagram illustrating a connection via data communication in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0032] FIG. 1 illustrates a communication system 10 representing an embodiment described herein. The system 10 includes several computers 11 in data communication with a network 15. In this manner, two (or more) computers 11 can perform data communication with each other via said network 15. The network 15 should be understood to represent any interconnection of two or more computing devices, and typically, at least a portion of the network 15 includes a public network, such as the Internet. The data communication may be based, at least in part, on the Internet Protocol (IP). However, other forms of data communication may be included, for example, some of the data communication may include protocols such as Bluetooth or USB. Although computers 11a and 11b are shown in direct data communication with the network 15, computers 11c-11e communicate with the network 15 via a private network 16a, and computers 11f-11h communicate with the network 15 via a private network 16b.

[0033] For purposes of this disclosure, general features shown in the figures are represented by reference numerals, such as computer 11 and network 15. Such reference numerals are shared between figures where appropriate. Where reference to a particular instance of a feature is desired, a lower case suffix is ​​added to the reference numeral. For example, in Figure 1, computer 11a can be distinguished from computer 11b.

[0034] For purposes of this disclosure, computer 11 should be considered to correspond to any suitable computing device having facilities for data communication over network 15. There are numerous implementations of such computers 11, such as, for example, standalone computing hardware (e.g., desktop or laptop computers), standalone servers, distributed computing configurations, mobile devices such as smartphones and tablets, and many others. In FIG. 1, for purposes of illustration, computers 11a and 11f-11h are depicted as servers, and computers 11b-11e are depicted as desktop computers. Computer 11 may, for example, correspond to a virtual computer implemented within a server environment. Thus, two computers 11 may correspond to virtual computers implemented within the same server infrastructure.

[0035] 2, in a general sense, computer 11 includes a processor 20 interfaced to a memory 21 and a network interface 22. The illustrated processor 20 may actually correspond to a single CPU, multiple CPUs, a functionally interconnected network of multiple CPUs implemented in separate hardware, a microcontroller, etc. Memory 21 typically includes volatile and non-volatile memory. Memory 21 is configured to store program instructions executable by processor 20 and provides a data space for storing data used by the program instructions.

[0036] The network interface 22 is configured to enable the processor 20 to communicate data over and receive data via the network 15. The network 15 shown in FIG. 1 should be interpreted as any interconnection of multiple devices, including computing devices and network nodes such as routers and switches. This connection may utilize wired electrical connections, optical connections, and wireless connections (usually many combinations of these). In this regard, data communication is typically defined by one or more protocols, for example the TCP / IP stack common to communication over the Internet. The network 15 may include a public network such as the Internet.

[0037] According to the embodiments described herein, it may be desirable to enable data communication between two computers 11 that may not be part of the same private network 16, with the effect being as if the two computers 11a, 11b were in direct data communication. It may also be desirable to allow a computer 11 to be effectively part of a private network 16 to which it does not already belong. Such a connection may be similar to a network tunnel, i.e., the functionality described herein may be similar or equivalent to known tunneling protocols.

[0038] For ease of explanation, referring to FIG. 3, it is desired to initiate and maintain data communication between computers 11a and 11b. Microtunnels are represented as directed connections by dashed arrows. The labels "first" and "second" are used to distinguish between these computers 11a and 11b, but these refer not only to the first computer 11a and the second computer 11b, but also to various features of said computers 11a and 11b. It should be understood that the terms "first" and "second" do not imply any particular ordering, and that there may be multiple "first" and "second" features associated with the corresponding computers 11a and 11b. In the figure, computers 11a and 11b are shown as servers and desktops, respectively. Of course, the particular computing devices are not limiting of these examples.

[0039] 4 shows a schematic diagram of a number of blocks 41, according to one embodiment. Each block 41 conceptualizes a configurable protocol or other software / algorithm (collectively referred to herein as a "protocol" or "data communication function") for use in initializing and / or ongoing data communication between two computers 11a and 11b. That is, each block 41 is configurable and plays a role in data communication between computers 11a and 11b. Each block 41 is associated with one or more attributes that define the operation of the block 41.

[0040] According to one embodiment, block attributes may define a block type for each block 41. In the embodiment described herein, block types include "encapsulated blocks" and "non-encapsulated blocks."

[0041] The encapsulation block type corresponds to a protocol that is utilized during ongoing data communication between the two computers 11a and 11b, i.e., after the data communication is initialized. In general, the encapsulation block is also involved in the initialization of the data communication. For example, the encapsulation block generally requires configuration for use with the data communication. On the other hand, the non-encapsulation block type corresponds to a protocol that is utilized only during the initialization of the data communication. Thus, the non-encapsulation block is not utilized for ongoing communication via the initialized data communication.

[0042] 4 shows the blocks 41 arranged in two sequences 42 of blocks 41, a first sequence 42a including first blocks 41a-41e and a second sequence 42b including second blocks 41f-41j. The first block 41a is associated with a first computer 11a and the second blocks 41f-41j are associated with a second computer 11b. According to one embodiment, at least one of the first blocks 41a-41e has a paired second block 41f-41j, as indicated by the connecting dotted lines. In the illustrated example, the first blocks 41a-41e are

[0043] According to one embodiment, the first sequence 42a is a data structure that defines a plurality of ordered first blocks 41a-41e, where each first block 41a-41e is conceptually arranged to be adjacent to another first block 41a-41e in a forward direction, a reverse direction, or both. More specifically, only the edge first blocks 41a and 41e are adjacent to only one first block 41b, 41d (respectively). The direction of the arrow 49a indicates the "forward direction". Similarly, the second sequence 42b is a data structure that defines a plurality of ordered second blocks 41f-41j, where each second block 41f-41j is conceptually arranged to be adjacent to another second block 41f-41j in a forward direction, a reverse direction, or both. More specifically, only the second blocks 41f and 41j at the ends are adjacent to only one second block 41g, 41i (respectively). The direction of the arrow 49b indicates the "forward direction." Therefore, this data structure may correspond to a doubly linked list.

[0044] This data structure can be created via a data structure creation process on each computer 11. For example, an application can be provided that is configured to accept configuration parameter entries (from user input, a file, or other known mechanisms) and create a data structure in a valid format. In another example, a user can directly create the data structure via user input. In another example, the data structure is provided from an external source. For example, a user of one computer 11a can communicate the data structure to another computer 11b via a communication means (e.g., network 15) or via storage such as a USB storage. Each sequence 42 is associated with configuration data. The configuration data can be incorporated into the data structure of the sequence 42 or can be stored separately. In practice, a combination of these options can be used. Also, at least a part of the configuration data can be provided from an external source, for example, user input. Thus, the data structure defines the protocol of each block 41 of the sequence and the ordering of the blocks 41, and the configuration data defines the parameters for configuring the protocol associated with the block 41.

[0045] Generally, once data communication is initialized, the protocol defined by the encapsulation block 41 can receive the data, encapsulate or perform other data processing actions according to the protocol and its configuration, and pass the processed data to the next block 41. The data can be passed via (for example) a binary stream interface.

[0046] 5 illustrates a method for initiating data communication according to one embodiment, utilizing the above-mentioned block 41. The method may be implemented by control software running on each computer 11a, 11b, i.e., a first control software running on the first computer 11a and a second control software running on the second computer 11b.

[0047] Step 100 corresponds to constructing a first sequence 42a in the memory of a first computer 11a, and step 101 corresponds to constructing a second sequence 42b in the memory of a second computer 11b. Of course, steps 100 and 101 can be performed in any order, or even simultaneously.

[0048] According to one embodiment, a block pair includes one of the first blocks 41a-41e and one of the second blocks 41f-41j having complementary protocol configurations (e.g., defining the same protocol, configured so that the protocols on the two computers 11a, 11b can talk to each other). For example, the first block 41e may be a TCP client and the second block 41f may be a TCP server, so that a TCP connection can be created between the two blocks 41e, 41f, and thus the computers 11a and 11b can communicate with each other. In another example, the first block 41d may be an AES encryption client and the second block 41g may be an AES encryption server. In general, there may be one or more block pairs.

[0049] According to one embodiment, the initialization includes processing each of the first and second sequences by respective control software running on each computer 11a, 11b.

[0050] In one embodiment, as shown in FIG. 6a, processing the first sequence 42a includes the first control software moving forward through the first sequence 42a, followed by moving backward through the first sequence 42a. Each first block 41a-41e has a direction attribute that defines whether it is being processed during a forward ("top-down") or backward ("bottom-up") move. Although not explicitly described herein, it is expected that some first blocks 41a-41e may be associated with both a forward and a backward direction. Similarly, according to this embodiment shown in FIG. 6b, processing the second sequence 42b includes the second control software moving forward (top-down) through the second sequence 42b, followed by moving backward ("bottom-up") through the second sequence 42b. In these figures, the shaded blocks 41 are the top-down blocks, and the non-shaded blocks 41 are the bottom-up blocks 41. The topmost block is the first block 41 in the sequence when proceeding in a top-down direction, and the bottommost block is the last block 41 in the sequence when proceeding in the same direction. Thus, blocks 41a and 41j are both topmost blocks, and blocks 41e and 41f are both bottommost blocks.

[0051] The concepts of "top-down" and "bottom-up" provide a conceptual link between the order of data flow and the order of initialization.

[0052] In another embodiment, each block 41 is read in order, in which case the ordering of blocks 41 in the data structure may differ from the conceptual ordering described in connection with the above embodiment, but if blocks 41 are processed according to their intended starting order (which may differ from the conceptual ordering of the data flow), then such ordering is selected instead.

[0053] FIG. 7 illustrates an initialization method (i.e., corresponding to step 103) performed by the first computer 11a according to one embodiment. Although reference is made to the first computer 11a merely for ease of explanation, the same method can in general be performed by the second computer 11b. In step 200, an initial first block 41a is identified, which is a block 41a with forward connections only. Then, each first block 41a-41e is checked in the forward direction (i.e., 41a→41b→41c→41d→41e), as described below. In one embodiment, the first control software reads the first data structure to identify the initial first block 41a.

[0054] In step 201, a current block 41 is selected, which is initially the first block 41a. Then, a check step 202 is performed, which corresponds to checking whether the current first block 41 is a top-down block type or not. If the current first block 41 is not a top-down block type, the process proceeds to step 204.

[0055] If the current first block 41 is a top-down block type, an activation process is performed in step 203. The activation process depends on the protocol associated with the current block 41. The activation usually depends on the predetermined block parameters associated with the current block 41. The activation may also depend on data communicated to the current block 41 from the previous block 41 in the activation sequence. In some cases, the activation may require receiving activation data from another computer 11 (possibly the second computer 11b). An example of protocol activation is described below. After the activation of the protocol associated with the current block 41 is completed, the process proceeds to step 204. Usually, the first control software activates the protocol associated with the current first block 41 according to the block parameters associated with the current first block 41.

[0056] In step 204, a check is made as to whether there is another linked first block 41 below, and if not, proceed to step 205. If there is, return to step 201 and this next block 41 becomes the current block 41. In this manner, the first control software continues to check whether each of the first blocks 41a-41e corresponds to a top-down block type, starting from the first block 41a to the first block 41e. In one embodiment, without making an explicit check, it is assumed that the initial first block 41a is a top-down block type.

[0057] Next, the first control software continues to check each of the first blocks 41a-41e in the reverse direction (i.e., 41e → 41d → 41c → 41b → 41a). In step 205, the first block 41e is selected as the current block, and then a check step 206 is performed. This corresponds to checking whether the current first block 41 is a bottom-up block type or not. If the current first block 41 is not a bottom-up block type, the process proceeds to step 208.

[0058] If the current first block 41 is a bottom-up block type, a start-up process is performed in step 204. As mentioned above, the start-up process depends on the protocol associated with the current block 41. Also, the start-up usually depends on the predetermined block parameters associated with the current block 41. Also, the start-up may depend on data communicated to the current block 41 from the previous block 41 in the start-up sequence. In some cases, the start-up may require receiving start-up data from another computer 11 (possibly the second computer 11b). An example of protocol start-up is described below. After the start-up of the protocol associated with the current block 41 is completed, proceed to step 204. Usually, the first control software starts the protocol associated with the current first block 41 according to the block parameters associated with the current block 41.

[0059] In step 208, a check is made to see if there is another linked first block 41 in the backward direction, and if not, proceed to step 209 (end). If there is, return to step 205, which becomes the current block 41. In this manner, the control software continues to check whether each first block 41 corresponds to a bottom-up block type, from the last first block 41 to the first first block 41.

[0060] It should be noted that the methods of Figures 5 and 7 may fail at any point, particularly during initialization of any of blocks 41, for example due to a timeout, authentication failure, network failure, or other relevant reasons. The determination of failure may be made by the relevant control software. Although failure is not shown as a step, generally a notification may be made (e.g., via a messaging service, a pop-up graphic box, test code, a log file entry, or other known means) indicating that a failure has occurred and providing information about the failure, if desired. Typically, the method will stop on initialization failure and no data communication will commence.

[0061] With respect to protocol initiation, encapsulation block 41 remains substantially operational after the method of Figure 7, i.e., encapsulation block 41 corresponds to the protocol utilized for the data communication ongoing in step 104. However, de-encapsulation block 41 is not maintained operational, it is only concerned with the initialization of the data communication.

[0062] Relatedly, the particular protocol utilized to initialize the data communication is defined by a first sequence 42a and a second sequence 42b (which may be complementary and may include one or more paired blocks 41). The first sequence 42a and the second sequence 42b are software configurable data structures. That is, the first sequence and the second sequence are defined as needed. Thus, data communications utilizing different protocols and different initialization parameters can be defined via software configuration, with each protocol being selectable and configurable.

[0063] The encapsulation block 41 defines the ongoing protocols, in that the protocols contribute to the ongoing data communication between the first and second computers 11a, 11b. Typically, these protocols correspond to known networking and data communication protocols such as TCP, HTTP, TLS, AES, etc. However, any suitable protocol may be applied. Thus, activation of the encapsulation block 41 typically corresponds to configuring, for example by the relevant control software, the associated protocols for a particular session of data communication. This may include, in various examples, the assignment of target IP addresses, target ports, encryption keys, etc.

[0064] FIG. 8 shows a schematic diagram of an operational data communication connecting applications 43a and 43b running on computers 11a and 11b, respectively. Due to the nature of the data communication, blocks 41b-41i are substantially invisible to the applications 43. Each application 43 is simply configured to communicate with its respective block 41a and 41j. Thus, the first block 41a can be referred to as the originating first block 41a, and the second block 41j can be referred to as the originating second block 41g. In the example of FIG. 8, it is assumed that blocks 41a-41j are each of the encapsulation block type (and thus involved in the ongoing operation of the data communication).

[0065] According to one embodiment, as illustrated in Fig. 8, a sequence 42 may include blocks 41 associated with different segments 44. A first sequence 42a includes first blocks 41a-41c associated with a first segment 44a and first blocks 41d-41e associated with a second segment 44b (of course, there may be more than two segments 44). The segments 44a, 44b define the first blocks 41a-41c, 41d-41e associated with separate communication functions. In this sense, the sequence 42 serves to bridge communication between two separate applications and / or protocols.

[0066] In one embodiment, at least some of the blocks 41 of a particular sequence 42 may be initialized asynchronously. That is, the control software may be configured to cause the initialization of these blocks 41 to occur independently of the order in which they are initialized. In such a variation, the control software may be configured to feed the output of one block 41 to the input of another block 41 such that, once initialization is complete, data flow occurs according to the correct encapsulation order (for example). However, such blocks 41 may be considered not to be fully initialized until a bitstream is connected to them, and in this respect, the blocks 41 are partially initialized asynchronously. The relationship blocks 41 for interconnections between segments 44 may be considered as encapsulation blocks 41 that are "next to" each other in the sequence 42.

[0067] In a particular example, blocks 41a-41c of a first segment 44a may be initialized asynchronously with blocks 41d-41e of a second segment 44b. Once initialized, the blocks 41 are connected such that an output of block 41 of one segment 44 (e.g., block 41c of the first segment 44a) is connected to an input of block 41 of another segment 44 (e.g., block 41d of the second segment 44b).

[0068] 8, a first segment 44a may be considered to relate to communication with an application 43a, while a second segment may be considered to relate to communication with a second computer 11b (i.e., a second sequence 42b). Although not shown, a similar arrangement of segments 44 may be applied to the second sequence 42b. The advantage of such an arrangement of segments 44 is that different data communication functions can be linked via a particular sequence 42.

[0069] An advantage of the embodiments described herein may be that an administrator, e.g., a system administrator associated with one or more computers 11 involved in an instance of data communication, can configure a particular arrangement with controls to define, e.g., transport protocols, security protocols, etc. This control is implemented by control software configured according to data structures that ensure compatibility on both ends of the data communication (e.g., corresponding to computer 11a and computer 11b). That is, an instance of data communication is customizable.

[0070] FIG. 9 illustrates an embodiment including a relay server 12. Although only one is shown for clarity only, there may generally be multiple relay servers 12. As with computer 11, relay server 12 may be any suitable computing device (including, for example, specialized computing devices such as network routers). Relay server 12 is configured for data communication with both first computer 11a and second computer 11b, typically via network 15. According to this embodiment, data communication is facilitated by relay server 12. That is, relay server 12 is involved in ongoing data communication, and thus includes encapsulating block types. As with first computer 11a and second computer 11b, relay server 12 is associated with block 41 (respectively, if applicable). Thus, relay server 12 includes a data structure, referred to herein as relay sequence 42c, that defines the associated block 41.

[0071] In the figure, the first sequence 42a of the first computer 11a includes the first blocks 41a to 41e, the second sequence 42b of the second computer 11b includes the second blocks 41f to 41j, and the relay sequence 42c of the relay server 12 includes the relay blocks 41p to 41r. In general, one or more of the first blocks 41 may be paired with the relay block 41. For example, as shown in the figure, the first block 41e is paired with the relay block 41p, and the second block 41f is paired with the relay block 41r. The initialization is similar to that described above, but there is a separate initialization of the relay blocks 41p to 41r. This can be performed like the initialization of the first and second blocks 41a to 41j. The relay server 12 is configured as a part of the data communication. Therefore, the first block 41e is normally instructed to communicate with the relay block 41p, and the second block 41f is normally instructed to communicate with the relay block 41r. As shown in the figure, the first block 41c is paired with the second block 41h, and the first block 41d is paired with the second block 41g, and communication between these blocks 41c, 41h, 41d, and 41g is performed via the relay server 12.

[0072] This embodiment may provide several advantages. For example, if the computers 11a and 11b utilize different transport protocols, the relay server 12 may convert between the protocols (e.g., via the relay block 41q). Additionally or alternatively, the relay server 12 may provide a logging function that records the communication between the first computer 11a and the second computer 11b. The relay server 12 may provide said function in a manner that is transparent to the application 43. Another advantage may be that one or both of the computers 11a and 11b may have access to the relay server 12, but a direct connection between said computers 11a and 11b may not be permitted by a firewall or other security measures.

[0073] FIG. 10 shows an embodiment including a connection server 13. The role of the connection server 13 in this embodiment is to contribute to the initialization of data communication, and has no role after the initialization (or may provide the functions of the relay server 12 described below). As with the computer 11, the connection server 13 can be any suitable computing device (including, for example, a specialized computing device such as a network router). In this sense, the connection server 12 is associated with at least one one-off protocol. The functions of the connection server 13 can be combined with those of the relay server 12 in a single computing device (for example, a server). As with the relay server 12, the connection server 13 can provide advantages when a direct connection between the two computers 11a, 11b is not possible (at least in the initialization phase) due to security protocols.

[0074] Figure 10 shows a connection server 13 in data communication with a first computer 11a and a second computer 11b (at least one computer 11 may correspond to the same computing device or may be located in a private network 16 together with the connection server 12, but the data communication is typically via a network 15). In the figure, the connection server 12 is shown "between" the first computer 11a and the second computer 11b. The purpose of the connection server 12 is to facilitate the creation of a connection between the first computer 11a and the second computer 11b.

[0075] 10 also shows a first sequence 42a corresponding to the first blocks 41a-41f associated with the first computer 11a, a second sequence 42b corresponding to the second blocks 41f-41j associated with the second computer 11b, and further connection blocks 41s-41u associated with a connection sequence 42d of the connection server 12. As can be seen, the first blocks 41d and 41e of the first computer 11a are paired with the connection blocks 41s and 41t of the connection server 12, but not with the second computer 11b. Similarly, the second blocks 41f and 41g of the second computer 11b are paired with the connection blocks 41t and 41u of the connection server 12, but not with the first computer 11a. It should be noted that although the first block 41s and the second block 41g are both shown paired with a connection block 41t, in reality they may instead correspond to two pairings with two associated connection blocks 41, simply represented in the figure as one block 41t.

[0076] During the initialization method of Figure 7, the connection server 13 is configured to facilitate the creation of a connection between the first computer 11a and the second computer 11b. Assume that the second computer 11b is configured to advertise its availability for a connection with the connection server 13, and the first computer 11a is configured to communicate with the connection server 13 to identify publications of the second computer 11b. This approach is exemplary and should not be considered limiting.

[0077] In this case, for example, the second block 41f is a top-down block, and the second block 41g is a bottom-up block. Therefore, the second block 41f starts first to establish a data connection with the connection block 41u (they correspond to the TCP protocol). This creates a TCP session between the second computer 11b and the connection server 13. During the initialization of the connection server 13, the connection block 41u is also started before the connection block 41t.

[0078] The second block 41g then communicates with the connection block 41t via the network connection established by the second block 41f and the connection block 41u. The connection block 41t corresponds to the "meet point", i.e. the function where the meet between the first computer 11a and the second computer 11b is configured to take place. The connection block 41t is therefore a non-encapsulating block and is not involved in the actual data communication. The second block 41g is a "meet publisher" and is configured to communicate with the meet point (the connection block 41t) to publish its own availability for receiving a connection. The publication includes identification information to identify a specific instance of the availability (e.g. a code name). The connection block 41t can be configured to maintain the publication of the availability for a predefined time or for a time defined in the communication from the second block 41g. This may be one minute. After this time, the second block 41g may be requested to re-communicate its own availability to the connection block 41t.

[0079] On the other "side", the computer 11a undergoes its own initialization, where the first block 41e is a top-down block and the first block 41d is a bottom-up block. Thus, the first block 41e starts first and establishes a data connection with the connection block 41s (they correspond to the TCP protocol), which creates a TCP session between the first computer 11a and the connection server 13. During the initialization of the connection server 13, the connection block 41s is also started before the connection block 41t.

[0080] The first block 41d then communicates with the connection block 41t via the network connection established by the first block 41e and the connection block 41s. The first block 41d is a "meet subscriber" and is configured to communicate with the meetpoint (connection block 41t) to identify published availability for further connection. The first block 41d communicates this request together with identification information, which is configured so that the meetpoint (connection block 41t) can match the first computer 11a with the second computer 11b. In other words, the identification information provided to the connection block 41t by both the first block 41d and the second block 41g allows the connection server 13 to determine that data communication should be initiated between the corresponding computers 11a, 11b.

[0081] After matching, the connection server 13 can be configured to manage the assistance in establishing data communication in various ways. For example, the TCP connections between the first computer 11a and the connection server 13 and between the second computer 11b and the connection server 13 may be replaced by direct TCP connections between the first computer 11a and the second computer 11b. In another example, the connection server 13 also implements a relay server 12, which proceeds to relay data between the first computer 11a and the second computer 11b. For example, the connection control software running on the connection server 13 can communicate updated information to the associated TCP blocks 41 of the first and second computers 11a, 11b, thereby causing the two to start communicating with each other instead of with the connection server 13.

[0082] After the "meeting" is completed, both the first computer 11a and the second computer 11b can continue with their respective initialization methods. For example, the first sequence 42a may proceed to the first block 41c and the second sequence 42b may proceed to the second block 41h. Thus, as a result of this method, the first block 41d, the second block 41g and the connection blocks 41s-41u are removed, which is shown in FIG. 11. Thus, FIG. 11 shows an example of only the blocks 41 remaining after the data communication initialization, i.e. the blocks 41 corresponding to the encapsulation block type. Thus, the first and second control software are configured to proceed with the initialization process in response to the creation of the connection between the first computer 11a and the second computer 11b.

[0083] An advantage of utilizing the connection server 13 may be that the computers 11a and 11b do not require any knowledge of each other's networks. All that is required is a common identity that allows the connection server 13 to facilitate the initialization of data communication. The connection server 13 may also assist in overcoming firewalls and NATs (for example) without requiring the setting of forwarding rules. When each computer 11a and 11b initiates a connection to the connection server 13, appropriate routing rules may be created on the fly based on known techniques. In one embodiment, the connection server 13 is also the relay server 12, thereby ensuring continuity of communication in the presence of a firewall or NAT.

[0084] 12a shows an embodiment in which the first sequence 42a includes first blocks 41a, 41b (shown shaded) that are not paired with second blocks 41g-41j, however the initialization of the first blocks 41a and 41b follows the same method as for example blocks 41c-41e described with reference to FIG.

[0085] Initialization of the sequence 42 on a particular computer 11 may occur in response to a start-up command. In one embodiment, the start-up command constitutes an explicit user action, for example, executing a command via a command line or a graphical user interface (GUI) to execute the control software based on particular configuration data that may be provided by user action (e.g., command line parameters) and / or provided in a predefined file.

[0086] In another embodiment, a library accessible to an application running on an operating system may be configured to provide automatic data communication via the methods described herein. That is, the library is the control software. Alternatively, the library may invoke the control software. The application may be configurable to utilize the library when establishing a network connection with another computer 11 (e.g., computer 11b when the library and application are running on computer 11a). The library is configured to initialize based on configuration data. At least a portion of the configuration data may be provided by the application invoking the library.

[0087] In another embodiment, a loopback address on computer 11 is provided such that a connection to the loopback address will initiate control software based on configuration data also associated with the loopback address. Loopback addresses are well known in the art. In one example, for IPv4, loopback addresses may be in the range 127.0.0.0 to 127.255.255.255, although it may be preferable to limit them to a subset of this range, for example 127.1.0.0 to 127.1.255.255.

[0088] Note that these examples do not refer to wake-up actions on the other (or each other) computer 11. In general, these computers 11 can be configured with their own wake-up actions to execute control software to initialize an associated sequence 42 (or sequences 42). However, this wake-up action may be combined with a communication received from another computer 11. For example, computer 11a may communicate with computer 11b, which causes computer 11b to initialize a sequence 42.

[0089] In one embodiment, computer 11 may be configured with a TCP listener (i.e., a TCP server) configured to listen on a particular port. Upon receiving a communication addressed to this port, computer 11 is configured to initiate the initialization of sequence 42 associated with that port. The association may be based on certain predefined configuration data.

[0090] The embodiments described herein may provide customizable networking, where data connections between specific computers 11 (or other networked devices, e.g., printers) are controlled via software implemented on the computers 11. That is, features such as security (e.g., authentication and encryption) may be controlled at the application layer level, as opposed to the transport layer or Internet layer (see, e.g., RFC1122) per connection. Furthermore, data connections may be device-scoped as well as application-scoped. This is possible because connections between blocks 41 are configured in software, and the transport layer is only responsible for transport (as opposed to security, etc.). Such flexibility allows administrators to quickly and securely access different devices.

[0091] An example of an implementation of the embodiments described herein is shown in Figures 13a and 13b.

[0092] In this example, a user 90 requests access to an application running on a computer 91a on a private network 92. FIG. 13a shows a prior art example in which a user 90 uses the user's computer 92a to connect to computer 91a through a VPN 94 associated with computer 91a. The prior art approach has several potential drawbacks. For example, the VPN 94 may be overly permissive in that it may grant access to the entire network, and even if security is adequate, it usually involves centralized processing with (potentially complex) routing rules. Complex "smart" routers may be required to handle packet destinations between the user's computer 92a and computer 91a. As a result, for example, user 90 may be able to access another computer 91b. Thus, the VPN 94 becomes a central point of failure. Another problem may be that the VPN 94 requires significant overhead to be implemented in the manner of packet inspection and routing. Finally, it may be difficult to isolate a particular application on computer 91a for interaction by user 90a.

[0093] FIG. 13b shows an implementation using the above embodiment. Here, a user 90a requests access to an application 95a, e.g., a VNC server, running on a computer 91a. The embodiments described herein may be utilized to provide a data connection between the technician's computer and the application 95a (indeed, the data connection may be specifically between application 96a and application 95a running on the technician's computer, as shown). This is one data connection. Next, the same user 90 in the same session may also request access to another application 95b, e.g., a file transfer server, running on the computer 91a. The embodiments described herein may be utilized to provide another data connection between the technician's computer and the application 95b (indeed, the data connection may be specifically between application 96b and application 95b running on the technician's computer 92a, as also shown). As shown in FIG. 13b, there are two data connections linking the technician's computer 92a to the computer 91a. This process can be continued to create a customized network connection between the user's computer 92a and the computer 91a.

[0094] Now consider the case where a second technician 90b requests access to an application 95c running on computer 90a. Using the embodiments described herein, a data connection is created between technician's computer 92b and application 95c (in fact, the data connection may specifically be between application 96c and application 95c running on technician's computer 92b, as shown). This is yet another connection. Second technician 90b may also request access to the first application 95a on computer 91a (through application 96a running on technician's computer 92b).

[0095] Now consider the case where a first technician 90a also requires a data connection to a second computer 91b, for example to access another instance of an application 91a (e.g., a VNC server). The embodiments described herein can be used to create this data connection.

[0096] The diagram in Fig. 13b is intended to show how the data connections described herein can be constructed to create a network of data connections targeted to a particular application 95, i.e., for example, a data connection between an application 95 and a corresponding application 96 running on different computers 91. Advantageously, these data connections are inherently secure according to the embodiments described herein. Each data connection must be authorized and is only accessible to a particular application 95, 96. These data connections are software defined. This approach can be considered a "bottom-up" approach to networking, focusing on individual software-defined data connections.

[0097] The actual transmission of data utilizes the transport layer (according to the OSI stack) and below, but security and authorization do not need to be handled in hardware. In fact, the transport layer only needs to transmit data packets. An advantage of the embodiments described herein may be that, in certain implementations, it results in reduced network hardware complexity.

[0098] Thus, the connections described herein can be thought of as the interaction of one or more (usually multiple) data connections, i.e., direct connections between specific computers 11 that ensure that specific computers 11 and, optionally, applications on those computers 11 are accessible by another party. As defined in software through the use of segments 42 and blocks 41 (and correspondingly the protocols associated with blocks 41), secure connections can be authorized and created as needed, and the transport layer only needs to communicate data between specific blocks 41.

[0099] In one example, the embodiments described herein enable distributed data monitoring. In a prior art system such as that shown in FIG. 13a, the VPN 94 may be configured to record the data flow between the computers 91a, 91b, and 92a. However, this constitutes a third party for at least one entity, thereby raising trust issues. According to the embodiments described herein, the sequence 42 may be configured with a logging block 41, i.e. a block 41 associated with computer software configured to record the data being communicated. Thus, such a logging block 41 may be configured according to the requirements of the organization associated with the sequence 42 for each data communication. Typically, such a block 41 is placed between the application 95, 96 and any encryption block 41 of the sequence 42. Thus, both organizations associated with the data communication may facilitate data recording according to their own policies without relying on a third party.

[0100] Further modifications may be made without departing from the spirit and scope of the present specification. For example, the configuration of individual blocks 41 may be limited by the system operator to a subset of possible configurations.

Claims

1. A method for data communication over a network, comprising: configuring, on a first computer, a first sequence including an ordered plurality of first blocks associated with at least one segment, each first block representing a configurable data communication function; allocating one or more of the first blocks to a first segment and allocating one or more other of the first blocks to a second segment; initializing the first block of the first segment and initializing the first block of the second segment; thereafter, causing data communication between a first block of the first segment and a first block of the second segment; performing data communication between the first computer and a second computer using one or more of the initialized first blocks; Including, 10. A method of data communication, wherein at least one segment is associated with data communication with an application running on the first computer.

2. The method of claim 1 , wherein at least one segment is associated with data communication with the second computer or another computer over a data network.

3. constructing, on a second computer, a second sequence including an ordered plurality of second blocks associated with at least one segment, wherein each of one or more of the second blocks is uniquely associated with a first block; initializing the second block to perform data communication between the first computer and the second computer; Further comprising: A method according to any preceding claim, wherein each second block represents a configurable data communication function.

4. 4. The method of claim 3, wherein at least one first block is an originating first block configured to interact with an application running on the first computer, and / or at least one second block is an originating second block configured to interact with an application running on the second computer.

5. 5. The method of claim 3 or 4, wherein initializing the first block of a segment and / or the second block of a segment comprises traversing them separately one by one in a first direction and then in an opposite second direction, and traversing comprises activating the communication functions associated with the first block and the second block according to an activation rule.

6. 6. The method of claim 5, wherein each first block and each second block is configurable as a top-down block type or a bottom-up block type, and the activation rules are such that when traversing in the first direction, only the communication functions associated with the first block and the second block of the top-down block type are activated, and when traversing in the second direction, only the communication functions associated with the first block and the second block of the bottom-up block type are activated.

7. 5. The method of claim 3 or 4, wherein initializing the first block and / or the second block includes traversing each one separately in only a first direction, and traversing includes activating the communication functions associated with the first block and the second block according to an activation rule.

8. 8. The method according to claim 3, wherein at least one first block and / or at least one second block are configured as an encapsulation block type such that the communication functions associated with the first block and the second block perform the data communication after initialization.

9. The method of claim 8 , wherein the at least one first block and the at least one second block are configured as a network protocol for communicating with an IP network.

10. 10. The method according to claim 3, wherein at least one first block and / or at least one second block are configured as a non-encapsulated block type such that the communication functions associated with the first block and the second block are not involved in the data communication after initialization.

11. The method according to any one of claims 3 to 10, further comprising one or more first blocks and / or one or more second blocks associated with a communication function configured to communicate with at least one relay server.

12. 12. The method of claim 11, wherein the first block of the first sequence and the second block of the second sequence communicate with the network via the first block and the second block configured to communicate with the at least one relay server.

13. The method according to any one of claims 3 to 12, further comprising one or more first blocks and / or one or more second blocks associated with a communication function configured to communicate with a connection server.

14. 14. The method of claim 13, wherein at least one first block and at least one second block associated with a communication function configured to communicate with the connection server are used only for initializing the data communication.

15. A method according to any one of claims 3 to 14, wherein the initialization of the first sequence is in response to receiving a wake-up command and / or the initialization of the second sequence is in response to receiving a wake-up command.

16. 16. The method according to claim 3, wherein the data communication is between a first application running on the first computer and a second application running on the second computer.

17. 20. A method for generating data communications between a plurality of applications, the method comprising: performing the method of claim 16 for each of one or more applications running on a first computer and one or more applications running on a second computer.

18. 1. A system including a first computer, The first computer, generating a first sequence including an ordered plurality of first blocks associated with at least one segment, each first block representing a configurable data communication function; allocating one or more of the first blocks to a first segment and allocating one or more other of the first blocks to a second segment; initializing the first block of the first segment based on the first sequence and initializing the first block of the second segment; thereafter, effecting data communication between a first block of the first segment and a first block of the second segment; using the one or more initialized first blocks to perform data communication with a second computer; A system, wherein at least one segment is associated with data communication with an application executing on the first computer.

19. A computer comprising a computer program arranged to cause the computer to carry out the method according to any one of claims 1 to 17.

Citation Information

Patent Citations

  • Software-defined network overlay

    JP2016504837A

  • Data communication system and method

    JP2016527579A

  • Hierarchical block-identified data communication for unified handling of structured data and data compression

    US20090164754A1

  • User-Space Enabled Virtual Private Network

    US20130332724A1

  • Method of communicating data packets within data communication systems

    US20180007108A1