This section is only applicable to the lab applications.
The test set supports the configuration, sending, and retrieving of the components of a generic RRLP message used to transport location services information between the MS and the Serving Mobile Location Centre (SMLC). The possible components of the message are:
The information that follows provides the user configurations allowed by the test set for of each of these components. For more information about each of the parameters and the meanings of their respective values refer to 3GPP TS 04.31, Location Services (LCS);Radio Resource LCS Protocol (RRLP) .
The configuration, sending, and retrieval of results for RRLP messages are all performed using GPIB commands only.
You can configure the RRLP message in any operating mode.
RRLP messages can only be sent while the test set is in Active Cell operating mode.
The RRLP pipe mode must be disabled. See CALL:PPRocedure:PMEasurement:PIPE for command information. See A-GPS (Assisted-GPS) for more information about the RRLP pipe mode.
For your mobile station to receive and respond to RRLP messages, it must be in one of the following states:
The mobile station can NOT be monitoring a PBCCH or transferring packet data. Verify that your mobile station is in one of the valid states before attempting to send it RRLP messages.
This component of the RRLP message is used to request location measurements or a location estimate from the MS. It includes instructions and can also include assistance data for the MS. The Measure Position Request component can contain several elements. Only the Positioning Instructions Element is required. The following table contains the elements and the fields and values that you can configure. You can configure the fields that have an "X" in the "User Configurable" column of the table. If there is no "X" designation, the value that is supplied by the test set for that parameter is shown in the table. The "Optional" column is used to indicate optional components and elements. You can include or exclude these components and elements using GPIB commands.
See CALL:PPRocedure:PMEasurement:MPRequest for the GPIB commands necessary to configure the Measure Position Request parameters.
The Event based RRLP functionality allows the user to send RRLP pipe data to the test set and have that data sent to the DUT when one of following signaling events occur:
The GPIB command to set the RRLP Event Type is CALL:PPRocedure:PMEasurement:PIPE:SEND:EVENt And use CALL:PPRocedure:PMEasurement:PIPE:SEND:EVENt:TIMeout to set the timeout value. An error will be generated if a timeout occurs and then the queued RRLP message is discarded.
The following table contains the elements and the fields and values of the Measure Position Response component of the RRLP message that you can retrieve using GPIB commands. The test set gives you access to the fields that have a "Yes" in the "Available" column of the table. A "No" indicates the information is not available.
| Multiple Sets Element | |
| Parameter | Available? |
| Number of Measurement Information Sets | YES |
| Number of Reference BTS' (= x, where 1 <= x <= 3) | YES |
| Reference BTS Relation to Measurement Elements | YES |
| Reference BTS Identity Element (Optional) | |
| Parameter | Available? |
| Cell ID Type (for each BTS `x' where 1 <= x <= 3) | YES |
| Reference LAC (for each BTS `x' where 1 <= x <= 3) | YES |
| Reference CI (for each BTS `x' where 1 <= x <= 3) | YES |
| Reference BCCH Carrier (for each BTS `x' where 1 <= x <= 3) | YES |
| Reference BSIC (for each BTS `x' where 1 <= x <= 3) | YES |
| Request Index (for each BTS `x' where 1 <= x <= 3) | YES |
| System Info Index (for each BTS `x' where 1 <= x <= 3) | YES |
| E-OTD Measurement Information Element (Optional) | |
| Parameter | Available? |
| Reference Frame Number (for each set `x' where 1 <= x <= 3) | YES |
| Reference Time Slot (for each set `x' where 1 <= x <= 3) | YES |
| Reference Quality (for each set `x' where 1 <= x <= 3) | YES |
| Number of Measurements (for each set `x' where 1 <= x <= 3) | YES |
| Std Resolution (for each set `x' where 1 <= x <= 3) | YES |
| TA Correction (for each set `x' where 1 <= x <= 3) | YES |
| Number of Measured Neighbours (n) (for each set `x' where 1 <= x <= 3) | YES |
| BTS `n' Identity Present (n <= 10) (for each set `x' where 2 <= x <= 3 - this field is not included in the first measurement set) | YES |
| BTS `n' Cell ID Type (n <= 10) (for each set `x' where 1 <= x <= 3) | YES |
| BTS `n' LAC (n <= 10) (for each set `x' where 1 <= x <= 3) | YES |
| BTS `n' CI (n <= 10) (for each set `x' where 1 <= x <= 3) | YES |
| BTS `n' BCCH Carrier (n <= 10) (for each set `x' where 1 <= x <= 3) | YES |
| BTS `n' BSIC (n <= 10) (for each set `x' where 1 <= x <= 3) | YES |
| BTS `n' Multiframe Offset (n <= 10) (for each set `x' where 1 <= x <= 3) | YES |
| BTS `n' Request Index (n <= 10) (for each set `x' where 1 <= x <= 3) | YES |
| BTS `n' System Info Index (n <= 10) (for each set `x' where 1 <= x <= 3) | YES |
| BTS `n' Neighbour Time Slot (n <= 10) (for each set `x' where 1 <= x <= 3) | YES |
| BTS `n' Number of EOTD Measurements (for each set `x' where 1 <= x <= 3) | YES |
| BTS `n' Std of EOTD (n <= 10) (for each set `x' where 1 <= x <= 3) | YES |
| BTS `n' OTD (n <= 10) (for each set `x' where 1 <= x <= 3) | YES |
| Location Information Element (Optional) | |
| Parameter | Available? |
| Reference Frame | YES |
| Fix Type | YES |
| GPS TOW | NO |
| Position Estimate - Type of Description | YES |
| Position Estimate - Sign of Latitude | YES |
| Position Estimate - Degrees Latitude | YES |
| Position Estimate - Degrees Longitude | YES |
| Position Estimate - Uncertainty Code | YES |
| Position Estimate - Uncertainty Semi Major | YES |
| Position Estimate - Uncertainty Semi Minor | YES |
| Position Estimate - Orientation Major Axis | YES |
| Position Estimate - Confidence | YES |
| Position Estimate - Direction of Altitude | YES |
| Position Estimate - Altitude | YES |
| Position Estimate - Altitude Uncertainty | YES |
| GPS Measurement Information Element (Optional) | |
| If GPS measurement information is provided, the message will still be decoded but no information will be available on this element via GPIB. | |
| Location Information Error Element (Optional) | |
| Parameter | Available? |
| Error Reason | YES |
| Extension Container Element | |
| If the Extension Container element is included, the message will still be decoded but no information will be available on this element via GPIB. | |
| Release 98 Extension Element (Optional) | |
| If the Release'98 Extension element is included, the message will still be decoded but no information will be available on this element via GPIB. | |
Most configurable elements of the Assistance Data component of the RRLP message are identical to related elements in the Measure Position Request message detailed in Measure Position Request Variable Parameters . Therefore, the values currently set for these common elements in the Measure Position Request message are used for constructing the Assistance Data message.
The following table contains the elements and the fields and values unique to the Assistance Data component of the RRLP message that you can configure. You can configure the fields that have an "X" in the "User Configurable" column of the table. If there is no "X" designation, the value that is supplied by the test set for that parameter is shown in the table. The "Optional" column is used to indicate optional components and elements. You can include or exclude these components and elements using GPIB commands.
| E-OTD Reference BTS for Assistance Data (Optional) | ||
| Field | Optional | |
| BCCH Carrier | ||
| BSIC | ||
| Timeslot Scheme | ||
| BTS Position - Type of Description | X | |
| BTS Position - Sign of Latitude | X | |
| BTS Position - Degrees Latitude | X | |
| BTS Position - Degrees Longitude | X | |
| BTS Position - Direction Altitude | X | |
| BTS Position - Altitude | X | |
| E-OTD Measurement Assistance Data (Optional) | ||
| User Configurable | ||
| Number of BTSs (n<= 8) | ||
| BTS[n] Multiframe Offset (n<= 8) | ||
| BTS[n] Rough RTD (n<= 8) | ||
| BTS[n] Fine RTD (n<= 8) | ||
| More Assistance Data to be Sent(Optional) | ||
| User Configurable | ||
| More Assistance Data | ||
| Optional | ||
See CALL:PPRocedure:PMEasurement:ADATa for the GPIB commands necessary to configure the Measure Position Request parameters.
Use the CALL:PPRocedure:PMEasurement:ADATa:ACKNowledged? to query the status of the last Assistance Data message sent to the mobile station.
The RRLP Protocol Error message can be sent in two directions:
The test set can both send and receive protocol error messages.
In a network, protocol error messages are only sent in response to a Measure Position Response from the mobile station. However, with the test set, you can send a protocol error message to the mobile station at any time. You can configure the error cause value to be sent and send the protocol error message using GPIB commands. See CALL:PPRocedure:PMEasurement:PERRor .
The mobile station can generate a protocol error message in response to either the Measure Position Request or Assistance Data messages. When this occurs, the following error message appears on the front panel display: "Protocol Error; RRLP Protocol Error Received from MS. Error Code <n>". <n> is a number between 0 and 5 and represents the value of the Protocol Error component of the RRLP message received from the MS. These values and their meanings are listed as settings for the command CALL:PPRocedure:PMEasurement:PERRor:CODE .
This error message can also be retrieved using the GPIB command SYSTem:ERRor? .