LPPe Tab
The LPPe (LTE Positioning Protocol Extensions) tab is used in the AMF Nodal, gNB CU SA Nodal and AMF Node test cases. The AMF Node test case support of LPPe is for testing of the AMF/gNB CU SA Nodal test cases, the AMF Node will provide limited server (LMF) support of LPPe. The LPPe tab is under the LMF tab in AMF Node and the LCS tab in AMF/gNB CU SA Nodal Nodals. It becomes available when LCS Support is enabled in AMF Nodal/AMF Node and gNB CU SA Nodal test cases.
LPPe is simply an extension of LPP. Basically a new information element is added to the LPP messages that requires LPPe support. Existing LPP call/message flows are not modified. When applicable the LPPe extension is added to the LPP message. Received LPP messages will be checked to determine if the LPPe extension was included and if so the extension will be parsed and processed as needed.
For LPPe we will support Capabilities Exchange, Assistance Data Transfer, and Location Information Transfer. On-demand transfer (server sends request for info and client immediately responds) for LPPe will be supported, periodic LPPe transfer is not initially supported. AGNSS and WLAN information is supported, the other types (OTDOA, ECID, EOTD, etc.) are not supported.
Click here for the list of supported the messages and associated information elements. See Limitations section at the bottom of this topic.
Segmented transfer (sections 5.2.3 and 5.2.4 from OMA spec) is not supported.
Only normal LPPe Mode is supported (section 5.3 of OMA spec), reversed mode is not supported.
Spec 3GPP 36.355 and OMA-TS-LPPe-V1_0-20150414-C
Related Measurements
Measurements collected for LPP related processing are reported on the LPP Server Session and LPP Client Session report tab.
|
Select to initiate/trigger LPPe . Available in AMF Nodal and AMF Node Test Cases. Tcl Parameter: LppSrvLppeEn |
|||||||||||||||||||
|
Apply Parameter Values from LPPe Node Test Data Files. The LPPE Node Test Data File is used to configure data that is common across all subscribers. Rather than storing the data with each subscriber a common data structure is allocated and used by all subscribers. This node data is configured in a separate TDF from the per-subscriber data. The node TDF is required in both the AMF Nodal and AMF Node test cases when LPPe is enabled. There are 11 different types of data configurable within the LPPE Node TDF. The 11 types are: Each type is defined in a separate row. The first column header (LPPE Type) is the type and must contain one of the values show above. When applicable multiple rows for the same type are allowed (and in fact expected). Each type is associated with its own set of column headers so that each row should have a limited number of columns with data. The remaining, unused columns for that row should remain blank. If a column has data but that column is not associated with the type being defined, that data will be ignored. There are some dependencies built into the code such that some types must be defined before others and some columns must precede other columns. In general, the column order provided in the sample TDF should be maintained. The software does not enforce or check to ensure items appear in the proper order; it simply assumes order has been maintained. LPPE Type – must be first column of the row, it defines which type of data is being configured in the row. Each of the types (e.g. Vendor ID, Reference Point, etc. ) and their associated columns are listed below. Vendor ID – should be the first things configured since other items (such as containers and reference points) are linked to vendors. Either a Vendor Standard ID (integer) or a Vendor Non-Standard ID (character string) is required but not both. There can be a maximum of 5 vendors configured. Column Headers for LPPE Type Vendor ID:
Reference Point – Ref Point Vendor ID is one of the vendors configured in the Vendor ID row. This field contains a standard format (integer value) or a non-standard format (character string). There can be a maximum of 5 reference points configured for the system (NOT 5 per vendor). Column Headers for LPPE Type Reference Point:
Location Container – Loc Container Vendor ID needs to be the first column followed by Loc Container ID and finally Loc Container Data. Column Headers for LPPE Type Location Container:
Assist Container – Assist Container ID must be first followed by Assist Container Vendor ID. The Assist Container Vendor ID is one of the vendors configured in the Vendor ID row. There can be a maximum of 5 assistance containers configured for the system (NOT 5 per vendor). Column Headers for LPPE Type Assist Container:
GNSS – GNSS must be configured before GNSS Signal and GNSS Signal Elements. Column Headers for LPPE Type GNSS: GNSS Signal – GNSS Signal must be configured before GNSS Signal Element. GNSS Signal ID must be first column followed by GNSS Signal HA and finally Signal GNSS. Signal GNSS is the GNSS ID previously configured in the GNSS row. There can be a maximum of 5 GNSS signals configured for the system (NOT 5 per vendor). Column Headers for LPPE Type GNSS Signal:
GNSS Signal Element - GNSS Sig Element Sig ID must be first column and is a GNSS Signal ID previously configured in a GNSS Signal row. There can be a maximum of 5 GNSS Signal Elements configured per GNSS Signal. Column Headers for LPPE Type GNSS Signal Element:
Fixed Access and Wireless Access are single elements (there is not an array of these) and as such should only have a single row in the TDF file. If multiple rows of either of these elements are defined, then the values used are from the last row of the element. Column Headers for LPPE Type Fixed Access:
Column Headers for LPPE Type Wireless Access:
WLAN – there can be multiple WLAN rows in a TDF file (maximum of 10). There is no WLAN ID and the WLANs are not linked to any other item. Column Headers for LPPE Type WLAN:
GNSS System Time – a single GNSS System Time element can be configured and will be used everywhere GNSS System Time is used in an LPPe message. Column Headers for LPPE Type GNSS System Time:
Tcl Parameter: LppClnLppeNodeCfgFile Tcl Parameter: LppSrvLppeNodeCfgFile See Test Data Files for further explanation and sample files. If a sample is not found for the specific TDF, you can obtain a sample file from your Technical Support representative. You may also use the following options to select an existing TDF or create/edit TDF-CSV files (TDF-CSV Editor). For most TDF Parameters used for Applying Parameters, each row in the file is the overridden value for a different “Session”, aka a different UE. But some TDFs are done in other dimensions, like Bearers, eNodeBs, Subscribers (2 per UE sometimes) or even Hosts, etc. Tooltips on the TDF Parameter:
Note that the “ID” is a unique ID. Please Provide the ID when reporting issues with a TDF. For TDFs that do not apply / override Parameters, but instead are just their own configuration or data or media files you won’t see TDF ID row details.
|
|||||||||||||||||||
| LPPe Session Test Data File |
The LPPe Session TDFs are a more traditional TDF in that each row in the TDF contains data for a single subscriber. There is a session TDF file for the client side (AMF Nodal) and a separate TDF for the server side (AMF Node). LPPe Server Test Data File : The LPPe server TDF is used in the AMF Node test case and drives the behavior of the LPP server with respect to LPPe. There are more than 50 columns in the LPPe server TDF. Fields that allow a TRUE/FALSE entry determine whether or not that item is included or not in the associated message. For example, Capability Req IP is a TRUE/FALSE column where TRUE means request the IP Address capabilities and FALSE means do not request the IP Address capabilities. Columns that are TRUE/FALSE fields are identified below by “T/F” The column headers that begin with “Capability” determine the content of the LPPe Request Capability message. Capability Req Assist - range 0 - 5, 255 [0 = none, 255 all vendors, 1 - 5 index of the single vendor to include] (column B) ; index into the Vendor IDs (configured in the node TDF) Capability Req Ref Point - range 0 - 5, 255 [0 = none, 255 all vendors, 1 - 5 index of the single vendor to include] (column F) ; index into the Vendor IDs (configured in the node TDF) The columns that begin with “Loc” determine the content of the LPPe Request Location message. Loc Req Info Container VendorID - range 0 - 5, 0 = none (column M); index into the Vendor IDs (configured in the node TDF), drives Location Information Container Request element Loc Req Relative Loc Change - range 0 - 5, 0 = not included (column N); number of relative location changes, drives Relative Location Change Request element Loc Req Local Position - range 0 - 5, 255 (column O); index into Reference Points (configured in the node TDF), drives Local Position Request Present, 0 = not included, 255 = all reference points, 1 - 5 index of the single reference point to include Loc Req Pos Type - range 0 - 2, (0=local optional, 1=local mandatory, 2=local only) (column P); value of Type Of Request field in Local Position Request element. Loc Agnss Req HA Duration - range 0 - 63, 0 = not included (column V); Loc Agnss Req HA Rate - range 0 - 63, 0 = not included (column X); value of Rate in Positioning Instructions in Agnss Request Information element The columns that begin with “Provide” determine the content of the LPPe Provide Assistance Data message.
LPPe Client Test Data File The LPPe Client TDF is used in the AMF Nodal test case. Fields that allow a TRUE/FALSE entry determine whether or not that item is included in the associated message. For example, Capability Incl IP is a TRUE/FALSE column where TRUE means include the IP Address Capabilities and FALSE means do not include the IP Address capabilities in the Capability Response. Columns that are TRUE/FALSE fields are identified below by “T/F”. Note that the item will be included in the response only if it has been requested and the associated flag is TRUE. If a flag is false that item will not be included in a response even though it may have been requested in the request message. The column headers that begin with “Capability” determine the content of the LPPe Provide Capability message. Capability Num Changes - range 1 - 5 (column H)
GNSS System Time - NOT CURRENTLY USED // Assist Agnss Ion Duration - range 1 - 63, 15 min increments (column BV)
Tcl Parameter: LppClnLppeSessionCfgFile Tcl Parameter: LppSrvLppeSessionCfgFile |
View TDF Actions/Options Menu)
Limitation/Caveat
The following sections list the messages and associated information elements at a high level. Items in Bold are at least partially, if not fully, supported, the remaining items are not supported. IEs that are not in Bold are not sent by Landslide and ignored if received.
1.0 Capabilities Exchange:
Capabilities Request
typedef struct LPPe_OMA_LPPe_RequestCapabilities {
LPPe_OMA_LPPe_CommonIEsRequestCapabilities
LPPe_OMA_LPPe_AGNSS_RequestCapabilities
LPPe_OMA_LPPe_WLAN_AP_RequestCapabilities
LPPe_OMA_LPPe_OTDOA_RequestCapabilities
LPPe_OMA_LPPe_EOTD_RequestCapabilities
LPPe_OMA_LPPe_OTDOA_UTRA_RequestCapabilities
LPPe_OMA_LPPe_ECID_LTE_RequestCapabilities
LPPe_OMA_LPPe_ECID_GSM_RequestCapabilities
LPPe_OMA_LPPe_ECID_UTRA_RequestCapabilities
LPPe_OMA_LPPe_ECID_WiMax_RequestCapabilities
LPPe_OMA_LPPe_Sensor_RequestCapabilities
LPPe_OMA_LPPe_SRN_RequestCapabilities
} LPPe_OMA_LPPe_RequestCapabilities;
1.1.1 OMA_LPPe_CommonIEsRequestCapabilities
typedef struct LPPe_OMA_LPPe_CommonIEsRequestCapabilities {
LPPe_OMA_LPPe_IP_Address_RequestCapabilities
LPPe_OMA_LPPe_LocationInformationContainerSupportReq
LPPe_OMA_LPPe_AccessCapabilitiesReq
LPPe_OMA_LPPe_AssistanceContainerSupportReq
LPPe_OMA_LPPe_HighAccuracyFormatCapabilitiesReq
LPPe_OMA_LPPe_ReferencePointCapabilitiesReq
LPPe_OMA_LPPe_RelativeLocationChange_RequestCapabilities
LPPe_OMA_LPPe_SegmentedAssistanceData_ReqCapabilities
LPPe_OMA_LPPe_ScheduledLocation_RequestCapabilities
LPPe_OMA_LPPe_SegmentedLocationInformation_ReqCapabilities
} LPPe_OMA_LPPe_CommonIEsRequestCapabilities;
1.1.2 OMA_LPPe_AGNSS_RequestCapabilities
typedef struct LPPe_OMA_LPPe_AGNSS_RequestCapabilities {
assistanceDataSupportListReq;
environmentObservationSupportListReq;
haGNSSsupportReq;
} LPPe_OMA_LPPe_AGNSS_RequestCapabilities;
1.1.3 OMA_LPPe_WLAN_AP_RequestCapabilities
Supported - No parsing, if IE exist in request then response should contain associated data.
2.0 Capabilities Provide
typedef struct LPPe_OMA_LPPe_ProvideCapabilities {
LPPe_OMA_LPPe_CommonIEsProvideCapabilities
LPPe_OMA_LPPe_AGNSS_ProvideCapabilities
LPPe_OMA_LPPe_WLAN_AP_ProvideCapabilities
LPPe_OMA_LPPe_OTDOA_ProvideCapabilities
LPPe_OMA_LPPe_EOTD_ProvideCapabilities
LPPe_OMA_LPPe_OTDOA_UTRA_ProvideCapabilities
LPPe_OMA_LPPe_ECID_LTE_ProvideCapabilities
LPPe_OMA_LPPe_ECID_GSM_ProvideCapabilities
LPPe_OMA_LPPe_ECID_UTRA_ProvideCapabilities
LPPe_OMA_LPPe_ECID_WiMax_ProvideCapabilities
LPPe_OMA_LPPe_Sensor_ProvideCapabilities
LPPe_OMA_LPPe_SRN_ProvideCapabilities
} LPPe_OMA_LPPe_ProvideCapabilities;
2.1.1 OMA_LPPe_CommonIEsProvideCapabilities
typedef struct LPPe_OMA_LPPe_CommonIEsProvideCapabilities {
LPPe_OMA_LPPe_IP_Address_Capabilities
LPPe_OMA_LPPe_AssistanceContainerSupport
LPPe_OMA_LPPe_LocationInformationContainerSupport
LPPe_OMA_LPPe_AccessCapabilities
LPPe_OMA_LPPe_RelativeLocationChange_Capabilities
LPPe_OMA_LPPe_HighAccuracyFormatCapabilities
LPPe_OMA_LPPe_ReferencePointCapabilities
LPPe_OMA_LPPe_SegmentedAssistanceData_ProvideCapabs
LPPe_OMA_LPPe_ScheduledLocation_Capabilities
LPPe_OMA_LPPe_SegmentedLocationInformation_ProvideCapabs
} LPPe_OMA_LPPe_CommonIEsProvideCapabilities;
2.1.2 OMA_LPPe_AGNSS_ProvideCapabilities
typedef struct LPPe_OMA_LPPe_AGNSS_ProvideCapabilities {
LPPe_OMA_LPPe_AGNSS_AssistanceDataSupportList
LPPe_OMA_LPPe_AGNSS_EnvironmentObservationSupportList
LPPe_OMA_LPPe_AGNSS_HAgnssSupport
} LPPe_OMA_LPPe_AGNSS_ProvideCapabilities;
2.1.3 OMA_LPPe_WLAN_AP_ProvideCapabilities
typedef struct LPPe_OMA_LPPe_WLAN_AP_ProvideCapabilities {
wlan_ecid_MeasSupported
LPPe_OMA_LPPe_WLAN_AP_Type_List
LPPe_OMA_LPPe_WLAN_AP_Capability
wlan_ap_ADSupported
additional_wlan_ecid_MeasSupported
} LPPe_OMA_LPPe_WLAN_AP_ProvideCapabilities;
2.0 Location Information Exchange:
2.1 Request Location Information
typedef struct LPPe_OMA_LPPe_RequestLocationInformation {
LPPe_OMA_LPPe_CommonIEsRequestLocationInformation
LPPe_OMA_LPPe_AGNSS_RequestLocationInformation
LPPe_OMA_LPPe_WLAN_AP_RequestLocationInformation
LPPe_OMA_LPPe_OTDOA_RequestLocationInformation
LPPe_OMA_LPPe_EOTD_RequestLocationInformation
LPPe_OMA_LPPe_OTDOA_UTRA_RequestLocationInformation
LPPe_OMA_LPPe_ECID_LTE_RequestLocationInformation
LPPe_OMA_LPPe_ECID_GSM_RequestLocationInformation
LPPe_OMA_LPPe_ECID_UTRA_RequestLocationInformation
LPPe_OMA_LPPe_ECID_WiMax_RequestLocationInformation
LPPe_OMA_LPPe_Sensor_RequestLocationInformation
LPPe_OMA_LPPe_SRN_RequestLocationInformation
} LPPe_OMA_LPPe_RequestLocationInformation
2.1.1. OMA_LPPe_CommonIEsRequestLocationInformation
typedef struct LPPe_OMA_LPPe_CommonIEsRequestLocationInformation {
LPPe_OMA_LPPe_IP_Address_Request
LPPe_OMA_LPPe_AccessTypeRequest
LPPe_OMA_LPPe_LocationInformationContainerRequest
LPPe_OMA_LPPe_RelativeLocationChange_Request
LPPe_OMA_LPPe_LocalPositionRequest
LPPe_OMA_LPPe_RequestPeriodicLocInfoWithUpdate
LPPe_OMA_LPPe_ScheduledLocation_Request
segmentedLIpreference
LPPe_OMA_LPPe_SegmentedLIResume
} LPPe_OMA_LPPe_CommonIEsRequestLocationInformation;
2.1.2 OMA_LPPe_AGNSS_RequestLocationInformation
typedef struct LPPe_OMA_LPPe_AGNSS_RequestLocationInformation {
LPPe_OMA_LPPe_AGNSS_PositioningInstructions
ionosphereMeasurementsReq
LPPe_OMA_LPPe_AGNSS_LocalSurfaceMeasurementReq
} LPPe_OMA_LPPe_AGNSS_RequestLocationInformation;
2.1.3 OMA_LPPe_WLAN_AP_RequestLocationInformation
typedef struct LPPe_OMA_LPPe_WLAN_AP_RequestLocationInformation {
requestedMeasurements
additionalRequestedMeasurements
} LPPe_OMA_LPPe_WLAN_AP_RequestLocationInformation;
2.2 Provide Location Information
typedef struct LPPe_OMA_LPPe_ProvideLocationInformation {
LPPe_OMA_LPPe_CommonIEsProvideLocationInformation
LPPe_OMA_LPPe_AGNSS_ProvideLocationInformation
LPPe_OMA_LPPe_OTDOA_ProvideLocationInformation
LPPe_OMA_LPPe_EOTD_ProvideLocationInformation
LPPe_OMA_LPPe_OTDOA_UTRA_ProvideLocationInformation
LPPe_OMA_LPPe_ECID_LTE_ProvideLocationInformation
LPPe_OMA_LPPe_ECID_GSM_ProvideLocationInformation
LPPe_OMA_LPPe_ECID_UTRA_ProvideLocationInformation
LPPe_OMA_LPPe_WLAN_AP_ProvideLocationInformation
LPPe_OMA_LPPe_ECID_WiMax_ProvideLocationInformation
LPPe_OMA_LPPe_Sensor_ProvideLocationInformation
LPPe_OMA_LPPe_SRN_ProvideLocationInformation
} LPPe_OMA_LPPe_ProvideLocationInformation;
2.2.1 OMA_LPPe_CommonIEsProvideLocationInformation
typedef struct LPPe_OMA_LPPe_CommonIEsProvideLocationInformation {
LPPe_OMA_LPPe_HighAccuracy3Dposition
LPPe_OMA_LPPe_LocalPosition
LPPe_OMA_LPPe_HighAccuracy3Dvelocity
LPPe_OMA_LPPe_IP_Address_List
LPPe_OMA_LPPe_LocationInformationContainer
LPPe_OMA_LPPe_ProvidePeriodicLocInfowithUpdate
LPPe_OMA_LPPe_RelativeLocationChangeList
LPPe_OMA_LPPe_ScheduledLocation
LPPe_OMA_LPPe_AccessTypes
LPPe_OMA_LPPe_SegmentedLITransfer
LPPe_OMA_LPPe_TimeStamp
LPPe_OMA_LPPe_LocationSource
} LPPe_OMA_LPPe_CommonIEsProvideLocationInformation;
2.2.2 OMA_LPPe_AGNSS_ProvideLocationInformation
typedef struct LPPe_OMA_LPPe_AGNSS_ProvideLocationInformation {
LPPe_GNSS_SystemTime
LPPe_OMA_LPPe_AGNSS_HAgnssProvide
LPPe_OMA_LPPe_AGNSS_IonosphereMeasurements
LPPe_OMA_LPPe_AGNSS_LocalSurfaceMeasurements
LPPe_OMA_LPPe_AGNSS_Error
} LPPe_OMA_LPPe_AGNSS_ProvideLocationInformation;
2.2.3 LPPe_OMA_LPPe_WLAN_AP_ProvideLocationInformation
typedef struct LPPe_OMA_LPPe_WLAN_AP_ProvideLocationInformation {
LPPe_OMA_LPPe_WLAN_AP_LocationInformationList
LPPe_OMA_LPPe_WLAN_AP_Error
} LPPe_OMA_LPPe_WLAN_AP_ProvideLocationInformation
3.0 Assistance Data Exchange:
3.1 Request Assistance Data
typedef struct LPPe_OMA_LPPe_RequestAssistanceData {
LPPe_OMA_LPPe_CommonIEsRequestAssistanceData
LPPe_OMA_LPPe_AGNSS_RequestAssistanceData
LPPe_OMA_LPPe_OTDOA_RequestAssistanceData
LPPe_OMA_LPPe_EOTD_RequestAssistanceData
LPPe_OMA_LPPe_OTDOA_UTRA_RequestAssistanceData
LPPe_OMA_LPPe_ECID_LTE_RequestAssistanceData
LPPe_OMA_LPPe_ECID_GSM_RequestAssistanceData
LPPe_OMA_LPPe_ECID_UTRA_RequestAssistanceData
LPPe_OMA_LPPe_WLAN_AP_RequestAssistanceData
LPPe_OMA_LPPe_Sensor_RequestAssistanceData
LPPe_OMA_LPPe_SRN_RequestAssistanceData
} LPPe_OMA_LPPe_RequestAssistanceData
3.1.1 OMA_LPPe_CommonIEsRequestAssistanceData
typedef struct LPPe_OMA_LPPe_CommonIEsRequestAssistanceData {
LPPe_EllipsoidPointWithAltitudeAndUncertaintyEllipsoid
LPPe_OMA_LPPe_AssistanceContainerRequestList
LPPe_OMA_LPPe_RequestPeriodicADwithUpdate
segmentedADpreference
LPPe_OMA_LPPe_SegmentedADResume
LPPe_OMA_LPPe_ReferencePointAssistanceReq
} LPPe_OMA_LPPe_CommonIEsRequestAssistanceData;
3.1.2 OMA_LPPe_AGNSS_RequestAssistanceData
typedef struct LPPe_OMA_LPPe_AGNSS_RequestAssistanceData {
LPPe_OMA_LPPe_AGNSS_CommonAssistanceDataReq
LPPe_OMA_LPPe_AGNSS_GenericAssistanceDataReq
} LPPe_OMA_LPPe_AGNSS_RequestAssistanceData
3.1.3 LPPe_OMA_LPPe_WLAN_AP_RequestAssistanceData
typedef struct LPPe_OMA_LPPe_WLAN_AP_RequestAssistanceData {
requestedAD
LPPe_OMA_LPPe_WLAN_AP_Type_List
} LPPe_OMA_LPPe_WLAN_AP_RequestAssistanceData;
3.2 Provide Assistance Data
typedef struct LPPe_OMA_LPPe_ProvideAssistanceData {
LPPe_OMA_LPPe_CommonIEsProvideAssistanceData
LPPe_OMA_LPPe_AGNSS_ProvideAssistanceData
LPPe_OMA_LPPe_OTDOA_ProvideAssistanceData
LPPe_OMA_LPPe_EOTD_ProvideAssistanceData
LPPe_OMA_LPPe_ECID_UTRA_ProvideAssistanceData
LPPe_OMA_LPPe_WLAN_AP_ProvideAssistanceData
LPPe_OMA_LPPe_Sensor_ProvideAssistanceData
LPPe_OMA_LPPe_SRN_ProvideAssistanceData
} LPPe_OMA_LPPe_ProvideAssistanceData
3.2.1 OMA_LPPe_CommonIEsProvideAssistanceData
typedef struct LPPe_OMA_LPPe_CommonIEsProvideAssistanceData {
LPPe_OMA_LPPe_AssistanceContainerProvideList
LPPe_OMA_LPPe_ProvidePeriodicADwithUpdate
LPPe_OMA_LPPe_SegmentedADTransfer
LPPe_OMA_LPPe_ReferencePoint
} LPPe_OMA_LPPe_CommonIEsProvideAssistanceData
3.2.2 OMA_LPPe_AGNSS_ProvideAssistanceData
typedef struct LPPe_OMA_LPPe_AGNSS_ProvideAssistanceData {
LPPe_OMA_LPPe_AGNSS_CommonAssistData
LPPe_OMA_LPPe_AGNSS_GenericAssistData
LPPe_OMA_LPPe_AGNSS_Error
} LPPe_OMA_LPPe_AGNSS_ProvideAssistanceData;
3.2.3 OMA_LPPe_WLAN_AP_ProvideAssistanceData
typedef struct LPPe_OMA_LPPe_WLAN_AP_ProvideAssistanceData {
LPPe_OMA_LPPe_WLAN_DataSet
LPPe_OMA_LPPe_WLAN_AP_Error
} LPPe_OMA_LPPe_WLAN_AP_ProvideAssistanceData