hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.8.4.1.2 Reference point MCData-IPcon-2 (unicast between the U-IPcon distribution function and the U-IPcon function)
| MCData-IPcon-2 reference point carries bidirectional IP Data for point-to-point MCData IP connectivity over the media plane between the IPcon distribution function of the MCData server and the IPcon function of the MCData client(s).
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.8.4.1.3 Reference point MCData-IPcon-3 (multicast between the IPcon distribution function and the IPcon function)
| MCData-IPcon-3 reference point carries downlink unidirectional IP Data over the media plane between the IPcon distribution function of the MCData server and the IPcon function of the MCData client(s).
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.8.4.2 Signalling control plane
| The description of the signalling control plane reference points is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5].
6A Identities
The MCData service specific identities (e.g. MCData ID, MCData group ID) are described in clause 8 of 3GPP TS 23.280 [5].
6B App... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7 Procedures and information flows
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.1 MCData service configuration
| The MCData service shall support the procedures and related information flows as specified in subclause 10.1 and Annex A of 3GPP TS 23.280 [5] with the following clarifications:
- The MC service client is the MCData client;
- The MC service server is the MCData server;
- The MC service ID is the MCData ID; and
- Th... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.2 Affiliation and de-affiliation to/from MCData group(s)
| The MCData service shall support the procedures and related information flows as specified in subclause 10.8 of 3GPP TS 23.280 [5] with the following clarifications:
- The MC service client is the MCData client;
- The MC service server is the MCData server;
- The MC service group is the MCData group;
- The MC servi... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3 Use of MBMS transmission (on-network)
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.1 Information flows for MBMS Transmission
| Information flows for generic MBMS procedures are defined in 3GPP TS 23.280 [5].
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.2 Use of pre-established MBMS bearers
| The MCData service shall support the procedure for using pre-established MBMS bearers as specified in 3GPP TS 23.280 [5] with the following clarifications:
- The MC service client is the MCData client;
- The MC service server is the MCData server; and
- The MC service ID is the MCData ID.
The MCData service shall u... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.3 Use of dynamic MBMS bearer establishment
| The MCData service shall support the procedure for using dynamic MBMS bearers as specified 3GPP TS 23.280 [5] with the following clarifications:
- The MC service client is the MCData client;
- The MC service server is the MCData server; and
- The MC service ID is the MCData ID.
The MCData service shall use the MCDa... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.4 Switching from MBMS bearer to unicast bearer
| The MCData service shall support the procedure for switching from MBMS bearer to unicast bearer as specified 3GPP TS 23.280 [5] with the following clarifications:
- The MC service client is the MCData client;
- The MC service server is the MCData server; and
- The MC service ID is the MCData ID.
The MCData service ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.5 Use of MBMS user services for file distribution
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.5.1 General
| This subclause defines information flows and procedures for usage of MBMS user services that applies to MCData file distribution. MBMS user services can be used for any MC service group.
The MBMS user service architecture is described in 3GPP TS 26.346 [21].
NOTE: The current specification does not cover MCData end-t... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.5.2 Information flows for MBMS user service usage
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.5.2.1 MBMS user service announcement
| Table 7.3.5.2.1-1 describes the information flow MBMS bearer announcement from the MCData server to the MCData client.
Table 7.3.5.2.1-1: MBMS user service announcement
Information element
Status
Description
MBMS user service id
M
Id of the MBMS user service
SA file
M
The service announcement file as returned... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.5.3 Procedures for MBMS user service usage
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.5.3.1 Use of pre-established MBMS user services
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.5.3.1.1 General
| In this scenario, the MCData server pre-establishes MBMS user service(s) in certain pre-configured areas before the initiation of a group file distribution. When a user originates a request for a file distribution in one of these areas, the MCData server can use the pre-established MBMS user service(s) for the DL media... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.5.3.1.2 Procedure
| Editor's note: The procedure in this clause needs to be revised considering that MBMS user services, as specified in 3GPP TS 26.346 [21], cannot be supported over the MB2 interface.
The procedure figure 7.3.5.3.1.2-1 shows only one of the receiving MCData clients using an MBMS user service.
Pre-conditions:
- The pa... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.5.3.2 Use of dynamic MBMS user service establishment
| Editor's note: The procedure in this clause needs to be revised considering that MBMS user services, as specified in 3GPP TS 26.346 [21], cannot be supported over the MB2 interface.
In this scenario depicted in figure 7.3.5.3.2-1, the MCData server decides to establish an MBMS user service for the distribution of a gi... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.5.3.3 Providing stored files in the MCData content server for distribution over MBMS
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.5.3.3.1 General
| As described in clause 6.6.3.1.5, the MCData content server provides a repository area where authorized MCData users temporarily store files that are intended to be shared with other MCData users. The distribution of such files targeting a group of MCData users can be performed over MBMS.
For the case that the MBMS us... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.5.3.3.2 File fetching by the MCData server
| A file can be fetched by the MCData server from the MCData content server over the MCData-FD-5 reference point using the file URL provided by MCData users. The MCData server, thus, enables via the xMB‑U interface that the file is ingested, either by pull or push, into the BM‑SC for distribution over MBMS.
NOTE 1: The ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.5.3.3.3 File fetching by the BM‑SC
| When the MCData server defines a pull ingest mode, the MCData server can alternatively provide to the BM‑SC the resource location in the MCData content server (i.e. the file URL contained within the received file distribution request). The BM‑SC, thus, will directly fetch the file from the MCData content server.
NOTE ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.6 Group communication connect and disconnect over MBMS bearer procedures
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.6.1 General
| MBMS bearer can be used for MCData group communication. One MBMS bearer is not permanently associated to one specific group or group communication. Before sending data packets of a group communication over MBMS bearer, the MCData server shall send the association information between group communication and the MBMS bea... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.6.2 Procedure
| The procedure in this clause uses an establishment of group communication as described in clause 7.4.2.7. Similary, the procedure defined in this clause is also applicable for the group communication established as described in clause 7.4.2.6.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.6.2.1 Group communication connect over MBMS bearer
| Pre-conditions:
- The MCData clients 1 to n are registered and affiliated to the same MCData group X.
- The MCData server has decided to use an MBMS bearer for the MCData service group communication associated with to the MCData group X.
Figure 7.3.6.2.1-1: Group communication connect on MBMS bearer.
1. Activat... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.3.6.2.2 Group communication disconnect from MBMS bearer
| Figure 7.3.6.2.2-1 shows the high level procedure where an UnmapGroupFromBearer message is sent by the MCData server to the MCData clients to indicate that the MCData group communication is being dissociated from the MBMS bearer.
Figure 7.3.6.2.2-1: Group communication disconnect on MBMS bearer.
1. The MC group com... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4 Short data service
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.1 General
| There are several procedures how an SDS message can be transported from the sender to the recipient. All of the following factors are used by MCData client for selecting appropriate SDS procedures:
- Whether the data to transfer is within or outside the SDS data size limit to transport over signalling control plane;
... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2 Short data service for on-network
| The procedures described in the following subclauses are limited to single MCData system only.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1 Information flows for short data service
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.1 MCData standalone data request
| Table 7.4.2.1.1-1 describes the information flow for the MCData standalone data request sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.4.2.1.1-1: MCData standalone data request (MCData client to MCData server)
Information element
Status
Description
MCD... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.2 MCData data disposition notification
| Table 7.4.2.1.2-1 describes the information flow for the MCData data disposition notification sent from the MCData client to the MCData server.
Table 7.4.2.1.2-1: MCData data disposition notification
Information element
Status
Description
MCData ID
M
The identity of the MCData user towards which the notification... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.3 MCData standalone session data request
| Table 7.4.2.1.3-1 describes the information flow for the MCData standalone session data request sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.4.2.1.3-1: MCData standalone session data request (MCData client to MCData server)
Information element
Status
... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.4 MCData standalone session data response
| Table 7.4.2.1.4-1 describes the information flow for the MCData standalone session data response sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.4.2.1.4-1: MCData standalone session data response
Information element
Status
Description
MCData ID
M
The ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.5 MCData session data request
| Table 7.4.2.1.5-1 describes the information flow for the MCData session data request sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.4.2.1.5-1: MCData session data request (MCData client to MCData server)
Information element
Status
Description
MCData ID... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.6 MCData session data response
| Table 7.4.2.1.6-1 describes the information flow for the MCData session data response sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.4.2.1.6-1: MCData session data response
Information element
Status
Description
MCData ID
M
The identity of the MCData... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.7 MCData group standalone data request (MCData client – MCData server)
| Table 7.4.2.1.7-1 describes the information flow for the MCData group standalone data request (in subclause 7.4.2.5.2) sent from the MCData client to the MCData server.
Table 7.4.2.1.7-1: MCData group standalone data request (MCData client – MCData server)
Information element
Status
Description
MCData ID
M
The i... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.8 MCData group standalone data request (MCData server – MCData client)
| Table 7.4.2.1.8-1 describes the information flow for the MCData group standalone data request (in subclause 7.4.2.5.2) sent from the MCData server to the MCData client.
Table 7.4.2.1.8-1: MCData group standalone data request (MCData server – MCData client)
Information element
Status
Description
MCData ID
M
The i... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.9 MCData data disposition notification (MCData server – MCData client)
| Table 7.4.2.1.9-1 describes the information flow for the MCData data disposition notification(s) sent from the MCData server to the MCData client.
Table 7.4.2.1.9-1: MCData data disposition notification(s) (MCData server – MCData client)
Information element
Status
Description
MCData ID
M
The identity of the MCDa... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.10 MCData group session standalone data request (MCData client – MCData server)
| Table 7.4.2.1.10-1 describes the information flow for the MCData group session standalone data request (in subclause 7.4.2.6.2) sent from the MCData client to the MCData server.
Table 7.4.2.1.10-1: MCData group session standalone data request (MCData client – MCData server)
Information element
Status
Description
M... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.11 MCData group session standalone data request (MCData server – MCData client)
| Table 7.4.2.1.11-1 describes the information flow for the MCData group session standalone data request (in subclause 7.4.2.6.2) sent from the MCData server to the MCData client.
Table 7.4.2.1.11-1: MCData group session standalone data request (MCData server – MCData client)
Information element
Status
Description
M... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.12 MCData group session standalone data response
| Table 7.4.2.1.12-1 describes the information flow for the MCData group standalone data response (in subclause 7.4.2.6.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.4.2.1.12-1: MCData group session standalone data response
Information element
Status
... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.13 MCData group data request (MCData client – MCData server)
| Table 7.4.2.1.13-1 describes the information flow for the MCData group data request sent from the MCData client to the MCData server.
Table 7.4.2.1.13-1: MCData group data request (MCData client – MCData server)
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending data
Func... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.14 MCData group data request (MCData server – MCData client)
| Table 7.4.2.1.14-1 describes the information flow for the MCData group data request sent from the MCData server to the MCData client.
Table 7.4.2.1.14-1: MCData group data request (MCData server – MCData client)
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending data
Func... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.15 MCData group data response
| Table 7.4.2.1.15-1 describes the information flow for the MCData group data response sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.4.2.1.15-1: MCData group data response
Information element
Status
Description
MCData ID
M
The identity of the MCData u... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.16 MCData one-to-one SDS communication upgrade request
| Table 7.4.2.1.16-1 describes the information flow for the MCData one-to-one SDS communication upgrade request sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.4.2.1.16-1: MCData one-to-one SDS communication upgrade request
Information element
Status
Descr... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.17 MCData one-to-one SDS communication upgrade response
| Table 7.4.2.1.17-1 describes the information flow for the MCData one-to-one SDS communication upgrade response sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.4.2.1.17-1: MCData one-to-one SDS communication upgrade response
Information element
Status
Des... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.18 MCData group SDS communication upgrade request
| Table 7.4.2.1.18-1 describes the information flow for the MCData group SDS communication upgrade request sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.4.2.1.18-1: MCData group SDS communication upgrade request (MCData client to MCData server)
Information... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.19 MCData group SDS communication upgrade response
| Table 7.4.2.1.19-1 describes the information flow for the MCData group SDS communication upgrade response sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.4.2.1.19-1: MCData group SDS communication upgrade response
Information element
Status
Description
... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.20 MCData group SDS communication in-progress priority state cancel request
| Table 7.4.2.1.20-1 describes the information for the MCData group SDS communication in-progress priority state cancel request sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.4.2.1.20-1: MCData group SDS communication in-progress priority state cancel reques... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.21 MCData group SDS communication in-progress priority state cancel response
| Table 7.4.2.1.21-1 describes the information flow for the MCData group SDS communication in-progress priority state cancel response sent from the MCData server to the MCData client.
Table 7.4.2.1.21-1: MCData group SDS communication in-progress priority state cancel response
Information Element
Status
Description
... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.1.22 MCData functional alias resolution response
| Table 7.4.2.1.22-1 describes the information flow MCData functional alias resolution response from the MCData server to the MCData client.
Table 7.4.2.1.22-1: MCData functional alias resolution response information elements
Information Element
Status
Description
MCData ID
M
The identity of the MCData user sendin... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.2 One-to-one standalone short data service using signalling control plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.2.1 General
| A MCData user initiates a standalone SDS data transfer with another MCData user. For the SDS data transfer signalling plane is used. The target MCData user may be addressed using the functional alias that can be shared with other MCData users.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.2.2 Procedure
| The procedure in figure 7.4.2.2.2-1 describes the case where an MCData user is initiating one-to-one MCData data communication for sending standalone SDS data to other MCData user, with or without disposition request. Standalone refers to sending unidirectional data in one transaction.
Pre-conditions:
1. The SDS payl... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.3 One-to-one standalone short data service using media plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.3.1 General
| A MCData user initiates a standalone SDS data transfer with another MCData user. For the SDS data transfer media plane is used. The target MCData user may be addressed using the functional alias that can be shared with other MCData users.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.3.2 Procedure
| The procedure in figure 7.4.2.3.2-1 describes the case where an MCData user is initiating one-to-one MCData data communication for sending standalone SDS data to other MCData user, with or without disposition request. Standalone refers to sending unidirectional data in one transaction. The SDS payload data size is assu... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.4 One-to-one short data service session
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.4.1 General
| A MCData user triggers an establishment of a MCData session with another MCData user for the exchange of SDS data. The target MCData user may be addressed using the functional alias that can be shared with other MCData users.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.4.2 Procedure
| The procedure in figure 7.4.2.4.2-1 describes the case where an MCData user is initiating data communication session with another MCData user for exchanging at least one SDS data transaction between them, with or without disposition request using MCData-SDS-1 and MCData-SDS-2 or MCData-SDS-3 reference points.
Pre-cond... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.5 Group standalone short data service using signalling control plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.5.1 General
| The initiation of a group standalone SDS to a selected group results in affiliated group members receiving the SDS data. The SDS payload data size is assumed to be below the configured maximum payload data size for SDS over signalling control plane.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.5.2 Procedure
| The procedure in figure 7.4.2.5.2-1 describes the case where an MCData user is initiating group standalone MCData data communication with or without disposition request, to a group.
Pre-conditions:
1. MCData users on MCData clients 1 to n belong to the same group and are already registered for receiving MCData servi... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.6 Group standalone short data service using media plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.6.1 General
| The initiation of a group standalone SDS to a selected group results in affiliated group members receiving the SDS data. The SDS payload data size is assumed to be above the configured maximum payload data size for SDS over signalling control plane.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.6.2 Procedure
| The procedure in figure 7.4.2.6.2-1 describes the case where an MCData user is initiating group standalone MCData data communication with or without disposition request to a group.
Pre-conditions:
1. MCData users on MCData client 1 to n belong to the same group and are already registered for receiving MCData service... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.7 Group short data service session
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.7.1 General
| The initiation of a group SDS to a selected group results in affiliated group members exchanging SDS data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.7.2 Procedure
| The procedure in figure 7.4.2.7.2-1 describes the case where an MCData user is initiating SDS data communication session with an MCData group for exchanging SDS data transactions between the group participants, with or without disposition request, using MCData-SDS-1 and MCData-SDS-2 reference points.
Pre-conditions:
... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.8 One-to-one SDS communication upgrade to an emergency one-to-one SDS communication
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.8.1 General
| This clause is for adding procedures related to upgrading an existing MCData one-to-one SDS communication to an MCData emergency one-to-one SDS communication.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.8.2 Procedure
| The procedure in figure 7.4.2.8.2-1 describes the case where an authorized MCData user is upgrading an ongoing MCData one-to-one SDS communication to an MCData emergency one-to-one SDS communication. This procedure is applicable only when MCData one-to-one SDS communication is established as described in subclause 7.4.... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.9 Group SDS communication upgrade to a group emergency SDS communication
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.9.1 General
| This clause is for adding procedures related to upgrading an existing MCData group SDS communication to an MCData emergency group SDS communication.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.9.2 Procedure
| The procedure in figure 7.4.2.9.2-1 describes the case where an authorized MCData user is upgrading an ongoing MCData group SDS communication to an MCData emergency group SDS communication. This procedure is applicable only when group MCData communication is established as described in subclause 7.4.2.6 "Group standalo... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.10 Group SDS communication in-progress emergency group state cancel
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.10.1 General
| This clause describes procedures related to MCData in-progress emergency group state cancel. The emergency state of the group can also be cancelled by the group FD in-progress emergency state cancellation procedure in subclause 7.5.2.13.2, or by the emergency alert cancellation procedure specified in 3GPP TS 23.280 [16... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.10.2 Procedure
| The procedure in figure 7.4.2.10.2-1 describes the case where an authorized MCData user cancels MCData group's in-progress emergency.
Pre-conditions:
1. The MCData group is previously defined on the group management server with MCData client 1, MCData client 2 and MCData client 3 affiliated to that MCData group.
2.... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.11 Group SDS communication upgrade to an imminent peril group SDS communication
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.11.1 General
| This clause is for adding procedures related to upgrade to an imminent peril group SDS communication.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.11.2 Procedure
| This procedure is applicable only when group MCData SDS communication is established as described in subclause 7.4.2.6 "Group standalone short data service using media plane" or as described in subclause 7.4.2.7 "Group short data service session". The MCData service shall support the procedures and related information ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.12 Group SDS communication in-progress imminent peril group state cancel
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.12.1 General
| This clause is for adding procedures related to group SDS communication in-progress imminent peril group state cancel.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.12.2 Procedure
| The MCData service shall support the procedures and related information flows as specified in subclause 7.4.2.10 "Group SDS communication in-progress emergency group state cancel" with the following clarifications:
- In step 2), the MCData client 1 sets imminent peril indicator; and
- In step 5), MCData users are not... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.13 Providing data for a user entering an ongoing MCData group conversation
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.13.1 General
| The MCData service shall support mechanisms that allow a MCData user be presented with the whole content of a group conversation in a group that he is a member of. This includes the content (messages) exchanged before the MCData user joins the group conversation.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.2.13.2 Procedure
| Figure 7.4.2.13.2-1 describes procedures for a MCData user joining late a group conversation.
Pre-conditions:
1. The MCData group is provisioned for lossless communication.
2. All members of the MCData group have an account created in the MCData message store.
3. MCData client 1, MCData client 2 and MCData client ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.3 Short data service for off-network
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.3.1 General
| Off-network SDS communications are based on ProSe capabilities as described in clause 7.16.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.3.2 Information flows for short data service
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.3.2.1 MCData standalone data request
| Table 7.4.3.2.1-1 describes the information flow for the MCData standalone data request sent from the MCData client to another MCData client.
Table 7.4.3.2.1-1: MCData standalone data request
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending data
MCData ID
M
The identi... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.3.2.2 MCData data disposition notification
| Table 7.4.3.2.2-1 describes the information flow for the MCData data disposition notification sent from the MCData client to another MCData client.
Table 7.4.3.2.2-1: MCData data disposition notification
Information element
Status
Description
MCData ID
M
The identity of the MCData user towards which the notifica... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.3.2.3 MCData group standalone data request
| Table 7.4.3.2.3-1 describes the information flow for the MCData group standalone data request sent from the MCData client to another MCData client.
Table 7.4.3.2.3-1: MCData group standalone data request
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending data
MCData group... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.3.3 One-to-one standalone short data service using signalling control plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.3.3.1 General
| This subclause describes the detailed procedures for the scenario where SDS data is to be sent to MCData user in off-network.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.4.3.3.2 Procedure
| Figure 7.4.3.3.2-1 describes procedures for an off-network MCData client 1 initiating one-to-one MCData data communication for sending standalone SDS data to other MCData client, with or without disposition request. Standalone refers to sending unidirectional data in one transaction. The SDS data size is assumed to be ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.