Title of Invention	A SYSTEM AND METHOD FOR PROVIDING SECURE MOBILITY AND INTERNET PROTOCOL SECURITY RELATED SERVICES TO A MOBILE NODE ROAMING IN A FOREIGN NETWORK
Abstract	The present invention is related to the scenario where a Mobile Node (MN) in roaming needs to connect to Network Gateway (NGW) for providing secure data path using IP security procedure. Also Mobile IP is required for providing mobility to the user, when the MN moves from one sub-network to another. However, when the Home Address of the network is not known, a cyclic interdependency is observed between the IPsec procedures and Mobile IP procedures. If the home address of the MN is not known initially during the procedure, IPsec SA's are formed between the MN and NGW such that only Mobile IP packets are passed through. After the Mobile IP Registration is completed, the Home Address of the MN is known from the MIP registration Reply. MN now forms a data path tunnel with the NGW by exchanging create child SA messages. Thus the MN can be proviqed with both security as well as the Mobility related services. .

Title of Invention

A SYSTEM AND METHOD FOR PROVIDING SECURE MOBILITY AND INTERNET PROTOCOL SECURITY RELATED SERVICES TO A MOBILE NODE ROAMING IN A FOREIGN NETWORK

Abstract

The present invention is related to the scenario where a Mobile Node (MN) in roaming needs to connect to Network Gateway (NGW) for providing secure data path using IP security procedure. Also Mobile IP is required for providing mobility to the user, when the MN moves from one sub-network to another. However, when the Home Address of the network is not known, a cyclic interdependency is observed between the IPsec procedures and Mobile IP procedures. If the home address of the MN is not known initially during the procedure, IPsec SA's are formed between the MN and NGW such that only Mobile IP packets are passed through. After the Mobile IP Registration is completed, the Home Address of the MN is known from the MIP registration Reply. MN now forms a data path tunnel with the NGW by exchanging create child SA messages. Thus the MN can be proviqed with both security as well as the Mobility related services. .

Full Text	WE CLAIM 1. A method for reminder management to increase the probability of retrieving the deferred offline message under Notify/Get scenario, where the said method can be implemented in the Client Side or Server Side. 2. A method as claimed in claim 1 wherein the reminder procedure in the client side implementation involves the steps of: (a) requesting the user, the need to be reminded about the MM later when the recipient user attempts to defer the MM by the said system; (b) reminding the recipient user later after 'n' seconds by the said system; (c) validating the recipient user's duration with the actual expiry of the MM by the said system; (d) asking the recipient user to re-enter the duration by the said system if the duration 'n' exceeds the expiry of MM; and (e) registering the MM notification along with the reminder duration in the local storage once the recipient user enters a valid duration. 3. A method as claimed in claim 2 wherein the said system is provided an option to have a default setting for reminders of any message which the user can opt to choose. 4. A method as claimed in claim 2 wherein the system has a reliable timer event manager, which monitors those notifications which are required to be reminded. 5. A method as claimed in claim 2 wherein once the said duration has expired, the timer event manager triggers the system to intimate the user about the retrieval of MM and the system in turn notifies the user about the need for retrieving the MM. 6. A method as claimed in claim 2 wherein the client side implementation deletes the corresponding reminders by the client from its storage once the recipient user retrieves the MM, 7. A method as claimed in claim 2 wherein apart from reminding the user, the reminder system allows the users to perform enabling and disabling of reminder mechanism, setting a default time duration for the reminders and setting or modifying or canceling of the individual message reminders. 8. A method as claimed in claim 2 wherein the MMS client maintains a reliable timer event manager to indicate the timer related events. 9. A method as claimed in claim 2 wherein the MMS client requests the user to specify the time for the next reminder. 10. A method as claimed in claim 2 wherein the MMS client provides the list of reminders to the users. 11. A method as claimed in claim 2 wherein the MMS client allows the user to alter the reminder values anytime before the expiry of MM. 12. A method as claimed in claim 2 wherein the MMS client removes the reminders once the reminders become invalid. 13. A method as claimed in claim 1 wherein the Reminder of Message procedure in the server side implementation involves the steps of: (a) Enables or disables the reminder mechanism for a particular MM; (b) Indicating the support for reminder management for the MM in the notification request. (c) Validating the recipient user's duration with the expiry of the MM by the said system; (d) Responding with a reminder value in the notification response; (e) Registering the time when the recipient user wants to receive the notification upon receiving the defer message request by the said system; (f) Sending a notification to the user upon expiry of reminder time; and (g) Managing the reminders that includes the update on the reminders, retrieval of reminders & Deletion of reminders. 14. A method as claimed in claim 12 wherein a header X-Mms-Allow-Reminder is added in the notification request which indicates whether the MMS Proxy Relay supports reminders for this MM. 15. A method as claimed in claim 12 wherein the said system in the MMS Proxy Relay assumes the expiry time as the duration, if the duration exceeds the expiry time. 16. A method as claimed in claim 1 wherein the deferred procedure in the server side implementation involves the steps of sending the duration 'n' in the Notification response / defer request by the client once the recipient user enters a valid duration. 17. A method as claimed in claim 12 wherein a header X-Mms-Reminder-Duration is added in the Notification Response message which indicates the duration of next reminder. 18. A method as claimed in claim 12 wherein the reminder system allows the users to perform enabling and disabling of reminders and when the server indicates the support of reminders in the notification request, the user decides not to set a reminder for a message where, the reminder duration header is not present in the notification response message and the MMS Proxy Relay disables the reminder for that particular MM. 19. A method as claimed in claim 12 wherein the reminder system allows the users to perform modifying or canceling the reminders using a reminder alter transaction using M-Reminder-Alter.Req and M-Reminder-Alter.conf primitives which allow the user to alter the existing timer values, or to create a new timer value, if not created earlier during the defer request. 20. A method as claimed in claim 12 wherein the reminder system allows the users to list the reminders using a reminder list view transaction using M-Reminder-Listview.Req and M-Reminder-Listview.conf primitives which allows the user to view list of reminders that are actively present in the said system. 21. A method as claimed in claim 1 wherein the MMS server sends a notification to the user upon the expiry of reminder duration. 22. A method as claimed in claim 1 wherein the MMS server maintains the reminder till the message is stored in the server. 23. A method for reminder management in a reminder management system to increase the probability of retrieving the deferred offline message under Notify/Get scenario substantially described particularly with reference to the accompanying drawings. WE CLAIM 1. A method for establishing mobility and Internet Protocol security related services by a Mobile Node roaming in a foreign network when the Home Address of the Mobile Node is not known, the method comprising the steps of: a. forming a secure dummy tunnel with the network gateway for a mobile IP passage; b. sending the mobile IP message for registration through the tunnel to the home agent; c. extracting the home address from a successful registration reply message; and d. sending a message to create the actual security association with the network gateway using the Home IP address to form a data path. 2. The method as claimed in claim 1 wherein IP security tunnel and Mobile IP registration are synchronously formed by breaking the cyclic interdependency between the requirement of Home Address for IP security association and the requirement of IP security association between Network gateway and Mobile Node for transporting the Mobile IP Registration Request messages. 3. A method as claimed in claim 1 wherein after obtaining the Home Address from the Mobile IP Registration Reply, the Mobile Node sends a Create Child SA message to the Network Gateway to form actual Security Association for the data path. 4. A method as claimed in claim 1 wherein the Mobile Node initiates the tunnel establishment request with the Network Gateway . 5. The method as claimed in claim 1 wherein the said mobile IP messages are processed at a Foreign Agent and forwarded to the Home Agent. 6. A method as claimed in claim 1 wherein the said Mobile IP Registration message comprises the Network Access Identifier, Mobile node Home Agent key generation nonce, Mobile Node and the authentication extensions if the home agent address and home network prefix are not known. 7. A method as claimed in claim 4 wherein the Network Gateway relays the Mobile IP Registration Reply to the Mobile Node which extracts Home Address through the already established tunnel. 8. A method as claimed in claim 1 wherein the said dummy tunnel is established between a Wireless Local Area Network 3^^ Generation capable User Equipment and a Packet data Gateway over a Wireless LAN -Third Generation Mobile System intenA/orking system. 9. A method as claimed in claim 1 wherein the said dummy tunnel is established between 3G-WLAN UE (WLAN 3G capable User Equipment) and Packet Data Gateway over a 3G-WLAN interworking system. 10. The method as claimed in claim 9 or 10 wherein the method comprises: a. sending an IKE_AUTH (Internet Key Exchange Authorization) request, without AUTH (Authorization) payload to initiate an EAP (Extensible Authentication Protocol) procedure by an UE and Traffic Selectors allowing only MIP (Mobile IP) messages to pass; b. forwarding an EAP (Extensible Authentication Protocol) success message by PDG (Packet Data Gateway) within an IKEv2 (Internet Key Exchange version 2 Protocol) message to the UE (WLAN-3G capable User Equipment) and forming a dummy tunnel with UE (WLAN-3G capable User Equipment) by sending agreed Traffic Selectors; c. Solicitation of Mobile Agent and Advertisement exchanging within the above formed dummy tunnel; d. forwarding the MIP Reply (Mobile IP registration Reply) by Packet data Gateway to the UE (User Equipment) (WLAN-3G capable User Equipment) through the dummy tunnel, and; e. forming an actual SA (Security Association) modifying the existing dummy tunnel by sending the Create__Child_SA (Security Association) IKEv2 (Internet Key Exchange version 2 Protocol) nnessages. 11. A system for establishing mobility and Internet Protocol security related services by a Mobile Node roaming in a foreign network by the said method when the Home Address of the Mobile Node is not known. 12.A method for establishing mobility and Internet Protocol security related services by a Mobile Node roaming in a foreign network when the Home Address of the Mobile Node is not known, substantially as herein above described and illustrated with reference to the accompanying drawings.

Full Text

WE CLAIM
1. A method for reminder management to increase the probability of retrieving the deferred offline message under Notify/Get scenario, where the said method can be implemented in the Client Side or Server Side.
2. A method as claimed in claim 1 wherein the reminder procedure in the client side implementation involves the steps of:

(a) requesting the user, the need to be reminded about the MM later when the recipient user attempts to defer the MM by the said system;
(b) reminding the recipient user later after 'n' seconds by the said system;
(c) validating the recipient user's duration with the actual expiry of the MM by the said system;
(d) asking the recipient user to re-enter the duration by the said system if the duration 'n' exceeds the expiry of MM; and
(e) registering the MM notification along with the reminder duration in the local storage once the recipient user enters a valid duration.

3. A method as claimed in claim 2 wherein the said system is provided an option to have a default setting for reminders of any message which the user can opt to choose.
4. A method as claimed in claim 2 wherein the system has a reliable timer event manager, which monitors those notifications which are required to be reminded.
5. A method as claimed in claim 2 wherein once the said duration has expired, the timer event manager triggers the system to intimate the user about the retrieval of MM and the system in turn notifies the user about the need for retrieving the MM.
6. A method as claimed in claim 2 wherein the client side implementation deletes

the corresponding reminders by the client from its storage once the recipient user retrieves the MM,
7. A method as claimed in claim 2 wherein apart from reminding the user, the reminder system allows the users to perform enabling and disabling of reminder mechanism, setting a default time duration for the reminders and setting or modifying or canceling of the individual message reminders.
8. A method as claimed in claim 2 wherein the MMS client maintains a reliable timer event manager to indicate the timer related events.
9. A method as claimed in claim 2 wherein the MMS client requests the user to specify the time for the next reminder.
10. A method as claimed in claim 2 wherein the MMS client provides the list of reminders to the users.
11. A method as claimed in claim 2 wherein the MMS client allows the user to alter the reminder values anytime before the expiry of MM.
12. A method as claimed in claim 2 wherein the MMS client removes the reminders once the reminders become invalid.
13. A method as claimed in claim 1 wherein the Reminder of Message procedure in the server side implementation involves the steps of:

(a) Enables or disables the reminder mechanism for a particular MM;
(b) Indicating the support for reminder management for the MM in the notification request.
(c) Validating the recipient user's duration with the expiry of the MM by the said system;
(d) Responding with a reminder value in the notification response;
(e) Registering the time when the recipient user wants to receive the

notification upon receiving the defer message request by the said system;
(f) Sending a notification to the user upon expiry of reminder time; and
(g) Managing the reminders that includes the update on the reminders, retrieval of reminders & Deletion of reminders.

14. A method as claimed in claim 12 wherein a header X-Mms-Allow-Reminder is added in the notification request which indicates whether the MMS Proxy Relay supports reminders for this MM.
15. A method as claimed in claim 12 wherein the said system in the MMS Proxy Relay assumes the expiry time as the duration, if the duration exceeds the expiry time.
16. A method as claimed in claim 1 wherein the deferred procedure in the server side implementation involves the steps of sending the duration 'n' in the Notification response / defer request by the client once the recipient user enters a valid duration.
17. A method as claimed in claim 12 wherein a header X-Mms-Reminder-Duration is added in the Notification Response message which indicates the duration of next reminder.
18. A method as claimed in claim 12 wherein the reminder system allows the users to perform enabling and disabling of reminders and when the server indicates the support of reminders in the notification request, the user decides not to set a reminder for a message where, the reminder duration header is not present in the notification response message and the MMS Proxy Relay disables the reminder for that particular MM.
19. A method as claimed in claim 12 wherein the reminder system allows the users to perform modifying or canceling the reminders using a reminder alter

transaction using M-Reminder-Alter.Req and M-Reminder-Alter.conf primitives which allow the user to alter the existing timer values, or to create a new timer value, if not created earlier during the defer request.
20. A method as claimed in claim 12 wherein the reminder system allows the users to list the reminders using a reminder list view transaction using M-Reminder-Listview.Req and M-Reminder-Listview.conf primitives which allows the user to view list of reminders that are actively present in the said system.
21. A method as claimed in claim 1 wherein the MMS server sends a notification to the user upon the expiry of reminder duration.
22. A method as claimed in claim 1 wherein the MMS server maintains the reminder
till the message is stored in the server.
23. A method for reminder management in a reminder management system to
increase the probability of retrieving the deferred offline message under
Notify/Get scenario substantially described particularly with reference to the
accompanying drawings.

WE CLAIM
1. A method for establishing mobility and Internet Protocol security related
services by a Mobile Node roaming in a foreign network when the Home
Address of the Mobile Node is not known, the method comprising the steps of:
a. forming a secure dummy tunnel with the network gateway for a mobile
IP passage;
b. sending the mobile IP message for registration through the tunnel to
the home agent;
c. extracting the home address from a successful registration reply
message; and
d. sending a message to create the actual security association with the
network gateway using the Home IP address to form a data path.
2. The method as claimed in claim 1 wherein IP security tunnel and Mobile IP registration are synchronously formed by breaking the cyclic interdependency between the requirement of Home Address for IP security association and the requirement of IP security association between Network gateway and Mobile Node for transporting the Mobile IP Registration Request messages.
3. A method as claimed in claim 1 wherein after obtaining the Home Address from the Mobile IP Registration Reply, the Mobile Node sends a Create Child SA message to the Network Gateway to form actual Security Association for the data path.
4. A method as claimed in claim 1 wherein the Mobile Node initiates the tunnel establishment request with the Network Gateway .
5. The method as claimed in claim 1 wherein the said mobile IP messages are processed at a Foreign Agent and forwarded to the Home Agent.
6. A method as claimed in claim 1 wherein the said Mobile IP Registration message comprises the Network Access Identifier, Mobile node Home Agent

key generation nonce, Mobile Node and the authentication extensions if the home agent address and home network prefix are not known.
7. A method as claimed in claim 4 wherein the Network Gateway relays the Mobile IP Registration Reply to the Mobile Node which extracts Home Address through the already established tunnel.
8. A method as claimed in claim 1 wherein the said dummy tunnel is established between a Wireless Local Area Network 3^^ Generation capable User Equipment and a Packet data Gateway over a Wireless LAN -Third Generation Mobile System intenA/orking system.
9. A method as claimed in claim 1 wherein the said dummy tunnel is established between 3G-WLAN UE (WLAN 3G capable User Equipment) and Packet Data Gateway over a 3G-WLAN interworking system.
10. The method as claimed in claim 9 or 10 wherein the method comprises:
a. sending an IKE_AUTH (Internet Key Exchange Authorization) request,
without AUTH (Authorization) payload to initiate an EAP (Extensible
Authentication Protocol) procedure by an UE and Traffic Selectors
allowing only MIP (Mobile IP) messages to pass;
b. forwarding an EAP (Extensible Authentication Protocol) success message
by PDG (Packet Data Gateway) within an IKEv2 (Internet Key Exchange
version 2 Protocol) message to the UE (WLAN-3G capable User
Equipment) and forming a dummy tunnel with UE (WLAN-3G capable
User Equipment) by sending agreed Traffic Selectors;
c. Solicitation of Mobile Agent and Advertisement exchanging within the
above formed dummy tunnel;
d. forwarding the MIP Reply (Mobile IP registration Reply) by Packet data
Gateway to the UE (User Equipment) (WLAN-3G capable User
Equipment) through the dummy tunnel, and;
e. forming an actual SA (Security Association) modifying the existing dummy
tunnel by sending the Create__Child_SA (Security Association) IKEv2

(Internet Key Exchange version 2 Protocol) nnessages.
11. A system for establishing mobility and Internet Protocol security related services by a Mobile Node roaming in a foreign network by the said method when the Home Address of the Mobile Node is not known.
12.A method for establishing mobility and Internet Protocol security related services by a Mobile Node roaming in a foreign network when the Home Address of the Mobile Node is not known, substantially as herein above described and illustrated with reference to the accompanying drawings.

Documents:

1443-che-2004 abstract-duplicate.pdf

1443-che-2004 claims-duplicate.pdf

1443-che-2004 descripition(completed)-duplicate.pdf

1443-che-2004 drawings-duplicate.pdf

1443-che-2004-abstract.pdf

1443-che-2004-claims.pdf

1443-che-2004-correspondnece-others.pdf

1443-che-2004-correspondnece-po.pdf

1443-che-2004-description(complete).pdf

1443-che-2004-drawings.pdf

1443-che-2004-form 1.pdf

1443-che-2004-form 19.pdf

1443-che-2004-form 26.pdf

1443-che-2004-form 3.pdf

1443-che-2004-form 5.pdf

« Previous Patent

Next Patent »

Patent Number

219667

Indian Patent Application Number

1443/CHE/2004

PG Journal Number

27/2008

Publication Date

04-Jul-2008

Grant Date

13-May-2008

Date of Filing

28-Dec-2004

Name of Patentee

SAMSUNG INDIA SOFTWARE OPERATIONS PRIVATE LIMITED

Applicant Address

Inventors:

#	Inventor's Name	Inventor's Address
1	DR. OSOK SONG
2	RAHUL VAIDYA
3	BALAJI SRINIVAS HOLUR
4	R. RAJAVELSAMY
5	JEEDIGUNTA VENKATESWAR

PCT International Classification Number

HO4Q7/38

PCT International Application Number

N/A

PCT International Filing date

PCT Conventions:

#	PCT Application Number	Date of Convention	Priority Country
1			NA