Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/70—Admission control; Resource allocation
  • H04L47/80—Actions related to the user profile or the type of traffic
  • H04L47/805—QOS or priority aware
• • 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/46—Interconnection of networks
  • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
  • H04L12/4608—LAN interconnection over ATM networks
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/70—Admission control; Resource allocation
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/54—Store-and-forward switching systems 
  • H04L12/56—Packet switching systems
  • H04L12/5601—Transfer mode dependent, e.g. ATM
  • H04L2012/5638—Services, e.g. multimedia, GOS, QOS
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/54—Store-and-forward switching systems 
  • H04L12/56—Packet switching systems
  • H04L12/5601—Transfer mode dependent, e.g. ATM
  • H04L2012/5638—Services, e.g. multimedia, GOS, QOS
  • H04L2012/5665—Interaction of ATM with other protocols
  • H04L2012/5667—IP over ATM

Definitions

• the present invention relates to an arrangement in a data transmission system, especially an internet system, in which system data is transmitted between terminals and servers with a certain level of QoS (Quality of Service) on IP (Internet Protocol) .
• QoS Quality of Service
• IP Internet Protocol
• the inventions relates to QoS settings on IP using web technology.
• ATM provides powerful mechanisms for QoS selection on specified connections (or flows), but as long as IP, or the commonly used upper layer protocols don't provide such mechanism, the applications are not given the abil- ity to select QoS.
• RSVP Resource Reservation Protocol
• ATM has incorporated the QoS conception
• QoS mapping for RSVP versus ATM The main drawback with this solution is that the RSVP protocol not yet is widespread. Probably it will take some time before it becomes widespread partly due to that it has to be implemented both at the client, server and router side.
• the RSVP standards are not yet stable either.
• Arequipa provides QoS on IP over ATM by using a Web browser. For information on this particular solution, see reference 1.
• European patent EP 0 732 835 A2 proposes a way to utilize internet for signalling and PSTN, or network with PSTN functionality, for real connections. Also security and charging mechanisms are included. The client establishes a so called communication number when signalling. This communication number is later utilized for setting up the real connection over PSTN or a similar network.
• a drawback by this solution is that dedicated client code has to be installed on every client. Besides, and most important, QoS on IP or internet and hereby possibilities for internet applications to utilize QoS, is not touched.
• the main object of the present invention is to provide an arrangement in a data communication system wherein QoS on
• IP can be changed, respectively improved according to appropriate user settings .
• Another object of the present invention is to provide an arrangement wherein the quality of e.g. real time applications can be changed to an appropriate level .
• Still another object of the present invention is to provide an arrangement wherein such change of quality can be implemented by using for example web technology.
• Fig. 1 is a schematic sketch illustrating an embodiment of the present invention as well as the key concepts thereof .
• Fig. 2 is a schematic sketch illustrating in further details an example of an embodiment of the present invention, especially for implementing QoS on IP over ATM.
• the key concepts of the invention is first of all the usage of 2 set of servers means, for example web server means, as well as the possibility of transferring data between terminals, for example browsers, and servers, as well as between servers.
• such implementation can involve :
• One Web server is running on IP/MAC. It is dedicated for the selection of new Web pages providing services with a corresponding QoS, hence this may be considered to be the signalling part.
• the other Web server (-s) run IP over whatever, e.g. ATM, and provide the requested services and corre- sponding QoS to the user.
• Which protocols IP may run on is dependent on what kind of network that is available. Even the PSTN may be the base network. If a phone, modem and TAPI are available, IP and HTTP may be running on top of TAPI. Naturally, the under- lying network may introduce limitations with respect to available QoS parameters.
• FIG. 1 there are illustrated the key concepts of the invention by means of order:
• a Web server I connected to the internet, a Web server II connected to the network providing QoS and some dedicated server code has to be installed on the server (-computer ( -s) ) .
• the client has to install a Web browser III.
• a client may perform the signalling part by utilizing the internet, the Web browser III and the internet Web server I.
• the connection establish- ment is performed by utilizing the network providing QoS, the Web browser III and the QoS dedicated Web server II.
• the client has established a connection providing QoS between the Web browser III and the QoS dedicated Web server II.
• FIG. 2 An example which illustrates the invention Figure 2 gives an illustration of a possible concrete implementation of QoS on IP by using Web technology.
• IP is running over ATM in a Classical IP, see reference 4, environment.
• Figure 2 illustrates an embodiment for implementing QoS on IP over ATM by using Classical IP over ATM and 2 Web servers I and II, respectively. Note that also the ordinary DNS and IP/MAC ARP server resides on the server (-computer) .
• Stepwise guide to Figure 2 a) The server (-computer) registrates and provides its ATM and IP address to the ATM ARP server b) The client registrates and provides its ATM and IP address to the ATM ARP server c) The client downloads the MAC Web server page. The ordinary MAC/IP ARP is used. d) The client selects the QoS parameters it wants for the coming ATM connection. If the client is going to select Servicel, the client has to utilize QoSl . The QoS data may be transferred to the MAC Web server e.g. by CGI scripts or Java applets/RMI, hence some server (-computer) code must be executing.
• the MAC Web server must in turn transfer the QoS parameters and the client's IP address to the ATM Web server Servicel resides at.
• Java/RMI or Java/CORBA may be applied to transfer these data from the MAC Web server to the ATM Web server.
• remote distribution mechanisms are superfluous, only a simple e.g. Java program is needed.
• f) Immediately after the ATM Web server has received all the data, it initiates the setup of an ATM connection with the specified QoS parameters towards the client. Either an ATM card API or a script utilizing the command shell may be used to initiate the ATM connection.
• the ATM Web server requests the ATM ARP server of the client's ATM address, receives the client's ATM address, performs the signalling with the specified QoS parameters and sets up the ATM connection towards the client .
• the client requests the ATM Web server page by clicking on Servicel which is the ATM Web server's URL.
• the DNS server will in turn return the ATM Web server's IP address.
• the server (-computer) program must be made in a way that ensures that the ATM connection exists before the downloading of the new Servicel ATM Web page starts.
• the client requests the ATM ARP server of the ATM Web server's ATM address and receives data about the already existing ATM connection. As stated in chapter "Precondition", the first attempt to retrieve the ATM server address was done by asking the ordinary IP/MAC ARP server.
• the client receives the requested Web page on the already existing ATM connection.
• the ATM Web page may be downloaded in the already opened Ethernet browser or as depicted in the figure, be downloaded in a new ATM browser.
• the server (-computer) program tears down the ATM connection.
• Web servers and the ATMARP servers resides on the same server (-computer), the same approach could be applied on a full scale Classical IP including routers, dedicated ARP servers, DNS servers and Web servers residing at completely different servers (-computers) .
• the HTTP protocol is not well suited to run video application and similar real time applications which ATM is good at.
• the co ing RTSP which is an alternative to HTTP, is better suited.
• the different IP addresses are used to differentiate between the different underlying networks. This technique is used under i) above. E.g. FORE, see reference 3, has implemented such an approach when it comes to IP over MAC and IP over ATM.
• LANE Local Area Network Emulation
• NHRP Next Hop Resolution Protocol
• IP Internet Protocol
• TCP Transport Control Protocol
• UDP User Datagram Protocol
• ATM Asynchronous Transport Mode
• RSVP Resource Reservation Protocol
• MAC Media Access Control
• PSTN Public Switched Telephone Network
• TAPI Telephone Application Programming Interface
• HTTP Hypertext Transport Protocol
• RTSP Real Time Streaming Protocol
• RTP Real Time Protocol
• DNS Domain Name Server
• IP/MAC ARP server translates an IP address to a MAC address .
• ATM ARP server translates and ATM address to an IP address .
• CGI Common Gateway Interface

Landscapes

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

Applications Claiming Priority (3)

Publications (1)

Family

ID=19901055

Family Applications (1)

Country Status (4)

Families Citing this family (2)

Family Cites Families (3)

• 1997
  • 1997-08-29 NO NO19973977A patent/NO312738B1/no unknown
• 1998
  • 1998-08-04 WO PCT/NO1998/000231 patent/WO1999012321A1/en not_active Application Discontinuation
  • 1998-08-04 EP EP98937881A patent/EP1008255A1/en not_active Withdrawn
  • 1998-08-04 AU AU86524/98A patent/AU8652498A/en not_active Abandoned

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events