| |
Figure 5.4-1 | MCData on-network architecture showing the unicast and MBMS delivery paths |
Figure 5.11-1 | IP connectivity model |
Figure 6.4.1-1 | Generic application plane functional model |
Figure 6.4.2-1 | Functional model for application plane of off-network MCData service |
Figure 6.5.1-1 | Application plane functional model for SDS |
Figure 6.5.2-1 | Application plane functional model for SDS |
Figure 6.6.1-1 | Application plane functional model for file distribution |
Figure 6.6.1a-1 | Application plane functional model for file distribution |
Figure 6.6.2-1 | Application plane functional model for FD |
Figure 6.7.1-1 | Application plane functional model for data streaming |
Figure 6.8.1-1 | Application plane functional model for IP connectivity |
Table 7.3.5.2.1-1 | MBMS user service announcement |
Figure 7.3.5.3.1.2-1 | Use of pre-established MBMS user service |
Figure 7.3.5.3.2-1 | Use of dynamic MBMS user service establishment |
Figure 7.3.5.3.3.2-1 | File fetching by the MCData server for file distribution over MBMS |
Figure 7.3.5.3.3.3-1 | File fetching by the BM-SC for file distribution over MBMS |
Figure 7.3.6.2.1-1 | Group communication connect on MBMS bearer |
Figure 7.3.6.2.2-1 | Group communication disconnect on MBMS bearer |
Table 7.4.2.1.1-1 | MCData standalone data request (MCData client to MCData server) |
Table 7.4.2.1.1-2 | MCData standalone data request (MCData server to MCData client) |
Table 7.4.2.1.2-1 | MCData data disposition notification |
Table 7.4.2.1.3-1 | MCData standalone session data request (MCData client to MCData server) |
Table 7.4.2.1.3-2 | MCData standalone session data request (MCData server to MCData client) |
Table 7.4.2.1.4-1 | MCData standalone session data response |
Table 7.4.2.1.5-1 | MCData session data request (MCData client to MCData server) |
Table 7.4.2.1.5-2 | MCData session data request (MCData server to MCData client) |
Table 7.4.2.1.6-1 | MCData session data response |
Table 7.4.2.1.7-1 | MCData group standalone data request (MCData client - MCData server) |
Table 7.4.2.1.8-1 | MCData group standalone data request (MCData server - MCData client) |
Table 7.4.2.1.9-1 | MCData data disposition notification(s) (MCData server - MCData client) |
Table 7.4.2.1.9A-1 | MCData aggregated data disposition notification |
Table 7.4.2.1.10-1 | MCData group session standalone data request (MCData client - MCData server) |
Table 7.4.2.1.11-1 | MCData group session standalone data request (MCData server - MCData client) |
Table 7.4.2.1.12-1 | MCData group session standalone data response |
Table 7.4.2.1.13-1 | MCData group data request (MCData client - MCData server) |
Table 7.4.2.1.14-1 | MCData group data request (MCData server - MCData client) |
Table 7.4.2.1.15-1 | MCData group data response |
Table 7.4.2.1.16-1 | MCData one-to-one SDS communication upgrade request |
Table 7.4.2.1.17-1 | MCData one-to-one SDS communication upgrade response |
Table 7.4.2.1.18-1 | MCData group SDS communication upgrade request (MCData client to MCData server) |
Table 7.4.2.1.18-2 | MCData group SDS communication upgrade request (MCData server to MCData client) |
Table 7.4.2.1.19-1 | MCData group SDS communication upgrade response |
Table 7.4.2.1.20-1 | MCData group SDS communication in-progress priority state cancel request (MCData client to MCData server) |
Table 7.4.2.1.20-2 | MCData group SDS communication in-progress priority state cancel request (MCData server to MCData client) |
Table 7.4.2.1.21-1 | MCData group SDS communication in-progress priority state cancel response |
Table 7.4.2.1.22-1 | MCData functional alias resolution response information elements |
Figure 7.4.2.2.2-1 | One-to-one standalone short data service using signalling control plane |
Figure 7.4.2.3.2-1 | One-to-one standalone short data service using media plane |
Figure 7.4.2.4.2-1 | One-to-one short data service session |
Figure 7.4.2.5.2-1 | Group standalone SDS using signalling control plane |
Figure 7.4.2.6.2-1 | Group standalone SDS using media plane |
Figure 7.4.2.7.2-1 | Group SDS session |
Figure 7.4.2.8.2-1 | MCData one-to-one SDS communication upgraded to MCData emergency one-to-one SDS communication |
Figure 7.4.2.9.2-1 | MCData group SDS communication upgraded to MCData emergency group SDS communication |
Figure 7.4.2.10.2-1 | MCData group SDS in-progress emergency group state cancel |
Figure 7.4.2.13.2-1 | Providing data for a user entering an ongoing MCData group conversation |
Table 7.4.3.2.1-1 | MCData standalone data request |
Table 7.4.3.2.2-1 | MCData data disposition notification |
Table 7.4.3.2.3-1 | MCData group standalone data request |
Figure 7.4.3.3.2-1 | One-to-one standalone short data service using signalling control plane |
Figure 7.4.3.4.2-1 | Group standalone short data service using signalling control plane |
Figure 7.4.3.6.2-1 | Group standalone short data service with MCData message store |
Table 7.5.2.1.1-1 | MCData upload data request |
Table 7.5.2.1.2-1 | MCData upload data response |
Table 7.5.2.1.3-1 | MCData download data request |
Table 7.5.2.1.4-1 | MCData download data response |
Table 7.5.2.1.5-1 | MCData FD request (using HTTP) from MCData client to MCData server |
Table 7.5.2.1.5-2 | MCData FD request (using HTTP) from MCData server to MCData client |
Table 7.5.2.1.5-3 | MCData FD request (using HTTP) from MCData server to MCData client |
Table 7.5.2.1.6-1 | MCData FD response (using HTTP) |
Table 7.5.2.1.7-1 | MCData download completed report |
Table 7.5.2.1.7A-1 | MCData aggregated download completed report |
Table 7.5.2.1.8-1 | MCData FD request (using media plane/MCData client to MCData server) |
Table 7.5.2.1.8-2 | MCData FD request (using media plane/MCData server to MCData server) |
Table 7.5.2.1.8-3 | MCData FD request (using media plane/MCData server to MCData client) |
Table 7.5.2.1.9-1 | MCData FD response (using media plane) |
Table 7.5.2.1.10-1 | MCData group standalone FD request (using HTTP) from MCData client to MCData server |
Table 7.5.2.1.10-2 | MCData group standalone FD request (using HTTP) from MCData server to MCData client |
Table 7.5.2.1.11-1 | MCData group standalone FD response (using HTTP) |
Table 7.5.2.1.12-1 | MCData group standalone FD request (using media plane/MCData client to MCData server) |
Table 7.5.2.1.12-2 | MCData group standalone FD request (using media plane/MCData server to MCData client) |
Table 7.5.2.1.13-1 | MCData group standalone FD response (using media plane) |
Table 7.5.2.1.14-1 | MCData remove file request |
Table 7.5.2.1.15-1 | MCData remove file response |
Table 7.5.2.1.19-1 | MCData file retrieve request |
Table 7.5.2.1.20-1 | MCData file retrieve response |
Table 7.5.2.1.21-1 | MCData group standalone FD over MBMS request |
Table 7.5.2.1.22-1 | MCData one-to-one FD upgrade request |
Table 7.5.2.1.23-1 | MCData one-to-one FD upgrade response |
Table 7.5.2.1.24-1 | MCData group FD upgrade request (MCData client to MCData server) |
Table 7.5.2.1.24-2 | MCData group FD upgrade request (MCData server to MCData client) |
Table 7.5.2.1.25-1 | MCData group FD upgrade response |
Table 7.5.2.1.26-1 | MCData group FD in-progress priority state cancel request (MCData client to MCData server) |
Table 7.5.2.1.26-2 | MCData group FD in-progress priority state cancel request (MCData server to MCData client) |
Table 7.5.2.1.27-1 | MCData group FD in-progress priority state cancel response information elements |
Table 7.5.2.1.28-1 | MCData file upload request |
Table 7.5.2.1.29-1 | MCData file upload response |
Table 7.5.2.1.30-1 | MCData file upload completion status |
Table 7.5.2.1.31-1 | MCData file download request |
Table 7.5.2.1.32-1 | MCData file download response |
Table 7.5.2.1.33-1 | MCData file availability request |
Table 7.5.2.1.34-1 | MCData file availability response |
Figure 7.5.2.2.2-1 | Uploading of the file residing in MCData UE using HTTP |
Figure 7.5.2.2.3-1 | Uploading of the file residing in MCData message store using HTTP |
Figure 7.5.2.2.4-1 | File upload using HTTP over network resources with required QoS |
Figure 7.5.2.3.2-1 | File download using HTTP |
Figure 7.5.2.3.3-1 | File download using HTTP over network resources with required QoS |
Figure 7.5.2.4.2-1 | One-to-one file distribution using HTTP |
Figure 7.5.2.4.3-1 | One-to-one file distribution using HTTP with interconnection |
Figure 7.5.2.5.2-1 | One-to-one file distribution using media plane |
Figure 7.5.2.6.2-1 | Group standalone FD using HTTP |
Figure 7.5.2.7.2-1 | Group standalone FD using media plane |
Figure 7.5.2.8.2-1 | File removal using HTTP by authorised user |
Figure 7.5.2.8.3-1 | File removal using HTTP by authorized user |
Figure 7.5.2.10.2-1 | Group standalone FD using the MBMS download delivery method |
Figure 7.5.2.11.2-1 | One-to-one FD communication upgrade to an emergency one-to-one FD communication |
Figure 7.5.2.12.2-1 | MCData group FD communication upgraded to an MCData emergency group FD communcation |
Figure 7.5.2.13.2-1 | MCData group FD in-progress emergency group state cancel |
Table 7.5.3.2.1-1 | MCData FD request (using media plane) |
Table 7.5.3.2.2-1 | MCData FD response (using media plane) |
Table 7.5.3.2.3-1 | MCData download completed report |
Table 7.5.3.2.4-1 | MCData group standalone FD request (using media plane) |
Table 7.5.3.2.5-1 | MCData group standalone FD response (using media plane) |
Figure 7.5.3.3.2-1 | One-to-one standalone file distribution using media plane |
Figure 7.5.3.4.2-1 | Group standalone file distribution using media plane |
Table 7.6.2.1.1-1 | MCData control indication |
Table 7.6.2.1.2-1 | MCData indication |
Table 7.6.2.1.3-1 | MCData get deferred list request |
Table 7.6.2.1.4-1 | MCData get deferred list response |
Figure 7.6.2.2.2-1 | Automatic transmission for SDS |
Figure 7.6.2.3.2-1 | Send data with mandatory download |
Figure 7.6.2.4.2-1 | Send data without mandatory download |
Figure 7.6.2.5.2-1 | Accessing list of deferred data group communications |
Table 7.7.2.1.1-1 | MCData communication release request (one-to-one communication using media plane) |
Table 7.7.2.1.2-1 | MCData communication release response (one-to-one communication using media plane) |
Table 7.7.2.1.3-1 | MCData communication release request (group communication using media plane) |
Table 7.7.2.1.4-1 | MCData communication release response (group communication using media plane) |
Table 7.7.2.1.8-1 | MCData server communication release request (one-to-one communication using media plane) |
Table 7.7.2.1.9-1 | MCData server communication release response (one-to-one communication using media plane) |
Table 7.7.2.1.10-1 | MCData server communication release request (group communication using media plane) |
Table 7.7.2.1.11-1 | MCData server communication release response (group communication using media plane) |
Table 7.7.2.1.13-1 | MCData release intent request (one-to-one communication using media plane) |
Table 7.7.2.1.14-1 | MCData more information response (one-to-one communication using media plane) |
Table 7.7.2.1.15-1 | MCData release intent request (group communication using media plane) |
Table 7.7.2.1.16-1 | MCData more information response (group communication using media plane) |
Table 7.7.2.1.17-1 | MCData auth user communication release request (one-to-one communication using media plane) |
Table 7.7.2.1.18-1 | MCData auth user communication release response (one-to-one communication using media plane) |
Table 7.7.2.1.19-1 | MCData auth user communication release request (group communication using media plane) |
Table 7.7.2.1.20-1 | MCData auth user communication release response (group communication using media plane) |
Table 7.7.2.1.21-1 | MCData request for extension |
Table 7.7.2.1.22-1 | MCData response for extension |
Figure 7.7.2.2.2.2-1 | Release of MCData communication using media plane |
Figure 7.7.2.3.2.2-1 | MCData server initiated release of MCData communication using media plane |
Figure 7.7.2.4.2-1 | MCData server initiates communication release with prior indication |
Figure 7.7.2.5.2-1 | An authorized MCData user initiates communication release without prior indication |
Figure 7.7.2.6.2-1 | An authorized MCData user initiates communication release with prior indication |
Figure 7.8.2.2.1-1 | One-to-one conversation management |
Figure 7.8.2.3.1-1 | Group conversation management |
Figure 7.8.3.1.1-1 | One-to-one conversation management |
Figure 7.8.3.2.1-1 | Group conversation management |
Figure 7.9.3.1.1-1 | Sharing enhanced status information |
Figure 7.9.4.1.1-1 | Sharing enhanced status information |
Figure 7.11-1 | MCData user authentication and registration, single domain |
Figure 7.13.1 | Message store structure |
Table 7.13.3.1.1-1 | MCData retrieve a stored object request |
Table 7.13.3.1.2-1 | MCData retrieve a stored object response |
Table 7.13.3.1.3-1 | MCData search stored objects request |
Table 7.13.3.1.4-1 | MCData search stored objects response |
Table 7.13.3.1.5-1 | MCData update a stored object request |
Table 7.13.3.1.6-1 | MCData update a stored object response |
Table 7.13.3.1.7-1 | MCData delete a stored object request |
Table 7.13.3.1.8-1 | MCData delete a stored object response |
Table 7.13.3.1.9-1 | MCData synchronization request |
Table 7.13.3.1.10-1 | MCData synchronization response |
Table 7.13.3.1.11-1 | MCData create a user account request |
Table 7.13.3.1.12-1 | MCData create a user account response |
Table 7.13.3.1.13-1 | MCData deposit an object request |
Table 7.13.3.1.14-1 | MCData deposit an object response |
Table 7.13.3.1.15-1 | MCData copy a stored object request |
Table 7.13.3.1.16-1 | MCData copy a stored object response |
Table 7.13.3.1.17-1 | MCData move a stored object request |
Table 7.13.3.1.18-1 | MCData move a stored object response |
Table 7.13.3.1.19-1 | MCData create folder request |
Table 7.13.3.1.20-1 | MCData create folder response |
Table 7.13.3.1.21-1 | MCData delete folder request |
Table 7.13.3.1.22-1 | MCData delete folder response |
Table 7.13.3.1.23-1 | MCData copy folder request |
Table 7.13.3.1.24-1 | MCData copy folder response |
Table 7.13.3.1.25-1 | MCData move folder request |
Table 7.13.3.1.26-1 | MCData move folder response |
Table 7.13.3.1.27-1 | MCData list folder request |
Table 7.13.3.1.28-1 | MCData list folder response |
Table 7.13.3.1.29-1 | MCData upload objects request |
Table 7.13.3.1.30-1 | MCData upload objects response |
Table 7.13.3.1.31-1 | MCData synchronization notification |
Table 7.13.3.1.32-1 | Create notification channel request |
Table 7.13.3.1.33-1 | Create notification channel response |
Table 7.13.3.1.34-1 | Open notification channel request |
Table 7.13.3.1.35-1 | Subscribe for notification request |
Table 7.13.3.1.36-1 | Subscribe for notification response |
Table 7.13.3.1.37-1 | MCData search folder request |
Table 7.13.3.1.38-1 | MCData search folder response |
Table 7.13.3.1.39-1 | MCData retrieve folder content request |
Table 7.13.3.1.40-1 | MCData retrieve folder content response |
Table 7.13.3.1.41-1 | MCData retrieve file to store locally request |
Table 7.13.3.1.42-1 | MCData retrieve file to store locally response |
Table 7.13.3.1.43 | Update notification channel request |
Table 7.13.3.1.44 | Update notification channel response |
Table 7.13.3.1.45 | Update notification subscription request |
Table 7.13.3.1.46 | Update notification subscription response |
Table 7.13.3.1.47 | Delete notification channel request |
Table 7.13.3.1.48 | Delete notification channel response |
Table 7.13.3.1.49 | Delete notification subscription request |
Table 7.13.3.1.50 | Delete notification subscription response |
Table 7.13.3.1.51-1 | Notification message |
Figure 7.13.3.2.2-1 | Retrieve a stored object |
Figure 7.13.3.3.2-1 | Search stored objects |
Figure 7.13.3.4.2-1 | Update a stored object |
Figure 7.13.3.5.2-1 | Delete a stored object |
Figure 7.13.3.6.2-1 | Synchronization |
Figure 7.13.3.7.2-1 | Create a user account |
Figure 7.13.3.8.2-1 | Deposit an object |
Figure 7.13.3.9.2-1 | Copy a stored object |
Figure 7.13.3.10.2-1 | Move a stored object |
Figure 7.13.3.11.2-1 | Create a new user folder |
Figure 7.13.3.12.2-1 | Delete a user folder |
Figure 7.13.3.13.2-1 | Copy a user folder |
Figure 7.13.3.14.2-1 | Move a user folder |
Figure 7.13.3.15.2-1 | Folder list operation |
Figure 7.13.3.16.2-1 | Upload objects |
Figure 7.13.3.17.2-1 | Notify client to synchronize using in-band connection |
Figure 7.13.3.17.3-1 | Notify client to synchronize through MCData notification server |
Figure 7.13.3.17.3-2 | Update a notification channel |
Figure 7.13.3.17.3-3 | Delete a notification channel |
Figure 7.13.3.18.2-1 | Search folder |
Figure 7.13.3.19.2-1 | retrieve folder content |
Figure 7.13.3.20.3-1 | store file contents distributed using HTTP - receiver side |
Figure 7.13.4.2-1 | Generic outgoing SDS procedure with MCData message store |
Figure 7.13.5.2-1 | Generic incoming SDS procedure with MCData message store |
Table 7.14.2.1.1-1 | MCData IPcon point-to-point request (MCData client to MCData server) |
Table 7.14.2.1.1-2 | MCData IPcon point-to-point request (MCData server to MCData client) |
Table 7.14.2.1.2-1 | MCData IPcon point-to-point response |
Table 7.14.2.1.3-1 | MCData remote IPcon point-to-point request |
Table 7.14.2.1.4-1 | MCData remote IPcon point-to-point response |
Table 7.14.2.1.5-1 | MCData remote IPcon point-to-point tear down request |
Table 7.14.2.1.6-1 | MCData remote IPcon point-to-point tear down response |
Table 7.14.2.1.7-1 | MCData remote IPcon point-to-point application priority change request |
Table 7.14.2.1.8-1 | MCData remote IPcon point-to-point application priority change response |
Figure 7.14.2.2.2-1 | Establishment of a point-to-point IP connectivity |
Figure 7.14.2.3.2-1 | Establishment of a remote point-to-point IP connectivity |
Figure 7.14.2.4.2-1 | Remote initiated tear down of a point-to-point IP connectivity |
Figure 7.14.2.5.2-1 | Point-to-point IP connectivity application priority change request by a remote MCData client |
Figure 7.14.2.6.2-1 | Establishment of IPcon group standalone communication session |
Table 7.17.2.1-1 | Ad hoc group data session request information elements |
Table 7.17.2.2-1 | Ad hoc group data session request return information elements |
Table 7.17.2.3-1 | Ad hoc group data session request information elements |
Table 7.17.2.4-1 | Ad hoc group data session request information elements |
Table 7.17.2.5-1 | Ad hoc group data session response information elements |
Table 7.17.2.6-1 | Ad hoc group data session response information elements |
Table 7.17.2.7-1 | Ad hoc group data session response information elements |
Table 7.17.2.8-1 | Ad hoc group data session release request information elements |
Table 7.17.2.8a-1 | Ad hoc group data session release request information elements |
Table 7.17.2.9-1 | Ad hoc group data session release response information elements |
Table 7.17.2.9a-1 | Ad hoc group data session release response information elements |
Table 7.17.2.10-1 | Ad hoc group data session notify |
Table 7.17.2.11-1 | Modify ad hoc group data session participants request |
Table 7.17.2.12-1 | Modify Ad hoc group data session participants response information elements |
Table 7.17.2.13-1 | Ad hoc group data session leave request information elements |
Table 7.17.2.13a-1 | Ad hoc group data session leave request information elements |
Table 7.17.2.14-1 | Ad hoc group data session leave response information elements |
Table 7.17.2.14a-1 | Ad hoc group data session leave response information elements |
Table 7.17.2.15-1 | Ad hoc group data session get userlist |
Table 7.17.2.16-1 | Ad hoc group data session get userlist response |
Table 7.17.2.17-1 | Ad hoc group data session add user notification information elements |
Table 7.17.2.18-1 | Ad hoc group data session remove user notification information elements |
Table 7.17.2.19-1 | Ad hoc group data session release notification information elements |
Table 7.17.2.20-1 | Modify ad hoc group data session criteria request |
Table 7.17.2.20a-1 | Modify ad hoc group data session criteria request |
Table 7.17.2.21-1 | Modify Ad hoc group data session criteria response information elements |
Table 7.17.2.21a-1 | Modify Ad hoc group data session criteria response information elements |
Figure 7.17.3.1.1-1 | Ad hoc group data communication setup |
Figure 7.17.3.1.2-1 | Release ad hoc group data communication by the MCData server |
Figure 7.17.3.1.2a-1 | Release ad hoc group data communication by an authorized user |
Figure 7.17.3.1.3-1 | Ad hoc group data communication participants determined by MCData server |
Figure 7.17.3.1.4-1 | Modification of ad hoc group data communication participants by an authorized user |
Figure 7.17.3.1.5-1 | Modification of ad hoc group data communication participants by the MCData server |
Figure 7.17.3.1.6-1 | Modification of ad hoc group data communication criteria by an authorized user |
Figure 7.17.3.2.1-1 | Ad hoc group data communication setup |
Figure 7.17.3.2.2-1 | Ad hoc group data communication release |
Figure 7.17.3.2.3-1 | Ad hoc group data communication setup involving multiple MCData systems |
Figure 7.17.3.2.4-1 | Modification of ad hoc group data communication participants by the MCData server |
Figure 7.17.3.2.5-1 | MCData server releases an ad hoc group data communication and stops the determination of ad hoc group data communication participants involving multiple MCData systems |
Figure 7.17.3.2.6-1 | Modification of ad hoc group data communication participants by an authorized user |
Figure 7.17.3.2.7-1 | Modifying the criteria for determining the participants during an ongoing ad hoc group data session between multiple MC systems |
Table 7.17.4.2-1 | short data service specific |
Figure 7.17.4.3.2-1 | Ad hoc group SDS data communication session |
Figure 7.17.4.4.2-1 | Ad hoc group SDS data communication session |
Table 7.17.5.2-1 | file distribution specific |
Figure 7.17.5.3.2-1 | Ad hoc group SDS data communication session |
Figure 7.17.5.4.2-1 | Ad hoc group FD data communication session |
Table 7.17.6.1.1-1 | Determine ad hoc group request (MCData client - MCData server) |
Table 7.17.6.1.2-1 | Determine ad hoc group response information elements |
Table 7.17.6.1.3-1 | Ad hoc group standalone data request (MCData client - MCData server) |
Table 7.17.6.1.4-1 | Ad hoc group standalone data request (MCData server - MCData client) |
Table 7.17.6.1.5-1 | Ad hoc group standalone data get userlist |
Table 7.17.6.1.6-1 | Ad hoc group standalone data get userlist response |
Figure 7.17.6.2.1-1 | Determine ad hoc group and preconfigured group |
Figure 7.17.6.3.2-1 | Ad hoc group standalone short data service involving single MCData system |
Figure 7.17.6.4.2-1 | Ad hoc group standalone short data service involving multiple MCData system |
Table 7.17.7.1.1-1 | Ad hoc group standalone FD request |
Table 7.17.7.1.2-1 | Ad hoc group standalone FD request |
Table 7.17.7.1.3-1 | Ad hoc group standalone FD request return information elements |
Table 7.17.7.1.4-1 | Ad hoc group standalone FD response |
Figure 7.17.7.2.2-1 | Ad hoc group standalone file distribution involving single MCData system |
Figure 7.17.7.3.2-1 | Ad hoc group standalone file distribution involving multiple MCData system |
Table A.2-1 | UE configuration data (on and off network) |
Table A.2-2 | UE configuration data (on network) |
Table A.3-1 | MCData user profile configuration data (on and off network) |
Table A.3-2 | MCData user profile configuration data (on network) |
Table A.3-3 | MCData user profile configuration data (off network) |
Table A.4-1 | Group configuration data (on and off network) |
Table A.4-2 | Group configuration data (on network) |
Table A.4-3 | Group configuration data (off network) |
Table A.5-1 | MCData service configuration data (on and off network) |
Table A.5-2 | MCData service configuration data (on network) |
Table A.5-3 | MCData service configuration data (off network) |
Figure B.1-1 | Transmission control process |
Figure D-1 | User message storage area example |