hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.4.3.6 Message notification client
|
The Message notification client is used to request the notification service from the MCData notification server. Once the notification service request is authorized by the MCData notification server, the Message notification client will communicate the callback endpoint, received from the MCData notification server, to the MCData message store to be used for notification message delivery.
When multiple MCData notification servers are deployed, the Message notification client shall select one for notification service at any given time. How the Message notification client selects the appropriate MCData notification server from multiple available MCData notification servers for service is implementation specific.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.4.4 Reference points
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.4.4.1 Application plane
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.4.4.1.1 General
|
The reference points for the application plane of MCData service are described in the following subclauses.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.4.4.1.2 Reference point MCData-2 (between the MCData server and the MCData user database)
|
The MCData-2 reference point, which exists between the MCData server and the MCData user database, is used by the MCData server to obtain information about a specific user. The MCData-2 reference point utilises a diameter management application protocol as defined in 3GPP TS 29.283 [12] and shall be intra-network.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.4.4.1.3 Reference point MCData-3 (between the MCData server and the MCData server)
|
The MCData-3 reference point, which exists between the MCData server and the MCData server for MCData application signalling for establishing MCData sessions, shall use the SIP-2 reference point for transport and routing of signalling. If each MCData server is served by a different SIP core then the MCData-3 reference point shall also use the SIP-3 reference point for transport and routing of signalling. Media is also transferred using the MCData-3 reference point.
6.4.4.1.3A Reference point MCData-5 (between the MCData server and the EPS)
The MCData-5 reference point, which exists between the MCData server and the EPS, is used, subject to the conditions below, by the MCData server to obtain unicast bearers with appropriate QoS from the EPS. It utilises the Rx interface of the EPS according to 3GPP TS 23.203 [14].
MCData-5 is not used when the MCData service provider and the PLMN operator do not have an operational agreement for QoS control to be provided directly from the MCData service provider domain.
MCData-5 may be used when the MCData service provider and the PLMN operator have an operational agreement where QoS control is provided directly from the MCData service provider domain.
NOTE: Any coordination between the P-CSCF use of Rx and the MCData server use of Rx (via MCData-5) from the MCData service provider domain is not specified in this release of this specification.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.4.4.1.4 Reference point MCData-6 (between the MCData server and the EPS)
|
The MCData-6 reference point, which exists between the MCData server and the EPS, is used to request the allocation and activation of multicast transport resources for MCData application usage. The MCData-6 reference point uses the MB2-C interface as defined in 3GPP TS 29.468 [16]. The MCData-6 reference point also uses the xMB-C interface as defined in 3GPP TS 29.116 [20] for file distribution.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.4.4.1.5 Reference point IWF-2 (between the interworking function to LMR system and the MCData server)
|
The IWF‑2 reference point is specified in 3GPP TS 23.283 [18].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.4.4.1.6 Reference point MCData-7 (between the Message store client and MCData message store)
|
The MCData-7 reference point, which exists between the Message store client and the MCData message store, is used by the Message store client to manage the information stored in the MCData message store, to subscribe to changes in the MCData message store and to synchronize between the MCData client and the MCData message store.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.4.4.1.7 Reference point MCData-8 (between the MCData message store and McData server)
|
The MCData-8 reference point, which exists between the MCData server and the MCData message store, is used by the MCData server to access and manage the MCData message store such as creating MCData user folders and depositing the communications history.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.4.4.1.8 Reference point MCData-9 (between the MC gateway server and the MC gateway server in a different MCData system)
|
The MCData-9 reference point, which exists between the MC gateway server and the MC gateway server in an interconnected MCData system for MCData application signalling for establishing MCData sessions, shall use the SIP‑3 reference point for transport and routing of signalling. The MCData-9 reference point also carries application data where the data size is too great to be transferred on the signalling plane.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.4.4.1.9 Reference point MCData-10 (between the Message notification client and MCData notification server)
|
The MCData-10 reference point, which exists between the Message notification client and the MCData notification server, is used by the Message notification client to create an appropriate notification channel(s) at the MCData notification server in order to direct events from MCData message store to the MCData notification server for subsequent delivery to the Message notification client on the UE.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.4.4.1.10 Reference point MCData-11 (between the MCData message store and the MCData notification server)
|
The MCData-11 reference point, which exists between the MCData message store and the MCData notification server, is used by the MCData message store to send notification message to the subscribed Message notification client.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5 Functional model for short data service
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5.1 On-network functional model
|
Figure 6.5.1-1 shows the application plane functional model for SDS.
Figure 6.5.1-1: Application plane functional model for SDS
In the model shown in figure 6.5.1-1, the following apply:
- MCData-SDS-1 reference point is primarily used for MCData application signalling during session establishment in support of SDS data transfer. Secondarily, MCData-SDS-1 reference point is used for uplink and downlink unicast SDS data transaction over signalling control plane by the SDS distribution function of the MCData server and SDS function of the MCData client.
- MCData-SDS-2 reference point carries uplink and downlink unicast SDS data over media plane between the SDS distribution function of the MCData server and the SDS function of the MCData client.
- MCData-SDS-3 reference point carries downlink multicast SDS data over media plane from the SDS distribution function of the MCData server to the SDS function of the MCData client.
Examples of SDS data (in the form of text, binary, application data, URL or combinations of these) are:
- information pertaining to applications e.g. health parameters of MCData user for situational awareness application;
- information pertaining to enhanced status service;
- text or URL data between MCData users;
- application data (e.g. health parameters) to the MCData user;
- location information (independent or along with user or application provided data);
- command instructions to invoke certain operations on the MCData UE e.g. invoking UE specific applications; and
- application plane identities for the MCData user and MCData application.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5.2 Off-network functional model
|
Figure 6.5.2-1 shows the off-network application plane functional model for SDS.
Figure 6.5.2-1: Application plane functional model for SDS
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5.3 Functional entities description
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5.3.1 Application plane
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5.3.1.1 SDS function
|
SDS function of the MCData client is responsible to handle SDS capability related requests and responses.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5.3.1.2 SDS distribution function
|
The SDS distribution function of the MCData server is responsible for the SDS data transaction to MCData communication participants. The SDS distribution function of the MCData server provides the following functionality:
- reception of uplink SDS data transaction by means of the MCData-SDS-1 and MCData-SDS-2 reference points;
- replicate the SDS data as needed for distribution to those MCData communication participants using unicast transport;
- distribute downlink data by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of the MCData-SDS-1 and MCData-SDS-2 reference points; and
- distribute downlink SDS data using multicast downlink transport by means of the MCData-SDS-3 reference point.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5.3.1.3 Transmission/Reception control
|
This functional entity is responsible for transmission and reception control of MCData SDS data transaction between the sending MCData UE, the MCData server, and the receiving MCData UE. For SDS capability, due to small data size, the SDS messages can be automatically sent.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5.3.2 Signalling control plane
|
The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5.4 Reference points
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5.4.1 Application plane
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5.4.1.1 Reference point MCData-SDS-1 (between the SDS distribution function and the SDS function)
|
MCData-SDS-1 reference point is used for uplink and downlink unicast SDS data transaction over signalling control plane by the SDS distribution function of the MCData server and SDS function of the MCData client. This reference point is also used for MCData application signalling during session establishment in support of SDS data transfer.
The MCData-SDS-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling. MCData-SDS-1 reference point can be used when the SDS payload data size does not exceed the configured maximum payload data size for SDS over signalling control plane, otherwise MCData-SDS-2 and MCData-SDS-3 may be used appropriately.
Reference point MCData-SDS-1 also provides support to delivered and read requests and notifications as appropriate.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5.4.1.2 Reference point MCData-SDS-2 (unicast between the SDS distribution function and the SDS function)
|
The MCData-SDS-2 reference point, which exists between the SDS distribution function and the SDS function of the MCData client, is used unicast SDS data transaction (when the SDS payload data size exceeds the configured maximum payload data size for SDS over signalling control plane) between the MCData server and the MCData client. The MCData-SDS-2 reference point uses the SGi reference point defined in 3GPP TS 23.002 [10].
Reference point MCData-SDS-2 also provides support to message thread indication using conversation identifier, delivered and read notifications as appropriate.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5.4.1.3 Reference point MCData-SDS-3 (multicast between the SDS distribution function and the SDS function)
|
The MCData-SDS-3 reference point, which exists between the SDS distribution function of the MCData server and the SDS function of the MCData client, is used by the SDS distribution function of the MCData server to send downlink multicast SDS data to the SDS function of the MCData client. The MCData-SDS-3 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [8].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.5.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].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6 Functional model for file distribution
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.1 On-network functional model
|
Figure 6.6.1-1 shows the application plane functional model for file distribution.
Figure 6.6.1-1: Application plane functional model for file distribution
In the model shown in figure 6.6.1-1, the following apply:
- MCData-FD-1 reference point is primarily used for MCData application signalling for establishing a session in support of MCData file distribution. Secondarily, MCData-FD-1 reference point is also used for both uplink and downlink unicast data (e.g., URL associated to file, file download completed report).
- MCData-FD-2 reference point carries uplink and downlink unicast file data between the FD functions of the MCData server and the MCData UE.
- MCData-FD-3 reference point carries downlink multicast file data from the FD function of the MCData server to the FD function of the MCData UE.
- MCData-FD-4 reference point carries uplink and downlink unicast file data between the media storage function of the MCData Content server and the media storage client of the MCData UE.
- MCData-FD-5 reference point supports the MCData server to access the stored files in the MCData content server for certain file distribution functions, such as retrieval a file to be distributed through multicast etc. This reference points also supports any necessary operational requirements.
- MCData-FD-7 reference point supports the upload and download of file data between MCData content server and MCData message store.
NOTE: The security aspects of MCData-FD-5 and MCData-FD-7 reference points are the responsibility of SA3 and thus outside the scope of the present document.
6.6.1a On-network functional model for interconnection
Figure 6.6.1a-1 shows the application plane functional model for file distribution with interconnection.
Figure 6.6.1a-1: Application plane functional model for file distribution
In the model shown in figure 6.6.1a-1, the following apply:
- MCData-FD-1, MCData-FD-2, MCData-FD-3, MCData-FD-4, MCData-FD-5 reference points are described in subclause 6.6.1.
- MCData-7 and MCData-8 reference points are described in subclause 6.4.4.1.
- The MC gateway server is described in subclause 6.4.3.1.5.
- MCData-3 and MCData-9 allow the MCData server in the primary MCData system to share URLs related to files for upload and download with the MCData server in the partner MCData system.
- MCData-FD-6 allows file contents and metadata to be shared between the MCData content server in the primary MCData system and the MCData content server in the partner MCData system. MCData‑FD‑6 is based on HTTP.
- The HTTP proxies are contained in the signalling plane. They provide topology and IP address hiding between MCData systems.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.2 Off-network functional model
|
Figure 6.6.2-1 shows the off-network application plane functional model for FD.
Figure 6.6.2-1: Application plane functional model for FD
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.3 Functional entities description
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.3.1 Application plane
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.3.1.1 FD function
|
FD function of the MCData client and the MCData server is responsible to handle file distribution capability related requests and responses.
The FD function of the MCData server is responsible for the distribution of file to the MCData communication participants. The FD function of the MCData server provides the following functionality:
- reception of uplink file data by means of the MCData-FD-2 reference point;
- replicate the file data as needed for distribution to those MCData communication participants using unicast transport;
- distribute downlink file data by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of the MCData-FD-2 reference point; and
- distribute downlink file data using multicast downlink transport by means of the MCData-FD-3 reference point.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.3.1.2 Media storage client
|
The media storage client is used to support FD function of the MCData client for file distribution capability. FD function of the MCData client interacts with media storage client for uploading and downloading file to or from the media storage function of the MCData content server.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.3.1.3 Transmission/Reception control
|
This functional entity is responsible for transmission and reception control of MCData file data between the sending MCData UE, the MCData server, and the receiving MCData UE. Transmission and reception control function is used to provide arbitration between multiple data requests and apply the necessary policy to ensure that appropriate data is transmitted between the MCData UE. However, when the file distribution requests are exceeding a certain size, it may be necessary to control the data that is transmitted or received by the MCData UEs. The control is subject to criteria like application level priorities (e.g. user priority, group priority), service type, emergency nature of the communication, etc.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.3.1.4 Media storage function
|
The media storage function is responsible for the storing of media uploaded by the media storage client of the MCData UE in case of MCData file distribution. It also supports download of stored media by the MCData UE in case of file distribution via media storage client.
The media storage function supports partial download requests of stored media by the MCData UE via media storage client.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.3.1.5 MCData content server
|
The MCData content server functional entity provides a repository area in the MCData trust domain allowing authorized MCData users to temporarily store files that are intended to share to other MCData users. It provides common pool of storage area (i.e. size) to all authorized MCData users to use, no personal space is allocated. An authorized MCData user can use the supported operations on the defined reference point to upload shared files and download the files that are shared to him. The MCData server will use the defined reference point to access the files stored in the MCData content server and support the necessary operational functionalities. As part of the file life cycle management the temporarily stored files will be removed periodically based on the Mission Critical service provider policy. An MCData content server may share files with another MCData content server in another MCData system to support interconnection.
If the MBMS user service architecture described in 3GPP TS 26.346 [21] is utilized for file distribution, the MCData content server provides the stored file associated to the established MBMS session.
NOTE: The security aspects of the MCData content server and its operational supports are the responsibility of SA3 and thus outside the scope of the present document.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.3.2 Signalling control plane
|
The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.4 Reference points
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.4.1 Application plane
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.4.1.1 Reference point MCData-FD-1 (between the FD functions of the MCData client and the MCData server)
|
MCData-FD-1 reference point is used for MCData application signalling for establishing a session in support of MCData file distribution. The bearer is also used for both uplink and downlink unicast data (e.g., URL associated to file, file download completed report). The MCData-FD-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling. MCData-FD-1 reference point can be used as long as the file size does not exceed the capabilities (e.g. payload or transmission limits) provided by MCData-FD-1.
Messages supported on this interface include the uplink and the downlink unicast file transaction between the MCData clients in MCData communication via the MCData server for:
- metadata (file size, type etc.) of the file being distributed;
- URL of the file being distributed;
- sending download completed report;
- small size file;
- conversation identifier for message thread indication; and
- application plane identities for the MCData user and MCData application.
Messages supported on this interface may also include the MCData client providing the MCData server with
- MCData application signalling for establishing a file distribution session in support of MCData communication.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.4.1.2 Reference point MCData-FD-2 (unicast between the FD functions of the MCData client and the MCData server)
|
The MCData-FD-2 reference point, which exists between the FD functions of the MCData client and the MCData server, is used for unicast file transaction between MCData server and MCData client. The MCData-FD-2 reference point uses the SGi reference point defined in 3GPP TS 23.002 [10].
Reference point MCData-FD-2 supports the following functions:
- file being distributed from and to the MCData client;
- conversation identifier for message thread indication; and
- application plane identities for the MCData user and MCData application.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.4.1.3 Reference point MCData-FD-3 (multicast between the FD functions of the MCData client and the MCData server)
|
The MCData-FD-3 reference point, which exists between the FD functions of the MCData client and the MCData server, is used by the FD function of the MCData server to send downlink multicast file data to the FD function of the MCData client. The MCData-FD-3 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [8] or the xMB-U interface as defined in 3GPP TS 26.348 [19].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.4.1.4 Reference point MCData-FD-4 (media storage function and media storage client)
|
The MCData-FD-4 reference point, which exists between the media storage function and the media storage client, is used by the media storage client of MCData UE to upload and download file to the media storage function of the MCData content server. The MCData-FD-4 reference point uses the HTTP reference point.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.4.1.5 Reference point MCData-FD-5 (FD function and media storage function)
|
The MCData-FD-5 reference point, which exists between FD function and the media storage function, is used by the FD function of MCData server to fetch the file in the MCData content server that was uploaded by the media storage client of a MCData UE for multicast delivery using MBMS. It also supports necessary operational functions such as size check for transmission control etc. The MCData-FD-5 reference point uses the HTTP reference point.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.4.1.6 Reference point MCData-FD-7 (media storage function and MCData message store)
|
The MCData-FD-7 reference point, which exists between media storage function and the MCData message store, is used by the media storage function to fetch the file residing in the MCData message store and store in its repository for distribution. It is also used by the MCData message store to download the file contents from the media storage function.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.6.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].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7 Functional model for data streaming
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7.1 On-network functional model
|
NOTE: As no detailed procedures are specified in the current specification the DS functional model is for information only.
Figure 6.7.1-1 shows the application plane functional model for data streaming.
Figure 6.7.1-1: Application plane functional model for data streaming
In the model shown in figure 6.7.1-1, the following apply:
- MCData-DS-1 reference point is used for MCData application signalling for establishing a session in support of MCData data streaming. The bearer is also used for both uplink and downlink unicast stream download reports (e.g. stream start and stop records).
- MCData-DS-2 reference point carries unicast data stream between the data streaming and distribution function of the MCData server and the DS function of the MCData UE. The bearer is used for both uplink and downlink unicast data streaming.
- MCData-DS-3 reference point carries multicast data stream from the data streaming and distribution function of the MCData server to the DS function of the MCData UE. The bearer is used for downlink multicast data streaming.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7.2 Off-network functional model
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7.3 Functional entities description
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7.3.1 Application plane
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7.3.1.1 DS function
|
DS function of the MCData client is responsible to handle DS capability related requests and responses for data streaming. FD function may interact with storage entity for retrieving the locally stored data for data streaming.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7.3.1.2 Data streaming and distribution function
|
The data streaming and distribution function is responsible for the distribution of data stream to MCData communication participants. The data streaming and distribution function provides the following functionality:
- reception of uplink data stream transmission by means of the MCData-DS-2 reference point;
- replicate the data stream as needed for distribution to those MCData communication participants using unicast transport;
- distribute downlink data stream by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of MCData-DS-2 reference point; and
- distribute downlink data stream using multicast downlink transport by means of the MCData-DS-3 reference point.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7.3.1.3 Transmission/Reception control
|
This functional entity is responsible for transmission and reception control of data stream between the sending MCData UE, the MCData server, and the receiving MCData UE. Transmission and reception control function is used to provide arbitration between multiple data requests and apply the necessary policy to ensure that appropriate data is transmitted between the MCData UEs.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7.3.2 Signalling control plane
|
The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7.4 Reference points
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7.4.1 Application plane
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7.4.1.1 Reference point MCData-DS-1 (between the data streaming and distribution function and the DS function)
|
MCData-DS-1 reference point is used for MCData application signalling for establishing a session in support of MCData data streaming. The bearer is also used for both uplink and downlink unicast stream download reports (e.g., stream start and stop records). The MCData-DS-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling.
Messages supported on this interface includes the uplink and the downlink unicast data stream between the MCData clients MCData communication via the MCData server for
- metadata of the data being streamed;
- URL of the data being streamed;
- sending stream download report;
- conversation identifier for message thread indication; and
- application plane identities for the MCData user and MCData application.
Messages supported on this interface may also include the MCData client providing the MCData server with
- MCData application signalling for establishing a UE data streaming session in support of MCData communication.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7.4.1.2 Reference point MCData-DS-2 (unicast between the data streaming and distribution function and the DS function)
|
The MCData-DS-2 reference point, which exists between the data streaming and distribution function and the DS function, is used to unicast data stream between the data streaming and distribution function of the MCData server and the DS function of the MCData client. The MCData-DS-2 reference point uses the SGi reference point defined in 3GPP TS 23.002 [10].
MCData-DS-2 supports the following functions:
- stream data from MCData UE;
- stream data from network;
- data stream controls from the authorized MCData UE;
- stream data stream controls from the MCData UE over uplink;
- start and stop data stream from MCData UE over downlink;
- conversation identifier for message thread indication; and
- application plane identities for the MCData user and MCData application.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7.4.1.3 Reference point MCData-DS-3 (multicast between the data streaming and distribution function and the DS function)
|
The MCData-DS-3 reference point, which exists between the data streaming and distribution function and the DS function, is used by the data streaming and distribution function of the MCData server to send multicast data stream to the DS function of the MCData client. The MCData-DS-3 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [8].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.7.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].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.8 Functional model for IP connectivity
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.8.1 On-network functional model
|
Figure 6.8.1-1 shows the application plane functional model for User-IP connectivity.
Figure 6.8.1-1: Application plane functional model for IP connectivity
In the model shown in figure 6.8.1-1, the following apply:
- MCData-IPcon-1 reference point is used for MCData application signalling for establishing a session in support of MCData IP connectivity.
- MCData-IPcon-2 reference point carries bidirectional IP Data for point-to-point MCData IP connectivity over the media plane between the U-IPcon distribution function of the MCData server and the IPcon function of the MCData client(s).
- MCData-IPcon-3 reference point is used by the IP-con distribution function of the MCData server to send unidirectional downlink IP Data to the IP-con function of the MCData clients.
- IPcon-host reference point is used for a data host, e.g. server, to use IP connectivity service capabilities. This reference point is outside the scope of the present document.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.8.2 Off-network functional model
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.8.3 Functional entities description
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.8.3.1 Application plane
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.8.3.1.1 IP connectivity function
|
IP connectivity function of the MCData client is responsible to handle IPcon capability related requests and responses.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.8.3.1.2 IPcon distribution function
|
The IPcon distribution function of the MCData server is responsible for the distribution of IP Data to MCData communication participants. The IPcon distribution function of the MCData server provides the following functionality:
- reception of uplink IP Data transmission by means of the MCData-IPcon-2 reference points;
- replicate the IP Data as needed for distribution to those MCData communication participants using unicast transport;
- distribute downlink data by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of the MCData-IPcon-2 reference points; and
- distribute downlink IP Data using multicast downlink transport by means of the MCData-IPcon-3 reference point.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.8.3.1.3 Transmission/Reception control
|
This functional entity is responsible for transmission and reception control of IP Data transaction between the sending MCData client, the MCData server, and the receiving MCData client. Transmission and reception control function is used to provide arbitration between multiple data requests and apply the necessary policy to ensure that appropriate IP Data are transmitted between the MCData clients.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.8.3.2 Signalling control plane
|
The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.8.4 Reference points
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.8.4.1 Application plane
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
6.8.4.1.1 Reference point MCData-IPcon-1 (between the IPcon distribution function and the U-IPcon function)
|
MCData-IPcon-1 reference point is used for MCData application signalling for establishing a session in support of MCData IP connectivity.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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).
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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).
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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 Application of functional model to deployments
The application of the functional model to deployments, and description of various deployment scenarios for the MCData service, can be found in clause 9 of 3GPP TS 23.280 [5].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7 Procedures and information flows
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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
- The MC service user profile index is the MCData user profile index.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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 service ID is the MCData ID; and
- The MC service group ID is the MCData group ID.
When an MCData user has affiliated to an MCData group then the MCData user can send and receive MCData related media for that MCData group. When an MCData user has de affiliated from an MCData group then the MCData user cannot send and receive MCData related media to and from that MCData group.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.3 Use of MBMS transmission (on-network)
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.3.1 Information flows for MBMS Transmission
|
Information flows for generic MBMS procedures are defined in 3GPP TS 23.280 [5].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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 use the MCData-6, MCData-SDS-1, MCData-SDS-2, MCData-SDS-3, MCData-FD-1, MCData‑FD-3, MCData-DS-1 and MCData‑DS-3 reference points for this procedure.
MCData may use pre-established MBMS bearer for the MCData features short data service, file distribution and data streaming. The MBMS bearer can be used by any group. Depending on the capacity of the MBMS bearer, the bearer can be used to broadcast one or more services in parallel.
Both the media packets as well as application level control signalling (e.g. transmission control) to the receiving users may be sent on the MBMS bearer. Optionally, a separate MBMS bearer could be used for the application level control signalling (e.g. transmission control), due to different bearer characteristic requirements.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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 MCData-6, MCData-SDS-1, MCData-SDS-3, MCData-FD-1, MCData‑FD-3, MCData-DS-1 and MCData-DS-3 reference points for this procedure.
MCData may use dynamic MBMS bearer for the MCData features short data service, file distribution and data streaming. The MBMS bearer can be used by any group. Depending on the capacity of the MBMS bearer, the bearer can be used to broadcast one or more services in parallel.
Both the media packets as well as application level control signalling (e.g. transmission control) to the receiving users may be sent on the MBMS bearer. Optionally, a separate MBMS bearer could be used for the application level control signalling (e.g. transmission control), due to different bearer characteristic requirements.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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 shall use the MCData-SDS-1, MCData-SDS-2, MCData-FD-1, MCData‑FD-3, MCData-DS-1 and MCData‑DS-3 reference points for this procedure.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.3.5 Use of MBMS user services for file distribution
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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-to-end encryption file distribution using MBMS when the BM-SC is in the MCData system trust domain.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.3.5.2 Information flows for MBMS user service usage
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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 in the create/update session response (subclause 5.4 in 3GPP TS 26.348 [19]) (see NOTE)
Monitoring state
O
The monitoring state is used to control if the client is actively monitoring the reception quality or the MBMS bearer used by the MBMS user service.
Unicast status
O
An indication that the listening status of the unicast bearer is requested.
NOTE: The SA file provides the TMGI, the list of MBMS service area identifiers, the frequency and the delivery parameters.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.3.5.3 Procedures for MBMS user service usage
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.3.5.3.1 Use of pre-established MBMS user services
|
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 transmission.
The MBMS user service can be announced prior to the file distribution or within the signalling message for the file distribution.
The MBMS user service does not transmit application level control signalling. An MBMS bearer could be used for the application level control messages according to the generic MBMS procedures defined in 3GPP TS 23.280 [5].
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 participating users are already affiliated.
Figure 7.3.5.3.1.2-1: Use of pre-established MBMS user service
1. The MCData server determines to create an MBMS user service with a given MBMS user service id. If the MCData server makes use of the xMB interface, the MCData server creates an MBMS user service over xMB-C (subclause 5.3 from 3GPP TS 26.348 [19]).
NOTE 1: The procedure to determine the creation of MBMS user services is implementation specific.
2. If the MCData server makes use of the xMB interface, the MCData server creates an MBMS session over xMB-C for the MBMS user service (subclause 5.4 from 3GPP TS 26.348 [19]), with the type set to "Files" to use the MBMS download delivery method. Additionally, the MCData server defines the ingest mode, pull or push, to provide the file into the BM‑SC via xMB‑U. This MBMS session will be used for file distribution. In response, the MCData server gets the TMGI of the MBMS bearer used for the MBMS session, and the SA file containing the metadata of the MBMS user service. When the push ingest mode is used, as part of the response from the BM‑SC the MCData server also obtains the URL to be used to push the file.
3a. Else, the MCData server activates an MBMS bearer over MB2-C for the MBMS user service.
3b. The MCData server, if not already in the possession of the SA file, generates the SA file containing the metadata of the MBMS user service.
4. The MCData server passes using control plane signalling the MBMS user service info for the service description associated with the pre-established MBMS user service to the MCData client. The MCData client obtains the TMGI, identifying the MBMS bearer, from the SA file included in the MBMS user service description.
5. The MCData client stores the information associated with the MBMS user service. The MCData client uses the TMGI and other MBMS user service related information to activate the monitoring of the MBMS bearer.
6. The MCData client that enters or is in the service area of at least one announced TMGI indicates to the MCData server that the MCData client is able to receive file distributed over MBMS, whereby the MCData server may decide to use this MBMS user service instead of unicast bearer for MC communication sessions.
NOTE 2: Step 4 is optional for the MCData UE on subsequent MBMS user service announcements.
NOTE 3: The information flow is specified in subclause 10.7.2.2 from 3GPP TS 23.280 [5].
7. If the MCData server makes use of the xMB interface and wants to deliver a file to a group, the MCData server updates the MBMS session to provide the file list when the pull ingest mode is defined. As described in 3GPP TS 26.348 [19], the file list includes, among other information, the file URL to be used by the BM‑SC to fetch the file and the earliest fetch time.
8. The MCData server signals the file transmission over the MBMS user service to the targeted MCData clients.
NOTE 4: After step 8, the file can be provided for distribution over the MBMS session. If the pull ingest mode is defined, the BM‑SC fetches the file from the indicated file URL. If the push ingest mode is defined, the MCData server can start pushing the file to the corresponding URL.
9. The file, transmitted with the MBMS download delivery method, is received by the MCData clients. If the MCData server does not make use of the xMB interface, the MCData server fragments the file to be sent, applies error correction according to the MBMS download delivery method (3GPP TS 26.346 [21]) and sent the FLUTE packets over MB2-U.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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 given file. The MBMS user service is announced to the MCData client, together with the file information to be received.
NOTE 1: The MCData server logic for determining when to establish the new MBMS user service is implementation specific. For example, the MCData server could decide to establish the MBMS delivery based on the location of the UE's that are a part of the targeted group.
Figure 7.3.5.3.2-1: Use of dynamic MBMS user service establishment
1. The MCData server determines to create a MBMS user service with a given an MBMS user service id for the group communication session. If the MCData server makes use of the xMB interface, the MCData server creates an MBMS user service over xMB-C (subclause 5.3 from 3GPP TS 26.348 [19]).
2. If the MCData server makes use of the xMB interface, the MCData server creates a MBMS session for the MBMS user service (subclause 5.4 from 3GPP TS 26.348 [19]), with the type set to "Files" to use the MBMS download delivery method. Additionally, the MCData server defines the ingest mode, pull or push, to provide the file into the BM‑SC via xMB‑U. When the pull ingest mode is defined, the MCData server provides the file list. The file list includes, among other information, the file URL to be used by the BM‑SC to fetch the file and the earliest fetch time. In response, the MCData server gets the TMGI of the MBMS bearer used for the MBMS session and the SA file containing the metadata of the MBMS user service. When the pull ingest mode is defined, the MCData server also obtains the scheduling parameter for the file delivery. When the push ingest mode is used, as part of the response from the BM‑SC the MCData server obtains the URL to be used to push the file.
3a. Else, the MCData server activates an MBMS bearer over MB2-C for the MBMS user service.
3b. The MCData server, if not already in the possession of the SA file, generates the SA file containing the metadata of the MBMS user service.
4. The MCData server passes using control plane signalling the SA file to the MCData client. The MCData client obtains the TMGI, identifying the MBMS bearer, from the SA file included in the MBMS user service description.
5. The MCData client stores the information associated with the MBMS user service. The MCData client uses the TMGI and other MBMS user service related information to activate the monitoring of the MBMS bearer.
6. The MCData client that enters or is in the service area of at least one announced TMGI indicates to the MCData server that the MCData client is able to receive file distributed over MBMS, whereby the MCData server may decide to use this MBMS user service instead of unicast bearer for MC communication sessions.
7. The MCData server signals the file transmission over the MBMS user service to the targeted MCData clients.
NOTE 2: After step 7, the file can be provided for distribution over the MBMS session. If the pull ingest mode is defined, the BM‑SC fetches the file from the indicated file URL. If the push ingest mode is defined, the MCData server can start pushing the file to the corresponding URL.
8. The file, transmitted with the MBMS download delivery method, is received by the MCData clients. If the MCData server does not make use of the xMB interface, the MCData server fragments the file to be sent, applies error correction according to the MBMS download delivery method (3GPP TS 26.346 [21]) and sent the FLUTE packets over MB2-U.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.3.5.3.3 Providing stored files in the MCData content server for distribution over MBMS
|
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 user service architecture is used over the xMB interface (specified in 3GPP TS 26.348 [19]), two ingest modes, push and pull, can be defined by the MCData server to ingest the file into the BM‑SC for distribution over the MBMS sessions.
NOTE: It is implementation specific if the MCData server uses pull or push ingest mode to ingest the file into the BM‑SC over the xMB interface.
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 file also becomes available for the case that the MCData server decides to distribute the file over the MB2 interface to MCData users from the target MCData group.
When the MCData server defines a pull ingest mode, the MCData server provides via the xMB‑C interface the resource location from which the BM‑SC will fetch the file as well as other session properties (e.g. file earliest fetch time), as described in 3GPP TS 26.348 [19].
When the MCData server defines a push ingest mode, the MCData server directly ingests into the BM‑SC via the xMB‑U interface the file obtained from the MCData content server. The BM‑SC provides to the MCData server the URL to be used to push the file(s).
NOTE 2: For the push ingest mode, the MCData server is always the functional entity ingesting the file content into the BM‑SC via the xMB‑U interface.
The procedure in figure 7.3.5.3.3.2-1 describes the case where the file to be distributed over MBMS is fetched by the MCData server from the MCData content server.
Pre-conditions:
- The MCData users on the MCData client 1 to n belong to the same MCData group and are already registered and affiliated for receiving MCData service.
- The file to be distributed is uploaded to the MCData content server.
- The BM‑SC has the necessary permissions to fetch a file from the MCData system.
Figure 7.3.5.3.3.2-1: File fetching by the MCData server for file distribution over MBMS
1. The MCData server receives a request from the MCData client 1 to distribute a file to a target MCData group. The MCData file distribution request contains the resource location (i.e. the file URL) in the MCData content server.
2. The MCData server decides to fetch the file from the MCData content server via the MCData-FD-5 reference point.
3. The MCData server creates an MBMS service and session for file delivery using xMB procedures via the xMB‑C interface, as described in 3GPP TS 26.348 [19]. The MCData server indicates, among other session properties, the ingest mode. For the case of pull ingest mode, the MCData server provides the file URL from which the BM‑SC will fetch the file. For the case of push ingest mode, the BM‑SC provides to the MCData server the URL to be used to push the file into the MBMS session.
NOTE 3: Step 3 may also occur before step 2.
4. The MCData server provides to the MCData users from the target MCData group the application signalling related to the MBMS session and the file distribution.
5a. For the case that the file is ingested into the BM‑SC based on the push ingest mode, the MCData server pushes the file to the URL indicated by the BM‑SC.
5b. For the case that the file is ingested into the BM‑SC based on the pull ingest mode, the BM‑SC pulls the file from the provided file URL.
6. The BM‑SC distributes the file over the established MBMS session. When the target MCData clients have activated the reception for that service and are located within the MBMS area coverage, the MCData clients receive the file.
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 1: In order to the enable that the BM‑SC fetches the file from the MCData content server, the MCData content server supports the xMB‑U interface to the BM‑SC.
NOTE 2: For the case that the file is ingested into the BM‑SC from the MCData content server, only the pull ingest mode is supported. When push ingest mode is required, the procedure is described in clause 7.3.5.3.3.2.
The procedure in figure 7.3.5.3.3.3-1 describes the case where the file to be distributed over MBMS is fetched by the BM‑SC from the MCData content server.
Pre-conditions:
- The MCData users on the MCData client 1 to n belong to the same MCData group and are already registered and affiliated for receiving MCData service.
- The file to be distributed is uploaded to the MCData content server.
- The BM‑SC has the necessary permissions to fetch a file from the MCData system.
Figure 7.3.5.3.3.3-1: File fetching by the BM‑SC for file distribution over MBMS
1. The MCData server receives a request from the MCData client 1 to distribute a file to a target MCData group. The MCData file distribution request contains the resource location (i.e. the file URL) in the MCData content server.
2. The MCData server creates an MBMS service and session for file delivery using xMB procedures via the xMB‑C interface, as described in 3GPP TS 26.348 [19]. The MCData server defines, among other session properties, the ingest mode to pull. The MCData server provides the file URL from which the BM‑SC will fetch the file from the MCData content server.
3. The MCData server provides to the MCData users from the target MCData group the application signalling related to the MBMS session and the file distribution.
4. The BM‑SC fetches the file from the MCData content server via the xMB‑U interface.
5. The BM‑SC distributes the file over the established MBMS session. When the target MCData clients have activated the reception for that service and are located within the MBMS area coverage, the MCData clients receive the file.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.3.6 Group communication connect and disconnect over MBMS bearer procedures
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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 bearer. The group session setup procedure indicates the media stream within one MBMS bearer that is used for the specific group communication. When the group communication over the MBMS bearer is finished, this temporary association information of an MCData group communication to specific resources on a MBMS bearer is undone.The procedure in clause 7.3.6 requires that the group session is setup before the data transmission starts. This eliminates the need for the receiving clients to continuously use a unicast bearer. Prior to group session setup, the MBMS bearer is activated and announced to the MCData clients.
NOTE: It is implementation-specific that one MBMS bearer can be re-assigned to different groups, or is associated to only one group.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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. Activation and announcement of MBMS bearer availability.
NOTE 1: The procedure does not include the steps for MCData client location reporting, or for MBMS capability information exchange.
2. The MCData client 1 initiates a group communication by sending a MCData group data request over a unicast PDN connection towards the MCData server.
3. MCData server initiates the MCData group data request towards each MCData clients 2 to n.
4. The receiving MCData clients 2 to n optionally notify the user about the incoming MCData session data request.
5. The receiving MCData client 2 to n accept or reject the MCData group data request and the corresponding result is in the MCData group data response towards MCData server.
6. The MCData server will send a MapGroupToBearer message over a previously activated MBMS bearer to all users that will receive the communication over an MBMS bearer. The MapGroupToBearer message includes association information between the group communication and MBMS bearer. The MapGroupToBearer message includes MCData group ID and information about the media stream identifier of the activated MBMS bearer and may include the identifier (i.e. the TMGI) of the MBMS bearer broadcasting the communication.
7. The MCData clients 2 to n process the MapGroupToBearer information and may send a MapGroupToBearer Ack back to the MCData server if required.
8. MCData server forwards the MCData group data response received from MCData client 2 to n to the MCData user initiating the MCData session data request.
NOTE 2: The steps 3 to 5 and steps 6 to 7 can occur in any order, and prior to step 9 depending on the conditions to proceed with the data transmission.
9. MCData client 1 sends the MC data over uplink unicast PDN connection towards the MCData server.
10. The MCData server sends the MC data over the indicated stream within the associated MBMS bearer to the MCData clients 2 to n.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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 communication is taking place over MBMS bearer. MCData client 1 is sending the MC data over a unicast PDN connection to the MCData server.
2. The MCData server sends the MC data over the MBMS bearer to MCData clients 2 to n.
3. After the MC data transmission is over, i.e., no further data to be sent over the group communication, the MCData server sends an UnMapGroupFromBearer to de-associate the group communication from the MBMS bearer.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.4 Short data service
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.