Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 23.768
Word version: 12.1.0
1…
4…
4
Assumptions and architectural requirements
5
Key Issues
6
Solutions
7
Evaluation
8
Conclusions
A
QoS and bearer parameters for Group Communications
$
Change History
4
Assumptions and architectural requirements
p. 8
4.1
General
p. 8
4.2
High-level reference diagram
p. 9
4.3
Reference points
p. 10
4.4
Assumptions
p. 10
4.5
Architectural requirements
p. 10
5
Key Issues
p. 10
5.1
Key Issue #1: Decision point for using PtP and/or PtM
p. 10
5.1.1
General description
p. 10
5.1.2
Group Privacy considerations for PtP/PtM decision
p. 10
5.2
Key Issue #2: GCSE_LTE interaction with ProSe UE-to-Network Relays
p. 11
5.2.1
General description
p. 11
5.3
Key Issue #3: Group Communication with geographical scope
p. 11
5.3.1
General description
p. 11
5.4
Key Issue #4: MuSe with additional media handling
p. 12
5.4.1
General description
p. 12
5.5
Key Issue #5: Service continuity
p. 12
5.5.1
General description
p. 12
5.6
Key Issue #6: Roaming support
p. 12
5.6.1
General description
p. 12
5.7
Key Issue #7: Interworking
p. 12
5.7.1
General description
p. 12
5.8
Key Issue #8: Priority and Pre-emption on Group Communication
p. 13
5.8.1
General description
p. 13
6
Solutions
p. 13
6.1
Solution 1 - Group Communications using pre-established eMBMS bearers
p. 13
6.1.1
Functional description
p. 13
6.1.1.1
Solution description
p. 13
6.1.1.2
Architecture reference model
p. 14
6.1.2
Procedures
p. 15
6.1.2.1
Group Communication Setup using pre-established eMBMS bearers
p. 15
6.1.2.2
Service continuity during unicast and MBMS switching
p. 16
6.1.2.2.1
General
p. 16
6.1.2.2.2
Switching from MBMS to unicast - make-before-break
p. 16
6.1.2.2.3
Switching from MBMS to unicast - Non make-before-break
p. 18
6.1.2.2.4
Switching from unicast to MBMS
p. 19
6.1.3
Impact on existing entities and interfaces
p. 20
6.1.4
Solution evaluation
p. 20
6.2
Solution 2 - GCSE AS counting of UEs per group per cell
p. 20
6.2.1
Functional description
p. 20
6.2.2
Procedures
p. 20
6.2.3
Impact on existing entities and interfaces
p. 21
6.2.4
Solution evaluation
p. 22
6.3
Solution 3 - Group Communications with MuSe (eNB centric)
p. 22
6.3.0
Overview
p. 22
6.3.1
Functional description
p. 23
6.3.2
Procedures
p. 24
6.3.2.1
Multicast Delivery Setup
p. 24
6.3.2.2
MuSe and Mobility handling
p. 25
6.3.2.3
MuSe with voice and video media handling
p. 26
6.3.3
Impact on existing entities and interfaces
p. 28
6.3.4
Solution evaluation
p. 28
6.4
Solution 4 - GCSE architecture using IMS and eMBMS
p. 28
6.4.1
Functional description
p. 28
6.4.1.1
Solution description
p. 28
6.4.1.2
Architecture reference model
p. 29
6.4.2
Procedures
p. 29
6.4.2.1
General
p. 29
6.4.2.2
GCSE group communication procedures
p. 29
6.4.2.2.1
Switching from unicast to eMBMS delivery for an ongoing GCSE group communication session
p. 29
6.4.2.3
GCSE Group membership procedures
p. 31
6.4.2.3.1
Subscribing to a GCSE group
p. 31
6.4.2.3.2
UE joining Group Communication
p. 31
6.4.3
Impact on existing entities and interfaces
p. 31
6.4.4
Solution evaluation
p. 31
6.5
Solution 5 - Group communications with pre-established MBMS broadcast Bearers and multicast/unicast switching
p. 31
6.5.1
Functional description
p. 31
6.5.2
Procedures
p. 33
6.5.3
Impact on existing entities and interfaces
p. 36
6.5.4
Solution evaluation
p. 36
6.6
Solution 6: MuSe with configurable geographic scope
p. 36
6.6.1
General description
p. 36
6.6.2
Procedures
p. 36
6.6.2.1
Group Communication within configured Geographic Service Area
p. 36
6.6.2.2
Group Communication with geographic service area override and filtering
p. 38
6.6.3
Impact on existing entities and interfaces
p. 40
6.6.4
Solution evaluation
p. 40
6.7
Solution 7: Assign and Re-assign Priority and Pre-emption capability for the GC
p. 40
6.7.1
Solution description
p. 40
6.7.1.1
General
p. 40
6.7.1.2
Session Setup Procedure
p. 40
6.7.1.3
Session update Procedure
p. 41
6.7.1.4
Session Release Procedure
p. 41
6.7.2
Impact on existing entities and interfaces
p. 41
6.7.3
Solution evaluation
p. 42
6.8
Solution 8: Service continuity from unicast to multicast delivery
p. 42
6.8.1
Functional Description
p. 42
6.8.2
Procedures
p. 42
6.8.3
Impact on existing entities and interfaces
p. 44
6.8.4
Solution evaluation
p. 44
6.9
Solution 9: Group Management and associated user interaction
p. 44
6.9.1
UE and GCSE AS roles and requirements
p. 44
6.9.2
Group management not at BM-SC level
p. 44
6.9.3
Solution evaluation
p. 45
6.10
Solution 10: Using pre-established eMBMS bearers as generic multicast delivery bearer
p. 45
6.10.1
Solution evaluation
p. 46
6.11
Solution 11: Scalability above the SGi reference
p. 46
6.11.1
Functional Description
p. 46
6.11.2
Impact on existing entities and interfaces
p. 46
6.11.3
Solution evaluation
p. 47
7
Evaluation
p. 47
7.1
Common approach
p. 47
7.1.1
GC2
p. 48
7.1.1.1
Information exchanged between GCSE AS and BM-SC
p. 48
7.1.1.2
GC2 procedure
p. 48
7.1.1.3
Control plane and User plane of GC2
p. 49
7.1.2
Roaming Architecture
p. 49
7.1.3
Call flows and procedures
p. 51
7.1.3.1
Downlink Media path setup for multipoint service
p. 51
7.1.3.1.1
General
p. 51
7.1.3.1.2
Pre-established eMBMS bearers
p. 51
7.1.3.1.3
Dynamic eMBMS bearers
p. 51
7.1.3.2
Media Traffic using unicast and eMBMS on DL
p. 52
7.1.3.3
Service continuity procedures between unicast and multipoint service
p. 52
7.1.3.3.1
Unicast to eMBMS
p. 52
7.1.3.3.2
eMBMS to Unicast
p. 52
7.2
GCSE_LTE common solution approach with respect to Group Management considerations
p. 53
7.2.1
Analysis of GCSE related contexts
p. 53
7.2.2
Key considerations
p. 53
8
Conclusions
p. 55
8.1
General
p. 55
8.2
Priority and Pre-emption on Group Communication
p. 56
A
QoS and bearer parameters for Group Communications
p. 58
A.1
General
p. 58
A.2
Overview
p. 58
A.3
Draft Changes to TS 23.203 v12.3.0
p. 58
$
Change History
p. 63