EP1502410A2 - Protocole de signalisation - Google Patents

Protocole de signalisation

Info

Publication number
EP1502410A2
EP1502410A2 EP03727408A EP03727408A EP1502410A2 EP 1502410 A2 EP1502410 A2 EP 1502410A2 EP 03727408 A EP03727408 A EP 03727408A EP 03727408 A EP03727408 A EP 03727408A EP 1502410 A2 EP1502410 A2 EP 1502410A2
Authority
EP
European Patent Office
Prior art keywords
signaling
client
server
data unit
protocol data
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.)
Ceased
Application number
EP03727408A
Other languages
German (de)
English (en)
Inventor
Uwe Schneider
Stefan Rinke
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.)
Combots Product GmbH and Co KG
Original Assignee
Web DE AG
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
Priority claimed from EP02009777A external-priority patent/EP1359702A1/fr
Priority claimed from EP02016141A external-priority patent/EP1383275A1/fr
Priority claimed from US10/201,446 external-priority patent/US20040019629A1/en
Priority claimed from EP20020020448 external-priority patent/EP1398933A1/fr
Priority claimed from US10/354,709 external-priority patent/US20040148392A1/en
Priority claimed from US10/395,951 external-priority patent/US20040205196A1/en
Application filed by Web DE AG filed Critical Web DE AG
Priority to EP03727408A priority Critical patent/EP1502410A2/fr
Publication of EP1502410A2 publication Critical patent/EP1502410A2/fr
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; Notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1023—Media gateways
    • H04L65/103—Media gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1033—Signalling gateways
    • H04L65/104—Signalling gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H04L65/1094—Inter-user-equipment sessions transfer or sharing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/401—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/403—Arrangements for multi-party communication, e.g. for conferences
    • H04L65/4038—Arrangements for multi-party communication, e.g. for conferences with floor control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • 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/08—Protocols for interworking; Protocol conversion
    • H04L69/085—Protocols for interworking; Protocol conversion specially adapted for interworking of IP-based networks with other networks
    • 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/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/38—Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections
    • H04M3/382—Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections using authorisation codes or passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
    • H04M3/493—Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
    • H04M3/493—Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
    • H04M3/4938—Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals comprising a voice browser which renders and interprets, e.g. VoiceXML
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/54—Arrangements for diverting calls for one subscriber to another predetermined subscriber
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/56—Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/0024—Services and arrangements where telephone services are combined with data services
    • H04M7/003—Click to dial services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/125—Details of gateway equipment
    • H04M7/1255—Details of gateway equipment where the switching fabric and the switching logic are decomposed such as in Media Gateway Control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
    • H04M2201/40—Electronic components, circuits, software, systems or apparatus used in telephone systems using speech recognition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2203/00—Aspects of automatic or semi-automatic exchanges
    • H04M2203/20—Aspects of automatic or semi-automatic exchanges related to features of supplementary services
    • H04M2203/2066—Call type detection of indication, e.g. voice or fax, mobile of fixed, PSTN or IP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2203/00—Aspects of automatic or semi-automatic exchanges
    • H04M2203/20—Aspects of automatic or semi-automatic exchanges related to features of supplementary services
    • H04M2203/2072—Schedules, e.g. personal calendars
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2203/00—Aspects of automatic or semi-automatic exchanges
    • H04M2203/60—Aspects of automatic or semi-automatic exchanges related to security aspects in telephonic communication systems
    • H04M2203/6054—Biometric subscriber identification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2242/00—Special services or facilities
    • H04M2242/22—Automatic class or number identification arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42025—Calling or Called party identification service
    • H04M3/42034—Calling party identification service
    • H04M3/42059—Making use of the calling party identifier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42348—Location-based services which utilize the location information of a target
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42382—Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
    • H04M3/493—Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
    • H04M3/4931—Directory assistance systems

Definitions

  • the present invention relates to signaling in a communications environment.
  • the present invention relates to a signaling protocol, or method for signaling, in a communications environment, wherein signaling provides information with respect to another communications environment.
  • the present invention relates to a communications environment, a method, a client, a server and software program products for implementing or carrying out the signaling protocol to which present invention relates to.
  • a communications environment may be a communications system comprising more than one component, i.e., more than one device and/or type of device, media and/or type of media, network and/or type of network.
  • a communications environment or communications system might for instance comprise a telephone, a Public Switched Telephone Network (PSTN) , a gateway to the Internet, etc .
  • PSTN Public Switched Telephone Network
  • communications environments for example computer based communications environments such as the Internet, communications environment comprising telephone networks, such as PSTN-based telephone communication environments, Global System for Mobile Communication (GSM) communications environments, Universal Mobile Telecommunications System (UMTS) communications environments and the like.
  • GSM Global System for Mobile Communication
  • UMTS Universal Mobile Telecommunications System
  • existing communications environments exhibit a plurality of communications capabilities, the communications environments are generally isolated from each other. Thus, communications performed in one communication environment are separated from communications performed in another communications environment.
  • no information is provided with respect to a second communications environment regarding communications performed in the second communications environment.
  • a general object of the present invention is to overcome the presently existing isolated coexistence of communications environments.
  • an object of the present invention is to provide access in one communications environment to information about a second communications environment, specifically information about communications performed in the second communications environment .
  • the present invention provides a method for signaling, or a signaling protocol, between a client and a server in a first communications environment.
  • the method includes providing information about a second communication environment to at least one of the client and the server.
  • the information may be provided in real-time by actively communicating the information from the client to the server and/or from the server to the client.
  • the server may be a telecommunications website and the client a specific entity associated with the telecommunications website. Properties and functions of a telecommunications web site are described in commonly-assigned U.S. patent application number 10/201446, entitled “Communications Environment,” filed July 23, 2002, and in commonly-assigned U.S. patent application entitled “Web Site Having an Event Identification Element” (attorney docket number 5007.1008), both of which are hereby incorporated by reference herein.
  • the information may be provided using a protocol data unit configured for the information.
  • the protocol data unit may include any of a first protocol data unit portion configured to indicate a version of a signaling protocol, a second protocol data unit portion configured to indicate a number of the protocol data unit, a third protocol data unit portion including a time stamp, a fourth protocol data unit portion including data useable by at least one of the client and the server, and a fifth protocol data unit portion including a signature.
  • the present invention also provides a communications environment comprising a client and a server, the client and/or the server being capable of providing information about a second communication environment to the other.
  • the present invention also provides a computer readable medium having stored thereon computer executable process steps operative to perform a method for signaling between a client and a server in a first communications environment.
  • the method includes providing information about a second communication environment to at least one of the client and the server.
  • information with respect to the second communications environment comprise data and/or information indicating operation modes of the second communications environment currently existing and/or desired/requested by the client and/or the server and communications performed in the second communications environment.
  • the signaling protocol defines a signaling that is to be actively communicated from the client to the server and/or vice versa.
  • the signaling according to the signaling protocol of the present invention is based on pushes from the client and/or the server (bi-directional pushing) such that polling of the client and/or the server is not necessary. This allows for a real-time signaling.
  • the signaling protocol according to the present invention is used for a signaling to be communicated between a specific entity as the client and a telecommunications website as the server associated to the client.
  • a telecommunications web site may be a web site adapted to provide, upon an access event, for private communications between two entities.
  • a telecommunications web site is assigned to or personalized for or corresponding to a specific person or entity.
  • Such a specific entity can be a person, a company or any other entity. Telecommunications web sites and specific entities are further discussed below.
  • the first communications environment comprises the specific entity and the telecommunication website which corresponds to the specific entity.
  • the first communications environment can comprise a computer-based communications environment system or network, such as the Internet.
  • the signaling protocol defines that any signaling communicated according thereto will be signed by a signature on the client CL and/or will be encrypted on the clients side.
  • the encryption is performed subsequent to signing a message.
  • the signaling protocol according to the present invention defines that, on the server
  • received signaling is decrypted and/or the signature is retrieved from signaling received by the server.
  • the server can compare the retrieved signature with a signature calculated on the server SV or obtained by other means .
  • the signaling protocol according to the present invention defines that each signaling comprises different protocol data units for providing the information with respect to the second communications environment.
  • the signaling protocol can further define that each of the protocol data units compromises a first protocol data unit portion indicating a version of the signaling protocol, second protocol data unit portion indicating the number of the respecting protocol data unit, a third protocol data unit portion including a time stamp, a fourth protocol data unit portion including data useable by at least one of the client and the server and a fifth protocol data unit portion including a signature.
  • the fifth protocol data unit portion can include a signature of the first, second, third and fourth protocol data unit portions as the signature.
  • the first, second, third, fourth and fifth protocol data unit portions can be symmetrically encrypted, in particular according to the RC 4 stream cipher.
  • the signature in the fifth protocol data unit portion can be retrieved/obtained on the server SV by means described in the RFC 2104 standard for cryptography, the so-called "request for command.” Also it is possible that the first, the second, the third and the fifth protocol data unit portion each has a predefined length.
  • the first protocol data unit portion can represent a number of the version of the signaling protocol currently used, for example for example protocol version one.
  • the second protocol data unit portion can indicate the number of its protocol data unit.
  • initialization protocol data unit is defined.
  • the initialization protocol data unit represents also a protocol data unit for a signaling but can • have a different structure with respect to its portions.
  • the initialization protocol data unit can comprise a first portion indicating the current version of the signaling protocol, a second unit indicating the number of this protocol data unit, a third portion indicating a time stamp generated on the client CL, a fourth portion indicating a major client version indicating major changes of the version (e.g., new functionalities) , a fifth portion indicating a minor client version indicating minor changes of the version (e.g., error/bug corrections, design modifications) , a sixth portion indicating a session cipher, for example according to RC 4, a seventh portion indicating a length of a session key in bytes, for example 16 bytes, an eighth portion indicating the session key generated on the client CL and a ninth portion indicating a signature generated on the client CL comprising 64 byte.
  • the packet is further encrypted by a public key method, such as, for example, an a public
  • the initialization protocol data unit is used by the client to contact the server to request that a signaling with respect to the second communications environment is desired. Therefore, the initialization protocol data unit is a signaling in initializing or initiating a signal according to the signaling protocol of the present invention. Therefore, this protocol data unit has the number 1.
  • different protocol data units and respective numbers are listed. The numbers associated to the protocol data units are just of exemplary character which also applies for the numbers contemplated for the in initializing protocol data unit.
  • the present invention contemplates a server-hello-signaling from the server to the client.
  • the present invention contemplates a protocol data unit 3 for a client-login-signaling from the client to the server, a protocol data unit 4 for login-response-signaling from the server to the client, a protocol data unit 5 for a keep-alive-request-signaling from the client to the server, a protocol data unit 6 for a keep-alive-response-signaling from the server to the client, a protocol data unit 7 for a logout- signaling from the client to the server, a protocol data unit 8 for a line-state-message-signaling from the server to the client, a protocol data unit 9 for a new-server-state- signaling from the server to the client, a protocol data unit 10 for a line-action-signaling from the client to the server, a protocol data unit 11 for a resynchronization-request- signaling from the client to the server, a protocol data unit 12 for a login-to-session-signaling from the client
  • the present invention provides a communications environment comprising a client and a server for communicating with each other by means of a first communications environment.
  • the communications environment according to the present invention utilizes a signaling according to an embodiment of the signaling protocol according to the present invention for providing information with respect to a second communications environment at least to one of the client and the server.
  • the client of the communications environment according to the present invention is a specific entity which a telecommunications web site is associated to while the server thereof is at least partially represented by the telecommunications web site associated to the specific entity.
  • Fig. 1 shows a schematic diagram depicting a client and a server in a first communications environment and end user units of a network a second communications environment.
  • Fig. 2 shows a schematic diagram depicting a specific entity and a telecommunications web site in a first communications environment and telephones of a telephone network in a second communications environment.
  • the signaling protocol according to the present invention is also referred to herein as a telecommunications web site signaling protocol.
  • Data exchange for this signaling protocol is telegram-oriented and "light weighted". This is to enable a server utilizing that signaling protocol to handle a plurality of clients. Further, all data exchanges or "telegrams" are idempotent in their semantics, Thus a double transmission can be achieved without problems. Further, data communications are secure since they are private and authenticated both from the server-side and the client-side. As set forth above, data polling is not employed in general. Rather, a client communicates its signaling to the server via a push of data while the server also communicates its signaling as push.
  • signaling characterized measures, modifications, actions and variations to be carried out with respect to a communications environment are generally not immediately answered by a respective return signaling. Rather, such a return signaling will be communicated upon the intended/desired modification etc. with respect to the particular communications environment is actually effected.
  • a user datagram protocol UDP is employed for data communications according to the protocol described here.
  • a first communications environment CEl comprises a plurality of clients of which only client CL is shown is shown in that figure and a server SV which can be embodied as hardware and/or software server.
  • a communication between the client CL and the server SV is executed via a communications link L.
  • Examples for this communications link comprise any wired and/or wireless transmission lines capable of transmitting data and/or information.
  • Fig. 1 illustrates a second communications environment CE2 wherein by means of a network communications between at least two end user units can be performed.
  • a network communications between at least two end user units can be performed.
  • only two end user units EUUl and EUU2 are shown.
  • communications originating from one of the end user units in the second communications environment CE2 can be routed from the second communications environment CE2 to another communications environment such as the first communications environment CEl or any other communications environment.
  • the first communications environment CEl this is illustrated by means of the arrow from the network N to the first communications environment CEl and vice versa.
  • the network N can be, for example, a telephone network
  • the end user units EUUl and EUU2 can be units or devices comparable to a telephone or providing its functions .
  • the end user units EUUl and EUU2 may be another device that can be used for communications, for example a keyboard, a computer terminal, a mobile phone, a fax, a telex, a mail pigeon, an ordinary letter, a scanner, a PSTN device, a Third Generation (3G) wireless communications device, especially a UMTS device, etc.
  • the end user unit may be a telecommunications web site, a telecommunications portal comprising more than one telecommunications web sites or a device using a browser-based application.
  • the signaling protocol according to the present invention is, as set forth above, employed to exchange information between the client CL and the server SV with respect to the second communications environment CE2.
  • the signaling protocol according to the present invention provides for a signaling characterizing desired, requested, prevailing and actually existing operation modes of the second communications environment CE2 with respect to an end user unit and its communications via the network N.
  • the end user to which a signaling according to the present invention between the client CL and the server SV relates to is an end user unit being associated to the client.
  • the client CL can be a personal computer while the end user unit to which a signaling according to the present invention to and from the client CL is related to can be a telephone or any other communications unit which can be or is used by the user of the personal computer representing the client CL.
  • the client CL is a computer-based end user unit such as a personal computer
  • the server SV is a system or unit comparable to a server known from the Internet
  • the first communications environment CEl comprises, at least partially, the Internet such that the communications link L is an Internet communication link
  • the network N is a telephone network
  • the end user units EUUl and EUU2 are telephones all thereof being comprised by the second communications environment CE2, thus, representing a telephone communications environment.
  • signaling according to the signaling protocol according to the present invention is communicated between the client CL and the server SV and provides information to the client CL and to the server SV with respect to intended/desired and carried out communications by means of the first end user unit EUUl. It is assumed that the first end user unit EUUlis associated with the client CL, as set forth above.
  • the signaling protocol according to the present invention provides different functionalities that are, in line with the above assumptions, explained with respect to the telephone communications environment CE2.
  • the functionality "login” for the client and, in response thereto, the functionality "acknowledgement” from the server SV are used.
  • the signaling protocol provides the functionality "line state". That functionality generally signalizes the state of the telephone line TL shown in Fig. 1.
  • that functionality comprises a signaling "ring” indicating that a telephone line to the first end user unit EUUl is desired from a third party, i.e. the telephone EUUl of the user of the client CL rings.
  • the functionality "line state” provides for a signaling "hang up” indicating that the telephone line to the end user unit EUUl terminated, i.e. that the user of the telephone EUUl has put down the handset.
  • Signaling and functionality in this regard are employed from the server SV to the client CL. This is due to the fact that the server SV obtains data and/or information in this regard from the second communications environment CE2. Examples of how such data and/or information can be provided to the server are explained below.
  • the signaling protocol provides the functionality "line actions" .
  • that functionality provides for a signaling indicating that the user of the client CL wants to establish a telephone communications link or telephone line from his/her end user unit EUUl to the end user unit EUU2, for example a telephone associated to another person.
  • Acknowledgements from the server SV in this regard are assumed to be signaled implicitly, i.e., the received packet is not directly acknowledged or confirmed, but rather a change of sate of the server is signaled.
  • the functionality "server state” is provided. That functionality allows for informing the client CL about states, conditions, operational modes and the like within the second communications environment CE2 with respect to the end user unit EUUl associated to the client CL.
  • the signaling protocol according to the present invention provides for the functionalities "keep alive”, “log out”, “time synchronization” and "packet delay” which will be explained in the description of protocol data units of the signaling protocol according to the present invention below.
  • all signaling related to that telephone line is characterized by a unique identification for that telephone line.
  • signaling according to the signaling protocol of the present invention is encrypted, advantageously according to TLS 1.0/SSL 3.0. That means an asymmetrical handshake and a symmetrical session encryption is used without client certificates.
  • the security of the signaling protocol according to the present invention is designed according to SSL standard.
  • the server SV transmits a certificate including a public key.
  • a session key provided from the client CL is encrypted with that key and used further on.
  • the signaling protocol according to the present invention does not support different certificates.
  • the step of transmitting a certificate including a public key from the server SV to the client CL can be omitted. Rather, in that case it is assumed that the public key is available on the client CL.
  • the signaling protocol includes the following definitions:
  • the line format is big endian, i.e., Most Significant Byte (MSB) first.
  • MSB Most Significant Byte
  • Byte steam (system of octets): MSB first. Bytes are integrated into a data bracket one after another.
  • Strings Coding with lengths descriptors, i.e., one word length is followed by string data. In case of an uneven length, a padding byte is subsequently used.
  • Example: "Haus 00 05 ⁇ " 'a' 'u' 's' 00". Not existing strings (empty strings) are coded as 00 00.
  • Padding for symmetrical block ciphers Since symmetrical ciphers often employ blocks having a predefined length, the lengths of the data packets are coded separately. Remaining space at the end of a data packet is padded with OxAA 0x55 until the next block is reached. The length is coded by utilizing a word a the beginning.
  • the signaling protocol according to an embodiment of the present invention employs two different ciphers: An asymmetrical initialization cipher (according to RSA) and a symmetrical session cipher according to RC4.
  • the initialization protocol data unit is only encrypted with the initialization cipher. Since the session cipher is proposed from the client CL, the session cipher is variable.
  • all protocol data units of the signaling protocol according to an embodiment of the present invention are always encrypted. Further, all protocol data units are provided with a time stamp and are signed. Except for the initialization protocol data unit, all protocol data units of the signaling protocol according to an embodiment of the present invention are defined to include the following protocol data unit portions PDUP: PDUPl : current version of the signaling protocol according to an embodiment of the present invention (e.g., 1); 1 word
  • protocol data unit number 1 word; PDUP3 time stamp; 2 words PDUP4 usable data, x words PDUP5 signature of PDUPsl-4, 16 byte
  • the protocol data unit portions 1-5 are symmetrically encrypted. In case of RC4 this maintains the length of the protocol data units .
  • the time stamp in the protocol data unit portion 4 prevents replay attacks since, for a verification of the signature, the time stamp is additionally used for a plausibility assessment.
  • plausibility refers to a protocol data unit being "not too old", for example not older than 30 minutes.
  • the signature of a received protocol data unit is retrieved and compared with a calculated signature.
  • a calculated signature obtained by means of the receiving party is calculated according to RFC 2104 as HMAC signature.
  • the initialization protocol data unit also referred to as protocol data unit 1 (PDUl) , provides for a so-called "client hallo" signaling from the client CL to the server SV and has the following format: PDUP1: Protocol version (e.g., 1) ; 1 Word PDUP2: PDU number 1; 1 Word PDUP3: Time stamp; 1 Long
  • PDUP4 Client version major [indicating major changes of the version (e.g., new functionalities); example: In version 3.5 of the client , "3" represents the major version number and "5" the minor version number]
  • PDUP5 Client version minor [indicating minor changes of the version (e.g., error corrections); example: In version 3.5 of the client , "3" represents the major version number and "5" the minor version number]
  • PDUP6 Session cipher 1 (RC4)
  • PDUP7 Session key length in Bytes (typically 16 Bytes)
  • PDUP8 Session key PDUP9 Signature
  • 64 Bytes The client generates the session key and the signature key.
  • Semantics for the client "I contact the server and request capacities of the server. If capacities of the server are available, I inform the server of the server of my IP- address/port. If no server capacity is available, I expect a forwarding address. In case I do not receive any information from the server within a certain time period (e.g., 30 seconds), I try again.”
  • Semantics for the server "A client having a peer-IP-address wants to register. In case, a session is already associated to this IP-address/port, I reject/dismiss this packet. If I have capacities available, I send a response (see “server hallo” signaling described below) and expect a response from the client within a predefined period of time (e.g., 1 minute) . Otherwise, I reject/dismiss this client session. If I do not have any capacities available, I return a forwarding/redirecting address to the client. In case the received request is alleged to be a request from an intruder (e.g., DoS attack), I record this event and reject/dismiss the packet . "
  • the protocol data unit portions 3-9 transmitted to the server are encrypted with the initialization cipher algorithm.
  • the format of the protocol data unit PDUl can be given as:
  • PDUP1 Protocol version (e.g., 1); 1 Word
  • PDUP2 PDU number 1; 1 Word
  • PDUP3-9 Crypt data (RSA 1024); 128 Bytes
  • This return packet has the following structure:
  • PDUP1 Protocol version (e.g., 1); 1 Word PDUP2 : PDU number 2 ; 1 Word PDUP3 : Timestamp (Server time), 1 Long
  • PDUP7 Reason code (Success: 0); 1 Word PDUP8: Redirect required (Yes: 1; No: 0); 1 Word
  • PDUP9 String: New Host: Format: HOST: PORT (optional in case of redirect)
  • PDUP10 HMAC over PDUPl - PDUP9; 16 Bytes
  • the protocol data unit portions 3-10 are encrypted with a session key and a session cipher. This applies also for the description of signaling structures and formats below.
  • Semantics for the server "I inform the client that he is allowed to authenticate himself or that he should contact another server. In case I have capacities available for a client, I wait a certain period of time (e.g., 60 seconds) for an authentication of the client. Otherwise, I dismiss/reject the whole client context with respect to this IP- address/port . "
  • Semantics for the client "If I receive a redirection/forwarding server address, I contact that address (e.g., a new URL) by means of a "client hallo" signaling. Otherwise, I authenticate myself to the server. "
  • client login For authentication, identification and login, the client employs a so-called “client login” signaling communicated from the client CL to the server SV which exhibits the following format:
  • PDUPl Protocol version (e.g., 1); 1 Word PDUP2 : PDU number 3 ; 1 Word PDUP3 : Time stamp (Client time); 1 Long PDUP4: Username; 1 String
  • Semantics for the client "I transmit my login and the password of my account to the server. I expect an acknowledgement by the server within a certain period of time (e.g., 30 seconds). Otherwise I keep trying.”
  • the server In response to the "client login” signaling, the server returns to the client a so-called “login response” signaling with the following structure:
  • PDUPl Protocol version (e.g., 1) ; 1 Word PDUP2: PDU number 4; 1 Word
  • PDUP3 Time stamp (Server time); 1 Long
  • Session Identification SessionlD (for later accesses per
  • n x [number of pairs of area tags and URL in a packet]
  • Area tag e.g., "Hist”
  • URL prefix for area e.g., "https://server.domain.com”
  • Semantics for the server "I inform the client whether its login was accepted or not. In case the login was accepted, I inform the client about its session identification sessionID and provide at least one pair of HTML-area-tags and URLs by means of which the client is enabled to download content utilizing HTTPS. (In case of a telecommunications web site functioning as server: "I generate the session identification sessionlD on the session server and register the session with the connection manager and the state managers of the core engines.” Telecommunications web sites are discussed below with reference to Fig. 2.). Otherwise I inform the client why the login has failed. "
  • Semantics for the client "In case of a successful login, I obtain a list of area tags and associated URLs. I expect that the server will communicate messages with respect to the state of the telephone line to my end user unit (telephone) in the future. Otherwise, I do not receive a session identification and no URLs but instead a coded reason for a rejection. "
  • a so-called "keep alive request" signaling which has the following format:
  • PDUPl Protocol version (e.g., 1); 1 Word PDUP2 PDU number 5; 1 Word PDUP3 Time stamp (client time) ; 1 Long PDUP4 empty PDUP5 Signature; 16 Bytes
  • the empty PDUP4 indicates the server that this message is a "keep alive request” signaling.
  • the "keep alive request” signaling will be communicated from the client to the server in predefined intervals to indicate "I am alive”. Otherwise the server will “drop” or “forget” the client. Then, the client has to login again ("client hello” signaling) to be connect to the server in this regard.
  • client hello signaling
  • the server In response to the "keep alive request” signaling received from the client the server returns a so-called “keep alive response” signaling with the following format
  • PDUPl Protocol version (e.g., 1); 1 Word PDUP2 PDU number 6; 1 Word PDUP3 Time stamp (server time) ; 1 Long PDUP4 empty PDU 5 Signature; 16 Bytes
  • the empty PDUP4 indicates the client that this message is a "keep alive response" signaling.
  • the client In case the client wants to terminate signaling actions according to the signaling protocol according to an embodiment of the present invention, the client communicates a so-called "logout" signaling to the server with the following structure:
  • PDUPl Protocol version (e.g., 1); 1 Word
  • PDUP2 PDU number 7 ; 1 Word
  • PDUP3 Timestamp (server time); 1 Long
  • PDUP4 Reason code [reasoning from the client to the server for logout]
  • the server terminates the session related to the client (in case of a telecommunications web site functioning as server, this termination is not performed with respect to the session server) .
  • the server To inform the client of modifications, variations, changes, etc. of the state of the line to the end user unit (telephone) associated to the client, the server employs a so-called “line state message” signaling with the following structure:
  • PDUPl Protocol version (e.g., 1); 1 Word PDUP2 PDU number 8; 1 Word PDUP3 Time stamp (server time) ; 1 Long PDUP4 new/current of the line; 1 Word Line identification LinelD; 1 String Call identification CalllD; 1 String
  • Caller Name (User of Client) Caller name; 1 String; optional PDUP5: Signature; 16 Bytes
  • the server provides the client with information with respect to the second communications environment being not directly related to the telephone line. Rather, that signaling realizes all push semantics possessing the characteristics of indicating an actualization.
  • the "new server state” signaling has the following structure: PDUPl: Protocol version (e.g., 1); 1 Word PDUP2: PDU number 9; 1 Word
  • PDUP3 Time stamp (Server time); 1 Long
  • PDUP4 Key for type of updated information (e.g., "42" for incoming call in the absence of the user of the client) ; 1
  • Word Value of up-dated information e.g., "5") or empty string; 1 String
  • the information can be directly transmitted by means of the protocol data unit portion 4 PDUP4.
  • the protocol data unit portion 4 PDUP4 For example, in the case of an incoming call directed to the end user unit (telephone) associated to the client, the following "new server state" signaling can be employed:
  • this protocol data unit portion 4 PDUP4 can be used to initiate a call from the client CL to the server to obtain the information the server wants to provide to the client.
  • the server wants to inform the client that a new fax has been received and wants to inform the client about the content of the fax, the following "new server state" signaling can be used:
  • a so-called “line action” signaling from the client to the server is employed.
  • Such signaling exhibits the following format: PDUPl: Protocol version (e.g., 1); 1 Word PDUP2: PDU number 10; 1 Word PDUP3 : Time stamp (client time); 1 Long
  • PDUP4 Action code (e.g., "hangup”, “park”, telephone line to " ) ; 1 Word LinelD; 1 Word CalllD; 1 String Destination; 1 String; optional
  • Semantics for the client "I instruct the server to perform a specific action with respect to my telephone. I expect that the server (continuously) informs me with regard to the performance to the requested action.”
  • Semantics for the server "The client requests a specific action to be performed with respect to its telephone. I obtain information with respect to the state of the telephone associated to the client, and forward the same to the client. (In case a telecommunications web site is used as server the request for a specific action with respect to the telephone associated to the client is forwarded to the core engine.) .
  • Examples of action codes used in the protocol data unit portion 4 are "DIAL”, “CREATECONF” , “XFERCONF” and “DETACHCONF” .
  • the "line action” signaling indicates a so-called initiating call which means that the number of the telephone associated to the client has to be called first, and the number of a party to which a telephone communication has to be established subsequently.
  • the line identification linelD is irrelevant. If the "destination" information is used in the protocol data unit portion 4, that information contains a telephone number or any comparable address information of a party to which the client wants to establish a communications link.
  • the contactID contains a destination contact, the number of which has to be called.
  • the call identification calllD indicates the identification of the existing call (i.e. telephone line to the telephone associated to the client) .
  • the line identification linelD is irrelevant while the "destination" information contains a telephone number or the like of the party to be called.
  • the contact identification contactID comprises an identification of the destination/party to be contacted while the telephone number or the like provided by the "destination" information of the protocol data unit portion 4 overwrites the contact identification contactID therein.
  • the client By means of the action code "CREATECONF" the client indicates that a conference call is to be established.
  • the line, call and contact identifications linelD, calllD and contactID are irrelevant, while the "destination" information in the protocol data -unit portion 4 indicates the number of channels, lines, etc. to be reserved.
  • the action code "XFERCONF" informs the server that the client intends to transfer a telephone line into a conference call.
  • the call identification calllD indicates the identification of the call to which the telephone line was directed so far.
  • the line identification linelD indicates the telephone line to be transferred, while the "destination" information characterizes the call identification calllD of the conference call to which the telephone line is to be transferred.
  • the contact identification contactID is irrelevant here.
  • the action code "DETACHCONF" is used.
  • the "destination information” and contact identification contactID are irrelevant, while the call identification calllD identifies the conference call from which the telephone line should be removed.
  • the line identification linelD characterizes the telephone line to be removed from the conference call .
  • PDUPl Protocol version (e.g., 1); 1 Word PDUP2 PDU number 11; 1 Word PDUP3 Time stamp (Client time) ; 1 Long PDUP4 empty PDUP5 empty
  • the server In response to such signaling the server returns a "line state” and/or “new server state” signaling to the client.
  • a so-called “login to session” signaling can be communicated from the client to the server.
  • Such signaling has the following structure:
  • PDUPl Protocol version (e.g., 1); 1 Word PDUP2 PDU number 12; 1 Word PDUP3 Time stamp (Client time) ; 1 Long PDUP4 SessionlD PDUP5 Signature; 16 Bytes
  • This signaling can be employed if the client is already communicating with the server, for example participates in a conventional Internet session with the server. Then, the "log in to session" signaling communicated from the client, informs the server that the client also wants to participate in a session wherein a signaling according to the signaling protocol of the present invention will be employed with respect to both the client and the server.
  • error message signaling has the following format: PDUPl: Protocol version (e.g., 1); 1 Word
  • PDUP2 PDU number 13 ; 1 Word
  • PDUP3 Time stamp (Client time); 1 Long
  • PDUP4 Error code (see table below); 1 Word
  • the signaling protocol according to an embodiment of the present invention is designed such that all functionalities for generating, analyzing, sending and receiving can be encapsulated in a software library. Further, it is possible that the signaling protocol according to an embodiment of the present invention can be implemented into conventional client software, such as software for personal computers.
  • Fig. 2 illustrates an embodiment of the present invention where the server SV described above with reference to Fig. 1 is a telecommunications web site TCW, and the client CL is a specific entity SE associated with the telecommunications web site TCW.
  • the discussion above with reference to Fig. 1 applies to the signaling between the specific entity SE and the telecommunications web site TCW.
  • Fig. 2 illustrates that the second communications environment CE2 is a telephone environment wherein telephones such as the telephones Tl and T2 can communicate via a telephone network TN. Examples for the telephone network TN include PSTN-based networks, GSM networks, UMTS networks, etc.
  • the telecommunications web site TCW uses its core engine CE.
  • switching means SW for example a PSTN switch, or comparable units such as gates, gateways and the like are used.
  • the switching means SW or the like are controlled and/or utilized by the core engine CE .
  • web site and "web page” define sites and sub- sites associated thereto which can be uniquely addressed by means of a single address, like a telephone number or an IP address, a uniform resource locator (URL) , etc.
  • a web site may be used in a 3G-communication environment, especially an UMTS environment.
  • a web site may be a site on the Internet with a specific URL, such as a site on the World Wide Web, which can be accessed by Internet visitors, and by the web site host.
  • the web site host is the owner of the web site.
  • a web site can include one or more web pages. These web pages are part of the one web site. It should be noted that the terms "web site” and “web page” are not to be considered to limit the present invention to conventional Internet web sites and web pages. Thus, the web site and its web page(s), respectively, can be accessed by establishing a communications link from the first end user unit independently of the network (s) employed.
  • a telecommunications web site is preferably a web site adapted to provide, upon an access event, for private communications between two entities .
  • the telecommunications web site corresponds to a first specific entity and is adapted to provide, upon an access by the first end user unit, for private communications between the first end user unit and the first specific entity.
  • the terms "telecommunications web site”, “web site” and “web page” may be understood to encompass software and hardware components effecting these entities. Such components may include one or more processors, for example.
  • a telecommunications web site is assigned to or personalized for or corresponding to a specific person or entity.
  • a specific entity can be a person, a company or any other entity.
  • the specific entity preferably acts as the host of the telecommunication web site.
  • the specific entity may be a single entity, e.g., a specific user or owner (e.g., a single person, a company, a unit of a company, etc.) of the telecommunications web site, a specific address, a specific location, a specific end user unit and the like.
  • properties and functions of a telecommunications web site, including its core engine are described in commonly- assigned U.S. patent application number 10/201446, entitled “Communications Environment,” filed July 23, 2002, and in commonly-assigned U.S. patent application number 10/354709, entitled “Web Site Having an Event Identification Element,” filed January 29, 2003.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un protocole de signalisation destiné à un client et à un serveur dans un environnement de communication. Ce protocole consiste à fournir au client et/ou au serveur des informations concernant un autre environnement de communication.
EP03727408A 2002-04-30 2003-04-30 Protocole de signalisation Ceased EP1502410A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP03727408A EP1502410A2 (fr) 2002-04-30 2003-04-30 Protocole de signalisation

Applications Claiming Priority (14)

Application Number Priority Date Filing Date Title
EP02009777 2002-04-30
EP02009777A EP1359702A1 (fr) 2002-04-30 2002-04-30 Environnement couvert par un système de communication comprenant un site web capable de télécommunications multimedia
EP02016141A EP1383275A1 (fr) 2002-07-19 2002-07-19 Environnement couvert par un système de communication comprenant un site web capable de télécommunications multimedia
EP02016141 2002-07-19
US10/201,446 US20040019629A1 (en) 2002-07-23 2002-07-23 Communications environment
US201446 2002-07-23
EP02020448 2002-09-11
EP20020020448 EP1398933A1 (fr) 2002-09-11 2002-09-11 Protocole securise de signalisation client-serveur
US354709 2003-01-29
US10/354,709 US20040148392A1 (en) 2003-01-29 2003-01-29 Website having an event identification element
US10/395,951 US20040205196A1 (en) 2003-03-24 2003-03-24 Signaling protocol
US395951 2003-03-24
EP03727408A EP1502410A2 (fr) 2002-04-30 2003-04-30 Protocole de signalisation
PCT/EP2003/004540 WO2003094431A2 (fr) 2002-04-30 2003-04-30 Protocole de signalisation

Publications (1)

Publication Number Publication Date
EP1502410A2 true EP1502410A2 (fr) 2005-02-02

Family

ID=29408174

Family Applications (1)

Application Number Title Priority Date Filing Date
EP03727408A Ceased EP1502410A2 (fr) 2002-04-30 2003-04-30 Protocole de signalisation

Country Status (3)

Country Link
EP (1) EP1502410A2 (fr)
AU (1) AU2003233211A1 (fr)
WO (1) WO2003094431A2 (fr)

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2173304C (fr) * 1995-04-21 2003-04-29 Anthony J. Dezonno Methode et systeme pour etablir des communications vocales via un reseau informatique
WO1998051063A1 (fr) * 1997-05-06 1998-11-12 Northern Telecom Limited Dispositif de gestion des appels et procedes permettant de traiter les appels durant une session internet
US6144667A (en) * 1997-08-07 2000-11-07 At&T Corp. Network-based method and apparatus for initiating and completing a telephone call via the internet
US20020046299A1 (en) * 2000-02-09 2002-04-18 Internet2Anywhere, Ltd. Method and system for location independent and platform independent network signaling and action initiating

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ALAN O. FREIER NETSCAPE COMMUNICATIONS ET AL.: "The SSL Protocol Version 3.0", DRAFT-IETF-TLS-SSL-VERSION3-00.TXT, 18 November 1996 (1996-11-18), IETF STANDARD-WORKING-DRAFT, pages 1 - 63, XP015029170 *

Also Published As

Publication number Publication date
AU2003233211A1 (en) 2003-11-17
WO2003094431A2 (fr) 2003-11-13
AU2003233211A8 (en) 2003-11-17
WO2003094431A3 (fr) 2004-04-01

Similar Documents

Publication Publication Date Title
Handley et al. SIP: session initiation protocol
US8537841B2 (en) Connection support apparatus and gateway apparatus
JP5143125B2 (ja) ドメイン間情報通信のための認証方法、システム、およびその装置
US7430664B2 (en) System and method for securely providing a configuration file over and open network
US8400970B2 (en) System and method for securing a personalized indicium assigned to a mobile communications device
US9088416B2 (en) Method for securely associating data with HTTP and HTTPS sessions
EP2096833B1 (fr) Système informatique de téléphonie sur IP (voix sur IP)
US20060050688A1 (en) Method and apparatus for user authentication
GB2433008A (en) Establishing a secure communications channel wherein setup messages include information about the level of security on each link they traverse
JP2004533751A (ja) データ記録を関連付けるためのシステムおよび方法
US20030050918A1 (en) Provision of secure access for telecommunications system
JP4838881B2 (ja) メディアデータを符号化および復号化するための方法、装置ならびにコンピュータプログラム製品
Spencer et al. Iax: Inter-asterisk exchange version 2
KR101478733B1 (ko) 단말기의 프로파일 정보를 네트워크에 등록하는 시스템
JP4472566B2 (ja) 通信システム、及び呼制御方法
EP1961149B1 (fr) Procédé destiné à associer de façon securisée des données au moyen de sessions http et https
JP4677350B2 (ja) 呼制御信号転送装置、呼制御信号転送方法および呼制御信号転送プログラム
US20040205196A1 (en) Signaling protocol
JP5609519B2 (ja) Ｓｉｐ機器
KR100871422B1 (ko) 인터넷폰 서비스 제공 장치 및 그 방법
EP1502410A2 (fr) Protocole de signalisation
US8259914B2 (en) System and method for a secure log-on to a communications system comprising network connection and connection handling computers
EP1398933A1 (fr) Protocole securise de signalisation client-serveur
US7197766B1 (en) Security with authentication proxy
EP1161827A2 (fr) Arrangement relatif a une procedure d'appel

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20041130

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK

RIN1 Information on inventor provided before grant (corrected)

Inventor name: RINKE, STEFAN

Inventor name: SCHNEIDER, UWE

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: COMBOTS PRODUCT GMBH & CO.KG

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20070927