Sign In to Follow Application
View All Documents & Correspondence

Method For Paging Legacy And Advanced Access Terminals

Abstract: The present invention provides a method for paging legacy and advanced access terminals. One embodiment of the method comprises receiving a notification that an access terminal is entering an idle mode and determining whether the access terminal is a legacy device identified by a fixed length identifier or an advanced device identified by one of a plurality of mode dependent identifiers. The mode dependent identifier is used to identify the advanced device in the idle mode. This embodiment may also include allocating one or more first paging cycles to the access terminal when it is a legacy device or one or more second paging cycles to the access terminal when it is an advanced device. The first and second paging cycles are different.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
17 December 2012
Publication Number
24/2014
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
Parent Application
Patent Number
Legal Status
Grant Date
2019-11-28
Renewal Date

Applicants

ALCATEL LUCENT
3 avenue Octave Gréard F 75007 Paris

Inventors

1. NAIR Suresh P.
33 Deerfield Road Whippany NJ 07981
2. FEDER Peretz
300 Starling Road Englewood NJ 07631

Specification

METHOD FOR PAGING LEGACY AND ADVANCED ACCESS TERMINALS
CROSS REFERENCE TO RELATEDAPPLICATIONS
"This application claims the benefit of the filing date of U.S. Provisional Application Ser. No.
61/356,861, filed June 21, 2010, entitled "Method for IEEE 802. 16m Paging Operation in Networks
Simultaneously Supporting Legacy and Advanced Mss".
This application is related to U.S. Patent Application 13/150,321, filed on June 1, 201 1, attorney docket
number 2100.048000 which claims the benefit of the filing date of U.S. Provisional Application Ser. No.
61/356,826, filed June 21, 2010, entitled "Method for Managing IEEE 802.16m AdvancedMS States and Identifiers
in a Wireless Network.
BACKGROUND
This invention relates generally to communication systems, and, more particularly, to wireless
communication systems.
Conventional wireless communication systems use a network of base stations or other access nodes to
provide wireless connectivity to a large and often mobile population of access terminals. Each access terminal
can be identified to the wireless communication system by an identifier that is permanently assigned or "burned
in" to the mobile unit. For example, implementations of WiMAX release 1 that are based on the standards and
protocols defined by IEEE 802. 16e (2009) use a constant 48-bit mobile station identifier (MS-ID) to identify the
access terminals in the network. The MS-ID is typically installed or programmed by the manufacturer of the
access terminal in the form of a media access control (MAC) identifier. For another example, wireless
communication systems that operate according to the Global System for Mobile communications (GSM) and/or
Universal Mobile Telecommunication Services (UMTS) standards and/or protocols may use a 64-bit
International Mobile Subscriber Identity (IMSI) to identify each mobile unit or access terminal.
The conventional mobile station identifier is used to identify the access terminal within the network
and over the air. For example, access terminals can be paged over the air by transmitting a hashed value derived
from the identifier, e.g., a 24-bit hash of a 48-bit identifier can be used to page access terminals. Access
terminals can also be associated with different identifiers in different circumstances. For example, WiMAX
networks that operate according to IEEE 802. 16m standards and/or protocols may identify access terminals
using a set of identification numbers that range in length from 10 bits to 72 bits depending on the operational
state of the access terminal. Consequently, the identifier that is used by the network and over the air varies as
the operational mode changes, e.g., as the access terminal shifts between sleeping, dormant, idle, active, or other
operational states. For example, idle access terminals that comply with IEEE 802. 16m can be identified by an
18-bit de-registration identifier that can be used to page access terminals over the air interface.
SUMMARY
The disclosed subject matter is directed to addressing the effects of one or more of the problems set
forth above. The following presents a simplified summary of the disclosed subject matter in order to provide a
basic understanding of some aspects of the disclosed subject matter. This summary is not an exhaustive
overview of the disclosed subject matter. It is not intended to identify key or critical elements of the disclosed
subject matter or to delineate the scope of the disclosed subject matter. Its sole purpose is to present some
concepts in a simplified form as a prelude to the more detailed description that is discussed later.
In one embodiment, a method is provided for paging legacy and advanced access terminals. One
embodiment of the method comprises receiving a notification that an access terminal is entering an idle mode
and determining whether the access terminal is a legacy device identified by a fixed length identifier or an
advanced device identified by one of a plurality of mode-dependent identifiers. The mode-dependent identifier
is used to identify the advanced device in the idle mode. This embodiment may also include allocating one or
more first paging cycles to the access terminal when it is a legacy device or one or more second paging cycles to
the access terminal when it is an advanced device. The first and second paging cycles are different.
In another embodiment, a method is provided for paging legacy and advanced access terminals. One
embodiment of the method comprises receiving at least one message addressed to an idle access terminal and
determining whether the idle access terminal is a legacy device identified by a fixed length identifier or an
advanced device identified by one of a plurality of mode-dependent identifiers. The mode-dependent identifier
is used to identify the advanced device in the idle mode. This embodiment may also include paging the idle
access terminal during one or more first paging cycles when it is a legacy device and one or more second paging
cycles when it is an advanced device.
BRIEF DESCRIPTION OF THE DRAWINGS
The disclosed subject matter may be understood by reference to the following description taken in
conjunction with the accompanying drawings, in which like reference numerals identify like elements, and in
which:
Figure 1 conceptually illustrates one exemplary embodiment of a wireless communication system;
Figure 2 conceptually illustrates one exemplary embodiment of a sequence of paging cycles and paging
offsets
Figures 3A and 3B conceptually illustrate embodiments of paging advertisement messages for legacy
devices and advanced devices, respectively;
Figure 4 conceptually illustrates one exemplary embodiment of a method for setting the paging
parameters of an access terminal;
Figure 5 conceptually illustrates one exemplary embodiment of a method of for paging legacy devices
and/or advanced devices; and
Figure 6 conceptually illustrates one exemplary embodiment of a method for allocating fixed length
identifiers such as pseudo-identifiers to access terminals.
While the disclosed subject matter is susceptible to various modifications and alternative forms,
specific embodiments thereof have been shown by way of example in the drawings and are herein described in
detail. It should be understood, however, that the description herein of specific embodiments is not intended to
limit the disclosed subject matter to the particular forms disclosed, but on the contrary, the intention is to cover
all modifications, equivalents, and alternatives falling within the scope of the appended claims.
DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS
Illustrative embodiments are described below. In the interest of clarity, not all features of an actual
implementation are described in this specification. It will of course be appreciated that in the development of
any such actual embodiment, numerous implementation-specific decisions should be made to achieve the
developers' specific goals, such as compliance with system-related and business-related constraints, which will
vary from one implementation to another. Moreover, it will be appreciated that such a development effort might
be complex and time-consuming, but would nevertheless be a routine undertaking for those of ordinary skill in
the art having the benefit of this disclosure.
The disclosed subject matter will now be described with reference to the attached figures. Various
structures, systems and devices are schematically depicted in the drawings for purposes of explanation only and
so as to not obscure the description with details that are well known to those skilled in the art. Nevertheless, the
attached drawings are included to describe and explain illustrative examples of the disclosed subject matter.
The words and phrases used herein should be understood and interpreted to have a meaning consistent with the
understanding of those words and phrases by those skilled in the relevant art. No special definition of a term or
phrase, i.e. , a definition that is different from the ordinary and customary meaning as understood by those
skilled in the art, is intended to be implied by consistent usage of the term or phrase herein. To the extent that a
term or phrase is intended to have a special meaning, i.e., a meaning other than that understood by skilled
artisans, such a special definition will be expressly set forth in the specification in a definitional manner that
directly and unequivocally provides the special definition for the term or phrase.
Generally, the present application describes embodiments of techniques that are used to support paging
of different types of access terminals in a wireless communication system. As wireless communication
continues to evolve, systems may be required to support communication with access terminals that operate
according to different standards and/or protocols. For example, legacy and advanced access terminals may be
identified with identifiers having different lengths and/or identifiers that are selected for the access terminal
based upon its operational mode. Conventional paging techniques do not support multiple paging formats. For
example, paging controllers that operate according to the 802. 16e standards and/or protocols may identify and
page idle access terminals on the basis of a 24-bit hash of a 48-bit mobile station identifier. However,
subsequent standards may identify and page idle access terminals on the basis of different identifiers. For
example, the 802. 16m standards identify idle access terminals using a deregistration identifier that is one of
several mode-dependent identifiers associated with the advanced access terminal. Embodiments of
deregistration identifiers may include 18 bits although other bit numbers could be used in other embodiments.
The present application therefore describes embodiments of techniques that can support identification
and paging of legacy and advanced access terminals. In one embodiment, a paging controller determines when
an access terminal is entering the idle mode and determines whether the access terminal is a legacy or advanced
device. Legacy devices are identified by their fixed length identifiers (such as the 48-bit mobile station
identifier) and advanced devices are identified by the mode-dependent identifier allocated in the idle mode.
Different paging cycles and/or paging offsets may then be allocated to groups of legacy devices and groups of
advanced devices. The paging cycle/offset information and idle mode identifiers for the access terminals can
then be dynamically stored, e.g., in a database associated with the paging controller. When the system needs to
locate an access terminal, it determines whether the access terminal is a legacy or advanced device and then
forms a paging advertisement message using the appropriate identifier. Paging advertisements may then be
transmitted to legacy devices in the set of legacy paging cycles/offsets in the legacy format or to advanced
devices in the mutually exclusive set of paging cycles/offsets in the advanced format.
Figure 1 conceptually illustrates one exemplary embodiment of a wireless communication system 100.
In the illustrated embodiment, the wireless communication system 100 includes a plurality of access nodes 105
such as base stations that are used to provide wireless connectivity. For example, the access node 105(1)
provides wireless connectivity within a geographical region such as a cell 140. The access nodes 105 depicted
in Figure 1 operate according to WiMAX standards and/or protocols such as the standards and/or protocols
defined by IEEE 802. 16m. However, persons of ordinary skill in the art having benefit of the present disclosure
should appreciate that alternative embodiments of the wireless communication system 100 may include access
nodes and/or access terminals that operate according to other standards and/or protocols. For example, the
access node 105(2) may support wireless communication according to one or more legacy standards and/or
protocols. Moreover, alternate embodiments of the techniques described herein may be implemented in other
types of systems and/or devices that use wireless communication techniques.
Access terminals 110 such as mobile units can access the wireless communication system 100 over an
air interface between the access terminals 110 and the access node 105. In the illustrated embodiment, the
access terminals 110 are legacy devices that use a single fixed length identifier to identify the access terminals
110 over the air interface and throughout the network. Exemplary fixed length identifiers include 48-bit mobile
station identifiers that are used in WiMAX systems that operate according to IEEE 802. 16e standards and/or
protocols. Alternatively, in GSM and/or UMTS systems, identifiers such as International Mobile Subscriber
Identity (IMSI) numbers may be used to identify the legacy access terminals 110. Fixed length identifiers may
be assigned to access terminals 110 when they are manufactured and/or configured prior to use within the
network 100. Fixed length identifiers are typically permanently allocated so that they can always be used to
uniquely identify an access terminal 110.
Access terminals 115 operate according to different standards and/or protocols than the access
terminals 110. In the illustrated embodiment, the access terminals 115 are advanced devices that can be
identified over the air interfaces using one of a set of mode-dependent identifiers. As used herein, the term
"mode-dependent identifier" is used to indicate that the different mode-dependent identifiers are used to identify
the access terminal 115 in different operational modes. In one embodiment, the different identifiers may have
different lengths. For example, identifiers of 10 bits, 12 bits, 18 bits, 24 bits, 48 bits, or 72 bits may be used as
one or more of the mode-dependent identifiers. In one embodiment, the set of mode-dependent identifiers is
defined by the relevant standards and/or protocols. For example, the WiMAX standards and/or protocols may
define the set of available mode-dependent identifiers in the manner indicated in Table 1. However, persons of
ordinary skill in the art having benefit of the present disclosure should appreciate that the particular set of modedependent
identifiers shown in Table 1 is intended to be exemplary and other sets may be defined for alternative
embodiments.
Table 1
ID NAME LENGTH DESCRIPTION
MAC ID 48 bits When it is used in header
STID Station ID 12 bits Used when MS is connected
TSTID Temporary Station ID 12 bits Used until STID is allocated
DID De-registration ID 18 bits Used when MS is in idle mode
CRID Context Retention ID 72 bits Assigned during initial network entry
MSTID Multicast Station ID 12 bits Identifies multicast broadcast flows with flow
identifier
The access terminals 110, 115 may implement different operational modes such as an active mode and
an inactive or idle mode. The active mode is used when the access terminal 110, 115 has an active
communication session or call with the system 100. Access terminals 110, 115 may conserve power and air
interface resources by entering the idle mode when it is not actively communicating with the system 100. In one
embodiment, the idle mode allows the access terminal 110, 115 to use lower power modes and to not be
registered with any access node 105 and yet the access terminal 110, 115 may receive downlink broadcast
traffic, e.g., when it wakes up during an allocated paging cycle and/or paging offset to monitor a paging channel.
Idle access terminals 110, 115 can be paged when downlink traffic arrives in the system 100. For example, one
or more of the access nodes 105 may form a paging group associated with a paging controller that is used to
page the idle access terminal 110, 115 located in the vicinity of the access nodes. Access terminals 110, 115
may be assigned to a paging controller in the paging group by the access node 105 before going into idle mode
and the access terminals 110, 115 may periodically wake up to either receive data or to update location change
with their paging controller.
In the illustrated embodiment, the wireless communication system 100 includes one or more paging
controllers 120 that are used to support paging operations in the wireless communication system 100.
Exemplary embodiments of the paging controllers 120 may be implemented in different network entities such as
access serving network gateways (ASN-GWs). Access terminals 110, 115 are assigned a paging controller 120
when they are preparing to enter the idle mode. For example, an access terminal 110, 115 that is entering the
idle mode may send a message to the associated access node 105, which may then convey this information to
the paging controller 120 to provide notification of idle mode entry. Since the access terminals 110 use a
different idle mode identifier than the access terminals 115, the paging controller 120 handles the idle mode
entry of the different types of access terminals 110, 115 in different ways. In the illustrated embodiment, the
paging controller 120 determines whether the requesting device is a legacy device such as an access terminal
110 or an advanced device such as an access terminal 115. The fixed length identifiers for idle legacy devices
are stored in a first database 125 and the identifier for idle advanced devices are stored in a second database 130.
Persons of ordinary skill in the art having benefit of the present disclosure should appreciate that alternative
embodiments may use other techniques for identifying and grouping legacy and advanced devices, such as using
a single database with entries that include a field that indicates legacy or advanced devices.
Different time intervals are allocated for paging the advanced and legacy devices. In the illustrated
embodiment, mutually exclusive sets or sequences of paging cycles are allocated to idle access terminals 110
and idle access terminals 115, respectively. For example, idle legacy access terminals 110 may be allocated to
paging cycles that are identified by an even value of a paging cycle number and idle advanced access terminals
115 may be allocated to paging cycles that are identified by an odd value of a paging cycle number. However,
other mutually exclusive or non-overlapping sets or sequences of paging cycles may be allocated to the legacy
and advanced devices. For example, in systems that are expected to include a relatively large number of
advanced access terminals 115 relative to the number of legacy access terminals 110, a relatively larger
proportion of the paging cycles may be allocated to advanced devices. Moreover, the mutually exclusive time
intervals used to page the different types of devices may be defined in terms of paging offsets in addition to or
instead of distinguishing between the different paging intervals on the basis of paging cycles. Information
identifying the allocated paging time intervals, cycles, and/or offsets may then be transmitted to the access
terminals 110, 115 so that they will know to monitor a paging channel for paging advertisement messages
during the appropriate paging time interval, cycle, and/or offset.
Figure 2 conceptually illustrates one exemplary embodiment of a sequence 200 of paging cycles and
paging offsets. In the illustrated embodiment, the sequence 200 includes a series of paging cycles 205 that
repeat over time. Each paging cycle 205 includes a plurality of time slots or time intervals 210 that may be
indicated using a corresponding paging offset 215. The paging cycles 205(1) and/or paging offsets 215(1) may
be allocated to legacy devices so that idle legacy devices can monitor paging channels during the indicated time
intervals. The paging cycles 205(2) and/or paging offsets 215(2) may be allocated to advanced devices so that
idle advanced devices can monitor paging channels during the indicated time intervals.
Referring back to Figure 1, the paging controller 120 can page one or more of the idle access terminals
110, 115 in response to receiving information and/or messages addressed to the corresponding access terminals
110, 115. In one embodiment, the network 100 receives a message that is addressed to an idle access terminal
110. The paging controller 120 (or other entity within the network 100) then determines whether the idle access
terminal 110 is a legacy device or an advanced device. For example, the paging controller 120 may use the
access terminal address to find the appropriate identifier in either the legacy database 125 or the advanced
database 130. Alternatively, the paging controller 120 may search for the identifier and then use information in
the database to determine whether the device is a legacy device or an advanced device. Based on this
determination, the paging controller 120 may create a paging advertisement message and distribute this message
to the various access nodes 105.
Different idle mode addresses or identifiers are used to page legacy and advanced devices. Paging
advertisement messages for legacy devices may include a hashed version of the legacy identifier and they may
be transmitted over the air interface during the allocated legacy paging cycles and/or paging offsets. For
example, the idle mode address may be a 24-bit field used to hash the access terminals 48-bit media access
control (MAC) address. The hash value may be defined as the remainder of the division (modulo-2) of the 48-
bit address multiplied by a polynomial D24 that is derived using the generator polynomial:
D = 2* + i 2 - - - - 17 + * - - - 1
For example, the 48-bit address 00:D0:59:0F:E2:2E would hash to the 24-bit identifier 0x5 1efe3 in this
embodiment. Paging advertisement messages for advanced devices may include the appropriate idle mode
identifier and they may be transmitted over the air interface during the allocated advanced paging cycles and/or
paging offsets. In one embodiment, the idle mode identifier is a deregistration identifier that uniquely identifies
the advanced access terminal within a set defined by a paging group identifier, a paging cycle, and a paging
offset. Exemplary parameters for one embodiment of a paging advertisement message format are shown in
Table 2. However, persons of ordinary skill in the art having benefit of the present disclosure should appreciate
that the particular set of parameters shown in Table 2 is intended to be exemplary and other sets may be defined
for alternative embodiments.
Figures 3A and 3B conceptually illustrate embodiments of paging advertisement messages 300(1-2) for
legacy devices and advanced devices, respectively. In the illustrated embodiment, each paging advertisement
message includes a message header 305 and a message body 310. The message header 305 includes an
identifier 315 of the access terminal that is being paged. Paging advertisement messages 300(1) that are
addressed to legacy devices may include an idle mode identifier 315(1) that is derived from the permanent
mobile station identifier. For example, the idle mode identifier 315(1) used to identify legacy devices may be a
24-bit hashed version of the permanent 48-bit mobile station identifier assigned to the legacy device. Paging
advertisement messages 300(2) that are addressed to advanced devices may include an idle mode identifier
315(2) such as a deregistration identifier that is defined by the relevant standards and/or protocols, such as the
IEEE 802.16m standards for WiMAX. Alternatively, a pseudo-identifier can be allocated to the advanced
device and then the pseudo-identifier may be used to generate the idle mode identifier 315(2). For example, a
48-bit pseudo-identifier can be allocated to the advanced device on initial network entry and then a hashed
version of the pseudo-identifier can be used as the idle mode identifier 315(2). The pseudo-identifier may be
selected to reduce or avoid the possibility of collisions with legacy mobile station identifiers and/or hashed
versions of the legacy mobile station identifiers associated with other legacy devices.
Figure 4 conceptually illustrates one exemplary embodiment of a method 400 for setting the paging
parameters of an access terminal. In the illustrated embodiment, a notification is received (at 405) indicating
that an access terminal is entering the idle mode, e.g., by switching to a lower power mode and releasing air
interface resources. The notification may be received at an access node and then conveyed to other entities in
the network such as a paging controller. In response to receiving the notification, the network determines (at
410) whether the access terminal is a legacy device or an advanced device. If the access terminal is a legacy
device that uses a single fixed length identifier to identify the device, the legacy identifier may be stored (at
415). For example, the paging controller may store (at 415) the legacy identifier in a database. The database
may be implemented as a separate database used only for legacy devices or it may be implemented as part of a
single database that is used for both legacy and advanced databases. In embodiments that use a single database
for both types of device, the paging controller may also store (at 415) information indicating that the access
terminal is a legacy device. The paging controller assigns (at 420) one or more paging cycles and/or paging
offsets to the legacy device. This information may be stored and also conveyed to the access terminal and
appropriate access nodes so that they know which paging cycles and/or paging offsets should be monitored
and/or used to page the access terminal.
If the network determines (at 410) that the access terminal is an advanced device that uses modedependent
identifiers depending on the operational mode of the advanced device, then the appropriate advanced
idle mode identifier may be stored (at 425) the database. As discussed herein, the database may be specifically
allocated to advanced devices or maybe part of a database that stores information for both legacy and advanced
devices. In one embodiment, the idle mode identifier is a deregistration identifier that is one of the modedependent
identifiers associated with the advanced device. Alternatively, a 48 bit pseudo-identifier may be
assigned to the advanced device, e.g. , at initial network entry, and then the pseudo-identifier may be used as the
idle mode identifier and stored (at 425) in the database. The paging controller assigns (at 430) one or more
paging cycles and/or paging offsets to the advanced device. The paging cycles and/or offsets assigned to the
advanced device are different than the paging cycles and/or offsets assigned to legacy devices. For example,
mutually exclusive sequences of paging cycles/offsets may be allocated to legacy and advanced devices. This
information may be stored and also conveyed to the access terminal and appropriate access nodes so that they
will know which paging cycles and/or paging offsets should be monitored and used to page the access terminal.
Figure 5 conceptually illustrates one exemplary embodiment of a method of 500 for paging legacy
devices and/or advanced devices. In the illustrated embodiment, the network receives (at 505) a downlink
message that is addressed to an idle access terminal. In response to receiving the message, an entity in the
network such as a paging controller determines (at 510) whether the idle access terminal is a legacy device or an
advanced device. If the idle access terminal is a legacy device, then the paging controller may form (at 515) a
paging advertisement message using the legacy fixed length identifier. For example, the paging controller may
form (at 515) a 24-bit hashed version of a 48-bit mobile station identifier and then includes the hashed identifier
in the paging advertisement message. The paging advertisement message may then be transmitted (at 520) or
broadcast over the air interface in the paging cycles and/or offsets allocated to legacy devices using one or more
access nodes. For example, the paging controller may distribute the paging advertisement message to different
groups of access nodes according to a predetermined paging scheme or algorithm until the paging controller
receives a response from the access terminal.
If the idle access terminal is an advanced device, then the paging controller can form (at 525) a paging
advertisement message using an idle mode identifier such as the deregistration identifier associated with the
access terminal. For example, the paging controller may include the deregistration identifier in the paging
advertisement message. Exemplary deregistration identifiers may include 12 bits, 18 bits, 24 bits, or other
numbers of bits. A 24-bit deregistration identifier may advantageously be used to harmonize the identifiers used
by legacy and advanced devices by using the same number of bits in the deregistration identifier used by
advanced devices and the hashed version of the fixed length identifier used by legacy devices. Alternatively, the
idle access terminal may be identified using a hashed version of a pseudo-identifier assigned to advanced
devices, e.g., at initial network entry of the access terminal. The paging advertisement message may then be
transmitted (at 530) or broadcast by one or more access nodes over the air interface in the paging cycles and/or
offsets allocated to the advanced devices. For example, the paging controller may distribute the paging
advertisement message to different groups of access nodes according to a predetermined paging scheme or
algorithm until the paging controller receives a response from the access terminal via one of the access modes.
Figure 6 conceptually illustrates one exemplary embodiment of a method 600 for allocating fixed
length identifiers such as pseudo-identifiers to access terminals. In the illustrated embodiment, an entity in the
network such as a base station or other access nodes such as ASN-GW or core network nodes receives (at 605) a
message during initial network entry of an access terminal. The received message includes information
indicating the identity of the access terminal. In one embodiment, the identity of the access terminal is indicated
using the true or permanent mobile station identifier, e.g., the 48 bit identifier that is given to the access terminal
when it is manufactured and/or configured. The network entity then determines (at 610) whether the access
terminal is a legacy device or an advanced device that supports the use of mode-dependent identifiers to identify
the access terminal during communication over an air interface. If the access terminal is a legacy device, then
the mobile station identifier can be provided (at 615) to other network elements such as ASN-GWs, AAA
servers, and the like so that these network-side elements can use the identifier to identify the access terminal.
Alternatively, the network entity may assign a pseudo-identifier that has the same number of bits as the mobile
station identifier and then provide (at 615) the pseudo-identifier to the network so that the pseudo-identifier can
be used to identify the access terminal without revealing the true mobile station identifier.
If the network entity determines (at 610) that the access terminal supports mode-dependent identifiers,
then a fixed length identifier can be allocated (at 620) to the access terminal. The fixed length identifier can
then be used to identify the access terminal, e.g., in messages transmitted over interfaces between network
elements such as base stations, ASN-GWs, AAA servers, and the like. For example, the fixed length identifier
may be a 48 bit identifier allocated to the access terminal. The fixed length identifier may be a random number
or may be derived from one or more other identifiers for information associated with the access terminal. The
fixed length identifier may also be associated (at 625) with the mode-dependent identifiers that are used to
identify the access terminal and communications over the air interface. In one embodiment, the network entity
creates a database entry including the information that associates the fixed and mode-dependent identifiers for
the access terminal. The database can be accessed to map or translate between fixed and mode-dependent
identifiers for uplink and/or downlink communication. The network entity can then provide (at 630) the fixed
length identifier to other elements in the network. In various embodiments, portions of the method 600 may be
performed before, concurrently with, or after authentication, authorization, and/or accounting processes are
performed for the access terminal.
Portions of the disclosed subject matter and corresponding detailed description are presented in terms
of software, or algorithms and symbolic representations of operations on data bits within a computer memory.
These descriptions and representations are the ones by which those of ordinary skill in the art effectively convey
the substance of their work to others of ordinary skill in the art. An algorithm, as the term is used here, and as it
is used generally, is conceived to be a self-consistent sequence of steps leading to a desired result. The steps are
those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities
take the form of optical, electrical, or magnetic signals capable of being stored, transferred, combined,
compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common
usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
It should be borne in mind, however, that all of these and similar terms are to be associated with the
appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically
stated otherwise, or as is apparent from the discussion, terms such as "processing" or "computing" or
"calculating" or "determining" or "displaying" or the like, refer to the action and processes of a computer
system, or similar electronic computing device, that manipulates and transforms data represented as physical,
electronic quantities within the computer system's registers and memories into other data similarly represented
as physical quantities within the computer system memories or registers or other such information storage,
transmission or display devices.
Note also that the software implemented aspects of the disclosed subject matter are typically encoded
on some form of program storage medium or implemented over some type of transmission medium. The
program storage medium may be magnetic (e.g., a floppy disk or a hard drive) or optical (e.g., a compact disk
read only memory, or "CD ROM"), and may be read only or random access. Similarly, the transmission
medium may be twisted wire pairs, coaxial cable, optical fiber, or some other suitable transmission medium
known to the art. The disclosed subject matter is not limited by these aspects of any given implementation.
The particular embodiments disclosed above are illustrative only, as the disclosed subject matter may
be modified and practiced in different but equivalent manners apparent to those skilled in the art having the
benefit of the teachings herein. Furthermore, no limitations are intended to the details of construction or design
herein shown, other than as described in the claims below. It is therefore evident that the particular
embodiments disclosed above may be altered or modified and all such variations are considered within the
scope of the disclosed subject matter. Accordingly, the protection sought herein is as set forth in the claims
below.
CLAIMS
WHAT IS CLAIMED:
1. A method, comprising:
receiving a notification that an access terminal is entering an idle mode;
determining whether the access terminal is a legacy device identified by a fixed length identifier or an
advanced device identified by one of a plurality of mode-dependent identifiers, wherein said one of the modedependent
identifiers is used to identify the advanced device in the idle mode; and
allocating at least one first paging cycle to the access terminal when it is a legacy device or at least one
second paging cycle, different than said at least one first paging cycle, to the access terminal when it is an
advanced device.
2. The method of claim 1, wherein determining whether the access terminal is a legacy device or an
advanced device comprises determining whether the access terminal is a legacy device or an advanced device
using information associated with the access terminal that is stored in an access node associated with the access
terminal.
3. The method of claim 1, wherein allocating said at least one first paging cycle or said at least one second
paging cycle comprises allocating a first sequence of first paging cycles or a second sequence of second paging
cycles, wherein the first and second sequences comprise mutually exclusive paging cycles.
4. The method of claim 1, comprising storing the fixed length identifier when the access terminal is a
legacy device and storing said one of the mode-dependent identifiers when the access terminal is an advanced
device, wherein storing said one of the mode-dependent identifiers comprises storing an 18-bit deregistration
identifier that is used to identify the access terminal when the access terminal is in the idle mode.
5. The method of claim 4, comprising receiving information addressed to the access terminal and forming
a paging advertisement message comprising a hashed representation of the fixed length identifier when the
access terminal is a legacy device or the de-registration identifier when the access terminal is an advanced
device.
6. The method of claim 4, wherein storing said one of the mode-dependent identifiers comprises storing a
pseudo-identifier that is the same length as a fixed length identifier used by legacy devices, and comprising
receiving information addressed to the access terminal and forming a paging advertisement message comprising
a hashed representation of the fixed length identifier when the access terminal is a legacy device or a hashed
representation of the pseudo-identifier when the access terminal is an advanced device.
7. The method of claims 5 or 6, comprising transmitting the paging advertisement message in said at least
one first paging cycle when the access terminal is a legacy device or said at least one second paging cycle when
the access terminal is an advanced device.
8. A method, comprising:
receiving at least one message addressed to an idle access terminal;
determining whether the idle access terminal is a legacy device identified by a fixed length identifier or
an advanced device identified by one of a plurality of mode-dependent identifiers, wherein said one of the
mode-dependent identifiers is used to identify the advanced device in the idle mode; and
paging the idle access terminal during at least one first paging cycle when it is a legacy device and at
least one second paging cycle, different than said at least one first paging cycle, when it is an advanced device.
9. The method of claim 8, wherein paging the idle access terminal comprises paging the idle access
terminal in at least one of a first plurality of first paging cycles when the idle access terminal is a legacy device
or one of a first plurality of second paging cycles when the idle access terminal is an advanced device, and
wherein the first and second pluralities comprise mutually exclusive paging cycles.
10. The method of claim 8, wherein paging the idle access terminal comprises forming a paging
advertisement message comprising a hashed representation of the fixed length identifier when the access
terminal is a legacy device or an 18-bit de-registration identifier when the access terminal is an advanced device.
11. The method of claim 8, wherein paging the idle access terminal comprises forming a paging
advertisement message comprising a hashed representation of the fixed length identifier when the access
terminal is a legacy device or a hashed representation of a pseudo-identifier allocated to the access terminal
when the access terminal is an advanced device.
12. The method of claims 10 or 11, comprising transmitting the paging advertisement message in said at
least one first paging cycle when the access terminal is a legacy device or said at least one second paging cycle
when the access terminal is an advanced device.

Documents

Application Documents

# Name Date
1 10487-CHENP-2012 POWER OF ATTORNEY 17-12-2012.pdf 2012-12-17
2 10487-CHENP-2012 PCT PUBLICATION 17-12-2012.pdf 2012-12-17
3 10487-CHENP-2012 FORM-5 17-12-2012.pdf 2012-12-17
4 10487-CHENP-2012 FORM-3 17-12-2012.pdf 2012-12-17
5 10487-CHENP-2012 FORM-2 FIRST PAGE 17-12-2012.pdf 2012-12-17
6 10487-CHENP-2012 FORM-18 17-12-2012.pdf 2012-12-17
7 10487-CHENP-2012 FORM-1 17-12-2012.pdf 2012-12-17
8 10487-CHENP-2012 DRAWINGS 17-12-2012.pdf 2012-12-17
9 10487-CHENP-2012 DESCRIPTION (COMPLETE) 17-12-2012.pdf 2012-12-17
10 10487-CHENP-2012 CORRESPONDENCE OTHERS 17-12-2012.pdf 2012-12-17
11 10487-CHENP-2012 CLAIMS SIGNATURE LAST PAGE 17-12-2012.pdf 2012-12-17
12 10487-CHENP-2012 CLAIMS 17-12-2012.pdf 2012-12-17
13 10487-CHENP-2012.pdf 2012-12-18
14 10487-CHENP-2012 CORRESPONDENCE OTHERS 21-05-2013.pdf 2013-05-21
15 10487-CHENP-2012 ASSIGNMENT 21-05-2013.pdf 2013-05-21
16 10487-CHENP-2012 FORM-3 19-06-2013.pdf 2013-06-19
17 10487-CHENP-2012 CORRESPONDENCE OTHERS 19-06-2013.pdf 2013-06-19
18 10487-CHENP-2012 FORM-3 12-11-2013.pdf 2013-11-12
19 10487-CHENP-2012 CORRESPONDENCE OTHERS 12-11-2013.pdf 2013-11-12
20 abstract10487-CHENP-2012.jpg 2014-04-04
21 10487-CHENP-2012 CORRESPONDENCE OTHERS 27-06-2014.pdf 2014-06-27
22 10487-CHENP-2012 FORM-3 14-08-2014.pdf 2014-08-14
23 10487-CHENP-2012 CORRESPONDENCE OTHERS 14-08-2014.pdf 2014-08-14
24 3758-CHENP-2012 CORRESPONDENCE OTHERS 20-10-2014.pdf 2014-10-20
25 3758-CHENP-2012 FORM-3 20-10-2014.pdf 2014-10-20
26 10487-CHENP-2012 FORM-3 20-10-2014.pdf 2014-10-20
27 10487-CHENP-2012 CORRESPONDENCE OTHERS 20-10-2014.pdf 2014-10-20
28 10487-CHENP-2012 FORM-3 03-03-2015.pdf 2015-03-03
29 10487-CHENP-2012 CORRESPONDENCE OTHERS 03-03-2015.pdf 2015-03-03
29 10487-CHENP-2012 CORRESPONDENCE OTHERS 20-10-2014.pdf 2014-10-20
30 10487-CHENP-2012. FORM-3 10-06-2015.pdf 2015-06-10
31 10487-CHENP-2012. CORRESPONDENCE OTHERS 10-06-2015.pdf 2015-06-10
31 3758-CHENP-2012 FORM-3 20-10-2014.pdf 2014-10-20
32 10487-CHENP-2012-Form 3-151015.pdf 2016-03-18
33 10487-CHENP-2012-Correspondence-151015.pdf 2016-03-18
34 Form 3 [02-06-2016(online)].pdf 2016-06-02
35 10487-CHENP-2012-Form 3-290216.pdf 2016-07-04
36 10487-CHENP-2012-Correspondence-F3-290216.pdf 2016-07-04
37 Form 3 [23-11-2016(online)].pdf 2016-11-23
38 Form 3 [24-11-2016(online)].pdf 2016-11-24
39 Form 3 [03-05-2017(online)].pdf 2017-05-03
40 10487-CHENP-2012-FER.pdf 2018-11-16
41 10487-CHENP-2012-PETITION UNDER RULE 137 [14-05-2019(online)].pdf 2019-05-14
42 10487-CHENP-2012-OTHERS [14-05-2019(online)].pdf 2019-05-14
43 10487-CHENP-2012-FORM 3 [14-05-2019(online)].pdf 2019-05-14
44 10487-CHENP-2012-FER_SER_REPLY [14-05-2019(online)].pdf 2019-05-14
45 10487-CHENP-2012-DRAWING [14-05-2019(online)].pdf 2019-05-14
46 10487-CHENP-2012-COMPLETE SPECIFICATION [14-05-2019(online)].pdf 2019-05-14
47 10487-CHENP-2012-CLAIMS [14-05-2019(online)].pdf 2019-05-14
48 10487-CHENP-2012-ABSTRACT [14-05-2019(online)].pdf 2019-05-14
49 10487-CHENP-2012_Marked up Claims_Granted 326181_28-11-2019.pdf 2019-11-28
50 10487-CHENP-2012_Drawings_Granted 326181_28-11-2019.pdf 2019-11-28
51 10487-CHENP-2012_Description_Granted 326181_28-11-2019.pdf 2019-11-28
52 10487-CHENP-2012_Claims_Granted 326181_28-11-2019.pdf 2019-11-28
53 10487-CHENP-2012_Abstract_Granted 326181_28-11-2019.pdf 2019-11-28
54 10487-CHENP-2012-PatentCertificate28-11-2019.pdf 2019-11-28
55 10487-CHENP-2012-IntimationOfGrant28-11-2019.pdf 2019-11-28

Search Strategy

1 Search10487CHENP2012_12-11-2018.pdf

ERegister / Renewals

3rd: 24 Feb 2020

From 16/06/2013 - To 16/06/2014

4th: 24 Feb 2020

From 16/06/2014 - To 16/06/2015

5th: 24 Feb 2020

From 16/06/2015 - To 16/06/2016

6th: 24 Feb 2020

From 16/06/2016 - To 16/06/2017

7th: 24 Feb 2020

From 16/06/2017 - To 16/06/2018

8th: 24 Feb 2020

From 16/06/2018 - To 16/06/2019

9th: 24 Feb 2020

From 16/06/2019 - To 16/06/2020

10th: 24 Feb 2020

From 16/06/2020 - To 16/06/2021