Content for TR 23.700-74 Word version: 18.0.0
1 Scope
2 References
3 Definitions of terms and abbreviations
3.1 Terms
3.2 Symbols
3.3 Abbreviations
4 Architectural Assumptions and Requirements
4.1 Architectural Assumptions
4.2 Architectural Requirements
...
...
1 Scope p. 8
The scope of this Technical Report is to study potential enhancements on generic group management, exposure and communication. Specifically, the following aspects are in the scope of the study:
-
Enhance group attribute management and group status event reporting:
- set/modify the group attributes: provisioning of service area or QoS applicable to each UE of a given group;
- subscribe to group status event reporting for the event "newly registered or (de)-registered group member".
- Study whether and how to enhance NEF exposure framework to enable capability exposure for provisioning of traffic characteristics and monitoring of performance characteristics applicable to each UE of a given group.
- Support group communication for a 5G VN, which supports multiple SMFs, including support of SMF redundancy for reliability of the 5G VN group communication.
- Whether additional mechanism or enhancement is needed and how to support group communication allowing UE to simultaneously send data to different groups, where each group has a different QoS policy (requirement regarding 5SEI as indicated in clause 6.13.2 of TS 22.261).
2 References p. 8
The following documents contain provisions, which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[3]
TS 23.502: "Procedures for the 5G system, Stage 2".
[4]
TS 23.503: "Policy and Charging Control Framework for the 5G System".
[5]
TS 22.104: "Service requirements for cyber-physical control applications in vertical domains".
[6]
TS 22.261: "Service requirements for next generation new services and markets".
[7]
TS 29.503: "5G System; Unified Data Management Services; Stage 3".
[8]
TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[9]
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[10]
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[11]
TS 29.505: "5G System; Usage of the Unified Data Repository services for Subscription Data; Stage 3".
[12]
TS 29.510: "5G System; Network function repository services; Stage 3".
[13]
TS 29.244: "Interface between the Control Plane and the User Plane nodes".
[14]
TS 23.527: "5G System; Restoration procedures".
3 Definitions of terms and abbreviations p. 9
3.1 Terms p. 9
For the purposes of the present document, the terms given in TR 21.905, in TS 23.501 and in TS 23.502 apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
The following definitions of terms are copied from TS 23.501:
5G LAN-type Service:
A service over the 5G system offering private communication using IP and/or non-IP type communications.
5G LAN-Virtual Network:
A virtual network over the 5G system capable of supporting 5G LAN-type service.
5G VN Group:
A set of UEs using private communication for 5G LAN-type service.
Private communication:
A communication between two or more UEs belonging to a restricted set of UEs.
3.2 Symbols p. 9
For the purposes of the present document, the following symbols apply:
3.3 Abbreviations p. 9
For the purposes of the present document, the abbreviations given in TR 21.905, in TS 23.501 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
5G LAN
5G Local Area Network
5G VN
5G LAN-Virtual Network
4 Architectural Assumptions and Requirements p. 9
4.1 Architectural Assumptions p. 9
The NEF exposure framework as in TS 23.501 is the baseline for study of 5G capabilities exposure for industrial and automation applications.
The QoS and policy framework as in TS 23.501 is used for enforcement of QoS applicable to each UE of a given group.
Existing QoS mechanism and service area mechanism are re-used for enforcement of service area or QoS applicable to each UE of a given group, thus neither new QoS nor service area enforcement mechanism will be specified.
Architecture and functions defined for 5G LAN-type service in clauses 4.4.6, 5.8.2.13 and 5.29 of TS 23.501 are used as the baseline for 5G VN group communication enhancements.
Unstructured PDU Session type is out of scope for this study.
4.2 Architectural Requirements p. 9
The solutions for this study will describe what kind of group the solution is targeting (e.g. 5G VN group, or a group UE identified by External Group ID, or a group UE identified Internal Group ID, or a group UE identified by address (multicast/broadcast address) or any other form of group).
