RU2368103C2 - Identification of mobile station in service centre of mobile station location detection - Google Patents

Abstract

FIELD: physics, communication. ^ SUBSTANCE: invention is related to communication engineering. Mobile station (MS) is configured with the possibility to code unique MS identifier (ID), such as international identification code of mobile station subscriber, in expansion container, which is optional information element identified with the help of radio resource location identification services protocol. Expansion container may be included as component into response message to measure position or message of protocol error. Centre of location identification is configured with the possibility to decode expansion container, extraction of MS ID and memorisation of MS ID in relation with unique identifier of positioning session. Mostly MS may be configured with parametre of testing mode. In one version of realisation MS ID coding in expansion container is activated in testing MS only when testing mode parametre is "ON". ^ EFFECT: provides for transfer of mobile station (MS) identification code into autonomous service centre of mobile station location detection. ^ 20 cl, 4 dwg, 1 tbl

Description

FIELD OF THE INVENTION

This application relates to the field of location services of mobile devices, and more particularly, to a method and device for transmitting an identification code of a mobile station to a stand-alone serving location center of mobile stations.

State of the art

Location services (short for LCS, COM for “location service”) for mobile phones and wireless digital communications devices (hereinafter collectively referred to as mobile stations or MSs, MSs) are an increasingly important area of activity for wireless providers. Location services information can be used to provide a variety of location services to users of mobile stations. For example, public security authorities can use the location information of a mobile station to determine the exact geographical location of a wireless device. Alternatively, the user of the mobile station can use the location information to determine the location of the nearest ATM, as well as the rewards assigned by that ATM. As another example, location information can help a traveler get step-by-step directions to their desired destination while on a route.

Technologies that allow a large number of system users to share a wireless communication system, such as, for example, global mobile communication system (GSM, GSM) technology, play an important role in meeting the growing demands of mobile computing, including the requirements for location services. As is well known, GSM uses a combination of time division multiple access and frequency division multiple access technologies that enable multiple users to interact simultaneously. GSM systems also often use universal packet radio technology to transmit data and provide location services.

The standards and functional descriptions for determining the position of the MS (“position” and “location” are used in the present description as equivalent terms relating to the geographical coordinates of the MS) in wireless communication systems. One exemplary reference relating to GSM and a COM is "3 ^{rd Generation Partnership Project, Technical Specification Group} , Services and System Aspects, Location Services (LCS), (Functional description) - Stage 2 (Release 1999)" (3- Partnership Project generation group, technical specification group, aspects of services and systems, location services (COM), (functional description) - Stage 2 (revision 1999)), (3GPP TS 03.71 V8.7.0), September, 2002. The link is referred to below as 3GPP TS 03.71 V8.7.0.

The second exemplary reference relating to GSM and SOM is the "3 ^{rd Generation Partnership Project, Technical Specification Group} GSM / EDGE Radio Access Network, Location Services (LCS), Mobile Stations (MS) - Serving Mobile Location Centre (SMLC) Radio Resource LCS Protocol (RRLP) (Release 1999) ”(3rd Generation Partnership Project, Technical Specification Group, GSM / EASD Radio Access Network (Electronic Data Acquisition Equipment), Location Services (COM), Radio Station COM Protocol (PSOMR) of the mobile station ( PS) - a service center for determining the location of mobile stations (OTSOMPS) (revision 1999)), (3GPP TS 04.31 V8.10.0), July, 2002. Link hereinafter referred to as 3GPP TS 04.31 V8.10.0.

A third exemplary reference relating to GSM and a COM is "3 ^{rd Generation Partnership Project, Technical Specification Group} Core Network, Mobile Application Part (MAP) specification (3G TS 29.002 version 3.h.0 Release 99)" (3- Partnership Project th generation, technical specification group, core network, mobile station support subsystem (POPD) specification (3G TS 29.002 version 3.h.0 edition 99)), June, 2000. The link is hereinafter referred to as 3GPP TS 29.002 V3.h.0.

A wireless communication network, such as a public land mobile network (PLMN, LMSSOP) in a GSM, can provide ancillary data to a MS that enables location measurements and / or improves measurement efficiency. One exemplary MS positioning method utilizes a global positioning system (GPS, GPS) and is referred to as “GPS assisted” or AGPS, GPS. In accordance with the SPGPS methods, the MS requests measurements from GPS satellites using auxiliary data provided by the network. In GSM systems, a request for measurements related to a given location is transmitted to a mobile location service center (SMLC, OTSOMPS). OTSOMPS manages the overall coordinates and plans the resources necessary to perform the positioning of the MS.

Development and validation of COM in a wireless communication system requires extensive operational testing. One problem that arises when testing COM in GSM systems having autonomous OTSOMPS, i.e. OTSOMPS, which is not integrated into the controller of the base station (BSC, KBS), is that the identification code of the testing PS is not transmitted to OTSOMPS in accordance with GSM standard specifications during a COM positioning session. The MS identification code is determined using a unique MS identifier (MS ID), such as the number of the international mobile subscriber identity code (IMSI, MOKAPS). The PS ID is usually available in the Subscriber Identity Code (SIM, IOCA) module or other equivalent component in the PS. The ID of the PS The PS that receives the services is provided to the BSC. However, during a positioning session, the BSC transmits only the logical link data element to the OTOMPS in order to distinguish one positioning session from another. Although this is an effective way for a normal operation, it makes testing very difficult, as the process of recovering information must be performed in order to associate a specific session with a specific PS.

Possible ways of addressing the problem of testing the identification code of the MS mentioned above may include combining the MSC in the BSC or modifying the MSC so that the information of the identification code of the MS is transmitted to the MSC in a non-standard way. However, these methods are undesirable, since such changes in the BSC are difficult and difficult to implement.

Therefore, an efficient method and apparatus is required for transmitting an MS identification code to a stand-alone OTSSMPS during a COM positioning session to facilitate operational testing.

SUMMARY OF THE INVENTION

A method and apparatus for providing the geographic location of a wireless mobile station, more specifically, a method and apparatus for transmitting an MS identification code to a stand-alone serving location center for mobile stations (MTSPS), have, in one example embodiment, a MS configured to encode its unique identifier of the MS (PS ID), such as the number of the international mobile subscriber identity code (MOKAPS), in an extension container, which is an optional information element defined by the Radio Resource Location Services (COM) protocol (PSOMP). An extension container may be included as a component in a location services message, such as a measure position response message or protocol error messages. OTSOMPS is configured to decode the expansion container, extract the PS ID and store the PS ID in connection with the unique identifier of the positioning session.

Advantageously, the MS can be configured with a test mode parameter. The test mode parameter can be set to “test mode on” (abbreviated as “on”) and “test mode off” (abbreviated as “off”), and the default value is “off”. In the MS, the configuration of the test mode parameter can be controlled by the appropriate command using the serial communication line to the telephone or through the user interface of the MS. In one embodiment, the encoding of the PS ID in the extension container is activated in the test PS only when the test mode parameter is set to “on”.

Brief Description of the Drawings

1 is a functional block diagram of an example wireless communication system used to provide wireless communications including location services.

FIG. 2 is a functional block diagram of another exemplary wireless communication system used to provide wireless communications including location services depicting additional system components.

3 is a functional block diagram illustrating a message flow between a mobile testing station and a serving location center of mobile stations.

4 is a flowchart illustrating the steps of an example method.

Detailed Description of a Preferred Embodiment

1 illustrates a simplified conventional wireless communications system 100 that can be configured to test location services. As shown in FIG. 1, a mobile station (110) (MS) communicates with one or more base transceiver stations 122, 124 (BTS, BTS) via wireless communication lines 152, 154. Each BTS provides a geographic area of coverage (or service), commonly referred to as a “cell”. Although two BTSs are illustrated by way of example, depending on the positioning mechanisms used, location services can be provided at MS 110 using only one BPS or using three or more BPSs. As described in 3GPP TS 03.71 V8.7.0, incorporated herein by reference, positioning mechanisms may include the arrival time of the uplink signal (mobile station - base station) (TOA, AM), extended observed time difference (E-OTD , R-NRV) and SPGPS. Both VP and R-NRV require signal exchange between PSs and multiple BPSs.

In accordance with the present description, the MS 110 may include, without limitation: a wireless telephone, a personal digital assistant with wireless functionality, a portable laptop computer having wireless functionality, and any other mobile digital device designed for personal communication via wireless compound.

BPS 122, 124 are operatively connected for data transmission with the controller 126 of the base station (BSC). BTS 122, 124, and BSC 126 are part of base station system 120. As shown in FIG. 1, BSC 126 is connected to a mobile station location center (MTSPS) 130. OTSOMPS manages the location services by managing the resources necessary to perform positioning of the MS. In alternative configurations, the OCMPS can be operatively connected through other elements (not shown) in a wireless communication system.

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, typically only one satellite or multiple satellites can be used to provide location services to a mobile station in a wireless communication system. Satellite data can also be received using other receivers (not shown) in the network 140 of the communication service provider. Those skilled in the art of communications will understand GPS positioning systems for wireless systems typically include elements such as fixed GPS receivers and / or global reference networks for receiving satellite signals and providing reference data to OTSOMPS. BSC 126 is connected to a communications service provider network 140 to receive and transmit data, such as audio / video / text transmission and programming data, position requests, etc. One example of a communications service provider network is a terrestrial network of a public mobile communications system ( NSMOSOP), working under the GSM.

2 shows another exemplary communication system 200 that can provide location services, illustrated in a functional block view. For simplicity, only one GPS satellite 272 and the associated broadcast signal link are illustrated.

As shown in FIG. 2, the MS 210 includes a central processing unit 212 (CPU, CPU), a memory 214, a user interface 213, a Subscriber Identity Code (MIKA) module 215, and a transceiver 216. The term “CPU” throughout the description, is intended to encompass any processing device, alone or in combination with other devices (such as memory), which can control the operation of a device (such as OTsOMPS 230 or PS 210, or a part thereof) into which it is included. For example, a CPU may include microprocessors, embedded controllers, application integrated circuits (ASICs, ISPOs), digital signal processors (DSPs, DSPs), state machines, specialized discrete hardware, and the like. The system and method described herein is not limited to the described specific hardware components or any specific hardware components selected for implementing the CPU 212.

The transceiver 216 allows the transmission and reception of data, such as data transmission and programming of audio / video / text, between the MS 210 and the remote location, such as BPS 224 and 226, or GPS satellites, such as satellite 272. The antenna 218 is electrically connected to the transceiver 216. The main work of PS 210 for voice and data transmission is well known in the art and is not described in detail in this application.

As shown in FIG. 2, system 200 includes an OCMPS 230 having a memory 234 and a CPU 232. The CPU 232 controls the operation of the OCOMPS 230 in accordance with programmed instructions and data stored in the memory 234. The memories 214 and 234 may include components read-only memory (ROM, ROM), random access memory (RAM, RAM) and non-volatile ROM components. A memory 234 stores and provides instructions and data for the CPU 212. The components of the OCOMPS 230 are connected together using an internal bus system 236. The components of the MS 210 are connected together using the internal bus system 219.

As described in more detail below, MIKA 215 includes a unique MS identifier (MS ID), such as a Mobile Station Subscriber Identity Code (IOSC), Mobile Station Subscriber Integrated Services Directory Number (MSISDN, NDISAPS) or another MS ID. MOKPS and NDISAPS are unique identifiers for PS, and any of them can be used. Subscriber ID (usually MOKPS, although NDISAPS or other Subscriber ID can be used) can be retrieved using CPU 212, encoded in accordance with programmed instructions and data stored in memory 214, included in the response message, measure PSOMP position or in an error message protocol and transmitted to OTSOMPS 230 through communication lines and system components, illustrated in figure 2.

User interface 213 may be used to control the settings of the test mode parameter, as described below. In one exemplary embodiment, the user interface may include a graphical user interface (GUI, GUI) and input devices such as a touch screen, pointing device, or keyboard. In another exemplary embodiment, the test mode parameter can be controlled using specific commands received via the connection (for example, a serial connection that is not shown) to a local device (not shown), such as a portable laptop computer or personal digital assistant, and the local device is operational connected to CPU 219.

As shown in FIG. 2, the communication system 200 includes a BSS, SBS 220, which, in turn, includes BSC 222 and a plurality of BTSs, such as BTS 224, 226. BTSs allow the transmission and reception of data (such as audio / video / text and programming data) between BSC 222 and remote locations, such as MS 210, or GPS satellites, such as satellite 272. Antennas 228 and 229 are electrically connected to BTS 224 and 226, respectively, in a known manner. MS 210 communicates with the BTS via wireless communication lines, such as communication line 272. Additional radio links (not shown) can be used to transmit signals between MS 210 and BPS 224 or other BTS (not shown). The basic operations of BSC 222 and BPS 224, 226 are well known in the art and therefore are not described in more detail in this application. BSC 222 is connected to a communications service provider network 240. The BSC 222 receives and transmits data, such as audio / video / text transmission data and programming data, position requests or position data, from a communication service provider network 240.

KBS 220 is also connected to OTsOMPS 230 in order to transmit and receive data related to COM. Examples of such data are described in detail below.

Messages PSOMRR COM exchanged between PS and OTsOMPS

Figure 3 illustrates the flow of messages PSOMP, which can be exchanged by the MS 310 test and OTOMPS 330 during the procedure for requesting a position. This procedure is described in more detail in reference 3GPP TS 04.31 V8.10.0.

PSOMRR auxiliary data message 342, PSOMRR protocol error message 346 and auxiliary data confirmation message 348 enable OTSOMPS to transmit auxiliary data to the MS related to position measurement and / or location calculation when downlink pseudo-segmentation (base station - mobile station) is used (in accordance with the prior art, as described in 3GPP TS 04.31 V8.10.0). If pseudo-segmentation is not used, the position request procedure skips messages 342, 346 and 348. The PSOMPP auxiliary data message 342, the PSOMPP protocol error message 346 and the auxiliary data confirmation message 348 can also enable OTOMPS to transmit auxiliary data requested by the MS. In this case, messages 352, 354, and 356 are skipped.

Using the PSOMPP auxiliary data message 342 or the request message 352 to measure the PSOMPR position, the OCOMP transmits the auxiliary data component to the MS. This component includes auxiliary data for measuring the location and / or calculating the location.

The MS transmits the PSOMPP message containing the protocol error component to the OTSOMPS using the PSOMPP protocol error message 346. This message is sent only if there is a problem that prevents the PS from receiving the complete and understandable component of the auxiliary data (the message contingent aspect is indicated in FIG. 3 by using a dashed line). The protocol error message 346 includes an optional information element referred to as an extension container. As described in more detail below, the extension container of the protocol error message 346 may be configured to transmit the PS ID (e.g., IOCS or NDISAPS) of the MS to the OTOMPS. This message is sent when there is a protocol error. Then, as described below, the following message can be used to transmit the identification code of the MS.

When the MS has received the full component of the auxiliary data, it transmits the auxiliary data confirmation message 348 to the MSSPP to the MSSP.

OTSOMPS transmits a component of the request to measure the position in the MS using the message 352 request position evaluation PSOMR. This component includes quality of service (QoS, QoS), other instructions, and possible supporting data.

The MS transmits the PSOMPP message containing the protocol error component to the OTsOMPS using the PSOMPP protocol error message 354. This message is only transmitted if there is a problem that prevents the PS from accepting a complete and understandable component of the request to measure the position. The protocol error message 354 also includes an optional extension container, which may be configured to transmit the PS ID (e.g., IOCS or NDISAPS) of the PS to the OTSOMPS. However, this message is only transmitted when a protocol error occurs. Then the following message, described below, can be used to transmit the identification code of the MS.

The MS attempts to report the requested location measurements using the response message 356 to measure the position of the PSOMP. Examples of location measurements may include position estimation, HRPS measurements, or measurement error. When the MS has position measurements, a position estimate or an indication of an error (measurement / position estimation is not possible), it transmits the results in the response component to measure the position to OTSOMPS.

Message 356 response to measure the position PSOMP also includes an optional extension container, which can be configured to transmit the ID of the PS (for example, MOKPS or NDISAPS) PS in OTSOMPS. If the position determination process has not previously been prematurely terminated due to an error, the extension container for this message may be configured to transmit the PS ID to OTSOMPS. If the process is prematurely terminated before this message, then one of the protocol error messages 346 or 354 may be used instead.

Description of extension container

The PSOMPR expansion container is exported from the extension data types of the mobile station extension subsystem (described in detail in the included 3GPP TS 29.002 V3.h.0 link). As a result, its description is consistent with the rules for describing the notation of the abstract syntax of POPD one (ASN.1, NAS.1). For actual field encoding / decoding, packet encoding rules (PER) are applied (for example, a bitmap for optional parameters, an extension pointer when using ellipse notation, etc.). As described below, PPAP compatible coding includes identifiers of objects that have been registered previously, or must still be registered.

Exemplary encoding of the NAS.1 extension container is shown in the pseudo code below.

POPD EXTENSION :: = CLASS { & Extension Type OPTIONAL, & Eid Extensions OBJECT ID Extension Container :: = SEQUENCE { List of Hidden Extensions [0] List of Hidden Extensions OPTIONAL, [1] PCS Extensions OPTIONAL, ...} List of Hidden Extensions :: = SIZE OF SEQUENCE (1 ... maxNumOfHidden Extensions) OF Hidden Extension maxNumOfHidden Extensions WHOLE :: = 10 Hidden Extension :: = Sequence { Extension id POP-EXT. & Extension Id ({Many Extensions}), Extension type POPD EXPANSION. & Extension Type ({Many Extensions} {@ Extension ID}) OPTIONAL}

In accordance with one embodiment, the designation PS can be encoded in the variable Type of extension. Optional PCS Extensions are not included in this exemplary embodiment. OI, IO (Object Identifier) should not be confused with IOCCO or another PS ID that can be used to identify testing PSs. The contents of the EUT, or “value” of the EUT, is preceded by a length pointer that provides the number of octets of the EUT value.

As described in the links included in this application, IO NAS.1 makes it possible to uniquely identify an object that is registered on the World Wide Web. The properties of the EUT are well known to specialists in the field of wireless communications and therefore are not described in more detail in this application. AIs can be registered through the appropriate organization or registration authority. An example of an existing IO registration, similar to registration that would be suitable for the exemplary embodiment, is the registration assigned to BASIC-PPK US.1, UNLAYED version: {join-iso-itu-t asnl (1) packed-encoding (3) basic (0) unaligned (1)} “Packed encoding of the same type NAS.1 (basic unaligned)”. A suitable IO can be represented using the hexadecimal PPK format and used for the “Extension ID” object of the approximate encoding of the extension container shown above. For this example, the IO is represented using the decimal digits “1,3,0,1”, which can be encoded using the hexadecimal sequence PPC 0x03.0x02.00.01 (0x03 is a variable length of 3 octets; 0x2b represents 43 = 40 * 1 + 3).

In one embodiment, the “Extension Type” variable is a component that contains covert extension data that can be used to transmit an IOCPS or another PS ID for a test PS. This is an open type NAS-1, therefore, it has a length determinant, followed by a list of fields. For the current example, the length of the hidden extension can be selected not exceeding 128 octets. Therefore, the length determiner can be encoded in one octet, or in 8 bits. In one embodiment, the field list of the variable Extension Type may have the following format:

Fields List :: = SEQUENCE { Test Modification Extensions Test Extension Modification, moxa MOKPS, ... }

The following notes apply in the example above: The elliptic notation “...” indicates that extensions can be added. If, in some exceptional case, the testing PS cannot provide its MOKPS, the MOKPS field may be filled with zeros. The Test Extension Modification is an integer variable that has a value between 0 and 63, exclusively, and can be represented using a 6-bit hexadecimal number. The IOCCO variable is an octet string with a fixed field of 8 octets.

Table 1 presents exemplary coding of the extension container in accordance with the above examples:

Table 1 EXAMPLE ENCODING CONTAINER CODING Field Variable Field length Comments Start extension container Extension pointer preamble 0 1 bit Expandable component but extension not present Optional Array Bitmap 10 2 bit A list of hidden extensions is present, pcs-extensions are missing Number of hidden extensions 1 to 10 4 bit The range of the encoded value is: (10-1), and 9 is 1001b (4-bit binary encoding) Start hidden extension (# 1) First (and last) hidden extension Optional Array Bitmap one 1 bit Indicates whether the optional Extension Type parameter is present (a value of 1 indicates that it is present) Start Extension ID This IO, which contains a length field and a value field Object ID Length 8 bit The length is encoded in one octet.
For this example, the number of octets in the IO value is 3, therefore, the length is encoded using the hexadecimal number of the control panel 0x03. Object ID Length In the present example, the IO value is (1,3,0,1) and encoded using the hexadecimal sequence 0x2b 00 01 (0x2b is equal to 43 = 40 * 1 + 3) Start Extension Type Length gauge 0b7b ... b1 8 bit For this example, the binary coding for the length determinant is: 0000 0010b (binary value) Start Extension Type value This is an open type bit field. Extension token 0 1 bit Not yet an extension Test Extension Modification 0 6 bit It identifies the modification number of the test extension. The initial value is 0.
Thus, a new parameter should not be added as an extension (using the extension preamble). Adding a new parameter should rely on a test modification of the extension. The value of MOKPS 8 octet 15 digits of binary encoded data - If the IKPS is less than 15 digits, the additional digits are encoded 1111b (binary value) Aggregate 0 one The total length of the bit field of the hidden extension without filler is 15 bits. Thus, one placeholder bit is needed to reach a 2 octet boundary.

Identification of test PS using OCOMPS and sample work.

In one exemplary embodiment, the testing MS is configured to encode the associated MS ID (e.g., IOCS or NDISAPS) in the extension container of the response message 356 to measure the position or in the extension container of the protocol error messages 346 and 354 (FIG. 3). As described above, the response message to measure the position is transmitted to OTSOMPS to inform the determination of the position. The protocol error messages are transmitted using the testing PS to the OTSOMPS in order to report the protocol error. OTSOMPS is configured to decode the expansion container, retrieve the ID of the MS and store the ID of the MS in connection with a unique identifier of the positioning session, which may belong to the set of identifiers of the positioning sessions supported by OTSOMPS.

When attempting to decode a hidden extension, the OCOMPS may first try to decode the EUT. If the received EUT is not recognized, OTsOMPS may try to skip the EUT and decode the length of the open type variable in order to skip the entire hidden extension container. If the expansion container prevents the proper decoding of the PSOMPP message, OTsOMPS can transmit the error message of the PSOMPP protocol to the MS and terminate the position determination session with the BSC.

Whenever the OCOMPS detects that the length determinant of the EUT or Extension Type is encoded using a value indicating that the length is greater than 16 K, the OCOMPS transmits a protocol error message to the MS. OTSOMPS completes the position determination session with the BSC.

Advantageously, the MS can be configured with a test mode parameter. The test mode parameter can be set to “test mode on” (abbreviated as “on”) and ”test mode off” (for short, “off”), and the default value is “off”. In the MS, the configuration of the test mode parameter can be controlled by the appropriate command using the serial communication line to the telephone or through the user interface (UI, UI) of the MS. Encoding of the ID of the PS in the extension container is activated in the test PS only when the test mode parameter is set to the “on” state. In one embodiment, the encoding of the PS ID in the extension container is activated in the test PS only when the test mode parameter is set to “on”.

4 is a flowchart illustrating steps in an exemplary method. At step 402, the MS receives a message from OTsOMPS. Exemplary messages may include a PSOMPP auxiliary data message or a request message to measure a PSOMPP position. The method proceeds to step 404.

Alternatively, the PS may be provided with a test mode parameter. If the MS is programmed to decode the MS ID and does not have a test mode parameter, then step 404 may be skipped and the method proceeds directly to step 406. If the test mode parameter is included in the MS and it is set to the ON state, the concept also proceeds to step 406. If the MS is not programmed to send the MS ID, or if the test mode parameter is set to the OFF state, the method proceeds to step 408.

At step 406, the MS encodes the associated MS ID in the extension container of a suitable response message, such as measure position response message 356 (FIG. 3), protocol error messages 346 and 354. Suitable messages may include any messages having an extension container. Other messages that can be sent that do not have an extension container, such as an ancillary data confirmation message, are not used to encode the MS ID and are not mentioned in the steps shown in FIG. 4. The method proceeds to step 408.

At step 408, the MS transmits a suitable response message to the OTSOMPS and proceeds to step 410.

At step 410, the OCOMPS processes the appropriate response message and proceeds to step 412.

At step 412, if the OCMPS is configured appropriately to retrieve the PS ID from the expansion container, the method proceeds to step 414. If the OCOMPS is unable to retrieve the PS ID, the method proceeds to step 416. If the PS ID was not sent (for example, the test mode was set to OFF), the method also proceeds to step 416.

At step 414, the OCOMPS remembers the PS ID in connection with the unique identifier of the positioning session for reference by the test engineers when required, and then continues with the normal processing functions.

At step 416, the OCOMPS can respond by sending a PSOMP protocol error message to the MS and ending the position determination session with the BSC before continuing with the normal processing functions. Alternatively, if the MS did not send the MS ID (for example, the test mode was turned OFF), OTsOMPS will also continue with the usual processing functions at step 416. As another option, the OTsOMPS can transmit the PSOMRR protocol error message to the PS without ending the session position determination with BSC before proceeding with normal processing functions. These possible responses using OCOMPS are further provided below.

There are several advantageous new aspects. For example, the implementation of hidden expansion affects only the operation of the PS and OTsOMPS. It does not affect the operation of other network elements, such as SBS, BSC, or a mobile switching center (not shown). The MS identification method and device does not affect other elements, since the PSOMPP messages are transmitted transparently using the BSC, and only the size of the PSOMPP message is an indicator for processing the message.

Another advantageous aspect relates to the possibility of mutual operations between the testing PS and the “simplified” OTSOMPS (that is, OTSOMPS, which is not configured to operate in the testing mode in accordance with the present description). If OTSOMPS cannot decode the expansion container (for example, as could happen with the roaming situation, despite the fact that roaming would not be a typical circumstance for PS testing), several possibilities may occur: 1) when the simplified OTSOMPS detects the presence of an optional container extensions, he can choose, not try to decode the message, and can send a protocol error message in response; 2) when the extension container is at the end of the message, the simplified OCOMPS may try to decode the message, but may stop decoding after reaching the extension container, thereby processing the message decoded before reaching the extension container; 3) the simplified OCOMPS may be able to decode the extension container, but decides to cancel the hidden extensions for which it does not recognize the IO. For the cases 2) and 3) mentioned above, the possibility of performing a positioning operation is supported. However, for the case 1 mentioned above, the test PS will not be able to perform the positioning operation until the test mode parameter is implemented and set to the OFF state.

Another advantage is the size of the response message to measure the position of the PSOMP. Adding a hidden extension increases the size of the PSOMPP payload, which can be a problem in terms of segmentation, especially to measure the position of the PSOMPP for the response message. However, if the message size remains up to 252 octets, segmentation of the communication line between the mobile station and the base station is necessary. The exemplary embodiment described above limits the increase in the size of the PSOMPP message to 128 octets (120 octets is a typical number for reporting one set of GPS measurements associated with 16 satellites) or less, reducing the likelihood that the full PSOMPP message will exceed 252 octets.

Those skilled in the art of communications and computers will understand that a computer-readable medium that explicitly performs the steps of the method of any of the embodiments described herein can be used in accordance with the present description. Such a storage medium may include, without limitation, RAM, ROM, ROM, EPROM (electrically programmable ROM), EEPROM (electrically erasable programmable ROM), floppy disk, hard disk, CD-ROM (ROM on CD), etc. The disclosure also includes the steps of a method of any of the above embodiments synthesized as digital logic in an integrated circuit, such as a gate array, field programmable or programmable logic matrix, or other integrated circuits, which may be cook or modified to carry out the instructions of a computer program.

Mobile stations 110 and 210 in accordance with the present description may include without limitation: a cordless telephone, a personal digital assistant with wireless functionality, a portable laptop computer with wireless functionality, and another mobile digital device for personal communication via a wireless connection.

A number of embodiments are described. However, it will be understood that the methods described herein may be performed in software or hardware, or a combination of hardware and software embodiments. As another example, it should be understood that functions described as being part of one module can generally be performed equivalently in another module. As another example, the steps or actions depicted or described in a particular sequence can usually be performed in a different order, with the exception of those embodiments described in the claims that include a specific order for the steps.

Claims (20)

1. A method for testing location services for use in a wireless communication system, the method comprising:
a) receive the first message of the location services in the mobile station (MS);
b) encode the unique identifier of the MS in the extension container of the second location services message;
c) transmitting a second positioning services message to a mobile location service center (GPSMTS) in response to a first message for location services, the GPSMC supporting a plurality of positioning session identifiers;
d) decode the extension container, thereby extracting the unique identifier of the MS; and
e) remember the unique identifier of the PS corresponding to the unique identifier of the session of positioning and associated with a unique identifier of the session of positioning belonging to the set of identifiers of session sessions of positioning. 2. The location services testing method of claim 1, wherein the first location services message is an ancillary data message of the radio location services (COM) radio resource protocol (PSOMP). 3. The location services testing method of claim 1, wherein the first location services message is a request message to measure the position of the PSOMP. 4. The method of testing location services according to claim 1, in which the unique identifier of the MS is the international identification code of the subscriber of the mobile station. 5. The method for testing location services according to claim 1, in which the unique identifier of the MS is the directory number of the integrated services of the subscriber of the mobile station. 6. The method for testing location services according to claim 1, wherein the step of encoding the unique identifier of the MS further includes setting a parameter of a test mode that controls the encoding of the unique identifier of the MS. 7. The location services testing method of claim 1, wherein the second location services message is a PSOMP protocol error message. 8. The location services testing method of claim 1, wherein the second location services message is a response message to measure a PSOMP position. 9. A system for testing location services in a wireless communication system, comprising
a) a mobile station (MS), configured to perform positioning functions, wherein the MS includes
i) a transceiver configured to receive a first location services message and transmit a second location services message; and
ii) a central processor (CPU) of the MS operatively connected to the transceiver, wherein the MS CPU receives the first location services message, and the MS CPU encodes a MS identifier that uniquely identifies the MS, and in addition, the MS CPU inserts a unique MS identifier in the expansion container a second location services message;
b) a base station system (SBS), wherein the SBS includes a base transceiver station (BTS) configured to transmit a first location service message to the MS and receive a second location service message from the MS; and
c) a mobile station serving location center (OTSOMPS) that manages the location services for the wireless communication system, wherein the OTSOMPS supports a plurality of positioning session identifiers and, in addition, the OTSOMPS includes
i) an OCOMPS CPU operatively connected to the SBS, wherein the OCOMPS CPU outputs a first location services message and transmits the first location services message to the SBS and, in addition, the OCOMPS CPU receives a second location services message from the SBS and decodes the extension container of the second services message determining a location, thereby extracting a unique identifier of the MS; and
ii) a memory coupled to the OCOMPS CPU, the memory storing a unique identifier of the MS corresponding to the unique identifier of the positioning session and associated with a unique identifier of the positioning session from the plurality of positioning session identifiers. 10. The system for testing location services according to claim 9, in which the MS CPU includes a test mode parameter and in which the MS CPU encodes the MS identifier and inserts a unique MS identifier in the expansion container in response to the setting of the test mode parameter. 11. The system for testing location services of claim 10, wherein the MS includes a user interface and in which the user interface is connected to the MS CPU to control the setting of the test mode parameter. 12. The system for testing the location services of claim 9, wherein the second location services message is a response message to measure the position of the radio location services (COM) radio resource protocol (PSOMP) message. 13. The system for testing location services of claim 9, wherein the second location services message is a PSOMP protocol error message. 14. The system for testing the location services of claim 9, wherein the first message of the location services is a PSOMPP ancillary data message. 15. The system for testing location services according to claim 9, in which the second message of the location services is a request message to measure the position PSOMP. 16. A system for testing location services according to claim 9, in which the MS includes a Subscriber Identity Code (MIKA) module that stores the unique identifier of the MS. 17. The system for testing location services according to claim 9, in which the unique identifier of the MS is the international identification code of the subscriber of the mobile station. 18. The system for testing location services according to claim 9, in which the unique identifier of the MS is the directory number of the integrated services of the subscriber of the mobile station. 19. A system for testing location services in a wireless communication system, comprising
a) means for receiving a first location services message;
b) means for encoding a unique identifier of the MS in the extension container of the second location services message;
c) means for transmitting a second positioning services message to a mobile location service center (MTSPS) in response to the first message of the location services, MTSOS supporting a plurality of positioning session identifiers;
d) means for decoding the extension container of the second location services message, thereby retrieving the unique identifier of the MS; and
e) means for storing a unique identifier of the MS corresponding to a unique identifier of a session of positioning and associated with a unique identifier of a session of positioning from a plurality of identifiers of positioning sessions. 20. A computer-readable medium comprising a computer program running on a general purpose computing device for testing location services in a wireless communication system comprising a plurality of mobile stations and a plurality of base stations, the program comprising
a) a first set of instructions for receiving a first message of location services in a mobile station (MS);
b) a second set of instructions for encoding a unique identifier of the MS in the extension container of the second message location services;
c) a third plurality of instructions for transmitting a second positioning services message to a mobile location service center (MTSO) in response to a first positioning services message, the MTSS supporting a plurality of positioning session identifiers;
d) a fourth plurality of instructions for decoding an extension container, thereby extracting a unique identifier of the MS; and
e) a fifth plurality of instructions for storing a unique identifier of a PS corresponding to a unique identifier of a positioning session and associated with a unique identifier of a positioning session belonging to a plurality of identifiers of positioning sessions.

Images