FORM 2
The Patent Act 1970
(39 of 1970)
&
The Patent Rules, 2005

COMPLETE SPECIFICATION
(SEE SECTION 10 AND RULE 13)

TITLE OF THE INVENTION

“Selection of Preferred Charging Scheme”

APPLICANTS:

Name Nationality Address
Alcatel Lucent France 54 rue de la Boétie, 75008 Paris, France.

The following specification particularly describes and ascertains the nature of this invention and the manner in which it is to be performed:-

TECHNICAL FIELD
[001] The present invention relates to communication systems and, more particularly, to multiple communication terminals belonging to subscribers in communication systems.

BACKGROUND
[002] Users use a communication terminal for establishing and maintaining a communication session with other users. Some users may have multiple communication terminals with which they can establish communication sessions. Each communication terminal may have subscriptions with different service providers and each communication terminal may also have different charging schemes. Charging scheme is the billing method used to determine the fee a user has to pay for using the network resources.
[003] For example, the user may have a first communication terminal on a subscription with service provider 1 and a second communication terminal on a subscription with service provider 2. Service provider 1 may allow the user to establish a communication session using the first communication terminal with a charging scheme 1 and service provider 2 may allow the user to establish a communication session using the second communication terminal with a charging scheme 2. The user may prefer to avail of charging scheme 1 rather than charging scheme 2 at a particular point in time. However, the user may not have access to both the communication terminals at a particular point in time. If the user does not have access to the communication terminal having the preferred charging scheme, the user would not be able to avail of the preferred charging scheme for a communication session although the user has subscribed for the charging scheme.
[004] Let us consider another example where a user has a land line phone and a cell phone, the charging scheme of the land line phone being more economical for long distance calls than the charging scheme of the cell phone. If the user only has access to the cell phone at a particular instant in time, then the user would not be able to avail of the charging scheme of the land line phone while making a long distance call.

SUMMARY
[005] In view of the foregoing, an embodiment herein provides a method for enabling a user to select a charging scheme associated with a first communication terminal, wherein the user is currently using a second communication terminal. The user using the second communication terminal to send a request to a network for applying the charging scheme to a communication session and the network charging the communication session based on the charging scheme of the first communication terminal. The user subscribes to the service of being able to choose a preferred the charging scheme from among the multiple charging schemes subscribed to by the user. The request includes number of the first communication terminal. The network creates a unique identification means for the user on receiving the request. The unique identification means is linked to atleast one of subscription id of the user, IP Multimedia Private Identity (IMPI) of the first and second communication terminals and IP Multimedia Public Identity (IMPU) of the first and second communication terminals. The unique identification means indicates the preferred charging scheme chosen by the user. The communication session is established by the user using the second communication terminal.
[006] Embodiments further disclose an application server for enabling a user to select a charging scheme associated with a communication terminal, wherein the user is currently using a second communication terminal. The application server receives a request for applying a charging scheme associated with a first communication terminal to a communication session, wherein the request is sent by the user using a second communication terminal. The application server creates a unique identification means for the user and links the unique identification means to the subscription details of the user and the communication session is charged based on the charging scheme of the first communication terminal. The unique identification means indicates the preferred charging scheme chosen by the user. The application server is adapted to store subscription details of the user and the application server is adapted to extract number of the first communication terminal from the request. The subscription details of the user may be atleast one of atleast one of a subscription id of the user, IP Multimedia Private Identity (IMPI) of the first and second communication terminals and IP Multimedia Public Identity (IMPU) of the first and second communication terminals.
[007] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES
[008] The embodiments herein will be better understood from the following detailed description with reference to the drawings, in which:
[009] FIG. 1 illustrates a block diagram of a user with multiple endpoints in an IMS network, according to an embodiment herein;
[0010] FIG. 2 illustrates a block diagram of a user with multiple endpoints belonging to different networks connected to an IMS network, according to an embodiment herein;
[0011] FIG. 3 illustrates a block diagram of an application server, according to an embodiment herein;
[0012] FIG. 4 is a flowchart depicting a method for selecting a preferred charging scheme, according to an embodiment herein;
[0013] FIG. 5 illustrates a flow diagram for selecting a preferred charging scheme for a communication session, according to an embodiment herein; and
[0014] FIG. 6a and FIG. 6b are flowcharts depicting a method for selecting a preferred charging scheme for a communication session, according to an embodiment herein.

DETAILED DESCRIPTION OF EMBODIMENTS
[0015] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0016] The embodiments herein disclose methods and systems for allowing a user having multiple communication terminals to start a communication session using any available terminal and being charged for the communication session with the charging scheme of any preferred communication terminal. Even if the user has access to only one communication terminal, the user would be able to start a communication session using the available terminal and choose a preferred charging scheme associated with any of the user’s communication terminals. Referring now to the drawings, and more particularly to FIGS. 1 through 5, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.
[0017] FIG. 1 illustrates a block diagram of a user with multiple endpoints in an IMS network. A user may have multiple communication terminals using which the user can start a communication session with another user. The communication terminal may also be called as an endpoint in a communication session between two users. For example, endpoint 1 101 may be an office land line phone, endpoint 2 102 may be a residence land line phone and endpoint 3 103 may be a cell phone. The user may have multiple endpoints for a single subscription or multiple endpoints for multiple subscriptions. The user may also have a single endpoint for a single subscription and multiple such subscriptions. For example, the user may have two cell phones with the service provider A1 or the user may have one cell phone with the service provider A2 and one cell phone with the service provider A1. The user may have different charging schemes for different endpoints. For example, the user may be charged INR 1 for two minutes per call using the land line phone and the user may be charged INR 2 per minute for a call using the cell phone. If the user has access to only one endpoint, the user can start a communication session using the available endpoint and be charged for the communication session based on the charging scheme of a different endpoint. For example, if the user has access to endpoint 3 103, the user can start the communication session using endpoint 3 103 and be charged for the communication session based on the charging scheme of endpoint 1 101.
[0018] To avail of the service to be able to choose a preferred charging scheme, the user has to subscribe to the service. For example, the user may subscribe to the service by sending a service activation code to the AS 105 and the code sent may be ACT #5656. After subscribing to the service, the user can choose a preferred charging scheme from among the charging schemes to which the user has subscribed. If the user has access to only one endpoint and the user wants to be charged for the communication session based on the charging scheme of a different endpoint, then the user sends a service code message to a Call Session Controller (CSC) 104, using the first endpoint, to invoke the service. The number of the endpoint whose charging scheme is to be used for the communication session is also included with the service code message. For example, if the user has access to endpoint 1 101 and the user wants to be charged for the communication session based on the charging scheme of endpoint 2 102, then the user sends the service code message to the CSC 104 using endpoint 1 101. The service code and the end point number sent may be #955 987-654-3210. The service code message and the endpoint 2 102 number may be sent to the CSC 104 in an invitation message. The CSC 104 provides communication session control in an Internet Protocol Multimedia Services (IMS) network. The CSC 104 provides services such as personal phone line, fixed or converged video telephony and other advanced multimedia services. The CSC 104 processes requests from the user and an Application Server (AS) 105. The AS 105 makes various services available to the user. For example, the service made available to a user by the AS 105 may be a telecommunication call. When a user subscribes to the service of being able to choose a preferred charging scheme, the AS 105 stores the details of the user. For example, the details stored may include the name of the user, the subscriptions of the user and the numbers of the multiple endpoints. Each endpoint would have an IMS user private identity IP Multimedia Private Identity (IMPI) and an IMS user public identity IP Multimedia Public Identity (IMPU). IMPI is the private identity assigned to an endpoint and the IMPU is the identity of the endpoint that is made available to other users so that other users can communicate with the user. The IMPI is unique to an endpoint and there may be multiple IMPU per IMPI. IMPI and IMPU are Uniform Resource Identifiers (URI’s) and the IMPU of an endpoint may also be shared with a second endpoint. The AS 105 obtains information about the various subscriptions of the user and the various charging schemes the user has subscribed to, from a database server 106. The database server 106 stores all details about the user and the details may include information about all the subscriptions of the user with various service providers and the charging scheme of all the subscriptions.
[0019] FIG. 2 illustrates a block diagram of a user with multiple endpoints belonging to different networks connected to an IMS network. A user may have multiple endpoints in different networks using which the user can start a communication session with another user. For example, User 2 endpoint 1 203 may be a cell phone in a Session Initiation Protocol (SIP) network and User 2 endpoint 2 204 may be an Integrated Services Digital Network (ISDN) phone. The user may have multiple endpoints for a single subscription or multiple endpoints for multiple subscriptions. The user may also have a single endpoint for a single subscription and multiple such subscriptions. If the user has access to only one endpoint, the user can start a communication session using the available endpoint and be charged for the communication session based on the charging scheme of a different endpoint.
[0020] To avail of the service to be able to choose a preferred charging scheme, the user has to subscribe to the service. After subscribing to the service, the user can choose a preferred charging scheme from among the charging schemes to which the user has subscribed. If the user has access to only one endpoint and the user wants to be charged for the communication session based on the charging scheme of a different endpoint, then the user sends a service code message to the CSC 104, using the first endpoint, to invoke the service. The number of the endpoint whose charging scheme is to be used for the communication session is also included with the service code message. FIG. 3 illustrates a block diagram of an application server. A user may have multiple endpoints using which the user can start a communication session with another user and the user may have different charging schemes for different endpoints. If the user has access to only one endpoint and the user wants to be charged for the communication session based on the charging scheme of a different endpoint, then the user sends a service code message to the CSC 104, using the first endpoint, to invoke the service. The number of the endpoint whose charging scheme is to be used for the communication session is also included with the service code message. The CSC 104 forwards the message to the AS 105. When a user subscribes to the service of being able to choose a preferred charging scheme, the AS 105 stores the details of the user. The details of the user are stored in a memory 303. When the AS 105 receives the message from the CSC 104, a processor 301 processes the message and determines that the message is sent to invoke the service of being able to choose a preferred charging scheme. The processor 301 extracts the endpoint number whose charging scheme is to be applied for the communication session. The processor 301 sends a request to the database server 106 to obtain the charging scheme of the user for the particular endpoint. The AS 105 communicates with other elements in the communication using a network interface 302. The AS 105 sends the request to the database server 106 using the network interface 302. The AS 105 also receives information from the database server 106 through the network interface 106. A charge-scheme-id would be created in the database server 106 and the charge-scheme-id would be tied to the IMPI and IMPU of the user. The charge-scheme-id indicates the charging scheme chosen by the user for the communication session. When the user wants to start a communication session using the available endpoint, the processor 301 checks for the charge scheme obtained from the database server 106 and associates the charging scheme for the communication session. The charge-scheme-id may also be created by the AS 105. The user would then be charged for the communication session using the preferred charging scheme, irrespective of which one of the user’s endpoints is used to make the communication session. The processor 301 controls the operation of the AS 105.
[0021] FIG. 4 is a flowchart depicting a method for selecting a preferred charging scheme. A user may have multiple endpoints using which the user can start a communication session with another user. The user may have multiple endpoints for a single subscription or multiple endpoints for multiple subscriptions. The user may also have a single endpoint for a single subscription and multiple such subscriptions. The user may have different charging schemes for different endpoints. If the user has access to only one endpoint, the user can start a communication session using the available endpoint and be charged for the communication session based on the charging scheme of a different endpoint. To avail of the service to be able to choose a preferred charging scheme, the user has to subscribe to the service. After subscribing to the service, the user can choose a preferred charging scheme from among the charging schemes the user has subscribed to. If the user has access to only one endpoint and the user wants to be charged for the communication session based on the charging scheme of a different endpoint, then the user sends (401) a request to the CSC 104, using the first endpoint, to invoke the service. The request message would include the service code message and the number of the endpoint whose charging scheme is to be used for the communication session. The CSC 104 forwards the message to the AS 105. When the AS 105 receives the message from the CSC 104, the AS 105 processes the message and determines that the message is sent to invoke the service of being able to choose a preferred charging scheme. The AS 105 extracts the endpoint number whose charging scheme is to be applied for the communication session. The AS 105 sends a request to the database server 106 to obtain (402) the charging scheme of the user for the particular endpoint. After receiving (403) information about the charging scheme, the database server 106 creates a charge-scheme-id and links the charge-scheme-id to the IMPI and IMPU of the user. The charge-scheme-id indicates the charging scheme chosen by the user for the communication session. If the service invocation has been successful, the AS 105 sends (404) a message indicating the successful invocation of the service to the user, through the CSC 104. When the user wants to start a communication session (405) using the available endpoint, the AS 105 checks for the charge-scheme-id and associates the charging scheme for the communication session. The user would then be charged for the communication session using the preferred charging scheme, irrespective of which one of the user’s endpoints is used for the communication session. The various actions in method 400 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 4 may be omitted.
[0022] FIG. 5 illustrates a flow diagram for selecting a preferred charging scheme for a communication session. A user may have multiple endpoints using which the user can start a communication session with another user. The user may have different charging schemes for different endpoints. If the user has access to only one endpoint, the user can start a communication session using the available endpoint and be charged for the communication session based on the charging scheme of a different endpoint. The user sends a request to the CSC 104, using the first endpoint, to invoke the service. The request message would include the service code message and the number of the endpoint whose charging scheme is to be used for the communication session. For example, the request message sent to the CSC 104 using the endpoint 1 101 may be an Invite 501 message. The CSC 104 forwards the message to the AS 105. For example, the message sent by the CSC 104 to the AS 105 may be an Invite 502 message. When the AS 105 receives the message from the CSC 104, the AS 105 processes the message and determines that the message is sent to invoke the service of being able to choose a preferred charging scheme. The AS 105 extracts the endpoint number whose charging scheme is to be applied for the communication session. The AS 105 sends an acknowledgement message to the user through the CSC 104 indicating the successful reception of the request message. For example, the acknowledgement message sent to the CSC 104 by the AS 105 may be the 200 OK 503 message and the acknowledgement message sent to endpoint 1 101 from the CSC 104 may be the 200 OK 504 message. The AS 105 also sends a message to the user through the CSC 104 to notify that the AS 105 would be handling the request. For example, the notification message sent to the CSC 104 by the AS 105 may be the Notify 505 message and the notification message sent to endpoint 1 101 from the CSC 104 may be the Notify 506 message. The CSC 104 also sends the notification message to endpoint 2 102 of the user. For example, the notification message sent to endpoint 2 102 from the CSC 104 may be the Notify 508. Endpoint 1 101 and endpoint 2 102 acknowledge the reception of the notification message by sending an acknowledgement message to the CSC 104. For example, the acknowledgement message sent to the CSC 104 by endpoint 1 101 may be a 200 OK 507 message and the acknowledgement message to the CSC 104 by endpoint 2 102 may be a 200 OK 509 message. The CSC 104 relays the acknowledgement message to the AS 105. For example, the acknowledgement message sent to the AS 105 by the CSC 104 may be the 200 OK 5010 message.
[0023] The AS 105 then sends a message to the database server 106 indicating the users request to charge the communication session using the preferred charging scheme. For example, the message may be sent as a Push Data Request (PDR) 5011 message and the PDR 5011 message may se sent as a header in the Diameter protocol. The database server 106 stores all details about the user. The database server 106 stores the subscription ID/ID’s, IMPI/IMPI’s, IMPU/IMPU’s and the charging plan of the user. For example, if the user has a single subscription and 3 endpoints, the details stored in the database server 106 may be
Subscription 1 – IMPI 1 – IMPU 1
Subscription 1 – IMPI 2 – IMPU 2
Subscription 1 – IMPI 3 – IMPU 3
If the user has 2 subscriptions and 2 endpoints, the details stored in the database server 106 may be
Subscription 1 – IMPI 1 – IMPU 1
Subscription 2 – IMPI 2 – IMPU 2
On receiving the message from the AS 105, the database server 106 creates a charge-scheme-id and links the charge-scheme-id to the IMPI and IMPU of the user. The charge-scheme-id is included as a new field and the charge-scheme-id indicates the charging scheme chosen by the user for the communication session. For example, if the user has a single subscription and 3 endpoints, the charge-scheme-id linked to the IMPI and IMPU of the user as
Subscription 1 – IMPI 1 – IMPU 1 – CS1
Subscription 1 – IMPI 2 – IMPU 2 – CS2
Subscription 1 – IMPI 3 – IMPU 3 – CS3
If the user has 2 subscriptions and 2 endpoints, the charge-scheme-id linked to the IMPI and IMPU of the user as
Subscription 1 – IMPI 1 – IMPU 1 – CS1
Subscription 2 – IMPI 2 – IMPU 2 – CS1
After creating the charge-scheme-id, the database server 106 sends to message to the AS 105 informing the AS 105 about the charging scheme of the user. For example, the message sent by the database server 106 to the AS 105 may be a Push Data Answer (PDA) 5012 message and the PDA 5012 message may be sent as a header in the Diameter protocol. The AS 105 then sends a notification message to the CSC 104 indicating the successful activation of the service. For example, the message sent to the CSC 104 by the AS 105 may be a Notify 5013 message. The CSC 104 then sends the notification message to endpoint 1 101 and endpoint 2 102. For example, the notification sent to endpoint 1 101 may be a Notify 5014 message and the notification sent to endpoint 2 102 may be a Notify 5015 message. Endpoint 1 101 and endpoint 2 102 acknowledge the reception of the notification message by sending an acknowledgement message to the CSC 104. For example, the acknowledgement message sent to the CSC 104 by endpoint 1 101 may be a 200 OK 5016 message and the acknowledgement message to the CSC 104 by endpoint 2 102 may be a 200 OK 5017 message. The CSC 104 relays the acknowledgement message to the AS 105. For example, the acknowledgement message to the AS 105 by the CSC 104 may be the 200 OK 5018 message. After sending the acknowledgement, the user may start a communication session using endpoint 1 101 and the AS 105 checks for the charge-scheme-id and associates the charging scheme for the communication session. Records would be generated for charging the user for the communication session and user would then be charged for the communication session using the preferred charging scheme.
[0024] FIG. 6a and FIG. 6b are flowcharts depicting a method for selecting a preferred charging scheme for a communication session. A user may have multiple endpoints using which the user can start a communication session with another user. The user may have different charging schemes for different endpoints. If the user has access to only one endpoint, the user can start a communication session using the available endpoint and be charged for the communication session based on the charging scheme of a different endpoint. The user sends (601) a request to the AS 105, using the first endpoint, to invoke the service. The request message would include the service code message and the number of the endpoint whose charging scheme is to be used for the communication session. When the AS 105 receives (602) the message, the AS 105 processes the message and determines that the message is sent to invoke the service of being able to choose a preferred charging scheme. The AS 105 extracts (603) the endpoint number whose charging scheme is to be applied for the communication session. The AS 105 sends (604) an acknowledgement message to the user through the CSC 104 indicating the successful reception of the request message. The AS 105 also sends a message to the user through the CSC 104 to notify that the AS 105 would be handling the request. Endpoint 1 101 and endpoint 2 102 acknowledge the reception of the notification message by sending (605) an acknowledgement message to the AS 105.
[0025] The AS 105 then sends (606) a message to the database server 106 indicating the users request to charge the communication session using the preferred charging scheme. The database server 106 stores all details about the user. The database server 106 stores the subscription ID/ID’s, IMPI/IMPI’s, IMPU/IMPU’s and the charging plan of the user. On receiving the message from the AS 105, the database server 106 creates (607) a charge-scheme-id and links the charge-scheme-id to the IMPI and IMPU of the user. The charge-scheme-id is included as a new field and the charge-scheme-id indicates the charging scheme chosen by the user for the communication session. After creating the charge-scheme-id, the database server 106 sends (608) to message to the AS 105 informing the AS 105 about the charging scheme of the user. The AS 105 then sends (609) a notification message to the CSC 104 indicating the successful activation of the service. The CSC 104 then sends (6010) the notification message to endpoint 1 101 and endpoint 2 102. Endpoint 1 101 and endpoint 2 102 acknowledge the reception of the notification message by sending (6011) an acknowledgement message to the AS 105. After sending the acknowledgement, the user may start (6012) a communication session using endpoint 1 101 and the AS 105 checks for the charge-scheme-id and associates the charging scheme for the communication session. Records would be generated for charging the user for the communication session and user would then be charged for the communication session using the preferred charging scheme. The various actions in method 600 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 6 may be omitted.
[0026] In another embodiment, the charge-scheme-id may also be created by the AS 105. A user may have multiple endpoints using which the user can start a communication session with another user. The user may have different charging schemes for different endpoints. If the user has access to only one endpoint, the user can start a communication session using the available endpoint and be charged for the communication session based on the charging scheme of a different endpoint. The user sends a request to the AS 105, using the first endpoint, to invoke the service. The request message would include the service code message and the number of the endpoint whose charging scheme is to be used for the communication session. When the AS 105 receives the message, the AS 105 processes the message and determines that the message is sent to invoke the service of being able to choose a preferred charging scheme. The AS 105 extracts the endpoint number whose charging scheme is to be applied for the communication session. The AS 105 creates a charge-scheme-id and links the charge-scheme-id to the IMPI and IMPU of the user. The charge-scheme-id is included as a new field and the charge-scheme-id indicates the charging scheme chosen by the user for the communication session. The charge-scheme-id is stored in the memory 303. After creation of the charge-scheme-id, the user may start a communication session using endpoint 1 101 and the AS 105 checks for the charge-scheme-id and associates the charging scheme for the communication session. Records would be generated for charging the user for the communication session and user would then be charged for the communication session using the preferred charging scheme.

[0027] Embodiments described herein allow the user to choose any preferred charging scheme from among the charging schemes the user has subscribed to. The user can start a communication session from any available endpoint and be charged for the communication session based on the charging scheme of any of the user’s endpoints. Thus the user has the option of choosing the preferred charging scheme that is most appropriate for the communication requirement. For example, if the user wants to make a long distance call and the user has a more economically viable option of making the call using a landline phone rather than through a cell phone. Then the user can make the call using the available cell phone and be charged for the call based on the charging scheme of the land line phone.
[0028] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The network elements shown in Fig. 1, Fig. 2 and Fig. 3 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.
[0029] The embodiment disclosed herein specifies a method and system for selection of a preferred charging scheme for a communication session. The mechanism allows allowing a user to choose a preferred charging scheme for the communication session providing a system thereof. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in a preferred embodiment through or together with a code written in e.g. Very high speed integrated circuit Hardware Description Language (VHDL) or another coding language, or implemented by one or more VHDL or by one or more software modules being executed on at least one hardware device. The hardware device can be any kind of device which can be programmed including e.g. any kind of computer like a server or a personal computer, or the like, or any combination thereof, e.g. one processor and two FPGAs. The device may also include means which could be e.g. hardware means like e.g. an ASIC, or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented in pure hardware, or partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g. using a plurality of CPUs.
[0030] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the claims as described herein.

CLAIMS

What is claimed is:

1. A method for enabling a user to select a charging scheme associated with a first communication terminal using a second communication terminal, said method comprising steps of
said user using said second communication terminal to send a request to a network for applying said charging scheme associated with said first communication terminal to a communication session; and
said network charging said communication session based on said charging scheme of said first communication terminal.

2. The method, as claimed in claim 1, wherein said method further comprises of said user subscribing to the service of being able to choose a preferred said charging scheme from among the multiple charging schemes subscribed to by said user.

3. The method, as claimed in claim 1, wherein said request includes number of said first communication terminal.

4. The method, as claimed in claim 1, wherein said network creates a unique identification means for said user on receiving said request.

5. The method, as claimed in claim 4, wherein said unique identification means is linked to atleast one of
subscription id of said user;
IP Multimedia Private Identity (IMPI) of said first and second communication terminals; and
IP Multimedia Public Identity (IMPU) of said first and second communication terminals.

6. The method, as claimed in claim 4, wherein said unique identification means indicates said preferred said charging scheme chosen by said user.

7. The method, as claimed in claim 1, wherein said communication session is established by said user using said second communication terminal.

8. An application server for enabling a user to select a charging scheme associated with a communication terminal using a second communication terminal, said application server comprising atleast one means adapted for
receiving a request for applying a charging scheme associated with a first communication terminal to a communication session, wherein said request is sent by said user using a second communication terminal;
creating a unique identification means for said user and linking said unique identification means to subscription details of said user; and
charging of said communication session based on said charging scheme of said first communication terminal.

9. The application server, as claimed in claim 8, wherein said application server is adapted to store said subscription details of said user, wherein said subscription details comprise atleast one of
subscription id of said user;
IP Multimedia Private Identity (IMPI) of said first and second communication terminals; and
IP Multimedia Public Identity (IMPU) of said first and second communication terminals.

10. The application server, as claimed in claim 8, wherein said application server is adapted to extract number of said first communication terminal from said request.

11. The application server, as claimed in claim 8, wherein said unique identification means indicates said preferred said charging scheme chosen by said user.

Dated this 25th November 2009

Dr. Kalyan Chakravarthy
Patent Agent