U.S. patent application number 15/065689 was filed with the patent office on 2016-06-30 for location information for a mobile station.
The applicant listed for this patent is Microsoft Technology Licensing, LLC. Invention is credited to Robert E. Denman, Ke-Chi Jang, Chung-Ching Wang.
Application Number | 20160192148 15/065689 |
Document ID | / |
Family ID | 42319438 |
Filed Date | 2016-06-30 |
United States Patent
Application |
20160192148 |
Kind Code |
A1 |
Jang; Ke-Chi ; et
al. |
June 30, 2016 |
Location Information for a Mobile Station
Abstract
In a wireless communications network, a method of performing a
location service with respect to a mobile station includes
communicating a paging message containing an indication of whether
the paging message is related to at least one of an
emergency-related location service and a law enforcement-related
location service. In another aspect, a mobile station in a wireless
communications network communicates messaging to move the mobile
station to a traffic channel in response to a callback by at least
one of an emergency services entity and a law enforcement entity.
The mobile station also receives a location request on the traffic
channel, the location request containing an indication of whether
the location request is related to at least one of an
emergency-related location service and a law enforcement-related
location service.
Inventors: |
Jang; Ke-Chi; (Plano,
TX) ; Denman; Robert E.; (Plano, TX) ; Wang;
Chung-Ching; (Plano, TX) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Microsoft Technology Licensing, LLC |
Redmond |
WA |
US |
|
|
Family ID: |
42319438 |
Appl. No.: |
15/065689 |
Filed: |
March 9, 2016 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
12732395 |
Mar 26, 2010 |
|
|
|
15065689 |
|
|
|
|
10800055 |
Mar 12, 2004 |
7738855 |
|
|
12732395 |
|
|
|
|
60454827 |
Mar 14, 2003 |
|
|
|
Current U.S.
Class: |
455/456.2 |
Current CPC
Class: |
H04W 4/029 20180201;
H04W 76/50 20180201; H04W 4/025 20130101; H04W 4/90 20180201 |
International
Class: |
H04W 4/02 20060101
H04W004/02; H04W 4/22 20060101 H04W004/22 |
Claims
1. A computer-implemented method comprising: receiving a position
request for a position of a mobile station; ascertaining that the
mobile station is involved in an active call session; querying a
base station involved in the call session for radio environment
information associated with the call session; receiving the radio
environment information from the base station; and forwarding the
radio environment information to a remote entity for determining
the position of the mobile station.
2. A computer-implemented method as recited in claim 1, wherein the
position request is received from an emergency service.
3. A computer-implemented method as recited in claim 1, wherein the
position request pertains to an emergency service.
4. A computer-implemented method as recited in claim 1, wherein the
position request comprises an InterSystemPositionRequest
(ISPOSREQ).
5. A computer-implemented method as recited in claim 1, wherein
said ascertaining comprises ascertaining that the mobile station is
on an active traffic channel.
6. A computer-implemented method as recited in claim 1, wherein
said querying comprises communicating a Radio Measurements for
Position Request to the base station.
7. A computer-implemented method as recited in claim 1, wherein the
radio environment information is received as part of a Radio
Measurements for Position Response.
8. A system comprising: one or more processors; and one or more
machine-readable storage media storing instructions that are
executable by the one or more processors to perform operations
including: receiving a position request for a position of a mobile
station; ascertaining that the mobile station is involved in an
active call session; querying a base station involved in the call
session for radio environment information associated with the call
session; receiving the radio environment information from the base
station; and forwarding the radio environment information to a
remote entity for determining the position of the mobile
station.
9. A system as recited in claim 8, wherein the one or more
processors and the one or more machine-readable storage media are
implemented as part of a mobile switching center.
10. A system as recited in claim 8, wherein the one or more
processors and the one or more machine-readable storage media are
implemented as part of a mobile switching center that services a
cell in which the base station resides.
11. A system as recited in claim 8, wherein the one or more
processors and the one or more machine-readable storage media are
implemented as part of a mobile switching center, and the position
request is received from a mobile position center remote from the
mobile switching center.
12. A system as recited in claim 8, wherein the remote entity
comprises a mobile position center.
13. A system as recited in claim 8, wherein the position request
pertains to an emergency service for the mobile station.
14. A computer-implemented method comprising: receiving a position
request for a position of a mobile station that is involved in an
active call session, the position request indicating that the
position request is related to an emergency service; forwarding a
request message for receipt by the mobile station, the request
message requesting the position of the mobile station and
indicating that the request is related to the emergency service;
receiving a response message from the mobile station including
position information for the mobile station, the response message
being multiplexed with the active call session; and determining
based on the position information a position of the mobile
station.
15. A computer-implemented method as recited in claim 14, wherein
the request message includes a configurable emergency services
field that indicates that the request message is related to the
emergency service.
16. A computer-implemented method as recited in claim 14, further
comprising, prior to said forwarding, adding an emergency services
field to the request message indicating that the request messaged
is related to the emergency service.
17. A computer-implemented method as recited in claim 14, wherein
the request message is multiplexed with the active call
session.
18. A computer-implemented method as recited in claim 14, wherein
the active call session occurs over a particular traffic channel,
and wherein said forwarding comprises forwarding the request
message over the particular traffic channel for receipt by the
mobile station.
19. A computer-implemented method as recited in claim 14, wherein
the active call session occurs over a particular traffic channel,
and wherein said receiving comprises receiving the response message
over the particular traffic channel.
20. A computer-implemented method as recited in claim 14, further
comprising sending the position of the mobile station to a mobile
position center.
Description
RELATED APPLICATIONS
[0001] This application is a continuation of and claims priority to
U.S. patent application Ser. No. 12/732,395, filed on Mar. 26, 2010
which in turn is a continuation of and claims priority to U.S.
patent application Ser. No. 10/800,055 which is now U.S. Pat. No.
7,738,855 which issued on Jun. 15, 2010, which in turn claims
priority to U.S. Provisional Patent Application Ser. No.
60/454,827, filed on Mar. 14, 2003, the disclosures of which are
incorporated in their entirety by reference herein.
TECHNICAL FIELD
[0002] The invention is generally related to providing
location-based services in a wireless communications network.
BACKGROUND
[0003] A mobile communications network is typically made up of a
plurality of cells. Each cell is provided by a radio base station,
with each base station connected to a mobile switching center or a
packet service node that manages communications sessions between
mobile stations and terminals coupled to a public switched
telephone network (PSTN) or a packet-based data network.
Communications between mobile stations and base stations are
performed over wireless links.
[0004] A service that can be provided by a wireless communications
network is a location service (for determining a position of a
mobile station). There are two general categories of location
services: emergency (E911) services (ES); and value added services
(VAS) or commercial services, such as navigational services (e.g.,
services to find a store or other location), locate-me type
services, and so forth.
[0005] A wireless communications network that is capable of
providing location services typically includes base stations, a
mobile switching center (MSC), a mobile position center (MPC), and
one or more position determining entities (PDEs). The MPC receives
location requests from either an ES network or a VAS-related
entity. The MPC selects a PDE to interact with the mobile station
and the MSC in the determination of the location of the mobile
station.
[0006] Standards that define protocol messaging for location
services in a wireless communications network include the
TIA/EIA/IS-801, TIA/EIA/IS-881, and J-STD-036-A standards.
Messaging exchanged between the MPC, PDE, MSC, and mobile station
for VAS-related location services is defined by TIA/EIA/IS-881,
while messaging for ES-related location services is defined by
J-STD-036-A. Per both standards, the MSC may receive the
InterSystemPositionRequest INVOICE (ISPOSREQ) message from the
serving MPC. The ISPOSREQ message may contain a field, referred to
as the LCS (location services) Client Type (CTYP) field, to
indicate whether or not the entity requesting location services is
requesting emergency services. The absence of the CTYP field
indicates that the requesting entity is ES-related.
[0007] The TIA/EIA/B-801 standard defines protocol messaging
conveyed between the mobile station and the PDE that includes
positioning determination data messages (PDDMs), where each PDDM
contains one or more request and/or response elements. PDDMs are
conveyed over a traffic channel for both ES and VAS-related
location services.
[0008] In certain scenarios, an ES-related entity, such as a public
safety answering point (PSAP) within an ES network, may attempt to
contact the mobile station user after an emergency services call
has ended due to either a call drop (due to signal attenuation or
other reason) or when the PSAP may want to call back the mobile
station user to obtain more information or to obtain an updated
position of a moving mobile station. Should the callback be
initiated by the PSAP for the purpose of location services, the
PDE, MSC, base station, and mobile station may in some scenarios
treat the location request as if the location request were related
to a value-added service, since these network elements typically
cannot distinguish a network-initiated location request related to
ES callback from a network-initiated, value-added service location
request. The mobile station is also unable to determine whether a
location request is VAS- or ES-related by examining the content of
a PDDM. Thus, if a mobile station is configured by a user such that
a mobile station disables all location services except for
ES-related services, the mobile station may reject ES-related
request elements received in a PDDM over a traffic channel if the
mobile station incorrectly assumes that the PDDM is from a
VAS-related entity. The inability to obtain the mobile station's
precise position may result in safety concerns.
[0009] In some cases, an ES-related entity may wish to perform an
idle-mode location query in which the ES-related entity attempts to
obtain the location of a mobile station that is idle without having
to establish a voice call. To do so, a page with a particular
service option (such as service option 35 or 36) for location
services is sent to the mobile station. However, the mobile station
has no way of knowing whether or not the page is related to an ES
location service. If the mobile station is configured to accept
ES-related location requests only, the mobile station may
incorrectly assume that the page is VAS-related and thus reject the
page's service option.
[0010] In other scenarios, a mobile station configured to accept
only ES-related location services may erroneously accept
VAS-related location requests if the mobile station incorrectly
determines that the VAS-related location request is ES-related. In
either case, the inability to accurately distinguish between
ES-related and VAS-related location requests results in erroneous
processing of such location requests in a wireless communications
network.
SUMMARY OF THE INVENTION
[0011] In general, according to one embodiment, a method of
performing a location service with respect to a mobile station
includes communicating a paging message in a mobile communications
network, the paging message containing an indication of whether the
paging message is related to at least one of an emergency-related
location service and a law enforcement-related location
service.
[0012] According to another embodiment, a mobile station in a
wireless communications network communicates messaging to move a
mobile station to a traffic channel in response to a callback by at
least one of an emergency service entity and a law enforcement
entity. The mobile station also receives a location request on the
traffic channel containing an indication of whether the location
request is related to at least one of an emergency-related location
service and a law enforcement-related location service.
[0013] Other or alternative features will become apparent from the
following description, from the drawings, and from the claims.
BRIEF DESCRIPTION OF THE DRAWINGS
[0014] FIG. 1 is a block diagram of a wireless communications
network that provides location services in accordance to some
embodiments of the invention.
[0015] FIG. 2 is a message flow diagram of a network-initiated
location service involving an idle mobile station, according to an
embodiment.
[0016] FIG. 3 is a message flow diagram of a network-initiated
location service involving an active mobile station, according to
an embodiment.
DETAILED DESCRIPTION
[0017] In the following description, numerous details are set forth
to provide an understanding of the present invention. However, it
will be understood by those skilled in the art that the present
invention may be practiced without these details and that numerous
variations or modifications from the described embodiments may be
possible.
[0018] FIG. 1 illustrates a mobile or wireless communications
network 100, which includes a serving network and a home network of
a mobile station 102. Examples of the mobile station 102 include
mobile phones, portable computers with wireless modems,
wireless-enabled personal digital assistants (PDAs), a global
positioning system (GPS) device, and so forth. When the mobile
station 102 moves out its home network into a visited network, the
visited network is the serving network for the mobile station 102.
Note, however, that the concept of serving network and home network
is provided for the purpose of example, as the description of some
embodiments of the invention is equally applicable to a mobile
station 102 that remains in its home network. In other words, for
purpose of some embodiments of the invention, it is irrelevant
whether the mobile station 102 resides in a visited network or in
its home network.
[0019] The mobile station 102 communicates with a base station 104
that serves a cell (or cell sector) in which the mobile station 102
is located. The base station 104 includes two entities, a base
transceiver system (BTS) 106 and a base station controller 108. The
BTS 106 communicates radio frequency (RF) signals with the mobile
station 102, and the BSC 108 communicates with a mobile switching
center (MSC) 110.
[0020] The MSC 110 is labeled MSC-S to indicate that it is a
serving MSC (for serving the mobile station 102). The serving
network also includes additional cells or cell sectors associated
with other respective base stations 104. In some embodiments, more
than one BTS 106 can be connected to one BSC 108.
[0021] In one example, the wireless communications network is a
code-division multiple access (CDMA) network that provides
circuit-switched and packet-switched services. In one
implementation, the air interface between a mobile station and a
BTS is defined by TIA/EIA/IS-95 and TIA/EIA/IS-2000, while
messaging between the MSC and a base station is defined by
TIA/EIA/IS-2001. In other implementations, other types of wireless
communications networks can incorporate some embodiments of the
invention. Examples of other wireless communications networks
include GSM (Global System for Mobile) networks, UMTS (Universal
Mobile Telecommunications System) networks, wireless LANs, and
other networks.
[0022] For providing location services, the serving network
includes a mobile position center (MPC) 116, labeled MPC-S (serving
MPC) to indicate that it is part of the serving network. The
serving network also includes a position determining entity (PDE)
118. Note that more than one PDE may be located in the serving
network. The PDE 118 helps to determine the position or location of
a mobile station in response to a request for location service. A
service control point (SCP) 124 is connected to the serving MPC 116
and serving MSC 110. The serving MPC 116 receives location or
position requests from a requesting entity, such as from an entity
in an emergency services (ES) network 112. Such an entity is a
public safety answering point (PSAP) 114, which is an entity in the
ES network 112 where emergency calls are received and routed for
processing of an emergency service. In providing emergency
services, the PSAP 114 requests, via the ES network 112, the
location of a mobile station that originated the emergency call.
Another type of requesting entity is a value-added service
(VAS-related) entity, such as location service (LCS) client 142,
that obtains the position of the mobile station 102 to provide
navigational services, locate-me type services, and so forth. In
the ensuing discussion, the terms "location request" and "position
request" are used interchangeably to refer to a request for
determining the geographic position or location of a mobile
station.
[0023] FIG. 1 also shows a home MPC (MPC-H) 120 in the home
network. For a mobile station that has not roamed outside its home
network, the same network element may function as both MPC-H and
MPC-S. The home MPC 120 is also connected to an SCP 124, which is
also connected to the serving MSC 110. Also, depicted in FIG. 1 is
an LCS client 122 connected to the home MPC 120.
[0024] When the mobile station 102 registers with the wireless
communications network 100, or when the mobile station 102
originates a call, the mobile station 102 may advise the wireless
communications network 100 of its location services capabilities in
a registration message or an origination message. According to
IS-2000, location service capabilities can be included in a
GEO_LOC_TYPE information element in the IS-2000 Registration
Message or Origination Message. If the location services
capabilities indicate support for TIA/EIA/IS-801, a PDE (such as
PDE 118) in the wireless communications network is able to
establish a session with the mobile station 102 for the exchange of
application-layer protocol messaging defined by TIA/EIA/IS-801. The
protocol messaging conveyed between the mobile station 102 and the
PDE 118 includes position determination data messages (PDDMs),
where each PDDM contains one or more request and/or response
elements. In the TIA/EIA/IS-801 exchange, the MSC 110 and base
station 104 provide transparent transport of the application-layer
protocol messaging (PDDMs). In other implementations, other types
of messaging may be provided to carry location service-related
information between the mobile station and another entity in the
wireless communications network 100.
[0025] In accordance with some embodiments of the invention,
special indicators are provided in messages communicated in the
wireless communications network 100 to indicate whether a location
request for the mobile station 102 is ES-related or VAS-related.
This indicator can be used by the mobile station 102 to reliably
determine that an incoming call or request is ES-related or
VAS-related. In some cases, a user of the mobile station 102 may
disable all location requests except for ES-related location
requests. In such a scenario, if the mobile station 102 is unable
to reliably determine whether an incoming location request is
related to emergency services or value-added services, the mobile
station 102 may reject an incoming ES-related location request or
erroneously accept VAS-related location requests based on an
incorrect determination that the VAS-related location requests are
ES-related.
[0026] The special indicator is in the form of an emergency
services field that is set to a first state to indicate that a
location request is ES-related, and to a second state to indicate
that a location request is VAS-related. The special indicator is
included in paging messages and/or in positioning messages (e.g.,
PDDMs) exchanged over a traffic channel.
[0027] A paging message that contains the special indicator refers
to either a paging request from the mobile switching center 110 to
a base station 104, or a page from a base station 104 to the mobile
station 102. For example, an MSC-to-BS paging request that can
include an emergency services information element can be an IS-2001
paging request. An example of a page from the base station 104 to
the mobile station 102 that can contain an emergency services field
includes an IS-2000 general page message (GPM) or a universal page
message (UPM) that is sent by the base station 104 to enable the
network to initiate a call with the mobile station. The emergency
services field included in the GPM or UPM may be referred to as an
EMERGENCY_SERVICES field, which is set to logical "1" to indicate
emergency services, and to logical "0" to indicate non-emergency
services (such as VAS-related services).
[0028] An indicator of whether a location request is ES-related or
VAS-related can also be included in position messages (e.g., PDDMs)
exchanged between a PDE and the mobile station. Thus, the
EMERGENCY_SERVICES field can also be added to the header of each
PDDM that is communicated from a PDE 118 to the mobile station 102
to indicate to the mobile station whether a received PDDM is
ES-related or VAS-related.
[0029] There are several scenarios in which the mobile station 102
may deny an ES-related location request, or erroneously accept a
VAS-related location request if the emergency services field
discussed above is not used. In a first scenario (referred to as
"Scenario 1"), for the mobile station 102 that has been configured
by its user to support only ES-related location services,
active-mode location queries during emergency callback will fail,
if the emergency services field according to some embodiments is
not used. Two types of position queries can be issued: idle-mode
position queries and active-mode position queries. Idle-mode
position queries are for location services for which the mobile
station is moved to a traffic channel for the purpose of exchanging
PDDMs. Active-mode position queries are for location services for
which the mobile station is already on a traffic channel for some
other service, such that the traffic channel can be additionally
used for the purpose of exchanging PDDMs.
[0030] In Scenario 1, the mobile station 102 originates an ES call
(such as to the PSAP 114), but the call drops before the ES network
112 is able to obtain the location of the mobile station. The call
may drop due to poor or weak RF signaling between the mobile
station and a base station. If such call drop occurs, the PSAP 114
may use a callback number provided to the PSAP 14 during the
initial call by the mobile station 102 to call back the mobile
station 102. Callback by the PSAP 114 causes the mobile station to
be moved to a traffic channel so that the traffic channel can be
used for the exchange of PDDMs. The PSAP 114 then sends a location
request to the serving network to obtain the location of the mobile
station. In response, the PDE 118 in the serving network initiates
a session with the mobile station (102) to obtain location
information of the mobile station. According to one implementation,
the PDE 118 can establish an TIA/EIA/IS-801 session with the mobile
station 102, where TIA/EIA/IS-801 defines messaging exchanged over
traffic channels for purposes of acquiring location information and
other related information. However, without the indicator provided
by some embodiments of the invention, the mobile station is unable
to determine whether the incoming location request from the PDE 118
is ES-related or VAS-related. The mobile station 102 may assume
that the incoming location request is VAS-related, and thus, the
location request may be rejected by the mobile station 102. As a
result, the PSAP 114 will not be able to obtain the precise
position of the mobile station 102.
[0031] In a second scenario ("Scenario 2"), for the mobile station
102 that has been configured by its user to support only ES-related
location services, an idle-mode location query initiated by the ES
network 112 will fail, if the emergency services field according to
some embodiments is not employed. In this case, the mobile station
102 is idle, such that a location request constitutes an idle-mode
location query. The mobile station is idle when it is currently not
communicating over a traffic channel in the wireless communications
network. In Scenario 2, the mobile station 102 originates an
emergency services call, but the call is subsequently released by
either the PSAP 114 or the mobile station 102. The PSAP 114 may
wish to obtain the updated position of the mobile station 102
(which may be moving) without having to again establish a voice
call. The serving MSC 110, upon receiving a location request from
the serving MPC 116, attempts an idle-mode location query, which
results in the base station 104 sending a page (that specifies
service option 35 or 36) to the mobile station 102. A page
specifying service option (SO) 35 or 36 is a page seeking a
location service, not a voice call. Since the mobile station is
configured to support location service for emergency services only,
and since emergency services calls are originated by the mobile
station, the mobile station 102 will reject this call. The PSAP 114
will thus be unable to obtain the updated, precise position of the
mobile station 102.
[0032] In a third scenario ("Scenario 3"), the mobile station 102
that has been configured to support only ES-related location
services may reject request elements in TIA/EIA/IS-801 PDDMs that
are ES-related, if the emergency services field according to some
embodiments is not used. In this scenario, the mobile station 102
is in a voice call, but then the mobile station 102 sends a flash
with information message (FWIM) to successfully place an emergency
services call. For some reason, such as delays due to congestion at
the serving MPC 116 or at the selected PDE 118, the PSAP 114 or the
mobile station 102 releases the emergency services call before
PDDMs are exchanged. At this time, the mobile station 102 resumes
the prior voice call. At some later point, the PDE 118 may finally
send the ES-related PDDMs to the mobile station; however, since the
mobile station 102 detects that the mobile station is not currently
in an emergency services call, the mobile station 102 assumes that
the PDDMs are VAS-related. As a result, the mobile station 102
rejects request elements contained in the PDDMs, which prevents the
PSAP 114 from obtaining the precise position of the mobile
station.
[0033] In a fourth scenario ("Scenario 4"), a mobile station that
has been configured to support only ES-related location services
may incorrectly accept PDDMs that are VAS-related, if the emergency
services field according to some embodiments is not used. In one
example, the mobile station 102 has just been configured to support
only ES-related location services, and the mobile station 102 is in
a voice call. Not knowing that the user has temporarily disabled
VAS-related location services, the provider of location services to
which the user subscribes attempts to initiate a VAS-related
session with the mobile station 102. Since the mobile station 102
is currently in a voice call, the query from the provider is an
active-mode location query. The PDE 118 is selected for the
VAS-related session, which sends a PDDM to the mobile station
containing request elements. In the meantime, the mobile station
102 has sent a flash with information message (FWIM) to initiate an
emergency services call. Before a request is received from the
emergency services network 112 by the serving MPC 116, the mobile
station 102 receives the VAS-related PDDM. Since the mobile station
is in an emergency services call, the mobile station 102 assumes
that the VAS-related PDDM is ES-related, and responds to the PDE
118 with a PDDM containing location-related information, in
violation of the configuration by the user in which the mobile
station is to only respond to ES-related location requests.
Effectively, in this case, a race condition exists between PDDMs
resulting from an ES-related location request and PDDMs resulting
from a VAS-related location request.
[0034] In a fifth scenario ("Scenario 5"), which is a continuation
of Scenario 4 discussed above, the mobile station 102 that is
currently in a VAS-related call session may be unable to preempt
the VAS-related session in order to accept an ES-related PDDM.
Thus, if the mobile station 102 receives an ES-related PDDM during
a VAS-related session, the mobile station 102 will reject the
request elements in the ES-related PDDM. As the mobile station
cannot distinguish between an ES-related PDDM from a VAS-related
PDDM, the mobile station 102 will be unable to preempt the
VAS-related session in order to expedite the ES-related
session.
[0035] To address these issues, emergency services fields are
inserted into paging messages (MSC paging requests, base station
pages) and/or positioning messages (e.g., PDDMs) for indicating
whether or not a location request is ES-related, as discussed
above. For Scenario 2 above, adding the EMERGENCY_SERVICES field in
the GPM or UPM (or other page from a base station to a mobile
station) enables the mobile station configured for ES-related
location services but not VAS-related location services to detect
that the page is ES-related. As a result, the mobile station allows
connection of SO 35 or SO 36 for the exchange of ES-related PDDMs
over a traffic channel To address Scenarios 1, 3, 4, and 5, adding
the EMERGENCY_SERVICES field to the header of a PDDM enables the
mobile station to discern whether or not a received PDDM is
ES-related. Also, in Scenario 5, the EMERGENCY_SERVICES field
enables the mobile station to preempt an existing VAS-related
session in favor of an ES-related session.
[0036] Due to explicit specification of whether a location request
is ES-related or VAS-related, the mobile station does not have to
rely on possibly spurious context information to determine whether
or not a PDDM is ES-related. Using context information above, the
mobile station may, under various circumstances, including but not
limited to those noted for Scenarios 1-5, incorrectly infer an
association between a location request and either a value-added
service or emergency service.
[0037] Although discussed in the context of emergency-related
location services, similar techniques can be applied for other
applications, such as for purposes of surveillance by law
enforcement entities. In these other implementations, a
SURVEILLANCE_SERVICES field can be added to the PDDM, GPM, or UPM,
to enable the mobile station 102 to determine whether a location
request is associated with surveillance by law enforcement
(referred to here as "law enforcement-related location service"). A
more general field, such a REGULATORY_SERVICES field, can be added
to the PDDM, GPM, or UPM to indicate either an ES-related location
service or a law enforcement-related location service is
requested.
[0038] FIG. 2 is a message flow diagram that illustrates an
idle-mode location query to the mobile station, which is in an idle
state (200). The mobile station 102 is in the idle state when it is
currently not in another call session. For purposes of the present
discussion, it is assumed that the mobile station has already
registered with the wireless communications network, and has
indicated the mobile station's ability to support location
services, including support for TIA/EIA/IS-801 protocol messaging
according to one implementation. The serving MPC (MPC-S) 116
receives (at 201) an ES-related position request from the ES
network 112. According to one implementation, the ES-related
position request is an EmergencyServicesPositionRequest INVOKE
(ESPOSREQ) message (as defined by J-STD-036-A). A position request
from a VAS-related entity, on the other hand, is an
InterSystemPositionRequest INVOKE (ISPOSREQ) message (as defined by
TIA/EIA/IS-881).
[0039] In response to the position request (received at 201), the
serving MPC 116 sends (at 202) a position request (which in one
implementation is in the form of an ISPOSREQ message to the serving
MSC 110). Effectively, the ISPOSREQ message sent from the serving
MPC 116 to the serving MSC 110 directs the serving MSC to move the
mobile station to a traffic channel for subsequent location
services messaging (e.g., TIA/EIA/IS-801 messaging). The ISPOSREQ
message also enable the serving MPC 116 to obtain radio environment
information for the mobile station, prior to selecting a PDE to
interact with the mobile station and the serving MSC in determining
the position of the mobile station.
[0040] The serving MSC 110, in response to the ISPOSREQ message
from the serving MPC 116, sends a paging request (at 204) to the
base station 104. The paging request includes an emergency services
information element for indicating whether the paging request is
related to emergency services. The ISPOSREQ message includes a
PositionRequestType parameter that includes a LCS Client Type
(CTYP) field. The CTYP field specifies whether or not the
requesting entity is related to emergency services. The emergency
services information element included in the paging request from
the serving MSC 110 to the base station 104 is set to a value that
corresponds to the value of CTYP in the ISPOSREQ message.
Alternatively, the absence of the CTYP field can be an indication
to the serving MSC 110 that the location request is related to
emergency services. The emergency services information element in
the paging request allows the base station 104 to determine whether
the incoming paging request is related to emergency services.
[0041] According to one implementation, the paging request sent at
204 specifies either service option 35 (SO 35) or service option 36
(SO 36). SO 35 and SO 36 are the service options used for location
services, according to TIA/EIA/TSB58-F.
[0042] In response to the paging request from the serving MSC 110,
the base station 104 sends a page (at 206) to the mobile station
102. The page can either be a universal page message (UPM) or a
general page message (GPM). The page sent at 206 specifies either
SO 35 or SO 36, based on the specification of the paging request
from the serving MSC 110. The page (UPM or GPM) also includes an
EMERGENCY_SERVICES field to indicate to the mobile station whether
or not the page is related to emergency services. The value of the
EMERGENCY_SERVICES field is based on the emergency services
information element in the paging request from the serving MSC
110.
[0043] In response, the mobile station 102 determines (at 207)
whether it should accept the page. If the mobile station 102 is
configured to accept ES-related location requests but not to accept
VAS-related location requests, the mobile station 102 will accept
the page if the EMERGENCY_SERVICES field in the page indicates
emergency services. To accept the service option of the page, the
mobile station 102 sends (at 208) a page response to confirm
support for the specified service option (SO 35 or 36). To reject
the page's service option according to one example implementation,
the page response sent by the mobile station specifies SO 0
(service option 0). In response to the page response sent at 208,
the base station 104 sends a paging response (at 210) back to the
serving MSC 110. The paging response (210) contains radio
environment information provided by the base station. After
receiving the paging response indicating acceptance of the
requested service option, the serving MSC 110, in collaboration
with the base station 104 and mobile station 102, moves (at 211)
the mobile station to a traffic channel against the requested
service option (SO 35 or SO 36). Also, the serving MSC 110 sends
(at 212) an isposreq message back to the serving MPC 116, which
includes the radio environment information.
[0044] Once the radio environment information has been received by
the serving MPC 116, the serving MPC 116 selects a PDE (such as the
PDE 118) for interacting with the serving MSC 110 and the mobile
station 102. The serving MPC 116 then sends (at 214) a
GeoPositionRequest INVOKE (GPOSREQ) message to the PDE 118. The
GPOSREQ message also contains a PositionRequestType parameter that
includes the CTYP field to indicate whether a location services
client is related to emergency services.
[0045] The PDE 118 then exchanges position determination data
messages (PDDMs) with the mobile station 102 (at 218 and 224). The
PDDMs are conveyed over a traffic channel assigned to the mobile
station 102. The PDDMs sent to the mobile station 102 contains
request elements for requesting location-related information. As
noted above, each PDDM sent from the base station 104 to the mobile
station 102 also contains the EMERGENCY_SERVICES field for
indicating whether the PDDM is related to ES-services. The state of
the EMERGENCY_SERVICES field is based on the value of the CTYP
field contained in the GPOSREQ message sent by the serving MPC 116
to the PDE 118.
[0046] At this point, the mobile station 102 determines (at 220)
whether or not it is to accept the PDDM. If the mobile station is
configured to accept only ES-related location services, then it
will accept the PDDM request from the PDE 118 if the
EMERGENCY_SERVICES field has a state to indicate emergency
services. If the location request in the PDDM is accepted by the
mobile station, the mobile station acquires GPS (Global Positioning
System) satellite information with assistance of data received from
the PDE 118. The GPS information is communicated by the mobile
station 102 back to the base station 104 in one or more PDDMs (sent
at 224). Alternatively, the mobile station 102 measures the time of
arrival of radio signals from multiple base stations and passes the
measurements to the PDE 118. Such information is passed in one or
more PDDMs (sent at 224). From information provided by the mobile
station 102, the PDE 118 computes (at 228) the position of the
mobile station 102. The position is calculated in terms of latitude
and longitude, according to one implementation. Alternatively, the
mobile station 102 itself computes its position, and passes the
position in a PDDM (at 224) to the PDE 118. The computed position
information is communicated to the serving MPC 116 in a gposreq
message (sent at 230). The position data is then sent (at 232) to
the location service client (in this case the ES network 112).
[0047] FIG. 3 is a message flow diagram in which a position request
is received while the mobile station is actively in a voice call
(300). Such a position request is referred to as an active-mode
position query. The serving MPC 116 receives (at 301) a position
request from the ES network 212 (in the form of an ESPOSREQ
message, according to one implementation). In response, the serving
MPC 116 sends (at 302) an ISPOSREQ message to the serving MSC 110.
The serving MSC 110, in response to the ISPOSREQ message,
determines (at 304) that the mobile station 102 is already on a
traffic channel. The serving MSC 110 (rather than sending a paging
request) sends (at 306) a query to the base station 104 for radio
environment information associated with the call session that the
mobile station 102 is currently involved in. In response, the base
station 104 sends (at 308) the radio environment information to the
serving MSC 110, which provides the information to the serving MPC
116 in an isposreq message (at 310). In one implementation
specified by TIA/EIA/IS-2001, the query for radio environment
information is called a Radio Measurements for Position Request,
and the response is called a Radio Measurements for Position
Response.
[0048] Once the serving MPC 116 has received the radio environment
information from the serving MSC 110, the serving MPC 116 sends (at
312) a GPOSREQ message to the PDE 118 (that has been selected to
interact with the serving MSC 110 and the mobile station 102 for
the requested location service). In response, the PDE 118 exchanges
(at 316 and 322) PDDMs with the mobile station on the established
traffic channel. The primary traffic (the traffic associated with
the call session that the mobile station was already on) and the
location services information traffic are multiplexed on the same
traffic channel. The PDDM sent by the PDE 118 to the mobile station
102 contains an EMERGENCY_SERVICES field to indicate to the mobile
station 102 whether the location service is ES-related. The state
of the EMERGENCY_SERVICES field is based on the state of CTYP in
the GPOSREQ message. Based on the EMERGENCY_SERVICES field in a
PDDM received from the base station 104, the mobile station 102, if
it is configured to support ES-related location services but not
VAS-related location services, determines (at 318) whether or not
to accept the location request. If the mobile station accepts the
request, the mobile station acquires position information to send
to the PDE 118 in one or more PDDMs.
[0049] From information received from the mobile station 102 in one
or more PDDMs, the PDE 118 computes (at 326) the position of the
mobile station 102, and sends the position information in a gposreq
message (at 328) to the serving MPC 116. The serving MPC 116 then
sends (at 330) the position data to the location service client
(which in this case is the ES network 112).
[0050] By adding the EMERGENCY_SERVICES field to the GPM or UPM (or
any other page from the base station to the mobile station), the
mobile station that is configured to support ES-related location
services but not VAS-related location services can detect that the
page is ES-related. As result, the mobile station can allow an SO
35 or 36 connection for the exchange of PDDMs over a traffic
channel.
[0051] Adding an EMERGENCY_SERVICES field to the header of a PDDM
(sent by the PDE 118 to the mobile station 102) enables the mobile
station to discern whether or not a received PDDM is ES-related. If
the mobile station is currently in a VAS-related session, the
mobile station can preempt the VAS-related session in favor of the
ES-related session.
[0052] According to one example implementation, the packet data
unit (PDU) format for a general page message (GPM) that is
addressed for a mobile station includes the following:
TABLE-US-00001 Field Length SERVICE_OPTION 0 or 16
EMERGENCY_SERVICES 0 or 1
[0053] If a location-based service option is requested, then the
base station sets the SERVICE_OPTION field to a corresponding value
for the requested service option (e.g., SO 35 or SO 36 according to
TIA/EIA/IS-801-1). The EMERGENCY_SERVICES field is omitted if the
SERVICE_OPTION field is not set to SO 35 or 36. However, if the
SERVICE_OPTION field is set to SO 35 or SO 36, then the
EMERGENCY_SERVICES field is set to "1" to indicate that the GPM is
related to an emergency call, or set to "0" if the GPM is not
related to an emergency call.
[0054] The PDU format for the universal page message (UPM) that is
addressed for a mobile station includes the following:
TABLE-US-00002 Field Length (Bits) SERVICE_OPTION 16 ADD_MS_RECORD
0 or 8 x EXT_MS_SDU_LENGTH EMERGENCY_SERVICES 0 or 1
[0055] The UPM also includes a SERVICE_OPTION field that can be set
to indicate a desired service option. The optional ADD_MS_RECORD
field refers to the additional mobile station addressed information
record. The EMERGENCY_SERVICES field is omitted if the
SERVICE_OPTION field does not specify SO 35 or 36. However, if
SERVICE_OPTION field specifies either SO 35 or 36, the
EMERGENCY_SERVICES field is set to "1" if the page is ES-related,
or set to "0" if the page is not ES-related.
[0056] According to one implementation, forward link messages that
can be sent from the PDE 118 to the mobile station 102 include
PDDMs according to the following format:
TABLE-US-00003 Field Length (Bits) SESS_START 1 SESS_END 1 O O O
NUM-REQUESTS 4 NUM_RESPONSES 4 EMERGENCY_SERVICES 1 RESERVE 7
[0057] Note that an EMERGENCY_SERVICES field is included in the
PDDM. The PDE 118 sets the EMERGENCY_SERVICES field to "1" if the
PDDM is related to emergency services; otherwise, the
EMERGENCY_SERVICES field is set to "0."
[0058] Instructions of the various software routines or modules
discussed herein (such as software executable in the mobile station
102, base station 104, MSC 110, MPC 116, and PDE 118) are loaded
for execution on corresponding control units or processors, such as
a processor 144 in the mobile station 102, a processor 136 in the
BSC 108, a processor 134 in the MSC 110, and a processor 130 in the
PDE 118. The control units or processors include microprocessors,
microcontrollers, processor modules or subsystems (including one or
more microprocessors or microcontrollers), or other control or
computing devices. As used here, a "controller" refers to hardware,
software, or a combination thereof. A "controller" can refer to a
single component or to plural components (whether software or
hardware).
[0059] Data and instructions (of the various software routines or
modules) are stored in one or more machine-readable storage media,
such as storage 146 in the mobile station 102, storage 138 in the
BSC 108, storage 134 in the MSC 110, and storage 132 in the PDE
118. The storage media include different forms of memory including
semiconductor memory devices such as dynamic or static random
access memories (DRAMs or SRAMs), erasable and programmable
read-only memories (EPROMs), electrically erasable and programmable
read-only memories (EEPROMs) and flash memories; magnetic disks
such as fixed, floppy and removable disks; other magnetic media
including tape; and optical media such as compact disks (CDs) or
digital video disks (DVDs).
[0060] The instructions of the software routines or modules are
loaded or transported to a system in one of many different ways.
For example, code segments including instructions stored on floppy
disks, CD or DVD media, a hard disk, or transported through a
network interface card, modem, or other interface device are loaded
into the system and executed as corresponding software routines or
modules. In the loading or transport process, data signals that are
embodied in carrier waves (transmitted over telephone lines,
network lines, wireless links, cables, and the like) communicate
the code segments, including instructions, to the system. Such
carrier waves are in the form of electrical, optical, acoustical,
electromagnetic, or other types of signals.
[0061] While the invention has been disclosed with respect to a
limited number of embodiments, those skilled in the art will
appreciate numerous modifications and variations therefrom. It is
intended that the appended claims cover such modifications and
variations as fall within the true spirit and scope of the
invention.
* * * * *