System and method of data access for mobile stations

This application is a continuation of application Ser. No. 12/818,307, filed on Jun. 18, 2011, now issued as U.S. Pat. No. 7,978,648 issued on Jul. 12, 2011, which is a continuation of Ser. No. 11/226,270, filed on Sep. 15, 2005, which issued as U.S. Pat. No. 7,756,075 on Jul. 13, 2010, the entire disclosures of both patents are hereby incorporated by reference for all purposes.

A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyrights whatsoever.

This patent document relates generally to mobile stations, and in particular to a system and method of data access for mobile stations.

In a mixed coverage area of 1XRTT and 1XEV-DO, it is very possible for carriers to deploy separate PDSN/AAA to manage each wireless network separately. Because of the separate management, it is possible for carriers to control data access (i.e. establish a PPP session) to each network with separate mobile authentication rules.

An EVDO capable device, when queried about Protocol Capability for Over The Air Provisioning, it will inform the network that it is capable of IS-683C version of PRL. Network therefore can download an IS-683C version of PRL but it is possible that user may not purchase EVDO service. Under such circumstances, device SW is unaware of such service unavailability and therefore will always try to perform any data access through the EVDO network. The EVDO standard already has the provision for AN level authentication, which is an optional feature that a carrier may or may not be implemented.

For scenarios where AN Authentication is disabled but PDSN/AAA authentication is separate between EVDO & 1X network, there needs to be a mechanism for a device with EVDO PRL but not configured by network for EVDO service to fall back to 1X system for data service; this behaviour is currently undefined.

Also, if the user later on purchases EVDO service, there needs to be a seamless mechanism for the device to resume from 1X fall back condition to start using the EVDO service without the need to reconfigure anything on the device—this behaviour is also not defined any where.

Hence there is a need for an improved data access method and apparatus for mobile terminal.

An embodiment of the patent disclosure will now be described by way of example only with reference to the following drawings in which:

FIGS. 1 a , 1 b and 1 c there is illustrated in a flow chart a method of data access for a mobile terminal, in accordance with an embodiment of the patent disclosure.

The patent disclosure describes a solution to one or more of the problems described above.

In accordance with an embodiment of the patent disclosure, there is provided a method of data access for a mobile terminal comprising the steps of determining whether first and second modes of wireless network coverage is available, selecting the first mode if available, on failure to establish access via the first mode, attempting access via the second mode and monitoring availability of the first mode.

In accordance with an embodiment of the patent disclosure, there is provided an apparatus for data access for a mobile terminal comprising a module for determining whether first and second modes of wireless network coverage is available, a module for selecting the first mode if available, a module for attempting access via the second mode on failure to establish access via the first mode and a module for monitoring availability of the first mode.

A system and method of the patent disclosure will now be described with reference to various examples of how the embodiments can best be made and used. For convenience, like reference numerals are used throughout the description and several views of the drawings to indicate like or corresponding parts, wherein the various elements are not necessarily drawn to scale.

The present patent disclosure describes various use cases related to PPP authentication retry procedures for 1X/1XEV-DO hybrid mobiles.

The present patent disclosure uses the following acronyms:

1XEV-DO 1X Evolution, Data-Only

PPP Point-to-Point Protocol

CHAP Challenge-Handshake Authentication Protocol

SID System ID

NID Network ID

PKZID Packet Zone ID

Referring to FIGS. 1 a , 1 b and 1 c there is in a flow chart a method of data access for a mobile terminal, in accordance with an embodiment of the patent disclosure. The present method of data access 10 is illustrated in FIG. 1 a . A hybrid device is in coverage for both 1X and 1XEV-DO systems as represented by state block 12 . The hybrid device attempts a PPP session setup in EVDO as represented by process block 14 . A decision block 16 determines if PPP authentication failed in EVDO. If NO as state “PPP up in EVDO” is entered at 20 .

A YES to decision block 16 leads to a process block 24 , which selects 1X system for subsequent data access attempts. Device will continue to monitor network changes in EVDO system.

Process block 24 leads to process block 26 , which attempts to set up PPP session in 1X. A decision block 28 determines whether PPP set up in 1X occurred, if YES the hybrid device enters a “PPP up in 1X” state 30 . If NO, the process passes on to block 32 of FIG. 1 b.

Referring to FIG. 1 b a process block 32 monitors network changes in both 1X and EVDO systems. Following step 32 , a decision block 34 detects whether a SubnetID change has occurred. If NO, a decision block 36 detects whether a SID/NID/PKZID change has occurred. If YES, the process returns to the process block 26 of FIG. 1 a.

A YES to decision block 34 leads to a process block 42 which selects EVDO system for subsequent data access attempts and passes the process back to the process block 14 of FIG. 1 a . A NO to the decision block 36 returns to monitoring network changes at process block 32 .

Referring to FIG. 1 c a process block 50 , coupled to the state block 30 of FIG. 1 a , monitors when an active 1X connection transitions to a dormant state. Following step 50 , a decision block 52 detects whether a SubnetID change has occurred. If NO, a decision block 54 determines if a connection is needed. If YES, the path returns to process block 50 . If NO, the path returns to the decision block 52 .

A YES to the decision block 52 leads to a process block 60 , which selects EVDO system for subsequent data access, and moves the PPP session from 1X to EVDO. Process block 60 leads to a state block 20 , which represents the device as having an active PPP session in EVDO.

The generalized method of FIGS. 1 a , 1 b , and 1 c can be used for a number of situations. By way of example several use cases are presented. For each case preconditions and post conditions are given as well as the steps taken by the process of FIGS. 1 a , 1 b and 1 c to transition the hybrid device.

Use Case 1: EVDO Auth Failure, Successful PPP Setup in 1X

Preconditions:

Hybrid device in 1XRTT/1XEV-DO coverage

Session, connection established in EVDO

LCP negotiation successful

Attempt data access authentication using negotiated protocol (e.g. CHAP)

Postconditions:

PPP established in 1X

Exposition:

1. Data access authentication fails in EVDO coverage, block 16 .

2. Select 1X system for subsequent data access attempts, block 24 .

3. Retry PPP setup in 1X, block 26 .

Use Case 2: EVDO Auth Failure, 1X Auth Failure

Preconditions:

Hybrid device in 1XRTT/1XEV-DO coverage

Session, connection established in EVDO

LCP negotiation successful

Attempt data access authentication using negotiated protocol (e.g. CHAP)

Postconditions:

No PPP session active

Exposition:

1. Data access authentication fails in EVDO coverage, block 16 .

2. Select 1X system for subsequent data access attempts, block 24 .

3. Retry PPP setup in 1X, block 26 .

4. Data access set up in 1X coverage, block 28 and up in block 30 .

Use Case 3: Data Auth Failure, PPP Retry on SubnetID Change

Preconditions:

Hybrid device fails EVDO and 1X data authentication

Postconditions:

Attempt PPP retry in 1X

Exposition:

1. Hybrid device detects change in SubnetID from received overhead messages, block 34 .

2. Select EVDO system for subsequent data access attempts, block 42 .

3. Retry PPP setup in EVDO, block 14 .

Use Case 5: Data Auth Failure, PPP Retry on SID/NID/PKZID Change

Preconditions:

Hybrid device fails EVDO and 1X data authentication

No change in SubnetID detected

Postconditions:

Attempt PPP retry in 1X

Exposition:

1. Hybrid device detects change in SID/NID/PKZID from received overhead messages, block 36 .

2. Retry PPP setup in 1X, block 26 .

Use Case 6: 1X PPP Established, Idle 1X Connection, No Pending Data, Detect New SubnetID

Preconditions:

PPP session active in 1X

1X connection is dormant

Postconditions:

PPP established in EVDO

Exposition:

1. Hybrid device detects change in SubnetID from received overhead messages, block 52 .

2. Select EVDO system for subsequent data access, block 60 . Move the active PPP session from 1X to EVDO.

3. PPP active in EVDO, block 20 .

Use Case 7: 1X PPP Established, Idle 1X Connection, Pending Data, Detect New SubnetID

Preconditions:

PPP session active in 1X

1X connection is dormant

Postconditions:

Attempt PPP retry in EVDO

Exposition:

1. Hybrid device detects change in SubnetID from received overhead messages, block 52 .

2. Establish 1X connection to service pending data, block 54 .

3. When connection transitions back to dormant, block 50 , check if hybrid device is still in new subnet, block 52 .

4. Select EVDO system for subsequent data access, block 60 . Move the active PPP session from 1X to EVDO.

5. PPP active in EVDO, block 20 .

While particular embodiments of the patent disclosure have been shown and described, changes and modifications may be made to such embodiments without departing from the true scope of the patent disclosure.