U.S. patent application number 14/494161 was filed with the patent office on 2015-04-23 for mobility information reporting.
The applicant listed for this patent is Candy Yiu, Yujian Zhang. Invention is credited to Candy Yiu, Yujian Zhang.
Application Number | 20150111581 14/494161 |
Document ID | / |
Family ID | 52826088 |
Filed Date | 2015-04-23 |
United States Patent
Application |
20150111581 |
Kind Code |
A1 |
Yiu; Candy ; et al. |
April 23, 2015 |
MOBILITY INFORMATION REPORTING
Abstract
Technology for reporting mobility information is disclosed.
Mobility information can be identified for the UE when the UE is in
idle mode, the mobility information including a visited cell
history for the UE when the UE is in idle mode. An evolved node B
(eNB) can be notified that the mobility information for the UE is
available when the UE transitions from the idle mode to a connected
mode. A request can be received from the eNB for the mobility
information. The mobility information can be sent to the eNB using
a reduced number of bits to represent the mobility information
while substantially maintaining a level of accuracy of a mobility
state estimation for the UE, wherein the mobility state estimation
is performed at the eNB in order to determine an estimated speed of
the UE.
Inventors: |
Yiu; Candy; (Beaverton,
OR) ; Zhang; Yujian; (Beijing, CN) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Yiu; Candy
Zhang; Yujian |
Beaverton
Beijing |
OR |
US
CN |
|
|
Family ID: |
52826088 |
Appl. No.: |
14/494161 |
Filed: |
September 23, 2014 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
61893792 |
Oct 21, 2013 |
|
|
|
Current U.S.
Class: |
455/437 ;
455/561 |
Current CPC
Class: |
H04L 47/28 20130101;
H04W 4/027 20130101; H04L 47/2466 20130101; H04W 72/085 20130101;
H04W 36/00 20130101; H04L 5/14 20130101; H04B 7/00 20130101; H04W
36/0069 20180801; H04W 72/0446 20130101; H04L 65/1016 20130101;
H04W 76/00 20130101; H04W 8/08 20130101; H04W 28/0247 20130101;
H04W 92/02 20130101; H04W 64/006 20130101; H04W 72/0413 20130101;
H04L 1/1607 20130101; H04M 11/04 20130101; Y02D 30/70 20200801;
H04W 88/08 20130101; H04L 65/1069 20130101; H04W 4/022 20130101;
H04W 36/0061 20130101; H04W 84/12 20130101; H04W 76/50 20180201;
H04W 28/08 20130101; G08B 25/016 20130101; H04L 1/1678 20130101;
H04L 47/2475 20130101; H04W 84/042 20130101; H04W 88/06 20130101;
H04W 28/0226 20130101; H04W 28/0268 20130101; H04L 65/1006
20130101; H04M 2242/04 20130101; H04W 4/90 20180201 |
Class at
Publication: |
455/437 ;
455/561 |
International
Class: |
H04W 36/00 20060101
H04W036/00; H04W 8/08 20060101 H04W008/08; H04W 64/00 20060101
H04W064/00 |
Claims
1-21. (canceled)
22. At least one non-transitory machine readable storage medium
having instructions embodied thereon for reporting mobility history
information, the instructions when executed perform the following:
saving, using at least one processor, mobility history information
at a user equipment (UE), the mobility history information
comprising a visited cell history that includes: an Evolved
Universal Terrestrial Access (EUTRA) global cell identifier (ID) or
a physical cell ID for one or more visited cells by the UE that are
included in the visited cell history; and a duration of stay of the
UE in the one or more visited cells that are included in the
visited cell history; and reporting, using the at least one
processor, the mobility history information in a visited cell
information element (IE) from the UE to an evolved node B
(eNB).
23. The at least one non-transitory machine readable storage medium
of claim 22, wherein the mobility history information includes the
visited cell history for the UE when the UE is in a radio resource
control (RRC) idle mode.
24. The at least one non-transitory machine readable storage medium
of claim 22, wherein the mobility history information includes the
visited cell history for the UE when the UE is in a radio resource
control (RRC) connected mode.
25. The at least one non-transitory machine readable storage medium
of claim 22, wherein the visited cell history in the mobility
history information includes the duration of stay and one or more
of the EUTRA global cell ID or the physical cell ID for up to 16
visited cells by the UE.
26. The at least one non-transitory machine readable storage medium
of claim 22, wherein the duration of stay of the UE in each visited
cell in the visited cell history is between 0 seconds and 4095
seconds.
27. The at least one non-transitory machine readable storage medium
of claim 22, further comprising instructions which when executed by
the at least one processor performs the following: identifying that
the duration of stay in a visited cell is greater than 4095
seconds; and setting the duration of stay for the visited cell in
the visited cell IE to 4095 seconds.
28. The at least one non-transitory machine readable storage medium
of claim 22, wherein the UE includes an antenna, a touch sensitive
display screen, a speaker, a microphone, a graphics processor, an
application processor, an internal memory, or a non-volatile memory
port.
29. A user equipment (UE) operable to report mobility history
information, the UE comprising one or more processors configured
to: save mobility history information at the UE, the mobility
history information comprising a visited cell history that includes
an Evolved Universal Terrestrial Access (EUTRA) global cell
identifier (ID) or a physical cell ID for one or more visited cells
by the UE that are included in the visited cell history, the
visited cell history including a duration of stay of the UE in the
one or more visited cells that are included in the visited cell
history; and report a visited cell information element (IE)
containing the mobility history information to an evolved node B
(eNB).
30. The UE of claim 29, wherein the mobility history information
includes the visited cell history for the UE when the UE is in a
radio resource control (RRC) idle mode.
31. The UE of claim 29, wherein the mobility history information
includes the visited cell history for the UE when the UE is in a
radio resource control (RRC) connected mode.
32. The UE of claim 29, wherein the visited cell history in the
mobility history information includes the duration of stay and one
or more of the EUTRA global cell ID or the physical cell ID for up
to 16 visited cells by the UE.
33. The UE of claim 29, wherein the duration of stay of the UE in a
visited cell in the visited cell history is between 0 seconds and
4095 seconds.
34. The UE of claim 29, wherein the one or more processors are
further configured to: identify that the duration of stay in a
visited cell is greater than 4095 seconds; and set the duration of
stay for the visited cell in the visited cell IE to 4095
seconds.
35. The UE of claim 29, wherein the UE includes an antenna, a touch
sensitive display screen, a speaker, a microphone, a graphics
processor, an application processor, an internal memory, or a
non-volatile memory port.
36. A system for reporting mobility history information, the system
comprising: a processing module configured to: collect mobility
history information at a user equipment (UE), the mobility history
information comprising a visited cell history that includes: an
Evolved Universal Terrestrial Access (EUTRA) global cell identifier
(ID) or a physical cell ID for each visited cell by the UE that is
included in the visited cell history; and a duration of stay of the
UE in each visited cell that is included in the visited cell
history; and store the mobility history information in a visited
cell information element (IE) at the UE, wherein the processing
module is stored in a digital memory device or is implemented in a
hardware circuit; and a transceiver module configured to report the
visited cell IE containing the mobility history information from
the UE to an evolved node B (eNB), the eNB performing a handover
decision using the mobility history information, wherein the
transceiver module is stored in a digital memory device or is
implemented in a hardware circuit.
37. The system of claim 36, wherein the processing module is
further configured to collect the mobility history information for
the UE when the UE is in a radio resource control (RRC) idle
mode.
38. The system of claim 36, wherein the processing module is
further configured to collect the mobility history information for
the UE when the UE is in a radio resource control (RRC) connected
mode.
39. The system of claim 36, wherein the visited cell history in the
mobility history information includes the duration of stay and one
or more of the EUTRA global cell ID or the physical cell ID for up
to 16 visited cells by the UE.
40. The system of claim 36, wherein the duration of stay of the UE
in each visited cell in the visited cell history is between 0
seconds and 4095 seconds.
41. The system of claim 36, wherein the processing module is
further configured to: identify that the duration of stay in a
visited cell is greater than 4095 seconds; and set the duration of
stay for the visited cell in the visited cell IE to 4095
seconds.
42. An evolved node B (eNB) operable to receive mobility history
information from a user equipment (UE), the eNB comprising one or
more processors configured to: receive a visited cell information
element (IE) from the UE, the visited cell IE including mobility
history information for the UE, wherein the mobility history
information comprises a visited cell history that includes an
Evolved Universal Terrestrial Access (EUTRA) global cell identifier
(ID) or physical cell ID for one or more visited cells by the UE
that are included in the visited cell history, the visited cell
history including a duration of stay of the UE in the one or more
visited cells that are included in the visited cell history.
43. The eNB of claim 42, wherein the mobility history information
includes the visited cell history for the UE when the UE is in a
radio resource control (RRC) idle mode.
44. The eNB of claim 42, wherein the mobility history information
includes the visited cell history for the UE when the UE is in a
radio resource control (RRC) connected mode.
45. The eNB of claim 42, wherein the visited cell history in the
mobility history information includes the duration of stay and one
or more of the EUTRA global cell ID or the physical cell ID for up
to 16 visited cells by the UE.
46. The eNB of claim 42, wherein the duration of stay of the UE in
a visited cell in the visited cell history is between 0 seconds and
4095 seconds.
47. At least one non-transitory machine readable storage medium
having instructions embodied thereon for receiving mobility history
information from a user equipment (UE), the instructions when
executed perform the following: receiving a visited cell
information element (IE) from the UE, the visited cell IE including
mobility history information for the UE, wherein the mobility
history information comprises a visited cell history that includes
an Evolved Universal Terrestrial Access (EUTRA) global cell
identifier (ID) or a physical cell ID for one or more visited cells
by the UE that are included in the visited cell history, the
visited cell history including a duration of stay of the UE in the
one or more visited cells that are included in the visited cell
history.
48. The at least one non-transitory machine readable storage medium
of claim 47, wherein the mobility history information includes the
visited cell history for the UE when the UE is in a radio resource
control (RRC) idle mode.
49. The at least one non-transitory machine readable storage medium
of claim 47, wherein the mobility history information includes the
visited cell history for the UE when the UE is in a radio resource
control (RRC) connected mode.
50. The at least one non-transitory machine readable storage medium
of claim 47, wherein the visited cell history in the mobility
history information includes the duration of stay and one or more
of the EUTRA global cell ID or the physical cell ID for up to 16
visited cells by the UE.
51. The at least one non-transitory machine readable storage medium
of claim 47, wherein the duration of stay of the UE in a visited
cell in the visited cell history is between 0 seconds and 4095
seconds.
Description
RELATED APPLICATIONS
[0001] The present application claims priority to U.S. Provisional
Patent Application No. 61/893,792, filed Oct. 21, 2013 with a
docket number of P61815Z, the entire specification of which is
hereby incorporated by reference in its entirety for all
purposes.
BACKGROUND
[0002] Wireless mobile communication technology uses various
standards and protocols to transmit data between a node (e.g., a
transmission station) and a wireless device (e.g., a mobile
device). Some wireless devices communicate using orthogonal
frequency-division multiple access (OFDMA) in a downlink (DL)
transmission and single carrier frequency division multiple access
(SC-FDMA) in an uplink (UL) transmission. Standards and protocols
that use orthogonal frequency-division multiplexing (OFDM) for
signal transmission include the third generation partnership
project (3GPP) long term evolution (LTE), the Institute of
Electrical and Electronics Engineers (IEEE) 802.16 standard (e.g.,
802.16e, 802.16m), which is commonly known to industry groups as
WiMAX (Worldwide interoperability for Microwave Access), and the
IEEE 802.11 standard, which is commonly known to industry groups as
WiFi.
[0003] In 3GPP radio access network (RAN) LTE systems, the node can
be a combination of Evolved Universal Terrestrial Radio Access
Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node
Bs, enhanced Node Bs, eNodeBs, or eNBs) and Radio Network
Controllers (RNCs), which communicates with the wireless device,
known as a user equipment (UE). The downlink (DL) transmission can
be a communication from the node (e.g., eNodeB) to the wireless
device (e.g., UE), and the uplink (UL) transmission can be a
communication from the wireless device to the node.
[0004] In homogeneous networks, the node, also called a macro node,
can provide basic wireless coverage to wireless devices in a cell.
The cell can be the area in which the wireless devices are operable
to communicate with the macro node. Heterogeneous networks
(HetNets) can be used to handle the increased traffic loads on the
macro nodes due to increased usage and functionality of wireless
devices. HetNets can include a layer of planned high power macro
nodes (or macro-eNBs) overlaid with layers of lower power nodes
(small-eNBs, micro-eNBs, pico-eNBs, femto-eNBs, or home eNBs
[HeNBs]) that can be deployed in a less well planned or even
entirely uncoordinated manner within the coverage area (cell) of a
macro node. The lower power nodes (LPNs) can generally be referred
to as "low power nodes", small nodes, or small cells.
[0005] In LTE, data can be transmitted from the eNodeB to the UE
via a physical downlink shared channel (PDSCH). A physical uplink
control channel (PUCCH) can be used to acknowledge that data was
received. Downlink and uplink channels or transmissions can use
time-division duplexing (TDD) or frequency-division duplexing
(FDD).
BRIEF DESCRIPTION OF THE DRAWINGS
[0006] Features and advantages of the disclosure will be apparent
from the detailed description which follows, taken in conjunction
with the accompanying drawings, which together illustrate, by way
of example, features of the disclosure; and, wherein:
[0007] FIG. 1 illustrates an accuracy of mobility state estimation
based on a number of cells a user equipment (UE) reports to a
network in accordance with an example;
[0008] FIGS. 2A-2B illustrate accuracies of mobility state
estimation based on a number of cells a user equipment (UE) reports
to a network and a resolution level in accordance with an
example;
[0009] FIG. 3 illustrates an accuracy of mobility state estimation
based on a maximum time of stay for a user equipment (UE) in
accordance with an example;
[0010] FIG. 4 is a mapping table used to represent mobility
information for a user equipment (UE) using a reduced number of
bits in accordance with an example;
[0011] FIG. 5 illustrates an accuracy of mobility state estimation
based on a type of mapping number used to represent the mobility
information for a user equipment (UE) in accordance with an
example;
[0012] FIG. 6 illustrates signaling between a user equipment (UE)
and an evolved node B (eNB) to determine a mobility state
estimation for the UE in accordance with an example;
[0013] FIG. 7 depicts functionality of computer circuitry of a user
equipment (UE) operable to report mobility information in
accordance with an example;
[0014] FIG. 8 depicts functionality of computer circuitry of an
evolved node B (eNB) operable to utilize mobility information
associated with a user equipment (UE) in accordance with an
example;
[0015] FIG. 9 depicts a flowchart of a method for reporting
mobility information in accordance with an example; and
[0016] FIG. 10 illustrates a diagram of a wireless device (e.g.,
UE) in accordance with an example.
[0017] Reference will now be made to the exemplary embodiments
illustrated, and specific language will be used herein to describe
the same. It will nevertheless be understood that no limitation of
the scope of the invention is thereby intended.
DETAILED DESCRIPTION
[0018] Before the present invention is disclosed and described, it
is to be understood that this invention is not limited to the
particular structures, process steps, or materials disclosed
herein, but is extended to equivalents thereof as would be
recognized by those ordinarily skilled in the relevant arts. It
should also be understood that terminology employed herein is used
for the purpose of describing particular examples only and is not
intended to be limiting. The same reference numerals in different
drawings represent the same element. Numbers provided in flow
charts and processes are provided for clarity in illustrating steps
and operations and do not necessarily indicate a particular order
or sequence.
EXAMPLE EMBODIMENTS
[0019] An initial overview of technology embodiments is provided
below and then specific technology embodiments are described in
further detail later. This initial summary is intended to aid
readers in understanding the technology more quickly but is not
intended to identify key features or essential features of the
technology nor is it intended to limit the scope of the claimed
subject matter.
[0020] A user equipment (UE) can report mobility information to a
network device, such as an evolved node B (eNB), upon transitioning
from a radio resource control (RRC) idle mode into an RRC connected
mode. In other words, when the UE switches to RRC connected from
RRC idle, the UE can communicate the mobility information to the
eNB. In one example, the UE can indicate an availability of a
visited cell history to the eNB when the UE transitions from RRC
idle to RRC connected. The eNB can receive the indication, and in
response, request the visited cell history from the UE.
[0021] The mobility information can include a physical cell
identifier (ID) and a time of stay for which the UE stays in a cell
corresponding with the physical cell ID. The time of stay for each
physical cell ID can be represented in seconds. Alternatively, the
mobility information can include a global cell ID and a time of
stay for which the UE stays in a cell corresponding with the global
cell ID. In other words, the visited cell history requested by the
eNB can include the physical/global cell IDs and the time of stay
(in seconds) for each physical/global cell ID. The physical cell ID
can range from 0-503 and can be represented using up to nine
bits.
[0022] The UE's mobility information (or visited cell history) can
include a plurality of physical cell IDs and time of stays. As a
non-limiting example, the mobility information can include a first
physical cell ID of 412 and an associated time of stay of 5.2
seconds, a second physical cell ID of 416 and an associated time of
stay of 8.3 seconds, and so on. The physical cell IDs can be
represented using nine bits, and as discussed in further detail
below, the time of stay can be represented using a reduced number
of bits (e.g., 3 to 8 bits).
[0023] The UE can provide the mobility information to the eNB, and
based on UE's mobility information, the eNB can perform a mobility
state estimation for the UE. The mobility state estimation can
refer to the UE's speed in idle mode or connected mode. The eNB can
use the physical cell IDs and/or global cell IDs that were visited
by the UE, as well as the time of stay for each of the physical
cell IDs and/or global cell IDs, in order to determine the mobility
state estimation for the UE. In other words, the physical/global
cell IDs and the corresponding time of stay information can be used
to determine the UE's mobility state (e.g., the UE's speed in idle
mode or connected mode). When the UE switches from the RRC idle
mode to the RRC connected mode, the eNB can set one or more
handover parameters according to the estimated UE mobility state
(e.g., the UE's estimated speed). In other words, the eNB can use
the mobility state estimation for the UE in order to set the
handover parameters for the UE. In one example, the eNB can set the
handover parameters based on the UE's mobility state in order to
enhance handover performance. The handover parameters that are
configured based on the UE's speed can include, but are not limited
to, time to trigger (ttt), A3offset, T312, etc. Each of these
handover parameters can affect handover performance.
[0024] A novel technique is described herein for representing the
time of stay information (that is transmitted from the UE to the
eNB along with the physical/global cell IDs) using a reduced number
of bits, while not compromising an accuracy of the mobility state
estimation at the network side (e.g., at the eNB). In other words,
the calculation of the UE's mobility state can remain substantially
accurate, even though a reduced number of bits are used to
represent the time of stay information. A mathematical model can be
used to estimate the UE speed at the network side based on a cell
size (e.g., a cell size of a macro cell or a pico cell). A novel
mapping table is described herein that represents specific time
sequences, which can reduce the entropy of the time of stay
information. As a result, the UE's mobility state can be determined
with substantially the same accuracy as full resolution time of
stay information, even though the number of bits used to represent
the time of stay can be reduced by more than 50%.
[0025] In one example, representing a time of stay of 408 seconds
can take 9 bits. The number of bits used to represent the time of
stay (in seconds) can be calculated using the equation 2.sup.n,
wherein n is the number of bits. 2.sup.8 is equal to 256, and
therefore, 8 bits is not sufficient to represent the time of stay
of 408 seconds. On the other hand, 2.sup.9 is equal to 512, and
therefore, 9 bits is sufficient to represent the time of stay of
408 seconds. In this example, the time of stay is represented using
the full resolution (i.e., every second of the time of stay is
accounted for when determining the number of bits for representing
the time of stay). The time sequence used to represent the 408
seconds can be 1, 2, 3, . . . 407, 408.
[0026] In past solutions, according to the equation 2.sup.n, 1 bit
can be used to represent a time of stay of 1 second, 2 bits can be
used to represent a time of stay for up to 4 seconds, 3 bits can be
used to represent a time of stay for up to 8 seconds, 4 bits can be
used to represent a time of stay for up to 16 seconds, 5 bits can
be used to represent a time of stay for up to 32 seconds, 6 bits
can be used to represent a time of stay for up to 64 seconds, 7
bits can be used to represent a time of stay for up to 128 seconds,
8 bits can be used to represent a time of stay for up to 256
seconds, 9 bits can be used to represent a time of stay for up to
512 seconds, 10 bits can be used to represent a time of stay for up
to 1024 seconds, and so on.
[0027] In the novel technique described herein, the time of stay
can be represented in a defined resolution in order to reduce the
number of bits used to represent the time of stay. For example, the
time of stay can be represented as a five second interval (e.g., 5
second, or 10 seconds, or 15 seconds). In other words, the time of
stay can be represented according to N resolutions, wherein N is an
integer. Therefore, a time of stay of 9 seconds can be represented
by 10 seconds and a time of stay of 13 seconds can be represented
by 15 seconds. As discussed in further detail below, representing
the time of stay information in N resolutions can result in a
substantially similar accuracy when calculating the UE's mobility
state, while at the same time reducing the number of bits used for
representing the time of stay.
[0028] As a non-limiting example, if the time of stay of 408
seconds is switched from full resolution (i.e., every 1 second) to
a 2-second resolution, the 408 seconds can be represented according
to 2, 4, 6, . . . 406, 408. In other words, this reduced time
sequence (i.e., time sequence with reduced entropy) can have 204
values, as opposed to 408 values. The number of bits for
representing 204 values is 8 bits since 2.sup.8 is equal to 256.
Therefore, in this example, modifying the resolution can save one
bit when representing the time of stay information. As another
non-limiting example, if the time of stay of 408 seconds is
switched to a 5-second resolution, the 408 seconds can be
represented according to 5, 10, . . . , 405, 410. In other words,
this reduced time sequence can have 82 values, as opposed to 408
values. The number of bits for representing 82 values is 7 bits
since 2.sup.7 is equal to 128. Therefore, in this example,
modifying the resolution can save two bits when representing the
time of stay information.
[0029] FIG. 1 illustrates an accuracy of mobility state estimation
based on a number of cells a user equipment (UE) reports to a
network, e.g., an evolved node B (eNB). For example, the UE can
report time of stay information for 8 cells or 16 cells. In other
words, for each of the cells, the UE can report a time of stay at
that respective cell. The cell can correspond to a global cell
identifier (ID) or a physical cell ID. In general, as the number of
cells increase, the accuracy can increase. The accuracy can refer
to a percentage (or likelihood) that the eNB correctly estimates
the UE's mobility state. In other words, the accuracy can refer to
the likelihood (as a percentage) that the eNB correctly determines
the UE's estimated speed when the UE transitions from a radio
resource control (RRC) idle mode to an RRC connected mode.
[0030] As shown in FIG. 1, the accuracy of the mobility state
estimation can be graphically represented with respect to the
number of cells that are reported by the UE. As shown in FIG. 1, a
UE can be traveling at 3 kilometers per hour (km/h), a UE can be
traveling at 30 km/h, and a UE can be traveling at 60 km/h. In
addition, FIG. 1 illustrates accuracy levels with respect to the
number of cells for a UE traveling at an average speed. With
respect to the UE traveling at 3 km/h, the accuracy can be
approximately 100% when the UE reports mobility information for 8
cells and the accuracy can be approximately 100% when the UE
reports mobility for 16 cells. In other words, the eNB is
approximately 100% likely to correctly estimate the UE's mobility
state when the UE reports mobility information for either 8 or 16
cells. With respect to the UE traveling at 30 km/h, the accuracy
can be approximately 83% when the UE reports mobility information
for 8 cells and the accuracy can be approximately 92% when the UE
reports mobility for 16 cells. With respect to the UE traveling at
60 km/h, the accuracy can be approximately 90% when the UE reports
mobility information for 8 cells and the accuracy can be
approximately 94% when the UE reports mobility for 16 cells. In
general, the accuracy can be greater when the UE reports mobility
information for 16 cells as opposed to 8 cells. In most cases, an
accuracy of at least 80% can be achieved.
[0031] In one example, a relatively slow moving UE (e.g., a UE
traveling at 3 km/h) can take approximately 408 seconds to traverse
or travel the longer distance of a macro cell with a radius of 170
meters. In other words, the UE's time of stay in a particular macro
cell can be 408 seconds. In previous solutions, reporting a time of
stay of up to 408 seconds can consume 9 bits. As previously
explained, the number of bits for representing the time of stay can
be determined using the equation 2.sup.n, wherein n is the number
of bits. If 8 bits are used (i.e., 2.sup.8), then only a maximum
time of stay of 256 seconds can be represented using the 8 bits. If
9 bits are used (i.e., 2.sup.9), then the time of stay of 408
seconds can be represented using the 9 bits. The UE can use 72 bits
(i.e., 9 bits.times.8) if the UE reports the time of stay for 8
cells. In other words, the UE's visited cell history can include 8
cells when the UE reports the visited cell history to the eNB,
e.g., when the UE goes into a connected mode from an idle mode.
[0032] FIGS. 2A-2B illustrate accuracies of mobility state
estimation based on a number of cells a user equipment (UE) reports
to a network and a resolution level. In one example, the number of
bits used for representing the time of stay can be reduced, while
substantially maintaining an acceptable accuracy. In other words,
the probability of the eNB correctly determining the UE's mobility
state can remain at an acceptable level, even though the UE's time
of stay (which is used to calculate the UE's mobility state), is
represented using a reduced number of bits. The time of stay can be
represented according to a defined resolution (in seconds). The
resolution can refer to a level of granularity at which the time of
stay can be represented in seconds. In other words, the resolution
can refer to possible time intervals that are used to represent the
time of stay (e.g., 1 second intervals, 5 second intervals, 10
second intervals). When the resolution is 1, the time of stay can
be represented as being 1 second, or 2 seconds, or 3 seconds, etc.
In other words, the time of stay can be represented as a multiple
of 1. When the resolution is 5, the time of stay can be represented
as being 5 seconds, or 10 seconds, or 15 seconds, or so on. In
other words, the time of stay can be represented as a multiple of
5. So even if an actual time of stay for the UE at a specific cell
is 11 seconds, if the resolution is every 5 seconds, the actual
time of stay can be represented as being 10 seconds (e.g., 10
seconds is closer to 11 seconds as compared to 15 seconds).
[0033] As described earlier, by modifying the resolution of the
time of stay representation, a reduced number of bits can be used.
For example, if the actual time of stay of 408 seconds is switched
from full resolution (i.e., every 1 second) to a 3-second
resolution, the 408 seconds can be represented according to 3, 6,
9, . . . 405, 408. The time of stay can be expressed in multiples
of 3 when the resolution is 3. In other words, this reduced time
sequence (i.e., time sequence with reduced entropy) can have 136
values, as opposed to 408 values. The number of bits for
representing 136 values is 8 bits since 2.sup.8 is equal to 256. As
another example, if the actual time of stay of 408 seconds is
switched to a 10-second resolution, the 408 seconds can be
represented according to 10, 20, . . . , 400, 410. The resolution
can be expressed in multiples of 10 when the resolution is 10. In
other words, this reduced time sequence can have 41 values, as
opposed to 408 values. The number of bits for representing 41
values is 6 bits since 2.sup.6 is equal to 64. The actual time of
stay of 408 seconds can be represented as being 410 seconds since
410 seconds is the closest time (e.g., at the given resolution of
10 seconds) to the actual time of stay of 408 seconds. Therefore,
the time of stay of 408 seconds can be represented using 9 bits at
full resolution (i.e., 1 second intervals), 8 bits when the
resolution is at 3 seconds, and 6 bits when the resolution is at 10
seconds, while at the same time, maintaining an acceptable accuracy
level.
[0034] As shown in FIG. 2A, the accuracy of the mobility state
estimation can be graphically represented with respect to the
resolution (in seconds) of the time of stay information for the UE.
FIG. 2A can represent the accuracy levels when the UE reports
mobility information for 8 cells. As shown in FIG. 2A, a UE can be
traveling at 3 kilometers per hour (km/h), a UE can be traveling at
30 km/h, and a UE can be traveling at 60 km/h. In addition,
accuracy levels may be represented with respect to resolution for a
UE traveling at an average speed. With respect to the UE traveling
at 3 km/h, the accuracy can be approximately 100% until the
resolution becomes approximately 30 seconds. In other words, the
eNB is approximately 100% likely to correctly estimate the UE's
mobility state until the resolution of the time of stay reaches
approximately 30 seconds (i.e., the time of stay is represented as
a multiple of 30). With respect to the UE traveling at 30 km/h, the
accuracy can be approximately 82% when the resolution is 1 second.
The accuracy can drop to accuracies of 75% when the resolution
becomes approximately 6 seconds (i.e., the time of stay is
represented as a multiple of 6) and 35% when the resolution becomes
approximately 11 seconds (i.e., the time of stay is represented as
a multiple of 11), respectively. With respect to the UE traveling
at 60 km/h, the accuracy can be approximately 100% when the
resolution is 10 seconds. The accuracy can drop to approximately
95% when the resolution is increased to 15 seconds, but can again
reach approximately 100% when the resolution is increased to 25
seconds.
[0035] As shown in FIG. 2B, the accuracy of the mobility state
estimation can be graphically represented with respect to the
resolution (in seconds) of the time of stay information for the UE.
FIG. 2B can represent the accuracy levels when the UE reports
mobility information for 16 cells. As shown in FIG. 2B, a UE can be
traveling at 3 kilometers per hour (km/h), a UE can be traveling at
30 km/h, and a UE can be traveling at 60 km/h. In addition,
accuracy levels may be represented with respect to resolution for a
UE traveling at an average speed. With respect to the UE traveling
at 3 km/h, the accuracy can be approximately 100%, even when the
resolution reaches approximately 45 seconds. In other words, the
eNB is approximately 100% likely to correctly estimate the UE's
mobility state even when the resolution of the time of stay reaches
approximately 45 seconds (i.e., the time of stay is represented as
a multiple of 45). With respect to the UE traveling at 30 km/h, the
accuracy can be approximately 91% when the resolution is 1 second.
The accuracy can drop to accuracies of 85% when the resolution
becomes approximately 6 seconds (i.e., the time of stay is
represented as a multiple of 6) and 32% when the resolution becomes
approximately 11 seconds (i.e., the time of stay is represented as
a multiple of 11), respectively. With respect to the UE traveling
at 60 km/h, the accuracy can be approximately 100% when the
resolution is 10 seconds. The accuracy can drop to approximately
96% when the resolution is increased to 15 seconds, but can again
reach approximately 100% when the resolution is increased to 25
seconds.
[0036] FIG. 3 illustrates an accuracy of mobility state estimation
based on a maximum time of stay for a user equipment (UE). Since
the maximum time for a UE traveling at 3 km/h to move across the
longest distance in a macro cell is approximately 408 seconds, in
some cases, a maximum time of stay for the UE can be reduced while
substantially not comprising the accuracy of the mobility state
estimation. As a non-limiting example, an actual time of stay of
408 seconds can be represented as 128 seconds (thereby reducing the
number of bits), and the accuracy of the mobility state estimation
for the UE using the value of 128 seconds instead of the actual
time of 408 seconds can be unlikely to substantially change the
likelihood of the eNB correctly determining the UE's mobility
state.
[0037] FIG. 3 illustrates accuracies of mobility state estimation
with respect to a maximum time of stay (in seconds) for the UE in a
particular cell, wherein the maximum time of stay includes 408
seconds, 128 seconds, 64 seconds and 32 seconds. The UE can report
time of stay information for 8 cells. As shown in FIG. 3 a UE can
be traveling at 3 kilometers per hour (km/h), 30 km/h, or 60 km/h.
In addition, FIG. 3 illustrates accuracy levels with respect to the
maximum time of stay when the UE is traveling at an average speed.
With respect to the UE traveling at 3 km/h, the accuracy can be
approximately 100% when the maximum time of stay is 408 seconds,
128 seconds, or 64 seconds. The accuracy can drop to approximately
50% when the maximum time of stay is 32 seconds. With respect to
the UE traveling at 30 km/h, the accuracy can be approximately 84%
when the maximum time of stay is 408 seconds, 128 seconds, 64
seconds, or 32 seconds. With respect to the UE traveling at 60
km/h, the accuracy can be approximately 90% when the maximum time
of stay is 408 seconds, 128 seconds, 64 seconds, or 32 seconds.
Therefore, the accuracy of the UE's mobility state is generally not
compromised, even when the maximum time of stay is modified to 64
seconds. In addition, the time of stay of 64 seconds can be
represented using six bits, whereas the time of stay of 408 seconds
can be represented using nine bits, thereby saving 3 bits when
representing the UE's time of stay in a particular cell.
[0038] FIG. 4 is an exemplary mapping table used to represent
mobility information for a user equipment (UE) using a reduced
number of bits. The number of bits used to represent the time of
stay information can be optimized or reduced without substantially
compromising an accuracy of the mobility state estimation. In
mapping number M1, a time of stay can be between 1-64 seconds. The
number of bits used to represent the time of stay (i.e., 64
possible values) can be 6 bits. In mapping number M2, a time of
stay can be between 1-32 seconds or 64 seconds. The number of bits
used to represent the time of stay (i.e., 33 possible values) can
be 6 bits. In mapping number M3, a time of stay can be between 1-16
seconds, 32 seconds or 64 seconds. The number of bits used to
represent the time of stay (i.e., 18 possible values) can be 5
bits. In mapping number M4, a time of stay can be between 1-18
seconds, 32 seconds or 64 seconds. The number of bits used to
represent the time of stay (i.e., 20 possible values) can be 5
bits. In mapping number M5, a time of stay can be between 1-9
seconds, 10 seconds, 12 seconds, 14 seconds, 16 seconds, 18
seconds, 32 seconds or 64 seconds. The number of bits used to
represent the time of stay (i.e., 16 possible values) can be 4
bits. In mapping number M6, a time of stay can be between 1-8
seconds, 10 seconds, 12 seconds, 14 seconds, 16 seconds, 18
seconds, 32 seconds or 64 seconds. The number of bits used to
represent the time of stay (i.e., 15 possible values) can be 4
bits. In mapping number M7, a time of stay can be between 1-8
seconds, 10 seconds, 13 seconds, 16 seconds, 19 seconds, 32 seconds
or 64 seconds. The number of bits used to represent the time of
stay (i.e., 14 possible values) can be 4 bits. In mapping number
M8, a time of stay can be 1 second, 2 seconds, 4 seconds, 8
seconds, 16 seconds, 32 seconds or 64 seconds. The number of bits
used to represent the time of stay (i.e., 7 possible values) can be
3 bits.
[0039] FIG. 5 illustrates an accuracy of mobility state estimation
based on a type of mapping number used to represent the mobility
information for a user equipment (UE). The accuracy of the mobility
state estimation can be graphically illustrated with respect to the
type of mapping number (e.g., M1-M8 as described above). The UE can
report time of stay information for 8 cells. With respect to a UE
traveling at 3 km/h, the mapping numbers M1-M8 can all provide
approximately 100% accuracy when determining the UE's mobility
state. With respect to a UE traveling at 30 km/h, the mapping
numbers M1-M7 can all provide approximately 80% accuracy when
determining the UE's mobility state and the mapping number M8 can
provide below 55% accuracy when determining the UE's mobility
state. With respect to a UE traveling at 60 km/h, the mapping
numbers M1-M7 can all provide approximately 90% accuracy when
determining the UE's mobility state and the mapping number M8 can
provide approximately 100% accuracy when determining the UE's
mobility state.
[0040] 3GPP Technical Specification (TS) 36.423 Section 9.2.38
discusses an X2 application protocol and UE history information. A
UE history information IE (information element) can include
information about cells that a UE has been served by in an active
state prior to a target cell. 3GPP TS 36.423 Section 9.2.39
discusses last visited cell information. The last visited cell
information can include evolved universal terrestrial access
network (E-UTRAN) or UTRAN or GSM/EDGE Radio Access Network (GERAN)
cell specific information. The last visited cell information can
include the following information:
TABLE-US-00001 IE type and IE/Group Name reference Description
Global Cell ID ECGI 9.2.14 Time UE stayed INTEGER The duration of
the time the UE in cell (0 . . . 4095) stayed in the cell in
seconds. If the UE stays in a cell more than 4095 s, this IE is set
to 4095
[0041] In addition, 3GPP TS 36.423 Section 9.2.40 discusses last
visited E-UTRAN cell information. The last visited E-UTRAN cell
information can include information about a cell that is to be used
for radio resource management (RRM) purposes.
[0042] FIG. 6 illustrates exemplary signaling between a user
equipment (UE) 602 and an evolved node B (eNB) 604 to determine a
mobility state estimation for the UE 602. The UE 602 can identify
its mobility information (or visited cell history). The mobility
information can include a physical cell identifier (ID) and a time
of stay for which the UE 602 stays in a cell corresponding with the
physical cell ID. The time of stay for each physical cell ID can be
represented in seconds. Alternatively, the mobility information can
include a global cell ID and a time of stay for which the UE 602
stays in a cell corresponding with the global cell ID. The UE's
mobility information (or visited cell history) can include a
plurality of physical cell IDs and corresponding time of stay
information.
[0043] The UE 602, upon transitioning from a radio resource control
(RRC) idle mode to an RRC connected mode, can indicate an
availability of the mobility information to an evolved node B
(eNB). The eNB 604 can receive the indication from the UE 602, and
then request the mobility information from the UE 602. The UE 602
can communicate the mobility information to the eNB 604, e.g., the
physical/global cell IDs and the time of stay (in seconds) for each
physical/global cell ID.
[0044] In one example, the UE 602 can communicate mobility
information (or cell history information) in accordance with 3GPP
TS 36.423 Release 12, e.g., the time of stay for the UE can be
expressed as an integer ranging from 0 to 4095 seconds. In another
example, the UE 602 can optimize the cell history by reporting an
E-UTRAN cell global ID (ECGI) of a first cell, but then reporting a
physical cell ID (PCI) of the remaining cells because it is not
likely that one cell has neighboring cells with the same PCI. The
time of stay information can be represented up to 64 seconds (6
bits) or 128 seconds (7 bits) or 256 seconds (8 bits) or 4095
seconds (12 bits).
[0045] In one example, the UE 602 can include the time of stay
information using a reduced number of bits. For example, the time
of stay information can be represented in a mapping as described
above (3 to 6 bits). In another example, the time of stay
information can be represented in a resolution of N steps, wherein
N is an integer. For example, if the resolution is every 2 seconds,
the time of stay can be represented as being 1 second, 3 seconds, 5
seconds, . . . , k seconds, or k+2 seconds, wherein k is a defined
integer. By representing the time of stay according to a defined
resolution, the number of bits used to represent the time of stay
can be reduced.
[0046] In another example, the time of stay information can be
represented in a multiple level of multiple resolutions. A sequence
S.sub.k can be a sequence starting from a defined integer. The
defined integer (or starting integer) can be defined as b.
Therefore, the sequence can be [b, b+k, b+2k, . . . , b+n*k],
wherein n is an integer. The time information mapping can be formed
in a sequence, such as S1, S2, S3, . . . , S.sub.k, . . . ,
S.sub.n. Any of the S.sub.i can be empty and can start and end with
an integer, but any number is S.sub.n will be greater than numbers
in S.sub.n-1. As a non-limiting example, a sequence having multiple
levels of multiple resolutions can include 2, 4, 5, 10, 15, 20, 30,
and 40. In this example, the resolution can start at 2 seconds,
then increase to 5 seconds, and then increase to 10 seconds. By
using multiple resolutions in the same sequence, a number of bits
used to represent the time of stay information can be reduced.
[0047] In one configuration, the time of stay information can
include reference signal receive power (RSRP) values of the cell.
The RSRP values can include minimum RSRP values, maximum RSRP
values and/or difference RSRP values. Therefore, for each cell that
the UE 602 has visited, the RSRP for that particular cell can be
included in the mobility information communicated from the UE 602
to the eNB 604.
[0048] The eNB 604 can receive the physical/global cell IDs and
times of stay (using the reduced number of bits) from the UE 602.
The eNB 604, based on UE's mobility information, can perform a
mobility state estimation for the UE. The mobility state estimation
can refer to the UE's speed in idle mode or connected mode. In
other words, the eNB can use the physical cell IDs or global cell
IDs that were visited by the UE, as well as the time of stay for
each of the physical cell IDs or global cell IDs, in order to
determine the mobility state estimation for the UE. The
physical/global cell IDs and the time can be used to determine the
UE's mobility state (e.g., the UE's speed in idle mode or connected
mode). The eNB 604 can determine the UE's mobility state with an
acceptable accuracy, even though the time of stay information can
be represented using a reduced number of bits. In other words, even
though the time of stay included in the mobility information does
not exactly correspond with an actual time of stay (due to the
reduced number of bits), the accuracy at which the eNB 604
calculates the UE's mobility state can still be acceptable, i.e.,
an accuracy level is above a defined threshold.
[0049] In one configuration, the eNB 604 can use the RSRP values
for the cells when determining the UE's speed. For example, if the
UE enters a cell from a cell edge and travels towards the center of
the cell, then the RSRP difference can be relatively high. If the
UE enters the cell from the cell edge and then exits the cell, then
the RSRP difference can be relatively low. Based on minimum RSRP
values, maximum RSRP values and differences in RSRP values, the eNB
604 can estimate the UE's speed.
[0050] The eNB 604 can perform the mobility state estimation for
the UE 602, and then use the mobility state estimation to set one
or more handover parameters for the UE 602. In one example, the eNB
can set the handover parameters based on the UE's mobility state in
order to enhance handover performance. The handover parameters that
are configured based on the UE's speed can include, but are not
limited to, time to trigger (ttt), A3offset, T312, etc. Each of
these handover parameters can affect handover performance. The eNB
604 can send updated handover parameters to the UE 602.
[0051] Another example provides functionality 700 of circuitry of a
user equipment (UE) operable to report mobility information, as
shown in the flow chart in FIG. 7. The functionality can be
implemented as a method or the functionality can be executed as
instructions on a machine, where the instructions are included on
at least one computer readable medium or one non-transitory machine
readable storage medium. The circuitry can be configured to store
mobility information for the UE when the UE is in idle mode, the
mobility information including a visited cell history for the UE
when the UE is in idle mode or a connected mode, as in block 710.
The circuitry can be configured to notify an evolved node B (eNB)
that the mobility information for the UE is available when the UE
transitions from the idle mode to a connected mode, as in block
720. The circuitry can be configured to receive a request from the
eNB for the mobility information, as in block 730. The circuitry
can be configured to send the mobility information to the eNB using
a reduced number of bits to represent the mobility information
while substantially maintaining a level of accuracy of a mobility
state estimation for the UE, as in block 740.
[0052] In one example, the mobility state estimation is performed
at the eNB in order to determine an estimated speed of the UE when
the UE is in idle mode or connected mode. In another example,
handover parameters for the UE are adjusted based in part on the
estimated speed of the UE when the UE is in idle mode or connected
mode. In yet another example, the mobility information with the
visited cell history for the UE includes one or more physical cell
identifiers (IDs) and a time of stay for the UE with respect to
each of the physical cell IDs.
[0053] In one configuration, the mobility information with the
visited cell history for the UE includes one or more global cell
identifiers (IDs) and a time of stay for the UE with respect to
each of the global cell IDs. In another configuration, the
circuitry can be further configured to send the mobility
information to the eNB via an over-the-air interface. In yet
another configuration, the circuitry can be further configured to
send the mobility information to the eNB via a UE History
information element (IE), wherein the UE History IE includes a Last
Visited E-UTRAN Cell IE.
[0054] In one example, the mobility information sent to the eNB
includes an E-UTRAN Cell Global Identifier (ECGI) of a first cell
visited by the UE when the UE is in idle mode and one or more
physical cell identifiers (PCIS) of remaining cells visited by the
UE when the UE is in idle mode and connected mode. In another
example, the mobility information sent to the eNB includes a time
of stay for the UE with respect to each of the physical cell IDs,
wherein a time of stay of less than 65 seconds is represented using
six bits, a time of stay of 65 to 128 seconds is represented using
seven bits, a time of stay of greater than 129 seconds is
represented using eight bits, and a time of stay of less than 4095
seconds is represented using up to twelve bits. In yet another
example, the mobility information sent to the eNB includes a time
of stay for the UE within physical cell for the UE, wherein the
reduced number of bits to represent the mobility information is
determined using a mapping table, wherein the reduced number of
bits in the mapping table ranges from three bits to six bits
depending on the time of stay of the UE within a physical cell.
[0055] In one configuration, the mobility information sent to the
eNB includes a time of stay for the UE with respect to the physical
cell IDs, wherein the time of stay is represented in a resolution
of N steps in order to achieve the reduced number of bits to
represent the mobility information, wherein N is an integer. In
another configuration, the mobility information sent to the eNB
includes a time of stay for the UE with respect to each of the
physical cell IDs, wherein the time of stay is represented in a
sequence of multiple resolutions in order to achieve the reduced
number of bits to represent the mobility information. In yet
another configuration, the mobility information sent to the eNB
includes at least one of a maximum reference signal received power
(RSRP), a minimum RSRP or a difference RSRP to enable the eNB to
determine the estimated speed of the UE when the UE is in idle
mode.
[0056] Another example provides functionality 800 of circuitry of
an evolved node B (eNB) operable to utilize mobility information
associated with a user equipment (UE), as shown in the flow chart
in FIG. 8. The functionality can be implemented as a method or the
functionality can be executed as instructions on a machine, where
the instructions are included on at least one computer readable
medium or one non-transitory machine readable storage medium. The
circuitry can be configured to receive mobility information from
the UE after the UE switches to a connected mode from an idle mode,
wherein the mobility information is represented by a reduced number
of bits and includes a visited cell history for the UE when the UE
is in idle mode, as in block 810. The circuitry can be configured
to perform a mobility state estimation for the UE based in part on
the mobility information being represented by the reduced number of
bits while a level of accuracy of the mobility state information
for the UE is substantially maintained, wherein the mobility state
estimation includes an estimated speed of the UE when the UE is in
idle mode, as in block 820. The circuitry can be configured to
adjust one or more parameters for the UE based in part on the
mobility state estimation for the UE, as in block 830.
[0057] In one example, the circuitry can be further configured to:
receive an indication from the UE that the mobility information is
available when the UE switches to the connected mode from the idle
mode; and send a request to the UE for the mobility information. In
another example, the mobility information with the visited cell
history for the UE includes one or more physical cell identifiers
(IDs) and a time of stay with respect to each of the physical cell
IDs.
[0058] In one configuration, the mobility information received at
the eNB includes a time of stay for the UE with respect to each of
the physical cell IDs, wherein a time of stay of less than 65
seconds is represented using six bits, a time of stay of 65 to 128
seconds is represented using seven bits, and a time of stay of
greater than 129 seconds is represented using eight bits. In
another configuration, the mobility information received at the eNB
includes a time of stay for the UE within physical cell for the UE,
wherein the reduced number of bits to represent the mobility
information is determined using a mapping table, wherein the
reduced number of bits in the mapping table ranges from three bits
to six bits depending on the time of stay of the UE within a
physical cell.
[0059] Another example provides a method 900 for reporting mobility
information, as shown in the flow chart in FIG. 9. The method can
be executed as instructions on a machine, where the instructions
are included on at least one computer readable medium or one
non-transitory machine readable storage medium. The method can
include the operation of identifying mobility information for the
UE when the UE is in idle mode, the mobility information including
a visited cell history for the UE when the UE is in idle mode, as
in block 910. The method can include the operation of notifying an
evolved node B (eNB) that the mobility information for the UE is
available when the UE transitions from the idle mode to a connected
mode, as in block 920. The method can include the operation of
receiving a request from the eNB for the mobility information, as
in block 930. In addition, the method can include the operation of
sending the mobility information to the eNB using a reduced number
of bits to represent the mobility information while substantially
maintaining a level of accuracy of a mobility state estimation for
the UE, wherein the mobility state estimation is performed at the
eNB in order to determine an estimated speed of the UE, as in block
940.
[0060] In one example, the method can further include the operation
of sending the mobility information to the eNB via an over-the-air
interface. In another example, the method can further include the
operation of sending the mobility information to the eNB via a UE
History information element (IE), wherein the UE History IE
includes a Last Visited E-UTRAN Cell IE.
[0061] FIG. 10 provides an example illustration of the wireless
device, such as a user equipment (UE), a mobile station (MS), a
mobile wireless device, a mobile communication device, a tablet, a
handset, or other type of wireless device. The wireless device can
include one or more antennas configured to communicate with a node,
macro node, low power node (LPN), or, transmission station, such as
a base station (BS), an evolved Node B (eNB), a baseband unit
(BBU), a remote radio head (RRH), a remote radio equipment (RRE), a
relay station (RS), a radio equipment (RE), or other type of
wireless wide area network (WWAN) access point. The wireless device
can be configured to communicate using at least one wireless
communication standard including 3GPP LTE, WiMAX, High Speed Packet
Access (HSPA), Bluetooth, and WiFi. The wireless device can
communicate using separate antennas for each wireless communication
standard or shared antennas for multiple wireless communication
standards. The wireless device can communicate in a wireless local
area network (WLAN), a wireless personal area network (WPAN),
and/or a WWAN.
[0062] FIG. 10 also provides an illustration of a microphone and
one or more speakers that can be used for audio input and output
from the wireless device. The display screen can be a liquid
crystal display (LCD) screen, or other type of display screen such
as an organic light emitting diode (OLED) display. The display
screen can be configured as a touch screen. The touch screen can
use capacitive, resistive, or another type of touch screen
technology. An application processor and a graphics processor can
be coupled to internal memory to provide processing and display
capabilities. A non-volatile memory port can also be used to
provide data input/output options to a user. The non-volatile
memory port can also be used to expand the memory capabilities of
the wireless device. A keyboard can be integrated with the wireless
device or wirelessly connected to the wireless device to provide
additional user input. A virtual keyboard can also be provided
using the touch screen.
[0063] Various techniques, or certain aspects or portions thereof,
can take the form of program code (i.e., instructions) embodied in
tangible media, such as floppy diskettes, CD-ROMs, hard drives,
non-transitory computer readable storage medium, or any other
machine-readable storage medium wherein, when the program code is
loaded into and executed by a machine, such as a computer, the
machine becomes an apparatus for practicing the various techniques.
Circuitry can include hardware, firmware, program code, executable
code, computer instructions, and/or software. A non-transitory
computer readable storage medium can be a computer readable storage
medium that does not include signal. In the case of program code
execution on programmable computers, the computing device can
include a processor, a storage medium readable by the processor
(including volatile and non-volatile memory and/or storage
elements), at least one input device, and at least one output
device. The volatile and non-volatile memory and/or storage
elements can be a RAM, EPROM, flash drive, optical drive, magnetic
hard drive, solid state drive, or other medium for storing
electronic data. The node and wireless device can also include a
transceiver module, a counter module, a processing module, and/or a
clock module or timer module. One or more programs that can
implement or utilize the various techniques described herein can
use an application programming interface (API), reusable controls,
and the like. Such programs can be implemented in a high level
procedural or object oriented programming language to communicate
with a computer system. However, the program(s) can be implemented
in assembly or machine language, if desired. In any case, the
language can be a compiled or interpreted language, and combined
with hardware implementations.
[0064] It should be understood that many of the functional units
described in this specification have been labeled as modules, in
order to more particularly emphasize their implementation
independence. For example, a module can be implemented as a
hardware circuit comprising custom VLSI circuits or gate arrays,
off-the-shelf semiconductors such as logic chips, transistors, or
other discrete components. A module can also be implemented in
programmable hardware devices such as field programmable gate
arrays, programmable array logic, programmable logic devices or the
like.
[0065] Modules can also be implemented in software for execution by
various types of processors. An identified module of executable
code can, for instance, comprise one or more physical or logical
blocks of computer instructions, which can, for instance, be
organized as an object, procedure, or function.
[0066] Nevertheless, the executables of an identified module need
not be physically located together, but can comprise disparate
instructions stored in different locations which, when joined
logically together, comprise the module and achieve the stated
purpose for the module.
[0067] Indeed, a module of executable code can be a single
instruction, or many instructions, and can even be distributed over
several different code segments, among different programs, and
across several memory devices. Similarly, operational data can be
identified and illustrated herein within modules, and can be
embodied in any suitable form and organized within any suitable
type of data structure. The operational data can be collected as a
single data set, or can be distributed over different locations
including over different storage devices, and can exist, at least
partially, merely as electronic signals on a system or network. The
modules can be passive or active, including agents operable to
perform desired functions.
[0068] Reference throughout this specification to "an example"
means that a particular feature, structure, or characteristic
described in connection with the example is included in at least
one embodiment of the present invention. Thus, appearances of the
phrases "in an example" in various places throughout this
specification are not necessarily all referring to the same
embodiment.
[0069] As used herein, a plurality of items, structural elements,
compositional elements, and/or materials can be presented in a
common list for convenience. However, these lists should be
construed as though each member of the list is individually
identified as a separate and unique member. Thus, no individual
member of such list should be construed as a de facto equivalent of
any other member of the same list solely based on their
presentation in a common group without indications to the contrary.
In addition, various embodiments and example of the present
invention can be referred to herein along with alternatives for the
various components thereof. It is understood that such embodiments,
examples, and alternatives are not to be construed as defacto
equivalents of one another, but are to be considered as separate
and autonomous representations of the present invention.
[0070] Furthermore, the described features, structures, or
characteristics can be combined in any suitable manner in one or
more embodiments. In the following description, numerous specific
details are provided, such as examples of layouts, distances,
network examples, etc., to provide a thorough understanding of
embodiments of the invention. One skilled in the relevant art will
recognize, however, that the invention can be practiced without one
or more of the specific details, or with other methods, components,
layouts, etc. In other instances, well-known structures, materials,
or operations are not shown or described in detail to avoid
obscuring aspects of the invention.
[0071] While the forgoing examples are illustrative of the
principles of the present invention in one or more particular
applications, it will be apparent to those of ordinary skill in the
art that numerous modifications in form, usage and details of
implementation can be made without the exercise of inventive
faculty, and without departing from the principles and concepts of
the invention. Accordingly, it is not intended that the invention
be limited, except as by the claims set forth below.
* * * * *