B.4 Resource representation and APIs for location reporting provided by SLM-C
24.5453GPPLocation Management - Service Enabler Architecture Layer for Verticals (SEAL)Protocol specificationRelease 17TS
B.4.1 SU_LocationReporting API provided by SLM-C
B.4.1.1 API URI
The CoAP URIs used in CoAP requests from SLM-S towards the SLM-C shall have the Resource URI structure as defined in Annex C.1.1 of 3GPP TS 24.546 [29] with the following clarifications:
– the <apiName> shall be "su-lr-c";
– the <apiVersion> shall be "v1"; and
– the <apiSpecificSuffixes> shall be set as described in clause B.4.1.2.
B.4.1.2 Resources
B.4.1.2.1 Overview
{apiRoot}/su-lr-c/<api-version>
/
s
u
–
/val-services
/{valServiceId}
/trigger-configuration
/location
Figure B.4.1.2.1-1: Resource URI structure of the SU_LocationReporting API provided by SLM-C
Table B.4.1.2.1-1 provides an overview of the resources and applicable CoAP methods.
Table B.4.1.2.1-1: Resources and methods overview
|
Resource name |
Resource URI |
CoAP method |
Description |
|
Trigger Configuration |
/val-services/{valServiceId}/trigger-configuration |
GET |
Retrieve trigger configuration of the SLM-C for a given VAL service, according to query criteria. |
|
PUT |
Update trigger configuration of the SLM-C for a given VAL service, according to query criteria. |
||
|
DELETE |
Delete trigger configuration of the SLM-C for a given VAL service, according to query criteria. |
||
|
Location |
/location |
GET |
Retrieve location information of the SLM-C. |
B.4.1.2.2 Resource: Trigger Configuration
B.4.1.2.2.1 Description
The Trigger Configuration resource allows a SLM-S to manage the trigger configuration of a SLM-C.
B.4.1.2.2.2 Resource Definition
Resource URI: {apiRoot}/su-lr-c/<apiVersion>/val-services/{valServiceId}/trigger-configuration
This resource shall support the resource URI variables defined in the table B.4.1.2.2.2-1.
Table B.4.1.2.2.2-1: Resource URI variables for this resource
|
Name |
Data Type |
Definition |
|
apiRoot |
string |
See Annex C.1.1 of 3GPP TS 24.546 [29]. |
|
apiVersion |
string |
See clause B.3.1.1. |
|
valServiceId |
string |
Identifier of a VAL service. |
B.4.1.2.2.3 Resource Standard Methods
B.4.1.2.2.3.1 GET
This operation retrieves the trigger configuration.
This method shall support the response data structures and response codes specified in table B.4.1.2.2.3.1-1.
Table B.4.1.2.2.3.1-1: Data structures supported by the GET Response payload on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
LocationReportConfiguration |
M |
0..1 |
2.05 Content |
The trigger configuration information. |
|
NOTE: The mandatory CoAP error status codes for the GET Request listed in table C.1.3-1 of 3GPP TS 24.546 [29] shall also apply. |
||||
B.4.1.2.2.3.2 PUT
This operation updates the trigger configuration.
This method shall support the request data structures specified in table B.4.1.2.2.3.2-1 and the response data structures and response codes specified in table B.4.1.2.2.3.2-2.
Table B.4.1.2.2.3.2-1: Data structures supported by the PUT Request payload on this resource
|
Data type |
P |
Cardinality |
Description |
|
LocationReportConfiguration |
M |
1 |
Updated details of the trigger configuration. |
Table B.4.1.2.2.3.2-2: Data structures supported by the PUT Response payload on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
|
LocationReportConfiguration |
O |
1 |
2.04 Changed |
The trigger configuration updated successfully and the updated trigger configuration may be returned in the response. |
|
|
NOTE: The mandatory CoAP error status codes for the PUT method listed in table C.1.3-1 of 3GPP TS 24.546 [29] shall also apply. |
|||||
B.4.1.2.2.3.3 DELETE
This operation deletes the trigger configuration.
This method shall support the response data structures and response codes specified in table B.4.1.2.2.3.3-1.
Table B.4.1.2.2.3.3-1: Data structures supported by the DELETE Response payload on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
n/a |
2.02 Deleted |
The trigger configuration is deleted. |
||
|
NOTE: The mandatory CoAP error status codes for the DELETE method listed in table C.1.3-1 of 3GPP TS 24.546 [29] shall also apply. |
||||
B.4.1.2.3 Resource: Location
B.4.1.2.3.1 Description
The Location resource allows a SLM-S to retrieve the location information of a SLM-C.
B.4.1.2.3.2 Resource Definition
Resource URI: {apiRoot}/su-lr-c/<apiVersion>/location
This resource shall support the resource URI variables defined in the table B.4.1.2.3.2-1.
Table B.4.1.2.3.2-1: Resource URI variables for this resource
|
Name |
Data Type |
Definition |
|
apiRoot |
string |
See Annex C.1.1 of 3GPP TS 24.546 [29]. |
|
apiVersion |
string |
See clause B.4.1.1. |
B.4.1.2.3.3 Resource Standard Methods
B.4.1.2.3.3.1 GET
This operation retrieves the location information.
This method shall support the response data structures and response codes specified in table B.4.1.2.3.3-1.
Table B.4.1.2.3.3-1: Data structures supported by the GET Response payload on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
|
LocationReport |
M |
0..1 |
2.05 Content |
The location information of the SLM-C. |
|
|
NOTE: The mandatory CoAP error status codes for the GET Request listed in table C.1.3-1 of 3GPP TS 24.546 [29] shall also apply. |
|||||
B.4.1.3 Data Model
B.4.1.3.1 General
Table B.4.1.3.1-1 specifies the data types defined specifically for the SU_LocationReporting API service provided by SLM-C.
Table B.4.1.3.1-1: SU_LocationReporing API provided by SLM-C specific Data Types
|
Data type |
Section defined |
Description |
Applicability |
|
ValTargetUe |
B.2.1 |
Information identifying a VAL user ID or VAL UE ID. |
|
|
GeographicArea |
B.2.1 |
Defines a geographical area. |
|
|
BaseTrigger |
B.2.3.1 |
The unique identity of the trigger criterion. |
|
|
LocationReportConfiguration |
B.2.3.2 |
The configuration for location reporting. |
|
|
TriggeringCriteriaType |
B.2.3.3 |
The triggering criteria of location reporting. |
|
|
CellChange |
B.2.3.4 |
The triggers of cell change. |
|
|
SpecificCells |
B.2.3.5 |
The specific cell list. |
|
|
TrackingAreaChange |
B.2.3.6 |
The triggers of tracking area change. |
|
|
SpecificTrackingAreas |
B.2.3.7 |
The specific tracking are list. |
|
|
PlmnChange |
B.2.3.8 |
The triggers of PLMN change. |
|
|
SpecificPlmns |
B.2.3.9 |
The specific PLMN list. |
|
|
MbmsSaChange |
B.2.3.10 |
The triggers of MBMS serving area change. |
|
|
SpecificMbmsSas |
B.2.3.11 |
The specific MBMS serving area list. |
|
|
MbsfnAreaChange |
B.2.3.12 |
The triggers of MBSFN area change. |
|
|
SpecificMbsfnAreas |
B.2.3.13 |
The specific MBSFN are list. |
|
|
PeriodicReport |
B.2.3.14 |
The trigger of periodical reporting. |
|
|
TravelledDistance |
B.2.3.15 |
The trigger of travelled distance. |
|
|
VerticalAppEvent |
B.2.3.16 |
The triggers of specific vertical application events. |
|
|
GeographicalAreaChange |
B.2.3.17 |
The triggers of geographical area change. |
|
|
SpecificGeoAreas |
B.2.3.18 |
The specific list of geographical areas. |
|
|
LocationReport |
B.2.3.19 |
The location report information. |
|
|
LocationInfo |
B.2.3.20 |
The location information. |
Table B.4.1.3.1-2 specifies the simple data types defined specifically for the SU_LocationReporting API service provided by SLM-C.
Table B.4.1.3.1-2: SU_LocationReporing API provided by SLM-C specific Simple Data Types
|
Data type |
Section defined |
Description |
|
Uinteger |
B.2.1 |
Information identifying a VAL user ID or VAL UE ID. |
|
TriggerId |
B.2.4 |
String representing a unique identifier of a trigger criterion. |
|
CellId |
B.2.4 |
String representing a unique identifier of a cell. |
|
TaId |
B.2.4 |
String representing a unique identifier of a tracking area. |
|
PlmnId |
B.2.4 |
String representing a unique identifier of a PLMN. |
|
MbmsSaId |
B.2.4 |
String representing a unique identifier of a MBMS serving area. |
|
MbsfnAreaId |
B.2.4 |
String representing a unique identifier of a MSFN area. |
Table B.4.1.3.1-3 specifies the enumerations defined specifically for the SU_LocationReporting API service provided by SLM-C.
Table B.4.1.3.1-3: SU_LocationReporing API provided by SLM-C specific Enumeration
|
Data type |
Section defined |
Description |
|
Accuracy |
B.2.5 |
The accuracy of location information. |
B.4.1.4 Error Handling
General error responses are defined in clause C.1.3 of 3GPP TS 24.546 [23].
B.4.1.5 CDDL Specification
B.4.1.5.1 Introduction
The data model described in clause B.4.1.3 shall be binary encoded in the CBOR format as described in IETF RFC 8949 [26].
Clause B.4.1.5.2 uses the Concise Data Definition Language described in IETF RFC 8610 [28] and provides corresponding representation of the SU_LocationReporting API provided by SLM-C data model.
B.4.1.5.2 CDDL document
;;; LocationReportConfiguration
;;+ Represents Location reporting configuration information.
LocationReportConfiguration = {
valTgtUes: [* ValTargetUe]
locationType: Accuracy
? triggeringCriteria: [* TriggeringCriteriaType]
? minimumIntervalLength: Uinteger
}
;;; Accuracy
Accuracy = "CURRENT_SERVING_NCGI" / "NEIGHBOURING_NCGI" / "MBMS_SA" / "MBSFN_AREA" / "CURRENT_GEOGRAPHICAL_COORDINATE"
;;; TriggeringCriteriaType
TriggeringCriteriaType = {
? cellChange: CellChange
? trackingAreaChange: TrackingAreaChange
? plmnChange: PlmnChange
? mbmsSaChange: MbmsSaChange
? mbsfnAreaChange: MbsfnAreaChange
? periodicReport: PeriodicReport
? travelledDistance: TravelledDistance
? verticalAppEvent: VerticalAppEvent
? geographicalAreaChange: GeographicalAreaChange
}
;;; CellChange
CellChange = {
? anyCellChange: BaseTrigger
? enterSpecificCells: SpecificCells
? exitSpecificCells: SpecificCells
}
;;; SpecificCells
SpecificCells = {
triggerId: TriggerId
cells: [* CellId]
}
;;; TrackingAreaChange
TrackingAreaChange = {
? anyTrackingAreaChange: BaseTrigger
? enterSpecificTrackingAreas: SpecificTrackingAreas
? exitSpecificTrackingAreas: SpecificTrackingAreas
}
;;; SpecificTrackingAreas
SpecificTrackingAreas = {
triggerId: TriggerId
trackingAreas: [* TaId]
}
;;; PlmnChange
PlmnChange = {
? AnyPlmnChange: BaseTrigger
? EnterSpecificPlmns: SpecificPlmns
? ExitSpecificPlmns: SpecificPlmns
}
;;; SpecificPlmns
SpecificPlmns = {
triggerId: TriggerId
plmns: [* PlmnId]
}
;;; MbmsSaChange
MbmsSaChange = {
? anyPlmnChange: BaseTrigger
? enterSpecificPlmns: SpecificMbmsSas
? exitSpecificPlmns: SpecificMbmsSas
}
;;; SpecificMbmsSas
SpecificMbmsSas = {
triggerId: TriggerId
mbmsSas: [* MbmsSaId]
}
;;; MbsfnAreaChange
MbsfnAreaChange = {
? anyPlmnChange: BaseTrigger
? enterSpecificMbsfnAreas: SpecificMbsfnAreas
? exitSpecificPlmn: SpecificMbsfnAreas
}
;;; SpecificMbsfnAreas
SpecificMbsfnAreas = {
triggerId: TriggerId
mbsfnAreas: [* MbsfnAreaId]
}
;;; PeriodicReport
PeriodicReport = {
triggerId: TriggerId
interval: Uinteger
}
;;; TravelledDistance
TravelledDistance = {
triggerId: TriggerId
distance: Uinteger
}
;;; VerticalAppEvent
VerticalAppEvent = {
? initialLogOn: BaseTrigger
? locConfigReceived: BaseTrigger
? anyOtherEvent: BaseTrigger
}
;;; GeographicalAreaChange
GeographicalAreaChange = {
? AnyGeoAreaChange: BaseTrigger
? EnterSpecificGeoAreas: SpecificGeoAreas
? ExitSpecificGeoAreas: SpecificGeoAreas
}
;;; SpecificGeoAreas
SpecificGeoAreas = {
triggerId: TriggerId
geoAreas: [* GeographicArea]
}
;;; LocationReport
LocationReport = {
valTgtUe: ValTargetUe
triggerIds: [* TriggerId]
locInfo: LocationInfo
}
;;; LocationInfo
LocationInfo = {
? cellId: CellId
? neighbouringCellIds: [* CellId]
? mbmsSaId: MbmsSaId
? mbsfnAreaId: MbsfnAreaId
? currentCoordinate: GeographicalCoordinates
}
;;; BaseTrigger
BaseTrigger = {
triggerId: TriggerId
}
;;; TriggerId
;;+ Unique identifier of a trigger.
TriggerId = text
;;; ValTargetUe
;;+ Represents information identifying a VAL user ID or a VAL UE ID.
valUserId = {
valUserId: text ; Unique identifier of a VAL user.
}
valUeId = {
valUeId: text ; Unique identifier of a VAL UE.
}
ValTargetUe = valUserId / valUeId
;;; Uinteger
;;+ Unsigned Integer, i.e. only value 0 and integers above 0 are permissible.
Uinteger = int .ge 0
;;; GeographicArea
;;+ Geographic area specified by different shape.
GeographicArea = Point / PointUncertaintyCircle / PointUncertaintyEllipse / Polygon / PointAltitude / PointAltitudeUncertainty / EllipsoidArc
;;; GADShape
;;+ Common base type for GAD shapes.
GADShape = {
shape: SupportedGADShapes
}
;;; Point
;;+ Ellipsoid Point.
Point = {
~GADShape
point: GeographicalCoordinates
}
;;; PointUncertaintyCircle
;;+ Ellipsoid point with uncertainty circle.
PointUncertaintyCircle = {
~GADShape
point: GeographicalCoordinates
uncertainty: Uncertainty
}
;;; PointUncertaintyEllipse
;;+ Ellipsoid point with uncertainty ellipse.
PointUncertaintyEllipse = {
~GADShape
point: GeographicalCoordinates
uncertaintyEllipse: UncertaintyEllipse
confidence: Confidence
}
;;; Polygon
;;+ Polygon.
objecv5 = {
pointList: PointList
}
Polygon = {
~GADShape
pointList: PointList
}
;;; PointAltitude
;;+ Ellipsoid point with altitude.
PointAltitude = {
~GADShape
point: GeographicalCoordinates
altitude: Altitude
}
;;; PointAltitudeUncertainty
;;+ Ellipsoid point with altitude and uncertainty ellipsoid.
PointAltitudeUncertainty = {
~GADShape
point: GeographicalCoordinates
altitude: Altitude
uncertaintyEllipse: UncertaintyEllipse
uncertaintyAltitude: Uncertainty
confidence: Confidence
}
;;; EllipsoidArc
;;+ Ellipsoid Arc.
EllipsoidArc = {
~GADShape
point: GeographicalCoordinates
innerRadius: InnerRadius
uncertaintyRadius: Uncertainty
offsetAngle: Angle
includedAngle: Angle
confidence: Confidence
}
;;; GeographicalCoordinates
;;+ Geographical coordinates.
GeographicalCoordinates = {
lon: -180.0..180.0
lat: -90.0..90.0
}
;;; UncertaintyEllipse
;;+ Ellipse with uncertainty.
UncertaintyEllipse = {
semiMajor: Uncertainty
semiMinor: Uncertainty
orientationMajor: Orientation
}
;;; PointList
;;+ List of points.
PointList = [3*15 GeographicalCoordinates]
;;; Altitude
;;+ Indicates value of altitude.
Altitude = -32767.0..32767.0
;;; Angle
;;+ Indicates value of angle.
Angle = 0..360
;;; Uncertainty
;;+ Indicates value of uncertainty.
Uncertainty = float32 .ge 0
;;; Orientation
;;+ Indicates value of orientation angle.
Orientation = 0..180
;;; Confidence
;;+ Indicates value of confidence.
Confidence = 0..100
;;; InnerRadius
;;+ Indicates value of the inner radius.
InnerRadius = (0..327675)
;;; SupportedGADShapes
;;+ Indicates supported GAD shapes.
SupportedGADShapes = "POINT" / "POINT_UNCERTAINTY_CIRCLE" / "POINT_UNCERTAINTY_ELLIPSE" / "POLYGON" / "POINT_ALTITUDE" / "POINT_ALTITUDE_UNCERTAINTY" / "ELLIPSOID_ARC" / "LOCAL_2D_POINT_UNCERTAINTY_ELLIPSE" / "LOCAL_3D_POINT_UNCERTAINTY_ELLIPSOID" / text
;;; CellId
;;+ Unique identifier of a cell.
CellId = text
;;; TaId
;;+ Unique identifier of a tracking area.
TaId = text
;;; PlmnId
;;+ Unique identifier of a PLMN.
PlmnId = text
;;; MbmsSaId
;;+ Unique identifier of a MBMS serving area.
MbmsSaId = text
;;; MbsfnAreaId
;;+ Unique identifier of a MBSFN area.
MbsfnAreaId = text
B.4.1.6 Media Types
See clause B.3.1.6.
Annex C (Informative):
IANA UDP port registration form
This annex contains information to be provided to IANA for SEAL Off-network Location Management Protocol (SLMP) UDP port registration. The following information is to be used to register SLMP user port number and service name in the "IANA Service Name and Transport Protocol Port Number Registry" and specifically "Service Name and Transport Protocol Port Number Registry". This registration form can be found at: https://www.iana.org/form/ports-services.
|
Assignee Name |
<MCC name> |
|
Assignee E-mail |
<MCC email address> |
|
Contact Person |
<MCC name> |
|
Contact E-mail |
<MCC email address> |
|
Resources required |
Port number and service name |
|
Transport Protocols |
UDP |
|
Service Code |
|
|
Service Name |
SLMP |
|
Desired Port Number |
|
|
Description |
Service Enabler Architecture Layer for Verticals (SEAL) Off-network Location Management Protocol (SLMP) is a 3GPP control protocol used by a SEAL Location Management Client (SLM-C) hosted on a User Equipment (UE). SLMP facilitates the SEAL location management service functionality between SLM-C hosted on UEs communicating using IP using a single physical network segment, separated from Internet and any other IP network. The network segment is wireless network segment and UEs are mobile devices. |
|
Reference |
3GPP TS 24.545 |
|
Defined TXT keys |
N/A |
|
If broadcast/multicast is used, how and what for? |
SLMP does not used broadcast/multicast. |
|
If UDP is requested, please explain how traffic is limited, and whether the protocol reacts to congestion. |
The number of SLMP messages that need to be sent between SEAL Location Management clients (SLM-C) depends upon the number of members of the SEAL group. SLMP employs a message control mechanism which includes a back-off mechanism to defer transmission of another SLMP message once a SLMP message is received. SLMP implements a timer-based mechanism once a SLMP message is sent waiting for SLMP message response. SLMP controls the number of messages transmitted within a certain, configurable amount of time, thus averting congestion. At maximum a few SLMP messages per second are expected in communication between SLMP clients. SLMP does not support any reaction to congestion. |
|
If UDP is requested, please indicate whether the service is solely for the discovery of hosts supporting this protocol. |
SLMP is not used solely for discovery of hosts supporting this protocol. |
|
Please explain how your protocol supports versioning. |
SLMP does not support versioning. |
|
If your request is for more than one transport, please explain in detail how the protocol differs over each transport. |
N/A |
|
Please describe how your protocol supports security. Note that presently there is no IETF consensus on when it is appropriate to use a second port for an insecure version of a protocol. |
SLMP does not support security. SLMP relies on the security mechanisms of the lower layers. |
|
Please explain why a unique port assignment is necessary as opposed to a port in range (49152-65535) or existing port. |
As a general principle, 3GPP protocols use assigned User Ports, e.g. GTP-C uses UDP port number 2123, GTP-U uses UDP port number 2152, S1AP uses SCTP port number 36412, X2AP uses SCTP port number 36422, WLCP uses 36411. A dynamic port number (i.e. 49152 to 65535) cannot be used for the SLMP because of the nature of communication on a single physical network segment, separated from Internet and any other IP network. The requirement of SLMP to continuously listen for incoming messages needs an always active listener port. There is no local server that is administering the use of emphemeral ports in the SLMP architecture, so there would be no way for one SLMP client to know that a port is already being used by another SLMP client. |
|
Please explain the state of development of your protocol. |
Protocol standard definition. No implementation exists yet. |
|
If SCTP is requested, is there an existing TCP and/or UDP service name or port number assignment? If yes, provide the existing service name and port number. |
N/A |
|
What specific SCTP capability is used by the application such that a user who has the choice of both TCP (and/or UDP) and SCTP ports for this application would choose SCTP? See RFC 4960 section 7.1. |
N/A |
|
Please provide any other information that would be helpful in understanding how this protocol differs from existing assigned services |
This protocol is between the UEs communicating using IP over a single physical network segment, separated from Internet and any other IP network. SEAL location management service functionality offered by the SLM clients (SLM-C) hosted by the UEs is to support vertical applications (e.g. V2X) over the 3GPP system. The need of listening for incoming messages requires an active listener port. This differs from existing protocols in 3GPP where UDP ports have been requested, as those protocols have been either between the UE and network or between network elements. |
Annex D (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2019-10 |
CT1#120 |
C1-196855 |
Draft skeleton provided by the rapporteur. |
0.0.0 |
|||
|
2019-10 |
CT1#120 |
Implementing the following p-CRs agreed by CT1: |
0.1.0 |
||||
|
2019-11 |
CT1#121 |
Implementing the following p-CRs agreed by CT1: Corrections done by the rapporteur. |
0.2.0 |
||||
|
2020-03 |
CT1#122-e |
Implementing the following p-CRs agreed by CT1: Corrections done by the rapporteur. |
0.3.0 |
||||
|
2020-03 |
CT-87e |
CP-200169 |
Presentation to TSG CT for information andapproval |
1.0.0 |
|||
|
2020-03 |
CT-87e |
Version 16.0.0 created after approval |
16.0.0 |
||||
|
2020-06 |
CT-88e |
CP-201129 |
0001 |
B |
IANA registration template of SEAL location management |
16.1.0 |
|
|
2020-06 |
CT-88e |
CP-201129 |
0002 |
F |
Removal of editor’s note on MIME types |
16.1.0 |
|
|
2020-06 |
CT-88e |
CP-201129 |
0003 |
B |
Resolution of editor’s note on application unique ID |
16.1.0 |
|
|
2020-06 |
CT-88e |
CP-201129 |
0004 |
B |
Structure and data semantics for query list of users based on location procedure |
16.1.0 |
|
|
2020-06 |
CT-88e |
CP-201129 |
0005 |
3 |
B |
XML scheme for location reporting configuration procedure for SEAL location management |
16.1.0 |
|
2020-06 |
CT-88e |
CP-201129 |
0013 |
F |
Correction of references |
16.1.0 |
|
|
2020-06 |
CT-88e |
CP-201129 |
0014 |
F |
Resolution of the editor’s note on access token |
16.1.0 |
|
|
2020-06 |
CT-88e |
CP-201129 |
0016 |
1 |
B |
SIP based subscription procedures |
16.1.0 |
|
2020-06 |
CT-88e |
CP-201129 |
0017 |
1 |
F |
Adding required XML elements for subscription |
16.1.0 |
|
2020-06 |
CT-88e |
CP-201129 |
0018 |
1 |
B |
Timers used in location management |
16.1.0 |
|
2020-09 |
CT-89e |
CP-202163 |
0019 |
F |
Miscellaneous editorial corrections |
16.2.0 |
|
|
2020-09 |
CT-89e |
CP-202163 |
0020 |
1 |
F |
Updates to HTTP based location information subscription procedure |
16.2.0 |
|
2020-09 |
CT-89e |
CP-202163 |
0021 |
1 |
F |
Updates to XML schema of configuration for SEAL location management |
16.2.0 |
|
2020-09 |
CT-89e |
CP-202163 |
0022 |
1 |
F |
XML schema for location information report |
16.2.0 |
|
2020-09 |
CT-89e |
CP-202163 |
0023 |
F |
XML schema for location based query |
16.2.0 |
|
|
2020-09 |
CT-89e |
CP-202163 |
0024 |
1 |
F |
XML schema for location information notification |
16.2.0 |
|
2020-09 |
CT-89e |
CP-202163 |
0025 |
F |
XML schema for location information request |
16.2.0 |
|
|
2020-09 |
CT-89e |
CP-202163 |
0026 |
1 |
F |
XML schema for location information subscription |
16.2.0 |
|
2020-09 |
CT-89e |
CP-202163 |
0027 |
F |
XML schema for location reporting trigger |
16.2.0 |
|
|
2020-12 |
CT-90e |
CP-203210 |
0028 |
3 |
F |
Add the XML schema of identity |
16.3.0 |
|
2020-12 |
CT-90e |
CP-203210 |
0029 |
1 |
F |
Update to the client-triggered or VAL server-triggered location reporting procedure |
16.3.0 |
|
2020-12 |
CT-90e |
CP-203210 |
0031 |
1 |
F |
Correct location trigger configuration |
16.3.0 |
|
2021-03 |
CT-91e |
CP-210111 |
0033 |
1 |
F |
Resolution of editor’s note under clause 6.2 |
16.4.0 |
|
2021-09 |
CT-93e |
CP-212138 |
0034 |
1 |
B |
Off network Location Management – Basic Message Control and Message Format |
17.0.0 |
|
2021-09 |
CT-93e |
CP-212138 |
0035 |
1 |
B |
Off network Location Management – Event-triggered location reporting procedure |
17.0.0 |
|
2021-09 |
CT-93e |
CP-212138 |
0036 |
1 |
B |
Off network Location Management – On-demand location reporting |
17.0.0 |
|
2021-12 |
CT-94e |
CP-213052 |
0037 |
1 |
C |
Message Id and Reply-to Message Id for SEAL offnetwork location management protocol |
17.1.0 |
|
2021-12 |
CT-94e |
CP-213031 |
0039 |
– |
B |
Reference update for HTTP/1.1 protocol |
17.1.0 |
|
2022-03 |
CT-95e |
CP-220245 |
0040 |
1 |
C |
Updates to Location information subscription procedure |
17.2.0 |
|
2022-03 |
CT-95e |
CP-220245 |
0041 |
– |
B |
Location area monitoring information procedure |
17.2.0 |
|
2022-06 |
CT-96 |
CP-221198 |
0052 |
– |
A |
Fix to send HTTP POST message to SLM-C |
17.3.0 |
|
2022-06 |
CT-96 |
CP-221217 |
0042 |
– |
B |
Addition of Functional entities for CoAP |
17.3.0 |
|
2022-06 |
CT-96 |
CP-221217 |
0043 |
– |
B |
Addition of Authenticated identity for CoAP |
17.3.0 |
|
2022-06 |
CT-96 |
CP-221217 |
0044 |
– |
B |
Addition of CoAP for Event-triggered location reporting procedure |
17.3.0 |
|
2022-06 |
CT-96 |
CP-221217 |
0045 |
– |
B |
Addition of CoAP for On-demand location reporting procedure |
17.3.0 |
|
2022-06 |
CT-96 |
CP-221217 |
0047 |
– |
B |
Addition of CoAP for Location reporting triggers configuration cancel procedure |
17.3.0 |
|
2022-06 |
CT-96 |
CP-221217 |
0048 |
– |
B |
Addition of CoAP for Event-triggered location information notification procedure |
17.3.0 |
|
2022-06 |
CT-96 |
CP-221217 |
0049 |
– |
B |
Addition of CoAP for Query list of users based on location |
17.3.0 |
|
2022-06 |
CT-96 |
CP-221217 |
0050 |
– |
B |
Addition of CoAP resource representation and encoding annex |
17.3.0 |
|
2022-06 |
CT-96 |
CP-221217 |
0046 |
1 |
B |
Addition of CoAP for Client-triggered or VAL server-triggered location reporting procedure |
17.3.0 |
|
2022-09 |
CT-97e |
CP-222150 |
0053 |
1 |
F |
Addition of altitude in location co-ordinates |
17.4.0 |
|
2022-12 |
CT-98e |
CP-223123 |
0054 |
1 |
F |
IANA Registration form for UDP Port number |
17.5.0 |
|
2022-12 |
CT-98e |
CP-223123 |
0055 |
1 |
F |
Resolution of editor’s note in B.3.1.6 |
17.5.0 |