C.2 Usage of CoAP as LWP
23.4343GPPFunctional architecture and information flowsRelease 18Service Enabler Architecture Layer for Verticals (SEAL)TS
This clause specifies how the CoAP protocol shall be used to realize the generic light-weight protocol in the signalling control plane.
The Constrained Application Protocol (CoAP) is a light-weight protocol defined by IETF in RFC 7252 [32] and designed specifically for application layer communication for constrained devices. CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity for constrained environments. RFC 7252 [32] specifies bindings to UDP and DTLS. IETF RFC 8323 [33] specifies bindings to TCP, WebSocket and TLS.
Figure C.2-1 illustrates the functional model for the LWP signalling control plane when CoAP is used as the LWP.
Figure C.2-1: Functional model for LWP signalling control plane when CoAP is used as LWP
When CoAP is used to realize the generic light-weight protocol defined in clause 6.2, then,
1. CoAP client is a realization of the LWP client
2. CoAP proxy is a realization of the LWP proxy, with the following clarifications:
a. CoAP proxy shall be able to terminate a DTLS, TLS or secure WebSocket session on LWP-1 reference point;
b. CoAP proxy shall be able to act as a cross-protocol CoAP-HTTP proxy to support LWP-HTTP-2 and LWP-HTTP-3 reference points;
3. CoAP server is a realization of the LWP server
4. CoAP supports the interactions over LWP-1, LWP-2 and LWP-3 reference points
5. The usage of CoAP by the SEAL service enablers shall follow the rules set out in clause 6.4.3.5.
Annex D (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2019-01 |
SA6#28 |
TS skeleton |
0.0.0 |
||||
|
2019-01 |
SA6#28 |
Implementation of the following pCRs approved by SA6: S6-190283, S6-190284, S6-190285, S6-190301, S6-190210, S6-190286, S6-190272, S6-190287, S6-190295, S6-190215, S6-190296, S6-190297 |
0.1.0 |
||||
|
2019-03 |
SA6#29 |
Implementation of the following pCRs approved by SA6: S6-190446, S6-190447, S6-190448, S6-190509, S6-190526, S6-190515, S6-190452, S6-190453, S6-190510, S6-190511, S6-190456, S6-190457, S6-190458 |
0.2.0 |
||||
|
2019-03 |
SA#83 |
SP-190063 |
Presentation for information at SA#83 |
1.0.0 |
|||
|
2019-04 |
SA6#30 |
Implementation of the following pCRs approved by SA6: S6-190661, S6-190663, S6-190848, S6-190746, S6-190747, S6-190748, S6-190749, S6-190750, S6-190872 |
1.1.0 |
||||
|
2019-05 |
SA6#31 |
Implementation of the following pCRs approved by SA6: S6-191003, S6-191115, S6-191005, S6-191116, S6-191117, S6-191007, S6-191189, S6-191212, S6-191121, S6-191012, S6-191229, S6-191191, S6-191124, S6-191013, S6-191192, S6-191193 |
1.2.0 |
||||
|
2019-05 |
SA#84 |
SP-190473 |
Presentation for Approval at SA#84 |
2.0.0 |
|||
|
2019-06 |
SA#84 |
SP-190473 |
MCC Editorial update for publication after TSG SA approval (SA#84) |
16.0.0 |
|||
|
2019-09 |
SA#85 |
SP-190733 |
0001 |
2 |
F |
Architecture requirements group management |
16.1.0 |
|
2019-09 |
SA#85 |
SP-190733 |
0002 |
3 |
F |
Group announcement and join |
16.1.0 |
|
2019-09 |
SA#85 |
SP-190733 |
0003 |
6 |
F |
Corrections to network resource management procedures |
16.1.0 |
|
2019-09 |
SA#85 |
SP-190733 |
0004 |
F |
N5 reference point description |
16.1.0 |
|
|
2019-09 |
SA#85 |
SP-190733 |
0006 |
1 |
F |
Change of service-based interface representation of the functional model for SEAL |
16.1.0 |
|
2019-09 |
SA#85 |
SP-190733 |
0007 |
F |
Remove EN on bearer type identification |
16.1.0 |
|
|
2019-09 |
SA#85 |
SP-190733 |
0008 |
F |
Remove EN on granularity of decision of NRM server |
16.1.0 |
|
|
2019-12 |
SA#86 |
SP-191111 |
0009 |
1 |
F |
Corrections to naming and other fixes |
16.2.0 |
|
2019-12 |
SA#86 |
SP-191111 |
0010 |
2 |
F |
Result element missing |
16.2.0 |
|
2019-12 |
SA#86 |
SP-191111 |
0011 |
1 |
F |
Anonymous requests |
16.2.0 |
|
2019-12 |
SA#86 |
SP-191111 |
0012 |
1 |
F |
No multicast resource management in 5GS |
16.2.0 |
|
2019-12 |
SA#86 |
SP-191111 |
0013 |
2 |
F |
Mention of SA3 responsibility in a published TS is not relevant. |
16.2.0 |
|
2019-12 |
SA#86 |
SP-191111 |
0014 |
2 |
F |
SEAL APIs corrections |
16.2.0 |
|
2019-12 |
SA#86 |
SP-191111 |
0015 |
1 |
F |
Update to location configuration procedure |
16.2.0 |
|
2020-03 |
SA#87-E |
SP-200114 |
0016 |
F |
Complete SS_NetworkResourceAdaptation API |
16.3.0 |
|
|
2020-03 |
SA#87-E |
SP-200114 |
0017 |
F |
Correct dynamic MBMS bearer establishment |
16.3.0 |
|
|
2020-03 |
SA#87-E |
SP-200114 |
0019 |
F |
MBMS procedures alignment |
16.3.0 |
|
|
2020-07 |
SA#88-E |
SP-200338 |
0021 |
1 |
F |
Align the Group Management API operation name with CT3 |
16.4.0 |
|
2020-07 |
SA#88-E |
SP-200338 |
0022 |
2 |
F |
Clarification and correction on media direction mode |
16.4.0 |
|
2020-09 |
SA#89-E |
SP-200841 |
0023 |
2 |
F |
Correct location trigger configuration |
16.5.0 |
|
2020-09 |
SA#89-E |
SP-200841 |
0024 |
1 |
F |
Clarifications on MBMS listening status uage |
16.5.0 |
|
2020-09 |
SA#89-E |
SP-200841 |
0025 |
2 |
F |
Correct SEAL location API operations |
16.5.0 |
|
2020-09 |
SA#89-E |
SP-200841 |
0026 |
1 |
F |
Correction to NRM unicast procedures |
16.5.0 |
|
2020-12 |
SA#90-E |
SP-200991 |
0029 |
1 |
F |
Clarification on group join notification |
16.6.0 |
|
2020-12 |
SA#90-E |
SP-200991 |
0030 |
1 |
F |
Resolution of ENs on security aspects |
16.6.0 |
|
2020-12 |
SA#90-E |
SP-200991 |
0033 |
1 |
F |
Clarifications for T8 interface |
16.6.0 |
|
2020-12 |
SA#90-E |
SP-200991 |
0036 |
1 |
F |
Correction to location notification to VAL server |
16.6.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0027 |
3 |
B |
Tracking UE and obtaining dynamic UE information |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0031 |
2 |
B |
Support local MBMS |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200999 |
0032 |
2 |
B |
Network slice adaptation for VAL applications |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200999 |
0034 |
1 |
F |
Clarifications for T8 interface |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200999 |
0035 |
1 |
B |
Temporary Groups formation |
17.0.0 |
|
2021-04 |
SA#91-E |
SP-210181 |
0038 |
3 |
B |
Service identification in location management procedures |
17.1.0 |
|
2021-04 |
SA#91-E |
SP-210181 |
0039 |
2 |
B |
Group management support for 5G-VN groups |
17.1.0 |
|
2021-04 |
SA#91-E |
SP-210181 |
0040 |
2 |
B |
Add location criteria to group creation request |
17.1.0 |
|
2021-04 |
SA#91-E |
SP-210181 |
0042 |
1 |
B |
Update to LMS server APIs |
17.1.0 |
|
2021-04 |
SA#91-E |
SP-210181 |
0044 |
B |
Enhancement of information flows to add VAL service specific information |
17.1.0 |
|
|
2021-04 |
SA#91-E |
SP-210181 |
0045 |
1 |
B |
Service identification in location management procedures |
17.1.0 |
|
2021-06 |
SA#92-E |
SP-210484 |
0037 |
3 |
B |
Network Slice Capability Management functional model |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210484 |
0043 |
3 |
B |
Off-network location management |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210485 |
0047 |
1 |
B |
Location report timestamp support |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210484 |
0049 |
2 |
F |
Update to GMS APIs |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210484 |
0051 |
2 |
B |
SEAL support for CoAP |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210484 |
0052 |
1 |
B |
Resolve EN for group management |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210484 |
0053 |
1 |
B |
Coordinated QoS/resource management for network-assisted UE-to-UE communications |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210484 |
0054 |
1 |
B |
Group list fetch procedure |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210484 |
0055 |
1 |
B |
Group management enhancements |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210485 |
0056 |
4 |
B |
SEAL Location Deviation Service |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210485 |
0057 |
1 |
B |
SEAL Event Monitoring Service |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210484 |
0058 |
1 |
B |
Requirements for Location management service |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210485 |
0059 |
B |
Supplementary location information to verticals |
17.2.0 |
|
|
2021-06 |
SA#92-E |
SP-210485 |
0060 |
2 |
B |
add VAL UE Information to configuration management procedure |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210483 |
0062 |
1 |
A |
Complete resource reservation with PCC procedure |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210484 |
0063 |
1 |
F |
QoS Monitoring support |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210484 |
0064 |
2 |
B |
Unified support for TSC/TSN services |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210484 |
0065 |
2 |
B |
SEAL enable 5G CN capabilities for SEAL groups |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210485 |
0066 |
2 |
B |
SEAL Location Deviation Service Information flows and APIs |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210484 |
0067 |
1 |
B |
API and information flow description for Temporary groups |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210483 |
0069 |
1 |
A |
Fixing the descriptions of IEs in Information flows for location information |
17.2.0 |
|
2021-09 |
na |
na |
0043 |
3 |
B |
Editorial re-application of CR0043r3 "Off-network location management" |
17.3.0 |
|
2021-09 |
SA#93-E |
SP-210964 |
0075 |
2 |
C |
Improved Event Monitoring Service |
17.3.0 |
|
2021-09 |
SA#93-E |
SP-210964 |
0076 |
2 |
B |
Utilize NEF location service for SEAL LM |
17.3.0 |
|
2021-09 |
SA#93-E |
SP-210964 |
0078 |
5 |
B |
Updates to Location based Group |
17.3.0 |
|
2021-09 |
SA#93-E |
SP-210964 |
0079 |
2 |
F |
Support for TSC services procedures |
17.3.0 |
|
2021-09 |
SA#93-E |
SP-210964 |
0080 |
1 |
F |
Support for TSN services procedures |
17.3.0 |
|
2021-09 |
SA#93-E |
SP-210964 |
0081 |
1 |
B |
Unicast QoS monitoring data retrieval |
17.3.0 |
|
2021-12 |
SA#94-E |
SP-211525 |
0082 |
1 |
F |
Corrections to network slice adaptation |
17.4.0 |
|
2021-12 |
SA#94-E |
SP-211521 |
0083 |
1 |
F |
Group Deletion procedure |
17.4.0 |
|
2021-12 |
SA#94-E |
SP-211525 |
0084 |
1 |
F |
Replace the NSCM with NSCE to align the terminologies |
17.4.0 |
|
2021-12 |
SA#94-E |
SP-211525 |
0086 |
1 |
F |
Removal of PCP from TSC stream discovery |
17.4.0 |
|
2021-12 |
SA#94-E |
SP-211525 |
0087 |
F |
Add missing location area monitoring API |
17.4.0 |
|
|
2022-03 |
SA#95-E |
SP-220101 |
0087 |
F |
Clarify the VAL UE ID |
17.5.0 |
|
|
2022-03 |
SA#95-E |
SP-220101 |
0092 |
1 |
F |
Correct QoS monitoring service |
17.5.0 |
|
2022-03 |
SA#95-E |
SP-220101 |
0093 |
F |
Correct TSC stream availability discovery |
17.5.0 |
|
|
2022-03 |
SA#95-E |
SP-220102 |
0091 |
1 |
B |
Complete location retrieval in an area |
18.0.0 |
|
2022-06 |
SA#96 |
SP-220473 |
0097 |
2 |
A |
Minor essential corrections to TS 23.434 |
18.1.0 |
|
2022-06 |
SA#96 |
SP-220473 |
0101 |
A |
Minor corrections on network resource management for 5G TSC |
18.1.0 |
|
|
2022-06 |
SA#96 |
SP-220473 |
0103 |
2 |
A |
QoS monitoring clarification |
18.1.0 |
|
2022-09 |
SA#97-E |
SP-220925 |
0104 |
3 |
B |
SEAL Notification Management service – Functional Model |
18.2.0 |
|
2022-09 |
SA#97-E |
SP-220925 |
0105 |
3 |
B |
SEAL Notification Management service – Information Flows and Procedures |
18.2.0 |
|
2022-09 |
SA#97-E |
SP-220920 |
0108 |
1 |
A |
EN resolution for network slice adaptation request |
18.2.0 |
|
2022-09 |
SA#97-E |
SP-220925 |
0110 |
1 |
B |
Establishing communication with service requirements |
18.2.0 |
|
2022-09 |
SA#97-E |
SP-220925 |
0111 |
2 |
B |
Information flows and procedures to maintain notification channel |
18.2.0 |
|
2022-09 |
SA#97-E |
SP-220925 |
0112 |
1 |
B |
Update_Unicast_QoS_Monitoring_Subscription operation in the SS_NetworkResourceMonitoring API |
18.2.0 |
|
2022-09 |
SA#97-E |
SP-220920 |
0115 |
2 |
A |
Correction on location management information flow |
18.2.0 |
|
2022-09 |
SA#97-E |
SP-220925 |
0116 |
B |
Update the scope and reference to support 5MBS |
18.2.0 |
|
|
2022-09 |
SA#97-E |
SP-220925 |
0117 |
2 |
B |
Update the requirement to support 5MBS |
18.2.0 |
|
2022-09 |
SA#97-E |
SP-220925 |
0118 |
1 |
B |
Update the NRM functional model to support 5MBS |
18.2.0 |
|
2022-09 |
SA#97-E |
SP-220925 |
0119 |
1 |
B |
MBS session creation and MBS session announcement |
18.2.0 |
|
2022-09 |
SA#97-E |
SP-220925 |
0120 |
2 |
B |
Updating MBS resources for group communications |
18.2.0 |
|
2022-09 |
SA#97-E |
SP-220925 |
0121 |
1 |
B |
MBS session deletion |
18.2.0 |
|
2022-09 |
SA#97-E |
SP-220925 |
0122 |
B |
Activate or de-activate multicast MBS sessions |
18.2.0 |
|
|
2022-09 |
SA#97-E |
SP-220925 |
0123 |
B |
Group media transmissions over 5G MBS sessions |
18.2.0 |
|
|
2022-09 |
SA#97-E |
SP-220925 |
0124 |
B |
Application level control signalling over 5G MBS sessions |
18.2.0 |
|
|
2022-12 |
SA#98-E |
SP-221244 |
0106 |
9 |
B |
VAL Server provisioning |
18.3.0 |
|
2022-12 |
SA#98-E |
SP-221244 |
0126 |
2 |
B |
Update the NSCE functional |
18.3.0 |
|
2022-12 |
SA#98-E |
SP-221244 |
0127 |
2 |
B |
Enhance the APIs of the network slice adaptation |
18.3.0 |
|
2022-12 |
SA#98-E |
SP-221249 |
0129 |
B |
Update to SEAL architecture to include SEALDD |
18.3.0 |
|
|
2022-12 |
SA#98-E |
SP-221244 |
0130 |
1 |
F |
Definition of MBS session announcement |
18.3.0 |
|
2022-12 |
SA#98-E |
SP-221244 |
0131 |
1 |
B |
Information flows for MBS procedures |
18.3.0 |
|
2022-12 |
SA#98-E |
SP-221244 |
0133 |
1 |
B |
Updating MBS with dynamic PCC |
18.3.0 |
|
2022-12 |
SA#98-E |
SP-221244 |
0134 |
2 |
B |
NRM coordination for redundant PDU Session establishment |
18.3.0 |
|
2022-12 |
SA#98-E |
SP-221244 |
0136 |
2 |
B |
VAL service area identifier usage |
18.3.0 |
|
2022-12 |
SA#98-E |
SP-221244 |
0137 |
F |
Add Cause IE to NSCE information flows |
18.3.0 |
|
|
2022-12 |
SA#98-E |
SP-221244 |
0138 |
2 |
F |
ADAE functional model in SEAL architecture |
18.3.0 |
|
2022-12 |
SA#98-E |
SP-221244 |
0139 |
2 |
F |
Service continuity between 5G MBS delivery and unicast delivery |
18.3.0 |
|
2022-12 |
SA#98-E |
SP-221244 |
0140 |
3 |
B |
VAL service inter-system switching between 5G and LTE |
18.3.0 |
|
2022-12 |
SA#98-E |
SP-221244 |
0141 |
1 |
B |
VAL service over 5GS supporting EPS interworking |
18.3.0 |