B.3 Resource representation and APIs for location reporting provided by SLM-S
24.5453GPPLocation Management - Service Enabler Architecture Layer for Verticals (SEAL)Protocol specificationRelease 17TS
B.3.1 SU_LocationReporting API provided by SLM-S
B.3.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";
– the <apiVersion> shall be "v1"; and
– the <apiSpecificSuffixes> shall be set as described in clause B.3.1.2.
B.3.1.2 Resources
B.3.1.2.1 Overview
Figure B.3.1.2.1-1: Resource URI structure of the SU_LocationReporting API provided by SLM-S
Table B.3.1.2.1-1 provides an overview of the resources and applicable CoAP methods.
Table B.3.1.2.1-1: Resources and methods overview
|
Resource name |
Resource URI |
CoAP method |
Description |
|
Trigger Configuration |
/val-services/{valServiceId}/trigger-configurations |
GET |
Retrieve trigger configuration of the SLM-C for a given VAL service, according to query criteria. |
|
Location Report |
/location-reports/{valTgtUe} |
PUT |
Report location information of the SLM-C. |
|
Locations |
/locations |
FETCH |
Observe the location information of another SLM-C. |
|
GET |
Retrieve location information of another SLM-C. |
||
|
Location Area Information |
/location-area-info |
FETCH |
Query the information, e.g., user information based on the specific location area. |
B.3.1.2.2 Resource: Trigger Configurations
B.3.1.2.2.1 Description
The Trigger Configurations resource allows a SLM-C to retrieve the trigger configuration for its own from SLM-S.
B.3.1.2.2.2 Resource Definition
Resource URI: {apiRoot}/su-lr/<apiVersion>/val-services/{valServiceId}/trigger-configurations
This resource shall support the resource URI variables defined in the table B.3.1.2.2.2-1.
Table B.3.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.3.1.2.2.3 Resource Standard Methods
B.3.1.2.2.3.1 GET
This operation retrieves the trigger configuration.
This method shall support URI query options specified in table B.3.1.2.2.3.1-1, the response data structures and response codes specified in table B.3.1.2.2.3.1-1.
Table B.2.1.2.3.3.1-1: URI query options supported by the GET Request on this resource
|
Name |
Data type |
P |
Cardinality |
Description |
|
val-tgt-ue |
string |
M |
1 |
The identifier of VAL UE owns the trigger configuration. |
|
NOTE: Other request options also apply in accordance with normal CoAP procedures. |
||||
Table B.3.1.2.2.3.1-2: Data structures supported by the GET Response payload on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
LocationReportConfiguration |
M |
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.3.1.2.3 Resource: Location Reports
B.3.1.2.3.1 Description
The Location Reports resource allows a SLM-C to report its own location information to SLM-S.
B.3.1.2.3.2 Resource Definition
Resource URI: {apiRoot}/su-lr/<apiVersion>/location-reports/{valTgtUe}
This resource shall support the resource URI variables defined in the table B.3.1.2.3.2-1.
Table B.3.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.3.1.1. |
|
valTgtUe |
string |
The identifier of VAL UE owns the location information. |
B.3.1.2.3.3 Resource Standard Methods
B.3.1.2.3.3.1 PUT
This operation sends a location report.
This method shall support the request data structures specified in table B.3.1.2.3.3.1-1, the response data structures and response codes specified in table B.3.1.2.3.3.1-2.
Table B.3.1.2.3.3.1-1: Data structures supported by the PUT Request payload on this resource
|
Data type |
P |
Cardinality |
Description |
|
LocationReport |
M |
1 |
The location report to be sent. |
Table B.3.1.2.3.3.1-2: Data structures supported by the PUT Response payload on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
LocationReport |
O |
0..1 |
2.04 Changed |
The location report was created successfully. |
|
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.3.1.2.4 Resource: Locations
B.3.1.2.4.1 Description
The Locations resource allows a SLM-C to retrieve the location information of another SLM-C. This resource is observable.
B.3.1.2.4.2 Resource Definition
Resource URI: {apiRoot}/su-lr/<apiVersion>/locations
This resource shall support the resource URI variables defined in the table B.3.1.2.4.2-1.
Table B.3.1.2.4.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. |
B.3.1.2.4.3 Resource Standard Methods
B.3.1.2.4.3.1 FETCH
This operation the location information of other SLM-Cs.
This method shall support:
– the request options specified in table B.3.1.2.4.3.1-1;
– the request data structures specified in table B.3.1.2.4.3.1-2;
– the response data structures and response codes specified in table B.3.1.2.4.3.1-3; and
– the response options specified in table B.3.1.2.4.3.1-4.
Table B.3.1.2.4.3.1-1: Options supported by the FETCH Request on this resource
|
Name |
Data type |
P |
Cardinality |
Description |
|
Observe |
Uinteger |
O |
0..1 |
When set to 0 (Register) it extends the GET request to subscribe to the changes of this resource. When set to 1 (Deregister) it cancels the subscription. |
|
NOTE: Other request options also apply in accordance with normal CoAP procedures. |
||||
Table B.3.1.2.3.3.1-2: Data structures supported by the FETCH Request payload on this resource
|
Data type |
P |
Cardinality |
Description |
|
LocationReportConfiguration |
O |
0..1 |
The trigger configuration information. |
Table B.3.1.2.4.3.1-3: Data structures supported by the FETCH Response payload on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
|
array(LocationReport) |
O |
0..N |
2.05 Content |
The location information based on the request from the SLM-C. |
|
|
NOTE: The mandatory CoAP error status codes for the FETCH Request listed in table C.1.3-1 of 3GPP TS 24.546 [29] shall also apply. |
|||||
Table B.3.1.2.4.3.1-4: Options supported by the 2.05 Response Code on this resource
|
Name |
Data type |
P |
Cardinality |
Description |
|
Observe |
Uinteger |
O |
0..1 |
Sequence number of the notification. |
|
NOTE: Other response options also apply in accordance with normal CoAP procedures. |
||||
B.3.1.2.4.3.2 GET
This operation retrieves the location information of another SLM-C.
This method shall support:
– the URI query options specified in table B.3.1.2.4.3.2-1; and
– the response data structures and response codes specified in table B.3.1.2.4.3.2-2.
Table B.3.1.2.4.3.2-1: URI query options supported by the GET Request on this resource
|
Name |
Data type |
P |
Cardinality |
Description |
|
val-tgt-ue |
string |
M |
1 |
The VAL UE owns the location information. |
Table B.3.1.2.4.3.2-2: Data structures supported by the GET Response payload on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
|
LocationReport |
O |
0..1 |
2.05 Content |
The location information based on the request from 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.3.1.2.5 Resource: Location Area Information
B.3.1.2.5.1 Description
The UE Information resource allows a SLM-C to query a list of users based on a specified location from SLM-S.
B.3.1.2.5.2 Resource Definition
Resource URI: {apiRoot}/su-lr/<apiVersion>/location-area-info
This resource shall support the resource URI variables defined in the table B.3.1.2.5.2-1.
Table B.3.1.2.5.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. |
B.3.1.2.5.3 Resource Standard Methods
B.3.1.2.5.3.1 FETCH
This operation queries the relevant information based on a specific location.
This method shall support:
– the request data structures specified in table B.3.1.2.5.3.1-1; and
– the response data structures and response codes specified in table B.3.1.2.5.3.1-2.
Table B.3.1.2.5.3.1-1: Data structures supported by the FETCH Request payload on this resource
|
Data type |
P |
Cardinality |
Description |
|
LocationAreaQuery |
M |
1 |
The specific location area for query. |
Table B.3.1.2.5.3.1-2: Data structures supported by the FETCH Response payload on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
LocationAreaInfo |
O |
0..1 |
2.05 Content |
The query result was returned successfully. |
|
NOTE: The mandatory CoAP error status codes for the FETCH method listed in table C.1.3-1 of 3GPP TS 24.546 [29] shall also apply. |
||||
B.3.1.3 Data Model
B.3.1.3.1 General
Table B.3.1.3.1-1 specifies the data types defined specifically for the SU_LocationReporting API service provided by SLM-S.
Table B.3.1.3.1-1: SU_LocationReporing API provided by SLM-S 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. |
|
|
LocationAreaQuery |
B.3.1.3.2.1 |
The specific location area. |
|
|
LocationAreaInfo |
B.3.1.3.2.2 |
The location-based query result. |
|
|
UeInfo |
B.3.1.3.2.3 |
The UE information. |
Table B.3.1.3.1-2 specifies the simple data types defined specifically for the SU_LocationReporting API service provided by SLM-S.
Table B.3.1.3.1-2: SU_LocationReporing API provided by SLM-S 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.3.1.3.1-3 specifies the enumerations defined specifically for the SU_LocationReporting API service provided by SLM-S.
Table B.3.1.3.1-3: SU_LocationReporing API provided by SLM-S specific Enumeration
|
Data type |
Section defined |
Description |
|
Accuracy |
B.2.5 |
The accuracy of location information. |
B.3.1.3.2 Structured data types
B.3.1.3.2.1 Type: LocationAreaQuery
Table B.3.1.3.2.1-1: Definition of type LocationAreaQuery
|
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
|
geoArea |
GeographicArea |
M |
1 |
The specific location area. |
B.3.1.3.2.2 Type: LocationAreaInfo
Table B.3.1.3.2.2-1: Definition of type LocationAreaInfo
|
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
|
ueList |
array(UeInfo) |
M |
1 |
The list of users inside the specific location area. |
B.3.1.3.2.3 Type: UeInfo
Table B.3.1.3.2.3-1: Definition of type UeInfo
|
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
|
valTgtUe |
ValTargetUe |
M |
1 |
VAL user information. |
|
|
ueLoc |
LocationInfo |
M |
1 |
Location information of the VAL user. |
B.3.1.3.3 Simple data types and enumerations
None.
B.3.1.4 Error Handling
General error responses are defined in Annex C.1.3 of 3GPP TS 24.546 [29].
B.3.1.5 CDDL Specification
B.3.1.5.1 Introduction
The data model described in clause B.3.1.3 shall be binary encoded in the CBOR format as described in IETF RFC 8949 [26].
Clause B.3.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-S data model.
B.3.1.5.2 CDDL document
;;; LocationAreaQuery
LocationAreaQuery = {
geoArea: GeographicArea
}
;;; LocationAreaInfo
LocationAreaInfo = {
? valReqUe: ValTargetUe
? ueList: [* UeInfo]
}
;;; UeInfo
UeInfo = {
? ueId: ValTargetUe
? ueLoc: LocationInfo
}
;;; 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.
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) .and int32
;;; 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.3.1.6 Media Types
The media type for a trigger configuration or location report configuration shall be "application/vnd.3gpp.seal-location-configuration+cbor".
The media type for a location information or location report shall be "application/vnd.3gpp.seal-location-info+cbor".
The media type for a location area query shall be "application/vnd.3gpp.seal-location-area-query+cbor".
The media type for a location area information shall be "application/vnd.3gpp.seal-location-area-info+cbor".
B.3.1.7 Media Type registration for application/vnd.3gpp.seal-location-configuration+cbor
Type name: application
Subtype name: vnd.3gpp.seal-location-configuration+cbor
Required parameters: none
Optional parameters: none
Encoding considerations: Must be encoded as using IETF RFC 8949 [26]. See "LocationReportConfiguration" data type in B.2.3.2 for details.
Security considerations: See Section 10 of IETF RFC 8949 [26] and Section 11 of IETF RFC 7252 [21].
Interoperability considerations: Applications must ignore any key-value pairs that they do not understand. This allows backwards-compatible extensions to this specification.
Published specification: 3GPP TS 24.545 "Location Management – Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification", available via http://www.3gpp.org/specs/numbering.htm.
Applications that use this media type: Applications supporting the SEAL location management procedures as described in the published specification.
Fragment identifier considerations: Fragment identification is the same as specified for "application/cbor" media type in IETF RFC 8949 [26]. Note that currently that RFC does not define fragmentation identification syntax for "application/cbor".
Additional information:
Deprecated alias names for this type: N/A
Magic number(s): N/A
File extension(s): none
Macintosh file type code(s): none
Person & email address to contact for further information: <MCC name>, <MCC email address>
Intended usage: COMMON
Restrictions on usage: None
Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
Change controller: <MCC name>/<MCC email address>
B.3.1.8 Media Type registration for application/vnd.3gpp.seal-location- info+cbor
Type name: application
Subtype name: vnd.3gpp.seal-location-info+cbor
Required parameters: none
Optional parameters: none
Encoding considerations: Must be encoded as using IETF RFC 8949 [26]. See "LocationReports" data type in clause B.2.3.19 for details.
Security considerations: See Section 10 of IETF RFC 8949 [26] and Section 11 of IETF RFC 7252 [21].
Interoperability considerations: Applications must ignore any key-value pairs that they do not understand. This allows backwards-compatible extensions to this specification.
Published specification: 3GPP TS 24.545 "Location Management – Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification", available via http://www.3gpp.org/specs/numbering.htm.
Applications that use this media type: Applications supporting the SEAL location management procedures as described in the published specification.
Fragment identifier considerations: Fragment identification is the same as specified for "application/cbor" media type in IETF RFC 8949 [26]. Note that currently that RFC does not define fragmentation identification syntax for "application/cbor".
Additional information:
Deprecated alias names for this type: N/A
Magic number(s): N/A
File extension(s): none
Macintosh file type code(s): none
Person & email address to contact for further information: <MCC name>, <MCC email address>
Intended usage: COMMON
Restrictions on usage: None
Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
Change controller: <MCC name>/<MCC email address>
B.3.1.9 Media Type registration for application/vnd.3gpp.seal-location-area-query+cbor
Type name: application
Subtype name: vnd.3gpp.seal-location-area-query+cbor
Required parameters: none
Optional parameters: none
Encoding considerations: Must be encoded as using IETF RFC 8949 [26]. See "LocationAreaQuery" data type in clause B.3.1.3.2.1 for details.
Security considerations: See Section 10 of IETF RFC 8949 [26] and Section 11 of IETF RFC 7252 [21].
Interoperability considerations: Applications must ignore any key-value pairs that they do not understand. This allows backwards-compatible extensions to this specification.
Published specification: 3GPP TS 24.545 "Location Management – Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification", available via http://www.3gpp.org/specs/numbering.htm.
Applications that use this media type: Applications supporting the SEAL location management procedures as described in the published specification.
Fragment identifier considerations: Fragment identification is the same as specified for "application/cbor" media type in IETF RFC 8949 [26]. Note that currently that RFC does not define fragmentation identification syntax for "application/cbor".
Additional information:
Deprecated alias names for this type: N/A
Magic number(s): N/A
File extension(s): none
Macintosh file type code(s): none
Person & email address to contact for further information: <MCC name>, <MCC email address>
Intended usage: COMMON
Restrictions on usage: None
Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
Change controller: <MCC name>/<MCC email address>
B.3.1.10 Media Type registration for application/vnd.3gpp.seal-location-area- info+cbor
Type name: application
Subtype name: vnd.3gpp.seal-location-area-info+cbor
Required parameters: none
Optional parameters: none
Encoding considerations: Must be encoded as using IETF RFC 8949 [26]. See "LocationAreaInfo" data type in clause B.3.1.3.2.2 for details.
Security considerations: See Section 10 of IETF RFC 8949 [26] and Section 11 of IETF RFC 7252 [21].
Interoperability considerations: Applications must ignore any key-value pairs that they do not understand. This allows backwards-compatible extensions to this specification.
Published specification: 3GPP TS 24.545 "Location Management – Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification", available via http://www.3gpp.org/specs/numbering.htm.
Applications that use this media type: Applications supporting the SEAL location management procedures as described in the published specification.
Fragment identifier considerations: Fragment identification is the same as specified for "application/cbor" media type in IETF RFC 8949 [26]. Note that currently that RFC does not define fragmentation identification syntax for "application/cbor".
Additional information:
Deprecated alias names for this type: N/A
Magic number(s): N/A
File extension(s): none
Macintosh file type code(s): none
Person & email address to contact for further information: <MCC name>, <MCC email address>
Intended usage: COMMON
Restrictions on usage: None
Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
Change controller: <MCC name>/<MCC email address>