Content for TR 23.700-24 Word version: 17.1.0
6 Solutions
6.1 Solution 1: Payload size of 2048 octets in Broadcast
6.2 Solution 2: Registering MSGin5G Client to MSGin5G Server
6.3 Solution 3: MSGin5G Triggering
6.4 Solution 4: Group management using SEAL
6.5 Solution 5: MSGin5G Group messaging
6.6 Solution 6: Charging
6.7 Solution 7: MSGin5G Server message broadcast
6.8 Solution 8: Identities
6.9 Solution 9: Point to point Messaging
6.10 Solution 10: Application to point Message Exchange
6.11 Solution 11: MSGin5G Application-to-point message exchange
6.12 Solution 12: Message segmentation and reassembly
6.13 Solution 13: MSGin5G Message Segmentation and Reassembly
6.14 Solution 14: Acknowledgement of Delivery Status
6.15 Solution 15: Point to point Messaging (UE reply a message)
...
...
6 Solutions p. 41
6.1 Solution 1: Payload size of 2048 octets in Broadcast p. 41
6.1.1 Description p. 41
6.1.2 Impacts on existing nodes and functionality p. 41
6.1.3 Solution evaluation p. 41
6.2 Solution 2: Registering MSGin5G Client to MSGin5G Server p. 42
6.2.1 Description p. 42
6.2.1.1 General p. 42
6.2.1.2 MSGin5G Client Registration p. 42
6.2.1.3 MSGin5G Client De-Registration p. 44
6.2.2 Impacts on existing nodes and functionality p. 44
6.2.3 Solution evaluation p. 45
6.3 Solution 3: MSGin5G Triggering p. 45
6.3.1 Description p. 45
6.3.1.1 General p. 45
6.3.1.2 MSGin5G Triggering p. 45
6.3.2 Impacts on existing nodes and functionality p. 47
6.3.3 Solution evaluation p. 47
6.4 Solution 4: Group management using SEAL p. 47
6.4.1 General p. 47
6.4.2 Solution description for establishing a group p. 47
6.4.3 Solution description for adding UEs to the group or removing UEs from the group p. 48
6.4.4 Solution description for configuration of a maximum number of members in a group p. 48
6.4.5 Solution description for group notification interworking using SEAL p. 48
6.4.6 Solution description for SEAL enhancements to group notification interworking p. 50
6.4.7 Solution description for group list fetch using SEAL p. 51
6.4.7.1 Information Elements p. 51
6.4.7.2 Group List Fetch p. 52
6.4.8 Solution description for enhancements to control group notifications p. 53
10.3.2.22 Subscribe group configuration request p. 53
10.3.2.29 Group registration request p. 54
10.3.2.31 Identity list notification p. 55
6.4.9 Solution evaluation p. 55
6.5 Solution 5: MSGin5G Group messaging p. 55
6.5.1 Description p. 55
6.5.1.1 General p. 55
6.5.1.2 MSGin5G Group messaging p. 55
6.5.1.3 MSGin5G client sends message to group p. 57
6.5.1.4 MSGin5G client receives message from group p. 58
6.5.1.5 Legacy 3GPP message client receives message from group p. 59
6.5.1.6 Non-3GPP message client receives message from group p. 60
6.5.2 Impacts on existing nodes and functionality p. 60
6.5.3 Solution evaluation p. 60
6.6 Solution 6: Charging p. 61
6.6.1 Description p. 61
6.7 Solution 7: MSGin5G Server message broadcast p. 61
6.7.1 Description p. 61
6.7.1.1 General p. 61
6.7.1.2 MSGin5G message broadcast p. 61
6.7.2 Impacts on existing nodes and functionality p. 63
6.7.3 Solution evaluation p. 63
6.8 Solution 8: Identities p. 63
6.8.1 General p. 63
6.8.2 UE service Identity (MSGin5G service ID) p. 63
6.8.3 Application server service identity (AS service ID) p. 63
6.8.4 MSGin5G group service identity (Group service ID) p. 64
6.8.5 Message Gateway service identity (GW service ID) p. 64
6.8.6 MSGin5G UE identity (MSGin5G UE ID) p. 64
6.8.7 non-MSGin5G UE identity (non-MSGin5G UE ID) p. 64
6.8.8 Solution Evaluation p. 64
6.9 Solution 9: Point to point Messaging p. 64
6.10 Solution 10: Application to point Message Exchange p. 68
6.11 Solution 11: MSGin5G Application-to-point message exchange p. 73
6.11.1 Description p. 73
6.11.1.1 General p. 73
6.11.1.2 Client registration enhancement for Application-to-point messaging p. 73
6.11.1.3 Application Server registration p. 74
6.11.1.4 Message exchanging procedure between Application Servers and MSGin5G Client p. 75
6.11.2 Impacts on existing nodes and functionality p. 77
6.11.3 Solution evaluation p. 78
6.12 Solution 12: Message segmentation and reassembly p. 78
6.12.1 General p. 78
6.12.2 Segmentation and reassembly in point-to-point messaging p. 78
6.12.3 Segmentation and reassembly in group messaging p. 80
6.12.4 Solution Evaluation p. 80
6.13 Solution 13: MSGin5G Message Segmentation and Reassembly p. 80
6.13.1 Description p. 80
6.13.1.1 General p. 80
6.13.1.2 Application-to-point non-IMS Message Segmentation and Reassembly p. 80
6.13.1.3 Point-to-application non-IMS Message Segmentation and Reassembly p. 82
6.13.1.4 Point-to-Point non-IMS Message Segmentation and Reassembly p. 84
6.13.1.5 Group Message Segmentation and Reassembly p. 85
6.13.1.6 MSGin5G message segment recovery p. 85
6.13.2 Impacts on existing nodes and functionality p. 86
6.13.3 Solution evaluation p. 86
6.14 Solution 14: Acknowledgement of Delivery Status p. 87
6.14.1 Description p. 87
6.14.2 Impacts on existing nodes and functionality p. 87
6.14.3 Solution evaluation p. 87
6.15 Solution 15: Point to point Messaging (UE reply a message) p. 87
