Content for TS 33.128 Word version: 18.7.0
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.42 Type: GNSSPositioningMethodAndUsage
7.3.3.2.43 Type: HorizontalVelocity
7.3.3.2.44 Type: HorizontalWithVerticalVelocity
7.3.3.2.45 Type: HorizontalVelocityWithUncertainty
7.3.3.2.46 Type: HorizontalWithVerticalVelocityAndUncertainty
7.3.3.2.47 Type: LocationPresenceReport
7.3.3.2.48 Type: AMFEventArea
7.3.3.2.49 Type: RMInfo
7.3.3.2.50 Type: CMInfo
7.3.3.2.51 Enumeration: AccuracyFulfilmentIndicator
7.3.3.2.52 Enumeration: PositioningMethod
7.3.3.2.53 Enumeration: PositioningMode
7.3.3.2.54 Enumeration: GNSSID
7.3.3.2.55 Enumeration: Usage
7.3.3.2.56 Enumeration: VerticalDirection
7.3.3.2.57 Type: IMSLocation
7.3.3.2.58 Type: PANIHeaderInfo
7.3.3.2.59 Type: SIPGeolocationHeaderInfo
7.3.3.2.60 Type: SIPLocationInfo
7.3.3.2.61 Type: SIPCNIHeaderInfo
7.3.3.2.62 Type: PresenceInfo
...
...
7.3.3.2.42 Type: GNSSPositioningMethodAndUsage p. 198
The GNSSPositioningMethodAndUsage type is derived from the data present in the GNSSPositioningMethodAndUsage type defined in clause 6.1.6.2.16 of TS 29.572.
Table 7.3.3.2.42-1 contains the details for the GNSSPositioningMethodAndUsage type.
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| mode | Positioning | 1 | Indicates 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 |
| gnss | GnssID | 1 | Indicates the related GNSS positioning method. Shall be encoded as described in clause 6.1.6.3.8 of TS 29.572. | M |
| usage | Usage | 1 | Indicates 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 |
7.3.3.2.43 Type: HorizontalVelocity p. 198
The HorizontalVelocity type is derived from the data present in the HorizontalVelocity type defined in clause 6.1.6.2.18 of TS 29.572.
Table 7.3.3.2.43-1 contains the details for the HorizontalVelocity type.
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| hSpeed | Horizontal | 1 | Horizontal speed in kilometres per hour. Shall be encoded as described in TS 29.572 Table 6.1.6.3.2-1. | M |
| bearing | Angle | 1 | Bearing angle in degrees, measured clockwise from North. Shall be encoded as described in TS 29.572 Table 6.1.6.3.2-1. | M |
7.3.3.2.44 Type: HorizontalWithVerticalVelocity p. 198
The HorizontalWithVerticalVelocity type is derived from the data present in the HorizontalWithVerticalVelocity type defined in clause 6.1.6.2.19 of TS 29.572.
Table 7.3.3.2.44-1 contains the details for the HorizontalWithVerticalVelocity type.
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| hSpeed | Horizontal | 1 | Horizontal speed in kilometres per hour. Shall be encoded as described in TS 29.572 Table 6.1.6.3.2-1. | M |
| bearing | Angle | 1 | Bearing angle in degrees, measured clockwise from North. Shall be encoded as described in TS 29.572 Table 6.1.6.3.2-1. | M |
| vSpeed | Vertical | 1 | Vertical Seed in kilometres per hour. Shall be encoded as described in TS 29.572 Table 6.1.6.3.2-1. | M |
| vDirection | Vertical | 1 | Vertical Direction: upward or downward. Shall be encoded as described in clause 6.1.6.3.13 of TS 29.572. | M |
7.3.3.2.45 Type: HorizontalVelocityWithUncertainty p. 199
The HorizontalVelocityWithUncertainty type is derived from the data present in the HorizontalVelocityWithUncertainty type defined in clause 6.1.6.2.20 of TS 29.572.
Table 7.3.3.2.45-1 contains the details for the HorizontalVelocityWithUncertainty type.
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| hSpeed | Horizontal | 1 | Horizontal speed in kilometres per hour. Shall be encoded as described in TS 29.572 Table 6.1.6.3.2-1. | M |
| bearing | Angle | 1 | Bearing angle in degrees, measured clockwise from North. Shall be encoded as described in TS 29.572 Table 6.1.6.3.2-1. | M |
| uncertainty | Speed | 1 | Uncertainty of horizontal speed in kilometres per hour. Shall be encoded as described in TS 29.572 Table 6.1.6.3.2-1. | M |
7.3.3.2.46 Type: HorizontalWithVerticalVelocityAndUncertainty p. 199
The HorizontalWithVerticalVelocityAndUncertainty type is derived from the data present in the HorizontalWithVerticalVelocityAndUncertainty type defined in clause 6.1.6.2.21 of TS 29.572.
Table 7.3.3.2.46-1 contains the details for the HorizontalWithVerticalVelocityAndUncertainty type.
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| hSpeed | Horizontal | 1 | Horizontal speed in kilometres per hour. Shall be encoded as described in TS 29.572 Table 6.1.6.3.2-1. | M |
| bearing | Angle | 1 | Bearing angle in degrees, measured clockwise from North. Shall be encoded as described in TS 29.572 Table 6.1.6.3.2-1. | M |
| vSpeed | Vertical | 1 | Vertical Seed in kilometres per hour. Shall be encoded as described in TS 29.572 Table 6.1.6.3.2-1. | M |
| vDirection | Vertical | 1 | Vertical Direction: upward or downward. Shall be encoded as described in clause 6.1.6.3.13 of TS 29.572. | M |
| hUncertainty | Speed | 1 | Uncertainty of horizontal speed in kilometres per hour Shall be encoded as described in TS 29.572 Table 6.1.6.3.2-1. | M |
| vUncertainty | Speed | 1 | Uncertainty of vertical speed in kilometres per hour. Shall be encoded as described in TS 29.572 Table 6.1.6.3.2-1. | M |
7.3.3.2.47 Type: LocationPresenceReport p. 199
The LocationPresenceReport type is used in the case the information is obtained from an AmfEventReport (clause 6.2.6.2.5 of TS 29.518) with event type Location_Report or Presence_In_AOI_Report.
Table 7.3.3.2.47-1 contains the details for the LocationPresenceReport type.
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| type | AMFEventType | 1 | Describes the type of event which triggers the report. | M |
| timestamp | Timestamp | 1 | This shall contain the time at which the event is generated. | M |
| areaList | SET OF AMFEvent | 0..MAX | This field shall be present when the AMFEventtype is set as "presenceInAOIReport". When present, this field represents the specified Area(s) of Interest the UE is currently in or out or unknown. | C |
| timeZone | TimeZone | 0..1 | This parameter shall be present if the local timeZone of the UE is known at the NF. | C |
| accessType | SET OF AccessType | 0..MAX | Describes the access type(s) of the UE. When reporting that the UE is reachable for DL traffic, this field shall indicate the access type(s) through which the UE is reachable. | C |
| rMInfoList | SET OF RMInfo | 0..MAX | Describes the registration management state of the UE. This field shald be present if it is known at the NF. Shall be encoded as defined in clause 6.2.6.2.8 of TS 29.518. | C |
| cMInfoList | SET OF CMInfo | 0..MAX | Describes the connection management state of the UE. This field shald be present if it is known at the NF. Shall be encoded as defined in clause 6.2.6.2.9 of TS 29.518. | C |
| reachability | UE | 0..1 | Describes the reachability of the UE. This field shald be present if it is known at the NF Shall be encoded as defined in clause 6.2.6.3.7 of TS 29.518. | C |
| location | UserLocation | 0..1 | Location information type derived from the data defined in the UserLocation type defined in clause 5.4.4.7 of TS 29.571.
This field shall be used to convey one or more of the following:
| C |
| additional | SEQUENCE OF Cell | 0..MAX | This parameter shall be present if the NF has additional cell information for the UE. Shall be used whenever Dual Connectivity is activated or whenever secondary cell information is available at the NF where the POI is located. | C |
7.3.3.2.48 Type: AMFEventArea p. 200
The AMFEventArea type is derived from the data present in the AMFEventArea type defined in clause 6.2.6.2.16 of TS 29.518.
Table 7.3.3.2.48-1 contains the details for the AMFEventArea type.
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| presence | Presence | 0..1 | This field shall be present if the Area of Interest subscribed is not a LADN service area. | C |
| lADNInfo | LADNInfo | 0..1 | This field shall be present if the Area of Interest subscribed is a LADN service area. | C |
7.3.3.2.49 Type: RMInfo p. 200
The RMInfo type is derived from the data present in the RMInfo type defined in clause 6.2.6.2.8 of TS 29.518.
Table 7.3.3.2.49-1 contains the details for the RMInfo type.
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| rMState | RMState | 1 | Describes the registration management state of the UE. | M |
| accessType | AccessType | 1 | Describes the access type of the UE that applies to the registration management state reported. | M |
7.3.3.2.50 Type: CMInfo p. 201
The CMInfo type is derived from the data present in the CMInfo type defined in clause 6.2.6.2.9 of TS 29.518.
Table 7.3.3.2.50-1 contains the details for the CMInfo type.
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| cMState | CMState | 1 | Describes the connection management state of the UE. | M |
| accessType | AccessType | 1 | Describes the access type of the UE that applies to the connection management state reported. | M |
7.3.3.2.51 Enumeration: AccuracyFulfilmentIndicator p. 201
The AccuracyFulfilmentIndicator indicates wheather the requested accuracy was fulfilled or not the AccuracyFulfilmentIndicator is derived from the data present in the AccuracyFulfilmentIndicator type defined in clause 6.1.6.3.12 of TS 29.572.
Table 7.3.3.2.51-1 contains the details of the AccuracyFulfilmentIndicator type.
| Enumeration value | Description |
|---|---|
| requestedAccuracyFulfilled(1) | Requested accuracy is fulfilled. |
| requestedAccuracyNotFulfilled(2) | Requested accuracy is not fulfilled. |
7.3.3.2.52 Enumeration: PositioningMethod p. 201
The PositioningMethod represents the method used to determine the location of the UE, the PositioningMethod is derived from the data present in the PositioningMethod type defined in clause 6.1.6.3.6 of TS 29.572.
Table 7.3.3.2.52-1 contains the details of the PositioningMethod type.
| Enumeration value | Description |
|---|---|
| cellID(1) | Cell ID positioning method. |
| eCID(2) | Enhanced cell ID methods based on LTE signals. |
| oTDOA(3) | Observed time difference of arrival positioning based on LTE signals. |
| barometricPressure(4) | Positioning method based on barometric Pressure Sensor. |
| wLAN(5) | WLAN positioning. |
| Bluetooth(6) | Bluetooth positioning. |
| mBS(7) | Terrestrial Beacon System (TBS) positioning based on MBS signals. |
| motionSensor(8) | Positioning method based on motion Sensor. |
| dLTDOA(9) | Downlink Time Difference of Arrival (DL-TDOA) based on NR signals. |
| dLAOD(10) | Downlink Angle-of-Departure (DL-AoD) based on NR signals. |
| multiRTT(11) | Multi-Round Trip Time Positioning (Multi-RTT based on NR signals). |
| nRECID(12) | NR enhanced cell ID methods (NR E-CID) based on NR signals. |
| uLTDOA(13) | Uplink Time Difference of Arrival (UL-TDOA) based on NR signals. |
| uLAOA(14) | Uplink Angle of Arrival (UL-AoA), including the Azimuth of Arrival (A-AoA) and the Zenith of Arrival (Z-AoA) based on NR signals. |
| networkSpecific(15) | Network specific position methods. |
7.3.3.2.53 Enumeration: PositioningMode p. 202
The PositioningMode represents the mode used to determine the location of the UE when a certain positioning method is used, the PositioningMode is derived from the data present in the PositioningMode type defined in clause 6.1.6.3.7 of TS 29.572.
Table 7.3.3.2.53-1 contains the details of the PositioningMode type.
| Enumeration value | Description |
|---|---|
| uEBased(1) | UE-based mode. |
| uEAssisted(2) | UE-assisted mode. |
| conventional(3) | Conventional mode. |
7.3.3.2.54 Enumeration: GNSSID p. 202
The GNSSID represents the different global navigation satellite systems, the GNSSID is derived from the data present in the GNSSID type defined in clause 6.1.6.3.8 of TS 29.572.
Table 7.3.3.2.54-1 contains the details of the GNSSID type.
| Enumeration value | Description |
|---|---|
| gPS(1) | GPS. |
| galileo(2) | Galileo. |
| sBAS(3) | Space Based Augmentation Systems. |
| modernizedGPS(4) | Modernized GPS. |
| qZSS(5) | Quasi Zenith Satellite System. |
| gLONASS(6) | Global Navigation Satellite System. |
| bDS(7) | BeiDou Navigation Satellite System. |
| nAVIC(8) | Navigation with Indian Constellation. |
7.3.3.2.55 Enumeration: Usage p. 202
The Usage represents the type of usage made of the location measurement from the UE, the Usage is derived from the data present in the Usage type defined in clause 6.1.6.3.9 of TS 29.572.
Table 7.3.3.2.55-1 contains the details of the Usage type.
| Enumeration value | Description |
|---|---|
| unsuccess(1) | Not successful. |
| successResultsNotUsed(2) | Successful result not used. |
| successResultsUsedToVerifyLocation(3) | Successful result used to verify the location estimate. |
| successResultsUsedToGenerateLocation(4) | Successful result used to generate the location estimate. |
| successMethodNotDetermined(5) | Successful method not determined. |
7.3.3.2.56 Enumeration: VerticalDirection p. 203
The VerticalDirection represents the direction (upward/downward) of the vertical speed, the VerticalDirection is derived from the data present in the VerticalDirection type defined in clause 6.1.6.3.13 of TS 29.572.
Table 7.3.3.2.56-1 contains the details of the VerticalDirection type.
| Enumeration value | Description |
|---|---|
| upward(1) | Vertical speed is upward. |
| downward(2) | Vertical speed is downward. |
7.3.3.2.57 Type: IMSLocation p. 203
The IMSLocation type is used to report information derived from the IMS.
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| pANI | SEQUENCE OF PANI | 0..MAX | Contains information from the P-Access-Network-Information header of the SIP Message. Shall be present if there are one or more PANI Header fields in the SIP message. One instance of PANIHeaderInfo shall be used for each P-Access-Network-Information header. | C |
| geolocation | SEQUENCE OF SIP | 0..MAX | Contains the information from the Geolocation-header of the SIP Message. Shall be present if there are one or more Geolocation-header fields. One instance of SIPGeolocationHeaderInfo shall be used for each Geolocation-header. | C |
| cNI | SEQUENCE OF SIPCNI | 0..MAX | Contains the information from the Cellular-Network-Info header of the SIP Message. Shall be present if there are one or more Cellular-Network-Info header fields. One instance of SIPCNIHeaderInfo shall be used for each Cellular-Network-Info header. | C |
7.3.3.2.58 Type: PANIHeaderInfo p. 203
The PANIHeaderInfo type is used to report information derived from the P-Access-Network-Information header field of the SIP Message (see clauses 7.2A.4.2 and 7.2A.4.3 of TS 24.229).
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| accessNetwork | SIP | 1 | Provides non-location related access network information. | M |
| accessInfo | SEQUENCE OF SIP | 0..MAX | Contains the location related information from the access-info field parameter of the PANI Header. One instance of SIPAccessInfo shall be used for each access-info field parameter of the PANI header. | C |
| pANI | SEQUENCE OF SIP | 0..MAX | Contains the location information from the PANI header in the LocationInfo structure. One instance of SIPLocationInfo shall be present for each access-info field parameter of a type that can be mapped to the LocationInfo structure. | C |
7.3.3.2.59 Type: SIPGeolocationHeaderInfo p. 204
The SIPGeolocationHeaderInfo type is used to report information derived from the Geolocation-header of a SIP message.
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| locationValue | UTF8String | 1 | Contains information from the locationValue header parameter of the Geolocation-header of the SIP Message (see Section 4.1 of RFC 6442). One instance of SIPGeolocationValue shall be used for each locationValue header parameter. | M |
| cidInfo | UTF8String | 0..1 | Contains the contents of the MIME bodypart if the locationValue is a cid-url (see Section 4.1 of RFC 6442 and Section 5 of RFC 6442). The value of the cidInfo field shall include the headers and contents of the MIME bodypart indicated by the cid-url. | C |
7.3.3.2.60 Type: SIPLocationInfo p. 204
The SIPLocationInfo type is used to report location information derived from the P-Access-Network-Information or Cellular-Network-Info header of a SIP message.
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| locationInfo | LocationInfo | 0..1 | Shall be used to report location information received from a 5G Access Network. | C |
| cellInformation | CellInformation | 0..1 | Shall be used to report the cell site information and cell radio related information for the cell reporteg in the locationInfo field. Shall be present if known at the NF where the POI is located or at the MDF. | C |
7.3.3.2.61 Type: SIPCNIHeaderInfo p. 204
The SIPCellularLocationInfo type is used to report cellular access network information derived from the Cellular-Network-Info (CNI) header of a SIP message (see clause 7.2.15.7 of TS 24.229).
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| cellular | SIPCellular | 1 | Provides non-location related cellular network information. | M |
| cellular | SEQUENCE OF SIPCellular | 0..MAX | Contains the location related information from the cellular-access-info field parameter of the CNI Header (see clause 7.2.15.7 of TS 24.229). Shall be present if the cellular-access-info field parameter of the CNI Header is present. | C |
| cNILocation | SEQUENCE OF SIP | 0..MAX | Contains the location information from the CNI header in the LocationInfo structure. One instance of SIPLocationInfo shall be present for each cellular-access-info field parameter of a type that can be mapped to the LocationInfo structure. | C |
7.3.3.2.62 Type: PresenceInfo p. 205
The PresenceInfo type is derived from the data present in the PresenceInfo type defined in clause 5.4.4.27 of TS 29.571.
Table 7.3.3.2.62-1 contains the details for the PresenceInfo type.
| Field name | Type | Cardinality | Description | M/C/O |
|---|---|---|---|---|
| presence | Presence | 0..1 | Indicates whether the UE is inside or outside of the area of interest or if the presence reporting area is inactive in the serving node. Shall be present when known at the NF. | C |
| tracking | SET OF TAI | 0..MAX | Represents the list of tracking areas that constitutes the area. This field contains the list of tracking areas when tracking areas are part of the area of interest. | C |
| eCGIList | SET OF ECGI | 0..MAX | Represents the list of EUTRAN cell IDs that constitutes the area. This field contains the list of ECGIs when ECGIs are part of the area of interest. | C |
| nCGIList | SET OF NCGI | 0..MAX | Represents the list of NR cell Ids that constitutes the area. This field contains the list of NCGIs when NCGIs are part of the area of interest. | C |
| globalRAN | SET OF GlobalRAN | 0..MAX | Represents the list of NG RAN node identifiers that constitutes the area. This field contains the list of GlobalRANNodeIDs when NG RAN Nodes are part of the area of interest. | C |
| global | SET OF GlobalRAN | 0..MAX | Represents the list of eNodeB identifiers that constitutes the area. This field contains the list of GlobalRANNodeIDs when eNbIDs are part of the area of interest. | C |
