(19)
(11)EP 1 588 236 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
30.03.2011 Bulletin 2011/13

(21)Application number: 04705134.7

(22)Date of filing:  26.01.2004
(51)Int. Cl.: 
H04L 29/06  (2006.01)
(86)International application number:
PCT/IB2004/000250
(87)International publication number:
WO 2004/068265 (12.08.2004 Gazette  2004/33)

(54)

ACCESS RIGHT CONTROL USING ACCESS CONTROL ALERTS

ZUGANGSRECHTSTEUERUNG DURCH ZUGANGSSTEUERUNGSWARNUNGEN

REGULATION DE DROITS D'ACCES AU MOYEN D'ALARMES DE CONTROLE D'ACCES


(84)Designated Contracting States:
DE FI FR GB NL

(30)Priority: 29.01.2003 US 353014

(43)Date of publication of application:
26.10.2005 Bulletin 2005/43

(73)Proprietor: Nokia Corporation
02150 Espoo (FI)

(72)Inventors:
  • TROSSEN, Dirk
    Cambridge, MA 02139 (US)
  • MEHTA, Kuleen
    Atlanta, GA 30331 (US)

(74)Representative: Higgin, Paul et al
Swindell & Pearson Limited 48 Friar Gate
Derby DE1 1GY
Derby DE1 1GY (GB)


(56)References cited: : 
WO-A-03/054717
US-A1- 2002 103 898
US-A1- 2002 131 395
WO-A-2004/063837
US-A1- 2002 126 701
  
  • ROSENBERG J: "A Presence Event Package for the Session Initiation Protocol (SIP)" IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, 6 December 2002 (2002-12-06), XP015027630
  • ANONYMOUS: "Presence Service; Architecture and Functional Description" 3GPP TS 23.141 V6.1.0, December 2002 (2002-12), pages 1-31, XP002288176
  • ROACH A: "Session Initiation Protocol (SIP)-Specific Event Notification. RFC 2543" IETF STANDARD, INTERNET ENGINEERING TASK FORCE, June 2002 (2002-06), XP015009043
  
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


Description

FIELD OF THE INVENTION



[0001] This invention relates generally to telecommunications networks. More particularly, the invention concerns systems and methods for providing access right controlled event subscription, for providing access control alerts, and for controlling access rights using access control alerts.

BACKGROUND OF THE INVENTION



[0002] Event subscription and notification in network environments is becoming increasingly commonplace and important. Event subscription generally allows a first network entity to subscribe to event notifications from a second entity that may be related to a third network entity. Common examples of events include "presence" and "location;" however, the number and types of events are endless. For instance, conventional instant messaging services permit a first user to subscribe to a presence event for a second user. As such, during the period of the subscription, the first user receives updates as to the presence status (e.g., online or offline) of the second user. The subscription may be for a single inquiry, which will return a response of "present" or "not present" for the second user. The subscription may also be for a set period of time, which may result in multiple updates, or for other options (e.g., status change notifications, ongoing notifications, etc.)

[0003] Various protocols may be used for event subscription and notification. For example, the Session Initiation Protocol (SIP) may be used for such purposes. Although SIP is primarily a tool for initiating a communication session between endpoints, extensions to SIP have been proposed to provide event registration and trigger notification (see e.g., IETF document RFC 3265, "SIP-Specific Event Notification," July 2002). Such a proposal, however, neither specifies the semantics of specific events, nor systems and methods for uploading event information.

[0004] Access control in general has been a topic for research, standardization, and product development for several years. It marks a fundamental task for information processing in which the rights of involved parties are controlled for access to, and the use of, certain resources and information, such as files and events. With regard to event subscription and notification, access control is typically governed by the particular event package. For example, instant messaging services generally maintain common host or central administration schemes that use proprietary software and methods for implementing their particular service. As such, access control to an event (e.g., permission for subscribing to notifications for the presence of a second user listed on a first user's buddy list) may be unique for the particular service. Such proprietary solutions may be acceptable for subscription to only a few events; however, as the number of event types increase and become more complex, these may become problematic.

[0005] As an example of the problems with proprietary methods for providing access control and/or access alerts (e.g., alerts for changes in access, alerts for access requests, etc.), consider a scenario involving a cascaded set of event servers. Suppose that a first event server provides events related to sensor information, such as GPS coordinates, and that a second event server subscribes to this information from the first one. For instance, the second server may use GPS coordinates of certain users to derive other information, such as location information that is more coarsely grained (e.g., city information for the certain users). Suppose that the city location information is then used as input through another event subscription to other event servers. Handling of access control in this cascaded case through proprietary methods for each server (or for each event package) may be extremely inefficient and very complex to handle - particularly for a user who is concerned about the usage of this type of information (i.e., his location).

[0006] Providing a standardized interface for specifying and handling access rights for the same information (e.g., location information) to any node (e.g., servers, mobile devices, PC's) may be very advantageous. Further, integrating access control functionality into a generic solution may greatly reduce the complexity for involved entities, particularly when an entity subscribes to a variety of different events. A candidate protocol for such a generic solution may include the Session Initiation Protocol (SIP); however, other protocols may also be used.

[0007] In the context of SIP and access rights, watcher subscriptions are known in which an entity is able to subscribe to the watcher list of a particular event, and as such, will be notified when a new user wishes to subscribe to a particular event. With the use of watcher subscriptions, on-line authorizations of subscriptions are supported. For example, suppose an online music video service allows users to request access to the service from a host entity. If a first user requests access from the host entity, and if an authorization entity for the music video service has subscribed to a "watcher" event related to access to the music video service, the authorization entity will receive a notification ("watcherinfo") from the host entity. Otherwise stated, the authorization entity has subscribed to watcher information from the music video host entity.

[0008] The watcherinfo notification indicates that the first user desires access to the music video service and may include pertinent information, such as a URL for the first user. In order to change access rights for the first user (e.g., permit the first user to access the music video service), the authorization entity typically uses proprietary methods. In other words, watcher events themselves do not provide notifications of changes to access rights nor do they change access rights. They simply watch for access rights requests. As discussed previously, proprietary methods for changing access rights and/or providing notifications of such changes may be very inefficient and complex.

[0009] Thus, a need exists for systems and methods that provide access controlled event subscription using a common framework. Further, a. need exists for systems and methods that provide access right change alerts using a common framework. Additionally, a need exists for systems and methods that provide access control for events through the use of access right change alerts using a common framework.

[0010] Rosenberg, J-, "A Presence Event Package for the Session Initiation Protocol (SIP)>> IETF Standard - Working Draft, Intetnet Engineering Task Force, IETF, 6 December 2002 and "3GPPTS 23.141: 3rd Generation Partnership Project; Technical Specification Group Service and System Aspects; Presence Service; Architecture and Functional Description (Release 6)", v.6.1.0, December 2002 disclose prior arrangements for monitoring the presence of user. A requestor can submir a subscribe a request for information regarding the presence of a user. If the requestor is entitled to access such information, for example, as indicated on a list of users permitted such access, the requested information is provided.

SUMMARY OF THE INVENTION



[0011] Some embodiment of the invention are presented in the appended claims.

[0012] Such network entities and methods may overcome the above-described problems and other problems that will become apparent when reading this specification, by providing access controlled event subscription using a common event framework and access right change alerts using a common event framework. The above aspects can also provide systems and methods for access right controlled event subscription using access right change alerts with a common event framework. Such systems and methods may be used with a wide variety of protocols, systems, and entities.

[0013] In some embodiments, the systems and methods of the present invention operate within a SIP infrastructure and therefore use a SIP event framework. In otter embodiments of the invention computer-executable instructions for implementing the disclosed methods are stored on computer-readable media. Other features and advantages of the invention will become apparent with reference to the following detailed description and figures.

BRIEF DESCRIPTION OF THE DRAWINGS



[0014] The invention will be described in detail in the following description of preferred embodiments with reference to the following figures wherein:

[0015] FIG. 1 shows an architecture that supports access control alerts and access controlled event subscription according to illustrative embodiments of the invention;

[0016] FIG. 2 shows a functional diagram of a mobile device that may act as the requester of FIG. 1;

[0017] FIG. 3 shows a functional diagram of a server, which may be representative of the SIP event server, local repository, alert event server, or requester of Fig. 1;

[0018] FIG. 4 shows message flows between entities of Fig. 1 for an access control alert method according to an illustrative embodiment of the invention;

[0019] FIG. 5 shows a SIP SUBSCRIBE or SIP NOTIFY message according to the embodiments of Fig. 4, 6 and/or 7;

[0020] FIG. 6 shows message flows between entities of Fig. 1 for a method of access controlled event subscription according to an illustrative embodiment of the invention; and

[0021] FIG. 7 shows message flows between entities of Fig. 1 for methods of access rights change notification according to another illustrative embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION



[0022] In the following description of the various embodiments, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration various embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural and functional modifications may be made without departing from the scope of the present invention. Referring now to Fig. 1, a general architecture 10 is shown that supports event subscription and notification in a network environment, and in particular, that supports access controlled event subscription and access change notifications.

[0023] The access control discussed along with embodiments for architecture 10 may be applicable to almost any access control information model. For purposes of these embodiments, access rights are generally assumed to be defined for a set of users regarding particular resources. The access right information may be provided or updated in a variety of methods. For example, access right information may be provided through a provider policy or through the user directly. For instance, a user of an instant messaging service may upload a "buddy list" indicating entities to whom he desires to grant access to a "presence" event related to his availability status.

[0024] The resources associated with access rights may be, for instance, SIP events or file system resources. For SIP events, the access rights generally determine which SIP events for a particular URI might be accessed by certain other URIs. In other words, there may be a relation between SIP events, a SIP URI of the entity to which the current event belongs, and the set of URIs of entities that may be allowed to obtain the current event. As an example, suppose an event is the presence information of a SIP user used in conjunction with an instant messaging service. As such, a buddy list for the SIP user could be a set of URIs which are allowed to obtain the presence event. Other examples of SIP events may be location events or other sensor events. In another example, resources may be file system resources. For file system resources, the access rights may be related to a particular file or directory and the set of users may constitute a set that is allowed to access the file or directory. Additionally, the type of access (e.g., read, write, modify) might be associated with the particular access right.

[0025] As shown in Fig. 1, the architecture 10 generally includes an alert event server 12, a SIP event server 14, an online authorizer 16, a requester 18 and an IP communication network 19 through which these entities may communicate. Each one of these entities is in communication with a respective local SIP proxy 20, 22 and 24, which handles SIP messages and appropriately forwards them to the specified entity. Architecture 10 is generally shown to be part of a SIP event framework and therefore includes local SIP proxies 20, 22 and 24 for forwarding registration/subscription/notification messages according to IETF document RFC 3265, "SIP-Specific Event Notification," July 2002 (hereinafter "RFC 3265"); however, other forwarding mechanisms may be used that might not include local SIP proxies.

[0026] Requester 18 may be a mobile device or other device or entity that requests information, services, content or other data as part of an event request. SIP event server 14 and alert event server 12 may each be any device or entity, including a mobile device, that hosts event subscription and notification for an event, such as an access right alert event. In general, SIP event server 14 provides various type of events and alert event server 12 provides alert events related to access control. SIP event server 14 and alert event server may each be in communication with one or more local repositories 27, which may be linked to one or more access control systems (not shown). The access control systems host access rights for particular resources, events, users, files and other information.

[0027] Although shown as a one-to-one relationship, multiple local repositories 27 may respectively be in communication with SIP event server 14 or alert event server 12. Further, each local repository 27 may be in communication with multiple event servers. Further, event servers 12, 14 may be in communication with one or more online authorizers 16, which authorize event subscriptions as needed. For example, if requester 18 requests access to an event hosted by SIP event server 14 to which requester 18 does not have access, SIP event server 14 may send a message to online authorizer 16 requesting authorization. Various transport or application protocols may be appropriate for interacting with online authorizer 16, such as TCP or HTTP.

[0028] Architecture 10 provides a session initiation protocol (SIP) framework. As such, alert event server 12, SIP event server 14, and requester 18 are each registered with a corresponding local SIP proxy 20, 22 and 24, respectively. Although shown as separate logical entities, SIP event server 14 and/or SIP proxy 20 may be co-located. However, SIP event server 14 is generally an entity that is logically separate from a SIP proxy, and hosts event subscription and notification. Additionally, alert event server 12 along with its respective SIP proxy 20 and local repository 27, and requester 18 along with its respective SIP proxy 22, may be separate or co-located entities that perform their respective logically separate functions. Based on architecture 10, methods of access controlled event subscription and access change notifications according to embodiments of the present invention may be practiced.

[0029] Referring now to Fig. 2, a functional diagram of a mobile device 13 is shown that may act as a requester 18 or a SIP Event Server 14 according to embodiments of the invention, and that may even act as alert event server 12 or online authorizer 16. The mobile device 13 generally includes a processor 30 connected to a display 21, a memory 23, a communication interface 25, a keypad 29, and an audio or audio/visual input 28. Stored within the memory 23 are instructions for creating messages related to the present invention, such as SUBSCRIBE messages, which are described later. The mobile device 13 may comprise a mobile telephone, personal digital assistant (PDA), IP-enabled display device, or other electronic device.

[0030] Referring now to Fig. 3, a functional diagram of a server 31 is shown that may act as a requester 18, a SIP event server 14, a local repository 27, a SIP proxy, an alert event server 12, or an online authorizer 16. In some embodiments, a single server 31 may support multiple logically separate, but co-located, ones of these entities. Server 31 generally includes a processor 32 connected to memory 34 and interface 36. Memory 34 contains instructions for processor 32 to perform steps associated with event subscription and notification, access control for these events, or access change notifications. Further, as a local repository, the memory 34 of server 31 may store a database 35 containing access control information for devices or URIs. Additionally, as a SIP event server, memory 34 may store a local database 35 containing subscription information for devices or URIs.

[0031] According to one embodiment, architecture 10 provides a common framework through which access control change alerts may be provided. Using a SIP framework, such an architecture 10 takes advantage of existing functionality to provide such alerts. Thus, rather than leaving access control change alert mechanisms to proprietary systems or to specific event packages, a common scheme for these alerts is provided. This reduces complexity and simplifies operation when multiple event subscriptions are maintained. Further, such alerts may be used in conjunction with an access control system as discussed below along with figures 6 and 7.

[0032] Suppose, as an example of access alerts, that a user (requester 18) subscribes to several instant messaging services and maintains several buddy lists for these services. Suppose further that the user subscribes to many different "presence" events for each of these other users. In order to accurately track the availability of other users, the user may desire to monitor the level of access he has to their presence information. As such, suppose that requester 18 subscribes to an "access control change" event for a particular other user (e.g., second user) on his buddy list for one of the instant messaging services. Suppose that the access control change event is hosted by a SIP event server, such as alert event server 12. Suppose also that another SIP event server, such as SIP event server 14, maintains the "presence" event for the second user. In another scenario, the presence event and the access control change event may be maintained by the same server. According to either scenario, requester 18 will receive alerts when his access to the second user's presence information changes while his subscription to such alerts is maintained. If the second user desires to remove or limit requester's 18 access to his presence information, requester 18 may be notified. Accordingly, requester 18 may accurately monitor his access level to the second user's presence information.

[0033] Using architecture 10 as an example framework, message flows for a method 100 of subscription and notification of access control changes alerts according to an illustrative embodiment of the invention is shown in Fig. 4. As an overview, method 100 generally includes the following: requester 18 subscribing to a "changed" event with alert event server 12 using a SIP SUBSCRIBE message 40 (shown in Fig. 5), alert event server 12 performing a match for appropriate access right information, and alert event server 12 sending one or more NOTIFY messages back to requester 18 as necessary with appropriate access right information. The method 100 generally begins when requester 18 attempts to determine its access level to a particular event. As such, requester 18 sends a SUBSCRIBE message 40 to its corresponding local SIP proxy 22, which contains as a payload the description of the event package and event type for subscription. SUBSCRIBE message 40 may contain an "expires" parameter (not shown) indicating a duration of the subscription. Depending on the length of the subscription, device 18 may receive periodic notifications in response to changes for the event or may receive a one-time notification of his access control state to the desired event. SUBSCRIBE message 40 according to this embodiment may be a message that is part of an extension to SIP as defined in RFC 3265.

[0034] The format of the access right description in the payload may include, for example, attribute-based formats such as SLP or RDF-based formats, or a dedicated SIP description format. SUBSCRIBE message 40 is appropriately forwarded to the alert event server 12 via proxies 22 and 20. Upon reception of SUBSCRIBE message 40, alert event server 12 stores the subscription for the specified event (e.g., changed access rights) in local database 35 stored in memory 34 (shown in Fig. 3). The associated description and the expiration time for the subscription are also stored in local database 35.

[0035] Referring now to Fig. 4 in particular, and Figs. 1-3 and 5 in general, message flows for method 100 of subscribing to an access control change event according to an embodiment of the invention will be described in more detail. As an example for use in describing these message flows, suppose that requester 18 desires to maintain accurate access state information for an entity listed in an instant messaging buddy list. Suppose further that alert event server 12 is a SIP event server that provides an access control event, and that SIP event server 14 is a SIP event server that provides various type of events, such as "presence" events. Accordingly, alert event server 12 hosts an event package compliant to IETF document RFC 3265, "SIP-Specific Event Notification," July 2002 named "access control." The "access control" event package provides access control to presence information for members of an instant messaging service. Within this event package, there is one event type defined, namely "changed," which is triggered when an access right has changed, such as for a specified buddy list member.

[0036] The event body contains information about the access rights of interest that may change, i.e., infomation about the resource and its associated access information that may change (e.g., buddy list name, presence state). Note that the naming for the package as well as the event are only illustrative. It is possible, however, to define a common event package template for handling access right alerts for each event package individually (e.g.,a standard message format compliant with RFC 3265 for an event type named "changed" for "access control" events).

[0037] As shown in Fig. 4, in order to subscribe to the event "changed" of the event package "access control", requester 18 sends 102 a SUBSCRIBE message 40 (shown in Fig. 5) to its local SIP proxy 22, which contains as a payload 39 the event package (e.g., access control) and event type (e.g., changed) to subscribe to. Further, it contains appropriate information about the resource whose access rights are supposed to be monitored (presence information for a buddy list name). Note that the format of the resource information and the access rights may be defined in various ways. For example, attribute-based formats such as used in SLP or RDF-based formats are candidates for this part of the invention.

[0038] The SUBSCRIBE message 40 is appropriately forwarded 104 to the local SIP proxy 20 for alert event server 12, and then forwarded 106 to alert event server 12. Upon reception of SUBSCRIBE message 40, alert event server 12 stores the subscription and the associated resource/access rights information in its local database 35 (shown in Fig. 3) with the associated expiration time given in the subscription. Compliant to the "SIP-Specific Event Notification" document RFC 3265, SUBSCRIBE message 40 is appropriately confirmed, e.g., with a '200 OK', to requester 18, which is shown as messages 108, 110, and 112.

[0039] This confirmation takes into account whether requester 18 is actually authorized to obtain the requested access right information. For instance, if requester 18 is not on the resource's buddy list, or is not the resource owner, then he is probably not a candidate for obtaining information about access right changes for the presence of this instant messaging resource beyond the mere information that the access right does not exist for him. The problem of appropriately filtering the information to be provided depends on the specific access right information model. As detailed herein, however, the invention assumes that an appropriate policy for information selection is provided at alert event server 12.

[0040] After confirming the SUBSCRIBE message, alert event server 12 sends 114 a match message 116 to the associated local repository 27 for performing a match with the registered access rights stored in repository 27. Note that an appropriate mapping of the access rights description format for the match message 116 may be necessary. Attribute-based formats such as used in SLP or RDF-based formats are candidates for the access rights description format; however, a dedicated format might be used.

[0041] Note also that if there are several local repositories, mapping of SUBSCRIBE message 40 may be necessary to identify the appropriate repository for receiving match message 116. For example, a repository identifier may be included in SUBSCRIBE message 40. Alert event server 12 may further determine the appropriate local repository 27 based on the access right description given in SUBSCRIBE message 40. This may be particularly true if the repository represents an access control repository of a particular technology. Further, alert event server 12 may determine the appropriate repository implicitly, such as through recognition of the format in SUBSCRIBE message 40 (e.g., SLP, RDF) and making a decision based thereon. Additionally, alert event server 12 may query the access rights with all associated local repositories by sending 144 appropriate match messages 116 to all associated repositories or agents. If the repository functionality is co-located with alert event server 12, match message 116 might not need to be sent. If several requests have been sent to several associated repositories 27, alert event server 40 preferably waits for responses 118 from all of these repositories.

[0042] After the reception 120 of repository responses 118, alert event server 12 appropriately filters the obtained information with respect to the subscribed user (i.e., requester 18), by applying a selection policy. The event server 12 then sends 122 a NOTIFY message 50 (shown in Fig. 5) back to requester 18. Message 50 contains the resource description (i.e., "presence" for the buddy list resource) plus associated access right information (e.g., access permitted) and the triggered event (e.g., changed) in an appropriate format (e.g., SLP). If there was not a match for the specific resource, the payload 39 contains an appropriate indication. The NOTIFY message 50 is appropriately routed through the SIP proxies 22, 20 to requester 18.

[0043] Note that the invention allows for a plain query of access rights. Suppose as an example that when requester 18 subscribes (i.e., steps 102, 104 and 106 in Fig. 4) to a changed event, the body of SUBSCRIBE message 40 specifies an expiration time of zero for the subscription. In this case, the subscription is not stored in local database 35. As such, only the information lookup with repository 27 (i.e., steps 114 and 120 shown in Fig. 4) are performed, which leads to an appropriate NOTIFY message 50 being sent to requester 18 (i.e., step 122 shown in Fig. 4).

[0044] If the subscription associated with SUBSCRIBE message 40 of Fig. 4 has not been a one-shot subscription (i.e., a non-zero expiration time has been given in message 40), alert event server 12 follows up with subsequent NOTIFY messages at appropriate times. For example, at pre-determined intervals or in response to changes to access control rights, local repository might notify 126 alert event server 12 of current access control rights. Upon reception of such an update, alert event server 12 performs appropriate matching functions by comparing the notified access control changes with subscriptions stored in database 35 (shown in Fig. 3). Note that such updates from local repository 27 may be unnecessary if repository 27 and alert event server 12 are co-located.

[0045] After comparing the update with stored subscriptions, alert event server 12 applies its local policies for filtering the information with respect to the authorization for obtaining these changes, and sends 128 appropriate NOTIFY messages to currently subscribed requesters, such as requester 18. These messages are appropriately routed through SIP proxies 20, 22 to the requester 18. As such, requester 18 is subsequently notified of changed access control information, which is given as payload 39 in the body of NOTIFY message 50 (shown in Fig. 5). If a stored subscription with alert event server 12 expires based on the expiration time given in SUBSCRIBE message 40, alert event server 12 removes the appropriate subscription from its local database 35 (shown in Fig. 3).

[0046] Method 100 shown in Fig. 4 is applicable to a wide range of events and circumstances. As discussed, it may be advantageous in stand-alone scenarios, such as providing access rights directly to an end user (e.g., updates buddy list information to a instant messenger). In other scenarios, such as a cascaded server scenario, method 100 may provide advantages in combination with other events and other methods. As an example discussed along with Fig. 7, method 100 may be used to provide change alerts to an entity that provides access controlled event subscription.

[0047] Referring to Fig. 1 along with Figs. 2-3 and 5-6, a system and method 200 for providing access controlled event subscription is shown according to an embodiment of the invention. This embodiment takes advantage of a common framework, such as a SIP event framework. Methods for access controlled event subscription using a common framework, such as SIP, can provide many advantages. For example, rather than requiring specific access right methods to be implemented in each entity hosting access rights, a method that takes advantage of a common framework, such as a SIP framework, may be almost universally applicable. Further, such an access control method may apply to a wide variety of events, in contrast to templates that are targeted to specific events or a script that applies to a specific event server.

[0048] As an example of a method for providing access control to events, suppose that a mobile device (not shown) provides context information to SIP event server 14. For instance, suppose the mobile device constantly provides its current location information using GPS coordinates. Suppose further that the user of the mobile device has joined multiple services that provide information, content and/or services based on the current location information of the mobile device. For instance, the user may have joined an emergency roadside service, a local news service, a tracking service through which a friend may monitor his location, a geographical map service that provides street maps for his present location, etc. As such, a variety of entities may need to subscribe to location information for the user's mobile device. The user, however, might not desire to permit all of these entities to have continual access to his location information. As such, the user may desire to change access rights as needed for these entities. According to method 200 for access right event subscription, these entities may subscribe to SIP event server 14 for receiving the user's location information automatically based on the current state of access rights set by the user. According to such an embodiment, the user may interact with alert event server 12 to change access rights for events, such as those related to his location information.

[0049] SIP event server 14 according to such an example maintains the location information for the user's mobile device. In accordance with such an embodiment, SIP event server implements a cache of access rights for a "location" event as well as other applicable events. The cache may be stored as part of database 35 shown in Fig. 3. The cache stored in database 35 preferably includes the event type for which the Access rights are defined, a list of users having access rights, and additional information. The list of users may be in the form of a URI list, which identifies the users that are allowed to subscribe (named "white list" in this embodiment) or those that are not allowed to subscribe (named "black list" in this embodiment). The additional information includes information that may be necessary to further characterize the subscription. For instance, the URI of the mobile device may be maintained in the present example as additional information used for properly identifying the device.

[0050] Using architecture 10 (shown in Fig. 1) as an example framework, a method 200 for providing access right controlled event subscription and notification according to an embodiment of the invention is shown in Fig. 6. According to such an embodiment, access to an event (e.g., subscription) is provided based on current access rights. As shown in Fig. 6, a requester 18 may attempt to subscribe to an event (e.g., location of the mobile device) by sending 202 a SUBSCRIBE message 40 (shown in Fig. 4) to its local SIP proxy 22, which contains as a payload 39 the event package and type for subscription (e.g., location). As with SUBSCRIBE messages 40 discussed previously in other embodiments, based on the particular SIP event package, various formats may be used for the subscription information plus any additional information that might be required to further identify the subscription. For example, attribute-based formats such as SLP or RDF based formats may be appropriate formats.

[0051] The SUBSCRIBE message 40 is appropriately forwarded 204, 206 to the SIP event server 14. Upon reception of the SUBSCRIBE message 40, SIP event server 14 performs a query on its local cache stored in database 35 (shown in Fig. 3) to obtain the access rights for this particular event (e.g., location). For this query, the event server might use additional information, such as the URI of the user to which the event 'belongs'.

[0052] The query's return may be categorized as "access denied," "access allowed," "access unclear," or "no access rights." Access denied may be returned if requester 18 is not included on the white list or if requester 18 is on the black list. Access allowed may be returned if requester 18 is included on the white list. Access unclear may be returned whenever there is a conflict, such as when requester 18 is on both lists. No access rights may be returned when there is no access information for requester 18, such as for an initial subscription. When SIP event server determines that access is denied for requester 18, it sends 226, 228 and 230, an appropriate NOTIFY message 50 to requester 18.

[0053] For situations where access is allowed, access is unclear, or there are no access rights, message flows 208-224 are executed. Note that even if the cache indicates positive access rights for the particular subscription, the current access rights are retrieved from the alert server. This is done to avoid concurrency situations in which the access rights at the alert server have already been changed, but the appropriate NOTIFY message 50 has not yet been arrived at SIP event server 14 to reflect the update. In such situations, the subscription could be granted based on stale information.

[0054] To avoid these situations, SIP event server 14 sends, via steps 208, 210 and 212 (SIP proxy routing), a SUBSCRIBE message 50 requesting updated access rights for the particular event (e.g., location for the user's mobile device) to alert server 12. This may done as a one-time subscription based on specifying an expiration time of zero in the SUBSCRIBE message 40. The SIP event server 14 may obtain the URI of alert server 12 for the particular subscription through various means. For example, this URI might be determined using a common naming scheme, e.g., username@access_control.domain, or the URI might be defined when providing the actual event information, such as during registration of the actual information source with the event server. In the mobile device location scenario, the mobile device may provide the URI for alert server 12 during initial registration with SIP event server 14.

[0055] Upon reception of the SUBSCRIBE message 40 requesting updated access information for the requested event (e.g., access information for event "location" of the mobile device), alert server 12 confirms the subscription appropriately by sending confirmation messages in steps 214, 216 and 218. If this confirmation is negative, e.g., the wrong alert server URI has been provided or the alert server does not support the requested access rights, SIP event server 14 denies the received subscription from requester 18 with an appropriate NOTIFY message 50 as shown in steps 226, 228 and 230. If the alert server subscription sent in step 212 is successful (e.g., correct alert server), a positive confirmation is sent in steps 214, 216 and 218, which is followed up with an appropriate NOTIFY message 50 sent in steps 220, 222 and 224 by alert server 12 to SIP event server 14. NOTIFY message 50 contains the current access rights for the requested event (e.g., location). SIP event server 14 in turn waits for this NOTIFY message 50 (based on receiving a confirmation message in step 218) and stores the current access right information in the cache of database 35. The SIP event server 14 then decides whether to grant the original subscription based on the updated cache information.

[0056] If the updated cache indicates access denied, a negative confirmation is sent back to the requester in steps 226, 228 and 230. If the cache indicates access allowed, a positive confirmation, i.e., '200 OK', is sent back to the requester in steps 226, 228 and 230. If the cache indicates access unclear, event server 14 distinguishes two different sub-cases:

on-line authorization and access denied. On-line authorization provides an optional feature of the present invention in compliance with event template packages for watcher information. If there exists an Online Authorizer relationship for this particular subscription, event server 14 sends an appropriate message (not shown) to OnlineAuthorizer 16 to ask for subscription permission. The OnlineAuthorizer 16 sends back an appropriate confirmation (not shown) that indicates whether to grant the original submission. In such an embodiment, SIP event server 14 may support the watcherinfo template, and the OnlineAuthorizer 16 might have a subscription to the watcherinfo for the particular event. In this case, SIP event server 14 sends an appropriate watcherinfo NOTIFY message 50 to the OnlineAuthorizer 16, which in turn sends back a message to the SIP event server 14 that contains information whether or not to grant the original subscription.



[0057] When access is denied based on unclear access rights, SIP event server 14 denies the original subscription and thereby sends a negative confirmation to requester 18 in steps 226, 228 and 230. If the updated cache stored in database 35 indicates that access is denied, it is treated as if the requester's identity were not listed on the white list or that the white list is empty. Note that the denied subscription from requester 18, or an accepted subscription, may have follow-up actions, such as those defined IETF's document RFC 3265, SIP-Specific Event Notification, July 2002.

[0058] Referring now to Fig. 7 along with Figs. 1-6, a method 300 is shown that represents another embodiment of the present invention. Method 300 is generally a variation of method 200 and includes many aspects and preferences of method 200, except for those related to access right change updates. Method 300 generally includes a system and method for providing access right controlled event subscription using access right change alerts. In other words, SIP event server 14 according to method 300 may take advantage of access right change subscription method 100 discussed along with Fig. 4 in order to automatically receive access right updates. As such, the method 200 for access right controlled subscription discussed along with Fig. 6 may be improved via combination with method 100 in a further embodiment of the invention. This is because it is likely that access rights will change over time at alert server 12 during existing subscriptions at SIP event server 14, In keeping with the location event scenario, this may be particularly true as the user of the mobile device travels and changes access rights based on his needs at his present location.

[0059] The handling of these updates and changes is shown generally in Figure 7. Since there already exists a subscription at event server 14 for a particular event (e.g., location), there also exists a subscription to the access right alert event at alert server 12 for the particular event as part of method 200 discussed along with Fig. 6. Hence, alert event server 12 sends 302 an access right change alert NOTIFY message to SIP event server 14 via steps 304 and 306 in response to an access right change. Upon reception of the alert (NOTIFY) message, event server 14 updates its local cache entry for the event for which the access right changed based on information for the event included in the alert event message sent in step 302.

[0060] Further, event server 14 checks existing subscriptions and filters those subscriptions that are affected by the received changes/updates. The check of these filtered subscriptions against the changes in access rights may lead to either verification or revocation of the requester's access rights to the event (e.g., location information). Revocation of requester's 18 access rights may occur if the updated/changed access rights indicate that requester 18 is no longer allowed to have access to the particular event, such as location information for the mobile device (not shown). This could be checked through the black list (i.e., requester is now in this list) or through the white list (i.e., the user is no longer in this list). As a consequence, SIP event server 14 deletes requester's subscription from its internal database and sends 308 a NOTIFY message 50 to the requester via steps 310 and 312. In the case that requester 18 is no longer in the white list in comparison with updated/changed access rights, but has not explicitly been excluded from the access rights (through adding to the black list), SIP event server 14 may use the OnlineAuthorizer 16 as discussed above to verify subscription rights online.

[0061] While the present invention has been described in connection with the illustrated embodiments, it will appreciated and understood that modifications may be made without departing from the scope of the invention as defined by the appended claims. In particular, the invention can apply to other session related protocols, to various discovery mechanisms and protocols, and to a variety of different devices and networks. Further, the present invention is applicable to a wide range of events and entities.


Claims

1. A method of requesting notification of a change of access rights comprising:

sending a subscription message comprising a request for information about access rights for a resource and for notification of a change of the access rights,

said access rights indicating access by other entities to said resource, wherein

the subscription message (40) specifies an event package and an event type to which to subscribe;

and

receiving, in response to said subscription message (40), a first notify message (50) including information about said access rights for said resource,

wherein a body of the first notify message (50) specifies a description of the resource, access right information associated with the resource, and a triggered event.


 
2. The method of claim 1, further comprising receiving a second notify message, said second notify message including information about changed access rights for said resource.
 
3. The method of claim 1, wherein said subscription message (40) is a session initiation protocol message.
 
4. The method of claim 1, wherein said information about access rights comprises information having an attribute-based format.
 
5. The method of claim 4, wherein said attribute-based format conforms with either a service location protocol (SLP) or Resource Description Framework (RDF).
 
6. A method of requesting notification of a change of access rights comprising;

receiving, from a requester (18), a subscription message (40) comprising a request for information about access rights for a resource and for notification of a change of the access rights

wherein said access rights indicate access by other entities to said resource,

wherein the subscription message (40) specifies an event package and an event type to which to subscribe;

confirming whether said requester (18) is authorized to obtain status information about said access rights for said resource;

matching said information about access rights with said access rights; and

creating , in response to the subscription message (40), a first notify message (50) comprising access right information for said resource,

wherein a body of the first notify message (50) specifies a description of the resource, access right information associated with the resource, and a triggered event.


 
7. The method of claim 6, further comprising creating a second notify message based on a changed status of access rights for said resource, said second notify message comprising changed access right information for said resource.
 
8. The method of claim 6, wherein said subscription message (40) is a session initiation protocol message.
 
9. The method of claim 6, wherein the matching of said information comprises:

sending a match message to a repository, said match message requesting access rights information for said resource; and

receiving a response from said repository, said response comprising access right information for said resource.


 
10. A method for providing access controlled event subscription comprising:

receiving from a requester (18) a subscription message (40) for an event for a resource, the requestor being a different entity than the resource;

querying a database (35) containing access rights for said event;

when said access rights does not indicate denial of access to said event,

accessing updated access rights; and

notifying said requester (18) of access status for said events based on said updated access rights;

wherein the accessing of updated access rights comprises sending a subscription message (40) to an access control network entity (12, 14) requesting updated access rights for said event and receiving updated access rights for said event in order to avoid notifying the requester (18) of access status for the event that is based on stale information obtained by querying the database (35).


 
11. The method of claim 10, wherein said step of accessing updated access rights comprises:

subscribing to an access rights change alert event for access rights of said event; and while said subscription is in effect, accessing the last received access rights received from said network entity (14) for said event.


 
12. The method of claim 10, wherein for said step of receiving, said subscription, message (40) comprises a session initiation protocol subscribe message.
 
13. The method of claim 10, wherein said database is stored on a local cache.
 
14. A computer-readable medium having computer-readabie instructions that 1 to when executed cause a processor to enable the method of any one of claims 1 to 13.
 
15. A device comprising: any one of claims 1 to 5.

means for performing all the steps of the methods of any one of claims 1 to 5.


 
16. A device as claimed in claim 15, wherein the device is a mobile device.
 
17. A device as claimed in claim 15, wherein the device is a mobile telephone, personal digital assistant or IP-enabled display device.
 
18. A device as claimed in claim 15, configured to create the subscription message (40).
 
19. A device comprising,

means for performing all the steps of the methods of any one of claims 6 to 13.


 
20. A device as claimed in claim 19, wherein the device is a network entity.
 


Ansprüche

1. Verfahren zum Anfordern einer Benachrichtigung über eine Änderung von Zugriffsrechten, umfassend:

- Senden einer Teilnahme-Nachricht, umfassend eine Anforderung von Informationen über Zugriffsrechte für eine Ressource und einer Benachrichtigung über eine Änderung der Zugriffsrechte;

- wobei die Zugriffsrechte den Zugriff von anderen Entitäten auf die Ressource anzeigen, wobei die Teilnahme-Nachricht (40) ein Ereignis-Paket und eine Ereignis-Art angibt, woran teilgenommen werden soll; und

- Empfangen einer ersten Benachrichtungs-Nachricht (50), die Informationen über die Zugriffsrechte für die Ressource einschließt, in Reaktion auf die Teilnahme-Nachricht (40), wobei ein Hauptteil der ersten Benachrichtigungs-Nachricht (50) eine Beschreibung der Ressource, Zugriffsrecht-Informationen, die mit der Ressource verknüpft sind, und ein ausgelöstes Ereignis bestimmt.


 
2. Verfahren nach Anspruch 1, weiter umfassend Empfangen einer zweiten Benachrichtigungs-Nachricht, wobei die zweite Benachrichtigungs-Nachricht Informationen über geänderte Zugriffsrechte für die Ressource einschließt.
 
3. Verfahren nach Anspruch 1, wobei die Teilnahme-Nachricht (40) eine Session-Initiation-Protocol-Nachricht ist.
 
4. Verfahren nach Anspruch 1, wobei die Informationen über Zugriffsrechte Informationen umfassen, die ein Attribut-basiertes Format aufweisen.
 
5. Verfahren nach Anspruch 4, wobei das Attribut-basierte Format mit entweder einem Service-Location-Protocol (SLP) oder einem Ressource-Description-Framework (RDF) konform ist.
 
6. Verfahren zum Anfordern einer Benachrichtigung über eine Änderung von Zugriffsrechten, umfassend:

- Empfangen einer Teilnahme-Nachricht (40), die eine Anforderung von Informationen über Zugriffsrechte für eine Ressource und einer Benachrichtigung über eine Änderung der Zugriffsrechte umfasst, von einem Anfordernden (18);

- wobei die Zugriffsrechte den Zugriff von anderen Entitäten für die Ressource angeben, wobei die Teilnahme-Nachricht (40) ein Ereignis-Paket und eine Ereignis-Art bestimmt, woran teilgenommen werden soll;

- Bestätigen, ob der Anfordernde (18) autorisiert ist, Statusinformationen über die Zugriffsrechte für die Ressource zu erhalten;

- Abgleichen der Informationen über Zugriffsrechte mit den Zugriffsrechten;
und

- Erzeugen einer ersten Benachrichtigungs-Nachricht (50), die Informationen über Zugriffsrechte für die Ressource umfasst, in Reaktion auf die Teilnahme-Nachricht (40);

- wobei ein Hauptteil der ersten Benachrichtigungs-Nachricht (50) eine Beschreibung der Ressource, Zugriffsrecht-Informationen, die mit der Ressource verknüpft sind, und ein ausgelöstes Ereignis angibt.


 
7. Verfahren nach Anspruch 6, weiter umfassend Erzeugen einer zweiten Benachrichtigungs-Nachricht, basierend; auf einem geänderten Status von Zugriffsrechten für die Ressource, wobei die zweite Benachrichtigungs-Nachricht Informationen über geänderte Zugriffsrechte für die Ressource umfasst.
 
8. Verfahren nach Anspruch 6, wobei die Teilnahme-Nachricht (40) eine Session-Initiation-Protocol-Nachricht ist.
 
9. Verfahren nach Anspruch 6, wobei das Abgleichen der Informationen umfasst:

- Senden einer Abgleichs-Nachricht an einen Speicher, wobei die Abgleichs-Nachricht Informationen über Zugriffsrechte für die Ressource anfordert; und

- Empfangen einer Antwort von dem Speicher, wobei die Antwort Informationen über Zugriffsrechte für die Ressource umfasst.


 
10. Verfahren zum Bereitstellen von zugriffsgesteuerter Ereignis-Teilnahme, umfassend:

- Empfangen einer Teilnahme-Nachricht (40) für ein Ereignis für eine Ressource, von einem Anfordernden (18), wobei der Anfordernde eine andere Entität als die Ressource ist;

- Abfragen einer Datenbank (35), die Zugriffsrechte für das Ereignis enthält;

- Zugreifen auf aktualisierte Zugriffsrechte, wenn die Zugriffsrechte keine Ablehnung des Zugriffs auf das Ereignis anzeigen; und

- Benachrichtigen des Anfordernden (18) über den Zugriffs-Status für die Ereignisse, basierend auf den aktualisierten Zugriffsrechten;

- wobei das Zugreifen auf aktualisierte Zugriffsrechte das Senden einer Teilnahme-Nachricht (40) an eine Zugriffssteuerungs-Netzwerkentität (12, 14) umfasst, die aktualisierte Zugriffsrechte für das Ereignis anfordert, und Empfangen von aktualisierten Zugriffsrechten für das Ereignis, um zu verhindern, dass der Anfordernde (18) über einen Zugriffs-Status für das Ereignis benachrichtigt wird, der auf abgelaufenen Informationen basiert, die durch Abfragen der Datenbank (35) erhalten werden.


 
11. Verfahren nach Anspruch 10, wobei der Schritt des Zugreifens auf aktualisierte Zugriffsrechte umfasst:

- Teilnehmen an einem Zugriffsrecht-Änderungsalarmereignis für Zugriffsrechte des Ereignisses;

- und während die Teilnahme in Kraft ist, Zugreifen auf die letzten empfangenen Zugriffsrechte, die von der Netzwerkentität (14) für das Ereignis empfangen wurden.


 
12. Verfahren nach Anspruch 10, wobei beim Schritt des Empfangens die Teilnahmenachricht (40) eine Session-Initation-Protocol-Teilnahme-Nachricht umfasst.
 
13. Verfahren nach Anspruch 10, wobei die Datenbank in einem lokalen Cache gespeichert ist.
 
14. Computerlesbares Medium mit computerlesbaren Anweisungen, die bei Ausführung einen Prozessor dazu veranlassen, das Verfahren nach einem der Ansprüche 1 bis 13 zu ermöglichen.
 
15. Vorrichtung, umfassend:

- Mittel zum Ausführen aller Schritte von einem der Ansprüche 1 bis 5.


 
16. Vorrichtung nach Anspruch.15., wobei die Vorrichtung eine Mobilvorrichtung ist.
 
17. Vorrichtung nach Anspruch 15, wobei die Vorrichtung ein Mobiltelefon, ein persönlicher digitaler Assistent oder eine IP-fähige Anzeigevorrichtung ist.
 
18. Vorrichtung nach Anspruch 15, die eingerichtet ist, um die Teilnahme-Nachricht (40) zu erzeugen.
 
19. Vorrichtung, umfassend:

- Mittel zum Ausführen aller Schritte der Verfahren nach einem der Ansprüche 6 bis 13.


 
20. Vorrichtung nach Anspruch 19, wobei die Vorrichtung eine Netzwerkentität ist.
 


Revendications

1. Procédé destiné à demander une notification d'une modification de droits d'accès, comprenant les étapes ci-dessous consistant à :

envoyer un message d'abonnement comprenant une demande d'informations afférentes à des droits d'accès pour une ressource et pour une notification d'une modification des droits d'accès ;

lesdits droits d'accès indiquant un accès par d'autres entités à ladite ressource,

dans lequel le message d'abonnement (40) spécifie une offre groupée d'événements et un type d'événement faisant l'objet d'un abonnement ;

et recevoir, en réponse audit message d'abonnement (40), un premier message de notification (50) comportant des informations afférentes auxdits droits d'accès pour ladite ressource ;

dans lequel un corps du premier message de notification (50) spécifie une description de la ressource, des informations connexes aux droits d'accès associées à la ressource, et un événement déclenché.


 
2. Procédé selon la revendication 1, comprenant en outre l'étape consistant à recevoir un second message de notification, ledit second message de notification comportant des informations afférentes aux droits d'accès modifiés pour ladite ressource.
 
3. Procédé selon la revendication 1, dans lequel ledit message d'abonnement (40) est un message de protocole d'ouverture de session.
 
4. Procédé selon la revendication 1, dans lequel lesdites informations afférentes aux droits d'accès comportent des informations présentant un format basé sur des attributs.
 
5. Procédé selon la revendication 4, dans lequel ledit format basé sur des attributs est conforme à un protocole de localisation de service (SLP) ou à un cadre de description des ressources (RFD).
 
6. Procédé destiné à demander une notification d'une modification de droits d'accès, comprenant les étapes ci-dessous consistant à :

recevoir, en provenance d'un demandeur (18), un message d'abonnement (40) comprenant une demande d'informations afférentes à des droits d'accès pour une ressource et pour une notification d'une modification des droits d'accès,

dans lequel lesdits droits d'accès indiquent un accès par d'autres entités à ladite ressource ;

et dans lequel le message d'abonnement (40) spécifie une offre groupée d'événements et un type d'événement faisant l'objet d'un abonnement ;

confirmer si ledit demandeur (18) est autorisé à obtenir des informations d'état afférentes auxdits droits d'accès pour ladite ressource ;

établir une correspondance entre lesdites informations afférentes aux droits d'accès et lesdits droits d'accès ; et

créer, en réponse au message d'abonnement (40), un premier message de notification (50) comprenant des informations afférentes aux droits d'accès pour ladite ressource ;

dans lequel un corps du premier message de notification (50) spécifie une description de la ressource, des informations connexes aux droits d'accès associées à la ressource, et un événement déclenché.


 
7. Procédé selon la revendication 6, comprenant en outre l'étape consistant à créer un second message de notification basé sur un état modifié de droits d'accès pour ladite ressource, ledit second message de notification comprenant des informations afférentes aux droits d'accès modifiés pour ladite ressource.
 
8. Procédé selon la revendication 6, dans lequel ledit message d'abonnement (40) est un message de protocole d'ouverture de session.
 
9. Procédé selon la revendication 6, dans lequel l'étape consistant à établir une correspondance desdites informations comprend les étapes ci-dessous consistant à :

envoyer un message de correspondance à un référentiel, ledit message de correspondance demandant des informations afférentes aux droits d'accès pour ladite ressource ; et

recevoir une réponse en provenance dudit référentiel, ladite réponse comprenant des informations afférentes aux droits d'accès pour ladite ressource.


 
10. Procédé destiné à fournir un abonnement à des événements à accès contrôlé, comprenant les étapes ci-dessous consistant à :

recevoir, en provenance d'un demandeur (18), un message d'abonnement (40) à un événement pour une ressource, le demandeur étant une entité distincte de la ressource ;

interroger une base de données (35) contenant les droits d'accès connexes audit événement ;

lorsque lesdits droits d'accès n'indiquent pas de déni d'accès audit événement :

accéder à des droits d'accès mis à jour ; et

informer ledit demandeur (18) quant à l'état d'accès auxdits événements sur la base desdits droits d'accès mis à jour ;

dans lequel l'étape d'accès à des droits d'accès mis à jour comprend l'étape consistant à envoyer un message d'abonnement (40) à une entité de réseau de commande d'accès (12, 14), à demander des droits d'accès mis à jour pour ledit événement et à recevoir des droits d'accès mis à jour pour ledit événement afin d'éviter d'informer le demandeur (18) quant à un état d'accès à l'événement qui serait basé sur des informations périmées obtenues lors de l'interrogation de la base de données (35).


 
11. Procédé selon la revendication 10, dans lequel ladite étape consistant à accéder à des droits d'accès mis à jour comprend les étapes ci-dessous consistant à :

s'abonner à un événement d'alerte pour modification de droits d'accès relativement aux droits d'accès dudit événement, et tandis que l'abonnement est en vigueur, accéder aux derniers droits d'accès reçus de ladite entité réseau (14) pour ledit événement.


 
12. Procédé selon la revendication 10, dans lequel, pour ladite étape de réception, ledit message d'abonnement (40) comprend un message d'abonnement de protocole d'ouverture de session.
 
13. Procédé selon la revendication 10, dans lequel ladite base de données est stockée sur une mémoire cache locale.
 
14. Support lisible par un ordinateur comportant des instructions lisibles par un ordinateur qui, lorsqu'elles sont exécutées, amènent un processeur à mettre en oeuvre le procédé selon l'une quelconque des revendications 1 à 13.
 
15. Dispositif comprenant :

un moyen pour mettre en oeuvre l'ensemble des étapes des procédés selon l'une quelconque des revendications 1 à 5.


 
16. Dispositif selon la revendication 15, dans lequel le dispositif est un dispositif mobile.
 
17. Dispositif selon la revendication 15, dans lequel le dispositif est un téléphone mobile, un assistant numérique personnel ou un dispositif d'affichage compatible IP.
 
18. Dispositif selon la revendication 15, configuré de manière à créer le message d'abonnement (40).
 
19. Dispositif comprenant :

un moyen pour mettre en oeuvre l'ensemble des étapes des procédés selon l'une quelconque des revendications 6 à 13.


 
20. Dispositif selon la revendication 19, dans lequel le dispositif est une entité de réseau.
 




Drawing





















REFERENCES CITED IN THE DESCRIPTION



This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

Non-patent literature cited in the description