Service node for providing telecommunication services

• US 6,831,915 B1
• Filed: 02/17/2000
• Issued: 12/14/2004
• Est. Priority Date: 02/20/1997
• Status: Expired due to Term

• Current Assignee: Comcast IP Holdings I LLC (Comcast Corporation)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Beyschlag, Ulf, Raguideau, Nicolas
• Primary Examiner(s): Nguyen, Chau
• Assistant Examiner(s): HYUN, SOON D
• Application Number:
  US09/367,804
• Time in Patent Office: 1,762 Days
• Field of Search: 370/352, 370/353, 370/355, 370/356, 370/522, 370/410, 370/360, 370/363, 370/368, 370/371, 370/524, 717/168-178
• US Class Current: 370/352
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1096 Supplementary features, e.g. call forwarding or call holding systems providing special services or facilities to telephony subscribers H04M3/42
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/401 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
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 2207/12 intelligent networks
• CPC Class Codes: H04M 3/42136 Administration or customisation of services
• CPC Class Codes: H04M 3/42153 by subscriber
• CPC Class Codes: H04M 3/42161 via computer interface
• CPC Class Codes: H04M 3/42229 Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location diverting calls from one subscriber to another subscriber, i.e. two different subscriptions H04M3/54; selecting arrangements in intelligent networks H04Q3/005
• CPC Class Codes: H04M 3/493 Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
• CPC Class Codes: H04M 7/12 for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
• CPC Class Codes: H04M 7/121 Details of network access arrangements or protocols
• CPC Class Codes: H04M 7/1235 where one of the core networks is a wireless network
• CPC Class Codes: H04M 7/126 Interworking of session control protocols
• CPC Class Codes: H04Q 11/0457 Connection protocols
• CPC Class Codes: H04Q 2213/13097 Numbering, addressing
• CPC Class Codes: H04Q 2213/13098 : Mobile subscriber
• CPC Class Codes: H04Q 2213/13103 : Memory
• CPC Class Codes: H04Q 2213/13175 : Graphical user interface [GUI], WWW interface, visual indication
• CPC Class Codes: H04Q 2213/13176 : Common channel signaling, CCS7
• CPC Class Codes: H04Q 2213/13196 : Connection circuit/link/trunk/junction, bridge, router, gateway
• CPC Class Codes: H04Q 2213/13204 : Protocols
• CPC Class Codes: H04Q 2213/13209 : ISDN
• CPC Class Codes: H04Q 2213/1322 : PBX
• CPC Class Codes: H04Q 2213/13298 : Local loop systems, access network
• CPC Class Codes: H04Q 2213/13345 : Intelligent networks, SCP
• CPC Class Codes: H04Q 2213/13383 : Hierarchy of switches, main and subexchange, e.g. satellite exchange
• CPC Class Codes: H04Q 2213/13389 : LAN, internet
• CPC Class Codes: H04W 4/06 : Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
• CPC Class Codes: H04W 76/10 : Connection setup
• CPC Class Codes: H04W 8/20 : Transfer of user or subscriber data

Abstract

A telephone network is provided with a service node SN (50) having an interface to the Internet. The SN (50) has a voice service browser (51) which it can use to access resources on the Internet, these resources preferably being held on WWW servers (52). A user of the telephone network places his own service logic programs, in the form of applets 55, on his WWW home page (53) together with content items such announcements and messages; these content items may be embedded in the applets (55) or held in separate files. When the SN (50) receives a service request to supply a service to a user identified as having his own service logic programs and content items available on the WWW, the voice service browser (51) reaches out over the WWW to retrieve the relevant service applet (55) and any associated content items. The voice service browser (51) then executes the applet (55) to provide the desired service including the delivery of content items through a text-to-voice converter or the like.

Claims

1. A service node for providing services in a telecommunications system that includes a bearer network for transmitting content between users, said service node comprising:

receiving means for receiving and temporarily storing service logic programs and associated, but separate, content that are normally held remote from the service node;

first control means responsive to an indication that a particular service associated with a particular user at least may soon be requested, to cause said receiving means to receive and store a particular service logic program corresponding to said particular service;

execution means for executing the service logic programs;

second control means responsive to a service request for said particular service, to cause the corresponding said particular logic program, received and stored by said receiving means, to be executed by said execution means;

third control means responsive to said particular service logic program when executing on said execution means to cause the receiving means to receive and store said content associated with said particular service logic program; and

bearer-network transmit means operable under control of said particular service logic program executing on said execution means, to deliver to said bearer network said content received by said receiving means which is associated with said particular service logic program.

2. A service node according to claim 1, wherein said receiving means at an instigation of said particular service logic program executing on said execution means, is operative to receive and temporarily store a follow-up service logic program associated with an executing program, said follow-up program being subsequently executed by the execution means in providing the requested service.

3. A service node according to claim 1, wherein said execution means can concurrently execute multiple particular service logic programs with interaction therebetween.

4. A service node according to claim 1, further comprising:

standard-program storage means for long-term storage of standard service logic programs usable in the provision of services to multiple users,

standard-content storage means for long-term storage of standard content usable in the provision of services to multiple users,

said second control means on receiving said service request being operative to cause the execution of said standard service logic program which initiates the delivery of said standard content through an interface of said bearer network, the second control means thereafter initiating the execution of the said particular service logic program.

5. A service node according to claim 4, wherein said indication to which the said first control means is responsive is said service request, said second control means serving to execute the said particular service logic program corresponding to said service request upon that program being received and stored by said receiving means.

6. A service node according to claim 1, wherein said indication to which the said first control means is responsive is said service request, said second control means serving to execute the said particular service logic program corresponding to said service request upon that program being received and stored by said receiving means.

7. A service node according to claim 1, wherein said indication to which the said first control means is responsive is a user-identifying indicator received at said service node and which, without being a service request for said particular service, indicates that said user is in a coverage area of said service node.

8. A service node according to claim 1, including a computer network interface for connection to a computer network that is generally accessible to the users of the telecommunications system but is logically distinct from the latter, the receiving means being operative to receive said service logic programs and content through said computer network interface.

9. A service node according to claim 8, wherein said telecommunications system is a public telephone system and said computer network is the Internet.

10. A service node according to claim 8, wherein said telecommunications system is a private telephone system including a PABX, and wherein said computer network is an intranet.

11. A service node according to claim 8, wherein said receiving means and execution means provide a WWW browser environment enabling service logic programs and content held on remote HTTP servers to be fetched over said computer network according to URIs derived from at least a first of:

said indications;

said service requests;

executing said service logic programs.

12. A method of providing services in a telecommunications system that includes a bearer network, and a node providing a service execution environment for running service logic programs in response to corresponding service requests received thereat, said node having means for receiving remotely-held service logic programs;

said method comprising the steps of;

(a) determining from indications within said telecommunications system that particular said remotely-held service logic programs may soon be required for execution by said node,

(b) in response to step (a) determining that a said particular remotely-held service logic program may soon be required for execution by said node, transferring that service logic program to said node for temporary storage thereat,

(c) thereafter executing at said node the particular service logic program transferred in step (b), in the event that a service request invoking that program is received by that node;

the service logic program transferred in step (b) having associated content intended for delivery to a user of the telecommunications system over said bearer network, this content being held remotely with the associated service logic program but separately therefrom and being retrieved to said node at the instigation of the associated service logic program and delivered by said node to the bearer network upon execution of the service logic program in step (c).

13. A method according to claim 12, wherein step (a) determines that a particular service logic program may soon be required when a potential user of that service is detected as being within a coverage zone of the telecommunications system.

14. A method according to claim 12, including the further step of:

(d) retrieving at an instigation of the service logic program executing in step (c), a remotely-held follow-up service logic program associated with the executing program, said follow-up program being temporarily stored at said node and subsequently executed by the node in providing the requested service.

15. A method according to claim 12, wherein said telecommunications system is a public telephone system and said remotely-held service logic programs are held on servers located on a computer network to which said node has access.

16. A method according to claim 15 wherein said computer network is the Internet.

17. A method of providing services in a telecommunications system that includes a bearer network, and a node providing a service execution environment for running service logic programs in response to corresponding service requests received thereat, said node having means for receiving remotely-held service logic programs;

said method comprising the steps of;

(a) receiving a service request at said node,

(b) initially responding to the service request received in step (a) by executing a standard service logic program held at that node, execution of said standard service logic program comprising a delivery of standard content, also held at said node, through said bearer network to a user of said telecommunications system identified in the service request,

(c) simultaneously with at least step (b), retrieving to said node a service logic program specific to said service request from a location remote from said node,

(d) executing the service logic program retrieved in step (c) at said node in coordination with a combination of the initial response provided by said standard service logic program in step (b) to said service request.

18. A method according to claim 17, wherein the service logic program retrieved in step (c) includes content intended for delivery to a user of the telecommunications system over said bearer network, step (d) involving delivery of the content by said node over said bearer network.

19. A method according to claim 17, wherein the service logic program retrieved in step (c) has associated content intended for delivery to a user of the telecommunications system over said bearer network, this content being held remotely with but separately from the associated service logic program but separately therefrom and being retrieved to said node at an instigation of the associated service logic program and delivered by said node to the bearer network under control of said associated service logic program in step (d).

20. A method according to claim 19, wherein the service logic program retrieved in step (c) causes its associated content to be fetched only when required for delivery over the bearer network.

21. A method according to claim 19, wherein the service logic program retrieved in step (c) causes its associated content to be fetched in anticipation of delivery of that content over the bearer network.

22. A method according to claim 17, including the further step of:

(e) retrieving at an instigation of the service logic program executing in step (d), a remotely-held follow-up service logic program associated with the executing program, said follow-up program being temporarily stored at said node and subsequently executed by the node in providing the requested service.

23. A method according to claim 17, wherein said remotely-held service logic program retrieved to said node in step (c) is retrieved by the node in response to receipt thereat of said service request.

24. A method according to claim 17, wherein said service request is passed to said node by a service control point of the telecommunication system, the retrieval of said remotely-held service logic program in step (c) being instigated by said service control point.

25. A method according to claim 24, wherein said remotely-held service logic program is initially retrieved to said service control point and is then passed from there to said node.

26. A method according to claim 17, wherein said telecommunications system is a public telephone system and said remotely-held service logic programs are held on servers located on a computer network to which said node has access.

27. A method according to claim 26 wherein said computer network is the Internet.

28. A method of providing services in a telecommunications system that includes a bearer network and a node providing a service execution environment for running service logic programs in response to corresponding service requests received thereat;

said method comprising the steps of;

(a) determining that a particular remotely-held service logic program may soon be required for execution by said node, this determination being effected as a consequence of a potential user of a service provided by said particular service logic program being detected, otherwise than through a request for said service, as being within a coverage zone of the telecommunications system,

(b) in response to said determination being made, transferring the said particular service logic program to said node for temporary storage thereat,

(c) thereafter executing at said node the said particular service logic program transferred in step (b), in the event that a service request invoking that program is received by that node.

29. A method according to claim 28, wherein the said particular service logic program transferred in step (b) includes content intended for delivery to a user of the telecommunications system over said bearer network, execution of said service logic program in step (c) involving delivery of the content by said node over said bearer network.

30. A method according to claim 28, wherein the said particular service logic program transferred in step (b) has associated content intended for delivery to a user of the telecommunications system over said bearer network, this content being held remotely with but separately from the associated service logic program but separately therefrom and being retrieved to said node at an instigation of the associated service logic program and delivered by said node to the bearer network upon execution of the service logic program in step (c).

31. A method according to claim 28, including the further step of:

(d) retrieving at an instigation of the service logic program executing in step (c), a remotely-held follow-up service logic program associated with an executing program, said follow-up program being temporarily stored at said node and subsequently executed by the node in providing the requested service.

32. A service node for providing services in a telecommunications system that includes a bearer network for transmitting content between users, said service node comprising:

receiving means for receiving and temporarily storing service logic programs and associated content that are normally held remote from the service node;

first control means responsive to an indication that a particular service associated with a particular user at least may soon be requested, to cause said receiving means to receive and store a particular service logic program corresponding to said particular service;

execution means for executing the service logic programs;

second control means responsive to a service request for said particular service, to cause the corresponding said particular logic program, received and stored by said receiving means, to be executed by said execution means;

bearer-network transmit means operable under control of said particular service logic program executing on said execution means, to deliver to said bearer network said content received by said receiving means which is associated with said particular service logic program; and

a computer network interface for connection to a computer network that is generally accessible to the users of the telecommunications system but is logically distinct from the latter, the receiving means being operative to receive said service logic programs and content through said computer network interface,

said receiving means and execution means providing a WWW browser environment enabling service logic programs and content held on remote HTTP servers to be fetched over said computer network according to URIs derived from at least a first of;

said indications;

said service requests;

executing said service logic programs.