Content for TS 25.453 Word version: 18.0.0

3.1 Definitions 3.2 Abbreviations 4.1 Procedure Specification Principles 4.2 Forwards and Backwards Compatibility 4.3 Specification Notations
...

1 Scope p. 10

The present document specifies the Positioning Calculation Application Part (PCAP) between the Radio Network Controller (RNC) and the Stand-Alone SMLC (SAS). It fulfills the RNC-SAS communication requirements specified in TS 25.305 and thus defines the Iupc interface and its associated signaling procedures.

2 References p. 10

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1] Void

[2] Void

[3]

TS 25.452: "UTRAN Iupc interface signalling transport".

[4]

TS 25.331: "Radio Resource Control (RRC) Protocol Specification".

[5] Void

[6]

TS 25.305: "Stage 2 functional specification of UE positioning in UTRAN".

[7]

ITU-T Recommendation X.680 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation".

[8]

ITU-T Recommendation X.681 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Information object specification".

[9]

ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)".

[10]

ICD-GPS-200: (12 April 2000) "Navstar GPS Space Segment/Navigation User Interface".

[11]

TS 23.032: "Universal Geographical Area Description (GAD)".

[12]

TR 25.921: (version 7.0.0) "Guidelines and principles for protocol description and error handling".

[13]

TS 25.133: "Requirements for support of Radio Resource management (FDD)".

[14]

TS 25.123: "Requirements for support of Radio Resource management (TDD)".

[15]

TS 22.071: "Location Services (LCS); Service Description; Stage1".

[16]

TS 25.212: "Multiplexing and Channel Coding (FDD)".

[17]

TS 25.213: "Spreading and Modulation (FDD)".

[18]

TS 25.223: "Spreading and Modulation (TDD)".

[19]

TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)".

[20]

TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)".

[21]

TS 25.102: "UE radio transmission and reception (TDD)".

[22]

Galileo OS Signal in Space ICD (OS SIS ICD), Issue 1.2, February 2014, European Union.

[23]

IS-GPS-200, Revision D, Navstar GPS Space Segment/Navigation User Interfaces, March 7th, 2006.

[24]

IS-GPS-705, Navstar GPS Space Segment/User Segment L5 Interfaces, September 22, 2005.

[25]

IS-GPS-800, Navstar GPS Space Segment/User Segment L1C Interfaces, March 31, 2008.

[26]

Specification for the Wide Area Augmentation System (WAAS), US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001.

[27]

IS-QZSS, Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS, Ver.1.0, June 17, 2008.

[28]

Global Navigation Satellite System GLONASS Interface Control Document, Version 5, 2002.

[29]

TS 45.005: "Radio transmission and reception".

[30]

TS 45.008: "Radio subsystem link control".

[31] Void

[32]

TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling".

[33]

BDS-SIS-ICD-2.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal (Version 2.0)", December 2013.

3 Definitions and abbreviations p. 11

3.1 Definitions p. 11

For the purposes of the present document, the following terms and definitions apply:

Stand-Alone SMLC (SAS):

logical node that interconnects to the RNC over the Iupc interface via the PCAP protocol.

An SAS performs the following procedures:

provide GNSS (i.e. GPS or GANSS (e.g. Galileo)) related data to the RNC;
performs the position calculation function based upon UE Positioning measurement data;
in SAS centric mode, selects the positioning method and controls the positioning procedure.

Elementary Procedure:

PCAP consists of Elementary Procedures (EPs).

An Elementary Procedure is a unit of interaction between the RNC and the SAS. An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used:

Class 1: Elementary Procedures with response (success or failure).
Class 2: Elementary Procedures without response.

For Class 1 EPs, the types of responses can be as follows:

Successful:

A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response.

Unsuccessful:

A signalling message explicitly indicates that the EP failed.

Class 2 EPs are considered always successful.

Information Exchange Context:

Information Exchange Context is created by the first Information Exchange Initiation Procedure initiated by the RNC and requested from the SAS.

The Information Exchange Context is deleted after the Information Exchange Termination or the Information Exchange Failure procedure when there is no more Information Exchange to be provided by the RNC to the SAS. The Information Exchange Context is identified by an SCCP connection as, for Information Exchanges, only the connection oriented mode of the signalling bearer is used.

Positioning Initiation Context:

In the SAS centric mode of operation each positioning request is assigned a unique logical connection identity, i.e., SCCP Source and Destination Local Reference numbers.

RNC Centric Mode of Operation:

The RNC determines, initiates and controls the positioning method to be used for each positioning request.

SAS Centric Mode of Operation:

The SAS determines, initiates and controls the positioning method to be used for each positioning request.

Positioning Event:

The activity associated with the positioning of a UE resulting from the reception of UE positioning request from the CN.

3.2 Abbreviations p. 12

For the purposes of the present document, the following abbreviations apply:

A-GANSS

Assisted GANSS

A-GPS

Assisted GPS

ASN.1

Abstract Syntax Notation One

BDS

BeiDou Navigation Satellite System

Core Network

CRNC

Controlling RNC

DBDS

Differential BDS

DGANSS

Differential GANSS

DGPS

Differential GPS

ECEF

Earth-Centered, Earth-Fixed

EGNOS

European Geostationary Navigation Overlay Service

Elementary Procedure

FDD

Frequency Division Duplex

GAGAN

GPS Aided Geo Augmented Navigation

GANSS

Galileo and Additional Navigation Satellite Systems

GLONASS

GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System)

GNSS

Global Navigation Satellite System

GPS

Global Positioning System

ICD

Interface Control Document

MBS

Metropolitan Beacon System

MSAS

Multi-functional Satellite Augmentation System

OTDOA

Observed Time Difference Of Arrival

PCAP

Positioning Calculation Application Part

PRC

Pseudorange Correction

QZSS

Quasi-Zenith Satellite System

RNC

Radio Network Controller

RNS

Radio Network Subsystem

RRC

Radio Resource Control

SAS

Stand-Alone SMLC

SBAS

Satellite Based Augmentation System

SCCP

Signalling Connection Control Part

SIB

System Information Block

SMLC

Serving Mobile Location Center

SRNC

Serving RNC

Space Vehicle

TDD

Time Division Duplex

TOD

Time of Day

TOW

Time of Week

User Equipment

UTC

Universal Coordinated Time

U-TDOA

Uplink Time Difference Of Arrival

UTRAN

Universal Terrestrial Radio Access Network

WAAS

Wide Area Augmentation System

WLAN

Wireless Local Area Network

4 General p. 13

4.1 Procedure Specification Principles p. 13

The principle for specifying the procedure logic is to specify the functional behaviour of the SAS exactly and completely. The RNC functional behaviour is left unspecified.

The following specification principles have been applied for the procedure text in clause 8:

The procedure text discriminates between:
1. Functionality which "shall" be executed:
  - The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value.
2. Functionality which "shall, if supported" be executed:
  - The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality.
Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included.

4.2 Forwards and Backwards Compatibility p. 13

The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include Id and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version.

4.3 Specification Notations p. 13

For the purposes of the present document, the following notations apply:

[FDD]

This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD.

[TDD]

This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD.

[3.84Mcps TDD]

This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD.

[1.28Mcps TDD]

This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD.

[7.68Mcps TDD]

This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD.

[FDD - …]

This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs.

[TDD - …]

This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD, including 7.68 Mcps TDD, 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs.

[3.84Mcps TDD - …]

This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs.

[1.28Mcps TDD - …]

This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs.

[7.68Mcps TDD - …]

This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs.

Procedure

When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Position Calculation procedure.

Message

When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. POSITION CALCULATION REQUEST message.

When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. Request Type IE.

Value of an IE

When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in clause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)" or "Geographical Coordinates ".

5 PCAP Services p. 14

PCAP provides the signalling services between RNC and SAS that are required to fulfill the PCAP functions described in clause 7. PCAP services are categorized as follows:

Position Calculation Service: They are related to a single UE and involve the transfer of UE Positioning measurement data and UE position estimate data over the Iupc interface between the SRNC and the SAS. They utilise connectionless signalling transport provided by the Iupc signalling bearer.
Information Exchange Service: They involve the transfer of GPS or GANSS related data over the Iupc interface between the RNC and the SAS on demand, on modification, or at regular intervals. They utilise connection-oriented signalling transport provided by the Iupc signalling bearer.
SAS Centric Position Service: They are related to the capability of the SAS to determine the positioning method used for individual positioning events. In this case the SRNC may allow A-GPS, A-GANSS, OTDOA, Cell ID and U-TDOA positioning events for a single UE to be originated by the SAS via PCAP messages. They utilise connection-oriented signalling transport provided by the Iupc signalling bearer.

6 Services Expected from Signalling Transport p. 15

Signalling transport (TS 25.452) shall provide the following service for the PCAP.

Connection oriented data transfer service. This service is supported by a signalling connection between the RNC and the SAS. It shall be possible to dynamically establish and release signalling connections based on the need. Each point-to-point operation shall have its own signalling connection. The signalling connection shall provide in sequence delivery of PCAP messages. PCAP shall be notified if the signalling connection breaks.
Connectionless data transfer service. PCAP shall be notified in case a PCAP message did not reach the intended peer PCAP entity.