Content for TS 23.002 Word version: 18.0.0

0… 3… 4… 4.2… 4a… 5… 5.5… 5.11… 5.17… 6… 6a… 6a.7… 6a.9… 6a.13… 6a.16… 7… A…

6a.1 GCR-specific interface 6a.3 LCS-specific interfaces 6a.4 CAMEL-specific interfaces 6a.5 CBS-specific interfaces 6a.6 Number portability specific interfaces
...

6a PLMN specific interfaces p. 90

6a.1 GCR-specific interface p. 90

6a.1.1 Interface between the MSC and its associated GCR (I-interface) p. 90

The GCR is the management data base for the voice group or broadcast calls in the area controlled by the associated MSC(s). Whenever the MSC needs data related to a requested voice group or broadcast call it interrogates the GCR to obtain the respective voice group or broadcast call attributes. The protocol used to transfer the data over this interface is not standardized.

6a.2 Void

6a.3 LCS-specific interfaces p. 90

6a.3.1 LCS interfaces using MAP p. 90

The following interfaces are based on MAP in LCS.

Lh interface: interface between GMLC and HLR. This interface is used by the GMLC to request the address of the visited MSC or SGSN for a particular target UE whose location has been requested (see TS 29.002).
Lg interface: interface between GMLC - MSC and GMLC - SGSN. This interface is used by the GMLC to convey a location request to the MSC or SGSN currently serving a particular target UE whose location was requested. The interface is used by the MSC or SGSN to return location results to the GMLC (see TS 29.002).
Lc interface: between GMLC and gsmSCF, CAMEL. This interface is used to get location information for CAMEL based services. (see TS 29.002).

6a.3.2 Void

6a.3.3 Void

6a.3.4 Void

6a.3.5 Interface between BSC and SMLC (Lb-interface) |R4| p. 90

In GERAN, a SMLC supports positioning via signalling on the Lb interface to the BSC serving the target MS.

Signalling on this interface uses BSSAP-LE, which is specified in TS 49.031

In UTRAN, the Lb interface is not standardized, the SMLC functionality is included in SRNC.

6a.3.6 Interface between Peer SMLCs (Lp-interface) p. 90

In GERAN, a SMLC may support the Lp interface to enable access to information and resources owned by another SMLC.

Signalling on this interface uses BSSAPP-LE, which is defined in TS 49.031, and SMLCPP, which is specified in TS 48.031.

In UTRAN, the SMLC functionality is included in SRNC and the Iur interface shall include the Lp interface type of functionality.

6a.3.7 Interface between BTS and LMU (Um-interface) p. 91

The Um/Uu interface specific to LCS is defined in TS 44.071.

6a.3.8 Interface between GMLC and External LCS Client (Le-interface) |R4| p. 91

The Le interface is used by the external LCS client to retrieve location information from the LCS server. Signalling on this interface may use the OMA Mobile Location Protocol (MLP) [62] and Open Service Access Application Programming Interface (OSA-API), TS 29.198.

6a.3.9 Interface between RNS and Stand-Alone LMU, UE (Uu-interface) |R5| p. 91

The Uu interface is used to communicate among the UE Positioning entities associated with the SRNC, the UEs and the stand-alone LMU. The Uu interface may pass measurement requests and results to and from the UE or the stand-alone LMU. UE Positioning operations at the Uu interface are generally defined in the 24- and 25-series of 3GPP Technical Specifications. Furthermore, TS 25.305 describes how a stand-alone LMU may be distinguished from a normal UE.

6a.3.10 Interface between SRNC and SAS (Stand-Alone SMLC) (Iupc-interface) |R5| p. 91

The Iupc interface defined for LCS is specified in TS 25.453.

6a.3.11 Interface between GMLC and GMLC (Lr-interface) |R6| p. 91

The Lr interface is used by the GMLC to communicate with other GMLCs. Signalling on this interface may use the OMA Roaming Location Protocol (RLP) [69].

6a.3.12 Interface between GMLC and MME (SLg-interface) |R9| p. 91

The SLg interface is used by the GMLC to communicate with MMEs. The SLg interface is defined in TS 29.172.

6a.3.13 Interface between MME and E-SMLC (SLs-interface) |R9| p. 91

The SLs interface is used to convey LCS messages between the MME and E-SMLC. It is also used for tunnelling positioning protocol messages between the E-SMLC and either E-UTRAN or UE which are transparent to the MME as described in TS 36.305. The SLs interface is defined in TS 29.171.

6a.3.14 Interface between GMLC and HSS (SLh-interface) |R9| p. 91

SLh interface between GMLC and HSS. This interface is used by the GMLC to request the address of the visited MME for a particular target UE whose location has been requested. The SLh interface is defined in TS 29.173.

6a.3.15 Interface between GMLC and SGSN (Lgd-interface) |R12| p. 91

Lgd is the interface that is used by the GMLC to convey a location request to the SGSN currently serving a particular target UE whose location was requested. The interface is also used by the SGSN to return location results to the GMLC. This interface is applicable only for an SGSN supporting EPS based interfaces and protocols. The Lgd interface is defined in TS 29.172.

6a.4 CAMEL-specific interfaces p. 92

The CAMEL-specific interfaces are detailed in TS 23.078. These interfaces are.

6a.4.1 GMSC - gsmSSF interface p. 92

This is an internal interface. The interface is described in the specification to make it easier to understand the handling of Detection Points (arming/disarming of DPs, DP processing etc.).

6a.4.2 gsmSSF - gsmSCF interface p. 92

This interface is used by the gsmSCF to control a call in a certain gsmSSF and to request the gsmSSF to establish a connection with a gsmSRF. Relationships on this interface are opened as a result of the gsmSSF sending a request for instructions to the gsmSCF.

6a.4.3 MSC - gsmSSF interface p. 92

This is an internal interface. The interface is described in the specification to make it easier to understand the handling of DPs (arming/disarming of DPs, DP processing etc.).

6a.4.4 gsmSCF - HLR interface p. 92

This interface is used by the gsmSCF to request information from the HLR. As a network operator option the HLR may refuse to provide the information requested by the gsmSCF.

This interface is also used for USSD operations, both for gsmSCF-initiated dialogues and MS-initiated dialogues (relayed via HLR). It is a network operator option whether to support or not USSD operations on this interface.

6a.4.5 gsmSCF - gsmSRF interface p. 92

This interface is used by the gsmSCF to instruct the gsmSRF to play tones/announcements to the users.

6a.4.6 MSC - gsmSCF interface p. 92

This interface is used by the MSC to send supplementary service invocation notifications to the gsmSCF.

6a.4.7 SGSN - gprsSSF interface p. 92

This is an internal interface. The interface is described in the specification to make it easier to understand the handling of DPs (arming/disarming of DPs, DP processing etc.).

6a.4.8 gprsSSF - gsmSCF interface (Ge Reference Point) p. 92

This interface is used by the gsmSCF to control a GPRS session or individual PDP Context in a certain gprsSSF. Relationships between the gprsSSF and the gsmSCF (GPRS dialogues) on this interface are opened as a result of the gprsSSF sending a request for instructions to the gsmSCF. This interface is also known as Ge reference point (see TS 23.060).

6a.5 CBS-specific interfaces p. 92

6a.5.1 Interface between the CBC and RNS (Iu_BC Interface) p. 92

The interface between the CBC and the RNS is specified in the 25.41x-series of Technical Specifications.

The CBC-RNS interface is used to carry information concerning:

the CBS messages itself; and
CBS delivery parameter.

6a.5.2 Interface between the CBC and MME (SBc Interface) |R8| p. 93

Reference point between CBC and MME for warning message delivery and control functions. This interface is specified in TS 29.168.

6a.5.3 Interface between the CBC and BSC |R9| p. 93

The interface between the CBC and the BSC is specified in TS 48.049.

The CBC-BSC interface is used to carry information concerning:

the CBS message and the warning message itself; and
CBS message and warning message delivery parameters.

6a.6 Number portability specific interfaces p. 93

6a.6.1 IN-based solution p. 93

6a.6.1.1 NPDB to MSC interface p. 93

Upon receiving an ISUP IAM, the (gateway or visited) MSC send a database query to the NPDB as a result of analysis of the received MSISDN. The MSISDN is included in the query to the NPDB. The NPDB determines whether the MSISDN is ported or not. If not, it responds back to the MSC to continue the normal call setup procedure for MT calls (optionally providing the Routing Number). If it is ported, the NPDB responds back to the MSC with a Routing Number pointing out the Subscription network.

6a.6.2 Signalling Relay-based solution p. 93

6a.6.2.1 GMSC to MNP-SRF interface p. 93

Upon receiving an ISUP IAM, the gateway MSC sends a routing interrogation to the MNP-SRF, which in turn will perform one of the actions, described in clause 4a.7, depending on the portability status of the subscriber and the network configuration (see TS 23.066).

6a.6.2.2 MNP-SRF to HLR interface p. 93

When the MNP-SRF receives a routing interrogation from the GMSC or an interrogating network entity (non/call related signalling), and it determines that the subscriber is not ported or it has been ported from another network, the MNP-SRF relays the message to the HLR.