Name

AVP Code

Data Type

Vendor

Accuracy-Fulfilment-Indicator

2513

Enumerated

3GPP

Used in the SLg interface to indicate whether the requested location accuracy has been met when providing location information. This AVP is typically included in location-related Diameter messages exchanged between a Gateway Mobile Location Centre (GMLC) and the Mobile Switching Center (MSC), Serving GPRS Support Node (SGSN), or Mobility Management Entity (MME).

Enumerated Values:

0: REQUESTED_ACCURACY_FULFILLED: Indicates that the requested location accuracy has been met.

1: REQUESTED_ACCURACY_NOT_FULFILLED: Indicates that the requested location accuracy could not be met.

Additional-Area

2565

Grouped

3GPP

Used in the SLg interface to provide additional area-related information for location-based services. It is primarily used in Provide Location Request (PLR) and Provide Location Answer (PLA) messages exchanged between the Gateway Mobile Location Centre (GMLC) and network nodes (MME, MSC, SGSN) in location-based services (LBS). 

The AVP structure is defined as follows:

Area-Type (Mandatory): Specifies the type of area being identified (e.g., Cell ID, Location Area, Tracking Area, Routing Area, Geographical Coordinates).

Area-Identification (Mandatory): Identifies the specific area related to the Area-Type.

Allows additional optional AVPs to be included.

Age-Of-Location-Estimate

2514

Unsigned32

3GPP

Used in the SLg interface to indicate how long ago the provided location estimate was obtained. The value is expressed in minutes and represents the time elapsed since the last known location was recorded according with 3GPP [TS 29.002].

AMF-Instance-Id

2566

UTF8String

3GPP

Used in the SLg interface to uniquely identify an Access and Mobility Management Function (AMF) instance in a 5G Core (5GC) network. This AVP contains the AMF Instance ID, encoded as an NfInstanceId, in accordance with 3GPP [TS 29.571], clause 5.3.2-1.

Area

2535

Grouped

3GPP

Used in the SLg interface to specify a geographical or network-defined area in location-based services (LBS). This AVP provides information about a specific location area, routing area, tracking area, or cell-based location. It is included in location service messages exchanged between the Gateway Mobile Location Centre (GMLC) and other network nodes, such as the MME, MSC, and SGSN.

The AVP structure is defined as follows:

Area-Type (Mandatory): Specifies the type of area being identified. 

Area-Identification (Mandatory): Provides the identifier of the specific area related to the Area-Type. 

Allows additional optional AVPs to be included.

Area-Definition

2534

Grouped

3GPP

Used in the SLg interface to specify one or more geographical or network-defined areas relevant to a location-based service (LBS) request. It allows the definition of multiple primary and additional areas that should be considered when determining the location of a User Equipment (UE). This AVP is primarily included in location-related Diameter messages such as Provide Location Request (PLR) and Provide Location Answer (PLA) exchanged between the Gateway Mobile Location Centre (GMLC) and network nodes like MME, MSC, and SGSN.

The AVP structure is defined as follows:

Area (Mandatory, 1 to 10 occurrences): Specifies the primary areas relevant to the location service request. 

Additional-Area (Optional, up to 240 occurrences): Specifies additional secondary areas that may be relevant to the location request. Not included in Packet-Switched Mobile Terminating Location Requests (PS-MT-LR) over the Lgd interface.

Allows additional optional AVPs to be included.

Area-Event-Info

2533

Grouped

3GPP

Used in the SLg interface to define the conditions for area-based event reporting in location-based services (LBS). This AVP provides configuration parameters that determine how and when a User Equipment (UE) location is reported based on area-based triggers.

It is used in Diameter messages exchanged between the Gateway Mobile Location Centre (GMLC) and network nodes such as the MME, MSC, and SGSN to support location tracking, geofencing, and periodic reporting.

The AVP structure is defined as follows:

Area-Definition (Mandatory): Specifies one or more areas where location events should be monitored. 

Occurrence-Info (Optional): Specifies whether the event should be reported once or multiple times. If omitted, the default value is ONE_TIME_EVENT (0).

Interval-Time (Optional, applicable for MULTIPLE_TIME_EVENT): Defines the interval (in seconds) between event reports when MULTIPLE_TIME_EVENT is selected.

Default value: 1 second if omitted.

Maximum-Interval (Optional, applicable for MULTIPLE_TIME_EVENT): Specifies the maximum allowable interval for reporting location updates. If omitted, the maximum value is assumed.

Sampling-Interval (Optional): Defines the frequency at which location data should be sampled. If omitted, the maximum value is assumed.

Reporting-Duration (Optional): Specifies how long the location reporting should continue.

If omitted, the maximum value is assumed.

Reporting-Location-Requirements (Optional): Defines specific requirements for location reporting in the event of area-based triggers.

Allows additional optional AVPs to be included.

Area-Identification

2537

OctetString

3GPP

Used in the SLg interface to specify the identification of a geographical or network-defined area applicable for area-based deferred location reporting. The coding format of this AVP depends on the Area-Type and follows standard encoding rules specified in 3GPP [TS 29.002] and 3GPP [TS 24.080].

This AVP is included in location-based services (LBS) messages exchanged between the Gateway Mobile Location Centre (GMLC) and network nodes such as MME, MSC, and SGSN to support area-based triggers, geofencing, and tracking.

Encoding Based on Area-Type:

Area-Type 0 to 5: Coded as per 3GPP [TS 29.002], describing Location Areas, Routing Areas, and Cell IDs.

Area-Type 6: Represents Tracking Area Identity (TAI) as defined in 3GPP [TS 24.080].

Area-Type 7: Represents E-UTRAN Cell Global Identifier (ECGI) as defined in 3GPP [TS 24.080].

Deferred EPC-MT-LR (Evolved Packet Core Mobile Terminating Location Request):

Only Area-Type 6 (TAI) and Area-Type 7 (ECGI) are applicable.

Area-Type

2536

Unsigned32

3GPP

Used in the SLg interface to specify the type of area identifier associated with a location-based request or event. This AVP is primarily used in Provide Location Request (PLR) and Provide Location Answer (PLA) messages exchanged between the Gateway Mobile Location Centre (GMLC) and network nodes such as MME, MSC, and SGSN for area-based mobility management.

Enumerated Values:

0: Country Code: Identifies the country in which the UE is located.

1: PLMN ID: Specifies the Public Land Mobile Network (PLMN) identifier.

2: Location Area ID: Represents the Location Area Identity (LAI), which groups a set of cells in GSM/UMTS networks.

3: Routing Area ID: Defines the Routing Area Identity (RAI), used for packet-switched mobility management in GPRS/UMTS networks.

4: Cell Global ID: Specifies the Cell Global Identity (CGI), which uniquely identifies a cell within a mobile network.

5: UTRAN Cell ID: Identifies a UTRAN (3G) cell using the UTRAN Cell Identity (UCI).

6: Tracking Area ID: Represents the Tracking Area Identity (TAI) used in LTE/5G networks for mobility tracking.

7: E-UTRAN Cell Global ID: Specifies the Evolved-UTRAN Cell Global Identity (ECGI) used in LTE/5G networks for uniquely identifying a cell.

Barometric-Pressure

2557

Unsigned32

3GPP

Used in the SLg interface to provide barometric pressure measurements associated with a location-based service (LBS) request or report. This AVP carries the Barometric Pressure Information Element as defined in 3GPP [TS 29.171].

Cell-Portion-ID

2553

Unsigned32

3GPP

Used in the SLg interface to indicate the specific portion of a cell where the User Equipment (UE) is currently located. This AVP contains the value of the "Cell Portion ID" Information Element as defined in 3GPP [TS 29.171].

Civic-Address

2556

UTF8String

3GPP

Used in the SLg interface to provide a human-readable geographic location of a User Equipment (UE). This AVP contains an XML-formatted document that follows the Civic Address Information Element as defined in 3GPP [TS 29.171].

Deferred-Location-Type

2532

Unsigned32 (Bitmask)

3GPP

Used in the SLg interface to specify the types of events that trigger a deferred location estimation request for a User Equipment (UE). Each bit in the bitmask represents a specific type of location-based event, indicating the conditions under which a location report or request should be generated.

This AVP is referenced in 3GPP [TS 23.271], Clause 4.4.2 and is included in Provide Location Request (PLR) and Provide Location Answer (PLA) messages exchanged between the Gateway Mobile Location Centre (GMLC) and network nodes such as MME, MSC, and SGSN for location-based services (LBS).

Bitmask Values:

0: UE-Available: Triggered when the UE establishes contact with the SGSN/MME.

1: Entering-Into-Area: Triggered when the UE enters a pre-defined geographical area.

2: Leaving-From-Area: Triggered when the UE leaves a pre-defined geographical area.

3: Being-Inside-Area: Triggered when the UE is inside a pre-defined geographical area.

4: Periodic-LDR: Triggered when a location report or request is activated after a predefined periodic timer expires in the UE.

5: Motion-Event: Triggered when the UE moves beyond a minimum linear distance (applicable to deferred EPC-MT-LR).

6: LDR-Activated: Triggered when location reporting has been activated in the UE (applicable to deferred EPC-MT-LR).

7: Maximum-Interval-Expiration: Triggered when the maximum reporting interval expires (applicable to deferred EPC-MT-LR).

Deferred-MT-LR-Data

2547

Grouped

3GPP

Used in the SLg interface to store deferred Mobile Terminating Location Request (MT-LR) data. It contains information about the type of deferred location request, potential termination causes, and the serving node where the UE has moved.

This AVP is used in Provide Location Request (PLR) and Provide Location Answer (PLA) messages to support deferred location reporting scenarios, where location determination occurs based on pre-defined triggers instead of immediate queries.

The AVP structure is defined as follows:

Deferred-Location-Type (Mandatory): Specifies the type of deferred location request based on event-driven triggers (e.g., UE motion, entering/exiting an area).

Termination-Cause (Optional): Indicates the reason for terminating a deferred location request. If present and set to MT_LR_RESTART, it means the location request was restarted, requiring the Serving-Node AVP to be included.

Serving-Node (Optional, required when Termination-Cause is MT_LR_RESTART): 

Specifies the new serving node (e.g., MME, MSC, SGSN) where the UE has moved.

Helps continue location tracking after a UE relocation.

Allows additional optional AVPs to be included.

Delayed-Location-Reporting-Data

2555

Grouped

3GPP

Used in the SLg interface to store information about delayed location reporting scenarios. It allows the termination cause and the serving node where the User Equipment (UE) has moved to be recorded when location reporting is deferred.

This AVP is included in Provide Location Request (PLR) and Provide Location Answer (PLA) messages, enabling efficient deferred location tracking for emergency services, lawful interception, and commercial location-based applications.

The AVP structure is defined as follows:

Termination-Cause (Optional): Specifies the reason for terminating a deferred location request. If the cause is MT_LR_RESTART, it indicates that the location request was restarted, requiring the Serving-Node AVP to be included.

Serving-Node (Optional, required when Termination-Cause is MT_LR_RESTART): Identifies the new serving node (e.g., MME, MSC, SGSN) where the UE has moved.

Assists in continuing location tracking after UE relocation.

Allows additional optional AVPs to be included.

ECGI (E-UTRAN Cell Global Identifier)

2517

OctetString

3GPP

Used in the SLg interface to uniquely identify an E-UTRAN cell within an LTE or 5G network. It follows the encoding specified in 3GPP [TS 29.274], Clause 8.21.5.

The ECGI consists of two key components:

PLMN ID (Public Land Mobile Network Identifier): Identifies the mobile network operator.

E-UTRAN Cell ID: Uniquely identifies a cell within the operator's network.

This AVP is included in Provide Location Request (PLR) and Provide Location Answer (PLA) messages to specify the exact LTE/5G cell where a User Equipment (UE) is currently located.

EUTRAN-Positioning-Data

2516

OctetString

3GPP

Used in the SLg interface to contain encoded positioning data obtained from E-UTRAN (LTE) networks. This AVP carries the Positioning-Data Information Element as specified in 3GPP [TS 29.171].

GERAN-GANSS-Positioning-Data

2526

OctetString

3GPP

Used in the SLg interface to contain positioning data from GERAN (GSM/EDGE Radio Access Network) and GANSS (Global Navigation Satellite System). It carries the encoded GANSS Positioning Data as defined in 3GPP [TS 49.031]. Included in Provide Location Request (PLR) and Provide Location Answer (PLA) messages to deliver GERAN and GNSS-based positioning data.

GERAN-Positioning-Data

2525

OctetString

3GPP

Used in the SLg interface to contain positioning data obtained from GERAN (GSM/EDGE Radio Access Network) cells. This AVP carries the encoded Positioning Data Information Element as specified in 3GPP [TS 49.031].

Included in Provide Location Request (PLR) and Provide Location Answer (PLA) messages to deliver GERAN-based positioning data.

GERAN-Positioning-Info

2524

Grouped

3GPP

Used in the SLg interface to provide positioning information derived from GERAN (GSM/EDGE Radio Access Network). It contains details about GERAN-based positioning data and GANSS-assisted GERAN positioning data.

This AVP is included in Provide Location Request (PLR) and Provide Location Answer (PLA) messages to enhance location determination and tracking accuracy.

The AVP structure is defined as follows:

GERAN-Positioning-Data (Optional): Contains the Positioning Data Information Element derived from GERAN-based positioning techniques. 

GERAN-GANSS-Positioning-Data (Optional): Contains Global Navigation Satellite System (GNSS) assisted positioning data for GERAN networks.

Allows additional optional AVPs to be included.

Horizontal-Accuracy

2505

Unsigned32

3GPP

Used in the SLg interface to specify the horizontal location accuracy of a User Equipment (UE) in a location-based service (LBS) request or report. This AVP follows the Uncertainty Code definition from 3GPP [TS 23.032], which indicates the maximum horizontal location error with 67% confidence.

Bits 6-0: Represent the Uncertainty Code, defining the level of accuracy.

Bits 7-31: Shall be ignored.

Interval-Time

2539

Unsigned32

3GPP

Used in the SLg interface to specify the minimum time interval between area reports or motion reports, measured in seconds. This AVP helps regulate location update frequency for deferred or periodic location reporting, ensuring that network-based tracking does not generate excessive signaling.

Value Range:

Minimum Value: 1 second

Maximum Value: 32767 seconds (≈9 hours, 6 minutes)

LCS-Codeword

2511

UTF8String

3GPP

Used in the SLg interface to specify a codeword string that can be sent as a notification message to the User Equipment (UE). The codeword serves as an identifier or confirmation mechanism for Location Services (LCS), allowing the subscriber to recognize and validate the location request.

LCS-EPS-Client-Name

2501

Grouped

3GPP

Used in the SLg interface to specify the name and format of a Location Services (LCS) client requesting the User Equipment (UE) location.

The AVP structure is defined as follows:

LCS-Name-String (Optional): Contains the name of the location services client. Helps identify the entity requesting the location.

LCS-Format-Indicator (Optional): Defines the format of the LCS-Name-String. Encoded as an enumerated value, following 3GPP [TS 32.299].

LCS-Priority

2503

Unsigned32

3GPP

Used in the SLg interface to indicate the priority level of a location request. It defines whether a location request should be processed with higher urgency or normal priority. This AVP follows the priority definition in 3GPP [TS 22.071], which specifies different LCS service classes and priority levels.

Priority Values:

0: Highest priority (emergency or high-urgency location requests).

1: Normal priority (standard location requests).

All other values: Treated as 1 (normal priority).

LCS-Privacy-Check

2512

Enumerated

3GPP

Used in the SLg interface to define privacy control settings for Location Services (LCS). It specifies whether the User Equipment (UE) location request is allowed, requires notification, or should be restricted based on subscriber preferences and regulatory requirements. 

If this AVP is not present, the default value is ALLOWED_WITHOUT_NOTIFICATION (0).

Enumerated Values:

0: ALLOWED_WITHOUT_NOTIFICATION: The location request is permitted without user notification.

1: ALLOWED_WITH_NOTIFICATION: The location request is permitted, but the user is notified.

2: ALLOWED_IF_NO_RESPONSE: The location request is permitted if there is no user response.

3: RESTRICTED_IF_NO_RESPONSE: The location request is restricted unless the user responds.

4: NOT_ALLOWED: The location request is denied.

LCS-Privacy-Check-Non-Session

2521

Grouped

3GPP

Used in the SLg interface to define the privacy handling of location requests for non-session-based location services (LCS).

It contains the LCS-Privacy-Check AVP, which specifies whether a location request should be allowed, restricted, or require user notification.

If this AVP is not present, the default value of LCS-Privacy-Check is ALLOWED_WITHOUT_NOTIFICATION (0).

The AVP structure is defined as follows:

LCS-Privacy-Check (Mandatory): Specifies privacy enforcement for location requests.

LCS-Privacy-Check-Session

2522

Grouped

3GPP

Used in the SLg interface to specify the privacy handling of location requests for session-based location services (LCS). It contains the LCS-Privacy-Check AVP, which defines whether a location request should be permitted, restricted, or require user notification.

If this AVP is not present, the default value of LCS-Privacy-Check is NOT_ALLOWED (4), meaning the session-based location request is denied by default unless explicitly permitted.

The AVP structure is defined as follows:

LCS-Privacy-Check (Mandatory): Specifies the privacy enforcement policy for session-based location requests.

LCS-QoS

2504

Grouped

3GPP

Used in the SLg interface to define the Quality of Service (QoS) requirements for Location Services (LCS). It specifies the expected accuracy, response time, and location measurement parameters for the requested UE location.

This AVP is included in location-based service requests to ensure that location determination meets the required QoS constraints.

The AVP structure is defined as follows:

LCS-QoS-Class (Optional): Defines the class of QoS required for the location request.

Horizontal-Accuracy (Optional): Specifies the expected accuracy of horizontal location.

Vertical-Accuracy (Optional): Defines the expected vertical accuracy (e.g., altitude-based positioning).

Vertical-Requested (Optional): Indicates if vertical location information (altitude) is required.

Response-Time (Optional): Specifies the maximum time allowed for obtaining location information.

LCS-QoS-Class

2523

Enumerated

3GPP

Used in the SLg interface to define the Quality of Service (QoS) class for Location Services (LCS). It specifies whether the requested location information should be obtained with strict accuracy requirements or if a best-effort approach is acceptable. This AVP ensures that location-based services (LBS) requests align with network capabilities and service-level expectations.

Enumerated Values:

0: ASSURED: The location request must meet the specified accuracy constraints.

1: BEST EFFORT: The location request should be processed with available accuracy, but no strict guarantees are enforced.

LCS-Reference-Number

2531

OctetString

3GPP

Used in the SLg interface to provide a unique reference identifier for a deferred location request. The LCS-Reference-Number AVP is of type OctetString of length 1.

LCS-Requestor-Name

2502

Grouped

3GPP

Used in the SLg interface to specify the identity and format of the entity requesting location-based services (LBS).

The AVP structure is defined as follows:

LCS-Requestor-Id-String (Optional): Contains the name or identifier of the requesting entity. 

LCS-Format-Indicator (Optional): Defines the format of the LCS-Requestor-Id-String.

Encoded following 3GPP [TS 32.299].

LCS-Service-Type-ID

2520

Unsigned32

3GPP

Used in the SLg interface to define the service type identifier associated with Location Services (LCS). It specifies the allowed service type for which an LCS client is authorized to request location data for a User Equipment (UE).

Linear-Distance

2560

Unsigned32

3GPP

Used in the SLg interface to specify the minimum straight-line distance (in meters) that a User Equipment (UE) must move before triggering a motion event report. This AVP is applicable only in deferred EPC-MT-LR (Evolved Packet Core - Mobile Terminating Location Request) scenarios, where location updates are provided asynchronously based on motion events rather than immediate requests.

Constraints:

Minimum Value: 1 meter

Maximum Value: 10,000 meters

Location-Event

2518

Enumerated

3GPP

Used in the SLg interface to specify the triggering event for a location request or update. It defines various scenarios under which a location request or report is initiated, ensuring proper handling of location-based services (LBS). This AVP is used to categorize location events related to emergency calls, deferred location requests, handovers, and periodic location reporting.

Enumerated Values:

0: EMERGENCY_CALL_ORIGINATION: Location request triggered by an emergency call initiation.

1: EMERGENCY_CALL_RELEASE: Location request triggered by the release of an emergency call.

2: MO_LR: Mobile-Originated Location Request initiated by the UE.

3: EMERGENCY_CALL_HANDOVER: Location request triggered by an emergency call handover.

4: DEFERRED_MT_LR_RESPONSE: Response to a deferred Mobile-Terminating Location Request (MT-LR).

5: DEFERRED_MO_LR_TTTP_INITIATION: Deferred Mobile-Originated Location Request (MO-LR) for TTTP initiation.

6: DELAYED_LOCATION_REPORTING: Location estimate for a UE that was temporarily unreachable.

7: HANDOVER_TO_5GC: Location event triggered by a handover to a 5G Core network (5GC).

LRA-Flags

2549

Unsigned32 (Bitmask)

3GPP

Contains a bit mask indicating specific location request attributes when using the Lgd interface. It is primarily used to define whether the MO-LR Short Circuit feature is utilized for obtaining location estimates. This AVP allows Granularity in LCS operations, ensuring that location determination methods are clearly defined.

Bitmask Definitions:

0: MO-LR-ShortCircuit-Indicator: Indicates that the MO-LR short circuit feature is used for obtaining the location estimate. This is applicable only when the message is sent over the Lgd interface.

Note: Bits not defined must be cleared by the sending GMLC and discarded by the receiving MME or SGSN.

LRR-Flags

2530

Unsigned32 (Bitmask)

3GPP

Contains a bit mask used in Location Report Request (LRR) messages over the SLg and Lgd interfaces. It specifies various location reporting attributes, including the interface type and the use of the MO-LR short circuit feature.

Bitmask Definitions:

0: Lgd/SLg-Indicator: (Set): The Location Report Request (LRR) message is sent on the Lgd interface (UE is attached via UTRAN/GERAN).

Cleared: The message is sent on the SLg interface (UE is attached via E-UTRAN).

1: MO-LR-ShortCircuit-Indicator: (Set): The MO-LR short circuit feature is used by the UE for location estimation in a deferred MT-LR procedure. Applicable only when sent over the Lgd interface.

2: MO-LR-ShortCircuit-Requested: (Set): The UE requests the MO-LR short circuit feature for location estimation. Used in periodic MO-LR TTTP procedures initiated by the UE over the Lgd interface.

Note: Bits not defined in this table must be cleared by the sending MME or SGSN and discarded by the receiving GMLC.

Maximum-Interval

2561

Unsigned32

3GPP

Used in SLg interface messages to specify the maximum allowed time interval (in seconds) between consecutive event reports in deferred EPC-MT-LR (Evolved Packet Core - Mobile Terminating Location Request) procedures.

Minimum Value: 1 second

Maximum Value: 86,400 seconds (24 hours)

Motion-Event-Info

2559

Grouped

3GPP

Specifies motion-related event reporting parameters for deferred EPC-MT-LR (Evolved Packet Core - Mobile Terminating Location Request) procedures.

The AVP structure is defined as follows:

Linear-Distance (Mandatory, Unsigned32): Defines the minimum straight-line distance (in meters) the UE must move before triggering a motion event.

Occurrence-Info (Optional, Enumerated): Indicates whether the motion event should be reported once (ONE_TIME_EVENT) or multiple times (MULTIPLE_TIME_EVENT).

Interval-Time (Optional, Unsigned32): Specifies the minimum interval (in seconds) between motion event reports. Only applicable when Occurrence-Info is MULTIPLE_TIME_EVENT.

Maximum-Interval (Optional, Unsigned32): Specifies the maximum interval (in seconds) between consecutive event reports. If omitted, the default value is the maximum allowed time.

Sampling-Interval (Optional, Unsigned32): Defines how frequently the network samples the UE's motion status. Default is the maximum allowed value if omitted.

Reporting-Duration (Optional, Unsigned32): Specifies how long motion event reporting should be active. Default is the maximum value if omitted.

Reporting-Location-Requirements (Optional, Unsigned32): Defines location reporting conditions based on network and regulatory policies.

Default Behavior:

If Occurrence-Info is not included, it defaults to ONE_TIME_EVENT (0).

If Interval-Time and Maximum-Interval are not included, the system defaults to Interval-Time = 1 second and Maximum-Interval = maximum allowed value.

If Sampling-Interval and Reporting-Duration are not included, they are set to their maximum allowable values.

Occurrence-Info

2538

Enumerated

3GPP

Specifies the event occurrence type for location reporting in deferred EPC-MT-LR (Mobile Terminating Location Request) and motion-based tracking scenarios. 

Enumerated Values:

0: ONE_TIME_EVENT: The event is reported only once upon meeting the trigger conditions (e.g., entering a specific area, motion detection).

1: MULTIPLE_TIME_EVENT: The event is reported multiple times whenever the trigger conditions are met, following configured interval and maximum duration settings.

1xRTT-RCID

2554

OctetString

3GPP (3GPP2)

Represents the 1xRTT Reference Cell Identifier (RCID). It consists of a Cell Identification Discriminator and a Cell Identification, formatted according to the Cell Identifier element as defined in 3GPP2 [A.S0014-D] (4.2.17). This AVP is used in location-based services (LBS) and radio network positioning to uniquely identify the serving cell in a 1xRTT (CDMA2000) network.

Encoding Format:

The 1xRTT-RCID field is extracted from octets 3 through the end of the Cell Identifier element.

The allowable cell identification discriminator values are:

0000 0010 (Binary) - (0x02 in hex) indicates a “Cell Identity (CI)” format​. It means the cell is being identified by a specific Cell ID value only, typically local to an MSC.

0000 0111 (Binary) - (0x07 in hex) represents “IS-41 Whole Cell Global Identification (ICGI)”​. It indicates that the cell identifier is a global one, including not just the cell’s local ID but also additional information to uniquely identify it across the wider network.

Periodic-LDR-Info

2540

Grouped

3GPP

Specifies parameters for periodic location reporting in the context of deferred location requests (LDR - Location Deferred Reporting). It ensures accurate periodic reporting of user location while maintaining compatibility with OMA MLP (Mobile Location Protocol) and RLP (Roaming Location Protocol).

The AVP structure is defined as follows:

Reporting-Amount (Mandatory, Unsigned32): Defines the number of location reports to be sent before the periodic reporting ends.

Reporting-Interval (Mandatory, Unsigned32): Specifies the time interval (in seconds) between consecutive location reports.

Allows additional optional AVPs to be included.

Reporting-Interval x Reporting-Amount shall not exceed 8639999 (99 days, 23 hours, 59 minutes and 59 seconds) for compatibility with OMA MLP and RLP.

Periodic-Location-Support-Indicator

2550

Enumerated

3GPP

Indicates whether the serving PLMN (Public Land Mobile Network), as identified by the Visited-PLMN-ID, supports periodic location reporting services for the User Equipment (UE). This information assists the requesting entity (such as a Gateway Mobile Location Centre or GMLC) in determining whether periodic location requests are supported by the visited network.

Enumerated Values:

PERIODIC_LOCATION_NOT_SUPPORTED (0): Indicates that the visited PLMN does not support periodic location reporting.

PERIODIC_LOCATION_SUPPORTED (1): Indicates that the visited PLMN supports periodic location reporting, allowing the requesting entity to proceed with periodic location requests.

If the AVP is not present, the default interpretation is PERIODIC_LOCATION_NOT_SUPPORTED (0).

PLA-Flags

2553

Unsigned32 (Bitmask)

3GPP

Conveys specific indicators related to deferred Mobile Terminated Location Requests (MT-LR), periodic location reporting, and optimized location procedures. The bits in this AVP represent various attributes and operational conditions in location-based services (LBS), particularly over the Lgd interface.

Bitmask Definitions:

0: Deferred-MT-LR-Response-Indicator: Indicates that the message is a response to a deferred MT-LR request.

1: MO-LR-ShortCircuit-Indicator: Indicates that the MO-LR short circuit feature has been accepted by the UE for periodic location reporting. Only applicable when the message is sent over the Lgd interface.

2: Optimized-LCS-Proc-Performed: Indicates that the combined MME/SGSN has executed an optimized location service (LCS) procedure to retrieve the UE’s location. This bit applies only to MT-LR procedures over the Lgd interface.

3: UE-Transiently-Not-Reachable-Indicator: Indicates that the UE is temporarily unreachable due to power-saving mechanisms such as extended idle mode DRX or Power Saving Mode. In this case, the location information will be provided later in a Subscriber Location Report when the UE becomes available.

NOTE: Bits not defined in this table shall be cleared by the sending MME or SGSN and discarded by the receiving GMLC.

PLMN-ID-List

2544

Grouped

3GPP

Used to identify a list of Public Land Mobile Networks (PLMNs) visited by the User Equipment (UE). It contains a Visited-PLMN-Id AVP, with an optional Periodic-Location-Support-Indicator AVP indicating whether periodic location reporting is supported in the given PLMN.

The AVP structure is defined as follows:

Visited-PLMN-Id (Mandatory, OctetString): Indicates the PLMN Identifier of the visited network.

Periodic-Location-Support-Indicator (Optional, Enumerated): Specifies whether the visited PLMN supports periodic location updates. If absent, it defaults to NOT_SUPPORTED (0).

Allows additional optional AVPs to be included.

PLR-Flags

2545

Unsigned32 (Bitmask)

3GPP

Used in location-based services (LBS) within Diameter SLg interface operations. It defines indicators for specific location request features, including MO-LR short circuit, optimized LCS processing, and delayed location reporting.

Bitmask Definitions:

0: MO-LR-ShortCircuit-Indicator: When set, indicates that the MO-LR short circuit feature is requested for periodic location events. Applicable only for deferred MT-LR procedures over the Lgd interface.

1: Optimized-LCS-Proc-Req: When set, indicates that the GMLC requests optimized LCS procedure for a combined MME/SGSN. Only applicable when GMLC initiates MT-LR over the Lgd interface and when HSS confirms support.

2: Delayed-Location-Reporting-Support-Indicator: When set, indicates that the GMLC supports delayed location reporting for UEs that are transiently not reachable (e.g., extended idle mode DRX, Power Saving Mode). As specified in clauses 9.1.6 and 9.1.15 of 3GPP [TS 23.271].

This enables:

- Receiving PROVIDE SUBSCRIBER LOCATION RESPONSE with UE-Transiently-Not-Reachable-Indicator in PLA-Flags.

- Receiving location updates via a SUBSCRIBER LOCATION REPORT when the UE becomes reachable.

Prioritized-List-Indicator

2551

Enumerated

3GPP

Indicates whether the PLMN-ID-List AVP is provided in a prioritized order or unordered.

Enumerated Values:

0: NOT_PRIORITIZED: The PLMN-ID-List AVP is unordered, meaning no specific priority is assigned to the PLMNs.

1: PRIORITIZED: The PLMN-ID-List AVP is provided in a prioritized order, meaning the first PLMN has the highest priority for selection.

If this AVP is not present, the default behavior is NOT_PRIORITIZED (0).

Pseudonym-Indicator

2519

Enumerated

3GPP

Defines whether a pseudonym is requested for the user identity.

Enumerated Values:

0: PSEUDONYM_NOT_REQUESTED: No pseudonym is requested. The user’s real identity is used.

1: PSEUDONYM_REQUESTED: A pseudonym is requested for identity protection.

If this AVP is not present, the default value is PSEUDONYM_NOT_REQUESTED (0).