hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 5.10 MCData message store
| MCData message store is used by MCData users to store their MCData communications permanently; it shall provide secured storage area for each authorized MCData user having a user account. The storage area is identified by the MCData user's MCData ID. The MCData message store shall allow an MCData user to access only th... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 5.11 IP connectivity (IPcon) capability
| IP connectivity service enables the exchange of IP Data using MCData transport service and provides the transport of IP Data for e.g. data hosts, servers, etc. that do not have mission critical communication capabilities. The exchange of IP Data is not limited in a transaction.
Figure 5.11-1: IP connectivity model
... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 5.12 MBMS user service architecture requirements
| The MBMS user service architecture offers a set of delivery methods to applications, specified in 3GPP TS 26.346 [21]. The MBMS download delivery method is used for the delivery of files over MBMS and provides reliability control by means of forward-error-correction.
The MCData File Distribution capability can use the... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 5.13 MBMS delivery via MB2 interface
| MBMS delivery via MB2 applies to MCData services that use media plane for user traffic delivery.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 5.14 Delivery Notification
| A MCData user may request a delivery report (such as delivered, message read, or file downloaded etc.) when sending a MCData data (i.e. a message or a file). The recipient((s) shall respond with the proper delivery status response(s) (such as delivered, message read, or file downloaded etc.) according to what is reques... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6 Functional model
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.1 General
| This clause defines the functional model for MCData service.
The security solution for the MCData service, including end-to-end encryption, is specified in 3GPP TS 33.180 [13].
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.2 Description of the planes
| The functional model for the support of MCData is defined as a series of planes to allow for the breakdown of the architectural description.
The description of the planes and the relationship between the planes are contained in the common functional architecture to support MC services in 3GPP TS 23.280 [5].
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.3 Transmission and reception control aspects
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.3.1 General
| The transmission and reception control are functions of the MCData server.
For small data transmissions there is no need for prior grant of request to transmit. The procedures in the present document describe when data is automatically sent.
For large data transmissions, i.e. large files, the data is transmitted only... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4 Generic functional model
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.1 On-network functional model
| Figure 6.4.1-1 shows the generic application plane functional model.
Figure 6.4.1-1: Generic application plane functional model
In the model shown in figure 6.4.1-1, capability functions (SDS, FD, DS, IPcon) of the MCData client and the MCData server along with their reference points (MCData-cap-1 to MCData-cap-n) ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.2 Off-network functional model
| Figure 6.4.2-1 shows the functional model for the application plane of MCData service for off-network operations.
Figure 6.4.2-1: Functional model for application plane of off-network MCData service
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.3 Functional entities description
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.3.0 General
| Each subclause is a description of a functional entity and does not imply a physical entity.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.3.1 Application plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.3.1.1 MCData client
| The MCData client functional entity acts as the user agent for all MCData application transactions. The client supports SDS, file distribution, data streaming and IP connectivity MCData capabilities utilized by MCData services like conversation management, robots control, enhanced status, database enquiries and secured... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.3.1.2 MCData server
| The MCData server functional entity provides centralised support for MCData services suite. Conversation management, robots, enhanced status, database enquiries and secured internet MCData services requiring one-to-one or group data communication are realized using SDS, file distribution, data streaming and IP connecti... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.3.1.3 MCData user database
| This functional entity contains information of the MCData user profile associated with an MCData ID that is held by the MCData service provider at the application plane. The MCData user profile is determined by the mission critical organization, the MCData service provider, and potentially the MCData user.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.3.1.4 Interworking function to LMR system
| The functional entity is specified in 3GPP TS 23.283 [18].
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.3.1.5 MC gateway server
| The MC gateway server provides support for MCData interconnection services with a partner MCData system in a different trust domain whilst providing topology hiding. It acts as a proxy for one or more MCData servers in the partner MCData system without needing to expose the MCData servers in the primary MCData system o... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.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].
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.3.3 MCData message store
| The MCData message store is a network base persistent store that allows Mission Critical Organization to configure their MCData users to permanently store their MCData communications. Once configured a MCData user will be allocated a secured storage area (i.e. size) in the MCData message store that is only accessible b... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.3.4 Message store client
| The Message store client is used to support MCData client to manage the MCData communication history stored in MCData message store for a particular MCData user, It supports the secure access to a MCData user's configured MCData message store area and operations relevant to the stored communication history such as fold... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.3.5 MCData notification server
| The MCData notification server provides the centralized notification function in the network. The MCData notification server allows an application (e.g. resident in the UE) to create a communication channel to receive real-time notifications from the network in either Pull or Push mode. Depending on the channel type cr... |
30497b4d3b4268dfe046b8ed41cd63fb | 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... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.4 Reference points
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.4.1 Application plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.4.4.1.1 General
| The reference points for the application plane of MCData service are described in the following subclauses.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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 ... |
30497b4d3b4268dfe046b8ed41cd63fb | 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 use... |
30497b4d3b4268dfe046b8ed41cd63fb | 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].
|
30497b4d3b4268dfe046b8ed41cd63fb | 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 mess... |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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... |
30497b4d3b4268dfe046b8ed41cd63fb | 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 notifica... |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.5 Functional model for short data service
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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 SD... |
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.5.3 Functional entities description
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.5.3.1 Application plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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 referenc... |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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].
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.5.4 Reference points
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.5.4.1 Application plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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... |
30497b4d3b4268dfe046b8ed41cd63fb | 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 M... |
30497b4d3b4268dfe046b8ed41cd63fb | 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 poin... |
30497b4d3b4268dfe046b8ed41cd63fb | 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].
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.6 Functional model for file distribution
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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... |
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.6.3 Functional entities description
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.6.3.1 Application plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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 foll... |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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 ensu... |
30497b4d3b4268dfe046b8ed41cd63fb | 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 dow... |
30497b4d3b4268dfe046b8ed41cd63fb | 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 ... |
30497b4d3b4268dfe046b8ed41cd63fb | 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].
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.6.4 Reference points
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.6.4.1 Application plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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 a... |
30497b4d3b4268dfe046b8ed41cd63fb | 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 suppo... |
30497b4d3b4268dfe046b8ed41cd63fb | 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.... |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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 operatio... |
30497b4d3b4268dfe046b8ed41cd63fb | 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 ... |
30497b4d3b4268dfe046b8ed41cd63fb | 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].
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.7 Functional model for data streaming
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.7.2 Off-network functional model
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.7.3 Functional entities description
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.7.3.1 Application plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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;
- replica... |
30497b4d3b4268dfe046b8ed41cd63fb | 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 th... |
30497b4d3b4268dfe046b8ed41cd63fb | 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].
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.7.4 Reference points
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.7.4.1 Application plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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 ... |
30497b4d3b4268dfe046b8ed41cd63fb | 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 referenc... |
30497b4d3b4268dfe046b8ed41cd63fb | 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 inter... |
30497b4d3b4268dfe046b8ed41cd63fb | 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].
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.8 Functional model for IP connectivity
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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 sessi... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.8.2 Off-network functional model
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.8.3 Functional entities description
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.8.3.1 Application plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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... |
30497b4d3b4268dfe046b8ed41cd63fb | 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 pol... |
30497b4d3b4268dfe046b8ed41cd63fb | 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].
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.8.4 Reference points
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 6.8.4.1 Application plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.