RU2314658C2 - Communication system - Google Patents

Abstract

FIELD: communication system.

SUBSTANCE: communication system contains at least one client, to which presence information is connected, where aforementioned presence information contains a set of parts, and at least one of aforementioned parts contains information, identifying application, for which aforementioned at least one part is intended; and at least one object, for which presence information is provided in connection with aforementioned at least one client, where aforementioned at least one object has at least one object application, where aforementioned at least one object is made with possible usage of aforementioned information for producing at least one part, intended for aforementioned at least one object application.

EFFECT: increased volume of presence information.

4 cl, 5 dwg

Description

FIELD OF THE INVENTION

This invention relates to a communication system, in particular to providing a presence service in a communication system.

State of the art

A diverse range of communication systems is used today, which makes it possible to communicate between two or more objects, such as subscriber equipment and / or other nodes associated with the system.

Known communication systems that provide wireless communication for the terminals of subscribers or other nodes. An example of a wireless system is a public land mobile network (PLMN). A PLMN is typically a cellular network in which a base transceiver station (BTS) or similar access entity serves subscriber equipment (UE), such as mobile stations, through a wireless interface. The operation of the device required for communication is usually controlled by one or more control objects, which themselves can be interconnected. One or more gateway nodes provide PLMN connectivity to other networks. Examples of other such networks are another cellular network, a public switched telephone network (PSTN), and a packet-switched data network, such as an Internet Protocol (IP) based network. Communication between the equipment of the subscriber and other elements of the communication system is based on the corresponding communication protocol, which defines the “rules” by which communication is controlled in the system.

The current third generation (3G) wireless system defines various servers for managing various communication services for mobile subscribers. They include servers that provide call status (em) control functions known as CSCFs. Monitoring functions can also be provided by objects such as the home subscriber server (HSS), and applications by various application servers. HSS is typically used to permanently store a subscriber profile and is used during authentication. For example, in the architecture of Release 5 for 3G, as defined in the partnership project of a number of companies to develop the third generation 3G standard (3GPP), these objects can be found as located in the Internet Protocol Multimedia Subsystem (IMS).

The IMS network can be at the core of the 3G architecture, supporting an Internet Protocol-based network that manages both traditional voice telephony and multimedia services. 3GPP has chosen Session Initiation Protocol (SIP) as the basic session signaling protocol for 3G networks. SIP was developed by the Internet Engineering Task Force (IETF). Those interested can find the 3GPP 24.229 specification, which describes the basic operation of the IMS network, from the SIP perspective, entitled "IP Multimedia Call Control Protocol based on SIP and SDP" at http://www.3gpp.org/ftp/Specs/Latest-drafts/24229 -201.zip. SIP is a request / response style protocol in the sense that for each message sent from the source, there is a corresponding response based on the receipt of confirmation of the destination of the sent message. (An acknowledgment message is a special case to which no reply is sent).

For example, in a 3G network, when a subscriber first turns on his mobile terminal, he must register his ID or address of the subscriber with the network before allowing the terminal to fully connect. This is done by sending a SIP 'REGISTER' message from the terminal to the IMS, which includes the details of the subscriber address. The IMS receives and processes this information using a Call Status Monitoring Function (S-CSCF), which in this context is referred to as a "registrar". The REGISTER message is used only to ensure correspondence between the subscriber’s nickname and the contact address, for example, to establish correspondence between the sip alias: mikko.lonnfors@sonera.com and the Internet terminal protocol address. The IMS confirms the registration by sending the appropriate acknowledgment message (e.g., 200 OK message) in accordance with the SIP. Subsequent registrations also take place (re-'REGISTER ') whenever the previous registration has ended or ends, or when there is a change in the state of the subscriber. When a subscriber wants to establish a session with another subscriber, such as a voice call or a messaging session (there is another way to send messages, that is, with a SIP message, in which case a session is not required), the session will be negotiated under SIP control.

Application Servers (ASs) can provide services through IMS, such as instant messaging, presence, local traffic reports, and conference facilities. The AS may remain within or outside the IMS network. Typically, the AS is external when the supported service is provided by a third party.

One specific example of status information is presence information. Subscribers or application servers subscribing to a presence service can determine the ability and availability of another subscriber, for example, to accept a call (depending on the equipment and service provider) among other features / attributes of the presence. However, in systems that support SIP, the presence may involve many indicators, such as “in the office and available for all calls”, “at home and available only for private calls” and “busy in the call” (or at least it turns out to be). This presence information allows a subscriber to establish the availability of another subscriber before attempting to make a call. A presence service can provide more than just information such as available / not available. It may contain visual, animated or sound elements and may describe various issues, for example, related to a game session.

This presence service, which is standardized in OMA 8 (open mobile alliance (www.openmobilealliance.org)), 3GPP and IETF, is attracting more and more attention. The number of applications with presence information is expected to increase in the future. As the number of applications increases, the amount of presence information also increases. From receiving terminal perspectives, increasing information poses a problem on how to use presence information, i.e. which parts of the presence information are suitable for which applications. A terminal can run one or more applications. For example, a terminal may run a dynamic phone book application and a games application.

Current IETF and 3GPP models use a tuple structure (groups of related data items or records). A tuple contains a “random” tuple identifier that does not have any semantics, i.e. it cannot be used to describe the purpose of a tuple. Each tuple can have several attributes. In addition, different tuples can have attributes that have the same name, but are intended to be used / interpreted in different ways depending on the sending / receiving application. For example, presence information may contain two tuples (one for games and one for dynamic phone book (DPB)), and each of these tuples may contain a status field. A dynamic phone book can be designed to understand state values: available, discrete, not accessible, while a game can be designed to understand state values: shooting, dead, pause, lost. As you can see from this example, status fields must be delivered to the correct application if they must have the correct value. This is a problem when the terminal has two or more applications. This is also a problem, even if the receiving terminal has only one application, and the sending terminal or presentation has many applications. If the data provided in the example is delivered to a terminal having, for example, only DPB, then it is necessary for the receiving terminal to be able to determine which tuple was intended for the DPB application.

There is currently no mechanism for passing information to the correct applications in a different way than for each application to check each tuple and to see if the status values have any value for the application. In other words, the trial and error method has been adopted. However, this creates uncertainty about the correctness of the information. This is the case, because in some cases, even if the value may be the same for the attribute, it may be misinterpreted by the wrong application. An example of this is the following: the sending terminal has a DPB and IM (instant messaging) application. It sets the status values: DPB = Closed, IM = Open. In this example, both applications would only use state values open and closed. Now, if the receiving terminal has only an IM application, then it accepts the states of both DPB and IM. If the receiving terminal experiences the first DPB status value, then it understands it and presents it to the subscriber through the IM application, saying that the IM application in the presentation terminal was closed, even though it was open.

It has been proposed that when a subscriber wishes to receive presence information about one other subscriber, so that the subscriber has the ability to turn on filters to reduce data from the presence server, i.e., presence information. These filters are configured to reduce data from the presence server to include only those parts that are of interest to the subscriber.

The approach in which tuple identifications are used as filtering criteria by observers (subscribers requesting presence information) and when authorization is based on tuple identifications has many drawbacks. If, for example, the monitored subscriber has 4 tuples (T1, T2, T3 and T4) and one observer is interested only in T2 and T3 tuples, then the observer sets filters to enable only T2 and T3 tuples to be marked for him. The observed subscriber may then decide, for some reason, to start showing different values to a particular observer, touching all tuples. Therefore, the observing subscriber creates new tuples T5, T6, T7 and T8 and creates a new access list, which allows the observer to see tuples T5-T8, and not T1-T4. But the observer has established filtering based on the identification of the tuple, which means that no tuples are provided for him. This is a disadvantage.

Another disadvantage of using tuple identifications in filtering is that usually the view does not want the observers to know that it is not allowed for the particular observer to receive the same detailed information as the other observer, or that the information transmitted to different groups of observers is slightly or completely differed from information transmitted to other observers.

It is a drawback that the filtering settings change each time the observer authorization information changes, since a different level of detail of the information is provided to the observer. This would be the case if filtering were based on unique tuple identifications.

SUMMARY OF THE INVENTION

Embodiments of the present invention are aimed at overcoming one or more of the above problems.

According to one aspect of the present invention, there is provided a communication system comprising at least one subscriber to which presence information is associated, the presence information comprising a plurality of parts, wherein at least one of said parts contains information identifying an application for which said at least least one part.

According to a second aspect of the present invention, a communication method is provided, comprising providing presence information for a connected subscriber, the presence information comprising a plurality of parts, wherein at least one of said parts contains information identifying an application for which said at least is intended one part; moreover, at least one of said parts is obtained by means of at least one object, wherein at least one object has at least one application of an object, and by means of at least one object, parts containing information identifying said at least one are obtained object application.

According to a third aspect of the present invention, a subscriber is provided in a communication system, said subscriber having associated presence information, the presence information comprising a plurality of parts, said subscriber being adapted to provide at least one of said parts with information identifying an application for which said at least one part.

According to a fourth aspect, the present invention provides an object in a communication system comprising at least one means of receiving an application for receiving at least one part of presence information associated with a subscriber, wherein at least one part contains information identifying the application, wherein configured to obtain at least a portion containing information identifying said at least one application.

The perfectly static filtering settings possible with the embodiments of the invention are useful, especially when the filters are stored in a specific server (for example, in the case of a presence list) or the like in advance.

Embodiments of the invention may allow concealment from observers of the fact that there is a different level of information (or completely different information) available to other observers.

Embodiments of the invention may allow changes to be made to authorization without affecting, for example, filtering settings or some other functionality that can be separated from authorization by imparting greater semantics to presence information elements.

Embodiments of the invention may enable an observer to request semantically understandable information instead of justifying a request for “insignificant” identification information.

Brief Description of the Drawings

For a better understanding of the present invention and how it can be implemented, reference will be made only by way of example to the accompanying drawings, in which:

FIG. 1 shows a communication system in which the present invention can be applied;

FIG. 2 shows schematically an embodiment of the invention;

FIG. 3 shows an embodiment of FIG. 2 in more detail;

FIG. 4 shows a portion of the IMS system of FIG. 1 in more detail;

FIG. 5 shows schematically an embodiment of the invention.

Detailed Description of Embodiments

Reference will now be made first to FIG. 1, which shows a typical 3rd generation (3G) wireless telecommunication system running a universal mobile communication system (UMTS). At the core of this system is the network of the Internet Protocol Multimedia Subsystem (IMS) 100, which routes calls and all kinds of sessions between two or more subscribers (or between the subscriber and the network element, for example, an application server) of the network and provides other network functions. Examples of subscribers are a mobile terminal 111, a travel computer 112, a personal desk assistant (PDA) 113, a public switched telephone network (PSTN) telephone 131, a computer terminal 123, an application server 121, and an application server 122. IMS uses an Internet Protocol-based network to process these calls, which can include both voice calls and multimedia calls.

The IMS network effectively acts as a gateway in the 3G system between subscribers 111, 112, 113 and other networks, such as PSTN 130 and an external network 120 based on the Internet Protocol. Signals are exchanged between the mobile terminal and other subscribers of the IMS network and within the IMS network under the control of a session initialization protocol (SIP). All links to messages that follow are SIP messages, unless otherwise noted, and will be shown in capital letters. It should be understood that although preferred embodiments of the present invention have been described in the context of SIP, other embodiments of the invention may be implemented under non-SIP conditions.

Reference will now be made to FIG. 2 and 3, which schematically show an embodiment of the present invention. FIG. 2 shows a transmitting terminal 10 and a receiving terminal 12. The transmitting terminal 10 is configured to provide presence information for the receiving terminal 12. A presence server 14 is provided. The presence server 14 and the transmitting terminal are sometimes called a presentation. The presence server 14 supplies the receiving terminal 12 with the required presence information. The presence server 14 will receive presence information from the transmitting terminal. It should be understood that the connection between the transmitting terminal 10 and the server 14 of presence, as well as the connection between the server 14 of the presence and the receiving terminal will be through not shown network elements or objects.

In embodiments of the invention, the transmitting terminal 10 (which may be any of the subscribers discussed above, and may be referred to as the observed subscriber (or presentation subscriber)) will mark the tuples of presence in such a way that the receiving terminal 12 (which may be any of the subscribers discussed above, and may be referred to as an observer) and, possibly, the presence server 14 can identify various pieces of presence information and pass them to the correct application. In particular, in embodiments of the invention, a semantically meaningful application identification information field is provided in each tuple or at least some tuples. This field is called the application identifier field. The information may be identification itself or information related to identification. The sending application inserts an application-specific identifier into this application identification information field, which can be recognized at the receiving end. The receiving terminal transmits tuples to the applications in this terminal identified in the application identifier field.

This will be discussed in more detail with reference to FIG. 3. At step 1, applications 16a, 16b, and 16c located in the transmitting terminal register their application identification with the presence subsystem 18 in the terminal. After this stage, applications can begin to publish information, which is information sent to the presence server (and from there to the receiving terminal, if the observer subscribed for the presence). In the example of FIG. 3, it is shown that the terminal has three applications. This is shown only by way of example, and a terminal or other subscriber may have more or less than three applications.

In step 2, each application 16 publishes presence information in a form that contains one or more tuples, and the presence subsystem attaches the application identifier to each tuple. After that, the presence subsystem 18 forwards the information to the presence server 14. In alternative embodiments, the application may attach the application identifier.

In step 3, the presence subsystem 20 of the receiving terminal 12 receives a “register” message from the presence server 14 of the new presence information. According to the application identifier (available in each tuple), the tuples are sent to the corresponding applications 22 of the receiving terminal by the presence subsystem. Alternatively, each application can accept all tuples, but will ignore any tuple that has the wrong application identification.

Thus, each application would have its own application identifier. For example, game1, game2, SMS, IM-1, IM-2, e-MAIL. If two terminals (1 and 2) have the same application, for example IM-1, then the application identifier is the same for this application. However, if terminal 3 has an application identified by IM-2 (made, for example, by another vendor), then the application will have a different application identifier than the IM-1 application in terminals 1 and 2. In such cases, the provided attributes can be used by another application, but care should be taken as it may be possible that attributes or their values are not interpreted correctly. An example of this is when there are two different clients for IM. The basic functionality may be the same and thus the state attribute would be true, no matter which application interprets this, but the remaining attributes may or may not be appropriate at all.

Since tuples contain the identification of the application, you can provide effective (application-specific) filtering capabilities and also find the correct application for which the tuples are intended.

Tuples have a common structure, presented in draft-impp-cpim-pidf-05.txt (link: http // www.ietf.org / internet-drafts / draft-ietf-impp-cpim-pidf-05.txt). Applications can then extend the “include additional information” options by defining new XML namespaces. XML is an extensible markup language (the markup language of the World Wide Web, based on SGML and designed to remove the restriction imposed by HTML, allows the page to contain a definition and execution plan for elements, as well as their contents).

Who or what defines the various tuples to be used with different applications may vary. This may depend on the type of application. It can be determined that some or all of the tuples have a standard format (standard attributes can be defined, for example, in the 3GPP standard). Alternatively or additionally, application developers can define their own tuples.

In general, there are no limits for the number of tuples or attributes in tuples that can have one representation.

An object that places an application identifier in each tuple can be a presence subsystem or an application that publishes this information. The uniqueness of the application identifier may, in some embodiments of the present invention, require registration. This can be the case with the uniqueness of the application identifier within other applications, as well as other collections of information that need semantic meaning.

The application identifier can be used in multi-valued support and filtering. For example, an application identifier can be used to hide various levels of “accuracy” of information. In this case, the application identifier is not unique. For clarity, application information is unique in the sense that different applications do not need to use the same application identifier, but the same application identifier can be present many times in the presence server in the context of different tuples. The tuple identifier is unique, but there is the same application identifier, for example, in two or three tuples in the presentation presence information. The application identifier can then be used in filtering. In other words, the observer (receiving terminal) can set the filter so that it does not receive all available presence information from the observed subscriber (presentation). This filter can be set so that the observer only receives presence information for certain applications, the filter filters certain presence information, or a combination of these two steps is performed.

For example, the following tuples are provided to the observer (if provided by the presence server presentation) if filtering is selected so that all tuples related to the “subscriber-provided location” must be provided:

View = ABC

CORTEGE 1

Tuple ID: xyz3226

application identifier = "subscriber-provided location"

location provided by the subscriber = Fake

CORTEAGE 2

Tuple ID: xyb3293

application identifier = "subscriber-provided location"

location provided by subscriber = HOUSE

CORTEGE 3

Tuple ID: xya3288

application identifier = "subscriber-provided location"

location provided by the subscriber = x-coordinate, y-coordinate

Reference is made to FIG. 5, in which the first view 30 provides tuples 1, 2, 3, 4, and 5. Each tuple contains an application identifier, so that tuples 1 and 2 have an application identifier “A”, tuples 3 and 4 have an application identifier “B”, and a tuple 5 has an application identifier “C”. Observer 32 only wants tuples with appendix “A”. The filter 34 thus filters the tuples and provides the subscriber 32 with tuples 1 and 2. It should be understood that in practice the filter can be part of a view, part of a separate object such as a server, or part of an observer 32. The application identifier is thus used to filter tuples.

Tuples can target various subscribers. Thus, tuples 1, 3, and 5 can be for one observer, and tuples 2 and 4 for another observer. Thus, the observer may be able to “see” only tuples 1, 3, and 5. Accordingly, if the observer only wants tuples for Appendix “A”, the observer will be provided with tuple 1. Filter 34 provides this additional filtering. In some embodiments of the invention, a separate filter is provided or guiding means are provided to ensure that the observer receives only tuples intended for him.

It is also possible that different groups of observers have different presence information available to the respective groups.

Embodiments of the present invention allow applications to easily recognize from the presence information which information this particular application can interpret and understand.

It should be understood that in embodiments of the present invention, application identification can be used by the presence server when it performs a filtering operation. In some embodiments, an operator-specific application may be provided in a presence server, which would also use application identifiers. The presence server could, for example, modify some attribute values inside the tuple, which it understands and to which the subscriber has granted access to the presence server.

Embodiments of the present invention can be used for filtering. For example, an observer may request only part of the presence information that relates to one or more specific applications. Filtering can be performed by the observed presentation either by the subscriber or by the presence server, observer or any other object. The filter information can be pre-stored in such a way that whenever the presence information is provided by a specific presentation to a particular observer, it will be filtered in accordance with the required applications. Filtering can determine the required applications, unnecessary applications, or a combination of these methods.

As noted above, an observer is usually a subscriber, as discussed above. A “presentation” can be considered a subscriber and a presence server associated with that subscriber. The presence server stores presence information for subscribers who are associated with this presence server. It should be understood that in practice more than one subscriber could be associated with each server. The presence server may be located in the terminal device (in the terminal).

Presence information, as currently defined in 3GPP, may include the following information: information, but not limited to the information and requirements of step 1 (requirements group), working on standards, should develop a concept that enables the expansion of presence.

Subscriber Status Network status means of communication; Contact address provided by the Subscriber location; network-provided location; text; a priority.

The presence may also include other information such as mood, favorite color, etc.

It should be understood that embodiments of the invention are not limited to an attribute called application identification information, but can also be applied to any attribute providing this type of operational capability.

Embodiments of the present invention are not limited to the use of tuples. Not all systems use tuples to structure a presence document, for example, a wireless rural presence processes presence information at an attribute level, in which case the application identifier is associated with each individual attribute.

FIG. 4 shows schematically an IMS network 100. The IMS includes various elements, including several call status monitoring (CSCF) functions. CSCF is equivalent to the SIP server in the IETF architecture.

The Requesting CSCF (I-CSCF) 201 is the IMS base node used to terminate calls in the IMS network operating on the edge of this network. Communication with external nodes of the mobile terminal 101, PDA 113, and application server 121 is shown here. It should be understood that the connections between the mobile terminal, the PDA and the application server to the I-CSCF may not be direct, but through a suitable intermediate network, such as the mobile core network 110 for the mobile terminal, and the Internet 120 for the application server, as shown in FIG. one.

HSS 202 is a centralized subscriber database that interfaces with both I-CSCF and S-CSCF 204, storing information for all IMS subscribers. The I-CSCF uses the HSS to perform functions such as authorizing new subscribers and retrieving S-CSCF routing information to move messages from external elements to the S-CSCF.

The S-CSCF is the IMS host responsible for the launch of services related to IMS subscribers. In this example, the S-CSCF also implements the functionality of the serving call state monitoring function for IMS subscribers by processing subscriber registrations. The functionality of the presence server is implemented as an application server.

It should be understood that the description of FIG. 4 is only a schematic representation and, in practice, additional elements, such as, for example, the CSCF intermediary program (P-CSCF), are somewhat out of the sentence. It should also be understood that embodiments of the invention may be used in systems other than the systems shown in FIG. four.

The presence module can be used to subscribe to presence information by any subscriber. The semantics of the presence module means that any subscriber can send a subscription message for presence information to the presence server, but if there is no such specific presence module, the presence server will not be able to recognize what event the subscriber tried to subscribe to. Therefore, it is necessary that the presence module is defined on the presence server, which can then receive and recognize the subscription message for the associated event for changes in the presence information. The presence server creates a state associated with the presence information, and when there is any change in the presence information, it will trigger a response or notification.

It should be understood that although embodiments of the present invention have been described in the context of 3G using SIP, other suitable interface systems and protocols could be used. In particular, embodiments of the invention may be used in an application in accordance with the IETF specifications.

It should also be noted here that although the foregoing describes exemplary embodiments of the invention, there are several variations and modifications that can be made to the described solution without going beyond the scope of the invention defined in the attached claims.

Claims (23)

1. A communication system comprising at least one subscriber equipment to which the presence information is associated, wherein the presence information contains a plurality of parts, wherein at least one of said parts contains information identifying an application in at least one other subscriber equipment for which said at least one portion is intended; and, at least one other subscriber equipment for which presence information is provided associated with said at least one subscriber equipment, wherein at least one other subscriber equipment has at least one application, wherein, at least one other subscriber equipment is configured to use said identifying information to obtain intended at least one piece of presence information for said at least one application at least one other subscriber equipment. 2. The system of claim 1, wherein said at least one other subscriber equipment comprises means for receiving said at least one portion of said information. 3. The system of claim 2, wherein said at least one other subscriber equipment comprises means for directing said at least one portion of said information to an identified application. 4. The system according to claim 3, in which the said means for directing contains an application subsystem. 5. The system of claim 1, wherein said at least one other subscriber equipment receives said at least one piece of said information in response to a request from at least one other subscriber equipment. 6. The system of claim 1, wherein said at least one subscriber equipment comprises at least one application. 7. The system of claim 1, wherein the at least one subscriber equipment comprises a presence subsystem. 8. The system according to claim 7, in which said at least one application is configured to register said subsystem for the presence of said information identifying said application. 9. The system according to claim 7, in which at least one of: said at least one application and said presence subsystem is configured to add said identification information to at least one part. 10. The system of claim 1, wherein said presence information comprises at least one of the following pieces of information: Subscriber status network status; means of communication; contact address provided by the subscriber location; Network location text; a priority; mood, favorite color. 11. The system according to claim 1, in which the system operates in accordance with a session initialization protocol (SIP). 12. The system of claim 1, wherein said piece of information comprises a tuple. 13. The system of claim 12, wherein said tuple comprises information identifying said subscriber equipment and information identifying said application. 14. The system of claim 1, wherein said at least one other subscriber equipment is configured to request only one or more portions of said presence information processed by one or more applications of said at least one other subscriber equipment. 15. The system of claim 14, wherein filtering means are provided to provide only requested portions of said presence information. 16. The system of claim 15, wherein said filtering means is provided in at least one of: a server; a presence server and said at least one subscriber equipment. 17. The system of claim 1, wherein said at least one other subscriber equipment is configured to use said information to filter said presence information. 18. The system of claim 1, wherein said application of at least one other subscriber equipment is configured to process at least one part of presence information that contains information identifying said application. 19. The communication method, which consists in the fact that provide presence information for the associated equipment of the subscriber, wherein the presence information contains a plurality of parts, wherein at least one of said parts contains information identifying an application for which said at least one part is intended; and receive through at least one other subscriber equipment, at least one of these parts, and at least one other subscriber equipment has at least one application, wherein at least one other subscriber equipment is configured to use said identifying information to obtain intended at least one piece of presence information for said at least one application of at least one other subscriber equipment. 20. The method of claim 19, wherein said at least one other subscriber equipment is processed in said application of at least one piece of presence information that contains information identifying an application of said other subscriber equipment. 21. Subscriber equipment in a communication system, said subscriber equipment comprising, at least one application configured to publish presence information, the presence information comprising a plurality of parts, wherein at least one of said parts has information identifying the application in other equipment of the subscriber for whom said at least , one part, and a presence subsystem configured to direct said presence information. 22. Subscriber equipment in a communication system, comprising, at least one application, and a presence subsystem for receiving at least one part of the presence information associated with other subscriber equipment, wherein at least one part contains information identifying an application of said subscriber equipment, wherein the presence subsystem is configured to receive at least a part containing information identifying said at least one application, and directing presence information to a corresponding application identified by said identifier itsiruyuschey information. 23. The subscriber equipment of claim 22, wherein the application identified in said at least one part is configured to process said at least one part of presence information that contains information identifying said application.

Images