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-38 Word version: 18.0.0

1… 5…

5.1 Key issue 1: functional architecture 5.2 Key issue 2 - Identification 5.3 Key issue 3 - Change user configuration 5.4 Key issue 4 - Group configuration data 5.5 Key issue 5 - Service configuration data 5.6 Key issue 6: authorization 5.7 Key issue 7: Secure exchange and topology hiding 7.1 Common ACM procedure 7.2 Mapping of solutions to key issues 7.3 Solution #1: Functional architecture 7.4 Solution #2: Enhancement to the MC service functional architecture 7.5 Solution #3: ACMC authorisation 7.6 Solution #4: Group configuration change 7.7 Solution #5: Request to add users for migration to a partner MC system 7.8 Solution #6: Request to remove users for migration from a partner MC system 7.9 Solution #7: Update MC service UE initial configuration 7.10 Solution #8: MC service user profile update request while receiving MC service from a partner MC system 7.11 Solution #9: Provide Interconnection Group IDs

5 Key issues p. 10

5.1 Key issue 1: functional architecture p. 10

5.2 Key issue 2 - Identification p. 11

5.3 Key issue 3 - Change user configuration p. 11

5.4 Key issue 4 - Group configuration data p. 11

5.5 Key issue 5 - Service configuration data p. 11

5.6 Key issue 6: authorization p. 12

5.7 Key issue 7: Secure exchange and topology hiding p. 12

6 Architecture requirements p. 12

6.1 General p. 12

6.2 Requirements p. 13

6.2.1 General p. 13

6.2.1.1 Description p. 13

6.2.1.2 Requirements p. 13

6.2.2 User and group authorization p. 13

6.2.2.1 Description p. 13

6.2.2.2 Requirements p. 13

6.2.3 User and group MC service registration p. 14

6.2.3.1 Description p. 14

6.2.3.2 Requirements p. 14

6.2.4 Information and selection of available group communication p. 14

6.2.4.1 Description p. 14

6.2.4.2 Requirements p. 14

6.2.5 Profiles for visiting MC service users p. 14

6.2.5.1 Description p. 14

6.2.5.2 Requirements p. 15

7 Solutions p. 15

7.1 Common ACM procedure p. 15

7.1.1 Pending requests p. 15

7.1.1.1 Solution description p. 15

7.1.1.1.1 General p. 15

7.1.1.1.2 Information flows p. 15

7.1.1.1.3 Procedure p. 16

7.1.1.2 Solution evaluation p. 17

7.1.2 Processing incoming requests automatically p. 17

7.1.2.1 Solution description p. 17

7.1.2.1.1 General p. 17

7.1.2.1.2 Automation performed by ACM server p. 17

7.1.2.1.3 Automation performed by automated ACM client p. 18

7.1.2.2 Solution evaluation p. 18

7.2 Mapping of solutions to key issues p. 19

7.3 Solution #1: Functional architecture p. 19

7.3.1 Solution description p. 19

7.3.1.1 General p. 19

7.3.1.2 Functional model p. 19

7.3.1.3 Functional entities description p. 20

7.3.2 Solution evaluation p. 20

7.4 Solution #2: Enhancement to the MC service functional architecture p. 20

7.4.1 Solution description p. 20

7.4.2 Functional model description p. 20

7.4.3 On-network functional model p. 20

7.4.4 Administrative configuration management client p. 21

7.4.5 Administrative configuration management server p. 22

7.4.6 Administrative configuration management server and client in a primary MC system and partner MC system p. 22

7.4.7 Solution evaluation p. 22

7.5 Solution #3: ACMC authorisation p. 22

7.5.1 Solution description p. 22

7.5.1.1 Overview p. 22

7.5.1.1a User profile configurations for using ACMX p. 23

7.5.1.2 ACMX authorisation for an authorised user p. 23

7.5.2 Solution evaluation p. 24

7.6 Solution #4: Group configuration change p. 24

7.6.1 Solution description p. 24

7.6.1.1 General p. 24

7.6.1.2 Procedure p. 25

7.6.1.2.1 Group membership update by authorized user from a partner MC system p. 25

7.6.2 Solution evaluation p. 27

7.7 Solution #5: Request to add users for migration to a partner MC system p. 27

7.7.1 Solution description p. 27

7.7.1.1 General p. 27

7.7.1.2 Information flows p. 27

7.7.1.2.1 User configuration request p. 27

7.7.1.2.2 User configuration response p. 28

7.7.1.3 Procedure p. 29

7.7.2 Solution evaluation p. 31

7.8 Solution #6: Request to remove users for migration from a partner MC system p. 31

7.8.1 Solution description p. 31

7.8.1.2 Information flows p. 31

7.8.1.2.1 Remove user configuration request p. 31

7.8.1.2.2 Remove user configuration response p. 32

7.8.1.3 Remove user configuration request from a partner MC system p. 32

7.8.2 Solution evaluation p. 34

7.9 Solution #7: Update MC service UE initial configuration p. 34

7.9.1 Solution description p. 34

7.9.1.1 General p. 34

7.9.1.2 Information flows p. 35

7.9.1.2.1 Update MC service UE initial configuration p. 35

7.9.1.2.2 Update MC service UE initial configuration response p. 35

7.9.1.3 Procedure p. 35

7.9.2 Solution evaluation p. 37

7.10 Solution #8: MC service user profile update request while receiving MC service from a partner MC system p. 37

7.10.1 Solution description p. 37

7.10.1.1 General p. 37

7.10.1.2 Information flows p. 38

7.10.1.2.1 MC service user profile update request p. 38

7.10.1.2.2 MC service user profile update response p. 38

7.10.1.3 Procedure p. 38

7.10.2 Solution evaluation p. 40

7.11 Solution #9: Provide Interconnection Group IDs p. 40

7.11.1 Solution description p. 40

7.11.1.1 General p. 40

7.11.1.2 Information flows p. 40

7.11.1.2.1 Group information provision request p. 40

7.11.1.2.2 Group information provision response p. 41

7.11.1.3 Procedure p. 41

7.11.1.3.1 Authorized user providing interconnection group ID(s) to authorized user of a partner MC system p. 41

7.11.2 Solution evaluation p. 43

8 Evaluation p. 44

8.1 Overview p. 44

8.2 Overall evaluation of key issue#1 p. 44

8.3 Overall evaluation of key issue#2 p. 44

8.4 Overall evaluation of key issue#3 p. 44

8.5 Overall evaluation of key issue#4 p. 45

8.6 Overall evaluation of key issue#5 p. 45

8.7 Overall evaluation of key issue#6 p. 45

8.8 Overall evaluation of key issue#7 p. 45

9 Conclusions p. 45

$ Change history p. 46