EP1604504A1 - Multi-supplier, multi-domain mediating element for event notification - Google Patents
Multi-supplier, multi-domain mediating element for event notificationInfo
- Publication number
- EP1604504A1 EP1604504A1 EP04714822A EP04714822A EP1604504A1 EP 1604504 A1 EP1604504 A1 EP 1604504A1 EP 04714822 A EP04714822 A EP 04714822A EP 04714822 A EP04714822 A EP 04714822A EP 1604504 A1 EP1604504 A1 EP 1604504A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- recovery
- data
- service providers
- user
- service provider
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/306—User profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Definitions
- the invention relates to the field of telecommunications. More specifically, the invention makes it possible to facilitate access to the multiple dynamic data (linked to a usage session) relating to all types of service users, data which may be required to be stored by service providers and which may be brought to consult with other service providers.
- service provider we mean both network service providers also called resource providers and application service providers.
- Application service providers are so called by the fact that these elements, physical or functional, implement a data processing which they receive to provide data processed expressly for an end user.
- Resource providers (or network service providers) have a support and assistance function for the transmission and transport of data in the network.
- the invention is related to a type of supplier which is interposed between the usual suppliers: these are mediation service providers, or generic service providers, which offer their services to other service providers.
- Each service provider manages information about its own customers. Certain information or data are said to be “static” and their value is fixed when subscribing or when modifying the service, others are said to be “dynamic” and only have value or even exist during a session for using the service (eg an address for 'access to the network). Among these, certain information is even more dynamic and can change during the same session (eg the location of a user). However, some applications require to take into account information which sometimes comes from different services offered by any service providers and multiple sometimes different from that providing said application. We could cite the provision of global location information for users (potentially across all access networks of all operators) or the provision of user presence information (over potentially all access networks).
- the invention relates to a concern to allow a generic service provider (or mediation service) to easily and efficiently retrieve dynamic information available to service providers and to notify the corresponding events to other service providers.
- a generic service provider or mediation service
- who would subscribe to such a multi-domain multi-supplier mediation service who would subscribe to such a multi-domain multi-supplier mediation service.
- the implementation of this system brings additional added value to the mediation service provider.
- the requesting application and the services having the information are offered by the same provider. services.
- the design complexity of the application is reduced due to the knowledge of the various equipment and interfaces making it possible to obtain the information.
- the application may even have to interface only with an information centralizing element for all the services of the same service provider.
- information notification is not always supported directly.
- the requesting application is supported by a service provider and the services having the useful information are supported by other service providers unknown to the first.
- one solution is to use the services of a user profile provider, capable of centralizing information related to services supported by multiple providers.
- the desired information is not necessarily all present at the profile provider and above all it is necessary to go "seek" the information, there is no associated notification service.
- the action When the action is limited to retrieving information only from one or more given service providers, it only has access to information from a subset of the services potentially accessible by a user.
- the application often has to deal with a design complexity which stems from the distribution of the equipment to be accessed and from the heterogeneity or absence of the interfaces to be supported.
- the objective of this invention is to allow the realization of a system for retrieving information available from any service provider to notify them to other service providers who have requested it, which is efficient and easy to implement.
- a mediation body between at least one application service provider and a plurality of service providers in a telecommunications network, this body comprising a means of recovering data concerning users from different -service providers, the recovery means being provided for acquiring indications qualifying a user and qualifying at least one desired type of data on this user, such indications being emitted by the application service provider, a mediation body characterized in that '' It comprises means capable of identifying a selection of service providers containing the type of data desired on the user, the retrieval means being further provided to take account of this selection so as to interrogate only the service providers thus selected.
- the result obtained allows a mediation service provider supporting this system to offer a global information notification service to application service providers.
- FIG. 1 is a diagram illustrating the elements of a preferred embodiment of the invention, illustrated in their technical environment;
- FIG. 2 is a diagram illustrating the flows exchanged, in the same embodiment of the invention.
- the present embodiment relates to a multi-domain multi-supplier mediation server for the notification of events to telecom service providers, which is based, in this example, on a assembly comprising a recovery and notification server 3, associated with a local database 2, a user information server on the service providers of the user 4, associated with a database also local 5.
- This database data 5 includes, for each user, an association between the user and all of the service providers having information on this user.
- element 1 represents an application (from an application service provider) requesting external information
- element 2 is a local database, database local to the recovery server and notification 1.
- Element 3 is a recovery and notification server for a mediation service provider (we are talking about role and not actor).
- Element 4 is a user information server on the user's service providers.
- Element 5 is a local database, database local to the user information server to the user information server on the user's service providers.
- the database 5 is, here, different from the database 2.
- the element 6 is an information serving entity, for a service or for a set of services, supporting notifications or not.
- FIG. 2 represents an example of interactions between the determining elements of the invention and the surrounding elements.
- a step a) the application 1 of the application service provider 1 subscribes (the subscription mechanism is not described here) with the recovery and notification server 3 to a notification service for a given user and given information. It provides in particular a user identification, the description of the desired information, the identification of the user information provider on the user's service providers. The description of the desired information is done in a description language general enough to cover all the types of information that an application may want to see.
- the recovery and notification server does not need to be associated in a unique way with a user information server on its suppliers.
- the latter must preferably support the interface recommended in this embodiment.
- the recovery and notification server 3 contacts the user information server 4 on the user's service providers to obtain the list of service providers 6 for the user having information desired by the user. application 1.
- This list is obtained from the association stored by the user information server 4 on the service providers of the user association between the user and his service providers.
- the authorization aspect by the user to access information concerning him is not present in this embodiment here but constitutes an advantageous functional addition among the functions of element 4.
- the precise protocol between the two servers does not is not described in detail.
- b) constitutes a response containing the list of service providers to the user corresponding to the request.
- the recovery and notification server contacts the service provider to user A in order to subscribe to the recovery of the desired information.
- the desired information is described in a description language general enough to cover all of the types of information that the server may wish to receive. The precise protocol between the two entities is not described in detail. For example c) constitutes a successful subscription response.
- a step d) the same interactions as in c) take place in the device, but with the service provider to user B.
- the recovery and notification server 4 indicates to the application that the subscription has gone well and that it is operational. Other messages exist to indicate a refusal to subscribe (bad authorization, missing information, ...)
- a step f) information to which the recovery and notification server has subscribed has just changed. It is assumed that the protocol between the service provider to user A and the latter supports notifications. The server 3 is therefore notified of the event.
- the recovery and notification server 3 notifies the application 1 of the application service provider with the information which has changed, in accordance with the subscription of the application contained in 2 which can then initiate adequate processing to this event.
- Other information associated with information that has changed may also be reported. For example if the notified information is the attachment to a network, we can trace the identification of the user in this network.
- a step h it is assumed that the protocol between the service provider to user B and the recovery and notification server 3 does not support notifications.
- the server 3 will therefore regularly, in this example, ask whether this or that information has changed.
- h ' is a negative response to a request for change.
- a step i) the server will regularly ask if this or that information has changed. It is assumed that this time i) is a positive response to a request for change.
- a step j) the recovery and notification server notifies the application with the information that has changed, in accordance with the application subscription which can then initiate adequate processing for this event.
- Other information associated with information that has changed may also be reported. For example, if the information notified is the attachment to a network, we can trace the identification of the user in this network.
- the functional content of the protocols is not detailed in the example, but one can of course include other functions such as stopping the subscription of the application, modifying the subscription.
- the recovery and notification server 3 supports the only interface with applications. It manages application subscriptions (as well as subscription changes, termination of application service providers clients of the mediation service provider), which it stores in its local database 2. The description of the desired information is made in a description language general enough to cover all the types of information that an application may want to see. It notifies applications 1 during events concerning the information subscribed.
- the server 3 supports an interface with the user information servers on the user service providers. This interface allows it in particular to retrieve service providers who are likely to have the information corresponding to application subscriptions, with the description of this information. It must also make it possible to check the authorizations of applications to upload user information.
- the server interfaces with service providers 6 having information relating to one or more users. It describes the information it wishes in a description language sufficiently general to cover all types of information. It supports various types of protocols, some supporting the transmission of notifications, others not. When the notifications are not supported by a service provider 6, the recovery server 3 implements the appropriate procedure to recover the information in the most efficient and quickest way possible.
- the user information server on the service providers 4 ′ supports an interface with the recovery and notification server. It stores in its local database the associations between the users it manages and the service providers 6 likely to contain information about these users. The various way (s) in which these associations can be informed are not described here. It can also store the permissions to access user information in its local database.
- An evolution consists in also storing the subscriptions of the recovery and notification server 3 in its local database
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
Claims
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR0302469 | 2003-02-28 | ||
FR0302469A FR2851869A1 (en) | 2003-02-28 | 2003-02-28 | MULTI-DOMAIN MULTI-SUPPLIER MEDIATION BODY FOR THE NOTIFICATION OF EVENTS |
PCT/FR2004/000434 WO2004080028A1 (en) | 2003-02-28 | 2004-02-26 | Multi-supplier, multi-domain mediating element for event notification |
Publications (1)
Publication Number | Publication Date |
---|---|
EP1604504A1 true EP1604504A1 (en) | 2005-12-14 |
Family
ID=32843067
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP04714822A Withdrawn EP1604504A1 (en) | 2003-02-28 | 2004-02-26 | Multi-supplier, multi-domain mediating element for event notification |
Country Status (4)
Country | Link |
---|---|
US (1) | US8135802B2 (en) |
EP (1) | EP1604504A1 (en) |
FR (1) | FR2851869A1 (en) |
WO (1) | WO2004080028A1 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080046721A1 (en) * | 2006-08-15 | 2008-02-21 | Thomas Zurek | Dynamic multiprovider |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6029171A (en) * | 1997-02-10 | 2000-02-22 | Actioneer, Inc. | Method and apparatus for group action processing between users of a collaboration system |
US20020007411A1 (en) * | 1998-08-10 | 2002-01-17 | Shvat Shaked | Automatic network user identification |
US6070083A (en) * | 1998-05-14 | 2000-05-30 | Nortel Networks Corporation | Mobile communication device and communication network for providing location services |
US6230018B1 (en) * | 1998-05-14 | 2001-05-08 | Nortel Networks Limited | Devices and processing in a mobile radio communication network having calibration terminals |
GB2338374A (en) * | 1998-06-10 | 1999-12-15 | Motorola Ltd | Locating a mobile telephone using time of arrival measurements |
BR9912270A (en) * | 1998-07-20 | 2001-06-05 | Signalsoft Corp | Location based subscriber services |
US6351757B1 (en) * | 1998-11-13 | 2002-02-26 | Creative Technology Ltd. | Method for conserving memory storage during an interpolation operation |
EP1252563A4 (en) * | 1999-12-23 | 2005-12-07 | M H Segan Ltd Partnership | System for viewing content over a network and method therefor |
JP2001338171A (en) * | 2000-05-29 | 2001-12-07 | Nec Corp | System and method for mediating service transaction and recording medium |
JP2002245282A (en) * | 2001-02-19 | 2002-08-30 | Hitachi Ltd | Method for providing information processing service, and method for controlling information processing resource |
US7302634B2 (en) * | 2001-03-14 | 2007-11-27 | Microsoft Corporation | Schema-based services for identity-based data access |
US20020143664A1 (en) * | 2001-04-03 | 2002-10-03 | Webb Brett M. | Network based gift reminder and purchasing system and method |
US7844055B2 (en) * | 2001-06-26 | 2010-11-30 | Link Us All, Llc | Detecting and transporting dynamic presence information over a wireless and wireline communications network |
US6885861B2 (en) * | 2001-08-24 | 2005-04-26 | Nokia Corporation | Service mobility and recovery in communication networks |
US7529711B2 (en) * | 2001-10-31 | 2009-05-05 | Nortel Networks Limited | Method and system for providing and billing internet services |
US20040128344A1 (en) * | 2002-12-30 | 2004-07-01 | Nokia Corporation | Content and service registration, query and subscription, and notification in networks |
-
2003
- 2003-02-28 FR FR0302469A patent/FR2851869A1/en active Pending
-
2004
- 2004-02-26 EP EP04714822A patent/EP1604504A1/en not_active Withdrawn
- 2004-02-26 US US10/547,165 patent/US8135802B2/en not_active Expired - Fee Related
- 2004-02-26 WO PCT/FR2004/000434 patent/WO2004080028A1/en active Application Filing
Non-Patent Citations (1)
Title |
---|
See references of WO2004080028A1 * |
Also Published As
Publication number | Publication date |
---|---|
WO2004080028A1 (en) | 2004-09-16 |
FR2851869A1 (en) | 2004-09-03 |
US8135802B2 (en) | 2012-03-13 |
US20060200544A1 (en) | 2006-09-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9565297B2 (en) | True convergence with end to end identity management | |
EP1590931B1 (en) | Method of presenting the status of a user using several communication devices | |
EP3087706B1 (en) | Method and system for communication between web browsers, using a unified communication environment | |
EP1376410A1 (en) | Method of managing context information by an intermediary server | |
US9178952B2 (en) | Systems and methods for service assurance using virtualized federated presence infrastructure | |
EP2879328A1 (en) | Method and server for reserving conference hardware resources | |
WO2011073586A1 (en) | Pre-loading of content between a content server and at least one terminal | |
EP1604504A1 (en) | Multi-supplier, multi-domain mediating element for event notification | |
EP1139637A2 (en) | Method and system to have privileges granted by an access manager in a communications network | |
WO2011124810A1 (en) | Management of personalized service in an ip network | |
FR2863810A1 (en) | Telecommunication services coordinating process for use over e.g. Internet, involves utilizing service mediation system to transmit users state in contact list to connected terminals | |
EP2819352B1 (en) | Posting and consultation of messages by users of social networks | |
EP2351328B1 (en) | Method and device for generating information descriptive of the situation of a user | |
EP1494419B1 (en) | System transmitting characteristic parameters of a communication session from a terminal to a remote server | |
EP3465476B1 (en) | Method for invoking an application service via a browser | |
CA2284392A1 (en) | Bridge permitting development of new services independent of the underlying network | |
FR2785121A1 (en) | METHOD FOR PERIODICALLY CHANGING INFORMATION PRESENTED BY A COMMUNICATION TERMINAL FROM DATA TRANSMITTED BY A SERVER | |
FR2871588A1 (en) | METHOD AND MODULE FOR DYNAMIC HOSTING OF SOFTWARE APPLICATIONS IN A GATEWAY BETWEEN AN OPERATOR NETWORK AND A LOCAL NETWORK | |
FR3000357A1 (en) | Method for transferring e.g. audio communication from e.g. smartphone to e.g. computer, involves receiving request for audio and/or video stream of communication and request for re-routing of stream from terminal to another terminal | |
EP2038797B1 (en) | Unit and method for managing at least one channel in an access session for accessing a service in a network | |
WO2010012961A2 (en) | Updating of content search criteria defined for a service provider | |
FR3038182A1 (en) | OPTIMIZED TERMINAL CHANGE DURING APPEALS | |
FR3053190A1 (en) | IDENTIFICATION OF USERS IN A PREFINED ENVIRONMENT | |
FR2858156A1 (en) | Electronic message service customization method, involves selecting user terminals according to available characteristics of available access services, and transmitting message to selected terminal using selected service | |
FR2782872A1 (en) | TELECOMMUNICATION NETWORK MANAGEMENT SYSTEM |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20050823 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL LT LV MK |
|
DAX | Request for extension of the european patent (deleted) | ||
17Q | First examination report despatched |
Effective date: 20070612 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: ORANGE |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 29/08 20060101ALI20160620BHEP Ipc: H04L 29/06 20060101AFI20160620BHEP |
|
INTG | Intention to grant announced |
Effective date: 20160725 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20161206 |