DESCRIPTION

COMMUNICATION TERMINAL, METHOD FOR CONTROLLING COMMUNICATION TERMINAL

TECHNICAL FIELD

[0001] The present invention relates to a technology in which the communication terminal obtains another communication terminal's identifier as basis for session re-direction.

BACKGROUND

[0002] Communication terminals such as mobile phones and personal computers (PCs), etc. are well known. Such communication terminals are capable of establishing a communication session with a communication node such as a multimedia server, another communication terminal, etc. For example, a mobile phone user can view a movie by establishing a video streaming session between their mobile phone and a streaming video server. [0003] A situation can arise in which a user would like to redirect their ongoing communication session to another communication terminal. For example, a user returns home and would like to redirect their ongoing streaming video session from their mobile phone to their

home PC in order to watch the movie on a larger display. Similarly, when a user leaves home, the user may wish to redirect their ongoing communication session from their home PC to their mobile phone in order to continue viewing a movie after leaving.

[0004] In order to perform such communication session redirection, the user must inform the streaming video server of the new target communication terminal. For example, in the case of communication terminals using the Session Initiation Protocol (SIP), if the ongoing communication .session was initiated by means of SIP, the user can redirect the session by sending a SIP INVITE message with the target terminal's SIP URI (Universal Resource Identifier) to the streaming video server.

[0005] However, to do so the user must know the target terminal's SIP URI and send it to the streaming video server. This is cumbersome for the user for several reasons.

[0006] - There is no standard way for the user to know the SIP URI of the target terminal. For example, some PCs may present a SIP URI on the display when the user clicks on a dedicated icon; some SIP-enabled Personal Digital Assistants (PDAs) may present a SIP URI when the

user pushes a dedicated button. These varying processes significantly degrade usability in finding the SIP URIs of the target terminals since the user must know in advance how to locate the SIP URI for each target terminal to be used, and then take action to manipulate the target terminal in order to retrieve the SIP URI. [0007] - After the user has retrieved the SIP URI of the target terminal, cumbersome manual operations are still required for the user to input the SIP URI of the target terminal into the originating terminal. These operations are especially cumbersome, for example, when a mobile phone, which may have a crude input device, serves as the originating terminal. [0008] - Input operations of the SIP URI may be simplified if the user registers, in advance, the SIP URIs of frequently-used target terminals in, for example, an electronic phonebook. However, the user must still perform cumbersome manual operations to open the phonebook, search for and select the entry of the target terminal - requiring, for example, button-based menu navigation on a mobile phone. Moreover, if arbitrary terminals located in public spaces (e.g., cafeterias, shops, stations, museums, etc.) are to serve as target terminals, the

electronic phonebook will not work effectively because the user cannot know the SIP URI of these terminals in advance and is thus forced to repeat manual input whenever the user wishes to use them.

SUMMARY

[0009] The feature of the present invention is to solve the pre-existing problem.

[0010] According to an aspect of the present invention, there is provided a communication terminal comprising an establishing means for establishing a communication session with a communication node by sending a request for establishment to the communication node. The communication terminal further comprises an obtaining means for obtaining a first identifier from an object that is associated with an alternative communication terminal. The first identifier identifies the alternative communication terminal. The communication terminal further comprises a redirecting means for redirecting the communication session to the alternative communication terminal by sending a request for redirection to the communication node. The request for redirection includes the first identifier.

[0011] According to another aspect of the present invention, there is provided a communication terminal comprising an establishing means for establishing a communication session with a communication node, the communication session being redirected from an originating communication terminal. The communication terminal further comprises an object which provides the originating communication terminal with a first identifier which identifies the communication terminal.

[0012] According to another aspect of the present invention, there is provided a method for controlling a communication terminal comprising an establishing step of establishing a communication session with a communication node by sending a request for establishment to the communication node. The method further comprises an obtaining step of obtaining a first identifier from an object that is associated with an alternative communication terminal. The first identifier identifies the alternative communication terminal. The method further comprises a redirecting step of redirecting the communication session to the alternative communication terminal by sending a request for redirection to the communication node. The

request for redirection includes the first identifier .

[0013] The main advantage of the present invention is as follows. When a user wishes to redirect an ongoing communication session from the communication terminal currently being used to an alternative communication terminal, the cumbersome operations which are caused by the user needing to know and input the terminal identifier of the alternative communication terminal are dramatically reduced because the communication terminal obtains the identifier from an object which is associated with the alternative communication terminal. [0014] Further features of the present invention will become apparent from the following description of exemplary embodiments with reference to the attached drawings, in which like reference characters designate the same or similar parts throughout the figures thereof.

BRIEF DESCRIPTION OF DRAWINGS

[0015] Fig. 1 illustrates an overview of the communication system according to the embodiment; [0016] Fig. 2 illustrates an exemplary configuration of the communication system according to the embodiment;

[0017] Fig. 3 is a sequence diagram showing the process of establishing the communication session between a mobile phone and a streaming video server;

[0018] Fig. 4 is a sequence diagram showing the process of redirecting the communication session, which is established in Fig. 3, from a mobile phone to a TV;

[0019] Fig. 5 is a sequence diagram showing the process in which a mobile phone regains the communication session, which is redirected in Fig. 4, from a TV;

[0020] Fig. 6 illustrates another exemplary configuration of the communication system according to the embodiment;

[0021] Fig. 7 illustrates an example of a SIP REGISTER message sent by the TV;

[0022] Fig. 8 illustrates an example of a SIP INVITE message sent by the mobile phone; and [0023] Fig. 9 illustrates yet another exemplary configuration of the communication system according to the embodiment.

DETAILED DESCRIPTION

[0024] Hereinafter, preferred embodiments of the present invention will be described. In the embodiments, it is assumed that each entity

(e.g., a mobile phone, PC, a streaming video server, etc.) is SIP-enabled and they are connected to a network capable of carrying SIP control messages. Herein we will refer to such a network as a "SIP network". It should be noted that the concept of the present invention can be applied to any type of communication network in which each entity can be identified by some' sort of identifier and the ongoing communication session can be redirected from one entity to another entity.

[0025] Fig. 1 illustrates an overview of a communication system 100 according to the embodiment. The communication system 100 comprises a communication node 101 and communication terminals 102 and 103, and they can communicate with each other via the SIP network 104.

[0026] The communication node 101 may be any type of SIP-enabled device such as a streaming video server, a mobile phone, a personal computer (PC), a television (TV), etc.

[0027] The communication terminals 102 and 103 may be SIP-enabled devices of any type (e.g., a mobile phone, PC, TV, etc.) . In the present embodiment, it is assumed that the communication terminal 102 has an ongoing (i.e., established)

communication session with the communication node 101, and redirects the ongoing communication session to the communication terminal 103. In other words, the communication terminal 102 is an originating terminal and the communication terminal 103 is a target terminal.

[0028] In the communication system 100, there is an object 105 associated with the communication terminal 103. The object 105 may be a memory, a memory writer, an image (e.g. two- dimensional bar code), etc. The object 105 may be built into the communication terminal 103, or it may be external to the communication terminal 103. For example, the object 105 may be two- dimensional bar code that is printed, for example, on paper, and this paper may be affixed to the communication terminal 103. Alternatively, this paper may be placed separately from the communication terminal 103 as long as the user can recognize the association between the paper (the object 105) and the communication terminal 103.

[0029] To perform session redirection, the communication terminal 102 obtains the SIP ,URI of the communication terminal 103 from the object 105. For example, if the object 105 is a memory in which the SIP URI of the communication

terminal 103 is stored, the communication terminal 102 may have a memory reader and obtain the SIP URI via the memory reader. Alternatively, if the object 105 is a memory writer, the communication terminal 102 may have a memory and obtains the SIP URI when the memory writer writes the SIP URI on the memory. Alternatively, if the object 105 is a two- dimensional bar code, the communication terminal 102 may have a camera and obtain the SIP URI by capturing the two-dimensional bar code as image data, e.g. presented at a display of terminal 103, and then converting it into text data. [0030] Since the communication terminal 102 is capable of obtaining the SIP URI of the communication terminal 103 via the object 105, cumbersome operations requiring the user to know and input a SIP URI are reduced.

[0031] After acquisition of the SIP URI, the communication terminal 102 can redirect the session using any of the known technologies for doing so. For example, via the SIP network 104, the communication terminal 102 may send a SIP INVITE message to the communication terminal 103 and thereby receives a Session Description Protocol (SDP) message describing the capabilities and session initialization of a

device (hereinafter, "an SDP message") of the communication terminal 103. Then, using SDP, the communication terminal 102 sends to the communication node 101 a ReINVITE message, which includes the SIP URI of the communication terminal 103, as a request for redirection. Finally, the communication node 101 stops the ongoing session and establishes the new session (i.e., the redirected session) with the communication terminal 103.

[0032] While no technical distinction need exist between them, for purposes of clarity, herein a distinction is drawn between a "communication terminal", referring to a device which initiates communication session redirection and/or receives the redirected session, and a "communication node", referring to the device with which the communication terminal is communicating. Communication nodes and communication terminals may share the same functionality and in some cases may be the same devices .

[0033] Hereinafter, the embodiment is described in more detail with reference to Fig. 2. In Fig. 2, it is assumed that the communication node 101 is a streaming video server 201, the communication terminal 102 is a

mobile phone 202, and the communication terminal 103 is a TV 203.

[0034] It should be noted that the components contained in the mobile phone 202 and the TV 203 are typically implemented by a combination of hardware and software (i.e., computer programs executed by the processor (not shown) ) , but they may also be implemented in dedicated hardware. [0035] The mobile phone 202 comprises a SIP unit 221 and an obtaining unit 222. The TV 203 comprises a SIP unit 231 and an object 105, although the object 105 may be external to the TV 203, as described above. The streaming video server 201, the SIP unit 221, and the SIP unit 231 can communicate with each other via SIP network 104 (not shown in Fig. 2) . [0036] The SIP unit 221 comprises an establishing unit 223 and a redirecting unit 224. [0037] The establishing unit 223 establishes a video streaming session with the streaming video server 201 by sending a request for establishment, which typically includes a SIP INVITE message, to the streaming video server 201. Details of the session establishment process will be explained later with reference to Fig. 3. [0038] The redirecting unit 224 redirects the

established session to the TV 203 by sending a request for redirection, which typically includes a SIP ReINVITE message, to the streaming video server 201. Details of the session redirection process will be explained later with reference to Fig. 4.

[0039] The SIP unit 221 may also comprise a regaining unit 225. The regaining unit 225 regains the redirected session from the TV 203 by sending a regaining request, which typically includes a SIP ReINVITE message, to the streaming video server 201. Details of the session regaining process will be explained later with reference to Fig. 5.

[0040] The obtaining unit 222 obtains the SIP URI of the TV 203 from the object 105. Implementation of the obtaining unit 222 varies depending upon the implementation of the object 105, and vice versa. For example, the obtaining unit 222 may comprise a memory reader 226, and the object 105 may comprise a memory 233 in which the SIP URI of the TV 203 is stored. In this case, the SIP unit 231 writes the SIP URI of the TV 203 on the memory 233, and the memory reader 226 retrieves the SIP URI from the memory 233. When the SIP URI of the TV 203 changes, the SIP unit 231 may update the content of the memory

233 .

[0041] Alternatively, the obtaining unit 222 may comprise a memory 227, and the object 105 may comprise a memory writer 232. In this case, the memory writer 232 writes the SIP URI of the TV 203, which has been received from the SIP unit 231, to the memory 227.

[0042] Alternatively, the obtaining unit 222 may comprise a capturing/converting unit 228, and the object 105 may comprise an image 234, which represents the SIP URI of TV 203. The image 234 may be a bar code, a two-dimensional bar code, text representing the SIP URI, etc. In this case, the capturing/converting unit 228, which may comprise a camera, captures the image 234 as image data. Then, the capturing/converting unit 228 converts the image data into the SIP URI. In case that the image 234 is text representing the SIP URI, for example, the capturing/converting unit 228 may comprise Optical Character Reader (OCR) functionality, which converts text into electronic form. The image 234 may be printed on paper in advance. Alternatively, the processor (not shown) of the TV 203 may generate the image 234 and display it on the display (not shown) of the TV 203. In this case, when the SIP URI of TV 203 changes, the image 234 can be updated. In

some embodiments, the capturing/converting unit 228 may capture the image of the target communication terminal itself. In this case, the capturing/converting unit 228 identify the target communication terminal by performing any known image recognition process, and obtains the SIP URI based on the result of the image recognition, for example from a database.

[0043] After the obtaining unit 222 obtains the SIP URI of the TV 203, the redirecting unit 224 receives the SIP URI from the obtaining unit 222 and redirects the ongoing session to the TV 203.

[0044] In some embodiments, the object 105 may include status information (e.g. "free" or "busy") which indicates whether or not the TV 203 accepts the session redirection initiated by the redirecting unit 224. For example, if the TV 203 has already had an established communication session, the status information may be "busy". The obtaining unit 222 obtains the status information as well as the SIP URI from the object 105, and the redirecting unit 224 redirects the ongoing session to the TV 203 if the status information indicates that the TV 203 accepts the session redirection (i.e., "free"). s described above, the object 105 may comprise

the image 234 (a bar code, a two-dimensional bar code, etc.) and may be displayed on the display (not shown) of the TV 203. In this case, the TV 203 may infer the status information by displaying the image 234 only when the TV 203 accepts the session redirection (i.e., "free"). If the image 234 is not displayed, the user of the mobile phone 202 may aware that the TV 203 will not accept the session redirection. [0045] The SIP Unit 231 comprises an establishing unit 235. The establishing unit 235 establishes a communication session, which is redirected from the mobile phone 202, with the streaming video server 201.

[0046] The SIP Unit 231 may also comprise a redirecting unit 236 that redirects (returns) the redirected session to the mobile phone 202. In the present embodiment, the redirection by the redirecting unit 236 is triggered by a BYE message sent from the regaining unit 225 (see Fig. 5) .

[0047] The salient feature of the implementation of the afore-described obtaining unit 222 and object 105 is that, in contrast with conventional solutions, only a few operations are required for the user of the mobile phone 202 to obtain the SIP URI of the TV 203 and input it

into the SIP unit 221. Accordingly, the user is relieved from the cumbersome operations encountered with conventional solutions when redirecting the ongoing session to an alternative communication terminal.

[0048] It should be noted that other implementations of the obtaining unit 222 and the object 105 are also possible as long as the reduction in user operations is maintained. [0049] Hereinafter, the detailed processes of session establishment, session redirection and session regaining are described with reference to Figs. 3-5. In the present embodiment, it is assumed that Third Party Call Control (3PCC) [1] is employed, but other technologies may also be employed .

[0050] In Figs. 3-5, it is assumed that the streaming video server 201 has SIP URI "svs@op.net", the mobile phone 202 ^λλ mp@oρ . net", and the TV 203 ^λλ tv@op . net" .

[0051] Fig. 3 is a sequence diagram showing the process of establishing the communication session (video streaming session) between the mobile phone 202 and the streaming video server 201.

[0052] In step S301, the establishing unit 223 of the mobile phone 202 sends a SIP INVITE

message to the streaming video server 201. The SIP INVITE message includes an SDP message describing the mobile phone 202. [0053] In step S302, the streaming video server 201 returns a 200 OK message, which includes an SDP message describing the streaming video server 201, to the establishing unit 223. [0054] In step S303, the establishing unit 223 sends an ACK message to the streaming video server 201, and the communication session is then established .

[0055] Fig. 4 is a sequence diagram showing the process of redirecting the communication session, which is established in Fig. 3, from the mobile phone 202 to the TV 203.

[0056] In step S401, the obtaining unit 222 obtains the SIP URI of the TV 203 from the object 105.

[0057] In step S402, the redirecting unit 224 sends an INVITE message to the TV 203, which is identified by the SIP URI obtained in step S401. The process in this step may be triggered by the acquisition of the SIP URI in step S401, or may be triggered by a user operation on the mobile phone 202.

[0058] In step S403, the TV 203 returns a 200 OK message, which includes an SDP message

describing the TV 203, to the redirecting unit 224. In some embodiments, the SDP message may include the state (i.e., "free" or "busy") of the TV 203.

[0059] In step S404, the redirecting unit 224 sends a ReINVITE message to the streaming video server 201, including in it the SDP message received in step S403.

[0060] In step S405, the streaming video server 201 returns a 200 OK message to the redirecting unit 224, including in it an SDP message description of the streaming video server 201.

[0061] In step S406, the redirecting unit 224 returns an ACK message to the streaming video server 201, and in step S407, the redirecting unit 224 returns an ACK message to the TV 203, including in it the SDP message received in step S405. The communication session is then redirected from the mobile phone to the TV 203. In other words, the (redirected) communication session is established between the streaming video server 201 and the TV 203. Note the mobile phone 202 still maintains two SIP dialogs; one is between the mobile phone 202 and the streaming video server 201 and the other is between the mobile phone 202 and the TV 203. These SIP

dialogs are necessary for the mobile phone 202 to regain the redirected communication session afterward as described in Fig. 5.

[0062] Fig. 5 is a sequence diagram showing the process in which the mobile phone 202 regains from the TV 203, the communication session, which was redirected in Fig. 4.

[0063] In step S501, the regaining unit 225 sends a ReINVITE message to the streaming video server 201 within the maintained SIP dialog between the mobile phone 202 and the streaming server 201, including in it an SDP message describing the mobile phone 202. The SDP message includes the SIP URI of the mobile phone 202.

The process in this step may be triggered, for example, by user operation of the mobile phone

202.

[0064] In step S502, the streaming video server 201 returns a 200 OK message to the regaining unit 225, including in it the SDP message describing the streaming video server

201.

[0065] In step S503, the regaining unit 225 sends a BYE message to the TV 203 within the maintained SIP dialog between the mobile phone

202 and the TV 203. ^■

[0066] In step S504, the TV 203 returns a 200

OK message to the regaining unit 225. At this time, the SIP dialog between the mobile phone 202 and the TV 203 is terminated.

[0067] In step S505, the regaining unit 225 returns an ACK message to the streaming video server 201. The communication session is then re-established between the streaming video server 201 and the mobile phone 202. In other words, the mobile phone 202 regains the communication session, which was redirected in Fig. 4. [0068] In the embodiment described above, the mobile phone 202 and the TV 203 directly send and receive messages (e.g., INVITE, ACK, etc.); likewise, the mobile phone 202 and the streaming video server 201 also directly send and receive messages .

[0069] However, it should be noted, for example, that an entity (e.g., an IMS (IP Multimedia Subsystem) application server) , which functions as a Back-to-Back User Agent (B2BUA) may be introduced. In this case, the redirecting unit 224 sends a ReINVITE message to the IMS application server in order to redirect the ongoing session.

[0070] In other words, the messages shown in Figs. 3-5 are not necessarily communicated directly between the streaming video server 201,

the mobile phone 202, and the TV 203; they may be communicated indirectly via another entity. In this case, the content and the sequence of the messages may be modified to suit the implementation of the entity introduced. [0071] In some embodiments, the obtaining unit 222 obtains a type of identifier for the TV 203 distinct from the SIP URI. The identifier may, for example, be a number uniquely associated with each communication terminal (hereinafter, "unique number"), the MAC (Media Access Control) address of the communication terminal, etc. [0072] This embodiment is advantageous in that the user cannot obtain the SIP URI of the TV 203 directly from the TV 203 identifier. This is because unrestricted disclosure of the SIP URIs of communication terminals to other terminals may lead malicious accesses (attacks) on the communication terminals. Accordingly, this embodiment improves the security of the communication system 100 (see Fig. 1) . [0073] This embodiment is also advantageous when the object 105 can only provide the obtaining unit 222 with a relatively limited amount of information. For example, a one- dimensional bar code usually cannot be made to store enough information to represent any

possible SIP URI, but a one-dimensional bar code can be made to store enough information to represent all possible numbers in the communication system 100.

[0074] Hereinafter, this embodiment is described with reference to Fig. 6, where it is assumed that a unique number is used as an identifier for explanatory purposes. [0075] A SIP server 601 works as a B2BUA and translates the unique numbers into .SIP URIs by accessing a storage 602.

[0076] The storage 602 stores the unique numbers in association with the SIP URIs of each communication terminal such as the TV 203. [0077] It should be noted that the storage 602 may be built into the SIP server 601. [0078] The unique number is, for example, generated in the TV 203 and stored in the storage 602 when the TV 203 is registered with the SIP server 601. Fig. 7 illustrates an example of a SIP REGISTER message sent by the TV 203. As shown, the unique number 912687 is suffixed to the SIP URI of the TV 203. Alternatively, the SIP REGISTER message may have a dedicated header (which represents the unique number), or the body of the SIP REGISTER message may include the unique number.

[0079] If this number has already been associated with another communication terminal in the storage 602, the SIP server 601 rejects the SIP REGISTER message. The TV 203 then generates another number (e.g., by using time as seed for a random number generator (not shown)) and sends another SIP REGISTER message to the SIP server 601.

[0080] When the mobile phone 202 redirects the ongoing session to the TV 203, the obtaining unit 222 obtains the unique number ("912687") from the object 105, and the redirecting unit 224 sends a SIP INVITE message, which includes the unique number, to the SIP server 601 instead of the TV 203. Fig. 8 illustrates an example of a SIP INVITE message sent by the redirecting unit 224.

[0081] Then, the SIP server 601 retrieves the SIP URI of the TV 203 from the storage 602, and the redirection is performed.

[0082] In some embodiments, the obtaining unit 222 and the object 105 may be capable of Near Field Communication (NFC) [2]. In this case, because the user only need bring the mobile phone 202 within close range of the object 105 to obtain the identifier (e.g., a SIP URI, a unique number, etc.) of the TV 203, the number of user

operations required to conduct session redirection can be dramatically reduced. In other words, if the obtaining unit 222 falls within communication range of an NFC-capable object 105 while the communication session is ongoing, the obtaining unit 222 may obtain the identifier of the TV 203 and the redirecting unit can redirect the ongoing session to the TV 203. [0083] Further, in some embodiments the mobile phone 202 comprises a notification unit 901, and the TV 203 comprises an obtaining unit 902 and a notifying unit 903 as shown in Fig. 9. The obtaining unit 222 obtains the identifier of TV 203 from the notifying unit 903 in conformance with NFC, and the obtaining unit 902 obtains the identifier of the mobile phone 202 from the notifying unit 901 in conformance with NFC. In other words, the obtaining unit 222 and the notifying unit 901 form an NFC unit 904. Also, the obtaining unit 902 and the notifying unit 903 form an NFC unit 905. The NFC unit 905 is one implementation of the object 105, and the NFC unit 904 is one implementation of an object which is associated with the mobile phone 202. The NFC units 904 and 905 exchange the identifier of the mobile phone 202 and the TV 203. [0084] In this case, the TV 203 may know the

identifier of the mobile phone 202 and the redirecting unit 236 redirects (returns) the redirected session to the mobile phone 202 by sending a request for return to the streaming video server 201. Accordingly, the mobile phone 202 can regain the redirected session without the regaining unit 225 (see Fig. 2). In other words, if the notifying unit 901 falls within NFC communication range with the obtaining unit 902 while the redirected communication session is ongoing, the notifying unit 901 notifies the obtaining unit 902 of the identifier of the mobile phone 202, and the redirecting unit 236 returns the redirected communication session to the mobile phone 202.

[0085] Furthermore, in the embodiment shown in Fig. 9, the TV 203 may initiate a communication session with the streaming video server 201 and redirect it to the mobile phone 202. In other words, communication terminals such as the mobile phone 202 and the TV 203 shown in Fig. 9 can handover ongoing communication sessions with each other any time they are brought within NFC communication range. Thereby, both the number and the cumbersome nature of the operations required for the user to initiate redirect (handover) communication sessions are

drastically reduced.

[0086] In some embodiments, the NFC units 904 and 905 may be used for charging. For example, the NFC unit 904 is equipped with electronic money functionality. The TV 203 is set in the hotel room (or in the airplane, train, cyber cafe, etc.) and the hotel manager (or the airline company, the railway company, the cyber cafe manager, etc.) wishes to charge the user of the mobile phone 202 for the use of the TV 203. In this case, the NFC unit 905 may subtract the electronic money value of the NFC unit 904 when the obtaining unit 222 obtains the identifier of the TV 203 thereby charging is accomplished. [0087] As described above, according to the present invention, the communication terminal (e.g., a mobile phone) comprises an obtaining unit (e.g., a memory reader) that obtains the identifier (e.g., a SIP URI) from an object (e.g., a memory), which is associated with another (alternative) communication terminal (e.g., a TV) . After the acquisition of the identifier of the alternative communication terminal, the communication terminal redirects the ongoing communication session to the alternative communication terminal. [0088] Accordingly, when the user wishes to

redirect the ongoing communication session from the communication terminal to an alternative communication terminal, the cumbersome operations, which require the user to know and input the identifier of the alternative communication terminal, are dramatically reduced.

[0089] While the present invention has been described with reference to exemplary embodiments, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. The scope of the following claims is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures and functions .

[0090] Abbreviations:

PC Personal Computer

SIP Session Initiation Protocol

URI Universal Resource Identifier

PDA Personal Digital Assistant

SDP Session Description Protocol

OCR Optical Character Reader

3PCC Third Party Call Control

IMS IP Multimedia Subsystem

B2BUABack-to-Back User Agent

MAC Media Access Control

NFC Near Field Communication

[0091] References:

[1] Best Current Practices for Third Party Call

Control (3PCC), J. Rosenberg et al., RFC3725,

2004-04

[2] ISO/IEC 18092 Near Field Communication -

Interface and Protocol (NFCIP-I), http: //standards. iso. org/ittf/PubliclyAvailableSt andards/c038578_ISO_IEC_18092_2004 (E) . zip