|Publication number||US7185087 B2|
|Application number||US 10/226,274|
|Publication date||Feb 27, 2007|
|Filing date||Aug 23, 2002|
|Priority date||Oct 26, 2001|
|Also published as||DE60205501D1, DE60205501T2, EP1442583A1, EP1442583B1, US20030084147, WO2003036915A1|
|Publication number||10226274, 226274, US 7185087 B2, US 7185087B2, US-B2-7185087, US7185087 B2, US7185087B2|
|Original Assignee||Telefonaktiebolaget Lm Ericsson (Publ)|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (10), Non-Patent Citations (7), Referenced by (7), Classifications (29), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This non-provisional patent application claims priority based upon the prior U.S. provisional patent applications entitled “Evolutions to OSA/Parlay Interfaces to Support the Virtual Home Environment (VHE) Business Model and User Profiles”, application Ser. No. 60/330,660, filed Oct. 26, 2001, in the name of Christophe Gourraud.
1. Field of the Invention
The present invention relates to maintaining service subscription information of third party services provided in a telecommunications networks.
2. Description of the Related Art
Current cellular telecommunications networks are mostly aimed at providing basic telephony services to subscribers. Additional services are provided by network owners or operators. In the coming years, new players will provide a wider range of value-added services to subscribers. In order to do so, these new players need to gain access to networks' infrastructure and capabilities. However, it must be done in a traceable way that will not compromise network security and integrity. Therefore, the development of standardized interfaces to the network has become a necessity.
For a few years now, 3GPP, in conjunction with other standardization bodies, has developed an Open Service Access (OSA) specification also referred to as Parlay/OSA. Its main objective is to provide Application Program Interfaces (APIs) for service development and deployment in telecommunications networks. On the business side, OSA is closer to third party service suppliers than network operators. In that sense, the focus of the group is on getting a wide range of network-oriented APIs. The APIs are built toward giving third party service suppliers access to the operator's network equipment functionalities.
At the present moment, user subscription information to a third party service is maintained by the third party service supplier. However, the third party services are mostly based on events occurring in the operator's network. Therefore, the third party-service supplier must ask the network operator to add triggers on corresponding events for each of its subscribed user. This registration process to third party services causes several problems. One of these problems is the number of different triggers that has to be maintained with consistency by the third party service supplier. Indeed, each modification in registration of any third party service results in modifications to a network operator's trigger database. Another problem arises because the registration of each trigger is performed by the third party service supplier into the operator's network. In fact, the network operator has no way of authenticating that the user allows the third party service supplier to receive the notification corresponding to each trigger. Yet another problem comes from the fact that the operator needs to open access to its network databases to third party service supplier. In some cases, it might be difficult to maintain consistent data in the network databases when new entries and or modifications to existing ones are made without the operator's control.
As it can be appreciated, there is a need for better service subscription information maintenance while providing third party services. The present invention provides such a solution.
The present invention is directed to an apparatus for managing registration of users of a network to a third party service. In that context, the apparatus is capable of receiving a registration request including a third party service reference from the user and generating a registration record having the third party service reference and a reference to the user from which the registration request has been received. The apparatus is also capable of receiving a trigger request from a Service Capability Server (SCS) and generating a trigger record. Both the trigger request and the trigger record comprises a reference to at least one event and the third party service reference.
The present invention is also directed to a Service Capability Server (SCS) for controlling interactions between a network and a third party service. The SCS comprises capabilities for receiving a trigger request for at least one event from the third party service. The trigger request comprises a reference to the at least one event and a third party service reference. The SCS is also capable of communicating with an apparatus in the network to add a trigger in a trigger table of the apparatus and capable of receiving a notification from the trigger table of an occurrence of the at least one event. The notification comprises the third party service reference, the reference to the at least one event and a reference to at least one user registered to the third party service within the network. The SCS is further capable of informing the third party service of the received notification of the occurrence of the at least one event.
Another aspect of the present invention is directed to a method for delivering a notification of an event to a third party service from a network, the network and the third party service interacting with each other through a Service Capability Server (SCS). The method comprises steps of detecting the event in the network, associating the event with a User_ID and s Service_ID and sending a notification to the SCS. The notification request comprises the Service_ID, the User_ID and a reference to the event. The method also comprises the step of informing the third party service of the received notification of the occurrence of the event. In the context, the User_ID is a reference to one of the users registered to the third party service and the Service_ID is a reference to the third party service.
Yet another aspect of the present invention is directed to a method for adding a trigger for an event in a network by a third party service, the network and the third party service interacting with each other through a Service Capability Server (SCS). The method comprises steps of sending a trigger request from the third party service to the SCS and informing the network of the received trigger request for the occurrence of the event. The trigger request comprises a reference to the vent and a reference to the third party service.
A more complete understanding of the present invention may be had by reference to the following Detailed Description when taken in conjunction with the accompanying drawings wherein:
The present invention relates to maintaining service subscription information of third party services provided to users in a network. At the present moment, the third party services maintain service subscription information outside the network. While it gives the third party services complete control on their registrations, it causes problems as stated previously. The invention uses a Service Capability Server (SCS) for controlling interactions between the third party services and the network. An apparatus in the network is also provided for maintaining a list of users registered to each of the third party services. The list of users may be referred to as the service subscription information. The apparatus also maintains a list of triggers on events of the network for which one of the third party services should be provided to one of the users of the network. The SCS is used by the apparatus to send event notifications to the third party services and by the third party services to send trigger request to the apparatus as explained in the following discussion.
Reference is now made to the Drawings where
In a first aspect of the present invention, the third party service 110 adds new triggers to the list of triggers of the apparatus 130. In order to do so, the third party service 110 sends a trigger request 150 to the SCS 120. The trigger request 150 contains a reference to the third party service and a reference to an event for which the third party service 110 needs to be notified. It should be noted that the reference to the third party service 110 can be an Internet Protocol (IP) address or any other identifier (Service_ID) understood by both the network 105 and the third party service 110. The event in the trigger request 150 is not linked to any of the users 140 since the third party service 110 is not aware of the registration of the user 140 thereto. The reference to the event can be an identifier (Event_ID) understood by both the network 105 and the third party service 110 such as a number of a text string. Furthermore, the trigger request may contain multiple references to multiple events. It is also important to note that the trigger request does not need to contain reference to users of the network 105.
Upon reception of the trigger request 150, the SCS 120 communicates with the apparatus 130 through a trigger request 152 to add a corresponding trigger to the list of triggers (step 154). In most implementations, the list of triggers is maintained in a trigger table and the list of users 140 is maintained in a registration table. Both tables are usually located in a database inside the apparatus 130. The step 154 of adding the trigger is normally performed by generating a trigger record containing the reference to the third party service 110 and the reference to the event. The trigger record is then added to the trigger table.
Another way of adding triggers into the list of triggers is to analyze an existing Service Level Agreement (SLA) between the third party service 110 and the network 105. For example, the SLA could specify that the third party service 110 is to be notified by default for a given list of events. The list of events would then be added to the list of triggers for the corresponding third party service 110.
In another aspect of the present invention, the user 140 registers to the third party service 110 (step 160) through the apparatus 130. The registration is done by sending a registration request 162 to the apparatus 130. The registration request 162 contains a reference to the third party service 110 and a reference to the user 140. The reference to the user 140 is an identifier (User_ID) provided by the network 105 to the user 140. Upon reception of the registration request 162, the apparatus 130 adds the user 140 (step 164) to the list of users. The step 164 of adding the user 140 is normally performed by generating a registration record containing the reference to the third party service 110 and the reference to the user 140 and adding the registration record to the registration table. It should be noted that the order in which the registration of the user 140 to the third party service 110 and the addition of the trigger in the apparatus 130 by the third party service 110 can be interchanged without impacting the teachings of the present invention.
When an event is detected in the network 105 (step 170), the apparatus 130 checks if one of the triggers in the list of triggers corresponds to the detected event. If so, an event notification 172 is sent toward the third party service 110 through the SCS 120. The event notification 172 contains a reference to the detected event, a reference to the third party service 110 and a reference to the user 140 registered to the third party service 110. When the SCS 120 receives the event notification, it informs the third party service 110 of the received event notification with an event notification 174. The third party service 110 can then be provided to the user 140 (step 180).
Reference is now made to
Reference is now made to
Reference is now made to
The innovative teachings of the present invention have been described with particular reference to numerous exemplary embodiments. However, it should be understood that this class of embodiments provides only a few examples of the many advantageous uses of the innovative teachings of the invention. In general, statements made in the specification of the present application do not necessarily limit any of the various claimed aspects of the present invention. Moreover, some statements may apply to some inventive features but not to others. In the drawings, like or similar elements are designated with identical reference numerals throughout the several views, and the various elements depicted are not necessarily drawn to scale.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5621892 *||Oct 10, 1995||Apr 15, 1997||Intel Corporation||Method and apparatus for managing alerts and events in a networked computer system|
|US6122510 *||Nov 4, 1997||Sep 19, 2000||Telefonaktiebolaget Lm Ericsson||Method and apparatus for providing network-specific mobile services|
|US6128503 *||Dec 8, 1997||Oct 3, 2000||Telefonaktiebolaget Lm Ericsson||Method and apparatus for coordinating mobile communications network services with intelligent network services|
|US6275957 *||Oct 20, 1998||Aug 14, 2001||Microsoft Corporation||Using query language for provider and subscriber registrations|
|US6460081 *||May 19, 1999||Oct 1, 2002||Qwest Communications International Inc.||System and method for controlling data access|
|US6628951 *||Jun 20, 2000||Sep 30, 2003||Sonera Oyj||Procedure and system for the transmission of information and establishment of a telecommunication connection|
|US6636588 *||Dec 28, 1999||Oct 21, 2003||Fujitsu Limited||Intelligent network system|
|US6771971 *||Jan 18, 2001||Aug 3, 2004||Sws Development, L.L.C.||Subscriber information service center (SISC)|
|US6829639 *||Nov 15, 1999||Dec 7, 2004||Netvision, Inc.||Method and system for intelligent global event notification and control within a distributed computing environment|
|US6910070 *||Jan 24, 2000||Jun 21, 2005||Oracle International Corporation||Methods and systems for asynchronous notification of database events|
|1||Initial Draft 3GPP TR23.955, 3<SUP>rd </SUP>Generation Partnership Project, Technical Specification Group Services and Systems Aspects, Virtual Home Environment (VHE) Concepts, Release 5/4, 3GPP TSG-SA2, Los Angeles, Jan. 22-26, 2001.|
|2||J.C-K Lee et al., Service Subscription Information Management in a TINA Environment Using Object-Oriented Middleware, 2001 IEEE, XP-10538408.|
|3||M.J. Yates et al., The Parlay Network API Specification, BT Technol J vol. 18 No. 2, Apr. 2000, XP-958413.|
|4||Menelaos K. Perdikeas et al., Parlay-Based Service Engineering in a Converged Internet-PSTN Environment, Computer Networks 35, 2001, XP- 4304867.|
|5||Michel L.F. Grech et al., Delivering Seamless Services in Open Networks Using Intelligent Service Mediation, Bell Labs Technical Journal, Jul.-Sep. 2000, XP-000975491.|
|6||PCT Search Report of Mar. 24, 2003, received in corresponding PCT application PCT/CA02/01595.|
|7||Sami Uskela, Virtual Home Environment (VHE), S-38.128 Telecommunications Technology, special assignment (4 cr.), May 6, 1999.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7499995 *||Jun 28, 2005||Mar 3, 2009||International Business Machines Corporation||Managing permission for accessing third party applications on a telecommunications network|
|US8745182 *||Aug 10, 2005||Jun 3, 2014||Optis Wireless Technology, Llc||Provision of public service identities|
|US9129028 *||Oct 31, 2014||Sep 8, 2015||Splunk, Inc.||Event field distributed search display|
|US20060293034 *||Jun 28, 2005||Dec 28, 2006||International Business Machines Corporation||Managing permission for accessing third party applications on a telecommunications network|
|US20090227236 *||Aug 10, 2005||Sep 10, 2009||Telefonaktiebolaget Lm Ericsson (Publ)||Provision of public service identities|
|US20130340007 *||Jun 12, 2013||Dec 19, 2013||Sony Corporation||Extensions to trigger parameters table for interactive television|
|US20150058375 *||Oct 31, 2014||Feb 26, 2015||Splunk Inc.||Event field distributed search display|
|U.S. Classification||709/224, 709/220, 709/223, 719/318, 707/999.001, 707/999.002|
|International Classification||G06F7/00, H04L29/08, H04L12/24, G06F15/173, G06F15/177, G06F9/44|
|Cooperative Classification||Y10S707/99931, Y10S707/99932, H04L41/5003, H04L41/5054, H04L67/2842, H04L67/20, H04L67/2819, H04L67/26, H04L67/28, H04L41/5032, H04L69/329|
|European Classification||H04L41/50D, H04L41/50G4, H04L29/08N19, H04L29/08N25, H04L29/08N27, H04L29/08A7|
|Aug 23, 2002||AS||Assignment|
Owner name: TELEFONAKTIEBOLAGET L M ERICSSON (PUBL), SWEDEN
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GOURRAUD, CHRISTOPHE;REEL/FRAME:013228/0714
Effective date: 20020822
|Aug 27, 2010||FPAY||Fee payment|
Year of fee payment: 4
|Aug 27, 2014||FPAY||Fee payment|
Year of fee payment: 8