WO2003081460A1 - Procede et systeme d'utilisation d'adresses de longueur fixe dans l'acheminement de messages - Google Patents

Procede et systeme d'utilisation d'adresses de longueur fixe dans l'acheminement de messages Download PDF

Info

Publication number
WO2003081460A1
WO2003081460A1 PCT/FI2002/000256 FI0200256W WO03081460A1 WO 2003081460 A1 WO2003081460 A1 WO 2003081460A1 FI 0200256 W FI0200256 W FI 0200256W WO 03081460 A1 WO03081460 A1 WO 03081460A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
fixed
access point
length
packet
Prior art date
Application number
PCT/FI2002/000256
Other languages
English (en)
Inventor
Juha Kumpulainen
Original Assignee
Wiral Ltd.
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 Wiral Ltd. filed Critical Wiral Ltd.
Priority to AU2002242769A priority Critical patent/AU2002242769A1/en
Priority to PCT/FI2002/000256 priority patent/WO2003081460A1/fr
Publication of WO2003081460A1 publication Critical patent/WO2003081460A1/fr

Links

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
    • H04L45/745—Address table lookup; Address filtering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • 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/24—Multipath
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/04—Protocols for data compression, e.g. ROHC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers

Definitions

  • the present invention generally relates to a service access point system composed of at least two servers, which are connected to each other by an intranet, and which routes messages sent by client applications.
  • a set of access points is connected to an access network that may be a fixed network or a wireless network.
  • the access network is preferably a packet-switched network, though it could also be a circuit- switched network.
  • the Internet is a packet-switched network whose nodes have an Internet peripheral address (IP address).
  • IP address consists of four numbers between 1 and 255, and dots separating each number; for example, 193.199.35.5. The first number refers to the topmost network level and the second number refers to the next level, etc.
  • the routers of the Internet locate the correct receiver by its IP address. Since the Internet is a packet-switched network, no circuit is allocated for the connection. Instead, data is transmitted in packets from the sender to the receiver.
  • Maximum transfer unit defines how many bytes an IP packet can at most contain.
  • the said MTU is usually at least 1500 bytes in Internet protocol version 4 (IP4v) and in Internet protocol version 6 (IP6v).
  • IP4v Internet protocol version 4
  • IP6v Internet protocol version 6
  • the minimum of the MTU is 576 bytes in IPv4 packets
  • the minimum of the MTU is 1280 bytes in IPv6 packets.
  • the said specifications guarantee that the size of an IP packet is at least 576 bytes in IPv4 transmissions and 1280 bytes in IPv6 transmissions.
  • the small size of a packet ensures that transmission capacity is divided between end-users of a network.
  • Each IP packet includes a header with the following information: a sender IP address, a receiver IP address, a sender port (application), and a receiver port (application), among other things.
  • Transmission control protocol/Internet protocol (TCP/IP) is a set of protocols that determine how IP packets are transmitted in the Internet. When using TCP/IP the bytes (octets) have a sequence number.
  • a receiver node detects if one or more bytes are missing. Then it sends a retransmission request for the missing bytes. In another protocol a receiver may send an acknowledgement as response to receiving bytes.
  • User datagram protocol (UDP) is in some cases alternative to TCP/IP. UDP offers a transmission with a minimum of protocol handling. Therefore retransmission requests or packet acknowledgements are not used in UDP. For the same reason a sender cannot know whether a receiver has received the packets sent.
  • the world wide web is an Internet-based, distrib- uted hypermedia information system.
  • the web pages are traditionally represented using hypertext markup language (HTML).
  • HTML and its successor, extensible markup language (XML), are intended for forming structured documents to be interchanged in the web. Structured documents are searched and read through software that is termed a browser.
  • Hypertext transfer protocol (HTTP) determines how structured documents are transferred in the Internet.
  • WML Wireless markup language
  • WAP wireless application protocol
  • short messages are another method to transmit data from a client to an access point.
  • GSM limits the length of short messages to 160 characters.
  • Multimedia messaging service (MMS) is able to deliver larger messages in a reasonable time compared to short message service (SMS). The fixed limit will be replaced by an ability to transfer much larger text contents, graphics, and audio/video clips.
  • the access network may be a fixed network or a wireless network, such as a GSM, GPRS, or UMTS.
  • the access network may be a wireless local area network (WLAN).
  • Clients send data via the access network to a set of access points. Data may be located, for example, in a TCP/IP packet, an UDP packet, or in a short message.
  • the data When a client is logged into a service and sends data to an access point, the data contains at least one reference address.
  • the said reference address identifies a sender, a receiver, or a service.
  • the reference address may be a fully qualified domain name (FQDN), or it may be an MSISDN number, i.e. a mobile subscriber integrated service digital network number.
  • data sent by a client may include one or more reference addresses which are, for example, MSISDN numbers or fully qualified domain names.
  • An e-mail address such as Alfa@wiral.com, is one example of an FQDN, but there are also other types of domain names.
  • the Internet consists of thousands of domains. Each domain has a domain name which is mapped to a certain IP-address. Several domain names may be mapped to the same IP-address. For example, domain names www.jypoly.fi and jkolamk.jkol.jypoly.fi are mapped to IP-address 193.199.35.1. Conversely, fully qualified domain names are unique, such as e-mail user names.
  • Domain names compose a hierarchical domain name system (DNS).
  • DNS domain name system
  • the root of a DNS tree is nameless.
  • Top-level domains are under the root: the original three-letter domains are .com, .net, .org, .edu, .int, .mil and .gov, plus two-letter top-level domains for each country. Under the top-level domains there are lower domains connected to the Internet.
  • the Internet includes domain name servers mapping domain names to IP addresses.
  • Uniform resource locator is a system uniquely identifying each resource in the Internet, i.e. where each document or file is located.
  • a URL address consists of a domain name and a search path.
  • the URL address "www.jypoly.fi/internet/jamk.nsf” consists of domain name "www.jypoly.fi” and search path "/internet/jamk.nsf .
  • a URL request consists of a protocol part and a URL address.
  • the protocol part is "http://"
  • the URL address is the before-mentioned "www.jypoly.fi/internet/jamk.nsf: http://www.jypoly.fi/internet/jamk.nsf
  • FIG. 1 shows a client-server system composed of one access point, wherein client Alfa 11 and client Beta 12 are logged in a service. Client Alfa and Beta applications have their own reference addresses related to the service. During the use of the service client Alfa sends data via an access network 13 to client Beta's reference address. An access point 14 receives the packets and transmits them to client Beta.
  • client Alfa is located in a mobile phone and client Beta is located in a laptop.
  • a client could be located in, for example, a personal digital assistant (PDA), a personal computer, or a network server.
  • PDA personal digital assistant
  • Jabber IM server described in http://www.jabber.org can be used as an access point for instant messaging (IM) services.
  • IM instant messaging
  • the access points can be connected to each other by means of an intranet.
  • IP4v and IP6v specifications guarantee that the size of IP packet is at least 576 bytes in IPv4 transmissions and 1280 bytes in IPv6 transmissions. These minimums of the MTUs should be taken into account in the intranet transmissions.
  • a reference address which includes an URL, may be very long. If an IP packet includes a 500 bytes long reference address the payload of the IP-packet may be less than 76 bytes in IP4v and less than 780 bytes in IP6v. If two reference addresses are included in an IP packet, the payload is even smaller.
  • various- length reference addresses make the handling of any type of packets inefficient, including the application level routing of the packets.
  • the invention relates to a system comprising at least two servers that are connected/coupled to each other by an intranet. These two servers may be both access points, or one of them may an access point and the other one a gateway.
  • An intranet may be e.g. 100 Mbps Ethernet.
  • the objective of the invention is to increase the communication capacity between a set of servers being coupled, directly or indirectly to an intranet, wherein at least one of the said servers is an access point.
  • This objective is achieved by increasing the payload of packets to be transmitted in the intranet.
  • the packets are preferably IP-packets whose size are maximum transfer unit (MTU).
  • MTU maximum transfer unit
  • Data sent by a client may be located in bigger packets/messages in an access network.
  • the packets/messages are fragmented into IP-packets of the size of the MTU to transmit the IP- packets efficiently in an intranet, especially when the intranet is an Ethernet network.
  • the maximum packet size of Ethernet is 1512 bytes.
  • Data sent by a client contains at least one reference address.
  • the reference address could be e.g. the receiver's e-mail address, such as beta@wiral.com.
  • the reference address is inputted as a parameter to a hash function that generates a 16 bytes long fixed-length address.
  • the fixed-length address replaces the reference address in the data part of the IP-packet that is transmitted in the intranet.
  • the payload of an IP-packet can be remarkably increased by replacing a reference address with a relative short fixed-length address.
  • a fixed-length address is more efficient to handle in a receiving access point than a various-length reference address.
  • the hash function named Digest generates statistically unique enough, 16 bytes long, fixed-length addresses from 1-500 bytes long reference addresses.
  • an access point When a client logs into a system, an access point generates a fixed-length address for the client and stores the fixed-length address gener- ated in a memory.
  • the access point When the client sends data to another client, the access point generates a fixed-length address using a reference address of the data as a parameter. Then the access point locates the fixed-length address and a payload in an IP-packet, and sends the IP-packet to an intranet.
  • Another access point, or a gateway belonging to the system receives the IP-packet, obtains the fixed-length address from it, and searches for the address from the memory. If the address is found, the data is transmitted to the certain client to which the fixed-length address was related when the certain client logged into the system.
  • Another objective of the invention is to implement a system which can be termed an application level message router and which is composed of commodity off the self (COTS) hardware.
  • the application level message router can be utilized, for example, in instant messaging (IM) services, wherein messages are routed inside the system and/or between systems.
  • IM instant messaging
  • Figure 1 shows an access point communicating with clients
  • Figure 2 shows a system composed of two access points
  • Figure 3 shows a system composed of an access point and a gateway
  • Figure 4 depicts a hash function generating a reference address to a fixed- length address
  • Figure 5A shows a packet to be transmitted in an intranet
  • Figure 5B shows a packet to be transmitted in an Ethernet network
  • Figure 6 shows a system containing three access points, a load balancer, and a gateway
  • An inventive access point system comprises at least two access points connected/coupled to each other by an intranet.
  • the access point system comprises at least one access point and a gateway connected/coupled to each other by an intranet.
  • FIG. 2 shows an access point system composed of two access points connected to each other by means of an intranet.
  • Client Alfa 21 and client Beta 22 are logged into a service that is provided by the domain of Wiral Ltd.
  • Client Alfa has an e-mail address alfa@wiral.com
  • client Beta has an e-mail address beta@wiral.com.
  • client Alfa sends data including a reference address via an access network 23 to client Beta's e-mail address.
  • client Alfa is logged into a first access point 24 and client Beta is logged into a second access point 25.
  • the first access point receives data sent by client Alfa, wherein the data includes a reference address and a payload.
  • the first access point generates a fixed-length address by applying a hash function to the reference address, locates the fixed-length address, i.e. the result of the hash function, and the payload in a packet, and sends the packet in the intranet 26.
  • the second access point receives the packet sent by the first access point and obtains the fixed-length address and the payload from the packet.
  • the second access point searches the fixed-length address from the memory, and if found, transmits the payload via the access network to the second client.
  • the packet with fixed-length address is transmitted from the first access point to the second access point.
  • client Beta connected to the second access point the following operations were performed. 1) The second access point received the same reference address from client Beta as client Alfa located in its data. In this case, the reference address is client Beta's e-mail address. 2) After that, the second access point generated a fixed-length address by applying a hash function to the reference address and located the fixed-length address and data related to the connection in a memory.
  • the second access point searches for a fixed-length address included in the packet from the memory.
  • the second access point sends the content of the packet to client Beta's IP address. Otherwise, the packet is discarded.
  • fixed-length addresses are located in a memory in data structure intended for search operations. Search means are discussed in patent application PCTxxxxxxxxxx.
  • clients Alfa and Beta are connected to the same access point. Then the said access point can send client Alfa's data directly to client Beta without using the intranet.
  • FIG. 3 shows an access point system composed of one access point and a gateway connected to each other by means of an intranet.
  • Client Alfa 31 and client Beta 32 are logged into a service that is provided by at least two different domains.
  • Client Alfa has an e-mail address alfa@wiral.com and client Beta has an e-mail address beta@notwiral.com.
  • Client Alfa sends data including via an access network 33 to client Beta's e-mail address.
  • Client Beta's email address is a reference address.
  • the access point 34 receives the message data packet including the reference address and the payload sent by client Alfa.
  • the access point generates a fixed- length address by inputting the reference address to a hash function, locates the fixed-length address and the payload in a packet, and sends the packet in the intranet 36.
  • the gateway 35 receives the packet sent by the access point and obtains the fixed-length address and the payload from the packet.
  • the gateway searches the fixed-length address from the memory, and if not found, transmits the payload sent by the client to another access point 37.
  • the other access point on domain notwiral.com transmits the data to client Beta.
  • An objective of the inventive method is to increase the communication capacity between a set of servers coupled, directly or indirectly to an intranet.
  • At least one of said servers is an access point which is adapted to communicate with clients.
  • the access point may or may not be connected to an access network, such as the Internet.
  • the method comprises the steps of receiving load data including a possible long reference address from a client in an access point, and generating a relatively short fixed-length address by applying a hash function to the reference address.
  • the fixed-length address and the payload are then located in a packet; and the packet is sent to the set of servers using the intranet.
  • the method reduces data volume between the servers, and thus increases the communication capacity.
  • Another objective of the invention is to implement an application level message router that is composed of commodity off a self (COTS) hard- ware.
  • COTS commodity off a self
  • the prior art solutions, such as Jabber include a separate router server.
  • the systems shown in FIG. 2 and 3 can be considered as application level message routers.
  • a separate router server is useless, because access points and a gateway are able to a route messages.
  • a system of a message router includes at least two servers that are connected together with at least one private network.
  • FIG. 4 depicts a hash function and its input and output.
  • the hash function 42 obtains a relatively long reference address 41 of variable length as a parameter and outputs a relative short fixed-length address 43.
  • the reference address 41 may be 3-511 bytes long, when the fixed-length ad- dress 43 is preferably 16 bytes long.
  • the hash function 42 is preferably Digest hash function, or to be more specific, the MD5 message-Digest algo- rithm described in RFC1321 published by the Internet engineering task force (IETF).
  • FIG. 5A shows a packet to be transmitted in an intranet.
  • the packet 501 includes a header 502, a fixed-length address 503 and a payload 504.
  • Load data is 505 composed of the payload 504 and the fixed-length address 503.
  • the header is fixed-length and includes network- and protocol- specific information and a size of load data.
  • the intranet is preferably an Ethernet network and packets to be transmitted in the intranet are preferably IP packets.
  • the invention is not limited to Ethernet or Internet protocol.
  • FIG. 5B shows a packet to be transmitted in an Ethernet network.
  • an intranet is an Ethernet using Internet protocol.
  • the packet 505 includes an Ethernet header 506, an IP-header 507, a data part header 508, and a payload 509.
  • the data part header is composed of the following information: a version 510 defining the structure of the data part header, a fixed-length address 511 , a second fixed-length address 512, and data length 513 defining a size of a payload.
  • the fixed-length address is generated by inputting a user name and domain name to a hash function and the second fixed-length address is generated by inputting a domain name to a hash function.
  • the fixed-length address is preferably intended for the use of an access point
  • the second fixed-length address is preferably intended for the use of a gateway.
  • an access point receives a packet from an intranet, it compares the fixed-length address with fixed length addresses stored in its memory. If the fixed-length address matches with some of them, the access point handles the packet as described in FIG. 2 or 3.
  • the node of the intranet is a gateway
  • the node/gateway compares, not the first, but the second fixed-length address with a fixed-length address stored in its memory, wherein the said fixed-length address is the domain name of the access point system. If they don't match, the node/gateway transmits the packet to another access point system.
  • the fixed-length address is intended for routing the packet inside an access point system and the second fixed-length address that is intended for routing the packet from the access point system to another system.
  • the access point or the gateway searches for the fixed-length address from the memory.
  • a packet to be transmitted in an intranet may include one, two, or more fixed-length addresses. If the packet includes at least two fixed-length addresses, one of the addresses may cause a predefined operation in a receiving access point or a gateway.
  • the predefined operation may be, for example, the comparing of domain names as described above.
  • a fixed length address is generated from just one reference address identifying a sender, a receiver, a service, or content, such as a WWW page.
  • some predefined combination of references addresses is inputted as a parameter to a hash function, for example, a character string composed of a sender and a receiver.
  • the combination single reference addresses may result in a longer reference address from which it is easier to generate a unique fixed-length address than from a single reference address.
  • FIG. 6 shows a system that contains three access points, a load balancer, and a gateway.
  • Client Alfa 61 communicates with client Beta 62 bi- directly via the said system. Either of the said clients has started the commu- nication by sending data via an access network 63 to a load balancer 64.
  • the load balancer takes care that the three access points, 65, 66, and 67 are uniformly loaded.
  • the three access points and a gateway 68 are connected to an intranet 69.
  • the load balancer may operate, for example, as follows: It receives an IP-packet from a client and obtains a sender related reference address from the packet. Then the load balancer inputs the said reference address to a hash function that outputs a fixed-length address.
  • the load balancer modulates the fixed-length address by three resulting in one of the numbers 0, 1 , or 2.
  • the numbers 0, 1 , and 2 are related to the access points 65, 66, and 67 as shown in FIG. 6. If a sender application is located in a mobile device it is important that the load balancer uses a sender related reference address, because the sender's IP address may change during the communication. If the access network is a fixed network, the load balancer may use the sender's IP address in its modulo function. In FIG. 6 the network 69 could connect the access points and the gateway to the load balancer. Alternatively, another private network can be used for transmitting data from the load balancer to the access points. It is also possible that the load balancer and the access points communicate via the access network 63, or via another public network.
  • the system may also include a login and authentication server.
  • the said server authenticates users and permits logins to the system.
  • the access points may have a shared authentication database, whereby they can authenticate users and permit logins.
  • An access point system composed of COTS hardware is cost- effective and scalable.
  • a new server can be easily added to the access point system to upgrade the capacity of the system or for another reason.
  • the system When an access point system is intended for providing instant messaging services, the system includes at least an access network and an intranet.
  • the system preferably uses 1) Internet protocol and unicast delivery method in the access network and 2) Internet protocol and broadcast, multicast, or any cast delivery method in the intranet that is preferably a type of Ethernet.
  • Unicast delivery method is intended for one-to-one connections, the other delivery methods being intended for one-to-many connections.
  • Broadcast and multicast delivery methods are usable in IP4v; multicast and any cast delivery method are usable in IP6v.
  • an access point system is composed of at least two servers, so that one server is an access point and another server is either an access point or a gateway.
  • one or more access point may operate as a spare unit, so that the spare unit is put into use if an access point collapses, or access points are overloaded.
  • connections between clients may or may not be bi-directional. It is possible that only one client sends data and another client just receives data. It is also possible that a client sends data to many clients, for example, in short messages.
  • the devices in which client applications are located may or may not be mobile devices.
  • the devices may also be personal computers.
  • the method and system described above can be utilized as a plat- form of instant messaging services.
  • both of them can be utilized in message routing, wherein at least a start message should include at least one reference address.
  • the start message begins a connection between clients.
  • Messages to be routed may be of any message type that is possible to transmit in an access network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un système de point d'accès constitué d'au moins deux serveurs et d'un intranet. Lorsqu'un client envoie des données à un autre client, le point d'accès produit une adresse de longueur fixe par saisie de l'adresse de référence obtenue à partir des données en tant que paramètre d'une fonction de hachage. L'adresse de référence peut être, par exemple, une adresse de courrier électronique d'un client destinataire. Le point d'accès positionne alors l'adresse de longueur fixe et une charge utile dans un paquet, et envoie le paquet sur l'intranet. Un autre point d'accès/serveur reçoit le paquet, en extrait l'adresse de longueur fixe et recherche cette adresse dans la mémoire. Si l'adresse est trouvée, le paquet est émis au client auquel l'adresse a été affectée lorsque le client s'est branché sur le système.
PCT/FI2002/000256 2002-03-26 2002-03-26 Procede et systeme d'utilisation d'adresses de longueur fixe dans l'acheminement de messages WO2003081460A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
AU2002242769A AU2002242769A1 (en) 2002-03-26 2002-03-26 Method and system of using fixed-length addresses in message routing
PCT/FI2002/000256 WO2003081460A1 (fr) 2002-03-26 2002-03-26 Procede et systeme d'utilisation d'adresses de longueur fixe dans l'acheminement de messages

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/FI2002/000256 WO2003081460A1 (fr) 2002-03-26 2002-03-26 Procede et systeme d'utilisation d'adresses de longueur fixe dans l'acheminement de messages

Publications (1)

Publication Number Publication Date
WO2003081460A1 true WO2003081460A1 (fr) 2003-10-02

Family

ID=28052039

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/FI2002/000256 WO2003081460A1 (fr) 2002-03-26 2002-03-26 Procede et systeme d'utilisation d'adresses de longueur fixe dans l'acheminement de messages

Country Status (2)

Country Link
AU (1) AU2002242769A1 (fr)
WO (1) WO2003081460A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR3069400A1 (fr) * 2017-07-24 2019-01-25 Outscale Adressage pour reseau de telecommunications utilisant la multidiffusion
WO2019167056A1 (fr) * 2018-02-28 2019-09-06 Sling Media Pvt. Ltd. Procédés et systèmes de routage sécurisé de dns
US10708202B2 (en) 2003-09-19 2020-07-07 Blackberry Limited Handheld electronic device and associated method providing time data in a messaging environment
US10742696B2 (en) 2018-02-28 2020-08-11 Sling Media Pvt. Ltd. Relaying media content via a relay server system without decryption

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5414704A (en) * 1992-10-22 1995-05-09 Digital Equipment Corporation Address lookup in packet data communications link, using hashing and content-addressable memory
US5490258A (en) * 1991-07-29 1996-02-06 Fenner; Peter R. Associative memory for very large key spaces
US5692177A (en) * 1994-10-26 1997-11-25 Microsoft Corporation Method and system for data set storage by iteratively searching for perfect hashing functions
US5708659A (en) * 1993-10-20 1998-01-13 Lsi Logic Corporation Method for hashing in a packet network switching system
US5914938A (en) * 1996-11-19 1999-06-22 Bay Networks, Inc. MAC address table search unit
US5940478A (en) * 1996-05-31 1999-08-17 Octel Communications Corporation Method and system for extended addressing plans
WO2000021254A2 (fr) * 1998-10-06 2000-04-13 Telefonaktiebolaget Lm Ericsson (Publ) Procede et appareil de transmission de paquets de donnees depuis un reseau de commutation de paquets externe vers une station radio mobile

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5490258A (en) * 1991-07-29 1996-02-06 Fenner; Peter R. Associative memory for very large key spaces
US5414704A (en) * 1992-10-22 1995-05-09 Digital Equipment Corporation Address lookup in packet data communications link, using hashing and content-addressable memory
US5708659A (en) * 1993-10-20 1998-01-13 Lsi Logic Corporation Method for hashing in a packet network switching system
US5692177A (en) * 1994-10-26 1997-11-25 Microsoft Corporation Method and system for data set storage by iteratively searching for perfect hashing functions
US5940478A (en) * 1996-05-31 1999-08-17 Octel Communications Corporation Method and system for extended addressing plans
US5914938A (en) * 1996-11-19 1999-06-22 Bay Networks, Inc. MAC address table search unit
WO2000021254A2 (fr) * 1998-10-06 2000-04-13 Telefonaktiebolaget Lm Ericsson (Publ) Procede et appareil de transmission de paquets de donnees depuis un reseau de commutation de paquets externe vers une station radio mobile

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10708202B2 (en) 2003-09-19 2020-07-07 Blackberry Limited Handheld electronic device and associated method providing time data in a messaging environment
US10735353B2 (en) 2003-09-19 2020-08-04 Blackberry Limited Handheld electronic device and associated method providing time data in a messaging environment
US11888601B2 (en) 2003-09-19 2024-01-30 Blackberry Limited User interface for messaging communications on an electronic device
US11985099B2 (en) 2003-09-19 2024-05-14 Blackberry Limited Handheld electronic device and associated method providing time data in a messaging environment
FR3069400A1 (fr) * 2017-07-24 2019-01-25 Outscale Adressage pour reseau de telecommunications utilisant la multidiffusion
WO2019020582A1 (fr) * 2017-07-24 2019-01-31 Outscale Adressage pour réseau de télécommunications utilisant la multidiffusion
WO2019167056A1 (fr) * 2018-02-28 2019-09-06 Sling Media Pvt. Ltd. Procédés et systèmes de routage sécurisé de dns
US10742696B2 (en) 2018-02-28 2020-08-11 Sling Media Pvt. Ltd. Relaying media content via a relay server system without decryption
US10785192B2 (en) 2018-02-28 2020-09-22 Sling Media Pvt. Ltd. Methods and systems for secure DNS routing
US11297115B2 (en) 2018-02-28 2022-04-05 Sling Media Pvt. Ltd. Relaying media content via a relay server system without decryption
US11546305B2 (en) 2018-02-28 2023-01-03 Dish Network Technologies India Private Limited Methods and systems for secure DNS routing

Also Published As

Publication number Publication date
AU2002242769A1 (en) 2003-10-08

Similar Documents

Publication Publication Date Title
US10819826B2 (en) System and method for implementing application functionality within a network infrastructure
US7685288B2 (en) Ad-hoc service discovery protocol
US8150957B1 (en) Method and system for managing network traffic
EP1234246B1 (fr) Systeme et procede d'acces au reseau sans reconfiguration
Bonaventure Computer Networking: Principles, Protocols and Practice
US20030018774A1 (en) System and method for load balancing in ad hoc networks
US20030046404A1 (en) Processing network communication control messages
WO2003081460A1 (fr) Procede et systeme d'utilisation d'adresses de longueur fixe dans l'acheminement de messages
El Saddik Multimedia Communications Multimedia Technologies & Applications
Fall A message-switched architecture for challenged Internets
WO2003081461A1 (fr) Moyens de recherche contenant des adresses de longueur fixe produites par une fonction de hachage
Clarke et al. A primer on Internet technology
Elahi et al. Internet Protocols Part II and MPLS
Kumar et al. Computer Network-Application Layer Protocol
KR100428312B1 (ko) 라우팅 프로토콜을 지원하기 위한 패킷 운영방법
Nagel et al. Networking Concepts and Protocols
Shah Support For Host Anycast, Priorities And Naming of Link-Local Addresses in IPv6
Ginoza Request for Comments Summary RFC Numbers 3500-3599
Hardy et al. Application protocols
Rahman et al. CoRE Working Group A. Castellani Internet-Draft University of Padova Intended status: Informational S. Loreto Expires: October 29, 2012 Ericsson
Rahman et al. CoRE Working Group A. Castellani Internet-Draft University of Padova Intended status: Informational S. Loreto Expires: September 13, 2012 Ericsson
Batchelder et al. A Content-Based Load-Balancing Router System
WO2000068812A1 (fr) Procede de fonctionnement d'un service d'annuaire de courrier electronique
Terzis Introduction to Computer Networks
Churchill Applications Need Their Own Protocols

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP