Tech-invite 3GPPspace IETFspace

21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 4‑5x

Content for TR 23.700-79 Word version: 18.0.0

0… 7…

7 Solutions p. 10

7.1 Functional architecture p. 10

7.1.1 General p. 10

7.1.2 Solution description p. 10

7.1.2.1 Functional architecture p. 10

7.1.2.2 Reference points p. 12

7.1.2.3 Media plane p. 13

7.1.3 Solution evaluation p. 14

7.2 Connection authorisation with the MC gateway UE p. 14

7.2.1 General p. 14

7.2.2 Information flows p. 14

7.2.2.1 Connection authorization request p. 14

7.2.2.2 Connection authorization response p. 15

7.2.3 MC service UE configuration data p. 15

7.2.4 Initial MC gateway UE configuration data p. 15

7.2.5 Procedure p. 16

7.2.6 Solution evaluation p. 17

7.3 Connection authorisation with an MC server via an MC gateway UE p. 17

7.3.1 General p. 17

7.3.2 Information flows p. 17

7.3.2.1 Connection authorization request p. 17

7.3.2.2 Connection authorization response p. 18

7.3.3 MC server configuration data p. 18

7.3.4 Initial MC gateway UE configuration data p. 18

7.3.5 Procedure p. 19

7.3.6 Solution evaluation p. 20

7.4 Using IMS identities behind the MC gateway UE p. 20

7.4.1 General p. 20

7.4.2 Solution description p. 20

7.4.3 Solution evaluation p. 22

7.5 Connection authorisation for non-3GPP devices that do not host an MC client p. 22

7.5.1 General p. 22

7.5.2 Information flows p. 23

7.5.2.1 Connection authorization request p. 23

7.5.2.2 Connection authorization response p. 23

7.5.3 MC server configuration data p. 23

7.5.4 Initial MC gateway UE configuration data p. 23

7.5.6 Solution evaluation p. 25

7.6 3GPP access network related location information management p. 25

7.6.1 General p. 25

7.6.2 Information flows p. 25

7.6.2.1 MC GW Location reporting configuration p. 25

7.6.2.2 MC GW Location information report p. 25

7.6.2.3 MC GW Location information request p. 26

7.6.3 Procedure p. 26

7.6.3.1 Event-triggered location reporting procedure p. 26

7.6.4.2 On-demand location reporting procedure p. 27

7.6.5.3 Location reporting cancel procedure p. 28

7.6.4 Solution evaluation p. 29

7.7 Routing of data and signalling by the MC gateway UE p. 29

7.7.1 General p. 29

7.7.2 MC client uses the IP address from the MC gateway UE p. 29

7.7.3 MC client uses an own IP address p. 30

7.7.4 Solution evaluation p. 30

7.8 MBMS Support for MC clients residing on non 3GPP devices p. 31

7.8.1 General p. 31

7.8.2 Information flows p. 31

7.8.2.1 MC GW MBMS bearer announcement p. 31

7.8.2.2 MC GW MBMS listening status report p. 31

7.8.2.3 MC GW MapGroupToBearer request p. 32

7.8.2.4 MC GW MapGroupToBearer response p. 32

7.8.2.5 MC GW MBMS bearer quality report p. 32

7.8.2.6 MC GW MBMS bearer suspension indication p. 33

7.8.3 Procedure p. 33

7.8.3.1 MBMS bearer announcement handling procedure p. 33

7.8.3.2 Procedure for handling MapGroupToBearer message p. 34

7.8.3.3 Procedure for MBMS bearer suspension notification p. 36

7.8.3.4 Procedure for reporting MBMS bearer quality p. 36

7.8.4 Solution Evaluation p. 37

8 Overall evaluation p. 37

8.1 Key issue and solution evaluation p. 37

8.1.1 Introduction p. 37

8.1.2 Results p. 38

9 Conclusions p. 38

A Gateway UE requirements p. 40

A.1 Shareable McPTT UEs and gateway UEs p. 40

A.2 Gateway requirements p. 40

$ Change history p. 41