WO2001013594A1 - Establishing communication in a packet data network - Google Patents

Establishing communication in a packet data network Download PDF

Info

Publication number
WO2001013594A1
WO2001013594A1 PCT/IB2000/001123 IB0001123W WO0113594A1 WO 2001013594 A1 WO2001013594 A1 WO 2001013594A1 IB 0001123 W IB0001123 W IB 0001123W WO 0113594 A1 WO0113594 A1 WO 0113594A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
callobject
incoming
call
communication
Prior art date
Application number
PCT/IB2000/001123
Other languages
French (fr)
Inventor
Christophe Bouret
Pekka Pessi
Original Assignee
Nokia Corporation
Nokia Inc.
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 Nokia Corporation, Nokia Inc. filed Critical Nokia Corporation
Priority to AU65861/00A priority Critical patent/AU6586100A/en
Publication of WO2001013594A1 publication Critical patent/WO2001013594A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer

Definitions

  • the present invention relates to a method and system for establishing communication over a data packet network.
  • the method and system for establishing communication over a data packet network in accordance with the present invention reduces transmission congestion on the data packet network, increases security options for call receivers on the data packet network and ensures more accurate billing procedures for facilitators of the data packet network.
  • VOIP voice over IP
  • the present invention provides a method and system for establishing communication over a data packet network, which includes, but is not limited to, the Internet, which reduces transmission traffic over the data packet networks, provides more reliable communication tracking and billing methods, and ensures security and privacy for users of the data packet networks.
  • each subscriber user of the data packet network has both an outgoing callobject and an incoming callobject stored at either of the local server or the user terminal, and communication over the data packet network is established utilizing the respective callobjects of both the calling party and the call receiving party.
  • each subscriber user of the data packet network registers an incoming callobject at a location directory service.
  • the incoming callobject includes an incoming callobject call originating service and an incoming callobject call presentation service.
  • the incoming callobject call originating service alone to be registered at the location directory service while the incoming callobject call presentation service is stored at either the local server or terminal of the respective subscriber user.
  • the incoming callobject to contain only the incoming callobject call originating service.
  • the incoming callobject call originating service includes call receiving capabilities and parameters which are customized by the respective subscriber user. For instance, assuming that the subscriber user's terminal is fully capable, the subscriber user is able to specify the call receiving parameters for communication on the data packet network. Such parameters include, but are not limited to, call forwarding, call waiting, caller ID, call blocking, voice mail, short message reception, video call reception and specific bandwidth requirements or configurations for an incoming call.
  • the incoming callobject call presentation service can be registered to the location directory service along with the incoming callobject call originating service in an incoming callobject package or it can be stored at the local server or terminal.
  • the incoming callobject call presentation service identifies the parameters of an incoming call to a subscriber user, thus allowing the subscriber user to dynamically respond to an incoming call.
  • the incoming callobject call presentation service is located at the terminal or local server of the calling party it is initialized by the incoming callobject call originating service with the call parameters and transferred to the local terminal or server of the receiving party. Otherwise the incoming callobject call presentation service is already located at the local terminal or server of the receiving party and is alerted of an incoming call request via messaging.
  • each subscriber user of the data packet network also has an outgoing callobject stored at either of the local server or the user terminal.
  • the outgoing callobject includes the outgoing calling capabilities of a subscriber user of the data packet network.
  • the subscriber user is able to specify the call receiving parameters for communication on the data packet network, including, but not limited to, call forwarding, call waiting, caller ID, call blocking, voice mail, text message reception, video data reception and specific bandwidth requirements or configurations for an incoming call.
  • the incoming callobject which stores these customized call receiving parameters are stored in the Incoming CallObject Call Originating Service or the receiving party's incoming callobject.
  • the receiving party then registers the respective incoming callobject in a location directory service (LDS).
  • LDS may be either a local service available only to subscriber users of the data packet network or a universal service available to all users of the data packet network.
  • the subscriber user when a subscriber user (calling party) of the data packet network wants to establish communication with the receiving party, the subscriber user transmits a query to the location directory service, in accordance with the receiving party's logical address. In response to the query, the calling party is able to download a copy of the receiving party's incoming callobject to either the calling party's local server or local terminal.
  • the calling party then checks whether the outgoing callobject of the calling party is compatible with the receiving party's incoming callobject. That is, the outgoing callobject stored at either of the local server or the user terminal includes the outgoing calling capabilities of a subscriber user of the data packet network, which include, but are not limited to, speed dialing, voice message data transmission, text data transmission, video data transmission, call monitoring, bandwidth specifications and security checking.
  • the calling party initiates communication with the receiving party by transmitting data.
  • Such transmission includes, but is not limited to, placing a telephone call, sending a text message, and sending video data.
  • the incoming callobject call presentation service is sent to either the local server or local terminal of the receiving party.
  • the parameters of the incoming call are presented to the receiving party, who is thus able to dynamically respond to the incoming communication from the calling party. That is, the receiving party is able to respond to the copy of the Incoming CallObject Call Originating Service, via the incoming callobject call presentation service, in response to the initial communication from the calling party.
  • the receiving party is still informed of the incoming call when the incoming callobject does not contain the incoming callobject call presentation service, although the parameters of the incoming call are not presented to the receiving party.
  • an object transfer protocol including, but not limited to, H323, SIP and other media package protocols.
  • the calling party is able to control incoming communication, both in terms of who sends communications and the format thereof.
  • security of such data packet network communication is enhanced.
  • the present invention is able to significantly reduce transmission traffic on the data packet network.
  • the present invention is able to improve billing procedures for data packet network communication by monitoring communication using the incoming callobjects.
  • Fig. 1 is a block diagram illustrating the network interconnection of elements according to the present invention
  • Fig. 2 illustrates the incoming callobject and outgoing callobject according to the present invention
  • Fig. 3 is a block diagram of the method steps according to the present invention. DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT
  • the present invention provides communication between users over a data packet network, which includes, but is not limited to, the Internet.
  • a data packet network which includes, but is not limited to, the Internet.
  • the block diagram of Fig. 1 depicts a network connection between only two users, the present invention is applicable to multiple users communicating over a data packet network.
  • the following description of communication between User A 10A and User B 10B includes references to the Incoming CallObject 60 and Outgoing CallObject 70 shown in Fig. 2, and further includes reference to the flow chart of Fig. 3.
  • User A 10A retrieves his/her Incoming CallObject 60 which may be stored at either local server 30A or local terminal 20A, to thereby customize the parameters for local call receiving capabilities. That is, assuming that both the local server 30A and terminal 20A are capable of such services, User A 10A specifies the local call receiving capabilities in the Incoming CallObject Call Originating Service 61 of the Incoming CallObject 60.
  • User A 10A can request that all incoming communication be forwarded to another address, and/or specify that certain callers or forms of incoming communication be blocked from establishing communication thereat. Further, User A 10A can specify such call receiving capabilities including caller ID, text message reception, video data reception and even specify bandwidth parameters for incoming communications.
  • the Incoming CallObject 60 is stored in either the local server 30A or local terminal 20A and is therefore dynamic, and can therefore be customized at any time by User A 10A to change the parameters for local call receiving capabilities.
  • the Incoming CallObject 60 is registered in the location directory service (LDS) 40.
  • LDS 40 is either a local service available only to subscriber users of the data packet network or a universal service available to all users of the data packet network.
  • the Incoming CallObject 60 can be stored in the LDS by an intermediary, including a gatekeeper.
  • the Incoming CallObject 60 that is registered in the LDS 40 includes at least the Incoming CallObject Call Originating Service 61 , and can further, but not necessarily, include the Incoming CallObject Call Presentation Service 62.
  • the Incoming CallObject Call Presentation Service 62 described below, can be registered at either the local server 30A or local terminal 20A.
  • User b 10B sends a query to LDS 40 in accordance with the logical address for User A 10A, when User B 10B wishes to establish communication with User A 10A via the data packet network 50.
  • Step S40 the calling capabilities of User B 10B specified in the Outgoing CallObject 70 are compatible with the customized call receiving capabilities of User A 10A specified in the Incoming CallObject 60. If not, no communication is available between User B 10B and User A 10A, via the data packet network (Step S45).
  • Step S60 a communication request along with identification data from the Incoming CallObject Call Presentation Service 62 is transmitted to User A 10A where the parameters of the requested communication from User B 10B is identified (Step S60).
  • the Incoming CallObject Call Presentation Service 62 is registered at either the local server 30A or local terminal 20A, the communication request is received thereat so that the Incoming CallObject Call Presentation Service 62 can identify the parameters of the requested communication from User B 10B.
  • User A 10A is able to dynamically respond (eg. accept or reject) to the communication request from User B 10B. If the communication request is denied or rejected by User A 10A (Step S65), User B 10B's attempt to establish communication with User A 10A is terminated. However, if User A 10A accepts the communication request, User B 10B is so notified and communication between User B 10B and User A 10A is established via the data packet network 50 (Step S70). The communication is established within the compliant parameters of the Incoming CallObject Call Originating Service 61 and the Outgoing CallObject 70, and is further established utilizing data packet network protocols including, but not limited to, H323, SIP, and various other media transfer packages.
  • data packet network protocols including, but not limited to, H323, SIP, and various other media transfer packages.
  • a subscriber user of a data packet network is able to customize communication receiving capabilities for receiving communications over the data packet network.
  • a result of such customization results in a reduced volume of data transmissions over the data packet network, increased security since a subscriber user is able to control users from whom communications are received as well as the types of communications received, and call tracking is improved, as well, to thus improve billing procedures.

Abstract

A method and system for establishing communication over a data packet network which reduces transmission congestion on the data packet network, increases security options for call receivers on the data packet network and ensures more accurate billing procedures for facilitators of the data packet network. CallObject specifying customizing call receiving parameters are downloaded by a calling party who then requests communication with the call receiving party, if there is compliance between the CallObject of the call receiving party and the CallObject of the calling party which specifies the calling capabilities of the calling party.

Description

ESTABLISHING COMMUNICATION IN A PACKET DATA NETWORK
BACKGROUND OF THE INVENTION
The present invention relates to a method and system for establishing communication over a data packet network. In particular, the method and system for establishing communication over a data packet network in accordance with the present invention reduces transmission congestion on the data packet network, increases security options for call receivers on the data packet network and ensures more accurate billing procedures for facilitators of the data packet network.
Demand for communication over data packet networks including, but not limited to, the Internet has increased dramatically. Specifically, the demand has been for the application of conventional (i.e. cellular) telephony technology to data packet networks, including voice over IP (VOIP) service, real time video transmission, text messaging, etc.
Accordingly, facilitators of communication over data packet networks are faced with the challenges of reducing transmission traffic over the data packet network(s), providing more reliable communication tracking and billing methods, and ensuring security and privacy of users of the data packet network(s). SUMMARY OF THE INVENTION
Therefore, the present invention provides a method and system for establishing communication over a data packet network, which includes, but is not limited to, the Internet, which reduces transmission traffic over the data packet networks, provides more reliable communication tracking and billing methods, and ensures security and privacy for users of the data packet networks.
In particular, each subscriber user of the data packet network has both an outgoing callobject and an incoming callobject stored at either of the local server or the user terminal, and communication over the data packet network is established utilizing the respective callobjects of both the calling party and the call receiving party. First of all, each subscriber user of the data packet network registers an incoming callobject at a location directory service. The incoming callobject includes an incoming callobject call originating service and an incoming callobject call presentation service. Furthermore, it is possible for the incoming callobject call originating service alone to be registered at the location directory service while the incoming callobject call presentation service is stored at either the local server or terminal of the respective subscriber user. Further still, it is possible for the incoming callobject to contain only the incoming callobject call originating service.
The incoming callobject call originating service includes call receiving capabilities and parameters which are customized by the respective subscriber user. For instance, assuming that the subscriber user's terminal is fully capable, the subscriber user is able to specify the call receiving parameters for communication on the data packet network. Such parameters include, but are not limited to, call forwarding, call waiting, caller ID, call blocking, voice mail, short message reception, video call reception and specific bandwidth requirements or configurations for an incoming call.
The incoming callobject call presentation service can be registered to the location directory service along with the incoming callobject call originating service in an incoming callobject package or it can be stored at the local server or terminal. The incoming callobject call presentation service identifies the parameters of an incoming call to a subscriber user, thus allowing the subscriber user to dynamically respond to an incoming call. When the incoming callobject call presentation service is located at the terminal or local server of the calling party it is initialized by the incoming callobject call originating service with the call parameters and transferred to the local terminal or server of the receiving party. Otherwise the incoming callobject call presentation service is already located at the local terminal or server of the receiving party and is alerted of an incoming call request via messaging.
If the incoming callobject contains only the incoming callobject call originating service, the receiving party is alerted of an incoming call request without being informed of the parameters of the call. Further still, as described above, each subscriber user of the data packet network also has an outgoing callobject stored at either of the local server or the user terminal. The outgoing callobject includes the outgoing calling capabilities of a subscriber user of the data packet network. Accordingly, the procedure for establishing communication utilizing a data packet network, in accordance with the present invention is as follows. A subscriber user (receiving party) retrieves his/her incoming callobject from either a respective local server or a local terminal, and designates local call receiving capabilities and parameters which are customized by the respective subscriber user. Thus, assuming that the subscriber user's local server and terminal are fully capable of such services, the subscriber user is able to specify the call receiving parameters for communication on the data packet network, including, but not limited to, call forwarding, call waiting, caller ID, call blocking, voice mail, text message reception, video data reception and specific bandwidth requirements or configurations for an incoming call. The incoming callobject which stores these customized call receiving parameters are stored in the Incoming CallObject Call Originating Service or the receiving party's incoming callobject.
The receiving party then registers the respective incoming callobject in a location directory service (LDS). The LDS may be either a local service available only to subscriber users of the data packet network or a universal service available to all users of the data packet network.
Next, when a subscriber user (calling party) of the data packet network wants to establish communication with the receiving party, the subscriber user transmits a query to the location directory service, in accordance with the receiving party's logical address. In response to the query, the calling party is able to download a copy of the receiving party's incoming callobject to either the calling party's local server or local terminal.
To actually initiate communication with the receiving party via the data packet network, the calling party then checks whether the outgoing callobject of the calling party is compatible with the receiving party's incoming callobject. That is, the outgoing callobject stored at either of the local server or the user terminal includes the outgoing calling capabilities of a subscriber user of the data packet network, which include, but are not limited to, speed dialing, voice message data transmission, text data transmission, video data transmission, call monitoring, bandwidth specifications and security checking.
If the calling party's outgoing callobject is compatible with the parameters of the receiving party's incoming callobject, specifically the Incoming CallObject Call Originating
Service, the calling party initiates communication with the receiving party by transmitting data. Such transmission includes, but is not limited to, placing a telephone call, sending a text message, and sending video data.
At this point, if the incoming callobject has been registered in the location directory service with both the Incoming CallObject Call Originating Service and the incoming callobject call presentation service, the incoming callobject call presentation service is sent to either the local server or local terminal of the receiving party. Thus, the parameters of the incoming call are presented to the receiving party, who is thus able to dynamically respond to the incoming communication from the calling party. That is, the receiving party is able to respond to the copy of the Incoming CallObject Call Originating Service, via the incoming callobject call presentation service, in response to the initial communication from the calling party. The receiving party is still informed of the incoming call when the incoming callobject does not contain the incoming callobject call presentation service, although the parameters of the incoming call are not presented to the receiving party. If the communication is accepted by the receiving party, full communication is established between the calling party and the receiving party over the data packet network, utilizing an object transfer protocol, including, but not limited to, H323, SIP and other media package protocols.
As a result of the data packet network communication of the present invention, the calling party is able to control incoming communication, both in terms of who sends communications and the format thereof. Thus, security of such data packet network communication is enhanced.
Furthermore, by first checking for compatibility between the calling party's outgoing callobject and the receiving party's incoming callobject before initiating communication there between, the present invention is able to significantly reduce transmission traffic on the data packet network.
Lastly, the present invention is able to improve billing procedures for data packet network communication by monitoring communication using the incoming callobjects. BRIEF DESCRIPTION OF THE DRAWINGS
The scope of the present invention will be apparent from the following detailed description, when taken in conjunction with the accompanying drawings, and such detailed description, while indicating preferred embodiments of the invention, are given as illustrations only, since various changes and modifications within the spirit and scope of the invention will become apparent to those skilled in the art from this detailed description, in which:
Fig. 1 is a block diagram illustrating the network interconnection of elements according to the present invention;
Fig. 2 illustrates the incoming callobject and outgoing callobject according to the present invention; and
Fig. 3 is a block diagram of the method steps according to the present invention. DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT
The present invention, as shown in Fig. 1 , provides communication between users over a data packet network, which includes, but is not limited to, the Internet. Although the block diagram of Fig. 1 depicts a network connection between only two users, the present invention is applicable to multiple users communicating over a data packet network. The following description of communication between User A 10A and User B 10B includes references to the Incoming CallObject 60 and Outgoing CallObject 70 shown in Fig. 2, and further includes reference to the flow chart of Fig. 3. Further still, the following description of communication between User A 10A and User B 10B assumes that User B 10B will be the calling party, attempting to establish communication with User A 10A, via the data packet network, although the Incoming CallObject 60 and Outgoing CallObject 70 are relevant to all such subscriber users of the data packet network. First of all, in order to receive communications via the data packet network which can include, but is not limited to, the Internet, User A 10A retrieves his/her Incoming CallObject 60 which may be stored at either local server 30A or local terminal 20A, to thereby customize the parameters for local call receiving capabilities. That is, assuming that both the local server 30A and terminal 20A are capable of such services, User A 10A specifies the local call receiving capabilities in the Incoming CallObject Call Originating Service 61 of the Incoming CallObject 60.
As an example only, User A 10A can request that all incoming communication be forwarded to another address, and/or specify that certain callers or forms of incoming communication be blocked from establishing communication thereat. Further, User A 10A can specify such call receiving capabilities including caller ID, text message reception, video data reception and even specify bandwidth parameters for incoming communications.
It should be noted that the Incoming CallObject 60 is stored in either the local server 30A or local terminal 20A and is therefore dynamic, and can therefore be customized at any time by User A 10A to change the parameters for local call receiving capabilities.
In step S10, the Incoming CallObject 60 is registered in the location directory service (LDS) 40. LDS 40 is either a local service available only to subscriber users of the data packet network or a universal service available to all users of the data packet network. The Incoming CallObject 60 can be stored in the LDS by an intermediary, including a gatekeeper. Furthermore, the Incoming CallObject 60 that is registered in the LDS 40 includes at least the Incoming CallObject Call Originating Service 61 , and can further, but not necessarily, include the Incoming CallObject Call Presentation Service 62. Conversely, the Incoming CallObject Call Presentation Service 62, described below, can be registered at either the local server 30A or local terminal 20A. In step S20, User b 10B sends a query to LDS 40 in accordance with the logical address for User A 10A, when User B 10B wishes to establish communication with User A 10A via the data packet network 50.
In response to the query, when a match is found between the logical address of User A 10A and the Incoming CallObject 60 of User A 10A, User B 10B is then able to download a copy of the Incoming CallObject 60 registered in the LDS 40 for User A 10A. The copy of the Incoming CallObject 60 for User A 10A is downloaded to either the local server 30B or local terminal 20B corresponding to User B 10B (Step S30). The combination of User B 10B sending the query and User B 10B downloading the Incoming CallObject 60 is known as fetching.
Thus, when User B 10B wishes to initiate communication with User A 10A, a check is made at either the local terminal 20B or local server 30B, to determine if the calling capabilities of User B 10B specified in the Outgoing CallObject 70 are compatible with the customized call receiving capabilities of User A 10A specified in the Incoming CallObject 60 (Step S40). If not, no communication is available between User B 10B and User A 10A, via the data packet network (Step S45).
Next, if the parameters of Outgoing CallObject 70 of User B 10B are compatible with the parameters of Incoming CallObject 60 of User A 10A, User B 10B continues to attempt to establish communication with User A 10A via the data packet network by sending a communication request to User A 10A. If the Incoming CallObject 60 includes both the
Incoming CallObject Call Originating Service 61 and the Incoming CallObject Call Presentation Service 62, a communication request along with identification data from the Incoming CallObject Call Presentation Service 62 is transmitted to User A 10A where the parameters of the requested communication from User B 10B is identified (Step S60). On the other hand, if the Incoming CallObject Call Presentation Service 62 is registered at either the local server 30A or local terminal 20A, the communication request is received thereat so that the Incoming CallObject Call Presentation Service 62 can identify the parameters of the requested communication from User B 10B.
Accordingly, after the parameters of the requested communication are identified in step S60, User A 10A is able to dynamically respond (eg. accept or reject) to the communication request from User B 10B. If the communication request is denied or rejected by User A 10A (Step S65), User B 10B's attempt to establish communication with User A 10A is terminated. However, if User A 10A accepts the communication request, User B 10B is so notified and communication between User B 10B and User A 10A is established via the data packet network 50 (Step S70). The communication is established within the compliant parameters of the Incoming CallObject Call Originating Service 61 and the Outgoing CallObject 70, and is further established utilizing data packet network protocols including, but not limited to, H323, SIP, and various other media transfer packages.
When the Incoming CallObject 60 contains only the Incoming CallObject Call Originating Service 61 , the receiving party is still informed of the incoming call, but is not informed of the parameters thereof. Call initialization otherwise remains the same as described above. Accordingly, by the present invention, a subscriber user of a data packet network is able to customize communication receiving capabilities for receiving communications over the data packet network. A result of such customization results in a reduced volume of data transmissions over the data packet network, increased security since a subscriber user is able to control users from whom communications are received as well as the types of communications received, and call tracking is improved, as well, to thus improve billing procedures.
While the present invention has been described in detail and pictorially in the accompanying drawings, it is not limited to such details since many changes and modifications may be made thereto without departing from the spirit and scope of the present invention. It is intended that all such modifications fall within the scope of the following claims.

Claims

WE CLAIM:
1. A method for establishing communication over a data packet network, said method comprising the steps of: registering an incoming callobject of a first terminal with a location directory service; fetching, by a second terminal, a copy of said incoming callobject of said first terminal from said location directory service; and initiating a communication from said second terminal to said first terminal in accordance with said incoming callobject of said first terminal.
2. A method according to Claim 1, wherein said incoming callobject of said first terminal includes an incoming callobject originating service.
3. A method according to Claim 2, wherein said incoming callobject originating service includes customized call receiving capability parameters for said first terminal.
4. A method according to Claim 3, wherein said customized call receiving capability parameters include call forwarding, call waiting, caller ID, call blocking, voice mail, short message reception, video call reception, and bandwidth specifications.
5. A method according to Claim 2, wherein said incoming callobject of said first terminal further includes an incoming callobject call presentation service which identifies parameters of the incoming communication from said second terminal.
6. A method according to Claim 5, wherein said incoming callobject call presentation service provides a user of said first terminal with dynamic interaction with said incoming callobject originating service when said second terminal initiates said communication to said first terminal.
7. A method according to Claim 5, wherein said parameters of said communication from said second terminal sent from said incoming callobject originating service include caller identification, short message text, voice message data, video message data and bandwidth specifications of said call.
8. A method according to Claim 5, wherein said incoming callobject originating service and said incoming callobject call presentation service are registered together in said incoming callobject in said location directory service.
9. A method according to Claim 8, wherein said incoming callobject call presentation service is transmitted to said first terminal after said second terminal fetches said incoming callobject of said first terminal from said location directory service.
10. A method according to Claim 5, wherein said incoming callobject call originating service is registered in said location directory service and said incoming callobject call presentation service is created and maintained at said first terminal.
11. A method according to Claim 2, wherein said second terminal has an outgoing callobject which includes call initiating capabilities of said second terminal.
12. A method according to Claim 11 , wherein said call initiating capabilities of said second terminal include speed dialing, voice message data transmission, text data transmission, video data transmission, call monitoring, bandwidth specifications of the call and security checking.
13. A method according to Claim 11 , wherein said incoming callobject of said first terminal is fetched from said location directory service by said second terminal in response to a query from said second terminal.
14. A method according to Claim 11 , wherein said step of initiating a call from said second terminal to said first terminal includes the sub-steps of: checking said outgoing callobject of said second terminal to determine if said communication desired by a user of said second terminal complies with the call initiating capabilities of said second terminal; sending, if said communication desired by a user of said second terminal is determined to comply with the call initiating capabilities of said second terminal, said communication from said outgoing callobject of said second terminal to the incoming callobject originating service of said first terminal; and sending said communication from said incoming callobject originating service of said first terminal to the user of said first terminal.
15. A method according to Claim 14, comprising the further sub-step of: identifying, by said incoming callobject call presentation service, the parameters of said communication sent from said incoming callobject originating service at said first terminal.
16. A method according to Claim 15, wherein said communication sent from said incoming callobject originating service of said first terminal is received by an incoming callobject call presentation service of said first terminal thus allowing the user of said first terminal to dynamically respond to said originating service callobject in response to said communication.
17. A method according to Claim 1 , wherein if said communication from said second terminal is accepted by a user of said first terminal, communication is established over a data packet network.
18. A method according to Claim 17, wherein said data packet network includes the Internet.
19. A method according to Claim 18, wherein said data packet network utilizes an H323 protocol standard.
20. A method according to Claim 16, wherein if said communication from said second terminal is accepted by a user of said first terminal, communication is established over a data packet network.
21. A method according to Claim 20, wherein said data packet network includes the Internet.
22. A method according to Claim 21 , wherein said data packet network utilizes an H323 protocol standard.
23. A method according to Claim 21 , wherein said data packet network supports object transfer protocol.
24. A method according to Claim 1 , wherein said incoming callobject of said first terminal is registered with said location directory service by a user of said first terminal.
25. A method according to Claim 1 , wherein said incoming callobject of said first terminal is registered with said location directory service by an intermediary.
26. A method according to Claim 1 , wherein said intermediary is a gatekeeper.
27. A method according to Claim 1 , wherein said second terminal fetches said incoming callobject of said first terminal directly to said second terminal.
1 28. A method according to Claim 1 , wherein said second terminal fetches said incoming callobject of said first terminal to a local server corresponding to said second terminal.
1 29. A method according to Claim 1 , wherein said location directory service is a local network directory.
1 30. A method according to Claim 1 , wherein said location directory service is a universal directory.
1 31. A method according to Claim 1 , wherein said incoming callobject of said first terminal is registered with said location directory service in accordance with a logical
3 address of said first terminal. l
32. A method according to Claim 1, wherein said incoming callobject is dynamic, l
33. A method according to Claim 11 , wherein said outgoing callobject is dynamic.
1 34. A communication system for a data packet network having a location directory service, said communication system comprising:
3 a first terminal which registers an incoming callobject with said location directory service; and
5 a second terminal which fetches a copy of said incoming callobject of said first terminal
6 from said location directory service, and initiates a communication to said first terminal in
7 accordance with said incoming callobject of said first terminal.
1 35. A communication system according to Claim 34, wherein said incoming callobject of
2 said first terminal includes an incoming callobject originating service.
1 36. A communication system according to Claim 34, wherein said incoming callobject
2 originating service includes customized call receiving capability parameters for said first
3 terminal.
1 37. A communication system according to 36, wherein said customized call receiving
2 capability parameters include call forwarding, call waiting, caller ID, call blocking, voice mail,
3 short message reception, video call reception, and bandwidth specifications.
1 38. A communication system according to Claim 35, wherein said incoming callobject of
2 said first terminal further includes an incoming callobject call presentation service which
3 identifies parameters of the incoming communication from said second terminal.
39. A communication system according to Claim 38, wherein said incoming callobject call presentation service provides a user of said first terminal with dynamic interaction with said incoming callobject originating service when said second terminal initiates said communication to said first terminal.
40. A communication system according to Claim 38, wherein said parameters of said communication from said second terminal sent from said incoming callobject originating service include caller identification, short message text, voice message data, video message data and bandwidth specifications of said call.
41. A communication system according to Claim 38, wherein said incoming callobject originating service and said incoming callobject call presentation service are registered together in said incoming callobject in said location directory service.
42. A communication system according to Claim 41 , wherein said incoming callobject call presentation service is transmitted to said first terminal after said second terminal fetches said incoming callobject of said first terminal from said location directory service.
43. A communication system according to Claim 38, wherein said incoming callobject call originating service is registered in said location directory service and said incoming callobject call presentation service is created and maintained at said first terminal.
44. A communication system according to Claim 35, wherein said second terminal has an outgoing callobject which includes call initiating capabilities of said second terminal.
45. A communication system according to Claim 45, wherein said call initiating capabilities of said second terminal include speed dialing, voice message data transmission, text data transmission, video data transmission, call monitoring, bandwidth specifications of the call and security checking.
46. A communication system according to Claim 44, wherein said incoming callobject of said first terminal is fetched from said location directory service by said second terminal in response to a query from said second terminal.
47. A communication system according to Claim 44, wherein said second terminal initiates said call to said first terminal by checking said outgoing callobject to determine if said communication complies with the call initiating capabilities of said second terminal, sending said communication from said outgoing callobject of said second terminal to the incoming callobject originating service of said first terminal if said communication is determined to comply with the call initiating capabilities of said second terminal, and sending said communication from said incoming callobject originating service of said first terminal to the user of said first terminal.
48. A communication system according to Claim 47, wherein said incoming callobject call presentation service identifies the parameters of said communication sent from said incoming callobject originating service at said first terminal.
49. A communication system according to Claim 48, wherein said communication sent from said incoming callobject originating service of said first terminal is received by an incoming callobject call presentation service of said first terminal thus allowing the user of said first terminal to dynamically interact with said originating service callobject in response to said communication.
50. A communication system according to Claim 34, wherein if said communication from said second terminal is accepted by a user of said first terminal, communication is established over a data packet network.
51. A communication system according to Claim 50, wherein said data packet network includes the Internet.
52. A communication system according to Claim 51 , wherein said data packet network utilizes an H323 protocol standard.
53. A communication system according to Claim 49, wherein if said communication from said second terminal is accepted by a user of said first terminal, communication is established over a data packet network.
54. A communication system according to Claim 53, wherein said data packet network includes the Internet.
55. A communication system according to Claim 54, wherein said data packet network utilizes an H323 protocol standard.
56. A communication system according to Claim 54, wherein said data packet network supports object transfer protocol.
57. A communication system according to Claim 34, wherein said incoming callobject of said first terminal is registered with said location directory service by a user of said first terminal.
58. A communication system according to Claim 34, wherein said incoming callobject of said first terminal is registered with said location directory service by an intermediary.
59. A communication system according to Claim 34, wherein said intermediary is a gatekeeper.
60. A communication system according to Claim 34, wherein said second terminal fetches said incoming callobject of said first terminal directly to said second terminal,
61. A communication system according to Claim 34, wherein said second terminal fetches said incoming callobject of said first terminal to a local server corresponding to said second terminal.
62. A communication system according to Claim 34, wherein said location directory service is a local network directory.
63. A communication system according to Claim 34, wherein said location directory service is a universal directory.
64. A communication system according to Claim 34, wherein said incoming callobject of said first terminal is registered with said location directory service in accordance with a logical address of said first terminal.
65. A communication system according to Claim 34, wherein said incoming callobject is dynamic.
66. A communication system according to Claim 44, wherein said outgoing callobject is dynamic.
PCT/IB2000/001123 1999-08-17 2000-08-14 Establishing communication in a packet data network WO2001013594A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU65861/00A AU6586100A (en) 1999-08-17 2000-08-14 Establishing communication in a packet data network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US37580699A 1999-08-17 1999-08-17
US09/375,806 1999-08-17

Publications (1)

Publication Number Publication Date
WO2001013594A1 true WO2001013594A1 (en) 2001-02-22

Family

ID=23482431

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2000/001123 WO2001013594A1 (en) 1999-08-17 2000-08-14 Establishing communication in a packet data network

Country Status (3)

Country Link
US (1) US20040042414A1 (en)
AU (1) AU6586100A (en)
WO (1) WO2001013594A1 (en)

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002208967A (en) * 2001-01-10 2002-07-26 Matsushita Electric Ind Co Ltd Concentrator
US20070294336A1 (en) * 2004-07-02 2007-12-20 Greg Pounds Proxy-based communications architecture
US7451921B2 (en) * 2004-09-01 2008-11-18 Eric Morgan Dowling Methods, smart cards, and systems for providing portable computer, VoIP, and application services
US8576270B1 (en) 2004-10-08 2013-11-05 Glowpoint, Inc. Intelligent call management and redirection
US7916716B1 (en) * 2004-11-03 2011-03-29 Sprint Communications Company L.P. System and method for providing local services within a consolidated network architecture
EP1864455A2 (en) * 2005-03-29 2007-12-12 Glowpoint, Inc. Video communication call authorization
US7813483B2 (en) * 2005-04-28 2010-10-12 Cisco Technology, Inc. System and method for providing presence information to voicemail users
US20070002777A1 (en) * 2005-05-31 2007-01-04 Glowpoint, Inc. Video-communication interface
EP1938202A2 (en) * 2005-08-25 2008-07-02 ERIKSSON, Andreas Systems and methods of implementing a single-number follow me service for videoconferencing
GB2433180B (en) * 2005-12-09 2008-01-30 Oracle Int Corp Communications method
US9635172B2 (en) * 2006-04-13 2017-04-25 Tp Lab Inc. Selective voice communication among multiple services
US8930464B1 (en) * 2007-03-30 2015-01-06 Emc Corporation Email content pre-caching to a local archive store
GB0905270D0 (en) * 2009-03-27 2009-05-13 British Telecomm Call barring
US20110302408A1 (en) * 2010-06-03 2011-12-08 Morrigan Partners Limited Secure Communication Systems, Methods, and Devices

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998041032A2 (en) * 1997-03-14 1998-09-17 Efusion, Inc. Method and apparatus for establishing a voice call to a pstn extension for a networked client computer
EP0905959A2 (en) * 1997-08-01 1999-03-31 Comverse Network Systems, Inc. A packet-switched-network telephone system

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5109519A (en) * 1989-03-28 1992-04-28 Wang Laboratories, Inc. Local computer participating in mail delivery system abstracts from directory of all eligible mail recipients only served by local computer
GB2249923B (en) * 1990-09-10 1995-03-08 Oki America Inc Remotely programmable radiotelephone
GB2295751A (en) * 1994-11-30 1996-06-05 Ibm Data communication system using directory service providing routing information
US5806000A (en) * 1995-10-12 1998-09-08 Telefonaktiebolaget Lm Ericsson (Publ) System and method for implementing short message service extension phones within a radio telecommunications network
US5802510A (en) * 1995-12-29 1998-09-01 At&T Corp Universal directory service
US5978681A (en) * 1996-06-07 1999-11-02 Telefonaktiebolaget L M Ericsson Method and apparatus for providing calling service features within incompletely upgraded cellular telephone networks
US7145898B1 (en) * 1996-11-18 2006-12-05 Mci Communications Corporation System, method and article of manufacture for selecting a gateway of a hybrid communication system architecture
US6292481B1 (en) * 1997-09-16 2001-09-18 Bell Atlantic Network Services, Inc. Inter-carrier signaling and usage accounting architecture for internet telephony
US6157636A (en) * 1997-03-06 2000-12-05 Bell Atlantic Network Services, Inc. Network session management with gateway-directory services and authorization control
US6289010B1 (en) * 1997-03-11 2001-09-11 Bell Atlantic Network Services, Inc. Inbound gateway authorization processing for inter-carrier internet telephony
US6198738B1 (en) * 1997-04-16 2001-03-06 Lucent Technologies Inc. Communications between the public switched telephone network and packetized data networks
US6185288B1 (en) * 1997-12-18 2001-02-06 Nortel Networks Limited Multimedia call signalling system and method
JP3641128B2 (en) * 1998-02-20 2005-04-20 株式会社東芝 MOBILE COMPUTER DEVICE, MOBILE COMPUTER MANAGEMENT DEVICE, MOBILE COMPUTER MANAGEMENT METHOD, AND COMMUNICATION CONTROL METHOD
US6343116B1 (en) * 1998-09-21 2002-01-29 Microsoft Corporation Computer telephony application programming interface
US6321250B1 (en) * 1998-10-01 2001-11-20 Ericsson Inc. Data communication system and method for transporting objects over a permanent connections
US7003463B1 (en) * 1998-10-02 2006-02-21 International Business Machines Corporation System and method for providing network coordinated conversational services

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998041032A2 (en) * 1997-03-14 1998-09-17 Efusion, Inc. Method and apparatus for establishing a voice call to a pstn extension for a networked client computer
EP0905959A2 (en) * 1997-08-01 1999-03-31 Comverse Network Systems, Inc. A packet-switched-network telephone system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CATCHPOLE A: "VOICE-DATA CONVERGENCE AND THE CORPORATE VOICE-OVER-IP TRIAL", BRITISH TELECOMMUNICATIONS ENGINEERING,GB,BRITISH TELECOMMUNICATIONS ENGINEERING. LONDON, vol. 17, no. 4, January 1999 (1999-01-01), pages 218 - 224, XP000801951, ISSN: 0262-401X *

Also Published As

Publication number Publication date
US20040042414A1 (en) 2004-03-04
AU6586100A (en) 2001-03-13

Similar Documents

Publication Publication Date Title
US8009592B2 (en) Method and apparatus for exchange of information in a communication system
US8660242B2 (en) System and method for electronic message notification
US6904140B2 (en) Dynamic user state dependent processing
JP3357591B2 (en) Communication device and communication path selection method
EP1797704B1 (en) A method and apparatus for multimedia communication
US9781257B2 (en) Technique for obtaining caller-originated alert signals in IP-based communication sessions
US6735288B1 (en) Voice over IP voice mail system configured for placing an outgoing call and returning subscriber to mailbox after call completion
US20070127645A1 (en) Technique for providing secondary information to a user equipment
US20080062893A1 (en) Method and apparatus for event-based exchange of information between communication devices conditioned on personal calendar information
US8400946B2 (en) System and method for sharing common location-related information between communication devices
US20070226240A1 (en) Technique for providing data objects prior to call establishment
US20070124481A1 (en) System and method for sharing event-triggered, location-related information between communication devices
US20070237320A1 (en) Technique for providing caller-originated alert signalsin circuit-switched communications
WO2001013594A1 (en) Establishing communication in a packet data network
EP2116033B1 (en) Method and apparatus for event-based synchronization of information between communication devices
EP1292091B1 (en) Method for transmitting short messages using internet phones and system therefor
US7366183B1 (en) Detecting multimedia capability of a caller
US20030185203A1 (en) Integrated high bandwidth communications system
US20080112390A1 (en) Apparatus to override the redirect or reject feature at an SIP end point
US6363430B1 (en) Methods and systems for providing an absent addressing service to customers in a communications network
WO2005125029A2 (en) System and method for electronic message notification
KR100797739B1 (en) Apparatus of integrated voice service on Java API
JP3976712B2 (en) Source terminal identification information notification system, incoming call device, server device, outgoing call device, registration device, terminal device, and gateway device
JP4560530B2 (en) Notification system, information processing apparatus, notification system notification method, information processing method, information processing program, and recording medium
JP2005094224A (en) Caller terminal identification information notifying system, call termination apparatus, call origination apparatus, server apparatus, registration apparatus, terminal, and gateway apparatus

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 CR CU CZ DE DK DM DZ 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 PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA 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 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 BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP