WO2005011308A1 - Identification d'une station mobile au niveau d'un central de de localisation des mobiles - Google Patents

Identification d'une station mobile au niveau d'un central de de localisation des mobiles Download PDF

Info

Publication number
WO2005011308A1
WO2005011308A1 PCT/US2004/010576 US2004010576W WO2005011308A1 WO 2005011308 A1 WO2005011308 A1 WO 2005011308A1 US 2004010576 W US2004010576 W US 2004010576W WO 2005011308 A1 WO2005011308 A1 WO 2005011308A1
Authority
WO
WIPO (PCT)
Prior art keywords
location services
message
identifier
unique
smlc
Prior art date
Application number
PCT/US2004/010576
Other languages
English (en)
Inventor
Suzanne Arcens
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to CA002530359A priority Critical patent/CA2530359A1/fr
Priority to KR1020057024606A priority patent/KR101162997B1/ko
Priority to CN200480017654XA priority patent/CN1810050B/zh
Priority to JP2006517084A priority patent/JP4554607B2/ja
Priority to EP04801783A priority patent/EP1639841A4/fr
Priority to MXPA05013930A priority patent/MXPA05013930A/es
Priority to BRPI0411941-0A priority patent/BRPI0411941A/pt
Publication of WO2005011308A1 publication Critical patent/WO2005011308A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/024—Guidance services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support

Definitions

  • LCS Location services
  • MSs Mobile Stations
  • a mobile station user can use location information to locate the nearest automatic teller machine, as well as the fee charged by that ATM.
  • location information can assist a traveler in obtaining step-by-step directions to a desired destination while en route.
  • GSM Global System for Mobile Corrvmunications
  • Technologies that permit a large number of system users to share a wireless communication system such as the Global System for Mobile Corrvmunications (GSM) technology, for example, play an important role in meeting the ever-increasing demands of mobile computing, including the demands for location services.
  • GSM uses a combination of Time Division Multiple Access and Frequency Division Multiple Access technologies that enable multiple users to communicate simultaneously.
  • GSM systems also frequently employ General Packet Radio Service technology to transmit data and to provide location services.
  • a second exemplary reference relating to GSM and LCS is the "3rd Generation Partnership Project, Technical Specification Group GSM/EDGE Radio Access Network, Location Services (LCS), Mobile Station (MS) - Serving Mobile Location Centre (SMLC) Radio Resource LCS Protocol (RRLP) (Release 1999),” (3GPP TS 04.31 V8.10.0), July, 2002.
  • the reference is referred to hereinafter as 3GPP TS 04.31 V8.10.0.
  • a third exemplary reference relating to GSM and LCS is the "3rd Generation Partnership Project, Technical Specification Group Core Network, Mobile Application Part (MAP) specification (3G TS 29.002 version 3.h.0 Release 99),” June, 2000.
  • MAP Technical Specification Group Core Network
  • MAP Mobile Application Part
  • a wireless communications network such as the Public Land Mobile Communications Network (PLMN) in GSM, can provide assistance data to a MS that enables location measurements and/or improves measurement performance.
  • PLMN Public Land Mobile Communications Network
  • One exemplary method of MS-assisted positioning employs the Global Positioning System (GPS), and is referred to as "assisted GPS" or AGPS.
  • GPS Global Positioning System
  • AGPS assisted GPS
  • the MS acquires measurements from GPS satellites using assistance data provided by the network.
  • measurements relating to a given location request are transmitted to a Serving Mobile Location Center (SMLC).
  • SMLC Serving Mobile Location Center
  • the SMLC manages the overall coordination and scheduling of resources required to perform positioning of an MS.
  • the BSC conveys only a logical reference datum to the SMLC to distinguish one positioning session from another.
  • this is an effective method for ordinary operation, it makes testing very difficult because an information recovery process must be accomplished in order to associate a particular session to a specific MS.
  • Possible methods of addressing the MS identity testing problem noted above may include integrating the SMLC in the BSC, or modifying the BSC such that the MS identity information is passed to the SMLC in a non-standard manner.
  • these methods are undesirable because such changes to the BSC are cumbersome and difficult to accomplish.
  • a method and apparatus for providing the geographical location of a wireless mobile station, and more particularly to a method and apparatus for conveying the identity of an MS to a stand-alone Serving Mobile Location Center has, in one exemplary embodiment, an MS configured to encode its unique MS identifier (MS ID), such as an International Mobile Subscriber Identity (LMSI), in an extension container, which is an optional information element defined by Radio Resource Location Services (LCS) Protocol (RRLP).
  • MS ID unique MS identifier
  • LMSI International Mobile Subscriber Identity
  • RRLP Radio Resource Location Services
  • the extension container may be included as a component in a location services message such as a Measure Position Response message or a Protocol Error message.
  • the SMLC is configured to decode the extension container, retrieve the MS ID, and store the MS ID in association with a unique positioning session identifier.
  • the MS may be configured with a test mode parameter.
  • the test mode parameter may be set to the values "test mode on” (abbreviated “ON”) and “test mode off” (abbreviated “OFF”), where the default value is "OFF.”
  • the configuration of the test mode parameter may be controlled via a proprietary command using a serial link into the phone, or via the MS user interface.
  • encoding of the MS ID in the extension container is activated at the test MS only when the test mode parameter is set to "ON.”
  • FIGURE 1 is a functional block diagram of an exemplary wireless communication system used to provide wireless communications including location services.
  • FIGURE 2 is a functional block diagram of another exemplary wireless communication system used to provide wireless communications including location services, showing additional system components.
  • FIGURE 3 is a functional block diagram illustrating the flow of messages between a test mobile station and a Serving Mobile Location Center.
  • FIGURE 4 is a flowchart diagram illusfrating steps of an exemplary method.
  • FIGURE 1 illustrates a simplified general wireless communication system 100 that may be adapted for testing location services. As shown in FIGURE 1, a Mobile
  • MS 110 conrmunicates with one or more Base Transceiver Stations (BTSs)
  • BTSs Base Transceiver Stations
  • Each BTS provides coverage (or service) to a geographical region commonly referred to as a "cell". Although two BTSs are illustrated by way of example, depending on the positioning mechanisms employed, location services may be provided to the MS 110 using only one BTS, or using three or more
  • positioning mechanisms may include Uplink Time of Arrival (TOA), Enhanced Observed Time
  • E-OTD E-OTD Difference
  • the MS 110 may include, without limitation: a wireless telephone, a personal digital assistant with wireless communication capabilities, a laptop having wireless communication capabilities, and any other mobile digital device for personal communication via wireless connection.
  • the BTSs 122, 124 are operatively coupled for data communication to a Base
  • BSC Station Controller
  • the BSC 126 is coupled to a Serving
  • SMLC Mobile Location Center 130.
  • An SMLC controls location services by managing the resources required to perform positioning of an MS.
  • the SMLC maybe operatively coupled through other elements (not shown) in the wireless communication system.
  • the MS 110 may receive signals, such as GPS signals, from one or more satellites 172, 174 via communication links 156, 158. Although two satellites are illustrated by way of example, only one satellite, or more usually, a plurality of satellites, may be employed when providing location services to a mobile station in a wireless communication system. Satellite data may also be received by other receivers (not shown) in the communication service provider network 140. Persons skilled in the communication arts will understand that GPS location systems for wireless systems generally include elements such as stationary GPS receivers and/or Wide Area Reference Networks for receiving satellite signals and providing reference data to SMLCs.
  • the BSC 126 is coupled to the communication service provider network 140 to receive and transmit data such as audio/video/text cornmumcation and programming data, position requests, etc.
  • PLMN Public Land Mobile Communication System Network
  • FIGURE 2 shows another exemplary communication system 200 capable of providing location services, illustrated in functional block form. For simplicity, only one GPS satellite 272, and its associated broadcast signal link 252, is illustrated.
  • the MS 210 includes a central processing unit (CPU) 212, a memory 214, a User Interface 213, a Subscriber Identity Module (SLM) 215, and a transceiver 216.
  • CPU central processing unit
  • a CPU can include microprocessors, embedded controllers, application specific integrated circuits (ASICs), digital signal processors (DSPs), state machines, dedicated discrete hardware, and the like.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • the system, apparatus, and method described herein are not limited to the specific hardware component described or by any specific hardware component selected to implement the CPU 212.
  • the transceiver 216 enables transmission and reception of data, such as audio/video/text communication and programming data, between the MS 210 and a remote location, such as the BTSs 224 and 226, or GPS satellites such as the satellite 272.
  • An antenna 218 is electrically coupled to the transceiver 216.
  • the basic operation of the MS 210 for voice and data commur ⁇ cation is well-known in the art and is not described in detail herein.
  • the system 200 includes a SMLC 230 having a memory 234, and a CPU 232.
  • the CPU 232 controls the operation of the SMLC 230 according to programmed instructions and data stored in the memory 234.
  • the memories 214 and 234 may include read-only memory (ROM) components, random- access memories (RAM), and non-volatile RAM components.
  • the memory 234 stores and provides instructions and data for the CPU 232.
  • the memory 214 stores and provides instructions and data for the CPU 212.
  • the components of the SMLC 230 are linked together by an internal bus system 236.
  • the components of the MS 210 are linked together by an internal bus system 219.
  • the SLM 215 includes a unique MS identifier (MS ID), such as an International Mobile Subscriber Identity (LMSI), Mobile Subscriber Integrated Services Directory Number (MSISDN), or other MS ID.
  • MS ID is unique identifiers for an MS, and either may be used.
  • the MS ID (typically an LMSI, although the MSISDN or other MS IDs may be employed) may be retrieved by the CPU 212, encoded according to programmed instructions and data stored in the memory 214, incorporated into an RRLP Measure Position Response message or a Protocol Error message, and conveyed to the SMLC 230 via the communication links and system components illustrated in FIGURE 2.
  • the User Interface 213 may be used to control the setting of a test mode parameter, as described below.
  • the User Interface may include a graphical user interface (GUI), and input devices such as a touch screen, pointing device or keypad.
  • GUI graphical user interface
  • the test mode parameter may be controlled using a proprietary command received through a connection (e.g., a serial connection, not shown) to a local device (not shown), such as a laptop computer or personal digital assistant, wherein the local device is operatively connected to the CPU 219.
  • the commumcation system 200 includes a BSS 220, which, in turn, includes a BSC 222 and a plurality of BTSs such as the BTSs 224, 226.
  • the BTSs permit the transmission and reception of data (such as audio/video/text and prograrrrming data) between the BSC 222 and remote locations, such as the MS 210, or GPS satellites, such as satellite 272.
  • Antennas 228 and 229 are electrically coupled to the BTSs 224 and 226, respectively, in known manner.
  • the MS 210 communicates with the BTSs via wireless links such as the wireless link 272.
  • Additional radio links may be used to transmit signals between the MS 210 and the BTS 224 or other BTSs (not shown).
  • the basic operation of the BSC 222 and BTSs 224, 226 is well- known in the art and therefore is not described in more detail herein.
  • the BSC 222 is connected to the Communication Service Provider Network 240.
  • the BSC 222 receives and transmits data, such as audio/video/text communication and programming data, position requests, or position data from the Communication Service Provider Network 240.
  • the BSC 220 is also coupled to the SMLC 230 in order to transmit and receive data relating to LCS. Examples of such data are described in detail below.
  • RRLP LCS Messages Exchanged between the MS and the SMLC [0030]
  • Figure 3 illustrates the flow of RRLP messages that may be exchanged between a test MS 310 and an SMLC 330 during a position request procedure. This procedure is described in greater detail in the reference 3GPP TS 04.31 V8J0.0.
  • the RRLP Assistance Data message 342, RRLP Protocol Error message 346, and RRLP Assistance Data Acknowledgement message 348 enable the SMLC to transmit assistance data to the MS relating to position measurement and/or MS location calculation when RRLP downlink pseudo-segmentation is used (according to well known art, as described in 3GPP TS 04.31 V8J0.0). If pseudo-segmentation is not used, the position request procedure skips the messages 342, 346 and 348.
  • the RRLP Assistance Data message 342, the RRLP Protocol Error message 346, and the RRLP Assistance Data Acknowledgement message 348 may also enable the SMLC to transmit assistance data requested by the MS. In this case messages 352, 354 and 356 are skipped.
  • the SMLC uses the RRLP Assistance Data message 342, or the RRLP Measure Position Request message 352, the SMLC transmits the Assistance Data component to the MS.
  • This component includes assistance data for location measurement and/or location calculation.
  • the MS transmits an RRLP message containing the Protocol Error component to the SMLC using the RRLP Protocol Error message 346. This message is sent only if there is a problem that prevents the MS from receiving a complete and understandable
  • the Protocol Error message 346 includes an optional information element referred to as an extension container.
  • the extension container of the Protocol Error message 346 maybe adapted to convey the MS D (e.g., LMSI or MSISDN) of the MS to the SMLC. This message is conveyed when there is a protocol error. Consequently, as described below, subsequent messages may be utilized for MS identity conveyance.
  • the MS When the MS has received the complete Assistance Data component, it transmits the RRLP, Assistance Data Acknowledgement message 348, to the SMLC.
  • the SMLC transmits the Measure Position Request component to the MS using the RRLP Measure Position Request message 352.
  • This component includes Quality of
  • QoS Quality of Service
  • the MS transmits an RRLP message containing the Protocol Error component to the SMLC using the RRLP Protocol Error message 354. This message is transmitted only if there is a problem that prevents the test MS from receiving a complete and understandable Measure Position Request component.
  • the Protocol Error message 354 also includes an optional extension container that may be adapted to convey the MS LD
  • the MS attempts to report the requested location measurements using the RRLP
  • Measure Position Response message 356 Examples of location measurements may include a position estimate, AGPS measurements, or a measurement error.
  • MS has location measurements, position estimate, or an error indication
  • the RRLP Measure Position Response message 356 also includes an optional extension container that may be adapted to convey the MS LD (e.g., LMSI or MSISDN) of the MS to the SMLC. If the position determination process has not been previously aborted due to an error, the extension container of this message may be implemented in order to convey the MS LD to the SMLC. If the process is aborted prior to this message, then one of the Protocol Error messages 346 or 354 may used instead.
  • MS LD e.g., LMSI or MSISDN
  • the RRLP extension container is exported from the Mobile Application Part (MAP) Extension Data Types (described in detail in the incorporated 3GPP TS 29.002 V3.h.0 reference). As a result, its specification complies with the MAP Abstract Syntax Notation One (ASNJ) description rules. For the actual field encoding/decoding, the Packed Encoding Rules (PER) PER apply (e.g., bitmap for optional parameters, extension indicator when the ellipsis notation is used, etc). As described below, the MAP compliant encoding involves object identifiers, which were either previously registered or are yet to be registered.
  • MAP Mobile Application Part
  • ASNJ MAP Abstract Syntax Notation One
  • MAP-EXTENSION :: CLASS ⁇ &ExtensionType OPTIONAL, &extensionId OBJECT IDENTIFIER ⁇
  • ExtensionContainer SEQUENCE ⁇ privateExtensionList [0]PrivateExtensionList OPTIONAL, pcs-Extensions [l]PCS-Extensions OPTIONAL,
  • the MS identification may be encoded in the extType variable.
  • the optional PCS-Extensions are not included in this exemplary embodiment.
  • the OI should not be confused with the LMSI or other MS JD which may be used to identify the test MS.
  • the content of the OI, or the OI "value”, is preceded by a length indicator that provides the number of octets of the OI value.
  • the ASN-1 OI enables unambiguous identification of an entity that is registered in a worldwide tree.
  • the properties of OIs are well known to persons skilled in the art of wireless communications, and therefore are not described in more detail herein. OIs may be registered through an appropriate organization or registration authority.
  • An example of an existing OI registration is the one assigned for the ASN-1 BASIC-PER, UNALIGNED variant: ⁇ joint-iso-itu-t asnl (1) packed- encoding (3) basic ( O ) unaligned (1) ⁇ "Packed encoding of a single ASNJ type (basic unaligned)."
  • a suitable OI may be represented by the known PER hexadecimal format and used for the "extld" entry of the exemplary ASN-1 encoding of the extension container shown above.
  • the "extType" variable is the component containing the private extension data that may be used to convey the LMSI or other MS LD for the test MS. It is an ASN-1 open type, therefore it has a length determinant followed by a field list. For the current example, the length of the private extension may be selected not to exceed 128 octets. The length determinant may therefore be encoded in one octet, or in 8 bits.
  • the ellipsis notation "" indicates that extensions can be added. If the test MS in some exceptional case cannot provide its LMSI, the LMSI field may be filled with zeros.
  • the TestExtension Revision is an integer variable having a value between 0 and 63, inclusive, and may be represented by a 6-bit hexadecimal number.
  • the LMSI variable is an octet string with a fixed size of 8 octets.
  • TABLE 1 is an exemplary extension container encoding in accordance with the teachings above:
  • a test MS is configured to encode its associated MS LD (e.g., LMSI or MSISDN) in an extension container of the Measure Position Response message 356, or in an extension container of the Protocol Error messages 346 and 354 (FIGURE 3).
  • MS LD e.g., LMSI or MSISDN
  • the Measure Position Response message is transmitted to an SMLC to report a position determination, AGPS measurements, or a measurement error.
  • the Protocol Error messages are transmitted by the test MS to an SMLC to report a protocol error.
  • the SMLC is configured to decode the extension container, retrieve the MS ID, and store the MS WD in association with a unique positioning session identifier that may belong to a plurality of position session identifiers maintained by the SMLC.
  • the SMLC may first attempt to decode the OI. If the received OI is not recognized, the SMLC may attempt to skip the OI and decode the length of the open type variable in order to skip the entire private extension container. If the extension container prevents proper decoding of the RRLP message, the SMLC may transmit a RRLP Protocol Error message to the MS and terminate the position determination session with the BSC. [0048] Whenever the SMLC detects that the length determinant of the OI, or of the ExtType, is encoded with a value indicating that the length is greater than 16K, the SMLC transmits a protocol Error message to the MS. The SMLC terminates the position determination session with the BSC.
  • the MS may be configured with a test mode parameter.
  • the test mode parameter may be set with the values "test mode on” (abbreviated “ON”) and “test mode off (abbreviated “OFF”), where the default value is "OFF.”
  • the configuration is done through a proprietary command using a serial link into the phone or via the MS user interface (UI).
  • Encoding of the MS LD in a message extension container is activated at the test MS only when the test mode parameter is set to "ON.”
  • encoding of the MS LD in the extension container is activated at the test MS only when the test mode parameter is set to "ON.”
  • FIGURE 4 is a flowchart diagram illustrating steps in an exemplary method.
  • an MS receives a message from an SMLC.
  • Exemplary messages may include an RRLP Assistance Data message or an RRLP Measure Position Request Message.
  • the method proceeds to a STEP 404.
  • the MS may be equipped with a test mode parameter. If the MS is programmed to encode the MS ID and does not have a test mode parameter, then the MS is programmed to encode the MS ID and does not have a test mode parameter, then the MS is programmed to encode the MS ID and does not have a test mode parameter, then the MS is programmed to encode the MS ID and does not have a test mode parameter, then the MS is programmed to encode the MS ID and does not have a test mode parameter, then the
  • STEP 404 may be skipped and the method proceeds directly to a STEP 406. If the test mode parameter is included in the MS, and it is set to ON, the concept also proceeds to the STEP 406. If the MS is not programmed to send an MS LD, or if the test mode parameter is set to OFF, the method proceeds to a STEP 408.
  • the MS encodes its associated MS LD in an extension container of a suitable response message, such as the Measure Position Response message 356 (FIGURE 3), the Protocol Error messages 346 and 354.
  • Suitable messages may include any messages having an extension container. Other messages that may be sent that do not have an extension container, such as the Assistance Data
  • the MS transmits the suitable response message to the SMLC, and proceeds to a STEP 410.
  • the SMLC processes the suitable response message and proceeds to a STEP 412.
  • the method proceeds to a STEP 414. If the SMLC fails to retrieve the MS ID, the method proceeds to a STEP 416. If no MS LD was sent (e.g., the test mode was set to OFF), the method also proceeds to the STEP 416.
  • the SMLC stores the MS LD in association with a unique positioning session identifier for reference by test engineers as needed, and then continues normal processing functions.
  • the SMLC may respond by transmitting an RRLP Protocol
  • the SMLC will also continue with normal processing functions at the STEP 416.
  • the SMLC may transmit an RRLP Protocol Error message to the MS without terminating the position determination session with the BSC, before continuing with normal processing functions.
  • Another advantageous aspect relates to the interoperability between a test MS and a "naive" SMLC (i.e., an SMLC that is not configured for operation in a test mode according to the teachings herein).
  • a "naive" SMLC i.e., an SMLC that is not configured for operation in a test mode according to the teachings herein.
  • an SMLC is unable to decode the extension container (e.g., as could occur with a roaming situation, although roaming would be an atypical circumstance for operation of a test MS)
  • several possibilities may occur: 1) when the naive SMLC detects the presence of the optional extension container, it may choose not to attempt to decode the message and may transmit a Protocol Error message in response; 2) when the extension container is at the end the message, the naive SMLC may attempt to decode the message, but stop the decoding upon reaching the extension container, thereby processing the part of the message decoded before reaching the extension container;
  • Yet another advantageous feature relates to the size of the RRLP Measure Position Response message.
  • the addition of a private extension increases the size of the RRLP payload, which maybe an issue in terms of segmentation, especially for the RRLP Measure Position Response message.
  • the message size remains under 252 octets, no uplink segmentation is required.
  • the exemplary embodiment described above limits the increase in the size of the RRLP message to 128 octets (120 octets is the typical number for reporting one set of GPS measurements associated with 16 satellites) or less, reducing the possibility that the complete RRLP message will exceed 252 octets.
  • the Mobile Stations 110 and 210 may include, without limitation: a wireless telephone, a personal digital assistant with wireless communication capabilities, a laptop having wireless communication capabilities, and any other mobile digital device for personal commumcation via wireless connection.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un système servant à transmettre l'identité d'une MS (110) à un central de localisation des mobiles (SMLC) (130). Dans un mode de réalisation exemplaire, une MS (110) est configurée pour coder un identificateur MS (MS ID) unique, tel qu'une identité internationale d'abonné mobile (IMSI), dans une mémoire d'extension qui est un élément d'information facultatif défini par le protocole pour les services de localisation (LCS) de ressources radio (RRLP). La mémoire d'extension peut être mise en oeuvre comme un composant dans un message de réponse à une position de mesure ou un message d'erreur de protocole. Le SMLC (130) est configuré pour décoder la mémoire d'extension, extraire le MS ID et enregistrer le MS ID en association avec un identificateur de session de positionnement unique. La MS (110) peut être configurée avantageusement avec un paramètre de mode d'essai. Dans un mode de réalisation, l'encodage du MS ID dans la mémoire d'extension n'est activé au niveau de la MS (110) d'essai que lorsque le paramètre de mode d'essai se trouve dans l'état 'ouvert'.
PCT/US2004/010576 2003-06-27 2004-04-06 Identification d'une station mobile au niveau d'un central de de localisation des mobiles WO2005011308A1 (fr)

Priority Applications (7)

Application Number Priority Date Filing Date Title
CA002530359A CA2530359A1 (fr) 2003-06-27 2004-04-06 Identification d'une station mobile au niveau d'un central de de localisation des mobiles
KR1020057024606A KR101162997B1 (ko) 2003-06-27 2004-04-06 서빙 모바일 위치 센터(ｓｍｌｃ)에서의 이동국 식별
CN200480017654XA CN1810050B (zh) 2003-06-27 2004-04-06 在服务移动定位中心识别移动台
JP2006517084A JP4554607B2 (ja) 2003-06-27 2004-04-06 サービスしている移動体位置決めセンタにおける移動局の識別
EP04801783A EP1639841A4 (fr) 2003-06-27 2004-04-06 Identification d'une station mobile au niveau d'un central de de localisation des mobiles
MXPA05013930A MXPA05013930A (es) 2003-06-27 2004-04-06 Identificacion de una estacion movil en un centro servidor de localizacion de moviles.
BRPI0411941-0A BRPI0411941A (pt) 2003-06-27 2004-04-06 identificação de uma estação móvel em um centro de localização de móvel servidor

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US48321203P 2003-06-27 2003-06-27
US60/483,212 2003-06-27

Publications (1)

Publication Number Publication Date
WO2005011308A1 true WO2005011308A1 (fr) 2005-02-03

Family

ID=34102648

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2004/010576 WO2005011308A1 (fr) 2003-06-27 2004-04-06 Identification d'une station mobile au niveau d'un central de de localisation des mobiles

Country Status (10)

Country Link
EP (1) EP1639841A4 (fr)
JP (1) JP4554607B2 (fr)
KR (1) KR101162997B1 (fr)
CN (1) CN1810050B (fr)
BR (1) BRPI0411941A (fr)
CA (1) CA2530359A1 (fr)
MX (1) MXPA05013930A (fr)
RU (1) RU2368103C2 (fr)
TW (1) TWI347142B (fr)
WO (1) WO2005011308A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007020991A1 (fr) * 2005-08-16 2007-02-22 Kabushiki Kaisha Toshiba Messagerie fantome
EP2547167A1 (fr) * 2011-07-11 2013-01-16 Koninklijke KPN N.V. Procédé et système pour services basés sur l'emplacement utilisant un paramétrage
JP2015057603A (ja) * 2007-09-11 2015-03-26 クゥアルコム・インコーポレイテッドＱｕａｌｃｏｍｍ Ｉｎｃｏｒｐｏｒａｔｅｄ 移動無線ネットワークにおける支援データの最適化された配列
US9591523B2 (en) 2010-11-05 2017-03-07 Qualcomm Incorporated Segmented data transfer with resume capability

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101466076B (zh) * 2007-12-17 2011-09-21 中兴通讯股份有限公司 Cdma集群系统中群组标识码的编码方法
KR102166258B1 (ko) * 2019-05-17 2020-10-15 넷마블 주식회사 위치기반 서비스 어플리케이션의 품질 테스트 기법

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020110096A1 (en) * 2001-02-13 2002-08-15 Hans Carlsson Wireless network architechture and protocol for location services in GPRS packet data network
US20030119526A1 (en) * 2001-12-26 2003-06-26 Edge Stephen William Hybrid architecture for supporting location determination in a wireless network
US20030120637A1 (en) 2001-12-26 2003-06-26 Autodesk, Inc. Location based services bridge to external data sources
US20040142702A1 (en) * 2003-01-21 2004-07-22 Eric Hefner Location technology support determinations in wireless communications networks and devices

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU747302B2 (en) * 1998-04-17 2002-05-16 Swisscom Mobile Ag Roaming method and devices appropriate therefor
US6219557B1 (en) * 1998-12-11 2001-04-17 Ericsson Inc. System and method for providing location services in parallel to existing services in general packet radio services architecture
US6313787B1 (en) * 1999-11-12 2001-11-06 Motorola, Inc. Method and apparatus for assisted GPS protocol
FI111788B (fi) * 2001-01-04 2003-09-15 Nokia Corp Menetelmä yksityisyyden tuottamiseksi tietoliikenneverkossa
FR2827050B1 (fr) * 2001-07-06 2005-02-11 Univ Paris 7 Denis Diderot Tomographe ultrasonore, systeme et procede de mesure tomographique ultrasonore au moyen d'un tel tomographe
ES2276855T3 (es) * 2001-11-27 2007-07-01 Siemens Aktiengesellschaft Procedimiento para consultar la conformidad para la captacion de datos de posicion de un aparato temrinal de telefonia movil, y red de comunicaciones movil correspondiente.
JP3491631B2 (ja) * 2001-11-28 2004-01-26 株式会社デンソー 無線通信端末

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020110096A1 (en) * 2001-02-13 2002-08-15 Hans Carlsson Wireless network architechture and protocol for location services in GPRS packet data network
US20030119526A1 (en) * 2001-12-26 2003-06-26 Edge Stephen William Hybrid architecture for supporting location determination in a wireless network
US20030120637A1 (en) 2001-12-26 2003-06-26 Autodesk, Inc. Location based services bridge to external data sources
US20040142702A1 (en) * 2003-01-21 2004-07-22 Eric Hefner Location technology support determinations in wireless communications networks and devices

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1639841A4

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007020991A1 (fr) * 2005-08-16 2007-02-22 Kabushiki Kaisha Toshiba Messagerie fantome
JP2015057603A (ja) * 2007-09-11 2015-03-26 クゥアルコム・インコーポレイテッドＱｕａｌｃｏｍｍ Ｉｎｃｏｒｐｏｒａｔｅｄ 移動無線ネットワークにおける支援データの最適化された配列
US9140801B2 (en) 2007-09-11 2015-09-22 Qualcomm Incorporated Delayed radio resource signaling in a mobile radio network
US9448308B2 (en) 2007-09-11 2016-09-20 Qualcomm Incorporated GPS yield for emergency calls in a mobile radio network
US9591523B2 (en) 2010-11-05 2017-03-07 Qualcomm Incorporated Segmented data transfer with resume capability
US9603053B2 (en) 2010-11-05 2017-03-21 Qualcomm Incorporated Segmented data transfer with resume capability
EP2547167A1 (fr) * 2011-07-11 2013-01-16 Koninklijke KPN N.V. Procédé et système pour services basés sur l'emplacement utilisant un paramétrage

Also Published As

Publication number Publication date
JP2007521742A (ja) 2007-08-02
CA2530359A1 (fr) 2005-02-03
RU2006102365A (ru) 2006-07-27
KR101162997B1 (ko) 2012-07-09
BRPI0411941A (pt) 2006-08-15
MXPA05013930A (es) 2006-03-09
CN1810050A (zh) 2006-07-26
JP4554607B2 (ja) 2010-09-29
KR20060017885A (ko) 2006-02-27
TWI347142B (en) 2011-08-11
EP1639841A4 (fr) 2011-05-11
EP1639841A1 (fr) 2006-03-29
TW200507670A (en) 2005-02-16
RU2368103C2 (ru) 2009-09-20
CN1810050B (zh) 2011-02-02

Similar Documents

Publication Publication Date Title
US9609554B2 (en) Methods, apparatuses, related computer program product and data structure for deciding on a signaling scheme for handover
US6912395B2 (en) Network and method for monitoring location capabilities of a mobile station
KR101679902B1 (ko) Ｌｔｅ에서의 위치결정, 위치확인 및 위치 기반 서비스를 위한 ｑｏｓ 판별을 가능하게 하는 신호 지원
EP1177694B1 (fr) Procede et systeme de distribution de donnees assistee par gps
US20120295623A1 (en) Methods and apparatuses for positioning a node in a wireless communications system using different ran/rats
CN101390431A (zh) 用户装备与无线网络之间的扩展能力传递
EP2740299B1 (fr) Procédé et appareil de distribution d'informations d'accès à un réseau local sans fil
US20050182565A1 (en) Method of supporting location services in a mobile radio communications system
US20070165573A1 (en) Mobility Management with Controlled Use of New Reject Causes
KR101417606B1 (ko) 이동 통신 디바이스의 배치 정보를 보고하기 위한 장치 및 방법
US7471953B2 (en) Location services for unlicensed mobile access
TW201021608A (en) Method of transmitting radio access capability and related communication device
CN107820236A (zh) 处理状态信息
JP2004512788A (ja) パケット交換メッセージと回線交換メッセージの両方を使用するパケット交換移動電話ネットワークにおける加入者端末の測位
US11818678B2 (en) Communication method, terminal device and network device
WO2020087327A1 (fr) Procédé et dispositif de communication
EP1639841A1 (fr) Identification d'une station mobile au niveau d'un central de de localisation des mobiles
JP2003513571A (ja) 移動局、無線電気通信システムおよび無線電気通信システムを操作する方法
US8406751B2 (en) Message having a first protocol revision field indicating a message format and a second protocol revision field indicating mandatory features in a standards revision
US20080267120A1 (en) Location Services for Unlicensed Mobile Access
WO2024027971A1 (fr) Procédé et appareil de récupération de transfert conditionnel à double connectivité
CN117795991A (zh) 一种用于边缘计算中的位置服务的方法
KR20070060717A (ko) 이동통신 시스템에서 단말기의 불법 사용 방지 방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DPEN Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed from 20040101)
WWE Wipo information: entry into national phase

Ref document number: 2004801783

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2006517084

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: PA/a/2005/013930

Country of ref document: MX

WWE Wipo information: entry into national phase

Ref document number: 2530359

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 1020057024606

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 2004817654X

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 3556/CHENP/2005

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2006102365

Country of ref document: RU

WWP Wipo information: published in national office

Ref document number: 1020057024606

Country of ref document: KR

WWP Wipo information: published in national office

Ref document number: 2004801783

Country of ref document: EP

ENP Entry into the national phase

Ref document number: PI0411941

Country of ref document: BR