Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 33.128  Word version:  18.6.0

Top   Top   Up   Prev   Next
0…   4…   5…   5.7…   6…   6.2.2.2A…   6.2.3…   6.2.3.2.7…   6.2.3.3…   6.2.4…   6.3…   6.3.2.2A…   6.3.3…   6.3.3.2…   6.3.3.2.4…   6.3.3.2A…   7…   7.3…   7.3.3…   7.3.3.2.21…   7.3.3.2.42…   7.3.3.2.63…   7.3.4…   7.4…   7.4.3.8…   7.5…   7.6…   7.7…   7.7.4…   7.8…   7.8.4…   7.9…   7.10…   7.10.4…   7.11…   7.12…   7.13…   7.13.3…   7.13.3.4…   7.14…   7.15…   8…   A…   D…   E…   M…

 

7.3.3.2.21  Type: CellInformationp. 182
Table 7.3.2.2-1 contains the details for the CellInformation type.
7.3.3.2.22  Type: RANCGIp. 182
Table 7.3.3.2.22-1 contains the details for the RANCGI type.
CHOICE Type Description
eCGIECGIShall be used to report the E-UTRA Cell Identity.
nCGINCGIShall be used to report the NR Cell Identity.
CGICGIShall be used to report the GERA or UTRA Cell Identity.
Up
7.3.3.2.23  Type: TAIp. 183
The TAI type is used to report the Tracking Area Identity. The TAI type is derived from the data present in the EutraLocation type defined in clause 5.4.4.3 of TS 29.571.
Table 7.3.3.2.23-1 contains the details for the TAI type.
Field name Type Cardi­nality Description M/C/O
pLMNIDPLMNID1The PLMN Identity of the TAI.M
tACTAC1The Tracking Area Code for the Tracking Area being reported.M
nIDNID0..1Network Identifier of the Tracking Area being reported. Shall be be present if the TAI being reported belongs to an SNPN.C
Up
7.3.3.2.24  Type: ECGIp. 183
The ECGI type is used to report the E-UTRA Cell Identity. The ECGI type is derived from the data present in the ECGI type defined in clause 5.4.4.5 of TS 29.571.
Table 7.3.3.2.24-1 contains the details for the ECGI type.
Field name Type Cardi­nality Description M/C/O
pLMNIDPLMNID1The PLMN Identity of the cell being reported.M
eUTRACellIDEUTRACellID1The E-UTRA Cell Identity for the cell being reported.M
nIDNID0..1Network Identifier of the cell being reported. Shall be be present if the cell being reported belongs to an SNPN.C
Up
7.3.3.2.25  Type: GlobalRANNodeIDp. 183
The GlobalRANNodeID type is derived from the data present in the GlobalRANNodeID type defined in clause 5.4.4.28 of TS 29.571.
Table 7.3.3.2.25-1 contains the details for the GlobalRANNodeID type.
Field name Type Cardi­nality Description M/C/O
pLMNIDPLMNID1The PLMN Identity of the RAN Node.M
aNNodeIDANNodeID1The Global Identifier for the Access Node.M
nIDNID0..1Network Identifier of the cell being reported. Shall be be present if the cell being reported belongs to an SNPN.C
Up
7.3.3.2.26  Type: ANNodeIDp. 183
The ANNodeID type is derived from the data present in the GlobalRANNodeID type defined in clause 5.4.4.28 of TS 29.571.
Table 7.3.3.2.26-1 contains the details for the ANNodeID type.
CHOICE Type Description
n3IWFIDN3IWFIDSBIShall be chosen if the AN node represents a N3IWF. When present, this field shall contain the identifier of the N3IWF.
gNBIDGNBIDShall be chosen if the RAN Node ID represents a gNB. When present, this field shall contain the identifier of the gNB.
nGENbIDNGENbIDShall be chosen if the RAN Node ID represents a NG-eNB. When present, this field shall contain the identifier of the NG-eNB.
eNbIDENbIDShall be chosen if the RAN Node ID represents a eNB. When present, this field shall contain the identifier of the eNB.
wAGFIDWAGFIDif the RAN Node ID represents a WAGF. When present, this field shall contain the identifier of the WAGF.
tNGFIDTNGFIDShall be present if the RAN Node ID represents a TNGF. When present, this field shall contain the identifier of the TNGF.
Up
7.3.3.2.27  Type: NgENBIDp. 184
The nGENbID type is derived from the data present in the NgeNbId type defined in TS 29.571 Table 5.4.2-1.
Table 7.3.3.2.27-1 contains the details for the NGENbID type.
CHOICE Type Description
macroNGENbIDBIT STRING (SIZE(20))Shall be chosen if the ng-eNB ID is a Macro ng-eNB ID. Shall be encoded as described in clause 9.3.1.8 of TS 38.413.
shortMacroNGENbIDBIT STRING (SIZE(18))Shall be chosen if the ng-eNB ID is a Short Macro ng-eNB ID. Shall be encoded as described in clause 9.3.1.8 of TS 38.413.
longMacroNGENbIDBIT STRING (SIZE(21))Shall be chosen if the ng-eNB ID is a Long Macro ng-eNB ID. Shall be encoded as described in clause 9.3.1.8 of TS 38.413.
Up
7.3.3.2.28  Type: NCGIp. 184
The NCGI type is used to report the NR Cell Identity. The NCGI type is derived from the data present in the NCGI type defined in clause 5.4.4.6 of TS 29.571.
Table 7.3.3.2.28-1 contains the details for the NCGI type.
Field name Type Cardi­nality Description M/C/O
pLMNIDPLMNID1The PLMN Identity of the cell being reported.M
nRCellIDNRCellID1The NR Cell Identity for the cell being reported.M
nIDNID0..1Network Identifier of the cell being reported. Shall be be present if the cell being reported belongs to an SNPN.C
Up
7.3.3.2.29  Type: IPAddrp. 184
The IPAddr type is used to report IP Addresses.
Table 7.3.3.2.29-1 contains the details for the IPAddr type.
Field name Type Cardi­nality Description M/C/O
iPv4AddressIPv4Address0..1The IPv4 address being reported. Shall be included if known at the NF where the POI is located.C
iPv6AddressIPv6Address0..1The IPv6 address being reported. Shall be included if known at the NF where the POI is located.C
Up
7.3.3.2.30  Type: TNAPIDp. 185
The TNAPID type is used to report the TNAP Identity. The TNAPID type is derived from the data present in the TnapId type defined in clause 5.4.4.62 of TS 29.571.
Table 7.3.3.2.30-1 contains the details for the TNAPID type.
Field name Type Cardi­nality Description M/C/O
sSIDSSID0..1The SSID of the access point to which the UE is attached. This parameter shall be present when the UE is accessing the 5GC via a trusted WLAN or if known at the NF where the POI is located.C
bSSIDBSSID0..1The SSID of the access point to which the UE is attached. This parameter shall be present if known at the NF where the POI is located.C
civicAddressCivicAddressBytes0..1The civic address of the TNAP to which the UE is attached including the associated Location-Information and Location-Data (see TS 29.571 Table 5.4.4.62-1. This parameter shall be present if known at the NF where the POI is located.C
Up
7.3.3.2.31  Type: TWAPIDp. 185
The TWAPID type is used to report the TWAP Identity. The TWAPID type is derived from the data present in the TwapId type defined in clause 5.4.4.63 of TS 29.571.
Table 7.3.3.2.31-1 contains the details for the TWAPID type.
Field name Type Cardi­nality Description M/C/O
sSIDSSID0..1The SSID of the access point to which the UE is attached.MD
bSSIDBSSID0..1The SSID of the access point to which the UE is attached. This parameter shall be present if known at the NF where the POI is located.C
civicAddressCivicAddressBytes0..1The civic address of the TNAP to which the UE is attached including the associated Location-Information and Location-Data (see TS 29.571 Table 5.4.4.62-1. This parameter shall be present if known at the NF where the POI is located.C
Up
7.3.3.2.32  Enumeration: W5GBANLineTypep. 185
The W5GBANLineType indicates the type of wireline access used connect to the 5GS. The W5GBANLineType type is derived from the data present in the LineType type defined in clause 5.4.3.33 of TS 29.571.
Table 7.3.3.2.32-1 contains the details for the W5GBANLineType type.
Enumeration value Description
dSL(1)DSL Line
pON(2)PON Line
Up
7.3.3.2.33  Enumeration: TransportProtocolp. 186
The TransportProtocol indicates the transport protocol used to connect to the 5GS. The TransportProtocol type is derived from the data present in the TransportProtocol type defined in clause 5.4.4.10 of TS 29.571 and Table 5.4.3.38.
Table 7.3.3.2.33-1 contains the details for the clause TransportProtocol type.
Enumeration value Description
uDP(1)UDP is in use.
tCP(2)TCP is in use.
Up
7.3.3.2.34  Type: PLMNIDp. 186
The PLMNID type is used to report the PLMN Identity. The PLMNID type is derived from the data present in the PlmnId type defined in clause 5.4.4.3 of TS 29.571.
Table 7.3.3.2.34-1 contains the details for the PLMNID type.
Field name Type Cardi­nality Description M/C/O
mCCMCC1The Mobile Country CodeM
mNCMNC1The Mobile Network CodeM
Up
7.3.3.2.35  Type: ENbIDp. 186
The ENbID type is used to report the ENb Identity. The ENbID type is derived from the data present in the ENbId type defined in clause 5.4.2 of TS 29.571.
Table 7.3.3.2.35-1 contains the details for the ENbID type.
CHOICE Type Description
macroENbIDBIT STRING (SIZE(20))Shall be chosen if the eNB ID is a Macro eNB ID. Shall be encoded as described in clause 9.2.1.37 of TS 36.413.
homeENbIDBIT STRING (SIZE(28))Shall be chosen if the eNB ID is a Home eNB ID.
Shall be encoded as descriped in clause 9.2.1.37 of TS 36.413.
shortMacroENbIDBIT STRING (SIZE(18))Shall be chosen if the eNB ID is a Short Macro eNB ID. Shall be encoded as described in clause 9.2.1.37 of TS 36.413.
longMacroENbIDBIT STRING (SIZE(21))Shall be chosen if the eNB ID is a Long Macro eNB ID. Shall be encoded as described in clause 9.2.1.37 of TS 36.413.
Up
7.3.3.2.36  Type: PositioningInfop. 186
The PositioningInfo type is derived from the data present in the ProvidePosInfo type defined in clause 6.4.6.2.3 of TS 29.518.
Table 7.3.3.2.36-1 contains the details for the PositioningInfo type.
Field name Type Cardi­nality Description M/C/O
positionInfoLocationData0..1This parameter shall be used any time information from LCS operations needs to be reported from the 5GC. This structure may also be used any time information from the ProvidePosInfo structure needs to be reported. This field is derived from the data present in the ProvidePosInfo type defined in clause 6.4.6.2.3 of TS 29.518.C
rawMLPResponseRawMLPResponse0..1 This field shall be used in the location field of the LALSReport record see clause 7.3.1.4. This field contains a copy of the unparsed XML code of the MLP Answer and Report messages. The contents of this field is described in OMA-TS-MLP-V3_5-20181211-C [20] clause 5.2.3.2.C
Up
7.3.3.2.37  Type: LocationDatap. 187
The LocationData type is derived from the data present in the LocationData type defined in clause 6.1.6.2.3 of TS 29.572.
Table 7.3.3.2.37-1 contains the details for the LocationData type.
Field name Type Cardi­nality Description M/C/O
locationEstimateGeographicArea1This field shall contain an estimate of the location of the UE in universal coordinates and the accuracy of the estimate. clause 6.1.6.2.5 of TS 29.572.M
accuracyFulfilmentIndicatorAccuracyFulfilmentIndicator0..1This enumerated field shall be present to represent whether the requested accuracy was fulfilled or not. Shall be encoded as described in clause 6.1.6.3.12 of TS 29.572.C
ageOfLocationEstimateAgeOfLocation0..1This field shall be present if information is available at the NF. Shall be encoded as described in TS 29.572, Table 6.1.6.3.2-1.C
velocityEstimateVelocityEstimate0..1This field shall be present if information is available at the NF. Shall be encoded as described in clause 6.1.6.2.17 of TS 29.572.C
civicAddressCivicAddress0..1This field shall be present if information is available at the NF. Shall be encoded as described in clause 6.1.6.2.14 of TS 29.572.C
positioningDataListSET OF PositioningMethodAndUsage0..MAXThis field shall be present if information is available at the NF. Shall be encoded as described in clause 6.1.6.2.15 of TS 29.572.C
gNSSPositioningDataListSET OF GNSSPositioningMethodAndUsage0..MAXThis field shall be present if information is available at the NF. Shall be encoded as described in clause 6.1.6.2.16 of TS 29.572.C
eCGIECGI0..1This field shall be present if information is available at the NF. Shall be encoded as described in clause 5.4.4.5 of TS 29.571.C
nCGINCGI0..1This field shall be present if information is available at the NF. Shall be encoded as described in clause 5.4.4.6 of TS 29.571.C
altitudeAltitude0..1This field shall be present if information is available at the NF. Shall be encoded as described in TS 29.572, Table 6.1.6.3.2-1.C
barometricPressureBarometricPressure0..1This field shall be present if information is available at the NF. Shall be encoded as described in TS 29.572, Table 6.1.6.3.2-1.C
Up
7.3.3.2.38  Type: RawMLPResponsep. 188
The RawMLPResponse type is derived from the data present in the slia MLP message described in OMA-TS-MLP-V3_5-20181211-C [20] clause 5.2.3.2.2 or the slirep MLP message described in OMA-TS-MLP-V3_5-20181211-C [20] clause 5.2.3.2.3 along with the OMA MLP result id defined in OMA-TS-MLP-V3_5-20181211-C [20], clause 5.4
Table 7.3.3.2.38-1 contains the details for the RawMLPResponse type.
CHOICE Type Description
mLPPositionDataUTF8String This field contains a copy of unparsed XML code of the MLP response message. The slia response message of this field are described in OMA-TS-MLP-V3_5-20181211-C [20] clause 5.2.3.2.2 and the slirep response message of this field is described in OMA-TS-MLP-V3_5-20181211-C [20] clause 5.2.3.2.3.
mLPErrorCodeINTEGER (1..699) This field contains the OMA MLP result id defined in OMA-TS-MLP-V3_5-20181211-C [20], clause 5.4.
Up
7.3.3.2.39  Type: VelocityEstimatep. 189
The VelocityEstimate type is derived from the data present in VelocityEstimate type in clause 6.1.6.2.17 of TS 29.572
Table 7.3.3.2.39-1 contains the details for the VelocityEstimate type.
CHOICE Type Description
horVelocityHorizontalVelocityVelocity estimate including horizontal speed and bearing. Shall be encoded as described in clause 6.1.6.2.18 of TS 29.572.
horWithVertVelocityHorizontalWithVerticalVelocityVelocity estimate including horizontal speed and bearing, and also vertical speed and vertical direction. Shall be encoded as described in clause 6.1.6.2.19 of TS 29.572.
horVelocityWithUncertaintyHorizontalVelocityWithUncertaintyVelocity estimate including horizontal speed and bearing; it also includes an uncertainty value. Shall be encoded as described in clause 6.1.6.2.20 of TS 29.572.
horWithVertVelocityAndUncertaintyHorizontalWithVerticalVelocityAndUncertaintyVelocity estimate including horizontal speed and bearing, and also vertical speed and vertical direction; it also includes uncertainty value for horizontal and vertical speeds. Shall be encoded as described in clause 6.1.6.2.21 of TS 29.572.
Up
7.3.3.2.40  Type: CivicAddressp. 189
The CivicAddress type is derived from the data present in the CivicAddress type defined in clause 6.1.6.2.14 of TS 29.572.
Table 7.3.3.2.40-1 contains the details for the CivicAddress type.
Field name Type Cardi­nality Description M/C/O
CountryUTF8String1The two-letter ISO 3166 country code in capital ASCII letters, e.g. DE or US.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
M
a1UTF8String0..1National subdivisions (state, canton, region, province, prefecture).
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
a2UTF8String0..1County, parish, gun (JP), district (IN). Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.C
a3UTF8String0..1City, township, shi (JP).
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
a4UTF8String0..1City division, borough, city district, ward, chou (JP).
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
a5UTF8String0..1Neighbourhood, block.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
a6UTF8String0..1Group of streets below the neighbourhood level.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
prdUTF8String0..1Leading street direction.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
podUTF8String0..1Trailing street suffix.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
stsUTF8String0..1Street suffix or type.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
hnoUTF8String0..1House number.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
hnsUTF8String0..1House number suffix.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
lmkUTF8String0..1Landmark or vanity address.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
locUTF8String0..1Additional location information.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
namUTF8String0..1Name (residence and office occupant).
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
pcUTF8String0..1Postal/zip code.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
bldUTF8String0..1Building (structure).
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
unitUTF8String0..1Unit (apartment, suite).
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
flrUTF8String0..1Floor.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
roomUTF8String0..1Room.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
plcUTF8String0..1Place-type.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
pcnUTF8String0..1Postal community name.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
poboxUTF8String0..1Post office box (P.O. box).
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
addcodeUTF8String0..1Additional code.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
seatUTF8String0..1Seat (desk, cubicle, workstation).
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
rdUTF8String0..1Primary road or street.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
rdsecUTF8String0..1Road clause.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
rdbrUTF8String0..1Road branch.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
rdsubbrUTF8String0..1Road sub-branch.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
prmUTF8String0..1Road pre-modifier.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
pomUTF8String0..1Road post-modifier.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.14-1.
C
Up
7.3.3.2.41  Type: PositioningMethodAndUsagep. 191
The PositioningMethodAndUsage type is derived from the data present in the PositioningMethodAndUsage type defined in clause 6.1.6.2.15 of TS 29.572.
Table 7.3.3.2.41-1 contains the details for the PositioningMethodAndUsage type.
Field name Type Cardi­nality Description M/C/O
methodPositioningMethod1Indicates the related positioning method.
Shall be encoded as described in clause 6.1.6.3.6 of TS 29.572.
M
modePositioningMode1Indicates the mode of the location measurement from the related positioning method. Shall be encoded as described in clause 6.1.6.3.7 of TS 29.572.M
usageUsage1Indicates the usage of the location measurement from the related positioning method. Shall be encoded as described in clause 6.1.6.3.9 of TS 29.572.M
methodCodeMethodCode0..1 This field shall be present when the method field is set as "networkSpecific".
Shall be encoded as described in clause 6.1.6.2.15 of TS 29.572.
C
Up

Up   Top   ToC