AU1825801A - Method, means and protocol for synchronous data transmitting over the internet - Google Patents

Method, means and protocol for synchronous data transmitting over the internet Download PDF

Info

Publication number
AU1825801A
AU1825801A AU18258/01A AU1825801A AU1825801A AU 1825801 A AU1825801 A AU 1825801A AU 18258/01 A AU18258/01 A AU 18258/01A AU 1825801 A AU1825801 A AU 1825801A AU 1825801 A AU1825801 A AU 1825801A
Authority
AU
Australia
Prior art keywords
data
protocol
packet
processing tables
internet
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
AU18258/01A
Inventor
Ronald Brandt
Christofor Kirkitadse
Robin-Keith Spires
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ROBIN KEITH SPIRES
Original Assignee
ROBIN KEITH SPIRES
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 ROBIN KEITH SPIRES filed Critical ROBIN KEITH SPIRES
Publication of AU1825801A publication Critical patent/AU1825801A/en
Abandoned legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4505Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/62Establishing a time schedule for servicing the requests
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63Routing a service request depending on the request content or context
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Description

AUSTRALIA
PATENTS ACT 1990 COMPLETE SPECIFICATION NAME OF APPLICANT(S): Ronald Brandt AND Christofor Kirkitadse AND Robin-Keith Spires ADDRESS FOR SERVICE: DAVIES COLLISON CAVE Patent Attorneys 1 Little Collins Street, Melbourne, 3000.
INVENTION TITLE: Method, means and protocol for synchronous data transmitting over the internet The following statement is a full description of this invention, including the best method of performing it known to me/us:- 1 I la Prior art: Discussion of the current Technology The internet today has the single ability to act as an asynchronous data packet conduit, sending and receiving pre- and or post-processed data. The internet does not have the ability (through protocols) to act in a synchronous manner in the sending and receiving of data packets. No method exists to utilize the internet as a medium for distributed data basing or as a conduit to share synchronize distributed data bases, other than downloading a data base for postprocessing and then up-loading the resulting delta (post-processed) data base.
Technical Problem No method is in place to synchronize data transmitted over the internet. No method exists for coordinating various data packets sent over the internet into a set of data containing more than one internet protocol. There is currently no possibility of utilizing "Packetized" data sets as means of synchronizing internet data.
oooo It is an object of the invention to propose a possibility to transmit and receive data in a synchronous manner over the internet or an intranet.
For achieving this object the invention proposes a method with the ""features of the claim i, a means with the features of claim 6 and a protocol with the features of claim 7. The wording of the claims and the wording of the abstract is included by reference into the specification.
Solution for the Technical Problem Through a "synchronous scheduling transport protocol" (SSTP), "packetized" data sets can be processed in "real-time" at a speed relative to the actual speed of the internet data transmission (see figure la). The "packetized" data sets can be pre-defined to contain various classes of routing and data protocol elements thereby creating "processing tables". The tables are utilized as a data-stack with an index. Real-time is a relative measurement of internet response time, connection speed and size of the data packet.
The data-stack also contains the "physical" locations of "processing tables" within the DNS naming convention which are used by the "Synchronizer" (see figure Ib).
The "Synchronizer" contains "response" information that triggers an immediate "handshake" to the initiating resource using another element of the "synchronous scheduling transport protocol" called the "Initiator".
The "Initiator" has its own "processing tables" which contain the "response communication protocol" (RCP) for the initiating "packetized" data set (see figure c).
Utilizing the stored RCP, the "Initiator" sends an immediate response to the initiating TCP/IP address which in return sends a "handshake" 3 to proceed, thereby establishing a "synchronous internet conduit" (SIC) for data transport. (see figure 2) With SSTP it is possible to utilize "Packetized" data set to implement a synchronous protocol within the confines of the present Internet topology. Further, it is possible to synchronize between distributed processes, data bases or networks thereby creating virtual synchronous systems that have multiple physical locations but act as a single entity (see figure 3).
Advantages Synchronous packetized data transfers are possible via the SIC. The SIC also allows for virtual distributed data basing, "real-time" 1 scheduling verification and message forwarding.
Distributed Customer Data can be synchronized in "real-time")' with sales and service inquiries performed over the Internet or within a corporate network (Intranet). This allows the possibility of building .9 distributed Inter- or Intranet Customer Call Centers.
Synchronous Computing can also be attained though virtual distributed data processing centers.
Synchronized distributed WANs (Internet) and LANs (Intranets) can be correlated to create one virtual WAN or LAN. This allows the possibility of cheap corporate networks over the internet.
Variations S: Synchronized Inter- Intranet Scheduling Center.
Synchronized Inter- Intranet Customer Call Center.
Synchronized Inter- Intranet Messaging Center Synchronized "real-time"'" Shared Distributed Data Base.
Virtual (non-"hard" connected) closed networks Virtual filtered or blocked data bases Synchronized Search Engines Synchronized Advertising Engines Short description of the drawings: Fig. la shows the classes data-stack of the protocol proposed by the invention; Fig. Ib shows the name space data-stack as used by the invention; Fig. Ic shows the routing decision data-stack; Fig. 2 shows the establishing of an synchronous internet conduit as proposed by the invention; Fig.3 shows an example of an synchronous network comprising three participants; Fig. 4 shows a polling by client resource; Fig. 5 shows a sending by server resource.
Fig. la shows a data stack comprising 4 data packets. Packet la contains data for one resource, packet 2a contains members of a data table. Packet 3a contains pseudo data namely a table consisting only of references. Packet 4a contains resource data, namely data concerning a person or resource horned on a server.
Fig. lb shows a data stack creating a name space processing table.
These data contain the ,physical" locations of processing tables within the DNS naming convention which are used by the synchronizer.
The syncihcroni.zel- contains response information that triggers an immediate handshake to the initiating resource using another element of the synchronous scheduling transport Vmman.ipsr.Ir protocol proposed by the invention called the initiator. The packet lb contains the table location, the packet 2b contains the SYNC record location and the packet 3b contains the server location, namely multiple tables but only one server.
Fig. ic shows the initiator RCP routing decision data stack. The initiator has its own processing tables which contain the response communication protocol (RCP) for the initiating packetized data set.
Packet ic contains distribution routing information: table domain sync-server-name sync reply. Packet 2c contains additional DNS
S..
resolving (SYNC record): table domain sync-server-name. Packet 3c S"contains create routing table: lower priority for DNS originating entries (in relay mode). Packet 4c contains trigger information: oo••• query routing tables: queue trigger and polling request.
Utilizing the stored RCP, the initiator means sends an immediate o response to the initiating TCP/IP address. This address sends in return a handshake to proceed. By this a synchronous internet conduit for data transport is established. This is shown in detail in Figure 2. Here the various interdependencies of the elements of the method S. of the invention are shown.
go Fig. 3 shows an example of a synchronous network with 3 resources interconnected. Each resource has an initiator means, a synchronizer means and a database. With the method of the invention it is possible to utilize packetized data sets to implement a synchronous protocol within the confines of the present internet topology. Further it is possible to synchronize between distributed processes, data bases or networks thereby creating virtual synchronous systems that have multiple physical locations but act as a single entity.
Fig. 4 shows a polling by client resource (pull). The client side sync triggering of polling operations greatly reduces the reply duration by making a real-time server side sync data handshake available. The single steps can be seen in fig. 4.
Fig. 5 shows a sending operation by a server resource. The server side sending or push operations allow the client to acknowledge an ,,open connection request" and triggers a query for a SYNC data handshake from the sending server.
Throughout this specification and the claims which follow, unless the context requires otherwise, the word "comprise", •and variations such as "comprises" and "comprising", will be understood to imply the inclusion of a stated integer or step or group of integers or steps but not the exclusion of any other integer or step or group of integers or steps.
The reference to any prior art in this specification is not, and should not be taken as, an acknowledgement or any form of suggestion that prior art forms part of the common general knowledge in Australia.

Claims (19)

1. Method for transmitting and/or receiving data in a synchronous manner over the internet/intranet, in which a protocol is used that comprises an initiating means, for initiating and establishing a conduit, and a synchronizing means.
2. Method according to claim i, according to which the data are transmitted in a packetized manner.
3. Method according to claim 1 or 2, wherein the data packets contain classes processing tables.
4. Method according to one of the preceding claims, wherein the data packets contain name space processing tables.
Method according to one of the preceding claims, wherein the data packets comprise routing decision processing tables. oo S..
6. Means for transmitting and/or receiving data in a synchronous manner over the internet/intranet according to which data packets are ooooo transmitted comprising various classes of routing and data protocol elements in a predefined manner, which are used as a data-stack with oooeo an index.
7. Protocol for transmitting and/or receiving data packets in a synchronous manner over the internet/intranet according to which the data packets comprise various classes of routing and data protocol elements in a predefined manner, which are used as a data-stack with *:an index. 8
8. Protocol according to claim 7, wherein the data-stack comprises classes processing tables.
9. Protocol according to claim 7 or 8, wherein the data-stack contains the locations of processing tables which are used by synchronizing means.
Protocol according to one of the claims 7 9, wherein the processing tables are name space processing tables.
11. Protocol according to one of the claims 7 10, wherein the data-stack comprises routing decision processing tables.
12. Protocol according to one of the claims 7 11, wherein processing tables for an initiating means contain a response communication protocol for the initiating data set.
13. Protocol according to one of the claims 7 12, wherein the **classes processing tables contain at least one packet with data for S°"one resource, at least one member packet with member of a data table, S°one packet with pseudo data and one resource packet.
14. Protocol according to one of the claims 10 13, wherein the name space processing table contains one packet with the table o o location, one packet with the sync record location and one packet oe with the server location.
15. Protocol according to one of the claims 11 14, wherein the routing decision processing table contains one packet with distribution routing information, one packet with additional DNS o* resolving data, one routing table with data for creating routing table and one trigger packet.
16. A method for transmitting and/or receiving data substantially as hereinbefore described with reference to the drawings and/or Examples.
17. Means for transmitting and/or receiving data substantially as hereinbefore described with reference to the drawings and/or Examples.
18. Protocol for transmitting and/or receiving data substantially as hereinbefore described with reference to the drawings and/or Examples.
19.. The steps, features, compositions and compounds fe" disclosed herein or referred to or indicated in the specification and/or claims of this application, individually or collectively, and any and all combinations of any two or more of said steps or features. S S. o DATED this SECOND day of FEBRUARY 2001 Ronald Brandt AND Christofor Kirkitadse AND Robin-Keith Spires by DAVIES COLLISON CAVE Patent Attorneys for the applicant(s)
AU18258/01A 2000-02-04 2001-02-02 Method, means and protocol for synchronous data transmitting over the internet Abandoned AU1825801A (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP00102129A EP1122920A1 (en) 2000-02-04 2000-02-04 Method and means for transmitting data
EP00102129 2000-02-04

Publications (1)

Publication Number Publication Date
AU1825801A true AU1825801A (en) 2001-08-09

Family

ID=8167762

Family Applications (1)

Application Number Title Priority Date Filing Date
AU18258/01A Abandoned AU1825801A (en) 2000-02-04 2001-02-02 Method, means and protocol for synchronous data transmitting over the internet

Country Status (5)

Country Link
US (1) US20010015970A1 (en)
EP (1) EP1122920A1 (en)
JP (1) JP2001244991A (en)
AU (1) AU1825801A (en)
CA (1) CA2334290A1 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7864682B2 (en) * 2006-06-27 2011-01-04 Samsung Electronics Co., Ltd. Method for routing data in networks
US20080080419A1 (en) * 2006-09-29 2008-04-03 Cole Terry L Connection manager with fast connect

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6006241A (en) * 1997-03-14 1999-12-21 Microsoft Corporation Production of a video stream with synchronized annotations over a computer network

Also Published As

Publication number Publication date
EP1122920A1 (en) 2001-08-08
US20010015970A1 (en) 2001-08-23
CA2334290A1 (en) 2001-08-04
JP2001244991A (en) 2001-09-07

Similar Documents

Publication Publication Date Title
US7505473B2 (en) Transmission of broadcast packets in secure communication connections between computers
US6654792B1 (en) Method and architecture for logical aggregation of multiple servers
US7069325B1 (en) Method and apparatus for handling requests in a network
KR100720307B1 (en) Protocol for instant messaging
US20030126213A1 (en) Establishing direct instant messaging communication between wireless devices
EP0820170A3 (en) Systems and methods for providing increased server performance in a communications network
WO2003055165A3 (en) Simplified stateless tcp/ip protocol
WO2003038565A3 (en) Method and system for processing query messages over a network
EP0996260A3 (en) Wide area load distribution apparatus and method
JP2013046087A (en) Network gateway device
EP0991229A3 (en) Bundling multiple network management packets
CN103312807A (en) Data transmission method, data transmission device and data transmission system
EP0921655A3 (en) Multicast transmission method
JP3666654B2 (en) Internet communication method {MethodforanInternetCommunication}
EP1104141A3 (en) System for generating composite packets
CN101621532B (en) Method for realizing HTTP application by thread pool
CN101272380A (en) Method, system and device for network action management
US20040054781A1 (en) Method for establishing point to point or point to multiple points internet connection(s)
AU1825801A (en) Method, means and protocol for synchronous data transmitting over the internet
JPH03162154A (en) Communication gateway system and its communication method
CN106612307A (en) Always-on service implementation method and device
JP2007515875A (en) Internet endpoint system
Cohn A lightweight transfer protocol for the US Navy SAFENET local area network standard
KR20210034675A (en) A method for setting up a stream, a method for providing stream identification information, the use of a DNS server, a device, a computer program, and a computer readable medium
WO2004114602A1 (en) Method for identifying personal information on network

Legal Events

Date Code Title Description
MK1 Application lapsed section 142(2)(a) - no request for examination in relevant period